NetBatch Manual

Scheduler Planning, Configuration, and
Management
NetBatch Manual—522460-004
3-40
Dealing With Scheduler Log Files
You also can use the EDIT program to list a closed log file’s contents after putting the
contents into an EDIT file. For example, this command creates file LOGTEMP, puts the
contents of LOGADQ into that file, then lists LOGTEMP:
> EDIT; GET LOGADQ PUT LOGTEMP; LIST ALL
For information about the FUP COPY command, see the File Utility Program (FUP)
Reference Manual. For information about the EDIT program, see the EDIT User’s
Guide and Reference Manual.
Interpreting the Contents of a Scheduler Log File
The log file records scheduler events in chronological order. Each event has a
timestamp, a keyword identifying the event type, and an event description. For
example:
For explanations of event keywords and a breakdown of the logging formats used in
event descriptions, see Table 3-3 and Table 3-4 on page 3-43.
The NETBATCH log file is an unstructured file with a record length of 132 bytes. If the
information to be logged is greater than 132 bytes, it is split into two consecutive
records. The fields used in the records are:
<Timestamp>: contains the date and time of the event.
<Main Event>: contains the event that has occurred.
<Jobno>: contains the job number associated with the event.
<Description>: contains information on the attributes linked with the event.
The format in which the information will be split is shown below.
Case 1: A job related event will be logged as
Record 1: <Timestamp> <Main Event> <Jobno>
Record 2: <Timestamp> <Description>
For example, the BEGIN JOB event will be logged as
Record 1: 06APR06 12:44:41 BEGIN JOB (SUPER.SUPER)
J23456789012345678901234:1 E_E23456789012345678901234 L_12 J_1
Record 2: 06APR06 12:44:41 J_1 P_DELAY \NODE1.$Z0H5:38494157
U_255,255
Case 2: A job independent event will be logged as
Record 1: <Timestamp> <Main Event>
19OCT94 13:36:46 START EXECUTOR E0 U_255,205 H_\MELBDEV.$ZTN0.#PTY4
Timestamp
Keyword Description
VST009.vsd