Technical data

Managing the Queue Manager and Queue Database
13.11 Solving Queue Manager Problems
13.11.2.2 Cause
The cause of the problem is the system’s inability to find the queue master file.
Often the logical is not defined correctly, or the disk is not available. For example,
the following message indicates that the master queue file does not exist in the
expected location:
%%%%%%%%%%% OPCOM 13-MAR-2000 15:53:52.84 %%%%%%%%%%%
Message from user JOB_CONTROL on ABDCEF
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT
%%%%%%%%%%% OPCOM 13-MAR-2000 15:53:53.04 %%%%%%%%%%%
Message from user JOB_CONTROL on ABDCEF
-SYSTEM-W-NOSUCHFILE, no such file
13.11.2.3 Correcting the Problem
On systems with multiple queue managers, 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. Correct any
problem indicated in the displayed information.
Example
$ START/QUEUE/MANAGER DUA55:[SYSQUE] !
%JBC-E-QMANNOTSTARTED, queue manager could not be started "
$ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=5 QUEUE_MANAGE,JOB_CONTROL #
%%%%%%%%%%% OPCOM 14-APR-2000 18:55:18.23 %%%%%%%%%%%
Message from user QUEUE_MANAGE on CATNIP
%QMAN-E-OPENERR, error opening DUA55:[SYSQUE]SYS$QUEUE_MANAGER.QMAN$QUEUES;
%%%%%%%%%%% OPCOM 14-APR-2000 18:55:18.29 %%%%%%%%%%%
Message from user QUEUE_MANAGE on CATNIP
-RMS-F-DEV, error in device name or inappropriate device type for operation
%%%%%%%%%%% OPCOM 14-APR-2000 18:55:18.31 %%%%%%%%%%%
Message from user QUEUE_MANAGE on CATNIP
-SYSTEM-W-NOSUCHDEV, no such device available
$
$ START/QUEUE/MANAGER DUA5:[SYSQUE] %
!
This command attempts to start the queue manager, specifying
DUA55:[SYSQUE] as the location of the queue and journal files.
" The error message indicates that the queue manager did not start.
# This command searches the operator log file for relevant messages. The
SEARCH command does not include a second queue manager name, such as
BATCH_MANAGE.
$ This message indicates that the queue file could not be opened because device
DUA55: does not exist.
% This command, which correctly specifies DUA5:[SYSQUE] as the location for
the queue and journal files, successfully starts the queue manager.
For more information about multiple queue managers and their process names,
see Section 13.8.1.
Managing the Queue Manager and Queue Database 13–17