NetBatch Manual

Scheduler Planning, Configuration, and
Management
NetBatch Manual—522460-004
3-21
Warm-Start Events
NBATTX O 847 0 18-Oct-94 13:57:38 255,255 …
NBATTX0 O 847 0 18-Oct-94 13:57:38 255,255 …
The START SCHEDULER command prepares the scheduler for use. The command
creates the scheduler’s backup process (in the CPU specified by the scheduler’s
BACKUPCPU attribute) and opens the database files.
Warm-Start Events
When a scheduler warm starts, these significant events occur:
1. When warm-start processing begins (RUN NETBATCH command excludes the !
parameter):
a. The scheduler renames its JOB file to JOBSAVED.
b. The scheduler uses JOBSAVED to build a new JOB file.
At the end of warm-start processing, the scheduler deletes JOBSAVED. If the
scheduler stops before processing ends, JOBSAVED remains in the database
for use during the next warm start, after which the scheduler deletes the file.
No user intervention is necessary.
If the JOB file is not secured “OOOO” to the local super ID by using the FUP
SECURE command with the PROGID option, warm-start processing fails:
25> NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.ZBAT
Warning - $ZBAT replied error 201 to the STARTUP message
- continuing
2: Process terminated with fatal errors or diagnostics
NetBatch: ERROR JOB file not CODE 847, SUPER.SUPER,
SECURE "OOOO", PROGID
To correct the problem:
1. Use the FUP GIVE command to assign JOB file ownership to the local
super ID.
2. Use the FUP SECURE, PROGID command to secure the file “OOOO” with
the PROGID option.
2. The scheduler process replies to its startup message, returning the TACL prompt,
when JOB file processing is complete. (JOB file processing can take up to five
minutes, depending on the number of jobs in the scheduler.) The scheduler returns
file-system error 12 (file in use) to an opener such as BATCHCOM until JOB file
processing ends.
3. After JOB file processing, the scheduler stops jobs that were executing when the
scheduler stopped. (A job can still be executing if the scheduler stopped by some
means other than an ABORT SCHEDULER or SHUTDOWN SCHEDULER
command.) The state of jobs stopped in this manner is SPECIAL-2 (2:NB failed).