General Information for ON DSNEVENT (CMEM)

ON DSNEVENT rules are triggered by the setting of data set disposition at time of deallocation (during step termination or dynamic deallocation).

DO statements in the rule are executed either immediately upon detection of the data set event or at the end of the job step that caused the data set event, depending on the value entered in the STEPRC subparameter (described above).

Immediate execution is useful for performing actions when data sets are dynamically de-allocated using long running address spaces (for example, CICS, TSO users, and file transfer monitors).

CMEM must be active before any tasks tracked by ON DSNEVENT rules begin; moreover, ON DSNEVENT rules only intercept data set events for jobs, started tasks, or TSO users that started after the rule was ordered.

Note: To monitor data set events for a job, started task or TSO user, the job, started task or TSO user must have MSGLEVEL=(1,1) and message IEF403I or IEF125I must appear in 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.

ON DSNEVENT rules do not intercept data set events, such as cataloging, uncataloging, or scratching, when they are performed using MVS CATALOG or SCRATCH macros.

The following restrictions apply to ON DSNEVENT statements:

• Do not specify an ON DSNEVENT statement with any other type of ON statement in a rule.
• Do not specify different STEPRC values in the same rule. If you do, the last specified value is used.

Entering values for the optional subparameters PROCSTEP, PGMSTEP and STEPRC limits the situations that can satisfy the step termination event. Conversely, if a subparameter is blank, that subparameter is ignored.

For example,

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

Note: BMC recommends applying a filter on the job name when using DSNEVENT rules. Using a filter will significantly reduce overhead to the system.