Defining WebSphere MQ objects

Use the WebSphere MQ for z/OS operations and control panels, or one of the other WebSphere MQ for z/OS command input methods, to define WebSphere MQ for z/OS objects. Refer to the WebSphere MQ Script (MQSC) Command Reference book for details of defining objects.

You define:

• A local queue with the usage of (XMITQ) for each sending message channel.
• Remote queue definitions.

  A remote queue object has three distinct uses, depending upon the way the name and content are specified:

  • Remote queue definition
  • Queue manager alias definition
  • Reply-to queue alias definition

  This is shown in Table 2.

• A process naming the MCA sender transaction, CKSG, as the application to be triggered by messages appearing on the transmission queue. The process definition parameter, USERDATA, must contain the name of the channel to be started by this process. See How to trigger channels.

The supplied sample CSQ4DISQ gives examples of the necessary definitions.

Multiple message channels per transmission queue

It is possible to define more than one channel per transmission queue, but only one of these channels needs to be active at any one time. The provision of multiple channels is recommended to provide alternative routes between queue managers for traffic balancing and link failure recovery.

You may start more than one channel to serve a transmission queue to increase message throughput, but when doing so, ensure that the queue has a SHARE attribute, and that there is not a need for sequential delivery of messages.