Performing problem determination for tracking events

This section describes how to run problem determination for tracking events if events are missing from the event data set.

Problem determination depends on which event is missing. In the following table, the first column refers to the event type that is missing, and the second column tells you what action to perform.

Table 1. Types of missing event and relative problem determination actions
Type	Problem determination actions
All	Verify in the EELMLOG data set that the event writer has started successfully. Verify that the definition of the EELEVDS ddname in the agent for z/OS started-task procedure is correct (that is, events are written to the correct data set). Verify that the required exits have been installed. Verify that the IEFSSNnn member of SYS1.PARMLIB has been updated correctly, and that an IPL of the z/OS® system has been performed since the update.
KJ1	Verify that the agent for z/OS subsystem was correctly defined.
A1	If event A3P is also missing: Verify that the agent for z/OS version of the JES2 exits 7 and 51 routines have been correctly installed. Use the JES commands `$T EXIT(7)` and `$T EXIT(51)` or `$DMODULE(TWSEXIT7)` and `$DMODULE(TWSXIT51)`. Verify that the JES2 initialization data set contains a LOAD statement and an EXIT7 statement for the agent for z/OS version of the JES2 exit 7 (TWSEXIT7). Verify that the exit has been added to a load module library reachable by JES2 and that JES2 has been restarted since this was done. If event A3P is present in the event data set, call a product service representative for programming assistance.
B1	Verify that the agent for z/OS version of the JES3 exit IATUX09 routine has been correctly installed. Verify that the exit has been added to a load-module library that JES3 can access. Verify that JES3 has been started.
A2 or B2	Verify that the job for which no type 2 event was created has started to execute. A type 2 event will not be created for a job that is flushed from the system because of JCL errors. Verify that the IEFUJI exit has been correctly installed: Verify that the SMF parameter member SMFPRMnn in the SYS1.PARMLIB data set specifies that the IEFUJI exit should be called. Verify that the IEFUJI exit has not been disabled by an operator command. Verify that the correct version of IEFUJI is active. If SYS1.PARMLIB defines LPALIB as a concatenation of several libraries, z/OS® uses the first IEFUJI module found. Verify that the library containing this module was updated by the agent for z/OS version of IEFUJI and that z/OS® has been IPLed since the change was made.
A3J or B3J	Verify that the IEFACTRT exit has been correctly installed. Verify that the SMF parameter member SMFPRMnn in the SYS1.PARMLIB data set specifies that the IEFACTRT exit should be called. Verify that the IEFACTRT exit has not been disabled by an operator command. Verify that the correct version of IEFACTRT is active. If SYS1.PARMLIB defines LPALIB as a concatenation of several libraries, z/OS® uses the first IEFACTRT module found. Verify that this library was updated by the agent for z/OS version of IEFACTRT and that z/OS® has been IPLed since the change was made.
A3P	If A1 events are also missing, follow the procedures described for A1 events. If A1 events are not missing, call a product service representative for programming assistance.
B3P	Verify that the agent for z/OS version of the JES3 exit IATUX19 routine has been correctly installed. Verify that the exit has been added to a load-module library that JES3 can access. Verify that JES3 has been restarted.
A5	Verify that JES2 has purged the job for which no A5 event was created. Ensure that you have not specified TYPE26=NO on the JOBCLASS and STCCLASS statements of the JES2 initialization parameters. If A1 events are also missing, follow the procedures described for A1 events. If A1 events are not missing, call a product service representative for programming assistance.
B5	Verify that JES3 has purged the job for which no B5 event was created.