Technical data

Managing the Queue Manager and Queue Database
13.11 Solving Queue Manager Problems
13.11.6 If You See Inconsistent Queuing Behavior on Different OpenVMS
Cluster Nodes
Use this section if you see the following symptoms:
• After submitting a print job, you can display the job with a SHOW ENTRY
command on the same node, but not on other nodes in the OpenVMS Cluster
environment.
• After defining or modifying a queue, the changes appear in a SHOW QUEUE
display on some nodes, but not on others.
• You can successfully submit or print a job on some nodes, but on other nodes,
you receive a JOBQUEDIS error.
13.11.6.1 Investigating the Problem
Perform the following steps:
1. Enter SHOW LOGICAL to translate the QMAN$MASTER logical
name within the environment of each node in the cluster. If there is
no translation on any given node, then translate the default value of
SYS$COMMON:[SYSEXE].
If the SHOW LOGICAL translations show a different physical disk name on
one or more nodes, you have identified the problem.
2. Check the operator log files that were current at the time that one of the
affected nodes booted. Search for an OPCOM message similar to the following
one from the process JOB_CONTROL:
%%%%%%%%%%% OPCOM 4-FEB-2000 14:41:20.88 %%%%%%%%%%%
Message from user JOB_CONTROL on MANGLR
%JBC-E-OPENERR, error opening BOGUS:[QUEUE_DIR]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 4-FEB-2000 14:41:21.12 %%%%%%%%%%%
Message from user JOB_CONTROL on MANGLR
-RMS-E-FNF, file not found
13.11.6.2 Cause
This problem may be caused by different definitions for the logical name
QMAN$MASTER on different nodes in the cluster, causing multiple queuing
environments. You typically find this problem in OpenVMS Cluster environments
when you have just added a system disk or moved the queuing database.
13.11.6.3 Correcting the Problem
Perform the following steps:
1. If only one queue manager and queue database exist, skip to step 2.
If more than one queue manager and queue database exist, perform the
following steps:
a. Enter a command in the following format on one of the nodes where the
QMAN$MASTER logical name is incorrectly defined:
STOP/QUEUE/MANAGER/CLUSTER/NAME_OF_MANAGER=name
where /NAME_OF_MANAGER specifies the name of the queue manager
to be stopped.
b. Delete all three files for the invalid queue database. (On systems with
multiple queue managers, you might have more than three invalid files.)
Managing the Queue Manager and Queue Database 13–21