z/OS Job Monitor Event

z/OS job monitors watch jobs for status changes.. You can specify fully qualified job names, program names, or step names or use wildcards in any field.

z/OS Job Monitor Properties

The fields displayed depend on the Event Type selected.

This table describes the z/OS Job Monitor Properties:

Field

Description

Event Type

Event Type. Available options:

Start of job
End of job
Abnormal end of job
Start of program
End of program
Abnormal end of program
End of step
Abnormal end of step

Start of program events may be reported even when the program does not execute. Start of program is detected by an IEFUSI SMF exit. IEFUSI exit routines receive control before the initiator checks to determine whether the job step will actually execute. That is, IEFUSI receives control before the system performs testing for COND and IF/THEN/ELSE/ENDIF, including ABENDs. This means that IEFUSI will always be called and start of program will be recorded, regardless of whether the step will execute.

Job

Job Name

Program

Program Name

Procedure Step

Procedure step name

Step

Step Name

For each of these names, either enter a fully qualified name or use wildcards according to these rules:

Wildcard	Description
?	A question mark (?) specifies the match of one character.
*	An asterisk (*) specifies a match of zero to any number of characters.

Event Tokens

This table describes the attributes, as tokens, returned from the agent to the scheduler when an event occurs. These tokens can be mapped to process variables in the event trigger definition.

Token	Description
[EVENT.ATTRIBUTE.EVENTTYPE]	Event Type
[EVENT.ATTRIBUTE.JOBNAME]	Job Name
[EVENT.ATTRIBUTE.PROCSTEPNAME]	Process step name
[EVENT.ATTRIBUTE.STEPNAME]	Step Name
[EVENT.ATTRIBUTE.PROGRAMNAME]	Program name