Examples

Example 1

This example shows an automation procedure that calls the ISSUEACT command to handle the HSM subsystem message, ARC0027I.

The automation policy is as follows:

Figure 1. DISPACF Sample Panel

AOFK3D0X                  SA z/OS - Command Response      Line  1    of 4
Domain ID   = IPSNO     ---------- DISPACF  ----------    Date = 07/19/00
Operator ID = SAUSER                                      Time = 18:20:45

Command = ACF ENTRY=HSM,TYPE=ARC0027I,REQ=DISP
SYSTEM = KEY3      AUTOMATION CONFIGURATION DISPLAY - ENTRY= HSM
-------------------------------------------------------------------------------
AUTOMATION CONFIGURATION DISPLAY - ENTRY= HSM
 TYPE IS ARC0027I
 CMD             = (,,'MVS S HSMPLOGB')
END OF MULTI-LINE MESSAGE GROUP

The NetView automation table entry to call ISSUEACT is:

IF MSGID = ’ARC0027I’ THEN
EXEC(CMD(’ISSUEACT’) ROUTE(ONE %AOFOPGSSOPER%));

The automation flag to check depends on the phase in the life cycle of the HSM subsystem. If no start up or shutdown is in progress for the application, ISSUEACT checks the recovery flag to validate that automation is allowed before issuing the command. If automation is allowed and message ARC0027I is received for job DFHSM, relating to the HSM subsystem, a command is issued that saves the HSM data set. If message ARC0027I is received for any job other than DFHSM, the message is not automated.

If you specify a clist named MYCLIST instead of an MVS command for the message ARC0027I in the message policy of the customization dialog, this clist can access the original message that triggered ISSUEACT via the named safe AOFMSAFE. Thus you are able to access the message attributes and all lines of a multiline message. The code to access this safe should look similar to the following:

/* MYCLIST */

...

/* Get the message from the SAFE called AOFMSAFE */
"PIPE (STAGESEP | NAME GETMSG)" ,
  "SAFE AOFMSAFE" ,
  "| STEM orig_msg."

...

Exit

Example 2

This example shows how ISSUEACT can be used to automatically respond to WTOR AHL125A, which is issued by GTF during initialization and which allows SA z/OS to accept or reject the trace options that GTF will use.

To enable SA z/OS to automatically accept the trace options, define value U as the reply to message AHL125A. To do this, select the MESSAGES/USER DATA policy item from the Policy Selection panel for the GTF subsystem in the customization dialog. In the Message Processing panel, specify AHL125A as the message ID and call action REP to get the related Reply Processing panel. Specify U in the Reply Text field.

Return to the Message Processing panel.

When you call action OVR, you can see that the automation table entry that will be created during the build process for the automation policy:

IF MSGID = ’AHL125A’ THEN
EXEC(CMD(’ISSUEACT’) ROUTE(ONE %AOFOPGSSOPER%));

ISSUEACT is called without parameters. Therefore the automation flag to be checked depends on the phase in the lifecycle of the GTF subsystem. Because message AHL125A is issued during the initialization of GTF, ISSUEACT checks the start flag to validate that automation is allowed before issuing the reply.

If automation is allowed and message AHL125A is received for job GTFPROD that is related to the GTF subsystem, ISSUEACT replies with value U to accept the trace options and to continue its initialization. If message AHL125A is received for any job other than GTFPROD, the message is not automated.