Starts the clusterwide queue manager for the queuing system
and opens that queue manager's queue database files. The /QUEUE
qualifier is optional, but the /MANAGER qualifier is required.
By default, the command affects the default queue manager,
SYS$QUEUE_MANAGER. Specify the /NAME_OF_MANAGER qualifier
to start a queue manager other than the default. For more
information, see the VSI OpenVMS System Manager's Manual.
Requires OPER (operator) and SYSNAM (system logical name)
privileges.
Format
START/QUEUE/MANAGER [dirspec]
1 – Parameter
dirspec
Specifies the directory location to contain the system queue and
journal files of the queue database. The queue file has a file
type of QMAN$QUEUES and contains queue definitions. The journal
file has a file type of QMAN$JOURNAL and contains job and other
information that lets the queue manager to return to its last
known state should a system be stopped unexpectedly. These files
must reside in the same directory.
The default location of the queue and journal files is
SYS$COMMON:[SYSEXE]. The optional dirspec parameter is used
only for specifying an alternate location for the queue and
journal files. The specification must include at least the
device and directory name. The asterisk (*) and the percent
sign (%) wildcard characters are not allowed in the directory
specification.
The directory you specify must be available to all nodes that
can run the queue manager. If the directory specification is a
concealed logical name, it must be identically defined on all
nodes in the cluster.
The location of the queue and journal files is stored in the
master file of the queue database. You do not have to respecify
the directory location with subsequent START/QUEUE/MANAGER
commands.
For information about changing the location of any of the queue
database files, see the Guide to Maintaining a VMS System.
2 – Description
The START/QUEUE/MANAGER command has the following uses:
o Enter the command START/QUEUE/MANAGER/NEW_VERSION to create
the queue database and initially start a queue manager.
See the description of the /NEW_VERSION qualifier for more
information. Once the queue manager has been started, it
will remain running unless it is explicitly stopped with the
STOP/QUEUE/MANAGER/CLUSTER command.
o If the STOP/QUEUE/MANAGER/CLUSTER command has been executed,
enter the START/QUEUE/MANAGER command to restart a queue
manager.
o In an OpenVMS Cluster, enter the START/QUEUE/MANAGER command
with the /ON qualifier to modify the list of preferred nodes
on which a queue manager can run. See the description of the
/ON qualifier for more information.
o In an OpenVMS Cluster, enter the START/QUEUE/MANAGER command
to ensure that a queue manager process is executing on the
most preferred, available node. If the queue manager is not
running on the most preferred, available node, the queue
manager will be moved to that node without interruption of
service. If you are using the default node list (*), the
queue manager will not move. For more information, see the
description of the /ON qualifier.
If the queue manager is in a location other than the default, and
in OpenVMS Cluster environments with multiple system disks, you
must define the logical name QMAN$MASTER. For instructions, see
the chapter about the queue manager and queue database in the VSI
OpenVMS System Manager's Manual.
If a queue manager does not start when you enter the
START/QUEUE/MANAGER command, you will receive the following
message:
%JBC-E-QMANNOTSTARTED, queue manager could not be started
If you see this message, search the operator log file
SYS$MANAGER:OPERATOR.LOG (or look on the operator console) for
messages from the facilities QUEUE_MANAGE and JOB_CONTROL for
information about the problem, as follows:
$ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=5 QUEUE_MANAGE,JOB_CONTROL
3 – Qualifiers
3.1 /ADD
Creates an additional queue manager in the existing queue
database. If the named queue manager already exists, the request
will be rejected.
3.2 /NAME_OF_MANAGER
/NAME_OF_MANAGER=name
Creates a non-default queue manager. The required name value may
be up to 31 characters long and may be a logical. The name will
serve as the identifier for the queue manager process and the
portion of the database that it is managing.
3.3 /NEW_VERSION
/NEW_VERSION
/NONEW_VERSION (default)
Specifies that a new (empty) version of the queue database is to
be created. This qualifier is required when initially creating
and starting the queuing system.
If you specify this qualifier and a queue database already
exists, the new master and queue files of the queue database
supersede existing versions of those files; however, the journal
file of the existing queue database is deleted. Jobs and other
information are lost.
3.4 /ON
/ON=(node[,...])
In an OpenVMS Cluster, specifies the nodes on which a clusterwide
queue manager can run. The default value for the node list is
the asterisk (*) wildcard character, meaning that all nodes in
the cluster are eligible to run the queue manager. If the node on
which the queue manager is running leaves the cluster, the queue
manager can automatically fail over to any available node in the
cluster. However, to specify a preferred order in which the nodes
should claim the queue manager, or to limit the nodes which can
run it, you must specify the /ON qualifier.
The node list you specify is stored in the queue database.
Anytime the START/QUEUE/MANAGER command is entered and neither
the /NEW_VERSION nor /ON qualifier is specified, the /ON list
stored in the queue database remains unchanged.
For highest availability, specify the asterisk (*) wildcard
character as the last node in the node list to indicate that
any remaining unlisted node can claim the queue manager, with
no preferred order. If you do not specify the asterisk (*)
wildcard character last in the node list, the queue manager can
only fail over if one of the nodes in the list is available;
however, if you want to exclude certain nodes from being eligible
to run the queue manager, you cannot use the asterisk (*)
wildcard character. You cannot specify the asterisk (*) wildcard
character as part of a node name.
Anytime the START/QUEUE/MANAGER command is entered (with or
without the /ON qualifier), the job controller will check to
see if one or more preferred queue manager nodes was currently
or previously specified with the /ON qualifier. If one or more
preferred nodes was specified, and the queue manager is running
on a node other than the first available node of those specified,
the queue manager process is moved from its current node and
restarted on the first available preferred node. Despite the
transition, queues on the running nodes are not stopped. All
requests to the queuing system, for example, PRINT, SUBMIT, and
SHOW ENTRY requests, will complete as expected.
4 – Examples
1.$ START/QUEUE/MANAGER/NEW_VERSION
$ SHOW QUEUE
%JBC-E-NOSUCHQUE, no such queue
The START/QUEUE/MANAGER command in this example starts the
queue manager and creates the queue and journal files in the
default location, SYS$COMMON:[SYSEXE]. Because the asterisk
(*) wildcard character is used by default as the value for the
list of nodes on which the queue manager can run, the queue
manager can fail over to any available node in the cluster.
This command starts the default queue manager SYS$QUEUE_MANAGER
because the /NAME_OF_MANAGER qualifier is not specified.
Both the SYS$COMMON:[SYSEXE] location and the value for the
/ON qualifier (which is * by default in this example) are
stored in the queue database for future reference. The newly
created queue database contains no queues or jobs. The SHOW
QUEUE command shows that no queues are defined on this cluster.
2.$ START/QUEUE/MANAGER/NEW_VERSION -
_$ /ON=(SATURN,VENUS,NEPTUN,*) DUA5:[SYSQUE]
The START/QUEUE/MANAGER command in this example creates the
queue and journal files on the cluster-accessible disk volume
DUA5, in directory SYSQUE. You must mount the disk before you
enter the START/QUEUE/MANAGER command.
The /ON qualifier specifies that the queue manager should run
first on node SATURN. If SATURN leaves the cluster, the queue
manager will attempt to fail over to VENUS. If VENUS is not
available, the queue manager will attempt to fail over to
NEPTUN. If NEPTUN is not available, the queue manager will
fail over to any other available node in the cluster.
3.$ START/QUEUE/MANAGER/NEW_VERSION -
_$ /ON=(SATURN,VENUS,NEPTUN,*) DUA5:[SYSQUE])
.
.
.
$ START/QUEUE/MANAGER
The START/QUEUE/MANAGER command in this example creates the
queue database as shown in the previous example. Suppose the
queue manager started on node SATURN.
Later, SATURN is removed from the cluster, and the queue
manager fails over to node VENUS. When SATURN rejoins the
cluster, the second START/QUEUE/MANAGER command in the example
is entered to move the queue manager back to node SATURN.
The second START/QUEUE/MANAGER command does not specify the
DUA5:[SYSQUE] parameter value or the /ON qualifier and its node
list because those previously supplied pieces of information
are stored in the queue database. The queue manager continues
to use the queue and journal files found at the location
stored in its database. The /ON list, stored as a result of the
previous START/QUEUE/MANAGER command, also remains unchanged.
4.$ START/QUEUE/MANAGER DUA4:[SYSQUE]
%JBC-E-QMANNOTSTARTED, queue manager could not be started
$ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=5 QUEUE_MANAGE,JOB_CONTROL
%%%%%%%%%%% OPCOM 14-DEC-2001 18:55:18.23 %%%%%%%%%%%
Message from user QUEUE_MANAGE on QMUNGR
%QMAN-E-OPENERR, error opening DUA4:[SYSQUE]SYS$QUEUE_MANAGER.QMAN$QUEUES;
%%%%%%%%%%% OPCOM 14-DEC-2001 18:55:18.29 %%%%%%%%%%%
Message from user QUEUE_MANAGE on QMUNGR
-RMS-F-DEV, error in device name or inappropriate device type for
operation
%%%%%%%%%%% OPCOM 14-DEC-2001 18:55:18.31 %%%%%%%%%%%
Message from user QUEUE_MANAGE on QMUNGR
-SYSTEM-W-NOSUCHDEV, no such device available
$ START/QUEUE/MANAGER DUA5:[SYSQUE]
In this example, the first START/QUEUE/MANAGER command
specifies device DUA4: as the location of the queue and journal
files. The error message indicates that the queue manager does
not start. The SEARCH command searches the operator log file
for relevant messages, and reveals that device DUA4: does not
exist. The second START/QUEUE/MANAGER command specifies the
correct device name, DUA5:.