Communication

The data router subtask is responsible for communicating the event to the controller event manager subtask, either by XCF, NCF, TCP/IP or by adding directly to the queue when the tracker and controller are started in the same address space. This eliminates the need for a separate event-reader function, saves time, and saves I/O operations.

The EWSEQNO value is not used to build a DD name, as happens with the event reader subtask. The event writer uses the EQQEVDS DD name to identify the event data set.

If a connection is lost between a tracker and the controller, the event writer continues to record events. When the connection is restored, the event data set is processed from the last event received by the controller before the outage.

Note: Controllers scheduling work (for a given z/OS image) must have unique subsystem names.