Defining Actions for Messages
SA z/OS allows you to define actions (commands or replies) for Application (APL), Monitor Resource (MTR), and MVS Component (MVC) policy entries.
The following information describes how to define commands or replies as actions. For example, suppose that you need to define a command action for a message XYZ222I for the HSM application, where XYZ222I is a new message that is not predefined by SA z/OS.
- The first step is to select an entry type (APL, MTR, or MVC) on the Entry Type Selection panel and a specific entry, which leads to the Policy Selection panel. In this example, select the APL entry type and the HSM application.
- On the Policy Selection panel, select MESSAGES/USER DATA policy item, which leads to the Message Processing panel. It's where you can define actions for messages.
- Specify the ID of the message that you want to automate. You can use system automation symbols
(AOCCLONE variables) or system symbols in message IDs. These symbols are resolved when AT and MRT
are loaded, but cannot be resolved for MPF.
Out of the box, SA z/OS supports trapping messages only by message IDs and a few other conditions that can be specified on the Message Processing panel. If these capabilities are not sufficient, you can define the AT entry yourself by defining an AT Override.
In this example, enter the message ID XYZ222I.
Message Processing Line 00000001 Col 001 075 Entry Type : Application PolicyDB Name : USER_PDB Entry Name : MYAPL Enterprise Name : USER_ENTERPRISE Line Commands: S/C (Cmd), R (Rep), K (Cod), U (Usr), A,M (AT, MRT, MPF) I, D (insert or delete lines), CN (Class Name) Message ID field length. . 16 (1 - 32) Cmd Message ID Description C R K U A M F c XYZ222I - Enter R (reply) or C (command) in the column next to the specified
message ID, and define the specific command or reply action on the displayed Reply
Processing or Command Processing panel.
In this example, enter C and define the following command for XYZ222I.
Command Processing : XYZ222I Line 00000001 Col 001 075 Mixed case . . . NO (YES NO) Cmd Ps/Select AutoFn/* Command Text MSG OPER1 ***RETRIEVED MESSAGE XYZ222I *** - After your reply or command definition, press PF3 to return to the Message
Processing panel. Issue A or M in the Cmd column next to the
specified message ID, the AT, MRT, and MPF entries that SA generated based on your specification are
then
displayed.
Message Automation Overview AC AT condition MS MRT action selection MF MPFLSTxx specifications AS AT status MO MRT override IG Ignore for AT, MRT, MPF AO AT override Message ID : XYZ22I Generated AT entry : IF MSGID = 'XYZ22I' THEN EXEC(CMD('ISSUEACT') ROUTE(ONE %AOFOPGSSOPER%)); Generated MRT entry : UPON ( MSGID = 'XYZ22I' ) REVISE('Y' AUTOMATE) Generated MPF entry : XYZ22IThis definition leads to the creation of an AT entry for message XYZ222I using the ISSUEACT command after the next configuration build process. If you want to pass parameters to ISSUEACT, you can do so as described in Defining AT Overrides.
For messaged defined in the MESSAGES/USER DATA policy item for MVS Components (MVC), the parameter SYSTEMMSG=YES is added to the generated ISSUEACT command.
For more information about ISSUEACT, see ISSUEACT (ISSUECMD, ISSUEREP) in Programmer's Reference.