HP OpenVMS Systems Documentation

HP OpenVMS DCL Dictionary

Stops all queues on the specified node. This command is useful if you want to stop a set of queues on a node with a single command (for example, before shutting down a node), but do not want to stop a queue manager throughout an OpenVMS Cluster.

The /QUEUES qualifier is optional, but the /ON_NODE qualifier is required.

Requires OPER (operator) privilege.

Format

STOP/QUEUES/ON_NODE[=node]

Parameters

None.

Description

The STOP/QUEUES/ON_NODE command notifies the queue manager to perform the following tasks:

• Abort all current jobs that cannot be restarted (in all of that queue manager's execution queues on the appropriate node), and requeue all current restartable jobs.
• Stop all of that queue manager's execution queues on the appropriate node. Force any of that queue manager's autostart queues on the node to fail over to the next available node in the queue's failover list (if any) on which autostart is enabled.
• Prevent any of that queue manager's autostart queues from failing over to the node.

By default, this command affects the node from which it is entered. Specify a nodename with the /ON_NODE qualifier to stop queues on a different node.

By default, the command affects autostart queues managed by the default queue manager, SYS$QUEUE_MANAGER. Specify the /NAME_OF_MANAGER qualifier to disable autostart of a different queue manager's autostart queues (on the node).

The STOP/QUEUES/ON_NODE command affects all autostart and nonautostart execution queues on the appropriate node that are managed by the queue manager. Autostart queues stopped as a result of this command remain active for autostart and will be restarted when the ENABLE AUTOSTART command is entered for the affected node or a node to which the queue can fail over. Nonautostart queues stopped as a result of this command must each be started with a START/QUEUE command specifying the queue name.

If you are using autostart queues, you might want to enter the DISABLE AUTOSTART/QUEUES command. For more information on the relationship between DISABLE AUTOSTART/QUEUES and STOP/QUEUES/ON_NODE, refer to the section on stopping queues before shutting down a system in the chapter about queues in the HP OpenVMS System Manager's Manual.

The STOP/QUEUES/ON_NODE command is included in the shutdown command procedure SYS$SYSTEM:SHUTDOWN.COM. If you shut down a node without using SHUTDOWN.COM, you might want to enter the STOP/QUEUES/ON_NODE command first. For more information on stopping queues before shutting down a node, refer to the chapter about queues in the HP OpenVMS System Manager's Manual.

Qualifier

/NAME_OF_MANAGER=name

Specifies the name of the queue manager controlling the queues you want to stop.

If the /NAME_OF_MANAGER qualifier is omitted, then the default queue manager name SYS$QUEUE_MANAGER is used. For more information on multiple queue managers, refer to the chapter about the queue manager in the HP OpenVMS System Manager's Manual.

Examples

$ 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.

$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.