     @                      DEC Distributed Queuing Service for OpenVMSC                      Systems_______________________________________ &                      Documentation Set  -                      Part Number: AA-Q5FVA-TE   E                      This manual consists of guides for the user, the F                      system manager, and the software installer. TheseF                      guides describe how to use, configure and manage,H                      and install the DEC Distributed Queuing Service forH                      OpenVMS Systems software on OpenVMS AXP and OpenVMS!                      VAX systems.           =                      Revision/Update Information: This manual D                                                   supersedes the VAXE                                                   Distributed Queuing F                                                   Service User's GuideD                                                   (AA-KM86B-TE), theA                                                   VAX Distributed A                                                   Queuing Service G                                                   Management Guide (AA- D                                                   KM87B-TE), the VAXE                                                   Distributed Queuing F                                                   Service InstallationB                                                   Guide (AA-KM94B-B                                                   TE), and the DECE                                                   Distributed Queuing E                                                   Service for OpenVMS B                                                   AXP InstallationF                                                   Guide (AA-PW1SA-TE).  F                      Operating System and Version: OpenVMS AXP Version@                                                   6.1 or higher.E                                                   OpenVMS VAX Version B                                                   5.5-2 or higher.D                                                   Future maintenanceF                                                   releases may requireB                                                   higher versions.  A                      Software and Version:        DEC Distributed A                                                   Queuing Service A                                                   Version 1.3 for B                                                   OpenVMS Systems.  2                      Digital Equipment Corporation+                      Maynard, Massachusetts                  E            __________________________________________________________ %            First Printing, March 1994   A            Digital Equipment Corporation makes no representations B            that the use of its products in the manner described inC            this publication will not infringe on existing or future C            patent rights, nor do the descriptions contained in this C            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.  B            The postpaid Reader's Comments forms at the end of thisA            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,B            Digital, OpenVMS, OpenVMS AXP, TK, VAX, VAXcluster, VAX6            DOCUMENT, VMScluster, and the DIGITAL logo.  ;            Motif is a registered trademark of Open Software             Foundation, Inc.   A            All other trademarks and registered trademarks are the 0            property of their respective holders.  E                                                                 S2439   0            This document is available on CD-ROM.  E            This document was prepared using VAX DOCUMENT Version 2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................     xi         Part I  User's Guide       1  Using the DQS Software  C          Understanding the Software.........................    1-2 C          Getting Help With DQS..............................    1-5   '    2  Printing Files Using DQS Software   C          Printing in Network Environments...................    2-2 C          Understanding Print Job Messages...................    2-5 C          Printing with Forms................................    2-6 C          Using PRINT Command Qualifiers.....................    2-7 C          Understanding PRINT Command Error Messages ........   2-11   &    3  Viewing the Status of Print Jobs  C          The QSHOW Command..................................    3-2 C          Checking the Status of a Print Job.................    3-3 C          Using QSHOW Command Qualifiers.....................    3-5 C          Understanding QSHOW Error Messages.................    3-7                     C                                                                 iii                  (      4  Deleting Print Jobs From a Queue  E            The QDELETE/ENTRY Command..........................    4-2 E            Deleting a Print Job...............................    4-3 E            Understanding QDELETE Error Messages...............    4-4   .      5  Modifying the Characteristics of a Job  E            The QSET/ENTRY Command.............................    5-2 E            Modifying a Print Job..............................    5-3 E            Using QSET Command Qualifiers......................    5-4 E            Understanding QSET Error Messages..................    5-6   (      6  Spooling Files to a Client Queue    $      Part II  System Manager's Guide  9      7  Understanding the DEC Distributed Queuing Service   E            Overview of the DQS Software.......................    7-2 E            Primary Functions of the DQS Software..............    7-5 E            Functions of the DQS Commands......................    7-7 E            Functions of DQS Software Components...............    7-9 E            The DQS Notification Service.......................   7-12 E            The DQS Symbionts..................................   7-14 E            Defining Forms on Client and Server Nodes..........   7-16 E            The DQS Server Account.............................   7-17 E            The Significance of Parameter 8 in DQS Printing....   7-18 E            Configuring DQS Software...........................   7-19 E            Using Daisy-Chained Queues.........................   7-21 E            DQS Error Conditions...............................   7-24 E            DQS Security Issues and Access Rights..............   7-28 E            Processes Created by DQS Software..................   7-29 E            Devices Supported by DQS Software..................   7-30 E            Batch Jobs and DQS Printing........................   7-31                         iv                  0         8  Configuring and Managing a DQS Server  H               Overview of Server Management......................    8-2H               Defining Server System Logical Names...............    8-3H               Modifying Definitions of Certain Logical Names.....    8-5H               Before You Set Up Remote Queues....................    8-6H               Understanding How to Set Up Remote Queues..........    8-7H               Understanding the Configuration File...............    8-8H               Setting Up Remote Queues...........................   8-10H               Enabling Network Access............................   8-11:               Denying Client Node Authorization to the DQSH               Server.............................................   8-13;               Granting Client Node Authorization to the DQS H               Server.............................................   8-14H               Making Your Changes Take Effect....................   8-16H               Determining How Clients are Accessing a Server.....   8-17H               Controlling the Note on the Job Banner Page........   8-23H               Enabling Status Messages for Queues................   8-25?               Enabling the DQS Print Symbiont To Control Remote H               Queues.............................................   8-279               Specifying the Scanning Interval for Server H               Notification.......................................   8-29H               Specifying a Directory for PrintServer Log Files...   8-31H               Specifying the Priority of the Server Process......   8-33:               Specifying the Maximum Priority of DQS PrintH               Jobs...............................................   8-34H               Specifying the Duration of Links to Client Nodes...   8-35:               Move the Server Account Directory to AnotherH               Device.............................................   8-37H               Advanced VMScluster DQS Configurations.............   8-398               Specifying Unique Notifier Lock Names in aH               VMScluster Environment.............................   8-407               Redefining DQS$SERVER_CONFIG_DAT_FILE and H               DQS$SERVER_CONFIG_TXT_FILE.........................   8-41H               Specifying Remote Queues on a VMScluster System....   8-43H               Configuring Daisy-Chained Queues...................   8-44H               Summary of Server Tasks............................   8-46                H                                                                        v                 -      9  Configuring and Managing a DQS Client   E            Overview of Client Management......................    9-2 E            Managing Client Processes..........................    9-3 E            Creating Client Queues with DQS$IMPORT.COM.........    9-4 4            Creating Client Queues with More AdvancedE            Methods............................................    9-6 :            Temporarily Changing the Definition of a ClientE            Queue..............................................   9-13 E            Deleting Client Queues.............................   9-15 3            Configuring Client Nodes in a VMScluster E            Environment........................................   9-16 0            Synchronizing Client and Server FormsE            Definitions........................................   9-17 E            Spooling to a Client Queue.........................   9-19 E            Controlling the Note on the Job Banner Page........   9-22 E            Regulating Forms Checking..........................   9-24         10  Troubleshooting  E            General Troubleshooting Guidelines.................   10-2 E            Running the IVP....................................   10-3 >            Problem: Remote Notification Is Not Working for AnyE            Jobs...............................................   10-6 ;            Problem: Notification of Print Job Completion Is E            Not Occuring for Some Jobs.........................   10-7 8            Problem: Jobs Remain in the Remote Queue WithE            Completion Status..................................   10-8 E            Problem: A Job Is Not Printing.....................   10-9 8            Problem: Many DQS Client Queues Slow Down theE            Network............................................  10-18   !      Part III  Installation Guide           11  What You Need to Know  E            Required Hardware and Software.....................   11-3 E            Licensing..........................................   11-5 E            Processes Created..................................   11-6 E            First-time Installation Considerations.............   11-7 E            Upgrade Considerations.............................   11-8 E            Time Required to Install...........................  11-10           vi                           12  Do This First   H               Inspect the Distribution Kit.......................   12-2H               Review DQS Installation............................   12-4H               Prepare for VMScluster Installation................   12-5H               Log In to a Privileged Account.....................   12-6H               Access Online Release Notes........................   12-8H               Determine Process Account Quotas...................   12-9H               Determine Disk Space...............................  12-11H               Set Up an Alternate Working Device.................  12-13H               Register Your License..............................  12-16H               Perform System Maintenance Procedures..............  12-18H               Perform First-Time Installation Activities.........  12-22H               Back Up Your System Disk...........................  12-25  "         13  Using the PCSI Utility  H               Accessing Release Notes............................   13-2H               Starting the Installation: DCL Interface...........   13-3H               Obtaining DCL Help.................................   13-7H               Determining Installation Defaults: DCL Interface...   13-8H               Verifying Preinstallation Tasks: DCL Interface.....   13-9H               Stopping and Restarting: DCL Interface.............  13-11H               Responding to Questions: DCL Interface.............  13-12H               Determining Installation Progress: DCL Interface...  13-14H               Starting the Installation: Motif Interface.........  13-15H               Obtaining Motif Help...............................  13-18H               Selecting Product Options: Motif Interface.........  13-20H               Stopping and Restarting: Motif Interface...........  13-21H               Recovering from Errors.............................  13-22  '         14  Using the VMSINSTAL Utility   H               Accessing Release Notes with VMSINSTAL.............   14-2H               Starting the Installation Procedure................   14-5H               Stopping and Restarting the VMSINSTAL Procedure....   14-7H               Responding to Installation Questions...............   14-8H               Following Installation Progress....................  14-12              H                                                                      vii                 &      15  After Installing DQS Software  E            Postinstallation Tasks: New Server Installation....   15-2 E            Postinstallation Tasks: New Client Installation....   15-4 6            Postinstallation Tasks for All Systems: NewE            Installation.......................................   15-5 1            Postinstallation Tasks: Upgrade Server E            Installation.......................................   15-8 1            Postinstallation Tasks: Upgrade Client E            Installation.......................................  15-11 :            Postinstallation Tasks for All Systems: UpgradeE            Installation.......................................  15-13 E            Postinstallation Tasks: VMScluster Nodes...........  15-16         Part IV  Appendixes          A  DQS User Messages   E            Message Section....................................    A-2   #      B  DQS System Manager Messages   E            DQS Message Format.................................    B-2 E            Submitting a Software Performance Report...........    B-3 E            Message Section....................................    B-4   .      C  Server and Client System Logical Names  E            DQS Product Logical Names..........................    C-2DE            DQS Server Logical Names...........................    C-4sE            Client Logical Names...............................    C-7a  (      D  Using DQS With Various Symbionts  E            How Various Symbionts Function.....................    D-2 7            Modifying Your Symbiont To Output Client JobtE            Information........................................    D-3t              	      viiig                 4         E  Files Installed or Modified on the System  H               Files Installed on Server Nodes....................    E-2H               Files Installed on Client-Only Nodes...............    E-6H               Files Modified by the Installation.................    E-8H               Accounts and Processes Added.......................    E-9H               Installed Images...................................   E-11           F  Sample Installations   H               Sample PCSI Installation on an OpenVMS System......    F-2=               Sample VMSINSTAL Installation on an OpenVMS AXP H               System.............................................    F-6  $         G  DQS Installation Messages  H               Installation Error Messages........................    G-3H               IVP Error Messages.................................    G-4H               Error Reporting....................................    G-5           Glossary    
         Index              Examples  =               7-1       A DQS Error That Prevents a Print Job H                         From Transferring........................   7-25  H               7-2       A DQS Error That Stops a Client Queue....   7-27  H               8-1       Viewing NETSERVER.LOG Information........   8-17  H               8-2       Logging Client Access to a Server........   8-18  H               8-3       Looking at DQS$SERVER.NODES .............   8-19  H               8-4       Enabling Client Accounting Information...   8-22  H               8-5       Defining a Status Message for a Queue....   8-26  H               8-6       Enabling the DQS Print Symbiont..........   8-28  <               8-7       Specifying the Scanning Interval forH                         DQS$NOTIFIER.............................   8-30  >               8-8       Specifying a Directory for PrintServerH                         Log Files................................   8-31  H                                                                       ix                 :            8-9       Specifying the Priority of the ServerE                      Process..................................   8-33o  8            8-10      Specifying the Maximum Priority forE                      Queuing Print Jobs.......................   8-34_  8            8-11      Specifying the Duration of Links toE                      Inactive Clients.........................   8-36   =            8-12      Specifying Unique Notifier Lock Names in E                      a Nonhomogeneous VMScluster..............   8-40   1            9-1       Creating a Client Queue withnE                      DQS$IMPORT.COM...........................    9-5u  0            9-2       Creating Client Queues WithE                      DQS$DEFINE.COM...........................    9-7u  E            9-3       Defining Generic Client Queues...........   9-10i  E            9-4       Defining Logical Client Queues...........   9-12i  E            9-5       Temporarily Changing the Remote Queue....   9-14E  E            9-6       Setting Up a LAT Port Device.............   9-19   =            9-7       Changing Client Queue Spooled to LTA999: E                      Device...................................   9-20p  E            9-8       Spooling to a LAT Port Device............   9-20   =            9-9       Regulating Forms Checking on Many Client,E                      Systems..................................   9-26,  :            F-1       Sample PCSI Client Installation on anE                      OpenVMS System...........................    F-2r  7            F-2       Sample PCSI Server Installation onaE                      OpenVMS VAX System.......................    F-4r  <            F-3       Sample VMSINSTAL Client Installation onE                      an OpenVMS AXP System....................    F-6   <            F-4       Sample VMSINSTAL Server Installation onE                      OpenVMS VAX System.......................   F-10_        Tables_  E            1         Additional Information...................    xvi   E            2         Conventions..............................   xvii.  ;            2-1       PRINT Command Qualifiers That Function E                      Differently with DQS Printing............    2-7.  7            5-1       QSET/ENTRY Command Qualifiers ThathE                      Function Differently with DQS Printing...    5-4g  E            7-1       Summary of DQS Commands..................    7-6.        x                 5               7-2       Functions of the DQS Software H                         Components...............................    7-9  9               8-1       Summary of Server Node Management H                         Tasks....................................   8-46  H               11-1      Summary: What You Need to Know...........   11-1  H               11-2      Prerequisite Software....................   11-4  H               12-1      Preinstallation Task Summary.............   12-1  ;               12-2      Process Quotas for the InstallationaH                         Account..................................   12-9  H               12-3      Disk Space Requirements..................  12-11  9               12-4      Minimum Required System ParameterYH                         Values...................................  12-18  H               13-1      PCSI Installation Task Summary...........   13-1  A               13-2      Features You Can Request When Starting aneH                         Installation.............................   13-5  H               14-1      VMSINSTAL Installation Task Summary......   14-1  H               15-1      Task Summary.............................   15-1  H               E-1       Files Installed on DQS Server Nodes......    E-2  :               E-2       Files Installed on DQS Client-OnlyH                         Nodes....................................    E-6                        H                                                                       xi    i                      H         ________________________________________________________________  H                                                                  Preface                 ABOUT THE SOFTWAREC               The DEC Distributed Queuing Service (DQS) for OpenVMS D               Systems software enables you to print files on devices@               that are attached to remote DECnet systems on yourB               network. DQS software also allows you to display theE               status of your jobs at any time during their processing 6               and to delete or modify your print jobs.  A               The DEC Distributed Queuing Service Version 1.3 for.E               OpenVMS systems software product replaces the following.               products:   E               o  VAX Distributed Queuing Service Version 1.2 software   H               o  DEC Distributed Queuing Service for OpenVMS AXP Version                  1.2 softwareo  H               This product is based on a client/server design, where twoE               components of software (client and server) cooperate to .               make the print service function.           PARTS OF THE MANUALw#               This manual contains:.  A               o  A user's guide that describes how to use the DQS.                  software   H               o  A system manager's guide that describes the concepts ofE                  the DQS software and how to configure and manage DQS *                  client and server systems      H                                                                       xi .               A            o  An installation guide that describes how to install D               the DQS software on OpenVMS AXP or OpenVMS VAX systemsD               using the VMSINSTAL utility or the POLYCENTER Software"               Installation utility  A            At the back of this document are two Reader's CommentstD            forms. If you have any comments about this document, fillE            out the form and mail it; your comments will be consideredc0            for any future revision of the guide.  
      AUDIENCE             This manual is for:  C            o  Anyone who wants to print files to printers on remote                OpenVMS systems.  ?               A knowledge of the Digital Command Language (DCL)iB               PRINT, SHOW/QUEUE, DELETE/ENTRY, and SET QUEUE/ENTRY"               commands is assumed.  C            o  DECnet network or system managers who are responsiblee?               for installing, configuring, and managing the DQS.(               software in their network.                                                  xii    c          H         ________________________________________________________________           Document Structure           USER'S GUIDEA               Part I, the user guide, has the following chapters:p  H               __________________________________________________________H               Chapter___Describes_______________________________________  G               Chapter   The DQS software and its capabilities, in brief                1s  G               Chapter   Printing files on remote nodes, including PRINTnH               2         command qualifiers and possible error conditions  ;               Chapter   Displaying the status of print jobs                3E  ,               Chapter   Deleting a print job               4   D               Chapter   Modifying the characteristics of a print job               5a  8               Chapter   Spooling files to a client queueH               6_________________________________________________________           SYSTEM MANAGER'S GUIDED               Part II, the system manager's guide, has the following               chapters:a  H               __________________________________________________________H               Chapter___Describes_______________________________________  G               Chapter   The DEC Distributed Queuing Service for OpenVMS D               7         Systems and its functions, including how theG                         software can be configured and how the softwareT0                         handles error conditions  D               Chapter   Configuring and managing a DQS server system               8   D               Chapter   Configuring and managing a DQS client system               9n  H               Chapter   Quidelines for troubleshooting problems with theH               10________DQS_software____________________________________  H                                                                     xiii    a                  INSTALLATION GUIDE.>            Part III, the installation guide, has the following            chapters:  E            __________________________________________________________ E            Chapter___Describes_______________________________________.  A            Chapter   Requirements for installing the DQS software.
            11.  1            Chapter   Preinstallation requirementsN
            12A  ?            Chapter   Installing the DQS software using the PCSI             13        utility  D            Chapter   Installing the DQS software using the VMSINSTAL            14        utility  +            Chapter   Postinstallation taskseE            15________________________________________________________.        APPENDIXES 0            Part IV has the following appendixes:  E            __________________________________________________________nE            Appendix____Describes_____________________________________0  1            Appendix A  DQS messages users may see1  ;            Appendix B  DQS messages system managers may seef  A            Appendix C  DQS server and client system logical names.  B            Appendix D  How the DQS software functions with various&                        print symbionts  B            Appendix E  Files installed and modified on your system  /            Appendix F  Sample installation logs.  E            Appendix_G__DQS_messages_installers_may_see_______________.            xiv               H         ________________________________________________________________            Associated Documentation           DQS INFORMATION E               The DEC Distributed Queuing Service for OpenVMS Systems *               information set consists of:  D               o  DEC Distributed Queuing Service for OpenVMS Systems"                  Documentation Set  D               o  DQS, PRINT, QDELETE, QSET, and QSHOW entries in the&                  OpenVMS HELP facility  G               o  Online Command Reference Card in SYS$HELP:DQS_COMMAND_.                  REF.PS   F               o  Online Release Notes in SYS$HELP:DQS013.RELEASE_NOTES  D               o  DEC Distributed Queuing Service for OpenVMS Systems                  Cover Lettern  D               o  DEC Distributed Queuing Service for OpenVMS Systems3                  Software Product Description (SPD)a                                            H                                                                       xv    e                  OTHER RESOURCES:            Resources listed in Table 1 may also be useful.    E      Table_1_Additional_Information__________________________________.  E      For_information_on_._._.________See_the_following_._._._________D  ;      The OpenVMS Digital Command     OpenVMS DCL Dictionary       Language (DCL) commands  D      Extensions to the DCL language  DECprint Supervisor for OpenVMS1      for PostScript printers         User's Guidet  @      Understanding OpenVMS system    OpenVMS System Messages andB      error messages                  Recovery Procedures Reference>                                      Manual or the online HELP6                                      /MESSAGE facility  D      OpenVMS system management, in   OpenVMS System Manager's ManualA      general                         and OpenVMS System Manager's1?                                      Utilities Reference Manual.  E      The POLYCENTER Software         Software Integrator User's Guidee      Installation utilityS  ?      How to license a product        OpenVMS License Management E      ________________________________Utility_Manual__________________                                         xvi    e          H         ________________________________________________________________           Conventions.  ?               Table 2 lists the conventions used in this guide.   H               Table_2_Conventions_______________________________________  H               Convention_____________Meaning____________________________  ?               OpenVMS system         Means both the OpenVMS AXPiE                                      operating system and the OpenVMS :                                      VAX operating system.  G               UPPERCASE TEXT         Indicates the name of a command, a G                                      file, a parameter, a procedure, or -                                      utility.n  E               $ PRODUCT              In interactive examples, prompts C                                      or displayed text appears in a G                                      monospace font. User input appears >                                      in a bold monospace font.  C               lowercase italics      Indicates variables in commandME                                      syntax or examples for which theQ;                                      user supplies a value..  H               Ctrl/x                 In interactive examples, a sequenceF                                      such as Ctrl/x indicates that youF                                      must hold down the Ctrl key whileH                                      you press another key or a pointingG                                      device button; for example, Ctrl/C./                                      or Ctrl/Z..  >               Return                 Indicates the Return key.  H               [ ]                    In command formats, square bracketsF                                      encloses optional values. (Do not8                                      type the brackets.)  D                                      In installation prompts, squareF                                      brackets enclose a default value.  H                                                 (continued on next page)    H                                                                     xvii l  i            E            Table_2_(Cont.)_Conventions_______________________________.  E            Convention_____________Meaning____________________________.  A                                   In a file specification, square D                                   brackets serve as delimiters for aE            _______________________directory_name.____________________t                                                                            
      xviii g                     H                                                                   Part IH         ________________________________________________________________  H                                                             User's Guide        H               This part describes how to use the DQS software on OpenVMSG               AXP and OpenVMS VAX systems. The User's Guide is intended.E               for anyone who wants to print, track, delete, or modifyS6               jobs on a remote printer in the network. i  n                  H                                                                        1H         ________________________________________________________________  H                                                   Using the DQS Software                 ABOUT THIS CHAPTER               This chapter:a  D               o  Provides an overview of the DEC Distributed Queuing5                  Service for OpenVMS Systems software   E               o  Explains how to get help when using the DQS commands                                                       H                                               Using the DQS Software 1-1               E      ________________________________________________________________         Understanding the Software             WHAT DQS CAN DO FOR YOUE            The DEC Distributed Queuing Service for OpenVMS Systems is 2            a software product that enables you to:  D            o  Print files on printers connected to remote systems in               your network.J  C            o  Show the status of your print jobs on remote systems.h  9            o  Delete your print jobs from remote systems..  B            o  Set the characteristics of your print jobs on remote               systems.  '            Using DQS software, you can:   9            o  Print files on any printer in your network.t  B            o  Take advantage of special printers that might not be8               physically connected to your local system.  =            o  Print files even if your system has no printers.               connected.  C            o  Distribute reports efficiently to remote sites within1A               your company or organization through both local and.!               wide area networks.m        WHAT YOU NEED TO KNOWA            If you know how to print files on OpenVMS systems, youc>            know how to use most DQS features. The DQS commandsB            (PRINT, QSHOW, QSET, and QDELETE) look and function theB            same as the Digital Command Language (DCL) PRINT, SHOW,$            SET, and DELETE commands.  E            To use DQS software, you do not need to log in to a remote D            system, copy files across a network, or have proxy accessE            or special privileges. You do not need to consider whether ,            a print queue is local or remote.        1-2 Using the DQS Softwarel C  S                     HOW DQS WORKS ?               This is what happens when you print using the DQS                software:M  H               __________________________________________________________H               Stage__Description________________________________________  E                 1    You issue a PRINT command and queue the job to a.F                      remote system. The remote system does not have to.                      be reachable at the time.  G                 2    The DQS software keeps trying until it establishes1E                      a DECnet link to the remote system and transfersf8                      the print job to the remote system.  ?                 3    After job transfer, you can request status E                      information, modify the print request, or delete #                      the print job..  B                 4    DQS software establishes a DECnet link to theA                      remote system and executes your request. ThesH                      remote system must be available for DQS software to*                      complete the request.  G                 5    The job prints on the remote printer. DQS software1B                      notifies you that the job has printed, if youH               _______include_the_/NOTIFY_qualifier_on_the_PRINT_command.           SOME DQS TERMSF               Some terms used in this guide in connection with the DQS               software are:o  :               o  Client - the system at which a you reside  F               o  Server - the system to which the printer is connected  9               o  Client queue - the queue you use locallyS  F               o  Remote queue - the queue on the server that feeds the                  printer  B               DQS software moves print jobs from client queues (onC               clients) to corresponding remote queues (on servers).     H                                               Using the DQS Software 1-3                       FOR MORE INFORMATION >            For more information on the differences between DQSC            commands and corresponding DCL commands, use this manualt(            or the OpenVMS HELP facility.  C            For more information on how to print files, refer to the C            descriptions of the PRINT, SHOW QUEUE, DELETE/ENTRY, and C            SET QUEUE /ENTRY commands in the OpenVMS DCL Dictionary.                                                                                 1-4 Using the DQS Software_ _  _          H         ________________________________________________________________           Getting Help With DQSE               THE HELP COMMAND@               To get help with the DQS commands, you can use the4               standard OpenVMS HELP facility. Enter:                 $ HELP command                 Where:  D               command   Is DQS or the PRINT, QSHOW, QDELETE, or QSET%                         command verb.m           EXAMPLEeC               For example, if you enter the following command, text H               displays on your terminal that explains how to use the DQS               QSHOW command.           $ HELP QSHOW <Return>   
         QSHOWc  P             Displays information about queues and jobs  that  are  currently  inP             queues.  If the queue is a DQS client queue, QSHOW also displays the;             remote queues associated with the client queue.n  P             o  Display characteristic names and numbers that  are  available  on-                queues (see /CHARACTERISTICS).p  P             o  Display form names and numbers that are available on queues  (see                /FORM).               Format:t  !               QSHOW  [queue-name]   +           Additional information available:e  '           Parameters Command_QualifierstS           /ALL       /BATCH     /BRIEF     /DEVICE    /FILES     /FULL      /OUTPUT %           /CHARACTERISTICS      /FORM            QSHOW Subtopic?   H                                               Using the DQS Software 1-5 o  n                  H                                                                        2H         ________________________________________________________________  H                                        Printing Files Using DQS Software                 ABOUT THIS CHAPTER               This chapter:   ?               o  Explains the DQS printing process in basic and #                  multinode networksm  H               o  Shows examples of messages you receive when you enter a                  DQS print job  >               o  Explains requirements for printing with forms  G               o  Lists differences between DQS PRINT qualifiers and DCLn!                  PRINT qualifiersu  A               o  Lists some status and error messages you may seeE           FOR MORE INFORMATIOND               If you need more information on how to use the DigitalF               Command Language (DCL) PRINT command and its qualifiers,2               refer to the OpenVMS DCL Dictionary.                            H                                    Printing Files Using DQS Software 2-1 _  _          E      ________________________________________________________________S  %      Printing in Network Environmentsi            BASIC NETWORK EXAMPLED            Assume that your site has a network of two systems, APPLE            and BANANA:  D            o  Node APPLE has an attached PrintServer 17/600 printer.  <            o  The PrintServer 17/600 queue on APPLE is named               Q_CHICAGO.  2            o  Node BANANA has no attached printer.        WITHOUT DQS SOFTWARE A            Without DQS software, from node APPLE, you can print a D            file named TRIP_REPORT.TXT on your own system by entering9            this PRINT command line at the DCL prompt ($):   ;            $ PRINT TRIP_REPORT.TXT/QUEUE=Q_CHICAGO <Return>a  B            Node BANANA users cannot use the printer on node APPLE.        WITH DQS SOFTWAREE            If DQS software is installed on both nodes, node APPLE can C            function as a server; that is, APPLE's printer can serveeE            users of both systems. Node BANANA is then the DQS client.   E            Assume that your system manager defined a client DQS queue E            for node BANANA that corresponds to the queue Q_CHICAGO on B            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 <Return>t  	      NOTE B            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 g  D                     BASIC CONFIGURATION F               Figure 2-1 illustrates how the system manager configures1               DQS software in this basic network._    !         MULTINODE NETWORK EXAMPLE D               DQS software can be installed on networks of any size.@               Figure 2-2 illustrates a slightly more complex DQSE               configuration consisting of three nodes: APPLE, BANANA,_               and CHERRY:_  F               o  Node APPLE has an attached PrintServer 17/600 printer!                  named Q_CHICAGO.   H               o  Node CHERRY has an attached LN06 printer named Q_PARIS.  5               o  Node BANANA has no attached printer.   F               DQS can be installed on all three nodes. Nodes APPLE andE               CHERRY can function as servers; that is, their printers F               can serve users of other systems. All three nodes can beG               clients; that is, they can use the printers of the server_               systems.  %         PRINTING IN MULTINODE NETWORK F               Your system manager can define client DQS queues for allE               three systems that send print jobs to the remote queuesrE               Q_CHICAGO and Q_PARIS. For example, your system managerS8               can define the following (see Figure 2-2):  H         ________________________________________________________________7                                           To send printeD         Define client    On client        jobs to remote   On serverH         queues:__________node:____________queues:__________nodes:_______  A         CQ_EUROPE        APPLE            Q_PARIS          CHERRYA  A         CQ_FRANCE        BANANA           Q_PARIS          CHERRY   @         CQ_ILLINOIS      BANANA           Q_CHICAGO        APPLE  H         CQ_USA___________CHERRY___________Q_CHICAGO________APPLE________  D               Then, from node APPLE, for example, you can queue yourA               file to print on the LN06 printer on node CHERRY by                entering:t  H                                    Printing Files Using DQS Software 2-3                 ;            $ PRINT TRIP_REPORT.TXT/QUEUE=CQ_EUROPE <Return>   C            From node BANANA you can queue your file to print on thec3            LN06 printer on node CHERRY by entering:F  ;            $ PRINT TRIP_REPORT.TXT/QUEUE=CQ_FRANCE <Return>3  D            In both examples, the print job, TRIP_REPORT.TXT, is sentD            to the remote queue Q_PARIS on the server node CHERRY for            printing.        MULTINODE CONFIGURATIONC            Figure 2-2 illustrates how the system manager configures 2            DQS software in this multinode network.        ADVANTAGES OF DQS PRINTING B            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 asi@            necessary. You can also direct output to printers you            know are idle.a                                                *      2-4 Printing Files Using DQS Software u             H         ________________________________________________________________  (         Understanding Print Job Messages               STATUS MESSAGESeE               When you queue a file to be printed, you receive one of *               two acknowledgment messages:  E               o  If the client queue is empty, you see a message thatOD                  indicates that the file is being transferred to the7                  server node for printing. For example:'  N                  Job MARCH-INVOICE (queue CLIENT, entry 806) started on CLIENT  D               o  If the client queue is not empty, you see a message                  like this:t  D                  Job MARCH-INVOICE (queue CLIENT, entry 810) pending?                       pending status caused by queue busy state   F               The messages list the client queue, in this case CLIENT,(               and the client job number.  B               As with the DCL software, these messages are sent byE               default. You can suppress default messages by using the_;               /NOIDENTIFY qualifier with the PRINT command.n           PRINT JOB ENTRY NUMBERS_G               When you queue a file to print, the DQS software displaysMH               the job entry number of the client (that is, your) system.H               Job numbers printed on the header, burst, or trailer pagesB               are client job numbers, if the DQS print symbiont orC               the DECprint Supervisor for OpenVMS software runs theoE               server's printer. Otherwise, the job numbers are serverR               job numbers.                  H                                    Printing Files Using DQS Software 2-5               E      ________________________________________________________________         Printing with Forms            REQUIREMENTS C            Before the DQS software transfers a print job, it checks "            on the form being used.  C            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 E               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 onC            the client, the queue manager mounts the form before the E            software transfers the job. This can take several minutes.   D            If you queue a job with a form that is not mounted on theC            server, the job does not print until the operator mounts             the form.                                      *      2-6 Printing Files Using DQS Software    a          H         ________________________________________________________________  &         Using PRINT Command Qualifiers      !         DQS QUALIFIER DIFFERENCES F               Most of the qualifiers to the PRINT command function theE               same with DQS printing as they do with standard OpenVMS_E               printing. Qualifiers that function differently with DQS_2               printing are described in Table 2-1.  D         Table 2-1 PRINT Command Qualifiers That Function DifferentlyH         __________with_DQS_Printing_____________________________________                       FunctionH         Qualifier___Without_DQS______Function_With_DQS__________________  F                     Prints job       Transfers job to the server after4         /AFTER=time after specified  specified time.                     time._  E         /DELETE     Deletes file     Deletes file on the client after F                     after printing.  transfer to the server (files areE                                      always deleted from the server's :                                      disk after printing).  H                                                 (continued on next page)                                    H                                    Printing Files Using DQS Software 2-7                 =      Table 2-1 (Cont.) PRINT Command Qualifiers That Function_E      __________________Differently_with_DQS_Printing_________________h                    Function E      Qualifier___Without_DQS______Function_With_DQS__________________P  1      /FORM=type  Uses form type.  Uses form type.   E                                   o  The form name must be defined onED                                      both the DQS client and server.  B                                   o  If the form is not mounted onB                                      the client, the queue managerA                                      software mounts it (this may ;                                      take several minutes).R  B                                   o  If the form is not defined onA                                      the server, the job does not A                                      transfer, but remains in the D                                      queue with error status %JBC-F-0                                      NOSUCHFORM.  ;                                   o  If the form is defined >                                      differently on server andD                                      client, the job is printed with5                                      the server form.o  ?      /HEADER     Specifies        Specifies whether header page C                  whether header   prints with file. The header pageiD                  page prints      includes server node and device inE                  with file.       the file specification; the version B                                   number of the file specification-                                   may differ.O  A      /HOLD       Holds job until  Does not transfer job to servers?                  released (by     until released (by QSET/ENTRYQ4                  SET/ENTRY        /RELEASE command).                  /RELEASE                   command).  E                                              (continued on next page).        *      2-8 Printing Files Using DQS Software l  i            @         Table 2-1 (Cont.) PRINT Command Qualifiers That FunctionH         __________________Differently_with_DQS_Printing_________________                       FunctionH         Qualifier___Without_DQS______Function_With_DQS__________________  E         /NOTIFY     Broadcasts       Broadcasts messages to you afternH                     message to       job transfers and after job prints.!                     you after job_                     prints._  F         /OPERATOR=  Sends string to  Sends string to operators on bothF         string      operator when    client and server when job begins.                     job begins to    to print.                     print.  @                     Passes from 1    Passes from 1 to 7 optionalD         /PARAMETERS to 8 optional    parameters to job. DQS softwareE         =(pa-       parameters to    reserves parameter 8 for its owntE         rameter     job.             use. If you specify parameter 8,nE         [,...])                      DQS software generates an error,qE                                      and leaves the job in the client G                                      queue with an error status of DQS- 2                                      F-P8RESERVED.  E                     Specifies        Specifies priority of print job. F         /PRIORITY=n priority of      Priority limits are configured onE                     print job.       the server for all client users.eH                                      You can request any print priority,H                                      but the server queues your job withG                                      no more than the specified maximum .                                      priority.  D         /SETUP=     Extracts         Extracts specified modules fromB         mod-        specified        device control library on theG         ule[,...]   modules from     server; the client system's device B                     device control   control libraries need not beH         ____________library._________defined.___________________________              H                                    Printing Files Using DQS Software 2-9                 
      EXAMPLESaB            For example, to transfer a file to the printer queue onD            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 <Return>M      Job CHANGES (queue CQ_EUROPE, entry 324) holding until 30-JUL-1994 11:30Q  =            If you want to be notified after your print job is @            transferred and completes, use the /NOTIFY qualifier.            For example:   7      $ PRINT CHANGES.PS/QUEUE=CQ_EUROPE/NOTIFY <Return> H      Job CHANGES (queue CQ_EUROPE, entry 548) started on queue CQ_EUROPE4      Job CHANGES (queue EUROPE, entry 548) completed  R      Print job CHANGES (queue CQ_EUROPE, entry 548) completed at 30-JUL-1994 10:24      $  >            Each "completed" message means something different.  E            o  The first indicates that the file transfer is complete.R  E            o  The second indicates that the job printed on the server                node.   E            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                H         ________________________________________________________________  2         Understanding PRINT Command Error Messages               ERROR MESSAGESG               If a DQS print job in a client queue fails to transfer tolF               the server, the job remains in the client queue with theF               message "terminated with error status" and an associatedF               error status. To examine the error status, use the QSHOW&               command (see Chapter 3).  B               If you specify the /NOTIFY qualifier, you receive anF               error message when your print job fails to transfer. For               example:  S         Job TRIP_REPORT (queue CQ_ILLINOIS, entry 341) terminated with error statusS         %status, message-text   F               You must either delete the job or release it for anotherF               try. The QDELETE/ENTRY command (for deleting jobs from a/               queue) is described in Chapter 4._  !         COMMON DQS ERROR MESSAGES B               Following are some common DQS error messages with an0               explanation and a recovery action.  F               o  %DQS-F-BADQUEUE-The remote queue on the server systemA                  is not accessible to DQS clients. Ask the system A                  manager to modify the remote queue on the server G                  system. (The DQS$QUEUE_remote-queue logical name needsp                   to be defined.)  C               o  %JBC-F-NOSUCHFORM-You specified a form that is not D                  defined on the server. Enter the job again, using aG                  different form or specifying a queue where the form isf                  defined.o  E               o  %DQS-F-P8RESERVED-You used the /PARAMETERS qualifieraF                  and specified all eight parameters. Reenter the print9                  request with less than eight parameters.   B               Refer to Appendix A for a complete list of messages.    H                                   Printing Files Using DQS Software 2-11    N                  H                                                                        3H         ________________________________________________________________  H                                         Viewing the Status of Print Jobs                 ABOUT THIS CHAPTER               This chapter:G  G               o  Compares the DQS QSHOW command with the DCL SHOW QUEUES                  command  G               o  Describes how to check the status of a print job using F                  the QSHOW command and how to interpret the associated                  outputm  >               o  Compares QSHOW qualifiers with DCL SHOW QUEUE                  qualifiersA  .               o  Explains QSHOW error messages                                        H                                     Viewing the Status of Print Jobs 3-1 s  s          E      ________________________________________________________________e        The QSHOW Command      E      COMPARISON_WITH_DCL_COMMAND_____________________________________u            ThisrE            command_._._.____Enables_you_to_._._._____________________P  @            DCL SHOW QUEUE   Display the status of queues on your)                             local system.n  @            DQS QSHOW        Display the status of both local andE            _________________remote_print_queues.______________________  C            Using the DCL SHOW QUEUE command to view the status of a E            DQS client queue works, but it does not show the status of E            the associated remote queue. For that information, use thehB            QSHOW command. You can use the QSHOW command to examine:            both client (local) and server (remote) queues.                                                  )      3-2 Viewing the Status of Print Jobsi s  t          H         ________________________________________________________________  *         Checking the Status of a Print Job               QSHOW COMMANDLE               To check the status of a print job, enter the followingC;               command at the DCL prompt on the client node:   0               $ QSHOW client-queue-name <Return>           SAMPLE OUTPUTrG               The following examples use the same node names and queuesaD               used in the DQS client/server examples from Chapter 2.  H               For example, you are working on node APPLE, and you queuedF               the file TRIP_REPORT.PS to the client queue CQ_EUROPE toF               print on the printer on node CHERRY. To check the status'               of your print job, enter:e  (               $ QSHOW CQ_EUROPE <Return>  4               The command output may look like this:  ?         ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]e*         Printer queue Q_PARIS, on CHERRY::  B           Jobname         Username     Entry       Blocks   StatusB           -------         --------     -----       ------   ------7             (5 intervening jobs containing 2019 blocks)oC           TRIP_REPORT     JONES        1229            98   Pendingu  Q         =============================to be transferred=========================== U         Server queue CQ_EUROPE, on APPLE::, mounted form LN06_DEFAULT (stock=DEFAULT)   8               The information in this example tells you:  F               o  The name of the client node is APPLE. The name of the'                  server node is CHERRY.L  D               o  The queue shown as the "server queue" is the clientG                  queue CQ_EUROPE on node APPLE. ("Server" refers to the F                  OpenVMS concept of server queues, not the DQS concept"                  of server nodes.)  F               o  The queue shown as "remote queue" is the remote queue(                  Q_PARIS on node CHERRY.  H                                     Viewing the Status of Print Jobs 3-3 T  E            A            o  Five print jobs are currently ahead of yours in theRC               remote queue. They total 2019 blocks of data. You cannC               use this information to estimate how long before your                job prints.t  B            o  Your print job is in the remote queue on node CHERRYB               awaiting printing (status "Pending"). If your job is1               printing, the status is "Printing."   E            o  The form on the client queue is named LN06_DEFAULT. You E               are informed if the client queue is stopped or stalled.   D            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 A               privileged user and you specify the /ALL qualifier._C               In any event, you cannot see other users' jobs in theS?               client queue, unless the queue is world readable.c  E            If you queue another job and check the status, you may get             results like this:,        $ QSHOW CQ_EUROPE <Return>   <      ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]'      Printer queue Q_PARIS, on CHERRY::r  ?        Jobname         Username     Entry       Blocks   Statusr?        -------         --------     -----       ------   ------i  N      =============================to be transferred===========================R      Server queue CQ_EUROPE, on APPLE::, mounted form LN06_DEFAULT (stock=DEFAULT)C        TRIP_REPORT     JONES        1234            98   Processingh  A            This example indicates that your job is in the processbB            of being transferred to the server node CHERRY. If jobsD            are ahead of yours in the client queue on node APPLE, the            status is "Pending."E              )      3-4 Viewing the Status of Print Jobs     R          H         ________________________________________________________________  &         Using QSHOW Command Qualifiers               DQS QSHOW QUALIFIERSG               The DQS QSHOW command uses the same qualifiers as the DCL 0               SHOW QUEUE command, plus one more.  H               QSHOW also uses the qualifier /QUEUE=queue-name to support8               the /FORM and /CHARACTERISTICS qualifiers.           /FORM QUALIFIER   E               o  To show the forms available on a local system, enter '                  this DCL command line:   ,                  $ SHOW QUEUE/FORM  <Return>  B               o  To show the forms available on the DQS client and'                  server systems, enter:r  9                  $ QSHOW /QUEUE=queue-name /FORM <Return>                                             H                                     Viewing the Status of Print Jobs 3-5 e                     /FORM EXAMPLE@            In this example, CQ_EUROPE is used as the queue-name:  ,      $ QSHOW /QUEUE=CQ_EUROPE /FORM <Return>  -            You see output like the following:e        Remote node CHERRY::m>      Form name                            Number   Description>      ---------                            ------   -----------K      A4_12 (stock=PLAIN_PAPER)              1129   A4 12-Pitch with margins ?      DCPS$DEFAULT (stock=DEFAULT)           1115   DCPS defaultt        Local node APPLE::u>      Form name                            Number   Description>      ---------                            ------   -----------K      A4_12 (stock=PLAIN_PAPER)              1129   A4 12-Pitch with marginss?      DCPS$DEFAULT (stock=DEFAULT)           1115   DCPS default_I      DEFAULT                                   0   System-defined defaultu>      KPS$DEFAULT (stock=DEFAULT)            1183   KPS defaultH      LANDSCAPE (stock=DEFAULT)                10   132 by 66 (landscape)D      LASERWRITER (stock=DEFAULT)              30   APPLE LASERWRITER8      LCG01$FORM (stock=DEFAULT)              455   LCG01F      LN01S (stock=DEFAULT)                    60   64000 by 66 (LN0S )E      LPS$$FORM                              1105   PostScript Default_G      LTR_10 (stock=PLAIN_PAPER)             1124   10-Pitch, no margins H      LTR_12 (stock=PLAIN_PAPER)             1127   12-Pitch with marginsG      PORTRAIT (stock=DEFAULT)                 20    80 by 60 (portrait) C      PSBLASER (stock=DEFAULT)                 47   postscript laser I      PS_PLAIN (stock=PLAIN_PAPER)           1132   PostScript (Macintosh)l?      WPSPLUS (stock=DEFAULT)                1101   WPS-PLUS/VMSs      $  @            The QSHOW command lists the forms mounted on both theB            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                H         ________________________________________________________________  *         Understanding QSHOW Error Messages               QSHOW ERROR MESSAGESG               The DQS QSHOW command uses the same error messages as the H               DCL SHOW QUEUE command. In addition, the QSHOW command hasF               its own messages for handling problems unique to the DQS               software.            SERVER UNREACHABLE>               For example, if the server node is not currentlyH               reachable, the DQS software cannot check the status of theF               remote queue. You receive an explanation of the problem,!               like the following:   "         $ QSHOW CQ_EUROPE <Return>  ?         ***** Remote queue CHERRY::Q_PARIS not accessible ***** I             %SYSTEM-F-UNREACHABLE, remote node is not currently reachable   I         ==============================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 QUEUEH               Another possible error is that the remote queue is definedH               incorrectly. DQS software displays the following messages:  "         $ QSHOW CQ_EUROPE <Return>/         %DQS-W-MSG_REMOTE, Remote system error:n@         -DQS-F-BADQUE, Specified queue not valid for DQS access.  I         ==============================to be transferred================== =         Server queue CQ_EUROPE, stopped, mounted form DEFAULT H          Remote system error:  Specified queue not valid for DQS access.  <           Jobname         Username     Entry  Blocks  Status<           -------         --------     -----  ------  ------=           Q2-FINANCIALS   JONES         1467       1  Pendinga  H                                     Viewing the Status of Print Jobs 3-7                 E            In this case, either the system manager on the server node-B            must redefine the remote queue or the system manager onD            the client node must redirect the client queue to a valid            remote queue.          FOR MORE INFORMATIONn?            Refer to Appendix A for a complete list of messages.s                                                                          )      3-8 Viewing the Status of Print Jobs                        H                                                                        4H         ________________________________________________________________  H                                         Deleting Print Jobs From a Queue                 ABOUT THIS CHAPTER               This chapter:f  D               o  Compares the DQS QDELETE/ENTRY command with the DCL%                  DELETE/ENTRY command   F               o  Describes how to delete a print job using the QDELETE                  /ENTRY commande  8               o  Lists some QDELETE/ENTRY error messages                                                H                                     Deleting Print Jobs From a Queue 4-1               E      ________________________________________________________________         The QDELETE/ENTRY Command      E      COMPARISON_WITH_DCL_COMMAND_____________________________________ E            This_command_._._.____Enables_you_to_._._.________________   A            DCL DELETE/ENTRY      Delete a job from a local queue.   B            DQS QDELETE/ENTRY     Delete either locally or remotelyE            ______________________queued_print_jobs.__________________   ?            The QDELETE/ENTRY command functions exactly like theiE            DELETE/ENTRY command. (These commands do not delete files; E            they only remove jobs from a print queue.) You can use the D            DQS QDELETE/ENTRY command instead of the DCL DELETE/ENTRY+            command for all your print jobs.d                                                      )      4-2 Deleting Print Jobs From a Queuei r  _          H         ________________________________________________________________           Deleting a Print Job               YOU NEED TO KNOW3               To delete a print job, you must know:e  H               o  The name of the queue from which you want to delete the                  job  4               o  The job's entry number in the queue  D               The PRINT command displays this information by default>               when you queue a file for printing. You can alsoE               obtain this information by using the QSHOW command (seeo               Chapter 3).            EXAMPLEmC               For example, if you queued the file TRIP_REPORT.PS to$E               client queue CQ_EUROPE to print on node CHERRY, and theuB               job is entry 1024, delete the print job by entering:  5               $ QDELETE/ENTRY=1024 CQ_EUROPE <Return>C  H               The DQS software removes the job from the client queue. IfF               the job has already transferred to the remote queue, theA               DQS software removes the job from the remote queue.            /NOTIFY QUALIFIERdE               If you specify the /NOTIFY qualifier when you queue the F               job for printing, the DQS software notifies you when the               job is deleted.a  <               $ QDELETE/ENTRY=341 CQ_EUROPE /NOTIFY <Return>H               Print job TRIP_REPORT (queue CQ_EUROPE, entry 341) deleted                  H                                     Deleting Print Jobs From a Queue 4-3 o  n          E      ________________________________________________________________i  )      Understanding QDELETE Error Messages             QDELETE ERROR MESSAGES B            The DQS QDELETE command uses the same error messages asC            the DCL DELETE command. In addition, the QDELETE commandiC            has its own messages for handling problems unique to ther            DQS software.        SERVER UNREACHABLEiE            If the server node is not currently reachable, the QDELETEaD            /ENTRY command fails and you receive an explanation, like            the following:   2            $ QDELETE/ENTRY=1067 CQ_EUROPE <Return>/            %DQS-I-NOJOBDELETED, No jobs deletede<            %DQS-I-INACCESSIBLE, Remote queue CHERRY::Q_PARIS                is inaccessible        INVALID REMOTE QUEUE D            If you use the QDELETE/ENTRY command to delete a job fromD            a queue on a remote system that is not defined as a validD            DQS remote queue, DQS software displays messages like the            following:m  2            $ QDELETE/ENTRY=1194 CQ_CANADA <Return>2            %DQS-W-MSG_REMOTE, Remote system error:C            -DQS-F-BADQUE, Specified queue not valid for DQS access.   E            In this case, either the system manager on the server node B            must redefine the remote queue or the system manager onD            the client node must redirect the client queue to a valid            remote queue.        FOR MORE INFORMATIONt?            Refer to Appendix A for a complete list of messages.d              )      4-4 Deleting Print Jobs From a Queueh P  M                  H                                                                        5H         ________________________________________________________________  H                                   Modifying the Characteristics of a Job                 ABOUT THIS CHAPTER               This chapter:   E               o  Compares the DQS QSET/ENTRY command with the DCL SET                   /ENTRY command_  C               o  Describes how to modify a print job using the QSET                   /ENTRY command   C               o  Describes the DQS command qualifiers with modified                   behavior   /               o  Lists some QSET error messagesD                                          H                               Modifying the Characteristics of a Job 5-1               E      ________________________________________________________________         The QSET/ENTRY Commandm      E      COMPARISON_WITH_DCL_COMMAND_____________________________________             ThispE            command_._._.____Enables_you_to_._._._____________________   C            DCL SET/ENTRY    Change the current status or attributessD                             of a job that is not currently executing'                             in a queue.d  A            DQS QSET/ENTRY   Changes the current status for either_E                             locally or remotely queued print jobs not.E            _________________executing_in_a_queue.____________________t  C            You can use the DQS QSET/ENTRY command for modifying all B            your print jobs. You must specify a queue name with the            QSET/ENTRY command.                                                  /      5-2 Modifying the Characteristics of a Jobs               H         ________________________________________________________________           Modifying a Print Jobh               YOU NEED TO KNOWB               Before you can modify a print job, you need to know:  H               o  The name of the queue that contains the job you want to                  modify   5               o  The job's entry number in that queue   H               The DQS PRINT command displays this information by defaultE               when you queue a file for printing. You can also obtainOG               this information by using the QSHOW command (described inw               Chapter 3).            QSET/ENTRY EXAMPLEC               For example, you queued the file CHANGES.PS to client G               queue CQ_EUROPE to print on node CHERRY and requested twon!               copies, as follows:d  B               $ PRINT CHANGES.PS/QUEUE=CQ_EUROPE/COPIES=2 <Return>@               Job CHANGES (queue CQ_EUROPE, entry 1324), pending  E               Now you change your mind and want three copies. You can )               modify the job by entering:   ;               $ QSET/ENTRY=1324 CQ_EUROPE/COPIES=3 <Return>   G               The DQS software modifies the job in the client queue. IfmF               the job already transferred to the remote queue, the DQSE               software modifies the job in the remote queue. However, D               DQS software cannot modify a job that is moving from aF               client queue to a remote queue or a job that is actually               printing.g                H                               Modifying the Characteristics of a Job 5-3    =          E      ________________________________________________________________   "      Using QSET Command Qualifiers            QSET QUALIFIER DIFFERENCES C            Most of the qualifiers to the QSET/ENTRY command act the C            same as they do with the standard DCL SET/ENTRY command. B            Those qualifiers that have modified functions when usedB            with the QSET/ENTRY command are described in Table 5-1.  :      Table 5-1 QSET/ENTRY Command Qualifiers That FunctionE      __________Differently_with_DQS_Printing_________________________   #                    Function Without E      Qualifier_____DQS_________________Function_With_DQS_____________   B      /AFTER=time   Prints job after    Transfers job to the server?                    specified time.     after specified time. If B                                        already transferred, prints@                                        job after specified time.  C      /FORM=type    Uses form type.     Uses form type; form name or E                                        number must be defined on bothn9                                        client and server.i  ?      /HEADER       Specifies whether   Specifies whether headernA                    header page is      page is printed with file.F@                    printed with file.  Page displays server node=                                        and device in the filenB                                        specification; file version9                                        number may differ.o  ?      /HOLD         Holds job until     Does not transfer job top@                    released (by SET    server until released. IfD                    /ENTRY/RELEASE      already transferred, does notD                    command).           print until released (by QSET?                                        /ENTRY/RELEASE command).   E                                              (continued on next page)           /      5-4 Modifying the Characteristics of a JobR r               E         Table 5-1 (Cont.) QSET/ENTRY Command Qualifiers That Function H         __________________Differently_with_DQS_Printing_________________  &                       Function WithoutH         Qualifier_____DQS_________________Function_With_DQS_____________  F         /NODELETE     Cancels file        While job is still in clientE                       deletion for        queue, this qualifier workssE                       job queued with     correctly; after the job isEC                       /DELETE qualifier.  transferred to the remotedB                                           queue, command fails and;                                           returns an error.   G         /PARAMETERS   Passes from 1       Passes from 1 to 7 parameters B         =(parame-     to 8 optional       to job. The DQS softwareB         ter[,...])    parameters to job.  reserves parameter 8 forE                                           its own use. If you specify H                                           parameter 8, the command fails?                                           and returns an error.L  E         /PRIORITY=n   Specifies priority  Specifies priority of print B                       of print job.       job. Priority limits areD                                           configured on server nodesG                                           for all client users. You can E                                           request any print priority, H                                           but the server queues your jobG                                           with no more than the allowed ;                                           maximum priority.:  @         /REQUEUE=     Queues job to       If the job has not yetC         queue-        another printer     transferred to the serverrE         name[:]       queue.              node, you can requeue it to E                                           any other queue. If the job_F                                           already transferred (but hasG                                           not printed), you can requeueuD                                           it to another queue on theH         __________________________________same_server.__________________                H                               Modifying the Characteristics of a Job 5-5 U             E      ________________________________________________________________   &      Understanding QSET Error Messages            QSET ERROR MESSAGESD            If the QSET/ENTRY command fails, the job's specifications>            are unchanged and the DQS software returns an error-            message. Some common messages are:k  @            o  If the server node is not currently reachable, the@               QSET/ENTRY command fails and returns the following               messages:P  *               %DQS-I-NOJOBSET, no jobs setE               %DQS-I-INACCESSIBLE, remote queue queue is inaccessibleN  E            o  If you specify a queue that points to an invalid remoteF@               queue, the command fails and returns the following               messages:   5               %DQS-W-MSG_REMOTE, remote system error:PG               -DQS-F-BADQUEUE, specified queue not valid for DQS access)  C               The server node system manager must modify the remotem               queue.  :            o  If you try to modify a job while it is beingD               transferred from the client queue to the remote queue,5               the request fails with an error status:g                 %JBC-E-EXECUTING  >            o  If you specify a form that is not defined on theE               client, the command fails and returns the error status:                  %JBC-E-NOSUCHFORM                 /      5-6 Modifying the Characteristics of a Job                  C               o  If you attempt to modify the status of a print job H                  with the QSET /ENTRY/NODELETE command after the job hasG                  transferred to the remote queue, the command fails and 0                  returns the following messages:  8                  %DQS-W-MSG_REMOTE, remote system error:I                  -DQS-E-NODELETE, /NODELETE is allowed only on local jobs -                  %DQS-I-NOJOBSET, no jobs setE  G               o  If you use the /PARAMETERS qualifier and specify eight C                  parameters for a job that already transferred, thelB                  command fails and returns the following messages:  /         %DQS-W-MSG-REMOTE, remote system error:OL         -DQS-F-P8RESERVED, parameter 8 is reserved for DQS on remote systems$         %DQS-I-NOJOBSET, no jobs set           FOR MORE INFORMATIONB               Refer to Appendix A for a complete list of messages.                                                    H                               Modifying the Characteristics of a Job 5-7    s                  H                                                                        6H         ________________________________________________________________  H                                         Spooling Files to a Client Queue                 SPOOLING FILESA               The OpenVMS operating system allows you to assign a=F               logical device in a source program to a physical device./               To spool files to a client queue:e  G               1. The system manager creates a LAT port and sets the LAT 6                  port spooled to the DQS client queue.  D               2. You specify the LAT port in a source program as the!                  physical device.   G               DQS software places the print output in a temporary file, E               enters the file in the client queue, then transfers the 5               file to the corresponding remote queue.a           EXAMPLE F               In a FORTRAN program, the statement PRINT directs outputD               to the terminal unless otherwise directed to a logicalG               device. If the LAT port is spooled to a client queue, you <               can direct program output to a remote printer.  G               For example, if the LAT port LTA999: is spooled to client H               queue CQ_USA (that is, the system manager used the commandC               line SET DEVICE LTA999/SPOOLED=CQ_USA), you can spool 7               output to the remote printer by entering:   1               $ DEFINE FOR$PRINT LTA999: <Return>a  B               When you execute your FORTRAN program, its output is=               spooled from LTA999 to the client queue CQ_USA.         H                                     Spooling Files to a Client Queue 6-1 o  n                  COLON REQUIRED D            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 QueueT C  a                  H                                                                  Part IIH         ________________________________________________________________  H                                                   System Manager's Guide        E               This part describes how to configure and manage the DQS_B               software on OpenVMS AXP and OpenVMS VAX systems. TheC               System Manager's Guide is intended for the network oro               system manager.e e  l                  H                                                                        7H         ________________________________________________________________  H                        Understanding the DEC Distributed Queuing Service                 ABOUT THIS CHAPTER%               This chapter describes:   A               o  An overview of the design of the DEC Distributed B                  Queuing Service for OpenVMS Systems (DQS) product  :               o  The primary functions of the DQS software  F               o  The functions of the DQS commands: PRINT, QSHOW, QSET*                  /ENTRY, and QDELETE/ENTRY  9               o  The functions of DQS software componentss  >               o  The DQS notification service and how it works  "               o  The DQS symbionts  7               o  The use of forms with the DQS softwareo  '               o  The DQS server accountM  *               o  Some configuration issues  /               o  Types of errors that may occurq  =               o  How the DQS software handles security issueso  6               o  The processes created by the software  6               o  How the DQS software supports devices  9               o  The use of a batch job with DQS softwaree    H                    Understanding the DEC Distributed Queuing Service 7-1               E      ________________________________________________________________U  !      Overview of the DQS Softwarey            WHAT IS DQS SOFTWARE?C            The standard OpenVMS queue system enables you to use theoA            OpenVMS PRINT command to print files on output devicesT9            that are connected to your local OpenVMS node.   >            The DQS software is an OpenVMS layered product thatE            extends the standard OpenVMS queue system to a distributede>            system environment. The DQS software enables you toA            use the OpenVMS PRINT command to print files on outputrE            devices that are connected to remote OpenVMS nodes in yourEA            network. You can also delete, and obtain or change theT)            status of your DQS print jobs.i        WHY USE DQS SOFTWARE?>            Installing and configuring the DQS software in your            network can provide:   E            o  Printing services to workstation users (and others) who +               do not have attached printersn  A            o  The sharing of expensive or unique printing devicesE8               among the users in your distributed system  >            o  The ability for your users to distribute reports@               efficiently to remote sites within your company orC               organization, because DQS software works in both widel*               area and local area networks  *      UNDERSTANDING DQS CLIENTS AND SERVERSE            The DQS software is based on a client/server design, which B            consists of two cooperating software components (client            and server)._  ?            The following terms are associated with DQS servers:u  E            Server      Nodes in your network that have connections totB            nodes       output devices (for example, printers) thatA                        you want to make available to the users oniB                        other nodes (client nodes) in your network.  :      7-2 Understanding the DEC Distributed Queuing Service t  i              C               Remote      DQS queue on the server node that directs G               queue       print jobs from client nodes to the connected E                           printer. (Standard OpenVMS print queues are_C                           queues that direct print jobs to printers 7                           connected to the local node.)T  @               Server      DQS software that you must install and4               software    configure on server nodes.  B               The following terms are associated with DQS clients:  F               Client      Nodes whose users are able to print files onG               nodes       printing devices that are connected to remoteh+                           DQS server nodes.r  C               Client      DQS queue on the client node that directs F               queue       print jobs to the associated remote queue on.                           the DQS server node.  @               Client      DQS software that you must install and4               software    configure on client nodes.  A               A node can be only a client, or both a client and a_F               server. Each client can be configured to send print jobsE               to any server. Similarly, each server can be configuredbB               to accept print jobs from any client. Chapters 8 andC               9 describe the procedures for configuring servers ande$               clients, respectively.  '         USING DQS SOFTWARE IN A CLUSTER H               In a VMScluster environment, a server is potentially everyC               node in a cluster. Similarly, a client is potentially C               every node in a cluster. Therefore, if a user logs on F               to different cluster members at different times, the DQS+               software is always available.o  ?               To use the DQS software in a cluster environment:_  *               1. Install the DQS software.  C               2. License each node in the cluster to be a DQS node.o  F               3. Invoke DQS$STARTUP.COM from each cluster member node.  A               While DQS software can be used on selected nodes ofm@               a cluster, doing so does not take advantage of the'               flexibility of a cluster.p  H                    Understanding the DEC Distributed Queuing Service 7-3 i               *      NETWORK REQUIREMENTS FOR DQS SOFTWARE>            DQS software uses the DECnet network to communicateD            between clients and servers and to perform its functions.%            The DQS software requires:   @            o  The client and server to communicate for the print4               request to be processed by the server.  C               However, users can queue print jobs at any time, evenHC               if the client system is not in communication with the E               desired server system. Similarly, a server can continuetB               to process print jobs, even if the client from whichC               the job was received is not in communication with then               server.   E            o  A connection between a client and a server remains long C               enough to transfer the complete file (or files) to be                printed.  E               If the connection is broken before the entire print jobtE               is transferred to the server, the DQS software attempts C               to transfer the entire print job after the connectiont               is reestablished.   B            o  Communication must exists between the client and theC               desired server to examine a remote queue or to deleteI0               or modify a job in a remote queue.  A            o  A connection must be established from the server tot@               the user's client system for a user to receive jobD               notification messages (described in the section titled,               The DQS Notification Service).  "      PHASE IV AND PHASE V NETWORKSC            The DQS software can be used in both DECnet Phase IV and_B            DECnet/OSI Phase V networks. DQS software also operatesC            in properly configured networks that use both networking=E            products. DECnet/OSI systems can be set up to use synonyms 0            to communicate with Phase IV systems.  ;            DECnet Phase IV networks limit node names to sixn@            characters. DECnet/OSI Phase V networks allow the useA            of an expanded node name (full names). DQS clients andaB            servers can handle node names with up to 150 characters)            with no embedded blank spaces.   :      7-4 Understanding the DEC Distributed Queuing Service r  S          H         ________________________________________________________________  -         Primary Functions of the DQS SoftwareP               OVERVIEWF               The major functions of the DQS software are initiated byG               the PRINT, QSHOW, QSET/ENTRY, and QDELETE/ENTRY commands.                 DQS software uses:  C               o  The standard OpenVMS PRINT command to initiate DQSr                  print requestsa  G               o  Modified versions of the OpenVMS SHOW, SET, and DELETE H                  commands to show, modify, and delete DQS print requests           PRIMARY FUNCTIONST?               Figure 7-1 shows the primary functions of the DQS                software.            THE PROCESS(G               The stages shown in Figure 7-1 are summarized as follows:s  H               __________________________________________________________H               StageDescription__________________________________________  A                 1  A user enters a PRINT command on a client node 1                    specifying a DQS client queue.W  F                 2  DQS software copies the file to be printed from theH                    client queue to the server node, and enters the print9                    job in the remote queue on the server.   B                 3  The remote queue sends the file to the server'sH               _____output_device_and_the_file_is_printed._______________           SUMMARY OF DQS COMMANDS A               Most of the standard OpenVMS command qualifiers areMF               fully supported for the DQS versions of the PRINT, SHOW,D               SET, and DELETE commands. Table 7-1 summarizes the DQS               commands..        H                    Understanding the DEC Distributed Queuing Service 7-5                 E            Table_7-1_Summary_of_DQS_Commands_________________________   E            Command_______Function____________________________________   E            PRINT         The OpenVMS PRINT command places a print job B                          in a client queue on a client system. TheD                          DQS symbiont transfers the print request toB                          the associated server system, where it isB                          placed in the associated remote queue andC                          directed to an output device for printing.r  D            QSHOW         Displays the status of a DQS print job thatA                          is in either a client or a remote queue.:  E            QDELETE       Prevents a print job from being processed or 3            /ENTRY        terminates its processing.t  E            QSET/ENTRY    Modifies the parameters of a print job afteruB                          the job has been queued but before it hasE            ______________been_processed._____________________________r        FOR MORE INFORMATION C            Refer to Part I for more information on the DQS commands              and their qualifiers.                                          :      7-6 Understanding the DEC Distributed Queuing Service               H         ________________________________________________________________  %         Functions of the DQS Commands_               PRINT COMMAND FUNCTIONS G               Figure 7-2 shows the functions of the PRINT command usingS               a DQS queue.           THE PROCESSo?               The stages in the PRINT process are summarized as                follows:  H               __________________________________________________________H               StageDescription__________________________________________  C                1   A user issues a PRINT command specifying the DQSS'                    client queue CQ_USA.D  G                2   The standard OpenVMS DCL command language intepretery0                    interprets the PRINT command.  H                3   The OpenVMS job controller in the client queue on theE                    client node queues the print job to the DQS clientr                    queue.B  D                4   The client symbiont, DQS$SMB, takes the print jobE                    from the client queue and transfers the job to the.9                    DQS$SERVER process on the server node.i  E                5   The DQS$SERVER process receives the print job from H                    the client symbiont, writes the file to a disk on theF                    server node, and places the print job in the remote#                    queue Q_CHICAGO.o  F                6   The print symbiont on the server retrieves the fileG                    when the file is ready to be printed and directs the H               _____file_to_the_output_device_for_printing.______________  A               After the printer prints the file, the DQS$NOTIFIERaF               process on a server deletes the file from the DQS serverF               account (see the section titled The DQS Server Account).D               If a user requests notification of job completion, theH               DQS$NOTIFIER attempts to notify the user before it deletes6               the files associated with the print job.  H                    Understanding the DEC Distributed Queuing Service 7-7 m  r                      OTHER DQS COMMANDSlC            Figure 7-3 shows the functions of the QSHOW, QSET/ENTRY, &            and QDELETE/ENTRY commands.        THE PROCESSE            The stages in the DQS QSHOW, QSET/ENTRY, and QDELETE/ENTRY 7            command processes are summarized as follows.F  E            __________________________________________________________eE            StageDescription__________________________________________   E             1   The DQS command interpreter DQS$CLIENT interprets the C                 command and transfers the request to the DQS$SERVER +                 process on the server node._  C             2   The DQS$SERVER process receives the command request B                 from the client node and passes the request to the'                 OpenVMS job controller.t  ?             3   The OpenVMS job controller performs the command B                 request and returns the appropriate information to'                 the DQS$SERVER process.T  A             4   DQS$SERVER then transfers this information to the 6                 DQS$CLIENT process on the client node.  B             5   DQS$CLIENT formats the information and directs theE            _____command_output_to_the_user_who_initiated_the_command.u  !      COMMANDS WITH OPENVMS QUEUES E            The DQS QSHOW, QSET/ENTRY, and QDELETE/ENTRY commands also A            work on standard OpenVMS print queues. For an entry in C            a standard OpenVMS queue, QSHOW, QSET/ENTRY, and QDELETE 6            /ENTRY do not send information to a server.                  :      7-8 Understanding the DEC Distributed Queuing Service               H         ________________________________________________________________  ,         Functions of DQS Software Components               SUMMARY OF COMPONENTShG               Table 7-2 summarizes the major software components of the 9               DQS software and describes their functions.t  H         Table_7-2_Functions_of_the_DQS_Software_Components______________  H         Component___Name__________Description___________________________  H         DQS         DQS$CLIENT    The DQS command interpreter is locatedC         command                   on clients and interprets the DQSQF         inter-                    QSHOW, QSET/ENTRY, and QDELETE/ENTRY+         preter                    commands.t  G                                   The standard OpenVMS command language B                                   interpreter interprets the PRINTE                                   command. The standard OpenVMS batch D                                   /print system enters the print job6                                   into a client queue.  C         DQS         DQS$SMB       The DQS symbiont runs on clients. E         symbiont                  Each client queue is serviced by aniG                                   OpenVMS process that runs the DQS$SMBMG                                   image. The DQS symbiont process takesiD                                   print jobs from a client queue andH                                   transfers the jobs to a process on the4                                   associated server.  H                                                 (continued on next page)                        H                    Understanding the DEC Distributed Queuing Service 7-9 r  s            E      Table_7-2_(Cont.)_Functions_of_the_DQS_Software_Components______   E      Component___Name__________Description___________________________   @      DQS         DQS$SERVER    The DQS server program is locatedA      server                    on servers and receives print jobs ?      program                   from the DQS symbiont DQS$SMB onsE                                clients. The server program writes theeB                                file(s) to be printed to the serverC                                disk and places the print request in ;                                the associated remote queue.t  D                                DQS$SERVER also processes QSHOW, QSET@                                /ENTRY, and QDELETE/ENTRY command>                                requests received from clients.  E                                The DQS server process is also located C                                on clients to receive job completiontE                                messages from the DQS$NOTIFIER process_A                                on servers. DQS$SERVER on a clienteA                                broadcasts job completion messages D                                sent by the DQS$NOTIFIER to each userC                                who owns a particular print job that -                                has completed.e  E                                              (continued on next page)                                       ;      7-10 Understanding the DEC Distributed Queuing ServiceT D  s            H         Table_7-2_(Cont.)_Functions_of_the_DQS_Software_Components______  H         Component___Name__________Description___________________________  A         NotificationDQS$NOTIFIER  The DQS notification program is E         program                   located on servers and periodically?D                                   scans DQS print jobs in the remoteF                                   queues to determine which print jobsC                                   have completed. After a print jobiE                                   completes, DQS$NOTIFIER informs theiG                                   DQS$SERVER process on the client from C                                   which the print job originated if 7                                   /NOTIFY is specified.   H         Modified    DQS$PRTSMB    The DQS print symbiont, DQS$PRTSMB, isF         OpenVMS                   located on servers and is a modifiedG         print                     version of the standard OpenVMS printcD         symbiont                  symbiont, PRTSMB. The modified DQSF                                   symbiont should replace the standardH                                   OpenVMS print symbiont so that client-D                                   specific information is printed onD                                   the flag, burst, and trailer pagesB                                   of the print output. See The DQSC                                   Symbionts for more information oniH         __________________________the_DQS_symbiont._____________________                                        H                   Understanding the DEC Distributed Queuing Service 7-11               E      ________________________________________________________________u  !      The DQS Notification Servicer            SENDING MESSAGES TO USERSC            If you specify /NOTIFY qualifier with the PRINT command, A            the notification service sends job completion messages *            when print jobs have completed.  :            DQS software returns two notification messages:  D            o  The first when the user's print job has transferred to               the server.o  A            o  The second after the job has printed on the server.   $      DELETING JOBS FROM REMOTE QUEUEE            The notification process on the server node, DQS$NOTIFIER, B            also has the task of deleting completed print jobs fromC            the remote queue. The DQS$SERVER program submits all DQSlB            print jobs with the /RETAIN=ALWAYS qualifier. DQS printC            jobs remain in DQS queues after the job is printed until )            the DQS$NOTIFIER deletes them.   =            If a user requests notification of job completion,sE            DQS$NOTIFIER attempts to notify the user before it deletesl:            the files associated with the user's print job.        HOW IT WORKSvC            Figure 7-4 shows how the DQS notification service works.O        THE NOTIFICATION PROCESS A            The DQS notification process shown in Figure 7-4 works             like this:e  E            __________________________________________________________sE            StageDescription__________________________________________m  ;             1   The DQS notification process on the server,l@                 DQS$NOTIFIER, periodically scans DQS jobs in the@                 remote queues to determine which print jobs have                 completed.    ;      7-12 Understanding the DEC Distributed Queuing Servicev    $          H               __________________________________________________________H               StageDescription__________________________________________  F                2   When a print job completes, the DQS$NOTIFIER checksG                    if the user specified /NOTIFY and sends a completion H                    message to the DQS$SERVER process on the client node.  @                3   The DQS$SERVER on the client receives the jobG                    completion message and a message is sent to the userrH               _____who_owns_the_job_that_has_completed._________________             FOR MORE INFORMATIONF               For more information on using the /NOTIFY qualifier withG               the PRINT command, refer to Chapter 2 and the OpenVMS DCLc               Dictionary.                                                             H                   Understanding the DEC Distributed Queuing Service 7-13               E      ________________________________________________________________v        The DQS Symbionts      
      OVERVIEWi>            The DQS software contains two symbionts DQS$SMB and;            DQS$PRTSMB, which are described in this section.         DQS$SMBA            DQS$SMB runs on client systems. The symbiont takes DQS B            print jobs from client queues and transfers them to the"            associated server node.        DQS$PRTSMBeD            DQS software provides its own print symbiont, DQS$PRTSMB,D            which is a modified version of the standard OpenVMS printA            symbiont, PRTSMB. (The DQS$PRTSMB symbiont is upwardly C            compatible with the OpenVMS PRTSMB symbiont.) DQS$PRTSMBhB            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 DQSr@            print output. With the DQS print symbiont controllingB            each remote queue on a server, the users of that serverB            see the same job information on their print output thatD            they saw displayed when they entered the print request on            the client node.s  A            If the standard OpenVMS print symbiont does not handlemB            banner pages to your satififaction, replace it with theA            DQS print symbiont, DQS$PRTSMB. If DQS$PRTSMB does not C            control a remote queue on a server, the standard OpenVMS C            print symbiont prints the job number of the print job in C            the remote queue, as well as the time that the print jobC<            was queued on the server on the DQS print output.  B            DQS$PRTSMB can only replace the OpenVMS print symbiont.                ;      7-14 Understanding the DEC Distributed Queuing Service     o                     FOR MORE INFORMATIONF               For a description of the procedures for enabling the DQSE               print symbiont to control remote queues, see Chapter 8.d  C               Refer to Appendix D for information on how DQS$PRTSMBe)               relates to other symbionts.o                                                                              H                   Understanding the DEC Distributed Queuing Service 7-15    u          E      ________________________________________________________________   .      Defining Forms on Client and Server Nodes      
      OVERVIEWiB            You must define all forms that you intend to specify onE            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 (seeQ            Chapter 9).        NO FORM ON SERVERC            If you attempt to print using a form that is not defineduA            on the associated server, the client queue accepts thebE            job and the system prompt returns ($). However, your printu@            job remains in the client queue with the error statusC            %DQS-F-NOSUCHFORM. A QSHOW command specifying the clientCD            queue where you queued the job shows the retained job and            the error message.p        DIFFERENT VALUESsA            Because DQS software transfers only a form's name from C            a client to its server, a form may have different values B            on different DQS systems. When the same form is definedA            differently throughout your network, the server's form_-            definition is used to print a job.n  C            Digital strongly recommends that you give forms with theTB            same name the same definitions throughout your network.C            However, you may want to have different form definitions A            because it enables users on client systems to maintain E            their local form definitions to use when printing locally.p        FOR MORE INFORMATIONeD            Chapter 9 describes the procedures for synchronizing form            definitions.Q                ;      7-16 Understanding the DEC Distributed Queuing Service                H         ________________________________________________________________           The DQS Server Account               OVERVIEWC               The DQS installation procedure creates a DQS account,aF               DQS$SERVER, and its associated directory [DQS$SERVER] on.               all DQS client and server nodes.           ON A SERVER_E               A DQS server process is run from the DQS$SERVER accountrG               when a connection request is received from a client node.rE               The directory associated with this account [DQS$SERVER]tE               stores files received from client nodes until the files_E               are printed on the server node's output device. After a H               print job completes, the files associated with the job are8               deleted from the server account directory.           ON A CLIENT E               The DQS$SERVER account is located on clients to receive C               job completion messages from the DQS$NOTIFIER process B               on the server. DQS$SERVER on a client broadcasts jobC               completion messages to each user who owns a completed_C               print job, if the user specified /NOTIFY on the PRINT                command.                                      H                   Understanding the DEC Distributed Queuing Service 7-17    i          E      ________________________________________________________________t  4      The Significance of Parameter 8 in DQS Printing      
      OVERVIEWoC            The OpenVMS PRINT command allows you to pass from one toeC            eight optional parameters with a print job. DQS softwareoA            uses parameter 8 to store print job information. Place E            your print parameter values in parameter 1 to parameter 7.S        USE IN DQS PRINTING?            DQS software uses the information in parameter 8 to:e  '            o  Validate a user's requests               o  Delete a print job               o  Modify a print job  :            The information stored in parameter 8 includes:              o  Client job number   A            o  Job owner; on OpenVMS systems this usually consists                of:l  !               -  Client node name_  *               -  User's name on the client  3            o  Time the job was queued on the clientc        ERROR MESSAGES B            DQS software issues an error (%DQS-E-P8RESERVED) if youB            attempt to specify parameter 8 with either a PRINT or a            QSET/ENTRY command.        FOR MORE INFORMATIONR&            For more information about:  A            o  The %DQS-E-P8RESERVED error message, see Appendix B   B            o  The format of the information stored in parameter 8,               see Appendix D  A            o  The use of the /PARAMETERS qualifier, see Chapter 2Q  ;      7-18 Understanding the DEC Distributed Queuing Service  T  P          H         ________________________________________________________________            Configuring DQS Software      &         CLIENT AND SERVER INSTALLATIONB               When you run the DQS installation procedure, you areD               asked whether you want to install DQS server software.D               You are given this option because not all DQS nodes inF               your network require server software (for example, thoseD               nodes without connections to output devices). However,G               most or all nodes in your network require client softwaresD               so that their users can have access to remote printingG               resources. Therefore, client software is always installed ,               when you install DQS software.  '         CLIENT AND SERVER CONFIGURATIONpH               A client must be configured to work with its correspondingC               servers (and vice versa) in order for DQS software to C               function. You can configure a server to serve as many H               clients as you want. Similarly, you can configure a clientH               to use the services of any number of servers. There are noG               restrictions on the number of DQS servers or clients thats+               you can have in your network.n  *         RESTRICTIONS TO DQS CONFIGURATIONSC               The DQS software is suitable for all OpenVMS nodes in @               DECnet networks. DQS software can be used in smallD               networks consisting of two nodes and in large networksG               consisting of many nodes. DQS software operates in either 8               local area networks or wide area networks.  H               DQS software is limited only by the ability of DQS serversC               to accept and maintain a large number of simultaneousSA               network connections (that is, logical links) to DQS_H               clients. The maximum number of logical links that a serverF               can support is a parameter that you can define using theF               Network Control Program (NCP) on DECnet Phase IV systemsH               and the Network Control Language (NCL) on DECnet/OSI PhaseF               V systems. The value of this parameter depends upon manyC               factors, such as the server's processor speed and itse                typical work load.      H                   Understanding the DEC Distributed Queuing Service 7-19                 C            Each logical link from a client creates one process on aiB            server. A server must be configured to allow for enoughD            processes. (See the section entitled Processes Created byE            DQS Software, which describes the processes created by thet5            DQS software on both clients and servers.)m  D            In addition to handling its other network applications, aC            server should be able to accept simultaneous connections @            from all clients that it serves. However, all clientsD            trying to access the server at the same time is unlikely.D            Any client that attempts to print on the server after theD            maximum number of logical links is reached, automaticallyB            attempts to reconnect to the server after a short wait.E            The QSHOW, QSET/ENTRY, and QDELETE/ENTRY command functions_6            do not attempt this automatic reconnection.                                                            ;      7-20 Understanding the DEC Distributed Queuing Service     f          H         ________________________________________________________________  "         Using Daisy-Chained Queues               PURPOSEtC               You can configure the DQS software in your network solF               that a client queue corresponds to a remote queue, whichE               in turn, corresponds to another remote queue on anothereH               server. This configuration is called daisy-chained queues.F               You can daisy-chain queues across as many servers as you               want.            BENEFITSA               Daisy-chained queues are useful when a printer on a D               server becomes temporarily unavailable. Users who wantD               to send jobs to the disabled server can still do so ifE               the server's system manager sets up the remote queue todD               redirect their print output to another server's outputD               device. No change is made to the user's client system,B               and the users may not even know that the printer was               unavailable.  A               Daisy-chained queues are also useful when a network C               link from a client to its server is only occasionally C               available. With daisy-chained queues you can effect aiF               "store and forward" function, where a job is transferredE               to a reachable, intermediate server that stores the job$4               until the desired server is reachable.           EXAMPLE E               Figure 7-5 depicts a daisy-chained queue configuration.            PROCESS B               The daisy-chain process shown in Figure 7-5 works as               follows:  H               __________________________________________________________H               StageDescription__________________________________________  @                1   A user enters a print job in the client queue0                    CQ_ILLINOIS on client node A.      H                   Understanding the DEC Distributed Queuing Service 7-21    o          E            __________________________________________________________ E            StageDescription__________________________________________   C             2   DQS software transfers the job to node B and enterst1                 it in the remote queue Q_CHICAGO.S  B             3   DQS software then transfers the job from node B toD                 node C, and enters it in the remote queue Q_PARIS on                 node C.   E            _4___The_job_is_printed_on_node_C's_printer.______________                                                                       ;      7-22 Understanding the DEC Distributed Queuing Service                           AVOIDING LOOPSB               Avoid creating a loop when configuring daisy-chainedF               queues. If you configure a daisy-chained queue to directC               a job back to the system where the job was originally G               queued, the job terminates on that system with the error,_               %DQS-E-LOOP.             FOR MORE INFORMATIONH               Refer to Part III for more information on the installation               of DQS software.  E               Chapters 8 and 9, respectively, describe the proceduresoG               for configuring servers and clients after installation ofs               the software.i  F               Chapter 8 describes the procedures for setting up daisy-               chained queues.a                                                      H                   Understanding the DEC Distributed Queuing Service 7-23    e          E      ________________________________________________________________r        DQS Error Conditionsu            ERROR DETECTIONB            When DQS software detects an error condition, the error@            is sent to the OpenVMS operator communication processC            (OPCOM). If an error is detected in a server process, it E            is also written to a NETSERVER.LOG log file on the server.D        TYPES OF ERRORSB            There are three basic types of errors that can occur in            DQS printing.  D            o  A print job fails because a network link to the serverD               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 serverS>               node after a five-minute wait (this value is not               changeable).  6            o  A print job cannot transfer to a server.  D               The DQS symbiont handles this type of error by keepingE               the print job in the client queue with the error status7A               "Retained on error." A QSHOW command specifying the C               client queue in question displays the specific reason_E               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.  E               This type of error occurs when a user attempts to print B               to an invalid remote queue or to a server node whoseA               name is unknown to the client node. A QSHOW command B               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 Servicen    c                     EXAMPLES?               Example 7-1 shows an error detected by the client H               symbiont, DQS$SMB. The error does not affect the operationD               of the symbiont but causes the job responsible for the@               error to terminate with error status. The affectedC               job remains in the client queue with the error status H               "Retained on error." In this case, you must either requeueF               or delete the print job. In Example 7-1, the client nodeH               has a form defined that is not defined on the server. ThisG               prevents the print job from transferring. A QSHOW commandiH               specifying the client queue where the job was queued showsE               the retained job and the specific reason for the error.R    >         Example 7-1 A DQS Error That Prevents a Print Job From                      Transferring           $ QSHOW QUEUE1 <Return>,  =         ** Remote queue - [ QUEUE1 => SYS$PRINT, on NODEB:: ]u,         Terminal queue SYS$PRINT, on NODEB::  U         ==============================to be transferred============================== =         Server queue QUEUE1, on NODEA::, mounted form DEFAULT   <           Jobname         Username     Entry  Blocks  Status<           -------         --------     -----  ------  ------F           JOB             PAUL          925       1  Retained on error+             %JBC-E-NOSUCHFORM, no such formn                                H                   Understanding the DEC Distributed Queuing Service 7-25 s  i            <            Example 7-2 shows an error detected by the clientC            symbiont, DQS$SMB, that caused the client queue to stop.sB            The DQS$STATUS_queue-name logical name is defined to beA            the error status. This action makes it easy to see theeB            reason for the error by issuing a QSHOW command for the@            client queue. In Example 7-2, the server node name isB            not known on the client. Therefore, the symbiont cannot?            process any jobs for that queue and stops the queue.t    	      NOTEoA            Remember to deassign the DQS$STATUS_queue-name logicalq+            name when you restart the queue.   ?            $ DEASSIGN/SYSTEM/USER DQS$STATUS_queue-name<Return>a                                                            ;      7-26 Understanding the DEC Distributed Queuing Service  e  a            9         Example 7-2 A DQS Error That Stops a Client Queue_           $ QSHOW QUEUE1 <Return>_  =         ***** Remote queue NODEB::QUEUE1 not accessible ***** 8             %SYSTEM-F-NOSUCHNODE, remote node is unknown  U         ==============================to be transferred==============================eF         Server queue QUEUE1, stopped, on NODEA::, mounted form DEFAULT7             remote system error: remote node is unknowna  <           Jobname         Username     Entry  Blocks  Status<           -------         --------     -----  ------  ------=           LOGIN           YOUNG          571       2  Pendinge           FOR MORE INFORMATIONG               Refer to Chapter 10 for guidelines on how to troubleshoot 9               error conditions that involve DQS software.                                                       H                   Understanding the DEC Distributed Queuing Service 7-27 j  a          E      ________________________________________________________________D  *      DQS Security Issues and Access Rights            RESTRICTING ACCESSr@            By default, all client nodes have access to a server.  B            You can restrict access to a server node only by client2            system, not by individual client users.        FOR MORE INFORMATIONjE            Chapter 8 describes the procedures for granting or denying %            client access to a server.i                                                              ;      7-28 Understanding the DEC Distributed Queuing Servicei n  e          H         ________________________________________________________________  )         Processes Created by DQS SoftwareN               ON A CLIENTtH               On a client node, every client queue that you create (thatH               is not a generic or logical queue) results in the creationE               of one process. Also, while a user is being notified of_E               print job completion, a process is temporarily created.            ON A SERVER G               For server nodes, every incoming connection from a client D               node results in the creation of one process. Also, theA               notification process on a server uses one permanent                process.                                                          H                   Understanding the DEC Distributed Queuing Service 7-29 i  t          E      ________________________________________________________________e  &      Devices Supported by DQS Software            SUPPORTED DEVICES?            DQS software does not run devices; rather, it placespE            print jobs in queues for processing. DQS software supportsm;            devices by placing jobs in queues, if the device   4            o  Is driven by an OpenVMS print symbiont  6            o  Does not use parameter 8 in job requests  C            DQS software does not support symbionts that require jobnB            information outside of that stored or maintained by the             OpenVMS queue system.                                                        ;      7-30 Understanding the DEC Distributed Queuing Service                H         ________________________________________________________________  #         Batch Jobs and DQS Printing_  A               DQS software supports the queuing of print jobs for8E               processing on remote nodes in your network. It does notm0               support the queuing of batch jobs.  E               Do not configure batch queues to be DQS printer queues. F               DQS software does not prevent you from configuring batchH               queues, but the security of the system decreases if you do               so.S                                                                    H                   Understanding the DEC Distributed Queuing Service 7-31 o  o                  H                                                                        8H         ________________________________________________________________  H                                    Configuring and Managing a DQS Server                 ABOUT THIS CHAPTERG               This chapter presents an overview of the management tasks B               required by a DQS server and describes how to do the               following:  G               o  Modify definitions of special logical names associated/$                  with the DQS server  )               o  Set up DQS remote queues:  F               o  Control DQS client access to servers and their remote                  queueso  A               o  Determine how DQS clients are accessing a serverD  C               o  Control the note on the banner page of a print job   6               o  Enable DQS status messages for queues  G               o  Enable the DQS print symbiont to control remote queues_  A               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  B               o  Move the server account directory to a new device  G               o  Configure server software for a VMScluster environmentf  -               o  Configure daisy-chain queuese  ?               The last section contains a summary of the servere               management tasks.   H                                Configuring and Managing a DQS Server 8-1 G  T          E      ________________________________________________________________   "      Overview of Server Management            MAIN TASKSeD            Configuring and managing a DQS server primarily involves:  9            o  Defining server system logical names in theo0               SYS$MANAGER:DQS$SYSTARTUP.COM file  ;               All site-specific definitions that affect thet>               behavior of the software belong in this file. If?               this file does not exist on your system, copy theOE               DQS$SYSTARTUP.TEMPLATE to DQS$SYSTARTUP.COM and edit itSE               to include the desired server logical name definitions.s  7            o  Setting up access to remote queues in the 4               SYS$MANAGER:DQS$SERVER_CONFIG.TXT file  4            The SYS$STARTUP:DQS$STARTUP.COM procedure  D            o  Invokes the SYS$MANAGER:DQS$SYSTARTUP.COM procedure to$               make changes permanent  E            o  Processes the SYS$MANAGER:DQS$SERVER_CONFIG.TXT file to C               set up DQS client node access to remote queues on DQS                server systems  3            Do not edit SYS$STARTUP:DQS$STARTUP.COM.         USING SYSMANmE            When directed to restart DQS software in a VMScluster, youa0            can use one of the following methods:  D            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               H         ________________________________________________________________  ,         Defining Server System Logical Names               PROCEDUREoG               To make permanent changes to your server configuration in ;               the DQS$SYSTARTUP.COM file, do the following:e  H               __________________________________________________________H               Step___Action_____________________________________________  A                1     Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.o  A                2     Add or change the definitions of the desiredaD                      server logical names. Make sure that you defineG                      the logical name systemwide and in executive mode:s  3                      $ DEFINE/SYSTEM/EXECUTIVE_MODEt4                      _$ logical-name values <Return>  G                      For example, to set the server process to run at at*                      priority of 5, enter:  K                      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$PRIORITY 5 <Return>   F                 3    Exit from the file SYS$MANAGER:DQS$SYSTARTUP.COM.  E                 4    If the change is required immediately, do one ofn#                      the following:   A                      o  Also enter the command at the DCL prompt.   B                      o  Execute the DQS startup command procedure.  8                      $ @SYS$STARTUP:DQS$STARTUP <Return>  E                      Otherwise, the change takes effect the next time G                      the SYS$STARTUP:DQS$STARTUP.COM is executed or the H               _______node_is_rebooted.__________________________________  8               Adding the logical name definitions to theA               SYS$MANAGER:DQS$SYSTARTUP.COM file ensures that the-C               logical name is defined each time your server rebootsbG               or each time the SYS$STARTUP:DQS$STARTUP.COM procedure iss+               executed on a cluster member.   H                                Configuring and Managing a DQS Server 8-3                       PRECAUTIONoA            Do not execute the DQS$STARTUP.COM procedure unless itoA            is necessary. Executing DQS$STARTUP.COM terminates anynC            DQS network operations in progress. This may cause files E            transferred from a client to be left on the server with noi@            association to the client job. When this happens, the?            server directory clean-up process, DQS$CLEANSRV.COM, A            detects and deletes the stray files left on the server >            disk. (DQS$STARTUP.COM submits the DQS$CLEANSRV.COM'            procedure at start-up time.)r          CHANGES AT DCL PROMPT?            You can also define some DQS server logical names byuC            entering the definition at the DCL prompt. These changesh#            to server configuration:   @            o  Take effect the next time the client establishes a'               connection to the server.D  B            o  Remain in effect until the server is rebooted or the0               DQS$STARTUP.COM is executed again.                                              .      8-4 Configuring and Managing a DQS Server    t          H         ________________________________________________________________  6         Modifying Definitions of Certain Logical Names               LOGICAL NAMES_C               For changes to the following logical name definitionstE               to take effect, you must make your changes in the site-SE               specific startup file DQS$SYSTARTUP.COM and restart all                server processes:s                    DQS$LOG_ACCESS )                  DQS$ACCOUNTING_BY_SYSTEM_&                  DQS$NOTIFY_CYCLE_TIME                  DQS$PRIORITY !                  DQS$MAX_PRIORITY                   DQS$IDLE_TIME  #         RESTARTING SERVER PROCESSESe:               To restart the server processes, execute the0               DQS$STARTUP.COM command procedure.  1               $ @SYS$STARTUP:DQS$STARTUP <Return>i  B               Executing DQS$STARTUP.COM terminates any DQS network%               operations in progress.                                       H                                Configuring and Managing a DQS Server 8-5 R  I          E      ________________________________________________________________   $      Before You Set Up Remote Queues            ENSURE QUEUES EXISTB            A queue must exist before you can set up the queue as aB            DQS remote queue. You can use existing queues or createC            (or initialize) new queues. (Refer to the OpenVMS System-B            Manager's Manual for information on how to initialize a            queue.)        FOR NEW INSTALLATIONSA            If you are installing this product for the first time,_=            the DQS installation provides the following serverrA            configuration file to which you need to add your queue             configurations:  ,            SYS$MANAGER:DQS$SERVER_CONFIG.TXT        FOR PRODUCT UPGRADESmB            If you are upgrading from a version previous to Version+            1.3, the installation procedure:t  @            o  Creates the SYS$MANAGER:DQS$SERVER_CONFIG.TXT file  E            o  Attempts to translate your current queue definitions to %               the format of this file   /            o  Provides you with messages in thev6               SYS$UPDATE:DQS$CONVERT_SECURITY.LOG file  D            o  Saves your queue definitions from the previous versionE               by renaming the old startup file to DQS$STARTUP.COM_OLDl  E            Compare the queue definitions in the DQS$SERVER_CONFIG.TXTu@            file to those in DQS$STARTUP.COM_OLD. You may need to?            edit DQS$SERVER_CONFIG.TXT to ensure that your queueh,            definitions are as you want them.            .      8-6 Configuring and Managing a DQS Server e  r          H         ________________________________________________________________  1         Understanding How to Set Up Remote Queuesf               KEYWORDS=               You enable network access to queues and control C               authorization to the server node and remote queues byrG               using the following keywords in the DQS$SERVER_CONFIG.TXTy               file:   H               QUEUE: Declares a queue as a DQS network accessible queue.F               You must specify this keyword to allow network printing.  H               You also use the QUEUE keyword to specify which authorized4               client nodes have access to the queue.  F               DENY_NODE: Denies a client node authorization to the DQSG               servers on the server node. This keyword takes precedencei&               over all other keywords.  B               ALLOW_NODE: Grants only the client nodes you specifyF               authorization to the DQS servers on the server node. All3               other nodes are denied authorization.   F               The QUEUE keyword differs from the other keywords. QUEUEE               controls access to queues, whereas ALLOW_NODE and DENY_uD               NODE authorize access to the DQS servers on the server               node.r  $         CLIENT AUTHORIZATION PROCESSE               Figure 8-1 shows how the configuration file checks thatdE               the client node is authorized to access the server nodei               and remote queue.                       H                                Configuring and Managing a DQS Server 8-7 h  e          E      ________________________________________________________________   )      Understanding the Configuration File             FEATURES OF THE FILE C            When you edit the DQS$SERVER_CONFIG.TXT file, notice theY            following:   -            o  The file is a simple text file.   -            o  Entries are not case-sensitive.r  @            o  Entries are specific keywords and their arguments.  @            o  Valid keywords and their arguments are as follows:  A                   Keyword      Argument 1              Argument 2-I                   -------      ------------------      ------------------tI                   QUEUE        queue_name              [client_node_name] /                   ALLOW_NODE   client_node_name 1                   DENY_NODE    [client_node_name]   D               You can the use wildcard character (*)  as an argument&               shown in brackets ([ ]).  B            o  Keywords are the first non-whitespace character on a               line.t  B            o  Keywords and arguments are separated by at least one               space.  A            o  Arguments are either simple names or complex names.u  ?               -  Simple names contain no spaces and do not spano=                  multiple lines. Simple names can contain anysA                  printable character, except the space character, E                  the exclamation point (!),  and the double quotation                   mark (").  B               -  Complex names have double quotation marks (")  asE                  delimiters at the beginning and the end of the name. B                  Complex names can contain any printable characterE                  (except the double quotation mark ("))  and can span ,                  multiple lines in the file.  .      8-8 Configuring and Managing a DQS Server                 C               o  The exclamation point (!) marks a comment. The DQS=D                  software treats lines beginning with an exclamationA                  point as comments and ignores them. Likewise, an B                  exclamation point on a line that is not part of aG                  complex name causes the rest of the line to be treated *                  as a comment and ignored.  F               o  The asterisk character (*) is the wildcard character.?                  An argument that consists of only the wildcardoH                  character implies that all client nodes are affected by,                  the operation. For example:  D                  DENY_NODE *        ! means deny access to ALL nodesM                  QUEUE Q_PARIS *    ! means allow ALL nodes access to Q_PARIS_                                                              H                                Configuring and Managing a DQS Server 8-9 n  o          E      ________________________________________________________________d        Setting Up Remote Queuese      
      OVERVIEWc@            Setting up remote queues involves editing DQS$SERVER_            CONFIG.TXT and:  B            1. Enabling network access to the queues with the QUEUE/               keyword. (This step is required.)   :            2. Optionally denying specific client nodes theC               authorization to access the DQS servers on the server_               node._  A            3. Optionally granting only specified client nodes theCC               authorization to access the DQS servers on the serverr               node.   -            4. Making the changes take effect.   @            The following sections explain how to do these tasks.                                            /      8-10 Configuring and Managing a DQS Server     N          H         ________________________________________________________________           Enabling Network Access                PROCEDUREA@               Enable network access to the queues with the QUEUE/               keyword. (This step is required.)   C               Specify one QUEUE entry for each remote queue on yourdD               system. This allows the remote queue to be DQS network4               accessible to authorized client nodes.  >               By default, all client nodes in your network are@               authorized to access the DQS servers on your node.           UNLIMITED QUEUE ACCESSE               You can use the asterisk (*) as a wildcard to allow allcA               authorized client nodes access to the print queues.i           EXAMPLErD               For example, the following entry allows all authorized?               client nodes access to the print queue Q_CHICAGO:r                 QUEUE Q_CHICAGO *i           LIMITED QUEUE ACCESSE               To allow only certain authorized client nodes access to D               your queue, enter a QUEUE entry for each node that you<               want to allow access to that particular queue.           EXAMPLE_B               For example, the following entries allows authorizedG               client nodes APPLE, BANANA, and CHERRY access to Q_PARIS:   Q               QUEUE Q_PARIS APPLE          ! Allow authorized client nodes APPLE,pI               QUEUE Q_PARIS BANANA         ! BANANA, and CHERRY access toe=               QUEUE Q_PARIS CHERRY         ! my queue Q_PARISo              H                               Configuring and Managing a DQS Server 8-11 d  e                  WHERE TO GO FROM HERE=            Enabling network queue access is the only required B            step. If you want to grant or deny certain client nodesE            authorization to DQS servers on your server node, continue B            to the next sections. Otherwise, see the section titled-            "Making Your Changes Take Effect."                                                                               /      8-12 Configuring and Managing a DQS Servert p  e          H         ________________________________________________________________  ;         Denying Client Node Authorization to the DQS Server                PURPOSEnC               Denying client nodes authorization to the DQS servers <               is primarily intended to shut out clients thatE               inappropriately and repeatedly establish connections to F               a server. Denied authorization takes precedence over any2               other form of client access control.           PROCEDUREoH               To deny a client node authorization to a DQS server on theE               server node, specify the name of the client node as thee6               first argument to the DENY_NODE keyword.           EXAMPLE G               For example, the following entry denies client node APPLEo<               from accessing DQS servers on the server node:                 DENY_NODE APPLE            DENYING ALL CLIENTSxH               To deny all client nodes authorization to the DQS servers,F               add an entry with the asterisk (*) as the first argument               to the keyword:   C               DENY_NODE *         ! Deny authorization to all nodes   @               This restricts all client nodes access to your DQS               servers.                          H                               Configuring and Managing a DQS Server 8-13 d  n          E      _________________________________________________________________  9      Granting Client Node Authorization to the DQS Servera            PURPOSEB            You can grant certain client nodes authorization to DQSC            servers on a server node. This method is useful when you C            want to allow a subset of client nodes access to the DQS &            servers on the server node.  
      REMINDER /            If you use ALLOW_NODE, keep in mind:e  A            o  You turn off the default that authorizes all clientO-               nodes access to the DQS server.Y  A            o  You must specify every client node that you want to 1               authorize access to the DQS server.   @            o  You cannot use an asterisk (*) with the ALLOW_NODE               keyword.        PROCEDUREA            Add the names of the client nodes to which you want to$C            grant authorization to the DQS server as the argument tor"            the ALLOW_NODE keyword.        EXAMPLE@            For example, the following entries allow client nodes5            APPLE and CHERRY access to the DQS server:s              ALLOW_NODE APPLEt            ALLOW_NODE CHERRY         USING ALLOW_NODE WITH QUEUEA            You can use the ALLOW_NODE and QUEUE keywords together B            as a filter in restricting access to the DQS server andD            queues. First you specify which clients nodes have access@            to the queue, then you specify which client nodes can!            access the DQS server.v        /      8-14 Configuring and Managing a DQS Server_ _  _                     PROCEDURE F               Use the following procedure to set up restricted access:  F               1. Use the QUEUE keyword to enable network access to the                  queues.  H                  For example, the following entries allow all authorizedD                  client nodes access to queues Q_OHIO, Q_KANSAS, and                  Q_SHANNON:_  J                  QUEUE Q_OHIO *        ! Allow all authorized client nodesK                  QUEUE Q_KANSAS *      ! access to queues Q_OHIO, Q_KANSAS, 6                  QUEUE Q_SHANNON *     ! and Q_SHANNON  D               2. Then, use ALLOW_NODE to authorize access to the DQSF                  servers. For example, the following entries authorizeG                  client nodes APPLE and GRAPE to access the DQS server:r  J                  ALLOW_NODE APPLE            ! Grant authorization only toK                  ALLOW_NODE GRAPE            ! client nodes APPLE and GRAPEO           RESULTH               The combination of the ALLOW_NODE and QUEUE entries allowsG               only a subset of client nodes (APPLE and GRAPE) access to 5               queues Q_OHIO, Q_KANSAS, and Q_SHANNON.            NOTEG               When using controlled access between two DQS server nodes F               that also act as client nodes, make sure each DQS serverE               node is authorized access to the other node. Otherwise,e9               notification messages may not be delivered.D                            H                               Configuring and Managing a DQS Server 8-15 _             E      ________________________________________________________________A  $      Making Your Changes Take Effect            PROCEDUREE            When you are finished adding keywords to the configurationeB            file, exit from the file and execute DQS$SERVER_UPDATE_0            CONFIG.COM to establish your changes:  ;            $ @SYS$MANAGER:DQS$UPDATE_SERVER_CONFIG <Return>   E            Changes to the DQS$SERVER_CONFIG.TXT data file take effectUC            the next time the client establishes a new connection toA            the server.                                                            /      8-16 Configuring and Managing a DQS Servert e  f          H         ________________________________________________________________  6         Determining How Clients are Accessing a Server               METHODS H               You can determine how and when clients access a particular3               server by doing any of the following:   E               o  You can check the NETSERVER.LOG log files, which are G                  created in the server account's directory. These filese)                  are periodically purged.h  F               o  If you enabled a server to log client access with theD                  DQS$LOG_ACCESS logical name, you can check the fileF                  created in the [DQS$SERVER.NODES] subdirectory of theG                  server account to see how many times and the last time D                  each client established a connection to the server.  D               o  If OpenVMS accounting is enabled, you can check theB                  process and image accounting records as describedD                  in the OpenVMS System Manager's Utilities Reference                  Manual.  H                  With OpenVMS accounting enabled and the DQS$ACCOUNTING_E                  BY_SYSTEM logical name defined, the server maintainsR0                  records of print jobs received.  "         CHECKING FOR CLIENT ACCESSE               You can check the NETSERVER.LOG log files in the serverSB               account directory for records of client node access.G               However, these files are periodically purged. Example 8-1S*               shows how to view this file.  ;               Example 8-1 Viewing NETSERVER.LOG Information   B               $ TYPE SYS$COMMON:[DQS$SERVER]NETSERVER.LOG <Return>  G               If you moved the directory, the log files might not be in                SYS$COMMON.r          H                               Configuring and Managing a DQS Server 8-17 i  a            &      LOGGING CLIENT ACCESS TO A SERVERE            DQS software counts each occurrence of a client connecting ?            to a server if you define the DQS$LOG_ACCESS logicalT?            name on the server. With DQS$LOG_ACCESS defined, thesB            server process creates a file in the [DQS$SERVER.NODES]E            subdirectory of the server account. This file has the name-E            of the client. If the [DQS$SERVER.NODES] subdirectory does <            not already exist, the server process creates it.          PROCEDURE0            To define the DQS$LOG_ACCESS logical:  E            __________________________________________________________fE            Step___Action_____________________________________________   >              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.  B              2    Add the definition of the DQS$LOG_ACCESS logical@                   name with an arbitrary value. Its value is not?                   important; only its presence on the server is                    important.  B              3    Save the file, SYS$MANAGER:DQS$SYSTARTUP.COM and'                   exit from the editor.s  ?              4    Restart all server processes by executing theeE            _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________n  
      EXAMPLESyD            Example 8-2 defines the DQS$LOG_ACCESS logical name to be'            the arbitrary value ENABLED.E  8            Example 8-2 Logging Client Access to a Server  I            $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$LOG_ACCESS ENABLED <Return>y                  /      8-18 Configuring and Managing a DQS Server     8            A               Example 8-3 shows a sample directory listing of the_H               [DQS$SERVER.NODES] subdirectory that contains the names of3               the clients that accessed the server.R    5               Example 8-3 Looking at DQS$SERVER.NODESo  @               $ Directory SYS$COMMON:[DQS$SERVER.NODES] <Return>  5               Directory SYS$COMMON:[DQS$SERVER.NODES]h  G               SMEDLY.;78     BUGSBY.;1407        JAZZY.;3     RAZBRY.;2a?               STENCL.;397         STIKNY.;24          TOKYO.;25                  Total of 7 files.n  :               Because there is a one-version limit for theG               [DQS$SERVER.NODES] subdirectory, only one file per client G               is created. The version number of the file corresponds to F               the number of logical-link connections received from the               client.   >               Node names displayed in this file are trimmed to?               8 characters. Some characters may be converted tot               underscores.  .         ENABLING CLIENT ACCOUNTING INFORMATIOND               With the DQS$ACCOUNTING_BY_SYSTEM logical name definedC               on the server, the DQS software includes the client'sAG               node name as the Account field in the server's accountinge               record.   @               User node names written to this record are trimmedB               to 8 characters. Some characters may be converted to               underscores.  $         EXAMPLE WITH LOGICAL DEFINED                 For example:            H                               Configuring and Managing a DQS Server 8-19 r  7                  $ RUN AUTHORIZE <Return>_       UAF> SHOW MACOMBER <Return>  D      Username: MACOMBER                         Owner:  Ted MacomberL      Account:  DEVELOPMENT                      UIC:    [100,1] ([MACOMBER])       . . .       UAF> EXIT <Return>   *      $ ACCOUNTING/TYPE=PRINT/FULL <Return>  I      Username:          MACOMBER          UIC:               [DQS$SERVER]rT      Account:           SMEDLY            Finish time:       14-FEB-1994 11:49:29.88T      Process ID:        00000D9A          Start time:        14-FEB-1994 11:49:24.59T      Owner ID:                            Elapsed time:                0 00:00:05.29T      Terminal name:                       Processor time:              0 00:00:00.00@      Remote node addr:                    Priority:          100E      Remote node name:                    Privilege <31-00>: 00000000tE      Remote ID:                           Privilege <63-32>: 00000000       Remote full name:E      Queue entry:       721               Final status code: 00040001       Queue name:        SERVER"      Job name:          ACCOUNTINGC      Final status text: %JBC-S-NORMAL, normal successful completionl  "      GETs from source:         180"      QIOs to printer:            5"      Pages printed:              5  #      EXAMPLE WITH LOGICAL UNDEFINED E            If you do not define this logical, the DQS client software @            uses the Account field specified in the client's UserB            Authorization File (UAF) on the client for the user who1            issued the PRINT command. For example:r  +      $ ACCOUNTING/TYPE=PRINT/FULL  <Return>                     /      8-20 Configuring and Managing a DQS Server                           PRINT Job Termination          --------------------- L         Username:          MACOMBER          UIC:               [DQS$SERVER]W         Account:           DEVELOPMENT       Finish time:       14-FEB-1994 11:49:07.65=W         Process ID:        00000D9A          Start time:        14-FEB-1994 11:49:02.36pW         Owner ID:                            Elapsed time:                0 00:00:05.29 W         Terminal name:                       Processor time:              0 00:00:00.00bC         Remote node addr:                    Priority:          100 H         Remote node name:                    Privilege <31-00>: 00000000H         Remote ID:                           Privilege <63-32>: 00000000         Remote full name:tH         Queue entry:       717               Final status code: 00040001!         Queue name:        SERVER %         Job name:          ACCOUNTING F         Final status text: %JBC-S-NORMAL, normal successful completion  %         GETs from source:         180 %         QIOs to printer:            5 %         Pages printed:              5Q           PROCEDURE B               To define the DQS$ACCOUNTING_BY_SYSTEM logical name:  H               __________________________________________________________H               Step___Action_____________________________________________  A                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.i  G                 2    Add the definition of the DQS$ACCOUNTING_BY_SYSTEM :                      logical name with an arbitrary value.  =                      $ DEFINE/SYSTEM/EXECUTIVE_MODE -<Return> @                      _$ DQS$ACCOUNTING_BY_SYSTEM ENABLE <Return>  G                 3    Exit from the file, SYS$MANAGER:DQS$SYSTARTUP.COM.n  B                 4    Restart all server processes by executing theH               _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________              H                               Configuring and Managing a DQS Server 8-21 D  S                  EXAMPLEC            Example 8-4 defines the DQS$ACCOUNTING_BY_SYSTEM logical_2            name to be the arbitrary value ENABLED.    7      Example 8-4 Enabling Client Accounting Informatione  M      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$ACCOUNTING_BY_SYSTEM ENABLED <Return>                                                                           /      8-22 Configuring and Managing a DQS Servero               H         ________________________________________________________________  3         Controlling the Note on the Job Banner Paged               BANNER PAGE NOTEH               The DQS software makes use of a print attribute to place aG               note on the banner page of a print job when logical names G               are defined in the DQS$SYSTARTUP.COM file. On the server, D               this logical name definition provides the default textD               "Print Job processed by DQS Vn.n". The note defined byH               this logical name prints on the banner page of a print job               if:c  H               o  The /NOTE qualifier is not specified by the client node*                  user on the PRINT command  @               o  The logical name definition for the note is not-                  specified for the client jobh  D               The note that prints on the banner page of a print job/               follows this order of precedence:   @               o  Note specified by the user with PRINT/NOTE=note  C               o  Note specified by a client logical name definitionU.                  (DQS$CLIENT_DEFAULT_JOB_NOTE)  C               o  Note specified by a server logical name definitionS.                  (DQS$SERVER_DEFAULT_JOB_NOTE)           OPTIONS -               You have the following options:r  F               o  Use the default note provided by the DQS software for                   the banner page  D               o  Turn off the DQS logical definitions for the banner                  page note  9               o  Define your own note for the banner page         H                               Configuring and Managing a DQS Server 8-23 o  g                  TO TURN OFF THE DEFAULTD            To turn off the DQS default note on the server system, do            the following:y  E            __________________________________________________________ E            Step___Action_____________________________________________   >              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.  A              2    Search for the following command and remove the :                   exclamation mark (!)  comment character:  G                   $! $ DEASSIGN/SYSTEM/EXEC DQS$SERVER_DEFAULT_JOB_NOTED  B              3    Save SYS$MANAGER:DQS$SYSTARTUP.COM and exit fromE            _______the_editor.________________________________________e  4            The change takes effect the next time the3            SYS$STARTUP:DQS$STARTUP.COM is executed.l        TO CHANGE NOTE TEXTC            To change the text of the note that prints on the banner "            page, do the following:  E            __________________________________________________________eE            Step___Action_____________________________________________w  >              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.  3              2    Search for the following command:t  G                   $! $ DEFINE/SYSTEM/EXEC DQS$SERVER_DEFAULT_JOB_NOTE -c  0                   $!      "Place your text here"  D                   Substitute your note for the text "Place your textB                   here" and remove the dollar sign and exclamation;                   mark ($!)  at the beginning of each line.t  A              3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM and E            _______exit_from_the_editor.______________________________r  D            The next time the SYS$STARTUP:DQS$STARTUP.COM is executedC            and the note is not specified by the user or the client,e>            your customized note prints on the job banner page.  /      8-24 Configuring and Managing a DQS Servern f  e          H         ________________________________________________________________  +         Enabling Status Messages for Queues                PURPOSE F               You can define the DQS$STATUS_queue-name logical name soH               that a status message is displayed each time a user entersG               a QSHOW command for the specified queue (or any DQS queue E               that points to that queue). This function is useful foreG               displaying printer status messages, such as "Q_PRINTER isr)               down until 1PM for repair."t           PROCEDUREP?               To define the DQS$STATUS_queue-name logical name:   H               __________________________________________________________H               Step___Action_____________________________________________  E                 1    Define the DQS$STATUS_queue-name logical name byeA                      entering the following at the system prompt:t  5                      $ DEFINE/SYSTEM/EXECUTIVE_MODE - A                      _$ DQS$STATUS_queue-name  "Message" <Return>a  D                      When defining the DQS$STATUS_queue-name logicalH                      make sure to enclose the message in quotation marks                      ("").  E                      You can define this logical name for both remote H               _______and_client_queues._________________________________  D               When you change the value of the DQS$STATUS_queue-nameG               logical name, the next display of the queue shows the newo               message.                    H                               Configuring and Managing a DQS Server 8-25 Q  A                  EXAMPLEB            Example 8-5 specifies that the status message "Down forD            repairs" displays each time a user enters a QSHOW command(            for the remote queue Q_PARIS.    6      Example 8-5 Defining a Status Message for a Queue  R      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$STATUS_Q_PARIS "Down for repairs" <Return>  C            When you want to remove the message for the queue, enter )            one of the following commands:   A      $ DEASSIGN/SYSTEM/EXECUTIVE_MODE DQS$STATUS_Q_PARIS <Return>   7      $ DEASSIGN/SYSTEM/USER DQS$STATUS_Q_PARIS <Return>Q                                                          /      8-26 Configuring and Managing a DQS Server  e             H         ________________________________________________________________  @         Enabling the DQS Print Symbiont To Control Remote Queues      !         WHY USE THE DQS SYMBIONT?lG               DQS software supplies its own print symbiont, DQS$PRTSMB,g?               which you can use to replace the standard OpenVMS_D               print symbiont on a server unless you use the DECprintE               Supervisor for OpenVMS software. The DQS print symbiontoB               writes client-specific job information on the burst,D               flag, and trailer pages of DQS print output. If you doD               not like the way the standard OpenVMS symbiont handlesE               banner pages, enable the DQS print symbiont DQS$PRTSMB.I           PROCEDURE TO ENABLE B               To enable the DQS print symbiont to control a remote&               queue, do the following:  H               __________________________________________________________H               Step___Action_____________________________________________  H                1     Stop the queue by entering STOP/QUEUE/RESET remote--                      queue at the DCL prompt.   G                2     Associate the DQS$PRTSMB process with the queue by H                      entering INIT/QUEUE/PROC=DQS$PRTSMB remote-queue at$                      the DCL prompt.  F                3     Restart the queue by entering START/QUEUE remote-,                      queue at the DCL prompt  C                4     Digital recommends that you also enter the SETiE                      QUEUE/RETAIN=ERROR queue-name command at the DCL C                      prompt to hold jobs in the queue that complete E                      unsuccessfully. With the /RETAIN=ERROR qualifieraH               _______set,_QSHOW_commands_display_the_error._____________                H                               Configuring and Managing a DQS Server 8-27    o                  EXAMPLEA            Example 8-6 shows how to enable the DQS print symbiontr:            DQS$PRTSMB to control the remote queue Q_PARIS.    6            Example 8-6 Enabling the DQS Print Symbiont  .            $ STOP/QUEUE/RESET Q_PARIS <Return>8            $ INIT/QUEUE/PROC=DQS$PRTSMB Q_PARIS <Return>)            $ START/QUEUE Q_PARIS <Return>C4            $ SET QUEUE/RETAIN=ERROR Q_PARIS <Return>        FOR MORE INFORMATIONSD            Refer to Chapter 7 for more information on the DQS$PRTSMB            symbiont.  E            Appendix D describes how the DQS software works with othero            print symbionts.                                                       /      8-28 Configuring and Managing a DQS ServerE R  .          H         ________________________________________________________________  @         Specifying the Scanning Interval for Server Notification               ABOUT THE NOTIFIERB               The DQS software supplies a process on server nodes,B               DQS$NOTIFIER, that can send notification messages toF               users after their print jobs complete. DQS$NOTIFIER runsE               as a detached process on a server and is started by the F               SYS$STARTUP:DQS$STARTUP.COM procedure at system start-upD               time. This process periodically scans remote queues to6               determine which print jobs are complete.           PROCEDURE >               You can specify the interval at which the serverE               notification process scans the remote queue by defining D               the DQS$NOTIFY_CYCLE_TIME logical name to be a time inE               OpenVMS delta time format. By default, the notify cycle #               time is five minutes.S  @               To specify the DQS$NOTIFY_CYCLE_TIME logical name:  H               __________________________________________________________H               Step___Action_____________________________________________  A                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.S  D                 2    Add the definition of the DQS$NOTIFY_CYCLE_TIMEH                      logical name with the desired time in OpenVMS delta!                      time format.R  G                 3    Exit from the file, SYS$MANAGER:DQS$SYSTARTUP.COM.d  3                 4    Stop the DQS$NOTIFIER process.   F                 5    Restart the DQS$NOTIFIER process by executing theH               _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________  E               If you change the default time, consider the following:g  B               o  If you define the cycle time to be less than fiveB                  minutes, the server's job controller and notifier=                  process use more of the server's CPU cycles.t  H                               Configuring and Managing a DQS Server 8-29 E  O            ?            o  If the cycle time you define is much greater than A               the default, users may not be notified of their job ,               completion in a timely manner.          EXAMPLEA            Example 8-7 defines the interval at which DQS$NOTIFIER >            scans the remote queues to be every 10 minutes. TheB            DQS$NOTIFIER process is stopped and restarted to effect            this change.r  ;            Example 8-7 Specifying the Scanning Interval fori#                        DQS$NOTIFIER         Add to DQS$SYSTARTUP.COM:  Q      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$NOTIFY_CYCLE_TIME "0 00:10:00.0" <Return>h  #      Then, enter at the DCL prompt:   ,      $ @SYS$STARTUP:DQS$STARTUP.COM <Return>                                                /      8-30 Configuring and Managing a DQS Serverh e  S          H         ________________________________________________________________  8         Specifying a Directory for PrintServer Log Files               OVERVIEWE               If your PrintServer software supports the return of logaD               files from DQS print jobs, you can specify a directory5               into which the log files can be placed.e  F               You specify a directory for the PrintServer log files byF               defining the DQS$LOG_AREA logical name to be the name of               the directory.           PROCEDUREAA               To specify a directory for PrintServer software logm               files:  H               __________________________________________________________H               Step___Action_____________________________________________  H                 1    Define the DQS$LOG_AREA logical name to be the nameF                      of the directory by entering the following at the                       DCL prompt:  3                      $ DEFINE/SYSTEM/EXECUTIVE_MODE @                      _$ DQS$LOG_AREA device:[directory] <Return>  H               __________________________________________________________  G               If you want this logical name to be permanent, define the @               logical name in the SYS$MANAGER:DQS$SYSTARTUP.COM.  B               If this logical name is not defined, the PrintServerC               software does not write log files for DQS print jobs.            EXAMPLE B               Example 8-8 specifies the directory [PRINTSERVER] on@               device $1$DUA0: on the server as the directory for$               PrintServer log files.  D         Example 8-8 Specifying a Directory for PrintServer Log Files  H                                                 (continued on next page)  H                               Configuring and Managing a DQS Server 8-31 o  o            C      Example 8-8 (Cont.) Specifying a Directory for PrintServer Logi                          Files  O      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$LOG_AREA $1$DUA0:[PRINTSERVER] <Return>i          FOR MORE INFORMATIONa:            For more information on logging options for theB            PrintServer Software, refer to the PrintServer Software(            for OpenVMS Management Guide.                                                                      /      8-32 Configuring and Managing a DQS Server     c          H         ________________________________________________________________  5         Specifying the Priority of the Server Process                PROCEDUREpF               You can specify the priority at which the server processB               runs by defining the DQS$PRIORITY logical name to be@               the desired priority. Be aware that redefining theE               DQS$PRIORITY logical name affects scheduling algorithms >               on the OpenVMS system and changes overall system               performance.  H               __________________________________________________________H               Step___Action_____________________________________________  A                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.a  H                 2    Add the definition of the DQS$PRIORITY logical name/                      with the desired priority.:  G                      If you do not define this logical name, the server ;                      process runs at priority 4 by default.l  D                 3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM and*                      exit from the editor.  B                 4    Restart all server processes by executing theH               _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________           EXAMPLES9               Example 8-9 shows the command to add to theiB               SYS$MANAGER:DQS$SYSTARTUP.COM file to set the server+               process to run at priority 5.   G               Example 8-9 Specifying the Priority of the Server Processt  D               $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$PRIORITY 5 <Return>  C               The next time a server process is started, the serverP5               process runs at the specified priority.         H                               Configuring and Managing a DQS Server 8-33               E      ________________________________________________________________i  6      Specifying the Maximum Priority of DQS Print Jobs            PROCEDURED            You can specify the maximum priority at which a print jobC            can be queued or set by a user, by defining the DQS$MAX_ !            PRIORITY logical name.   E            __________________________________________________________ E            Step___Action______________________________________________  >              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.  D              2    Add the definition of the DQS$MAX_PRIORITY logical9                   name with the desired maximum priority.o  C                   If you do not define this logical name, the value >                   of the SYSGEN parameter DEFQUEPRI is used by                   default.  A              3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM andb'                   exit from the editor.   ?              4    Restart all server processes by executing the E            _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________e        EXAMPLEE            Example 8-10 specifies that print jobs can be queued at noe#            higher than priority 42.   C            Example 8-10 Specifying the Maximum Priority for Queuing "                         Print Jobs  F            $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$MAX_PRIORITY 42 <Return>                  /      8-34 Configuring and Managing a DQS Server                H         ________________________________________________________________  8         Specifying the Duration of Links to Client Nodes               OVERVIEWB               You can specify the duration that a server maintainsG               logical links to inactive clients. A client is considered C               inactive if it is not sending print jobs to a server.            PROCEDUREeC               You specify the duration of logical links by definingnG               the DQS$IDLE_TIME logical name to be the time duration ino3               minutes in OpenVMS delta time format.   H               __________________________________________________________H               Step___Action_____________________________________________  B                 1    Edit the file, SYS$MANAGER:DQS$SYSTARTUP.COM.  D                 2    Add the definition of the DQS$IDLE_TIME logicalF                      name with the desired duration time in minutes in/                      OpenVMS delta time format.   D                      If you do not define this logical name, an idle;                      time of 15 minutes is used by default.   D                 3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM and*                      exit from the editor.  B                 4    Restart all server processes by executing theH               _______SYS$STARTUP:DQS$STARTUP.COM_procedure._____________  H               When you redefine the DQS$IDLE_TIME logical name, consider               the following:  H               o  If you define the idle time to be less than 15 minutes,H                  processes may be created on your server more often than                   you would like.  B               o  If you define the idle time to be greater than 15D                  minutes, too many processes may remain for too long                   on your server.    H                               Configuring and Managing a DQS Server 8-35                       EXAMPLEC            Example 8-11 specifies that the server maintains logicala9            links to idle clients for at least 45 minutes.     D            Example 8-11 Specifying the Duration of Links to Inactive                         Clientse  O            $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$IDLE_TIME "0 00:45:00.0" <Return>r        IDLE TIME EXCEEDED_0            The DQS software responds as follows:  E            __________________________________________________________hE            When_._._.____________Then_._._.__________________________o  C            Idle time specified   The server process disconnects the <            by the DQS$IDLE_      logical link to the client.            TIME logical name is             exceededs  E            The client has        The client reestablishes the logicale4            a print job to        link to the server.            transfer to theE            server____________________________________________________p                                        /      8-36 Configuring and Managing a DQS Server  u  u          H         ________________________________________________________________  ;         Move the Server Account Directory to Another Device                STORAGE SPACEQA               The amount of storage space required for the server_B               account directory varies depending on the following:  )               o  Number of queues defined_  B               o  Expected number and size of the queued print jobs  E               o  Rate at which printers can print jobs (so that filest                  are deleted)N  A               The DQS server installation sets the default devicenD               for the server account to SYS$COMMON:. You can use theF               DQS$SERVER_CHANGE_DEFAULT_DEVICE.COM procedure to changeA               the default to another disk or back to SYS$COMMON:.            PROCEDUREdC               If you want to move the server account directory to aiH               device other than the system disk, execute the DQS$SERVER_A               CHANGE_DEFAULT_DEVICE.COM procedure by entering thea2               following command at the DCL prompt:  F               $ @SYS$MANAGER:DQS$SERVER_CHANGE_DEFAULT_DEVICE <Return>  C               DQS$SERVER_CHANGE_DEFAULT_DEVICE.COM asks you for theP-               device for the account storage.t  0         Enter device for the DQS$SERVER account:  @               Enter the name of the device to use for the serverC               account. For example, if your server account is to beQ2               on device USERDISK, enter USERDISK:.  B         Enter device for the DQS$SERVER account:USERDISK: <Return>  B               After you enter the device name, you see a series of5               status messages, such as the following:            User record(s) updated?         DQS$SERVER directory is now located on device USERDISK:   &         To start DQS, enter following:  .                 $ @SYS$STARTUP:DQS$STARTUP.COM  H                               Configuring and Managing a DQS Server 8-37 _  _            B      In VMScluster environment, you need to start DQS on each node      in a cluster.        $                                                                                  /      8-38 Configuring and Managing a DQS Servert s  d          H         ________________________________________________________________  .         Advanced VMScluster DQS Configurations               OVERVIEWB               In an OpenVMScluster environment, you can configure:  A               o  A set of queues to be shared by all nodes in the                   cluster  @               o  A set of queue to be shared by some nodes and aE                  different set of queues to be shared by other nodes.A  G               When you configure different sets of queues, you need to:   7               1. Redefine the DQS$NOTIFIER_LOCK logical_  B               2. Specify two separate DQS$SERVER_CONFIG.TXT files.  G               The following sections explain how to configure different1               sets of queues.                                               H                               Configuring and Managing a DQS Server 8-39 r  s          E      ________________________________________________________________m  :      Specifying Unique Notifier Lock Names in a VMScluster      Environment            REQUIREMENTD            When you configure different sets of queues for differentB            groups of nodes, you must define the same notifier lockE            name on all cluster members that share a particular set of             queues.        PROCEDUREA            To ensure that each set of queues is associated with alB            common and unique notifier lock, define the DQS$NOTIFY_D            LOCK logical name to be the same, unique lock name on all;            cluster nodes that share the same set of queues.7  C            By default, the DQS installation names the notifier lock             to be DQS$NOTIFIER.        EXAMPLE            For example:t  B            o  A VMScluster system consists of nine nodes with fourC               members that share one set of queues and five members$/               that share another set of queues.   D            o  Four members that share the same set of queues use the6               default notifier lock name DQS$NOTIFIER.  E            o  Five cluster members that share the other set of queues A               require that you define a unique notifier lock nameeB               on each of them. The lock name DQS$NOTIFIER_2 can beD               defined on each of these five cluster members as shown               in Example 8-12.  <      Example 8-12 Specifying Unique Notifier Lock Names in a+                   Nonhomogeneous VMScluster   K      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$NOTIFY_LOCK DQS$NOTIFIER_2 <Return>         /      8-40 Configuring and Managing a DQS Server                H         ________________________________________________________________  1         Redefining DQS$SERVER_CONFIG_DAT_FILE and "         DQS$SERVER_CONFIG_TXT_FILE      !         RECOMMENDED CONFIGURATION A               Digital recommends that you use the same DQS server B               configuration for all nodes within your cluster. TheF               DQS installation sets up the DQS software on your systemG               with this recommended configuration in mind. As a result, D               the default values for the locations of the DQS serverF               configuration files are both specifically located in the<               SYS$COMMON areas of your clusters file system.  C               The DQS software uses VMS logical names to locate theN)               server configuration files.   &         LOCATION OF CONFIGURATION DATA;               The location of the server configuration text_=               is controlled by the logical DQS$SERVER_CONFIG_h=               TXT_FILE. The default value for this logical isA7               SYS$COMMON:[SYSMGR]DQS$SERVER_CONFIG.TXT.   F               The location of the encoded file that the DQS$SERVER.EXED               program uses to validate a client's request for accessG               to a particular server queue is controlled by the logicalID               DQS$SERVER_CONFIG_DAT_FILE. The default value for thisB               logical is SYS$COMMON:[SYSEXE]DQS$SERVER_CONFIG.DAT.  6         SPECIFYING MULTIPLE SERVER CONFIGURATION FILESA               DQS can support multiple server configuration fileseF               within a cluster. If your cluster cannot use the defaultG               configuration, you can use the DQS$SERVER_CONFIG_TXT_FILEfE               and DQS$SERVER_CONFIG_DAT_FILE logical names to provide F               multiple, separate, DQS server configurations within the               same cluster.h                H                               Configuring and Managing a DQS Server 8-41                       PROCEDURE?            To modify the logicals, use the following procedure:   5            1. Edit the site-specific DQS startup files,               SYS$STARTUP:DQS$SYSTARTUP.COM.  D            2. Change SYS$COMMON: to SYS$SYSROOT: in following lines:  <               $ DEFINE/SYS/EXEC DQS$SERVER_CONFIG_TXT_FILE -;                    SYS$COMMON:[SYSMGR]DQS$SERVER_CONFIG.TXT$  <               $ DEFINE/SYS/EXEC DQS$SERVER_CONFIG_DAT_FILE -;                    SYS$COMMON:[SYSMGR]DQS$SERVER_CONFIG.DATh  ;            3. Restart DQS to effect the change by executing *               SYS$STARTUP:DQS$STARTUP.COM.                                                          /      8-42 Configuring and Managing a DQS Server_ _  _          H         ________________________________________________________________  7         Specifying Remote Queues on a VMScluster Systemr      &         EXECUTE THE START-UP PROCEDUREF               If you specify remote queues on any node in a VMSclusterF               system, you must execute the SYS$STARTUP:DQS$STARTUP.COMB               procedure on each cluster member. If you do not, DQSF               connections to the cluster fail randomly because not allA               nodes in the cluster are configured as DQS servers.c  G               The cluster should have an incoming cluster alias defined_A               so that clients can direct their print jobs to that                cluster alias.                                                            H                               Configuring and Managing a DQS Server 8-43    e          E      ________________________________________________________________   %      Configuring Daisy-Chained QueuesM      
      BENEFITS A            Daisy-chained queues are useful when a server's output_C            device becomes unavailable. In this case, you can define C            the remote queue for the unavailable device also to be a E            client queue that directs print jobs to yet another remote ,            queue on another DQS server node.  
      DEFINING D            To define a remote queue as a daisy-chained queue, defineB            the remote queue to be a DQS client queue, using any of.            the methods described in Chapter 9:  <            o  Use SYS$MANAGER:DQS$DEFINE.COM if you want the)               definition to be temporary.r  C            o  Add the definition to DQS$SYSTARTUP.COM if you want a "               permanent defintion.        BEWARE OF LOOPSE            The DQS software does not prevent you from creating a loop E            in your daisy-chained queues. Be sure not to set up daisy- B            chained queues where print jobs ultimately are directed<            back to the queue from which they were forwarded.        FIXING LOOPING ERRORS?            Perform the following procedure to eliminate a loop:e  D            1. Stop any queue in the loop, then stop the other queues               in the loop.  A            2. Edit the configuration file (DQS$SYSTARTUP.COM) and3B               change the client and/or server queue definitions to!               eliminate the loop._  C            3. Restart DQS and the queues on each node. DQS$NOTIFIERSA               deletes any copies of jobs that were created in thec               loop.h  A            4. Enter the QSHOW command to verify that the loop hasT               been eliminated.  /      8-44 Configuring and Managing a DQS Servert                 G               5. Manually delete any print jobs that were replicated int                  the loop.                                                                                      H                               Configuring and Managing a DQS Server 8-45 _  _          E      ________________________________________________________________R        Summary of Server Tasks  C            Table 8-1 lists the management tasks and how the task is (            performed for the DQS server.  E      Table_8-1_Summary_of_Server_Node_Management_Tasks_______________   E      For_this_task_._._.___You_do_this_._._._________________________   A      Editing site-         Edit the SYS$MANAGER:DQS$SYSTARTUP.COM @      specific startup      procedure so that it defines each DQS?      file to define        logical name definition you specify.T      logical names  -      Setting up remote     Add entries to the B      queues                SYS$MANAGER:DQS$SERVER_CONFIG.TXT file.D                            For each remote queue on the server node,B                            include a QUEUE keyword followed by theB                            name of the queue as the first argumentB                            and the name of the client node that isE                            permitted to send jobs to the remote queues2                            as the second argument.  -      Granting clients      Add entries to therB      controlled access to  SYS$MANAGER:DQS$SERVER_CONFIG.TXT file.>      a server              For each client node allowed accessA                            to remote queues on the server system,sB                            include the ALLOW_NODE keyword with theC                            name of the client node as the first andTC                            only argument. Client nodes must also be_C                            allowed access through the QUEUE entries_<                            in the server configuration file.  E                                              (continued on next page)                     /      8-46 Configuring and Managing a DQS Serveri    o            H         Table_8-1_(Cont.)_Summary_of_Server_Node_Management_Tasks_______  H         For_this_task_._._.___You_do_this_._._._________________________  0         Denying clients       Add entries to theE         access to a server    SYS$MANAGER:DQS$SERVER_CONFIG.TXT file. C                               For each client node denied access to A                               remote queues on the server system, D                               include the DENY_NODE keyword with theF                               name of the client node not permitted toE                               access the server as the first and only '                               argument./  D         Logging client        Define the DQS$LOG_ACCESS logical nameF         access to a server    so that the server creates a file in theC                               server account that has the name of a D                               client and counts each time the clientE                               establishes a connection to the server.i  A         Enabling client       Define the DQS$ACCOUNTING_BY_SYSTEMcG         accounting            logical name so that a client's node nameeF         information           (in the format node-name) is used in the9                               server's accounting record.   F         Enabling status       Define the DQS$STATUS_queue-name logicalA         messages for a queue  name to be a status message that is_D                               displayed for each queue that has thisG                               logical name defined when a QSHOW commandY(                               is issued.  G         Enabling the DQS      Issue OpenVMS commands to stop the remote H         print symbiont for a  queue, initialize the queue specifying theH         remote queue          DQS$PRTSMB process, and restart the queue.  F         Specifying the        Define the DQS$NOTIFY_CYCLE_TIME logicalF         interval at           name to be the interval at which the DQSH         which the server      server notification process (DQS$NOTIFIER)G         notification process  scans the remote queues to determine when_7         scans the remote      a print job has completed          queues  H                                                 (continued on next page)      H                               Configuring and Managing a DQS Server 8-47 u  ,            E      Table_8-1_(Cont.)_Summary_of_Server_Node_Management_Tasks_______   E      For_this_task_._._.___You_do_this_._._._________________________t  E      Specifying a          Define the DQS$LOG_AREA logical name to bemC      directory for         the directory into which PrintServer log ,      PrintServer log       files are placed.
      files  E      Specifying the        Define the DQS$PRIORITY logical name to betD      priority of the       the priority at which you want the server*      server process        process to run.  C      Specifying the        Define the DQS$MAX_PRIORITY logical name @      maximum priority      to be the maximum priority at which aA      of DQS print jobs     print job can be queued on the server.   @      Specifying the time   Define the DQS$IDLE_TIME logical name@      for maintaining       to be the duration of time the server?      links to client       maintains a logical link to a client E      nodes                 symbiont that is idle (that is, a symbiontb@                            that is not transferring print jobs).  =      Moving the DQS        Run the DQS$SERVER_CHANGE_DEFAULT_a0      server default        DEVICE.COM procedure.      directory.j  B      Configuring           Define the same DQS$NOTIFY_LOCK logical@      different sets        name on all nodes in a nonhomogeneousE      of queues in a        VMScluster that share the same queue file.gE      VMScluster system.    By default, the DQS installation names the_<                            notifier lock to be DQS$NOTIFIER.  C                            Redefine the logicals DQS$SERVER_CONFIG_ C                            DAT_FILE and DQS$SERVER_CONFIG_TXT_FILE.   C      Configuring server    Execute the DQS$STARTUP.COM command file D      software in a         on all cluster members in order to define@      VMScluster            remote queues throughout the cluster.  D      Setting up daisy-     Define a remote queue to also be a clientA      chained remote        queue that directs jobs to yet anothervE      queues________________remote_queue._____________________________t    /      8-48 Configuring and Managing a DQS ServerM o  u                  H                                                                        9H         ________________________________________________________________  H                                    Configuring and Managing a DQS Client                 ABOUT THIS CHAPTERG               This chapter presents an overview of the management taskst;               required by a DQS client and explains how to:N  C               o  Use the DQS startup procedure in client managementE  A               o  How to manage processes created by client queuesa  E               o  Create client queues with basic and advanced methods   D               o  Temporarily change the definition of a client queue  %               o  Delete client queues   C               o  Configure client nodes in a VMScluster environmentn  @               o  Synchronize client and server forms definitions  (               o  Spool to a client queue  F               o  Modify the default note on the banner page of a print                  job  8               o  Regulate forms checking on client nodes                    H                                Configuring and Managing a DQS Client 9-1 A  P          E      ________________________________________________________________   "      Overview of Client Management            MANAGEMENT TASKSrC            Configuring and managing a DQS client primarily involves =            defining DQS client queues to direct print jobs to C            associated remote queues on server systems. You can also :            modify and delete DQS client queue definitions.  B            DQS software provides the following methods of defining&            and managing client queues:  ?            o  A basic method using the DQS$IMPORT.COM procedureo  #            o  More complex methods:h  4               -  Adding definitions as parameters to4                  the DQS$DEFINE.COM procedure in the3                  SYS$MANAGER:DQS$SYSTARTUP.COM filed  /               -  Defining generic client queuess  /               -  Defining logical client queuesd  (      EXECUTING THE DQS STARTUP PROCEDURE>            To start or restart client queues, you must use the@            SYS$STARTUP:DQS$STARTUP.COM procedure. This procedureE            invokes the required procedures to define client queues on             the system.                            .      9-2 Configuring and Managing a DQS Client               H         ________________________________________________________________  !         Managing Client Processes                OVERVIEWB               On a client node, every client queue that you createC               (that is not a generic or a logical queue) results ind*               the creation of one process.           ONE CLIENT; ONE PROCESS C               If you do not anticipate a problem with the number of G               processes on your client node, then you can use either ofo?               the following procedures to create client queues:C  @               o  DQS$IMPORT.COM (described in the section titled<                  Creating Client Queues with DQS$IMPORT.COM)  @               o  DQS$DEFINE.COM (described in the section titledC                  Creating Client Queues with More Advanced Methods)   F               Both result in the creation of a process for each client               queue.           REDUCING PROCESSESF               If you do not want to create as many processes as clientG               queues, then you can create either of the following types                of client queues:T  G               o  Generic client queues (described in the section titlede9                  Method 2: Defining Generic Client Queuese  C               o  Logical client queues (as described in the section_                  titlede9                  Method 3: Defining Logical Client Queues   D               Generic and logical queues direct jobs to other clientH               execution queues that actually process the job. Therefore,>               fewer processes are created on your client node.            H                                Configuring and Managing a DQS Client 9-3    _          E      ________________________________________________________________g  /      Creating Client Queues with DQS$IMPORT.COMR            A BASIC METHOD ?            The most basic way to create DQS client queues is tot7            invoke the DQS$IMPORT.COM command procedure.t  9            The DQS$IMPORT.COM procedure provides a way to A            permanently define client queues. The queue definition B            is automatically added to the DQS$SYSTARTUP.COM commandC            file. This ensures that the client queue starts with the E            proper definition each time the client system is rebooted.         BEFORE YOU START C            Before you can define a client queue with the DQS$IMPORT             command procedure:   C            o  You must have the following privileges: SYSPRV, OPER,R)               SYSNAM, NETMBX, and TMPMBX.h  ;            o  The associated server node must be reachable.e  A            o  The associated remote queue must be initialized andu,               defined as a DQS remote queue.        PROCEDUREE            Create a client queue with the DQS$IMPORT.COM procedure as             follows:   E            __________________________________________________________ E            Step___Action_____________________________________________   A              1    Invoke the DQS$IMPORT.COM command file for each 2                   client queue you want to create.  @                   $ @SYS$MANAGER:DQS$IMPORT server-node::remote-                    queue <Return>  >                   For each client queue, supply the associatedD                   remote queue and server node in the format server-E            _______node::remote-queue_as_a_parameter_to_the_procedure.V    .      9-4 Configuring and Managing a DQS Client                 5               DQS$IMPORT.COM then does the following:   D               o  Creates the client queue, giving it the name of its)                  associated remote queue.   8               o  Adds the client queue definition to theD                  DQS$SYSTARTUP.COM file so that the queue definition                  is persistent.            EXAMPLE$B               Example 9-1 show how to use DQS$IMPORT.COM to create@               a client queue Q_CHICAGO that uses the name of theE               corresponding remote queue Q_CHICAGO on the server nodeI               APPLES.   E               Example 9-1 Creating a Client Queue with DQS$IMPORT.COMM  B               $ @SYS$MANAGER:DQS$IMPORT APPLES::Q_CHICAGO <Return>  E               DQS$IMPORT.COM adds this client queue definition to the %               DQS$SYSTARTUP.COM file.            NOTEE               DQS$IMPORT.COM adds an invocation of the DQS$DEFINE.COM A               procedure to the SYS$MANAGER:DQS$SYSTARTUP.COM file_C               for each client queue and executes the DQS$DEFINE.COM B               procedure to actually create the queue. When you useG               DQS$IMPORT.COM to create a client queue, the client queuet6               and the remote queue have the same name.                                H                                Configuring and Managing a DQS Client 9-5 b  u          E      ________________________________________________________________   6      Creating Client Queues with More Advanced Methods            ADVANCED METHODS A            More advanced methods of creating client queues are as             follows:   @            o  Adding a definition for a client queue directly toA               the DQS$SYSTARTUP.COM file using the DQS$DEFINE.COM &               procedure and parameters  ,            o  Defining generic client queues  ,            o  Defining logical client queues        METHOD 1: USING DQS$DEFINEqD            Creating a client queue with the DQS$DEFINE.COM procedureC            is useful when you want the name of a client queue to be ;            different from its associated remote queue name.u        PROCEDURED            Create client queues with the DQS$DEFINE.COM procedure as            follows:N  E            __________________________________________________________eE            Step___Action_____________________________________________   A              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file and$>                   search for the statement, "DQS Client QueuesA                   Definitions". The statement appears in the fileR                   as follows:   ?                   $!-------------------------------------------D2                   $! DQS Client Queues DefinitionsA                   $!--------------------------------------------.d                .      9-6 Configuring and Managing a DQS Client i  t          H               __________________________________________________________H               Step___Action_____________________________________________  F                 2    On a new line following the "DQS Client Queue..."A                      statement, insert a DCL command that invokesnB                      the SYS$MANAGER:DQS$DEFINE.COM procedure (see"                      Example 9-2).  C                      For each invocation of DQS$DEFINE.COM that youuC                      insert, supply the following parameters in theoF                      following order (the last parameter is optional):  )                      a. Client queue namea  :                      b. Its corresponding server node name  ;                      c. Its corresponding remote queue nameM  "                      d. A zero (0)  G                      e. Qualifiers with which to start the client queue   C                      Separate each parameter by at least one space. @                      Spaces are not permitted in the parameters.  C                      Example 9-2 shows how to edit this information_D                      properly into the SYS$MANAGER:DQS$SYSTARTUP.COMH               _______file.______________________________________________  ;               DQS$DEFINE.COM is the procedure that actuallyT;               creates a DQS client queue. When you edit thesC               SYS$MANAGER:DQS$SYSTARTUP.COM file, you should inserthC               your invocation of DQS$DEFINE.COM exactly as shown ine               Example 9-2.           EXAMPLEnH               In Example 9-2, SYS$MANAGER:DQS$SYSTARTUP.COM is edited toH               contain an invocation of the DQS$DEFINE.COM procedure thatE               associates the client queue CQ_ILLINOIS with the remotec3               queue Q_CHICAGO on server node APPLE.   >         Example 9-2 Creating Client Queues With DQS$DEFINE.COM  H                                                 (continued on next page)    H                                Configuring and Managing a DQS Client 9-7 t  e            C      Example 9-2 (Cont.) Creating Client Queues With DQS$DEFINE.COM   6      $ EDIT/EDT SYS$MANAGER:DQS$SYSTARTUP.COM <Return>          1       $! IDENT=V1.33      *FIND 'DQS Client Queues Definitions' <Return> 1        113       $! DQS Client Queues Definitions 	        $!       *INSERT <Return>eG        $ @SYS$MANAGER:DQS$DEFINE CQ_ILLINOIS -    ! Queue being definedr?                       APPLE -                     ! Server node H                       Q_CHICAGO -                 ! Queue on server nodeP                       0 -                         ! Unit number of pseudo-deviceV                       /NOENABLE_GENERIC           ! Optional qualifiers on local queue
      <Ctrl/Z>   0        113       $! DQS Client Queue Definitions
      *EXIT5      SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM;6 119 lines       $  -      METHOD 2: DEFINING GENERIC CLIENT QUEUESm=            You can define client queues to be generic queues,_=            which direct print jobs to execution queues on thed?            client for processing. Defining generic queues givesE@            you many independently targeted queues processed by aC            single symbiont. In this way, you trade off parallel jobe=            transfers for fewer processes on your client node.         PROCEDUREA            To define generic client queues, perform the following             steps:   E            __________________________________________________________ E            Step___Action_____________________________________________e  9              1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM.v  E                   You should include all generic queue definitions in E                   the SYS$MANAGER:DQS$SYSTARTUP.COM file so that they                     are permanent.          .      9-8 Configuring and Managing a DQS Client n             H               __________________________________________________________H               Step___Action_____________________________________________  B                 2    Add a definition of the execution queue. Your>                      command should have the following format:  @                      $ @SYS$MANAGER:DQS$DEFINE execution-queue -0                      _$ server-node remote-queue6                      _$ 0 /ENABLE_GENERIC[/qualifiers]  F                 3    Add the definition of the DQS$REMOTE_client-queueD                      logical name for the associated server node andD                      remote queue, in the form, server-node::remote-                      queue:y  5                      $ DEFINE/SYSTEM/EXECUTIVE_MODE - D                      _$ DQS$REMOTE_client-queue server-node::remote-                      queue  F                 4    Add the command to initialize and start the queueE                      specifying the /GENERIC qualifier. The parameterrF                      to the /GENERIC qualifier must be the name of theG                      execution queue on the client system. Your commando6                      should have the following format:  G                      $ INITIALIZE/QUEUE/START/GENERIC=execution-queue - $                      _$ client-queue  F                 5    Save the DQS$SYSTARTUP.COM file and exit from the                      editor.  H               __6____Execute_the_DQS$STARTUP.COM_procedure._____________  H               If the DQS$REMOTE_client-queue logical name is not definedF               for a generic queue, the logical name definition for theH               execution queue is used to establish the associated server$               node and remote queue.                  H                                Configuring and Managing a DQS Client 9-9 n  h                  EXAMPLEB            Example 9-3 shows how to define a generic client queue.    /      Example 9-3 Defining Generic Client Queues   H      $ @SYS$MANAGER:DQS$DEFINE D NODEC QUEUE4 0 /ENABLE_GENERIC <Return>  G      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_A NODEA::QUEUE1 <Return> 2      $ INITIALIZE/QUEUE/START/GENERIC=D A <Return>  G      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_B NODEB::QUEUE2 <Return>i2      $ INITIALIZE/QUEUE/START/GENERIC=D B <Return>  G      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_C NODEA::QUEUE3 <Return> 2      $ INITIALIZE/QUEUE/START/GENERIC=D C <Return>  D            Example 9-3 defines the generic queues A, B, and C, whichC            direct print jobs to the client execution queue D. Thereg4            is a single symbiont running for queue D.  C            o  If you print to queue A, your job transfers to server .               node NODEA, remote queue QUEUE1.  C            o  If you print to queue B, your job transfers to servert.               node NODEB, remote queue QUEUE2.  C            o  If you print to queue C, your job transfers to server .               node NODEA, remote queue QUEUE3.  C            o  If you print to queue D, your job transfers to servers.               node NODEC, remote queue QUEUE4.        EFFICIENCY SUGGESTIONC            An execution queue connects to the associated server for @            each of its generic queues. However, defining genericC            queues with the same associated server to direct jobs to 6            the same execution queue is most efficient.        FOR MORE INFORMATION_@            Refer to the OpenVMS System Manager's Manual for more)            information on generic queues.       /      9-10 Configuring and Managing a DQS Client                  0         METHOD 3: DEFINING LOGICAL CLIENT QUEUESB               Logical queues are similar to generic queues in thatD               each can have its own remote queue, independent of theH               execution queue. The difference is that you use the ASSIGND               /QUEUE command to associate the logical queue with its               execution queue.  D               The DQS software determines the associated server nodeG               and remote queue by looking for a DQS$REMOTE_client-queues2               logical name for each logical queue.           PROCEDUREiD               To define logical client queues, perform the following               steps:  H               __________________________________________________________H               Step___Action_____________________________________________  F                 1    Stop the client queue with the following command:  =                      $ STOP/QUEUE/RESET client-queue <Return>h  D                 2    Define the DQS$REMOTE_client-queue logical nameH                      for the associated server node and remote queue, inF                      the form, server-node::remote-queue. Your command6                      should have the following format:  5                      $ DEFINE/SYSTEM/EXECUTIVE_MODE -iD                      _$ DQS$REMOTE_client-queue server-node::remote-#                      queue <Return>q  E                 3    Associate the logical client queue with a clientc%                      execution queue.D  <                      $ ASSIGN/QUEUE execution-queue logical-#                      queue <Return>   -                 4    Start the logical queue.   H               _______$_START/QUEUE_logical-queue_<Return>_______________  G               If DQS$REMOTE_client-queue is not defined for the logicalrF               queue, the DQS software uses the logical name definition&               for the execution queue.  H                               Configuring and Managing a DQS Client 9-11 S  A                  EXAMPLE;            Example 9-4 shows how to define a logical queue.     /      Example 9-4 Defining Logical Client Queuesu  (      $ STOP/QUEUE/RESET QUEUE_A <Return>N      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_QUEUE_A NODEX::QUEUE_Y <Return>,      $ ASSIGN/QUEUE QUEUE_D QUEUE_A <Return>#      $ START/QUEUE QUEUE_A <Return>_  B            Example 9-4 assigns the logical client queue QUEUE_A toE            direct print jobs to the execution queue QUEUE_D, which iscD            a DQS queue. QUEUE_D processes jobs queued to QUEUE_A andB            directs them to the server NODEX, remote queue QUEUE_Y.        FOR MORE INFORMATION @            Refer to the OpenVMS System Manager's Manual for more)            information on logical queues.                                                     /      9-12 Configuring and Managing a DQS Clients    a          H         ________________________________________________________________  =         Temporarily Changing the Definition of a Client Queue                OVERVIEWE               The DQS software determines a client queue's associatedl=               server node and remote queue by translating therG               DQS$REMOTE_client-queue logical name to be the associated B               server and remote queue. The DQS$REMOTE_client-queueD               logical name is defined for a client queue by both the?               DQS$IMPORT.COM and the DQS$DEFINE.COM procedures.u           PROCEDURE A               To temporarily change the target of a client queue:   H               __________________________________________________________H               Step___Action_____________________________________________  D                 1    Stop the client queue by entering the following/                      command at the DCL prompt:e  =                      $ STOP/QUEUE/RESET client-queue <Return>e  F                 2    Redefine the DQS$REMOTE_client-queue logical name3                      at the DCL prompt by entering:n  F                      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_client-=                      queue server-node::remote-queue <Return>C  E                 3    Restart the queue at the DCL prompt by entering:   H               _______$_START/QUEUE_queue-name_<Return>__________________  >               This temporary definition of the client queue isB               lost the next time the client system reboots because>               the logical name definition was not added to the1               SYS$MANAGER:DQS$SYSTARTUP.COM file.               H                               Configuring and Managing a DQS Client 9-13 n  c                  EXAMPLEE            Example 9-5 shows how to change the definition of a clienteA            queue temporarily. This example stops the client queue C            CQ_ILLINOIS, redefines its remote node to be server nodeR?            CHERRY, remote queue Q_OHIO, and restarts the clienth            queue.     6      Example 9-5 Temporarily Changing the Remote Queue  ,      $ STOP/QUEUE/RESET CQ_ILLINOIS <Return>R      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$REMOTE_CQ_ILLINOIS CHERRY::Q_OHIO <Return>'      $ START/QUEUE CQ_ILLINOIS <Return>                                                                 /      9-14 Configuring and Managing a DQS Clientc n  _          H         ________________________________________________________________           Deleting Client Queues               PROCEDUREeD               To delete a client queue, perform the following steps:  H               __________________________________________________________H               Step___Action_____________________________________________  D                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file andC                      delete the lines that define the client queue.M  H                 2    Stop the queue by entering the following command at$                      the DCL prompt:  =                      $ STOP/QUEUE/RESET client-queue <Return>   2                 3    Delete any jobs in the queue.  >                      $ QDELETE/ENTRY=job-entry-numbers client-#                      queue <Return>i  G                 4    Delete the queue by entering the following commandx'                      at the DCL prompt:t  9                      $ DELETE/QUEUE client-queue <Return>e  5                 5    Deassign the queue logical name:C  =                      $ DEASSIGN/SYSTEM/USER DQS$REMOTE_queue- "                      name <Return>  E                      Where queue-name is the name of the client queue:H               _______that_you_deleted.__________________________________                  H                               Configuring and Managing a DQS Client 9-15 M  T          E      ________________________________________________________________S  9      Configuring Client Nodes in a VMScluster Environmentn            EXECUTE STARTUP FILENC            You must execute the SYS$STARTUP:DQS$STARTUP.COM commandu=            file on each cluster member to define the requirede@            DQS logical names on each cluster member. This actionC            makes available the DQS software to users in the clusterC*            regardless of the cluster node.        CLUSTER ALIASB            You should use an outgoing cluster alias as the name ofB            your client system. This makes the cluster appear to beD            one system to its server(s). If you do not define and useC            this cluster alias, users may switch cluster members andtE            may not be able to show, modify, or delete print jobs that             they own.                                                    /      9-16 Configuring and Managing a DQS Client                H         ________________________________________________________________  9         Synchronizing Client and Server Forms Definitions       $         ABOUT THE DQS$CLIENT PROGRAMB               You should synchronize form definitions between yourC               client and server systems. Do this by running the DQShE               client program SYS$SYSTEM:DQS$CLIENT.EXE. This requires_2               OPER, TMPMBX, and NETMBX privileges.  E               The DQS$CLIENT program looks at the queues on a client._D               For each queue, it queries the associated server(s) toE               determine what forms are defined there. DQS$CLIENT then @               defines all the server forms on the client system.           PROCEDUREl@               To synchronize forms on your DQS client and server               systems:  H               __________________________________________________________H               Step___Action_____________________________________________  H                 1    Run the DQS$CLIENT program by issuing the following                      command:_  H               _______$_RUN_SYS$SYSTEM:DQS$CLIENT_<Return>_______________  H               DQS$CLIENT synchronizes client forms with the server formsC               in alphabetical order of the client queue names. Each C               server is queried only once, regardless of the number D               of client queues associated with remote queues on that               server.t  ,         CONFLICTING SERVER FORMS DEFINITIONSA               If DQS$CLIENT finds conflicting form definitions onrD               different servers, it is not able to define both formsE               on a DQS client. For example, if one DQS server defineseC               form 3 as X and another defines 3 as Y, form 3 can be H               defined as either X or Y at a DQS client. No practical wayF               exists to determine which case of form 3, X or Y, occurs               at the client.  F               If DQS$CLIENT encounters more than one form number for aF               given form name, you may not get the results you desire.  H                               Configuring and Managing a DQS Client 9-17    _                  FORM DEFINITION OVERRIDE_D            For DQS$CLIENT to override the local form definition withA            its value on the server, you must define the DQS$FORM_s>            OVERRIDE logical name on the client system to be an            arbitrary value.v  @            If you do not define DQS$FORM_OVERRIDE on your client<            node, your local form definitions are maintained.  D            When you run DQS$CLIENT, you are notified that your localC            form definition is superseded by the server's definitione?            (with DQS$FORM_OVERRIDE defined) or remains the same_+            (DQS$FORM_OVERRIDE not defined).m        PROCEDURE?            To allow the server form definition to supersede the             client definition:   E            __________________________________________________________ E            Step___Action_____________________________________________l  D              1    Edit SYS$MANAGER:DQS$SYSTARTUP.COM file and search.                   for the following statement:  *                   $! Form Synchronization:  C              2    Uncomment the DQS$FORM_OVERRIDE logical name with$8                   an arbitrary value, for example, TRUE.  B                   $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$FORM_OVERRIDE"                   _$ TRUE <Return>  E            __3____Exit_from_the_DQS$SYSTARTUP.COM_file.______________o                        /      9-18 Configuring and Managing a DQS Cliente -  i          H         ________________________________________________________________  "         Spooling to a Client Queue               PROCEDUREDF               To spool to a DQS client queue, you must associate a LATC               port with the DQS client queue. To do so, perform the                following steps:  H               __________________________________________________________H               Step___Action_____________________________________________  +                 1    Run the LATCP utility.t  1                 2    Create the LAT port LTAnnn:.   G                      The nnn represents a number that is not already ino>                      use on your system, for example, LTA999:.  -                 3    Exit from LATCP utility.   H               __4____Set_that_LAT_port_device_spooled.__________________  E               A user-written program can then output to the specified_F               LAT port device. The program output is written to a diskG               and queued to the specified output queue when the file iso               closed.            NOTEE               If the LAT software is not started, enter the following.0               command at the OpenVMS DCL prompt:  5               $ @SYS$STARTUP:LAT$STARTUP.COM <Return>_           EXAMPLE_@               Example 9-6 shows how to set up a LAT port device.  0         Example 9-6 Setting Up a LAT Port Device  H                                                 (continued on next page)        H                               Configuring and Managing a DQS Client 9-19 E  e            5      Example 9-6 (Cont.) Setting Up a LAT Port Device         $ MCR LATCP <Return>L(      LATCP> CREATE PORT LTA999: <Return>      LATCP> SHOW PORT <Return>M      Port Name  Port Type    Status         Remote Target (Node/Port/Service)rU      ---------  -----------  -------------  ----------------------------------------- .      _LTA999:   Application  Inactive       //        LATCP> EXIT <Return>D2      $ SET DEVICE LTA999:/SPOOLED=QUEUE_Z <Return>  B            You can spool this LTA999 device to only one DQS clientC            queue at a time. Example 9-7 shows how to change the DQS B            client queue that is spooled to the LTA9999: device, byC            entering the following DCL commands where new_queue_name 3            is the name of the new DQS client queue:u  ?            Example 9-7 Changing Client Queue Spooled to LTA999:                         DeviceL  1            $ SET DEVICE LTA999/NOSPOOLED <Return> >            $ SET DEVICE LTA999/SPOOLED=new_queue_name <Return>  C            Example 9-8 shows how to use the LAT port with a FORTRAN =            program. In this example, the FOR$PRINT logical is_@            associated with the LTA999: device. In this case, theB            LTA999: device is spooled to a DQS client queue QUEUE_ZB            (see Example 9-6). When the program runs, the output is@            directed through the FOR$PRINT logical to the LTA999:@            device, and from there to the spooled queue, QUEUE_Z.  .      Example 9-8 Spooling to a LAT Port Device  E                                              (continued on next page)u                    /      9-20 Configuring and Managing a DQS ClientY A  E            9         Example 9-8 (Cont.) Spooling to a LAT Port Device/  +         $ DEFINE FOR$PRINT LTA999: <Return>1%         $ SHOW QUEUE QUEUE_Z <Return>RI           Server queue QUEUE_Z, stopped, on YOUNG::, mounted from DEFAULTN#         $ TYPE EXAMPLE.FOR <Return>L)                 print *,'This is a test.'                  endU         $ RUN EXAMPLE <Return>%         $ SHOW QUEUE QUEUE_Z <Return>/I           Server queue QUEUE_Z, stopped, on YOUNG::, mounted from DEFAULTe  =            Jobname         Username     Entry  Blocks  Statust=            -------         --------     -----  ------  ------n>            FORPRINT        YOUNG          573       1  Pending>            FORPRINT        YOUNG          573       1  Pending	         $   ?               This example shows QUEUE_Z as stopped to show thet4               submitted job in the DQS server queue.                                                  H                               Configuring and Managing a DQS Client 9-21               E      ________________________________________________________________   0      Controlling the Note on the Job Banner Page            HOW THE NOTE IS PRINTEDE            The DQS software makes use of a print attribute to place a.D            note on the banner page of a print job when logical namesC            are defined in the DQS$SYSTARTUP.COM file. On the clientsB            node, this logical name definition provides the defaultE            text "Print Job transported by DQS Vn.n". The note definedeD            by this logical name prints on the banner page of a printD            job if the /NOTE qualifier is not specified by the client*            node user on the PRINT command.  A            The note that prints on the banner page of a print jobe,            follows this order of precedence:  8            o  Note specified by the user with PRINT/NOTE  B            o  Note specified by the client logical name definition+               (DQS$CLIENT_DEFAULT_JOB_NOTE)Q  B            o  Note specified by the server logical name definition+               (DQS$SERVER_DEFAULT_JOB_NOTE)-        OPTIONS*            You have the following options:  C            o  Use the default note provided by the DQS software forr               the banner page.  A            o  Turn off the DQS logical definitions for the banner_               page note.  7            o  Define your own note for the banner page._                  /      9-22 Configuring and Managing a DQS Client  m  :                     TO TURN OFF THE DEFAULTlG               To turn off the DQS default note on the client system, do-               the following:  H               __________________________________________________________H               Step___Action_____________________________________________  A                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.F  D                 2    Search for the following command and remove the<                      exclamation mark (!) comment character:  J                      $! $ DEASSIGN/SYSTEM/EXEC DQS$CLIENT_DEFAULT_JOB_NOTE  D                 3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM andH               _______exit_from_the_editor.______________________________  6               The change takes efect the next time the6               SYS$STARTUP:DQS$STARTUP.COM is executed.           TO CHANGE NOTE TEXTRF               To change the text of the note that prints on the banner%               page, do the following:   H               __________________________________________________________H               Step___Action_____________________________________________  A                 1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file.e  6                 2    Search for the following command:  J                      $! $ DEFINE/SYSTEM/EXEC DQS$CLIENT_DEFAULT_JOB_NOTE -  3                      $!      "Place your text here"S  G                      Substitute your note for the text "Place your text E                      here" and remove the dollar sign and exclamation =                      mark ($!) at the beginning of each line.i  D                 3    Save the file SYS$MANAGER:DQS$SYSTARTUP.COM andH               _______exit_from_the_editor.______________________________  G               The next time the SYS$STARTUP:DQS$STARTUP.COM is executedMH               and the note is not specified by the user, your customized1               note prints on the job banner page.f  H                               Configuring and Managing a DQS Client 9-23 _  _          E      ________________________________________________________________f        Regulating Forms Checking            THE FORMS CHANGE TIMER ?            A part of the DQS software known as the forms change @            timer periodically checks DQS client queues to see ifD            an operator or the software, itself, has properly changed            forms.t  B            The DQS software requires a match of form types between<            the one mounted on a DQS client queue and the one2            specified for each of the queue's jobs.        LOGICAL NAMES?            Regulating the forms change timer component requires D            editing the SYS$MANAGER:DQS$SYSTARTUP.COM file and adding$            logical name definitions:  E      ________________________________________________________________qE      Logical_Name_____Parameter_Action_______________________________   D      DQS$NO_FORMS     TRUE      Turns off the forms timer on all DQS'                                 queues.Q  B                                 If a DQS client node submits a job@                                 to one of its queues and the jobC                                 requires a form that is not mountede@                                 on the queue, no data transfers,B                                 no errors occur, and the job waits-                                 indefinitely.   D      DQS$FORM_queue_  TRUE      Names a particular DQS client queue,>      name                       queue_name. You can repeat theA                                 logical definition for any numberY5                                 of DQS client queues.   E                                 If a DQS client node submits a job tocC                                 the named queue with a form that iseB                                 not mounted on the queue, the dataB                                 transfers and no errors occur. TheD                                 result is similar to having the formE      ___________________________mounted_on_the_queue.________________m  /      9-24 Configuring and Managing a DQS ClientU /  E                     PROCEDURED;               To regulate forms checking, do the following:O  H         ________________________________________________________________H         Step___Action___________________________________________________  E           1    Edit the SYS$MANAGER:DQS$SYSTARTUP.COM file to add the_                logical names._  0                Look for the following statement:  %                $! Forms Change Timer:l  B           2    Uncomment the command that defines the logical nameA                DQS$NO_FORMS to be TRUE for all DQS client queues:_  A                $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$NO_FORMS "TRUE"   @           3    Uncomment the command that defines a logical nameD                DQS$FORM_queue_name to be TRUE, where queue_name is a+                particular DQS client queue.l  H                $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$FORM_queue_name "TRUE"  G                This command applies only to the named DQS client queue. G                Repeat this command for any number of DQS client queues.n  D           4    Save the file, SYS$MANAGER:DQS$SYSTARTUP.COM and exit                from the editor.   A           5    Execute the SYS$STARTUP:DQS$STARTUP.COM procedure:   H         _______$_@SYS$STARTUP:DQS$STARTUP.COM_<Return>__________________                        H                               Configuring and Managing a DQS Client 9-25 e                     EXAMPLEA            Example 9-9 shows how to add logical names to regulateeB            forms checking on VMScluster systems with 50 clients orC            more. This examples turns off the forms change timer for C            all client queues and allows client queues LNO6_ROOM23A,_@            LPS17_NUM016, and LPS17_600_BLUE to accept print jobs3            regardless of the forms mounted on them.m    A      Example 9-9 Regulating Forms Checking on Many Client Systems         $!:      $! Forms Change Timer:       $!lM      $!   Uncomment the following logical if you desire to turn off the formsoI      $!   change timer. Digital recommends that you do this on VMSclusterw4      $!   systems with 50 or more DQS client queues.      $!t5      ! DEFINE/SYSTEM/EXECUTIVE_MODE DQS$NO_FORMS TRUEs      $!o=      $! Ignoring forms definitions on specific client queues:.      $!eN      $!   You can disable certain client queues from rejecting print jobs whenM      $!   the form mounted on the client queue differs from  the form mountedrR      $!   on the remote queue.  Define a logical of the form DQS$FORM_queue_name .S      $!   This allows the client queue, 'queue_name' ,  to accept and process jobs,gJ      $!   regardless of the form mounted on the remote queue. For example:      $!_      $!_@      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$FORM_LNO6_ROOM23A "TRUE"@      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$FORM_LPS17_NUM016 "TRUE"B      $ DEFINE/SYSTEM/EXECUTIVE_MODE DQS$FORM_LPS17_600_BLUE "TRUE"  C            After adding these logical name definitions to the site-hA            specific startup file DQS$SYSMANAGER:DQS$SYSTARTUP.COMi2            and executing the DQS startup procedureE            SYS$STARTUP:DQS$STARTUP, the DQS software no longer checksl@            for forms mismatches between each named queue and its            jobs.            /      9-26 Configuring and Managing a DQS Cliente                       H                                                                       10H         ________________________________________________________________  H                                                          Troubleshooting                 ABOUT THIS CHAPTER?               This chapter provides some general guidelines for E               troubleshooting apparent problems with the DQS software 4               and suggests recovery procedures when:  3               o  Remote notification is not workingQ  G               o  Jobs remain in the remote queue with completion statusa  &               o  A job is not printing  A               o  Large numbers of DQS client queues slow down thee                  network  F               The guidelines are not meant to cover all possible errorF               conditions, but are intended to help you understand some                common situations.                                  H                                                     Troubleshooting 10-1 n  F          E      ________________________________________________________________i  '      General Troubleshooting Guidelinese            WHAT TO DO FIRSTQB            If something fails to work with the DQS software, check            these first:c  B            o  Determine whether your DQS configuration has changed               recently.   C            o  Run the DQS Installation Verification Procedure (IVP)sB               located in SYS$TEST:DQS$IVP.COM. It may confirm thatA               the DQS software is functioning properly, or it mayR)               detect the error condition.   D            o  Check that the DQS$STARTUP.COM procedure is invoked in'               the system start-up file,E  B               -  SYS$STARTUP:SYSTARTUP_V5.COM for OpenVMS VAX V5.n                  systems  C               -  SYS$STARTUP:SYSTARTUP_VMS.COM for OpenVMS VAX V6.nu0                  systems and OpenVMS AXP systems  A               DQS$STARTUP.COM starts the DQS software and invokes D               procedures that define the required DQS logical names.D               If the DQS$VERSION system logical name is not defined,A               then this may be the cause of your error condition.   C            o  On client nodes, check that queues are defined in thee1               SYS$MANAGER:DQS$SYSTARTUP.COM file._  E            o  On server nodes, check that remote queues are set up in_9               the SYS$MANAGER:DQS$SERVER_CONFIG.TXT file.S                        10-2 Troubleshooting                H         ________________________________________________________________           Running the IVPn               COMMAND E               You can execute the Installation Verification ProcedureTH               (IVP) to check if the DQS software is running properly. To!               run the IVP, enter:>  .               $ @SYS$TEST:DQS$IVP.COM <Return>           IVP ON A CLIENT NODEH               Following is a sample of an IVP run on a node with the DQS)               client software configured._  5          DQS V1.3 Installation Verification Procedurei  S           Restricted Rights: Use, duplication, or disclosure by the U.S. GovernmentqO           is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofdS           DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as_           applicable._  R           This software is proprietary to and embodies the confidential technologyO           of Digital Equipment Corporation. Possession, use, or copying of thistS           software and media is authorized only pursuant to a valid written licensen4           from Digital or an authorized sublicensor.  H               For a client-only node, the following prompt is displayed:  M         It is necessary to test the DQS client with a remote DQS server node.   (         Enter remote server NODE::QUEUE:  H               Enter the name of a server node and a remote queue on thatG               node. For example, to test the proper operation of servereA               queue Q_CHICAGO on node APPLE, enter the following:   H               Enter remote server NODE::QUEUE APPLES::Q_CHICAGO <RETURN>  G               For the IVP to succeed on a client-only installation, theA#               following must exist:_  E               o  A remote queue on the server node that is accessible G                  from the client system (see the chapter on configuring H                  a DQS server in the Chapter 8 for information on making+                  server queues accessible).i  H                                                     Troubleshooting 10-3 v               ?            o  The DQS$IVP_TEST_FORM on the server node. If this A               form no longer exists on the server node, enter the 8               following DCL commands on the server node:  4               $ DEFINE/FORM DQS$IVP_TEST_FORM 1110 -3                       /STOCK = DQS_IVP_TEST_STOCK - L                       /DESCRIPTION = "DQS test form, do not delete" <Return>  A            Then, if the DQS software is working properly. the IVP ?            displays a series of messages (this may take severalc            minutes), such as:n  1            %DQS-I-CRESRVQUE Creating remote queue 1            %DQS-I-CRECLIQUE Creating client queuen1            %DQS-I-CHKCLIQUE Checking client queueQ:            %DQS-I-ENTJOB Entering test job in client queue<            %DQS-I-CHECKJOB Checking test job in client queue4            %DQS-I-SNDJOB Sending job to remote queue=            %DQS-I-CHKSRVQUE Checking test job in remote queue 7            %DQS-I-DELJOB Deleting job from remote queue D            %DQS-I-CHKDEL Checking that job is gone from remote queue:            %DQS-I-CLEANUP Cleaning up, deleting IVP queues0            %DQS-I-QUESUCCESS IVP test successful        IVP ON A SERVER NODE E            Following is a sample of an IVP run on a node with the DQS &            server software configured.  2       DQS V1.3 Installation Verification Procedure  P        Restricted Rights: Use, duplication, or disclosure by the U.S. GovernmentL        is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofP        DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as        applicable.  O        This software is proprietary to and embodies the confidential technologyuL        of Digital Equipment Corporation. Possession, use, or copying of thisP        software and media is authorized only pursuant to a valid written license1        from Digital or an authorized sublicensor.   A            Then, if the DQS software is working properly. the IVPE?            displays a series of messages (this may take several:            minutes), such as:           10-4 Troubleshooting     r            4               %DQS-I-CRESRVQUE Creating remote queue4               %DQS-I-CRECLIQUE Creating client queue4               %DQS-I-CHKCLIQUE Checking client queue=               %DQS-I-ENTJOB Entering test job in client queue ?               %DQS-I-CHECKJOB Checking test job in client queue 7               %DQS-I-SNDJOB Sending job to remote queue @               %DQS-I-CHKSRVQUE Checking test job in remote queue:               %DQS-I-DELJOB Deleting job from remote queueG               %DQS-I-CHKDEL Checking that job is gone from remote queue =               %DQS-I-CLEANUP Cleaning up, deleting IVP queuesW3               %DQS-I-QUESUCCESS IVP test successfule    )         FOR INFORMATION ON ERROR MESSAGES @               If the DQS IVP encountered problems, the procedureF               displays error messages. Refer to Appendix B, DQS SystemC               Manager Messages for an explanation of specific error                messages.o                                                      H                                                     Troubleshooting 10-5 N             E      ________________________________________________________________n  =      Problem: Remote Notification Is Not Working for Any Jobsn            ACTIONf>            If remote notification is not working check for the            following:/  @            o  The DQS$NOTIFIER process is running on the server.  >            o  The network object DQS is defined on the client.  A            o  The client node is defined in the server node's NCP @               database for DECnet Phase IV systems or the serverA               node's NCL database for DECnet/OSI Phase V systems.o  D            o  If the client node is in a cluster, make sure that theE               DQS software is properly configured on all nodes of the                cluster.                                                        10-6 Troubleshooting2 o  g          H         ________________________________________________________________  E         Problem: Notification of Print Job Completion Is Not Occuringd         for Some Jobso               ACTIONB               The DQS$NOTIFIER searches the node for all known DQSE               server queues when it starts. If you define a new queue D               as a valid DQS server queue, you must stop and restartE               the DQS$NOTIFIER process to enable print job completion H               messages of jobs submitted to the new queue. The simpliest/               way to do this is to restart DQS.A  3               If the DQS$NOTIFIER is not restarted:M  C               o  Print jobs remain in the DQS server queue with the.(                  retained attribute set.  5               o  The temporary files are not deleted.   D               o  The user is not notified when the job is completed.                                              H                                                     Troubleshooting 10-7               E      ________________________________________________________________t  D      Problem: Jobs Remain in the Remote Queue With Completion Status            ACTIONY  C            o  Make sure that the DQS$NOTIFIER process is running onh               the server.   A            o  If the server is a member of a VMScluster system in-@               which the queues are not common across the clusterB               members, check the definition of the DQS$NOTIFY_LOCK5               logical name as described in Chapter 8.n                                                                    10-8 Troubleshooting                H         ________________________________________________________________  &         Problem: A Job Is Not Printing               INFORMATION YOU NEED@               To determine why a print job does not appear to beC               printing, you need to determine the following for thep               job:  D               o  The status; is it in the process of printing on the7                  server node? Is it stopped or stalled?_  F               o  The location; is it in the client queue or the remote                  queue?R           USING THE QSHOW COMMAND B               To obtain this information, issue a QSHOW command atD               the client system of the client queue to which the jobF               was queued for printing. The output of the QSHOW commandF               provides information on both the status and the location               of the print job.t  #         EXAMINING THE QSHOW DISPLAYdD               The output of the QSHOW command is designed to provideB               all the information you need to determine the statusE               and location of a print job. The command output usuallynD               appears as follows, showing the location of the job on5               either the client or the server system:c  @          ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]          Terminal queue Q_PARISa  K          ==============================to be transferred=================== 5          Server queue CQ_EUROPE, mounted form DEFAULT   =            Jobname         Username     Entry  Blocks  Status =            -------         --------     -----  ------  ------ ?            JOB             GUENTHER      2737       1  Printing             H                                                     Troubleshooting 10-9    e            '      UNDERSTANDING LOCATION INFORMATION C            Note that the client queue and remote queue are referredaA            to in the command output as the "Server queue" and theiD            "Remote queue," respectively. This terminology is tied toB            the OpenVMS concept of served queues. For the DQS QSHOW            command,   9            o  Server queue refers to the DQS client queuee  9            o  Remote queue refers to the DQS remote queueh  =            When the QSHOW command output contains informationcA            for both the client and remote queues (as shown in thenE            preceding display) you should first decide whether the job_C            is in the client queue, in the remote queue, or neither.E        LOCATION: NEITHER NODED?            If the job is not in either the client or the remote 9            queue, then the following possibilities exist:_  *            o  The job printed and is lost.  @            o  The user printed to a different queue or printed a               different job.  @            o  The actual printer was different from the expectedB               one. The system manager or the DQS software may have@               rerouted the request to another available printer.  B            If you suspect a DQS problem, examine the NETSERVER.LOGE            files in the DQS server account's directory or, if OpenVMS"=            accounting is enabled, check the accounting files.o        LOCATION: SERVER NODEA            If the job is located on the server node, then the DQSpD            software has functioned properly. If the job still is not<            printing, then the following possibilities exist:  A            o  It may be pending because of form or characteristica               problems.m  B            o  It may be held or waiting to print after a specified               time.n  A            Check that the printer is on line, powered on, and hase            paper in it.C        10-10 Troubleshooting $  Y                     LOCATION: CLIENT NODE_B               If the job is still located on the client node, thenA               examine the status of the client queue in the QSHOWAD               output. The queue status is either stopped or stalled.    (         UNDERSTANDING STATUS INFORMATIONA               You see the following status if there is a problem:t  D               o  Stopped: If the queue is stopped, the QSHOW commandE                  output contains the reason for stopping the queue ifoE                  the DQS software stopped the queue. The queue may bemH                  stopped because the remote system is unknown or because@                  the client node is denied access to the server.  D                  Check the OPCOM output or the OPERATOR.LOG file for:                  messages regarding why the queue stopped.  E               o  Stalled: Stalled means that the DQS symbiont has not G                  sent a checkpoint message to the job controller within F                  the timeout limit of the stall timer. This could meanF                  that the server is running slowly. It could also meanF                  that the DQS symbiont failed to connect to the server?                  and is in the process of retrying the connect.   F                  Check for the OPCOM message "Remote system off line."  E                  Disk problems on the server can also cause a stalledm                  state.e  G                  The stalled state is transient and requires no special$D                  attention. The DQS software automatically tries theE                  job every five minutes. Generally, this action alone7,                  corrects the stalled state.  D               Any of the following indicate that the client queue is&               operational and running:  D               o  Printing: Indicates that the job is transferring toD                  the server node. This may signify that the user wasE                  impatient, that the server system was overloaded, or C                  that the transfer is slow. This status is shown as                   follows:     H                                                    Troubleshooting 10-11 _  _            =       ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]        Terminal queue Q_PARIS  H       ==============================to be transferred===================2       Server queue CQ_EUROPE, mounted form DEFAULT  :         Jobname         Username     Entry  Blocks  Status:         -------         --------     -----  ------  ------<         JOB             MACOMBER      2738       1  Printing  C            o  Pending: Indicates that the job cannot be transferred =               for some reason local to the client system. YoueA               can determine the reasons for this pending state by                entering:n  .               $ QSHOW/FULL queue-name <Return>  ;               Possible reasons for a pending status are theo               following:  C               -  A characteristic was used to print the job that is +                  not enabled for the queue.1  E                  In this case, add the appropriate characteristics to_=                  the queue or remove them from the print job.   B               -  The form type mounted for the queue may not match5                  the form type specified for the job.   E                  In this case, the DQS software automatically changes                   forms.   .               This status is shown as follows:  =       ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]a       Terminal queue Q_PARIS  H       ==============================to be transferred===================2       Server queue CQ_EUROPE, mounted form DEFAULT  :         Jobname         Username     Entry  Blocks  Status:         -------         --------     -----  ------  ------;         JOB             DAVIES        2739       1  Pending   C            o  Holding: Indicates that the job cannot be transferred E               because the user specified that the job should be held.U.               This status is shown as follows:        10-12 Troubleshooting t  r            @          ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]          Terminal queue Q_PARIS   K          ==============================to be transferred=================== 5          Server queue CQ_EUROPE, mounted form DEFAULT   =            Jobname         Username     Entry  Blocks  Statuse=            -------         --------     -----  ------  ------ >            JOB             WOODWARD      2740       1  Holding  @               o  Holding until: Indicates that the job cannot beD                  transferred because the user specified that the jobD                  should be held until after the specified time. This,                  status is shown as follows:  @          ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]          Terminal queue Q_PARIS   K          ==============================to be transferred=================== 5          Server queue CQ_EUROPE, mounted form DEFAULTn  =            Jobname         Username     Entry  Blocks  Status =            -------         --------     -----  ------  ------ D            JOB             SMITH         2741       1  Holding untilN                                                               1-Jan-1994 01:00  C               o  Retained on completion: Indicates that the job has5G                  transferred to the server system. This status is shown                   as follows:  @          ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]          Terminal queue Q_PARIS   K          ==============================to be transferred===================r5          Server queue CQ_EUROPE, mounted form DEFAULT   =            Jobname         Username     Entry  Blocks  Statusn=            -------         --------     -----  ------  ------Q?            JOB             SCHULLMAN     2742       1  RetainedsK                                                               on completiono  D               o  Retained on error: Indicates that the job failed toC                  transfer to the server system because of the errorr$                  shown with the job.  H                                                    Troubleshooting 10-13                 ?               The user should correct the problem and retry thee7               request. This status is shown as follows:o  <      ** Remote queue - [ CQ_EUROPE => Q_PARIS, on CHERRY:: ]      Terminal queue Q_PARISn  G      ==============================to be transferred===================g1      Server queue CQ_EUROPE, mounted form DEFAULT   9        Jobname         Username     Entry  Blocks  Statust9        -------         --------     -----  ------  ------TD        JOB             TIMLEGE       2743       1  Retained on error(          %JBC-E-NOSUCHFORM, no such form        THE REMOTE QUEUE DISPLAYhD            Issuing a QSHOW command for a client queue sometimes doesD            not show job status information because either the remoteD            queue or the server node is inaccessible. In these cases,=            you see the following in the QSHOW command output:   )            o  No remote queue informations  >            o  A message explaining why the remote queue is not               reachabler  %      MISSING REMOTE QUEUE INFORMATION B            When the remote queue information does not display whenD            you issue a QSHOW command, it means that the DQS softwareC            does not view the client queue as a valid DQS queue. The 2            command output would appear as follows:  2       Server queue CQ_EUROPE, mounted form DEFAULT  :         Jobname         Username     Entry  Blocks  Status:         -------         --------     -----  ------  ------;         JOB             CHO           2744       1  Pendingu  B            In this case, you should issue a QSHOW/FULL command forD            the queue. If the command output contains the informationA            /PROCESSOR=DQS$SMB, invoke the DQS$STARTUP.COM file toQ1            define the queue as a valid DQS queue.   A            You can also check the DQS$REMOTE_client-queue logicalnE            name definition for the client queue. It should be defined)D            system wide and in executive mode to be the corresponding(            server node and remote queue.        10-14 Troubleshooting i  r            2         ERROR MESSAGES IN THE REMOTE QUEUE DISPLAYG               In some cases, the QSHOW command output contains an errorwE               message that cites a reason why the remote queue is not E               accessible. The command output would appear as follows:   @          ***** Remote queue CHERRY::Q_PARIS not accessible *****J              %SYSTEM-F-UNREACHABLE, remote node is not currently reachable  P          ==============================to be transferred========================5          Server queue CQ_EUROPE, mounted form DEFAULTC  E               The following is a list of error messages that might bee<               displayed when a remote queue is inaccessible:  F               o  -DQS-F-BADNODE, specified node has been denied access                   to this server.  /         %DQS-W-MSG_REMOTE, remote system error:CM         -DQS-F-BADNODE, specified node has been denied access to this server. G         %SYSTEM-F-LINKDISCON, network partner disconnected logical linkr  H                  Explanation: The specified queue is not accessible withD                  the DQS software because the client system has been:                  specifically denied access to the server.  E                  User Action: Check with the server system manager toaF                  remove the client's node name from deny status in the,                  DQS$SERVER_CONFIG.TXT file.  A               o  -DQS-F-BADQUE, specified queue not valid for DQS                   access.  /         %DQS-W-MSG_REMOTE, remote system error: 8         -DQS-F-BADQUE, specified queue not valid for DQS         access._  O         ==============================to be transferred======================== 4         Server queue CQ_EUROPE, mounted form DEFAULT  H                  Explanation: The specified queue is not accessible withH                  the DQS software. Either the client's node name was notF                  added to the access list or the remote queue does not                  exist.   E                  User Action: Check with the server system manager to 4                  determine the reason for the error.  H                                                    Troubleshooting 10-15                 E            o  %SYSTEM-F-INVLOGIN, login information invalid at remotel               node  <      ***** Remote queue CHERRY::Q_PARIS not accessible *****E          %SYSTEM-F-INVLOGIN, login information invalid at remote node_  L      ==============================to be transferred========================1      Server queue CQ_EUROPE, mounted form DEFAULT   D               Explanation: The server account information may not be               defined properly.   A               User Action: Make sure the server's password in theD?               network object database on the server matches the$@               password in the UAF. Also, make sure the owner andD               UIC of the server's directory is the server's account.  =            o  -DQS-E-NOTSTARTED, DQS has not been started yetN  ,      %DQS-W-MSG_REMOTE, Remote system error:4      -DQS-E-NOTSTARTED, DQS has not been started yet  H       ==============================to be transferred===================2       Server queue CQ_EUROPE, mounted form DEFAULT  B               Explanation: The DQS software was not started on the               server.   E               User Action: Ask the server system manager to start the D               DQS software. After the DQS software is started, thereB               may be a delay of up to five minutes before jobs are               transferred.  :            o  %SYSTEM-F-NOSUCHNODE, remote node is unknown  =       ***** Remote queue CHERRY::Q_PARIS not accessible *****f6           %SYSTEM-F-NOSUCHNODE, remote node is unknown  H       ==============================to be transferred===================2       Server queue CQ_EUROPE, mounted form DEFAULT  ?               Explanation: The server node is not known to your                client node.  D               User Action: Either add the server node to your DECnetD               node database or change the node name to a known node.        10-16 Troubleshooting    n            B               o  %SYSTEM-F-NOSUCHOBJ, network object is unknown at                  remote node  @          ***** Remote queue CHERRY::Q_PARIS not accessible *****J              %SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node  K          ==============================to be transferred=================== 5          Server queue CQ_EUROPE, mounted form DEFAULT   D                  Explanation: Either the specified node is not a DQSD                  server node or the DQS server has not been started.  F                  User Action: Change the node to a DQS server or start3                  the DQS server on the server node.Q  D               o  %SYSTEM-F-UNREACHABLE, remote node is not currently                  reachable  @          ***** Remote queue CHERRY::Q_PARIS not accessible *****J              %SYSTEM-F-UNREACHABLE, remote node is not currently reachable  K          ==============================to be transferred===================n5          Server queue CQ_EUROPE, mounted form DEFAULT   F                  Explanation: The server is not on the network. If theE                  job is in the queue, it is transferred to the server[9                  soon after the server becomes reachable.u  E                  User Action: Wait until the server becomes reachable=E                  or queue your print job to a remote queue on another                   server node.U                            H                                                    Troubleshooting 10-17               E      ________________________________________________________________   :      Problem: Many DQS Client Queues Slow Down the Network            ABOUT THE PROBLEM?            A part of the DQS software known as the forms changeuC            timer periodically checks DQS client queues to see if an C            operator or the software has properly changed forms. ThelB            DQS software requires a match of form types between theB            one mounted on a DQS client queue and the one specifiedD            for each of the queue's jobs. This checking can slow downD            the overall performance of a VMScluster system with 50 or"            more DQS client queues.        ACTIONbB            To increase performance of systems with many DQS clientD            queues, you can turn off the forms change timer component>            of the DQS software. As a result, the software cutsA            forms-checking operations to a minimum and performancec>            is improved. Digital recommends that you do this on@            VMScluster systems with 50 or more DQS client queues.  ?            Regulating the forms change timer component requires D            editing the SYS$MANAGER:DQS$SYSTARTUP.COM file and adding>            logical name definitions DQS$NO_FORMS and DQS$FORM_C            queue_name. For information, refer to the section titledn2            Regulating Forms Checking in Chapter 9.                                        10-18 Troubleshooting h  Q                  H                                                                 Part IIIH         ________________________________________________________________  H                                                       Installation Guide                     OVERVIEWD               This part describes how to install the DQS software onB               OpenVMS AXP and OpenVMS VAX systems using either theD               POLYCENTER Software Installation (PCSI) utility or theD               VMSINSTAL installation utility. The Installation GuideB               is intended for the network or system manager who is6               responsible for installing the software.    $         USING THE INSTALLATION GUIDEB               You can use either the PCSI utility or the VMSINSTAL.               utility to install the software.  A               Refer to the following flowchart to determine which E               sections of this guide are relevant to the installationo)               utility that you are using.o m                     H                                                                       11H         ________________________________________________________________  H                                                    What You Need to Know                 ABOUT THIS CHAPTERA               This chapter describes what you need to know beforeeH               installing the DEC Distributed Queuing Service for OpenVMSE               Systems (DQS) software on an OpenVMS AXP or OpenVMS VAX ;               system. Table 11-1 lists the topics included.a  H               Table_11-1_Summary:_What_You_Need_to_Know_________________  H               Topic__Title______________________________________________  3                 1    Required hardware and softwaret                   2    Licensing  &                 3    Processes created  ;                 4    First-time installation considerationsg  +                 5    Upgrade considerationse  H               __6____Time_required_to_install___________________________                          H                                               What You Need to Know 11-1 i  r                  RELATED INFORMATION>            Chapter 12 describes what you need to do before you$            install the DQS software.  =            Chapter 13 describes how to install the DQS client @            and server software with the PCSI utility. Chapter 14=            describes how to install the DQS client and server /            software with the VMSINSTAL utility.   <            Refer to Part II, the System Manager's Guide, forB            information on how to set up and manage DQS software on6            client and server nodes after installation.        FOR INFORMATION ON TERMSs?            This guide refers to DQS server nodes, client nodes, @            remote queues, and client queues. For a definition ofC            these terms and concepts, refer to Chapter 7 in Part II, &            the System Manager's Guide.                                                            11-2 What You Need to KnowU E  o          H         ________________________________________________________________  &         Required Hardware and Software               HARDWARE REQUIRED C               DQS software can be installed on any Alpha AXP or VAXI               processor.  !         OPERATING SYSTEM VERSIONS E               Installation of DEC Distributed Queuing Service VersionnB               1.3 for OpenVMS systems software requires one of the               following:  F               o  OpenVMS VAX Operating System, Version 5.5-2 or higher  D               o  OpenVMS AXP Operating System, Version 6.1 or higher  H               Future DEC Distributed Queuing Service for OpenVMS SystemsC               releases may require higher versions of the operatingtE               system, as described in the online release notes or thej#               product cover letter.e  !         OPENVMS TAILORING CLASSES B               The OpenVMS operating system comes with a variety ofF               support options, or tailoring classes. Tailoring classesE               include such features as networking and RMS journaling. A               For full functionality of this layered product, thee7               following tailoring classes are required:=  )               o  OpenVMS Required Saveset                   o  Network Support  *               o  Secure User's Environment                    H                                               What You Need to Know 11-3                       PREREQUISITE PRODUCTS>            Table 11-2 provides information on the software youC            must have installed on your system before installing DQSh            software.    E            Table_11-2_Prerequisite_Software__________________________   E            Prerequisite_Products___Purpose___________________________R  D            DECnet for OpenVMS      Networking software; Required forE            Systems, V5.5 (Phase    DQS client to server and server to 7            IV) or DECnet/OSI for   client communication              OpenVMS Systems, V5.6E            (Phase_V)_________________________________________________         FOR MORE INFORMATIONO8            For a complete list of the supported hardwareC            configurations, required operating system components andrC            software, see the DQS Software Product Description (SPD)e@            included with your distribution kit. In addition, theD            SPD contains a complete list of prerequisite and optional7            software and their required version numbers.                                                   11-4 What You Need to Know                H         ________________________________________________________________           LicensingS               REQUIREMENTSE               The DQS product supports the OpenVMS License ManagementSD               Facility (LMF) provided by OpenVMS systems. Before youH               can start the DQS software, LMF requires that you registerC               a License Product Authorization Key (License PAK) foraE               the product. The License PAK is shipped with the kit ifaE               you ordered a license and media together; otherwise, itRC               is shipped separately to a location specified by your=E               license order. Use the LMF utility to register and loaduF               the information from your License PAK into your system's               license database.   E               Traditionally, each node that executes the DQS softwareB!               requires a license.            FOR MORE INFORMATIONF               Refer to the DEC Distributed Queuing Service for OpenVMSA               Systems Software Product Description (SPD) for more B               information on DQS licensing. For information on howD               to license DQS software after it is installed, see the8               OpenVMS License Management Utility Manual.                                      H                                               What You Need to Know 11-5 f  o          E      ________________________________________________________________a        Processes Created            CLIENT NODES=B            On a client node, every client queue you create that is?            not a generic or logical queue, creates one process.n@            Also, the system creates a temporary process when theD            DQS software notifies the user of a print job completion.        SERVER NODES C            On server nodes, every incoming connection from a client ?            node results in the creation of a process. Also, theoC            notification process on a server node uses one permanento            process.o                                                                11-6 What You Need to Know  O  o          H         ________________________________________________________________  .         First-time Installation Considerations      *         REGISTRATION OF PRODUCTS WITH PCSIA               If you are installing the DQS product with the PCSIiA               utility, then any software product required for DQS F               installation must also be registered in the PCSI productG               database. Products installed with installation procedurese@               other than the PCSI utility, such as the VMSINSTAL?               utility, cannot be registered in the PCSI product-               database.            FOR MORE INFORMATIONA               For information on how to determine if products areuA               registered in the PCSI database and how to registereF               products in the database, see the section titled Perform?               First-Time Installation Activities in Chapter 12.                                                     H                                               What You Need to Know 11-7 c  n          E      ________________________________________________________________e        Upgrade Considerationss            NEW STARTUP FILE 9            Version 1.3 of the DQS software provides a newR@            DQS$STARTUP.COM command procedure. Your older version@            of DQS$STARTUP.COM file is copied to DQS$STARTUP.COM_:            OLD. The new startup procedure does not contain;            DQS queue definitions or definitions for logicalo?            names that you can change. Instead an editable file,e@            SYS$MANAGER:DQS$SYSTARTUP.TEMPLATE, is provided where?            you can make changes to DQS logical name definitionstC            and define client queues. You copy this file by changingm5            .TEMPLATE to .COM and making your changes.a  :            Whenever, you execute the DQS startup procedureD            SYS$STARTUP:DQS$STARTUP.COM, it invokes the site-specific;            startup procedure SYS$MANAGER:DQS$SYSTARTUP.COM.t  )      NEW SECURITY AND QUEUE ACCESS SYSTEMrC            Version 1.3 of the DQS software provides a new method to B            define a set of accessible server queues and to control"            access to these queues.  >            During the installation procedure, the DQS softwareA            attempts to use information from the currently runningsC            system to convert your server queue definitions into theeD            new security and queue access system. This conversion mayA            not be correct even though it is successful. After theaC            installation you need to validate that your server queue #            definitions are correct.   	      NOTE C            Make sure that the DQS software is running on the serveryC            node when you are installing server software. ConversionS@            of your current server queue definitions into the newA            security and queue access system requires this. If DQSEB            software is not running you have the following options:  >            o  Stopping the installation, executing the startup8               procedure, and restarting the installation          11-8 What You Need to Know  u  o            D               o  Manually entering your server queue definitions andD                  client access information after the installation is                  complete.    H         FOR MORE_INFORMATION____________________________________________"               For more informationH               on_._._.______________Refer_to_._._.______________________  .               Validating the        Chapter 15"               conversion of server               queue definitions   D               Adding or changing    Part II, System Manager's Guide,E               DQS logical name      Chapter 8, Defining Server System 1               definitions           Logical Nameso  D               Setting up client     Part II, System Manager's Guide,G               node access to        Chapter 8, Setting Up Remote Queuess               remote queues onH               server_nodes______________________________________________                                                H                                               What You Need to Know 11-9               E      ________________________________________________________________e        Time Required to Install=  :            Depending on your type of media and your system1            configuration, DQS installation takes:   ?            o  About 10 minutes, if you are installing using the                VMSINSTAL utility   C            o  About 5 minutes, if you are installing using the PCSI                utility                                                                            11-10 What You Need to Know                       H                                                                       12H         ________________________________________________________________  H                                                            Do This First                 ABOUT THIS CHAPTER?               This chapter describes what you need to do before H               installing the DEC Distributed Queuing Service for OpenVMSE               Systems (DQS) software on an OpenVMS AXP or OpenVMS VAXyE               system. Table 12-1 summarizes the preinstallation taskso(               described in this chapter.  H               Table_12-1_Preinstallation_Task_Summary___________________  H               Task___Description________________________________________  1                 1    Inspect the distribution kitF  0                 2    Review the DQS installation  8                 3    Prepare for VMScluster installation  3                 4    Log in to a privileged accountm  4                 5    Access the online release notes  5                 6    Determine process account quotasr  )                 7    Determine disk spacee  7                 8    Set up an alternate working deviceS  *                 9    Register your license  :                10    Perform system maintenance procedures  ?                11    Perform first-time installation activities   H               _12____Back_up_your_system_disk___________________________  H                                                       Do This First 12-1 =  =          E      ________________________________________________________________   !      Inspect the Distribution Kit             DQS FOR OPENVMS AXP KITB            For OpenVMS AXP systems, the distribution kit contains:  A            o  DQS software on a layered-product compact disc (CD-                ROM).b  >            o  DQS documentation in text and PostScript format,?               provided with the software on the layered producte               CD-ROM.   3               -  Software Product Description (SPD)   D               -  DEC Distributed Queuing Service for OpenVMS Systems                  Cover Letter_  D               -  DEC Distributed Queuing Service for OpenVMS Systems"                  Documentation Set  2               -  Software Performance Report (SPR)  @            o  DQS documentation in an online format, provided onA               the software layered products documentation CD-ROM. A               (Hardcopy documentation can be ordered separately.)                                         12-2 Do This First                           DQS FOR OPENVMS VAX KIToE               For OpenVMS VAX systems, the distribution kit contains:n  H               o  Bill of materials (BOM) and indented bills report (BIL)  D               o  Media containing the DQS client and server software  '                  -  TK50 streaming tapeQ  2                  -  9-track 1600 BPI magnetic tape  '               o  Hardcopy Documentation   6                  -  Software Product Description (SPD)  G                  -  DEC Distributed Queuing Service for OpenVMS Systemsv                      Cover Letter  G                  -  DEC Distributed Queuing Service for OpenVMS Systems %                     Documentation Sete  5                  -  Software Performance Report (SPR)N  ?               Contact your Digital representative if any of thei1               components of your kit are missing.e  F               The DQS client and server software and documentation areD               also available online on the Consolidated Distribution               CD-ROM.                                 H                                                       Do This First 12-3 _  _          E      ________________________________________________________________         Review DQS Installation            BEFORE STARTINGE            Before you begin the installation, review the installationl            procedure.   4            o  See Chapter 13 for the PCSI procedure.  9            o  See Chapter 14 for the VMSINSTAL procedure.I        OPTIONS3            You can select to set up your system as:n  %            o  A DQS server and cliente              o  A DQS client  A            A DQS server system can accept print requests from DQS C            client systems. DQS client systems initiate remote printi            requests.  B            When you select the DQS server option, the installation2            procedure also provides client support.                                            12-4 Do This First  t  i          H         ________________________________________________________________  +         Prepare for VMScluster Installation                OVERVIEWC               The DQS software operates in VMScluster environments._D               Printing within the VMScluster system does not requireD               the DQS software. However, printing between VMSclusterH               systems requires that you install the DQS software on each               VMScluster.r  !         VMSCLUSTER CONSIDERATIONSmF               When installing the DQS software on a VMScluster system,%               plan for the following:a  E               o  All DQS software files are placed in the clusterwide_B                  system directories by the installation procedure.  .               o  The DQS software startup fileD                  SYS$STARTUP:DQS$STARTUP.COM must be executed duringB                  system startup on each node within the VMScluster;                  system where you want DQS software to run.i  G               o  The DQS installation procedure defines the DQS network_F                  object on the cluster member that you are logged intoH                  when installing the DQS software. The definition of the>                  network object enables the cluster member to:  G                  -  Receive notification messages from the DQS$NOTIFIEReD                     indicating the completion status of a particular"                     print request.  D                  -  Act as a DQS server if you choose the DQS server                     option.i                    H                                                       Do This First 12-5 o  o          E      ________________________________________________________________a  #      Log In to a Privileged AccountM            PRIVILEGES NEEDED?            To install DQS software, you must be logged in to an <            account that has SETPRV or at least the following            privileges:              o  CMKRNL              o  WORLDa              o  SYSPRV              o  SYSNAM              o  OPER              o  NETMBX              o  TMPMBX  =            Digital recommends that you use the system manager_@            account, SYSTEM. This account provides the privilegesE            necessary to register your Product Authorization Key (PAK)y(            and install the DQS software.                                        12-6 Do This Firstt a  n            $         DETERMINE ACCOUNT PRIVILEGES;               Determine your account privileges as follows:e  H               __________________________________________________________H               Step___Action_____________________________________________  E                 1    Check the default privileges of the installationr@                      account. Log in and enter this DCL command:  7                      $ SHOW PROCESS/PRIVILEGES <Return>r  G                      If the account lacks the SETPRV privilege, proceedr                      to step 2.L  0                 2    Do either of the following:  C                      o  Ask your system manager to use AUTHORIZE tosG                         modify the default privileges of the account to 5                         include the SETPRV privilege.i  G                      o  Run AUTHORIZE and make the changes yourself, if >                         your account has the SYSPRV privilege:  6                      $ SET DEFAULT SYS$SYSTEM <Return>,                      $ RUN AUTHORIZE<Return>)                      UAF> MODIFY account-h5                      name/PRIVILEGES=(SETPRV)<Return>E&                      UAF> EXIT<Return>  F                 3    To activate the change in privileges, log out andH               _______then_log_in_again._________________________________                            H                                                       Do This First 12-7 e  _          E      ________________________________________________________________e         Access Online Release Notes            REVIEW THE NOTESs=            The DQS product provides online release notes. You @            should review the release notes because they describeB            new features and differences among multiple versions ofC            the DQS software, as well as changes in the installationd            procedure.u        FOR MORE INFORMATIONyD            For information on how to access the release notes before8            or after a PCSI installation, see Chapter 13.  D            For information on how to access the release notes during=            or after a VMSINSTAL installation, see Chapter 14.r                                                            12-8 Do This Firstt u  e          H         ________________________________________________________________  (         Determine Process Account Quotas               MINIMUM REQUIREMENTSG               Table 12-2 lists the minimum quotas that the installation <               utility requires for the installation account.  H               Table_12-2_Process_Quotas_for_the_Installation_Account____                 ASTLM     24                 BIOLM     18                 BYTLM     18,000                 DIOLM     18                 ENQLM     30  H               FILLM_____20______________________________________________  #         TO VERIFY AND CHANGE VALUESyD               Use the OpenVMS Authorize utility to verify and changeE               process quotas for the installation account in the user G               authorization file (SYSUAF.DAT). (Some sites may restrict,A               the use of the OpenVMS Authorize utility to certaina"               accounts or people.)                                H                                                       Do This First 12-9 e  o                  EXAMPLEE            To verify and then change the BYTLM quota for the account-hC            name installation account, you might enter the followingt            command sequence:  E            __________________________________________________________ E            To_._._.______________Enter_._._._________________________f  D            Invoke the            $ RUN SYS$SYSTEM:AUTHORIZE <Return>            Authorize utility  @            Show the account      UAF> SHOW account-name <Return>            quotaso  B            Modify the BYTLM      UAF> MODIFY account-name /BYTLM =/            quota                 18000 <Return>   3            Exit the Authorize    UAF> EXIT <Return>o            utility  2            Log out               $ LOGOUT <Return>  E            Log in to activate    Perform the login procedure for yournE            the_new_quotas________system._____________________________c        FOR MORE INFORMATIONeD            For more information on modifying account quotas, see theE            description of the Authorize utility in the OpenVMS Systemo+            Management documentation subkit._                                      12-10 Do This First I  a          H         ________________________________________________________________           Determine Disk Space               REQUIREMENTSH               DQS requirements for free disk storage space are differentE               during installation than after installation. Table 12-3 G               summarizes the storage requirements. The numbers provided G               are approximate. Installation and use of the DQS softwaretF               should not require more than the number of blocks listed               in Table 12-3.  H               Table_12-3_Disk_Space_Requirements________________________  <               Operating        Blocks During    Blocks AfterH               System___________Installation_____Installation____________  4               OpenVMS AXP      4500             2300  H               OpenVMS_VAX______2700_____________1300____________________  *         EXTRA FOR SERVER ACCOUNT DIRECTORYF               In addition, the disk where the server account directoryF               is located requires extra space for temporary storage ofE               files queued for printing. Disk space for storing fileseC               to be printed does not have to be on the system disk.rE               See Chapter 8 for information on how to move the server 2               account directory to another device.           PROCEDURESH               To determine the number of free disk blocks on the currentA               system disk, enter the following command at the DCLS               prompt:r  2               $ SHOW DEVICE SYS$SYSDEVICE <Return>                  H                                                      Do This First 12-11                       FOR MORE INFORMATIONrB            If you need to create free disk space, refer to the theA            OpenVMS Upgrade and Installation Manual or the OpenVMSp/            DECwindows Motif Installation Guide.D  B            If you need to move the server account to another disk,D            refer to Chapter 15, the section entitled Move the Server/            Account Directory to Another Device.n                                                                                12-12 Do This First Q  o          H         ________________________________________________________________  *         Set Up an Alternate Working Device               REASONA               The DQS software installation requires fewer blocks B               of free disk space if you create a temporary working/               directory on an alternate device.r           BEFORE YOU BEGINF               You have the option of creating the working directory onE               the alternate device before you begin the installation.aG               For example, to create the working directory [INSTALL] onu/               the alternate device DUA2, enter:n  8               $ CREATE/DIRECTORY DUA2:[INSTALL] <Return>           OPTIONSgE               Consider the following when deciding whether to specifytC               a temporary working directory when installing the DQSh               software.1  H               __________________________________________________________H               If_you_._._._____Then_the_installation_utility_._._.______  E               Specify a        Creates a working subdirectory for the C               directory        product and then deletes the working B                                subdirectory after the installation)                                completes.   B               Do not specify   Creates the working subdirectory onD               a directory      the specified device with a directoryF                                specification of [000000.facvvu], whereB                                facvvu represents the facility nameE                                and version number of the product. The G                                installation utility deletes the workingpB                                subdirectory after the installation)                                completes._            H                                                      Do This First 12-13               E            ___________________________________________________________E            If_you_._._._____Then_the_installation_utility_._._.______T  B            Specify a        Creates the directory that you specifyC            nonexistent      and the working subdirectory. After the D            directory        installation completes, the installationD                             utility deletes the working subdirectoryE            _________________but_does_not_delete_the_directory._______                                                                                   12-14 Do This First                          EXAMPLESD               You can enter the following command to install the DQS<               software using an alternate working directory:  "               o  With PCSI utility  Q                  $ PRODUCT INSTALL DQS/VERSION=1.3 /WORK=DUA2:[INSTALL]  <Return>a  '               o  With VMSINSTAL utility   Y                  $ @SYS$UPDATE:VMSINSTAL DQS013 MUA0: OPTIONS AWD=DUA2:[INSTALL] <Return>m  H               __________________________________________________________               Where . . .iH               __________Is_._._.________________________________________  C               DUA2:     The alternate working device name, for this                           example.  C               [INSTALL] For this example, the name of the directorys@                         on the alternate working device in whichD                         the installation utility creates the productH               __________subdirectory.___________________________________            USING A DFS-MOUNTED DISKB               You can specify a DFS-mounted disk as your alternateC               working device. However, the DFS client (installationaG               procedure) is unable to determine available disk space on H               the DFS-mounted disk and incorrectly reports a total of -1               free blocks.  F               Before using a DFS-mounted disk, determine its free diskF               space. Log in to the system on which the disk is locally,               mounted and enter the command:  $               $ SHOW DEVICE <Return>  C               Refer to Table 12-3 for the amount of free disk space F               that must be on the DFS-mounted disk to complete the DQS               installation.           H                                                      Do This First 12-15 b             E      ________________________________________________________________v        Register Your License            REQUIREMENTC            The DQS product supports the License Management FacilityDD            (LMF) provided by the OpenVMS systems. Before you can runD            the DQS IVP and start the DQS software, LMF requires thatD            you register a License Product Authorization Key (LicenseD            PAK) for the product. License PAK information is providedC            with the DQS product. Register and load this information E            into your system's license database using the LMF utility.H        PROCEDURE$            To register your license:  E            __________________________________________________________ E            Step___Action_____________________________________________m  A              1    Log in to the system manager's account, SYSTEM.a  C              2    You then have a choice of two ways to perform thea                   registration:o  D                   o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure.A                      When it prompts you for information, responde9                      with the data from your License PAK.n  7                   $ @SYS$UPDATE:VMSLICENSE.COM <Return>c  B                   o  At the DCL prompt, enter the LICENSE REGISTERA                      command with the appropriate qualifiers that ?                      correspond to the License PAK information.e  -                   $ LICENSE REGISTER <Return>c  E                   Add information carefully. The utility may return a C                   checksum error message if you omit or incorrectlytC                   enter any license data. Check characters typed oneE            _______each_line,_not_just_the_checksum_string.___________               12-16 Do This First                          FOR MORE INFORMATIONH               For complete information on using the LMF utility, see the8               OpenVMS License Management Utility Manual.                                                                                    H                                                      Do This First 12-17 r  d          E      ________________________________________________________________S  *      Perform System Maintenance Procedures      
      OVERVIEW A            This section explains how to use the System Generation C            utility (SYSGEN) and the AUTOGEN utility to prepare your D            system for installation of the DQS software. AUTOGEN uses@            system configuration data to automatically set system            parameters.        REQUIRED VALUESB            Table 12-4 lists the minimum required system parametersB            for the installation. These values do not represent theA            number required to run your system and other software.c  E            Table_12-4_Minimum_Required_System_Parameter_Values_______a  5            System        OpenVMS AXP      OpenVMS VAXrE            Parameters____Values___________Values_____________________   .            GBLPAGES       1500             600  E            GBLSECTIONS______10_______________5_______________________h  :            If your your system does not have the necessaryA            global pages and global section SYSGEN parameters, ther            installation fails.  /      CHECK GLOBAL PAGES AND SECTIONS PARAMETERSrD            To install and run DQS software, you must have sufficient@            free global pages and global sections. First find outC            how many free global pages and sections you have on yours?            system. Then use AUTOGEN if you need to increase thee>            global pages and global sections system parameters.  =            To check the values of the global pages and globalcB            sections parameters, use the DCL WRITE command with the0            F$GETSYI lexical function as follows:                12-18 Do This First e  f            <               $ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")               7578  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")               143   F               If the SYSGEN values displayed by the system are greaterC               than the values listed in Table 12-4, you do not needhA               to increase them. If the values of the global pages D               and global sections parameters displayed by the systemE               are less than the values listed in Table 12-4, you must_A               increase their values. Proceed to the next section.   3         CHANGE GLOBAL PAGES AND SECTIONS PARAMETERS @               Use the AUTOGEN command procedure to change systemB               parameters. AUTOGEN automatically adjusts values forF               parameters that are associated with the values you reset               manually.R  H               __________________________________________________________H               Step___Action_____________________________________________  <                 1    Edit the SYS$SYSTEM:MODPARAMS.DAT file.  E                 2    Modify incremental parameters, such as these, byfF                      typing ADD_parameter in the file, where parameter0                      is GBLPAGES or GBLSECTIONS.  H                      For example, to increase the global pages parameterF                      by 2000, add this line in the MODPARAMS.DAT file:  (                      ADD_GBLPAGES = 2000  E                 3    After making your changes, exit from the editor.e                      H                                                      Do This First 12-19               E            __________________________________________________________nE            Step___Action_____________________________________________L  >              4    Execute the AUTOGEN procedure to recalculate?                   your system parameters. The following command A                   recalculates your system parameters and reboots                    the system:   ?                   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT <Return>   >                   When you specify REBOOT, AUTOGEN performs an@                   automatic system shutdown and then reboots the?                   system. Any users logged on to the system are>C                   immediately disconnected during the shutdown. ThemE                   automatic reboot puts the new parameter values into E            _______effect.____________________________________________d                                                                  12-20 Do This First                 C               The AUTOGEN utility automatically adjusts some of the7E               SYSGEN parameters based on the consumption of resources_?               since the last reboot. If you do not want to take A               advantage of this automatic adjustment, include theaC               NOFEEDBACK qualifier on the AUTOGEN command line. Fore               example,  F               $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK <Return>           FOR MORE INFORMATIONG               For more information about using the AUTOGEN utility, see F               the OpenVMS System Manager's Utilities Reference Manual.                                                                  H                                                      Do This First 12-21 f             E      ________________________________________________________________   /      Perform First-Time Installation Activities             PCSI UTILITY_?            These activities apply if you are installing the DQS *            software with the PCSI utility.  '      REGISTER PRODUCTS IN PCSI DATABASElE            The PCSI utility checks for software products required fortC            installation and use of the DQS software. These products2>            need to be registered in the PCSI product database.  ?            For example, DQS installation requires either of theL            following:   C            o  OpenVMS VAX operating system, Version 5.5-2 or higher_  A            o  OpenVMS AXP operating system, Version 6.1 or higherR  D            To determine if the required operating system software isB            registered and to register the product, if required, do            the following:         USING THE MOTIF INTERFACED            Perform the following steps to check the operating system            software on Motif:i  E            __________________________________________________________ E            Step___Action_____________________________________________   >              1    Enter the PRODUCT command at the DCL prompt.  $                   $ PRODUCT <Return>  C                   The PCSI Main menu displays the Show Product List $                   window by default.  @              2    Scroll through the list of installed products.A                   Search for DEC AXPVMS VMS V6.1 or higher or DEC @                   VAXVMS VMS V5.5-2 or higher. If your operatingC                   system (or other required software) is not in the B                   list, you must register the product. See Step 3.        12-22 Do This First Y  c          H               __________________________________________________________H               Step___Action_____________________________________________  D                 3    Pull down the Mode menu and select the REGISTERH                      PRODUCT command. Enter the product name and versionH               _______of_the_product_to_register.________________________                                                                                H                                                      Do This First 12-23 m               )      USING THE DCL COMMAND LINE INTERFACE D            Perform the following steps to check the operating system            software from DCL:_  E            __________________________________________________________SE            Step___Action_____________________________________________e  E              1    Enter the PRODUCT SHOW PRODUCT product-name command $                   at the DCL prompt.  6                   $ PRODUCT SHOW PRODUCT *VMS <Return>  C              2    Search the list for DEC AXPVMS VMS V6.1 or higheru5                   or DEC VAXVMS VMS V5.5-2 or higher.   E                   If the required operating system (or other requiredmE                   software) is not in the SHOW PRODUCT list, then youu;                   need to register the product. See Step 3.t  A              3    Enter the PRODUCT REGISTER PRODUCT product-name0E                   command at the DCL prompt. For example, to register31                   OpenVMS VAX Version 6.0, enter:A  .                   $ PRODUCT REGISTER PRODUCT -E            ________$_VMS/VERSION=6.0_/SOURCE=SYS$UPDATE:_<Return>____e                                              12-24 Do This First r  i          H         ________________________________________________________________            Back Up Your System Disk               OVERVIEWF               Near the beginning of the installation, the installationG               utility asks if you completed the pre-installation tasks.eH               Digital recommends that you do a system disk backup beforeE               installing any software. Use the backup procedures that +               are established at your site.            FOR MORE INFORMATIONA               For details on performing a system disk backup, see E               the section on the Backup utility in the OpenVMS Systemi.               Management documentation subkit.           TO PROCEEDF               Before proceeding with the installation of the software,1               refer to the flowchart in Part III.o                                                  H                                                      Do This First 12-25 t                     H                                                                       13H         ________________________________________________________________  H                                                   Using the PCSI Utility                 ABOUT THIS CHAPTERD               This chapter provides information about the POLYCENTERH               Software Installation utility (PCSI) and the procedure forH               installing the DEC Distributed Queuing Service for OpenVMSG               Systems software. Table 13-1 lists the tasks described in                this chapter.o  H               Table_13-1_PCSI_Installation_Task_Summary_________________  H               Task___Description________________________________________  ,                 1    Accessing release notes  =                 2    Starting the installation: DCL interfacei  '                 3    Obtaining DCL Help   E                 4    Determining installation defaults: DCL interface   C                 5    Verifying preinstallation tasks: DCL interface_  ;                 6    Stopping and restarting: DCL interfacet  ;                 7    Responding to questions: DCL interfaceC  E                 8    Determining installation progress: DCL interfaceo  ?                 9    Starting the installation: Motif interfaces  )                10    Obtaining Motif Help   ?                11    Selecting product options: Motif interfaceC  =                12    Stopping and restarting: Motif interface   H               _13____Recovering_from_errors_____________________________  H                                              Using the PCSI Utility 13-1 s  s          E      ________________________________________________________________u        Accessing Release Notes            PROCEDUREE            To extract a copy of the release notes for the DQS productr$            to an online disk, enter:  V      $ PRODUCT EXTRACT RELEASE_NOTES DQS /VERSION=Vn.n /FILE=output-file-name <Return>              Where:1  B            o  The Vn.n represents the version number. For example,*               V1.3 stands for Version 1.3.  B            o  The output-file-name is the name you provide for the!               release notes file.   <            By default the PCSI utility searches the locationD            defined by PCSI$SOURCE. If the software kit is in anotherE            location, this location must be specified with the /SOURCE )            qualifier on the command line._  g      $ PRODUCT EXTRACT RELEASE_NOTES DQS /VERSION=Vn.n /SOURCE=location /FILE=output-file-name <Return>   @            After extracting the release notes to a file, you canA            print or view the file. You do not need to install thei9            software before you extract the release notes.o        AFTER THE INSTALLATION D            After you install DQS software, type or print the release            notes file from:<  (            SYS$HELP:DQSnnn.RELEASE_NOTES  B            The nnn represents the version number. For example, 013"            stands for Version 1.3.                     13-2 Using the PCSI Utility _  _          H         ________________________________________________________________  0         Starting the Installation: DCL Interface               COMMAND TO USEF               To start the installation of the DQS software, enter the8               PRODUCT INSTALL command at the DCL prompt.  B               If this is the first time you are installing the DQSH               software, include the /HELP qualifier on the command line.H               /HELP provides detailed explanations about the product andH               product options. When you perform subsequent installationsG               or upgrades, you can choose to bypass the explanations toi               save time.  C               The following command installs Version 1.3 of the DQS 2               software with detailed explanations:  =               $ PRODUCT INSTALL DQS/VERSION=1.3 /HELP<Return>o  A               The installation utility displays messages like thep9               following and asks if you want to continue:   7         $ PRODUCT INSTALL DQS/VERSION=1.3 /HELP<Return> 0         The following product has been selected:1         DEC [AXP|VAX]VMS DQS Vn.n     [Available]   .         Do you want to continue [YES] <Return>  N         *** DEC [AXP][VAX]VMS DQS Vn.n: DEC [AXP][VAX]VMS DQS Vn.n for OpenVMS  N             Requires from nnn to nnn disk blocks depending upon configuration.  L             The DEC Distributed Queuing Service for OpenVMS Systems uses theI             DECnet networking system to extend the standard OpenVMS queue K             system to enable users to print jobs connected to other systemseM             than their own, and to show the status of, cancel, and change theh:             specifications of their jobs on those systems.  :             Copyright  1994 Digital Equipment Corporation  P             All Rights Reserved. Unpublished rights reserved under the copyright&             laws of the United States.
             .u
             .i
             .P  H                                              Using the PCSI Utility 13-3 _  _                  SPECIFYING KIT LOCATIONB            You can specify the location (source) of the DQS kit in            one of two ways:   >            o  If you install your product kits from a location@               defined by the PCSI$SOURCE logical name, make sure?               that the DQS kit is in this location. By default,EC               the PCSI utility searches the location defined by ther'               PCSI$SOURCE logical name.t  E               For example, this command defines DISK$:[LOCAL_KITS] asLC               the device and directory that contains products to be                installed:  >               $ DEFINE PCSI$SOURCE DISK$:[LOCAL_KITS] <Return>  <               For this example, the DQS kit should reside inA               DISK$:[LOCAL_KITS] to use the default location. You @               do not need to include the location on the command               line:r  8               $ PRODUCT INSTALL DQS/VERSION=n.n <Return>  D            o  If the DQS kit is not in the default location, includeB               the /SOURCE qualifier on the PRODUCT INSTALL command               line:   E               $ PRODUCT INSTALL/SOURCE=MUA0: DQS/VERSION=1.3 <Return>r  C               For this example, MYDISK$:[NEW_PRODUCTS] contains the '               DQS kit for installation.                                    13-4 Using the PCSI Utility                          COMMAND LINE FEATURES B               You can also request features like purging files andC               running the installation verification procedure (IVP)sE               by adding appropriate qualifiers to the PRODUCT INSTALLoE               command line. Table 13-2 lists features you can controlN&               with command qualifiers.    B               Table 13-2 Features You Can Request When Starting anH               ___________Installation___________________________________  H               Feature_________________Qualifier_________________________  +               Display full            /HELPr               descriptions               of all product"               installation options               and information   *               Display log messages    /LOG               on your terminal  +               Save previous           /KEEPr!               versions of product_               files during an_               upgradeA  -               Include a remark in     /REMARKE"               the product database  7               Specify where the       /SOURCE=dev:[dir]o!               distribution kit iso               locatedc  -               Choose not to run       /NOTESTt               the installation               verification               procedure (IVP)u  2               Specify a work area     /WORK=deviceH               for_temporary_files_______________________________________        H                                              Using the PCSI Utility 13-5    y                  FOR MORE INFORMATIONoE            For more detailed information on all features that you can C            request when starting an installation, refer to DCL helpe+            for the PRODUCT INSTALL command.                                                                                          13-6 Using the PCSI Utility R             H         ________________________________________________________________           Obtaining DCL Help               DCL HELP OPTIONS;               The following DCL help options are available:g  H               __________________________________________________________H               Option_Action_____________________________________________  G                 1    Include the /HELP qualifier on the PRODUCT INSTALL "                      command line.  C                 2    During the installation, press the Help key ortD                      enter a question mark in response to a question+                      from the PCSI utility.   G                 3    Type the DCL command HELP PRODUCT, followed by the F                      name of a PCSI command (for example, HELP PRODUCTH               _______INSTALL).__________________________________________                                                H                                              Using the PCSI Utility 13-7               E      ________________________________________________________________d  5      Determining Installation Defaults: DCL Interface       
      OVERVIEW_E            During installation, the PCSI utility allows you to acceptSA            or change the defaults. Default values are enclosed inh            brackets ([]).         DQS DEFAULT VALUES C            The DQS software offers you the option to install or notG@            install the server software on the system. The clientA            software is always installed. The initial installation 6            default is to install client software only.  I      The DQS client software will be installed automatically on this node_  F      Do you want to install the DQS server software on this node? [NO]  B            If you are installing the DQS software on a system thatC            has a printer that you want to make available to clients D            on other systems, then you enter YES and press the Return            key.   B            This action changes the default value for this questionB            to YES. The next time you install the DQS software, the            question is:u  I      The DQS client software will be installed automatically on this nodes  G      Do you want to install the DQS server software on this node? [YES]d                                 13-8 Using the PCSI Utility p             H         ________________________________________________________________  6         Verifying Preinstallation Tasks: DCL Interface               VERIFY TASKSE               During the installation procedure, you are asked if youtG               completed the preinstallation tasks for the DQS software.e  U          You need to complete the pre-installation tasks to install the DQS software.n&          Do you want to continue [YES]  %         TASKS CHECKED BY PCSI UTILITY B               The PCSI utility might verify that any or all of the;               following is true, depending on your product:   ;               o  You are logged in to a privileged account.I  A                  It is good practice to install software from theyF                  system manager's account with your default device and-                  directory set to SYS$UPDATE.   9               o  Disk space for installation is adequate.   H                  If sufficient disk space is not found, the installation:                  procedure provides the following options:  H                  -  You can restart the installation and specify anotherF                     disk to use as an alternate working device for theC                     temporary working directory. See Chapter 12 forBE                     information about how to use an alternate working                      device.   G                  -  You can abort the installation and then create morerF                     disk space on the system disk. The OpenVMS UpgradeH                     and Installation Manual and OpenVMS DECwindows MotifD                     Installation Guide describe how to use tailoringE                     utilities so that you can delete files and createe$                     more disk space.  H                  If you lack sufficient free disk space for installationE                  or have no other disk to use as an alternate working ;                  device, the installation procedure aborts.t    H                                              Using the PCSI Utility 13-9 _  _            =            o  OpenVMS AXP Version 6.1 or higher is installed._  ?            o  OpenVMS VAX Version 5.5-2 or higher is installed.t  B            When the PCSI utility detects a problem in any of theseD            areas, it asks if you want to terminate the installation.A            If you want to stop the installation, press the Returnl2            key. If you want to continue, enter NO.        NOT CHECKED BY PCSI UTILTYoC            The PCSI utility does not check process quotas or systemiB            parameters. You need to make sure that these values are            sufficient.  C            You must also make sure that the DQS software is runningFE            if you are upgrading from a version of the software before_>            Version 1.3 and you are installing server software.                                                        !      13-10 Using the PCSI Utilityc h  E          H         ________________________________________________________________  .         Stopping and Restarting: DCL Interface  3               To stop and restart the installation:   H               __________________________________________________________H               Step___Action_____________________________________________  H                1     To stop the procedure at any time press <Ctrl/Y> or  E                      if you are asked if you want to continue, answer_                      NO.  C                2     To retry the installation procedure, enter the_H                      PRODUCT INSTALL command as described in the sectionH               _______titled_Starting_the_Installation:_DCL_Interface.___                                                          H                                             Using the PCSI Utility 13-11               E      ________________________________________________________________p  +      Responding to Questions: DCL Interface             VALID RESPONSES?            The following are valid responses to questions askedr"            during an installation:  D            o  Press the Help key or enter a question mark to request=               additional information provided by the product.   <            o  Enter your own value and press the Return key.  =            o  Press the Return key to accept a default value.I        QUESTIONS YOU ARE ASKEDD            While installing the DQS software with the DCL interface,@            you might be asked the following questions. (Refer to:            Appendix F to see sample installation dialogs.)  &            o  If you want to continue:  6               -  Verify the product(s) being installed  -      The following product has been selected:h(      DEC VAXVMS DQS V1.3     [Available]  #      Do you want to continue? [YES]   D               -  Verify that you completed all preinstallation tasks  Q      You need to complete the pre-installation tasks to install the DQS software.I#      Do you want to continue? [YES]   >            o  If you want to accept the default values for the               product:  ?      Do you want all the default values for this product? [YES]i  B            o  If you want to install the DQS server software (thatB               is, does this node have an attached printer that youE               want to set up to accept print jobs from users on nodes                 in other systems):  F      Do you want to install the DQS server software on this node? [NO]  9               Client software is automatically installed.   !      13-12 Using the PCSI Utility_ _  _            2               o  If you want to view your choices:  ,         Do you want to view the values? [NO]  G                  If you want to view your answers to the quesions asked B                  during the installation, answer YES and press the                  Return key.  8         Do you want to view the values [NO] YES <Return>  L         DEC VAXVMS DQS V1.3: DEC VAXVMS DQS V1.3 for OpenVMS     [Available]/             DEC VAXVMS VMS V6.0     [Available]lL             Do you want to install the DQS server software on this node: YES  3             Are you satisfied with the values [YES]   F                  If you are satisfied with your selections, answer YESF                  and press the Return key. The installation of the DQS$                  software continues.  F                  If you are not satisfied with your selections, answerE                  NO to this question. You now have the opportunity top@                  make new selections or to end the installation.  ?             Are you satisfied with the values [YES] NO <Return>g  A             Do you want to re-enter the values [YES] YES <Return>n  7                 *** DEC VAXVMS VMS V6.0     [Available]   ?             Did you complete the pre-installation tasks for DQSt)             Do you want to continue [YES]             .            .            .                    H                                             Using the PCSI Utility 13-13               E      _________________________________________________________________  5      Determining Installation Progress: DCL Interface_      
      PROGRESSR>            As an installation procedure progresses, the system<            displays a percentage to indicate how much of the-            installation is done. For example:L  G      Portion Done: 10%...20%...30%...40%...50%...70%...80%...90%...100%W.      The following product has been installed:      DEC VAXVMS DQS V1.3	         . 	         .s	         .e  D            If you started the installation using the /LOG qualifier,;            the system displays details of the installation.                                                     !      13-14 Using the PCSI Utilityh o  a          H         ________________________________________________________________  2         Starting the Installation: Motif Interface               COMMAND TO USEF               To start the installation of the DQS software, enter theA               SET DISPLAY and PRODUCT commands at the DCL prompt.u  .               $ SET DISPLAY/CREATE/NODE=mynode                $ PRODUCT <Return>           PCSI MAIN WINDOW;               The PCSI main window opens (see Figure 13-1).   =               The items in this window include the following:   H         ________________________________________________________________H         This_Item..._____Displays...____________________________________  /         Title bar        The name of the windows  <         Menu bar         The menu names for the PCSI utility  D         The Product      The list of software products available for%         List box         installation   F         The Product and  An asterisk (*) wildcard, which indicates allF         Version fields   versions of all products are displayed in theH         _________________Product_List_box_______________________________                              H                                             Using the PCSI Utility 13-15 i                     PROCEDURE TO INSTALL B            Use the following procedure to install the DQS software7            using the Motif interface (see Figure 13-2):   C            1. From the Main Menu, pull down the Mode menu and clickn>               on Installation The software installation window               displays.i  B            2. Double-click on the button to the left of DEC AXPVMSB               DQS Vn.n (for OpenVMS AXP systems) or DEC VAXVMS DQSE               Vn.n (for OpenVMS VAX systems). (You may have to scroll (               to find the product name.)  D               The Selected Product list box then displays either DECE               AXPVMS DQS Vn.n or DEC VAXVMS DQS Vn.n to be installed.u  E            3. If the DQS distribution kit is located in a place other]?               than the default (that is, other than a directoryd@               pointed to by the PCSI$SOURCE logical name), enterD               the device and directory in the Source field and click#               on the Filter button.s  E            4. Click on the Install box at the bottom of the screen toc'               install the DQS software.h  B            5. When the installation is complete, you can return to@               the Install Product List screen by clicking on theE               Start New Operation box in the Work in Progress window.i                                  !      13-16 Using the PCSI Utility     a                                                                                                      H                                             Using the PCSI Utility 13-17 I  N          E      ________________________________________________________________n        Obtaining Motif Help             MOTIF HELP OPTIONSl:            The following Motif help options are available:  E            __________________________________________________________iE            Option_Action_____________________________________________e  7              1    Choose On Context from the Help menu.o  E                   For a description of objects and labels in the mainCD                   window, move the resulting ? to a screen object or&                   label and click MB1.  6              2    Choose On Window from the Help menu.  C                   For a description of how fonts are used to convey E                   different types of information, double click on the B                   Display Conventions topic. Double click on otherA                   help topics for information on how to perform aR                    specific task.  C              3    Double click on option names that are preceded by A                   a right arrow =  in the Selected Products to be %                   Installed list box.A  E                   For a full description of suboptions (if provided),NC                   continue clicking on the resulting right arrow =  /                   that precedes each suboption.C  A              4    Choose On Help from the Help menu to learn more E            _______about_using_the_online_help_system.________________         MOTIF HELP TOPICSD            Motif help describes how to get started performing a task$            from the Motif interface.  E            __________________________________________________________ E            Step___Help_Topic_________________________________________e  "             1     Select the task.  .             2     Select one or more products.  )             3     Select product options._  !      13-18 Using the PCSI Utility_ _  _          H               __________________________________________________________H               Step___Help_Topic_________________________________________  H               _4_____Start_the_task.____________________________________             FOR MORE INFORMATIONB               For information about how you can customize menus byD               adding and removing menu items, refer to the Customize'               help topic for each menu.                                                                         H                                             Using the PCSI Utility 13-19 a  c          E      ________________________________________________________________n  /      Selecting Product Options: Motif Interfacer            HOW TO SELECTC            After you select the product, you can select and displayeA            information about product options by clicking on icons C            or by choosing items from the Options menu. You can also E            double-click on the options name to get a full descriptioni            of the option.         AVAILABLE OPTIONS0            The DQS product offers these options:  .            o  Install the client software only  4            o  Install the client and server software  @            The client software is always installed, but does notE            need to be configured for a server node. Choose to install_B            the server software if your node has a printer that youD            want to make available to clients on other systems in the            network._                                          !      13-20 Using the PCSI Utility_ _  _          H         ________________________________________________________________  0         Stopping and Restarting: Motif Interface               PROCEDURE 3               To stop and restart the installation:o  H               __________________________________________________________H               Step___Action_____________________________________________  H                1     To stop the procedure at any time press <Ctrl/Y> or0                      click on the Cancel button.  @                2     To retry the installation procedure, selectF                      Installation from the PCSI utility Mode pull-downE                      menu as described in the section titled Starting_H               _______the_Installation:_Motif_Interface._________________                                                      H                                             Using the PCSI Utility 13-21    a          E      ________________________________________________________________         Recovering from ErrorsS            HOW TO RECOVER C            This section describes how to recover from errors during              product installation.  B            If the installation procedure fails for any reason, the*            following message is displayed:  -            %PCSI-E-OPFAILED, operation failedi1              Terminating is strongly recommended.s,              Do you want to terminate? [YES]  D            An error during the installation can occur if one or more-            of the following conditions exist:s  8            o  The operating system version is incorrect.  +            o  Disk space is not sufficient.   ;            o  The OpenVMS Help library is currently in use.a  B            o  System parameters are not set to the correct values.  B            If you receive any error message beginning with %PCSI-,C            refer to OpenVMS System Messages and Recovery ProceduresdD            Reference Manual for an explanation and possible solution            to the problem.  C            Most DEC Distributed Queuing Service for OpenVMS Systems_E            software messages have the same format as standard OpenVMS /            system messages: %DQS-E-ident, text.   :            If the installation fails, you must restart theC            installation procedure. If the installation fails due tosE            an IVP failure, contact a Digital Services representative.             !      13-22 Using the PCSI Utilityo a  n                  H                                                                       14H         ________________________________________________________________  H                                              Using the VMSINSTAL Utility                 ABOUT THIS CHAPTERC               This chapter provides information about the VMSINSTAL C               installation utility and the procedure for installingdE               the DEC Distributed Queuing Service for OpenVMS SystemssD               software. Table 14-1 lists the tasks described in this               chapter.  H               Table_14-1_VMSINSTAL_Installation_Task_Summary____________  H               Task___Description________________________________________  ,                 1    Accessing release notes  8                 2    Starting the installation procedure  G                 3    Stopping and restarting the installation procedureu  9                 4    Responding to installation questionse  H               __5____Following_installation_progress____________________                            H                                         Using the VMSINSTAL Utility 14-1 l  i          E      ________________________________________________________________s  +      Accessing Release Notes with VMSINSTAL             DURING THE INSTALLATION=            You can read or print the DQS release notes before >            installating the DQS software. To do this, you must@            include OPTIONS N on the command line when you invoke#            the VMSINSTAL procedure:i  <      $ @SYS$UPDATE:VMSINSTAL DQS013 MUA0: OPTIONS N <Return>  @            OPTIONS N allows you to select release notes options:  H      Release notes included with this kit are always copied to SYS$HELP.  )         Additional Release Notes Options:a  &              1.  Display release notes$              2.  Print release notes              3.  Both 1 and 2w"              4.  None of the above  "      * Select option [3]: <Return>  E            __________________________________________________________t            Enter . . .E            __________VMSINSTAL_._._._________________________________q  A            1 or 3    Displays the release notes at your terminal.h  D            2 or 3    Prompts you for a print queue name for printing3                      the release notes, as follows:   5                      Queue name [SYS$PRINT]: <Return>   @                      Enter a queue name or press the Return key.>                      Remember, to print the release notes, youB                      must have a printer attached to the system onD                      which you are installing the DQS software. (YouE                      cannot use the DQS software to print the releasetB                      notes until after the software is installed.)A                      VMSINSTAL queues a copy of the release notes_@                      to print and displays a message such as the                      following:r  J                      Job DQS013 (queue queue, entry nnn) started on device  %      14-2 Using the VMSINSTAL Utility2               H               __________________________________________________________               Enter . . .sH               __________VMSINSTAL_._._._________________________________  E               4         Copies the product release notes to SYS$HELP. H               __________Release_notes_are_neither_displayed_or_printed._                                                                                H                                         Using the VMSINSTAL Utility 14-3                 D            Digital recommends that you read the release notes before:            installing the DQS software for the first time.  >            After you have answered the questions regarding the4            release notes, this message is displayed:  G            * Do you want to continue the installation [N]? YES <Return>   @            Enter YES or NO, as appropriate. If you enter YES andB            press the Return key, the procedure continues with this            message:   `      %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.        AFTER THE INSTALLATIONiD            After the installation procedure completes, release notes5            are available from the following location:X  (            SYS$HELP:DQSnnn.RELEASE_NOTES  B            The nnn represents the version number. For example, 013"            stands for Verison 1.3.                                              %      14-4 Using the VMSINSTAL Utility     t          H         ________________________________________________________________  +         Starting the Installation Procedurea               BEFORE YOU STARTD               Before you start the installation of the DQS software,F               log in to the system manager account. The system managerG               account has the necessary privileges to run the VMSINSTALo               utility.  +         LOGGING YOUR INSTALLATION PROCEDURElB               If you want to save a copy of your VMSINSTAL session@               for future reference, you can enter the SET HOST 0C               /LOG command at the system prompt before starting theyE               installation of the software. This creates the log file <               SETHOST.LOG in your current default directory.           COMMAND LINEF               To start the installation of the DQS software, enter the2               following command at the DCL prompt:  T               $ @SYS$UPDATE:VMSINSTAL DQSnnn dev: [OPTIONS N,AWD=dev:[dir]] <Return>  G               @SYS$UPDATE:VMSINSTAL invokes the VMSINSTAL procedure. InwG               addition, you can supply the following information in ther               command line:e  ?               DQSnnn      Refers to the DEC Distributed QueuingoF                           Service for OpenVMS Systems saveset. The nnnE                           represents the version number. For example, 6                           013, stands for Version 1.3.  H               dev:        Is the device where your distribution media is"                           mounted.                    H                                         Using the VMSINSTAL Utility 14-5                   C            OPTIONS N   Causes VMSINSTAL to ask you about displaying 5                        or printing the release notes.   =                        Digital recommends that you review they@                        release notes before you proceed with the@                        installation of the software in case theyB                        contain information about the installation.  A                        If you are restarting the installation andiC                        have already reviewed the release notes, you 8                        do not need to specify OPTIONS N.  @                        Release notes are installed on the system<                        whether or not you specify OPTIONS N.  <            OPTIONS     Lets you specify an alternate workingD            AWD=dev:[dir]irectory for the temporary working directoryB                        used by VMSINSTAL during installation. WithE                        this option, fewer free blocks are required oni'                        the system disk.   @                        The dev:[dir] names the alternate workingA                        device and directory under which VMSINSTAL_B                        creates its working directory. Specifying a2                        directory name is optional.  C                        If you do not specify this option, VMSINSTAL >                        creates the following temporary working!                        directory:D  4                        SYS$SPECIFIC:[SYSUPD.DQS$nnn]  B            In response to the VMSINSTAL command, a banner like the4            following may be displayed on the screen:  K                    OpenVMS VAX Software Product Installation Procedure Vx.x_  &            It is 11-JUN-1994 at 15:47.:            Enter a question mark (?) at any time for help.          %      14-6 Using the VMSINSTAL Utility  u  r          H         ________________________________________________________________  7         Stopping and Restarting the VMSINSTAL Procedurei               PROCEDUREhH               To stop the installation procedure at any time, press CtrlE               /Y. The installation procedure deletes all files it has_1               created up to that point and exits._  G               If you want to retry the installation procedure after you H               press Ctrl/Y, you must invoke VMSINSTAL again, as shown inE               the section titled Starting the Installation Procedure.o                                                                H                                         Using the VMSINSTAL Utility 14-7               E      ________________________________________________________________   )      Responding to Installation Questions             VALID RESPONSES>            The VMSINSTAL utility asks a series of questions toB            which you must provide answers. The following are valid?            responses to questions asked during an installation:   =            o  Press the Return key to accept a default value.   A               In most cases, a default response appears in square B               brackets ([])  at the end of the question or prompt.  <            o  Enter your own value and press the Return key.  >            o  Enter a question mark (?)  to request additional2               information provided by the product.        QUESTIONS YOU ARE ASKED?            During the installation of the DQS software with thehD            VMSINSTAL utility, you are asked the following questions:  &            o  If you want to continue:  6               -  After warnings about the environment:  I      %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.tC      %VMSINSTAL-W-ACTIVE, The following processes are still active:1              DECW$SERVER_0              _FTA13:              VUE$DAVIES_3               DECW$TE_005C +      * Do you want to continue anyway [NO]?   B                  This display is informational. The default is NO.C                  If you answer NO or only press the Return key, the_D                  installation terminates and you are returned to theB                  system command level. If you answer YES and press<                  the Return key, the installation continues.  8               -  After selecting a release notes option:  5      * Do you want to continue the installation [NO]?   %      14-8 Using the VMSINSTAL Utility     e            E                     Enter YES or NO, as appropriate. If you enter YESsE                     and press the Return key, the procedure continues &                     with this message:  c         %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.   D               o  If you are satisfied with the backup of your system                  disk:  O                  * Are you satisfied with the backup of your system disk [YES]?t  E                  You are reminded that you should back up your systeme6                  disk before you install the software.  <               o  Where the distribution volumes are mounted:  B                  * Where will the distribution volumes be mounted:  =                  If you did not indicate the device where thecB                  distribution volumes are mounted when you invokedG                  VMSINSTAL, you are asked this question. Enter the namem:                  of the device where you loaded the media.  A               o  To select a release notes option, if you enteredM/                  OPTIONS N on the command line:   T                  Release notes included with this kit are always copied to SYS$HELP.  5                     Additional Release Notes Options:p  2                          1.  Display release notes0                          2.  Print release notes)                          3.  Both 1 and 2 .                          4.  None of the above  %                  * Select option [3]:   C                  Digital recommends that you read the release notes C                  before installing the software for the first time._  E               o  To enter a print queue name for printing the release_E                  notes, if you selected release notes options 2 or 3:b  (                  Queue name [SYS$PRINT]:  F                  Enter a queue name or press the Return key. Remember,D                  to print the release notes, you must have a printerC                  attached to the system on which you are installing F                  the DQS software. (You cannot use the DQS software toD                  print the release notes until after the software is                  installed.)  H                                         Using the VMSINSTAL Utility 14-9 n  l            9            o  If you want to install the server software:i  I              The DQS client will be installed automatically on this node.a  H      * Do you want to install the DQS server software on this node [NO]?  B               The DQS software offers you the option to install or@               not install the server software on the system. TheC               client software is always installed. The installationt9               default is to install client software only.   @               If you are installing the DQS software on a systemC               that has a printer that you want to make available torD               clients on other systems, then you enter YES and press               the Return key.o  D            o  If you want to proceed (after selecting to install the               server software):   8                                    *** PLEASE NOTICE ***  M              If you are upgrading DQS server software from an earlier versionDM              to DQS V1.3, the earlier version of the DQS server software must_P              be running. This allows the DQS V1.3 installation procedure to readK              the existing DQS server configuration information and create apI              new DQS V1.3 server configuration file. Otherwise, after the H              installation, you must manually update your DQS V1.3 server               configuration file.  J              The directory and name of the DQS V1.3 configuration file is:  8                        SYS$MANAGER:DQS$SERVER_CONFIG.TXT  G              Digital recommends that you review the new DQS V1.3 server M              configuration file after this installation. Refer to the section L              on server management in the DQS System Manager's Guide for more              information._  M              The DQS client configuration is not automatically updated. Refer L              to the section on client management in the DQS System Manager's(              Guide for more information.  $      * Do you want to proceed [YES]?  >            o  If you want to run the Installation Verification               Procedure (IVP):  ?      * Do you want to run the IVP after the installation [YES]?   &      14-10 Using the VMSINSTAL Utility                 ?                  Digital recommends that you answer YES to thisl                  question.  ?               o  If you want to purge files replaced during the &                  installation process:  I         * Do you want to purge files replaced by this installation [YES]?   D                  If you want to retain the old copies, answer NO andE                  press the Return key. Otherwise, answer YES or press F                  the Return key. (Remember, once the files are purged,9                  they are erased and cannot be accessed.)t  H               o  If you have loaded and registered an authorization key:  !                 Product:      DQSg!                 Producer:     DEC !                 Version:      1.3s)                 Release Date: 07-MAR-1994   L         * Does this product have an authorization key registered and loaded?  @                  The DQS product supports the License ManagementD                  Facility (LMF). Before starting the DQS software onD                  an OpenVMS system, LMF requires that you register aH                  License Product Authorization Key (License PAK) for the                  DQS product._  E                  You must load the DQS License PAK on each node in anND                  OpenVMS cluster. For information on registering andB                  loading your License PAK, see the OpenVMS License+                  Management Utility Manual.l  +         GETTING HELP ON VMSINSTAL QUESTIONS D               To get help on any of the VMSINSTAL questions, enter a<               question mark (?) in response to the question.                  H                                        Using the VMSINSTAL Utility 14-11 r  i          E      ________________________________________________________________a  $      Following Installation Progress            NO MORE QUESTIONSE            After validating that you have loaded the DQS License PAK,r,            VMSINSTAL asks no more questions.  )                     No further questions.l        STATUS MESSAGESE            The DQS installation procedure then creates the DQS$SERVER ?            account and directory, installs the client software, @            installs the server software if selected, and createsC            the DQS network object. VMSINSTAL displays informational B            messages about the status of the installation, like the            following:   9      %VMSINSTAL-I-RESTORE, Restoring product saveset B...tQ      %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DQS$SERVER.V2      %UAF-I-ADDMSG, user record successfully addedT      %UAF-I-RDBADDMSGU, identifier DQS$SERVER value: [000300,000311] added to rights
      database   +              DQS$SERVER account is created.   Q      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER. +      %UAF-I-MDFYMSG, user record(s) updated D      %VMSINSTAL-I-SYSDIR, This product creates system disk directoryR                                                           SYS$COMMON:[DQS$SERVER].  C              [DQS$SERVER] directory is created in SYS$COMMON: area.   1              Installing DQS SERVER software . . ._  1              Installing DQS CLIENT software . . .   +              DQS network object is created.2            &      14-12 Using the VMSINSTAL Utility g                        INFORMATIONAL MESSAGES<               VMSINSTAL displays the following informationalE               messages that concern system parameter requirements and *               postinstallation procedures:  P               ******************************************************************P               *           Instructions for completing DQS installation         *P               ******************************************************************  M                 o Please follow the post installation instructions which haveqC                   been outlined in the DQS V1.3 Installation Guide.   N                 o Please be sure to edit your OpenVMS System Startup ProcedureQ                   and add the following line to invoke the DQS Startup Procedure:   6                         $ @SYS$STARTUP:DQS$STARTUP.COM  N                 o Once you have completed the DQS post installation proceduresP                   you can invoke the DEC DQS installation verification procedureL                   to test your customizations. To invoke this file start DQS                   and type:_  /                         $ @SYS$TEST:DQS$IVP.COM   I                 o This installation has updated the DCL Tables. Therefore J                   users must log out and then back in, in order to use theM                   QSHOW, QDELETE, and QSET commands for displaying, deleting, A                   and modifying jobs on the remote server queues.r  L                 o Please read the DQS V1.3 release notes located in the file1                   SYS$HELP:DQS013.RELEASE_NOTES .   V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...           VERIFICATION MESSAGES F               If you indicated that you want to run the IVP as part ofE               the installation, the following messages are displayed;e.               otherwise, this step is skipped:  F         Beginning of the DQS V1.3 Installation Verification Procedure.  L           Copyright Digital Equipment Corporation 1994. All rights reserved.  S           Restricted Rights: Use, duplication, or disclosure by the U.S. Government O           is subject to restrictions as set forth in subparagraph (c)(1)(ii) of S           DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as_           applicable._  H                                        Using the VMSINSTAL Utility 14-13 c  r            O        This software is proprietary to and embodies the confidential technologySL        of Digital Equipment Corporation. Possession, use, or copying of thisP        software and media is authorized only pursuant to a valid written license1        from Digital or an authorized sublicensor.L  *      %DQS-I-QUESUCCESS IVP test successfulL      End of the DEC DQS for OpenVMS V1.3 Installation Verification Procedure  >            The IVP checks to see if files are installed in theB            correct locations. Then, the IVP displays the following            message:t  0            %DQS-I-QUESUCCESS IVP test successful        PROCEDURE ENDING MESSAGES@            Once installation is completed, this message appears:  6            Installation of DQS Vn.n completed at hh:mm  ,            VMSINSTAL procedure done at hh:mm  A            The message from VMSINSTAL means that the installation A            and verification (if selected) of the DQS software has B            completed successfully. If VMSINSTAL reports a failure,1            review the installation prerequisites.   E            You can run the IVP at any time to check the DQS software.v        FOR MORE INFORMATIONe6            Refer to Chapter 15 for more information on2            postinstallation procedures, including:  D            o  Editing the system startup file to include DQS startup               commando  =            o  Running the IVP independent of the installation   <            o  Setting up DQS software to run in a VMScluster               environment   A            For details on setting up the DQS queues, see Part II,y"            System Manager's Guide.      &      14-14 Using the VMSINSTAL Utility    g                  H                                                                       15H         ________________________________________________________________  H                                            After Installing DQS Software                 ABOUT THIS CHAPTERD               This chapter describes tasks that you need to do after;               installing the DQS software (see Table 15-1).e  H               Table_15-1_Task_Summary___________________________________  H               Task___Description________________________________________  D                1     Postinstallation Tasks: New Server Installation  D                2     Postinstallation Tasks: New Client Installation  @                3     Postinstallation Tasks for All Systems: New!                      Installation   H                4     Postinstallation Tasks: Upgrade Server Installation  H                5     Postinstallation Tasks: Upgrade Client Installation  D                6     Postinstallation Tasks for All Systems: Upgrade!                      Installationy  H               _7_____Postinstallation_Tasks:_VMScluster_Nodes___________           NOTE@               If you find software problems while performing the@               postinstallation procedures, report the problem toE               Digital. Refer to Appendix G for instructions on how to                report problems.          H                                       After Installing DQS Software 15-1 e             E      ________________________________________________________________   4      Postinstallation Tasks: New Server Installation      
      OVERVIEWaC            This section describes the tasks you may need to perform ?            if this is a new installation of the DQS software on_A            a DQS server node and tells you where to look for moreM"            information, if needed.  &      MOVE DQS SERVER ACCOUNT DIRECTORY?            The DQS server uses a directory to temporarily storenC            copies of the files that it is printing for DQS clients. ;            These print files vary in size. Depending on therA            requirements of your environment, you may need to movel>            this directory to an alternate device. DQS softwareE            provides a command procedure that enables you to change or 5            move this directory to a different device.   C            If needed, move the DQS server account default directory             to another device._        REFERENCEC            See the section titled Move the Server Account Directory A            to Another Device in Chapter 8 of the System Manager'si            Guide for details.         DEFINE SERVER QUEUES ?            Before client nodes can access remote queues on your @            server node using the DQS software, define the set ofE            queues on a DQS server node that may be made accessible to,            remote queues.           REFERENCE=            See the section titled Setting Up Remote Queues in ?            Chapter 8 of the System Manager's Guide for details.               '      15-2 After Installing DQS Softwaren                 !         CUSTOMIZE SERVER SOFTWARE G               If you need to change DQS server logical definitions that C               relate to the behavior of the server software, do theh               following:  B               a. Copy SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE to6                  SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM.  G               b. Edit SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM and make the 7                  required changes for your environment.D           REFERENCE H               See Chapter 8 in the System Manager's Guide for details on$               managing a DQS server.                                                              H                                       After Installing DQS Software 15-3 h             E      ________________________________________________________________   4      Postinstallation Tasks: New Client Installation      
      OVERVIEWR?            The next sections describe the tasks you may need tosD            perform if this is a new installation of the DQS softwareD            on a DQS client node and tells you where to look for more"            information, if needed.        CUSTOMIZE CLIENT SOFTWARE>            Customize the DQS client software for your specific            environment.   D            If you need to change DQS client logical definitions that@            relate to the behavior of the client software, do the            following:I  3            a. If you have not already done so, copy :               SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE to3               SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM.   D            b. Edit SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM and make the4               required changes for your environment.        REFERENCEE            See Chapter 9 in the System Manager's Guide for details on !            managing a DQS client.:                                '      15-4 After Installing DQS Software                H         ________________________________________________________________  @         Postinstallation Tasks for All Systems: New Installation               OVERVIEWF               This section describes the tasks you may need to performD               on all sytems if this is a new installation of the DQS               software.c            EDIT SYSTEM STARTUP FILEH               Edit the system startup file and add the command line that&               starts the DQS software.  H               __________________________________________________________H               Operating_System______Name_of_Startup_File________________  5               OpenVMS AXP and       SYSTARTUP_VMS.COM !               OpenVMS VAX Versionu               6.no  4               OpenVMS VAX Version   SYSTARTUP_V5.COMH               5.n_______________________________________________________  &               DECnet Phase IV systems:  H               With DECnet Phase IV networking software, the DQS software@               must start after the network has started. You mustH               position this new command line after the line that invokesE               the network startup command procedure. The following isyE               a sample portion of a system startup file that has beent/               edited to start the DQS software:l  D               $ @SYS$MANAGER:STARTNET.COM    ! Start DECnet software                      .                      .                      .F               $ @SYS$STARTUP:DQS$STARTUP.COM ! Then start DQS software  F               Some installations use a batch job to start the network.D               With DECnet Phase IV networking software, the job thatF               starts the network must complete before the DQS softwareG               can be started. The following portion of a system startupsB               file shows one way to ensure that the network starts&               before the DQS software:  H                                       After Installing DQS Software 15-5 o  a                        $ SUBMIT -hH              SYS$MANAGER:STARTNET.COM, -  ! Start DECnet software, first                   .y                   .s                   .eD              SYS$STARTUP:DQS$STARTUP.COM  ! Then, start DQS software  !            DECnet Phase V systemsf  B            These examples do not apply to the networks running theA            DECnet/OSI Phase V networking software. DECnet Phase VlB            software is started automatically. Check system startupD            requirements for any restrictions on the placement of the            DQS startup command.e        START DQS SOFTWAREn<            The installation procedure does not start the DQS>            software. On all nodes that you want to run the DQS*            software, execute this command:  2            $ @SYS$STARTUP:DQS$STARTUP.COM <Return>  D            You can also use the SYSMAN utility to start DQS software'            in a VMScluster environment.         RUNNING IVP;            To run the IVP independently of the installationrD            procedure, enter the following command at the DCL prompt:  +            $ @SYS$TEST:DQS$IVP.COM <Return>   @            The DQS IVP is a command procedure that verifies thatB            the DQS files are installed correctly. The installationE            procedure places the IVP command file, DQS$IVP.COM, in theo            SYS$TEST directory.  A            To troubleshoot a failed IVP, you can verify that each*C            directory contains its proper file names by entering thee/            following command at the DCL prompt:r  6            $ DIRECTORY SYS$COMMON:[SYS*]*DQS* <Return>        '      15-6 After Installing DQS SoftwareT U  i            "         ACTIVATE DCL COMMAND TABLEG               The installation procedure modifies the DCL command table D               so that the DQS commands are recognized and processed.E               Users who are logged on during the installation processsG               can use the DQS PRINT command immediately. However, other D               DQS commands: QSHOW, QDELETE/ENTRY, QSET/ENTRY are not               available.  C               Notify all logged-in users who want to use the QSHOW,sE               QDELETE/ENTRY, QSET/ENTRY commands that they need to dot&               either of the following:  .               o  Log out and log back in again  1               o  Enter the following DCL command:   <                  $ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES  H                  You can also use the SYSMAN utility to activate the DCL4                  tables in a VMScluster environment.                                                  H                                       After Installing DQS Software 15-7               E      ________________________________________________________________t  8      Postinstallation Tasks: Upgrade Server Installation      
      OVERVIEW C            This section describes the tasks you may need to perform A            if this is an upgrade installation of the DQS software D            on a DQS server node and tells you where to look for more"            information, if needed.  &      MOVE DQS SERVER ACCOUNT DIRECTORY?            The DQS server uses a directory to temporarily storesC            copies of the files that it is printing for DQS clients.e;            These print files vary in size. Depending on the A            requirements of your environment, you may need to move_>            this directory to an alternate device. DQS softwareE            provides a command procedure that enables you to change or 5            move this directory to a different device.n        REFERENCEC            See the section titled Move the Server Account DirectoryrA            to Another Device in Chapter 8 of the System Manager'so            Guide for details.S    $      VERIFY QUEUE ACCESS DEFINITIONS@            If your DQS server system is running the DQS softwareD            during the installation procedure, the procedure convertsA            the Version 1.n server queue access definitions to thetA            new format provided with DQS Version 1.3 software. TheMC            installation procedure creates the following file, which-?            should contain the queue access definitions for your             environment:r  ,            SYS$MANAGER:DQS$SERVER_CONFIG.TXT  =            The queue access definitions are specified in your C            DQS$STARTUP.COM file. The installation procedure renames%@            your previous DQS$STARTUP.COM to DQS$STARTUP.COM_OLD.  E            Please review your DQS$STARTUP.COM_OLD file and compare it-?            to the queue access definitions in the new .TXT file     '      15-8 After Installing DQS Software  $  M            E               Check the following log file for any issues encounteredrH               during the conversion of your queue definitions to the new)               security and access format:   A               $ TYPE SYS$UPDATE:DQS$CONVERT_SECURITY.LOG <Return>i           REMOVE RIGHTSLIST IDS E               After DQS Version 1.3 software has been running on yourpC               system for a few weeks and you are satisfied with the G               operation of the new queue access mechanism, you may wantuD               to remove all the DQS$NODE_xxxx rightslist identifiersE               from your rightslist database. Do not do this until younG               are sure that you do not want to go back to a DQS Version*               1.2 environment.  H               Use the OpenVMS Authorize utility to remove the rightslistB               identifiers that were used prior to DQS version 1.3.  ?               The DQS V1.3 rightslist identifiers have the formMG               DQS$NODE_nodename, where nodename is a 6-character DECnett               node name.           PROCEDURE @               Use the following procedure to remove a rightslist               identifier:h           $ MCR AUTHORIZEc0         UAF> REMOVE/IDENTIFIER DQS$NODE_nodename         UAF> EXITi           EXAMPLE:?               The following example removes DQS$NODE_SMEDLY ande<               DQS$NODE_JONJON from the rights list database:           $  MCR AUTHORIZE.         UAF> REMOVE/IDENTIFIER DQS$NODE_SMEDLYR         Identifier DQS$NODE_SMEDLY value: %X800100A2 removed from rights data base.         UAF> REMOVE/IDENTIFIER DQS$NODE_JONJONR         Identifier DQS$NODE_JONJON value: %X800100A3 removed from rights data base         UAF> EXITe          H                                       After Installing DQS Software 15-9 d                     CUSTOMIZE SERVER SOFTWAREE            With DQS Version 1.3, the DQS startup procedure is dividedo            into two files:  9            o  SYS$STARTUP:DQS$STARTUP.COM: Used to invokeu,               SYS$MANAGER:DQS$SYSTARTUP.COM.  B            o  SYS$MANAGER:DQS$SYSTARTUP.COM: Used to customize DQS               logical names.  A            DQS$STARTUP.COM invokes SYS$MANAGER:DQS$SYSTARTUP.COM,a1            which contains all the customizations.   E            A site-specific startup template that you can customize ist%            provided your convenience:c  4            SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE        PROCEDURE<            To change server logical definitions, perform the            following:7  ?            a. Copy SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE to 3               SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM.T  C            b. Edit SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM and add therD               server related changes that were previously defined inE               DQS$STARTUP.COM. These can be found in DQS$STARTUP.COM_                OLD.  A            DQS server queue access is no longer defined by addingaD            logical definitions to the startup procedure. Do not copyA            the following logicals to your DQS$SYSTARTUP.COM file:i  #            o  DQS$CONTROLLED_ACCESSk              o  DQS$DENY_ACCESSn  9            o  DQS$QUEUE_xxxx (where xxxx is a queue-name)e        REFERENCEE            See Chapter 8 in the System Manager's Guide for details on $            customizing a DQS server.    (      15-10 After Installing DQS Software p  r          H         ________________________________________________________________  ;         Postinstallation Tasks: Upgrade Client InstallationA               OVERVIEWF               This section describes the tasks you may need to performD               if this is an upgrade installation of the DQS softwareG               on a DQS client node and tells you where to look for moren%               information, if needed.Q  !         CUSTOMIZE CLIENT SOFTWARETA               Customize the DQS client software for your specific                environment.  D               With DQS Version 1.3, the startup procedure is divided               into two files:   <               o  SYS$STARTUP:DQS$STARTUP.COM: Used to invoke/                  SYS$MANAGER:DQS$SYSTARTUP.COM.r  E               o  SYS$MANAGER:DQS$SYSTARTUP.COM: Used to customize thet&                  client logical names.  D               DQS$STARTUP.COM invokes SYS$MANAGER:DQS$SYSTARTUP.COM,1               which contains all the definitions.   H               A site specific startup template that you can customize is(               provided your convenience:  7               SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE   >               To change client logical definitions perform the               following:  6               a. If you have not already done so, copy=                  SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE to 6                  SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM.  G               b. Edit SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.COM and make the_G                  client-related changes that were previously defined innH                  DQS$STARTUP.COM. These can be found in DQS$STARTUP.COM_                  OLD.     H                                      After Installing DQS Software 15-11 l  o                  REFERENCEE            See Chapter 9 in the System Manager's Guide for details on              customizing a client.                                                                                    (      15-12 After Installing DQS Software               H         ________________________________________________________________  D         Postinstallation Tasks for All Systems: Upgrade Installation               OVERVIEWF               This section describes the tasks you may need to performE               on all sytems if this is an upgrade installation of the                DQS software.             EDIT SYSTEM STARTUP FILE@               Edit the system startup file to check that the DQS,               software is started correctly.  H               __________________________________________________________H               Operating_System______Name_of_Startup_File________________  5               OpenVMS AXP and       SYSTARTUP_VMS.COM_!               OpenVMS VAX Versiont               6.no  4               OpenVMS VAX Version   SYSTARTUP_V5.COMH               5.n_______________________________________________________  E               Look in the system startup procedure for the one of then               following lines:  -               o  @SYS$MANAGER:DQS$STARTUP.COMh  -               o  @SYS$STARTUP:DQS$STARTUP.COMy  E               DQS Version 1.3 software requires that the DQS softwareQF               start from the SYS$STARTUP directory. Change the command=               to the following if it was not already changed:e  *               @SYS$STARTUP:DQS$STARTUP.COM  H               Do this on each node of a cluster that you want to run theG               DQS software. DQS software then starts automatically when                the node reboots.h          H                                      After Installing DQS Software 15-13 Q  E                  START DQS SOFTWAREn<            The installation procedure does not start the DQS>            software. On all nodes that you want to run the DQS*            software, execute this command:  2            $ @SYS$STARTUP:DQS$STARTUP.COM <Return>  D            You can also use the SYSMAN utility to start DQS software'            in a VMScluster environment.d        RUN IVP?            To run the IVP independently of the any installation D            procedure, enter the following command at the DCL prompt:  +            $ @SYS$TEST:DQS$IVP.COM <Return>   @            The DQS IVP is a command procedure that verifies thatB            the DQS files are installed correctly. The installationE            procedure places the IVP command file, DQS$IVP.COM, in theR            SYS$TEST directory.  A            To troubleshoot a failed IVP, you can verify that each C            directory contains its proper file names by entering the /            following command at the DCL prompt:d  6            $ DIRECTORY SYS$COMMON:[SYS*]*DQS* <Return>        UPDATE SERVER QUEUES B            After the DQS software is running, if you installed the?            DQS software on a server node, execute the following_            command procedure:_  @            $ @SYS$MANAGER:DQS$SERVER_UPDATE_QUEUE_DEFNS <Return>  B            DQS Version 1.3 software does not require DQS queues toC            have the /RETAIN queue attribute. This command procedure E            allows you to change the definitions of your DQS queues toe&            eliminate these attributes.              (      15-14 After Installing DQS Software E               "         ACTIVATE DCL COMMAND TABLEG               The installation procedure modifies the DCL command tableeD               so that the DQS commands are recognized and processed.E               Users who are logged on during the installation processaG               can use the DQS PRINT command immediately. However, otherRD               DQS commands: QSHOW, QDELETE/ENTRY, QSET/ENTRY are not               available.  C               Notify all logged-in users who want to use the QSHOW, E               QDELETE/ENTRY, QSET/ENTRY commands that they need to doe&               either of the following:  .               o  Log out and log back in again  1               o  Enter the following DCL command:n  <                  $ SET COMMAND /TABLES=SYS$LIBRARY:DCLTABLES  D                  You can also use the SYSMAN utility to activate DCL1                  tables a VMScluster environment.                                                   H                                      After Installing DQS Software 15-15    a          E      ________________________________________________________________R  -      Postinstallation Tasks: VMScluster Nodesi      
      OVERVIEWdC            This section describes the tasks you may need to perform_"            on a VAXcluster system.        EDIT SYSTEM STARTUP FILE E            Edit the system startup file and add the following line to C            start the DQS software for each cluster member where the &            DQS software is to execute:  %            $ @SYS$STARTUP:DQS$STARTUP_        REPLACE DCL TABLES_E            If you install DQS client software on a VMScluster member,E?            the DCL tables are updated to include the DQS QSHOW,o@            QDELETE/ENTRY, and QSET/ENTRY commands on that memberE            only. To include these commands in the DCL tables of othern@            cluster members, either execute the SYSMAN utility orA            issue the following commands from the system manager'sr*            account on each cluster member:              $ INSTALL <Return>h8            INSTALL> REPLACE SYS$SHARE:DCLTABLES <Return>!            INSTALL> EXIT <Return>             $        DEFINE NETWORK OBJECTE            The DQS network object must be defined on each node withinT=            the VMScluster where you want to run DQS software.a  >            On DECnet Phase IV systems, use the Network ControlB            Program. On DECnet/OSI Phase V systems, use the Network"            Control Language (NCL).              NCP Commandss  A            To define the DQS object using NCP, execute the SYSMANe)            utility or follow these steps:t  D            a. Obtain the randomly generated password, created duringC               the installation procedure, for the DQS client/server   (      15-16 After Installing DQS Software R  A            E                  account. From a privileged account on the node where @                  you installed the software, enter the following                  commands:  .                  $ RUN SYS$SYSTEM:NCP <Return>.                  NCP> SHOW OBJECT DQS <Return>  C                  The system returns the password for the DQS client H                  /server account in the Password field. In the followingE                  example, TESTING123 is the randomly generated cliente*                  /server account password.  C                  Object Volatile Summary as of  5-JAN-1994 10:42:14t  K                    Object  Number  File/PID          User Id       Password   M                   DQS          66  DQS$SERVER.EXE    DQS$SERVER    TESTING123                   NCP>Y  F               b. Enter the following NCP commands on each of the otherF                  nodes in the VMScluster environment to define the DQSH                  object (using the returned password for password in the                  commands)::  .                  $ RUN SYS$SYSTEM:NCP <Return>P                  NCP> DEFINE OBJECT DQS NUMBER 66 FILE DQS$SERVER.EXE - <Return>=                  _ USER DQS$SERVER PASSWORD password <Return> M                  NCP> SET OBJECT DQS NUMBER 66 FILE DQS$SERVER.EXE - <Return>S=                  _ USER DQS$SERVER PASSWORD password <Return>n#                  NCP> EXIT <Return>o                  $                 NCL Commands  D               To define the DQS object using NCL, execute the SYSMANH               utility or enter the following NCL commands on each of the8               other nodes in the VMScluster environment:  =               s>(NCL>) CREATE SESSION CONTROL APPLICATION DQS 9               NCL> SET SESSION CONTROL APPLICATION DQS, -aI               _NCL> ADDRESS = {NUMBER=66}, IMAGE NAME = DQS$SERVER.EXE, -tC               _NCL> INCOMING PROXY = FALSE, OUTGOING PROXY=FALSE, - @               _NCL> NODE SYNONYM=FALSE, USER NAME = "DQS$SERVER"  4               Node 0 Session Control Application dqs4               at 1994-03-16-13:34:58.193-05:00I1.614                 Characteristics   H                                      After Installing DQS Software 15-17 r               2                Addresses                         =                   {E                       number = 66                   }SA                Image Name                        = DQS$SERVER.EXEn8                Incoming Proxy                    = False8                Outgoing Proxy                    = False8                Node Synonym                      = False?                User Name                         = "DQS$SERVER"               NCL> EXIT                                                                    (      15-18 After Installing DQS Software                       H                                                                  Part IVH         ________________________________________________________________  H                                                               Appendixes                     CONTENTSC               This part contains additional information for the DQSc6               user, system manager, and the installer.  =               For the   Description of relevant DQS messages.f               user:p  E               For the   Description of relevant DQS messages, summary E               system    of DQS server and client logical names, and aeH               manager:  description of how other symbionts interact with)                         the DQS software.n  A               For       List of files added to the system, sampletE               the in-   installation scripts and configuration files, C               staller:  and a description of relevant DQS messages.R    U                  H                                                                        AH         ________________________________________________________________  H                                                        DQS User Messages                 ABOUT THIS APPENDIXoF               This appendix lists error and diagnostic messages issuedH               by the DEC Distributed Queuing Service for OpenVMS SystemsF               (DQS) software. Each message includes a description and,F               where appropriate, corrective actions that you can take.           DQS MESSAGE FORMATB               Most DQS messages follow the same format as standard<               OpenVMS system messages and appear as follows:                  %DQS-l-ident, text                 Where:  D               l        Is the severity level of the message, such as2                        -W-, for a warning message.  G               ident    Is the message identification, such as NOACCESS.   H               text     Is the message text, such as "specified node does7                        not have access to this server."E           SEVERITY CODESH               DQS messages use the same severity codes as OpenVMS system*               messages: S, I, W, E, and F.           FOR MORE INFORMATIONH               DQS messages that concern the management and configuration?               of the DQS software are documented in Appendix B.r  ?               Refer to the OpenVMS System Messages and RecoveryrC               Procedures Reference Manual for an explanation of the C               format and a definition of severity codes for OpenVMS                system messages.  H                                                    DQS User Messages A-1    n          E      ________________________________________________________________g        Message Section            NOTIFICATION MESSAGESA            The DQS software can return the following notificationo>            messages (these messages do not follow the standard#            OpenVMS message format).   ?        Print job file-name (queue queue-name, entry job-number)M2          terminated with error status at date/time  A          Explanation: Your print job has not successfully printed$C          on the server node. A secondary error message is displayedd6          describing the reason why the error occurred.  C          User Action: Rectify the problem based on the reason given (          in the secondary error message.  ?        Print job file-name (queue queue-name, entry job-number)D          completed at date/timer  :          Explanation: None, this message is informational.  .          User Action: Retrieve your print job.        DQS MESSAGE DEFINITIONSA            Because all DQS messages have the same prefix %DQS-l-,oA            the messages in this section are listed alphabeticallyi,            according to their message ident.  E        BADNODE, specified node has been denied access to this server.   ;          Explanation: The remote node for your queue is not %          accessible from your client.   2          User Action: Contact your system manager.  8        BADQUE, specified queue not valid for DQS access.  ;          Explanation: The remote queue on the server is noti#          accessible by DQS clients.e  2          User Action: Contact your system manager.        A-2 DQS User Messages                 G          BAD_REMOTE_NAME,  logical-name must be defined for this queue.   B             Explanation: The remote system name has been specified             incorrectly.  5             User Action: Contact your system manager.]  -          CHECKPOINTED,  job was checkpointed.v  F             Explanation: Your print job was checkpointed and DQS could&             not remove the checkpoint.  D             User Action: Delete your job from the queue and resubmit             it.y  1          ENTRY_REQUIRED,  /entry=number required.u  G             Explanation: You did not specify the required /ENTRY=numberT6             qualifier in your QSET or QDELETE command.  D             User Action: Reenter the command using the /ENTRY=numberC             qualifier, specifying the appropriate job entry number.i  9          ERROROPENING,  error opening file-name as input.o  G             Explanation: The client's print symbiont could not open the F             specified file for the reason cited in the secondary errorE             message that accompanies this message. This error messageoG             will be printed in the print output on the server. Usually,sF             this message occurs when the file to be printed is deletedD             before the file is transferred by the client symbiont to             the server.n  F             User Action: Rectify the problem based on the reason given+             in the secondary error message.s  0          ERRORREADING,  error reading file-name.  G             Explanation: The client's print symbiont could not read the F             specified file for the reason cited in the secondary error2             message that accompanies this message.  F             User Action: Rectify the problem based on the reason given+             in the secondary error message.   H                                                    DQS User Messages A-3 U  O            =        INACCESSIBLE, remote queue queue-name is inaccessible.i  B          Explanation: The server you are attempting to print to is          not accessible.  D          User Action: The job will not be processed until the serverA          is reachable. However, for QSHOW, QSET/ENTRY, or QDELETE D          /ENTRY command functions, you must wait until the server is          available.S  >        INCOMPPROT, incompatible DQS Server and Client protocol          versions.  ?          Explanation: The version of DQS software on the clientT@          is incompatible with the version of DQS software on the          server.  2          User Action: Contact your system manager.  #        INVLOGFIL, invalid log file.   A          Explanation: You specified an invalid log file in a QSETl>          /ENTRY command. The reason for the error in your fileC          specification is cited in the secondary error message that "          accompanies this message.  D          User Action: Correct the file specification and reenter the          QSET/ENTRY command.  ;        INVQUAVAL, value 'value' invalid for /qualifier-name_          qualifier._  <          Explanation: You specified an invalid value for the#          qualifier /qualifier-name.   A          User Action: Specify the proper value for the qualifier.u  1        INVVER, versions of protocol do not match.t  B          Explanation: The version of DQS software on the client isD          incompatible with the version of DQS software on the server=          to which you are attempting to queue your print job.e  2          User Action: Contact your system manager.        A-4 DQS User Messages _               ,          JOBDELETED,  number job(s) deleted.  D             Explanation: The QDELETE/ENTRY command you specified didE             not delete all of the jobs you specified, only the number (             of jobs specified by number.  C             User Action: Check the job number(s) for the job(s) you F             attempted to delete, as well as your access privileges for9             deleting those jobs, and reenter the command.A  @          LONGNODENAME,  Node name size problem due to DECnet/OSI             fullname.Q  >             Explanation: The DQS symbiont received a node nameF             (possibly from a daisy-chained queue) that is too long forE             the version of the OpenVMS operating system or the DECnetS*             networking software to handle.  C             User Action: Notify your system manager of the problem. ;             Systems need upgrading or DQS queues need to be !             reconfigured or both.   !          MSG_PE,  protocol error.   B             Explanation: A protocol error indication was received.G             This error usually occurs when incompatible versions of DQSt9             software reside on server and client systems.r  5             User Action: Contact your system manager.   *          MSG_REMOTE,  remote system error:  F             Explanation: An error occurred on the remote system and isE             described in the secondary error message that accompanies              this message.l  F             User Action: Rectify the problem based on the reason given+             in the secondary error message.E  G          NOACCESS,  specified node does not have access to this server.h  @             Explanation: The client is not authorized to use the#             queue(s) on the server.e  5             User Action: Contact your system manager.   H                                                    DQS User Messages A-5 r               9        NODELETE, /NODELETE is allowed only on local jobs.r  B          Explanation: You cannot use the /NODELETE qualifier for aD          job that is not on your local node; that is, a job that has#          transferred to the server.w  A          User Action: Do not use the /NODELETE qualifier for jobsr-          that have transferred to the server.m  %        NOJOBDELETED, no jobs deleted.A  A          Explanation: The QDELETE/ENTRY command you specified did1          not delete any jobs.S  =          User Action: Check the job number of the job you arem@          attempting to delete, as well as your access privileges*          to delete the job, and try again.          NOJOBSET, no jobs set.   B          Explanation: The QSET/ENTRY command you specified did not          set any jobs.  =          User Action: Check the job number of the job you aren@          attempting to modify, as well as your access privileges*          to modify the job, and try again.  2        NOSUCHQUE, no such remote queue queue-name.  C          Explanation: The remote queue specified by queue-name does +          not currently exist on the server.E  2          User Action: Contact your system manager.  $        NOTOWN, not owner of the job.  C          Explanation: You are not the owner of the job that you are D          attempting to delete or modify. The DQS software determinesD          job ownership by the node name and user name with which the          job was initiated.   D          User Action: Ensure that you have specified the correct jobA          number and that you are working from the same account on :          the same client from which you initiated the job.  E        NO_ACCESS_CONTROL, no access control strings allowed in serverI          node name.e  ?          Explanation: The remote system name has been specified_          incorrectly._  2          User Action: Contact your system manager.        A-6 DQS User Messages    i            H          NO_NODE_SPECIFIED,  printer queue name does not specify a node.  B             Explanation: The remote system name has been specified             incorrectly.  5             User Action: Contact your system manager.h  B          NO_SET_LISTS,  list of job numbers for SET not supported.  E             Explanation: You cannot specify a sequence of job numbers <             in a QSET/ENTRY command, such as /ENTRY=(1,2,3).  E             User Action: Issue a separate QSET/ENTRY command for each              job.  D          P8RESERVED,  parameter 8 (P8) is reserved for DQS on remote             systems.  C             Explanation: You attempted to specify P8 when issuing aSE             PRINT command to a DQS queue. Parameter 8 is reserved for              DQS information.  A             User Action: Do not specify P8 when using DQS queues. D             Instead add your P8 arguments to parameters 1 through 7.  /          REC_MSG,  received message: "message".B  D             Explanation: The server is running an old version of DQS             software.S  5             User Action: Contact your system manager.   .          REINSTALL,  install new DQS software.  B             Explanation: The version of DQS software on the clientC             is incompatible with the version of DQS software on the              server.e  5             User Action: Contact your system manager.i  E          REQNOEXIST,  requeue remote does not exist on remote system.e  B             Explanation: The queue you specified with a QSET/ENTRYD             /REQUEUE=queue-name command does not exist. You can onlyG             requeue to a queue that is on the same remote system as the              print job.  B             User Action: Requeue your job to another remote queue,D             or delete the job and submit a new job to a valid remote             queue.  H                                                    DQS User Messages A-7 f  t                  H                                                                        BH         ________________________________________________________________  H                                              DQS System Manager Messages                 ABOUT THIS APPENDIX F               This appendix alphabetically lists and defines all errorG               and diagnostic messages issued by DQS. Where appropriate, D               it describes any corrective actions that you can take.                                                            H                                          DQS System Manager Messages B-1    i          E      ________________________________________________________________         DQS Message FormatE  @            DQS messages have the same format as standard OpenVMS1            system messages and appear as follows:E              %DQS-l-ident, texte              Where  A            l        Is the severity level of the message, such as /                     -W-, for a warning message.d  D            ident    Is the message identification, such as NOACCESS.  E            text     Is the message text, such as "specified node doesg4                     not have access to this server."  $      SEVERITY LEVELS OF DQS MESSAGES  E            DQS messages use the same severity codes as OpenVMS system '            messages: S, I, W, E, and F.L        FOR MORE INFORMATIONCC            DQS messages that concern printing with the DQS softwareS@            are documented in Appendix A for the user and in this+            appendix for the system manager.L  <            Refer to the OpenVMS System Messages and Recovery@            Procedures Reference Manual for an explanation of the@            format and a definition of severity codes for OpenVMS            system messages.                           $      B-2 DQS System Manager Messages               H         ________________________________________________________________  0         Submitting a Software Performance Report               WHEN TO SUBMITH               When you receive a DQS internal software error, you shouldD               submit a Software Performance Report (SPR) to Digital.  F               Refer to the Appendix G for information on how to submit               an SPR.                                                                     H                                          DQS System Manager Messages B-3 -  A          E      ________________________________________________________________         Message Section            DQS NOTIFICATION MESSAGESA            The DQS software can return the following notification >            messages (these messages do not follow the standard#            OpenVMS message format).   A        Print job job (queue queue, entry job-number) completed at           date time  D          Explanation: Your print job has printed successfully on the          server.  =          User Action: None. This is an informational message.o  D        Print job job (queue queue, entry job-number) terminated with"          error status at date time  A          Explanation: Your print job has not printed successfully C          on the server node. A secondary error message is displayed :          that describes the reason why the error occurred.  B          User Action: Rectify the problem based on the information"          in the secondary message.        DQS MESSAGE DEFINITIONSA            Because all DQS messages have the same prefix %DQS-l-, A            the messages in this section are listed alphabetically_,            according to their message ident.  A        BADFILE, UL total syntax errors detected in file: filename           errors.  >          Explanation: The DQS$SERVER_UPDATE_CONFIG.EXE programC          detected errors when parsing the server configuration texteB          file. The name of the file and the total number of syntax*          errors in the file are displayed.  >          User Action: Edit the file and fix the syntax errors.D          Invoke the SYS$MANAGER:DQS$SERVER_UPDATE_CONFIG.COM command(          procedure to effect the change.  $      B-4 DQS System Manager Messages                 F          BADFORM,  INTERNAL SOFTWARE ERROR - Translate form failed for             form form-name.c  7             Explanation: This is an internal DQS error.   '             User Action: Submit an SPR.i  A          BADNAM,  INTERNAL SOFTWARE ERROR - process name does not )             contain underscore, and must.   7             Explanation: This is an internal DQS error.   '             User Action: Submit an SPR.u  H          BADNODE,  specified node has been denied access to this server.  F             Explanation: Your client is denied access to the server to=             which you are attempting to queue your print job.t  F             User Action: Consult the server system manager and requestG             that your client node have access to the server. The servernD             system manager needs to modify the DQS$SERVER_CONFIG.TXT&             file to allow this access.  ;          BADQUE,  specified queue not valid for DQS access.   F             Explanation: The remote queue you specified is not definedF             on the server as accessible to DQS clients. This means one/             of the following conditions exists:   D             o  The SYS$MANAGER:DQS$SYSTARTUP.COM command file on the.                server is not set up correctly.  @             o  The SYS$STARTUP:DQS$STARTUP.COM file has not been                executed.  C             o  The client is not permitted to use the remote queue.   F             User Action: Consult the server system manager and requestE             that your node be granted access to the remote queue. The G             system manager may need to modify the DQS$SERVER_CONGIG.TXTe$             file on the server node.      H                                          DQS System Manager Messages B-5 u  u            D        BAD_REMOTE_NAME, logical-name must be defined for this queue.  A          Explanation: The client queue you specified has not beeneA          defined as a DQS client queue. For a queue to be definedBB          as a client queue, a logical name of the form DQS$REMOTE_4          client-queue must be defined for the queue.  =          User Action: Check the SYS$MANAGER:DQS$SYSTARTUP.COM >          command file to see whether the client queue has beenB          defined; if so, reexecute the SYS$STARTUP:DQS$STARTUP.COM8          command file. If not, add a command line to the8          SYS$MANAGER:DQS$SYSTARTUP.COM command file that@          invokes the SYS$MANAGER:DQS$DEFINE.COM command file and@          defines the queue as a DQS client queue. Then reexecute%          SYS$STARTUP:DQS$STARTUP.COM.   C          If the queue is not intended to be a DQS client queue, youDD          can initialize the queue with a symbiont other than the DQS          symbiont.  C          If these actions fail to solve the problem, submit an SPR.   &        BADTMPFILE, bad temporary file.  C          Explanation: A temporary file created during the IVP could           not be deleted.  B          User Action: The IVP may not have failed. Delete the file          manually.  B        BLKCNTEXC, INTERNAL SOFTWARE ERROR - Block count in message          header too large.  4          Explanation: This is an internal DQS error.  $          User Action: Submit an SPR.  #        CANTPRINT, cannot print job.y  A          Explanation: The IVP could not execute the PRINT commandc          and has failed.  1          User Action: Reinstall the DQS software.t  E        CHANGEFORMFAILED, INTERNAL SOFTWARE ERROR - Change form faileds          for queue queue-name.  4          Explanation: This is an internal DQS error.  $          User Action: Submit an SPR.  $      B-6 DQS System Manager Messages e  g            -          CHECKPOINTED,  job was checkpointed.   D             Explanation: Your print job was checkpointed and the DQS2             software cannot remove the checkpoint.  D             User Action: Delete your job from the queue and resubmit             it.   /          DISKFULL,  remote server disk is full.c  F             Explanation: Your print job cannot be copied to the serverE             node. Either there is not enough disk space on the server D             to store your file(s) for printing, or the quota for the9             DQS server account [DQS$SERVER] was exceeded.c  F             User Action: If this error persists, either ask the serverG             system manager to free up some disk space on the server, or -             queue your job to another server.   F          EMPTYFILE,  DQS server configuration file: filename is empty.  @             Explanation: Either the DQS$SERVER_UPDATE_CONFIG.EXEB             program or the DQS$SERVER program encountered an empty8             file when trying to read the indicated file.  D             User Action: Check that the file exists, is unprotected,F             and is not corrupted. The file's contents may have somehowD             become corrupted. If file name is DQS$SERVER_CONFIG.DAT,?             you can regenerate the file by deleting DQS$SERVER_ D             CONFIG.DAT and then invoking the SYS$MANAGER:DQS$SERVER_E             UPDATE_CONFIG.COM command procedure to recreate the file.   0          ENTRY_REQUIRED,  entry=number required.  G             Explanation: You did not specify the required /ENTRY=number 6             qualifier in your QSET or QDELETE command.  D             User Action: Reenter the command using the /ENTRY=numberC             qualifier, specifying the appropriate job entry number.   9          ERROROPENING,  error opening file-name as input.r  @             Explanation: The DQS client symbiont cannot open theF             specified file for the reason cited in the secondary errorF             message that accompanies this message. The secondary errorA             message is printed in the print output on the server.cB             Usually, this error message occurs when the file to be  H                                          DQS System Manager Messages B-7 S  f            A          printed is deleted before the file is transferred by theo'          client symbiont to the server.t  B          User Action: Rectify the problem based on the information"          in the secondary message.  -        ERRORREADING, error reading file-name.E  @          Explanation: The DQS client symbiont could not read theC          specified file for the reason cited in the secondary erroro/          message that accompanies this message.f  B          User Action: Rectify the problem based on the information"          in the secondary message.  =        INACCESSIBLE, remote queue queue-name is inaccessible.   ?          Explanation: A connection cannot be established to the A          server with which you are attempting to perform a QSHOW, /          QSET/ENTRY, or QDELETE/ENTRY function.S  A          User Action: Remember that if you submit a print requesta?          to the server, it is not processed until the server isOD          reachable. However, for QSHOW, QSET/ENTRY, or QDELETE/ENTRYA          command functions, the server must be reachable when the           command is issued.   >        INCOMPPROT, incompatible DQS Server and Client protocol          versions.  ?          Explanation: The version of DQS software on the clientp@          is incompatible with the version of DQS software on the          server.  ?          User Action: Make sure that compatible versions of DQS =          software are installed on both the client and servery          systems.   8        INVALIDSERVER, invalid server node or queue name.  D          Explanation: During a client IVP, you entered either a nodeD          name or a queue name that is not valid. You are prompted to-          provide another node and queue name.y  C          User Action: Enter a valid node and queue name in responser          to the prompt:N  !          Enter remote NODE::QUEUEe  $      B-8 DQS System Manager Messages l  t            H          INVBLKTYP,  INTERNAL SOFTWARE ERROR - Invalid block type number             in message.C  7             Explanation: This is an internal DQS error.   '             User Action: Submit an SPR.5  F          INVLINE,  invalid line encountered in file: filename, at line             number line.  A             Explanation: The DQS$SERVER_UPDATE_CONFIG.EXE program ;             detected a syntax error when parsing the servertA             configuration file. The name of the file and the line/>             number where the error was detected are displayed.  @             User Action: Edit the file and fix the syntax error.G             Invoke the SYS$MANAGER:DQS$SERVER_UPDATE_CONFIG.COM commandl+             procedure to effect the change.   &          INVLOGFIL,  invalid log file.  G             Explanation: You specified a log file incorrectly in a QSETeD             /ENTRY command. The reason for the error is cited in theB             secondary error message that accompanies this message.  G             User Action: Correct the file specification and reenter theo             QSET/ENTRY command.d  H          INVMSGLEN,  INTERNAL SOFTWARE ERROR - Invalid message length in             header.C  7             Explanation: This is an internal DQS error.i  '             User Action: Submit an SPR.e  C          INVMSGTYP,  INTERNAL SOFTWARE ERROR - Invalid message typec             number in header.e  7             Explanation: This is an internal DQS error.a  '             User Action: Submit an SPR.a  E          INVMSG,  INTERNAL SOFTWARE ERROR -invalid message in currente             state.  7             Explanation: This is an internal DQS error.   '             User Action: Submit an SPR.   H                                          DQS System Manager Messages B-9 t  u            ;        INVQUAVAL, value 'value' invalid for /qualifier-namec          qualifier.o  ?          Explanation: The value you specified for the qualifiern$          /qualifier-name is invalid.  @          User Action: Consult the documentation if necessary and4          specify the proper value for the qualifier.  4        INVREQCOD, invalid request code, code = code.  B          Explanation: The job controller issued an invalid request          code.  $          User Action: Submit an SPR.  1        INVVER, versions of protocol do not match..  C          Explanation: The software version of DQS on your client isND          incompatible with the software version of DQS on the server=          to which you are attempting to queue your print job.   ?          User Action: Make sure that the proper versions of DQS ?          software are installed both on your client and on your           client's server(s).  )        JOBDELETED, number job(s) deleted.D  B          Explanation: The QDELETE/ENTRY command you issued did notA          delete all of the jobs you specified, only the number ofa"          jobs specified by number.  @          User Action: Check the job number(s) for the job(s) youB          attempted to delete as well as your access privileges for          deleting those jobs.o  =        LONGNODENAME, Node name size problem due to DECnet/OSI           fullname.  ;          Explanation: The DQS symbiont received a node nameaC          (possibly from a daisy-chained queue) that is too long for B          the version of the OpenVMS operating system or the DECnet'          networking software to handle.e  D          User Action: Upgrade systems to DECnet/OSI Phase V software'          or reconfigure queues or both.r  %      B-10 DQS System Manager Messages                  !          MSG_PE,  protocol error.r  B             Explanation: A protocol error indication was received.E             This error is usually incurred by having incompatible DQS ;             software versions on server and client systems.a  F             User Action: Make sure that your client and server systemsG             have compatible versions of DQS software installed on them.o  *          MSG_REMOTE,  remote system error.  D             Explanation: An error occurred on the remote system. TheB             error is described in the secondary error message that%             accompanies this message.   E             User Action: Rectify the problem based on the information_%             in the secondary message.   @          MSG_TYPE_RANGE,  INTERNAL SOFTWARE ERROR - Message type2             received 'message-value' out of range.  7             Explanation: This is an internal DQS error.g  '             User Action: Submit an SPR.r  E          MSG_TYPE_UNEXPECTED,  INTERNAL SOFTWARE ERROR - Message typek0             received 'message-value' unexpected.  7             Explanation: This is an internal DQS error.S  '             User Action: Submit an SPR.   B          MSG_UNK,  INTERNAL SOFTWARE ERROR - Unknown error message             class: class.a  7             Explanation: This is an internal DQS error.a  '             User Action: Submit an SPR.a  G          NOACCESS,  specified node does not have access to this server.   A             Explanation: Your client is not authorized to use the #             queue(s) on the server.m  B             User Action: If you want your client to use the remoteC             queue(s) on the server, you must have the server systemfB             manager grant your client system access to the server.  H                                         DQS System Manager Messages B-11 e  v            2        NODELETE, job cannot be deleted from queue.  D          Explanation: The IVP could not delete the test job from the!          remote queue and failed.S  @          User Action: Delete the job manually, check the network!          link, and rerun the IVP.m  9        NODELETE, /NODELETE is allowed only on local jobs.n  B          Explanation: You cannot use the /NODELETE qualifier for aD          job that is not on your local node (that is, a job that has$          transferred to the server).  A          User Action: Do not use the /NODELETE qualifier for jobs -          that have transferred to the server._  '        NODEOFF, node node-name offline.   ;          Explanation: The specified server is not currently :          reachable and a job is waiting to transfer to it.  ?          User Action: Check the status of the server or ask thee@          server system manager to bring the server back on line.  B        NOJID, INTERNAL SOFTWARE ERROR - Job number, job name, or *          required.  4          Explanation: This is an internal DQS error.  $          User Action: Submit an SPR.  %        NOJOBDELETED, no jobs deleted._  B          Explanation: The QDELETE/ENTRY command you issued did not          delete any jobs.S  =          User Action: Check the job number of the job you aree@          attempting to delete, as well your access privileges to          delete the job.          NOJOBSET, no jobs set.   C          Explanation: The QSET/ENTRY command you issued did not set           any jobs.  =          User Action: Check the job number of the job you aren@          attempting to modify, as well your access privileges to          modify the job.  %      B-12 DQS System Manager Messagesj n  e            G          NOPRIV,  need SYSPRV, SYSNAM, OPER, NETMBX, TMBMBX privileges.p  ?             Explanation: Your account does not have the correct.6             privileges, or they have not been enabled.  D             User Action: Change your account registration (or enable/             your privileges) and rerun the IVP.   F          NOREMOTEQUE,  remote queue does not exist or is inaccessible.  B             Explanation: The remote queue you specified during theE             installation does not exist, the network link is down, ori@             the client does not have access to the remote queue.  E             User Action: For a server IVP, reinstall the DQS software F             For a client IVP, check the target queue name, the networkG             link, and that the DQS$QUEUE_queue-name logical name on thelF             server allows the client access. Then reinstall the server'             software and rerun the IVP.l  5          NOSUCHQUE,  no such remote queue queue-name.A  A             Explanation: The remote queue specified by queue-nametB             does not currently exist on the server, even though it3             is defined as a valid DQS remote queue.a  E             User Action: Initialize the specified remote queue on then             server.e  '          NOTOWN,  not owner of the job.:  F             Explanation: You are not the owner of the job that you areG             attempting to delete or modify. The DQS software determinesxG             job ownership by the node name and user name with which theb             job was initiated.  A             User Action: Check to see that you have specified the E             correct job number. If so, make sure that you are working @             from the same account on the same client as when you             initiated the job.  @          NOTSTARTED,  The DQS software has not been started yet.  E             Explanation: The DQS software has not been started on theo             server yet.G  C             User Action: Ask the server system manager to start thefG             DQS software. Print jobs transfer up to 5 minutes after thet             software starts.  H                                         DQS System Manager Messages B-13                 E        NO_ACCESS_CONTROL, no access control strings allowed in serverS          node name.f  =          Explanation: A DQS$REMOTE_client-queue logical name, ?          which specifies a client queue's associated server and A          remote queue, includes access control information in itst          definition.  @          User Action: Redefine the logical name using the formatA          DQS$REMOTE_client-queue server-node::remote-queue. Also,eD          check the definition of the DQS$REMOTE logical name for the:          client queue in the DQS$STARTUP.COM command file.  E        NO_NODE_SPECIFIED, printer queue name does not specify a node.5  A          Explanation: A DQS$REMOTE_client-queue logical name doesf3          not specify a node name in its definition.e  @          User Action: Redefine the logical name using the format@          DQS$REMOTE_client-node server-node::remote-queue. Also,D          check the definition of the DQS$REMOTE logical name for the:          client queue in the DQS$STARTUP.COM command file.  ?        NO_SET_LISTS, list of job numbers for SET not supported.t  B          Explanation: You cannot specify a sequence of job numbers9          in a QSET/ENTRY command, such as /ENTRY=(1,2,3).a  B          User Action: Issue a separate QSET/ENTRY command for each          job entry.v  5        OLDIVP, old IVP job exists in queue, deleting.   A          Explanation: An IVP test print job already exists in the           queue. It is deleted.  >          User Action: No user action. This is an informational          message.i  =        OPENFILE, error opening DQS server configuration file:s          filename.  =          Explanation: Either the DQS$SERVER_UPDATE_CONFIG.EXE ?          program or the DQS$SERVER program encountered an errore0          when trying to open the indicated file.  D          User Action: Check that the file exists and is unprotected.A          Make sure there is sufficient disk space to create a newS          file.  %      B-14 DQS System Manager Messageso a  .            F          P8RESERVED,  parameter P8 is reserved for the DQS software on             remote systems.I  G             Explanation: You specified parameter 8 when issuing a PRINThC             command to a DQS queue. Parameter 8 is reserved for DQSe             information.  F             User Action: Do not specify parameter 8 when using the DQSG             software. Combine parameter 8 arguments with parameter 1 tor"             parameter 7 arguments.  @          PE_MSG_NAME,  INTERNAL SOFTWARE ERROR - Protocol error,              message_type = type.  7             Explanation: This is an internal DQS error.r  '             User Action: Submit an SPR.   B          PE_MSG_NUMBER,  INTERNAL SOFTWARE ERROR - Protocol error,+             unknown message_type = #number.t  7             Explanation: This is an internal DQS error.k  '             User Action: Submit an SPR.   C          PROTOCOL_ERROR,  INTERNAL SOFTWARE ERROR - Protocol error;e.             invalid message received - number.  7             Explanation: This is an internal DQS error.t  '             User Action: Submit an SPR.V  @          READFILE,  error reading DQS server configuration file:             filename.r  @             Explanation: Either the DQS$SERVER_UPDATE_CONFIG.EXEB             program or the DQS$SERVER program encountered an error3             when trying to read the indicated file.   D             User Action: Check that the file exists, is unprotected,F             and is not corrupted. The file's contents may have somehowD             become corrupted. If file name is DQS$SERVER_CONFIG.DAT,?             you can regenerate the file by deleting DQS$SERVER_ D             CONFIG.DAT and then invoking the SYS$MANAGER:DQS$SERVER_E             UPDATE_CONFIG.COM command procedure to recreate the file.   H                                         DQS System Manager Messages B-15 D  a            ,        REC_MSG, received message: "message".  >          Explanation: One of the previous messages came from aC          server that is running obsolete DQS software and that doeso&          not return a full error code.  D          User Action: Install the current version of DQS software on          the server.  +        REINSTALL, install new DQS software.   ?          Explanation: The version of DQS software on the client @          is incompatible with the version of DQS software on the          server.  C          User Action: Make sure that your client and server systemse<          have compatible versions of DQS software installed.  =        REPORT, reporting the following message to the client.   =          Explanation: The subsequent error messages are being '          reported to the client system.e            User Action: None.   A        REQNOEXIST, requeue, remote queue does not exist on remote           system.  ?          Explanation: The queue you specified with a QSET/ENTRY A          /REQUEUE=queue-name command does not exist. You can only D          requeue to a queue that is on the same remote system as the          print job.D  ?          User Action: Requeue your job to another remote queue,eA          or delete the job and submit a new job to a valid remotes          queue.e  A        SHUTDOWN, shutting down queue queue-name because of error.   D          Explanation: An error occurred while processing a print jobA          on the queue queue-name. The queue is stopped because itu!          cannot process any jobs.   B          User Action: Issue a QSHOW command of the specified queueA          to determine the reason for the error. Correct the errorQ          and restart the queue.i  %      B-16 DQS System Manager Messagesa f  u            ?          TOOMANYERRORS,  too many errors talking to the server.h  G             Explanation: Too many errors have occurred while attemptingED             to transfer a print job to a server. The client symbiont-             stops until the problem is fixed.C  ?             User Action: Check the reported errors, rectify thei2             problem, and restart the client queue.  F          UNEXPECTEDSTATE,  INTERNAL SOFTWARE ERROR - Unexpected state:4             UL, encountered while parsing arguments.  A             Explanation: The DQS$SERVER_UPDATE_CONFIG.EXE programnA             detected an inconsistency in its internal state while (             parsing the user input file.  F             User Action: Submit an SPR. If necessary, use the previous@             version of DQS$SERVER_CONFIG_.TXT file and rerun the             program. [En  ?          UNKNOWN_FUNCTION,  INTERNAL SOFTWARE ERROR - function:a"             function-name unknown.  7             Explanation: This is an internal DQS error.U  '             User Action: Submit an SPR.s  G          VALID_MESSAGES,  INTERNAL SOFTWARE ERROR - Valid messages maskd             = number.   G             Explanation: Indicates which messages this server expected.r  '             User Action: Submit an SPR.S  =          WAIT,  waiting for file to transfer to remote queue.n  F             Explanation: The test file is being transferred or will be             transferred.  A             User Action: No user action. This is an informationalt             message.  A          WRITEFILE,  error writing DQS server configuration file:e             filename.e  A             Explanation: The DQS$SERVER_UPDATE_CONFIG.EXE programeF             encountered an error when trying to write to the indicated             file.   :             User Action: Check that the file exists and isB             unprotected. Make sure sufficient disk space exists toB             extend the file. When the problem is fixed, invoke the  H                                         DQS System Manager Messages B-17 m  i            C          SYS$MANAGER:DQS$SERVER_UPDATE_CONFIG.COM command proceduree          to effect the change.  :        XFERFAILED, Failed to transfer job to remote queue.  >          Explanation: The file could not be transferred to the          remote queue.  C          User Action: An additional status message accompanies this C          error message to explain why the transfer failed. Possible @          reasons for the transfer failure include the following:  ?          o  DQS$IVP_TEST_FORM may no longer exist on the server              node.E  +             %JBC-E-NOSUCHFORM\ No such forme  D             To define the DQS$IVP_TEST_FORM, enter the following DCL)             command on the server system:   2             $ DEFINE/FORM DQS$IVP_TEST_FORM 1110 -2                      /STOCK = DQS_IVP_TEST_STOCK -B                      /DESCRIPTION = "DQS test form, do not delete"  C             Define this form on the server and start the IVP again.   D          o  Not enough disk space is available, the DQS software was6             not started, or some other problem exists.  %             %DQS-W-MSG-REMOTE, reason.  ?             The reason defines the problem. Examine the reason, /             correct the problem, and try again.d  8        XFERFAILED, transfer to server failed with error.  B          Explanation: Your current print job failed to transfer toB          the server node for the reason specified in the secondaryC          error message. The DQS software attempts to retransfer the           job after a wait.  D          User Action: If the problem persists, ask the server system?          manager to rectify the problem on the server node. The >          problem may be transient, such as unavailability of a          temporary resource.  %      B-18 DQS System Manager MessagesT N               F          XFERTIME,  timed out trying to transfer file to remote queue.  C             Explanation: The file transfer could not complete in 15              minutes.  B             User Action: Check the network link and rerun the IVP.                                                                              H                                         DQS System Manager Messages B-19 a  n                  H                                                                        CH         ________________________________________________________________  H                                   Server and Client System Logical Names                 ABOUT THIS APPENDIXsD               This appendix alphabetically summarizes the DQS serverC               and client system logical names. Each logical name istH               described briefly, along with its value, function, default(               value (if any), and image.                                                          H                               Server and Client System Logical Names C-1 u  t          E      ________________________________________________________________o        DQS Product Logical Names            IMPORTANTC            The following logical names are used by the DQS software E            and should NOT be modified. These logical name definitionso=            may affect the DQS client software, the DQS server             software, or both.p  E      ________________________________________________________________       Product LogicalE      Name________________Description,_Value,_Default,_and_Image______s  E      DQS$CONFIGURATION   Description: Type of DQS software installed.D  A                          Value: Value is either CLIENT or SERVER.G  '                          Default: None.-  3                          Image: DQS$SERVER, DQS$SMBe  >      DQS$CONTROLLED_     Description: Set by the DQS software.B      ACCESS              Indicates on the server whether or not toE                          check the security database to grant clientsa.                          access to the server.  C                          Default: None. If this logical name is not C                          defined on a server, the DQS software does A                          not check on whether a client is a valid ,                          client of a server.  *                          Image: DQS$SERVER  >      DQS$DENY_ACCESS     Description: Set by the DQS software.E                          Indicates on the server whether to check theoB                          security database to determine if clients?                          have been denied access to the server.n  C                          Default: None. All client nodes are valid.e  *                          Image: DQS$SERVER    /      C-2 Server and Client System Logical Namesj m  a          H         ________________________________________________________________         Product LogicaloH         Name________________Description,_Value,_Default,_and_Image______  A         DQS$QUEUE_remote-   Description: Set by the DQS software.h@         queue               Identifies a queue as a DQS network--                             accessible queue.   B                             Default: None. If this logical name isE                             not defined for a queue, the queue is not <                             available as a DQS remote queue.  -                             Image: DQS$SERVERt  H         DQS$VERSION         Description: A string that names the versionA                             number of the installed DQS software.   H                             Value: Vn.n. The n.n is a number that standsD                             for the currently installed version; for*                             example, V1.3.  D                             Default: Version number of the installedH         ____________________product.____________________________________                                              H                               Server and Client System Logical Names C-3    s          E      ________________________________________________________________         DQS Server Logical Names             MODIFYING NAMES;            DQS software provides the following logical namey>            definitions for the DQS server software. The systemB            manager can modify the definitions in the site-specific;            startup procedure SYS$MANAGER:DQS$SYSTARTUP.COM.   E      ________________________________________________________________       Server LogicalaE      Name________________Description,_Value,_Default_and_Image_______g  B      DQS$ACCOUNTING_BY_  Description: Enables client node names toC      SYSTEM              be used in the account field in a server'si+                          accounting record.u  *                          Value: Arbitrary.  =                          Default: If this logical name is not @                          defined, accounting by client system is%                          not enabled.s  *                          Image: DQS$SERVER  ;      DQS$IDLE_TIME       Description: The delta time that aiE                          DQS$SERVER process maintains a connection to E                          an inactive client that is not sending print                           jobs.  /                          Value: The delta time.e  =                          Default: "0 00:15:00.0" (15 minutes)e  *                          Image: DQS$SERVER  ;      DQS$LOG_ACCESS      Description: Creates a file in the ?                          [DQS$SERVER.NODES] subdirectory of thec>                          DQS server account each time a client@                          establishes a connection to the server.  *                          Value: Arbitrary.  =                          Default: If this logical name is not >                          defined, a file is not created in the6                          [DQS$SERVER.NODES] directory.  *                          Image: DQS$SERVER  /      C-4 Server and Client System Logical Namesk u  t          H         ________________________________________________________________         Server LogicalH         Name________________Description,_Value,_Default_and_Image_______  C         DQS$LOG_AREA        Description: Specifies the directory inoC                             which PrintServer log files are placed.s  =                             Value: The name of the directory.n  F                             Default: The DQS server account directory,)                             [DQS$SERVER].Q  /                             Image: DQS$NOTIFIER   >         DQS$MAX_PRIORITY    Description: Specifies the maximumE                             processing priority with which a user can-:                             have a job queued on a server.  8                             Value: The maximum priority.  F                             Default: The value of the SYSGEN parameter<                             DEFQUEPRI, which is usually 100.  -                             Image: DQS$SERVER   E         DQS$NOTIFY_CYCLE_   Description: Interval at which the servertD         TIME                process scans remote queues to determine9                             when print jobs are complete.   >                             Value: Time in OpenVMS delta time.  ?                             Default: "0 00:05:00.0" (5 minutes)   /                             Image: DQS$NOTIFIERn  G         DQS$NOTIFY_LOCK     Description: Prevents multiple DQS$NOTIFIERsC                             processes from running on a homogeneoust.                             VMScluster system.  8                             Value: The name of the lock.  1                             Default: DQS$NOTIFIERa  /                             Image: DQS$NOTIFIER   E         DQS$PRIORITY        Description: Priority at which the servers)                             process runs.   H                             Value: Form decimal number between 0 and 16.  0                             Default: Priority 4.  -                             Image: DQS$SERVERe  H                               Server and Client System Logical Names C-5 m  a          E      ________________________________________________________________f      Server LogicalEE      Name________________Description,_Value,_Default_and_Image_______o  C      DQS$SERVER_CONFIG_  Description: Specifies the location of the 4      TXT_FILE            DQS$SERVER_CONFIG.TXT file.  2                          Value: File specification  @                          Default: SYS$COMMON:[SYSMGR]DQS$SERVER_#                          CONFIG.TXTM  <                          Image: DQS$SERVER_UPDATE_CONFIG.EXE  C      DQS$SERVER_CONFIG_  Description: Specifies the location of the 4      DAT_FILE            DQS$SERVER_CONFIG.DAT file.  2                          Value: File specification  @                          Default: SYS$COMMON:[SYSMGR]DQS$SERVER_#                          CONFIG.DATa  =                          Image: DQS$SERVER_UPDATE_CONFIG.EXE,e#                          DQS$SERVER   A      DQS$SERVER_         Description: Places a note on the bannerOB      DEFAULT_JOB_NOTE    page of DQS jobs to indicate that the DQS<                          software was used to print the job.  B                          Value: Text string that is the message to@                          print on the banner page of print jobs.  E                          Default: Text string "Print Job processed byr#                          DQS V1.3."i  *                          Image: DQS$SERVER  E      DQS$STATUS_queue-   Description: Specifies that a status messaged>      name                for a queue is displayed when a QSHOW8                          command of the queue is issued.  A                          Value: Arbitrary text string that is the 8                          status message to be displayed.  =                          Default: If this logical name is notrA                          defined, no status message is displayed.i  E      ____________________Image:_DQS$CLIENT,_DQS$SMB,_DQS$SERVER______n  /      C-6 Server and Client System Logical Namesi s  n          H         ________________________________________________________________           Client Logical Names               MODIFYING NAMESQ>               DQS software provides the following logical nameH               definitions for the DQS client software. These definitionsH               can be modified by the system manager in the site-specific>               startup procedure SYS$MANAGER:DQS$SYSTARTUP.COM.  H         ________________________________________________________________         Client LogicalH         Name________________Description,_Value,_Default,_and_Image______  D         DQS$CLIENT_         Description: Places a note on the bannerE         DEFAULT_JOB_NOTE    page of DQS jobs to indicate that the DQS ?                             software was used to print the job.f  E                             Value: Text string that is the message tofC                             print on the banner page of print jobs.t  G                             Default: Text string "Print Job transporteds)                             by DQS V1.3."i  *                             Image: DQS$SMB  B         DQS$FORM_OVERRIDE   Description: Overrides a client's formD                             definition with its server's definition.  -                             Value: Arbitrary.x  *                             Default: None.  -                             Image: DQS$CLIENTN  D         DQS$REMOTE_client-  Description: Associates the client queueG         queue               with a corresponding server system (or with H                             multiple servers) and with a remote queue on(                             each server.  H                             Value: The server node name and remote queueC                             name in the format server-node::remote-a"                             queue.  D                             Default: None. This logical name must beF                             defined in order for the queue to function2                             as a DQS client queue.  6                             Image: DQS$SMB, DQS$CLIENT  H                               Server and Client System Logical Names C-7 a  f          E      ________________________________________________________________h      Client LogicalnE      Name________________Description,_Value,_Default,_and_Image______t  E      DQS$STATUS_queue-   Description: Specifies that a status messagen>      name                for a queue is displayed when a QSHOW8                          command of the queue is issued.  A                          Value: Arbitrary text string that is theA8                          status message to be displayed.  =                          Default: If this logical name is notEA                          defined, no status message is displayed.   E      ____________________Image:_DQS$CLIENT,_DQS$SMB,_DQS$SERVER______                                                               /      C-8 Server and Client System Logical NamesG X  i                  H                                                                        DH         ________________________________________________________________  H                                         Using DQS With Various Symbionts                 ABOUT THIS APPENDIX ?               This appendix describes how jobs print when printbF               symbionts other than the DQS print symbiont (DQS$PRTSMB)1               are used to process DQS print jobs.S  ?               Any symbiont that is built according to the rules C               specified in the OpenVMS documentation should be able (               to process DQS print jobs.                                                    H                                     Using DQS With Various Symbionts D-1 o  g          E      _________________________________________________________________  #      How Various Symbionts Function       #      REPLACING THE OPENVMS SYMBIONToA            Only the OpenVMS print symbiont PRTSMB can be replacedkC            with the DQS print symbiont DQS$PRTSMB. Replacing PRTSMBiA            with the DQS print symbiont causes client-specific jobrD            information to be printed on the flag, burst, and trailerE            pages of DQS print output. This is recommended because theGC            job information includes the client node job number, thetD            client node name, and the time the print job is queued on            the client node.   @            Other symbionts cannot be replaced with the DQS printB            symbiont. In these cases, the server job number and the?            time that the print job was queued on the server arei!            printed on the output.s        LIST OF PRINT SYMBIONTS>            The following is a list of various print symbionts:  E            o  Standard OpenVMS print symbiont (PRTSMB). The DQS printe;               symbiont should replace the OpenVMS symbiont.l  E            o  PrintServer 40 symbiont (LPS$SMB). The LPS$SMB symbiontE;               cannot be replaced by the DQS print symbiont.C  @            o  LAT printer symbiont (LATSYM). The LATSYM symbiont;               cannot be replaced by the DQS print symbiont.h  >            o  User-modified symbionts. User-modified symbiontsD               cannot be replaced by the DQS print symbiont. However,?               users can modify their symbionts to print client-o?               specific information, as described in the sectionsA               titled Modifying Your Symbiont To Output Client JobE               Information.  C            o  User-written symbionts. User-written symbionts cannote?               be replaced with the DQS print symbiont. However,e?               users can modify their symbionts to print client-m?               specific information, as described in the sectioneA               titled Modifying Your Symbiont To Output Client Jobm               Information.  )      D-2 Using DQS With Various Symbiontsm b  r          H         ________________________________________________________________  @         Modifying Your Symbiont To Output Client Job Information               FORMATC               DQS remote user information is stored in parameter 8.fF               You can modify your symbiont to use this client-specificG               print information. The user information has the following                format:   3               DQS: nnnnxjob-owner dd-mmm-yyyy hh:mm                  Where:  D               nnnn             Is the job number on the client node.F                                This requires a minimum of 4 charactersD                                and a maximum of 10. If the number isE                                less than 4 characters, the job number 7                                contains leading spaces.h  H               x                Is a single nonnumeric code that delimits.                                the job number.  F               job-owner        Is the client's node name (which may beD                                trimmed) a double colon (::), and the2                                client's user name.  F               dd-mmm-yyyy      Is the date and time the job was queued-               hh:mm            on the client._           EXAMPLEuD               In this example of a remote user name, each circumflex5               character ( ^ ) denotes a single space.s  <               DQS:^^^12xAPPLES::SHANNON^^^^05-FEB-1994^04:55  %         IMPORTANT PARSING INFORMATIONeE               Additional considerations for using parameter 8 include_               the following:  D               o  If a parameter 8 string does not parse according toE                  the format as specified, it is not processed as a P8r                  string.  H                                     Using DQS With Various Symbionts D-3 V  G            E            o  When interpreting the job-number field, if the value of$E               the job-number is zero, the symbiont uses the local jobSE               number associated with the print job by the batch/print E               system. (This works because the value 0 is currently anl"               illegal job number.)  D            o  When processing the job-owner field, a symbiont shouldC               treat the entire job-owner as a string. The string is D               terminated by the first space. On OpenVMS systems, theE               job-owner for DQS purposes has the form NODE::USERNAME.   E               Because of restrictions with trimmed full node names, aiA               symbiont should not rely on the NODE-NAME::USERNAME >               type syntax, nor should a symbiont interpret the.               contents of the job-owner field.  B            o  The P8 string has a maximum length of 254 characters2               (not including the null terminator).  B            o  Digital reserves the right to add new information toB               the end of the P8 string. Print symbionts that parseD               this string should not depend on the string length norE               should they interpret undocumented information that may,/               appear in a particular P8 string.e  E      DIFFERENCES_FROM_PREVIOUS_VERSIONS______________________________iE            Item________In_Version_1.2___In_Version_1.3_______________e  E            Job         Always 4         May be more than 4 characterss-            Number      characters       long.             field       long.  B            Job Owner   Number of        Always one space after the.            field       spaces after     field.                         the fieldE            ____________varies._______________________________________h                  )      D-4 Using DQS With Various Symbiontsu V  .                  H                                                                        EH         ________________________________________________________________  H                                Files Installed or Modified on the System                 ABOUT THIS APPENDIX_C               This appendix describes the files produced or changed H               during the DQS installation. This information is organized               as follows:_  H               __________________________________________________________H               SectionTopic______________________________________________  4                 1    Files installed on server nodes  9                 2    Files installed on client-only nodesf  @                 3    Existing files modified by the installation  E                 4    Accounts and processes added by the installation_  H               __5____Installed_images___________________________________  G               Unless otherwise specified, all files are copied from theY               DQS savesets.t           FOR MORE INFORMATIOND               For more information on using and modifying DQS files,?               refer to the Part II, the System Manager's Guide.r                    H                            Files Installed or Modified on the System E-1    d          E      ________________________________________________________________   $      Files Installed on Server Nodes  A            Table E-1 lists the files that are installed on server             nodes.   E            Table_E-1_Files_Installed_on_DQS_Server_Nodes_____________   E            File_Name_____________Description_________________________j  E            ___________________Added_to_SYS$MANAGER:__________________   E            DQS$CLEANSRV.COM      Deletes lost files in the DQS server D                                  account. There are a few conditionsA                                  where files may be "lost" in thec+                                  directory.r  C            DQS$DEFINE.COM        Defines DQS client queues. InvokedcD                                  by the DQS$IMPORT, DQS$IVP, and the=                                  DQS$SYSTARTUP command files.o  :            DQS$IMPORT.COM        Allows you to Add another@                                  client queue to the current DQS@                                  configuration on a client node.  ?            DQS$SERVER_CHANGE_    Allows you to move the default_E            DEFAULT_DEVICE.COM    server account directory to a devicec>                                  other than the system device.  E            DQS$SERVER_           Allows you to define a set of serverrC            CONFIG.TEMPLATE       queues accessible over the networkr?                                  and to control access to thesed(                                  queues.  B            DQS$SERVER_           Provides information about client>            CONFIG.TXT            node access to server queues.  D            DQS$SERVER_UPDATE_    Allows you to enable changes to the<            CONFIG.COM            DQS$SERVER_CONFIG.TXT file.  C            DQS$SERVER_UPDATE_    Allows you to update server queues B            QUEUE_DEFNS.COM       by removing the /RETAIN qualifier5                                  for DQS Version 1.3.r  E                                              (continued on next page)   2      E-2 Files Installed or Modified on the System Q  O            H               Table_E-1_(Cont.)_Files_Installed_on_DQS_Server_Nodes_____  H               File_Name_____________Description_________________________  H               __________________Added_to_SYS$MANAGER:___________________  E               DQS$SYSTARTUP.        Allows you to modify server site-mE               TEMPLATE              specific logical definitions that B                                     affect the behavior of the DQS-                                     software.g  H               __________________________________________________________H               __________________Added_to_SYS$STARTUP:___________________  D               DQS$STARTUP.COM       Defines DQS defaults and logicalG                                     names and invokes the site-specifictG                                     DQS$SYSTARTUP.COM. This new startup @                                     procedure is provided by theH                                     installation. Do not edit this file.  H               __________________________________________________________H               __________________Added_to_SYS$MESSAGE:___________________  F               DQS$MSG.EXE           Provides the text for DQS-specific3                                     error messages.o  H                                                 (continued on next page)                                    H                            Files Installed or Modified on the System E-3                 E            Table_E-1_(Cont.)_Files_Installed_on_DQS_Server_Nodes_____N  E            __________________________________________________________   E            ___________________Added_to_SYS$SYSTEM:___________________   D            DQS$CLIENT.EXE        The user command execution program.>                                  Executes the QSHOW, QSET, and2                                  QDELETE commands.  @            DQS$NOTIFIER.EXE      A detached process that runs onA                                  the server node. Sends print jobD>                                  notification to client users.  E            DQS$PRTSMB.EXE        Replaces the standard print symbiont @                                  on the server node. Places DQS-B                                  specific information on the FLAG,B                                  BURST, and TRAILER pages of printA                                  output. Use this symbiont if you C                                  do not like how the standard print$D                                  symbiont handles information on the.                                  banner pages.  A            DQS$SERVER.EXE        The DQS server program. Receivesu>                                  incoming requests from clientD                                  nodes and processes them. Processes@                                  all DQS commands (PRINT, QSHOW,D                                  QDELETE, and QSET). If notification<                                  is requested, also performsA                                  notification on the client node.e  A            DQS$SERVER_           Private DQS server configuration_C            CONGFIG.DAT           data file. This file is created by A                                  the DQS$SERVER_UPDATE_CONFIG.COMnB                                  procedure. Do not edit this file.  E            DQS$SERVER_UPDATE_    Server configuration update program.             CONFIG.EXE   B            DQS$SMB.EXE           The DQS symbiont. Transfers print?                                  jobs and files from the client_6                                  system to the server.  E                                              (continued on next page)   2      E-4 Files Installed or Modified on the System _  _            H               Table_E-1_(Cont.)_Files_Installed_on_DQS_Server_Nodes_____  H               File_Name_____________Description_________________________  H               ____________________Added_to_SYS$TEST:____________________  B               DQS$IVP.COM           Verifies that the DQS softwareH                                     installation completed successfully.  H               __________________________________________________________H               ____________________Added_to_SYS$HELP:____________________  A               DQSnnn.RELEASE_       The release notes for the DQSuC               NOTES                 product. The nnn represents the H                                     version number; for example, 013 forH               ______________________Version_1.3.________________________                                                          H                            Files Installed or Modified on the System E-5               E      ________________________________________________________________o  )      Files Installed on Client-Only Nodes   D            Table E-2 lists the files installed on a DQS client node.  E            Table_E-2_Files_Installed_on_DQS_Client-Only_Nodes________   E            File_Name_____________Purpose_____________________________   E            ___________________Added_to_SYS$MANAGER:__________________   C            DQS$DEFINE.COM        Defines DQS client queues. InvokeddD                                  by the DQS$IMPORT, DQS$IVP, and the=                                  DQS$SYSTARTUP command files.n  :            DQS$IMPORT.COM        Allows you to Add another@                                  client queue to the current DQS@                                  configuration on a client node.  B            DQS$SYSTARTUP.        Allows you to modify client site-B            TEMPLATE              specific logical definitions that?                                  affect the behavior of the DQSi*                                  software.  E            __________________________________________________________uE            ___________________Added_to_SYS$STARTUP:___________________  >            DQS$STARTUP.COM       Starts the DQS client queues.:                                  Invokes the site-specificD                                  DQS$SYSTARTUP.COM. Do not edit this&                                  file.  E            ___________________________________________________________E            ___________________Added_to_SYS$MESSAGE:__________________m  C            DQS$MSG.EXE           Provides the text for DQS-specifici0                                  error messages.  E                                              (continued on next page)             2      E-6 Files Installed or Modified on the System t  a            B               Table E-2 (Cont.) Files Installed on DQS Client-OnlyH               __________________Nodes___________________________________  H               __________________________________________________________  H               ___________________Added_to_SYS$SYSTEM:___________________  G               DQS$CLIENT.EXE        The user command execution program.sA                                     Executes the QSHOW, QSET, and 5                                     QDELETE commands.r  @               DQS$SERVER.EXE        If print job notification isD                                     requested, performs notification7                                     on the client node.g  E               DQS$SMB.EXE           The DQS symbiont. Transfers printmB                                     jobs and files from the client9                                     system to the server.t  H               __________________________________________________________H               ____________________Added_to_SYS$TEST:____________________  =               DQS$IVP.COM           Verifies the DQS softwarehH                                     installation completed successfully.  H               __________________________________________________________H               ____________________Added_to_SYS$HELP:____________________  A               DQSnnn.RELEASE_       The release notes for the DQShC               NOTES                 product. The nnn represents theBH                                     version number, for example, 013 forH               ______________________Version_1.3.________________________                          H                            Files Installed or Modified on the System E-7 b  t          E      ________________________________________________________________b  '      Files Modified by the Installationi            MODIFIED FILES ?            The DQS software modifies the following files during             installation:  1            o  SYS$HELP:HELPLIB.HLB - Help library   @            o  SYS$LIBRARY:DCLTABLES.EXE - DCL command definition               tables  @            o  DQS$STARTUP.COM_OLD - Older version of the startupC               command file renamed by the Version 1.3 installation.m@               Defines DQS defaults and all DQS logical names for(               previous version software.                                                      2      E-8 Files Installed or Modified on the System               H         ________________________________________________________________  $         Accounts and Processes Added  B               The DQS installation adds the following accounts and               processes:             ACCOUNTS: G               A DQS client/server account, DQS$SERVER, is added to both &               server and client nodes.  C               The DQS$SERVER account is given the following OpenVMS:               privilges:                 o  TMPMBXh                 o  NETMBX            PROXIES:7               No proxies are added by the installation.            DECNET OBJECTS:oH               The following are created on both server and client nodes:                 o  Object: DQS                 o  Number: 66r  )               o  File/PID: DQS$SERVER.EXE   $               o  User ID: DQS$SERVER  #               o  Proxy access: nonen           NOTE@               The default user ID is DQS$SERVER; the password isC               randomly generated during the installation procedure.            PROCESSES:F               On clients, each newly created client queue (that is notD               a generic or logical queue) results in a process beingH               created. Also, while print job notification is returned to<               a client user, a temporary process is created.    H                            Files Installed or Modified on the System E-9 a  s            C            On servers, each logical link to a client node creates aTC            process. Also, the notification process on a server uses !            one permanent process.                                                                                     3      E-10 Files Installed or Modified on the Systemt               H         ________________________________________________________________           Installed Images               EXECUTABLE FILESE               The following executables are installed as known images "               when DQS is started:  H               __________________________________________________________H               Image____________Privileges_______________________________  D               DQS$NOTIFIER     CMKRNL, ALTPRI, OPER, TMPMBX, NETMBX,$                                WORLD  D               DQS$SERVER       SYSPRV, CMKRNL, ALTPRI, OPER, TMPMBX,,                                NETMBX, WORLD                 DQS$MSG   H               DQS$SMB___________________________________________________                                                H                           Files Installed or Modified on the System E-11    y                  H                                                                        FH         ________________________________________________________________  H                                                     Sample Installations                 ABOUT THIS APPENDIX G               This appendix contains sample installation dialogs of thenB               DEC Distributed Queuing Service for OpenVMS Systems.  H               __________________________________________________________H               SectionTopic______________________________________________  E                 1    Sample PCSI installations on OpenVMS VAX systems_  F                 2    Sample VMSINSTAL installations on OpenVMS VAX andH               _______AXP_systems________________________________________                                              H                                                 Sample Installations F-1 N  e          E      ________________________________________________________________i  2      Sample PCSI Installation on an OpenVMS System            CLIENT INSTALLATIONB            Example F-1 shows a sample DQS PCSI client installationB            on an OpenVMS VAX system. The DQS software resides in a@            directory pointed to by the PCSI$SOURCE logical name.  >      Example F-1 Sample PCSI Client Installation on an OpenVMS                  System   0      $ DEFINE PCSI$SOURCE NODEA$MKA500: <Return>#      $ PRODUCT INSTALL DQS <Return>   -      The following product has been selected:o      DEC VAXVMS DQS V1.3  ,      Do you want to continue? [YES] <Return>  =      *** DEC VAXVMS DQS V1.3: DEC VAXVMS DQS V1.3 for OpenVMS_  7          Copyright  1994 Digital Equipment Corporation &          Digital Equipment Corporation  3          This product uses the PAKs:  DEC DQS V1.3.s  I      Do you want all the default values for this product? [YES]  <Return>   3      Do you want to view the values? [NO]  <Return>b        Execution phase starting -      The following product will be installed:s      DEC VAXVMS DQS V1.3;      Estimated space information for volume DISK$OPENVMS060 -      710 required; 64060 available; 63350 net @      Portion Done: 0%...10%...20%...40%...60%...70%...90%...100%.      The following product has been installed:      DEC VAXVMS DQS V1.3      Start of test procedure4      End of test procedure; completed with no errors  =      *** DEC VAXVMS DQS V1.3: DEC VAXVMS DQS V1.3 for OpenVMSo  E                                              (continued on next page)_        F-2 Sample Installations_ _  _            A         Example F-1 (Cont.) Sample PCSI Client Installation on anl*                             OpenVMS System  B             [DQS$SERVER] directory is created in SYS$COMMON: area.*             DQS$SERVER account is created.  B             This product requires the following SYSGEN parameters:$                 GBLPAGES minimum 600B             This product requires the following SYSGEN parameters:%                 GBLSECTIONS minimum 5   0             The client installation is complete.*             DQS network object is created.7             Perform post-installation before using DQS.o	         $                                                             H                                                 Sample Installations F-3                 )      PCSI INSTALLATION OF SERVER SOFTWAREo@            Example F-2 shows a sample DQS server installation on?            an OpenVMS VAX system. The DQS software resides in a @            directory pointed to by the PCSI$SOURCE logical name.    ?      Example F-2 Sample PCSI Server Installation on OpenVMS VAX                   System   0      $ DEFINE PCSI$SOURCE NODEA$MKA500: <Return>#      $ PRODUCT INSTALL DQS <Return>   -      The following product has been selected: (      DEC VAXVMS DQS V1.3     [Available]  ,      Do you want to continue? [YES] <Return>  =      *** DEC VAXVMS DQS V1.3: DEC VAXVMS DQS V1.3 for OpenVMSo  7          Copyright  1994 Digital Equipment Corporation.  &          Digital Equipment Corporation  3          This product uses the PAKs:  DEC DQS V1.3.   F          Do you want all the default values for this product? [YES] NO  4              *** DEC VAXVMS VMS V6.1     [Available]  Q          You need to complete the pre-installation tasks to install DQS software.o0          Do you want to continue? [YES] <Return>  J      The DQS client software will be installed automatically on this node.  R      Do you want to install the DQS server software on this node [NO] YES <Return>  3      Do you want to view the values? [NO]  <Return>h  E                                              (continued on next page)l                  F-4 Sample Installations  i  N            F         Example F-2 (Cont.) Sample PCSI Server Installation on OpenVMS&                             VAX System            Execution phase starting0         The following product will be installed:         DEC VAXVMS DQS V1.3 >         Estimated space information for volume DISK$OPENVMS0601         1018 required; 64248 available; 63230 net O         Portion Done: 0%...10%...20%...30%...40%...50%...70%...80%...90%...100%_1         The following product has been installed:_         DEC VAXVMS DQS V1.3P         Start of test procedure 7         End of test procedure; completed with no errorsl  @         *** DEC VAXVMS DQS V1.3: DEC VAXVMS DQS V1.3 for OpenVMS  B             [DQS$SERVER] directory is created in SYS$COMMON: area.  *             DQS$SERVER account is created.  B             This product requires the following SYSGEN parameters:$                 GBLPAGES minimum 600  B             This product requires the following SYSGEN parameters:%                 GBLSECTIONS minimum 5e  0             The client installation is complete.  0             The server installation is complete.  *             DQS network object is created.  7             Perform post-installation before using DQS. 	         $i                      H                                                 Sample Installations F-5 o  o          E      ________________________________________________________________I  ;      Sample VMSINSTAL Installation on an OpenVMS AXP System_            CLIENT INSTALLATION@            Example F-3 shows a sample installation of DQS clientA            software on an OpenVMS AXP system, using the VMSINSTALo            utility.a  C      Example F-3 Sample VMSINSTAL Client Installation on an OpenVMS                   AXP SystemQ        Username: SYSTEM <Return>      Password: <Return>c  3      $ @SYS$UPDATE:VMSINSTAL DQS013 MKA500:<Return>   =      OpenVMS AXP Software Product Installation Procedure V6.1          It is 22-MAR-1994 at 13:57.  4      Enter a question mark (?) at any time for help.  C      %VMSINSTAL-W-ACTIVE, The following processes are still active:P              DQS$NOTIFIER   8      * Do you want to continue anyway [NO]? YES <Return>L      * Are you satisfied with the backup of your system disk [YES]? <Return>  :      Please mount the first volume of the set on  MKA500:."      * Are you ready? YES <Return>4      %MOUNT-I-MOUNTED, DQS mounted on _AXPPD$MKA500:  .      The following products will be processed:          DQS V1.3   8              Beginning installation of DQS V1.3 at 14:06  ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ...mP      %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  I              The DQS client will be installed automatically on this node.,  E                                              (continued on next page)         F-6 Sample Installations  u  e            F         Example F-3 (Cont.) Sample VMSINSTAL Client Installation on an.                             OpenVMS AXP System  T         * Do you want to install the DQS server software on this node [NO]? <Return>K         * Do you want to run the IVP after the installation [YES]? <Return> R         * Do you want to purge files replaced by this installation [YES]? <Return>  !                 Product:      DQSp!                 Producer:     DECX!                 Version:      1.3 (                 Release Date: 7-MAR-1994  Y         * Does this product have an authorization key registered and loaded? YES <Return>   %                 No further questions.   >         %VMSINSTAL-I-RESTORE, Restoring product save set B ...T         %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER..         %UAF-I-MDFYMSG, user record(s) updatedT         %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER..         %UAF-I-MDFYMSG, user record(s) updatedT         %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER..         %UAF-I-MDFYMSG, user record(s) updated  4                 Installing DQS CLIENT software . . .  K              Checksum file updated last by WEBER on 22-MAR-1994 09:40:50.30_  9         %NET$CONFIGURE-I-VERCHECKSUM, verifying checksums U         %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by          NET$CONFIGUREeX         %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet/OSI for OpenVMS configuration completedL              Checksum file updated last by SYSTEM on 22-MAR-1994 14:08:08.73  9         %NET$CONFIGURE-I-VERCHECKSUM, verifying checksums T         %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account DQS$SERVERC         $NCL @SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL-TEMP;   .         Node 0 Session Control Application DQS.         at 1994-03-22-14:08:16.150-05:00I0.649           Characteristics   H                                                 (continued on next page)  H                                                 Sample Installations F-7 _  _            C      Example F-3 (Cont.) Sample VMSINSTAL Client Installation on an +                          OpenVMS AXP System   ,          Addresses                         =
             {                 number = 66
             }T<          Client                            = <Default value>2          Incoming Alias                    = False2          Incoming Proxy                    = False2          Outgoing Alias                    = False2          Outgoing Proxy                    = False2          Node Synonym                      = FalseF          Image Name                        = SYS$SYSTEM:DQS$SERVER.EXE9          User Name                         = "DQS$SERVER"f<          Incoming OSI TSEL                 = <Default value>        $vef = F$verify(vef) R      %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by      NET$CONFIGUREU      %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet/OSI for OpenVMS configuration completed Q      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER. +      %UAF-I-MDFYMSG, user record(s) updated_  +              DQS network object is created._  O              ****************************************************************** O              *           Instructions for completing DQS installation         * O              ******************************************************************t  J              o Please follow the post installation instructions which have@                been outlined in the DQS V1.3 Installation Guide.  K              o Please be sure to edit your OpenVMS System Startup Procedure_N                and add the following line to invoke the DQS Startup Procedure:  3                      $ @SYS$STARTUP:DQS$STARTUP.COMA  K              o Once you have completed the DQS post installation procedureshM                you can invoke the DEC DQS installation verification proceduresI                to test your customizations. To invoke this file start DQSs                and type:  ,                      $ @SYS$TEST:DQS$IVP.COM  E                                              (continued on next page)         F-8 Sample Installationst c  n            F         Example F-3 (Cont.) Sample VMSINSTAL Client Installation on an.                             OpenVMS AXP System  I                 o This installation has updated the DCL Tables. ThereforetJ                   users must log out and then back in, in order to use theM                   QSHOW, QDELETE, and QSET commands for displaying, deleting, A                   and modifying jobs on the remote server queues.   L                 o Please read the DQS V1.3 release notes located in the file1                   SYS$HELP:DQS013.RELEASE_NOTES ._  V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  H         Beginning of the DQS V1.3-0 Installation Verification Procedure.  L           Copyright Digital Equipment Corporation 1994. All rights reserved.  S           Restricted Rights: Use, duplication, or disclosure by the U.S. Government_O           is subject to restrictions as set forth in subparagraph (c)(1)(ii) of S           DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as_           applicable._  R           This software is proprietary to and embodies the confidential technologyO           of Digital Equipment Corporation. Possession, use, or copying of thisdS           software and media is authorized only pursuant to a valid written license 4           from Digital or an authorized sublicensor.  -         %DQS-I-QUESUCCESS IVP test successful Q         End of the DEC DQS for OpenVMS V1.3-0 Installation Verification Procedurer  ;                 Installation of DQS V1.3 completed at 14:08   F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  M             Creating installation data file: VMI$ROOT:[SYSUPD]DQS013.VMI_DATAI  1                 VMSINSTAL procedure done at 14:08 	         $_              H                                                 Sample Installations F-9 s  A                  SERVER INSTALLATIONB            Example F-4 shows a sample installation of a DQS serverD            on an OpenVMS VAX system using the VMSINSTAL installation            procedure.     D      Example F-4 Sample VMSINSTAL Server Installation on OpenVMS VAX                  Systemn        Username: SYSTEM <Return>      Password: <Return>P  1      $ @SYS$UPDATE:VMSINSTAL DQS013 MUA0:<Return>   I              OpenVMS VAX Software Product Installation Procedure T6.1-5Y3J         It is 18-MAR-1994 at 09:51.  4      Enter a question mark (?) at any time for help.  C      %VMSINSTAL-W-ACTIVE, The following processes are still active:               _FTA13:              DAVIES               _FTA6:R8      * Do you want to continue anyway [NO]? YES <Return>L      * Are you satisfied with the backup of your system disk [YES]? <Return>  .      The following products will be processed:          DQS V1.3R  7              Beginning installation of DQS V1.3 at 9:53n  ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ...   P      %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  I              The DQS client will be installed automatically on this node..  L      * Do you want to install the DQS server software on this node [NO]? YES  3                               *** PLEASE NOTICE ***   E                                              (continued on next page)i        F-10 Sample Installations    o            C         Example F-4 (Cont.) Sample VMSINSTAL Server Installation on .                             OpenVMS VAX System  P                 If you are upgrading DQS server software from an earlier versionP                 to DQS V1.3, the earlier version of the DQS server software mustS                 be running. This allows the DQS V1.3 installation procedure to readeN                 the existing DQS server configuration information and create aI                 new DQS V1.3 server configuration file.  Otherwise, aftereK                 installation, you must manually update your DQS V1.3 serverT#                 configuration file.   M                 The directory and name of the DQS V1.3 configuration file is:R  9                         SYS$MANAGER:DQS$SERVER_CONFIG.TXTD  J                 Digital recommends that you review the new DQS V1.3 serverP                 configuration file after this installation. Refer to the sectionO                 on server management in the DQS System Manager's Guide for more                  information.  P                 The DQS client configuration is not automatically updated. ReferO                 to the section on client management in the DQS System Manager's +                 Guide for more information.   0         * Do you want to proceed [YES]? <RETURN>K         * Do you want to run the IVP after the installation [YES]? <RETURN>uR         * Do you want to purge files replaced by this installation [YES]? <RETURN>               Product:      DQS !                 Producer:     DEC_!                 Version:      1.3_(                 Release Date: 7-MAR-1994P         * Does this product have an authorization key registered and loaded? YES  %                 No further questions._  >         %VMSINSTAL-I-RESTORE, Restoring product save set B ...T         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DQS$SERVER.5         %UAF-I-ADDMSG, user record successfully added_X         %UAF-I-RDBADDMSGU, identifier DQS$SERVER value [000300,000311] added to rights d         atabasey  .                 DQS$SERVER account is created.  H                                                 (continued on next page)  H                                                Sample Installations F-11    t            @      Example F-4 (Cont.) Sample VMSINSTAL Server Installation on+                          OpenVMS VAX System   Q      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER. +      %UAF-I-MDFYMSG, user record(s) updatedtQ      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER. +      %UAF-I-MDFYMSG, user record(s) updated.Q      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER. +      %UAF-I-MDFYMSG, user record(s) updatediU      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[DQS       $SERVER].  C              [DQS$SERVER] directory is created in SYS$COMMON: area.   1              Installing DQS SERVER software . . .p  1              Installing DQS CLIENT software . . .   F           Checksum file updated last by CHO on 17-MAR-1994 09:48:25.61  6      %NET$CONFIGURE-I-VERCHECKSUM, verifying checksumsU      %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NEe      T$CONFIGUREU      %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet/OSI for OpenVMS configuration completed F           Checksum file updated last by CHO on 18-MAR-1994 09:56:48.116      %NET$CONFIGURE-I-VERCHECKSUM, verifying checksumsQ      %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account DQS$SERVERx@      $NCL @SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL-TEMP;  +      Node 0 Session Control Application DQS +      at 1994-03-18-09:57:00.327-05:00I0.289M  +      Node 0 Session Control Application DQSr+      at 1994-03-18-09:57:00.947-05:00I0.289h  E                                              (continued on next page)                         F-12 Sample Installations r  t            C         Example F-4 (Cont.) Sample VMSINSTAL Server Installation ono.                             OpenVMS VAX System           Characteristicsf/             Addresses                         =                 {                   number = 66                 }?             Client                            = <Default value>F5             Incoming Alias                    = FalseR5             Incoming Proxy                    = Falsee5             Outgoing Alias                    = False 5             Outgoing Proxy                    = Falsei5             Node Synonym                      = FalsepI             Image Name                        = SYS$SYSTEM:DQS$SERVER.EXEs<             User Name                         = "DQS$SERVER"?             Incoming OSI TSEL                 = <Default value>s           $vef = F$verify(vef)X         %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NE         T$CONFIGURE X         %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet/OSI for OpenVMS configuration completedT         %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER..         %UAF-I-MDFYMSG, user record(s) updated  .                 DQS network object is created.  P               ******************************************************************P               *           Instructions for completing DQS installation         *P               ******************************************************************  M                 o Please follow the post installation instructions which have C                   been outlined in the DQS V1.3 Installation Guide.   N                 o Please be sure to edit your OpenVMS System Startup ProcedureQ                   and add the following line to invoke the DQS Startup Procedure:   6                         $ @SYS$STARTUP:DQS$STARTUP.COM  N                 o Once you have completed the DQS post installation proceduresP                   you can invoke the DEC DQS installation verification procedureL                   to test your customizations. To invoke this file start DQS                   and type:o  H                                                 (continued on next page)  H                                                Sample Installations F-13    t            @      Example F-4 (Cont.) Sample VMSINSTAL Server Installation on+                          OpenVMS VAX SystemX  ,                      $ @SYS$TEST:DQS$IVP.COM  F              o This installation has updated the DCL Tables. ThereforeG                users must log out and then back in, in order to use theGJ                QSHOW, QDELETE, and QSET commands for displaying, deleting,>                and modifying jobs on the remote server queues.  I              o Please read the DQS V1.3 release notes located in the file .                SYS$HELP:DQS013.RELEASE_NOTES .  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   C      Beginning of the DQS V1.3 Installation Verification Procedure.   I        Copyright Digital Equipment Corporation 1994. All rights reserved.   P        Restricted Rights: Use, duplication, or disclosure by the U.S. GovernmentL        is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofP        DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as        applicable.  O        This software is proprietary to and embodies the confidential technologyML        of Digital Equipment Corporation. Possession, use, or copying of thisP        software and media is authorized only pursuant to a valid written license1        from Digital or an authorized sublicensor.f  *      %DQS-I-QUESUCCESS IVP test successfulL      End of the DEC DQS for OpenVMS V1.3 Installation Verification Procedure  8              Installation of DQS V1.3 completed at 09:57  .              VMSINSTAL procedure done at 09:57        $                      F-14 Sample Installations                       H                                                                        GH         ________________________________________________________________  H                                                DQS Installation Messages                 ABOUT THIS APPENDIX C               This appendix describes error messages that you might1F               encounter when you install or verify the installation ofH               DQS software. Suggestions for error recovery are included,G               as well as instructions for reporting problems to DigitaliG               for irrecoverable errors. Refer to the following sectionsx.               for information on these topics:  H               __________________________________________________________H               SectionTopic______________________________________________  0                 1    Installation error messages  '                 2    IVP error messages   H               __3____Error_reporting____________________________________           MESSAGE FORMAT<               All DQS error messages begin with this prefix:                 %DQS-l-ident,r  H               The messages in this appendix are listed alphabetically by6               their message ident (or identification).           FOR MORE INFORMATION?               Refer to the OpenVMS System Messages and Recovery C               Procedures Reference Manual for an explanation of the                following:  @               o  The format of OpenVMS system messages and their                   severity levels  A               o  Error messages beginning with %PCSI and possibleT,                  solutions to these problems  H                                            DQS Installation Messages G-1 n  C            B            For a description of any errors returned by the LicenseB            Management Facility (LMF), refer to the OpenVMS License%            Management Utility Manual.R                                                                                    "      G-2 DQS Installation Messages c  m          H         ________________________________________________________________  #         Installation Error MessagesO  B               This section describes error messages that you might>               encounter while you are installing DQS software.             MESSAGE SECTIONcF          NOSPACE, there is not enough free space on the system disk to             install DQS Vn.n  E             Explanation: There is not enough free space on the systemo&             disk for the installation.  9             User Action: Delete some files and try again.c  D          VERSION, DQS Vn.n requires OpenVMS Version Vn.n or later to             install   G             Explanation: The installed version of the OpenVMS operating_/             system is not the prerequisite one.I  F             User Action: Install or upgrade to the appropriate versionA             of the OpenVMS operating system and reinstall the DQS              software.                                         H                                            DQS Installation Messages G-3               E      ________________________________________________________________n        IVP Error Messages=  ?            This section describes error messages that you might C            encounter when you run the DQS Installation Verification             Procedure (IVP).:          IVP MESSAGES *        FILENOTFOUND file-name is not found  D          Explanation: The IVP could not find the file file-name. The/          file-name may be one of the following:-  &          o  SYS$MANAGER:DQS$CLIENT.EXE  #          o  SYS$MANAGER:DQS$SMB.EXE   &          o  SYS$MANAGER:DQS$SERVER.EXE  #          o  SYS$MANAGER:DQS$MSG.EXEe  ?          Refer to Appendix E for information about these files.N  B          User Action: Reinstall the DQS software. If you still get6          this message, report your problem to Digital.                                      "      G-4 DQS Installation Messages               H         ________________________________________________________________           Error Reporting*               REPORTING*E               If an error occurs while you are using the DQS softwareiG               and you have followed the suggestions in this section andaG               the troubleshooting section in the Part II and still haveeH               reason to believe that the error is a problem with the DQS5               sofware, report the problem to Digital.Y           ACTIONSUA               Depending on the nature of the problem and the typelD               of support you have, you can take one of the following               actions:  C               o  Call Digital if your software contract or warrantyt=                  agreement entitles you to telephone support.Y  ?               o  Determine whether the problem is a result of a(F                  defective media. If so, contact your Digital Services>                  representative for a replacement copy. If theG                  requirements for installing the DQS software have been D                  met, and the media is not defiective, then submit aG                  Software Performance Report (SPR). When you prepare to 8                  submit an SPR, please do the following:  D                  -  Provide as complete a description of the problemD                     as possible, trying not to overlook any details.E                     Include in the description the version numbers ofOF                     the DQS software and operating system (both server                      and client).  G                  -  Reduce the problem to as simple a case as possible, 3                     preferably to a single command.   ;                  -  Include listings of all output from theo:                     DQS software (if any) and any relevantF                     SYS$MANAGER:OPERATOR.LOG entries and NETSERVER.LOGE                     files. The DQS$NETSERVER.LOG files are located in,=                     the DQS server account default directory.r      H                                            DQS Installation Messages G-5 C  o            '               -  Provide the following:   A                  *  A SHOW LOGICAL listing of all the DQS logicaliC                     definitions on both the server and client nodes   A                  *  A SHOW QUEUE/FULL/ALL listing of the queue onf4                     both the server and client nodes  @                  *  A SHOW PROCESS/ALL listing of the server DQS                     processt  A            o  Fill out and submit a Reader's Comments form if theaE               problem has to do with the DQS documentation. There are E               Reader's Comments forms at the back of each manual. Use D               the form from the manual in which you found the error.2               Include the section and page number.  D            Review the current Software Product Description (SPD) andC            Warranty Addendum. If you encounter a problem during theeA            warranty period, report the problem as indicated abovenC            or follow alternate instructions provided by Digital forr1            reporting SPD nonconformance problems.V                                              "      G-6 DQS Installation Messages i  P                      H         ________________________________________________________________  H                                                                 Glossary                     burst page  B               A page printed between print jobs or copies of printC               files, if requested. Useful for separating print jobsa?               manually. The burst page contains client-specifico>               information if the remote queue on the server isG               controlled by the DQS software. Otherwise, the burst pages3               contains server-specific information.E                 client nodee  H               Nodes whose users can print files on printing devices that2               are attached to remote server nodes.                 client queue  E               DQS queue on the client node that directs print jobs toE?               the associated remote queue on the server system.t                 client software   F               DQS software that is installed on all nodes, and must be@               configured if the node is to act as a client node.                 DECnet  ,               Digital's networking protocol.                 DECnet long name  D               Long node names allowed by the DECnet/OSI for OpenVMS,-               Version 5.6 software (Phase V).     H                                                               Glossary-1 r               !            device control library   D            A library that contains a series of text modules that canC            be sent to the device associated with a queue, to affecteD            the behavior of that device. DQS printing uses the device0            control libraries of the server node.              DQS  3            Acronym for Distributed Queuing Service.               execution queue  >            The print queue associated with a specific physical"            printing output device.              flag page  B            An optional page that precedes each file or job that is@            printed. The flag page contains information about theB            printer and the print job. If DQS software controls theB            remote queue on the server, then the flag page contains@            client-specific information. Otherwise, the flag page0            contains server-specific information.              full name  C            For DQS purposes, the DECnet client's or server's remotelA            node name comprised of 1 to 150 characters. The DECnetd.            full name has the following format:  6            NamespaceNickname:.DirectoryPath.NodeObject  D            The node full name must begin with the namespace nicknameC            and a colon (:) and the directory path must begin with aoD            dot (.). The full name can be any combination of letters,B            digits, and certain punctuation characters from the OSIC            Latin-1 character set. Some other characters are alloweddA            as long as they are enclosed in quotation marks. For a0@            list of all allowable characters, refer to DECnet/OSI)            DECdns Management, Appendix A.               generic queue  ?            The logical printer queue that accepts the print job D            from the user and directs it to the appropriate execution            queue.m        Glossary-2r s  l                           logical queueS                  See generic queue.                 PCFi  5               Acronym for product configuration file.Y                 PCSI  C               Acronym for POLYCENTER Software Installation utility.                  print jobA  G               A print request of one or more files and associated printl               requirements.e                 print queueD  A               The queue in which a print job waits to be printed.t                 server nodey  G               Nodes in your network that have an attached output devicesE               (for examples, printers) that you can make available tof?               the users on remote client nodes in your network.                  server softwaree  E               DQS software that must be installed and configured on aK8               node for the node to act as a server node.                 remote queue  G               DQS queue on the server node that directs print jobs fromP8               the remote client to the attached printer.                 trailer page  D               An optional print page that follows each file printed.E               The trailer page is often printed even if the print jobrE               fails, and contains messages to the user explaining theAC               reason for the print error. The trailer page containsoF               client-specific information if the DQS software controlsD               the remote queue on the server. Otherwise, the trailer8               page contains server-specific information.  H                                                               Glossary-3                               E      ________________________________________________________________   E                                                                 Indexs    >      A                                    Client node (cont'd);      ___________________________           configuring in a E      Access rights,  7-28                     VMScluster environment, 2      Accounting,  8-17                        9-16A        for client access to                definition,  1-3, 2-2, 7          servers,  8-18                       7-3, 12-4 ;      ALLOW_NODE keyword,  8-14            Client queue, 1-3s>      ASSIGN/QUEUE command                  advanced methods of<        for defining logical                   creating,  9-6>          queues,  9-11                     changing definition@      AUTOGEN utility,  12-18                  temporarily,  9-13  8      B                                     creating withB      ___________________________              DQS$DEFINE.COM file,1      Banner page note,  8-23,                 9-6l8         9-22                               creating withB      Batch jobs                               DQS$IMPORT.COM file,1        and printing, 7-31                     9-4i  ;                                            definition,  7-3*:      C__________________________           deleting,  9-15  A      Client                                finding status,  10-11*A        as a VMScluster system,             setting up a LAT port, 2          7-3                                  9-19=        connectivity requirements           spooling to,  9-19t9          ,  7-4                           Client softwaree;      Client access                         definition,  7-3 <        checking, 8-17                      upgrading,  15-11=      Client logical names,  C-7           Command interpreterAA        defining, 9-11, 15-4                for DQS commands,  7-9i2      Client node                          Commands9        configuring, 7-3, 7-19              enabling after B                                               installation,  15-7,3                                               15-15   E                                                               Index-1                  ;      Commands (cont'd)                    DQS messages, A-1 B        PRINT, 2-2                         DQS$ACCOUNTING_BY_SYSTEME        QDELETE, 4-2                         logical name,  8-5, 8-17,E0        QSET, 5-2                            8-47:        QSHOW, 3-2                          function,  8-19?        summary, 7-6                       DQS$CLEANSRV.COM file D      Configuration                         function in DQS printing,1        for client nodes, 7-3,                 8-4e<          7-19                             DQS$CLIENT programC        for server nodes, 7-3,              for synchronizing forms, 2          7-19                                 9-179        restrictions, 7-19                  function,  7-9 D      Connectivity requirements            DQS$DEFINE.COM file, 8-44,/        for DQS, 7-4                         9-6v  A                                            creating client queuest8      D__________________________              with,  9-6C      Daisy-chained queues                  parameters for invoking, 1        benefits, 7-21                         9-7 C        creating loops, 7-23               DQS$FORM_OVERRIDE logicald0        defining, 8-44                       name:        definition, 7-21                    function in DQS@        function, 7-21                         environment,  9-18E        setting up, 8-48                   DQS$IDLE_TIME logical name, 5      DECnet Phase IV                        8-5, 8-48 :        installation requirements           defining,  8-35:          ,  11-4                           function,  8-35=        postinstallation steps,            DQS$IMPORT.COM file$D          15-5                              connectivity requirements4        use with the DQS software              ,  9-4>          ,  7-4                            for creating client:      DECnet/OSI Phase V                       queues,  9-46        installation requirements           using,  9-4@          ,  11-4                          DQS$LOG_ACCESS logicalB        postinstallation steps,              name,  8-5, 8-17, 8-47:          15-6                              function,  8-18D        use with the DQS software          DQS$LOG_AREA logical name,6          ,  7-4                             8-31, 8-48:      DENY_NODE keyword,  8-13              function,  8-31B      Disk space requirements,             DQS$MAX_PRIORITY logical<         12-11                               name,  8-5, 8-48:      Distribution kit                      function,  8-34B        OpenVMS AXP systems, 12-2          DQS$MOVE_DEFDIR.COM fileA        OpenVMS VAX systems, 12-3           moving server account, 2                                               8-37        Index-2    S            F         DQS$NOTIFIER program                DQS$SERVER_CONFIG.TXT file7          defining the scanning                 (cont'd)s:             interval,  8-29                   format,  8-8E          function,  7-12                      granting client access, 5         DQS$NOTIFY_CYCLE_TIME                    8-46vG           logical name,  8-5, 8-47            setting up remote queues, 5          defining,  8-29                         8-46aD          function,  8-29                    DQS$SERVER_UPDATE_QUEUE_D         DQS$NOTIFY_LOCK logical                DEFNS.COM file, 15-14<           name,  8-40, 8-48                 DQS$SMB symbiontB          defining,  8-40                      function,  7-9, 7-14G         DQS$PRIORITY logical name,          DQS$STARTUP.COM file,  11-8eD           8-5, 8-48                           editing to synchronize<          defining,  8-33                         forms, 9-18A          function,  8-33                      for defining client C         DQS$PRTSMB symbiont, 8-47                logical names, 9-2_A          enabling,  8-27                      for starting client <          function,  7-11, 7-14                   queues, 9-2D          function with other                  invoking,  15-6, 15-14E             symbionts,  D-2                   on a VMScluster system, 4          replacing PRTSMB,  7-14                 7-3E         DQS$REMOTE logical name             DQS$STARTUP.COM_OLD file,e3          changing definition,  9-13            11-8 D          function in generic                DQS$STATUS logical name,3             queues,  9-9                       8-47i=          function in logical                  function,  8-25 G             queues,  9-11                     in error reporting,  7-26 B         DQS$SERVER account                  DQS$SYSTARTUP.COM file;          setting up during                    editing,  8-2 A             installation,  14-12              for defining server D         DQS$SERVER program                       logical names, 8-3,5          function,  7-10, 7-11                   8-46G"          function on client,  7-17-          function on server,  7-17          E_G         [DQS$SERVER.NODES]                  ___________________________ C           subdirectory                      Error messages see also 7          for accounting,  8-18                 Messages)C          of server account,  8-18           Error conditions,  7-24dD         DQS$SERVER_CHANGE_DEFAULT_            function of DQS$STATUSC           DEVICE.COM file,  8-37                 logical name, 7-26YD         DQS$SERVER_CONFIG.TXT file,           in DQS printing,  7-24=           8-2                                 printing,  7-24:          denying client access,              8-47  H                                                                  Index-3 e  f            6      Error messages                       Global pagesB        see also Messages                   changing system values,3        during installation, G-3               12-19_B        during installation                 checking system values,3          verification,  G-4                   12-18 9        for daisy-chained queues,          Global sections B          7-23                              changing system values,3        for QDELETE command, 4-4               12-19IB        for QSET command, 5-6               checking system values,3        PRINT command, 2-11                    12-18          QSHOW command, 3-7, 10-15E        with parameter 8, 7-18             H__________________________e?      Error reporting                      Hardware requirementse;        procedures, G-5                    HELP command, 1-5i  +      F__________________________          I E      Files                                ___________________________ C        installed on DQS client            Installation Verification =          nodes,  E-6                        Procedure see IVP @        installed on DQS server            Installation procedureB          nodes,  E-2                       accounts added by,  E-9D        modified by the                     checking progress,  13-149          installation procedure,           errors,  13-22u@                                            files added on client9          E-8                                  nodes,  E-6o@        purging, 14-11                      files added on server9      Forms                                    nodes,  E-2s?        displaying, 3-5                     files modified,  E-8tD        function, 7-16                      first-time considerations5        requirements for printing              ,  11-7l@          with,  2-6                        following progress of?      Forms synchronization                    VMSINSTAL,  14-12fA        editing DQS$SYSTARTUP.COM           getting help from DCL,t2          file,  9-18                          13-7C        for DQS jobs, 7-16                  getting help from MOTIF,G3        in DQS environments, 9-17              13-18eC        performing, 9-17                    invoking from DCL,  13-3   D      G                                     invoking VMSINSTAL,  14-5B      ___________________________           on a VMScluster system,7      Generic queues                           7-3, 12-5eD        configuring, 9-10                   OpenVMS tailoring classes8        defining, 9-8                          for,  11-3:        definition, 9-8                     planning,  12-4  @                                            processes added,  E-9        Index-4                          Installation procedureG           (cont'd)                          L__________________________n  ;          purging files replaced             LAT port,  9-19 G             by,  14-11                      License Management Facility 5          sample dialogs,  F-1                 See LMF E          starting from MOTIF,               License PAK,  11-5, 12-16i;             13-15                           License Producta?          stopping from DCL,  13-11             Authorizatin Keyl=          stopping from MOTIF,                 See License PAKiC             13-21                           Licensing requirements, 3          stopping with VMSINSTAL,              11-5 =             14-7                            LMF,  11-5, 12-16 <          system management                  Log files,  8-31F             procedures,  12-18                specifying the location,5          upgrade considerations,                 8-31 @             11-8                            Logical device,  6-18          what you need to know,             Logical linkD             11-1                              specifying duration inC          with PCSI,  13-3                        DQS printing, 8-35 9          with VMSINSTAL,  14-1              Logical links,<         Installation requirements,            setting,  7-198           11-1                              Logical name5          accounts,  12-6                      summarytC          disk space,  12-11                      for servers,  8-46 :          hardware,  11-3                    Logical queues=          licensing,  11-5                     defining,  9-11 ?          operating system,  11-3              definition,  9-11           PCSI,  11-7-          prerequisite products,             MeG             11-4                            ___________________________ :          privileges,  12-6                  Messages,  B-4G          process account quotas,              format with DQS software,l9             12-9                                 A-1, B-2 G          software,  11-3                      from notification service ;          time,  11-10                            , A-2, B-4dH         IVP                                   severity levels,  A-1, B-2H          for troubleshooting,  10-2           showing print status,  2-5B          running separately,  15-6          Moving server account,3          troubleshooting,  15-6                8-37h          H                                                                  Index-5                 :                                           Operating system?      N__________________________            requirements,  11-3 ;      NETSERVER.LOG file,  7-24            OPERATOR.LOG filea?        checking client access,             for troubleshooting,s3          8-17                                 10-11i          for troubleshooting,sE          10-10                            P__________________________s  -      Network connections                  PAKs:        setting, 7-19                       See License PAK;      Network connectivity                 Parameter 8, 7-18,A        requirements for                    format of information,r7          DQS$IMPORT.COM file,                 7-18, D-3 :          9-4                               modifying,  D-34      Networking software                  Parameters=        installation requirements           for DQS$DEFINE.COMa>          ,  11-4                              invocation,  9-76      /NOTE                                PCSI utility:        DQS default note, 8-23,             DCL help,  13-7?          9-22                              DCL interface,  13-3r<      Notification service                  installing server=        connectivity requirements              software,  13-8r?          ,  7-4                            invoking from MOTIF, 3        DQS$SERVER program, 7-13,              13-15l=          7-17                              MOTIF help,  13-18 B        function, 7-12                      MOTIF interface,  13-15@        messages, 7-12, 7-13,               registering products,9          A-2, B-4                             11-7, 12-22CD        /NOTIFY qualifier, 7-12             stopping from DCL,  13-11?        troubleshooting, 10-6               stopping from MOTIF,t3      /NOTIFY qualifier,  7-12                 13-21   :                                           Postinstallation=      O__________________________           customizing clientu  D      Operator Communication                   software,  15-4, 15-11=         Process see OPCOM                  customizing servereD      OPCOM                                    software,  15-3, 15-10B        for troubleshooting,                defining server queues,2          10-11                                15-2A        function, 7-24                      editing system startup @      OpenVMS tailoring classes,               file,  15-5, 15-13?         11-3                               for OpenVMS clusters =                                               members,  15-16 @                                            moving server accountD                                               directory,  15-2, 15-8        Index-6 e               >         Postinstallation (cont'd)           Print job (cont'd)  F          running the IVP                      displaying entry number,4             separately,  15-6,                   5-3@             15-14                             entry number,  2-5A          starting DQS software,                  displaying,  4-3w=             15-6, 15-14                       modifying,  5-3n@          updating server queues,              specifying maximum?             15-14                                priority, 8-34_H          upgrading client software            status messages,  A-2, B-4D             ,  15-11, 15-13                   troubleshooting,  10-9:          upgrading DQS server,              Print Symbiont=             15-8                              function,  8-27 B          upgrading server software          Printing process,  7-76             ,  15-13                        Privileges@          verifying queue                      for installing DQS?             definitions,  15-8                   software, 12-6LD         PRINT command, 2-2, 7-5               for running DQS$CLIENT>          /AFTER qualifier,  2-7                  program, 9-17F          /DELETE qualifier,  2-7              for using DQS$IMPORT.COM:          error messages,  2-11                   file, 9-4>          /FORM qualifier,  2-8                modifying,  12-7B          function,  7-6, 7-7                Process account quotas?          /HEADER qualifier,  2-8              modifying,  12-10-G          /HOLD qualifier,  2-8                required for installationt7          network connectivity                    , 12-9Q5             requirements,  1-3              Processes B          /NOIDENTIFY qualifier,               client requirements,:             2-5                                  7-29, 9-3G          notification completion,             created in server account 7             1-3                                  , 7-17g:          notification of                      DQS$NOTIFIERC             completion,  7-12                    scanning interval,18          /NOTIFY qualifier,  1-3,                   8-29A             2-9, 2-10, 4-3, 7-12              priority for server >          /OPERATOR qualifier,  2-9               process, 8-33G          /PARAMETERS qualifier,               reducing amount on clientnE             2-9                                  node, 9-3, 9-8, 9-11eG          /PRIORITY qualifier,  2-9            required by DQS software, 5          qualifiers,  2-7, 7-6                   11-6 ?          /SETUP qualifier,  2-9               restarting server ?         Print job                                processes, 8-5 B          deleting from a queue,               server requirements,;             4-2                                  7-20, 7-29   H                                                                  Index-7                       Product Authorization KeyE        See License PAK                    R__________________________   7      PRODUCT INSTALL command,             Release notes >         13-3                               accessing with PCSI<        qualifiers, 13-5                       utility,  13-2D      PRTSMB print symbiont,                accessing with VMSINSTAL,2         7-11                                  14-2  ;                                           Remote queue, 1-3 ;      Q__________________________           definition,  7-3 6      QDELETE command,  4-2                 /RETAIN=ALLC        error messages, 4-4                    characteristic,  7-12 E      QDELETE/ENTRY command                /RETAIN=ALL characteristic,e0        function, 7-6, 7-8                   7-12          qualifiers, 7-6E      QSET command,  5-2                   S__________________________ >        /AFTER qualifier, 5-4              Software Performance:        error messages, 5-6                  Report>see SPR?        /FORM qualifier, 5-4               Software requirementso@        /HEADER qualifier, 5-4             Security requirements,0        /HOLD qualifier, 5-4                 7-280        /NODELETE qualifier, 5-5           ServerB        /PARAMETERS qualifier,              as a VMScluster system,1          5-5                                  7-3nD        /PRIORITY qualifier, 5-5            connectivity requirements        /REQUEUE qualifier, 5-54      QSET/ENTRY command                       ,  7-4D        function, 7-6, 7-8                  logical link requirements5        qualifiers, 7-6                        ,  7-19 8      QSHOW command,  3-2, 10-9            Server account<        enabling status messages,           definition,  7-17D          8-25                              directory function,  7-17=        error messages, 3-7,                [DQS$SERVER.NODES],A          10-15                                subdirectory,  8-18 ?        examining output, 10-9              file deletion,  7-17 <        finding status, 10-11,              stray files,  8-4B          10-12, 10-13                     Server account directoryB        for troubleshooting,                moving to a new device,2          10-10                                8-37@        function, 7-6, 7-8                  moving to new device,8        qualifiers, 7-6                        15-2, 15-8C        /QUEUE qualifier, 3-5              Server logical names, C-4 E                                            defining,  8-3, 8-46, 15-3         Index-8 I  x            E         Server node                         System generation utilityI@          allowing access to                   See SYSGEN utility=             specific clients,  8-14         System management >          configuring,  7-3, 7-19               procedures, forB          definition,  1-3, 2-2,                installation, 12-18=             7-2, 12-4                       System parametersu=          enabling,  13-8                      setting,  12-18 ?          installation requirements          System startup file_C             ,  11-8                           editing,  15-5, 15-134         Server process, 7-17G          error conditions,  7-24            T__________________________ D          setting priority,  8-33            Tailoring classes,  11-3;         Server processes                    Troubleshooting E          restarting,  8-5                     error messages in QSHOW ?         Server queues                            display, 10-15 ?          defining,  8-6, 11-8, 15-2           guidelines,  10-2 ;          updating,  15-14                     in VMScluster          Server softwaretC          customizing,  15-3, 15-10               environments, 10-8eB          definition,  7-3                     NETSERVER.LOG files,6          installing,  13-8                       10-10C          on a VMScluser node,  8-39           notification service, 5          on a VMScluster system,                 10-6QG             8-48                              OPERATOR.LOG file,  10-111?          upgrading,  15-8                     print jobs,  10-9c           SpoolingG          to a client queue,  6-1            V__________________________ =         SPR                                 VMScluster system C          instructions for                     as a DQS client,  7-3tC             submitting,  G-5                  as a DQS server,  7-3 @         Status messages                       configuring client?          for DQS queues,  8-25                   software, 9-16 @         Symbionts                             configuring serverE          DQS$PRTSMB,  7-11, 7-14,                software, 8-39, 8-48 F             8-47                              defining the DQS object,6          DQS$SMB,  7-9, 7-14                     15-16G          functions with DQS                   DQS$STARTUP.COM procedurec6             software,  D-2                       , 7-3F          OpenVMS PRTSMB,  7-11                installing DQS software,5         SYSGEN utility, 12-18                    12-5 F         SYSTARTUP_V5.COM file,                licensing of nodes,  7-3F           15-6                                nonhomogeneous clusters,  ;                                                  8-40, 8-48   H                                                                  Index-9                 B      VMScluster system (cont'd)            printing release notes,8        outgoing cluster alias                 14-2, 14-9C          for clients,  9-16                responding to questions,n2        postinstallation tasks,                14-8B          15-16                             running the IVP,  14-10@        troubleshooting, 10-8               setting up DQS clientE      VMSINSTAL command,  14-5                 /server account,  14-12gD      VMSINSTAL procedure                  VMSLICENSE.COM file, 12-16          aborting, 14-7nE        following progress, 14-12          W__________________________1;        help, 14-11                        Working directory ;        installing server                   creating,  12-13_D          software,  14-10                  using a DFS-mounted disk,3        invoking, 14-5                         12-15c        logging, 14-5                                                          
      Index-10 