dfhe5_cicsmq.html |
Last updated: Saturday, 15 June 2019If you use the CICS-WebSphere MQ adapter, bridge, trigger monitor, or API crossing exit to connect CICS® to WebSphere® MQ, check your configuration and make any necessary changes.
When you upgrade to a new version or release of WebSphere MQ, ensure that you specify the new versions of the WebSphere MQ libraries in the STEPLIB and DFHRPL concatenations in your CICS procedure, replacing the previous versions of these libraries. 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.
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.
Last updated: Saturday, 15 June 2019