General Information

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

The action parameters (DO statements) in the rule can be performed either immediately upon detection of the data set event, or at the end of the jobstep that caused the data set event. For information on how the time and conditions of execution are determined, see "STEPRC" in ON DSNEVENT: Message/Event Selection Parameter.

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 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.

ON DSNEVENT rules do not intercept data set events (for example, cataloging, uncataloging, or scratching) when they are performed through z/OS CATALOG or SCRATCH macros.

Note: When the IDCAMS IBM utility is used to delete a file, it verifies the existence of the file by using file data set events with a disposition of RETAIN. It does not create any data set events with a disposition of DELETE.

The following System variables can be specified in ON DSNEVENT rules:

• %%$DSN (data set name)
• %%$DSNDISP (data set disposition)
• %%$Dn (qualifiers of the data set name).

For more information about those variables, see AutoEdit Facility.

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

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.

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 you enter S*13, the code criteria are satisfied by codes such as S013, S613, S913.

When specifying condition or abend codes, the following qualifiers can be used as indicated:

• > (Greater than) – valid for condition codes and user abend codes
• < (Less than) – valid for condition codes and user abend codes
• N (Not exist) – triggers the rule if the specified code does not exist in the step
  Valid as a qualifier for condition codes, user abend codes, and system abend codes.

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.

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