OpenVMS Cluster Systems - OpenVMS Systems - HP

Setting Up and Managing Cluster Queues
7.7 Setting Up Print Queues
7.7.3 Ensuring Queue Availability
You can also use the autostart feature to simplify startup and ensure high
availability of execution queues in an OpenVMS Cluster. If the node on which the
autostart queue is running leaves the OpenVMS Cluster, the queue automatically
fails over to the next available node on which autostart is enabled. Autostart
is particularly useful on LAT queues. Because LAT printers are usually shared
among users of multiple systems or in OpenVMS Cluster systems, many users
are affected if a LAT queue is unavailable.
Format for creating autostart queues:
Create an autostart queue with a list of nodes on which the queue can run by
specifying the DCL command INITIALIZE/QUEUE in the following format:
INITIALIZE/QUEUE/AUTOSTART_ON=(node-name::device:,node-name::device:, . . . ) queue-name
When you use the /AUTOSTART_ON qualifier, you must initially activate
the queue for autostart, either by specifying the /START qualifier with the
INITIALIZE /QUEUE command or by entering a START/QUEUE command.
However, the queue cannot begin processing jobs until the ENABLE AUTOSTART
/QUEUES command is entered for a node on which the queue can run. Generic
queues cannot be autostart queues.
Rules: Generic queues cannot be autostart queues. Note that you cannot specify
both /ON and /AUTOSTART_ON.
Reference: Refer to Section 7.13 for information about setting the time at which
autostart is disabled.
7.7.4 Examples
The following commands make the local print queue assignments for JUPITR
shown in Figure 7–2 and start the queues:
$ INITIALIZE/QUEUE/ON=JUPITR::LPA0/START/NAME_OF_MANAGER=PRINT_MANAGER JUPITR_LPA0
$ INITIALIZE/QUEUE/ON=JUPITR::LPB0/START/NAME_OF_MANAGER=PRINT_MANAGER JUPITR_LPB0
7–6 Setting Up and Managing Cluster Queues