Initialization statements

When a tracker is connected with the Z controller (that is, through an XCF, NCF, or TCP/IP connection) or the tracker and Z controller are running in the same address space, the event writer can be used to forward events directly to the Z controller.

When an event writer is started with the EWSEQNO keyword on the EWTROPTS initialization statement, the event writer logs event information on the event data set and adds the event concurrently to the data router queue. The event is not read back from the event data set each time, as it is by an event reader subtask. In this configuration, events are only read back from DASD if they need to be resent to the Z controller during restart processing (for example when the communication link to the Z controller becomes active after an outage).

For more information about the ERDROPTS and EWTROPTS initialization statements, see ERDROPTS and EWTROPTS. For detailed information about allocating event data sets, see also Event data sets (EQQEVDS, EQQEVDnn, and EQQHTTP0).