Verifying tracking events

This section describes how to check that the agent is collecting tracking event information and writing it to the event data set (EELEVDS).

Job tracking works correctly only if the agent for z/OS receives information about all the status changes of the jobs it submitted. Job tracking gets this information from SMF and JES exits. These exits gather the necessary information, and an exit record is added to the event writer queue of the agent via ECSA buffers. The event writer queue is active also when the agent is not active.

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 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 agent for z/OS 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. Events generated by the agent for z/OS. shows the event types that are generated by the agent for z/OS.

Table 1. Events generated by the agent for z/OS.
Event type	Description	Generated by...
KJ1	Job submission event. A job has been submitted to JES by the agent for z/OS.	Agent
A1	Reader event. A job has entered the JES2 system.	JES2 exits EXIT7 and EXIT51
B1	Reader event. A job has entered the JES3 system.	JES3 exit IATUX09
A2 or B2	Job-start event. A job has started to execute.	SMF exit IEFUJI
A3J or B3J	Job-end event. A job has finished executing.	SMF exit IEFACTRT
A3P	Job-termination event. A job has been added to the JES2 output queues.	JES2 exit EXIT7
B3P	Job-termination event. A job has been added to the JES3 output queues.	JES3 exit IATUX19
A5	Purge event. All output for a job has been purged from the JES2 system.	JES2 exit EXIT7
B5	Purge event. All output for a job has been purged from the JES3 system.	SMF exit IEFU83

If any of these event types are not being created in the event data set (EELEVDS) after the first submission, a problem must be corrected before the agent for z/OS is started in production mode.

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

Run a job from conman or the Dynamic Workload Console:
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 EELEVDS data set using the ISPF/PDF browse facility. You will find the following events in the event data set:
  - Type KJ1 event
  - Type A1 event (for JES2) or type B1 event (for JES3)
  - Type A2 event (for JES2) or type B2 event (for JES3)
  - Type A3J event (for JES2) or type B3J event (for JES3)
  - Type A3P event (for JES2) or type B3P event (for JES3)