IBM MQ parameters

Specifies that BMC AMI Ops Automation for MQ should automatically enable instrumentation events for a queue manager during connection if it is not already enabled

You can specify that all, none of selected events are enabled. When you specify multiple event types, you must code them consecutively, without using blank spaces or commas (does not apply if you are specifying Y or N). Valid values are as follows:

• N: Do not enable any events
• Y: Enable all events
• S: Enable start/stop (strstpev) events
• L: Enable local (localev) events
• I: Enable inhibit (inhibtev) events
• P: Enable performance (perfmev) events
• R: Enable remote (remoteev) events
• F: Enable configuration (configev) events
• M: Enable command (cmdev) events
• C: Enable channel (chlev) events
• V: Enable ssl (sslev) events
• B: Enable bridge (bridgeev) events
• X: Enables non-display command events (CMDEV(NODISPLAY))

The default value is NO.

Specifies the action BMC AMI Ops Automation should take when the product attempts to listen to a queue which is defined as GET(DISABLED)

Possible settings are

• JRNL: Issue a message to the BBI Journal stating that BMC AMI OpsA cannot listen to the queue.
• WTO: Issue a write-to-operator (WTO) message stating that BMC AMI OpsA cannot listen to the queue.
• IGNORE: Take no action.
• ALTER: Alter the queue to GET(ENABLED).

The default value is JRNL.

Specifies the action BMC AMI OpsA should take when the product attempts to listen to a queue which is defined as NOSHARE. Possible settings are

• JRNL: Issue a message to the BBI Journal stating that BMC AMI OpsA cannot listen to the queue.
• WTO: Issue a write-to-operator (WTO) message stating that BMC AMI OpsA cannot listen to the queue.
• IGNORE: Take no action.
• ALTER: Alter the queue to share.

The default value is JRNL.

Specifies the name of the IBM MQ Event Listener PROC

Do not use this parameter if the IBM MQ Event Listener is not required. For more information about the IBM MQ Event Listener and coexistence of BMC AMI OpsA and other BMC products that require the IBM MQ event queues, see Automating-IBM-MQ-events.

Specifies whether BMC AMI Ops Automation for MQ should open and listen for messages on QALIAS type queues

For example, if the selection criteria for a Rule for messages going to the base queue does not specifically contain the queue name then the Rule might fire twice; once for the base queue and once for the alias queue.

Specifies an AlternateUserid to be specified when issuing MQSC or PCF MQ commands from BMC AMI OpsA

The user ID is used when MQ commands are issued from an EXEC or from a Rule.

There is no default; valid values are as follows:

• RACF: specifies that the security ID of the BBI-SS PAS is used as the AlternateUserid for commands
• user ID: specifies that a valid user ID is used as the AlternateUserid

This global parameter can be overridden with the ALTUSER() | AU() parameter of the IMFEXEC CMD TYPE(MQS) command or as an action from a MQ initiated Rule. When you use this parameter the MQ PUT1 options will include MQOO_ALTERNATE_USER_AUTHORITY, MQPMO_DEFAULT_CONTEXT and MQPMO_ALTERNATE_USER_AUTHORITY and the AlternateUserid will be placed in the object descriptor.

For more information about the IMFEXEC CMD TYPE(MQS) and issuing MQ commands from Rules, see Automating-IBM-MQ-events.