HELP ENABLE — VMS 5.5-2H4
Additional information available:
AUTOSTART
The ENABLE AUTOSTART command enables the autostart feature.
By default, this command uses the /QUEUES qualifier.
Requires OPER (operator) privilege.
Use this command to automatically start on the node all stopped
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.
An autostart queue is active if it has been activated by the
/START qualifier with the INITIALIZE/QUEUE command or by the START
/QUEUE command, and has not been stopped by the STOP/QUEUE/NEXT or
STOP/QUEUE/RESET command.
When a node boots, autostart is disabled until you enter the
ENABLE AUTOSTART command. Typically, you would add this command to
your site-specific startup command procedure or your queue startup
command procedure to start a node's autostart queues each time the
node boots. procedure SYSTARTUP_V5.TEMPLATE.
For more information about autostart queues, see the Guide to
Maintaining a VMS System.
Format
ENABLE AUTOSTART[/QUEUES]
Additional information available:
Parameters
None.
QUALIFIERS
Additional information available:
/ON_NODE
/ON_NODE=nodename
Specifies a node in a VAXcluster. Use this qualifier to enable
autostart on a node other than the one on which the command is
entered.
/QUEUES
Specifies that autostart is to be enabled for queues. (This parameter is used by default.)
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 and 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
all autostart queues on the node and prevents queues from
failing over to the node.
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 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 it 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
autostart queues on that node and to start any active autostart
queue that might fail over to it.
Later, suppose node NEPTUN must be removed from the cluster.
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.