General Information

ON STEP rules are triggered when specified job steps terminate with specified return codes or statuses.

Specification of values for the PROCSTEP, PGMSTEP, and STEPRC optional subparameters limit the situations that can satisfy the step termination event. Conversely, if a subparameter is blank, that subparameter is ignored. For example:

• If PGMSTEP and PROCSTEP values are both specified, the rule is triggered only if the specified PGMSTEP is completed in the specified PROCSTEP procedure.
• If a PGMSTEP value is specified without a PROCSTEP value, the rule is triggered if the PGMSTEP is completed anywhere within the job stream.

Note:

To monitor data set events for a job, started task or TSO user, the job, started task or TSO user must have MSGLEVEL set to (1,1) and the IEF403I message or the IEF125I message should appear on the job log.

A DSNEVENT can be triggered only on the Control-O/CMEM that runs on the same z/OS system on which the event occurs. Even a focal Control-O or CMEM in a Sysplex environment is insufficient. This is because Control-O or CMEM intercepts the messages written to JESYSMSG while they are being written, which can be done only on the same system where the event happens.

The SMFID and SYSTEM Subparameters

The default values for the SMFID and SYSTEM subparameters are the current system. If no value is specified for either SMFID or SYSTEM, the rule is triggered only by events that occur in the current system.

The STEPRC Subparameter

When specifying a condition code or abend code in the STEPRC subparameter, any characters in the code can be replaced by an asterisk (*). An asterisk means "any value" for the character it replaces. For example, if S*13 is specified, the code criteria is satisfied by codes such as S013, S613, S913. When specifying condition and abend codes, the following qualifiers shown in Table 166 can be used as indicated.

Table 166 STEPRC ON STEP Subparameter Qualifiers