Checking the message log (EQQMLOG)

Start the controller. See Tivoli® Workload Scheduler for z/OS®: Managing the Workload for information on starting and stopping Tivoli Workload Scheduler for z/OS.

When the controller is started, check the message log:

Ensure that the return code for all initialization options is 0 (message EQQZ016I).
Check that all required subtasks are active.
Look for these messages when the controller is started:

Active general-service messages
```
EQQZ005I OPC SUBTASK GENERAL SERVICE IS BEING STARTED
EQQZ085I OPC SUBTASK GS EXECUTOR 01 IS BEING STARTED
EQQG001I SUBTASK GS EXECUTOR 01 HAS STARTED

·
·
·

EQQG001I SUBTASK GENERAL SERVICE HAS STARTED
```
Note:
The preceding messages, EQQZ085I and EQQG001I, are repeated for each general service executor that is started. The number of executors started depends on the value you specified on the GSTASK keyword of the OPCOPTS initialization statement. The default is to start all five executors.
Active data-router-task messages
```
EQQZ005I OPC SUBTASK DATA ROUTER TASK IS BEING STARTED
EQQF001I DATA ROUTER TASK INITIALIZATION IS COMPLETE
```
When you start a controller and no current plan exists, you will still see a number of EQQZ005I messages each indicating that a subtask is being started. But these subtasks will not start until a current plan is created. You will also see this message:

Current plan message
```
EQQN105W NO VALID CURRENT PLAN EXISTS. CURRENT PLAN VSAM I/O IS NOT
POSSIBLE
```
If you have specified an event-reader function or NCF connections, these tasks will end if no current plan exists. You can verify the remaining tasks when you have created a current plan and connections can be established. Verifying configuration describes these tasks.
Check that the log is complete.
Figure 24 shows an example of the MLOG for a controller.

Note:

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.