+

Search Tips | Advanced Search

CSQINP1 and CSQINP2 input data sets changed on z/OS

The CSQINP1 and CSQINP2 initialization input data sets changed in Version 7.1. The data sets include more samples and the contents of some samples have been moved to other samples. Particular changes to take note of are the commands to define queues to hold publish/subscribe state information. The commands must be in the right order.


Important changes to initialized input data sets since IBM WebSphere MQ Version 7.1 on z/OS

Review the changes, and update the customized versions you are currently using as required, if your enterprise is using IBM WebSphere MQ Version 7.0.

The queue manager uses queues to hold persistent state information about publish/subscribe. Durable subscriptions are held as messages on SYSTEM.DURABLE.SUBSCRIBER.QUEUE and retained publications on SYSTEM.RETAINED.PUB.QUEUE.

The ordering of the definitions of these queues is important. Member CSQ4MSTR of SCSQPROC shows the necessary ordering of the supplied definitions in the CSQINP2 concatenation. The default system subscription, SYSTEM.DEFAULT.SUB, requires SYSTEM.DURABLE.SUBSCRIBER.QUEUE that in turn requires the storage class SYSLNGLV, which is defined in CSQ4INYS. If you migrating from a previous release, and modifying customized procedures, define these resources in the following order:
  1. Storage class SYSLNGLV. It requires a defined mapping to a defined page set.
  2. SYSTEM.DURABLE.SUBSCRIBER.QUEUE
  3. SYSTEM.DEFAULT.SUB
Note:

The changes to CSQINP1 and CSQINP2 are required in Create procedures for the IBM MQ queue manager and Customize the initialization input data sets.