Willow banner
Nav0
Home
Nav2
Products
Nav2
Purchase
Nav2
Support
Nav3
About
Nav2
Contact
 

 

 MQ Client for HP-UX (Itanium Edition)

 version 5.3 (32-bit only)

 

Status:  Discontinued.
Supports:  HP-UX 11.23 or later
End of Service: 12/31/2014.  Contact us if you will need support beyond this date.

Notes

Version 5.3 of the 32-bit MQ Client running on HP-UX Itanium (ia64) processors was previously shipped as an IBM product (SupportPac MQC1).  As of October 1st, 2007, responsibility for the product has been transferred to Willow Technology to extend the life and support of this product for those customers who need it.

To purchase either a license or support contract for  MQ Client for HP-UX (Itanium Edition), please contact Willow's sales office.

This client implementation supports 32-bit execution only and is not enabled for Secure Socket Layer (SSL) security .

A MQ client is part of the product that can be installed on its own, on a separate machine from the base product and server. You can run a MQ (MQSeries) application on a WebSphere MQ client and it can interact, by means of a communications protocol, with one or more MQ servers and connect to their queue managers. The servers to which the client connects may or may not be part of a cluster. MQ Family Platforms provides a list of which platforms are supported as MQ Clients and/or Servers.

An application that you want to run in the WebSphere MQ client environment must first be linked with the relevant client library. When the application issues an MQI call, the MQ client code directs the request to a queue manager, where it is processed and from where a reply is sent back to the client. The link between the application and the client code is established dynamically at runtime.

The MQI is available to applications running on the client platform; the queues and other MQ (MQSeries) objects are held on a queue manager that you have installed on a server machine.

POSSIBLE USES Why use MQ clients? Using MQ clients is an efficient way of implementing MQ messaging and queuing. You can have an application that uses the MQI running on one machine and the queue manager running on a different machine, either physical or virtual. The benefits of doing this are:

-There is no need for a full MQ implementation on the client machine. -Hardware requirements on the client system are reduced. -System administration requirements are reduced. -A MQ application, running on a client can connect to multiple queue managers on different systems. -Alternative channels using different transmission protocols may be used.

What applications run on a MQ client? The full MQI is supported in the client environment and this enables almost any MQ application to be relinked to run on a MQ client. Link the application on the MQ client to the MQIC library, rather than to the MQI library. The exceptions are an application that needs syncpoint coordination with other resource managers, and Get(signal) on z/OS.

Note: An application running on a MQ client may connect to more than one queue Manager concurrently, or use a queue manager name with an asterisk (*) on an MQCONN or MQCONNX call.

The application will have to be changed if you want to link to the queue manager libraries instead of the client libraries, as this function will not be available.

Prerequisites:

  • HP-UX B.11.23 (aka 11i version 2.0)
  • TCP/IP SNAplus2 R6.11.23.001
  • HP C/ANSI C compiler C.05.50
  • HP aC++ Compiler C.05.50

Third Party Software:

  • MicroFocus COBOL (Server Express 2.2)

 

[ Home | Products | Purchase | Support | About Us | ContactUs]

Copyright Willow Technology, Inc. 1996-2020.  All rights reserved.
Trademarks | Privacy