Starting an event writer with an event reader function

In situations where a tracker does not have a DASD connection with the controller, use an event writer that is started with an event-reader function.

This can improve performance because events are not written to the event data set and then read back again, which requires an event-reader task to continually check the event data set for new events.

Instead, the event writer writes events to the event data set and forwards them directly to the controller through an XCF, NCF, or TCP/IP link.