Document revision date: 30 March 2001 | |
![]() |
![]() ![]() ![]() ![]() |
![]() |
Previous | Contents | Index |
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 |
The queuing system does not work correctly under the following circumstances:
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:
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.
13.11.5.1 Investigating the Problem
Perform the following steps:
%%%%%%%%%%% OPCOM 4-FEB-2000 15:36:49.15 %%%%%%%%%%% Message from user QUEUE_MANAGE on ZNFNDL %QMAN-E-COMMERROR, unexpected error #5 in communicating with node CSID 000000 %%%%%%%%%%% OPCOM 4-FEB-2000 15:36:49.15 %%%%%%%%%%% Message from user QUEUE_MANAGE on ZNFNDL -SYSTEM-F-WRONGACP, wrong ACP for device_ |
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS SHOW SCSSYSTEMID Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCSSYSTEMID 19941 0 -1 -1 Pure-numbe SYSMAN> PARAMETERS SHOW SCSNODE Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCSNODE "RANDY " " " " " "ZZZZ" Ascii SYSMAN> EXIT $ RUN SYS$SYSTEM:NCP NCP> SHOW EXECUTOR SUMMARY Node Volatile Summary as of 5-FEB-2000 15:50:36 Executor node = 19.45 (DREAMR) State = on Identification = DECnet for OpenVMS V7.2 NCP> EXIT $ WRITE SYS$OUTPUT 19*1024+45 19501 |
If the DECnet node name and node ID do not match the SCSNODE and
SCSSYSTEMID system address parameters, IPC (interprocess communication,
an operating system internal mechanism) cannot work properly and the
affected node will not be able to participate in the queuing system.
13.11.5.3 Correcting the Problem
Perform the following steps:
Use this section if you see the following symptoms:
Perform the following steps:
%%%%%%%%%%% 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 |
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:
STOP/QUEUE/MANAGER/CLUSTER/NAME_OF_MANAGER=name |
where /NAME_OF_MANAGER specifies the name of the queue
manager to be stopped.
If you encounter problems with the queuing system that you need to report to a Compaq support representative, provide the information in the following table. This information will help Compaq support representatives diagnose your problem. Please provide as much of the information as possible.
Information | Description |
---|---|
Summary of the problem |
Include the following information:
|
Steps for reproducing the problem | Specify the exact steps and include a list of any special hardware or software required to reproduce the problem. |
Configuration information |
For example:
|
Output from the SHOW QUEUE/MANAGERS/FULL command |
Use SYSMAN to enter the command on all nodes, as follows:
$ RUN SYS$SYSTEM:SYSMAN Type the output file SYSMAN.LIS to verify that the output for all nodes match. |
Location of the queue and journal files | If possible, find out the most recent value that was specified in the dirspec parameter of the START/QUEUE/MANAGER command (to specify the location of the queue and journal files). If none was specified, the default is SYS$COMMON:[SYSEXE]. |
Translation of QMAN$MASTER logical name |
Verify that the translation is the same on all nodes.
Enter the following commands, and include the resulting output:
If the translations returned from the SHOW LOGICAL command are not physical disk names, repeat the SHOW LOGICAL command within the environment of each node to translate the returned value until you reach a translation that includes the physical device name. |
Operator log file output |
Enter the following commands to search the operator log for any message
output by the job controller or queue manager:
$ SEARCH SYS$MANAGER:OPERATOR.LOG/WINDOW=5 - On systems with multiple queue managers, for queue managers other
than the default, specify the first 12 characters of the queue manager
name of any additional queue manager. For example, for a queue manager
named PRINT_MANAGER, specify PRINT_MANAGE as follows:
|
Information returned from relevant DCL commands | Include this information if entering a DCL command shows evidence of the problem. |
A copy of the journal file of the queue database |
Use the Backup utility (BACKUP) with the /IGNORE=INTERLOCK qualifier to
create a copy of the file SYS$QUEUE_MANAGER.QMAN$JOURNAL, and provide
this copy to Compaq.
On systems with multiple queue managers, include copies of journal files for all queue managers. Journal files for queue managers other than the default are named in the format name_of_manager.QMAN$JOURNAL. |
Copies of any process dumps that might have been created |
Enter the following commands to find any related process dumps, and
provide copies of the files to Compaq:
$ RUN SYS$SYSTEM:SYSMAN If the problem involves an execution queue using a symbiont other than PRTSMB or LATSYM, also include process dump files from the symbiont. The file name has the format image_file_name.DMP. |
Output from the SHOW QUEUE command | If your problem affects individual queues, enter the SHOW QUEUE command to show each affected queue. |
Any other relevant information |
For example:
|
If you have a printer connected to your system, or if you want to use batch processing, you must use queues. A queue allows users to submit requests for printing or batch processing at any time; the system then prints or processes jobs as resources allow.
Before setting up queues, you need to understand how the queue manager and the queue database operate and how to create them for the OpenVMS queuing system. These are explained in Chapter 13.
Information Provided in This Chapter
This chapter describes the following tasks:
Task | Section |
---|---|
Managing queues on small systems | Section 14.1.1 |
Designing your batch queue environment | Section 14.2.1 |
Designing your output queue environment | Section 14.2.2 |
Planning your queue setup | Section 14.3 |
Creating and starting queues | Section 14.4 |
Restarting execution queues on reboot | Section 14.5 |
Using queue options | Section 14.6 |
Using and creating forms | Section 14.6.7 |
Using queue management commands | Section 14.7.1 |
Managing jobs in queues | Section 14.7.2 |
Solving queue problems | Section 14.8 |
This chapter explains the following concepts:
Concept | Section |
---|---|
Queuing process | Section 14.1 |
Types of queues | Section 14.1.2 |
Autostart feature | Section 14.1.3 |
Options for controlling access to queues | Section 14.6.1 |
Job retention | Section 14.6.2 |
Queue characteristics | Section 14.6.3 |
Batch processing options | Section 14.6.4 |
Job scheduling options | Section 14.6.5 |
Banner pages | Section 14.6.6 |
Forms and stock | Section 14.6.7 |
Page and line overflow | Section 14.6.7.8 |
Initial form feed | Section 14.6.7.9 |
Device control libraries | Section 14.6.8 |
This chapter contains many references to DCL commands. You can find additional information about all DCL commands in the OpenVMS DCL Dictionary. |
A batch or print job submitted either by entering the DCL command SUBMIT or PRINT or through an application is sent to a queue for processing. Information about the user's queue request, including the type of job, the file name or names, the name of the queue, and any special options, is sent to the queue manager. The queue manager stores and retrieves appropriate information from the queue database to print or execute the job.
The queue manager places the job in the appropriate queue to await its turn for processing. Only one print job can be printed on a printer at a single time. However, more than one batch job can execute simultaneously in a batch queue.
For more information about the queue manager and queue database, and
the operation of batch and print queues, including print symbionts, see
Chapter 13.
14.1.1 Managing Queues on Small Systems
Many features available for queues are not required on small systems with minimal queuing needs (for example, on workstations). If you are managing a small system, you probably need only the information in the following sections:
Topic | Section |
---|---|
Simple batch queue configuration | Section 14.2.1.1 |
Simple output queue configuration | Section 14.2.2.1 |
Setting up and starting queues | Section 14.3 |
Choosing and specifying queue options | Section 14.6 |
Managing queues | Section 14.7.1 |
Managing jobs in queues | Section 14.7.2 |
14.1.2 Understanding Classes and Types of Queues
In general, queues can be divided into two classes:
Class | Description |
---|---|
Execution queues | Queues that accept batch or print jobs for processing. |
Generic queues | Queues that hold jobs until an appropriate execution queue becomes available. The queue manager then requeues the job to the available execution queue. |
The following sections provide more details about execution and generic queues.
Previous | Next | Contents | Index |
![]() ![]() ![]() ![]() |
privacy and legal statement | ||
6017PRO_056.HTML |