Action Specification for MQS panels
- The Action Specification(s) - MQS panels I and II, shown in Action Specification(s) I - MQS panel and Action Specification(s) II - MQS panel, are two panels that are used for specifying an action when a MQS Rule fires.
- The ALERT Action(s) panels are where you can create a BMC AMI Ops Automation ALERT as part of the Rule’s action. For more information, refer the Using-Rules-with-BMC-AMI-Ops-Automation
- The BMC EM/SIM Event Action panel - MQS panel allows you to send events from BMC AMI OpsA to a BMC Impact Manager cell. For more information, refer to the Using-Rules-with-BMC-AMI-Ops-Automation.
In addition, you can the Remove DLH field to remove a Dead Letter Header or you can copy a message by specifying a IBM MQ queue name in the Destination Queue Manager field.
Action Specification(s) I - MQS panel
COMMAND ===> TGT --- JB71
Rule-set === AAORUL00 Rule-id === NEWMQ
Automation Actions:
Journal ===>
* Exec Name/Parms ==> VARDISP G(Y) Q(Y) MQ51(Y) E51(Y)
* Cmd(Type MQ ) ===>
* Issue Msg( WTO ) =>
POST Target ===>
POST ID ===>
POST Parms ===>
MQ Automation Actions:
Keep Message ===> YES (Yes or NO) Remove DLH ===> (Yes or No)
Destination Que ===>
Destination QMgr ===>
* Enter a question mark(?) and blank in any field on the line for more options.
Press ENTER to continue, END return to Detail Control, CANCEL to cancel changes
Action Specification(s) II - MQS panel
COMMAND ===> TGT --- JB71
Rule-set === AAORUL00 Rule-id === NEWMQ
Send (TSO IDs) ===>
DOM Id ===> Delete Operator Message
Set IOA Variable ===> ===>
Press ENTER to continue, END return to Detail Control, CANCEL to cancel changes
The following table describes the Action Specification - MQS fields for panel I and II.
Field name | Description |
|---|---|
Journal | This field specifies whether the message will be recorded in the BBI-SS PAS Journal. Valid values are YES, NO, and REW. The default is NO. A value of REW copies a reworded message to the BBI-SS PAS Journal. Use REW with the Reword Msg field. |
EXEC Name/Parms | This field allows up to 56 characters and is used to schedule an EXEC to perform advanced automation that cannot be performed by a Rule. Local and SHARED variables are valid. The EXEC parameters may be specified, which are passed when the EXEC is scheduled for execution.
To display a separate panel where you can enter an EXEC name and additional parameters, enter a question mark (?) and a blank in this field. For more information about the REXX Exec or CLIST panel, refer to Using-Rules-with-BMC-AMI-Ops-Automation. |
Cmd(Type) | This field allows up to 126 characters and is used to issue one or more console commands. Local and SHARED variables are valid. The following list shows command types and origin:
If the Rule event type is not MQS or the targeted local-system z/OS queue manager is not the queue manager firing the Rule, MQ commands must begin with the name of the queue manager processing the specified command. For example: queuemgrname: command text Optional keywords for command type MQ:
|
Cmd(Type) (continued) |
To display a separate panel where you can enter commands and additional parameters, enter a question mark (?) and a blank in this field. For more information about the Command(s) panel, refer to Using-Rules-with-BMC-AMI-Ops-Automation. |
Cmd(Type) (continued) | |
Set Variable | In the first entry, up to 33 characters are allowed. In this field specify the name of the variable to be modified. Only SHARED variables will be created or updated. SHARED and local variables and constants may be used to create the variable name. In the second entry, up to 17 characters are allowed. SHARED and local variables and constants are valid. Use this field to assign a new value (using a variable or unsigned constant) or modify (using a signed constant).
|
DOM ID | This field allows up to 33 characters and is used to allow a Rule to issue a Delete Operator Message (DOM) to delete a highlighted message from the operator console.
|
Issue WTO Msg | This field allows up to 125 characters and allows a Rule to issue a message to a console (Write To Operator). Specify the message you would like issued to the operator console. The message is issued without routing or descriptor codes. The message may be selected by another Rule.
To display a separate panel where you can enter messages and additional parameters, enter a question mark (?) and a blank in this field. For more information about the Command(s) panel, refer to Using-Rules-with-BMC-AMI-Ops-Automation. |
POST Target | This field specifies the SSID of the target BBI-SS PAS that will execute the POST action of an EXEC. If this field is not specified, the target is the local BBI-SS PAS that fires the Rule. The target name can be 1-32 characters in length and can be a variable name. |
POST ID | This field specifies the matching name information which is specified in one EXEC’s WAIT parameter that causes another waiting EXEC to be POSTed to run The POST ID can be 1-32 characters long and may be a variable name. For example, to post an EXEC that is waiting for the name of WAITFORME, enter WAITFORME in this field. |
POST Parms | When you are using the POST function in a Rule, you can specify optional parameter information that is passed in the IMFPOST variable to the waiting EXEC. The POST Parms value can be 1-56 characters and special characters and embedded blanks are supported. One or more variable names are allowed in this field. |
Keep Message | You can enter Yes or No to specify whether or not to keep the message in the source IBM MQ queue.
An entry in this field is not required. The default is Yes. |
Destination Queue | You can enter up to 48 characters in this field for the name of the IBM MQ queue to copy/move messages to.
Using 'Keep Message=NO and Destination Queue' causes a message to be moved from one queue to another while 'Keep Messages=YES and Destination Queue' causes a message to be copied from one queue to another. If Keep(YES) and destination queue are both specified, the Keep/Copy will be synchronized. |
Remove DLH | During a Copy or Move operation, if YES is specified in this field, the original dead letter message is rebuilt by removing the Dead Letter Header and restoring the original Encoding, CodedCharSetId and Format fields back into the message descriptor. Using this function, you can strip a dead letter message of all information regarding dead letter processing and forward it to an alternate queue for normal processing. In addition, when using this option, a message passed to a Rule-scheduled EXEC will not contain the Dead Letter Header. |
Destination Mgr | A queue manager to which the message is targeted during a Copy or Move operation can be specified in this field. Without this specification, the message is PUT to a destination queue on the current queue manager for which the Rule fired. To use this field, the Destination Queue field must be set. The specified queue manager ID is placed into the object descriptor so that normal IBM MQ queue and queue manager resolution take place. |
Set IOA Variable | This field sets the value of any global IOA variable. The request to set an IOA variable is sent to all subscribing Control-O and CMEM regions (or both) in the local LPAR. From there it can be sent to other INCONTROL products in the sysplex that are using INCONTROL resources and facilities. You can use this set of fields to assign a new variable value by using a BMC AMI OpsA variable, character string, or an unsigned constant in the second field.Valid values are as follows:
|