Document revision date: 15 July 2002

Figure 14-8 shows a typical OpenVMS Cluster output queue configuration. For information about OpenVMS Cluster queue configurations, refer to OpenVMS Cluster Systems.

Figure 14-8 Output Queue Configuration in an OpenVMS Cluster

If your system runs application programs that write output directly to a printer rather than submit it to an output queue, or if you will be using LAT queues, spool your printers. Spooling your printers causes application programs to write output to an intermediate storage device so that the printer remains available to other users while the program is running.

Figure 14-9 shows an output configuration with spooled printers.

Figure 14-9 Queue Configuration with Spooled Devices

For more information about spooling printers, see Section 8.8.2.1.

14.2.2.8 Distributing Printing

The OpenVMS batch and print queuing system enables users to print files on output devices attached to the local system or OpenVMS Cluster system.

The Distributed Queuing Service (DQS) layered product extends the printing capabilities of the OpenVMS queuing system to a distributed environment. DQS enables users to print files on output devices attached to remote nodes in your network.

For more information, refer to the DQS documentation or your Compaq support representative.

14.3 Planning Your Queue Setup

You must create queues for users to submit jobs; you must start the queues so that jobs can begin processing. To set up and start queues, follow these steps:

Step	Task	For More Information
1	Make sure you have started the queue manager and created the queue database.	Section 13.5
2	If your configuration includes output queues, set up output devices and create a command procedure to set up the devices on reboot.	Section 14.3.1
3	If you plan to use any queue options, such as forms, characteristics, and banner pages, determine the qualifiers needed to specify those options. In addition, define any forms and characteristics you will use before you create queues. (Because of the length of the instructions for this step, the corresponding section in the manual follows the section for step 5.)	Section 14.6
4	Create and start queues.	Section 14.4
5	Create a command procedure to perform the necessary setup tasks each time your system reboots.	Section 14.5

14.3.1 Setting Up Output Devices

Before creating output queues, you must set up the devices to which the queues will direct output.

How to Perform This Task

1. Install any printers, plotters, and other output devices to which your users will have access. For information, refer to the documentation provided with the hardware.
2. If you will use LAT printers, create logical LAT ports. You must create a logical LAT port on each service node to which a LAT printer is to be available, and associate the logical port with a physical port or service on the terminal server node. To do so, use the LATCP commands CREATE PORT and SET PORT. For more information, refer to the OpenVMS System Management Utilities Reference Manual.
3. Set device characteristics for line printers and printers attached to terminal ports. To do so, use a series of SET commands. For more information, see Section 8.8.1. In step 5, you create a command procedure to set up your devices each time the system reboots. The commands you enter to set device characteristics must be included in this command procedure.
4. Spool printers. If you use LAT printers, or if you run applications that write output directly to a printer, spool your printers. For more information about spooled printers, see Section 14.2.2.7.
   To spool a printer, use the SET DEVICE/SPOOLED command, as explained in Section 8.8.2.1.
5. Create a command procedure to set up your device characteristics and spool printers each time the system reboots. You must include the commands you entered in steps 3 and 4 in the command procedure. (Include the commands you entered to set up logical ports in step 2 in your site-specific LAT startup command procedure SYS$MANAGER:LAT$SYSTARTUP.COM.)
   If your configuration is simple, you can add the commands to SYSTARTUP_VMS.COM. If your configuration requires a large number of commands, create a separate command procedure (for example, DEVICE_SETUP.COM), and execute it from SYSTARTUP_VMS.COM. In the command procedure, a SET TERMINAL command must precede a SET DEVICE/SPOOLED command for the same output device.

Example

$ SET PRINTER/TAB/PAGE=66/WIDTH=132/LOWER/FF/NOCR - _$ /FALLBACK/NOWRAP/NOTAB LPA0:(1) $ SET TERMINAL/SPEED=9600/PAGE=100/WIDTH=200/DEVICE=LN03/NOBROADCAST - _$ /NOECHO/HARDCOPY/NOTYPE_AHEAD/NOFORM/NOWRAP/PASTHRU/PERMANENT LTA3331:(2) $ SET DEVICE/SPOOLED=(LPA0,SYS$SYSDEVICE) LPA0:(3) $ SET DEVICE/SPOOLED=(LN03_1,SYS$SYSDEVICE) LTA3331:(4)

This example performs the following actions:

1. Sets parameters for the line printer device
2. Sets parameters for the LAT printer device
3. Spools device and creates queue called LPA0
4. Spools device and creates queue called LN03_1

Create queues in the following order:

1. Execution queues
2. Generic queues

For detailed instructions on creating and starting queues, see the following sections:

Task	For More Information
Autostart execution queues	Section 14.4.1
Nonautostart execution queues	Section 14.4.2
Generic queues	Section 14.4.3

