NetBatch Manual

Commands
NetBatch Manual—522460-004
6-157
START SCHEDULER Command
START SCHEDULER Command
Use the START SCHEDULER command to make available for use a scheduler you are
cold starting or warm starting. For cold starts, use the command after running the
scheduler program NETBATCH and executing the ADD SCHEDULER command. For
warm starts, use the command immediately after running the scheduler program.
file-name
specifies a command output file. The file can be a device, a process, or a disk file.
For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT
file if the file does not exist. If you specify / OUT / (that is, omit file-name),
BATCHCOM suppresses output.
Considerations
•
The START SCHEDULER command is available to NetBatch supervisors only.
•
The START SCHEDULER command starts a scheduler whose primary process
only is running and whose database exists. The command creates the scheduler’s
backup process and opens its database files.
•
To create a primary scheduler process, use the TACL RUN command to run the
scheduler program NETBATCH.
•
To create a scheduler database, use the ADD SCHEDULER command.
•
The START SCHEDULER command uses information from files in the scheduler
database to start the scheduler.
•
If you cold started the scheduler, you must configure it before you can submit jobs
for execution. Scheduler configuration involves changing default scheduler
attributes (if necessary), adding executors and classes, and so on.
•
If you warm started the scheduler, its configuration is the same as when the
scheduler stopped, except for the log file. For more information, see Section 3,
Scheduler Planning, Configuration, and Management.
•
You can omit the object keyword SCHEDULER from the START SCHEDULER
command only when SCHEDULER is the current assumed object. For more
information, see ASSUME SCHEDULER Command on page 6-73.
START [ SCHEDULER ] [ / OU[T] [ file-name ] / ]
Caution. The ADD SCHEDULER command purges existing scheduler database files (except
BATCHCTL and log files) before creating and initializing new files. Do not use the command
unless you are sure loss of the existing files will not affect your organization. If in doubt, back
up the files before using the command.