HP OpenVMS System Manager's Manual, Volume 1:...

Managing the Queue Manager and Queue Database

Stopping and Restarting the Queue Manager

Saving and Restoring the Queue Database

Using Multiple Queue Managers  

Understanding Multiple Queue Managers  

Explanations of items related to the operation of multiple queue managers follow.

Restrictions on Using Multiple Queue Managers

Multiple queue managers have the following restrictions:

• Queues running on one queue manager cannot reference queues running on a different queue manager. For example, a generic queue running on queue manager A cannot direct jobs to an execution queue running on queue manager B.



• You cannot move a job from a queue on one queue manager to a queue on a different queue manager.



• The operating system allows a maximum of five queue managers in an OpenVMS Cluster environment.

Names of Multiple Queue Managers

The process name for a queue manager is the first twelve characters of the queue manager name. The default queue manager name is SYS$QUEUE_MANAGER; the default queue manager process name is QUEUE_MANAGE. If you create an additional queue manager named PRINT_MANAGER, the process name is PRINT_MANAGE.

Know the process names of all your queue managers so that you can troubleshoot queue manager problems, as explained in Solving Queue Manager Problems.

Multiple Queue Managers' Use of Queue Database Files

Multiple queue managers share a single master file. However, a queue database with multiple queue managers contains a queue file and a journal file for each queue manager, as explained in Understanding the Queue Database.

Commands for Managing Multiple Queue Managers

By default, the following commands affect the default queue manager SYS$QUEUE_MANAGER or the queues running on the default queue manager:

• START/QUEUE/MANAGER



• ENABLE AUTOSTART/QUEUES and DISABLE AUTOSTART/QUEUES



• STOP/QUEUES/ON_NODE



• STOP/QUEUE/MANAGER/CLUSTER



• DELETE/QUEUE/MANAGER

The /NAME_OF_MANAGER qualifier allows you to specify a different queue manager for these commands.

Creating Additional Queue Managers  

To create one or more additional queue managers, follow these steps:

1. Follow steps 1 and 2 in Starting the Queue Manager and Creating a Queue Database.
2. To create an additional queue manager, enter a command in the following format:START/QUEUE/MANAGER/ADD/NAME_OF_MANAGER=name[/ON=(node,...)] [dirspec]where:

   /ADD	Creates an additional queue manager in the existing master file and creates new queue and journal files
   /NAME_OF_MANAGER=name	Creates a non-default queue manager with a name up to 31 characters long. You can create a maximum of five queue managers.
   /ON= (node,...)	Allows you to customize failover of the queue manager. For more information, see Customizing Queue Manager Failover.
   dirspec	Specifies the location of the queue and journal files, as explained in Specifying the Location of Queue and Journal Files. Use this parameter if you are creating the queue and journal files in a location other than the default.

   
   

Do not specify the /NEW_VERSION qualifier when you create an additional queue manager: multiple queue managers share a single master file. An additional queue file and journal file are created automatically for each additional queue manager.

The command in the following example creates and starts a new queue manager named BATCH_MANAGER.

$ START/QUEUE/MANAGER/ADD/NAME_OF_MANAGER=BATCH_MANAGER/ON=(A,B,*) DUA2:[QUEUES]

Creating and Moving Queues with Multiple Queue Managers  

When you create a queue with the INITIALIZE/QUEUE command, specify the name of the queue manager on which it is to run by including the /NAME_OF_MANAGER qualifier. If you do not specify the /NAME_OF_MANAGER qualifier, the queue is created to run on the default queue manager, SYS$QUEUE_MANAGER.

To move an existing queue from its original queue manager to a different queue manager, delete the queue with the DELETE/QUEUE command and re-create the queue with the INITIALIZE/QUEUE command.

Maintaining Queue Managers  

When entering DCL commands to maintain the queue manager, be sure to specify the /NAME_OF_MANAGER qualifier to specify the queue manager to which the command is to apply. If you do not specify the /NAME_OF_MANAGER qualifier, the command is executed on the default queue manager, SYS$QUEUE_MANAGER.

Example

In the following example:

• The first command creates and starts the queue manager PRINT_MANAGER and creates master, queue, and journal files.



• The second command creates and starts an additional queue manager, BATCH_MANAGER; queue and journal files are created for it automatically.



• The default queue manager SYS$QUEUE_MANAGER is not defined.



• The SHOW QUEUE/MANAGERS command displays information about the queue managers running on your system, as explained in Displaying Information About Queue Managers.

$ START/QUEUE/MANAGER/NEW_VERSION/NAME_OF_MANAGER=PRINT_MANAGER -
_$ /ON=(JADE,RUBY,*) 
$ START/QUEUE/MANAGER/ADD/NAME_OF_MANAGER=BATCH_MANAGER -
_$ /ON=(OPAL,PEARL,*) 
$ SHOW QUEUE/MANAGERS/FULL                               
Master file:  SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
 
Queue manager PRINT_MANAGER, running, on JADE::
  /ON=(JADE,RUBY,*)
  Database location:  SYS$COMMON:[SYSEXE]
 
Queue manager BATCH_MANAGER, running, on OPAL::
  /ON=(OPAL,PEARL,*)
  Database location:  SYS$COMMON:[SYSEXE] 

Stopping and Restarting the Queue Manager

Saving and Restoring the Queue Database