Verifying tracking events

The next verification phase is to check that the tracker is collecting tracking-event information and writing it to the event data set (EQQEVDS).

Tivoli Workload Scheduler for z/OS job tracking works correctly only if it receives information about status changes for all jobs or started tasks to be tracked. Job tracking gets this information from SMF and JES exits. These exits gather the necessary information, and an exit record is added to the Tivoli Workload Scheduler for z/OS event-writer queue via ECSA buffers.

The event writer

The event writer removes the event from its queue and creates an event record that is written to an event data set. The event writer also forwards the event if it has been started with an event-reader function. If a separate event reader is used, the event is read from the event data set. In either case, the reader task uses the connection with the controller to transfer the event to a queue at the controller. The event-manager subtask then processes the event and the current plan is updated.

The event data set

The event data set is needed to even out any difference in the rate that events are being generated and processed, and to prevent events from being lost if the Tivoli Workload Scheduler for z/OS address space or a subtask must be restarted. The first byte in an exit record is A if the event is created on a JES2 system, or B if the event is created on a JES3 system. This byte is found in position 21 of a standard event record, or position 47 of a continuation (type N) event. Bytes 2 and 3 in the exit record define the event type. These event types are generated by Tivoli Workload Scheduler for z/OS for jobs and started tasks:

1: Reader event. A job has entered the JES system.
2: Job-start event. A job has started to execute.
3S: Step-end event. A job step has finished executing.
3J: Job-end event. A job has finished executing.
3P: Job-termination event. A job has been added to the JES output queues.
4: Print event. An output group has been printed.
5: Purge event. All output for a job has been purged from the JES system.

If any of these event types are not being created in the event data set (EQQEVDS), a problem must be corrected before Tivoli Workload Scheduler for z/OS is started in production mode.

Notes:

The creation of step-end events (3S) depends on the value you specify in the STEPEVENTS keyword of the EWTROPTS statement. The default is to create a step-end event only for abending steps in a job or started task.
The creation of print events depends on the value you specify in the PRINTEVENTS keyword of the EWTROPTS statement. By default, print events are created.

Perform these actions to verify that events are being created on your system:

Run a job:
1. Submit a job like the following, ensuring that the output is written to a non-held output class:
  Test job
```
//VERIFY1  JOB   STATEMENT PARAMETERS



//VERIFY   EXEC  PGM=IEBGENER
//*
//SYSPRINT DD DUMMY
//SYSUT2   DD SYSOUT=A
//SYSIN    DD DUMMY
//SYSUT1   DD *
    SAMPLE TEST OUTPUT STATEMENT 1
//*
```
2. Verify that the job has executed, printed, and purged.
3. Browse the EQQEVDS data set using the ISPF/PDF browse facility. You should find these events on the event data set:
  - Type 1 event
  - Type 2 event
  - Type 3J event
  - Type 3P event
  - Type 4 event
  - Type 5 event.
  The events are prefixed with A for JES2 or B for JES3. You might also find type 3S as events, depending on the value specified on the STEPEVENTS keyword of the EWTROPTS initialization statement.
Repeat step 1 for a started task.