NetBatch Manual

Commands
NetBatch Manual—522460-004
6-177
STATUS-HISTORY Command
•
The run number for a recurrent job (a job with the CALENDAR or EVERY attribute)
increments by one each time the job runs. The run number for a nonrecurrent job
is always one, no matter how many times the job runs.
•
When STATUS-HISTORY command output goes to the current terminal,
BATCHCOM displays the name of the log file being scanned on line 25. For
example:
Scanning : \MELRISK.$QA.ZBAT.LOGAAL
•
When command output goes to a location other than the current terminal, the
name of the log file being scanned appears in the output. For example:
Scanning : \MELRISK.$QA.ZBAT.LOGAAN
Scanning : \MELRISK.$QA.ZBAT.LOGAAO
Scanning : \MELRISK.$QA.ZBAT.LOGAAP
Scanning : \MELRISK.$QA.ZBAT.LOGAAQ
Scanning : \MELRISK.$QA.ZBAT.LOGAAR
14SEP94 10:04:51 BEGIN JOB …
•
On a scheduler warm start when the scheduler’s previous log file was a disk file
and the scheduler encounters a file-system error on that file, this warning appears:
*WARNING* Scheduler log-file chaining lost:
Error file-system-error-no. Continuing …
The warning, which has no effect on the scheduler, indicates a break in the disk
log-file sequence. As a result, log-file scanning by the STATUS-HISTORY
command terminates at the break with a “file not found” error instead of continuing
through subsequent files. To continue the search, enter a STATUS-HISTORY
command that specifies the next read-accessible log file in the range you want
searched.
Example
This example shows the STATUS-HISTORY command listing the log-file events
generated by the most recent run of job 29:
10} STATUS-HISTORY 29
08SEP94 16:12:01 BEGIN JOB (SUPER.SUPER)DG2:829 E_E4 J_29
P_DELAY U_255,255
08SEP94 16:12:02 LIST JOB DG2 EXECUTING J_29
08SEP94 16:12:02 START EXECUTOR-PROGRAM U_255,255 J_29
P_DELAY \MELRISK.$X747:8994225
08SEP94 16:13:02 STOP CC_0 EXECUTOR-PROGRAM J_29
\MELRISK.$X747:8994225
08SEP94 16:13:02 FINISH JOB DG2 T_0:0:0:2 J_29 P_DELAY
Output 5 Lines