1 – AUTOSTART
Enables the autostart feature on a node for all autostart queues
managed by the specified queue manager. By default, this command
uses the /QUEUES qualifier.
Requires OPER (operator) privileges.
Use this command to automatically start on the node all active
autostart queues that are capable of executing on or that fail
over to the specified node. By default, this command affects the
node from which it is entered. Specify the /ON_NODE qualifier to
enable autostart on a different node.
For more information on autostart queues, see the chapter on
batch and print queues in the VSI OpenVMS System Manager's Manual.
Format
ENABLE AUTOSTART[/QUEUES]
1.1 – Qualifiers
1.1.1 /NAME_OF_MANAGER
/NAME_OF_MANAGER=name
Specifies the name of the queue manager controlling the autostart
queues you want to enable. The qualifier allows the autostart
feature to be used differently for different sets of queues.
If the /NAME_OF_MANAGER qualifier is omitted, the default queue
manager name SYS$QUEUE_MANAGER is used.
For more information on multiple queue managers, see the chapter
on the queue manager in the VSI OpenVMS System Manager's Manual.
1.1.2 /ON_NODE
/ON_NODE=nodename
Specifies a node in an OpenVMS Cluster system. Use this qualifier
to enable autostart on a node other than the one from which you
enter the command.
1.1.3 /QUEUES
Specifies that autostart is to be enabled for queues. (This
qualifier is used by default.)
1.2 – Examples
1.$ INITIALIZE/QUEUE/BATCH/START-
_$ /AUTOSTART_ON=SATURN:: BATCH_1
$ ENABLE AUTOSTART/QUEUES
.
.
.
$ DISABLE AUTOSTART/QUEUES
In this example, the INITIALIZE/QUEUE command creates an
autostart queue BATCH_1, capable of running on node SATURN.
The /START qualifier activates the queue for autostart. The
ENABLE/AUTOSTART/QUEUES command (executed on node SATURN)
enables autostart on the node, causing the queue (and any other
active autostart queues on the node) to begin executing jobs.
The DISABLE AUTOSTART command (executed on node SATURN) stops
autostart queues on the node and prevents any queues from
failing over to the node.
These commands only affect queues managed by the default
queue manager SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER
qualifier is not specified.
Because BATCH_1 is set up to run only on one node, the queue
cannot fail over to another node and therefore is stopped;
however, the queue remains active for autostart and will
be started when the ENABLE AUTOSTART command is entered for
node SATURN. No START/QUEUE command is needed to restart
BATCH_1 unless autostart of the queue is deactivated with the
STOP/QUEUE/NEXT or STOP/QUEUE/RESET command.
2.$ INITIALIZE/QUEUE/BATCH/START-
_$ /AUTOSTART_ON=(NEPTUN::,SATURN::) BATCH_1
$ ENABLE AUTOSTART/QUEUES/ON_NODE=NEPTUN
$ ENABLE AUTOSTART/QUEUES/ON_NODE=SATURN
.
.
.
$ STOP/QUEUES/ON_NODE=NEPTUN
In this example, the INITIALIZE/QUEUE command creates an
autostart queue BATCH_1. The /START qualifier activates the
queue for autostart.
The first ENABLE AUTOSTART/QUEUES command causes the queue
to begin executing on node NEPTUN. The second ENABLE
AUTOSTART/QUEUES command enables autostart on node SATURN to
start all stopped active autostart queues on that node and to
start any autostart queues that might fail over to that node.
Later, suppose node NEPTUN must be removed from the OpenVMS
Cluster system. The STOP/QUEUES/ON_NODE command stops all
queues on node NEPTUN, and causes the autostart queue BATCH_
1 to fail over to node SATURN. Because the queue is active
for autostart, and because autostart has been enabled on node
SATURN, the queue is automatically started on that node.
This command only affects queues managed by the default
queue manager SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER
qualifier is not specified.