Technical data

Setting Up and Maintaining Queues
14.1 Understanding Queuing
14.1.2.2 Generic Queues
Descriptions of types of generic queues follow:
• Generic batch queues direct jobs only to batch execution queues. Generic
batch queues are typically used in OpenVMS Cluster environments to
distribute the batch work load across several nodes (see Section 14.2.1.3).
Generic batch queues are not automatically stopped when a node shuts down.
Therefore, they do not need to be started when a node reboots.
• Generic output queues direct jobs to any of the three types of output
execution queues: print, terminal, or server. Generic output queues are
typically used to distribute the output work load among several like printers
(see Section 14.2.2.5).
Generic output queues are not automatically stopped when a node shuts
down. Therefore, they do not need to be started when a node reboots.
• Logical queues are a special type of generic output queue that transfers
jobs to another output execution queue. You might use a logical queue to
temporarily redirect a queue when the device on which it runs is broken.
A logical queue transfers its jobs into the execution queue specified with the
ASSIGN/QUEUE command. For information about setting up a logical queue,
see Section 14.7.1.10.
14.1.3 Understanding Autostart Queues
Compaq recommends that you use autostart queues whenever possible for a
variety of reasons. Autostart queues simplify startup and ensure high availability
of execution queues, allowing you to perform the following tasks:
• With a single command, start all autostart queues on a node
• Specify a list of nodes (in an OpenVMS Cluster environment) to which a
queue can automatically attempt to fail over
Autostart failover is particularly useful on LAT queues. Because LAT printers
are usually shared among users of multiple systems or OpenVMS Cluster
systems, many users are affected if a LAT queue is unavailable. For highest
availability, set up your LAT queues with a list of nodes to which the queue
can fail over, so the queue can continue to run even if a node becomes
unavailable.
To use autostart queues, you must perform the following three steps:
Task Description
1 Create the queue as an autostart queue and, optionally, specify a failover list.
2 Activate the queue for autostart. You can do this either when you create a
queue, or after you create one.
3 Enable autostart on a node. You can do this before or after you create a queue.
When you enable autostart on a node, the queue manager automatically starts
all stopped, active autostart queues capable of running on the node. Any
autostart queue that fails over to the node is also automatically started.
Section 14.3 explains these steps in detail.
14–4 Setting Up and Maintaining Queues