jobname

Name (or mask) of the job to be monitored for data set events. Mandatory.

JTYPE

Type of job that triggered the data set event.

• J – batch job (JOB)
• S – started task (STC)
• T – TSO user (TSU)
• '   ' (blank) – Any type of job. Default. Valid only if STEPRC is blank, when the rule is processed immediately upon detection of the data set event.

If a value is set for JTYPE, only jobs of the specified type will trigger the rule.

SMFID

SMF ID of the CPU to monitor for data set events. Mask characters (* and ?) are supported. The default is the current CPU.

SYSTEM

Name of the system to monitor for data set events. Mask characters (* and ?) are supported. The default is the current system.

DSN

Name of data set (or mask) to be monitored for this event within the selected jobs. Mandatory.

DISP

Data set disposition. Mandatory. The abbreviation (that is, the first letter) of the desired value can be specified. Valid values are:   

• CATLG – Cataloged (including SMS-managed files and ROLLED-IN SMS-managed GDG files).
• DELETE – Deleted.
• UNCATLG – Uncataloged.
• KEEP – Kept (including SMS-managed files).
• RETAIN – Cataloged or Kept.
• SCRATCH – Deleted and uncataloged (SMS managed files).
• NCT2 – Occurrence of a NOT CATLG 2 event – when a data set was created in a previous job step, but not cataloged at deallocation because its name already exists in the z/OS catalog.
• ALL – Any of the above dispositions.
• * – Any of the above data set dispositions, except NCT2.

PROCSTEP

Procedure stepname (or mask) to be monitored for this event within the selected jobs.

This parameter is optional. If omitted, all procedure steps in the selected jobs are monitored.

Note: When a started task is initiated, it can be assigned a task ID. For example, in command S GTF.G, the task ID of GTF is G. If a task ID is not specified, z/OS assigns a default task ID to the started task, as follows:

• For a system started task with stepname IEFPROC, z/OS sets an internal task ID.
• For other started tasks, the default task ID is the procedure (started task) name.

Therefore, when using Control-O to monitor system started tasks, if no task ID is specified in the START command, the PROCSTEP subparameter should not be specified.

PGMSTEP

Program step name (or mask) to be monitored for this event within the selected jobs.

This parameter is optional. If omitted, all program steps in the selected jobs are monitored.

Note: When a system started task with the step name IEFPROC is initiated, z/OS assigns the step a default program step name. Therefore, when using Control-O to monitor these system started tasks, the PGMSTEP subparameter should not be specified.

STEPRC

Determines at what point in the jobstep being monitored the DO statements in the rule are executed. Valid values are:

• value – see below
• '   ' (blank) – If no completion code is specified, the rule is executed immediately upon detection of the specified data set event. Default.

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

If STEPRC is not blank, Control-O will wait until the step ends to trigger the rule. In this case, the DO statements of the rule may not be performed for a very long time. For example, if you set STEPRC to a non-blank value for a TSO user, the rule will not be triggered until the TSO user logs off.

If any of the following values is specified for STEPRC, execution of the DO statements in this rule is delayed until the end of the monitored job step, and is dependent upon how the jobstep is ended.

• OK – step ended with a condition code of 0
• NOTOK – step ended with a non-zero condition code
• **** – step ended with any condition code
• Cnnnn – condition code
• Snnn – system abend code
• Unnnn – user abend code

Asterisks can be specified in place of code digits. Condition codes and abend codes can be preceded by code qualifiers (<, >, N). This is described in General Information.

Note: If you use STEPRC in a long-running task, rules do not execute until tasks such as STC (such as CICS, IMS) or TSO USER terminate.

And/Or/Not

Conjunctional subparameter that permits linking of ON statements. Valid values:

• A (And) – Both statements must be satisfied.
• O (Or) – Only one statement need be satisfied.
• N (Not) – The condition in the following statement must not be satisfied.

For detailed information on this subparameter, see General Information.