Tracker message log

Look for the following messages in the log of each tracker:

Active data-router-task messages
EQQZ005I SUBTASK DATA ROUTER TASK IS BEING STARTED
EQQF001I DATA ROUTER TASK INITIALIZATION IS COMPLETE
Active submit-task messages
EQQZ005I SUBTASK JOB SUBMIT TASK IS BEING STARTED
EQQSU01I THE SUBMIT TASK HAS STARTED

Also, verify that the tracker has started an event writer. You should see these messages:

Active event-writer messages
EQQZ005I SUBTASK EVENT WRITER IS BEING STARTED
EQQW065I EVENT WRITER STARTED
If the tracker forwards events to the controller, ensure that an event-reader function is specified. This can be a separate event-reader task or an event writer that has been started with the EWSEQNO keyword. In some configurations, both functions can be started in a tracker.
  • Although no messages are issued if you use EWSEQNO to start the reader function, check that EWSEQNO appears on the EWTROPTS statement and that the return code for this statement is 0.
  • If you have specified a separate event-reader function, check that these messages appear:
    Active event-reader messages
    EQQZ005I SUBTASK EVENT READER IS BEING STARTED
    EQQR025I ERDR 01 STARTED

    The numeric value on message EQQR025I indicates which event reader is being started. The same value cannot be specified on EWSEQNO and ERSEQNO keywords at the same node, and no more than 16 reader tasks can be specified at this node.

Note: If the tracker uses an XCF connection, no messages appear in the tracker message log unless an error has occurred. To verify XCF connection messages, check the message log of the controller.

If the tracker uses an NCF connection, check that these messages appear (where NCFTRK01 and NCFCON01 represent the VTAM® application IDs of the tracker and controller):

Active NCF-connection messages
EQQZ005I SUBTASK VTAM I/O TASK IS BEING STARTED
EQQV001I NCF APPLICATION STARTED
EQQV024I ACB SUCCESSFULLY OPENED
EQQV036I SESSION NCFTRK01-NCFCON01 ESTABLISHED
EQQV040I CURRENTLY RUNNING WITH 'NCFCON01' AS CONTROLLER

Sample message log for a tracker shows an example of the MLOG for a tracker. The tracker is connected to the controller via a VTAM® link. The VTAM® application IDs are NCFTRK01 for the tracker and NCFCON01 for the controller. The controller is active.