DEC Distributed Queuing Service for OpenVMS Systems_______________________________________ Documentation Set Part Number: AA-Q5FVA-TE This manual consists of guides for the user, the system manager, and the software installer. These guides describe how to use, configure and manage, and install the DEC Distributed Queuing Service for OpenVMS Systems software on OpenVMS AXP and OpenVMS VAX systems. Revision/Update Information: This manual supersedes the VAX Distributed Queuing Service User's Guide (AA-KM86B-TE), the VAX Distributed Queuing Service Management Guide (AA- KM87B-TE), the VAX Distributed Queuing Service Installation Guide (AA-KM94B- TE), and the DEC Distributed Queuing Service for OpenVMS AXP Installation Guide (AA-PW1SA-TE). Operating System and Version: OpenVMS AXP Version 6.1 or higher. OpenVMS VAX Version 5.5-2 or higher. Future maintenance releases may require higher versions. Software and Version: DEC Distributed Queuing Service Version 1.3 for OpenVMS Systems. Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Printing, March 1994 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1994. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, DEC, DECnet, DECwindows, Digital, OpenVMS, OpenVMS AXP, TK, VAX, VAXcluster, VAX DOCUMENT, VMScluster, and the DIGITAL logo. Motif is a registered trademark of Open Software Foundation, Inc. All other trademarks and registered trademarks are the property of their respective holders. S2439 This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. xi Part I User's Guide 1 Using the DQS Software Understanding the Software......................... 1-2 Getting Help With DQS.............................. 1-5 2 Printing Files Using DQS Software Printing in Network Environments................... 2-2 Understanding Print Job Messages................... 2-5 Printing with Forms................................ 2-6 Using PRINT Command Qualifiers..................... 2-7 Understanding PRINT Command Error Messages ........ 2-11 3 Viewing the Status of Print Jobs The QSHOW Command.................................. 3-2 Checking the Status of a Print Job................. 3-3 Using QSHOW Command Qualifiers..................... 3-5 Understanding QSHOW Error Messages................. 3-7 iii 4 Deleting Print Jobs From a Queue The QDELETE/ENTRY Command.......................... 4-2 Deleting a Print Job............................... 4-3 Understanding QDELETE Error Messages............... 4-4 5 Modifying the Characteristics of a Job The QSET/ENTRY Command............................. 5-2 Modifying a Print Job.............................. 5-3 Using QSET Command Qualifiers...................... 5-4 Understanding QSET Error Messages.................. 5-6 6 Spooling Files to a Client Queue Part II System Manager's Guide 7 Understanding the DEC Distributed Queuing Service Overview of the DQS Software....................... 7-2 Primary Functions of the DQS Software.............. 7-5 Functions of the DQS Commands...................... 7-7 Functions of DQS Software Components............... 7-9 The DQS Notification Service....................... 7-12 The DQS Symbionts.................................. 7-14 Defining Forms on Client and Server Nodes.......... 7-16 The DQS Server Account............................. 7-17 The Significance of Parameter 8 in DQS Printing.... 7-18 Configuring DQS Software........................... 7-19 Using Daisy-Chained Queues......................... 7-21 DQS Error Conditions............................... 7-24 DQS Security Issues and Access Rights.............. 7-28 Processes Created by DQS Software.................. 7-29 Devices Supported by DQS Software.................. 7-30 Batch Jobs and DQS Printing........................ 7-31 iv 8 Configuring and Managing a DQS Server Overview of Server Management...................... 8-2 Defining Server System Logical Names............... 8-3 Modifying Definitions of Certain Logical Names..... 8-5 Before You Set Up Remote Queues.................... 8-6 Understanding How to Set Up Remote Queues.......... 8-7 Understanding the Configuration File............... 8-8 Setting Up Remote Queues........................... 8-10 Enabling Network Access............................ 8-11 Denying Client Node Authorization to the DQS Server............................................. 8-13 Granting Client Node Authorization to the DQS Server............................................. 8-14 Making Your Changes Take Effect.................... 8-16 Determining How Clients are Accessing a Server..... 8-17 Controlling the Note on the Job Banner Page........ 8-23 Enabling Status Messages for Queues................ 8-25 Enabling the DQS Print Symbiont To Control Remote Queues............................................. 8-27 Specifying the Scanning Interval for Server Notification....................................... 8-29 Specifying a Directory for PrintServer Log Files... 8-31 Specifying the Priority of the Server Process...... 8-33 Specifying the Maximum Priority of DQS Print Jobs............................................... 8-34 Specifying the Duration of Links to Client Nodes... 8-35 Move the Server Account Directory to Another Device............................................. 8-37 Advanced VMScluster DQS Configurations............. 8-39 Specifying Unique Notifier Lock Names in a VMScluster Environment............................. 8-40 Redefining DQS$SERVER_CONFIG_DAT_FILE and DQS$SERVER_CONFIG_TXT_FILE......................... 8-41 Specifying Remote Queues on a VMScluster System.... 8-43 Configuring Daisy-Chained Queues................... 8-44 Summary of Server Tasks............................ 8-46 v 9 Configuring and Managing a DQS Client Overview of Client Management...................... 9-2 Managing Client Processes.......................... 9-3 Creating Client Queues with DQS$IMPORT.COM......... 9-4 Creating Client Queues with More Advanced Methods............................................ 9-6 Temporarily Changing the Definition of a Client Queue.............................................. 9-13 Deleting Client Queues............................. 9-15 Configuring Client Nodes in a VMScluster Environment........................................ 9-16 Synchronizing Client and Server Forms Definitions........................................ 9-17 Spooling to a Client Queue......................... 9-19 Controlling the Note on the Job Banner Page........ 9-22 Regulating Forms Checking.......................... 9-24 10 Troubleshooting General Troubleshooting Guidelines................. 10-2 Running the IVP.................................... 10-3 Problem: Remote Notification Is Not Working for Any Jobs............................................... 10-6 Problem: Notification of Print Job Completion Is Not Occuring for Some Jobs......................... 10-7 Problem: Jobs Remain in the Remote Queue With Completion Status.................................. 10-8 Problem: A Job Is Not Printing..................... 10-9 Problem: Many DQS Client Queues Slow Down the Network............................................ 10-18 Part III Installation Guide 11 What You Need to Know Required Hardware and Software..................... 11-3 Licensing.......................................... 11-5 Processes Created.................................. 11-6 First-time Installation Considerations............. 11-7 Upgrade Considerations............................. 11-8 Time Required to Install........................... 11-10 vi 12 Do This First Inspect the Distribution Kit....................... 12-2 Review DQS Installation............................ 12-4 Prepare for VMScluster Installation................ 12-5 Log In to a Privileged Account..................... 12-6 Access Online Release Notes........................ 12-8 Determine Process Account Quotas................... 12-9 Determine Disk Space............................... 12-11 Set Up an Alternate Working Device................. 12-13 Register Your License.............................. 12-16 Perform System Maintenance Procedures.............. 12-18 Perform First-Time Installation Activities......... 12-22 Back Up Your System Disk........................... 12-25 13 Using the PCSI Utility Accessing Release Notes............................ 13-2 Starting the Installation: DCL Interface........... 13-3 Obtaining DCL Help................................. 13-7 Determining Installation Defaults: DCL Interface... 13-8 Verifying Preinstallation Tasks: DCL Interface..... 13-9 Stopping and Restarting: DCL Interface............. 13-11 Responding to Questions: DCL Interface............. 13-12 Determining Installation Progress: DCL Interface... 13-14 Starting the Installation: Motif Interface......... 13-15 Obtaining Motif Help............................... 13-18 Selecting Product Options: Motif Interface......... 13-20 Stopping and Restarting: Motif Interface........... 13-21 Recovering from Errors............................. 13-22 14 Using the VMSINSTAL Utility Accessing Release Notes with VMSINSTAL............. 14-2 Starting the Installation Procedure................ 14-5 Stopping and Restarting the VMSINSTAL Procedure.... 14-7 Responding to Installation Questions............... 14-8 Following Installation Progress.................... 14-12 vii 15 After Installing DQS Software Postinstallation Tasks: New Server Installation.... 15-2 Postinstallation Tasks: New Client Installation.... 15-4 Postinstallation Tasks for All Systems: New Installation....................................... 15-5 Postinstallation Tasks: Upgrade Server Installation....................................... 15-8 Postinstallation Tasks: Upgrade Client Installation....................................... 15-11 Postinstallation Tasks for All Systems: Upgrade Installation....................................... 15-13 Postinstallation Tasks: VMScluster Nodes........... 15-16 Part IV Appendixes A DQS User Messages Message Section.................................... A-2 B DQS System Manager Messages DQS Message Format................................. B-2 Submitting a Software Performance Report........... B-3 Message Section.................................... B-4 C Server and Client System Logical Names DQS Product Logical Names.......................... C-2 DQS Server Logical Names........................... C-4 Client Logical Names............................... C-7 D Using DQS With Various Symbionts How Various Symbionts Function..................... D-2 Modifying Your Symbiont To Output Client Job Information........................................ D-3 viii E Files Installed or Modified on the System Files Installed on Server Nodes.................... E-2 Files Installed on Client-Only Nodes............... E-6 Files Modified by the Installation................. E-8 Accounts and Processes Added....................... E-9 Installed Images................................... E-11 F Sample Installations Sample PCSI Installation on an OpenVMS System...... F-2 Sample VMSINSTAL Installation on an OpenVMS AXP System............................................. F-6 G DQS Installation Messages Installation Error Messages........................ G-3 IVP Error Messages................................. G-4 Error Reporting.................................... G-5 Glossary Index Examples 7-1 A DQS Error That Prevents a Print Job From Transferring........................ 7-25 7-2 A DQS Error That Stops a Client Queue.... 7-27 8-1 Viewing NETSERVER.LOG Information........ 8-17 8-2 Logging Client Access to a Server........ 8-18 8-3 Looking at DQS$SERVER.NODES ............. 8-19 8-4 Enabling Client Accounting Information... 8-22 8-5 Defining a Status Message for a Queue.... 8-26 8-6 Enabling the DQS Print Symbiont.......... 8-28 8-7 Specifying the Scanning Interval for DQS$NOTIFIER............................. 8-30 8-8 Specifying a Directory for PrintServer Log Files................................ 8-31 ix 8-9 Specifying the Priority of the Server Process.................................. 8-33 8-10 Specifying the Maximum Priority for Queuing Print Jobs....................... 8-34 8-11 Specifying the Duration of Links to Inactive Clients......................... 8-36 8-12 Specifying Unique Notifier Lock Names in a Nonhomogeneous VMScluster.............. 8-40 9-1 Creating a Client Queue with DQS$IMPORT.COM........................... 9-5 9-2 Creating Client Queues With DQS$DEFINE.COM........................... 9-7 9-3 Defining Generic Client Queues........... 9-10 9-4 Defining Logical Client Queues........... 9-12 9-5 Temporarily Changing the Remote Queue.... 9-14 9-6 Setting Up a LAT Port Device............. 9-19 9-7 Changing Client Queue Spooled to LTA999: Device................................... 9-20 9-8 Spooling to a LAT Port Device............ 9-20 9-9 Regulating Forms Checking on Many Client Systems.................................. 9-26 F-1 Sample PCSI Client Installation on an OpenVMS System........................... F-2 F-2 Sample PCSI Server Installation on OpenVMS VAX System....................... F-4 F-3 Sample VMSINSTAL Client Installation on an OpenVMS AXP System.................... F-6 F-4 Sample VMSINSTAL Server Installation on OpenVMS VAX System....................... F-10 Tables 1 Additional Information................... xvi 2 Conventions.............................. xvii 2-1 PRINT Command Qualifiers That Function Differently with DQS Printing............ 2-7 5-1 QSET/ENTRY Command Qualifiers That Function Differently with DQS Printing... 5-4 7-1 Summary of DQS Commands.................. 7-6 x 7-2 Functions of the DQS Software Components............................... 7-9 8-1 Summary of Server Node Management Tasks.................................... 8-46 11-1 Summary: What You Need to Know........... 11-1 11-2 Prerequisite Software.................... 11-4 12-1 Preinstallation Task Summary............. 12-1 12-2 Process Quotas for the Installation Account.................................. 12-9 12-3 Disk Space Requirements.................. 12-11 12-4 Minimum Required System Parameter Values................................... 12-18 13-1 PCSI Installation Task Summary........... 13-1 13-2 Features You Can Request When Starting an Installation............................. 13-5 14-1 VMSINSTAL Installation Task Summary...... 14-1 15-1 Task Summary............................. 15-1 E-1 Files Installed on DQS Server Nodes...... E-2 E-2 Files Installed on DQS Client-Only Nodes.................................... E-6 xi ________________________________________________________________ Preface ABOUT THE SOFTWARE The DEC Distributed Queuing Service (DQS) for OpenVMS Systems software enables you to print files on devices that are attached to remote DECnet systems on your network. DQS software also allows you to display the status of your jobs at any time during their processing and to delete or modify your print jobs. The DEC Distributed Queuing Service Version 1.3 for OpenVMS systems software product replaces the following products: o VAX Distributed Queuing Service Version 1.2 software o DEC Distributed Queuing Service for OpenVMS AXP Version 1.2 software This product is based on a client/server design, where two components of software (client and server) cooperate to make the print service function. PARTS OF THE MANUAL This manual contains: o A user's guide that describes how to use the DQS software o A system manager's guide that describes the concepts of the DQS software and how to configure and manage DQS client and server systems xi o An installation guide that describes how to install the DQS software on OpenVMS AXP or OpenVMS VAX systems using the VMSINSTAL utility or the POLYCENTER Software Installation utility At the back of this document are two Reader's Comments forms. If you have any comments about this document, fill out the form and mail it; your comments will be considered for any future revision of the guide. AUDIENCE This manual is for: o Anyone who wants to print files to printers on remote OpenVMS systems. A knowledge of the Digital Command Language (DCL) PRINT, SHOW/QUEUE, DELETE/ENTRY, and SET QUEUE/ENTRY commands is assumed. o DECnet network or system managers who are responsible for installing, configuring, and managing the DQS software in their network. xii ________________________________________________________________ Document Structure USER'S GUIDE Part I, the user guide, has the following chapters: __________________________________________________________ Chapter___Describes_______________________________________ Chapter The DQS software and its capabilities, in brief 1 Chapter Printing files on remote nodes, including PRINT 2 command qualifiers and possible error conditions Chapter Displaying the status of print jobs 3 Chapter Deleting a print job 4 Chapter Modifying the characteristics of a print job 5 Chapter Spooling files to a client queue 6_________________________________________________________ SYSTEM MANAGER'S GUIDE Part II, the system manager's guide, has the following chapters: __________________________________________________________ Chapter___Describes_______________________________________ Chapter The DEC Distributed Queuing Service for OpenVMS 7 Systems and its functions, including how the software can be configured and how the software handles error conditions Chapter Configuring and managing a DQS server system 8 Chapter Configuring and managing a DQS client system 9 Chapter Quidelines for troubleshooting problems with the 10________DQS_software____________________________________ xiii INSTALLATION GUIDE Part III, the installation guide, has the following chapters: __________________________________________________________ Chapter___Describes_______________________________________ Chapter Requirements for installing the DQS software 11 Chapter Preinstallation requirements 12 Chapter Installing the DQS software using the PCSI 13 utility Chapter Installing the DQS software using the VMSINSTAL 14 utility Chapter Postinstallation tasks 15________________________________________________________ APPENDIXES Part IV has the following appendixes: __________________________________________________________ Appendix____Describes_____________________________________ Appendix A DQS messages users may see Appendix B DQS messages system managers may see Appendix C DQS server and client system logical names Appendix D How the DQS software functions with various print symbionts Appendix E Files installed and modified on your system Appendix F Sample installation logs Appendix_G__DQS_messages_installers_may_see_______________ xiv ________________________________________________________________ Associated Documentation DQS INFORMATION The DEC Distributed Queuing Service for OpenVMS Systems information set consists of: o DEC Distributed Queuing Service for OpenVMS Systems Documentation Set o DQS, PRINT, QDELETE, QSET, and QSHOW entries in the OpenVMS HELP facility o Online Command Reference Card in SYS$HELP:DQS_COMMAND_ REF.PS o Online Release Notes in SYS$HELP:DQS013.RELEASE_NOTES o DEC Distributed Queuing Service for OpenVMS Systems Cover Letter o DEC Distributed Queuing Service for OpenVMS Systems Software Product Description (SPD) xv OTHER RESOURCES Resources listed in Table 1 may also be useful. Table_1_Additional_Information__________________________________ For_information_on_._._.________See_the_following_._._._________ The OpenVMS Digital Command OpenVMS DCL Dictionary Language (DCL) commands Extensions to the DCL language DECprint Supervisor for OpenVMS for PostScript printers User's Guide Understanding OpenVMS system OpenVMS System Messages and error messages Recovery Procedures Reference Manual or the online HELP /MESSAGE facility OpenVMS system management, in OpenVMS System Manager's Manual general and OpenVMS System Manager's Utilities Reference Manual The POLYCENTER Software Software Integrator User's Guide Installation utility How to license a product OpenVMS License Management ________________________________Utility_Manual__________________ xvi ________________________________________________________________ Conventions Table 2 lists the conventions used in this guide. Table_2_Conventions_______________________________________ Convention_____________Meaning____________________________ OpenVMS system Means both the OpenVMS AXP operating system and the OpenVMS VAX operating system. UPPERCASE TEXT Indicates the name of a command, a file, a parameter, a procedure, or utility. $ PRODUCT In interactive examples, prompts or displayed text appears in a monospace font. User input appears in a bold monospace font. lowercase italics Indicates variables in command syntax or examples for which the user supplies a value. Ctrl/x In interactive examples, a sequence such as Ctrl/x indicates that you must hold down the Ctrl key while you press another key or a pointing device button; for example, Ctrl/C or Ctrl/Z. Return Indicates the Return key. [ ] In command formats, square brackets encloses optional values. (Do not type the brackets.) In installation prompts, square brackets enclose a default value. (continued on next page) xvii Table_2_(Cont.)_Conventions_______________________________ Convention_____________Meaning____________________________ In a file specification, square brackets serve as delimiters for a _______________________directory_name.____________________ xviii Part I ________________________________________________________________ User's Guide This part describes how to use the DQS software on OpenVMS AXP and OpenVMS VAX systems. The User's Guide is intended for anyone who wants to print, track, delete, or modify jobs on a remote printer in the network. 1 ________________________________________________________________ Using the DQS Software ABOUT THIS CHAPTER This chapter: o Provides an overview of the DEC Distributed Queuing Service for OpenVMS Systems software o Explains how to get help when using the DQS commands Using the DQS Software 1-1 ________________________________________________________________ Understanding the Software WHAT DQS CAN DO FOR YOU The DEC Distributed Queuing Service for OpenVMS Systems is a software product that enables you to: o Print files on printers connected to remote systems in your network. o Show the status of your print jobs on remote systems. o Delete your print jobs from remote systems. o Set the characteristics of your print jobs on remote systems. Using DQS software, you can: o Print files on any printer in your network. o Take advantage of special printers that might not be physically connected to your local system. o Print files even if your system has no printers connected. o Distribute reports efficiently to remote sites within your company or organization through both local and wide area networks. WHAT YOU NEED TO KNOW If you know how to print files on OpenVMS systems, you know how to use most DQS features. The DQS commands (PRINT, QSHOW, QSET, and QDELETE) look and function the same as the Digital Command Language (DCL) PRINT, SHOW, SET, and DELETE commands. To use DQS software, you do not need to log in to a remote system, copy files across a network, or have proxy access or special privileges. You do not need to consider whether a print queue is local or remote. 1-2 Using the DQS Software HOW DQS WORKS This is what happens when you print using the DQS software: __________________________________________________________ Stage__Description________________________________________ 1 You issue a PRINT command and queue the job to a remote system. The remote system does not have to be reachable at the time. 2 The DQS software keeps trying until it establishes a DECnet link to the remote system and transfers the print job to the remote system. 3 After job transfer, you can request status information, modify the print request, or delete the print job. 4 DQS software establishes a DECnet link to the remote system and executes your request. The remote system must be available for DQS software to complete the request. 5 The job prints on the remote printer. DQS software notifies you that the job has printed, if you _______include_the_/NOTIFY_qualifier_on_the_PRINT_command. SOME DQS TERMS Some terms used in this guide in connection with the DQS software are: o Client - the system at which a you reside o Server - the system to which the printer is connected o Client queue - the queue you use locally o Remote queue - the queue on the server that feeds the printer DQS software moves print jobs from client queues (on clients) to corresponding remote queues (on servers). Using the DQS Software 1-3 FOR MORE INFORMATION For more information on the differences between DQS commands and corresponding DCL commands, use this manual or the OpenVMS HELP facility. For more information on how to print files, refer to the descriptions of the PRINT, SHOW QUEUE, DELETE/ENTRY, and SET QUEUE /ENTRY commands in the OpenVMS DCL Dictionary. 1-4 Using the DQS Software ________________________________________________________________ Getting Help With DQS THE HELP COMMAND To get help with the DQS commands, you can use the standard OpenVMS HELP facility. Enter: $ HELP command Where: command Is DQS or the PRINT, QSHOW, QDELETE, or QSET command verb. EXAMPLE For example, if you enter the following command, text displays on your terminal that explains how to use the DQS QSHOW command. $ HELP QSHOW QSHOW Displays information about queues and jobs that are currently in queues. If the queue is a DQS client queue, QSHOW also displays the remote queues associated with the client queue. o Display characteristic names and numbers that are available on queues (see /CHARACTERISTICS). o Display form names and numbers that are available on queues (see /FORM). Format: QSHOW [queue-name] Additional information available: Parameters Command_Qualifiers /ALL /BATCH /BRIEF /DEVICE /FILES /FULL /OUTPUT /CHARACTERISTICS /FORM QSHOW Subtopic? Using the DQS Software 1-5 2 ________________________________________________________________ Printing Files Using DQS Software ABOUT THIS CHAPTER This chapter: o Explains the DQS printing process in basic and multinode networks o Shows examples of messages you receive when you enter a DQS print job o Explains requirements for printing with forms o Lists differences between DQS PRINT qualifiers and DCL PRINT qualifiers o Lists some status and error messages you may see FOR MORE INFORMATION If you need more information on how to use the Digital Command Language (DCL) PRINT command and its qualifiers, refer to the OpenVMS DCL Dictionary. Printing Files Using DQS Software 2-1 ________________________________________________________________ Printing in Network Environments BASIC NETWORK EXAMPLE Assume that your site has a network of two systems, APPLE and BANANA: o Node APPLE has an attached PrintServer 17/600 printer. o The PrintServer 17/600 queue on APPLE is named Q_CHICAGO. o Node BANANA has no attached printer. WITHOUT DQS SOFTWARE Without DQS software, from node APPLE, you can print a file named TRIP_REPORT.TXT on your own system by entering this PRINT command line at the DCL prompt ($): $ PRINT TRIP_REPORT.TXT/QUEUE=Q_CHICAGO Node BANANA users cannot use the printer on node APPLE. WITH DQS SOFTWARE If DQS software is installed on both nodes, node APPLE can function as a server; that is, APPLE's printer can serve users of both systems. Node BANANA is then the DQS client. Assume that your system manager defined a client DQS queue for node BANANA that corresponds to the queue Q_CHICAGO on APPLE. From node BANANA, to queue your file to print on node APPLE, you enter the identical command line: $ PRINT TRIP_REPORT.TXT/QUEUE=Q_CHICAGO NOTE If the generic queue SYS$PRINT is defined as Q_CHICAGO, users can print files by entering PRINT file-name. 2-2 Printing Files Using DQS Software BASIC CONFIGURATION Figure 2-1 illustrates how the system manager configures DQS software in this basic network. MULTINODE NETWORK EXAMPLE DQS software can be installed on networks of any size. Figure 2-2 illustrates a slightly more complex DQS configuration consisting of three nodes: APPLE, BANANA, and CHERRY: o Node APPLE has an attached PrintServer 17/600 printer named Q_CHICAGO. o Node CHERRY has an attached LN06 printer named Q_PARIS. o Node BANANA has no attached printer. DQS can be installed on all three nodes. Nodes APPLE and CHERRY can function as servers; that is, their printers can serve users of other systems. All three nodes can be clients; that is, they can use the printers of the server systems. PRINTING IN MULTINODE NETWORK Your system manager can define client DQS queues for all three systems that send print jobs to the remote queues Q_CHICAGO and Q_PARIS. For example, your system manager can define the following (see Figure 2-2): ________________________________________________________________ To send print Define client On client jobs to remote On server queues:__________node:____________queues:__________nodes:_______ CQ_EUROPE APPLE Q_PARIS CHERRY CQ_FRANCE BANANA Q_PARIS CHERRY CQ_ILLINOIS BANANA Q_CHICAGO APPLE CQ_USA___________CHERRY___________Q_CHICAGO________APPLE________ Then, from node APPLE, for example, you can queue your file to print on the LN06 printer on node CHERRY by entering: Printing Files Using DQS Software 2-3 $ PRINT TRIP_REPORT.TXT/QUEUE=CQ_EUROPE From node BANANA you can queue your file to print on the LN06 printer on node CHERRY by entering: $ PRINT TRIP_REPORT.TXT/QUEUE=CQ_FRANCE In both examples, the print job, TRIP_REPORT.TXT, is sent to the remote queue Q_PARIS on the server node CHERRY for printing. MULTINODE CONFIGURATION Figure 2-2 illustrates how the system manager configures DQS software in this multinode network. ADVANTAGES OF DQS PRINTING With DQS software, you can choose to print files on the printer that is most convenient to your location. You can take advantage of different types of printers as necessary. You can also direct output to printers you know are idle. 2-4 Printing Files Using DQS Software ________________________________________________________________ Understanding Print Job Messages STATUS MESSAGES When you queue a file to be printed, you receive one of two acknowledgment messages: o If the client queue is empty, you see a message that indicates that the file is being transferred to the server node for printing. For example: Job MARCH-INVOICE (queue CLIENT, entry 806) started on CLIENT o If the client queue is not empty, you see a message like this: Job MARCH-INVOICE (queue CLIENT, entry 810) pending pending status caused by queue busy state The messages list the client queue, in this case CLIENT, and the client job number. As with the DCL software, these messages are sent by default. You can suppress default messages by using the /NOIDENTIFY qualifier with the PRINT command. PRINT JOB ENTRY NUMBERS When you queue a file to print, the DQS software displays the job entry number of the client (that is, your) system. Job numbers printed on the header, burst, or trailer pages are client job numbers, if the DQS print symbiont or the DECprint Supervisor for OpenVMS software runs the server's printer. Otherwise, the job numbers are server job numbers. Printing Files Using DQS Software 2-5 ________________________________________________________________ Printing with Forms REQUIREMENTS Before the DQS software transfers a print job, it checks on the form being used. o If the form exists on both the client and the server, the file is printed. o If the form does not exist on the client, the job cannot be queued. o If the form does not exist on the server, the job terminates with an error and remains in the queue until you delete or requeue it. If you queue a job with a form that is not mounted on the client, the queue manager mounts the form before the software transfers the job. This can take several minutes. If you queue a job with a form that is not mounted on the server, the job does not print until the operator mounts the form. 2-6 Printing Files Using DQS Software ________________________________________________________________ Using PRINT Command Qualifiers DQS QUALIFIER DIFFERENCES Most of the qualifiers to the PRINT command function the same with DQS printing as they do with standard OpenVMS printing. Qualifiers that function differently with DQS printing are described in Table 2-1. Table 2-1 PRINT Command Qualifiers That Function Differently __________with_DQS_Printing_____________________________________ Function Qualifier___Without_DQS______Function_With_DQS__________________ Prints job Transfers job to the server after /AFTER=time after specified specified time. time. /DELETE Deletes file Deletes file on the client after after printing. transfer to the server (files are always deleted from the server's disk after printing). (continued on next page) Printing Files Using DQS Software 2-7 Table 2-1 (Cont.) PRINT Command Qualifiers That Function __________________Differently_with_DQS_Printing_________________ Function Qualifier___Without_DQS______Function_With_DQS__________________ /FORM=type Uses form type. Uses form type. o The form name must be defined on both the DQS client and server. o If the form is not mounted on the client, the queue manager software mounts it (this may take several minutes). o If the form is not defined on the server, the job does not transfer, but remains in the queue with error status %JBC-F- NOSUCHFORM. o If the form is defined differently on server and client, the job is printed with the server form. /HEADER Specifies Specifies whether header page whether header prints with file. The header page page prints includes server node and device in with file. the file specification; the version number of the file specification may differ. /HOLD Holds job until Does not transfer job to server released (by until released (by QSET/ENTRY SET/ENTRY /RELEASE command). /RELEASE command). (continued on next page) 2-8 Printing Files Using DQS Software Table 2-1 (Cont.) PRINT Command Qualifiers That Function __________________Differently_with_DQS_Printing_________________ Function Qualifier___Without_DQS______Function_With_DQS__________________ /NOTIFY Broadcasts Broadcasts messages to you after message to job transfers and after job prints. you after job prints. /OPERATOR= Sends string to Sends string to operators on both string operator when client and server when job begins job begins to to print. print. Passes from 1 Passes from 1 to 7 optional /PARAMETERS to 8 optional parameters to job. DQS software =(pa- parameters to reserves parameter 8 for its own rameter job. use. If you specify parameter 8, [,...]) DQS software generates an error, and leaves the job in the client queue with an error status of DQS- F-P8RESERVED. Specifies Specifies priority of print job. /PRIORITY=n priority of Priority limits are configured on print job. the server for all client users. You can request any print priority, but the server queues your job with no more than the specified maximum priority. /SETUP= Extracts Extracts specified modules from mod- specified device control library on the ule[,...] modules from server; the client system's device device control control libraries need not be ____________library._________defined.___________________________ Printing Files Using DQS Software 2-9 EXAMPLES For example, to transfer a file to the printer queue on node CHERRY from the client queue CQ_EUROPE on node APPLE after 11:30 in the morning, use the /AFTER qualifier: $ PRINT CHANGES.PS/QUEUE=CQ_EUROPE/AFTER=11:30 Job CHANGES (queue CQ_EUROPE, entry 324) holding until 30-JUL-1994 11:30 If you want to be notified after your print job is transferred and completes, use the /NOTIFY qualifier. For example: $ PRINT CHANGES.PS/QUEUE=CQ_EUROPE/NOTIFY Job CHANGES (queue CQ_EUROPE, entry 548) started on queue CQ_EUROPE Job CHANGES (queue EUROPE, entry 548) completed Print job CHANGES (queue CQ_EUROPE, entry 548) completed at 30-JUL-1994 10:24 $ Each "completed" message means something different. o The first indicates that the file transfer is complete. o The second indicates that the job printed on the server node. The messages may not appear immediately; the actual timing depends on the system load and backlog in the queues. 2-10 Printing Files Using DQS Software ________________________________________________________________ Understanding PRINT Command Error Messages ERROR MESSAGES If a DQS print job in a client queue fails to transfer to the server, the job remains in the client queue with the message "terminated with error status" and an associated error status. To examine the error status, use the QSHOW command (see Chapter 3). If you specify the /NOTIFY qualifier, you receive an error message when your print job fails to transfer. For example: Job TRIP_REPORT (queue CQ_ILLINOIS, entry 341) terminated with error status %status, message-text You must either delete the job or release it for another try. The QDELETE/ENTRY command (for deleting jobs from a queue) is described in Chapter 4. COMMON DQS ERROR MESSAGES Following are some common DQS error messages with an explanation and a recovery action. o %DQS-F-BADQUEUE-The remote queue on the server system is not accessible to DQS clients. Ask the system manager to modify the remote queue on the server system. (The DQS$QUEUE_remote-queue logical name needs to be defined.) o %JBC-F-NOSUCHFORM-You specified a form that is not defined on the server. Enter the job again, using a different form or specifying a queue where the form is defined. o %DQS-F-P8RESERVED-You used the /PARAMETERS qualifier and specified all eight parameters. Reenter the print request with less than eight parameters. Refer to Appendix A for a complete list of messages. Printing Files Using DQS Software 2-11 3 ________________________________________________________________ Viewing the Status of Print Jobs ABOUT THIS CHAPTER This chapter: o Compares the DQS QSHOW command with the DCL SHOW QUEUE command o Describes how to check the status of a print job using the QSHOW command and how to interpret the associated output o Compares QSHOW qualifiers with DCL SHOW QUEUE qualifiers o Explains QSHOW error messages Viewing the Status of Print Jobs 3-1 ________________________________________________________________ The QSHOW Command COMPARISON_WITH_DCL_COMMAND_____________________________________ This command_._._.____Enables_you_to_._._._____________________ DCL SHOW QUEUE Display the status of queues on your local system. DQS QSHOW Display the status of both local and _________________remote_print_queues._____________________ Using the DCL SHOW QUEUE command to view the status of a DQS client queue works, but it does not show the status of the associated remote queue. For that information, use the QSHOW command. You can use the QSHOW command to examine both client (local) and server (remote) queues. 3-2 Viewing the Status of Print Jobs ________________________________________________________________ Checking the Status of a Print Job QSHOW COMMAND To check the status of a print job, enter the following command at the DCL prompt on the client node: $ QSHOW client-queue-name SAMPLE OUTPUT The following examples use the same node names and queues used in the DQS client/server examples from Chapter 2. For example, you are working on node APPLE, and you queued the file TRIP_REPORT.PS to the client queue CQ_EUROPE to print on the printer on node CHERRY. To check the status of your print job, enter: $ QSHOW CQ_EUROPE The command output may look like this: ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ] Printer queue Q_PARIS, on CHERRY:: Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ (5 intervening jobs containing 2019 blocks) TRIP_REPORT JONES 1229 98 Pending =============================to be transferred=========================== Server queue CQ_EUROPE, on APPLE::, mounted form LN06_DEFAULT (stock=DEFAULT) The information in this example tells you: o The name of the client node is APPLE. The name of the server node is CHERRY. o The queue shown as the "server queue" is the client queue CQ_EUROPE on node APPLE. ("Server" refers to the OpenVMS concept of server queues, not the DQS concept of server nodes.) o The queue shown as "remote queue" is the remote queue Q_PARIS on node CHERRY. Viewing the Status of Print Jobs 3-3 o Five print jobs are currently ahead of yours in the remote queue. They total 2019 blocks of data. You can use this information to estimate how long before your job prints. o Your print job is in the remote queue on node CHERRY awaiting printing (status "Pending"). If your job is printing, the status is "Printing." o The form on the client queue is named LN06_DEFAULT. You are informed if the client queue is stopped or stalled. o You have no jobs awaiting transfer to the server. Like the DCL SHOW QUEUE command, the DQS QSHOW command normally shows only your jobs, unless you are a privileged user and you specify the /ALL qualifier. In any event, you cannot see other users' jobs in the client queue, unless the queue is world readable. If you queue another job and check the status, you may get results like this: $ QSHOW CQ_EUROPE ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ] Printer queue Q_PARIS, on CHERRY:: Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ =============================to be transferred=========================== Server queue CQ_EUROPE, on APPLE::, mounted form LN06_DEFAULT (stock=DEFAULT) TRIP_REPORT JONES 1234 98 Processing This example indicates that your job is in the process of being transferred to the server node CHERRY. If jobs are ahead of yours in the client queue on node APPLE, the status is "Pending." 3-4 Viewing the Status of Print Jobs ________________________________________________________________ Using QSHOW Command Qualifiers DQS QSHOW QUALIFIERS The DQS QSHOW command uses the same qualifiers as the DCL SHOW QUEUE command, plus one more. QSHOW also uses the qualifier /QUEUE=queue-name to support the /FORM and /CHARACTERISTICS qualifiers. /FORM QUALIFIER o To show the forms available on a local system, enter this DCL command line: $ SHOW QUEUE/FORM o To show the forms available on the DQS client and server systems, enter: $ QSHOW /QUEUE=queue-name /FORM Viewing the Status of Print Jobs 3-5 /FORM EXAMPLE In this example, CQ_EUROPE is used as the queue-name: $ QSHOW /QUEUE=CQ_EUROPE /FORM You see output like the following: Remote node CHERRY:: Form name Number Description --------- ------ ----------- A4_12 (stock=PLAIN_PAPER) 1129 A4 12-Pitch with margins DCPS$DEFAULT (stock=DEFAULT) 1115 DCPS default Local node APPLE:: Form name Number Description --------- ------ ----------- A4_12 (stock=PLAIN_PAPER) 1129 A4 12-Pitch with margins DCPS$DEFAULT (stock=DEFAULT) 1115 DCPS default DEFAULT 0 System-defined default KPS$DEFAULT (stock=DEFAULT) 1183 KPS default LANDSCAPE (stock=DEFAULT) 10 132 by 66 (landscape) LASERWRITER (stock=DEFAULT) 30 APPLE LASERWRITER LCG01$FORM (stock=DEFAULT) 455 LCG01 LN01S (stock=DEFAULT) 60 64000 by 66 (LN0S ) LPS$$FORM 1105 PostScript Default LTR_10 (stock=PLAIN_PAPER) 1124 10-Pitch, no margins LTR_12 (stock=PLAIN_PAPER) 1127 12-Pitch with margins PORTRAIT (stock=DEFAULT) 20 80 by 60 (portrait) PSBLASER (stock=DEFAULT) 47 postscript laser PS_PLAIN (stock=PLAIN_PAPER) 1132 PostScript (Macintosh) WPSPLUS (stock=DEFAULT) 1101 WPS-PLUS/VMS $ The QSHOW command lists the forms mounted on both the client and the server nodes, referred to as "local" and "remote" nodes, respectively, in the command output. 3-6 Viewing the Status of Print Jobs ________________________________________________________________ Understanding QSHOW Error Messages QSHOW ERROR MESSAGES The DQS QSHOW command uses the same error messages as the DCL SHOW QUEUE command. In addition, the QSHOW command has its own messages for handling problems unique to the DQS software. SERVER UNREACHABLE For example, if the server node is not currently reachable, the DQS software cannot check the status of the remote queue. You receive an explanation of the problem, like the following: $ QSHOW CQ_EUROPE ***** Remote queue CHERRY::Q_PARIS not accessible ***** %SYSTEM-F-UNREACHABLE, remote node is not currently reachable ==============================to be transferred================== Server queue CQ_EUROPE, stalled, mounted form DEFAULT Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ TRIP_REPORT JONES 1366 98 Processing Q2-FINANCIALS JONES 1367 1 Pending INVALID REMOTE QUEUE Another possible error is that the remote queue is defined incorrectly. DQS software displays the following messages: $ QSHOW CQ_EUROPE %DQS-W-MSG_REMOTE, Remote system error: -DQS-F-BADQUE, Specified queue not valid for DQS access. ==============================to be transferred================== Server queue CQ_EUROPE, stopped, mounted form DEFAULT Remote system error: Specified queue not valid for DQS access. Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ Q2-FINANCIALS JONES 1467 1 Pending Viewing the Status of Print Jobs 3-7 In this case, either the system manager on the server node must redefine the remote queue or the system manager on the client node must redirect the client queue to a valid remote queue. FOR MORE INFORMATION Refer to Appendix A for a complete list of messages. 3-8 Viewing the Status of Print Jobs 4 ________________________________________________________________ Deleting Print Jobs From a Queue ABOUT THIS CHAPTER This chapter: o Compares the DQS QDELETE/ENTRY command with the DCL DELETE/ENTRY command o Describes how to delete a print job using the QDELETE /ENTRY command o Lists some QDELETE/ENTRY error messages Deleting Print Jobs From a Queue 4-1 ________________________________________________________________ The QDELETE/ENTRY Command COMPARISON_WITH_DCL_COMMAND_____________________________________ This_command_._._.____Enables_you_to_._._.________________ DCL DELETE/ENTRY Delete a job from a local queue. DQS QDELETE/ENTRY Delete either locally or remotely ______________________queued_print_jobs.__________________ The QDELETE/ENTRY command functions exactly like the DELETE/ENTRY command. (These commands do not delete files; they only remove jobs from a print queue.) You can use the DQS QDELETE/ENTRY command instead of the DCL DELETE/ENTRY command for all your print jobs. 4-2 Deleting Print Jobs From a Queue ________________________________________________________________ Deleting a Print Job YOU NEED TO KNOW To delete a print job, you must know: o The name of the queue from which you want to delete the job o The job's entry number in the queue The PRINT command displays this information by default when you queue a file for printing. You can also obtain this information by using the QSHOW command (see Chapter 3). EXAMPLE For example, if you queued the file TRIP_REPORT.PS to client queue CQ_EUROPE to print on node CHERRY, and the job is entry 1024, delete the print job by entering: $ QDELETE/ENTRY=1024 CQ_EUROPE The DQS software removes the job from the client queue. If the job has already transferred to the remote queue, the DQS software removes the job from the remote queue. /NOTIFY QUALIFIER If you specify the /NOTIFY qualifier when you queue the job for printing, the DQS software notifies you when the job is deleted. $ QDELETE/ENTRY=341 CQ_EUROPE /NOTIFY Print job TRIP_REPORT (queue CQ_EUROPE, entry 341) deleted Deleting Print Jobs From a Queue 4-3 ________________________________________________________________ Understanding QDELETE Error Messages QDELETE ERROR MESSAGES The DQS QDELETE command uses the same error messages as the DCL DELETE command. In addition, the QDELETE command has its own messages for handling problems unique to the DQS software. SERVER UNREACHABLE If the server node is not currently reachable, the QDELETE /ENTRY command fails and you receive an explanation, like the following: $ QDELETE/ENTRY=1067 CQ_EUROPE %DQS-I-NOJOBDELETED, No jobs deleted %DQS-I-INACCESSIBLE, Remote queue CHERRY::Q_PARIS is inaccessible INVALID REMOTE QUEUE If you use the QDELETE/ENTRY command to delete a job from a queue on a remote system that is not defined as a valid DQS remote queue, DQS software displays messages like the following: $ QDELETE/ENTRY=1194 CQ_CANADA %DQS-W-MSG_REMOTE, Remote system error: -DQS-F-BADQUE, Specified queue not valid for DQS access. In this case, either the system manager on the server node must redefine the remote queue or the system manager on the client node must redirect the client queue to a valid remote queue. FOR MORE INFORMATION Refer to Appendix A for a complete list of messages. 4-4 Deleting Print Jobs From a Queue 5 ________________________________________________________________ Modifying the Characteristics of a Job ABOUT THIS CHAPTER This chapter: o Compares the DQS QSET/ENTRY command with the DCL SET /ENTRY command o Describes how to modify a print job using the QSET /ENTRY command o Describes the DQS command qualifiers with modified behavior o Lists some QSET error messages Modifying the Characteristics of a Job 5-1 ________________________________________________________________ The QSET/ENTRY Command COMPARISON_WITH_DCL_COMMAND_____________________________________ This command_._._.____Enables_you_to_._._._____________________ DCL SET/ENTRY Change the current status or attributes of a job that is not currently executing in a queue. DQS QSET/ENTRY Changes the current status for either locally or remotely queued print jobs not _________________executing_in_a_queue.____________________ You can use the DQS QSET/ENTRY command for modifying all your print jobs. You must specify a queue name with the QSET/ENTRY command. 5-2 Modifying the Characteristics of a Job ________________________________________________________________ Modifying a Print Job YOU NEED TO KNOW Before you can modify a print job, you need to know: o The name of the queue that contains the job you want to modify o The job's entry number in that queue The DQS PRINT command displays this information by default when you queue a file for printing. You can also obtain this information by using the QSHOW command (described in Chapter 3). QSET/ENTRY EXAMPLE For example, you queued the file CHANGES.PS to client queue CQ_EUROPE to print on node CHERRY and requested two copies, as follows: $ PRINT CHANGES.PS/QUEUE=CQ_EUROPE/COPIES=2 Job CHANGES (queue CQ_EUROPE, entry 1324), pending Now you change your mind and want three copies. You can modify the job by entering: $ QSET/ENTRY=1324 CQ_EUROPE/COPIES=3 The DQS software modifies the job in the client queue. If the job already transferred to the remote queue, the DQS software modifies the job in the remote queue. However, DQS software cannot modify a job that is moving from a client queue to a remote queue or a job that is actually printing. Modifying the Characteristics of a Job 5-3 ________________________________________________________________ Using QSET Command Qualifiers QSET QUALIFIER DIFFERENCES Most of the qualifiers to the QSET/ENTRY command act the same as they do with the standard DCL SET/ENTRY command. Those qualifiers that have modified functions when used with the QSET/ENTRY command are described in Table 5-1. Table 5-1 QSET/ENTRY Command Qualifiers That Function __________Differently_with_DQS_Printing_________________________ Function Without Qualifier_____DQS_________________Function_With_DQS_____________ /AFTER=time Prints job after Transfers job to the server specified time. after specified time. If already transferred, prints job after specified time. /FORM=type Uses form type. Uses form type; form name or number must be defined on both client and server. /HEADER Specifies whether Specifies whether header header page is page is printed with file. printed with file. Page displays server node and device in the file specification; file version number may differ. /HOLD Holds job until Does not transfer job to released (by SET server until released. If /ENTRY/RELEASE already transferred, does not command). print until released (by QSET /ENTRY/RELEASE command). (continued on next page) 5-4 Modifying the Characteristics of a Job Table 5-1 (Cont.) QSET/ENTRY Command Qualifiers That Function __________________Differently_with_DQS_Printing_________________ Function Without Qualifier_____DQS_________________Function_With_DQS_____________ /NODELETE Cancels file While job is still in client deletion for queue, this qualifier works job queued with correctly; after the job is /DELETE qualifier. transferred to the remote queue, command fails and returns an error. /PARAMETERS Passes from 1 Passes from 1 to 7 parameters =(parame- to 8 optional to job. The DQS software ter[,...]) parameters to job. reserves parameter 8 for its own use. If you specify parameter 8, the command fails and returns an error. /PRIORITY=n Specifies priority Specifies priority of print of print job. job. Priority limits are configured on server nodes for all client users. You can request any print priority, but the server queues your job with no more than the allowed maximum priority. /REQUEUE= Queues job to If the job has not yet queue- another printer transferred to the server name[:] queue. node, you can requeue it to any other queue. If the job already transferred (but has not printed), you can requeue it to another queue on the __________________________________same_server.__________________ Modifying the Characteristics of a Job 5-5 ________________________________________________________________ Understanding QSET Error Messages QSET ERROR MESSAGES If the QSET/ENTRY command fails, the job's specifications are unchanged and the DQS software returns an error message. Some common messages are: o If the server node is not currently reachable, the QSET/ENTRY command fails and returns the following messages: %DQS-I-NOJOBSET, no jobs set %DQS-I-INACCESSIBLE, remote queue queue is inaccessible o If you specify a queue that points to an invalid remote queue, the command fails and returns the following messages: %DQS-W-MSG_REMOTE, remote system error: -DQS-F-BADQUEUE, specified queue not valid for DQS access The server node system manager must modify the remote queue. o If you try to modify a job while it is being transferred from the client queue to the remote queue, the request fails with an error status: %JBC-E-EXECUTING o If you specify a form that is not defined on the client, the command fails and returns the error status: %JBC-E-NOSUCHFORM 5-6 Modifying the Characteristics of a Job o If you attempt to modify the status of a print job with the QSET /ENTRY/NODELETE command after the job has transferred to the remote queue, the command fails and returns the following messages: %DQS-W-MSG_REMOTE, remote system error: -DQS-E-NODELETE, /NODELETE is allowed only on local jobs %DQS-I-NOJOBSET, no jobs set o If you use the /PARAMETERS qualifier and specify eight parameters for a job that already transferred, the command fails and returns the following messages: %DQS-W-MSG-REMOTE, remote system error: -DQS-F-P8RESERVED, parameter 8 is reserved for DQS on remote systems %DQS-I-NOJOBSET, no jobs set FOR MORE INFORMATION Refer to Appendix A for a complete list of messages. Modifying the Characteristics of a Job 5-7 6 ________________________________________________________________ Spooling Files to a Client Queue SPOOLING FILES The OpenVMS operating system allows you to assign a logical device in a source program to a physical device. To spool files to a client queue: 1. The system manager creates a LAT port and sets the LAT port spooled to the DQS client queue. 2. You specify the LAT port in a source program as the physical device. DQS software places the print output in a temporary file, enters the file in the client queue, then transfers the file to the corresponding remote queue. EXAMPLE In a FORTRAN program, the statement PRINT directs output to the terminal unless otherwise directed to a logical device. If the LAT port is spooled to a client queue, you can direct program output to a remote printer. For example, if the LAT port LTA999: is spooled to client queue CQ_USA (that is, the system manager used the command line SET DEVICE LTA999/SPOOLED=CQ_USA), you can spool output to the remote printer by entering: $ DEFINE FOR$PRINT LTA999: When you execute your FORTRAN program, its output is spooled from LTA999 to the client queue CQ_USA. Spooling Files to a Client Queue 6-1 COLON REQUIRED The colon following LTA999: is mandatory. If omitted, the file, LTA999.LIS is created in the current directory. 6-2 Spooling Files to a Client Queue Part II ________________________________________________________________ System Manager's Guide This part describes how to configure and manage the DQS software on OpenVMS AXP and OpenVMS VAX systems. The System Manager's Guide is intended for the network or system manager. 7 ________________________________________________________________ Understanding the DEC Distributed Queuing Service ABOUT THIS CHAPTER This chapter describes: o An overview of the design of the DEC Distributed Queuing Service for OpenVMS Systems (DQS) product o The primary functions of the DQS software o The functions of the DQS commands: PRINT, QSHOW, QSET /ENTRY, and QDELETE/ENTRY o The functions of DQS software components o The DQS notification service and how it works o The DQS symbionts o The use of forms with the DQS software o The DQS server account o Some configuration issues o Types of errors that may occur o How the DQS software handles security issues o The processes created by the software o How the DQS software supports devices o The use of a batch job with DQS software Understanding the DEC Distributed Queuing Service 7-1 ________________________________________________________________ Overview of the DQS Software WHAT IS DQS SOFTWARE? The standard OpenVMS queue system enables you to use the OpenVMS PRINT command to print files on output devices that are connected to your local OpenVMS node. The DQS software is an OpenVMS layered product that extends the standard OpenVMS queue system to a distributed system environment. The DQS software enables you to use the OpenVMS PRINT command to print files on output devices that are connected to remote OpenVMS nodes in your network. You can also delete, and obtain or change the status of your DQS print jobs. WHY USE DQS SOFTWARE? Installing and configuring the DQS software in your network can provide: o Printing services to workstation users (and others) who do not have attached printers o The sharing of expensive or unique printing devices among the users in your distributed system o The ability for your users to distribute reports efficiently to remote sites within your company or organization, because DQS software works in both wide area and local area networks UNDERSTANDING DQS CLIENTS AND SERVERS The DQS software is based on a client/server design, which consists of two cooperating software components (client and server). The following terms are associated with DQS servers: Server Nodes in your network that have connections to nodes output devices (for example, printers) that you want to make available to the users on other nodes (client nodes) in your network. 7-2 Understanding the DEC Distributed Queuing Service Remote DQS queue on the server node that directs queue print jobs from client nodes to the connected printer. (Standard OpenVMS print queues are queues that direct print jobs to printers connected to the local node.) Server DQS software that you must install and software configure on server nodes. The following terms are associated with DQS clients: Client Nodes whose users are able to print files on nodes printing devices that are connected to remote DQS server nodes. Client DQS queue on the client node that directs queue print jobs to the associated remote queue on the DQS server node. Client DQS software that you must install and software configure on client nodes. A node can be only a client, or both a client and a server. Each client can be configured to send print jobs to any server. Similarly, each server can be configured to accept print jobs from any client. Chapters 8 and 9 describe the procedures for configuring servers and clients, respectively. USING DQS SOFTWARE IN A CLUSTER In a VMScluster environment, a server is potentially every node in a cluster. Similarly, a client is potentially every node in a cluster. Therefore, if a user logs on to different cluster members at different times, the DQS software is always available. To use the DQS software in a cluster environment: 1. Install the DQS software. 2. License each node in the cluster to be a DQS node. 3. Invoke DQS$STARTUP.COM from each cluster member node. While DQS software can be used on selected nodes of a cluster, doing so does not take advantage of the flexibility of a cluster. Understanding the DEC Distributed Queuing Service 7-3 NETWORK REQUIREMENTS FOR DQS SOFTWARE DQS software uses the DECnet network to communicate between clients and servers and to perform its functions. The DQS software requires: o The client and server to communicate for the print request to be processed by the server. However, users can queue print jobs at any time, even if the client system is not in communication with the desired server system. Similarly, a server can continue to process print jobs, even if the client from which the job was received is not in communication with the server. o A connection between a client and a server remains long enough to transfer the complete file (or files) to be printed. If the connection is broken before the entire print job is transferred to the server, the DQS software attempts to transfer the entire print job after the connection is reestablished. o Communication must exists between the client and the desired server to examine a remote queue or to delete or modify a job in a remote queue. o A connection must be established from the server to the user's client system for a user to receive job notification messages (described in the section titled The DQS Notification Service). PHASE IV AND PHASE V NETWORKS The DQS software can be used in both DECnet Phase IV and DECnet/OSI Phase V networks. DQS software also operates in properly configured networks that use both networking products. DECnet/OSI systems can be set up to use synonyms to communicate with Phase IV systems. DECnet Phase IV networks limit node names to six characters. DECnet/OSI Phase V networks allow the use of an expanded node name (full names). DQS clients and servers can handle node names with up to 150 characters with no embedded blank spaces. 7-4 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Primary Functions of the DQS Software OVERVIEW The major functions of the DQS software are initiated by the PRINT, QSHOW, QSET/ENTRY, and QDELETE/ENTRY commands. DQS software uses: o The standard OpenVMS PRINT command to initiate DQS print requests o Modified versions of the OpenVMS SHOW, SET, and DELETE commands to show, modify, and delete DQS print requests PRIMARY FUNCTIONS Figure 7-1 shows the primary functions of the DQS software. THE PROCESS The stages shown in Figure 7-1 are summarized as follows: __________________________________________________________ StageDescription__________________________________________ 1 A user enters a PRINT command on a client node specifying a DQS client queue. 2 DQS software copies the file to be printed from the client queue to the server node, and enters the print job in the remote queue on the server. 3 The remote queue sends the file to the server's _____output_device_and_the_file_is_printed._______________ SUMMARY OF DQS COMMANDS Most of the standard OpenVMS command qualifiers are fully supported for the DQS versions of the PRINT, SHOW, SET, and DELETE commands. Table 7-1 summarizes the DQS commands. Understanding the DEC Distributed Queuing Service 7-5 Table_7-1_Summary_of_DQS_Commands_________________________ Command_______Function____________________________________ PRINT The OpenVMS PRINT command places a print job in a client queue on a client system. The DQS symbiont transfers the print request to the associated server system, where it is placed in the associated remote queue and directed to an output device for printing. QSHOW Displays the status of a DQS print job that is in either a client or a remote queue. QDELETE Prevents a print job from being processed or /ENTRY terminates its processing. QSET/ENTRY Modifies the parameters of a print job after the job has been queued but before it has ______________been_processed._____________________________ FOR MORE INFORMATION Refer to Part I for more information on the DQS commands and their qualifiers. 7-6 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Functions of the DQS Commands PRINT COMMAND FUNCTIONS Figure 7-2 shows the functions of the PRINT command using a DQS queue. THE PROCESS The stages in the PRINT process are summarized as follows: __________________________________________________________ StageDescription__________________________________________ 1 A user issues a PRINT command specifying the DQS client queue CQ_USA. 2 The standard OpenVMS DCL command language intepreter interprets the PRINT command. 3 The OpenVMS job controller in the client queue on the client node queues the print job to the DQS client queue. 4 The client symbiont, DQS$SMB, takes the print job from the client queue and transfers the job to the DQS$SERVER process on the server node. 5 The DQS$SERVER process receives the print job from the client symbiont, writes the file to a disk on the server node, and places the print job in the remote queue Q_CHICAGO. 6 The print symbiont on the server retrieves the file when the file is ready to be printed and directs the _____file_to_the_output_device_for_printing.______________ After the printer prints the file, the DQS$NOTIFIER process on a server deletes the file from the DQS server account (see the section titled The DQS Server Account). If a user requests notification of job completion, the DQS$NOTIFIER attempts to notify the user before it deletes the files associated with the print job. Understanding the DEC Distributed Queuing Service 7-7 OTHER DQS COMMANDS Figure 7-3 shows the functions of the QSHOW, QSET/ENTRY, and QDELETE/ENTRY commands. THE PROCESS The stages in the DQS QSHOW, QSET/ENTRY, and QDELETE/ENTRY command processes are summarized as follows. __________________________________________________________ StageDescription__________________________________________ 1 The DQS command interpreter DQS$CLIENT interprets the command and transfers the request to the DQS$SERVER process on the server node. 2 The DQS$SERVER process receives the command request from the client node and passes the request to the OpenVMS job controller. 3 The OpenVMS job controller performs the command request and returns the appropriate information to the DQS$SERVER process. 4 DQS$SERVER then transfers this information to the DQS$CLIENT process on the client node. 5 DQS$CLIENT formats the information and directs the _____command_output_to_the_user_who_initiated_the_command. COMMANDS WITH OPENVMS QUEUES The DQS QSHOW, QSET/ENTRY, and QDELETE/ENTRY commands also work on standard OpenVMS print queues. For an entry in a standard OpenVMS queue, QSHOW, QSET/ENTRY, and QDELETE /ENTRY do not send information to a server. 7-8 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Functions of DQS Software Components SUMMARY OF COMPONENTS Table 7-2 summarizes the major software components of the DQS software and describes their functions. Table_7-2_Functions_of_the_DQS_Software_Components______________ Component___Name__________Description___________________________ DQS DQS$CLIENT The DQS command interpreter is located command on clients and interprets the DQS inter- QSHOW, QSET/ENTRY, and QDELETE/ENTRY preter commands. The standard OpenVMS command language interpreter interprets the PRINT command. The standard OpenVMS batch /print system enters the print job into a client queue. DQS DQS$SMB The DQS symbiont runs on clients. symbiont Each client queue is serviced by an OpenVMS process that runs the DQS$SMB image. The DQS symbiont process takes print jobs from a client queue and transfers the jobs to a process on the associated server. (continued on next page) Understanding the DEC Distributed Queuing Service 7-9 Table_7-2_(Cont.)_Functions_of_the_DQS_Software_Components______ Component___Name__________Description___________________________ DQS DQS$SERVER The DQS server program is located server on servers and receives print jobs program from the DQS symbiont DQS$SMB on clients. The server program writes the file(s) to be printed to the server disk and places the print request in the associated remote queue. DQS$SERVER also processes QSHOW, QSET /ENTRY, and QDELETE/ENTRY command requests received from clients. The DQS server process is also located on clients to receive job completion messages from the DQS$NOTIFIER process on servers. DQS$SERVER on a client broadcasts job completion messages sent by the DQS$NOTIFIER to each user who owns a particular print job that has completed. (continued on next page) 7-10 Understanding the DEC Distributed Queuing Service Table_7-2_(Cont.)_Functions_of_the_DQS_Software_Components______ Component___Name__________Description___________________________ NotificationDQS$NOTIFIER The DQS notification program is program located on servers and periodically scans DQS print jobs in the remote queues to determine which print jobs have completed. After a print job completes, DQS$NOTIFIER informs the DQS$SERVER process on the client from which the print job originated if /NOTIFY is specified. Modified DQS$PRTSMB The DQS print symbiont, DQS$PRTSMB, is OpenVMS located on servers and is a modified print version of the standard OpenVMS print symbiont symbiont, PRTSMB. The modified DQS symbiont should replace the standard OpenVMS print symbiont so that client- specific information is printed on the flag, burst, and trailer pages of the print output. See The DQS Symbionts for more information on __________________________the_DQS_symbiont._____________________ Understanding the DEC Distributed Queuing Service 7-11 ________________________________________________________________ The DQS Notification Service SENDING MESSAGES TO USERS If you specify /NOTIFY qualifier with the PRINT command, the notification service sends job completion messages when print jobs have completed. DQS software returns two notification messages: o The first when the user's print job has transferred to the server. o The second after the job has printed on the server. DELETING JOBS FROM REMOTE QUEUE The notification process on the server node, DQS$NOTIFIER, also has the task of deleting completed print jobs from the remote queue. The DQS$SERVER program submits all DQS print jobs with the /RETAIN=ALWAYS qualifier. DQS print jobs remain in DQS queues after the job is printed until the DQS$NOTIFIER deletes them. If a user requests notification of job completion, DQS$NOTIFIER attempts to notify the user before it deletes the files associated with the user's print job. HOW IT WORKS Figure 7-4 shows how the DQS notification service works. THE NOTIFICATION PROCESS The DQS notification process shown in Figure 7-4 works like this: __________________________________________________________ StageDescription__________________________________________ 1 The DQS notification process on the server, DQS$NOTIFIER, periodically scans DQS jobs in the remote queues to determine which print jobs have completed. 7-12 Understanding the DEC Distributed Queuing Service __________________________________________________________ StageDescription__________________________________________ 2 When a print job completes, the DQS$NOTIFIER checks if the user specified /NOTIFY and sends a completion message to the DQS$SERVER process on the client node. 3 The DQS$SERVER on the client receives the job completion message and a message is sent to the user _____who_owns_the_job_that_has_completed._________________ FOR MORE INFORMATION For more information on using the /NOTIFY qualifier with the PRINT command, refer to Chapter 2 and the OpenVMS DCL Dictionary. Understanding the DEC Distributed Queuing Service 7-13 ________________________________________________________________ The DQS Symbionts OVERVIEW The DQS software contains two symbionts DQS$SMB and DQS$PRTSMB, which are described in this section. DQS$SMB DQS$SMB runs on client systems. The symbiont takes DQS print jobs from client queues and transfers them to the associated server node. DQS$PRTSMB DQS software provides its own print symbiont, DQS$PRTSMB, which is a modified version of the standard OpenVMS print symbiont, PRTSMB. (The DQS$PRTSMB symbiont is upwardly compatible with the OpenVMS PRTSMB symbiont.) DQS$PRTSMB causes the client job number, the client node name, and the time a print job was queued on the client to be printed on the flag, burst, and trailer pages of DQS print output. With the DQS print symbiont controlling each remote queue on a server, the users of that server see the same job information on their print output that they saw displayed when they entered the print request on the client node. If the standard OpenVMS print symbiont does not handle banner pages to your satififaction, replace it with the DQS print symbiont, DQS$PRTSMB. If DQS$PRTSMB does not control a remote queue on a server, the standard OpenVMS print symbiont prints the job number of the print job in the remote queue, as well as the time that the print job was queued on the server on the DQS print output. DQS$PRTSMB can only replace the OpenVMS print symbiont. 7-14 Understanding the DEC Distributed Queuing Service FOR MORE INFORMATION For a description of the procedures for enabling the DQS print symbiont to control remote queues, see Chapter 8. Refer to Appendix D for information on how DQS$PRTSMB relates to other symbionts. Understanding the DEC Distributed Queuing Service 7-15 ________________________________________________________________ Defining Forms on Client and Server Nodes OVERVIEW You must define all forms that you intend to specify on both the client and its associated servers. To synchronize form definitions on your clients and servers, you can run the DQS$CLIENT program on the client system (see Chapter 9). NO FORM ON SERVER If you attempt to print using a form that is not defined on the associated server, the client queue accepts the job and the system prompt returns ($). However, your print job remains in the client queue with the error status %DQS-F-NOSUCHFORM. A QSHOW command specifying the client queue where you queued the job shows the retained job and the error message. DIFFERENT VALUES Because DQS software transfers only a form's name from a client to its server, a form may have different values on different DQS systems. When the same form is defined differently throughout your network, the server's form definition is used to print a job. Digital strongly recommends that you give forms with the same name the same definitions throughout your network. However, you may want to have different form definitions because it enables users on client systems to maintain their local form definitions to use when printing locally. FOR MORE INFORMATION Chapter 9 describes the procedures for synchronizing form definitions. 7-16 Understanding the DEC Distributed Queuing Service ________________________________________________________________ The DQS Server Account OVERVIEW The DQS installation procedure creates a DQS account, DQS$SERVER, and its associated directory [DQS$SERVER] on all DQS client and server nodes. ON A SERVER A DQS server process is run from the DQS$SERVER account when a connection request is received from a client node. The directory associated with this account [DQS$SERVER] stores files received from client nodes until the files are printed on the server node's output device. After a print job completes, the files associated with the job are deleted from the server account directory. ON A CLIENT The DQS$SERVER account is located on clients to receive job completion messages from the DQS$NOTIFIER process on the server. DQS$SERVER on a client broadcasts job completion messages to each user who owns a completed print job, if the user specified /NOTIFY on the PRINT command. Understanding the DEC Distributed Queuing Service 7-17 ________________________________________________________________ The Significance of Parameter 8 in DQS Printing OVERVIEW The OpenVMS PRINT command allows you to pass from one to eight optional parameters with a print job. DQS software uses parameter 8 to store print job information. Place your print parameter values in parameter 1 to parameter 7. USE IN DQS PRINTING DQS software uses the information in parameter 8 to: o Validate a user's request o Delete a print job o Modify a print job The information stored in parameter 8 includes: o Client job number o Job owner; on OpenVMS systems this usually consists of: - Client node name - User's name on the client o Time the job was queued on the client ERROR MESSAGES DQS software issues an error (%DQS-E-P8RESERVED) if you attempt to specify parameter 8 with either a PRINT or a QSET/ENTRY command. FOR MORE INFORMATION For more information about: o The %DQS-E-P8RESERVED error message, see Appendix B o The format of the information stored in parameter 8, see Appendix D o The use of the /PARAMETERS qualifier, see Chapter 2 7-18 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Configuring DQS Software CLIENT AND SERVER INSTALLATION When you run the DQS installation procedure, you are asked whether you want to install DQS server software. You are given this option because not all DQS nodes in your network require server software (for example, those nodes without connections to output devices). However, most or all nodes in your network require client software so that their users can have access to remote printing resources. Therefore, client software is always installed when you install DQS software. CLIENT AND SERVER CONFIGURATION A client must be configured to work with its corresponding servers (and vice versa) in order for DQS software to function. You can configure a server to serve as many clients as you want. Similarly, you can configure a client to use the services of any number of servers. There are no restrictions on the number of DQS servers or clients that you can have in your network. RESTRICTIONS TO DQS CONFIGURATIONS The DQS software is suitable for all OpenVMS nodes in DECnet networks. DQS software can be used in small networks consisting of two nodes and in large networks consisting of many nodes. DQS software operates in either local area networks or wide area networks. DQS software is limited only by the ability of DQS servers to accept and maintain a large number of simultaneous network connections (that is, logical links) to DQS clients. The maximum number of logical links that a server can support is a parameter that you can define using the Network Control Program (NCP) on DECnet Phase IV systems and the Network Control Language (NCL) on DECnet/OSI Phase V systems. The value of this parameter depends upon many factors, such as the server's processor speed and its typical work load. Understanding the DEC Distributed Queuing Service 7-19 Each logical link from a client creates one process on a server. A server must be configured to allow for enough processes. (See the section entitled Processes Created by DQS Software, which describes the processes created by the DQS software on both clients and servers.) In addition to handling its other network applications, a server should be able to accept simultaneous connections from all clients that it serves. However, all clients trying to access the server at the same time is unlikely. Any client that attempts to print on the server after the maximum number of logical links is reached, automatically attempts to reconnect to the server after a short wait. The QSHOW, QSET/ENTRY, and QDELETE/ENTRY command functions do not attempt this automatic reconnection. 7-20 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Using Daisy-Chained Queues PURPOSE You can configure the DQS software in your network so that a client queue corresponds to a remote queue, which in turn, corresponds to another remote queue on another server. This configuration is called daisy-chained queues. You can daisy-chain queues across as many servers as you want. BENEFITS Daisy-chained queues are useful when a printer on a server becomes temporarily unavailable. Users who want to send jobs to the disabled server can still do so if the server's system manager sets up the remote queue to redirect their print output to another server's output device. No change is made to the user's client system, and the users may not even know that the printer was unavailable. Daisy-chained queues are also useful when a network link from a client to its server is only occasionally available. With daisy-chained queues you can effect a "store and forward" function, where a job is transferred to a reachable, intermediate server that stores the job until the desired server is reachable. EXAMPLE Figure 7-5 depicts a daisy-chained queue configuration. PROCESS The daisy-chain process shown in Figure 7-5 works as follows: __________________________________________________________ StageDescription__________________________________________ 1 A user enters a print job in the client queue CQ_ILLINOIS on client node A. Understanding the DEC Distributed Queuing Service 7-21 __________________________________________________________ StageDescription__________________________________________ 2 DQS software transfers the job to node B and enters it in the remote queue Q_CHICAGO. 3 DQS software then transfers the job from node B to node C, and enters it in the remote queue Q_PARIS on node C. _4___The_job_is_printed_on_node_C's_printer.______________ 7-22 Understanding the DEC Distributed Queuing Service AVOIDING LOOPS Avoid creating a loop when configuring daisy-chained queues. If you configure a daisy-chained queue to direct a job back to the system where the job was originally queued, the job terminates on that system with the error, %DQS-E-LOOP. FOR MORE INFORMATION Refer to Part III for more information on the installation of DQS software. Chapters 8 and 9, respectively, describe the procedures for configuring servers and clients after installation of the software. Chapter 8 describes the procedures for setting up daisy- chained queues. Understanding the DEC Distributed Queuing Service 7-23 ________________________________________________________________ DQS Error Conditions ERROR DETECTION When DQS software detects an error condition, the error is sent to the OpenVMS operator communication process (OPCOM). If an error is detected in a server process, it is also written to a NETSERVER.LOG log file on the server. TYPES OF ERRORS There are three basic types of errors that can occur in DQS printing. o A print job fails because a network link to the server is not available or because there is insufficient disk space on the server. The DQS symbiont handles this type of error by automatically trying to reconnect to the server node after a five-minute wait (this value is not changeable). o A print job cannot transfer to a server. The DQS symbiont handles this type of error by keeping the print job in the client queue with the error status "Retained on error." A QSHOW command specifying the client queue in question displays the specific reason for the error. In this case, you must requeue, release, or delete the print job. This type of error is depicted in Example 7-1. o A client queue is stopped by the DQS symbiont. This type of error occurs when a user attempts to print to an invalid remote queue or to a server node whose name is unknown to the client node. A QSHOW command specifying the client queue in question displays the specific reason for the error. This type of error is depicted in Example 7-2. 7-24 Understanding the DEC Distributed Queuing Service EXAMPLES Example 7-1 shows an error detected by the client symbiont, DQS$SMB. The error does not affect the operation of the symbiont but causes the job responsible for the error to terminate with error status. The affected job remains in the client queue with the error status "Retained on error." In this case, you must either requeue or delete the print job. In Example 7-1, the client node has a form defined that is not defined on the server. This prevents the print job from transferring. A QSHOW command specifying the client queue where the job was queued shows the retained job and the specific reason for the error. Example 7-1 A DQS Error That Prevents a Print Job From Transferring $ QSHOW QUEUE1 ** Remote queue - [ QUEUE1 => SYS$PRINT, on NODEB:: ] Terminal queue SYS$PRINT, on NODEB:: ==============================to be transferred============================== Server queue QUEUE1, on NODEA::, mounted form DEFAULT Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ JOB PAUL 925 1 Retained on error %JBC-E-NOSUCHFORM, no such form Understanding the DEC Distributed Queuing Service 7-25 Example 7-2 shows an error detected by the client symbiont, DQS$SMB, that caused the client queue to stop. The DQS$STATUS_queue-name logical name is defined to be the error status. This action makes it easy to see the reason for the error by issuing a QSHOW command for the client queue. In Example 7-2, the server node name is not known on the client. Therefore, the symbiont cannot process any jobs for that queue and stops the queue. NOTE Remember to deassign the DQS$STATUS_queue-name logical name when you restart the queue. $ DEASSIGN/SYSTEM/USER DQS$STATUS_queue-name 7-26 Understanding the DEC Distributed Queuing Service Example 7-2 A DQS Error That Stops a Client Queue $ QSHOW QUEUE1 ***** Remote queue NODEB::QUEUE1 not accessible ***** %SYSTEM-F-NOSUCHNODE, remote node is unknown ==============================to be transferred============================== Server queue QUEUE1, stopped, on NODEA::, mounted form DEFAULT remote system error: remote node is unknown Jobname Username Entry Blocks Status ------- -------- ----- ------ ------ LOGIN YOUNG 571 2 Pending FOR MORE INFORMATION Refer to Chapter 10 for guidelines on how to troubleshoot error conditions that involve DQS software. Understanding the DEC Distributed Queuing Service 7-27 ________________________________________________________________ DQS Security Issues and Access Rights RESTRICTING ACCESS By default, all client nodes have access to a server. You can restrict access to a server node only by client system, not by individual client users. FOR MORE INFORMATION Chapter 8 describes the procedures for granting or denying client access to a server. 7-28 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Processes Created by DQS Software ON A CLIENT On a client node, every client queue that you create (that is not a generic or logical queue) results in the creation of one process. Also, while a user is being notified of print job completion, a process is temporarily created. ON A SERVER For server nodes, every incoming connection from a client node results in the creation of one process. Also, the notification process on a server uses one permanent process. Understanding the DEC Distributed Queuing Service 7-29 ________________________________________________________________ Devices Supported by DQS Software SUPPORTED DEVICES DQS software does not run devices; rather, it places print jobs in queues for processing. DQS software supports devices by placing jobs in queues, if the device o Is driven by an OpenVMS print symbiont o Does not use parameter 8 in job requests DQS software does not support symbionts that require job information outside of that stored or maintained by the OpenVMS queue system. 7-30 Understanding the DEC Distributed Queuing Service ________________________________________________________________ Batch Jobs and DQS Printing DQS software supports the queuing of print jobs for processing on remote nodes in your network. It does not support the queuing of batch jobs. Do not configure batch queues to be DQS printer queues. DQS software does not prevent you from configuring batch queues, but the security of the system decreases if you do so. Understanding the DEC Distributed Queuing Service 7-31 8 ________________________________________________________________ Configuring and Managing a DQS Server ABOUT THIS CHAPTER This chapter presents an overview of the management tasks required by a DQS server and describes how to do the following: o Modify definitions of special logical names associated with the DQS server o Set up DQS remote queues o Control DQS client access to servers and their remote queues o Determine how DQS clients are accessing a server o Control the note on the banner page of a print job o Enable DQS status messages for queues o Enable the DQS print symbiont to control remote queues o Specify the scanning interval for the DQS server notification process o Specify a directory for PrintServer log files o Specify the priority of the server process o Specify the maximum priority of DQS print jobs o Specify the duration of links to client nodes o Move the server account directory to a new device o Configure server software for a VMScluster environment o Configure daisy-chain queues The last section contains a summary of the server management tasks. Configuring and Managing a DQS Server 8-1 ________________________________________________________________ Overview of Server Management MAIN TASKS Configuring and managing a DQS server primarily involves: o Defining server system logical names in the SYS$MANAGER:DQS$SYSTARTUP.COM file All site-specific definitions that affect the behavior of the software belong in this file. If this file does not exist on your system, copy the DQS$SYSTARTUP.TEMPLATE to DQS$SYSTARTUP.COM and edit it to include the desired server logical name definitions. o Setting up access to remote queues in the SYS$MANAGER:DQS$SERVER_CONFIG.TXT file The SYS$STARTUP:DQS$STARTUP.COM procedure o Invokes the SYS$MANAGER:DQS$SYSTARTUP.COM procedure to make changes permanent o Processes the SYS$MANAGER:DQS$SERVER_CONFIG.TXT file to set up DQS client node access to remote queues on DQS server systems Do not edit SYS$STARTUP:DQS$STARTUP.COM. USING SYSMAN When directed to restart DQS software in a VMScluster, you can use one of the following methods: o Invoke SYS$STARTUP:DQS$STARTUP.COM on each node in the cluster. o Execute the SYSMAN utility. 8-2 Configuring and Managing a DQS Server ________________________________________________________________ Defining Server System Logical Names PROCEDURE To make permanent changes to your server configuration in the DQS$SYSTARTUP.COM file, do the following: __________________________________________________________ Step___Action_____________________________________________ 1 Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file. 2 Add or change the definitions of the desired server logical names. Make sure that you define the logical name systemwide and in executive mode: $ DEFINE/SYSTEM/EXECUTIVE_MODE _$ logical-name values