Security between  BMC AMI Ops Monitor for MQ  and MVS queue managers

Security checking is not required. The omission of security checking minimizes administration time and reduces overhead.

1. If the IBM MQ connection security switch profile is not defined, add profiles to the MQCONN class and authorize the BBI-SS PAS ID for READ access to those profiles.These profiles have the following format:

   ssid.BATCH

   The ssid is the subsystem ID of the queue manager.

   The following example shows this type of profile:

   CSQ1.BATCH

2. If the IBM MQ context security switch profile is not defined, add profiles to the MQADMIN class and authorize the BBI-SS PAS ID for Control access to those profiles.These profiles have the following format:

   ssid.CONTEXT.**

   The following example shows this type of profile:

   CSQ1.CONTEXT.**

3. BMC AMI Ops Monitor for MQ creates reply queues for each local MVS queue manager, which are used for replies to commands. If the queue security switch profile is not defined, add profiles for these reply queues and authorize the BBI-SS PAS ID for ALTER access to the profiles.For more information, see Defining-queue-profiles.

   The reply queue names have the following format:

   prefix.REPLY.
   target

   Reply queue name variables

   Variable	Description
   prefix	Reply-to queue prefix that is defined in the MVS queue manager profile The default prefix value is BBSMVMQS. For more information, see Managing-queue-manager-profiles. For an MVS queue manager that serves as a proxy for a remote queue manager, two reply queues are created with the same prefix (one with the MVS queue manager target name, and one with the remote queue manager target name).
   target	Target name that is defined in the Job Name Table (JNT) BBIJNT00 or on the TGTDEF view in Plex Manager