NetBatch Manual

Scheduler Planning, Configuration, and
Management
NetBatch Manual—522460-004
3-10
Running NETBATCH
Scheduler altered
26> BATCHCOM $WXYZ; START SCHEDULER
Scheduler started
For complete warm-start instructions, see Warm Starting a Scheduler on page 3-18.
Cold Starts Versus Warm Starts
This table describes when to cold start or warm start a scheduler:
Running NETBATCH
To run the scheduler program NETBATCH, use the TACL RUN command:
node
is the name of the node where the NETBATCH program file resides. If the node is
remote, you must have remote access to it (that is, you must have remote
passwords set up on both local and remote nodes). The default is the node where
the process that creates the NETBATCH process is running.
volume
is one of:
$volume-name.subvolume-name
specifies the volume and subvolume containing the NETBATCH program file
(usually $SYSTEM.SYSTEM).
subvolume-name
specifies the subvolume containing the NETBATCH program file.
The default volume varies, depending on whether the RUN command is explicit or
implicit:
•
For an explicit RUN command, enter RUN followed by the NETBATCH
program file name. If you enter a partially qualified file name, the TACL
program expands it by using the current default node, volume, and subvolume
names.
If you want to … Then perform a …
Start a scheduler whose database does not exist Cold start
Start a scheduler that opens an existing scheduler database Warm start
Start a scheduler that purges an existing scheduler database Cold start
[ RUN ] [ \node. ] [ volume. ] NETBATCH
/ NAME [ $schd ] , NOWAIT [ , run-option ]… /
[ schd-database-subvol ] [ ! ] [ \remote-node ]…
[ EMS ] [ DISPLAY-SPI ] [ REPORT-ON jobrun-database-subvol]