Setting up BMC AMI Ops Automation for MQ to issue commands to distributed queue managers

To set up BMC AMI OpsA to issue commands to a distributed queue manager, you must define the sender and receiver channels, the transmission queue, and both a z/OS and a distributed queue manager alias. Use the following procedure to define a channel, a transmission queue, and queue manager aliases when using TCP as the transmission type.

Related topic

Defining-connectivity

  1. To define the sender channel at the z/OS queue manager, type:

    DEFINE CHANNEL (z/OS-qmgrid.to.distributedqmgrid)+           
               CHLTYPE(SDR)+
               CONNAME (distributed ip address)+
               XMITQ (distributed qmgrid.xmitq)+
               TRPTYPE(TCP)

  2. To define the transmission queue on the z/OS queue manager, type:

    DEFINE QLOCAL (distributedqmgrid.xmitq)+
               USAGE (XMITQ)

  3. To define the receiver channel at the distributed queue manager, type:

    DEFINE CHANNEL (z/OSqmgrid.to.distributedqmgrid)+
               CHLTYPE(RCVR) +
               TRPTYPE(TCP)

  4. To define the z/OS queue manager alias name on the distributed queue manager, type:

    DEFINE QREMOTE (z/OSqmgrid)+
               RQMNAME (z/OSqmgrid)+
               XMITQ (z/OSqmgrid.xmitq)

  5. To define the distributed queue manager alias name on the z/OS queue manager, type:

    DEFINE QREMOTE (distributedqmgrid)+
               RQMNAME (distributedqmgrid)+
               XMITQ (distributedqmgrid.xmitq)

    Important

    You must define queue manager aliases for BMC AMI OpsA to issue commands to distributed queue managers and for responses to return to z/OS.

    If you have not set up BMC AMI Ops Automation for MQ to listen for distributed instrumentation events, you must perform steps 1 through 3 in Setting-up-BMC-AMI-Ops-Automation-for-MQ-to-listen-for-distributed-instrumentation-events.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*