|
VMS Help STOP, /QUEUE, /ON_NODE, Examples *Conan The Librarian |
1.$ STOP/QUEUES/ON_NODE
The STOP/QUEUES/ON_NODE command in this example stops all
queues on the node from which it is entered. The autostart
feature is disabled on this node for all autostart queues.
However, the queue manager process continues to run and
schedules jobs as requested for execution on its unstopped
queues on other nodes in the OpenVMS Cluster.
This command only affects queues managed by the default
queue manager SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER
qualifier is not specified.
2.$INITIALIZE/QUEUE-
_$/AUTOSTART_ON=(JADE::,RUBY::,OPAL::)/BATCH/START BATCH_1
$ENABLE AUTOSTART/QUEUES/ON_NODE=JADE
$ENABLE AUTOSTART/QUEUES/ON_NODE=RUBY
.
.
.
$ STOP/QUEUES/ON_NODE=JADE
$ SHOW QUEUE BATCH_1
Batch queue BATCH_1, idle, on RUBY::
The INITIALIZE/QUEUE command in this example creates the
autostart queue BATCH_1 capable of running on node JADE,
RUBY, or OPAL. The /START qualifier activates the queue for
autostart. The first ENABLE AUTOSTART/QUEUES command enables
autostart of all autostart queues on node JADE, causing the
queue BATCH_1 to begin processing on that node. The second
ENABLE AUTOSTART/QUEUES command enables autostart for all
autostart queues on node RUBY.
Later, suppose node JADE needs to be removed from the cluster.
The STOP/QUEUES/ON_NODE command in the example stops all queues
on node JADE without stopping the clusterwide queue manager,
and causes the autostart queue BATCH_1 to failover to node
RUBY, the next available node in its failover list. Because
the STOP QUEUES/ON_NODE command disables autostart, the ENABLE
AUTOSTART/QUEUES command must be executed on node JADE when it
reboots for autostart queues to run on that node in the future.
This command only affects queues managed by the default
queue manager SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER
qualifier is not specified.
|
|