NetBatch Manual

Commands
NetBatch Manual—522460-004
6-4
Considerations
subvolume. (This file contains the standard help text supplied with NetBatch
software.) When BATCHIMU is not in the program-file subvolume, the help
request fails, and BATCHCOM displays a message similar to this:
0011-E File or record does not exist, BATCHIMU
Examples
•
The explicit RUN command in this example starts an interactive BATCHCOM
session. The STATUS SCHEDULER command, being the first scheduler-related
command after the session begins, opens scheduler $ZBAT by default and
displays its details.
> RUN $SYSTEM.SYSTEM.BATCHCOM
BATCHCOM - T9190D30 …
1} STATUS SCHEDULER
NETBATCH SERVER - T9190D30 … Time: 26AUG94 10:05:08
SCHEDULER STATUS
Process : \MELBDEV.$ZBAT Primary : 0,45 Backup : 1,77 .
2}
•
The implicit RUN command in this example starts an interactive BATCHCOM
session and causes BATCHCOM to open scheduler $SCHD on node \MELBQAT:
> BATCHCOM \MELBQAT.$SCHD
BATCHCOM - T9190D30 …
NETBATCH SERVER - T9190C23 … Time: 26AUG94 10:10:07
1}
•
The implicit RUN command in this example starts a noninteractive BATCHCOM
session during which BATCHCOM executes a STATUS SCHEDULER command.
Because the RUN command does not specify a scheduler, the STATUS command
opens and displays details of scheduler $ZBAT.
> BATCHCOM; STATUS SCHEDULER
SCHEDULER STATUS
Process : \MELBDEV.$ZBAT Primary : 0,45 Backup : 1,77 .
•
The implicit RUN command in this example is the same as in the previous
example, but the STATUS SCHEDULER command fails because $ZBAT is not
running:
> BATCHCOM; STATUS SCHEDULER
STATUS SCHEDULER
-^-0014-
E Device does not exist, \MELBDEV.$ZBAT
•
The implicit RUN command in this example causes BATCHCOM to check, but not
execute, the two commands in file STATUS. The first command is syntactically
correct, but the second contains a spelling error.
> BATCHCOM /IN STATUS/ \MELBQAT.$SCHD, SYNTAX
BATCHCOM - T9190D30 …
NETBATCH SERVER - T9190C23 … Time: 26AUG94 10:26:04
STATUS EXECUTOR *