PATHWORKS Advanced Server software lets you share printers connected to the network. You can create a PATHWORKS Advanced Server print share for any OpenVMS print queue and assign access permissions to that share. Users can then send print jobs to the queue specified by the share as though they were using a local printer.

The procedures you use to manage shared printers are:

• Planning Printer Services --- describes how to plan printer services to meet client needs.
• Setting Up a New Printer --- describes how to set up network printers.
• Managing Print Shares --- describes how to add, display, and remove print shares.
• Managing Print Queues --- describes the management of shared print queues.
• Managing Print Jobs --- describes the management of print jobs in shared print queues.

The PATHWORKS Advanced Server makes printers available to network users through shared print queues. A print queue stores print jobs as users submit them. When a printer associated with the queue becomes available, PATHWORKS Advanced Server routes a job to that printer.

To share a printer, you create a PATHWORKS Advanced Server print share and assign the share name to a queue that points to the printer. Because PATHWORKS Advanced Server is based on the OpenVMS operating system, the print queues and the printers that you share are actually OpenVMS print queues and printers.

This chapter describes how to share printers that are physically connected to a server. You can also share local printers connected to client workstations. For PATHWORKS clients, see your client documentation.

5.1.1 OpenVMS Print Queues

See the OpenVMS System Manager's Manual and the Advanced Server for OpenVMS Concepts and Planning Guide to understand how print queues are set up on OpenVMS systems.

OpenVMS systems use execution queues and generic queues to provide access to printers as follows:

• There are one or more execution queues for each printer.
• One or more generic queues can point to multiple execution queues and, therefore, multiple printers.
• Print jobs can be submitted either to a generic queue or to an execution queue.

The PATHWORKS Advanced Server allows you to create print queues using the ADD PRINT QUEUE command, as described later in this guide.

5.1.2 Types of PATHWORKS Advanced Server Print Queues

A PATHWORKS Advanced Server print queue can be either of the following:

• A printer queue, pointing directly to a physical printer (an OpenVMS execution queue)
• A routing queue, pointing to one or more printer queues (an OpenVMS generic queue)

To support the printing needs of your users, plan print queues and print shares to meet their requirements. You can set up printers as shared devices, and you can establish constraints on print queues.

5.2.1 Sharing Printers and Print Queues

The way you make printers available to PATHWORKS Advanced Server users depends on your server installation and whether you want to share existing print queues or create new ones.

• If the printer you want to share does not have an existing OpenVMS print queue, you can create one using the procedure in Setting Up a New Printer.
• If you have installed PATHWORKS Advanced Server software on a server for the first time and the printer you want to share has an existing OpenVMS queue, you can share that queue or create and share a new queue. You can display existing print queues using the SHOW PRINT QUEUE command. You must define a PATHWORKS Advanced Server print share for every OpenVMS print queue that you want PATHWORKS Advanced Server users to access.
• If you have installed PATHWORKS Advanced Server software on a server that ran PATHWORKS V5 for OpenVMS (LAN Manager) software, and the printer you want to share was previously shared, you can use the PATHWORKS Upgrade utility to automatically convert existing print shares to PATHWORKS Advanced Server print shares, as described in the PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide.

To make a print share operational, a print queue much be established first. To establish both a print queue and a print share, first set up the print queue, then set up the print share.

You set up or establish a print share so that users can send print requests to the print share rather than to individual print queues. For Windows NT, Windows 95, and Windows 98, the share name and the queue name must be the same; for other clients, like Windows 3.11, the share and queue names can be different. Multiple print shares can point to the same print queue.

The PATHWORKS Advanced Server print queue name is limited to no more than 12 characters. If the OpenVMS print queue name has more than 12 characters, you can define an OpenVMS logical name for the print queue, to translate the queue name. You might use a logical name that is the same as the share name.

For example, the following OpenVMS command defines a logical name GLENDA for the OpenVMS print queue GLENDASPRINTER:

$ DEFINE/SYSTEM GLENDA GLENDASPRINTER

Then you can use the logical name to specify the print queue when you set up a print share for it.

PATHWORKS Advanced Server users access the print queue by specifying a print share.

5.3 Setting Up a New Printer

The information in this section applies only to printers supported by the OpenVMS operating system. If you start with no OpenVMS queue and create a PATHWORKS Advanced Server queue, PATHWORKS Advanced Server creates the OpenVMS print queue.

