Parameters for BBPARM member AAOPRMxx

The following table describes the parameters contained in BBPARM member AAOPRMxx for the BMC AMI Ops Automation for MQ component.

You can specify that each BBI-SS PAS use its own AAOPRMxx member where xx is a user-specified two-character suffix. In the UBBPARM member CFGssidA (where ssid is the subsystem ID), specify the AAOPRMxx member name for the subsystem. For more information, see Customizing-BMC-AMI-Ops-Automation-after-installation.

Parameter	Description
MQALTUSR=[RACF \| user ID]	Specifies an AlternateUserid to be specified when issuing MQSC or PCF MQ commands from BMC AMI Ops Automation 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 (IBM RACF) specifies that the security ID of the BBI-SS PAS is used as the alternate user ID for commands. User ID specifies that a valid user ID is used as the alternate user ID. This global parameter can be overridden with the ALTUSER() \| AU() parameter of the IMFEXEC CMD TYPE(MQS) command or from the Rule panel where you define a command that initiated from a MQS 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 alternate user ID will be placed in the object descriptor. See CMD-Issue-a-command-to-IBM-MQ-with-response for more information about the IMFEXEC CMD TYPE(MQS) and issuing MQ commands from Rules.
MQAUPRMS=[Y \| N]	Specifies whether individual MQSC or PCF MQ commands that are issued from EXECs or Rules can use the ALTUSER parameter to override the global parameter MQALTUSR (when specified) and specify an AlternateUserid When no value is specified for the MQALTUSR parameter, this parameter allows or denies the use of AlternateUserid for MQ command. Default value is NO, which means that the ALTUSER value is ignored.
MQDEBUG= [Y\| N]	Specifies whether or not to turn on MQ debugging messages Default value is NO. Use only at the direction of BMC AMI OpsA Support team and be aware that this setting can generate large amounts of output.
MQEV=Y\|N (or any combination of SLIPRFMCVB) Example 1 MQEV=PFMC specifies BMC AMI Ops Automation for MQ to enable Performance, Configuration, Command and Channel events Example 2 MQEV=Y specifies BMC AMI Ops Automation for MQ to enable SLIPRF (Start, Stop, Local, Inhibit, Performance and Remote and Config) events only Example 3 MQEV=SLIPRFMCVB specifies that BMC AMI Ops Automation for MQ enable ALL event types Example 4 MQEV=SLIPRFMCVB specifies that BMC AMI Ops Automation for MQ enable ALL event types except for CMDEV which should be set to CMDEV(NODISPLAY)	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 BMC AMI Ops Automation for MQ enables All of the instrumentation events (applies to the SLIPRF types only) None of the instrumentation events Selected instrumentation events Specifying multiple types (other than Y or N) must be coded consecutively without blanks or commas. Valid values are N - Do not enable any events. Y - Enable all events (SLIPRF types only). S - Enabled 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 - Enable non-display command events The default value is NO.
QALIAS=[Y \| N]	Specifies whether BMC AMI Ops Automation for MQ should open and listen for messages on QALIAS type queues Note If you specify an alias queue name in BBPARM AAOMQLxx in addition to specifying a base queue, any Rules that you have written for a message for the base queue might also fire for the alias queue. Example If the selection criteria for a Rule for messages going to the base queue does not specifically contain the queue name, the Rule might fire twice; once for the base queue and once for the alias queue.
MQGINHIB=xxxxxxxx\| JRNL	Specifies the action BMC AMI OpsA should take when BMC AMI OpsA attempts to listen to a queue that 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.
MQNSHARE=xxxxxxxx\| JRNL	Specifies the action BMC AMI OpsA should take when BMC AMI OpsA attempts to listen to a queue that 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.
MQEVLPRC=xxxxxxxx	Specifies the name of the IBM MQ Event Listener PROC Only use this parameter if the IBM MQ Event Listener is required. Refer to Setting-up-BMC-AMI-Ops-Automation-for-MQ-to-co-exist-with-BMC-Performance-Manager-for-IBM-MQ-for-z-OS-and-OS-390 for more information about the IBM MQ Event Listener and co-existence of BMC AMI OpsA and other BMC Software products that require the IBM MQ event queues.

The following sections describe which actions are taken, based on the parameters setting that you specify in BBPARM member AAOPRMxx described in above table, when BMC AMI OpsA tries to automate IBM MQ events.

This section contains the following topics:

Parameters for BBPARM member AAOPRMxx

On this page