Technical data

Managing the Queue Manager and Queue Database
13.11 Solving Queue Manager Problems
13.11.3 If the Queuing System Stops or the Queue Manager Does Not Run on
Specific Nodes
Use this section if the queue manager does not run on a specific node in the
cluster, or if the queuing system stops, especially after one of the following
actions:
• The node on which the queue manager was running leaves the cluster.
• A new node boots into the cluster.
• You change the node list specified with the /ON qualifier of the
START/QUEUE/MANAGER command.
• You start the queue manager after moving the queue database.
13.11.3.1 Investigating the Problem
Check the operator log that was current at the time the queue manager started
up or failed over. Search the log for operator messages from the queue manager.
On systems with multiple queue managers, also search for messages displayed by
additional queue managers by including their process names in the search string.
To display information about queue managers running on your system, use the
SHOW QUEUE/MANAGERS command, as explained in Section 13.4.
For more information about multiple queue managers and their process names,
see Section 13.8.1.
The following messages indicate that the queue database is not in the specified
location:
%%%%%%%%%%% OPCOM 4-FEB-2000 15:06:25.21 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
%QMAN-E-OPENERR, error opening CLU$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$QUEUES;
%%%%%%%%%%% OPCOM 4-FEB-2000 15:06:27.29 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 4-FEB-2000 15:06:27.45 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
-SYSTEM-W-NOSUCHFILE, no such file
The following messages indicate that the queue database disk is not mounted:
%%%%%%%%%%% OPCOM 4-FEB-2000 15:36:49.15 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
%QMAN-E-OPENERR, error opening DISK888:[QUEUE_DATABASE]SYS$QUEUE_MANAGER.QMAN$QUEUES;
%%%%%%%%%%% OPCOM 4-FEB-2000 15:36:51.69 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
-RMS-F-DEV, error in device name or inappropriate device type for operation
%%%%%%%%%%% OPCOM 4-FEB-2000 15:36:52.20 %%%%%%%%%%%
Message from user QUEUE_MANAGE on MANGLR
-SYSTEM-W-NOSUCHDEV, no such device available
13.11.3.2 Cause
The queuing system does not work correctly under the following circumstances:
• If the dirspec parameter specified with the START/QUEUE/MANAGER
command (specifying the location of the queue and journal files) is not
translated exactly the same on all nodes, and the queue manager starts on
one of the affected nodes. You typically find this problem in an OpenVMS
Cluster environment when you add a system disk or move the queue
database.
13–18 Managing the Queue Manager and Queue Database