Checking the message log (EQQMLOG)

Start the tracker.

When the tracker is started, check the message log:

• Check that the return code for all initialization options is 0 (message EQQZ016I).
• Ensure that all required subtasks are active.
  • The data-router and submit tasks are always started. You should see these messages:

    EQQZ005I OPC SUBTASK DATA ROUTER TASK IS BEING STARTED
    EQQF001I DATA ROUTER TASK INITIALIZATION IS COMPLETE  
    
    EQQZ005I OPC 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:

    EQQZ005I OPC SUBTASK EVENT WRITER IS BEING STARTED
    EQQW065I EVENT WRITER STARTED

• Examine error messages.
  Note:

  The first time the event writer is started, it formats the event data set. Ignore the SD37 abend code that is issued during the formatting process.

  If you see error messages in the message log for an event reader or an NCF connection, this is because you cannot fully verify an event-reader function or NCF connection until the controller is active and a current plan exists. Active tracker-connection messages for XCF connections are written to the controller message log when the controller is started. If you have specified any of these functions, follow the procedures in Verifying configuration when you have completed initial verification procedures.

• Check that your log is complete.

  Figure 25 shows an example of the MLOG for a tracker. If your log seems to be incomplete, information might be in a buffer. If you are unsure whether the log is complete, issue a dummy modify command like this: F ssname,xx. Message EQQZ049E is written to the log when the command is processed. This message will be the last entry in the log.