                           C                      HP_DECprint_Supervisor_(DCPS)_for_OpenVMS_____ +                      System Manager's Guide   .                      Order Number: AA-PSVEL-TE    "                      November 2005  C                      This manual describes how to create DCPS print ?                      queues, customize the DCPS environment and ;                      troubleshoot common printing problems.           D                      Revision/Update Information: This manual super-G                                                   sedes the DCPS System G                                                   Manager's Guide V2.4.   H                      Software Version:            HP DECprint SupervisorE                                                   (DCPS) for OpenVMS, =                                                   Version 2.5   G                      Operating System:            OpenVMS Alpha Version D                                                   6.2, 7.3-2, or 8.2E                                                   OpenVMS I64 Version >                                                   8.2 or 8.2-1E                                                   OpenVMS VAX Version D                                                   5.5-2, 6.2, or 7.3        ,                      Hewlett-Packard Company*                      Palo Alto, California                 E            __________________________________________________________   E             Copyright 2005 Hewlett-Packard Development Company, L.P.   @            Confidential computer software. Valid license from HPC            required for possession, use or copying. Consistent with ?            FAR 12.211 and 12.212, Commercial Computer Software, B            Computer Software Documentation, and Technical Data forE            Commercial Items are licensed to the U.S. Government under 0            vendor's standard commercial license.  @            The information contained herein is subject to change>            without notice. The only warranties for HP products=            and services are set forth in the express warranty >            statements accompanying such products and services.@            Nothing herein should be construed as constituting anD            additional warranty. HP shall not be liable for technical=            or editorial errors or omissions contained herein.   E            Adobe, Adobe PostScript 3 and PostScript are trademarks of &            Adobe Systems Incorporated.  D            Intel and Itanium are trademarks or registered trademarksA            of Intel Corporation or its subsidiaries in the United &            States and other countries.  B            Microsoft and Windows are U.S. registered trademarks of!            Microsoft Corporation.   <            UNIX is a registered trademark of The Open Group.              Printed in the U.S.  D            The DECprint Supervisor documentation set is available on            CD-ROM.                               C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................   xiii         1  DCPS Overview   C          1.1   Purpose of the DCPS Software.................    1-1 C          1.2   DCPS Software Components.....................    1-3 C          1.2.1     The Print Symbiont.......................    1-4 C          1.2.2     Device Control Libraries.................    1-5 C          1.2.3     Translators..............................    1-5       2  Setting Up Printers   C          2.1   Networked Printers...........................    2-1 C          2.1.1     TCP/IP Printers..........................    2-2 C          2.1.1.1     Raw TCP/IP Printers....................    2-3 C          2.1.1.2     LPD Printers...........................    2-3 C          2.1.1.3     CPAP Printers..........................    2-4 C          2.1.2     LAT Printers.............................    2-4 4          2.1.2.1     Configuring the Printer for LATC                      Access.................................    2-4 /          2.1.2.2     Setting DECserver LAT Port C                      Characteristics........................    2-4 C          2.1.2.3     Editing the LAT Configuration File.....    2-7 C          2.1.2.4     Setting the Communications Speed.......    2-9 C          2.1.3     DECnet Printers..........................    2-9 C          2.1.4     AppleTalk Printers.......................   2-10 C          2.2   Directly-Connected Serial Printers...........   2-10 C          2.3   General Information..........................   2-11 C          2.3.1     Supported Printers.......................   2-11 C          2.3.2     Setting the printer timeout..............   2-11 C          2.3.3     Changing the Printer Password............   2-12 C          2.3.4     Setting the Printer Name.................   2-12   C                                                                 iii                  +      3  Creating and Modifying Print Queues   ;            3.1   If You Are Installing the Software for the E                  First Time...................................    3-1 <            3.2   If You Are Upgrading From DECprint PrintingE                  Services Software (CPS)......................    3-1 E            3.3   Setting Up Execution Queues..................    3-1 >            3.3.1     Supplying the Name of the Execution QueueE                      (P1).....................................    3-4 E            3.3.2     Supplying the Printer Device Name (P2)...    3-5 =            3.3.2.1     If Your Printer Is On a TCP/IP Network E                        and Uses Raw TCP/IP Sockets ...........    3-7 =            3.3.2.2     If Your Printer Is On a TCP/IP Network E                        and Uses LPD...........................    3-9 =            3.3.2.3     If Your Printer Is On a LAT Network or E                        Directly Connected.....................   3-10 =            3.3.2.4     If Your PrintServer Printer Is Part of E                        a TCP/IP Network ......................   3-10 =            3.3.2.5     If Your PrintServer Printer Is Part of E                        a DECnet Network ......................   3-11 >            3.3.2.6     If Your Printer Is Part of an AppleTalkE                        Network................................   3-11 7            3.3.3     Supplying the Library Logical Name E                      (P3).....................................   3-12 4            3.3.4     Assigning Default PRINT CommandE                      Parameters to the Queue (P4).............   3-12 7            3.3.5     Supplying Default Queue Attributes E                      (P5).....................................   3-14 :            3.3.6     Setting the Speed for Serial PrintersE                      (P6).....................................   3-15 ;            3.3.7     Supplying SET DEVICE Qualifiers to the E                      Queue (P7)...............................   3-15 >            3.3.8     Enabling SET VERIFY When Initializing theE                      Queue (P8)...............................   3-15 7            3.4   Running the Startup Procedure in Setup E                  Mode.........................................   3-16 E            3.5   Customizing Execution Queue Behavior.........   3-17 4            3.5.1     Running DCPS as a MultistreamedE                      Process..................................   3-17 9            3.5.1.1     Managing Print Queues When Running E                        Multistreamed..........................   3-18 9            3.5.1.2     Changing the DCPS Environment When E                        Running Multistreamed..................   3-19           iv                  8               3.5.1.3     Determing the Proper Value forH                           DCPS$MAX_STREAMS.......................   3-19=               3.5.2     Interrupting Busy Printers When a Job H                         Starts...................................   3-20>               3.5.3     Suppressing PostScript SynchronizationH                         When a Job Starts........................   3-20>               3.5.4     Purging the Symbiont Process's WorkingH                         Set......................................   3-21H               3.5.5     Enabling Spooling for LPD Queues.........   3-22H               3.5.6     Specifying Sheet Size for LPD Queues.....   3-23H               3.5.7     Specifying Product Name for LPD Queues...   3-24H               3.5.8     Suppressing Unsolicited PJL Messages.....   3-325               3.5.9     Suppressing the OPCOM Message H                         USERNOTFOUND.............................   3-33?               3.5.10    Using Old ANSI Translator Page Size for H                         A4 Landscape ............................   3-33H               3.6   Setting Up Generic Queues....................   3-343               3.7   Activating Changes to the Queue H                     Definitions..................................   3-35H               3.8   Testing the Printing System..................   3-36    2         4  Providing Automatic Data Type Detection  H               4.1   How DCPS Automatically Detects Data Type.....    4-1H               4.2   Specifying Automatic Data Type Detection.....    4-29               4.2.1     Linking File Extensions with Data H                         Types....................................    4-2=               4.2.2     Specifying Default Data Types for the H                         System and Queues........................    4-3H               4.2.3     How Users Control Data Type Detection....    4-4  3         5  Manipulating Print Jobs and Print Queues   H               5.1   Displaying Print Job Status..................    5-1H               5.2   Deleting a Print Job.........................    5-2H               5.3   Releasing a Print Job in the Holding State...    5-3H               5.4   Requeuing Print Jobs.........................    5-4H               5.4.1     Requeuing Pending Print Jobs.............    5-4?               5.4.2     Requeuing the Currently Printing Job to H                         Another Queue............................    5-4?               5.4.3     Requeuing Current and Future Print Jobs H                         in a Queue...............................    5-4H               5.5   Modifying the Attributes of a Print Job......    5-5  H                                                                        v                 E            5.6   Displaying a Queue...........................    5-5 E            5.7   Pausing a Queue..............................    5-6 E            5.8   Starting a Queue.............................    5-7 E            5.9   Modifying the Attributes of a Queue..........    5-8 E            5.10  Preventing Users from Printing to a Queue....    5-8 E            5.11  Deleting a Queue.............................    5-9 E            5.12  Responding to a Stalled Queue................    5-9 E            5.13  Stopping and Starting the Queue Manager......   5-10     3      6  Specifying Separation, Log, and Error Pages   E            6.1   What Are Separation Pages?...................    6-1 E            6.2   Enabling Job Separation Pages................    6-2 E            6.2.1     Error Messages on the Trailer Page.......    6-3 E            6.2.2     Suppressing Job Trailer Pages............    6-3 <            6.2.3     Specifying a Special Input Tray for JobE                      Burst and Flag Pages ....................    6-4 E            6.3   Enabling File Separation Pages...............    6-7 E            6.4   Adding a System Message to Separator Pages...    6-8 E            6.5   Extended File Specifications.................    6-8 E            6.6   Requesting Job Log Pages.....................    6-9 E            6.7   The File Error Page..........................    6-9   ;      7  Creating Setup Modules and Device Control Libraries   E            7.1   What Is a Setup Module?......................    7-1 E            7.2   Locating Setup Modules.......................    7-1 E            7.2.1     Locating Custom Setup Modules............    7-2 7            7.2.2     Displaying the Contents of a Setup E                      Module...................................    7-3 E            7.3   Creating Custom Setup Modules................    7-3 E            7.4   Creating Device Control Libraries............    7-4 E            7.4.1     Putting Setup Modules in Libraries.......    7-5 E            7.4.2     Specifying a Library Search List ........    7-5 <            7.4.3     Device Control Libraries Must Exist forE                      Queue to Start ..........................    7-7 ;            7.4.4     Preserving Custom Setup Modules During E                      Upgrades.................................    7-8 E            7.5   Including Setup Modules in Print Job.........    7-8 E            7.6   Persistently Loading PostScript Resources ...    7-9 ;            7.7   Changing the Default Character Set for PCL E                  and Proprinter Print Jobs....................   7-11           vi                  <               7.8   Specifying Printer Resolution with SetupH                     Module.......................................   7-12<               7.9   Modifying DECimage Parameters with SetupH                     Modules......................................   7-136               7.10  Providing Access to Font CartridgeH                     Emulation....................................   7-15H               7.11  Device Control Library Cache Feature.........   7-16H               7.12  Printing on Unrecognized Printers............   7-17    4         8  Creating and Maintaining Form Definitions  H               8.1   Associating Setup Modules with Forms.........    8-1H               8.2   Associating a Form with a Print Queue........    8-2H               8.3   Creating Form Definitions for ANSI Files.....    8-3H               8.4   Displaying Forms and Their Attributes........    8-5H               8.5   Deleting a Form..............................    8-5H               8.6   Using the Default ANSI Form Definition.......    8-6  /         9  Charging Users for Printer Resources   ?               9.1   Accounting Information Supplied by the DCPS H                     Software.....................................    9-1>               9.2   Accounting Information Supplied by the JobH                     Controller...................................    9-2?               9.2.1     Accounting Fields Left Blank by the Job H                         Controller...............................    9-3>               9.2.2     Accounting Fields Filled with Zeros byH                         the Job Controller.......................    9-4H               9.3   Accuracy of DCPS Page Counts.................    9-46               9.4   Compatibility with Mechanical PageH                     Counters.....................................    9-5  (         10  Printer-Specific Information  H               10.1  Apple LaserWriter Plus Printer...............   10-1H               10.1.1    LPS$PERSISTENT_RESOURCES Not Supported...   10-19               10.2  Compaq Laser Printer LN16 and GENICOM H                     microLaser 170...............................   10-1H               10.2.1    Printer Configuration Setting............   10-1H               10.2.2    LAT and AppleTalk Configuration..........   10-2@               10.3  Compaq Laser Printer LN32 and LNM40; GENICOMH                     Intelliprint mL, LN and microLaser Series....   10-3    H                                                                      vii                 E            10.3.1    Printer Configuration Settings...........   10-3 E            10.3.1.1    Language-Sensing Mode..................   10-3 8            10.3.1.2    Printer Setting May Cause StalledE                        Queues.................................   10-3 E            10.3.2    LAT and AppleTalk Configuration..........   10-4 E            10.3.3    Queue Aborts When Using TCPware..........   10-4 E            10.4  DIGITAL Colorwriter LSR 2000 Printer.........   10-4 E            10.4.1    NIC Does Not Work with Raw TCP/IP........   10-4 E            10.5  DIGITAL DECcolorwriter 1000 Printer..........   10-5 E            10.5.1    Printer-Specific Setup Files.............   10-5 E            10.6  DIGITAL DEClaser 3500 Printer................   10-6 E            10.6.1    Job Remains in Starting State............   10-6 6            10.6.2    Interaction Between CommunicationE                      Protocol and Native PCL Support..........   10-6 E            10.6.3    NIC Does Not Work with Raw TCP/IP........   10-6 E            10.7  DIGITAL DEClaser 5100 Printer................   10-7 =            10.7.1    Native PCL Is Unavailable with EtherTalk E                      Protocol on NIC .........................   10-7 E            10.7.2    NIC Does Not Work with Raw TCP/IP........   10-7 E            10.7.3    Downloading and Deleting Fonts...........   10-7 E            10.7.4    Error Page Feature.......................   10-7 E            10.8  DIGITAL Laser Printer LN15+..................   10-8 E            10.8.1    Printer Configuration Settings...........   10-8 E            10.9  DIGITAL Laser Printer LN17+ps................   10-9 E            10.9.1    Job Remains in Starting State............   10-9 E            10.9.2    LPD Printing.............................   10-9 E            10.9.3    Incorrect Sheet Count....................   10-9 E            10.9.4    Downloading and Deleting Fonts...........  10-10 5            10.9.5    Colored Separator Pages and Tray E                      Switching................................  10-10 E            10.10 DIGITAL Laser Printer LN20...................  10-10 E            10.10.1   Incorrect Sheet Count....................  10-10 E            10.11 DIGITAL Laser Printer LN40...................  10-10 E            10.11.1   Incorrect Sheet Count....................  10-10 E            10.12 Compaq and DIGITAL Laser Printer LNC02.......  10-11 E            10.12.1   Minimum Firmware Version.................  10-11 E            10.12.2   Incorrect Sheet Count....................  10-11 E            10.13 DIGITAL PrintServer 17 Printer...............  10-11 5            10.13.1   Colored Separator Pages and Tray E                      Switching................................  10-11 E            10.14 HP 9085 MFP..................................  10-12 E            10.14.1   IP Requirements..........................  10-12 E            10.15 HP Color LaserJet 4650 ......................  10-12     	      viii                  H               10.15.1   Printer Fails with Service Error.........  10-12H               10.16 HP Color LaserJet 5500.......................  10-12H               10.16.1   Problems Starting Queues.................  10-12H               10.17 HP Color LaserJet 5550 ......................  10-13H               10.17.1   Printer Fails with Service Error.........  10-13H               10.18 HP LaserJet IIID Printer.....................  10-13H               10.18.1   Job Remains in Starting State............  10-13H               10.18.2   Incorrect Sheet Count on Duplex Jobs.....  10-13H               10.19 HP LaserJet IIISi Printer....................  10-13;               10.19.1   Incorrect Sheet Count on Native PCL H                         Jobs.....................................  10-14H               10.19.2   Incorrect Sheet Count on Duplex Jobs.....  10-14H               10.20 HP LaserJet 4SiMX Printer....................  10-14H               10.20.1   Incorrect Sheet Count on Duplex Jobs.....  10-14H               10.21 HP LaserJet 5M Printer.......................  10-14H               10.21.1   Problems Selecting an Input Tray.........  10-14H               10.21.2   Incorrect Sheet Count on Duplex Jobs.....  10-14H               10.22 HP LaserJet 5SiMX Printer....................  10-15H               10.22.1   Job Trailer Pages Print in Next Bin......  10-15<               10.22.2   Tray Is Not Available Due to Lack ofH                         Memory for Loaded Paper .................  10-15;               10.22.3   Duplex Not Supported Due to Lack of H                         Memory for Loaded Paper .................  10-15H               10.22.4   Incorrect Sheet Count on Duplex Jobs.....  10-15H               10.23 HP LaserJet 2100 and 2200....................  10-15H               10.23.1   Problems Starting Queues.................  10-15H               10.24 HP LaserJet 4000, 4050 and 5000..............  10-15H               10.24.1   Minimum Firmware Version.................  10-16H               10.25 HP LaserJet 4200 and 4300....................  10-16H               10.25.1   Problems Starting Queues.................  10-16H               10.26 HP LaserJet 4250 and 4350....................  10-16H               10.26.1   Printers Fail with Service Error.........  10-16H               10.27 HP LaserJet 8000, 8100 and 8150..............  10-17H               10.27.1   Optional Mailbox.........................  10-17H               10.27.2   Problems Starting Queues.................  10-17H               10.27.3   Minimum Firmware Version.................  10-17H               10.28 HP LaserJet 9050.............................  10-17H               10.28.1   Printer Fails with Service Error.........  10-17H               10.29 HP LaserJet 9055 MFP and 9065 MFP............  10-17H               10.29.1   Printers Fail with Service Error.........  10-18H               10.30 HP XL300 Printer.............................  10-18H               10.30.1   Communication Problem....................  10-18H               10.31 Lexmark Optra Rt+ Printer....................  10-18    H                                                                       ix                 E            10.31.1   Tray Linking and INPUT_TRAY..............  10-18 E            10.32 Lexmark Optra S, Optra T and T Series........  10-18 E            10.32.1   Problems Starting Queues.................  10-18 E            10.33 Tektronix Phaser.............................  10-18 E            10.33.1   Printer Configuration Settings...........  10-18 8            10.34 Xerox Phaser 4500, 6250, 7300, 7750 andE                  8400.........................................  10-19 E            10.34.1   Protocols Supported......................  10-19     #      11  Troubleshooting Procedures   :            11.1  What to Do if a Raw TCP/IP Printer is NotE                  Printing.....................................   11-1 :            11.1.1    Job Remains in Starting State for RawE                      TCP/IP or LAT Queue .....................   11-1 :            11.1.2    Job Remains in Starting State for RawE                      TCP/IP Queue.............................   11-2 ;            11.1.3    Connection Terminations for Raw TCP/IP E                      Queue....................................   11-2 ;            11.1.4    NOT_READY Warnings for Unavailable Raw E                      TCP/IP Printer...........................   11-3 4            11.2  What to Do if an LPD Printer is NotE                  Printing.....................................   11-4 E            11.2.1    No Output Printed from LPD Job...........   11-4 E            11.2.2    LPD Queue Stops and Job Put on Hold......   11-4 ;            11.3  What to Do if a PrintServer Printer Is Not E                  Printing.....................................   11-5 6            11.4  What to Do if a Serial Printer Is NotE                  Printing.....................................   11-6 =            11.4.1    What to Do if a Locally-Connected Serial E                      Printer Will Not Start Printing..........   11-6 =            11.4.2    What to Do if a Locally-Connected Serial E                      Printer Has Stopped Printing.............  11-11 7            11.4.3    What to Do if a LAT Printer Is Not E                      Printing.................................  11-13 ;            11.4.3.1    How to Determine Which Host Controls E                        the Printer............................  11-13 2            11.4.3.2    How to Troubleshoot PrinterE                        Communications Problems................  11-17 E            11.4.3.3    Common LAT Error Messages..............  11-17 <            11.4.4    How to Eliminate Excess Login Dialog onE                      Serial Printers..........................  11-20           x                 9               11.5  What to Do if Printing Is Slower than H                     Expected.....................................  11-21@               11.6  What to Do if Layup Definition Files Are NotH                     Found........................................  11-228               11.7  What to Do if Files Are Printed withH                     Unexpected Results...........................  11-22>               11.7.1    What to Do if Default Queue ParametersH                         Are Not Effective........................  11-22=               11.7.2    What to Do if a File Data Type Is Not H                         Recognized...............................  11-23    .         A  Printing System Management Commands  H               A.1   Overview of Management Commands .............    A-1H               A.2   Use of SET PRINTER with DCPS ................    A-3  %         B  Logical Names Used by DCPS   )         C  Downloading and Deleting Fonts     ;         D  DECprint Supervisor (DCPS) and DECprint Printing "            Services Software (CPS)  H               D.1   DCPS/CPS Coexistence.........................    D-1H               D.2   Upgrading from CPS to DCPS...................    D-1H               D.3   DCPS$ Prefix.................................    D-2H               D.4   Startup File Converter.......................    D-3H               D.5   Eliminating Generic Queues...................    D-3H               D.6   Page Scaling.................................    D-39               D.7   Layup for PS Level 2 Printers & Layup H                     Fixes........................................    D-4H               D.8   Layup Options on PRINT Command Line..........    D-4H               D.9   Page Sizes...................................    D-4<               D.10  Selecting Separator Pages from AlternateH                     Tray.........................................    D-5H               D.11  Stopping Unreachable PrintServer.............    D-5H               D.12  Overwriting First Line.......................    D-5H               D.13  Stall Timeouts...............................    D-5H               D.14  Requeuing a Job..............................    D-5H               D.15  Reading Stream Files.........................    D-6H               D.16  Copies Start on New Sheets...................    D-6H               D.17  Generic Queues Restarted.....................    D-6  H                                                                       xi                 E            D.18  Proprinter Translator........................    D-6 E            D.19  DCPS and PATHWORKS Libraries.................    D-6 E            D.20  Printing with Macintosh and PC Files.........    D-7 E            D.21  Improved Color Function for Colormate PS.....    D-7 E            D.22  Printing Security Messages...................    D-7     
      Index    
      Examples   =            3-1       Creation of an Execution Queue Entry for E                      a Raw TCP/IP Printer ....................    3-2   =            3-2       Creation of an Execution Queue Entry for E                      a PrintServer Printer ...................    3-2   =            3-3       Creation of an Autostart Queue Entry for E                      a Raw TCP/IP Printer ....................    3-3   E            3-4       Setting Up a Generic Queue...............   3-35   3            7-1       Search List for Device Control E                      Libraries................................    7-5   E            8-1       Sample Form Definition, CONFIDENTIAL.....    8-1         Tables   E            1         DECprint Supervisor Documentation........     xv   E            2-1       DECserver Port Characteristics...........    2-6   4            2-2       Printer-Required DECserver PortE                      Characteristics..........................    2-6   E            3-1       Parameter Values for Execution Queues....    3-4   E            3-2       Raw TCP/IP Port Numbers..................    3-8   E            3-3       Internal LPD Queue Names.................    3-9   E            3-4       Recognized Product Names.................   3-25   E            3-5       Parameter Values for Generic Queues......   3-34   E            3-6       IVP Files with Different Data Types......   3-36   E            5-1       Commands to Display Queues...............    5-6   E            6-1       Tray Number Values.......................    6-5   E            7-1       Printer Resolution Setup Modules.........   7-12   E            7-2       Enabling and Disabling DECimage .........   7-13         xii                 7               7-3       DECimage Setup Modules-Combined H                         Parameters...............................   7-14  9               7-4       DECimage Setup Modules-Individual H                         Parameters...............................   7-14  H               8-1       DEFINE /FORM Qualifiers for ANSI Files...    8-4  H               10-1      Valid Language Sensing Configurations....   10-3  H               10-2      LN15 Configuration Settings..............   10-8  6               10-3      Tektronix Phaser ConfigurationH                         Settings.................................  10-19  H               A-1       Printing System Management Commands......    A-1  =               A-2       SET PRINTER Qualifier Equivalents for H                         DECprint Supervisor Queues...............    A-5  H               B-1       DCPS Logical Names.......................    B-2                                                H                                                                     xiii                           H         ________________________________________________________________  H                                                                  Preface               Intended Audience   H               This manual is for OpenVMS system managers and data centerD               operators. Using this guide, you can create and modifyE               print queues, maintain the print jobs and print queues, G               and set up printing environments to meet the needs of the $               printing system users.  @               This guide is also intended for advanced users andH               applications programmers who customize the printing systemH               using form definitions, setup modules and layup definitionE               files. The DCPS User's Guide describes how users access 2               the features of the printing system.  E               Be sure to read the DCPS Software Installation Guide if F               you have not installed the DECprint Supervisor software.           Document Structure  D               This manual contains the following chapters and appen-               dices:  A               o  Chapter 1 provides an overview of DCPS features.   F               o  Chapter 2 provides information about setting up a newF                  printer or changing the setup of an existing printer.  E               o  Chapter 3 explains how to start up the DCPS printing @                  environment and test a printer and print queue.  H               o  Chapter 4 explains data types and how to customize yourF                  DCPS printing environment to handle the types of jobs"                  your users print.  B               o  Chapter 5 describes commands used to maintain andB                  control print jobs, queues and the queue manager.  H                                                                     xiii                 D            o  Chapter 6 explains job separator, log and error pages.  A            o  Chapter 7 explains setup modules and device control_               libraries.  A            o  Chapter 8 describes how to create and maintain form-               definitions.  =            o  Chapter 9 describes page accounting informationt               reported by DCPS.   C            o  Chapter 10 contains information about using DCPS with                 specific printers.  C            o  Chapter 11 contains information about troubleshootingh                printing problems.  D            o  Appendix A reviews OpenVMS DCL commands used to manage8               queues, jobs and related system resources.  A            o  Appendix B provides information about logical namese               used by DCPS.   C            o  Appendix C explains the use of the DCPS font download                utility.  A            o  Appendix D explains the difference between DECprint D               Supervisor (DCPS) and DECprint Printing Services (CPS)5               software, and their ability to coexist.         Related Documents  >            The primary source of information about DCPS is the-            following set of software manuals:                             xiv                 H               Table_1_DECprint_Supervisor_Documentation_________________  B               Software Installation Describes how to install DCPS.               Guide   G               System Manager's      Describes how system managers, data D               Guide                 center operators and applicationE                                     programmers can create and managePH                                     DCPS print queues and solve printing-                                     problems.u  F               User's Guide          Describes how to use DCPS to print>                                     to PostScript[R] printers.  F               Software Product      Contains the full list of printersD               Description (SPD      supported by DCPS and additionalF               44.15.xx)             information about the features andH               ______________________requirements_of_DCPS_V2.5.__________  F               For additional information about HP OpenVMS products andC               services, visit the following World Wide Web address:l  /                   http://www.hp.com/go/openvms/a           Reader's Commentse  C               HP welcomes your comments on this manual. Please sendr<               comments to either of the following addresses:  +               Internet    openvmsdoc@hp.come  1               Mail        Hewlett-Packard Companys>                           OSSG Documentation Group, ZKO3-4/U08-                           110 Spit Brook RoadS.                           Nashua NH 03062-2698  -         How to Order Additional Documentation   F               For information about how to order additional documenta-?               tion, visit the following World Wide Web address:   9                   http://www.hp.com/go/openvms/doc/order/_  D               Part numbers for DCPS-related documentation are listedF               in the Ordering Additional Documentation appendix of theE               Software Installation Guide, System Manager's Guide andC               User's Guide.   H                                                                       xv t  e                  Conventions  =            The following conventions are used in this manual:.  D            Ctrl/x           A sequence such as Ctrl/x indicates thatC                             you must hold down the key labeled Ctrl.E                             while you press another key or a pointingP*                             device button.  A            <Return>         In examples, a key name enclosed in a A                             box indicates that you press a key on E                             the keyboard. (In text, a key name is not /                             enclosed in a box.).  A                             In the HTML version of this document,.@                             this convention appears as brackets,.                             rather than a box.  C             . . .           A horizontal ellipsis in examples indi-TE                             cates one of the following possibilities:   A                             o  Additional optional arguments in a ;                                statement have been omitted..  A                             o  The preceding item or items can be.:                                repeated one or more times.  @                             o  Additional parameters, values, or@                                other information can be entered.  ;            ( )              In command format descriptions,t>                             parentheses indicate that you mustA                             enclose choices in parentheses if youn2                             specify more than one.  D            [ ]              In command format descriptions, bracketsE                             indicate optional choices. You can choose A                             one or more items or no items. Do not B                             type the brackets on the command line.B                             However, you must include the brackets?                             in the syntax for OpenVMS directory >                             specifications and for a substringE                             specification in an assignment statement.           xvi l  g              G               |                In command format descriptions, vertical.D                                bars separate choices within bracketsF                                or braces. Within brackets, the choicesD                                are optional; within braces, at leastF                                one choice is required. Do not type theA                                vertical bars on the command line..  E               { }              In command format descriptions, braces B                                indicate required choices; you mustG                                choose at least one of the items listed. D                                Do not type the braces on the command$                                line.  H               bold text        This typeface represents the introductionD                                of a new term. It also represents theE                                name of an argument, an attribute or a.&                                reason.  >               italic text      Italic text indicates important>                                information, complete titles ofF                                manuals or variables. Variables includeG                                information that varies in system outputtB                                (Internal error number), in commandD                                lines (/PRODUCER=name) and in commandF                                parameters in text (where dd representsH                                the predefined code for the device type).  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.i  E               Monospace text   Monospace type indicates code examples.?                                and interactive screen displays.e  F               -                A hyphen at the end of a command formatE                                description, command line or code line.F                                indicates that the command or statement?                                continues on the following line..  A               numbers          All numbers in text are assumed toeA                                be decimal unless otherwise noted. B                                Nondecimal radixes-binary, octal orD                                hexadecimal-are explicitly indicated.  H                                                                     xvii r  e                  H                                                                        1H         ________________________________________________________________  H                                                            DCPS Overview      (         1.1 Purpose of the DCPS Software  C               The DECprint Supervisor software allows people to use-G               and manage networked PostScript printers. For example, it-               allows users to:  G               o  Print customized documents, print two-sided and selectf                  input trays.s  D               o  Modify printed documents without changing the filesC                  that are printed, which saves paper and allows the 8                  production of custom printed documents.  A               o  Print different types of files on the PostScripte                  printers.  F               o  Access printers from the OpenVMS operating system andE                  from personal computers (PCs) and Macintosh systems.   H               The system manager makes the printing system easier to use               by providing:   B               o  Default queue attributes, so users do not have toD                  specify certain parameters, such as duplex printing  B               o  Setup modules, which are stored in device control>                  libraries and are used to modify the printing+                  environment for print jobs   F               o  Form definitions, specifying sets of print attributesH                  and including setup modules to make them all easier for                   users to access  @               o  Layup definition files, which you can create toF                  customize the way print jobs are printed on the media  8               DCPS also provides the following features:  $               o  Document Formatting  H                                                        DCPS Overview 1-1 .  .            #               DCPS allows users to:n  @               -  Change the size of pages as they are printed toD                  fit the physical size of media, using the following                  command:.  M                      $ PRINT /PARAMETERS=(PAGE_SIZE=n,SHEET_SIZE=m) file-spect  D               -  Specify page layup handling as the file is printed,-                  using the following command:   =                      $ PRINT /PARAMETERS=(LAYUP=option=value).  A               -  Save paper, using one of the following commands:r  ;                      $ PRINT /PARAMETERS=(PAGE_LIMIT="n,m") 6                      $ PRINT /PARAMETERS=(NUMBER_UP=n)  C               -  Print multiple uncollated copies of each sheet via.+                  the SHEET_COUNT parameter..  B               -  Use device control modules for all data types via?                  the /SETUP qualifier. ANSI modules may includegB                  control sequences. PCL modules may include binary                  font data.a  #            o  Data Type Translationl  ?               DCPS lets users print additional file data types,                including:  E               -  PCL 4 (Printer Control Language) files generated forQA                  printing on Hewlett-Packard LaserJet IID devices   ?               -  Proprinter files generated for printing on IBM.(                  Proprinter XL24 devices  >               -  ReGIS graphics files (monochrome output only)  E               -  TEKTRONIX files, generated for printing on TEKTRONIX2"                  4010/4014 devices  C               -  ASCII text files, to be printed with line numbers,rA                  page headers, and alternating groups of gray and.                  white bars3  C               -  DIGITAL Document Interchange Format (DDIF) bitonal4                  image files  +            o  Automatic Data Type Detectiont        1-2 DCPS Overview .  .            B                  Users do not need to specify the data type of theD                  print file, in most cases. DCPS recognizes files ofF                  the supported data types and automatically translates4                  them to PostScript before printing.  C                  DCPS can print files that contain both text (ANSI,.B                  PCL, or Proprinter data) and PostScript data. ForG                  example, users can print electronic mail messages thatoE                  contain PostScript files. The user submits the print.H                  job without specifying any data type. The DCPS softwareC                  begins printing the file as text and automatically.G                  recognizes the change to PostScript, printing the file.                  properly.  D                  See Chapter 4 for information about customizing theA                  printing system to recognize and print the filese1                  generated by users at your site.                  DCPS Version  D               The version of DCPS software currently running on yourH               system is printed on job and file separator pages, as wellE               as in the logical name DCPS$VERSION. If DCPS$VERSION isiA               undefined, DCPS has not been started on the system.r  $         1.2 DCPS Software Components  E               The DECprint Supervisor software includes the following                components:.  F               o  A print symbiont, which processes print requests from=                  OpenVMS print queues assigned to the printer   E               o  Queue management services, as described in Chapter 5.  H               o  Data type translators to translate non-PostScript files3                  for printing on PostScript devices.  G               o  A device control library for setup modules that affectrA                  the printing of files, as described in Chapter 7i  B               The DECprint Supervisor symbiont is used in place ofA               the OpenVMS print symbiont, PRTSMB. The software isnC               distributed as executable image files, text, and helpi               files.  H                                                        DCPS Overview 1-3 I  l            A            Figure 1-1 illustrates the process by which print jobs.A            are produced on an OpenVMS system and delivered to the.            printer.   D            The software components of a DECprint Supervisor printing:            system are described in the following sections.        1.2.1 The Print SymbiontS  E            Users send jobs to the printer using the DCL PRINT command.E            or using an application program that generates the OpenVMSeE            system service call SYS$SNDJBC. The print symbiont manages.D            the print jobs. The DECprint Supervisor software performs$            the following operations:  !            o  Maintains resources.  /            o  Sends control data to the printer   0            o  Sends the data file to the printer  '            o  Monitors printer progress   $            o  Reports printer status               o  Handles exceptions  A            For example, suppose a user issues the following PRINT             command:.  8                $ PRINT /QUEUE=POST3 /NOTIFY THORNTON.TXT  A            The PRINT command line is translated to system servicetA            calls, which are sent to the job controller. The callsSE            are converted to job controller data structures, which arerC            then passed to the symbiont for processing. The symbiont.E            sends the processed arguments and file data to the printereA            and notifies the user by displaying messages about the #            status of the print job.   D            See the DCPS User's Guide for information about the PRINT&            command and its qualifiers.            1-4 DCPS Overview                 &         1.2.2 Device Control Libraries  F               A device control library is an OpenVMS text library thatD               contains setup modules. The symbiont uses modules fromG               the device control library to implement the various PRINTCG               parameters. The DECprint Supervisor software extracts the.H               appropriate module, depending on the qualifier that eitherG               appears on the PRINT command line or is associated with a G               print queue, and inserts the module into the data stream.1  G               The device control library also contains modules that the H               symbiont does not automatically use. Some of these modulesD               contain PostScript procedures, for example, to includeG               an error handler in a print job or to extend the findfont C               procedure to recognize alternate character encodings. ;               These are described in the DCPS User's Guide.   A               You can create setup modules to be used on your own >               systems. When you create setup modules, you mustC               store them in a device control library other than the E               DCPS$DEVCTL library. Create a device control library as G               described in Chapter 7 and add your library to the device F               control library search list defined in DCPS$STARTUP.COM.  H               When you create a site-specific device control library forE               your custom setup modules, the contents of your library F               are retained from one version of the DECprint SupervisorH               software to the next. The standard device control library,C               DCPS$DEVCTL, is overwritten when you upgrade from one 2               version of the software to the next.           1.2.3 Translators.  ?               When a print job submits a print file that is not1B               PostScript (or PCL, if your printer has a native PCL@               interpreter), the symbiont invokes a translator toE               translate the user's input file into PostScript. (Refer E               to Chapter 4 for more information about customizing theD:               printing system for certain types of files.)  C               DECprint Supervisor software can detect the file data D               type automatically. You need not specify the data typeF               on the PRINT command line. Translation to PostScript forF               successful printing is automatic. It is not necessary toC               maintain generic print queues for default data types.   H                                                        DCPS Overview 1-5    .            D            The system manager can associate a default data type withB            a generic print queue, allowing users to print files byD            specifying the generic queue name. See Chapter 3 for more            information..  B            If DCPS incorrectly identifies the data type of a file,>            you can identify the data type on the command line:  <                $ PRINT MYFILE.MEM /PARAMETERS=DATA_TYPE=ANSIC                $ PRINT MYFILE.POST /PARAMETERS=DATA_TYPE=POSTSCRIPT                                                                             1-6 DCPS Overview r  e                  H                                                                        2H         ________________________________________________________________  H                                                      Setting Up Printers      E               If you are installing DECprint Supervisor for the first.F               time, or installing new printers, read this chapter. YouC               may also find this chapter useful if you are changing.F               the setup of an existing printer. The following sectionsH               describe how to set up your printers to work with DECprint"               Supervisor software.  F                 ________________________Note  ________________________  D                 If you are changing the setup of a printer for which@                 a DCPS queue already exists, you must first stopC                 the associated queue using the STOP /QUEUE /NEXT or +                 STOP /QUEUE /RESET command.   E                 _____________________________________________________p  C               The devices that can be used with DECprint Supervisor.E               software are listed in the Software Product Description                (SPD).           2.1 Networked Printers  H               Your printer may contain a network interface card (NIC) orF               may be accessable to the network via a print server of a               terminal server.  @               Printers can be configured as network printers if:  D               o  The printer is connected to a NIC, print server, or!                  terminal server.d  H               o  Every host system using the printer is running DECprintE                  Supervisor software. If any host system accesses the0C                  printer by any other means, the printer system maym                  fail.  H                                                  Setting Up Printers 2-1    -            ;            Network printing has the following implications:-  <            o  The printer may be used from multiple systems.  A            o  There is no centralized accounting for the printer.rC               Each system maintains separate accounting information.8               for the printing performed by that system.  C            o  Multiple systems running DECprint Supervisor softwareS+               contend for the same printer.   B            o  There is no centralized print queue for the printer,               which means:  C               -  The SHOW QUEUE command does not display the queuesn7                  located on other nodes in the network.   A               -  The system does not provide print job scheduling A                  or load balancing among printers or nodes in the                   network.P  D            Except for LPD connections, DCPS requires that the entireB            communication path between your OpenVMS system and yourC            printer be bi-directional. For a networked printer, this A            communication path includes the connection between the C            printer and the network device as well as the connection.>            between the network device and your OpenVMS system.  D            LAT and AppleTalk network devices, and serial interfaces,C            usually provide bi-directional communication. Raw TCP/IP.E            network devices, and parallel ports on a printer, terminaliE            server, or print server, may not satisfy this requirement. A            Except for LPD connections, the DCPS software will not.E            work with a connection that does not allow status messages.D            and other information to be sent from the printer to your            OpenVMS system.        2.1.1 TCP/IP Printers  @            Printer protocols that layer upon TCP/IP are Raw TCP,C            LPD, Telnet and CPAP. DCPS uses CPAP to communicate with B            DIGITAL PrintServer printers. DCPS does not support the            Telnet protocol.i          2-2 Setting Up Printers    P            F               Before you can communicate with your printer via TCP/IP,@               you must define an IP address for it. You may also@               assign a name to the address. Refer to the printerG               documentation for information on setting the printer's IP.G               address. Refer to HP TCP/IP Services for OpenVMS, ProcesssH               Software MultiNet for OpenVMS, or Process Software TCPwareG               documentation for information on configuring your OpenVMS *               system's TCP/IP environment.  D               If your printer is connected through a print server orC               terminal server, you must configure the IP address of.C               the server. You also need to configure the connection F               between the printer and the server (for example, you mayC               need to perform actions similar to those described in G               Section 2.1.2.2 for LAT printers). Refer to documentation H               for your terminal server or printer server for information@               on configuring its network and printer interfaces.  #         2.1.1.1 Raw TCP/IP Printersi  G               Raw TCP/IP is a network protocol that utilizes the TCP/IP.E               protocol directly without any additional interpretation E               of the TCP data stream. It is supported by many printer E               Network Interface Cards (NICs), print servers, terminal ?               servers and other systems with remote LPD queues..  D               To communicate with your printer using Raw TCP/IP, theB               NIC, print server or terminal server that you use toD               connect your printer to the network must provide a RawE               TCP/IP port. Further, this Raw TCP/IP port must support G               bi-directional communication between the printer and your1D               OpenVMS system. DCPS does not work with unidirectionalG               Raw TCP/IP ports, such as those found on the NICs for the F               DEClaser 3500 and 5100 printers, the RapidPrint 200, andE               Hewlett-Packard JetDirect cards that interface with the 4               printer via its XIO (versus MIO) slot.           2.1.1.2 LPD Printers  A               LPD is a network protocol that is supported by many D               printer Network Interface Cards (NICs), print servers,C               terminal servers and PrintServer printers. Unlike thenH               other protocols that DCPS supports, LPD is unidirectional.B               This provides support for more printers but providesC               fewer features that rely on information returned from =               the printer, such as error and status messages.r  H                                                  Setting Up Printers 2-3 )                     2.1.1.3 CPAP Printers  =            CPAP (Common Printer Access Protocol) is a networkr<            protocol that is supported by DIGITAL PrintServerC            printers. CPAP is the preferred protocol for printing to.E            PrintServer printers over TCP/IP and the required protocol             for DECnet.        2.1.2 LAT Printers   3      2.1.2.1 Configuring the Printer for LAT Access.  E            To configure serial printers as network printers through ar@            LAT connection to the Ethernet, change the following:  ?            1. If you are using a serial printer connected via aa@               terminal server, set the necessary port and serverB               characteristics for the printer (see Section 2.1.2.2%               for DECserver devices).   I            2. Make the necessary changes to SYS$STARTUP:LAT$SYSTARTUP.COM.$               (see Section 2.1.2.3).  A            3. Set the communications speed (see Section 2.1.2.4)..  E            You can also change the printer password and printer name..D            These changes are optional and explained in Section 2.3.3            and Section 2.3.4.   7      2.1.2.2 Setting DECserver LAT Port Characteristics.  C               ________________________Note ________________________.  ;               The process for configuring non-DECserver LAT.A               devices is not described here, but many LAT devices ?               use the same commands used by a DECserver device. A               Refer to the online help or other documentation forDA               your NIC, terminal server, or print server for more                information.  C               _____________________________________________________c  =            To change DECserver port characteristics, you needu>            privileged status on the DECserver device. Once youC            have privileged status, use the DEFINE PORT and SET PORTn            commands.        2-4 Setting Up Printers .  .            F               The DEFINE command changes the port's characteristics inH               the server's permanent database. These changes do not take7               effect until the next login for the port.r  B               SET commands take effect immediately, but only alterE               the port's characteristics for the current session. For.H               example, to change the INPUT SPEED and OUTPUT SPEED valuesE               on PORT_6 to 19200 baud (on a DECserver 200), issue the A               following commands from the console server manager:   #               LOCAL> SET PRIVILEGEDD                PASSWORD> password  +               LOCAL> SET PORT 6 SPEED 19200r.               LOCAL> DEFINE PORT 6 SPEED 19200  F                 ________________________Note  ________________________  B                 DECprint Supervisor supplies a sample command fileA                 for this purpose, if using LAT. This command file2A                 sets the characteristics for a DECserver with the C                 Terminal Server Manager (TSM) software, and records D                 data in the TSM database. (TSM is a software productC                 available separately from HP.) The command file is:   M                 SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]DCPS$CONFIG-PRINTER-PORT.COM   C                 This command file provides examples of characteris- C                 tics for DECserver 100, DECserver 200 and DECserver                  500 devices.  E                 _____________________________________________________n  C               For information about the commands and procedures for G               your DECserver device, refer to your DECserver management                guide.  D               Make sure the DECserver port characteristics match theD               settings on your printer. Table 2-1 and Table 2-2 list@               DECserver port characteristics that must match the'               settings on your printer.4        H                                                  Setting Up Printers 2-5                 E            Table_2-1_DECserver_Port_Characteristics__________________3              Character     8            size               Parity        None.              Input speed   9600   E            Output_speed__9600________________________________________   D            Make sure the queue limit is not set to 0, which disables            queuing.i  E            Table_2-2_Printer-Required_DECserver_Port_Characteristics_S  E            Characteristic_____________Default_Settings_______________   ,            ACCESS                     REMOTE  .            AUTOBAUD                   DISABLED  .            AUTOCONNECT                DISABLED  .            AUTOPROMPT                 DISABLED  .            BREAK                      DISABLED  .            BROADCAST                  DISABLED  )            FLOW CONTROL               XONO  -            INPUT FLOW CONTROL[1]      ENABLED   -            OUTPUT FLOW CONTROL[1]     ENABLEDn  .            INACTIVITY LOGOUT          DISABLED  .            LOSS NOTIFICATION          DISABLED  .            MESSAGE CODES              DISABLED  -            QUEUING                    ENABLED   .            VERIFICATION               DISABLEDE            [1]Characteristic_not_supported_by_the_DECserver_500______i              server.E            __________________________________________________________         2-6 Setting Up Printers e  s            F                 ________________________Note  ________________________  >                 On many versions of DECserver devices, QUEUING=                 is not a port characteristic, but is a servers8                 characteristic whose default is ENABLED.  E                 _____________________________________________________:  2         2.1.2.3 Editing the LAT Configuration File  H               The LAT configuration file (SYS$STARTUP:LAT$SYSTARTUP.COM)C               defines host node service characteristics. Before youeA               start the print queues, make sure the LAT driver ist.               running and ports are available.  F                 ________________________Note  ________________________  =                 Commands referenced in this section are LATCP A                 commands. For more information on LATCP commands,yC                 refer to the HP OpenVMS System Management Utilitiesd!                 Reference Manual.c  E                 _____________________________________________________   H               1. Edit LAT$SYSTARTUP.COM and add the following command toF                  create an applications port on the host node (service6                  node) that will support your printer:  6                  $ CREATE PORT LTAd:/NOLOG/APPLICATION  E                  In this command format, you supply the number of the G                  applications port for d, which must be a unique number                   from 1-9999.   F                 ________________________Note  ________________________  A                 LTA devices are not always dedicated to printers;tB                 they may be shared with other devices. Connections<                 to the LTA device from the other devices areB                 established dynamically among the lowest available@                 ports. If you assign a higher port number to the=                 printer, you can help secure the port for the A                 printer and prevent interference from connections !                 to other devices.f  E                 _____________________________________________________i  H                                                  Setting Up Printers 2-7                 @            2. In LAT$SYSTARTUP.COM, add the following command toE               associate the applications port with a remote port on a                server:   P               $ SET PORT LTAd:/NODE=server_name/PORT=port_name/QUEUE/APPLICATION  E               In the command format, you supply the following values:   4               LTAd:     Name of the application port  7               server_   Name assigned to the LAT device                name  .               port_     LAT device's port name               name  ?               The following example associates application port A               LTA9000: with port PORT_7 on a remote DECserver 200                named LN03RDS:  L               $ SET PORT LTA9000:/NODE=LN03RDS/PORT=PORT_7/QUEUE/APPLICATION  B               If the LAT device is dedicated to printing services,B               you can define the LAT connection for the printer inA               the DCPS$STARTUP.COM file. This makes it easier for4A               you to solve configuration problems because all the D               information is in one file. However, if the LAT deviceC               also supports devices other than printers, you should <               define the port in the LAT$SYSTARTUP.COM file.  E            3. To make a successful LAT connection, you must make suresA               the following lists of groups have at least one LATl               group in common:  ?               o  On the LAT port, authorized groups and currentn                  groups   4               o  On the service node, enabled groups  ?               If you did not set up these groups correctly, you E               receive the following error message when a print job ish               submitted:  4               %DCPS-E-LRJACCESSDENIED, Access denied  E               You can use LATCP commands to include the necessary LAT C               group designations. For additional information, refer E               to the HP OpenVMS System Management Utilities References               Manual.e        2-8 Setting Up Printers n  e            F                 ________________________Note  ________________________  B                 This information is not required for the DECserver                 90L device.   E                 _____________________________________________________n  0         2.1.2.4 Setting the Communications Speed  F               Make sure the serial printer communications speed is setH               to the default (9600 baud). If you want the printer to runD               at a different baud rate, use the following procedure.  H               If the printer is on a DECserver device, use the following               steps:  G               1. Set the printer to the appropriate baud rate (see youre6                  printer hardware installation guide).  A               2. Set the DECserver communications speed (see your 5                  terminal server installation guide).n  D               3. Power on the printer. Wait for the printer to ejectH                  the power-up test page, and then check the test page toF                  ensure that the desired settings are indicated on the                  test page.            2.1.3 DECnet Printerss  A               DCPS uses CPAP over DECnet only to print to DIGITALg#               PrintServer printers.   F               Before you can communicate with your DIGITAL PrintServerE               printer via DECnet, you must assign a DECnet address toeA               it. You may also associate a name with the address.a  G               Refer to the PrintServer documentation for information onb3               setting the printer's DECnet address.f  E               To associate a DECnet node name name with the printer'saD               DECnet address, use the NCP command if you are runningF               DECnet Phase IV software, or the DECNET_REGISTER commandB               if you are running DECnet-Plus (formerly DECnet/OSI)B               software. Refer to the DECnet documentation for more>               information about node names and these commands.  H                                                  Setting Up Printers 2-9                       2.1.4 AppleTalk Printers   ?            If you use your printer in an AppleTalk network, thee=            address of the printer in the AppleTalk network isb@            normally the printer's PostScript printername. If twoA            or more printers have the same printer name and are on B            the same zone of the AppleTalk network, the actual nodeB            names for these printers will be depend on the order inB            which the printers are powered up. Printers of the sameB            product type will have the same printername until it isD            explicity changed. Therefore, it is necessary to change aC            printer's printer name to ensure the printer is uniquely D            and consistently identified on the network. Use the tools?            provided with your printer, and/or your Macintosh tot+            change the name of your printer.a  +      2.2 Directly-Connected Serial Printers   <            For your printer and OpenVMS system to be able toB            communicate, you must set the baud rate of your printerC            and system's serial interfaces to the same values. Also, C            your printer should be set for eight-bit characters with             no parity.i  C               ________________________Note ________________________l  A               When choosing a baud rate other than the default of <               9600 baud, consider the following limitations:  B               o  OpenVMS drivers do not support baud rates of 3600                  and 7200 baud.s  >               o  DMZ32 serial interfaces, Revision E or lower,6                  require a speed of 4800 baud or less.  A               o  If you select an improper speed, the printer mayr6                  not operate or may stop unexpectedly.  C               _____________________________________________________   B            Refer to your printer's hardware installation guide forE            information on configuring its serial interface. After you D            have made the necessary changes, turn the printer off andC            back on. Then manually print a test page and verify that 0            the reported settings are as desired.        2-10 Setting Up Printers                  ?               Set the baud rate of your OpenVMS system's serialdA               interface by specifying a value for P6 when setting D               up the corresponding DCPS print queue, as described in               Section 3.3.6.  F                 ________________________Note  ________________________  E                 CSA0: (printer port 0 on VAXstation II and VAXstation @                 II/GPX systems) is not a supported interface for                  serial printers.  @                 DEClaser printers may require an H8571-E adapter;                 if you are using a DECconnect serial cable. A                 Refer to your printer installation guide for more                  information.  E                 _____________________________________________________            2.3 General Information             2.3.1 Supported Printers  E               You can use DCPS with many PostScript printers. ConsultiA               the SPD for the list of supported printers. You maykE               also be able to use DCPS in an unsupported fashion with:@               printers not listed in the SPD (see Section 7.12).  A               Before installing a printer, perform the following:   E               o  Install a PostScript option if your printer requiresr                  one.r  B               o  Install at least the minimum amount of memory for%                  PostScript printing.t  H               Printing legal size paper or printing duplex requires moreF               memory than the base configuration. Consult your printer3               manual for your minimum requirements.s  )         2.3.2 Setting the printer timeoutk  F               The printer may abort a print job if it does not receiveE               data for a specified period of time. HP recommends that F               you change the timeout value to zero (0), which means no               timeout.  H               You may be able to set the timeout value through the frontC               panel, as documented in the operator's guide for your                printer.  H                                                 Setting Up Printers 2-11 g  t            A            You can also change the printer timeout value with the C            setdefaulttimeouts PostScript operator. Modify the stan-             dard fileA            SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]LPS$SET_TIMEOUT.PS to B            change the timeout value to 0. Print the file using theE            DATA_TYPE=POSTSCRIPT parameter to change the timeout valuerD            in the printer's nonvolatile memory to 0, thus preventing-            timeout conditions on the printer.e  C            To submit the file for printing as a PostScript job, useg!            the following command:m  K                $ PRINT /QUEUE=queue-name /PARAMETERS=(DATA_TYPE=POSTSCRIPT)i$                _$ LPS$SET_TIMEOUT.PS  @            When the print job is processed, a page is printed to>            indicate that the timeout was successfully changed.  (      2.3.3 Changing the Printer Password  B            PostScript printers have passwords that restrict access@            to certain functions. You can change the password forD            your printer from the default value. For serial printers,C            submit a print job that includes the current password asTE            well as the new password. Refer to the PostScript PrintersaA            Programmer's Supplement for information about changing #            your printer's password.q  >            The default password for ScriptPrinters is (LN03R),>            with the parentheses required. The default password@            for DEClaser printers is 0 (the number zero), withoutC            parentheses. If you change the printer password from thee@            default, print jobs may take longer to print, because@            the printer password is required to persistently loadD            PostScript prologues for ANSI files and separation pages.  #      2.3.4 Setting the Printer Name   @            Some system messages include the printer name. If youE            have not set a unique printer name, these messages contain D            the default printer name. The default printer name is theD            model name of the printer. For example, on an HP LaserJet@            9000 printer where the name has not been changed, the?            following message reflects the default printer name:   [            %DCPS-I-TRAYSUBST, Output will be delivered to the only tray on HP LaserJet 9000U        2-12 Setting Up Printersa t               @               If you change the DEClaser printer name to "OfficeF               Printer", the same error message reflects the unique new               printer name:S  `                   %DCPS-I-TRAYSUBST, Output will be delivered to the only tray on Office Printer  F               For non-PrintServer printers, the printer name is storedE               in the printer's nonvolatile memory. To set the printer C               name, edit a copy of the file LPS$SET_PRINTER_NAME.PS                found inG               SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]) to include the desirediG               name and password. Select a printer name of 31 charactersh               or less.  D               Then submit the file for printing as a PostScript job:  P                   $ PRINT /QUEUE=queue-name /PARAMETERS=(DATA_TYPE=POSTSCRIPT) -,                   _$ LPS$SET_PRINTER_NAME.PS  H               Edit and submit a copy of LPS$SET_PRINTER_NAME.PS for each2               printer that requires a unique name.                                                H                                                 Setting Up Printers 2-13 E  O                  H                                                                        3H         ________________________________________________________________  H                                      Creating and Modifying Print Queues      G               This chapter explains how to start up the printing system #               and test the printer.h  F                 ________________________Note  ________________________  D                 Make sure the system queue manager is running before                  creating queues.  E                 _____________________________________________________i  A         3.1 If You Are Installing the Software for the First Timef  D               If this is a new installation, you can use the startupD               template file to help you set up your queues. Copy the7               printer startup template file as follows:   H                   $ COPY SYS$COMMON:[SYS$STARTUP]DCPS$STARTUP.TEMPLATE -1                   _$ SYS$COMMON:[SYS$STARTUP].COM   @         3.2 If You Are Upgrading From DECprint Printing Services             Software (CPS)  A               DECprint Printing Services (CPS) is the predecessorh@               software to DECprint Supervisor (DCPS). If you areB               upgrading from CPS to DCPS, see Section D.2 for more               information.  '         3.3 Setting Up Execution QueuesU  D               You must create an execution queue for each PostScriptH               printer. Execution queues schedule jobs for processing andH               deliver the print jobs to a printer. An execution queue is3               associated with a particular printer.     H                                  Creating and Modifying Print Queues 3-1                 E            When you create an execution queue, you supply informationeA            about the queue, including its name and default param-oB            eters. Example 3-1 shows creation of an execution queueE            for a Raw TCP/IP printer. Example 3-2 shows creation of an D            execution queue for a PrintServer printer. These commands*            are placed in DCPS$STARTUP.COM.    ?      Example 3-1 Creation of an Execution Queue Entry for a Raw                   TCP/IP Printer   G          $ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - H              2UP -                           ! P1 - Execution queue nameU              "IP_RawTCP/lnm40.my.com" -      ! P2 - Interconnect protocol/device namesQ              DCPS_LIB -                      ! P3 - Logical name for library(ies) L              "NUMBER_UP=2" -                 ! P4 - Default queue parametersL              "/DEFAULT=(FLAG,FORM=MYFORM)" - ! P5 - Default queue qualifiersU              "" -                            ! P6 - Communication speed (serial only)eJ              "" -                            ! P7 - Device characteristicsA              ""                              ! P8 - Verify on/offm  >            This queue is called 2UP and uses Raw TCP/IP to theB            printer called lnm40.my.com. Jobs printed to this queueC            print two pages to a sheet, with a flag page and includeI'            the code in the form MYFORM.   ;      Example 3-2 Creation of an Execution Queue Entry for a $                  PrintServer Printer  G          $ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - H              LPS20$BULL09 -                  ! P1 - Execution queue nameU              "DECnet/BULL09" -               ! P2 - Interconnect protocol/device name Q              DCPS_LIB -                      ! P3 - Logical name for library(ies)rL              "SIDES=2" -                     ! P4 - Default queue parametersL              "" -                            ! P5 - Default queue qualifiersU              "" -                            ! P6 - Communication speed (serial only)iJ              "" -                            ! P7 - Device characteristicsA              ""                              ! P8 - Verify on/off7  A            This queue is called LPS20$BULL09 and uses DECnet to aeB            PrintServer printer called BULL09. Jobs printed to this!            queue print in duplex.l      ,      3-2 Creating and Modifying Print Queues e  n            F         Example 3-3 Creation of an Autostart Queue Entry for a Raw TCP                     /IP Printere  J             $ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE -A                 HP9000_RAW -                                 ! P1fA                 (FOO,BAR)::"IP_RawTCP/hp9000.lkg.dec.com" -  ! P2 A                 DCPS_LIB -                                   ! P3 A                 "SIDES=2" -                                  ! P4 A                 "/SEPARATE=(NOBURST,FLAG)" -                 ! P5 A                 "" -                                         ! P6 A                 "" -                                         ! P7 A                 ""                                           ! P8   G               This queue is called HP900_RAW and uses Raw TCP/IP to theyD               printer called hp9000.lkg.dec.com. The queue is set toH               autostart on nodes FOO and BAR. Jobs printed to this queueE               print in duplex and with a flag page but no burst page.n  F                 ________________________Note  ________________________  ?                 Configure your system so that required software B                 is started before you start your execution queues.A                 For example, for a networked printer, ensure thatiA                 the corresponding TCP/IP, LAT, DECnet, AppleTalk, B                 or PrintServer Supporting Host software is started                 first.  <                 Also, if you invoke DCPS$EXECUTION_QUEUE.COM@                 directly, and neglect to add the same command to?                 DCPS$STARTUP.COM, some DCPS queues may not workY2                 after your OpenVMS system reboots.  E                 _____________________________________________________   F               The following sections describe each item of information@               you need to supply to DCPS$EXECUTION_QUEUE.COM, as$               outlined in Table 3-1.                H                                  Creating and Modifying Print Queues 3-3 l               E            Table_3-1_Parameter_Values_for_Execution_Queues___________   E            Parameter___Value_________________________________________f  2            P1          Name of the execution queue            (required)w  D            P2          Printer device description, including some or,            (required)  all of the following:  A                        Node name if in an OpenVMS Cluster and you_C                        want to specify the system on which the DCPSr)                        queue is to be runr  ,                        Interconnect protocol  :                        Port number for Raw TCP/IP printers  2                        Queue name for LPD printers  E                        AppleTalk zone for AppleTalk printers and zone '                        name is requiredi  D                        AppleTalk printer type for AppleTalk printers3                        and printer type is requirede  >            P3          Logical name pointing to device control#            (required)  library(ies)   /            P4          Default queue parametersr            (optional)   /            P5          Default queue qualifierso            (optional)n  B            P6          Communication speed (for directly-connected+            (optional)  serial devices only)d  -            P7          Device characteristicsp            (optional)i  9            P8          Verification setting for debuggingaE            (optional)________________________________________________s  9      3.3.1 Supplying the Name of the Execution Queue (P1)   <            An execution queue name can have 1-31 characters,E            including uppercase and lowercase alphabetical characters, D            digits, the dollar sign ($), and the underscore characterE            (_). The queue name must include at least one alphabetical 8            character and cannot have intervening spaces.  ,      3-4 Creating and Modifying Print Queues s  .            4         3.3.2 Supplying the Printer Device Name (P2)  D               The printer device name specifies the interconnect andH               device used to access the printer, and the OpenVMS Cluster.               member node on which it resides.  A               If the OpenVMS system is not a member of an Openvms H               Cluster, specify the P2 parameter in the following format:  E                   "interconnect/interconnect_specific_device_address"i  B               If the system is a member of an OpenVMS Cluster, andE               you want the queue to run on a particular system in thewH               cluster, specify the P2 parameter in the following format:  K                   node::"interconnect/interconnect_specific_device_address"t  F               If the system is a member of an OpenVMS Cluster, and youG               want the queue to be an autostart queue and run on one oreF               more systems in the cluster, specify the P2 parameter in#               the following format:e  ^                   AUTOSTART_ON=(nodelist)::"interconnect/interconnect_specific_device_address"                 where:  H               o  node is the name of the OpenVMS Cluster member on which$                  the queue executes.  E               o  nodelist contains the name(s) of the cluster membersmB                  on which the queue executes. The node list shouldE                  be either one node name, or more than one node name, %                  separated by commas.   F               o  interconnect specifies the interconnect type. You can.                  specify one of the following:                  H                                  Creating and Modifying Print Queues 3-5    n          E               _______________________________________________________t9                                             Specify . . . E               For_._._._______________________________See_._._.______   E               Printers that connect with    IP_       Section 3.3.2.1e2               Raw TCP/IP sockets            RawTCP  E               Printers that connect with    IP_LPD    Section 3.3.2.2                LPD   E               Printers that connect         serial    Section 3.3.2.3i"               directly or with LAT  E               PrintServer printers that     IP_CPAP   Section 3.3.2.5r'               connect with TCP/IP usingm*               the CPAP protocol and TCP/IP  E               PrintServer printers that     DECnet    Section 3.3.2.4o'               connect with DECnet using *               the CPAP protocol and DECnet  E               Printers that connect with    AppleTalk Section 3.3.2.6 %               EtherTalk and LocalTalkrE               protocols______________________________________________e  @            o  interconnect_specific_device_address is the actual%               address of the printer.a  B            Please note the following details concerning autostart:  D            o  The same procotol and device is used on all nodes. YouE               must ensure the printer device is available on any nodeu.               specified in the autostart list.  A            o  DCPS does not check the node name(s) you specify torB               determine if it is an existing node name. Be sure to.               specify the node name correctly.  C            o  You must ensure that DCPS is installed and configured :               on any node specified in the autostart list.  ?            o  DCPS autostart queues are activated for autostartsA               when DCPS$STARTUP is run, unless it is being run inpE               setup mode. (See Section 3.4 for more information about @               running the DCPS startup procedure in setup mode.)  6            o  AUTOSTART_ON may be abbreviated as AUTO.  ,      3-6 Creating and Modifying Print Queues    l            D               o  Do not use double colons (::) when specifying nodesF                  in the autostart list. A double colon must be used toE                  separate the list of autostart nodes and the rest ofr"                  the P2 parameter.  F                 ________________________Note  ________________________  ?                 The device specification syntax allows a device B                 name to be longer than 39 characters. Those device@                 names that are longer than 39 characters displayB                 as "DCPS$" for the value of the /ON qualifier. TheA                 device name is stored in logical name DCPS$queue- !                 name_DEVICE_NAME.   E                 _____________________________________________________   C         3.3.2.1 If Your Printer Is On a TCP/IP Network and Uses Rawy                 TCP/IP Sockets  C               Enter the device information in the following format:P  *                   "IP_RawTCP/address:port"                 where:  E               address is the IP address of your NIC, print server, orPB               terminal server in either a named or numeric format.  E               port is the number of the Raw TCP port for your networkcA               device. Check the documentation for your NIC, printnD               server, or terminal server to determine what number toF               use. Table 3-2 shows the port numbers for some commonly-C               used devices. If no port number is specified, 9100 is                used.a                      H                                  Creating and Modifying Print Queues 3-7 h  o            E            Table_3-2_Raw_TCP/IP_Port_Numbers_________________________i  A               20nn  DECserver terminal servers, where "nn" is thea(                     physical port numberD               2501  DIGITAL LN17ps and DIGITAL Laser Printer LN17+ps                     Emulex NICs_8               3001  DIGITAL Laser Printer LN15 and LN15+7                     DIGITAL RapidPrint 500 print server .               6869  Compaq Laser Printer LNC02>                     DIGITAL Laser Printer LN20, LN40 and LNC02=               9100  Compaq Laser Printer LN16, LN32 and LNM40 >                     GENICOM Intelliprint mL, LN and microLaser                     printers:                     GENICOM RapidPrint MPS100 print server.                     HP Color LaserJet printers(                     HP LaserJet printers*                     IBM InfoPrint printers@                     Lexmark C, Optra, S, Optra T, T and W series                     printers-                     Tektronix Phaser printersi.                     Xerox DocuPrint N printers?                     HP JetDirect, Lexmark and XCD print servers E            ___9101__HP_9085_MFP______________________________________   B            For example, a Raw TCP/IP printer could be specified by             any of the following:  +                "IP_RawTCP/ln40.my.org:6869"a)                "IP_RawTCP/8.9.10.11:9100" -                "IP_RawTCP/hp4300.lkg.dec.com"D  C               ________________________Note ________________________E  :               If you specify the wrong port number for the=               printer, DCPS is unable to communicate with theI;               printer. However, because the symptoms are noAA               different than if the printer were busy or offline,D=               you do not receive any indication that the port_               number is wrong.  C               _____________________________________________________         ,      3-8 Creating and Modifying Print Queues                 C         3.3.2.2 If Your Printer Is On a TCP/IP Network and Uses LPDl  C               Enter the device information in the following format:h  -                   "IP_LPD/address:queue-name"                  where:  B               address is the IP address of your NIC, print server,C               terminal server or remote system in either a named or                numeric format.p  H               queue-name is the name of the internal queue name for yourG               network device. Check the documentation for your printer,_D               NIC, print server or terminal server to determine whatC               name to use, if any. Most printers do not require youCE               to specify an internal queue name, but you must specify.D               a queue name for a remote LPD queue. See Table 3-3 forE               some printers that require an internal queue name to bet.               specified when creating a queue.  F               For example, an LPD printer could be specified by any of               the following:  &                   "IP_LPD/ln40.my.org"$                   "IP_LPD/8.9.10.11"6                   "IP_LPD/lsr2000.lkg.dec.com:xjprint"3                   "IP_LPD/linuxbox.zko.hp.com:ln03"   H               Table_3-3_Internal_LPD_Queue_Names________________________  H               Printer____________________Internal_Queue_Name____________  0               DIGITAL Colorwriter LSR    xjprint               2000  .               DIGITAL DEClaser 3500      PORT1  1               DIGITAL Laser Printer      PASSTHRU_               LN17+pst  H               DIGITAL_LN17ps_____________PASSTHRU_______________________  A               If you fail to specify the internal queue name when H               required or specify the wrong name, your print job will beH               put on hold and the queue will stop. You will also receive0               messages similar to the following:  H                                  Creating and Modifying Print Queues 3-9                 J                %DCPS-F-LPDTERMINATED, LPD connection abnormally terminatedN                -DCPS-I-JOB_ID, for job S (queue SNOBALL, entry 866) on SNOBALL  G                %%%%%%%%%%%  OPCOM  19-SEP-2003 12:12:48.88  %%%%%%%%%%% 1                Message from user SYSTEM on FUNYET Y                Queue SNOBALL: %DCPS-F-LPDTERMINATED, LPD connection abnormally terminated   <      3.3.2.3 If Your Printer Is On a LAT Network or Directly              Connected  8            Use the following format for serial printers:  E            __________________________________________________________o            If Your            Serial      Use Thisn#            Printer is  Format . . .rE            On_._._.________________Where_._._._______________________   C            A local     "SERIAL     x is the printer type code, y is D            serial      /Txyn"      the controller name, and n is the;            line                    host system unit number.   D            A LAT port  "SERIAL     n is the host system unit number.E            ____________/LTAn"________________________________________   C               ________________________Note _________________________  @               The SET TERMINAL and SET DEVICE commands translate=               the name of the printer for serial printers. To ?               prevent the commands from translating the printereA               name, prefix the printer name with an underscore (_                ).  C               _____________________________________________________   D      3.3.2.4 If Your PrintServer Printer Is Part of a TCP/IP Network  @            Enter the device information in the following format:                   "IP_CPAP/address"  F            where address is the IP address of your DIGITAL PrintServer7            printer in either a named or numeric format.l  D            For example, a PrintServer TCP/IP node could be specified&            by either of the following:  +                "IP_CPAP/garmnd.dsg.dec.com"_&                "IP_CPAP/16.128.144.11"  -      3-10 Creating and Modifying Print Queuesd t  t            G         3.3.2.5 If Your PrintServer Printer Is Part of a DECnet Network   C               Enter the device information in the following format:   #                   "DECNET/nodename"e  D               where nodename is the DECnet node name of your DIGITAL"               PrintServer printer.  G               For example, a PrintServer DECnet node could be specifiede               by:c  !                   "DECNET/GARMND"c  ?         3.3.2.6 If Your Printer Is Part of an AppleTalk Network_  G               You can include printers in your printing system that arerE               connected to an AppleTalk network. To make an AppleTalk B               printer a network sharable device, the PATHWORKS forF               OpenVMS (Macintosh) software must be running on the same2               node that is running the DCPS queue.  C               Enter the device information in the following format:l  3                   "APPLETALK/printername@zone@type"p                 where:  C               o  printername is the AppleTalk node name assigned to G                  the printer. This is the PostScript printer name. This #                  value is required.o  G               o  zone is the zone that includes the printer. This valuetC                  is optional. The default is the AppleTalk zone for G                  the network segment of the OpenVMS system on which the (                  print queue is running.  G               o  type describes the printer's accessibility. This value A                  is optional. Generally, the type is LaserWriter.o  @               When only printername is required, the informationD               provided for P2 would be just "APPLETALK/printername".  E               For example, an AppleTalk printer could be specified by #               any of the following:L  H                                 Creating and Modifying Print Queues 3-11 u  s            )                "APPLETALK/Paul's Printer"p-                "APPLETALK/Paul's Printer@MRO"n9                "APPLETALK/Paul's Printer@MRO@LaserWriter"o  C               ________________________Note ________________________e  @               PATHWORKS for OpenVMS (Macintosh) has been retired)               and is no longer supported.e  C               _____________________________________________________u  2      3.3.3 Supplying the Library Logical Name (P3)  =            The name of the standard device control library is ;            DCPS$DEVCTL. This is the default library name ifi?            this parameter is blank. Refer to Chapter 7 for moremB            information about creating device control libraries and<            defining the device control library logical name.  B      3.3.4 Assigning Default PRINT Command Parameters to the Queue            (P4)i  >            You can specify default PRINT command parameters to?            associate with the queue. Any PRINT parameter can be_<            associated by default with a queue. Default PRINT?            parameters are used when the print job prints on thes?            specified queue, unless the user specifies differentnD            parameter values in the PRINT command line. The parameterB            values specified in the PRINT command line override the$            default queue parameters.  D            Place quotes around default PRINT parameters, as shown in!            the following example:r  0            $ @SYS$STARTUP:DCPS$EXECUTION_QUEUE -N                2UP -                               ! P1 - Execution queue name[                "SERIAL/TTB4:" -                    ! P2 - Interconnect protocol/Device name W                DCPS_LIB -                          ! P3 - Logical name for library(ies) R                "SIDES=2"                           ! P4 - Default queue parameters            -      3-12 Creating and Modifying Print Queuese P  o            B               How DECprint Supervisor Prioritizes PRINT Parameters  F               Parameters set by the /PARAMETERS qualifier of the PRINTG               command override any defaults set for the queue. DECprint A               Supervisor uses default values for parameters, from 5               highest to lowest priority, as follows:f  :               1. Parameters specified in the PRINT command  ?               2. Queue defaults specified for the generic queue   A               3. Queue defaults specified for the execution queuea  7               4. Defaults built into the DCPS software:D  '                     DATA_TYPE=AUTOMATICu2                     INPUT_TRAY=printer-specific[1]@                     LAYUP_DEFINITION=no default layup definition2                     MEDIA_TYPE=printer-specific[1]'                     MESSAGES=NOMESSAGES                      NUMBER_UP=0n3                     OUTPUT_TRAY=printer-specific[1]i'                     PAGE_LIMIT=no limitt-                     PAGE_ORIENTATION=PORTRAITd2                     PAGE_SIZE=(same as SHEET_SIZE)                     NOPUNCH'!                     SHEET_COUNT=1 2                     SHEET_SIZE=printer-specific[1]-                     SIDES=printer-specific[1]p                     STAPLE=NONE                      TAB=NOTABt  A               Some parameter values are controlled by the printer B               hardware and can be set through means other than theH               DECprint Supervisor software. DIGITAL PrintServer printersF               are affected by the PrintServer Software. Other printersA               are controlled through the printer control panel oro               switches.o    !               ___________________eF               [1]These settings depend on the setting of the printer's  (                  PostScript interpreter.  H                                 Creating and Modifying Print Queues 3-13    c            2      3.3.5 Supplying Default Queue Attributes (P5)  C            You can supply a value to override or add to the default D            queue attributes. Do not use the INITIALIZE/QUEUE command=            to set these qualifiers. Enter them into the queue_            definition instead.  D            By default, the printer startup command procedure createsE            print queues with the following INITIALIZE/QUEUE qualifiere            settings:  /            o  /SEPARATE=(BURST,TRAILER,NORESET)   <               The /SEPARATE qualifier is used to specify job>               separation pages. The default setting specifies:  !               -  Job burst pages.   #               -  Job trailer pages.   ;               -  No reset module is sent between print jobs A                  (NORESET). This setting is included for compati- D                  bility with sites upgrading from PrintServer client                  software.  (            o  /FORM_MOUNTED=DCPS$DEFAULT  A               This qualifier allows you to include a default form B               definition assumed to be mounted on the printer. TheA               default form for ANSI jobs only is DCPS$DEFAULT. IfiB               you include a form definition with the /FORM_MOUNTED@               qualifier, specify the same form definition in the)               /DEFAULT qualifier as well.p              o  /DEFAULT=(NOFEED),  <               The /DEFAULT qualifier specifies default PRINTC               qualifiers. The standard queue definition specifies a E               default setting of NOFEED on print jobs. You can modify D               this command line to include any PRINT qualifiers. ForE               example, you can include your own form to be applied toH<               print jobs when a form definition is required:  /                   /DEFAULT=(FORM=MYFORM,NOFEED)e  ?               If you specify the /DEFAULT qualifier, be sure to C               include the FORM and NOFEED keywords. If they are not B               included, the values revert to the OpenVMS defaults,C               which are not compatible with the DECprint Supervisors               software.P  -      3-14 Creating and Modifying Print Queues                  F                 ________________________Note  ________________________  C                 If you include more than one qualifier in the queueaB                 definition, enclose the values in quotation marks.  E                 _____________________________________________________   8         3.3.6 Setting the Speed for Serial Printers (P6)  F               You can set the communications speed for serial printers?               attached directly to your OpenVMS system. If thiseE               parameter is blank, the default is 9600 baud. To changeaH               the speed, replace the null string ("") with a value, suchH               as "19200". For printers that utilize network connections,(               this parameter is ignored.  ?         3.3.7 Supplying SET DEVICE Qualifiers to the Queue (P7)e  H               You can specify the SET DEVICE command qualifiers for thisF               queue. For example, to enable error logging, include the               following string:   "                   "/ERROR_LOGGING"  A               Now, all error messages reported by the printer areeF               recorded in the error log file, SYS$ERRORLOG:ERRLOG.SYS.E               You can read this file using the ANALYZE/ERROR command.o  ?               This parameter is valid for serial printers only.   B         3.3.8 Enabling SET VERIFY When Initializing the Queue (P8)  C               You can specify the setting of the SET VERIFY commandTE               for the DCPS$EXECUTION_QUEUE.COM command procedure. The E               default setting is NOVERIFY, to save log file space andoB               console log space. If P8 contains 1, then SET VERIFYD               is enabled, which is useful for diagnosing problems inD               the printer startup file. (Refer to the HP OpenVMS DCLF               Dictionary for more information about the SET [NO]VERIFY               command.)           H                                 Creating and Modifying Print Queues 3-15    2            4      3.4 Running the Startup Procedure in Setup Mode  D            The DCPS startup procedure, DCPS$STARTUP, can be run in aC            shortened "setup" mode. This mode would most commonly befC            used if your queues are autostart queues, and you wantediD            to speed up the execution of DCPS$STARTUP. In setup mode,B            logical names needed by DCPS are defined, but no queues,            are created, modified or started.  B            To run DCPS$STARTUP in setup mode, pass SETUP as the P1"            parameter. For example,  .              $ @SYS$STARTUP:DCPS$STARTUP SETUP  >            To define logical names, DCPS$STARTUP now creates a?            "setup file" each time it runs in normal (non-setup) B            mode. This file is called DCPS$STARTUP_SETUP.COM and is@            run when DCPS$STARTUP is later run in setup mode. TheC            setup file should not be modified and is only for use bye            DCPS$STARTUP.  C            Please note the following details concerning setup mode:   F            o  When run in setup mode, all commands in DCPS$STARTUP.COM@               are executed, except for initializing or modifying;               queues with calls to DCPS$EXECUTION_QUEUE andmB               DCPS$GENERIC_QUEUE. All other code, such as creatingA               LAT devices or defining queue-related logical namesa?               such as DCPS$queue-name_NO_SYNC will be executed.e  C            o  If the setup file does not exist when DCPS$STARTUP ispD               run in setup mode, startup will run in normal mode and+               a setup file will be created.n  @            o  DCPS$STARTUP will display whether it is running in#               setup or normal mode.D  E            o  If running in setup mode, DCPS$STARTUP will display thet:               creation date of the setup file it is using.  @            o  If running in setup mode, and DCPS$STARTUP.COM has@               been modified since the setup file was created, an>               informational message will be displayed. StartupB               will continue in setup mode, ignoring changes to theE               procedure made in the portion of DCPS$STARTUP that does C               not run in setup mode. In this case, DCPS$STARTUP.COMs@               should be reviewed to see if any changes affecting  -      3-16 Creating and Modifying Print Queues     $            H                  queues were made, and run again in normal mode so a new+                  setup file can be created.q  C               o  If you want to use DCPS$STARTUP in setup mode, and @                  you have not previously done so, make sure your?                  DCPS$STARTUP.COM procedure was created from at A                  least the V2.3 version of DCPS$STARTUP.TEMPLATE._>                  If your DCPS$STARTUP.COM is too old, you mustC                  copy DCPS$STARTUP.TEMPLATE to DCPS$STARTUP.COM and >                  incorporate your site-specific modifications.  0         3.5 Customizing Execution Queue Behavior  D               You can alter the behavior of DCPS print symbionts andG               their corresponding execution queues in a number of ways, C               several of which are described in this section. Other_B               options are listed in Appendix B, along with generalD               guidelines for making the changes. Some customizationsH               apply to all DCPS queues while others apply only to queues               that you specify.   5         3.5.1 Running DCPS as a Multistreamed Process   D               DECthreads is used to implement the numerous functions@               of DCPS. All processes that use DECthreads executeD               periodically to determine if any threads can run. EvenA               when no jobs are printing, DECthreads causes a DCPSrA               process to run to determine if any threads can run.fD               If there are many DCPS queues started on a system, theF               scheduling and periodic execution of all these processesD               can use a significant amount of CPU time. This problemE               is resolved by running DCPS as a multistreamed process,cD               thereby reducing the number of symbiont processes that               must execute.   G               When running multistreamed, one DCPS process can run more F               than one DCPS execution queue. A new DCPS process is notC               started every time a DCPS print queue is started, but H               only when all current processes are supporting a specifiedH               maximum number of queues ("streams"). The number of queuesH               that a DCPS symbiont process will support is determined byE               the value of the logical name DCPS$MAX_STREAMS when then!               process is started.e    H                                 Creating and Modifying Print Queues 3-17 n               ?            DCPS can be configured to support up to 32 execution =            queues per DCPS symbiont process. The logical nameuC            DCPS$MAX_STREAMS is used to specify the number of queuesnE            per DCPS symbiont process. To define this logical, specify >            the following command in your DCPS$STARTUP.COM file@            (a template is provided in DCPS$STARTUP.TEMPLATE) andA            substitute the number of queues per process to use. If @            this logical name is not defined, a DCPS process will0            support only one (1) execution queue.  K                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$MAX_STREAMS max-number   D            Execute your DCPS$STARTUP.COM file to define this logicalB            name and start your queues with DCPS as a multistreamed            process.q  D            A DCPS process terminates only when all queues associated(            with the process are stopped.  =      3.5.1.1 Managing Print Queues When Running Multistreamed   E            The OpenVMS Queue Manager controls when a symbiont processTC            is created and terminated. Generally a new DCPS symbiont C            process is created when there are no free streams in allL,            existing DCPS symbiont processes.  ?            The set of print queues that a DCPS symbiont process B            supports is determined by the order in which queues are?            started, and by any subsequent stopping (STOP /QUEUE C            /RESET or STOP /QUEUE /NEXT) and starting (START /QUEUE)"B            of queues. DCPS defines a logical name which identifies@            the process ID for a queue (Section 5.8). You can useE            these logical names to determine the process that supportsiB            a queue and the set of queues that are supported by the            same process.  A            Although not likely, a problem observed with one queueeD            could be the result of a problem that exists with another?            queue, because both queues are supported by the sameaA            process. It may not be sufficient to examine the state A            of one job on one queue to identify a problem. You mayE@            need to look at the state of the first job on all the1            queues supported by that DCPS process.0    -      3-18 Creating and Modifying Print Queues                  E               A DCPS queue should not be stopped by stopping the DCPS H               process that supports that queue. Stopping a DCPS symbiontD               process with STOP /IDENTIFICATION will stop all of the/               queues supported by that process.   :         3.5.1.2 Changing the DCPS Environment When Running                 Multistreamed   C               With a single-streamed DCPS symbiont process, changeshB               to DCPS logicals names and other aspects of the DCPSB               environment may not take effect until after you haveA               issued a STOP /QUEUE /RESET and then a START /QUEUEnE               command for the associated queue, depending on what you_#               are trying to change.o  D               To change the behavior for a single DCPS queue that isF               associated with a multistreamed process, you may need toD               stop all the DCPS queues associated with that symbiontG               process and then restart them before the change will takeoE               effect. This is because some aspects of the environment G               are determined only when the DCPS symbiont process starts E               (rather than when a DCPS queue starts) and the symbiontMF               process does not stop until all of its associated queues               are stopped.  ?         3.5.1.3 Determing the Proper Value for DCPS$MAX_STREAMS   C               There are several factors to consider to determine an D               appropriate number of queues per DCPS symbiont process               including:  D               o  You can reduce the number of process slots taken byE                  DCPS by increasing the number of queues per process.VH                  This will free up process slots. By reducing the numberE                  of DCPS symbiont processes, you reduce the number offF                  DECthread processes that must run periodically, which-                  improves system performance.   H               o  Even though a DCPS process can be configured to supportB                  more than one execution queue, DCPS can translateA                  only one file at a time. To avoid contention foreH                  translators, when a stream (queue) in a process needs aF                  translator that is already in use, the translator forH                  that stream is started in a separate temporary process.H                  This can impact performance if your site primarily usesE                  one translator, and print queues are generally busy.s  H                                 Creating and Modifying Print Queues 3-19    g            B               To reduce the likelihood of a impact on performance,:               choose a smaller value for DCPS$MAX_STREAMS.  B            o  The maximum number of queues per process is 32. This<               limit is imposed by the OpenVMS queue manager.  E            o  A DCPS process running multiple print queues represents D               a potential single point of failure. If the supervisor?               process fails, or someone stops the process, then *               several queues are affected.  7      3.5.2 Interrupting Busy Printers When a Job Startsf  >            DCPS normally waits for a Raw TCP/IP, LAT or serialB            printer to be idle before sending a new job to it. ThisC            is especially important in a networked environment where D            a printer can be shared among DCPS queues, LATSYM queues,-            Windows[R] and UNIX[R] hosts, etc.a  >            Prior to version V1.2, DCPS used an aggressive syn-?            chronization sequence to gain control of a printer'sn@            PostScript interpreter. This scheme worked well in an@            all-DCPS environment, but in a multi-host environment?            it sometimes caused print jobs from other systems tor!            terminate prematurely.   A            If you rely on DCPS's earlier behavior to abort errant D            PostScript jobs on one queue by starting a job on anotherE            queue, you can define the following system logical name to 0            restore the more aggressive behavior:  X                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_INTERRUPT_WHEN_BUSY TRUE  C      3.5.3 Suppressing PostScript Synchronization When a Job Starts   C            DCPS begins a job on a Raw TCP/IP, LAT or serial printerd>            by synchronizing with its PostScript interpreter toC            ensure that the interpreter is ready to accept commands.u@            However, some PostScript printers are not always in aE            state where they can recognize the synchronization control @            characters. In particular, some printers that supportA            additional printer languages like PCL do not correctly D            respond to this sequence under certain circumstances. ForC            example, the DEClaser 3500, when in PS/PCL sensing mode,mD            inadvertently switches to PCL mode when DCPS sends a CtrlD            /T character to its serial port. The printer, then out of  -      3-20 Creating and Modifying Print Queuesp t  b            F               the PostScript mode, does not respond, and the print job1               gets stuck in the "starting" state.   F               You can define a logical name to cause the DCPS symbiontC               to avoid using its usual synchronization sequence for_G               printers that use a Raw TCP/IP, LAT or serial connection. @               The logical name has no effect when using printers@               connected via other means. Refer to Chapter 10 for/               printer-specific recommendations.   H               To disable the synchronization sequence for a print queue,(               use the following command:  O                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_NO_SYNC TRUE.  F               The absence of the synchronization step is not generallyC               a problem for most modern serially-connected printersPE               because such printers use flow control to hold off data H               when the interpreter is not ready to accept data. However,E               the printer is more vulnerable to printing "garbage" or H               losing jobs if communication parameters, such as baud rateD               and stop bits, are not set correctly. Depending on theE               configuration, it's also possible to lose print jobs ifeF               the printer data cable is disconnected or the printer is               powered off.  8         3.5.4 Purging the Symbiont Process's Working Set  C               The DCPS symbiont purges its working set after it has H               been idle for a period of time in order to conserve systemG               resources. The time delay is intended to help prevent theoF               system from thrashing by keeping the program in physical6               memory while more work is apt to arrive.  D               By default, DCPS waits ten (10) minutes after becomingH               idle before purging its working set. You can increase thisH               value, if desired, by defining a system-wide logical name:  R                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$PURGE_TIME "0 hh:mm:ss.00"  >               where hh:mm:ss.00 is an OpenVMS delta-time valueE               specifying the desired time delay. If the value is lessTC               than the default of ten seconds, the default is used.     H                                 Creating and Modifying Print Queues 3-21 w               +      3.5.5 Enabling Spooling for LPD Queues   @            Remote LPD queues, and some LPD printers, require theC            size of the job to be known before the job is sent. DCPS.@            can produce a temporary spool file so the size can beA            determined. By default, DCPS LPD jobs are not spooled,aA            so specific action must be taken to send DCPS LPD jobss@            to remote LPD queues or LPD printers that require it.@            Spooling can be specified for the whole system or for7            individual queues by defining logical names.c  @            Because spooling requires an extra step to create theD            temporary spool file, you should enable spooling only forC            printers that require it. Common reasons to use spooling             are:P  ?               You are printing to a remote LPD queue on anotherw               system. B               Your printer does not print anything when using DCPS#               LPD without spooling.y<               Your printer is a larger multi-function deviceA               that does not work with DCPS Raw TCP or LPD withoutr               spooling.y  C            To turn on spooling, define one of the following logicalC?            names. Neither of these logical names are defined byh            default.               o  DCPS$SPOOL  D               When defined, all LPD jobs from all queues will createE               a temporary spool file before being sent to the printer                or remote queue.  #            o  DCPS$queue-name_SPOOLu  B               When defined, LPD jobs from this queue will create aC               temporary spool file before being sent to the printerl               or remote queue.  B            To specify where temporary spool files will be created,C            the following logical name is used. This logical name isC            always defined.  "            o  DCPS$SPOOL_DIRECTORY  -      3-22 Creating and Modifying Print Queuese                 B                  Spool files will be created in this directory andB                  deleted after being sent to the printer or remoteE                  queue. Print jobs are not spooled unless spooling is A                  enabled with one of the two logical names above.E  G                  You will be asked for the location for your DCPS spool H                  directory when installing DCPS if it is not already de-H                  fined. The default location is SYS$COMMON:[DCPS$SPOOL],G                  but you should specify a location on a non-system disk F                  that is available to all queues for which spooling isH                  enabled. This directory is protected such that only theE                  DCPS print symbiont process and privileged users canF&                  view the spool files.  2         3.5.6 Specifying Sheet Size for LPD Queues  N               The logical names DCPS$SHEET_SIZE and DCPS$queue-name_SHEET_SIZEE               are used to tell DCPS about the printer's default paper_C               size. The system-wide logical name DCPS$SHEET_SIZE is D               defined in DCPS$STARTUP.COM to be LETTER. If you use aC               different paper size at your site, change or redefinerE               the value of this logical name. You can also change thenE               value for individual queues by defining a value for thet8               queue-specific DCPS$queue-name_SHEET_SIZE.  B               For example, to specify A4 as the default paper size               system-wide:  B                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$SHEET_SIZE                   A4  D               To specify LEGAL as the default paper size for a queue               called LAWYERS:   P                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$LAWYERS_SHEET_SIZE LEGAL  F               The definition of the DCPS$SHEET_SIZE logical name is inH               the new version of DCPS$STARTUP.TEMPLATE shipped with thisD               version of DCPS. You should copy DCPS$STARTUP.TEMPLATEG               to .COM and edit the resulting DCPS$STARTUP.COM with youri$               site-specific changes.  C               Note the following behavior concerning the sheet sizen               logical name:r  F               o  If neither the system-wide nor queue-specific versionD                  of this logical name are defined, the default sheet'                  size is set to LETTER.q  H                                 Creating and Modifying Print Queues 3-23 u               A            o  If the sheet size is defined to be a size that does E               not exist on the printer, the job will not print and no -               error message will be received.   E            o  The logical name should be used for LPD queues only. Itx5               is not supported for other queue types.L  1      3.5.7 Specifying Product Name for LPD Queues   A            Most DCPS LPD queues will use printers unrecognized by @            DCPS, so most queues will not require the use of thisD            logical name. However, you might want to use LPD to printA            to a DCPS-supported printer. For example, the HP Color C            LaserJet 8500 and 8550, DIGITAL Colorwriter LSR 2000 and D            DEClaser 3500 are not supported by DCPS with any other IP2            protocol, but can now be used with LPD.  D            If you have a DCPS-supported printer that you want to useE            with LPD, you must define the DCPS$queue-name_PRODUCT_NAME <            logical name to be the PostScript product name of>            the printer as shown in Table 3-4. You must specify@            the product name exactly, including spacing. However,:            capitalization and trailing spaces are ignored.  C               ________________________Note ________________________   A               Not all printers listed in Table 3-4 are officiallye                supported by DCPS.  C               _____________________________________________________I  =            For example, to set up a queue called MFP to an HP C            LaserJet 9000 MFP printer, you can use commands such as:_  G                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$MFP_PRODUCT_NAME - (                _$ "HP LaserJet 9000 MFP"G                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$MFP_PRODUCT_NAME -.(                _$ "hp LaserJet 9000 mfp"  C            If you specify "HPGENERIC", your printer will be treateda?            as an "HP Generic" printer. If you specify any otherlD            string, your printer will be treated as an "unrecognized"            printer.     -      3-24 Creating and Modifying Print Queues_ T  _            H               Table_3-4_Recognized_Product_Names________________________                 Colormate PS                 Colormate PS40                 Colormate PS80                 Colorwriter 1000  "               Colorwriter LSR 2000  '               Compaq Laser Printer LN16n  '               Compaq Laser Printer LN32t  (               Compaq Laser Printer LNC02  (               Compaq Laser Printer LNM40  !               DECcolorwriter 1000_                 DEClaser 1150t                 DEClaser 1152/                 DEClaser 2150t                 DEClaser 2250l                 DEClaser 3250                  DEClaser 3500                  DEClaser 5100s  (               DIGITAL Laser Printer LN15  (               DIGITAL Laser Printer LN20  (               DIGITAL Laser Printer LN40  )               DIGITAL Laser Printer LNC02h  (               GENICOM Intelliprint cL160  (               GENICOM Intelliprint mL260  (               GENICOM Intelliprint mL402  (               GENICOM Intelliprint mL450                 GENICOM LN21                 GENICOM LN28                 GENICOM LN45                 GENICOM LNM40n  $               GENICOM microLaser 170  H                                 Creating and Modifying Print Queues 3-25 a  o            E            Table_3-4_(Cont.)_Recognized_Product_Names________________P  !            GENICOM microLaser 210f  !            GENICOM microLaser 280   !            GENICOM microLaser 320.  !            GENICOM microLaser 401p              HP 9085mfp   !            HP Color LaserJet 2500o  (            HP Color LaserJet 2550 Series  !            HP Color LaserJet 3000   !            HP Color LaserJet 3700n  !            HP Color LaserJet 3800T  !            HP Color LaserJet 4500c  !            HP Color LaserJet 4550h  !            HP Color LaserJet 4600n  !            HP Color LaserJet 4610   !            HP Color LaserJet 4650o  !            HP Color LaserJet 4700   $            HP Color LaserJet 4730mfp  !            HP Color LaserJet 5500   !            HP Color LaserJet 5550m  !            HP Color LaserJet 8500p  !            HP Color LaserJet 8550r  !            HP Color LaserJet 9500i  %            HP Color LaserJet 9500 MFPt  "            HP LaserJet 1300 Series  "            HP LaserJet 1320 Series  "            HP LaserJet 2100 Series              HP LaserJet 2200k  "            HP LaserJet 2300 series              HP LaserJet 2410q              HP LaserJet 2420   -      3-26 Creating and Modifying Print QueuesT    u            H               Table_3-4_(Cont.)_Recognized_Product_Names________________                 HP LaserJet 2430                  HP LaserJet 4 Plus  %               HP LaserJet 4000 Seriesi  %               HP LaserJet 4050 Seriesa  "               HP LaserJet 4100 MFP  %               HP LaserJet 4100 SeriesL                 HP LaserJet 4200                 HP LaserJet 4200Le                 HP LaserJet 4240                 HP LaserJet 4240Np                 HP LaserJet 4250                 HP LaserJet 4250LL                 HP LaserJet 4300  "               HP LaserJet 4345 MFP                 HP LaserJet 4350                 HP LaserJet 4MLo                 HP LaserJet 4MPt                 HP LaserJet 4PJg                 HP LaserJet 4Si_                 HP LaserJet 4V  %               HP LaserJet 5000 Seriesi  %               HP LaserJet 5100 Series                  HP LaserJet 5200                 HP LaserJet 5200LD                 HP LaserJet 5M                 HP LaserJet 5Si   %               HP LaserJet 8000 Seriesr  %               HP LaserJet 8100 Seriest  %               HP LaserJet 8150 Series   "               HP LaserJet 9000 MFP  H                                 Creating and Modifying Print Queues 3-27 Q  e            E            Table_3-4_(Cont.)_Recognized_Product_Names________________o  "            HP LaserJet 9000 Series               HP LaserJet 9000L MFP              HP LaserJet 9040 MFPu              HP LaserJet 9050p              HP LaserJet 9050 MFPo              HP LaserJet 9055mfp              HP LaserJet 9065mfp              HP LaserJet III              HP LaserJet IIIDa              HP LaserJet IIISi              HP LaserJet IIP  )            Hewlett-Packard LaserJet IIISiu              IBM InfoPrint 32/40              IBM Infoprint 21I              LN17psw              LPS17              LPS17/600              LPS20              LPS20+Q              LPS32              LPS40              LPS40+P              LaserJet 4               LaserJet II              LaserWriter II NT              LaserWriter II NTX               LaserWriter IIf              LaserWriter IIg  #            LaserWriter Personal NTR               LaserWriter Plus   -      3-28 Creating and Modifying Print Queues                  H               Table_3-4_(Cont.)_Recognized_Product_Names________________  !               LaserWriter Pro 600a  !               LaserWriter Pro 630s  !               LaserWriter Pro 810e  $               LaserWriter Select 310  $               LaserWriter Select 320  $               LaserWriter Select 360                 Lexmark C720                 Lexmark C750                 Lexmark C910                  Lexmark Optra C710  (               Lexmark Optra LaserPrinter  "               Lexmark Optra S 1250  "               Lexmark Optra S 1255  "               Lexmark Optra S 1620  "               Lexmark Optra S 1625  "               Lexmark Optra S 1650  "               Lexmark Optra S 1855  "               Lexmark Optra S 2420  "               Lexmark Optra S 2450  "               Lexmark Optra S 2455  #               Lexmark Optra Se 3455i                  Lexmark Optra T610                  Lexmark Optra T612                  Lexmark Optra T614                  Lexmark Optra T616                  Lexmark Optra W810                 Lexmark T520                 Lexmark T522                 Lexmark T620                 Lexmark T622  H                                 Creating and Modifying Print Queues 3-29 i  r            E            Table_3-4_(Cont.)_Recognized_Product_Names________________T              Lexmark W820               Phaser 200e              Phaser 200i              Phaser 220e              Phaser 220i              Phaser 300i              Phaser 4500DP              Phaser 4500No              Phaser 4500Xr              Phaser 6250DP              Phaser 6250DT              Phaser 6250DX              Phaser 6250Nl              Phaser 7300DN              Phaser 7300DT              Phaser 7300DX              Phaser 7300N               Phaser 740g              Phaser 740E              Phaser 740P              Phaser 750DPe              Phaser 750DX               Phaser 750N              Phaser 7750DN              Phaser 7750DX              Phaser 7750GX              Phaser 780GN               Phaser 780N              Phaser 8400DP              Phaser 8400DX  -      3-30 Creating and Modifying Print Queues                  H               Table_3-4_(Cont.)_Recognized_Product_Names________________                 Phaser 8400N                 Phaser 850DP                 Phaser 850DX                 Phaser 850NI                 Phaser III PXi                 ScriptPrinterS  #               Xerox DocuPrint N2025   #               Xerox DocuPrint N2125e  !               Xerox DocuPrint N24a  #               Xerox DocuPrint N2825e  !               Xerox DocuPrint N32s  #               Xerox DocuPrint N3225s  !               Xerox DocuPrint N40e  #               Xerox DocuPrint N4025   #               Xerox DocuPrint N4525d  "               Xerox DocumentCentre                 Xerox WCP 232r                 Xerox WCP 238                  Xerox WCP 245F                 Xerox WCP 255                  Xerox WCP 265                  Xerox WCP 275                  Xerox WCP 35                 Xerox WCP 45                 Xerox WCP 55                 Xerox WCP 65                 Xerox WCP 75  H               Xerox_WCP_90______________________________________________  H                                 Creating and Modifying Print Queues 3-31    l            /      3.5.8 Suppressing Unsolicited PJL MessagesD  D            Printers sometimes send out unsolicited PJL messages thatE            DCPS then displays on the screen as user data. This can befE            caused by previous print jobs from other operating systems A            that change printer characteristics so that all futurenB            jobs send back these messages. While these messages areA            often harmless, sometimes they can interfere with DCPSO)            communications to the printer.s  B            Sometimes, the PJL messages can interfere with DCPS and@            cause the DCPS job to stall and never print. For thisC            reason, you can define two logical names to suppress PJL 5            messages from being sent from the printer.   Z                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_SUPPRESS_PJL_MESSAGES TRUEO                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$SUPPRESS_PJL_MESSAGES TRUE   A            The recommended method for suppressing PJL messages is C            to define the logical name DCPS$queue-name_SUPPRESS_PJL_ C            MESSAGES for each queue having the problem. For example,.=            to suppress PJL messages on a queue called HP4200:o  V                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$HP4200_SUPPRESS_PJL_MESSAGES TRUE  @            You can suppress PJL messages on all DCPS queues with?            the logical name DCPS$SUPPRESS_PJL_MESSAGES, but youaB            should use this logical name with caution. Defining theC            logical name causes DCPS to send the PJL commands to thepC            printer to suppress PJL messages. Since some printers do B            not support PJL commands, defining the logical name forD            such queues will cause the printer to hang and the job toD            stall. If you are unsure if all your printers support PJLC            commands, define the logical name for individual queues.e  >            You do not need to stop and restart the queue after%            defining the logical name.   C               ________________________Note ________________________   =               These new logical names replace the unsupported ;               command procedure UNSOLICITED-PJL-FIX.COM andu-               provide improved functionality.t  C               _____________________________________________________E  -      3-32 Creating and Modifying Print Queuesa    t            8         3.5.9 Suppressing the OPCOM Message USERNOTFOUND  D               If DCPS is running on an OpenVMS cluster that has moreH               than one User Authorization file (UAF), it is possible theG               user submitting a print job does not have a UAF record onnH               the system running the DCPS queue. DCPS prints the job but5               issues a USERNOTFOUND operator message:i  J                   %%%%%%%%%%%  OPCOM   1-JUN-2005 18:43:55.87  %%%%%%%%%%%4                   Message from user SYSTEM on LITERAc                   Queue SHARIE: %DCPS-W-USERNOTFOUND, user name FOO not found, no log files created .                   -RMS-E-RNF, record not found  G               Because the username cannot be found, DCPS cannot performnD               the MESSAGES=KEEP or MESSAGES=PRINT parameter request.  D               To prevent this OPCOM message from being displayed forC               every job, define one of the following logical names,rF               depending on whether you want the message suppressed for,               one print queue or all queues:  [                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_IGNORE_UNKNOWN_USER TRUE P                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$IGNORE_UNKNOWN_USER TRUE  C         3.5.10 Using Old ANSI Translator Page Size for A4 Landscapen  E               All versions of the ANSI translator prior to DCPS V1.1A G               had a problem printing 66 lines of text in landscape mode F               on A4 paper. Certain printers have slightly smaller thanE               average print areas when using A4 paper, which resulted E               in the 66th line being lost or clipped when using printRD               parameters of PAGE_SIZE=A4,PAGE_ORIENTATION=LANDSCAPE.  B               The ANSI translator now correctly prints 66 lines ofB               text in landscape mode on A4 paper. The fix involvedE               changing the vertical spacing of the font used (SGR 15)dE               and correcting the maximum printable area for A4 paper.   @               If you use preprinted forms that depend on the oldD               translator's behavior, you can retain the old behavior.               by defining a DCPS logical name:  [                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_OLD_ANSI_PAGE_SIZES TRUEi    H                                 Creating and Modifying Print Queues 3-33 u  i            "      3.6 Setting Up Generic Queues  E            Generic queues are not associated with a specific printer;mE            rather, they point to the execution queues. Generic queuesoC            can be associated with more than one execution queue and A            can distribute print jobs among queues, or they can beeC            used to associate specific DECprint Supervisor functionsQC            with a print job. Generic queues are optional. Table 3-5n@            describes the parameters that can be used to define a            generic DCPS queue.  E            Table_3-5_Parameter_Values_for_Generic_Queues_____________h  E            Parameter___Value_________________________________________.  1            P1          Name of the generic queue.l@            (required)  In Example 3-4, DRAFT_DOCS is the generic  A                        queue to which users will send print jobs.   B            P2          Name of the execution queue(s) to which theC            (required)  generic queue can send jobs. You must supplyxA                        at least one execution queue name for eacho0                        generic queue definition.  B                        In Example 3-4, the generic queue will sendE                        print jobs to two execution queues: LN03R_TTB4n&                        and LN03R_TTB7.  0            P3          Default PRINT parameters.E            (optional)  In Example 3-4, LAYUP=LPS$SINGLEHOLES provideso  >                        a default layup definition file for the%                        generic queue.a  =            P4          Explicit INITIALIZE /QUEUE qualifiers.             (optional)   E            P5          Setting of the SET VERIFY command. The default E            (optional)__is_SET_NOVERIFY.______________________________   >            Example 3-4 shows how to set up a generic queue forD            printing with a layup definition file. This generic queueD            feeds print jobs to either of two ScriptPrinter execution            queues.  -      3-34 Creating and Modifying Print Queues  a  s            4               Example 3-4 Setting Up a Generic Queue  1               $ @SYS$STARTUP:DCPS$GENERIC_QUEUE -cX                   DRAFT_DOCS -                                 ! P1 - Generic queue name]                   "LN03R_TTB4,LN03R_TTB7" -                    ! P2 - Execution queue name(s) ^                   "LAYUP=LPS$SINGLEHOLES"                      ! P3 - Default queue parameters  7         3.7 Activating Changes to the Queue Definitionse  F               When you create or modify the DCPS$STARTUP.COM file, youC               must activate the changes for the DECprint SupervisortB               to use the new queue definitions. You can wait untilE               you stop and restart the system, or you can execute the 0               DCPS$STARTUP.COM file, as follows:  C               1. Stop the print queues that you modified. If any of C                  the modified queues are running on a multistreamed D                  symbiont, stop all other queues that are using thatA                  same symbiont (see Section 3.5.1.2). To stop the C                  queues, enter the following command for each print                   queue:d  3                      $ STOP /QUEUE /NEXT queue-namei  D               2. Edit the system startup file SYS$MANAGER:SYSTARTUP_L                  VMS.COM to include a command that invokes DCPS$STARTUP.COM.  E                  Look for the following command in the system startup.                  file:  0                      $ @SYS$STARTUP:DCPS$STARTUP  G                  If this command is not in the system startup file, addl>                  it to the file. Use the following guidelines:  G                  o  If you are using a printer with TCP/IP, add the newn1                     line after TCP/IP is started.   D                  o  If you are using a printer with LAT, add the new.                     line after LAT is started.  F                  o  If you are using a printer with AppleTalk, add the8                     new line after AppleTalk is started.  G                  o  If you are using a PrintServer printer with DECnet, @                     add the new line after the command to invokeF                     STARTNET.COM. PrintServer Software must be runningG                     on the PrintServer host system before you start the                      queues.Q  H                                 Creating and Modifying Print Queues 3-35 l  c            A               o  If the system startup file includes a command toY                  start@                  LPS$STARTUP.COM, replace it with the command to(                  start DCPS$STARTUP.COM.  E               o  If you are upgrading from DECprint Printing ServicesiC                  (CPS), delete the command to start CPS$STARTUP.COMu.                  from the system startup file.  7            3. Execute the printer startup command file:   -                   $ @SYS$STARTUP:DCPS$STARTUPx  E            If the queues are on an OpenVMS Cluster system, you shouldmC            execute the command above from all nodes in the cluster.a  >            The print queues are started by the printer startupC            command file. See Section 3.8 for information on testing &            your new queue definitions.  $      3.8 Testing the Printing System  C               ________________________Note ________________________   @               Execution of the IVP (@SYS$TEST:DCPS$IVP) does not&               cause anything to print.  C               _____________________________________________________   E            You can test the printing system by printing the IVP filesoB            from SYS$COMMON:[SYSTEST.DCPS]. The IVP files representE            the different data types that DCPS supports. The IVP filesi#            are listed in Table 3-6.d  E            Table_3-6_IVP_Files_with_Different_Data_Types_____________   E            File_Name_____________File_Type___________________________   ,            DCPS$IVP_ANSI.DAT     ASCII files  -            DCPS$IVP_LIST.DAT     Simple ASCIIs  2            DCPS$IVP_PCL.DAT      PCL Level 4 files  1            DCPS$IVP_POST.DAT     PostScript filesi  1            DCPS$IVP_PROPRINTER.DAProprinter filesa  -      3-36 Creating and Modifying Print Queues  f  t            H               Table_3-6_(Cont.)_IVP_Files_with_Different_Data_Types_____  H               File_Name_____________File_Type___________________________  /               DCPS$IVP_REGIS.DAT    ReGIS filesr  H               DCPS$IVP_TEK4014.DAT__Tektronix_4010/4014_files___________  H               DCPS can automatically detect the file's data type. You doH               not have to specify the data type on the command line. ForA               example, you can enter the following PRINT command:   H                   $ PRINT/QUEUE=queue-name/NOTIFY DCPS$IVP_data-type.DAT  F               If the print queue is linked to a specific data type, orG               you are testing the LIST data type, specify the data typer               of the file.  H               For example, to print DCPS$IVP_POST.DAT, use the following               PRINT command:  -                   $ PRINT /QUEUE=queue-name -p?                   _$ /PARAMETERS=DATA_TYPE=POSTSCRIPT /NOTIFY - ?                   _$ SYS$COMMON:[SYSTEST.DCPS]DCPS$IVP_POST.DATo                                          H                                 Creating and Modifying Print Queues 3-37                       H                                                                        4H         ________________________________________________________________  H                                  Providing Automatic Data Type Detection      F               DECprint Supervisor software can determine the data typeF               of the file to be printed. This chapter explains how youF               can customize your printing system to print the types of-               files that users need to print.,  4         4.1 How DCPS Automatically Detects Data Type  D               If a user does not specify the data type and the printH               queue has no default data type, DCPS examines each file inH               the print job. DCPS attempts to determine the data type ofF               the file from instructions in the file, or from the file               name extension.t  G               If DECprint Supervisor software cannot determine the file3G               data type by any of these methods, the file is printed asmF               a text file. Text files are handled as ANSI files unlessE               another default text file data type (PCL or Proprinter)aE               has been defined by the system manager for the queue ord               for the system.e  C               When files are treated as text files in this way, thetE               DECprint Supervisor software can detect PostScript dataeF               after the text, so a file that starts with text followed0               by PostScript is printed properly.  G               The process of determining the file data type is repeatedaE               for each file in a print job, so a single print job cany/               contain different types of files.h              H                              Providing Automatic Data Type Detection 4-1 r               1      4.2 Specifying Automatic Data Type Detectione  ?            You can control how the DECprint Supervisor software A            determines the data type of files as they are printed.N            You can:5  D            o  Link file extensions with data types. You can edit theC               default file extension data file to add or modify the D               standard list of file extensions and the data types to;               which they are associated. See Section 4.2.1.   C            o  Specify the default data type to use when DCPS cannotsB               determine the file's data type in any other way. YouD               can specify a system wide default and a queue-specific8               default text data type. See Section 4.2.2.  @            If necessary, you can create generic queues that haveC            default data types, so that every file sent to the queue A            is assumed to be that data type. Only the user's PRINTl?            parameters can override the queue default data type.u  2      4.2.1 Linking File Extensions with Data Types  ?            The DECprint Supervisor software uses a data file toe@            link file extensions to data types. Use the followingA            procedure to create a local data file of your system'st9            file extensions and the associated data types.n  B            1. If your system does not have a customized data file,C               use the sample file supplied with your software. Copy D               the file, and change the file's extension, as shown in$               the following command:                 $ COPYJ               _From: SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT  G               _To: SYS$COMMON:[SYSLIB]DCPS$FILE_EXTENSION_DATA_TYPE.DAT   C               If the .DAT file is not in variable or stream format, D               DCPS cannot read it when the queues are started. OPCOMA               will report the error, and the symbiont process may A               be terminated. You should save the .DAT file in the ?               appropriate format, and then restart the printingo5               system using the DCPS$STARTUP.COM file.   0      4-2 Providing Automatic Data Type Detection m  i            G               2. Edit the file. The file has the default file extensiont4                  and data types listed. For example:                    POSTSCRIPT:                          EPS                          EPSFo                          POST                           PS                           ;  F                  The example shows that files with extensions of .EPS,H                  .EPSF, .POST, and .PS are linked to the PostScript data                  type.  B                  Add extensions that are specific to your site, or@                  modify any that have a different local meaning.  B                  You can specify any valid DATA_TYPE value, exceptF                  AUTOMATIC. Do not abbreviate the data type names. The+                  valid data type names are:i                       ANSI                     ASCIIi                     DDIF                     LIST                     PCL/                     POSTSCRIPT                     PROPRINTER                     REGISt                     TEK4014p  E         4.2.2 Specifying Default Data Types for the System and Queuesn  F               You can specify a system wide default text data type andF               queue-specific default text data types. If DCPS softwareF               cannot determine the data type, the file is processed as0               the default data type you specify.  G               The factory default data type is ANSI. If users regularly @               print PCL or Proprinter text files instead of ANSIC               files, you should change the default from ANSI to PCLs               or Proprinter.  @               Define one or both of the following logical names:  B               o  DCPS$DEFAULT_TRANSLATOR specifies the system wide(                  default text data type.  H                              Providing Automatic Data Type Detection 4-3 x               E               To define a system wide default text data type, use they                following command:  N               $ DEFINE/SYSTEM/EXECUTIVE DCPS$DEFAULT_TRANSLATOR text_data_type  D            o  DCPS$queuename_DEFAULT_TRANSLATOR specifies the queue-)               specific default data type.t  D               To define a queue-specific default text data type, use$               the following command:  X               $ DEFINE/SYSTEM/EXECUTIVE DCPS$queuename_DEFAULT_TRANSLATOR text-data-type  3            Valid values for the text-data-type are:o               o  ANSI (the default)              o  PCLf              o  PROPRINTER  0            Do not abbreviate the data type name.  ?            If the system wide data type differs from the queue-wA            specific data type, the queue-specific data type takest            precedence.  A            The queue-specific logical name is useful when a queue @            is used by PATHWORKS clients. Text files printed fromD            PCs may be PCL or Proprinter files. The following exampleE            specifies the PCL data type for the queue named PATHWORKS:p  J            $ DEFINE/SYSTEM/EXECUTIVE DCPS$PATHWORKS_DEFAULT_TRANSLATOR PCL  A            The DECprint Supervisor software attempts to determineSA            the file data type for each file sent to the PATHWORKS D            queue. If a file data type cannot be determined, the fileD            is processed as a PCL file. If the file contains PCL text:            followed by PostScript, it is printed properly.  0      4.2.3 How Users Control Data Type Detection  =            Users control the way print jobs are processed forw7            automatic data type detection by specifying:   D            o  The data type with the /PARAMETERS=DATA_TYPE qualifier#               in the PRINT command.i  0      4-4 Providing Automatic Data Type Detection u  o            A                  This qualifier overrides the automatic data typeeG                  detection process; only the presence of DDIF file tagscD                  can prevent the file from being processed using theG                  translator associated with the specified data type. IfiH                  the file contains DDIF tags and is explicitly specifiedC                  as another data type, the file is not printed. The G                  following error message is displayed, and the DECprint H                  Supervisor software continues with the next file in the$                  print job (if any):  H                  INVDDIFDATA, Invalid DDIF data, flushing to end of file  G               o  Automatic data type detection with the following PRINTo                  parameter:a  A                  /PARAMETERS=DATA_TYPE=AUTOMATIC[=text-data-type]   F                  Users can specify the /PARAMETERS=DATA_TYPE=AUTOMATICH                  qualifier to specify automatic data type detection (forF                  example, if the print queue has a default data type).  G                  If the user includes the default text data type (text-rE                  data-type) in the DATA_TYPE=AUTOMATIC parameter, the/C                  DECprint Supervisor software assumes the specified E                  data type if the data type of a print file cannot be                   determined.  B                  The text-data-type value is optional; the defaultD                  is ANSI. Users should include this value to specifyC                  another text data type, such as PCL or Proprinter..  G                  The DECprint Supervisor software can print a file that C                  starts with the default text data type followed bywF                  PostScript data. If a user needs to print a file thatF                  begins with PCL text followed by PostScript data, theF                  user can explicitly set the default text data type to:                  be PCL using the following PRINT command:  T                  $ PRINT/QUEUE=PS20$A10 PIC.MSG/PARAMETERS=(DATA_TYPE=AUTOMATIC=PCL)  D                  This feature is useful for printing files generatedB                  by electronic messaging systems. For example, youF                  can print a PostScript file that was sent to you fromE                  someone using the messaging system, if the resultingi@                  file contains a text message header followed by!                  PostScript data.   H                              Providing Automatic Data Type Detection 4-5 t                     H                                                                        5H         ________________________________________________________________  H                                 Manipulating Print Jobs and Print Queues      A               This chapter describes the commands for maintaining E               and controlling print jobs, print queues, and the queue                manager.  D               Some of the commands described in this chapter require               privileges.y  '         5.1 Displaying Print Job Statusu  F               You can use the SHOW ENTRY command to display the statusD               of a print job. You do not need privileges to use thisH               command to display your own print jobs, but privileges are<               required to display another user's print jobs.  B               The SHOW ENTRY command lists all your print jobs. ToA               display the status of another user's print job, you D               must supply the job number with the SHOW ENTRY commandD               or specify the user using the /USER qualifier. You canH               display the job numbers for all print jobs in a designatedB               queue using the SHOW QUEUE /ALL command, as follows:  (               $ SHOW QUEUE /ALL PS40$A12  Y                   Printer queue PS40$A12, busy, on LEVEL::PS40, mounted form DCPS$DEFAULTl!                   (stock=DEFAULT)i  F                     Entry  Jobname         Username     Blocks  StatusF                     -----  -------         --------     ------  ------H                      304      MEMO         MSMITH            5  Printing  A               You can use the SHOW ENTRY /FULL command to displaytB               information about a specific print job. For example:      H                             Manipulating Print Jobs and Print Queues 5-1 r  i            !            $ SHOW ENTRY 304 /FULLr  A                Entry  Jobname         Username     Blocks  StatusEA                -----  -------         --------     ------  ------ C                  304  MEMO            MSMITH            5  Printings4                       On busy printer queue PS40$A121                       Submitted 14-JUN-2005 10:41 @                       /FORM=DCPS$DEFAULT (stock=DEFAULT) /NOTIFY#                       /PRIORITY=100 C                       File: _$1$DUA10:[MSMITH]MEMO.TXT;1 (printing)0  C               ________________________Note ________________________   B               Print job status may be shown as "Printing" when the?               file has not yet actually started printing on the1               printer.  C               _____________________________________________________         5.2 Deleting a Print Job1  =            You can delete a print job using the DELETE /ENTRYt<            command. You can delete you own print job withoutB            privileges. However, you must have privileges to delete%            another user's print jobs.o  D            The DELETE /ENTRY command accepts the print job number as$            an argument. For example:  "                $ DELETE /ENTRY=569  ?            This command deletes print job 569. The system sendsoA            messages indicating the successful print job deletion.   B            The print job is terminated in a method that depends on@            the status of the print job when you issue the DELETE            /ENTRY command.                1      5-2 Manipulating Print Jobs and Print Queues  o  a          H               __________________________________________________________!               If you issue DELETEJH               /ENTRY_._._._____________DCPS_software_._._.______________  G               When the print job is    May take several seconds to stopeH               printing                 the print job. The printer printsD                                        data in its buffers, plus anyE                                        required job trailer pages and G                                        job log pages. During this time,MH                                        a SHOW QUEUE command displays the@                                        job's status as Aborting.  7               Before a connection      Prints no pages. #               is established with a                network printera  G               After the connection is  Prints the job trailer page withrD               established              a message indicating the factF                                        that you deleted the print job.  E               Before the job burst     May not print the job burst or B               or job flag pages are    job flag page. However, jobD               printed                  trailer and job log pages areH                                        printed if the queue is set up toH               _________________________print_them.______________________  6         5.3 Releasing a Print Job in the Holding State  H               When a print job is in the Holding state, you must releaseG               it for it to print. The user can put a job in the Holding F               state using the PRINT /AFTER or PRINT /HOLD command. TheH               user or system operator can put a print job in the Holding6               state using the SET ENTRY /HOLD command.  E               Use the SET ENTRY /RELEASE command to release the printeC               job to be printed. You must specify the job number inHB               the SET ENTRY command. This command does not requireB               privileges if you are releasing a print job that youC               submitted. Privileges are required to release another                 user's print jobs.                 For example:  *                   $ SET ENTRY /RELEASE 569  E               In this example, print job 569 was in the Holding stater,               and was released for printing.  H                             Manipulating Print Jobs and Print Queues 5-3                       5.4 Requeuing Print Jobs   E            You can change the print queue for one or more print jobs, 2            as described in the following sections.  '      5.4.1 Requeuing Pending Print Jobs   D            You can requeue a print job that has not started printingD            using the SET ENTRY /REQUEUE command. Without privileges,>            you can requeue your jobs. With privileges, you can?            requeue any print job that has not started printing.uB            You must supply the job entry number with the SET ENTRYC            command. The /REQUEUE qualifier requires the name of thee(            new print queue. For example:  9                $ SET ENTRY /REQUEUE=POSTSCRIPT$DUPLEX 596W  @            This command changes the print queue for job 596. The<            print job is sent to the POSTSCRIPT$DUPLEX queue.  @      5.4.2 Requeuing the Currently Printing Job to Another Queue  E            When a printer problem prevents completion of the printing E            job, you can requeue the print job to another printer. Use D            the STOP /QUEUE /REQUEUE command to send the print job toB            another print queue. You supply both the old queue name@            and the new queue name for this command. For example:  J                $ STOP /QUEUE /REQUEUE=POSTSCRIPT$DUPLEX POSTSCRIPT$SIMPLEX  D            In this example, the print job that is currently printing            on the queue K            POSTSCRIPT$SIMPLEX is stopped and requeued to POSTSCRIPT$DUPLEX.rD            The POSTSCRIPT$SIMPLEX queue is not stopped and continues3            with printing the next job in the queue.g  =      5.4.3 Requeuing Current and Future Print Jobs in a Queuet  ?            The ASSIGN /MERGE command allows you to specify thatWA            all print jobs in a certain queue, and those submitted A            later for that queue, are to be sent to another queue. B            The ASSIGN /MERGE command requires privileges. You mustD            supply the old queue name and the new queue name. Use the            following procedure:   ;            1. Use the STOP /QUEUE /NEXT command to stop the @               malfunctioning print queue after the current print               job has finished.   1      5-4 Manipulating Print Jobs and Print Queues                  D               2. Use the STOP /QUEUE /REQUEUE command to requeue the9                  currently printing job to the new queue.a  G               3. Use the ASSIGN /MERGE command to cause all pending and ?                  future print jobs to be requeued. For example:g  8                      $ STOP /QUEUE /NEXT PRINTER$NOTABLEH                      $ STOP /QUEUE /REQUEUE=PRINTER$ABLE PRINTER$NOTABLEA                      $ ASSIGN /MERGE PRINTER$ABLE PRINTER$NOTABLEh  3         5.5 Modifying the Attributes of a Print Job   ?               The SET ENTRY command allows a user to modify theeD               attributes of a pending print job. You cannot modify aH               print job that has begun printing. If you have privileges,C               you can modify the attributes of print jobs submitted2E               by other users. The SET ENTRY command requires that younB               specify the job number and allows you to specify oneC               or more PRINT command qualifiers, which are listed ine&               Appendix A. For example:  H                   $ SET ENTRY 596 /PARAMETERS=PAGE_ORIENTATION=LANDSCAPE  H               This example changes a print job from portrait orientationA               to landscape orientation. If the original PRINT job5C               contained any PRINT parameters, you must specify them_E               all again when you modify any print parameters with the H               SET ENTRY /PARAMETERS command. If you do not respecify theG               PRINT parameters, the print job will be printed using thedH               default parameter values for those not included in the SET               ENTRY command.           5.6 Displaying a Queue  F               You can display a print queue, including its status, itsH               attributes and the print jobs in the queue, using the SHOWF               QUEUE command. This command does not require privileges,H               unless you wish to view queue security information or view2               print jobs belonging to other users.  D               To display a specific queue, supply the queue name. ToE               display all of the queues, omit the queue name from the B               SHOW QUEUE command. Use the commands in Table 5-1 to/               display information about queues.q  H                             Manipulating Print Jobs and Print Queues 5-5 S  E            E            Table_5-1_Commands_to_Display_Queues______________________s  E            To_list:___________________Enter:_________________________m  0            The name and description   SHOW QUEUE#            of every print and batch             queue  @            The names of all the       SHOW QUEUE /DEVICE=PRINTER            print queues   5            All the jobs in all the    SHOW QUEUE /ALLc            queuess  @            All the jobs in the        SHOW QUEUE /ALL queue-name            specified queue  6            The attributes of all the  SHOW QUEUE /FULL            queues   A            The attributes of a        SHOW QUEUE /FULL queue-name E            certain_queue_____________________________________________n        5.7 Pausing a Queue  A            Use the STOP /QUEUE command to pause a queue. You mustn@            have privileges and supply the queue name to the STOP            /QUEUE command.  B            You can pause the queue after the current print job hasA            completed by using the STOP /QUEUE /NEXT command. Thisr@            allows the current job to complete before pausing the            queue. For example:  (                $ STOP /QUEUE /NEXT PS$A4  D            This command pauses the queue PS$A4 after the current job"            has completed printing.  D            If it is necessary to pause the queue without waiting forB            the current job to complete, use the STOP /QUEUE /RESET             command. For example:  )                $ STOP /QUEUE /RESET PS$A4e  A            This command pauses the queue PS$A4 and printing stopsc            immediately.   1      5-6 Manipulating Print Jobs and Print Queuesi o  b                F                 ________________________Note  ________________________  @                 When communications problems arise with a serialB                 or raw TCP/IP interconnect, the symbiont will keepB                 listening for up to 4 minutes before disconnectingC                 from the printer. Therefore, under some conditions, C                 the device is not released immediately after a STOPi0                 /QUEUE /RESET command is issued.  E                 _____________________________________________________n  =               See Appendix A for more STOP /QUEUE qualifiers.a           5.8 Starting a Queue  H               Use the START /QUEUE command to restart a print queue thatG               has been paused with the STOP /QUEUE command. If you makenG               changes to a print queue in DCPS$STARTUP.COM, restart the H               queue by executing the DCPS$STARTUP.COM file, as described               in Section 3.7._  C               For example, to restart print queue PS40$A15, use theO                following command:  )                   $ START /QUEUE PS40$A15A  F               If you interrupt a printing job when you stop the queue,@               the print job restarts when you restart the queue.  E               The logical name, DCPS$queuename_PID, is defined by theiG               symbiont when it starts executing. This allows the system,H               manager to determine which symbiont is assigned to a givenG               queue, and is especially useful when using multi-streamed=+               symbionts. See Section 3.5.1.o  F                 ________________________Note  ________________________  ?                 When a DCPS queue is started, the symbiont doesp?                 not immediately attempt to make a connection toeA                 the printer, to minimize the possibility that thepD                 queue will not start. This is particularly importantC                 while starting queues at system boot time, to avoidCC                 introducing delays or errors into the boot process.MC                 It is not until DCPS starts processing a job from a   H                             Manipulating Print Jobs and Print Queues 5-7 6  t            A               queue that DCPS determines the state of the printerp.               and its associated interconnect.  C               _____________________________________________________w  ,      5.9 Modifying the Attributes of a Queue  ?            You can temporarily modify the attributes of a print E            queue with the SET QUEUE command. When the printing system B            is restarted, the queue attributes you set with the SETD            QUEUE command are lost. To permanently modify print queue6            attributes, edit the DCPS$STARTUP.COM file.  @            The qualifiers to the SET QUEUE command are listed inC            Appendix A. Note that some print queue attributes cannotN.            be set using the SET QUEUE command.  >            The following command limits the print jobs for the:            PS$DRAFT queue to those of 1000 blocks or less.  5                $ SET QUEUE PS$DRAFT /BLOCK_LIMIT=1000e  E            The SET QUEUE command requires privileges; you must supply 9            the queue name and the appropriate qualifiers.e  3      5.10 Preventing Users from Printing to a Queue   @            Use the SET QUEUE /CLOSE command to close a queue andA            prevent users from submitting print jobs to the queue.TC            This command requires privileges and you must supply the #            queue name. For example:   '                $ SET QUEUE /CLOSE PS$A4L  B            After you enter this command, the PS$A4 queue is closedE            and users cannot submit print jobs to the queue. The print B            jobs that are currently in the queue are completed. You@            can open the print queue using the following command:  &                $ SET QUEUE /OPEN PS$A4          1      5-8 Manipulating Print Jobs and Print Queuese 4  o                     5.11 Deleting a Queue   B               You can delete a print queue using the DELETE /QUEUEE               command. This command requires privileges. Follow these +               steps to delete a DCPS queue:g  H               1. Make sure that there are no generic queues running thatE                  are associated with the queue that you are deleting, C                  by displaying the queue using the SHOW QUEUE /FULLeE                  command. If there are generic queues associated with <                  the queue, delete the generic queues first.  E               2. Pause the queue using the STOP /QUEUE /NEXT command. H                  Wait for the printing to stop on the printer before you"                  delete the queue.  C               3. Requeue all the print jobs in the queue and future A                  print jobs for the queue using the ASSIGN /MERGEs-                  command (see Section 5.4.3).d  G               4. Delete the queue with the DELETE /QUEUE command. EnterMC                  the queue name as an argument to this command. For G                  example, the following command deletes the queue PS$A4 D                  and any print jobs that were pending in that queue.  *                      $ DELETE /QUEUE PS$A4  H               Remember to modify the DCPS$STARTUP.COM file to delete theG               queue permanently. Otherwise, when the printing system is D               restarted, the print queue you deleted will come back.  *         5.12 Responding to a Stalled Queue  @               Printers are reported as Stalled when the DECprintF               Supervisor does not receive information from the printerA               within a specified amount of time. When the stalledRA               timeout value is exceeded, the following message iss               displayed:  A                   PRINTERSTALLED, Printer printer-name is stalled   @               You can alter the stalled printer timeout value be!               defining a logical:P  W                   $ DEFINE /SYSTEM /EXECUTIVE DCPS$queuename_STALL_TIME "0 hh:mm:ss.00"   >               where hh:mm:ss.00 is an OpenVMS delta-time value0               specifying the desired time delay.  H                             Manipulating Print Jobs and Print Queues 5-9                 @            The default stalled timeout value is four minutes. HP@            recommends that you do not change this timeout value.  B            When you receive a message that the printer is stalled,C            you must determine if action is required. If the stalled >            message came from a networked printer (for example,?            a PrintServer printer), the stalled message probablyh@            indicates that a long time has passed between networkA            communications and therefore you can safely ignore theo            stalled messages.  C            But if the stalled message follows other printer-relatednB            messages, they may indicate another reason for the longE            delay. The printer might be out of paper, or it might have A            a paper jam. Therefore, when a print queue is stalled, C            you should check your OPCOM messages to see if a printer E            condition was previously reported. Refer to Chapter 11 fora            more information.  A            DCPS may also temporarily define a system-wide logicaltA            giving some indication of why the queue is stalled. TotE            examine this logical, execute the following command on theiD            system where the execution queue is running. If the queueC            is on an OpenVMS Cluster, be sure to use the appropriateI            cluster member.  4                $ SHOW LOGICAL DCPS$queuename_STALLED  1      5.13 Stopping and Starting the Queue Manager   D            To stop and start all the queuing activity on the system,@            stop and start the queue manager. System shutdown andE            startup procedures perform these operations automatically. C            The commands to stop and start the queue manager requirei            privileges.  =            You can stop the queue manager using the following_            command:   .                $ STOP /QUEUE /MANAGER /CLUSTER  C            When you are ready to start the queue manager, enter theA            following command:   &                $ START /QUEUE /MANAGER  2      5-10 Manipulating Print Jobs and Print Queues a                     H                                                                        6H         ________________________________________________________________  H                              Specifying Separation, Log, and Error Pages      &         6.1 What Are Separation Pages?  B               Separation pages are sheets that show where a user'sD               print job or each file in a print job begins and ends.'               Separation pages include:   F               o  Burst pages - printed at the beginning of a print job                  or file.   H               o  Flag pages - printed at the beginning of a print job or                  file.  E               o  Trailer pages - printed at the end of a print job orh                  file.  E               A job flag page looks like a job burst page without the,E               border around the page. A job trailer page looks like amD               job flag page with the message "END OF JOB" printed atH               the top and with additional information listed for the jobH               (for example, when it finished, which PRINT qualifiers andE               parameters were used, and how many pages were printed).tF               File separation pages are differentiated from each otherG               in an analagous fashion, and from job separation pages by_E               the presence of file-specific information (for example, H               the file specification, file size, and modification time).  E               You can enable separation pages for print jobs and eachlG               file in a print job. The following sections show you how.z              H                          Specifying Separation, Log, and Error Pages 6-1 ,               &      6.2 Enabling Job Separation Pages  D            Job separation pages keep print jobs separate. Figure 6-1B            shows one type of job separation page-a job burst page.  A            You enable and disable job separation pages by editingaD            the DCPS$STARTUP.COM file; the user cannot override these            settings.  >            Enter the /SEPARATE qualifier to parameter 5 in theD            execution queue entry in DCPS$STARTUP.COM, as shown here:  2                @sys$startup:dcps$execution_queue -M                    DCPS_TTB4 -                    ! P1 - Execution queue nameeD                    "SERIAL/TTB4" -                ! P2 - Device nameR                    DCPS_LIB -                     ! P3 - Logical name for /LIBRARYQ                    "" -                           ! P4 - Default queue parameters 5                    "/SEPARATE=(BURST,NOFLAG,TRAILER)"eQ                                                   ! P5 - Default queue qualifiers               Notes:p  C            o  Job burst pages do not imply job flag pages for DCPS,a@               as is true for some other OpenVMS print symbionts.  >            o  You can use the SET QUEUE command to temporarily8               specify job separation pages. For example:  I                   $ SET QUEUE /SEPARATE=(BURST,NOFLAG,TRAILER) queue-namey  A            o  Job separation pages are not affected by parameterst>               set with the PRINT /PARAMETERS command or by the>               PostScript file being printed. The pages use the@               default PostScript context of the printer, not the(               context of the user's job.  E            o  Even if you disable separation pages, DCPS prints a joboC               trailer page if an error occurs in the print job. TheeD               job trailer page contains messages about the errors in               a print job.          4      6-2 Specifying Separation, Log, and Error Pages                 0         6.2.1 Error Messages on the Trailer Page  @               If the print job contains errors, the trailer pageE               includes messages that can help the user determine whattF               went wrong with the print job. Following are examples of               these messages:e  W                   28-JUN-2005 11:03  %DCPS-I-TRAYSUBST, Output will be delivered to the2+                   only tray on printer-name   U                   28-JUN-2005 11:03  %DCPS-W-INVACC, invalidaccess: Attempt to accesstL                   restricted object or capability - offending command is get  F               These types of messages are also displayed on the user'sH               terminal if /NOTIFY was specified in the PRINT command for               the print job.  H               The following types of messages are not printed on the job               trailer page:s  '               o  Start and end messagesn  H               o  Hardware printer error messages, such as "out of paper"  3               o  Messages related to communications:  G               o  Messages that the software uses to manage resources int                  the printer  +         6.2.2 Suppressing Job Trailer Pages   E               DCPS normally prints a job trailer page if errors occur H               during the job, even if /SEPARATE=TRAILER is not specifiedE               for the queue, as mentioned in sections Section 6.2 andhC               Section 6.2.1. This behavior may be undesireable when.E               printing on expensive media, especially if the reported %               errors are unimportant.i  C               To prevent DCPS from printing job trailers, even when H               errors occur for the job, define the following system-wide               logical:  X                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_SUPPRESS_JOBTRAILER 1  F                 ________________________Note  ________________________  B                 Running DCPS this way makes it much more difficultA                 to diagnose real problems when they arise. If you B                 are getting nuisance error messages, HP recommends  H                          Specifying Separation, Log, and Error Pages 6-3 e  y            A               that you resolve the underlying problem rather thant'               suppressing the messages.   C               _____________________________________________________   A      6.2.3 Specifying a Special Input Tray for Job Burst and Flag             Pages  B            When users print jobs on expensive or special media, itB            may be desirable to print job burst and flag pages fromB            a special input tray. This technique is also useful forB            specifying a different color paper for separating print            jobs.  B            You may specify a special input tray for job flag pages?            and job burst pages. Define a logical name using the             following command:   P                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_SEPARATOR_TRAY n  C            In this command, queue-name is the name of the execution D            queue and n is the PostScript input tray number. The tray@            numbers are specific to your printer model and may beB            listed in your printer owner's manual. This feature mayB            not work with all printers, especially newer models andC            those that do not select input trays with the PostScriptc)            Level 1 setpapertray operator.                                     4      6-4 Specifying Separation, Log, and Error Pages                 C               Table 6-1 shows the values for HP, Compaq and DIGITAL                printers.D    H               Table_6-1_Tray_Number_Values______________________________  H               Printer_______________________Tray____________Tray_Number_  =               HP LaserJet (most models)     tray 1          3S:                                             (multipurpose)  =                                             tray 2          0   =                                             tray 3          1   B                                             tray 4          4 or 5  =                                             tray 5          6   =                                             envelope        6t2                                             feeder  =               Compaq Laser Printer LN16     upper           0   =                                             lower           1   =                                             multipurpose    3i  =               Compaq Laser Printer LN32     multipurpose    0                and LNM40E  =                                             tray 1          1   =                                             tray 2          2a  =                                             tray 3          3f  =                                             tray 4          4r  =                                             tray 5          5f  =                                             envelope        6U2                                             feeder  =               Compaq and DIGITAL Laser      upper           1t               Printer LNC02c  =                                             lower           5_  =               DEClaser 1150 and 1152        multipurpose    0P  =                                             cassette        1   =               DEClaser 2150 and 2250        manual feed     0   =                                             lower           1g  =                                             upper           2i  H                          Specifying Separation, Log, and Error Pages 6-5 i               E            Table_6-1_(Cont.)_Tray_Number_Values______________________   E            Printer_______________________Tray____________Tray_Number_   :                                          envelope        3/                                          feederh  :            DEClaser 3250                 multipurpose    0  :                                          upper           1  :                                          lower           2  :                                          high capacity   3/                                          feederd  :            DEClaser 3500                 upper           0  :                                          lower           2  :                                          multipurpose    3  :            DEClaser 5100                 multipurpose    0  :                                          upper           1  :                                          lower           2  :            DIGITAL Colorwriter 1000      upper           0  :                                          lower           1  :            DIGITAL Colorwriter LSR 2000  upper           1            and 2000[+]  :                                          lower           2  :            DIGITAL Laser Printer LN15    upper           0            and LN15+  :                                          lower           1  :                                          multipurpose    3  :            DIGITAL LN17ps and Laser      main            0            Printer LN17+ps  :                                          multipurpose    1  :                                          lower 1         2  :                                          lower 2         3  :                                          envelope        4/                                          feederE  :            DIGITAL Laser Printer LN20    multipurpose    1  4      6-6 Specifying Separation, Log, and Error Pages b  l            H               Table_6-1_(Cont.)_Tray_Number_Values______________________  H               Printer_______________________Tray____________Tray_Number_  =                                             upper           2   =                                             lower           5   =               DIGITAL Laser Printer LN40    upper           1i  =                                             middle          2   =                                             lower           3_  =                                             LCIT            5   =               DIGITAL PrintServer 17 and    upper           1                17/600  =                                             lower           2o  =               DIGITAL PrintServer 20, 32,   upper           1                32plus and 40e  =                                             lower           2   H               ______________________________LCIT____________3___________  *         6.3 Enabling File Separation Pages  H               File separation pages separate the files in the print job.>               Figure 6-2 shows an example of a file flag page.  H               To enable default file separation pages, do the following:  P               o  For an execution queue, specify /DEFAULT=(file-separation-page)!                  in parameter P5.s  Q               o  For a generic queue, specify the /DEFAULT=(file-separation-page)d!                  in parameter P4.   B               Users can override the default file flag, burst, and>               trailer attributes for a queue by specifying theC               /[NO]FLAG, /[NO]BURST, and /[NO]TRAILER qualifiers inE                the PRINT command.  A               In the following example, each file in the job willED               be preceded by a file flag page and followed by a file               trailer page:   K                   $ PRINT /FLAG=ALL /TRAILER=ALL FILE1.PS,FILE2.PS,FILE3.PS-  H                          Specifying Separation, Log, and Error Pages 6-7 i               C               ________________________Note ________________________   >               If the PAGE_LIMIT parameter is used in the PRINTB               command, or if the print job is terminated, the fileA               flag page and file trailer page may not be printed.   C               _____________________________________________________   3      6.4 Adding a System Message to Separator Pages   B            You can add a system message to the top of job and fileA            burst, flag, and trailer pages for all jobs printed on <            your system. The following example shows you how:  V                $ DEFINE /EXECUTIVE_MODE /SYSTEM PSM$ANNOUNCE "Computer Services Group"  B            The example shows that the logical name PSM$ANNOUNCE is)            now "Computer Services Group"._  C               ________________________Note ________________________n  =               The PSM$ANNOUNCE logical is used by other printr?               symbionts (for example, LATSYM) as well as by the_A               DCPS symbiont. Your definition of PSM$ANNOUNCE will 0               also affect these other symbionts.  C               _____________________________________________________p  %      6.5 Extended File SpecificationsH  B            DCPS provides default support for systems with Extended@            File Specifications, including ODS-5 volumes and deep            directories.   >            Any file in any directory on an ODS-5 volume can be>            printed. Since files on ODS-5 volumes may have longA            directory and file names, the name may be truncated oneE            file separator pages and in the heading when printing withdD            the LIST translator. If the file name is truncated, it is/            so indicated with an ellipsis (...).           4      6-8 Specifying Separation, Log, and Error Pages                 $         6.6 Requesting Job Log Pages  H               A job log page is an optional sheet with information aboutE               the print job and any messages that occurred during thenF               print job. Use the MESSAGES=PRINT parameter in the PRINTD               command to print a job log page. When printed, the jobD               log page precedes the job trailer page. If you are notF               printing job trailer pages, the job log page is the last               page of a job.           6.7 The File Error Page   C               If the software cannot access the print file when the E               print job starts printing, a file error page is printed H               and the software continues with the next file in the print               job (if any).   E               The file error page contains the following information:   %               o  File log page banners  1               o  Client node name and user's name                  o  Job number   G               o  File identification (file name, extension, and versionM                  only)  =               o  File specification (full file specification)e  "               o  The messages area                            H                          Specifying Separation, Log, and Error Pages 6-9 s  u                  H                                                                        7H         ________________________________________________________________  H                      Creating Setup Modules and Device Control Libraries      #         7.1 What Is a Setup Module?   C               A setup module is a file containing instructions thateB               modify the appearance of a print job or redefine the,               instructions in the print job.  D               You can include a setup module in a print job with theE               PRINT command's /SETUP qualifier. The following examplehH               uses a setup module that specifies 600 dots-per-inch (DPI)               resolution:r  I                   $ PRINT /QUEUE=LPS32$2SIDES /SETUP=RES_600X600 IMAGE.PSP  F               You can also implicitly include setup modules in a print<               job through the use of a form (see Chapter 8).  "         7.2 Locating Setup Modules  F               DCPS ships with various setup modules, which are located6               in the following device control library:  )               SYS$LIBRARY:DCPS$DEVCTL.TLB   C               To list the setup modules, use the following command:n  ?                   $ LIBRARY /LIST /TEXT SYS$LIBRARY:DCPS$DEVCTL   @               The list of setup modules displays, similar to the               following:            H                  Creating Setup Modules and Device Control Libraries 7-1 Y  E                            DCW1000_DISPLAY                DCW1000_ENHANCEDh                DCW1000_HIGHRES)                LPS$$APPLE360_INITPSDEVICE )                LPS$$APPLE360_SETINPUTTRAYj                RES_1200X1200                RES_1200X600   C               ________________________Note ________________________e  B               Do not modify any of the setup modules or the device               control library.  C               _____________________________________________________t  D            Some setup modules are created only for certain printers.E            Those setup modules have the printer name as part of theirnD            file name. For instance, the setup module DL3500_RET_DARK5            is intended for the DEClaser 3500 printer.Q  C               ________________________Note ________________________t  A               Do not change the contents of the standard suppliede%               device control library.   C               _____________________________________________________M  (      7.2.1 Locating Custom Setup Modules  <            Custom setup modules go in special device controlB            libraries, which are required to be .TLB (text library)D            files located in SYS$LIBRARY. The following command listsA            all of the text libraries in SYS$LIBRARY. To determine5D            what subset of these are special device control librariesA            used with DCPS, correlate the .TLB file names with theaA            libraries and library search lists associated with thelB            /LIBRARY qualifier for your system's DCPS print queues.  ,                $ DIRECTORY SYS$LIBRARY:*.TLB            <      7-2 Creating Setup Modules and Device Control Libraries                 7         7.2.2 Displaying the Contents of a Setup ModuleX  F               To see the instructions that a setup module contains, do               the following:  A               1. Extract the setup module from the device controleB                  library. The following example extracts the setupA                  module DI_ON from DCPS$DEVCTL.TLB and renames ito5                  MYSETUP.TXT in the user's directory:R  [                      $ LIBRARY /EXTRACT=DI_ON /OUTPUT=MYSETUP /TEXT SYS$LIBRARY:DCPS$DEVCTLa  G               2. Type or edit the setup module to display its contents:   '                      $ TYPE MYSETUP.TXT$  F                  The setup module DI_ON enables DECimage, and contains,                  the following instructions:                        %! 2                      % ~~~~~~~~~~ DI_on ~~~~~~~~~~;                      statusdict begin false setDECimage end.O                      systemdict /languagelevel known {languagelevel} {1} ifelseeB                      2 ge {currentpagedevice /Install get exec} if:                      statusdict begin true setDECimage end2                      % ~~~~~~~~~~~~~~~~~~~~~~~~~~~  F                 ________________________Note  ________________________  >                 Some setup modules contain escape sequences orA                 graphics, which cannot be displayed when you typeOC                 the file. For such modules, you may wish to use theb;                 DUMP /RECORD command on the extracted file.a  E                 _____________________________________________________e  )         7.3 Creating Custom Setup Modulesl  F               You can create setup modules that affect print jobs withF               different data types. Some setup modules manipulate ANSIF               print jobs, while others affect PostScript jobs. You canA               create setup modules for any data type you support.   G               o  If your PCL or Proprinter setup module needs carriage- D                  control characters after each line, manually supplyE                  them when you create the setup module file. (PCL and   H                  Creating Setup Modules and Device Control Libraries 7-3 y  w            E               Proprinter setup modules do not end line with carriage-t>               control characters because the setup modules mayC               contain binary data, like fonts and raster graphics.)   B            o  ANSI setup modules cause a page eject in the printer>               before the data file, if the setup module causes%               anything to be printed.   *      7.4 Creating Device Control Libraries  A            To make the setup module accessible to users, you must_D            create a device control library and put the module in theC            library. Create a different library for setup modules ofWD            each data type. Do not include setup modules of differentC            data types in the same library. You can create a library :            for ANSI, PCL, Proprinter, or PostScript files.  C               ________________________Note ________________________   B               Do not put your custom setup modules in the standard:               DCPS$DEVCTL library. Custom setup modules inA               DCPS$DEVCTL will be deleted if you upgrade DECprinte"               Supervisor software.  C               _____________________________________________________e  C            To create a library for setup modules, use the following             command format:  F                $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]library-name  @            You supply the library-name, the name you give to the            library.n  @            The following command creates a new PostScript deviceE            control library, PS1, for your customized PostScript setup             modules:   =                $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PS1$  @            For more information, refer to the HP OpenVMS Command>            Definition, Librarian and Message Utilities Manual.      <      7-4 Creating Setup Modules and Device Control Libraries                 0         7.4.1 Putting Setup Modules in Libraries  E               To insert a setup module into a device control library, /               use the following command format:p  N                   $ LIBRARY /INSERT /TEXT SYS$LIBRARY:library-name module-name  H               In the command line, you supply the following information:  6               library-name     The name of the library  ;               module-name      The name of the setup module   E               The following command puts the PostScript setup module, B               CONFIDENTIAL.PS, into your PostScript device controlH               library, PS1.TLB, and names the setup module CONFIDENTIAL:  I                   $ LIBRARY /INSERT /TEXT SYS$LIBRARY:PS1 CONFIDENTIAL.PS_  ?               The following command puts the ANSI setup module, A               A4_PAGE.TXT, into your ANSI device control library, <               ANSI1.TLB, and names the setup module A4_PAGE:  G                   $ LIBRARY /INSERT /TEXT SYS$LIBRARY:ANSI1 A4_PAGE.TXTn  .         7.4.2 Specifying a Library Search List  ?               If you have several device control libraries, you$>               need to set up a search list of the libraries inE               SYS$STARTUP:DCPS$STARTUP.COM. The search list specifies H               which device control libraries to search, and the priority               of the libraries.r  ?               Example 7-1 shows a search list of device controln               libraries.  B               Example 7-1 Search List for Device Control Libraries  =                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB -t#                   _$ DCPS$DEVCTL, - 3                   _$ "PS1 /DATA_TYPE=POSTSCRIPT", - /                   _$ "ANSI1 /DATA_TYPE=ANSI", -y                   _$ PS2    H                  Creating Setup Modules and Device Control Libraries 7-5 _  _            ;            In Example 7-1, the software does the following:   F            1. Looks in the standard device control library DCPS$DEVCTLB               for required setup modules and for any setup modules<               that have been specified with /SETUP or /FORM.  C            2. Looks in the PostScript library PS1 for any specifiedeD               setup modules not found in the standard device controlE               library. (PostScript setup modules can be used with anySD               type of file, so the PostScript device control libraryC               is always included in the search for a setup module.)   C            3. If the print job is ANSI, looks in the library called                ANSI1.  D            4. If the print job is a data type other than ANSI, skipsB               the ANSI1 library and looks for it in the PostScript               library PS2.  ?            To define your library logical name and search list, '            perform the following steps:   9            1. Edit DCPS$STARTUP.COM and replace the line:   G                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB DCPS$DEVCTL                  with the lines:A  K                   $ DEFINE /EXECUTIVE_MODE /SYSTEM logical-name search-list   ;               In the command line, you supply the followings               information:  @               logical-name: Use a logical name that expands to aD               list of library names. Make sure the logical name alsoB               appears in the execution queue definition (parameter               P3).  D               search-list: Add the list of libraries to be searched.@               Use the following guidelines as you add libraries:  ;               o  Place the standard device control library,TB                  DCPS$DEVCTL, first in the list for most efficient                  printing.  A                  If you do not include DCPS$DEVCTL in the libraryu@                  search list, the symbiont stops and returns the)                  following error message:   Y                      REQMODNOTFOUND, Required device control module module-name not foundp  <      7-6 Creating Setup Modules and Device Control Libraries t  i            G                  o  Make sure all the library names are in SYS$LIBRARY.n  A                  o  Make sure all the library names have the file5$                     extenstion .TLB.  A                  o  For each library that includes the /DATA_TYPE ?                     qualifier, enclose the library name and the C                     qualifier in quotation marks. If you do not use H                     the /DATA_TYPE qualifier, you do not need to encloseD                     the library name in quotation marks. The default:                     data type for a library is PostScript.  E                  o  If an ANSI module and a PostScript module performcG                     the same function and have the same name, determineeD                     which one you want as the default for ANSI jobs.  C                     If you want ANSI jobs to default to PostScript, F                     place the PostScript device control library beforeF                     the ANSI library. If you want ANSI jobs to defaultC                     to ANSI, place the ANSI library in front of theN'                     PostScript library.e  E               2. Stop and restart the execution queue to include yourEG                  new library. (If you add a setup module to an existingcE                  library, you do not have to reinitialize the queue.)h  E               For example, to add PostScript libraries called PS1 andt;               PS2, and an ANSI library called ANSI1, enter:   J                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB DCPS$DEVCTL, -3                      "PS1 /DATA_TYPE=POSTSCRIPT", -n/                      "ANSI1 /DATA_TYPE=ANSI", -q                      PS2  D         7.4.3 Device Control Libraries Must Exist for Queue to Start  E               All device control libraries specified for a queue mustrC               exist for the queue to start. For example, if a queueaB               is defined with the following logical, the librariesC               SYS$LIBRARY:DCPS$DEVCTL.TLB, SYS$LIBRARY:ANSI.TLB and:B               SYS$LIBRARY:PS.TLB must all exist as text libraries:  =                   $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB -u#                   _$ DCPS$DEVCTL, -l.                   _$ "ANSI /DATA_TYPE=ANSI", -/                   _$ "PS /DATA_TYPE=POSTSCRIPT"   H                  Creating Setup Modules and Device Control Libraries 7-7 p  f            :      7.4.4 Preserving Custom Setup Modules During Upgrades  D            When you install DECprint Supervisor software, it creates?            a new version of the standard device control librarye<            (DCPS$DEVCTL.TLB). If you purged old files during@            the software installation, early copies of the deviceC            control library are deleted. (Refer to the DCPS Software 4            Installation Guide for more information.)  B            When you add custom setup modules, create a new libraryE            and refer to it in the library search list. This preserves D            your custom setup modules when you upgrade your software.  C            Upgrading from DECprint Printing Services or PrintServer             Client Software  >            DECprint Printing Services software and PrintServerB            Client software have their own device control libraries@            (CPS$DEVCTL.TLB and LPS$DEVCTL.TLB). When you upgradeC            to DECprint Supervisor, the CPS$ and LPS$ device control A            libraries are no longer used. If you have custom setupaB            modules in either of those libaries, insert the modulesC            into a new library and specify the library in the devicef'            control library search list.   -      7.5 Including Setup Modules in Print Joba  C            You can specify setup modules using the /SETUP qualifiert             in the PRINT command.  C            To include an ANSI setup module in a print job using the.>            /SETUP qualifier, use the following command format:  J                $ PRINT /QUEUE=queue-name /SETUP=module-name print-file.TXT  D            If you enter the command wrong, the error is not detectedB            until the file prints. To enable the software to detectE            the error immediately, you can include the setup module in 2            a form. See Chapter 8 for instructions.  =            If users access a setup module frequently, you canoE            associate the setup module with a queue, so that all print B            jobs submitted to that queue are printed with the setup@            module automatically. See Chapter 8 for instructions.  <      7-8 Creating Setup Modules and Device Control Libraries    u            5         7.6 Persistently Loading PostScript Resources       F                 ________________________Note  ________________________  >                 This feature applies only to desktop printers;?                 PrintServer printers are loaded with persistentA9                 resources using the PrintServer software.s  E                 _____________________________________________________   B               Downloading PostScript code with every print job canD               adversely affect printing performance. To resolve thisH               problem, you can load a module that permanently resides in               the printer.  D               The module LPS$PERSISTENT_RESOURCES loads persistentlyD               to desktop printers. To create a persistent PostScript)               module, follow these steps:g  F               1. Create a new device control library for site-specificG                  PostScript setup modules, using the following command:r  L                      $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]library-name  F               2. Edit the SYS$STARTUP:DCPS$STARTUP.COM file to includeG                  the new device control library in the search list. Uset@                  the following command in the DCPS startup file:  g                      $ DEFINE /SYSTEM /EXECUTIVE /NOLOG DCPS_LIB DCPS$DEVCTL, "library-name /DATA=POST"e  F               3. In the execution queue definition for each PostScriptD                  printer to which you want to load the setup module,D                  ensure that the logical name DCPS_LIB is entered inF                  parameter 3 as the device control search list logical                  name.  0               4. Save the DCPS$STARTUP.COM file.  A               5. Stop the queues for the printers affected by thebF                  change, using the STOP /QUEUE /RESET command for each                  queue.o  7               6. Execute the new DCPS$STARTUP.COM file.l  H                  Creating Setup Modules and Device Control Libraries 7-9 s  c            @            7. Test each print queue by sending two print jobs toD               the printer. The setup module is loaded with the firstB               print job sent to the printer. The setting should be:               effective for the second print job, as well.  C               ______________________ CAUTION ______________________-  B               Problems can occur from the misuse of the persistentB               setup feature. Keep the following in mind when using               this feature:   B               o  Only PostScript setup modules can be persistently@                  loaded. Other data types cannot be persistently                  loaded.  @               o  A setup module can exceed the printer's virtual:                  memory. Different models of printers haveB                  different capacities. For example, a setup module=                  can overwhelm a printer with too many fonts.f  B               o  A shared network printer can be used from several?                  nodes in the network. Make sure the same setup @                  module is loaded from all the nodes that access@                  the printer to ensure consistent print results.A                  If you required different setup modules load the ?                  setup module with each print job, using either /                  the /SETUP or /FORM qualifier.i  =               o  Improper PostScript coding in a persistently A                  loaded setup module can cause unexpected resultsrA                  that are difficult to analyze. Also, because ther>                  code remains in the printer until the printer@                  is turned off, users from different systems mayB                  have print jobs fail with unexpected results, but@                  would not be able to determine the cause of the                  problem.   C               _____________________________________________________               =      7-10 Creating Setup Modules and Device Control LibrariesB    p            E         7.7 Changing the Default Character Set for PCL and Proprinter              Print Jobs    E               The default character set for PCL files is Roman-8. The E               default character set for Proprinter files is code page H               437, character set 1. To change the default character set,*               use the following procedure:  @               1. Create one device control library for PCL setupA                  modules, one for Proprinter modules, and another B                  library for PostScript modules. Use the following                  commands:  G                      $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PCL_LIBe  G                      $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PRO_LIB   F                      $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PS_LIB  E               2. Edit DCPS$STARTUP.COM to include these libraries, asl                  follows:   T                      $ DEFINE /EXECUTIVE_MODE /SYSTEM /NOLOG DCPS_LIB DCPS$DEVCTL, -.                         "PCL_LIB /DATA=PCL", -.                         "PRO_LIB /DATA=PRO", -                         PS_LIB  G                  The PostScript device control library (PS_LIB) must be )                  last in the search list.   4               3. Create the following setup modules:  E                  o  The DEF_CHAR_SET.PCL file selects the PC-8 Danish--                     /Norwegian character set:   7                             <ESC>!`1P<ESC>(11U<ESC>!`0P_  D                     Replace <ESC> with the escape character (decimal                     27).  D                  o  The DEF_CHAR_SET.PRO file selects code page 850:  6                             <ESC>`<ETX><NUL><CR>R<ETX>  G                     -  Replace <ESC> with the escape character (decimal                         27).e  H                     -  Replace <ETX> with the etx character (decimal 3).  H                 Creating Setup Modules and Device Control Libraries 7-11 e  g            B                  -  Replace <NUL> with the null character (decimal                     0).p  C                  -  Replace <CR> with the carriage return character !                     (decimal 13).   @               o  The DEF_CHAR_SET.PS PostScript file is used forD                  printing files that are neither PCL nor Proprinter.  A            4. Put these modules in the appropriate device control B               libraries, using the LIBRARY command as shown in the                following example:  U                   $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PCL_LIB DEF_CHAR_SET.PCLg  U                   $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PRO_LIB DEF_CHAR_SET.PROR  S                   $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PS_LIB DEF_CHAR_SET.PS   D            5. Create a form definition that includes DEF_CHAR_SET asE               the setup module. You can associate this form with your 1               printer execution queue as follows:   \                   $ DEFINE /FORM DEF_CHAR_SET form-number /SETUP=DEF_CHAR_SET /STOCK=DEFAULT  A               To make this change to the queue permanent, specifya@               this form in the execution queue definition in the$               DCPS$STARTUP.COM file.  8      7.8 Specifying Printer Resolution with Setup Module  E            These setup modules allow you to manipulate the resolution *            of PostScript Level 2 printers.  E            Table_7-1_Printer_Resolution_Setup_Modules_________________  E            Setup_Module__________Description_________________________   @            RES_300X300           300 dpi horizontal and vertical  ?            RES_600X300           600 dpi horizontal and 300 dpi )                                  vertical   B            RES_600X600           600 dpi horizontal and vertical -(                                  default  @            RES_1200X600          1200 dpi horizontal and 600 dpi)                                  vertical   E            RES_1200X1200_________1200_dpi_horizontal_and_vertical____q  =      7-12 Creating Setup Modules and Device Control Libraries                  F                 ________________________Note  ________________________  B                 Not all resolutions are supported by all printers.A                 To have the printer notify you if it cannot print A                 at a specified resolution, add the /NOTIFY switch A                 to the PRINT command. If the printer cannot print A                 at the requested resolution, it prints at a lower                  resolution.r  E                 _____________________________________________________   <         7.9 Modifying DECimage Parameters with Setup Modules  E               There following setup modules invoke DECimage or modifyd@               the DECimage parameters. They are grouped into the#               following categories:   -               Enabling and Disabling DECimageE  F               These setup modules leave all current parameters intact,E               and turn DECimage on or off. It is not necessary to usenH               these modules if you use other DECimage setup modules. TheF               DECimage setup modules automatically invoke DECimage for$               the current print job.  H               Table_7-2_Enabling_and_Disabling_DECimage_________________  H               Setup_Module__________Description_________________________  5               DI_ON                 Turns DECimage ONT  H               DI_OFF________________Turns_DECimage_OFF__________________  !               Combined Parameters   @               These setup modules adjust two DECimage parameters               simultaneously.                 H                 Creating Setup Modules and Device Control Libraries 7-13                 E            Table_7-3_DECimage_Setup_Modules-Combined_Parameters______   E            Setup_Module__________Description_________________________p  ;            DI_HICONTRAST         Punch0 = 0.2, Punch1 = 0.8r  ;            DI_LOCONTRAST         Punch0 = -.1, Punch1 = 1.1u  ;            DI_BRIGHTER           Punch0 = -.2, Punch1 = 0.8p  ;            DI_DARKER             Punch0 = 0.2, Punch1 = 1.2   E            DI_NORMAL_____________Punch0_=_0,_Punch1_=_1______________                Individual Parameters  A            When you specify one of these setup modules, all otherrC            parameters remain at the default value or the value most ?            recently modified by another setup module. The setup B            modules have no order dependency, so they may appear in/            any order on the print command line.   E            Table_7-4_DECimage_Setup_Modules-Individual_Parameters____   E            Setup_Module__________Description_________________________   +            DI_PUNCH0_0           Punch0 = 0r  -            DI_PUNCH0_0P1         Punch0 = 0.1   -            DI_PUNCH0_0P2         Punch0 = 0.2   -            DI_PUNCH0_M0P1        Punch0 = -.1   -            DI_PUNCH0_M0P2        Punch0 = -.2   +            DI_PUNCH1_1           Punch1 = 1   -            DI_PUNCH1_0P8         Punch1 = 0.8   -            DI_PUNCH1_0P9         Punch1 = 0.9   -            DI_PUNCH1_1P1         Punch1 = 1.1a  -            DI_PUNCH1_1P2         Punch1 = 1.2   0            DI_SHARP_0P5          Sharpness = 0.5  0            DI_SHARP_1            Sharpness = 1.0  0            DI_SHARP_1P5          Sharpness = 1.5  0            DI_SHARP_2            Sharpness = 2.0  E            DI_SHARP_2P5__________Sharpness_=_2.5_____________________   =      7-14 Creating Setup Modules and Device Control Libraries                  +               DECimage Setup Module Example   G               The following example adds sharpening and shifts the gray                levels:   [                   $ PRINT /NOTIFY /QUEUE=queue-name /SETUP=(DI_SHARP_2,DI_DARKER) file-name   9         7.10 Providing Access to Font Cartridge Emulation   E               The DCPS software can emulate physical font cartridges.pD               Use the FONTS_USED parameter with the PRINT command toC               specify one or more soft font modules from the device_=               control library SYS$LIBRARY:CPS$ANSI_FONTS.TLB.   C               This feature, which is available for ANSI files only,eF               supports documents that require font cartridges to printD               on DIGITAL ANSI printers. Just as with these printers,H               the document must contain escape sequences that select the               desired fonts.  F                 ________________________Note  ________________________  <                 DCPS software does not include any soft font@                 modules. SoftFont kits have been retired and are,                 no longer available from HP.  E                 _____________________________________________________O  E               You can associate one or more default soft font modulesNF               with a print queue, so that users do not have to specifyD               this parameter on the PRINT command line. For example,B               to establish CGTRIUM24_ISO1 as the default soft fontA               module for the queue, include the following line in                DCPS$STARTUP.COM:   '               FONTS_USED=CGTRIUM24_ISO1   F               (Add the line to P4 in the execution queue definition or5               as P3 in the generic queue definition.)e  H               You can combine soft font modules for user convenience, atF               the expense of disk space and loading time. For example,H               if users need to load all three DEC Multinational CG TimesG               soft font modules together, create a new module using thed-               following sequence of commands:   H                 Creating Setup Modules and Device Control Libraries 7-15 u  y            U                $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES8-10-12_MCSN  S                $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES14-18_MCSP  P                $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES24_MCS  W                $ COPY CGTIMES8-10-12_MCS.TXT, CGTIMES14-18_MCS.TXT, CGTIMES24_MCS.TXT - $                _$ ALLCGTIMES_MCS.TXT  T                $ LIBRARY /INSERT /TEXT SYS$LIBRARY:CPS$ANSI_FONTS ALLCGTIMES_MCS.TXT  D            Users can specify the new module with the print parameter%            FONTS_USED=ALLCGTIMES_MCS._  .      7.11 Device Control Library Cache Feature  A            DCPS includes a device control library caching featurep@            that optimizes the retrieval of certain commonly-used-            PostScript device control modules.c  B            The caching feature causes modules with names beginning=            with LPS$$ to be read only the first time they are C            requested. Those modules reside in the symbiont's cache.oB            Jobs that follow can quickly access those modules untilD            you reset the queue or restart the system. This minimizesB            access to the primary device control library, saves CPU'            time, reduces disk activity.E  A            The device control library caching feature is disabled C            by default. To enable the device control library cachingaD            feature for a specific queue, enter the following command*            before you start a print queue:  N                $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_DEVCTL_CACHE 1  B            Caching device control library modules can decrease theC            total CPU time consumed by the symbiont by as much as 17 D            percent. I/O activity on the part of the symbiont is also,            reduced by as much as 50 percent.  D            You can define the system logical DCPS$DEVCTL_CACHE (withB            no queue name specified) to specify that device controlB            library caching is enabled for all DCPS print execution!            queues on that system.   =      7-16 Creating Setup Modules and Device Control Libraries     F            .         7.12 Printing on Unrecognized Printers  A               The DCPS software automatically obtains a printer'slD               product name before printing jobs. It uses the productE               name to select and download device control modules thate5               are specific to the particular printer.   G               If you use the DCPS software with a printer whose productPF               name it does not recognize, the product name defaults toG               "HPGENERIC" if it is an HP printer, and "UNRECOGNIZED" if_H               it is not. The supervisor downloads device control modulesG               associated with that name. Although this configuration is H               unsupported, the modules associated with an "unrecognized"F               printer may be sufficient to permit simple printing withB               that device. Printers identified as "generic HP" useF               commands common to most HP printers and allow additionalF               features such as tray selection and use of the printer's%               native PCL interpreter.-  F               If a printer is being treated as a "generic HP" printer,G               an OPCOM message similar to the following will be issued:l  H                 %%%%%%%%%%%  OPCOM  14-NOV-2002 16:25:43.37  %%%%%%%%%%%2                 Message from user SYSTEM on FUNYETZ                 Queue MY_NEW_PRINTER: %DCPS-W-HPGENERIC, Product name hp LaserJet 9999 not0                  recognized; assuming HP Generic  @               If a printer is being treated as an "unrecognized"H               printer, an OPCOM message similar to the following will be               issued:X  H                 %%%%%%%%%%%  OPCOM  20-MAY-2003 16:54:05.25  %%%%%%%%%%%2                 Message from user SYSTEM on FUNYET[                 Queue YOUR_NEW_PRINTER: %DCPS-W-UNRECOGNIZED, Product name Foo Bar 1234 not 2                  recognized; assuming Unrecognized  G               A system manager can also modify the corresponding deviceLH               control modules as needed without affecting the character-G               istics of any of the supported printers. By following the_F               comments contained within the LPS$$UNRECOGNIZED modules,G               along with some knowledge of PostScript and the specificsrG               of the printer, and examination of device control modulestD               for similarly programmed printers (if any), the systemF               manager may be able to get tray and sheet size selection&               working for the printer.  H                 Creating Setup Modules and Device Control Libraries 7-17 p  t            C               ________________________Note ________________________   @               Your use of an unrecognized printer with DCPS, and>               any use or modification of the LPS$$UNRECOGNIZED;               device control modules, is without support orcB               assistance from Hewlett-Packard Company. Further, HPB               makes no commitment to maintain the same contents ofB               or interface to these modules for different versions               of DCPS.  C               _____________________________________________________   E            Device control modules are located in the following device             control library:e  /              SYS$COMMON:[SYSLIB]DCPS$DEVCTL.TLBs  E            The device control modules associated with an unrecognizedf            printer are:S  +              LPS$$UNRECOGNIZED_INITPSDEVICES)              LPS$$UNRECOGNIZED_SETCONTEXTn+              LPS$$UNRECOGNIZED_SETINPUTTRAY ,              LPS$$UNRECOGNIZED_SETOUTPUTTRAY  A            If you modify these modules for a certain printer, youn>            should always place the modified modules in a site-=            specific device control library (see Section 7.4).o                                  =      7-18 Creating Setup Modules and Device Control Librariesl I                     H                                                                        8H         ________________________________________________________________  H                                Creating and Maintaining Form Definitions      F               You can create form definitions, which users can includeB               in their PRINT command to modify the appearance of aD               file. A form definition can specify several attributesC               for a print job, including the type of paper stock on G               which it is to be printed; the width, length, and marginscD               associated with the paper; whether long text lines areE               to be truncated or wrapped onto another line; and setups;               modules to be implicitly sent to the printer.~  D               When users specify an unknown form name in their PRINTG               command, DECprint Supervisor informs them immediately. InnH               contrast, if they specify an unknown setup module in theirH               PRINT command, DECprint Supervisor does not inform them ofG               the problem until it starts printing the job and needs to &               access the setup module.  H               The commands for creating, maintaining, and deleting forms8               require that you have operator privileges.  0         8.1 Associating Setup Modules with Forms  E               To associate a setup module with a form, use the DEFINEt6               /FORM command with the /SETUP qualifier.  H               Example 8-1 defines a form called CONFIDENTIAL that uses a*               setup module called PRIVATE.  >               Example 8-1 Sample Form Definition, CONFIDENTIAL  3                   $ DEFINE /FORM CONFIDENTIAL 101 -uO                   _$ /DESCRIPTION="prints the word CONFIDENTIAL on each page" -n%                   _$ /STOCK=DEFAULT - #                   _$ /SETUP=PRIVATEs    H                            Creating and Maintaining Form Definitions 8-1 t  m            ;            When you define a form, you supply the followingh&            qualifiers and information:  A            o  Form Name: You select the name for the form you areiC               defining. The name can consist of up to 31 characters A               and must contain at least one alphabetic character.e  D            o  Form Number: You specify a number for the form you are               defining.p  D            o  /DESCRIPTION:  You can optionally add a description toB               the form to help users understand what the different               forms do.   A            o  /STOCK: You supply the name of the media that needs A               to be in the printer when this form is invoked. The D               media you specify must match the media in the printer.@               If they do not match, the job is held in the queueE               until users load the specified media or modify the formSC               definition. Use the DEFAULT parameter to use whateverv&               media is in the printer.  E            o  /SETUP: You must supply the name of the setup module(s)l0               you want associated with the form.  C               ________________________Note ________________________M  A               The existence of the setup module(s) is not checkedh%               until the form is used.a  C               _____________________________________________________e  .      8.2 Associating a Form with a Print Queue  =            If users invoke a setup module frequently, you canLA            associate the setup module with a form, then associate E            the form with a queue. This method ensures that print jobsbE            submitted to the queue automatically use the setup module.uA            Use the following procedure to associate a form with a             queue:e  D            1. Associate the setup module with the form, as described               in Section 8.1.     2      8-2 Creating and Maintaining Form Definitions I  R            H               2. Associate the form with the execution queue, by editingA                  parameter 5 (P5) in DCPS$STARTUP.COM as follows:-  F                  o  With the /FORM_MOUNTED qualifier, specify the name;                     of the form you want tied to the queue.   D                  o  Specify the /DEFAULT=FORM=form-name qualifier toG                     ensure that every job prints with the form, even if 1                     the user does specify a form.   A                  The following example associates the form called B                  CONFIDENTIAL with an execution queue called XLR8:  9                      $ @SYS$STARTUP:EXECUTION_QUEUE.COM - J                        XLR8-                    !P1 - Execution queue nameA                        "DECNET/XLR8" -          !P2 - Device name.O                        DCPS_LIB -               !P3 - Logical name for /LIBRARYc>                        "" -                     !P4 - Not usedV                        "/FORM_MOUNTED=CONFIDENTIAL/DEFAULT=(FORM=CONFIDENTIAL,NOFEED)"N                                                 !P5 - Queue default qualifiers  4         8.3 Creating Form Definitions for ANSI Files  G               When you define forms for ANSI files, you can use various F               qualifiers that affect the page layout. For example, theE               following command defines the form CENTER to have a top 2               margin of 6 and a left margin of 10:  A                   $ DEFINE /FORM /MARGIN=(TOP=6,LEFT=10) CENTER 3A  ?               You can use the qualifiers in Table 8-1 with forme-               defintions for ANSI files only:_                          H                            Creating and Maintaining Form Definitions 8-3 n  e            E            Table_8-1_DEFINE_/FORM_Qualifiers_for_ANSI_Files__________l  E            This_Qualifier_._._.__Does_the_Following_._._.____________   A            /LENGTH=n             Sets the length of each page, in '                                  lines.o  2            /MARGIN=keyword=n     Sets the margins.  >                                  You supply one or more of the4                                  following keywords:  )                                  -  TOP=nd  ,                                  -  BOTTOM=m  +                                  -  RIGHT=yl  *                                  -  LEFT=z  ?                                  To supply more than one margin =                                  keyword, enclose the list in 4                                  parentheses, as in:  =                                      /MARGIN=(TOP=n,BOTTOM=m)f  D            /PAGE_SETUP=module    Applies a page setup module to each1                                  page in the job.E  E            /[NO]TRUNCATE         Truncates long lines that do not fit 3                                  in the page width.n  >            /WIDTH=n              Sets the width of the page in7                                  columns or characters.   C            /[NO]WRAP             Wraps lines wider than the page totE            ______________________the_next_line.______________________r              Notes:e  E            o  These form definitions are useful only with ANSI files,:E               because other types of files have internal controls forw               these attributes.e  ;            o  You can prevent the software from wrapping oryA               truncating long lines by including both /NOWRAP ande1               /NOTRUNCATE in the form definition.I  2      8-4 Creating and Maintaining Form Definitions                 1         8.4 Displaying Forms and Their Attributes   B               You can display the forms that already exist on your0               system with the following command:  $                   $ SHOW QUEUE /FORM  6               The form definitions display as follows:  K                   Form name                            Number   Description K                   ---------                            ------   ----------- X                   A4_12 (stock=PLAIN_PAPER)              1129   A4 12-Pitch with marginsa                   A4_LPT_GRAY (stock=PLAIN_PAPER)        1118   A4 DP line printer with gray barso2                   A4_LPT_PLAIN (stock=PLAIN_PAPER)_                                                          1119   A4 Plain DP line printer formatuJ                   BOOT_CHART (stock=DEFAULT)               37   BOOT_CHARTV                   BSS$LANDSCAPE (stock=DEFAULT)          3301   BSS Specific LandscapeU                   BSS$PORTRAIT (stock=DEFAULT)           3302   BSS Specific Portrait   E               You can display the attributes of a form using the SHOW B               QUEUE /FORM /FULL command. For example, this command6               displays the attributes of DCPS$DEFAULT:  7                   $ SHOW QUEUE /FORM /FULL DCPS$DEFAULT   K                   Form name                            Number   DescriptionNK                   ---------                            ------   -----------rL                   DCPS$DEFAULT (stock=DEFAULT)           1115   DCPS defaultC                       /LENGTH=66 /STOCK=DEFAULT /TRUNCATE /WIDTH=80n           8.5 Deleting a Formu  F               Use the DELETE /FORM command to delete a form definitionF               from the system's form table. The format of this command               is as follows:  *                   $ DELETE /FORM form-name  E               In the command line, you supply form-name, which is the"6               name assigned to the form you are using.  G               Before you use the DELETE /FORM command, execute the SHOW F               QUEUE /FULL /ALL command. References to a form can existH               as an attribute of an active print queue or as a qualifierF               to a print request. If you try to delete a form that hasH               outstanding references, you are notified of the condition,A               and the form is not deleted. (Refer to Appendix A.)   H                            Creating and Maintaining Form Definitions 8-5 C               /      8.6 Using the Default ANSI Form Definition   B            If users omit a form definition in their PRINT command,E            but supply one of the following qualifiers, DCPS links the7C            default form definition DCPS$DEFAULT with the ANSI file.e                 /HEADERp               /SPACE!               /PARAMETERS=[NO]TAB                                                                         2      8-6 Creating and Maintaining Form Definitions t  a                  H                                                                        9H         ________________________________________________________________  H                                     Charging Users for Printer Resources      D               This chapter describes the accounting information thatE               is supplied to the OpenVMS accounting files by the DCPSi               software.   H               The OpenVMS Accounting Utility reads information about theO               use of system resources from the file SYS$MANAGER:ACCOUNTING.DAT. @               The DCPS software records information in this fileD               about printer usage. For information about the OpenVMSF               Accounting Utility, see the HP OpenVMS System Management)               Utilities Reference Manual.s  @         9.1 Accounting Information Supplied by the DCPS Software  F               The print symbiont supplies the following information in5               the accounting file for each print job:i                 o  Pages printed  F                  This is the actual number of sheets printed. When youD                  are using the NUMBER_UP parameter to print multipleC                  pages on a sheet, this field records the number offC                  sheets of paper printed, not the number of logical E                  pages printed. The number of sheets printed includesiA                  the separation (flag, trailer, and burst) pages.tD                  When the print job is deleted by the user or systemH                  operator, this information reflects the number of pages7                  printed before the job was terminated.a  G                  The value shown in the accounting file and on the DCPS G                  trailer page will not be correct for all printers. See 2                  Section 9.3 for more information.  !               o  Gets from sourceu  G                  This is the number of RMS "gets" from all files in thet*                  print job (records read).                 o  QIO puts_  H                                 Charging Users for Printer Resources 9-1 l  o            C               This is the number of QIO "writes" to the printer pern               job.  @            When a print job has been completed successfully, theB            print symbiont sends a request to the job controller toD            insert certain accounting data fields into the accountingC            log file. For successful jobs and jobs terminated by thebC            DELETE /ENTRY command, the accounting file also includes !            the following message:o  9            %SYSTEM-S-NORMAL, normal successful completion   B            If the print job terminates abnormally, the informationC            the print symbiont supplies in the accounting log may beeC            incomplete. To filter out such jobs, count only the jobs A            that receive the successful completion status message.B>            Any of the following may cause the job to terminate            abnormally:  (            o  STOP /QUEUE /RESET command              o  Symbiont crash              o  Printer crashs  %            o  Network connection lostd  >      9.2 Accounting Information Supplied by the Job Controller  C            The job controller supplies the following information in .            the accounting file for print jobs:              o  Username  @               User name of the user who submitted the print job.              o  Accounth  C               Account name of the user who submitted the print job.3  ,            o  UIC (user identification code)  :               UIC of the user who submitted the print job.              o  Process ID  A               Process ID of the user who submitted the print job.c              o  Start Time  -      9-2 Charging Users for Printer Resourceso                 E                  The time the print job reached the top of the deviceeC                  queue (not necessarily the time that the print job *                  actually began to print).                 o  Finish Time  4                  The time the job finished printing.                 o  Elapsed Timeh  A                  The wall-clock time it took for the job to printo0                  (finish time minus start time).                 o  Priority_  1                  Queue priority of the print job.o  "               o  Final Status Code  B                  Exit status of the print job. The status code for%                  success is 00040001.                  o  Queue Entry  E                  Queue entry number. This is the print job number. Ine5                  this example, 222 is the job number:   >                  $ PRINT /QUEUE=LN03R$SCRIPT4 /NOTIFY TEST.MEMU                    Job TEST (queue LN03R$SCRIPT4, entry 222) started on queue SCRIPT4e                 o  Queue Name   0                  Name of the print device queue.                 o  Queue Job  A                  Print job name, as printed on the job flag page.   .               o  Final Status Text = F$MESSAGE  A                  The text for the Final Status code. The text for /                  completion of a normal job is:.  =                  %JBC-S-NORMAL,  Normal successful completionh  @         9.2.1 Accounting Fields Left Blank by the Job Controller  G               The job controller fills the following fields with blankso4               in the accounting file for print jobs:                 o  Owner IDc                 o  Terminal Name  !               o  Remote Node Namee  H                                 Charging Users for Printer Resources 9-3 i  r                        o  Remote IDr  D      9.2.2 Accounting Fields Filled with Zeros by the Job Controller  C            The job controller fills the following fields with zerosn1            in the accounting file for print jobs:               o  Privilege <31-00>_              o  Privilege <63-32>   %      9.3 Accuracy of DCPS Page Countss  E            The page count reported by DCPS in the accounting file andtB            on the DCPS trailer page relies on information returned?            by the printer. Some printers do not report accurates5            information, due to different methods for:   &            o  Counting pages vs. sides  A               Some printers count physical sheets of paper, while 4               others count images, or sides printed.  $            o  When pages are counted  C               Some printers count pages interpreted by the printer,n9               while others count pages physically output.e  =            For the page count reported by DCPS to be correct, @            the printer must count physical sheets interpreted by@            the printer. All Compaq, DIGITAL and GENICOM printersD            supported by DCPS, except the following models, adhere toD            this requirement and send the proper information to DCPS.  '               Compaq Laser Printer LN20 '               Compaq Laser Printer LN40S(               Compaq Laser Printer LNC02)               DIGITAL Laser Printer LNC02   C            No other printers, including HP printers, are guaranteedS4            to supply correct accounting information.        -      9-4 Charging Users for Printer Resourcese a               7         9.4 Compatibility with Mechanical Page Counters   E               The PrintServer printers have mechanical page counters.   G               The mechanical page counter is different from the counterCC               accessible through the PostScript pagecount operator.e  B               o  The mechanical page counter counts all the sheets:                  printed since the print engine was built.  H               o  The PostScript page counter counts the number of sheets+                  printed by the controller.e  G               Under normal use, the totals of both counters increase at>G               a similar rate, but there can be a significant differencedG               between them. Print engine test pages, initiated with the H               test button on the printer, are recorded on the mechanicalH               counter but not on the PostScript counter. Also, replacingH               components can affect the counters. For example, replacingA               the nonvolatile memory of the controller resets thehG               PostScript counter, but it does not affect the mechanicalt               counter.  G               Because the counters record different events, they should -               be used for different purposes:   F               o  Use the PostScript counter to determine the number of<                  sheets printed within a PostScript program.  F               o  Use the mechanical counter to track print engine use.                              H                                 Charging Users for Printer Resources 9-5 _                     H                                                                       10H         ________________________________________________________________  H                                             Printer-Specific Information      F               This chapter provides management information about usingG               DCPS with specific printers. Printer-specific informationlB               that might be of interest to general users is in theD               DCPS User's Guide rather than in this manual. The DCPSH               Release Notes may also contain additional printer-specific               information.  ?               Check the documentation for your printer, network_A               interface card, print server, or terminal server torC               determine the correct TCP port number to use. The TCPzE               port number may also be listed in Table 3-2. If no port 0               number is specified, 9100 is used.  +         10.1 Apple LaserWriter Plus Printerf  5         10.1.1 LPS$PERSISTENT_RESOURCES Not Supportedt  A               The DCPS feature to load the module LPS$PERSISTENT_ F               RESOURCES outside the PostScript server loop for desktopA               printers is not supported for the LaserWriter Plus.   A         10.2 Compaq Laser Printer LN16 and GENICOM microLaser 170_  ,         10.2.1 Printer Configuration Setting  ?               DCPS requires the printer's PERSONALITY be set toeC               POSTSCRIPT. If the PERSONALITY is set to AUTO or PCL,lH               DCPS jobs will remain in a Starting state and never print.C               This setting is in the printer console's CONFIG menu.,  H               Setting the PERSONALITY to POSTSCRIPT will still allow PCL>               jobs coming from Windows PCs to print correctly.      H                                        Printer-Specific Information 10-1    u            +      10.2.2 LAT and AppleTalk ConfigurationE  B            To create a LAT device for use by a DCPS queue, you can?            use either of the following sets of values for LATCP             qualifiers:  )            o  /NODE=nodename /PORT=PORT_1,              o  /SERVICE=service  C            where nodename is the printer's NIC nodename and servicey?            is the name of a valid service on the printer. Theses?            values can be obtained from the printer NIC's status B            page or by logging in to the NIC via Telnet or LAT. ForD            example, this command shows the printer NIC's nodename to            be PRQ_00001F:_  #                Local_4> show server Y                   NET16 Version V1.0/1(990126)           Uptime:                 23:17:07_Y                   Hardware Addr: 00-50-27-00-00-1f       Name/Nodenum:      PRQ_00001F/ 0o%                   Ident String: NET16u  A            To create a DCPS queue using AppleTalk, you must use aaA            service name. You can use one of the default services,bE            modify a default service or create your own. The followingSB            is an example of a service that can be used by both LATE            and AppleTalk. In this example, DCPS_LN16 is the AppleTalk_            name.  .                Local_4> list service dcps_ln16  Q                Service:  DCPS_LN16         Ident:  DCPS Compaq Laser Printer LN16 4                  Rating: N/A               Ports:  1Y                  Characteristics:          Queueing  Binary  Rtel  Connections  AppleTalkW.                                            Lat,                  SOJ: <none>     EOJ: <none>"                  Enabled Groups: 0  B            Create AppleTalk services with caution, as creating theD            same service name on more than one printer will result inB            multiple printers using the same AppleTalk name on your            network.i  A            Refer to the printer's Ethernet Network Interface CardnD            (NIC) Reference Manual for more information about setting/            characteristics of printer services.   &      10-2 Printer-Specific Information h               F         10.3 Compaq Laser Printer LN32 and LNM40; GENICOM Intelliprint)              mL, LN and microLaser Series1  F                 ________________________Note  ________________________  A                 This section does not apply to the GENICOM micro-U"                 Laser 170 printer.  E                 _____________________________________________________   -         10.3.1 Printer Configuration Settings   &         10.3.1.1 Language-Sensing Mode  B               DCPS can print to these printers when the printer isD               in PostScript mode or automatic language-sensing mode.C               Make sure the INTERPRETER and FORMAT settings are setoE               as described in Table 10-1. These values are set in thel6               INTERFACE menu on the printer's console.  H               Table_10-1_Valid_Language_Sensing_Configurations__________  H                                     Printer_Settings____________________  H               Printer_Mode__________Interpreter_Format__________________  3               PostScript/PCL        Auto        Raws*               sensing               Switch  H               PostScript____________PostScript__Normal__________________  9         10.3.1.2 Printer Setting May Cause Stalled QueuesR  A               The factory default value for the printer's DelayedlB               Output Close setting may cause DCPS queues to stall.A               The default value is OFF and is intended to improveeE               performance by controlling how quickly the printer endsiD               one job and starts another. However, if you also printE               from environments other than DCPS, this value may cause E               DCPS queues to stall. Therefore, if you also print from F               multiple environments, set the value to ON. If you printG               only from DCPS, you may leave the value of Delayed Output_               Close at OFF.   B               The setting for Delayed Output Close is found on theA               printer's console as DELAY OUT CLOSE in the NETWORKs0               section of the INTERFACE menu. [*]  !               ___________________ ?               [*]This setting does not appear on LN32 and LNM40   H                                        Printer-Specific Information 10-3 S  T            +      10.3.2 LAT and AppleTalk Configuration   D            Please see Section 10.2.2 for information about configur-(            ing LAT and AppleTalk queues.+      10.3.3 Queue Aborts When Using TCPwareo  A            When using TCPware with these printers, it is possiblefB            to receive numerous userdata messages on the screen andC            have the queue fail with an OPCOM message similar to thef            following:r  E              %%%%%%%%%%%  OPCOM  21-APR-1999 15:09:53.22  %%%%%%%%%%%s.              Message from user SYSTEM on ZIPPYD              Queue LN32_RAW: %DCPS-F-EXQUOTA, process quota exceeded  >            This problem occurs when running TCPware V5.3-3 andC            network firmware V1.0/4 (990323). To avoid this problem,AA            the system manager should perform one of the followingC            steps:A  3            o  Issue the following TCPware commands:2  "                  $ NETCU STOP /TCP9                  $ NETCU START /TCP /NOPATH_MTU_DISCOVERY   <            o  Upgrade TCPware to a version later than V5.3-3  6            o  Apply TCPware patch kit DRIVERS_V533P020  4            o  Upgrade the printer's network firmware  .      10.4 DIGITAL Colorwriter LSR 2000 Printer  -      10.4.1 NIC Does Not Work with Raw TCP/IPc  D            DCPS cannot communicate with the Colorwriter LSR 2000 viaC            a Raw TCP/IP connection because the NIC does not supportd$            Raw TCP/IP communication.  @            DCPS can use LPD or AppleTalk to communicate with theC            Colorwriter LSR 2000 printer. If you use LPD to print toeB            this printer, specify the internal queue name 'xjprint'#            when creating the queue.               ___________________  @                printers with firmware earlier than version 3.03.  &      10-4 Printer-Specific Information t  ,            0         10.5 DIGITAL DECcolorwriter 1000 Printer  +         10.5.1 Printer-Specific Setup Files   @               You can use the files listed in the table below toF               alter the persistent state of the printer, affecting allH               subsequent jobs that the printer receives from your systemE               and from other systems in the network until the printeroE               is turned off and back on. The files are located in theb:               SYS$COMMON:[SYSHLP.EXAMPLES.DCPS] directory.  H               __________________________________________________________H               Setup_File____________Description_________________________  =               DCW1000_CONFIG.PS     Sets the printer timeoutse  G               DCW1000_DEVPARAM.PS   Changes configuration of the serialu(                                     port  :               DCW1000_STARTPG.PS    Enables the start page  ;               DCW1000_NOSTRTPG.PS   Disables the start pager  ?               DCW1000_PRNTCNFG.PS   Enables a software-selectedr4                                     information page  F               DCW1000_PSCRIPT.PS    Changes the port to PostScript andH               ______________________default_on_all_ports________________                 Notes:  B               o  When you send the DCW1000_DEVPARAM.PS file to theD                  printer, the communications settings change and theF                  queue hangs. You must STOP/RESET the queue and changeE                  the corresponding settings on the DECserver or other G                  LAT device to which the printer is connected. Also, be E                  sure that the printer is running in PostScript mode.   H               o  By default, the DIP switches on the back of the printerE                  are in the down position, indicating that the serial G                  interface can be adjusted and that no color correction F                  is set. The factory default is 9600 baud, 8 bits, andE                  no parity. See the DECcolorwriter 1000 documentation C                  for further information on how setup files and DIP #                  switches interact.   C               o  To check the current configuration of the printer, H                  toggle DIP switch 4 from down to up, then to down (withH                  the other three DIP switches in the down position). The  H                                        Printer-Specific Information 10-5 n  r            E               printer prints a configuration page. Make sure that thef4               printer is running in PostScript mode.    '      10.6 DIGITAL DEClaser 3500 Printer5  )      10.6.1 Job Remains in Starting Statem  B            When using DCPS with the DEClaser 3500 printer with theA            optional serial port, the job may remain in a startingcA            state. If this is the case, you must choose one of then            following options:d  @            1. Lock the printer to PostScript mode. (On the frontC               panel: Serial, Printer Type = STD PostScript). Do notBB               use the DCPS$queuename_NO_SYNC logical name. In thisC               mode, native PCL is not available because the printerSC               does not respond to PJL sequences. You should use theoD               workaround described in Section 10.7.1 to force use of#               the PCL 4 translator.   E            2. Set the serial port language sensing mode to Automatic. @               (On the front panel: Serial, Printer Type = PS/PCLD               Sensing) and define the DCPS$queuename_NO_SYNC logical?               name as described in Section 3.5.3. In this mode, @               the printer responds to PJL sequences and switches?               to native PCL 5 or PostScript as indicated by the                datastream.l  A      10.6.2 Interaction Between Communication Protocol and Nativek             PCL Support   A            The optional network card supports switching to native A            PCL; however, the protocol must be set to autosensing.   -      10.6.3 NIC Does Not Work with Raw TCP/IP_  D            DCPS cannot communicate with the printer via a Raw TCP/IPD            connection because the NIC does not support bidirectional             TCP/IP communication.  =            As an alternative, you can use LAT or LPD with thesA            printer's NIC or connect the printer to a print server E            (for example, the Rapidprint 500) or a terminal server. IfTE            you use LPD to print to this printer, specify the internalS6            queue name 'PORT1' when creating the queue.  &      10-6 Printer-Specific Information                 *         10.7 DIGITAL DEClaser 5100 Printer  G         10.7.1 Native PCL Is Unavailable with EtherTalk Protocol on NIC   B               Because of a problem with the Network Interface CardC               (NIC), DCPS cannot switch the printer into native PCL C               when using the EtherTalk protocol. Users will see the_               error:  R               %DCPS-W-UNDEF, undefined: Name not known - offending command is <1B>D               %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored  F               A partial workaround is possible by specifying a defaultD               print job parameter of PAGE_LIMIT=999999 for the queueD               when you create it in DCPS$STARTUP.COM. This parameter@               forces any PCL files to be printed through the PCLC               translator. Remember, though, that the PCL translator;)               is PCL 4 rather than PCL 5.   0         10.7.2 NIC Does Not Work with Raw TCP/IP  D               DCPS cannot communicate with the printer via a Raw TCPD               /IP or LPD connection because the NIC does not support9               bidirectional TCP/IP or LPD communications.i  G               As an alternative, you can connect the printer to a print D               server (for example, the Rapidprint 500) or a terminal6               server, or use a LAT connection instead.  -         10.7.3 Downloading and Deleting Fontse  @               You may download or delete fonts from the DEClaser@               5100 printer's optional hard drive using the FONT_?               DOWNLOADER.COM procedure described in Appendix C.h  !         10.7.4 Error Page Featurea  A               The DEClaser 5100 printer has a feature that ejectsnB               the current sheet and then prints a PostScript ErrorC               information sheet when a PostScript interpreter erroreF               occurs. While this feature provides a powerful means forF               analyzing PostScript problems, it is not recommended forC               everyday use with the DCPS software for the followingn               reasons:  F               o  PostScript error pages are printed when a user enters3                  DELETE/ENTRY to abort a print job.s  H                                        Printer-Specific Information 10-7 l  n            B            o  PostScript error pages are printed after a not readyB               condition is cleared (paper supplied, jam corrected,C               etc.) if a job was submitted on the serial port while 1               the printer was not ready to print.o  ?            You should disable the feature called "Print Errors" @            through the DEClaser 5100 front panel before startingC            print queues with DCPS. Enable the feature only when yout;            are interested in analyzing PostScript problems.O  C            If a job fails to print because of a "limitcheck" error,nD            check to see if "page protection required" is part of theC            error message. If so, the job failed because the printeroE            could not compose the page fast enough to keep up with thedE            printer's engine. Turning on the printer's page protection 1            feature will probably fix the problem.   %      10.8 DIGITAL Laser Printer LN15+o  ?            The DIGITAL Laser Printer LN15+ is an upgrade to the =            DIGITAL Laser Printer LN15. References in the DCPS_E            documentation to the DIGITAL Laser Printer LN15 also applyx.            to the DIGITAL Laser Printer LN15+.  *      10.8.1 Printer Configuration Settings  C            DCPS requires certain LN15 printer characteristics to be A            set. If these values, described in Table 10-2, are notnC            set, DCPS jobs will remain in a Starting state and nevert            print.r  E            Table_10-2_LN15_Configuration_Settings____________________   E            Setting_________Value_____Where_Set_____Documentation_____   C            PERSONALITY     PS        Printer       LN15 User Manualo,                                      console0                                      CONFIG menu  C            NPAP MODE       OFF       Printer       LN15 User Manuala,                                      console-                                      PARALLELu)                                      menur  A            PORT 1          ENABLED   Ethernet      RapidPrint 600 ?            BITRONICS                 card          Print Server E            __________________________management____Installation_Guidep  &      10-8 Printer-Specific Information o               *         10.9 DIGITAL Laser Printer LN17+ps  @               The DIGITAL Laser Printer LN17+ps is an upgrade to@               the DIGITAL LN17ps printer. References in the DCPSD               documentation to the DIGITAL LN17ps printer also apply3               to the DIGITAL Laser Printer LN17+ps.U  ,         10.9.1 Job Remains in Starting State  E               If you use a Raw TCP/IP or LAT-connected LN17ps printer"F               with DCPS, the associated DCPS print job may remain in a               Starting state./  >               You must either set the Ethernet port to use the@               PostScript language and disable automatic languageF               sensing, or define a DCPS$queuename_NO_SYNC logical nameF               for the associated queue as described in Section 11.1.1.  E               o  If all the print jobs that the printer receives fromsE                  its Ethernet port come from DCPS, including PCL jobsaE                  that use the printer's native PCL 5e interpreter, dom                  the following:   C                  Set the printer's Ethernet port System Language to/E                  PostScript and turn off Language Sensing. You change F                  these settings from the interface menu on the printer@                  console, as described in the LN17ps User Guide.  H               o  If any of the print jobs that the printer receives fromF                  its Ethernet port do not contain PostScript data (forE                  example, they contain PCL or ASCII data) and DCPS is ?                  not the source of such data, do the following:   F                  Enable Language Sensing on the the printer's EthernetG                  port. Define a DCPS$queuename_NO_SYNC logical name forrE                  the associated queue as described in Section 11.1.1.            10.9.2 LPD PrintingO  B               If you use LPD to print to this printer, specify theE               internal queue name 'PASSTHRU' when creating the queue.E  $         10.9.3 Incorrect Sheet Count  E               The sheet count reported on the job trailer page and indG               the OpenVMS accounting file may be several sheets too fewiF               due to a limitation with the LN17ps printer. There is no               known workaround.A  H                                        Printer-Specific Information 10-9 e  b            *      10.9.4 Downloading and Deleting Fonts  E            You may download or delete fonts from the LN17ps printer'sn<            optional hard drive using the FONT_DOWNLOADER.COM-            procedure described in Appendix C.o  6      10.9.5 Colored Separator Pages and Tray Switching  E            The LN17ps can switch between input trays when a specifiedi<            tray becomes empty. By default, tray switching isE            disabled. If you currently specify colored separator pages B            by using the DCPS$queuename_SEPARATOR_PAGE logical, you>            may want to ensure that tray switching is disabled.  E            You disable tray switching from the printer console, underiB            the PostScript menu. See the LN17ps User Guide for more            information.   B            Use one of the following PostScript tray numbers as the>            value of the DCPS$queuename_SEPARATOR_PAGE logical:  !                 0       Main trayo"                 1       Front tray$                 2       Lower 1 tray$                 3       Lower 2 tray  %      10.10 DIGITAL Laser Printer LN20   "      10.10.1 Incorrect Sheet Count  ?            The sheet count reported on the job trailer page and ?            in the OpenVMS accounting file is incorrect due to a >            limitation with the LN20 printer. There is no knownC            workaround. The LN20 has, however, an accounting feature19            that can be used to track printer utilization.4  %      10.11 DIGITAL Laser Printer LN40   "      10.11.1 Incorrect Sheet Count  ?            The sheet count reported on the job trailer page and ?            in the OpenVMS accounting file is incorrect due to a ?            limitation with the LN40 printers. There is no knownfC            workaround. The LN40 has, however, an accounting feature 9            that can be used to track printer utilization.p  '      10-10 Printer-Specific Information                  4         10.12 Compaq and DIGITAL Laser Printer LNC02  (         10.12.1 Minimum Firmware Version  F               To use the LNC02 with the Raw TCP/IP protocol from DCPS,G               the printer must be running a minimum firmware version of H               System Release 1.1.1, Revision 3.11. This firmware version@               number is displayed on the printer's startup page.  %         10.12.2 Incorrect Sheet CountN  B               The sheet count reported on the job trailer page andB               in the OpenVMS accounting file is incorrect due to aB               limitation with the LNC02 printer. There is no knownG               workaround. The LNC02 has, however, an accounting featureE<               that can be used to track printer utilization.  ,         10.13 DIGITAL PrintServer 17 Printer  :         10.13.1 Colored Separator Pages and Tray Switching  @               PrintServer Software, Version 5.0, adds input trayB               failover to the PrintServer 17 series printers. ThisC               feature allows the printer to automatically switch to D               another input tray containing the same size media whenH               the current tray becomes empty. This feature is enabled by               default.  C               If you currently use colored flag pages, you may wanttF               to disable this feature. To disable input tray failover,*               perform the following steps:  <               1. Edit LPS$SUPPORT:LPSDEFAULTS.<printer name>  6               2. Search for the /TraySwitch parameter:  D                    /TraySwitch true  % Controls input tray failover.6                                      % false = disable4                                      % true = enable  B               3. Change the value of the TraySwitch parameter fromE                  "true" to "false". PostScript is case sensitive; the 9                  only valid values are "true" or "false".   D                    /TraySwitch false % Controls input tray failover.6                                      % false = disable4                                      % true = enable  H                                       Printer-Specific Information 10-11    t            C            4. Enable the changes by issuing the reconfigure command /               from the remote console facility.n  .               $ MCR LPS$CONSOLE <printer name>               LPS> PRIV:"               Password: <password>               LPS> RECONFIGt               LPS> EXIT   D            Refer to the DEC PrintServer Supporting Host Software for?            OpenVMS Management Guide for additional information.         10.14 HP 9085 MFP        10.14.1 IP Requirements  B            To print to this printer with LPD, you must enable DCPS)            spooling. (See Section 3.5.5.)m  ;            To print to this printer with Raw TCP, you must:i  E            o  Enable the Direct Queue on the printer. The port number                is 9101.  B            o  Apply patch number 1-FBSB1 to the printer, available               from HP.  =            o  Define the logical name DCPS$queuename_NO_SYNC.   !      10.15 HP Color LaserJet 4650   -      10.15.1 Printer Fails with Service Errori  C            When printing certain PostScript files, this printer canrC            fail with a 49.4C02 service error. This problem has beenr?            fixed in printer firmware version 20050524 07.003.3.o  !      10.16 HP Color LaserJet 5500e  %      10.16.1 Problems Starting Queuesr  D            This printer does not respond to the DCPS synchronization?            request at the beginning of a job when running olderlB            versions of firmware. Therefore, you should upgrade theC            printer's firmware to at least version 20030605 04.016.2 '            or DCPS jobs will not start.s  '      10-12 Printer-Specific Informationp t  b            H               If you do not upgrade the printer firmware, you can defineC               the logical name DCPS$queuename_NO_SYNC before queues C               to these printers are started. It is also recommended A               that the printer's personality setting be set to PSlF               (PostScript). However, setting the printer's personalityE               to PS (PostScript) alone will not solve the problem forg               this printer.c  $         10.17 HP Color LaserJet 5550  0         10.17.1 Printer Fails with Service Error  F               When printing certain PostScript files, this printer canF               fail with a 49.4C02 service error. This problem has beenB               fixed in printer firmware version 20050524 07.007.3.  &         10.18 HP LaserJet IIID Printer  -         10.18.1 Job Remains in Starting State   D               The DCPS$queuename_NO_SYNC logical name can be used toB               solve reported problems printing to HP LaserJet IIIDF               printers with HP-supplied PostScript Level 2 cartridges.F               Those cartridges have a known problem where they corruptF               status messages they send to a host. This can cause jobsE               to get stuck in the "starting" state when DCPS tries touE               use its synchronization sequence. See Section 3.5.3 forr               more information.r  4         10.18.2 Incorrect Sheet Count on Duplex Jobs  @               The HP LaserJet IIID and several other HP LaserJetB               printers do not internally count physical sheets butH               instead count pages imaged. Therefore the "Sheets printed"A               data of the trailer page will reflect the number of F               images processed. For example, a six-page print job withG               burst and trailer pages enabled and /PARAMETERS=(SIDES=2) E               specified will show "Sheets printed" as eight when only &               five sheets are printed.  '         10.19 HP LaserJet IIISi Printer         H                                       Printer-Specific Information 10-13 m  h            5      10.19.1 Incorrect Sheet Count on Native PCL Jobs   C            The HP LaserJet IIISi printer does not keep track of the A            sheet count while printing native PCL files. The sheet_D            count reported at the end of the job, both on the trailerC            page and to the OpenVMS accounting system, includes onlyoC            those sheets printed in PostScript mode, such as the job B            separation pages. There is no known workaround for this            problem.m  1      10.19.2 Incorrect Sheet Count on Duplex Jobso  C            The HP LaserJet IIISi printer exhibits the same behaviorT<            with sheet count as mentioned in Section 10.18.2.  $      10.20 HP LaserJet 4SiMX Printer  1      10.20.1 Incorrect Sheet Count on Duplex Jobse  C            The HP LaserJet 4SiMX printer exhibits the same behaviorP<            with sheet count as mentioned in Section 10.18.2.  !      10.21 HP LaserJet 5M Printer   -      10.21.1 Problems Selecting an Input Trayc  C            DCPS may ignore explicit INPUT_TRAY parameter values for C            the HP LaserJet 5M printer, instead utilizing paper from B            another input tray. DCPS may also report that TRAY_1 isB            not available, even though the tray is a standard tray,             when tray 1 is empty.  >            Both classes of problems are related to the printer>            attempting to select an alternate input tray if theB            desired tray is empty or otherwise not satisfactory. ToA            avoid these problems, use the HP 5M console to specifytB            that tray 1 is a "cassette" and to lock out all but oneD            of the available input trays. Refer to the printer's user'            manual for more information.   1      10.21.2 Incorrect Sheet Count on Duplex Jobsl  E            The HP LaserJet 5M printer exhibits the same behavior withp7            sheet count as mentioned in Section 10.18.2.   '      10-14 Printer-Specific Information  o  t            '         10.22 HP LaserJet 5SiMX Printers  3         10.22.1 Job Trailer Pages Print in Next Bino  E               If the network manager has placed the mailbox bins into D               "job separator mode" using the administration softwareE               supplied with the printer, the DCPS job log and trailergE               pages print in the next bin, separated from the rest ofy               the job.  F         10.22.2 Tray Is Not Available Due to Lack of Memory for Loaded                 PaperC  F               If an input tray is loaded with a paper size that cannotD               be printed with the current memory configuration, DCPSF               reports the tray as not available. (Refer to the HP5SiMX5               users's guide for memory requirements.)n  E         10.22.3 Duplex Not Supported Due to Lack of Memory for Loaded                  Paperr  @               If an input tray is loaded with a paper size which?               cannot be printed in duplex mode with the currentnC               memory configuration, DCPS reports that duplex is notnG               supported. (Refer to the HP5SiMX users's guide for memorya               requirements.)  4         10.22.4 Incorrect Sheet Count on Duplex Jobs  F               The HP LaserJet 5SiMX printer exhibits the same behavior?               with sheet count as mentioned in Section 10.18.2.   '         10.23 HP LaserJet 2100 and 2200r  (         10.23.1 Problems Starting Queues  @               Some models in this series may not allow DCPS jobs?               to start. To resolve this, either set the printere>               to PostScript mode or suppress DCPS's PostScriptG               synchronization. See Section 11.1.1 for more information.   -         10.24 HP LaserJet 4000, 4050 and 5000       H                                       Printer-Specific Information 10-15    m            %      10.24.1 Minimum Firmware Version   @            To use an HP LaserJet 4000 or 5000 printer from DCPS,A            the printer must be running a minimum firmware versionpB            of 19980714 MB3.68. To use an HP LaserJet 4050 printer,B            it is recommended that the printer be running a minimumC            firmware version of 19991030 MB6.30. Earlier versions oftD            firmware may cause problems such as misprinted or missingE            characters when using the DCPS ANSI translator, especiallyoC            when printing jobs with landscape orientation or NUMBER_ D            UP. This firmware version number is displayed as Firmware8            Datecode on the printer's configuration page.  C            If your printer is running an older version of firmware, =            contact HP and request the proper version. The new9B            firmware will be sent on a SIMM to be installed in your            printer.   $      10.25 HP LaserJet 4200 and 4300  %      10.25.1 Problems Starting Queues_  D            These printers do not respond to the DCPS synchronization?            request at the beginning of a job when running olderfB            versions of firmware. Therefore, you should upgrade theC            printer's firmware to at least version 20030530 04.047.2o'            or DCPS jobs will not start.C  E            If you do not upgrade the printer firmware, you can defines@            the logical name DCPS$queuename_NO_SYNC before queues@            to these printers are started. It is also recommended>            that the printer's personality setting be set to PSC            (PostScript). However, setting the printer's personalitymB            to PS (PostScript) alone will not solve the problem for            these printers.  $      10.26 HP LaserJet 4250 and 4350  -      10.26.1 Printers Fail with Service Errorn  E            When printing certain PostScript files, these printers can C            fail with a 49.4C02 service error. This problem has been ?            fixed in printer firmware version 20050831 08.009.3.     '      10-16 Printer-Specific Informationa W  e            -         10.27 HP LaserJet 8000, 8100 and 8150C            10.27.1 Optional Mailbox  G               DCPS numbers the optional mailbox bins on the HP LaserJet A               8000 printer from 1-5, 1-7 or 1-8, depending on theYB               particular option installed. This is consistent withF               the numbers molded into the plastic beside the bins. TheG               printer's console, in contrast, refers to these same binsPH               as numbers two through nine. Refer to the HP LaserJet UserE               Guide for your printer model for more information abouttG               the numbering and purpose of trays with different optionsl!               and configurations.T  (         10.27.2 Problems Starting Queues  @               Some models in this series may not allow DCPS jobs?               to start. To resolve this, either set the printer/>               to PostScript mode or suppress DCPS's PostScriptG               synchronization. See Section 11.1.1 for more information.   (         10.27.3 Minimum Firmware Version  >               To use a HP LaserJet 8000 printer from DCPS, theC               printer must be running a minimum firmware version ofrH               19980610 MB4.28. This firmware version number is displayedG               as Firmware Datecode on the printer's configuration page.   F               If your printer is running an older version of firmware,@               contact HP and request the proper version. The newE               firmware will be sent on a SIMM to be installed in your1               printer.           10.28 HP LaserJet 9050  0         10.28.1 Printer Fails with Service Error  F               When printing certain PostScript files, this printer canF               fail with a 49.4C02 service error. This problem has beenB               fixed in printer firmware version 20050617 08.102.2.  /         10.29 HP LaserJet 9055 MFP and 9065 MFP       H                                       Printer-Specific Information 10-17                 -      10.29.1 Printers Fail with Service Error   C            When printing certain PostScript files, this printer can C            fail with a 49.4C02 service error. This problem has been ?            fixed in printer firmware version 20050601 07.004.0.         10.30 HP XL300 Printer   "      10.30.1 Communication Problem  C            If a file printed to the XL300 printer contains multiplevC            userdata messages that are returned in quick succession, @            some messages may be lost, and others returned incor-D            rectly. Also, messages that the DECprint Supervisor wantsB            returned to it will occasionally get garbled. This willA            result in spurious messages to the user's terminal (if @            /NOTIFY is set). Otherwise, the job prints correctly.  $      10.31 Lexmark Optra Rt+ Printer  (      10.31.1 Tray Linking and INPUT_TRAY  A            If tray linking is enabled by the printer console, the_A            linked trays cannot be selected individually using theoB            INPUT_TRAY parameter. Specifying any linked tray in theB            INPUT_TRAY parameter causes the printer to select amongA            the linked trays in accordance with its own algorithm.n  0      10.32 Lexmark Optra S, Optra T and T Series  %      10.32.1 Problems Starting Queues   C            Some models in the Lexmark Optra S, Optra T and T series D            may not allow DCPS jobs to start. To resolve this, either@            set the printer to PostScript mode or suppress DCPS'sB            PostScript synchronization. See Section 11.1.1 for more            information.u        10.33 Tektronix Phaser_  +      10.33.1 Printer Configuration Settingsn  @            You must change the following AppSocket settings when+            using Phaser printers with DCPS:   '      10-18 Printer-Specific Information  a               H               Table_10-3_Tektronix_Phaser_Configuration_Settings________  H               AppSocket_Setting_______Value_____________________________  0               Interpreter or          PostScript               Language  H               Filtering_______________Interpreter-Based_________________  :         10.34 Xerox Phaser 4500, 6250, 7300, 7750 and 8400  #         10.34.1 Protocols Supportedy  A               To print to these printers over TCP/IP, use the LPD E               protocol. Because the printers do not return end-of-jobeD               information to DCPS, it is not possible to use the RawH               TCP protocol with these printers. Jobs printed via Raw TCPG               will stall after the job is printed and may eventually be                put on hold.                                                    H                                       Printer-Specific Information 10-19    n                  H                                                                       11H         ________________________________________________________________  H                                               Troubleshooting Procedures      B               This chapter contains troubleshooting procedures for@               diagnosing error conditions on the printer system.  ?               When a printer problem occurs, information may bekG               displayed on the user's terminal if the /NOTIFY qualifier E               is included on the PRINT command line. This informationv4               may indicate the cause of the failure.  H               Check the job trailer page from the print job, which showsF               some of the messages that result from printing. ProblemsE               with the print files are indicated on a file error page                 (see Section 6.7).  H               When a printing system problem occurs, examine the consoleH               output or the OPERATOR.LOG file for operator communicationG               manager (OPCOM) messages. If your terminal is not runningwC               OPCOM, use REPLY/ENABLE to enable PRINTER and CENTRAL B               messages. Restart the symbiont, and reprint the job.E               Then you can read the relevant messages. This procedurerF               requires OPER privileges. Printer messages are listed in$               the DCPS User's Guide.  ?         11.1 What to Do if a Raw TCP/IP Printer is Not Printinge  B         11.1.1 Job Remains in Starting State for Raw TCP/IP or LAT                Queue  E               Most printers respond to the PostScript synchronization F               command at the beginning of a DCPS job, but some do not.F               If all jobs to a queue remain in the Starting state, you:               may need to take one of the following steps:  0               o  Change Printer Language Setting    H                                          Troubleshooting Procedures 11-1    _            C               Often, setting the printer's language-sensing mode to3D               PostScript, instead of auto-sensing between PostScriptD               and PCL, will solve the problem. Refer to your printerE               documentation for instructions on changing the languageiD               for the appropriate port. This is the preferred method'               for avoiding the problem.s  )            o  Define NO_SYNC Logical Nameu  B               If the problem is not solved by changing the printer?               setting, you can tell DCPS to skip the PostScripteB               synchronization command by defining the logical name>               DCPS$queuename_NO_SYNC and restarting the queue.=               This works with printers that use raw TCP/IP oriA               LAT connections on built-in Network Interface Cards D               (NICs). It has no effect when using printers connectedA               via other interconnects. See Section 3.5.3 for more                information.  >      11.1.2 Job Remains in Starting State for Raw TCP/IP Queue  <            If you set up a DCPS queue that uses a raw TCP/IPB            connection and specify an incorrect TCP port number forC            the printer, any print jobs that you submit to the queue A            will remain in a starting state. DCPS cannot determine_C            that you have provided an incorrect port number, because D            the network failure that it receives is no different than3            if the printer had been busy or offline.n  D            Note that a print job in a raw TCP/IP queue may remain in6            a starting state for other reasons as well.  <            Check the documentation for your printer, network>            interface card, print server, or terminal server to@            determine the correct TCP port number to use. The TCP7            port number may also be listed in Table 3-2.   8      11.1.3 Connection Terminations for Raw TCP/IP Queue  D            You may get CONTERMINATED errors for long print jobs whenC            using raw TCP/IP connections. For jobs that consist of a,C            single file or only use the native PostScript capability D            of the printer (for example, they do not use native PCL),B            these errors are most likely to occur at the end of theC            job, with job trailer pages (if specified for the queue) @            and print job accounting (if enabled) being lost. For  $      11-2 Troubleshooting Procedures n  e            E               other jobs, these errors may occur in the middle of theoC               job, with subsequent documents as well as the traileriH               pages and accounting information being lost. DCPS requeuesE               the terminated jobs, placing them in a Holding state so.H               that you can reprint them once you resolve the termination               problem.  E               Some network devices, including the HP JetDirect cards,cG               drop a TCP/IP connection if they do not receive any input E               from the host system within a specified amount of time.iC               This is a feature meant to prevent host software fromTC               monopolizing the device. DCPS, however, waits for thelH               printer to acknowledge that previous documents are printedC               before switching from PostScript to some other nativeuF               printer language and also before printing a trailer pageC               and gathering accounting information. Even though the C               printer may be busy, the NIC may not receive any more <               input from DCPS before the timeout is reached.  E               If your NIC allows you to alter the TCP/IP idle timeout E               value, you can work around this problem by disabling or E               increasing the timeout. Check your NIC documentation to C               determine if this is possible, and how to do it. Then D               release any requeued jobs for which desired output was7               lost, and delete the other requeued jobs.r  G               Note that it is the length of a job in time (versus size) E               that is important. For example, a very small PostScriptTF               program can take a very long time to print. Hence, it isC               difficult to predict how large a timeout is adequate.c  D         11.1.4 NOT_READY Warnings for Unavailable Raw TCP/IP Printer  D               If a job is queued to a printer that uses a raw TCP/IPF               connection, and the printer is busy or offline, you will=               get NOT_READY warning messages for the printer.   G               If you believe or determine that the printer is busy, youcD               can ignore these messages. DCPS cannot, unfortunately,G               differentiate between the printer being busy, offline, orN$               otherwise unavailable.        H                                          Troubleshooting Procedures 11-3 a               6      11.2 What to Do if an LPD Printer is Not Printing  *      11.2.1 No Output Printed from LPD Job  @            If you do not get any printed output after an LPD job<            completes, it could be the result of a PostScriptA            error not reported by the printer. Because LPD is uni-n@            directional, DCPS cannot report a PostScript error to@            the user as it can with other protocols. To assist inC            determining the cause of the problem, turn on PostScriptMB            error reporting on the printer. (Refer to the printer's+            documentation for instructions.)e  A            Common causes of PostScript errors on LPD printers are A            missing or incorrect values for the DCPS logical names E            DCPS$SHEET_SIZE, DCPS$queue-name_SHEET_SIZE or DCPS$queue- +            name_PRODUCT_NAME logical names.   @            Receiving no output may also be caused by the printerA            expecting file size information before the job is sente@            to the printer. This problem often occurs with largerC            multi-function devices. If you suspect this might be theoD            problem, define the logical name DCPS$queue-name_SPOOL to$            enable DCPS LPD spooling.  /      11.2.2 LPD Queue Stops and Job Put on Holdo  E            If you set up a DCPS queue that uses an LPD connection andeD            specify an incorrect internal queue name for the printer,C            or omit one when it is required, any print jobs that you E            submit to the queue will be put on hold and the queue will 9            stop. The following message will also be seen:e  J                %DCPS-F-LPDTERMINATED, LPD connection abnormally terminatedN                -DCPS-I-JOB_ID, for job S (queue SNOBALL, entry 866) on SNOBALL  G                %%%%%%%%%%%  OPCOM  19-SEP-2003 12:12:48.88  %%%%%%%%%%%s1                Message from user SYSTEM on FUNYET Y                Queue SNOBALL: %DCPS-F-LPDTERMINATED, LPD connection abnormally terminated   <            Check the documentation for your printer, network=            interface card, print server or terminal server top@            determine the correct internal queue name to use. SeeE            the Section 3.3.2.2 section of this manual for informationo%            about creating LPD queues.   $      11-4 Troubleshooting Procedures                 F                 ________________________Note  ________________________  C                 Most printers do not require an internal queue namePA                 to be specified when creating an LPD print queue.a  E                 _____________________________________________________u  E               Although an incorrect or missing internal queue name is H               the most common cause, this error can also occur after theE               line printer daemon (LPD) on the printer or remote host D               establishes a connection but rejects the print job for               some reason.  @         11.3 What to Do if a PrintServer Printer Is Not Printing  ?               The following troubleshooting procedures can helpiA               you diagnose error conditions that can occur duringn>               installation of DECprint Supervisor software for#               PrintServer printers.t  G               If the printer is not printing, check the OPCOM messages.tF               If the cause of the failure is not immediately apparent,:               check the queue characteristics, as follows:  F               1. Execute the following instruction, inserting the name1                  of the PrintServer device queue:-  -                  $ SHOW QUEUE queue-name/FULL   ?                  For example, the queue characteristics for thenF                  PrintServer device queue LPS40$FANG on node VIPER are                  as follows:  -                  $ SHOW QUEUE LPS40$FANG/FULL   R                  Printer queue LPS40$FANG, on VIPER::FANG, mounted form DCPS$$FORM                   (stock=DEFAULT)Z                      /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT /LIBRARY=DCPS_LIB /OWNER=[SYSTEM]Y                      /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) -                      /SEPARATE=(FLAG,TRAILER)                   $  @               2. If the queue characteristics do not match thoseF                  recorded in DCPS$STARTUP.COM, delete the device queueF                  and all generic queues that point to it. Then executeF                  the DCPS$STARTUP.COM file. DCPS$STARTUP is located in+                  SYS$STARTUP:. For example:e  H                                          Troubleshooting Procedures 11-5 L  r            0               $ STOP/RESET/QUEUE generic-queue-15               $ STOP/RESET/QUEUE other-generic-queuesn-               $ STOP/RESET/QUEUE pserver-name,,               $ DELETE/QUEUE generic-queue-11               $ DELETE/QUEUE other-generic-queueso)               $ DELETE/QUEUE pserver-namet)               $ @SYS$STARTUP:DCPS$STARTUPi  D               Recheck the queue characteristics. If they are correct@               and the job still does not print, refer to the DEC>               PrintServer Supporting Host Software for OpenVMS7               Management Guide for further information.   8      11.4 What to Do if a Serial Printer Is Not Printing  B            When you examine the OPCOM messages, look for a message=            from the printer indicating NOTREADY. This messagetB            indicates that the printer is unable to acknowledge any<            queries from the system. Check for the following:  0            o  Faulty communication line or cable  .            o  Incorrect port baud rate setting  ?            o  Incorrect switch settings or front panel settingst  B            o  Excessive line noise resulting in lost response from               the printer   %            o  No power to the printerL  =            o  Faulty connector or incorrect type of connectors  A            o  Incorrect bits/character, incorrect parity, or bothi  A      11.4.1 What to Do if a Locally-Connected Serial Printer WillS             Not Start Printing  E            The steps in this section apply to any serial printer on a1            local line.  $            Step 1: Print a test page  @            Manually print a test page on your printer, following/            instructions in your owner's manual.   $      11-6 Troubleshooting Procedures                 D               If able to print a test page, go on to step 2 to checkF               the printer hardware and software configurations. If theE               printer does not produce a test page, check the printerw               hardware.   !               o  Is the power on?r  (               o  Is the printer on line?  8               o  What is the status of the print engine?  =               Step 2: Check the printer hardware and software                configurations  B               The configuration settings on the printer and in theD               software associated with the printer must be the same.H               To verify that the settings match, check a printed summaryE               sheet or the printer console or switches to verify thatbE               the settings are consistent for the following settings:s                 o  Paper sizeR  D               o  Communication: 9600 baud (or appropriate baud rate)  1               o  Eight bits, no parity (required)r                 o  Flow control   H               Refer to the printer owner's manual for information on how'               to change these settings.h  F               Check the terminal device characteristics of a directly-G               connected serial printer by issuing the following command (               on the node of the device:  ,               $ SHOW TERMINAL device-name[:]  H               The variable device-name is the device name in the printerA               startup file in parameter P2 of the execution queuee               definition.   6               Check for the following characteristics:                 o  Eight bitst                 o  Parity: Nonen  '               o  Input speed: 9600 baudv  (               o  Output speed: 9600 baud  H                                          Troubleshooting Procedures 11-7 L               D            The summary sheet and the terminal settings should be the            same.  D            If your printer interface runs at a different speed, makeB            sure you set the same configuration switch settings and"            device characteristics.  B            If the printer is connected directly to the host, checkE            the baud rate setting in the printer startup command file. B            If you did not enter a baud rate in parameter P6 of theA            execution queue definition, the startup procedure setseD            the printer speed at 9600 baud. Refer to the SET TERMINALC            command in the HP OpenVMS DCL Dictionary for information @            on changing the system's interpretation of the device            characteristics.n  B            If your printer is connected by a LAT device to a local-            area Ethernet, see Section 11.4.3.h  E            If the settings agree and the job still does not print, gon            to step 3.   0            Step 3: Check communications software  @            Test the operation of the communications equipment by=            attempting to send data directly to the device. To @            perform this procedure, make sure the queue is paused            (see Section 5.7).   <            The device must not be spooled to accomplish thisC            procedure. If the device is spooled, enter the followinge            command:   (            $ SET DEVICE LTAnnnn:/NOSPOOL  C            To test the communications setup, issue the SET HOST/DTEnD            command to the printer. Use the commands in the following            examples:  "            $ SET HOST/DTE LTA9092:2            Connection established, type ^\ to exit            Ctrl/T             %%[ status: idle ]%%r  B            After you press Ctrl/T, you should receive a message in            the form ofB            %%[Status: description]%%. If you receive this message,D            the connection to the printer is established and working.  $      11-8 Troubleshooting Procedures                 @               If no message of this type is displayed, enter the0               commands in the following example:                 ^\!               $ COPY TT: LTA9092:                showpage               Ctrl/Z               $   G               The test is successful if a page of paper is ejected from D               the printer. If no paper is ejected, there is a faultyB               connection with the printer. In this case, check theG               communications cables. Then try the commands in the first-               example again.  D               If the COPY command succeeds, but the SET HOST commandE               fails, check the communications cables inbound from the ?               printer to the host node for a faulty connection.I  ,               Step 4: Check DCPS$STARTUP.COM  D               Make sure that the DCPS$STARTUP.COM file reflects yourD               print queue needs and that the changes are appropriateD               for your printer. To check the printer execution queueE               characteristics, enter the following command, insertingi6               the name of the printer execution queue:  /               $ SHOW QUEUE/FULL exec-queue-namen  H               For example, the characteristics for the printer execution;               queue TXA1_LN03R on host EDEN are as follows:   *               $ SHOW QUEUE/FULL TXA1_LN03R  7                Printer queue TXA1_LN03R, on EDEN::TXA1:eT                /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT /LIBRARY=DCPS_LIB /OWNER=[SYSTEM]S                /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE)S(                /SEPARATE=(BURST,TRAILER)               $C  0               Specifically, check the following:  4               o  Make sure that /PROCESSOR=DCPS$SMB.  >               o  Check that /FORM=DCPS$DEFAULT, or matches theF                  changes you made to DCPS$STARTUP.COM. Ensure that theE                  printer is capable of printing according to the form                   definition.  H                                          Troubleshooting Procedures 11-9 a  e            @            o  Make sure that the /LIBRARY qualifier value is theE               same as parameter P3 in DCPS$STARTUP.COM and if it is a C               logical name, that the logical name has been defined.   E            If the queue characteristics do not match those defined in >            DCPS$STARTUP.COM, stop the printer execution queue.  ?            Next, execute the DCPS$STARTUP.COM file, as follows:   &            $ @SYS$STARTUP:DCPS$STARTUP  >            Recheck the execution queue characteristics. If theA            characteristics are correct and the job still does not             print, go to step 5.   1            Step 5: Check queue logical defaulting   A            Use the following command to check the values of queue D            default parameters in the DCPS$STARTUP.COM file, in P4 ofE            the execution queue definition, and in parameter P3 of the $            generic queue definition.  2            $ SHOW LOGICAL DCPS$queuename_PARAMETER  1            Step 6: Check the queue configurations   C            The values you provide in DCPS$STARTUP.COM are validatedsA            by DCPS for syntax only. Then the values are passed tolE            the appropriate OpenVMS utility and those utilities reportrD            any further errors. Refer to OpenVMS documentation or useE            the HELP /MESSAGE utility for more information about errore.            messages by these OpenVMS commands:              o  INITIALIZE /QUEUE               o  SET DEVICE              o  SET TERMINAL  C               ________________________Note ________________________I  <               To debug DCL command procedures and record the>               information in a file, you can use the following               commands:   8               $ SET HOST hostname /LOG [/LAT | /TELNET ]               $ SET VERIFY  <               Alternatively, you can set parameter P8 in the?               execution queue definition in DCPS$STARTUP.COM toM  %      11-10 Troubleshooting Procedures  l  o            *                 1 for automatic recording.  E                 _____________________________________________________   C         11.4.2 What to Do if a Locally-Connected Serial Printer Has-                Stopped Printing9  C               When your printer stops printing, follow these steps:J  H               o  If your printer fails consistently, follow the steps in                   Section 11.4.1.  H               o  If your printer fails occasionally, follow the steps in                  this section.  E               After checking all messages, including the notificationsF               messages from the PRINT command, the console output, andH               the OPCOM log, go to step 1 if the cause of the problem is               not apparent.   /               Step 1: Print the IVP data sheets   E               Print the following Installation Verification Procedure09               (IVP) files from SYS$COMMON:[SYSTEST.DCPS]:0  "                  DCPS$IVP_ANSI.DAT"                  DCPS$IVP_POST.DAT#                  DCPS$IVP_REGIS.DATP%                  DCPS$IVP_TEK4014.DATn!                  DCPS$IVP_PCL.DAT1(                  DCPS$IVP_PROPRINTER.DAT  H               Remember to use the appropriate DATA_TYPE parameter value,B               indicated in the file name following the underscore,D               for each of the files. For example, to print DCPS$IVP_9               REGIS.DAT, use the following PRINT command:n  D               $ PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=REGIS)-A               /NOTIFY SYS$COMMON:[SYSTEST.DCPS]DCPS$IVP_REGIS.DAT   E               If the files are not printed, go to step 2 to check thed#               files for user error.   F               If any of the IVP files are not printed, check to see ifG               the translator execution files exist, using the followingt               command:  H                                         Troubleshooting Procedures 11-11 i  r            "            $ DIR SYS$SHARE:TRN$*.*  (            Directory SYS$COMMON:[SYSLIB]  F            TRN$ANSI_PS.EXE;     TRN$DDIF_PS.EXE;     TRN$REGIS_PS.EXE;K            TRN$TEK4014_PS.EXE;  TRN$PCL_PS.EXE;      TRN$PROPRINTER_PS.EXE;               Total of 6 files.  :            If the correct files are present, go to step 2.  ;            If any files are missing, reinstall the DECprintp            Supervisor software.   -            Step 2: Check files for user errorr  C            If a particular file fails to print, examine the traileroA            page from the print job for messages that indicate thedD            cause of the failure. For an explanation of, and recoveryA            procedures for the error messages, see the DCPS User'se            Guide.   ?            If the file is a PostScript file, an error exists in @            either the PostScript file or in the application that?            generated the PostScript file. If the application is A            supplied by HP, contact the HP Customer Support Center0'            and submit a problem report.   @            If the file is other than a PostScript file, an errorB            exists in the translation process. If the translator isE            supplied by HP, contact the HP Customer Support Center anda#            submit a problem report.n  A            Sometimes, when the serial communication cable betweenm=            the printer and the host is disconnected and later @            reconnected, the active print job displays the statusD            Printing when nothing is happening at the printer. Power-?            cycle the printer, then resubmit the lost print job.a  C               ________________________Note ________________________o  A               When reconnecting the printer to the host, turn offa?               and then turn on the printer. Turning the printers?               off and on ensures proper synchronization betweenn1               the print symbiont and the printer.   C               _____________________________________________________   %      11-12 Troubleshooting Proceduresf a  n            :         11.4.3 What to Do if a LAT Printer Is Not Printing  E               A network environment allows several separately managed E               systems to access the same printer. Therefore, when the H               printer is not printing, you must determine which node has%               control of the printer.m  C               The remaining sections discuss the following steps insC               troubleshooting the printer in a network environment:s  @               1. Determining the node that controls the printer:  /                  o  Determine the printing nodea  8                  o  Determine the LAT node and port name  :                  o  Check the port and system server names  >                  o  Determine the host controlling the printer  -               2. Troubleshooting the printer:   .                  o  Check port characteristics  7                  o  Follow procedures in Section 11.4.1l  -               3. Other troubleshooting hints:   #                  o  NOTREADY statusP  C                  o  Common error messages and their probable causes   A         11.4.3.1 How to Determine Which Host Controls the Printerb  D               A network printer may fail to print if another node isB               accessing the printer, or if the printer has stoppedF               printing. Perform the following steps to determine which.               host has control of the printer.  2               Step 1: Determine your printing node  B               To determine which node runs your printer, issue theF               following command, inserting the name of the print queue               you use:  *               $ SHOW QUEUE/FULL queue-name  F               From the first line of the following sample display, youE               determine that FIERY is the node that runs your printer D               and LTA546 is the application port associated with the               print queue:  H                                         Troubleshooting Procedures 11-13 h  p            L            Printer queue LN03R3, on FIERY::LTA546, mounted form DCPS$DEFAULTP                                                                  (stock=DEFAULT)B                /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT (stock=DEFAULT)L                /NOENABLE_GENERIC /LIBRARY=DCPS_LIB lowercase /OWNER=[SYSTEM]S                /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE)o(                /SEPARATE=(BURST,TRAILER)            $  B            Perform steps 2 and 3 on the node (FIERY) that runs the            printer.i  @            Step 2: Determine LAT node and port name to which the            printer is connecteds  F            Look in the LAT startup file SYS$STARTUP:LAT$SYSTARTUP.COM.?            The SET PORT command associates the application porti?            (LTAd) with a specific port (/PORT=port_name) on the0(            server (/SERVER=server_name).  L            CREATE PORT LTA546: /NOLOG  /APPLICATION                 ! LN03R3I            SET PORT LTA546: /APPLICATION /QUEUE /NODE=TAS204 /PORT=PORT_7e  C               ________________________Note ________________________i  @               The port must be set with queuing enabled (/QUEUE)8               and as an application port (/APPLICATION).  G               Make sure that SYSTARTUP_VMS.COM invokes LAT$STARTUP.COM.v  C               _____________________________________________________   5            Step 3: Check port and server system namesr  C            Ensure that port and server system settings are the samegA            as those in the SYS$STARTUP:LAT$SYSTARTUP.COM. Use thetB            LATCP SHOW PORT command to look at the application port            (LTAd) as follows:1  !            $ RUN SYS$SYSTEM:LATCP0            LCP>SHOW PORT lta54601            Local Port Name = LTA546:  application   0              Specified Remote Node Name = TAS2040              Specified Remote Port Name = PORT_7-              Actual Remote Node Name = TAS204i-              Actual Remote Port Name = PORT_7.!              Link Name = LAT$LINK5  %      11-14 Troubleshooting Procedures                  ?               Step 4: Determine which host controls the printer.  B               You can determine which host controls the printer byD               logging in to a terminal that is connected directly toC               a DECserver or by connecting to a LAT device over the G               network. If you have direct access to the DECserver port, %               go directly to step 4B.   0               Step 4A: Connect to the LAT device  F               Use either the Network Control Program (NCP) or TerminalE               Server Manager (TSM) to connect to the DECserver deviceo               over the network.a  7               To use NCP, issue the following commands:   F               o  To determine the type of service circuit, for example<                  UNA-0 or QNA-0, use the following commands:                    $ MCR NCP)                  NCP> SHOW KNOWN CIRCUITSR  G               o  To determine the 48-bit Ethernet address (for example,y@                  08-00-2B-05-C7-05), use the following commands:                    $ MCR LATCP+                  LCP> SHOW NODE server-namea  I                  For example, to get the Ethernet address for TAS200PSSA,s-                  enter the following command:l  *                  LCP> SHOW NODE TAS200PSSA  W                  Node Name:   TAS200PSSA                      LAT Protocol Version: 5.1QX                  Node State:  Reachable                       Address: 08-00-2B-05-C7-056                  Node Ident:  LN03R V2.0 DECServer 200  0                  Incoming Connections:   Enabled  0                  Circuit Timer (msec):        800                  Multicast Timer (msec):      30  0                  Service Groups:   15, 31-32  99  G                  Service Name     Status       Rating    Identificationo2                  BURNET           Available      0  H                  In this example, the Ethernet address 08-00-2B-05-C7-05                  is displayed.  H                                         Troubleshooting Procedures 11-15 _  t            C               You can use the service circuit name and the Ethernet D               address to make a connection to the LAT node using the                following command:                 $ MCR NCP Q               NCP> CONNECT VIA service-circuit PHYSICAL ADDRESS nn-nn-nn-nn-nn-nny  E            After entering the NCP CONNECT command, press Return until E            you get the pound sign (#) prompt. At this prompt type the 6            password (ACCESS) to get the Local> prompt:              #            username: usernames            Local>i  +            Step 4B: At the LAT console portr  A            After making your connection and logging in to the LAT.1            console, enter the following commands:                Local> SET PRIVILEGED            Password>&            Local> SHOW SESSIONS PORT_7  *            The default password is SYSTEM.  C            The following example shows a SHOW SESSIONS PORT command_A            on a DECserver 200 that tells you that a remote system "            HAILEY controls port 7.  &            Local> SHOW SESSIONS PORT 7C            Port 7:  (Remote)      Connected       Current Session 1c9            -Session 1: Hailey     Connected       Pasthrui  D            If your system runs the TSM software, issue the following            commands:  $            $ RUN SYS$SYSTEM:TSM$MAIN!            TSM> USE SERVER tas204T            TSM> SET PRIVILEGED            Password>$            TSM> SHOW SESSIONS PORT_7  C               ________________________Note ________________________o  A               To run the TSM program, you need read access to the @               TSM management directory file and OPER privileges.  %      11-16 Troubleshooting Procedures  n  p            D                 For more information, refer to the Guide to Terminal                 Server Manager.u  E                 _____________________________________________________   D         11.4.3.2 How to Troubleshoot Printer Communications Problems  G               After determining which system controls the printer port, !               follow these steps.   0               Step 1: Check port characteristics  D               Compare the LAT port characteristics with those listedG               in the DCPS Software Installation Guide. To view the portsH               characteristics, issue the SHOW PORT command at the Local>(               prompt or the TSM> prompt.  6               Step 2: Use procedures in Section 11.4.1  :               Follow the steps in the appropriate section:  2               o  For a new printer, Section 11.4.1  H               o  For a printer that has stopped printing, Section 11.4.2  C               If you follow these procedures and the printer is not %               printing, go to step 3.   4               Step 3: Regain control of the LAT port  @               You may need to disconnect a symbiont process thatF               controls the port connected to the printer. For example,G               an unsupported version of the symbiont software might not G               disconnect after it gains control of the port. Disconnect >               the symbiont process with the following command:  #               Local> SET PRIVILEGEDm               Password>e,               Local> LOGOUT PORT port_number  H               You need privileged status on the LAT node to execute this               command.  *         11.4.3.3 Common LAT Error Messages  H               The following list contains common error messages receivedC               in a network environment. The error message prefix issF               DCPS$. The severity level is not indicated. The messagesH               are arranged alphabetically by ident-string. (Refer to theG               DCPS User's Guide for an explanation of the error messager               format.)  H                                         Troubleshooting Procedures 11-17                 ?        DCPS$_CONAPPLICATION, Connection request is not to a LATn          applications port  D          Explanation: This message usually occurs when a LAT port isD          not reserved as an applications port, and another device isD          connected to the port that is requested by the printer. The@          LAT configuration file LAT$SYSTARTUP.COM should contain>          a line similar to the following with the /APPLICATION          parameter.t  K          SET PORT LTAnnn:/NODE=server-name/PORT=port-name/QUEUE/APPLICATIONt  D          To avoid this problem, specify a higher port number for the          printer.o  <        DCPS$_CONTERMINATED, Connection abnormally terminated  C          Explanation: This message occurs when communication to the B          LAT node is interrupted. This results in a stopped queue.          Check the following:a  0          o  Power is supplied to the LAT device.  +          o  Printer port is not logged off.u  A          o  All connections from LAT device to the Ethernet cables             are working.  D        DCPS$_CONTIMEOUT, Connection timed out, server not available,+          or incorrect server name specifiede  A          Explanation: This message occurs when the server name isiC          not recognized. This problem may indicate the collision ofi2          user terminal space and the printer port.  B          Verify that the server name connected to the printer portA          is correct. Compare the server name specified in the LAT B          configuration file LAT$SYSTARTUP.COM with the server nameC          on the LAT device. LAT$SYSTARTUP.COM should contain a line "          similar to the following:  K          SET PORT LTAxxx:/NODE=server_name/PORT=port_name/QUEUE/APPLICATIONu  B          Use the SHOW PORT command to find the server name associ-$          ated with the printer port:  #          Local> SHOW PORT port-nameP  %      11-18 Troubleshooting Procedures  u               -          DCPS$_LRJACCESSDENIED, Access deniedt  C             Explanation: This message usually occurs when the groupaB             code specified in LAT$SYSTARTUP.COM does not match oneE             of the groups on the LAT device connected to the printer.sF             Thus, the printer software does not have access to the LATE             port. The LAT configuration file LAT$SYSTARTUP.COM shouldr4             contain a line similar to the following:  ,             SET NODE/GROUP=group-list/ENABLE  G             Compare groups, /GROUP=group-list, set in LAT$SYSTARTUP.COMDA             with those set on the LAT device (SHOW PORT command).o  8          DCPS$_LRJDELETED, Queue entry deleted by server  B             Explanation: This message occurs when someone manually8             terminates the connection to the LAT device.  4          DCPS$_LRJILLEGAL, Illegal request parameter  D             Explanation: This message indicates that an internal LATF             error has occurred. Contact the HP Customer Support Center(             and submit a problem report.  /          DCPS$_LRJINUSE, Port or service in use   G             Explanation: This message usually occurs on a LAT port when D             port-name is not set with the queuing parameter (/QUEUE)D             enabled or when the queue limit is too small. On the LAT0             device, enter the following command:  +             SET PORT port-name QUEUE ENABLEh  3          DCPS$_LRJNAMEUNKNOWN, Port Name is unknown   F             Explanation: This message occurs when the port name speci-G             fied in the LAT configuration file LAT$SYSTARTUP.COM is nothG             known on the server. Compare the port name specified in thePE             LAT configuration file LAT$SYSTARTUP.COM with the printereC             port name associated with the server. LAT$SYSTARTUP.COM ;             should contain a line similar to the following:P  N             SET PORT LTAnnn:/NODE=server-name/PORT=port-name/QUEUE/APPLICATION  A             Find the name of the printer port associated with theI5             server, by issuing the following command:   (             Local> SHOW PORT port-number  H                                         Troubleshooting Procedures 11-19 i               C        DCPS$_LRJNOTOFFERED, Service is not offered on the requestedu
          porti  A          Explanation: This message usually occurs when the access C          mode is not set to REMOTE on the LAT port. Use the SET andrB          DEFINE commands as follows to set the access mode for the          port:  2          Local> SET PORT port-number ACCESS REMOTE5          Local> DEFINE PORT port-number ACCESS REMOTEe  C               ________________________Note _________________________  B               For more information, refer to the DCPS User's GuideB               or to the troubleshooting guide for your LAT device.  C               _____________________________________________________   C      11.4.4 How to Eliminate Excess Login Dialog on Serial Printersm  @            Serial printers transmit unsolicited data to the hostB            system when power-up initialization occurs. The OpenVMS@            operating system normally interprets unsolicited dataA            from a terminal device as a login request. The printern@            software startup file sets the SECURE_SERVER terminalA            characteristic for all printer terminal devices on thedC            host system. SECURE_SERVER prevents the OpenVMS host andtC            the printer from engaging in a potentially endless loginw            dialog.  B            To eliminate login dialog, set terminal characteristicsD            for terminal devices by using the following procedures in            this order:  "            1. SYSGEN AUTOCONFIGURE              2. SYSTARTUP_VMS   &            3. DCPS$EXECUTION_QUEUE.COM  >            AUTOCONFIGURE uses SYSGEN parameters to set defaultC            terminal characteristics for all terminal devices on theiB            system. Your system will not encounter the login dialogB            problem if SECURE_SERVER is set with SYSGEN. The SYSGENB            parameter that accomplishes this is TTY_DEFCHAR2. ReferB            to the HP OpenVMS System Management Utilities Reference?            Manual for information on setting SYSGEN parameters.   %      11-20 Troubleshooting Procedures_ _  _            @               The system startup procedure may also set terminalE               characteristics. Since this command file executes prioreC               to the printer startup file, your system will be less_H               vulnerable to the login dialog problem if SECURE_SERVER isG               set for printer terminal devices within the SYSTARTUP_VMSa               file.   C               DCPS$EXECUTION_QUEUE.COM (the printer execution queue H               command file) sets the SECURE_SERVER terminal characteris-G               tic for printer terminal devices by default. This file isn+               provided in the software kit.o  F               If your printer is configured on a LAT device in a localE               area Ethernet, set the LAT port and the terminal server G               characteristics for the printer to minimize login dialog.eH               Refer to the DCPS Software Installation Guide for LAT port               characteristics.  ;         11.5 What to Do if Printing Is Slower than Expectedc  5               Slower printing speeds can result from:i  @               o  Printing of complex ANSI jobs from applications  4               o  Printing of complex PostScript jobs  @               o  Occurrence of ANSI translator prologue mismatch  F               o  Changing the printer password from the default (refer:                  to the DCPS Software Installation Guide).  F               Complex ANSI jobs include those that use many downloadedF               fonts on a page. These jobs always take longer to print.  H               For serial printers, a 30-second delay before the printingF               of ANSI jobs indicates an ANSI prologue mismatch between@               the ANSI translator and the print job. On a serialH               printer, power cycle the printer (turn it off and then on)H               to load the appropriate prologue. The first ANSI print jobG               is delayed by the loading of the prologue, but subsequenth;               ANSI print jobs are printed more efficiently.U  D               If your printer is connected to multiple nodes runningF               different versions of the printing system, power cyclingD               the printer may not eliminate the 30-second delay. TheH               node that connects to the printer first persistently loadsG               its prologue. The other nodes must load the prologue withEC               every print job. To eliminate the delay in this case,o  H                                         Troubleshooting Procedures 11-21 $  R            A            every node should run the same version of the DECprint             Supervisor software.s  <      11.6 What to Do if Layup Definition Files Are Not Found  C            DECprint Supervisor software places the following samplerB            layup definition files in the location specified by the#            logical name DCPS$LAYUP:                  LPS$HOLES.LUPm!               LPS$SINGLEHOLES.LUP !               LPS$DOUBLEHOLES.LUP                LPS$NUP.LUPh)               COLOR-PRINTER-FULL-PAGE.LUP &               PROPRINTER-FULL-PAGE.LUP  ;            Make sure that the layup directory logical name,cE            DCPS$LAYUP, points to SYS$SYSDEVICE:[SYSHLP.EXAMPLES.DCPS] E            or to the directory that contains the .LUP sample files one$            all nodes in the cluster.  A      11.7 What to Do if Files Are Printed with Unexpected Resultsh  C            The DECprint Supervisor software attempts to print everyc@            file in every print job even if there are problems in>            the specification of print parameters and print jobE            attributes. Print queues with erroneous default parametersiB            can still print files, but all the print parameters areB            not effective and messages are generated indicating the3            problem, as described in Section 11.7.1.   B            In cases where the file is printed using the wrong dataE            type translator, the file data type has not been correctlya>            determined by the DECprint Supervisor software. The@            methods for solving problems with automatic data type5            detection are described in Section 11.7.2.   D      11.7.1 What to Do if Default Queue Parameters Are Not Effective  D            If you enter a parameter in DCPS$STARTUP.COM incorrectly,C            print jobs sent to that print queue are printed, but thefD            invalid parameter and the parameters following it are not$            applied to the print job.    %      11-22 Troubleshooting Proceduresp t  m            D               If an invalid print parameter is included in the queueH               definition, the printing system generates an error messageE               that is displayed on your screen and printed on the jobtE               trailer page for every print job sent to the associatednC               queue. The parameters that are not processed take the,               default settings.   B               In the following example, there is an extra L in theA               argument to the second parameter, PAGE_ORIENTATION.s?               Therefore, the printing system ignores the secondaF               parameter, NUMBER_UP=2. Only the first parameter, SHEET_#               SIZE=B, is processed.d  G               $ @SYS$STARTUP:DCPS$GENERIC_QUEUE -     ! Landscape queue O                    DCPS$WIDE$PRINT -                  ! P1 - Generic queue nametX                    TEK4014_TTB4 -                     ! P2 - /GENERIC = execution queuesH                    "SHEET_SIZE=B,PAGE_ORIENTATION=LANDSCAPE,NUMBER_UP=2"T                                                       ! P3 - Default queue parameter  B               For every print job for this queue, an error messageE               similar to the following is displayed on the screen and E               printed on the job trailer page in the message section:   R               10-JUN-2005 15:21 %DCPS-E-PARSYNERR, Syntax error in the /PARAMETERS=               qualifier at or near PAGE_ORIENTATION=LANDSCAPEd  ?         11.7.2 What to Do if a File Data Type Is Not Recognizeds  D               If the DECprint Supervisor software fails to determineC               the data type of a print file correctly, the user caneG               explicitly specify the DATA_TYPE parameter. If necessary,oE               you can set up a generic queue for specific data types.uE               All files printed to this queue will have the specifiedDE               data type, unless the user explicitly specifies anothereE               data type using the DATA_TYPE parameter. Users can alsorE               specify the DATA_TYPE=AUTOMATIC parameter to explicitlyn4               specify automatic data type detection.  G               The automatic data type feature examines the following to 2               determine the data type of the file:  B               1. The value of the DATA_TYPE parameter in the PRINT                  command  N               2. The queue default data type specified in the DCPS$STARTUP.COM                  file   H                                         Troubleshooting Procedures 11-23    s            C            3. OpenVMS file tags (for example, DDIF stored_semantics                tags)   &            4. The contents of the file               5. The file extension  ?            If the DECprint Supervisor software cannot determinet@            the file data type from these steps, the default text>            data type is used. If no default text data type has>            been defined by the user or the system manager (seeB            Section 4.2.2), the file is processed as ANSI. When the?            default text data type is used, the text can precede A            PostScript; the file is printed properly. However, thetD            file may not be printed properly if any more text followsD            the PostScript data. In this case, it may be necessary toB            edit the file and print the text and PostScript data as            separate files.  @            In general, though, users should not be encouraged toD            modify the contents of their files or the file extensions@            so that the data type can be determined. Instead, theB            application that generates the file may be examined andB            modified if necessary; or you can provide site-specificD            file extension files, default text data types, or generic3            queues with explicit default data types.                                       %      11-24 Troubleshooting Proceduresd o  h                  H                                                                        AH         ________________________________________________________________  H                                      Printing System Management Commands      A               You use standard OpenVMS DCL commands to manage theeB               DECprint Supervisor queues, jobs, and related system               resources.  F                 ________________________Note  ________________________  A                 Remember that the management commands only affects>                 the system on which they are issued. A networkB                 printer can serve other systems as well, with eachA                 system having its own set of queues, jobs, forms,                  etc.  E                 _____________________________________________________   +         A.1 Overview of Management Commands:  G               Table A-1 lists the commands used to manage print queues, G               print jobs, and related system resouces. More information C               for these commands can be found in the HP OpenVMS DCLk               Dictionary.r  H               Table_A-1_Printing_System_Management_Commands_____________  H               Command___________________Function________________________  G               ASSIGN /MERGE             Removes jobs from one queue and E                                         puts them in another existinga.                                         queue.  E               ASSIGN /QUEUE             Assigns a logical queue to an 8                                         execution queue.  E               DEASSIGN /QUEUE           Deassigns a logical queue andd@                                         stops the logical queue.  H                                  Printing System Management Commands A-1                 E            Table_A-1_(Cont.)_Printing_System_Management_Commands_____t  E            Command___________________Function________________________l  C            DEFINE /CHARACTERISTIC    Defines a queue characteristick5                                      name and number.i  A            DEFINE /FORM              Defines a printer form name,r<                                      number, and attributes.  @            DELETE /CHARACTERISTIC    Deletes the definition of a:                                      queue characteristic.  D            DELETE /ENTRY             Deletes one or more job entries2                                      from a queue.  @            DELETE /FORM              Deletes the definition of a*                                      form.  5            DELETE /QUEUE             Deletes a queue.a  E            INITIALIZE /QUEUE         Not recommended for use with theHB                                      DECprint Supervisor software.  E            SET ENTRY                 Changes or deletes attributes of C                                      a job that is in the queue but =                                      not currently executing.   ;            SET QUEUE                 Changes the status and ;                                      attributes of a queue.   E            SET QUEUE /ENTRY          This command has been supersededED                                      by the SET ENTRY command, whichE                                      performs identical functions. HPiD                                      recommends that you use the SET3                                      ENTRY command.d  <            SET QUEUE /RETAIN         Retains print jobs uponE                                      completion or termination due toa.                                      an error.  D            SHOW ENTRY                Display information about print*                                      jobs.  ?            SHOW QUEUE                Displays information about 5                                      queues and jobs.f  E            SHOW QUEUE /CHARACTERISTICDisplays information about queue E                                      characteristic names and numbersg:                                      available on a queue.  ,      A-2 Printing System Management Commands h  r            H               Table_A-1_(Cont.)_Printing_System_Management_Commands_____  H               Command___________________Function________________________  F               SHOW QUEUE /FORM          Displays the names and numbersE                                         of the forms defined for your /                                         system.P  C               START /QUEUE              Starts or restarts a queue.   C               START /QUEUE /MANAGER     Starts the system job queuetC                                         manager and opens the queuee-                                         file.a  B               STOP /QUEUE               Pauses an execution queue.  F               STOP /QUEUE /ABORT        Stops the executing print job,D                                         but does not stop the queue.  B               STOP /QUEUE /MANAGER      Stops the system job queueH                                         manager and closes the job queue-                                         file.   A               STOP /QUEUE /NEXT         Stops the queue after thef@                                         current job has finished1                                         printing.r  E               STOP /QUEUE /REQUEUE      Stops the executing print job H                                         and requeues it to the specifiedD                                         queue, but does not stop the.                                         queue.  E               STOP /QUEUE /RESET        Stops a queue immediately andrH               __________________________returns_control_to_the_system.__  (         A.2 Use of SET PRINTER with DCPS  H               Because PostScript printers are controlled by the DECprintE               Supervisor software, the DCL SET PRINTER command has noeE               meaning in a DECprint Supervisor environment. Print joblE               characteristics for the DECprint Supervisor are set and '               displayed by other means.   C               Print job characteristics for DECprint Supervisor are                determined by:  4               1. Parameters embedded in the job data  F               2. Parameters passed in the /PARAMETERS qualifier of the                  PRINT command  H                                  Printing System Management Commands A-3 h  i            %            3. DEFINE /FORM qualifiers   D            4. For PrintServer printers, default parameters which are7               in the PrintServer configuration databasen  D            5. The default queue parameters, which are defined in the#               DCPS$STARTUP.COM filem  ?            Items 1, 2, and 3 in this list are controlled by the @            PostScript interpreter or the data syntax translator,B            depending on the type of job being processed. Item 4 isD            controlled by the PrintServer server management interfaceD            described in the DEC PrintServer Supporting Host Software(            for OpenVMS Management Guide.  =            Table A-2 shows the SET PRINTER qualifiers and thet?            equivalent control in a DECprint Supervisor printing             system.                                                      ,      A-4 Printing System Management Commands _  _            F               Table A-2 SET PRINTER Qualifier Equivalents for DECprintH               __________Supervisor_Queues_______________________________                 SET PRINTERsH               Qualifier_____Equivalent_Control__________________________  C               /CR           Insertion of carriage return charactersmB                             is controlled by the current data type'                             translator.d  @               /FALLBACK     Translation of DIGITAL multinationalC                             characters is controlled by the currentnD                             font. If the character does not exist inH                             the specified font, the font error character#                             prints.a  C               /FF           Mechanical form feeds are controlled bylC                             the current data type translator or the 3                             PostScript interpreter.   >               /LOWERCASE    The DECprint Supervisor printer isD                             considered to be a lowercase printer. ItF                             does not translate lowercase to uppercase.  D               /PAGE         The number of lines printed on each page@                             is controlled by the ANSI translatorE                             (ANSI files only). This characteristic iss;                             available through DEFINE /FORM.o  A               /PASSALL      Whether the system interprets special G                             characters or forwards them as 8-bit binaryrG                             data is controlled by the current data typem'                             translator.e  B               /PRINTALL     Whether the printer interprets specialC                             characters or prints their 8-bit binary,H                             equivalent is controlled by the current data,                             type translator.  ?               /TRUNCATE     Truncation of data that exceeds the F                             limitation imposed by the /WIDTH qualifierG                             is controlled by the form definition or ther9                             current data type translator.   D               /WIDTH        The number of characters allowed on eachA                             line of the currently installed media/D                             is controlled by the form definition, orB                             a combination of the current data type<                             translator and the current font.  E               /WRAP         Generation of a carriage-return/line-feedrG                             by the printer when it reaches the end of a H                             line PrintingoSystemyManagementdCommandsnA-5H               ______________the_current_data_type_translator.___________ e  p            C               ________________________Note ________________________   9               Not all data type translators implement the @               preceding functions in the same manner; refer to aA               translator's documentation for specific informatione!               about its behavior._  C               _____________________________________________________s                                                                          ,      A-6 Printing System Management Commands S  A                  H                                                                        BH         ________________________________________________________________  H                                               Logical Names Used by DCPS      C               This appendix provides some information about OpenVMS H               logical names that are used by the DECprint Supervisor for               OpenVMS software.R  E               Here are some guidelines for using these logical names:P  G               o  Any logical whose name begins with "DCPS" is only used C                  by the DECprint Supervisor software. Other logical E                  names (for example, PSM$ANNOUNCE) may be used by anda@                  impact other components of your OpenVMS system.  D               o  You should place your desired definitions for theseG                  logical names in DCPS$STARTUP.COM or in something that H                  it invokes. The startup procedure template has comments3                  about how to define some of these.r  @               o  Changes to some logical names have an immediateA                  effect, while changes to others take effect only D                  when a queue starts or when a DCPS symbiont process@                  is first created. The ramifications of this areH                  particularly significant if you are using multistreamedC                  DCPS symbiont processes (see Section 3.5.1.2). YoueH                  should assume that the symbiont reads all logical namesE                  only when it is first created, thus requiring you touG                  first stop all queues and then retart them before your )                  changes can take effect.   C               o  You should define the desired logical names in the F                  system table in executive mode (that is, using DEFINE*                  /EXECUTIVE_MODE /SYSTEM).  E               o  In an OpenVMS Cluster environment, you should definesD                  the desired logical names on all nodes that utilizeG                  the DCPS software. To examine logical names defined by E                  DCPS, you need to look on the node on which the DCPS -                  symbiont process is running.   H                                           Logical Names Used by DCPS B-1 v  2            @            o  Additional logical names may be listed in the DCPS               Release Notes.  @            Table B-1 lists the logical names used by DCPS, theirA            acceptable values and a brief explanation of what they ?            mean. There are also references to other sections of C            this document or other documents where you can find moret/            information about the logical names.   C               ________________________Note ________________________n  =               In the Table B-1, qn is an abbreviation for the                queue name.d  C               _____________________________________________________o  E      Table_B-1_DCPS_Logical_Names____________________________________   *                                 AcceptableE      Logical_Name_______________Values____Meanings_and_References____   E      _________Logical_names_that_provide_information_to_DCPS_________g  <      DCPS_LIB[1]                search    List of DCPS setupB                                 list      libraries and their data>                                           types; Section 7.4.2  B      DCPS$DEFAULT_TRANSLATOR    <set of   System wide default textB                                 transla-  data type; Section 4.2.2(                                 tors>[2]  E      DCPS$qn_DEFAULT_           <set of   Queue specific default textdB      TRANSLATOR                 transla-  data type; Section 4.2.2(                                 tors>[2]  <      DCPS$DEVCTL_CACHE          TRUE      Enable system wideA                                           device control caching;T6                                           Section 7.11  ?      DCPS$qn_DEVCTL_CACHE       TRUE      Enable queue specific A                                           device control caching;t6                                           Section 7.11  E      [1]Defined_with_a_default_value_in_the_DCPS$STARTUP.COM_________E  :      [2]<set of translators> = ANSI, AUTOMATIC, LIST, PCL,%      POSTSCRIPT, REGIS, TEK4014, etc._  #      B-2 Logical Names Used by DCPS_                 H         Table_B-1_(Cont.)_DCPS_Logical_Names____________________________  -                                    Acceptable H         Logical_Name_______________Values____Meanings_and_References____  H         _________Logical_names_that_provide_information_to_DCPS_________  ?         DCPS$qn_DEVICE_NAME[3]     string    Actual device name_F                                              associated with the queueB                                              when name is too longB                                              for INITIALIZE /QUEUED                                              /ON qualifier (and SHOWF                                              QUEUE /FULL lists "DCPS$"D                                              as the device instead);:                                              Section 3.3.2  A         DCPS$IGNORE_UNKNOWN_USER   TRUE      Disable unknown userdC                                              error system wide whenpG                                              username not found in UAF; :                                              Section 3.5.9  A         DCPS$qn_IGNORE_UNKNOWN_    TRUE      Disable unknown useriC         USER                                 error for a queue when G                                              username not found in UAF;i:                                              Section 3.5.9  D         DCPS$qn_INTERRUPT_WHEN_    TRUE      Disable wait for serialG         BUSY                                 printers to be "not busy";a:                                              Section 3.5.2  H         DCPS$LAYUP[4]              search    Directory where layup filesF                                    list      are stored; DCPS Software?                                              Installation Guide   A         DCPS$MAX_STREAMS           0..32     Number of queues perCC                                              DCPS symbiont process; :                                              Section 3.5.1  C         DCPS$qn_NO_SYNC            TRUE      Disable usual synchro-rG                                              nization on printers otheraG                                              than PrintServer printers; :                                              Section 3.5.3  H         [3]Defined_by_DCPS$EXECUTION_QUEUE.COM__________________________  F         [4]Defined by DCPS$REQUIRED.COM using information you supplied$         during the DCPS installation  H                                           Logical Names Used by DCPS B-3                 E      Table_B-1_(Cont.)_DCPS_Logical_Names____________________________d  *                                 AcceptableE      Logical_Name_______________Values____Meanings_and_References____   E      _________Logical_names_that_provide_information_to_DCPS_________p  =      DCPS$qn_OLD_ANSI_PAGE_     TRUE      Use old (pre-V1.1A)tA      SIZES                                vertical spacing for A4 B                                           size in ANSI translator;8                                           Section 3.5.10  C      DCPS$qn_PARAMETER[3]       string    Default queue parameters;T7                                           Section 3.3.4   E      DCPS$qn_PRODUCT_NAME       string    Product name to use for thedB                                           printer on an LPD queue;7                                           Section 3.5.7   E      DCPS$PURGE_TIME            delta     Time to wait before purging,D                                 time      working set; Section 3.5.4  A      DCPS$qn_SEPARATOR_TRAY     number    Tray number to take job D                                           burst and flag pages from;7                                           Section 6.2.3   >      DCPS$SHEET_SIZE            string    Sheet size to use asE                                           default for all LPD queues; 7                                           Section 3.5.6a  >      DCPS$qn_SHEET_SIZE         string    Sheet size to use asD                                           default for the printer onE                                           an LPD queue; Section 3.5.6e  E      DCPS$SPOOL                 string    Enable spooling for all LPDe?                                           queues; Section 3.5.5-  D      DCPS$qn_SPOOL              string    Enable spooling for an LPD>                                           queue; Section 3.5.5  A      DCPS$SPOOL_DIRECTORY       string    Directory used to store$@                                           temporary spool files;7                                           Section 3.5.5   B      DCPS$qn_STALL_TIME         delta     Timeout before declaring<                                 time      a printer stalled;6                                           Section 5.12  E      [3]Defined_by_DCPS$EXECUTION_QUEUE.COM__________________________O  #      B-4 Logical Names Used by DCPSD                 H         Table_B-1_(Cont.)_DCPS_Logical_Names____________________________  -                                    Acceptable H         Logical_Name_______________Values____Meanings_and_References____  H         _________Logical_names_that_provide_information_to_DCPS_________  D         DCPS$qn_SUPPRESS_          TRUE      Disable printing of jobC         JOBTRAILER                           trailer; Section 6.2.2s  E         DCPS$SUPPRESS_PJL_         TRUE      Suppress unsolicited PJL C         MESSAGES                             messages received fromTD                                              printers on all queues;:                                              Section 3.5.8  E         DCPS$qn_SUPPRESS_PJL_      TRUE      Suppress unsolicited PJLiC         MESSAGES                             messages received fromEB                                              printer on one queue;:                                              Section 3.5.8  @         PSM$ANNOUNCE               string    String which prints@                                              on separator pages;8                                              Section 6.4  H         ________________________________________________________________H         ________Logical_names_that_return_information_from_DCPS_________  H         DCPS$qn_PID                          Process ID of DCPS symbiontC                                              controlling the queue;t8                                              Section 5.8  C         DCPS$qn_STALLED                      Reason for queue being B                                              stalled; Section 5.12  B         DCPS$VERSION                         DCPS software versionC                                              running on the system;hH         _____________________________________DCPS_Version_______________                H                                           Logical Names Used by DCPS B-5    e                  H                                                                        CH         ________________________________________________________________  H                                           Downloading and Deleting Fonts      O               You may be able to use the SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]FONT_oE               DOWNLOADER.COM command procedure to list, download, and_C               delete fonts on the optional hard drive on a printer. G               The procedure is known to work with the DEClaser 5100 andtH               LN17ps printers, and may work with other printers as well.  D               To use the procedure, invoke it and follow the prompts                that it gives you.                                                      H                                       Downloading and Deleting Fonts C-1 l  r                  H                                                                        DH         ________________________________________________________________  H                DECprint Supervisor (DCPS) and DECprint Printing ServicesH                                                           Software (CPS)      @               This appendix explains the differences between theD               DECprint Supervisor software and the DECprint PrintingE               Services software, and their ability to coexist. "DCPS"uH               refers to the DECprint Supervisor product; "CPS" refers to5               the DECprint Printing Services product.o            D.1 DCPS/CPS Coexistence  C               DCPS software can coexist on the same system with CPScC               Version 4.0 or Version 4.1 software. The installationSF               of DCPS software does not delete or modify components ofD               CPS software. You may continue to run both products onD               the same system, or you may migrate the existing queueA               structure from the CPS product to the DCPS product.n  &         D.2 Upgrading from CPS to DCPS  A               If you are upgrading from CPS to DCPS, convert yourn.               CPS$STARTUP.COM file as follows:  -               1. Enter the following command:v  3                  $ @SYS$STARTUP:CPS_TO_DCPS_STARTUP   C               2. Answer the questions displayed on your screen. For                   example:e  D                  Enter filename of CPS startup file to be converted;M                  Default filename is SYS$SYSROOT:[SYS$STARTUP]CPS$STARTUP.COMt                      [default]:u  =                  disk$manager:[cps_conversion]cps$startup.com   C                  Enter filename of DCPS startup file to be created; Y                  Default filename is SYS$SYSROOT:[SYS$STARTUP]DCPS$STARTUP.COM [default]:   >                  disk$manager:[cps_conversion]dcps$startup.com  H  Supervisor     (DCPS) and DECprint Printing Services Software (CPS) D-1                 @               Please read or run DIFFERENCES on the output file,D                       DISK$MANAGER:[CPS_CONVERSION]DCPS$STARTUP.COM,7               to be sure the new file meets your needs.S  =            The procedure creates a startup file that DECprintrC            Supervisor recognizes, but does not change your existingS@            queue definitions. If you need to add new queues, see            Section 3.3  =            DCPS has an automatic data type detection feature.kA            Therefore, you no longer need to specify the data typed6            as a queue default or in the PRINT command.  E            If you defined generic queues for default data types, edita,            DCPS$STARTUP.COM and remove them.        D.3 DCPS$ Prefixt  C            All file names, logical names, and messages for the DCPSiE            product start with the DCPS$ prefix. This ensures that you E            can continue to use CPS software to drive some queues, and E            add the DCPS software to drive others. The default OpenVMSe             form is DCPS$DEFAULT.  C            Certain files, however, are considered system resources, @            and are shared between the DCPS and CPS products, and?            possibly other products. These shared resources are:t               o  CPS$ANSI_FONTS.TLB  D               This is the library containing downloadable fonts that7               emulate LN03 or DEClaser font cartridges.   #            o  Data type translatorso  A               The DCPS product installs its translators using theuA               same directory and file name structure that the CPSt               product used.o  B            Secondary messages (those generated by other facilitiesD            such as RMS, and passed along by the DCPS product) retain@            the code of the facility that originated the message.      Q      D-2 DECprint Supervisor (DCPS) and DECprint Printing Services Software (CPS)     P            "         D.4 Startup File Converter  D               The conversion tool, CPS_TO_DCPS_STARTUP.COM, convertsG               the startup file for the CPS software so that it uses thecD               names from the DCPS product. This tool is described in               Section 3.2.  H               The following table lists the CPS_Name and the correspond-(               ing DCPS_Name conversions.  H               __________________________________________________________H               CPS_Name___________________DCPS_Name______________________  5               CPS$STARTUP                DCPS$STARTUP   =               CPS$EXECUTION_QUEUE        DCPS$EXECUTION_QUEUEe  6               CPS$REQUIRED               DCPS$REQUIRED  5               CPS$GENERIC                DCPS$GENERIC   1               CPS_LIB                    DCPS_LIBt  4               CPS$DEVCTL                 DCPS$DEVCTL  A               LPS$queuename_PARAMETER    DCPS$queuename_PARAMETERa  B               CPS$queuename_STALL_TIME   DCPS$queuename_STALL_TIME  3               LPS$LAYUP                  DCPS$LAYUPf  <               DECprint Printing          DECprint SupervisorH               Services__________________________________________________  D               The conversion tool does not change queue names or the&               structure of the queues.  &         D.5 Eliminating Generic Queues  H               DCPS software has the ability to automatically detect dataG               types, so you may be able to reduce the number of generichE               queues or eliminate them altogether. Refer to Chapter 4 D               for more information on automatic data type detection.           D.6 Page Scaling  B               The DCPS product can scale the logical page image toD               fit the output sheet if the job provides the following               parameters:j  &               PAGE_SIZE=p,SHEET_SIZE=s  5               Note that p and s are different values.   H  Supervisor     (DCPS) and DECprint Printing Services Software (CPS) D-3    a            B            The job assumes the parameter NUMBER_UP=1. With CPS, itD            was necessary to explicitly provide a NUMBER_UP parameter,            in order to trigger page scaling.  4      D.7 Layup for PS Level 2 Printers & Layup Fixes  E            The DCPS software layup facility supports PostScript Levelc@            2 operators when connected to printers that implementC            PostScript Level 2. It also fixes or extends support for %            several Level 1 operators.   @            Level 1 PostScript programs produced by Macintosh and?            PC applications generally print better with the DCPS D            product than they did with the CPS product. Problems with<            CorelDraw and Macintosh programs have been fixed.  ,      D.8 Layup Options on PRINT Command Line  E            With DCPS software, you can provide layup options directly B            with the LAYUP_DEFINITIONS parameter, or you can recordB            those options in a .LUP file and provide that file nameA            with the parameter. Providing the layup options on thegD            PRINT command makes it possible to pass them with jobs toC            be printed on another system via the Distributed QueuinguC            Services product. CPS V4.1 software offers only the .LUPf            file option.   B            See the DCPS User's Guide for information on expressingA            layup options in a layup definition file or as a PRINT             parameter.s        D.9 Page Sizesp  D            In the CPS V4.1 product, the following page sizes did notD            exist or were not correctly interpreted. The DCPS product2            defines and interprets these correctly.                 A6               C                Da               7x9n               7_envelope               10x14h               11x14l               PostCard  Q      D-4 DECprint Supervisor (DCPS) and DECprint Printing Services Software (CPS)     .            :         D.10 Selecting Separator Pages from Alternate Tray  H               To select job separator pages from an alternate tray usingE               the DCPS software, define the following system logical:r  S               $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queuename_SEPARATOR_TRAY number   E               Note that number is a valid tray number for the printertE               served by that queue, and is printer-specific. Refer torE               your printer documentation to obtain the correct value.e  -         D.11 Stopping Unreachable PrintServer   D               If the operator issues STOP/QUEUE/RESET, and the queueC               is connected to a DIGITAL PrintServer printer that is H               unreachable, the queue stops properly. This was not always2               the case with the CPS V4.1 software.  #         D.12 Overwriting First Lineo  F               In the CPS V4.1 product, the top line was overwritten ifG               the record started with a form feed. This works correctly #               in the DCPS software.            D.13 Stall Timeoutso  E               The CPS V4.1 software did not start the stall timer forfC               directly-connected serial printers. The DCPS softwaren               starts the timer.n  F               In the CPS V4.1 product, the default timeout for a stallH               message was one minute. This frequently resulted in "queueA               stalled" messages when the printer was processing a C               compute-intensive page (and was not really stalled at4B               all). In the DCPS product, the stall timeout is four               minutes.           D.14 Requeuing a Job  A               When a network error occurred while connecting to a_G               printer, the CPS V4.1 software would requeue the job withnH               the /HOLD attribute. The DCPS software requeues it without"               the /HOLD attribute.    H  Supervisor     (DCPS) and DECprint Printing Services Software (CPS) D-5                       D.15 Reading Stream Files  A            If a PostScript file has a record attribute of STREAM, B            STREAM_LF, or STREAM_CR, it is read in head1 mode. ThisE            allows the DCPS software to print very long stream records E            that the CPS software cannot print. Files of this type are ;            sometimes written by PC communications programs._  $      D.16 Copies Start on New Sheets  ?            When /COPIES=n is requested, and n is more than one,->            each copy starts on a new sheet, even when printing@            with NUMBER_UP or SIDES=2. This was not the case with3            PostScript jobs in the CPS V4.1 product.p  "      D.17 Generic Queues Restarted  >            On shutdown, OpenVMS stops execution queues but notA            generic queues. As a result, when the system starts up_C            again, the generic queues begin running even though they @            may have the wrong characteristics. When you start upB            generic queues in the CPS V4.1 product, you get warningE            messages saying that the queues are already running (as of B            OpenVMS V5.5). When the DCPS software starts up genericD            queues, it stops and then restarts those that are already            running.         D.18 Proprinter Translator   D            The DCPS software contains a new Proprinter-to-PostScriptC            translator not available in the CPS product. For generalPA            information on using the PROPRINTER data type, see the_            DCPS User's Guide._  &      D.19 DCPS and PATHWORKS Libraries  C            PATHWORKS for OpenVMS (Macintosh) creates its own device >            control library, MSAP$DEVCTL.TLB, and also puts its@            modules into the CPS library if there is one. It doesD            not put them in the DCPS library. To rectify this, defineE            DCPS_LIB as a search list that points to both the DCPS andeC            PATHWORKS libraries. An example in DCPS$STARTUP.TEMPLATEo             shows how to do this.    Q      D-6 DECprint Supervisor (DCPS) and DECprint Printing Services Software (CPS)e f  t            F                 ________________________Note  ________________________  B                 PATHWORKS for OpenVMS (Macintosh) has been retired+                 and is no longer supported.   E                 _____________________________________________________T  1         D.20 Printing with Macintosh and PC Files   F               The DCPS software contains a new PostScript example fileF               to improve printing of Macintosh and PC files on DIGITAL#               PrintServer printers.e  5         D.21 Improved Color Function for Colormate PSu  A               The color transfer function of the Colormate PS has E               been changed to avoid the problems of gray scale imagesNC               that are muddy or brown, and natural images with poornF               flesh tones. The Colormate PS now runs prints with a newD               default color transfer function to provide better grayE               scale images and natural flesh tones. Consequently, you D               may notice the following changes when you print on the               Colormate PS:   :               o  Graphic images may not seem as brilliant.  B               o  Grays will be accurately rendered as gray and not                  brown.   D               o  Some pictures may appear to have less yellow and/or#                  more blue in them.   '         D.22 Printing Security Messagest  ;               The DCPS product provides a new example file:r  >               SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]CONFIDENTIAL.PS  F               This file shows how to redefine the showpage operator toH               write "Confidential" at the top and bottom of each page asF               an overlay (that is, after the contents of the page have               been imaged).       H  Supervisor     (DCPS) and DECprint Printing Services Software (CPS) D-7                               E      ________________________________________________________________   E                                                                 Index       E      A__________________________          C__________________________   D      Accounting fields                    Changing the character setB        filled with zeros by job             for PCL and Proprinter8          controller,  9-4                   files,  7-11B        left blank by job                  Character sets, changingB          controller,  9-3                   for PCL and Proprinter8        supplied by DCPS, 9-1                files,  7-112        supplied by job                    Commands?          controller,  9-2                  See also Print queuee6      Accounting utility,  9-1                 commands>      Automatic data type                   DELETE /ENTRY,  5-2:         detection                          SET ENTRY,  5-5;        overview, 1-2                       SHOW ENTRY,  5-1h@        solving problems with,              SHOW QUEUE,  5-1, 5-5=          11-23                             START /QUEUE,  5-7 A        specifying a default text           START /QUEUE /MANAGER, 2          data type for,  4-3                  5-10@      Autostart queues,  3-5                STOP /QUEUE /MANAGER,2        defining, 3-5                          5-10  @      B                                    Converting queues from=      ___________________________            DECprint Printingu:      Baud rate limitations,  2-9            Services,  3-1.      Bi-directional                       CPAP>         communication                      definition of,  3-7=        requirement for, 2-2                specifying networka<      Burst page,  6-1                         address,  3-10  6                                           CPS software  @                                            See DECprint Printing6                                               Services  E                                                               Index-1t M  g            D      Custom setup modules,  7-8           Device name, specifying inC                                             DCPS$STARTUP.COM,  3-10 4      D__________________________          DisplayingA      Data type detection,  1-2             print job status,  5-1 7      DCPS                                  queues,  5-5   +        software overview, 1-3             EbE      DCPS$DEFAULT form,  8-6              ___________________________,8      DCPS$STARTUP.COM                     Error messages<        creating, 3-1                       for LAT connected>        running in setup mode,                 printers,  11-179          3-16                             Error page, 6-9 >        specifying the device              Ethernet use, serial:          name in,  3-10                     printers,  2-1?      DEClaser font emulation,             Execution queues, 3-1 D         7-15                               specifying printer device<      DECnet                                   name in,  3-107        specifying PrintServer             Extended Filee@          network address,  3-11             Specifications,  6-8       DECprint Printing Services,E         D-1                               F__________________________ 9        converting from, 3-1               File burst page ;      DECprint Supervisor                   specifying,  6-7 >        features, 1-1                      File error page, 6-98      Default form,  8-6                   File flag page;      Default queue                         specifying,  6-7 ?        parameters, 3-13                   File separation pages ;           syntax errors handling           specifying,  6-7a;             ,  11-22                      File trailer page ;           syntax for, 3-12                 specifying,  6-7 8        qualifiers, 3-14                   Flag page, 6-1C      Default text data type,              Font cartridge emulation, 0         4-3                                 7-15/      Defining                             FontseD        print queue qualifiers,             downloading and deleting,1          3-14                                 C-1 9      DELETE /ENTRY command,  5-2          /FORM qualifier <      DELETE /FORM command,  8-5            with DELETE,  8-5@      Deleting                              with SET /QUEUE,  8-2B        forms, 8-5                          with START /QUEUE,  8-2/        print jobs, 5-2                    FormstC      Device control library,               associating with queues,s1         1-5, 7-1                              8-2   8                                            default,  8-6        Index-2                 8         Forms (cont'd)                      LPD (cont'd)  A          deleting,  8-5                       specifying internal D                                                  printer queue name,4         G__________________________              3-9@         Generic queues, 3-34                  specifying network=          defining,  3-34                         address, 3-9rF                                               specifying product name,5         I__________________________              3-24lD         IP_CPAP                               specifying sheet size,5          See CPAP                                3-23n=                                               troubleshooting E         IP_RawTCP                                procedures for, 11-4f  D          See Raw TCP/IP                     LPS$$UNRECOGNIZED,  7-17  G         J__________________________         M__________________________/  4         Job burst page                      MessagesC          specifying,  6-2                     network error,  11-17n5         Job flag page                       Modifying_E          specifying,  6-2                     DCPS symbiont behavior, 5         Job log page                             3-17_G          description of,  6-9                 execution queue behavior, 5          specifying,  6-9                        3-17 H         Job not printing, 11-5                print job attributes,  5-5;         Job trailer page                      queues,  3-35_B          specifying,  6-2                   Multistreamed symbiont  6                                                processG         L__________________________           changing DCPS environment   ;         LAT                                      with, 3-19 D          port characteristics                 running DCPS as,  3-17  "             required for printing,G             2-4                             N__________________________s  <          terminal server,  2-4              Network printersE         LAT protocol file, editing            troubleshooting,  11-13            the,  2-7RG         LAT startup file, 2-4               O__________________________P9         Library search list for             ODS-5 VolumesPE           setup modules,  7-5                 printing files on,  6-8 A         Login dialog, reducing for          OPCOM messages,  11-1m!           serial printers,  11-20          Log page, 6-1s         LPDV          definition of,  3-9!          enabling spooling,  3-22n  H                                                                  Index-3 t  g            6                                           Print queues:      P__________________________           autostart,  3-59      Page counters, mechanical,            commands,  A-1v@         9-5                                customizing executionC      PCL files                                queue behavior,  3-17 ;        changing character set              displaying,  5-5fA          for,  7-11                        enabling LPD spooling,y2      Persistent resources,                    3-22:         loading, 7-9                       execution,  3-19      PJL messages,  3-32                   generic,  3-34 <      Port characteristics,  2-4            interrupting busy?      PRINT command,  1-4                      printers when jobt;        /BURST qualifier, 6-7                  starts,  3-20 5        /FLAG qualifier, 6-7                parametersl<        MESSAGES parameter, 6-9                default,  3-13;        /TRAILER qualifier, 6-7                syntax,  3-12YC      Printer name, setting,                   syntax errors,  11-22u<         2-12                               qualifiers,  3-14<      Printers                              running DCPS as aD        troubleshooting newly                  multistreamed process,2          installed,  11-6                     3-17A      Printers, serial use on               running multistreamed, 2         Ethernet, 2-1                         3-18A      Printer-specific                      specifying LPD productC9         information, 10-1                     name,  3-24s?      Printer startup file                  specifying LPD sheeta9        defining autostart queues              size,  3-23.8          in,  3-5                          stalled,  5-99        defining execution queues           starting,  5-7tD          in,  3-1                          suppressing PJL messages,2        defining generic queues                3-32A          in,  3-34                         suppressing PostScript D      Printing system management               synchronization when a?         commands, A-1                         job starts,  3-20_@      Print job attributes,                 suppressing the OPCOMC         changing, 5-5                         message USERNOTFOUND,a2      Print jobs                               3-33?        characteristics, A-3                testing the printing ;        deleting, 5-2                          system,  3-36 9        holding, 5-3                        types of,  3-1 >        printer state is unknown,          PrintServer printersD          5-7                               specifying DECnet network<        releasing, 5-3                         address,  3-11          Index-4    o            ?         PrintServer printers                Raw TCP/IP (cont'd)x=           (cont'd)                            troubleshootingn  E          specifying TCP/IP network               procedures for, 11-1E5             address,  3-10                  Resources H          troubleshooting                      persistently loading,  7-9  !             procedures for,  11-5 G         Print symbiont                      S__________________________ B          device control library             Search list for deviceE             for,  1-5                          control libraries, 7-5d<         Proprinter files                    Separation pagesG          changing character set               adding system message to,E4             for,  7-11                           6-8A         PSM$ANNOUNCE, 6-8                     definition of,  6-1_  E                                               enabling for file,  6-7 D         Q__________________________           enabling for job,  6-2  ;         Qualifiers, print queue,            Serial printers_F           3-14                                eliminating login dialog:         Queue                                    on, 11-20?          See Print queue                    Serial printers, on <         Queue logical names, 11-10             Ethernet, 2-1C         Queue manager                       SET ENTRY command,  5-5 D          starting,  5-10                    SET ENTRY /HOLD command,2          stopping,  5-10                       5-3G         Queue parameters                    SET ENTRY /RELEASE command, 2          default,  3-12                        5-3=          defaulting order of,  3-13         SET PRINTER,  A-3 =          redefining,  3-12                  Setup mode,  3-16 ?          syntax for,  3-12                  Setup modules,  7-8n>         Queue structure                       customized,  7-8D          of autostart queues,               SHOW ENTRY command,  5-1E             defining,  3-5                  SHOW QUEUE command,  5-1, 2          of execution queues,                  5-5;             defining,  3-1                  Spooling,  3-22 E          of generic queues,                 Stalled print queue,  5-9s4             defining,  3-34                 Starting@                                               print queues,  5-7B         R                                     queue manager,  5-10F         ___________________________         START /QUEUE command,  5-7A         Raw TCP/IP                          START /QUEUE /MANAGER <          definition of,  3-7                   command, 5-108          specifying network                 Startup file<             address,  3-7                     creating,  3-1          specifying TCP port             number,  3-7  H                                                                  Index-5                 D      Startup file (cont'd)                Troubleshooting procedures4        running in setup mode,               (cont'd)  C          3-16                              for Raw TCP/IP printers, 2      Stopping                                 11-1D        queue manager, 5-10                 for slow printing,  11-21@      STOP /QUEUE /MANAGER                  for stopped printers,3         command, 5-10                         11-11d<      Supported printers                    when jobs are not=        using, 2-11                            printing,  11-5 @      Symbiont,  1-4                        when layup definitionB      System startup file,                     files are not found,3         editing the, 3-35                     11-22O  E      T__________________________          U__________________________   @      TCP/IP                               Unrecognized printers,  0        See also CPAP                        7-17  D        See also LPD                       Unsupported printers, 7-17          See also Raw TCP/IP        setting up printer, 2-1       Telnet, not supported,  3-7      Text data type default,         4-3       Third-party printers         unsupported, 7-17      Trailer page,  6-1       Translators,  1-5      Troubleshooting procedures         for a printer in a           network environment,           11-13        for incorrectly          translated files,          11-23        for jobs not printing, 
          11-1P        for LPD printers, 11-4n        for newly installed          printers,  11-6         for PrintServer printers,
          11-5         for queue default          parameters,  11-22$        Index-6