Factors influencing performance

Performance in the tracker is influenced by:

• The number of events generated on the system.
• The logical record length of the event data set (EQQEVDS) when the restart and cleanup function is used.
• The size of the job logs when JCC or the restart and cleanup function is used.
• A specific event reader subtask started using ERDRTASK(1) rather than EWSEQNO (Event Data Set Sequence Number) in the EWTROPTS. When a specific event reader subtask is started, events are written to the event data set by the event writer subtask and then immediately read back by the event reader task. If the connection method is XCF, NCF, or the controller and tracker are started in the same address space, use EWSEQNO (Event Data Set Sequence Number) instead. When you use EWSEQNO (Event Data Set Sequence Number) the events are queued to the subtask responsible for communication with the event manager at the same time as they are written to the event data set.
• The value defined by ERWAIT, when event reader subtasks are used, identifies the time the task waits before rechecking the event data set if no new events were found at the last attempt.
• Performance in the user exits EQQUX004, EQQUX005, EQQUX006, EQQUX008, and EQQUX010.
• JES performance when the JCC is started or the restart and cleanup function is used to retrieve job logs.