MSGa
A Rule with MLWTO Minor = ALL specified is not evaluated until the entire MLWTO has been issued. In other words, it does not fire until the MLWTO is considered complete by z/OS or when BMC AMI Ops Automation times out. A MLWTO is considered complete when the text line with a text type of E or DE has been received. For more information about message text type codes, refer to the IBM documentation MVS Programming: Assembler Services Reference, Volume 2.
In addition, when you specify MLWTO Minor = ALL, the Rule cannot take the action of suppressing the message or preventing it from being recorded in the CONSOLE or MVS SYSLOG. To perform both automation and suppress the WTO, you can create another Rule for the WTO but create it the same as any other single line WTO, and do not specify any values in "MLWTO Minor" field. Then, ensure this Rule follows the Rule performing the automation actions and also ensure that Rule Set strategy is ALL. Therefore, the action fields Display at Dest and SYSLOG Display (which normally appear for MSG-initiated Rules on the Action Specification panel), do not appear when you specify MLWTO Minor = ALL.
BMC Software recommends that you use the variable &LINEx_WORDn on the Variable Dependencies panel so that you can create Rules that fire based on specific content of the MLWTO where
- &LINEx resolves to the line of the MLWTO message. &LINE1 contains the contents of the major line of the MLWTO and &LINE2 through &LINEx contain the succeeding minor lines.
WORDn resolves to words in &LINE1.
Individual &WORDn variables that are not part of an &LINEx stem variable always refer to words on &LINE1 (the major line).
- LINEx_WORDn resolves to words in the specific line specified with LINEx.
See Example-1-creating-a-Rule-where-MLWTO-minor-ALL for an example.
See Selecting INDIVIDUAL for information about this event type and the automation strategy INDIVIDUAL.