To set up a new printer to make it available to PATHWORKS Advanced Server clients:

1. Connect the printer to your server. Refer to your printer documentation for physical connection information.
2. Create a printer queue for the printer.
3. Create a routing print queue (optional).
4. Create a print share for the queue.

To share a PostScript printer, you must use DECprint Supervisor for OpenVMS software to create the queue, then create a PATHWORKS Advanced Server print share for the queue.

Printers supported by PATHWORKS Advanced Server software include:

• PostScript printers supported by DECprint Supervisor for OpenVMS software
• All printers supported by OpenVMS

To display the printers that are supported, enter the following command:

LANDOFOZ\\TINMAN>HELP ADD PRINT QUEUE /TYPE

5.3.2 Connecting Your Printer

When you connect your printer, make a note of the printer type and the name of the physical device or port to which it is connected. For example, the type of printer may be a DL3200 (a DEClaser 3200), and the physical device or port to which it is connected may be an LTA201.

The list of physical device connectors includes:

• OPxn
• TTxn
• TXxn
• LTxnnn

When you use OpenVMS commands to set up a printer, you create an OpenVMS print queue. When you create a PATHWORKS Advanced Server print share for an existing print queue, you make the associated printer available to PATHWORKS Advanced Server users, and you can control which users can access the print share. See Section 5.3.4, Creating a PATHWORKS Advanced Server Print Share.

You can create routing queues that point to a printer queue; this is useful if you need to set different print queue characteristics for a printer. You can also set up a PATHWORKS Advanced Server print queue to point to multiple printers. When a job reaches the start of the queue, the queue sends it to the first available printer.

To create a print queue:

Use the ADD PRINT QUEUE command. Use the SET PRINT QUEUE command to change the characteristics of an existing queue.

For each PATHWORKS Advanced Server print queue, you must specify whether it is a printer queue or a routing queue. For a printer queue, you can specify the printer device type and the port to which the printer is connected to the OpenVMS system. For a routing queue, you can specify one or more printer queues to which the print jobs in the routing queue will be sent.

For example, the following command creates a printer queue called GLENDA1 for the DEClaser 3200 printer that is connected to LTA201:

LANDOFOZ\\TINMAN> ADD PRINT QUEUE GLENDA1 /PRINTER - _LANDOFOZ\\TINMAN> /DEVICE=LTA201/TYPE=DL3200 %PWRK-S-QUEADD, queue "GLENDA" added on server "TINMAN" LANDOFOZ\\TINMAN>

The following command sets up or establishes the routing queue called GLENDA. Print jobs sent to GLENDA go to either of the two printer queues, GLENDA1 or GLENDA2. The description of the routing queue is "Glenda's routing queue."

LANDOFOZ\\TINMAN> ADD PRINT QUEUE GLENDA - LANDOFOZ\\TINMAN> /ROUTETO=(GLENDA1,GLENDA2) - _LANDOFOZ\\TINMAN> /DESCRIPTION="GLENDA's routing queue" %PWRK-S-QUEADD, queue "GLENDA" added on server "TINMAN" LANDOFOZ\\TINMAN>

5.3.4 Creating a PATHWORKS Advanced Server Print Share

To give network users access to a print queue, you share that queue over the network by creating a print share. To access the print queue, network users specify the share name associated with that queue. If you do not specify permissions when you add the print share, it is available to all users. You control user access by specifying permissions for the print share. When multiple permissions apply to a print job, the minimum permission is used.

To create a print share:

Use the ADD SHARE/PRINT command and set permissions for the share. You should add a print share based on a routing queue that points to the specific printer queue. For example:

1. Set up your routing queue.
2. Set up your print share with the same name as the routing queue.

For example, the following command sets up a print share called GLENDA. The share name is the same as the routing queue name, as required by Windows NT.

LANDOFOZ\\TINMAN> ADD SHARE/PRINT GLENDA/DESCRIPTION="GLENDA's print share" %PWRK-S-SHAREADD, share "GLENDA" added on server "TINMAN" LANDOFOZ\\TINMAN>

5.4 Managing Print Shares

The following sections describe how to set permissions on print shares to control access to the printers, how to change the characteristics of a print share, and how to stop sharing a print queue.

5.4.1 Controlling Access to Print Shares

