Technical data

Managing the Queue Manager and Queue Database
13.11 Solving Queue Manager Problems
• If the queue database disk is not mounted for the node on which the queue
manager attempts to run.
In general, the queuing system will be shut off completely if the queue manager
encounters a serious error and forces a crash or failover twice in two minutes
consecutively on the same node. Therefore, the queuing system may have
stopped, or it may continue to run if the queue manager moves to yet another
node on which it can access the database after the original failed startup.
13.11.3.3 Correcting the Problem
Perform the following steps:
1. If the queue manager is stopped, enter START/QUEUE/MANAGER and
include the following information:
• An appropriate list of nodes with the /ON qualifier.
• The appropriate dirspec parameter (to specify the location of the queue
and journal files). All the nodes included in the node list with the /ON
qualifier must be able to access this directory.
2. On all nodes specified in the node list (except on any nodes that boot from the
disk where the queue database files are stored), add a MOUNT command to
the SYLOGICALS.COM procedure to mount the disk that holds the master
file. You do not need to explicitly mount the disk on a node where it is the
system disk.
13.11.4 If the Queue Manager Becomes Unavailable
The queue manager becomes unavailable if it does not start or has stopped
running.
13.11.4.1 Investigating the Problem
To investigate the problem, enter SHOW CLUSTER to see if the nodes on the list
are available.
13.11.4.2 Cause
An insufficient failover node list might have been specified for the queue manager,
so that none of the nodes in the failover list is available to run the queue
manager.
13.11.4.3 Correcting the Problem
Make sure the queue manager list contains a sufficient number of nodes by
entering START/QUEUE/MANAGER with the /ON qualifier to specify a node list
appropriate for your configuration.
If you are in doubt about what nodes to specify, Compaq recommends that you
specify an asterisk (*) wildcard character as the last node in the list; the asterisk
indicates that any remaining node in the cluster can run the queue manager.
Specifying the asterisk prevents your queue manager from becoming unavailable
because of an insufficient node list.
13.11.5 If the Queuing System Does Not Work on a Specific OpenVMS Cluster
Node
Use this section if the queuing system does not work on a specific node when it
starts up.
Managing the Queue Manager and Queue Database 13–19