NetBatch Manual
Scheduler Planning, Configuration, and
Management
NetBatch Manual—522460-004
3-38
Dealing With Scheduler Log Files
Dealing With Scheduler Log Files
The scheduler records in a log file details of events that occur while it is running. You
can use the log, for example, for troubleshooting purposes. The log can be a device, a
process, or any type of unstructured disk file except an EDIT file.
Figure 3-7 on page 3-38 shows a commented example of a scheduler log file. The
example lists events such as scheduler startup, class and executor configuration, job
submission and execution, and scheduler shutdown. For explanations of the example’s
event keywords and a breakdown of the logging formats used in the event
descriptions, see Table 3-3 on page 3-41 and Table 3-4 on page 3-43.
Figure 3-7. Example of a Scheduler Log File
Executor selected; state changed to
ACTIVE
Primary scheduler process started
(CPU 1)
START SCHEDULER command
executed
Confirmation that backup process
started
Confirmation that executor program
started
Confirmation that executor program
stopped
Executor released and state changed
to
ON
Event
keyword
Event
timestamp
Event
description
NETBATCH SCHEDULER/MONITOR - T9190D20 …
SCHEDULER \MELBDEV.$:0:83:17941432 U_255,255
H_\MELBDEV.$T4.#A
03MAR93
03MAR93 Scheduler Primary \MELBDEV.$SCHD CPU 1
03MAR93 Purge any existing scheduler database files
03MAR93 U_255,255 P_BATCHCOM \MELBDEV.$:0:83:17941432
03MAR93
SCHEDULER \MELBDEV.$:0:83:17941432 U_255,255
H_\MELBDEV.$T4.#A
03MAR93 Scheduler Backup \MELBDEV.$SCHD CPU 2 U_255,255
H_\MELBDEV.$T4.#A
03MAR93 \MELBDEV.$SCHD:20110521
03MAR93 CLASS DEFAULT U_255,255 H_\MELBDEV.$T4.#A
03MAR93 EXECUTOR E0 CPU 0 U_255,255 H_\MELBDEV.$T4.#A
03MAR93 EXECUTOR E0 U_255,255 H_\MELBDEV.$T4.#A
03MAR93 EXECUTOR E0 S_ON U_255,255 H_\MELBDEV.$T4.#A
03MAR93 JOB ABC C_DEFAULT:3 J_1 U_255,255 H_\MELBDEV.$T4.#A
03MAR93 JOB ABC READY J_1 U_255,255 H_\MELBDEV.$T4.#A
03MAR93 JOB (SUPER.SUPER)ABC E_E0 L_1362 J_1 U_255,255
03MAR93 EXECUTOR E0
S_ACTIVE
03MAR93 JOB ABC J_1
03MAR93 JOB ABC EXECUTING J_1
03MAR93
EXECUTOR-PROGRAM U_255,255 J_1 P_TACL
\MELBDEV.$Z587:20112569
03MAR93 CC_0 EXECUTOR-PROGRAM J_1 \MELBDEV.$Z587:20112569
03MAR93 EXECUTOR E0
S_ON
03MAR93 JOB ABC J_1
03MAR93 SHUTDOWN SCHEDULER \MELBDEV.$:0:83:17941432
U_255,255 H_\MELBDEV.$T4.#A
03MAR93 Myself U_255,255 H_\MELBDEV.$T4.#A
03MAR93
14:49:38
14:49:02
14:49:02
14:49:13
14:49:44
14:49:46
14:49:49
14:49:59
14:50:40
14:50:51
14:50:52
14:57:15
14:57:15
14:57:19
14:57:19
14:57:20
14:57:20
14:57:20
14:57:39
14:57:39
14:57:39
15:01:12
15:01:12
14:57:39
ADD
CREATE
COLD
OPEN
START
CREATE
START
ADD
ADD
START
UPDATE
ADD
LIST
BEGIN
UPDATE
UPDATE
LIST
START
STO
P
UPDATE
DELET
E
SHUTDN
DOSTOP
FINISH JOB ABC T_0:0:5:100 J_1 P_TACL
Log file header
Cold start
indicated
BATCHCOM opens
scheduler
ADD SCHEDULER command
executed
Backup scheduler process
started
ADD CLASS command
executed
ADD EXECUTOR command
executed
START EXECUTOR command
executed
Executor state changed to
ON
SUBMIT JOB command
executed
Job state changed to
READY
Executor program startup
begins
Job state changed to
EXECUTING
Confirmation that job
finished
Job deleted from scheduler
database
SHUTDOWN SCHEDULER command
executed
Backup scheduler process
stopped
VST103.vsd