OpenVMS Cluster Systems - OpenVMS Systems - HP

Setting Up and Managing Cluster Queues
7.2 Controlling Queue Availability
WHEN... THEN... Comments
The operating system
automatically restores
the queuing system with
the parameters defined in
the queuing database.
This is because when you start the
queuing system, the characteristics you
define are stored in a queue database.
To control queues, the queue manager maintains a clusterwide queue database
that stores information about queues and jobs. Whether you use one or several
queue managers, only one queue database is shared across the cluster. Keeping
the information for all processes in one database allows jobs submitted from any
computer to execute on any queue (provided that the necessary mass storage
devices are accessible).
7.3 Starting a Queue Manager and Creating the Queue Database
You start up a queue manager using the START/QUEUE/MANAGER command as
you would on a standalone computer. However, in an OpenVMS Cluster system,
you can also provide a failover list and a unique name for the queue manager.
The /NEW_VERSION qualifier creates a new queue database.
The following command example shows how to start a queue manager:
$ START/QUEUE/MANAGER/NEW_VERSION/ON=(GEM,STONE,*)
The following table explains the components of this sample command.
Command Function
START/QUEUE/MANAGER Creates a single, clusterwide queue manager named SYS$QUEUE_
MANAGER.
/NEW_VERSION Creates a new queue database in SYS$COMMON:[SYSEXE] that
consists of the following three files:
/ON=(node-list)
[optional]
7–2 Setting Up and Managing Cluster Queues
• QMAN$MASTER.DAT (master file)
• SYS$QUEUE_MANAGER.QMAN$QUEUES (queue file)
• SYS$QUEUE_MANAGER.QMAN$JOURNAL (journal file)
Rule: Use the /NEW_VERSION qualifier only on the first invocation
of the queue manager or if you want to create a new queue database.
Specifies an ordered list of nodes that can claim the queue manager if
the node running the queue manager should exit the cluster. In the
example:
• The queue manager process starts on node GEM.
• If the queue manager is running on node GEM and GEM leaves
the cluster, the queue manager fails over to node STONE.
• The asterisk wildcard ( * ) is specified as the last node in the node
list to indicate that any remaining, unlisted nodes can start the
queue manager in any order.
Rules: Complete node names are required; you cannot specify the
asterisk wildcard character as part of a node name.
If you want to exclude certain nodes from being eligible to run the
queue manager, do not use the asterisk wildcard character in the
node list.