Always set permissions explicitly on a print share; this forces the permissions set on the share to apply to the queue, so they are the same on both the share and the queue. If you do not specify permissions on a print share, the default is to allow access by all users (that is, /PERMISSIONS=(EVERYONE=FULL)). The default setting sets permissions on the share, not on the queue. Any permissions set previously on the queue are retained and not explicitly visible. Therefore, when you add a print share that points to an existing queue, the queue may have permissions retained from a previous print share, which may conflict with the permissions on the print share. To ensure that permissions are set correctly, set permissions when you set up a new print share.

The following table lists permission levels for print shares.

Table 5-1 Print Share Permissions

With this permission...	Users can...
NONE	Have no access to the share.
PRINT	Have print access to the share. Can pause and delete their own jobs.
MANAGE_DOCUMENTS	Manage print jobs; for example, pause and delete print jobs not their own.
FULL	Have full access to the share. Can modify and delete both shares and queues. This is the default if you do not specify permissions when creating the share.

As part of monitoring printer security, you can enable auditing and keep track of successful and failed attempts to access a print share. The server logs these events in the audit trail. See Chapter 6, Monitoring Events and Troubleshooting for information about enabling auditing for printer events.

To set permissions for a shared print queue:

Use the ADD SHARE/PRINT command or the MODIFY SHARE command. The following example adds a share called WESTWITCH and sets the permissions for the print share so that user SCARECROW has full access to the share, but user LION has no access to the share. The share WESTWITCH is a print share and TOTO is the name of an existing print queue.

LANDOFOZ\\TINMAN> ADD SHARE/PRINT WESTWITCH TOTO- _LANDOFOZ\\TINMAN>/PERMISSIONS=(SCARECROW=FULL,LION=NONE) - _LANDOFOZ\\TINMAN>/DESCRIPTION="Shared Print Queue in the Land of Oz" %PWRK-S-SHAREADD, share "WESTWITCH" added on server "TINMAN" LANDOFOZ\\TINMAN>

5.4.2 Changing Print Share Options

PATHWORKS Advanced Server lets you change the options for an existing print share. For example, you may want to revise the share's description. Changes you make take effect immediately for new print jobs, but do not affect jobs already in the queue, except for changes in the routing list.

The options you can change include:

• Description
• Maximum number of users (limit)
• Permissions

To change the maximum number of connections for an existing print share:

Use the MODIFY SHARE command. For example, to set the print share TOTO to have no limit on the number of client connections, enter the following command:

LANDOFOZ\\TINMAN> MODIFY SHARE TOTO/NOLIMIT/NOCONFIRM %PWRK-S-SHAREMOD, share "TOTO" modified on server "TINMAN" LANDOFOZ\\TINMAN>

To change the permissions for an existing print share:

Use the MODIFY SHARE command. The following example modifies permissions for the print share WESTWITCH, so that user LION has PRINT access to the share, and user TINY has MANAGE_DOCUMENTS access to the share.

LANDOFOZ\\TINMAN> MODIFY SHARE WESTWITCH/NOCONFIRM - _LANDOFOZ\\TINMAN>/PERMISSIONS=(LION=PRINT,TINY=MANAGE_DOCUMENTS) %PWRK-S-SHAREMOD, share "WESTWITCH" modified on server "TINMAN"

5.4.3 Displaying Information About Print Shares

You can display the print share information, including the permissions on the share.

To display information about a print share:

Use the SHOW SHARES /FULL command. For example, to display the permissions for the print share WESTWITCH, enter the following command:

LANDOFOZ\\TINMAN> SHOW SHARES WESTWITCH/FULL Shared resources on server "TINMAN": Name Type Description ----------- --------- --------------------------------------- WESTWITCH Printer Shared Print Queue in the Land of Oz Path: TOTO Connections: Current: 0, Maximum: No limit Share Permissions: Everyone Full Control LION Print TINY Manage Documents Total of 1 share LANDOFOZ\\TINMAN>

5.4.4 Stopping a Print Share

You may need to stop sharing a print share for several reasons:

• To reorganize shared print queues.
• To remove a printer, if this printer is the only printer servicing the queue.
• To remove a shared print queue that is no longer needed.

To stop sharing a print share:

Use the REMOVE SHARE command. The queue still exists and can be displayed using the SHOW PRINT QUEUE command, but it is unavailable to network users. Jobs in the print queue complete as usual. For example:

LANDOFOZ\\TINMAN> REMOVE SHARE TOTO Do you really want to remove share "TOTO" [YES or NO] (YES) : YES %PWRK-S-SHAREREM, share "TOTO" removed from server "TINMAN" LANDOFOZ\\TINMAN>

5.5 Managing Print Queues

This section provides information about displaying, modifying, and managing print queues.

5.5.1 Displaying Print Queue Information

You can display a list of the server's print queues, information about a specific queue, or information about the print jobs in each queue. To display information about the print queues on a server, use one of the following procedures.

To display information about all print queues on a server:

Use the SHOW PRINT QUEUES command. For example:

LANDOFOZ\\TINMAN> SHOW PRINT QUEUES Name Jobs Status Printer/Routing Description ----------- ---- ------------ --------------- --------------- User_PRNT 2 destination LRA0:GENERIC paused GLENDA 0 PAUSED LANDOFOZ\\TINMAN>

The PATHWORKS Advanced Server displays the queue name and status of each queue.

To display information about a single print queue:

Use the SHOW PRINT QUEUE command. For example:

LANDOFOZ\\TINMAN> SHOW PRINT QUEUE TOTO Name Jobs Status Printer/Routing Description ----------- ---- ------------ --------------- --------------- TOTO 1 printing LRA0:GENERIC LANDOFOZ\\TINMAN>

The PATHWORKS Advanced Server displays the queue name and status of the queue and the number of print jobs currently in the queue.

5.5.2 Changing the Printer Type

Specify the type of printer supported by a shared print queue using the SET PRINT QUEUE command.

To set or change a printer type:

Use the SET PRINT QUEUE command with the /TYPE qualifier. For example, the following command sets the print queue TOTO to support a DEClaser 3200 printer:

LANDOFOZ\\TINMAN> SET PRINT QUEUE TOTO/TYPE=DL3200 %PWRK-S-QUESET, characteristics set for queue "TOTO" on server "TINMAN" LANDOFOZ\\TINMAN>

5.5.3 Pausing a Print Queue

You can hold or pause a print queue; this prevents the queue from sending any jobs to printers. When you do this, printers associated with the queue finish printing their current jobs, but all further jobs stay in the queue until the queue is released.

To pause a print queue:

Use the PAUSE PRINT QUEUE command. For example:

LANDOFOZ\\TINMAN> PAUSE PRINT QUEUE TOTO Do you really want to pause print queue "TOTO" [YES or NO] (YES) : YES %PWRK-S-QUESET, queue "TOTO" paused on server "TINMAN" LANDOFOZ\\TINMAN> SHOW PRINT QUEUE Name Jobs Status Printer/Routing Description ---------- ----- ------------------ --------------- ---------------- BRUCE_PRNT 0 destination paused LRA0:GENERIC PARSIFAL 0 ACTIVE BRUCE_PRNT TOTO 0 PAUSED BRUCE_PRNT Printer in the Land of Oz LANDOFOZ\\TINMAN>

You can also pause a print queue with the SET PRINT QUEUE/PAUSE command. In the following example, the queue called BRUCE_PRNT is a printer queue that points to a physical device, LRA0:GENERIC, and the queues GLENDA and TOTO are routing queues that point to the printer queue BRUCE_PRNT.

LANDOFOZ\\TINMAN> SET PRINT QUEUE TOTO/PAUSE %PWRK-S-QUESET, queue "TOTO" paused on server "TINMAN" LANDOFOZ\\TINMAN> SHOW PRINT QUEUE Name Jobs Status Printer/Routing Description ---------- ----- ------------------ --------------- ------------ BRUCE_PRNT 0 destination paused LRA0:GENERIC GLENDA 0 ACTIVE BRUCE_PRNT TOTO 0 PAUSED BRUCE_PRNT Printer in the Land of Oz LANDOFOZ\\TINMAN>

5.5.4 Continuing a Print Queue

After you have paused a print queue, you can continue printing on the queue, returning it to normal status. Continuing a queue that is in an error condition clears the error.

To continue a print queue:

Use the SET PRINT QUEUE /CONTINUE command. For example:

LANDOFOZ\\TINMAN> SET PRINT QUEUE TOTO/CONTINUE %PWRK-S-QUESET, queue "TOTO" continued on server "TINMAN" LANDOFOZ\\TINMAN>

This example continues a paused print queue. Any jobs that were waiting in the paused print queue can now print.