14.4.1 Creating and Starting Autostart Execution Queues

To create and start an autostart execution queue, complete these tasks:

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.

Example

$ INITIALIZE/QUEUE/START/DEFAULT=(NOBURST,FLAG=ALL,TRAILER=ONE) - _$ /AUTOSTART_ON=(LILITH::LPA0:,SMITTN::LPA0:) LPA0(1) $ INITIALIZE/QUEUE/START/DEVICE=TERMINAL/ - _$ /AUTOSTART_ON=(LILITH::LTA3331:,SMITTN::LTA555:) - _$ /RECORD_BLOCKING/BLOCK_LIMIT=600/CHARACTERISTICS=(EAST)- _$ /SEPARATE=(NOBURST,NOTRAILER,NOFLAG,RESET=ANSI$RESET) - _$ /DEFAULT=(NOFEED,NOBURST,FLAG=ONE,NOTRAILER,FORM=MEMO) - _$ /LIBRARY=LN03LIBRARY /PROCESSOR=LATSYM LN03_1(2) $ ENABLE AUTOSTART/QUEUES(3) $ ENABLE AUTOSTART/QUEUES/ON_NODE=SMITTN(4)

The commands in this example perform the following tasks:

1. Creates an autostart queue named LPA0 and activates it for autostart. Because this is an autostart queue with a failover list, this queue can run on either LILITH::LPA0 or SMITTN::LPA0.
2. Creates an autostart queue named LN03_1 for LAT printers and activates it for autostart. Because this is an autostart queue with a failover list, this queue can run on either of the printers attached to LAT ports LTA3331: on node LILITH or LTA555: on node SMITTN.
3. Enables autostart on the node on which the process is running. Assume this is node LILITH. Because both LPA0 and LN03_1 are active autostart queues capable of running on node LILITH, these queues will start up on this node.
4. Enables autostart on node SMITTN. If LILITH becomes unavailable, both LPA0 and LN03_1 can fail over to node SMITTN.

Detailed explanations of each task follow.

14.4.1.1 Creating an Autostart Queue

To create an autostart execution queue, use the /AUTOSTART_ON qualifier with the INITIALIZE/QUEUE command, as shown in the following table:

For...	Use This Command...
Output queues	INITIALIZE/QUEUE/AUTOSTART_ON=(node::[device:] [,...]) queue-name For node::, specify the name of the node on which the queue is to run. For device:, specify the name of the output device to which the queue's output is sent. To allow the autostart queue to fail over to another node and device, specify a list of nodes and devices, separated by commas.
Batch queues	INITIALIZE/QUEUE/BATCH/AUTOSTART_ON=(node:: [,...]) queue-name The /BATCH qualifier creates a batch queue. For node::, specify the name of the node on which the queue is to run. To allow the autostart queue to fail over to another node, specify a list of nodes, separated by commas.

How to Specify a Failover List

As the table indicates, to specify a failover list:

• For output queues, replace device with a list of failover devices.
• For batch queues, replace node with a list of failover nodes.

You must activate an autostart queue in one of the following ways:

• Use the /START qualifier in the INITIALIZE/QUEUE command used to create the queue, as follows:

  INITIALIZE/QUEUE/START/AUTOSTART_ON[/qualifiers,...] queue-name

• Enter START/QUEUE after you create the queue, as follows:

  START/QUEUE[/qualifiers,...] queue-name

How to Start a Deactivated Queue

To start an autostart queue that has been deactivated by STOP/QUEUE/NEXT or STOP/QUEUE/RESET, enter START/QUEUE. The queue is then automatically started by the queue manager either:

• Immediately if a node on which the queue can run is enabled for autostart
• As soon as a node on which the queue can run is enabled for autostart

You must enable autostart on a node to start autostart queues. You can do this either before or after you create an autostart queue. Perform the following steps to enable autostart:

1. For each node on which you want autostart queues to run (including those to which the queues can later fail over), enter the following command:

   $ ENABLE AUTOSTART/QUEUES

   
   Enabling autostart on a node notifies the queue manager to automatically perform the following tasks:

   • Start all active and valid autostart queues on the node
   • Start any active autostart queue that fails over to the node
   
   By default, the command affects the node from which it is entered. Specify the /ON_NODE qualifier to enable autostart on a different node.

   Note The ENABLE AUTOSTART/QUEUES command starts only valid, active autostart queues capable of running on a node. If an autostart queue does not start when you enter this command, the queue might not be active for autostart. You must activate autostart queues, as explained in Section 14.4.1.2.

2. Add the ENABLE AUTOSTART/QUEUES command to your startup command procedure on each node that is to run autostart queues to ensure that autostart is enabled each time the node reboots.

How to Start Stopped Autostart Queues

