Upgrading connections with WebSphere MQ

If you use the CICS-WebSphere MQ adapter, bridge, trigger monitor, or API crossing exit to connect CICS® to WebSphere® MQ, you have some changes to make when you upgrade your version of CICS®.

All versions

Specify the new versions of WebSphere MQ libraries in the STEPLIB and DFHRPL concatenation

You must replace the existing versions of the WebSphere® MQ libraries with the new ones in the STEPLIB and DFHRPL concatenation in your CICS procedure.The libraries are thlqual .SCSQAUTH, thlqual .SCSQCICS, and thlqual .SCSQLOAD, where thlqual is the high-level qualifier for the WebSphere MQ libraries. The SCSQAUTH library is included in both concatenations, but the SCSQLOAD library and the optional SCSQCICS library are included in the DFHRPL concatenation only. Include the WebSphere MQ libraries after the CICS libraries to ensure that the correct code is used.

V4.1

Exploit new WebSphere MQ Version 7 API calls

New or changed CICS applications that use the new API calls in WebSphere MQ Version 7 must be link-edited with the WebSphere MQ API stub modules that are shipped with CICS .

The new API calls are MQBUFMH, MQCB, MQCTL, MQCRTMH, MQDLTMH, MQDLTMP, MQINQMP, MQMHBUF, MQSETMP, MQSTAT, MQSUB, and MQSUBRQ. These Version 7 API calls are only supported in CICS when you use the stubs shipped with CICS , not the stubs shipped with WebSphere MQ. New and existing CICS applications that do not use the Version 7 API calls can use the stubs shipped with CICS or WebSphere MQ.

If you use the new Version 7 API calls MQCB and MQCTL for asynchronous message consumption by CICS applications, you must code your program using information given in the CICS documentation, in addition to the WebSphere MQ programming documentation. The requirements for asynchronous message consumption in a CICS environment are listed in Asynchronous message consumption and callback routines in the IBM Knowledge Center.

Replace existing mechanisms for managing instances of CKTI transactions with MQMONITOR resources

To complement the existing MQCONN resource, CICS TS 5.4 introduced the MQMONITOR resource definition and new EXEC CICS and CEMT commands for the CICS-WebSphere MQ monitor.

Before CICS TS 5.4, you cannot start more than one instance of CKTI against the same initiation queue from a single CICS subsystem. When the MQ connection is disconnected and then reconnected, CKTI has to be manually restarted.

The new MQMONITOR resource provides a better mechanism for managing instances of CKTI transactions. It is recommended that you replace existing mechanisms for managing instances of CKTI transactions with MQMONITOR resources. The benefits are as follows:

  • You can have more than one MQMONITOR resource monitoring an MQ initiation queue. Any number of MQMONITOR resources can be defined and installed in a CICS region.
  • An MQMONITOR can be configured to start the associated transaction (for example, CKTI) automatically when the MQ connection is established. Using the MQMONITOR resource removes the need to use the CKQC transaction to start and stop monitors manually.
  • Configuration options include the ability to specify a transaction ID to be used by the monitor, the user ID under which a monitor task runs, and the user ID to be used by the monitor to start the application tasks if an alternative user ID is not provided by the application. These options allow better security controls.

Follow Setting up a MQMONITOR resource for the CICS-WebSphere MQ bridge to define and install an MQMONITOR for monitoring an MQ initiation queue.

You can use new EXEC CICS and CEMT commands to work with the MQMONITOR resource definition. You can also use the SET MQMONITOR command to start and stop a CICS-WebSphere MQ monitor, as an alternative to issuing CKQC commands.

Replace existing mechanisms for managing instances of CKBR transactions with MQMONITOR resources

The recommended method of controlling the CICS-WebSphere MQ bridge transaction CKBR is to use an MQMONITOR resource. Doing so allows the bridge to automatically restart when the connection to the WebSphere MQ manager is established.

Follow this procedure to set up an MQMONITOR for the CICS-WebSphere MQ bridge.



upgrade_mq.html | Timestamp icon Last updated: Sunday, 4 June 2017