You can start all stopped active autostart queues on a node by enabling autostart for queues with ENABLE AUTOSTART/QUEUES. Including a separate START/QUEUE command to start an active autostart queue is not necessary.

When a node reboots, autostart is disabled until you enter ENABLE AUTOSTART/QUEUES.

14.4.1.4 Adding Commands to Your Startup Procedure

Compaq recommends that you add ENABLE AUTOSTART/QUEUES to your startup procedure on all of your nodes. Add this command following the commands that configure printer devices and mount important disks. Adding the command eliminates the necessity of adding it later, if you need to add autostart queues or add nodes to autostart queue failover lists.

The following example illustrates some sample commands that you might add to a node's SYSTARTUP_VMS.COM procedure:

$! Start the nonautostart batch queue $ START/QUEUE SYS$BATCH $! Start all autostart queues $ ENABLE AUTOSTART/QUEUES

For more examples, see the SYS$MANAGER:SYSTARTUP_VMS.COM template on your system disk.

14.4.2 Creating and Starting Nonautostart Execution Queues

This section describes how to create and start a nonautostart queue.

Example

The following example creates a batch queue named SYS$BATCH and starts the queue on LILITH:

$ INITIALIZE/QUEUE/START/BATCH/ON=LILITH::SYS$BATCH

14.4.2.1 Creating a Nonautostart Queue

To create a nonautostart execution queue, use the /ON qualifier with the INITIALIZE/QUEUE command, as shown in the following table:

Type of Queue	Command
Output queues	INITIALIZE/QUEUE/ON=node::device: queue-name For node::, specify the node on which the queue is to execute. For device:, specify the device to which the queue's output is sent.
Batch queues	INITIALIZE/QUEUE/BATCH/ON=node:: queue-name The /BATCH qualifier is required to create a batch queue. For node::, specify the node on which the queue is to execute.

14.4.2.2 Starting a Nonautostart Queue

You must start a nonautostart queue in one of the following ways:

• Enter the /START qualifier in the INITIALIZE/QUEUE command that you use to create the queue, with the following format:

  INITIALIZE/QUEUE/START/ON[/qualifiers,...] queue-name

• Enter START/QUEUE after you create the queue, using the following format:

  START/QUEUE[/qualifiers,...] queue-name

  
  For each nonautostart queue, you must include a START/QUEUE command naming the queue in your startup command procedure.

This section describes how to create and start a generic queue.

14.4.3.1 Creating a Generic Queue

To create a generic queue, use the /GENERIC qualifier with the INITIALIZE/QUEUE command, as shown in the following table:

Type of Queue	Command
Output queue	INITIALIZE/QUEUE/GENERIC[=(queue-name[,...])] queue-name The /GENERIC qualifier specifies that the queue is a generic queue. For the first queue-name, specify the execution queue to which the generic queue sends jobs. For the second queue-name, specify the generic queue to which output is sent.
Batch queues	INITIALIZE/QUEUE/BATCH/GENERIC[=(queue-name[,...]) queue-name The /BATCH qualifier is required to create a batch queue. For queue-name, specify the execution queue to which the generic queue sends jobs. The execution queue must be a batch queue.

You can also set up a generic queue without explicitly naming the execution queues to which it may send jobs. Instead, use the /ENABLE_GENERIC qualifier with INITIALIZE/QUEUE, START/QUEUE, or SET QUEUE for the execution. This method is not normally recommended. However, if your queue configuration is simple, you can use this method.

Example

The following example creates a generic queue (LN03_PRINT), which lists execution queues to which LN03_PRINT sends jobs:

$ INITIALIZE/QUEUE/GENERIC=(LN03_1,LN03_2,LN03_3) LN03_PRINT

14.4.3.2 Starting a Generic Queue

You must start a generic queue in one of the following ways:

• Use the /START qualifier in the INITIALIZE/QUEUE command used to create the queue, using the following format:

  INITIALIZE/QUEUE/START/GENERIC(=queue-name[,...])[/qualifiers, ...] queue-name

• Enter START/QUEUE after you create the queue, using the following format:

  START/QUEUE[/qualifiers,...] queue-name

Information about forms, characteristics, and queues is stored in the queue database. For this reason, creating forms, queues, and characteristics each time the node or OpenVMS Cluster system reboots is unnecessary. However, you must start nonautostart execution queues and enable autostart each time a node reboots. To do so, create a command procedure.

If your configuration is simple, you can add the commands to the site-specific startup command procedure SYSTARTUP_VMS.COM. If your configuration requires a large number of commands, create a separate command procedure and execute it from SYSTARTUP_VMS.COM.

Generic queues are not automatically stopped when a node shuts down. Therefore, including commands to start generic queues in your startup command procedure is unnecessary.

	privacy and legal statement
6017PRO_059.HTML