                                 H                     HP_DECprint_Supervisor_(DCPS)_for_OpenVMS___________!                     Release Notes     !                     November 2005   F                     This manual contains information about the current$                     release of DCPS.              E                     Revision/Update Information:  These release notes E                                                   supersede all other @                                                   documentation.  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.2I                                                   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                  J           ________________________________________________________________  D            Copyright 2005 Hewlett-Packard Development Company, L.P.  ?           Confidential computer software. Valid license from HP B           required for possession, use or copying. Consistent with>           FAR 12.211 and 12.212, Commercial Computer Software,A           Computer Software Documentation, and Technical Data for D           Commercial Items are licensed to the U.S. Government under/           vendor's standard commercial license.   ?           The information contained herein is subject to change A           without notice. The only warranties for HP products and C           services are set forth in the express warranty statements A           accompanying such products and services. Nothing herein E           should be construed as constituting an additional warranty. E           HP shall not be liable for technical or editorial errors or %           omissions contained herein.   D           Adobe, Adobe PostScript 3 and PostScript are trademarks of%           Adobe Systems Incorporated.   C           Intel and Itanium are trademarks or registered trademarks @           of Intel Corporation or its subsidiaries in the United%           States and other countries.   A           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.   C           The DECprint Supervisor documentation set is available on            CD-ROM.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................      v   !   1  DCPS Version 2.5 Information   C         1.1   DCPS Version 2.5 Changes......................    1-1 C         1.1.1     New Printers Supported....................    1-1 C         1.1.2     Enhanced LPD Support......................    1-1 C         1.1.2.1     Spooling Overview.......................    1-1 C         1.1.2.2     Enabling Spooling.......................    1-2 C         1.1.2.3     Spooling Errors.........................    1-3 C         1.1.3     Improved Installation Procedure...........    1-3 C         1.1.4     Flag Page Improvement.....................    1-3 C         1.2   DCPS Version 2.5 Fixes........................    1-4 7         1.2.1     Problems Starting Queues and Deleting C                   Jobs......................................    1-4 C         1.2.2     Job Fails when Selecting Trays............    1-4 C         1.2.3     Stapling Error............................    1-5 C         1.2.4     LPD Jobs Fail with PostScript Error.......    1-5 C         1.2.5     AppleTalk File Omitted from Kit...........    1-5 C         1.2.6     Performance on Integrity Systems..........    1-5 3         1.2.7     Incorrect OLDSETUP Message During C                   Startup...................................    1-5   !   2  Printer-Specific Information   C         2.1   Printer Firmware..............................    2-1 C         2.1.1     Printers Fail with Service Error..........    2-1 C         2.1.2     Problems Starting Queues..................    2-2             C                                                                 iii                         3  DCPS Restrictions  E           3.1   AppleTalk on OpenVMS V8.2 and Later Systems...    3-1 E           3.2   Printers with Auto-Sensing Features...........    3-1 <           3.3   Job Remains in Starting State for Raw TCP/IPE                 or LAT Queue..................................    3-2 <           3.4   Job Remains in Starting State for Raw TCP/IPE                 Queue.........................................    3-2 6           3.5   Connection Terminations for Raw TCP/IPE                 Queue.........................................    3-3 =           3.6   NOT_READY Warnings for Unavailable Raw TCP/IP E                 Printer.......................................    3-4 1           3.7   Translators Do Not Generate Color E                 PostScript....................................    3-4 =           3.8   Job Trailer Page Jogs with PostScript Level 2 E                 Printers......................................    3-4 9           3.9   Unable to Perform ANSI Tray Selection for E                 Certain Printers .............................    3-4 <           3.10  Some Printers Do Not Send Status Messages toE                 the Host......................................    3-5 2           3.11  Printer Name Is Not Always PrintedE                 Correctly.....................................    3-6 =           3.12  DDIF Printing Requires DECwindows Software or E                 DECimage Application Services.................    3-6 9           3.13  Compatibility of NUMBER_UP and PostScript E                 Drivers.......................................    3-6 E           3.14  LIST Translator Ignores PAGE_SIZE Parameter...    3-6 =           3.15  Embedded PJL Commands Discarded; Avoid Binary E                 Mode..........................................    3-7 >           3.16  Avoid STOP /QUEUE /RESET Usage for PrintServerE                 Printer Which Is Rejecting Connections........    3-7 E           3.17  No Job Trailer Page on DELETE /ENTRY..........    3-7 <           3.18  Problems with PostScript Files When PrintingE                 with /COPIES .................................    3-8 E           3.19  Problems Using PAGE_LIMIT with /JOB_COUNT.....    3-8 9           3.20  Setting I/O Buffers Too Small May Produce E                 OPCOM Errors..................................    3-8                      iv                   .         4  Other Restrictions that Affect DCPS  9               4.1   DCPS Processes Consume CPU after Time I                     Change........................................    4-1 =               4.2   Starting Queue Causes Invalid Device Name I                     Error.........................................    4-2 ?               4.3   Problems Starting Queues with Multistreamed I                     Symbionts.....................................    4-2 I               4.4   I/O Errors for Serially-Connected Printers....    4-3 @               4.5   Symbiont Aborts with Access Violation or BadI                     Parameter Error ..............................    4-3   "         A  Raw TCP/IP Port Numbers             Tables  I               1         DECprint Supervisor Documentation.........     vi   I               1-1       Spool File Error Messages.................    1-3   I               2-1       Firmware with Service Error Fix...........    2-1   I               2-2       Minimum Recommended Firmware..............    2-2   I               A-1       Raw TCP/IP Port Numbers...................    A-1                                       I                                                                         v                              I         _________________________________________________________________   I                                                                   Preface                Intended Audience   C               These release notes describe new features, bug fixes, D               usage hints, restrictions and other useful informationF               for this release of DECprint Supervisor. System managersG               and users should review this document for new information >               about installing and using this release of DCPS.           Document Structure  D               These release notes contain the following chapters and               appendices:   C               o  Chapter 1 describes changes included in DCPS V2.5.   E               o  Chapter 2 provides information about using DCPS with #                  specific printers.   E               o  Chapter 3 identifies current restrictions that exist                    with DCPS V2.5.  G               o  Chapter 4 contains information about OpenVMS operating ?                  system problems that are known to impact DCPS.   F               o  Appendix A lists commonly-used port numbers used when(                  setting up IP printers.           Related Documents   A               The primary source of information about DCPS is the 0               following set of software manuals:      I                                                                         v                    E           Table_1_DECprint_Supervisor_Documentation__________________   >           Software              Describes how to install DCPS.           Installation Guide  C           System Manager's      Describes how system managers, data @           Guide                 center operators and applicationA                                 programmers can create and manage D                                 DCPS print queues and solve printing)                                 problems.   E           User's Guide          Describes how to use DCPS to print to 7                                 PostScript[R] printers.   B           Software Product      Contains the full list of printers@           Description (SPD      supported by DCPS and additionalB           44.15.xx)             information about the features andE           ______________________requirements_of_DCPS_V2.5.___________   B           For additional information about HP OpenVMS products and?           services, visit the following World Wide Web address:   +               http://www.hp.com/go/openvms/        Reader's Comments   ?           HP welcomes your comments on this manual. Please send 8           comments to either of the following addresses:  '           Internet    openvmsdoc@hp.com   -           Mail        Hewlett-Packard Company :                       OSSG Documentation Group, ZKO3-4/U08)                       110 Spit Brook Road *                       Nashua NH 03062-2698  )     How to Order Additional Documentation   7           For information about how to order additional D           documentation, visit the following World Wide Web address:  5               http://www.hp.com/go/openvms/doc/order/   @           Part numbers for DCPS-related documentation are listedB           in the Ordering Additional Documentation appendix of theA           Software Installation Guide, System Manager's Guide and            User's Guide.        vi                            Conventions   @               The following conventions are used in this manual:  G               Ctrl/x           A sequence such as Ctrl/x indicates that F                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button.   D               <Return>         In examples, a key name enclosed in aD                                box indicates that you press a key onH                                the keyboard. (In text, a key name is not2                                enclosed in a box.)  I                                In the HTML version of this document, this E                                convention appears as brackets, rather *                                than a box.  @                . . .           A horizontal ellipsis in examples=                                indicates one of the following -                                possibilities:   D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.   I                                o  Additional parameters, values, or other =                                   information can be entered.   >               ( )              In command format descriptions,I                                parentheses indicate that you must enclose I                                choices in parentheses if you specify more (                                than one.  G               [ ]              In command format descriptions, brackets H                                indicate optional choices. You can chooseD                                one or more items or no items. Do notE                                type the brackets on the command line. E                                However, you must include the brackets B                                in the syntax for OpenVMS directoryA                                specifications and for a substring H                                specification in an assignment statement.  I                                                                       vii                      C           |                In command format descriptions, vertical @                            bars separate choices within bracketsB                            or braces. Within brackets, the choices@                            are optional; within braces, at leastB                            one choice is required. Do not type the=                            vertical bars on the command line.   A           { }              In command format descriptions, braces E                            indicate required choices; you must choose C                            at least one of the items listed. Do not ?                            type the braces on the command line.   D           bold text        This typeface represents the introductionE                            of a new term. It also represents the name D                            of an argument, an attribute or a reason.  :           italic text      Italic text indicates importantE                            information, complete titles of manuals or C                            variables. Variables include information A                            that varies in system output (Internal <                            error number), in command lines (D                            /PRODUCER=name) and in command parameters;                            in text (where dd represents the @                            predefined code for the device type).  B           UPPERCASE TEXT   Uppercase text indicates a command, theD                            name of a routine, the name of a file, orC                            the abbreviation for a system privilege.   E           Monospace text   Monospace type indicates code examples and 7                            interactive screen displays.   B           -                A hyphen at the end of a command formatA                            description, command line or code line B                            indicates that the command or statement;                            continues on the following line.   @           numbers          All numbers in text are assumed to beE                            decimal unless otherwise noted. Nondecimal C                            radixes-binary, octal or hexadecimal-are 0                            explicitly indicated.           viii                         I                                                                         1 I         _________________________________________________________________   I                                              DCPS Version 2.5 Information     G               This section describes changes included in DCPS V2.5. You D               can find more information for several of these changes/               elsewhere in these release notes.   $         1.1 DCPS Version 2.5 Changes  $         1.1.1 New Printers Supported  @               DCPS V2.5 adds support for the following printers:  '                  HP Color LaserJet 3000 '                  HP Color LaserJet 3800 '                  HP Color LaserJet 4610 '                  HP Color LaserJet 4700 +                  HP Color LaserJet 4730 MFP !                  HP LaserJet 1300 !                  HP LaserJet 1320 !                  HP LaserJet 4240 !                  HP LaserJet 5200 &                  Xerox DocuPrint N4525  "         1.1.2 Enhanced LPD Support  A               DCPS now works with remote LPD queues and with more (               printers that support LPD.  !         1.1.2.1 Spooling Overview   H               Remote LPD queues, and many LPD printers, require the sizeE               of the job to be known before the job is sent. DCPS can C               now produce a temporary spool file so the size can be E               determined. By default, DCPS LPD jobs will use the pre- E               V2.5 behavior, so specific action must be taken to send E               DCPS LPD jobs to remote LPD queues or LPD printers that H               require it. Spooling can be specified for the whole systemA               or for individual queues by defining logical names.   I                                          DCPS Version 2.5 Information 1-1                    ?           Because spooling requires an extra step to create the C           temporary spool file, you should enable spooling only for B           printers that require it. Common reasons to use spooling           are:  >           o  You are printing to a remote LPD queue on another              system.  E           o  Your printer does not print anything when using DCPS LPD               without spooling.  E           o  Your printer is a larger multi-function device that does C              not work with DCPS when using the Raw TCP protocol, or D              LPD protocol without spooling. These devices often haveA              their own internal queues that accept jobs for later               printing.       1.1.2.2 Enabling Spooling   A           To enable spooling, define one of the following logical >           names. Neither of these logical names are defined by           default.             o  DCPS$SPOOL   E              When defined, all LPD jobs from all queues will create a E              temporary spool file before being sent to the printer or               remote queue.  "           o  DCPS$queue-name_SPOOL  A              When defined, LPD jobs from this queue will create a E              temporary spool file before being sent to the printer or               remote queue.  E           To specify where temporary spool files will be created, the E           following logical name is used. This logical name is always            defined.  !           o  DCPS$SPOOL_DIRECTORY   >              Spool files will be created in this directory andE              deleted after being sent to the printer or remote queue. B              Print jobs are not spooled unless spooling is enabled5              with one of the two logical names above.   =              You will be asked for the location for your DCPS :              spool directory when installing DCPS if it is9              not already defined. The default location is >              SYS$COMMON:[DCPS$SPOOL], but you should specify aC              location on a non-system disk that is available to all   $     1-2 DCPS Version 2.5 Information                   H                  queues for which spooling is enabled. This directory isI                  protected such that only the DCPS print symbiont process ?                  and privileged users can view the spool files.            1.1.2.3 Spooling Errors   F               Error messages you can receive while using spooling are:  I               Table_1-1_Spool_File_Error_Messages________________________   I               Error_Message____Description_______________________________   H               SPOOLBADDEVICE   Error in DCPS$SPOOL_DIRECTORY device name  G               SPOOLBADDIR      DCPS$SPOOL_DIRECTORY directory not found   G               SPOOLERROR       Error creating spool file in DCPS$SPOOL_ (                                DIRECTORY  7               SPOOLFILENOOPEN  Error opening spool file   C               SPOOLNOLOGICAL   Logical name DCPS$SPOOL_DIRECTORY is (                                undefined  C               SPOOLNOPRIV      No privilege to write to DCPS$SPOOL_ (                                DIRECTORY  D               SPOOLNOWRITE     DCPS$SPOOL_DIRECTORY device is write-I               _________________locked____________________________________   -         1.1.3 Improved Installation Procedure   D               When installing DCPS V2.4 with the POLYCENTER SoftwareE               Installation Utility (PCSI), the installation procedure C               required all DCPS queues in the cluster to be stopped I               before proceeding with the installation. Now, you are given E               choices including stopping only the queues that will be +               affected by the installation.   #         1.1.4 Flag Page Improvement   H               DCPS separator pages display information about the printerE               in the lower right-hand corner of the page: the product I               name and, if different, the printer name. (The product name G               cannot be customized, but the printer name can be changed                 for each printer.)  B               Now, the printer name is displayed in parentheses to5               differentiate it from the product name.   I                                          DCPS Version 2.5 Information 1-3                         1.2 DCPS Version 2.5 Fixes  8           The following problems are fixed in DCPS V2.5.  4     1.2.1 Problems Starting Queues and Deleting Jobs  D           In DCPS V2.3 and V2.4, problems might arise when a Raw TCP$           job was in Starting state:  A           o  If the job was aborted with a DELETE /ENTRY command, ;              DCPS would take a long time to delete the job.   ?           o  If the queue was stopped with a STOP /QUEUE /RESET >              command, starting this or other queues would then5              sometimes fail with the following error:   F                  %DCPS-F-STREAMUSE, Request 4 for Stream Id n ignored.3                  Not consistent with symbiont state   C           Now, starting jobs will abort quickly when requested, and D           stopping the queue will not cause the STREAMUSE error when'           subsequently starting queues.   (     1.2.2 Job Fails when Selecting Trays  B           In DCPS V2.4, requesting a tray by specifying the INPUT_?           TRAY parameter could result in the job failing with a =           INTRAYNOTAVL error message. For example, specifying >           /PARAMETERS=INPUT_TRAY=TRAY_2 when printing to an HPC           LaserJet 8150 printer would result in the following error            messages:   S               %DCPS-E-INTRAYNOTAVL, No tray_2 tray is installed on HP LaserJet 8150 W               -DCPS-I-JOB_ID, for job MYJOB (queue HP8150_RAW, entry 245) on HP8150_RAW   D               %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignoredW               -DCPS-I-JOB_ID, for job MYJOB (queue HP8150_RAW, entry 245) on HP8150_RAW   >           This problem would occur when selecting trays on the           following printers:                 HP LaserJet 2100               HP LaserJet 2200               HP LaserJet 8000               HP LaserJet 8100               HP LaserJet 8150   $     1-4 DCPS Version 2.5 Information                            1.2.3 Stapling Error  A               If the LaserJet 9000 printer was set to staple jobs C               by default, the DCPS STAPLE=NONE parameter would have C               no effect and DCPS jobs would always be stapled. Now, @               overriding the printer's default staple setting byE               specifying STAPLE=NONE correctly produces a non-stapled                job.  I               This problem was fixed for other printers in DCPS V2.4, but A               the problem remained for the LaserJet 9000 printer.   1         1.2.4 LPD Jobs Fail with PostScript Error   B               If the logical name DCPS$queue-name_PRODUCT_NAME wasA               not defined for an LPD queue, print jobs could fail C               with a PostScript "checkconfiguration" error. As with E               any PostScript error with LPD jobs, if PostScript error E               reporting was not enabled on the printer, the job would +               fail with no error indicated.   F               Now, if the logical name is not defined, DCPS assumes itI               is an "unrecognized" printer and the job will not fail with                this error.   -         1.2.5 AppleTalk File Omitted from Kit   H               The AppleTalk file DCPS$BE_APPLETALK.EXE was inadvertentlyG               omitted from the DCPS V2.4 PCSI kit for OpenVMS Alpha and B               VAX. This file is now included in the DCPS V2.5 kit.  .         1.2.6 Performance on Integrity Systems  G               When running on OpenVMS I64, DCPS V2.4 symbiont processes @               could use large amounts of CPU time when printing.<               Performance in V2.5 has been greatly improved.  7         1.2.7 Incorrect OLDSETUP Message During Startup   D               When starting DCPS in "setup" mode, it was possible toC               incorrectly receive a message indicating your startup C               command procedure was newer than your setup file. The F               following message could be displayed even if the startupE               file had not been changed since the setup file had been                created:  F                   %DCPS-W-OLDSETUP, setup file older than startup file  I                                          DCPS Version 2.5 Information 1-5                    B           The result was that a new setup file was created and theA           commands to start queues in DCPS$STARTUP were executed. C           Although all queues were correctly started, this caused a B           slower startup compared to the desired behavior of usingB           information in the setup file. This check is now handled           correctly.                                                                              $     1-6 DCPS Version 2.5 Information                         I                                                                         2 I         _________________________________________________________________   I                                              Printer-Specific Information     E               This chapter provides information about using DCPS with D               specific printers. The DCPS System Manager's Guide andC               DCPS User's Guide contain additional printer-specific                information.           2.1 Printer Firmware  G               Your printer's firmware version is displayed as "Firmware H               Datecode" on the printed configuration page, the printer'sF               web page and the WebJetAdmin printer management utility.  E               Printer firmware and instructions for downloading it to G               your printer can be obtained from the HP web page. Choose F               Printing and Multifunction and then Support and Drivers.  .         2.1.1 Printers Fail with Service Error  F               When printing certain PostScript files, some HP printersF               fail with a 49.4C02 service error. This problem has beenG               fixed in printer firmware. Table 2-1 shows which printers I               have this problem and in which firmware version the problem D               is fixed. Your printer must be running this version of:               firmware at a minimum to avoid this problem.  I               Table_2-1_Firmware_with_Service_Error_Fix__________________   I               Printer___________Firmware_Version_________________________   1               HP Color          20050524 07.003.3                LaserJet 4650   1               HP Color          20050524 07.007.3                LaserJet 5550   1               HP LaserJet 4250  20050831 08.009.3   I                                          Printer-Specific Information 2-1                    E           Table_2-1_(Cont.)_Firmware_with_Service_Error_Fix__________   E           Printer___________Firmware_Version_________________________   -           HP LaserJet 4350  20050831 08.009.3   -           HP LaserJet 9050  20050617 08.102.2   -           HP LaserJet 9055  20050601 07.004.0 
           MFP   -           HP LaserJet 9065  20050601 07.004.0 E           MFP________________________________________________________   "     2.1.2 Problems Starting Queues  E           Some HP printers do not respond to the DCPS synchronization ;           request at the beginning of a job. Therefore, you =           must upgrade the printer's firmware to at least the ?           version shown in Table 2-2 or define the logical name A           DCPS$queue-name_NO_SYNC before queues to these printers C           are started, or DCPS jobs will not start. See Section 3.3 C           in these Release Notes or the DCPS System Manager's Guide            for more information.   ?           It is also recommended that the printer's personality B           setting be set to PS (PostScript). Setting the printer'sA           personality to PS (PostScript) alone will not solve the E           problem for these printers. This problem is resolved in the 1           following versions of printer firmware:   E           Table_2-2_Minimum_Recommended_Firmware_____________________   E           Printer___________Firmware_________________________________   -           HP Color          20030605 04.016.2            LaserJet 5500   -           HP LaserJet 2300  20030530 04.047.2   -           HP LaserJet 4200  20030530 04.016.1   E           HP_LaserJet_4300__20030530_04.016.1________________________   >           This restriction is still in effect for the HP Color            LaserJet 2500 printer.  $     2-2 Printer-Specific Information                         I                                                                         3 I         _________________________________________________________________   I                                                         DCPS Restrictions     I               This chapter identifies the current restrictions that exist E               with DCPS. See the DCPS System Manager's Guide and DCPS =               User's Guide for printer-specific restrictions.   7         3.1 AppleTalk on OpenVMS V8.2 and Later Systems   E               One of the network protocols used by DCPS is AppleTalk, F               provided on OpenVMS Alpha and VAX systems by the layeredF               product PATHWORKS for OpenVMS (Macintosh). Although thisB               product is retired and no longer supported, DCPS has6               continued to work with AppleTalk queues.  B               However, changes made to OpenVMS in V8.2 prevent theD               AppleTalk protocol from being started. Therefore, DCPSG               does not work with AppleTalk queues starting with OpenVMS                V8.2.   H               Starting a DCPS queue that executes on an OpenVMS V8.2 andI               later system will fail with the following operator message:   D                   %DCPS-F-CANNOTSTART, cannot start queue queue_nameN                   %DCPS-F-TRANSPORTNOTSUP, transport not supported - AppleTalk@                   %SYSTEM-F-IVPARAM, invalid parameter specified  E               To avoid this problem in an OpenVMS cluster, change the H               node on which the queue executes to one running an OpenVMS5               version earlier than V8.2, if possible.e  /         3.2 Printers with Auto-Sensing Features   H               Many printers can sense the data type of a print job. SuchE               printers allow you to specify how and whether the auto- C               sensing feature is enabled, per interconnect channel, E               through the front panel or printer management software.     I                                                     DCPS Restrictions 3-1                    =           For most printers that offer this feature, the DCPSn<           software works properly when the printer is set to?           "PostScript" mode or to "Auto-Sensing" mode. You must C           set such printers to operate in one of these modes before >           starting the DCPS queues. The DCPS software does not?           operate properly if the printer is set to "PCL" mode.   ?           See Chapter 2 and the DCPS System Manager's Guide for !           additional information.a  A     3.3 Job Remains in Starting State for Raw TCP/IP or LAT Queue   A           Most printers respond to the PostScript synchronization_E           command at the beginning of a DCPS job, but some do not. IftC           all jobs to a queue remain in the Starting state, you maye2           need to take one of the following steps:  ,           o  Change Printer Language Setting  B              Often, setting the printer's language-sensing mode toC              PostScript, instead of auto-sensing between PostScriptsC              and PCL, will solve the problem. Refer to your printerrD              documentation for instructions on changing the languageC              for the appropriate port. This is the preferred methodo&              for avoiding the problem.  (           o  Define NO_SYNC Logical Name  A              If the problem is not solved by changing the printeri>              setting, you can tell DCPS to skip the PostScriptA              synchronization command by defining the logical namer>              DCPS$queue-name_NO_SYNC and restarting the queue.@              This works with printers that use Raw TCP/IP or LATD              connections on built-in Network Interface Cards (NICs).@              It has no effect when using printers connected with!              other interconnects.t  :     3.4 Job Remains in Starting State for Raw TCP/IP Queue  ;           If you set up a DCPS queue that uses a Raw TCP/IPiA           connection and specify an incorrect TCP port number for B           the printer, any print jobs that you submit to the queueE           will remain in a starting state. DCPS cannot determine thatMA           you have provided an incorrect port number, because the_B           network failure that it receives is no different than if/           the printer had been busy or offline.        3-2 DCPS Restrictions. .  .              I               Note that a print job in a Raw TCP/IP queue may remain in aC7               starting state for other reasons as well.   I               Check the documentation for your printer, network interface.E               card, print server, or terminal server to determine the.E               correct TCP port number to use. The TCP port number may *               also be listed in Table A-1.  8         3.5 Connection Terminations for Raw TCP/IP Queue  G               You may get CONTERMINATED errors for long print jobs when.I               using Raw TCP/IP connections, especially with printers that G               have large memory or disks for spooling data, such as the-G               HP Color LaserJet 9500 and LaserJet 9055 MFP and 9065 MFP                printers..  I               For jobs that consist of a single file or that only use theaG               native PostScript capability of the printer, these errors.F               are most likely to occur at the end of the job, with jobG               trailer pages (if specified) and print job accounting (if.I               enabled) being lost. For other jobs, these errors may occur D               in the middle of the job, with subsequent documents asH               well as the trailer pages and accounting information beingH               lost. DCPS requeues the terminated jobs, placing them in aI               Holding state so that you can reprint them once you resolve.&               the termination problem.  F               Some network devices, including HP JetDirect cards, dropB               a TCP/IP connection if they do not receive any inputE               from the host system within a specified amount of time.VC               This is a feature meant to prevent host software fromuC               monopolizing the device. DCPS, however, waits for thenH               printer to acknowledge that previous documents are printedC               before switching from PostScript to some other native F               printer language and also before printing a trailer pageC               and gathering accounting information. Even though the I               printer may be busy, the NIC may not receive any more input-6               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 H               determine if and how this is possible. (Recent HP printersH               call this setting the TCP/IP "idle timeout".) Then releaseF               any requeued jobs for which desired output was lost, and-               delete the other requeued jobs.   I                                                     DCPS Restrictions 3-3. .  .              C           Note that it is the length of a job in time (versus size)iD           that is important. For example, a small PostScript programC           can take a long time to print. Therefore, it is difficult 5           to predict how large a timeout is adequate..  =     3.6 NOT_READY Warnings for Unavailable Raw TCP/IP PrinterP  @           If a job is queued to a printer that uses a Raw TCP/IPB           connection, and the printer is busy or offline, you will9           get NOT_READY warning messages for the printer.i  ?           If you believe or determine that the printer is busy,.B           you can ignore these messages. DCPS cannot differentiate>           between the printer being busy, offline or otherwise           unavailable.  4     3.7 Translators Do Not Generate Color PostScript  D           The translators provided with DCPS (for example, ReGIS) doE           not generate color PostScript commands, even if your source.A           file contains color information. The colors are insteadO/           translated to various shades of gray.f  >     3.8 Job Trailer Page Jogs with PostScript Level 2 Printers  E           When job jogging is enabled on PostScript Level 2 printers, B           jogging occurs between the body of a job and its trailer           page (if any).  B     3.9 Unable to Perform ANSI Tray Selection for Certain Printers  <           An attempt to print an ANSI file containing a trayB           selection escape sequence might fail, depending on whichB           printer you are using. If so, the job might abort with aD           PostScript configuration error, with the offending command           being "setpapertray".   ?           Also, some printers, such as the Compaq Laser Printers@           LN16 and GENICOM microLaser 170, have input trays with@           PostScript tray numbers of 0. The ANSI escape sequenceA           DECASFC is used to select trays, but a value of 0 means @           "no tray change" and selecting tray 0 is therefore not;           possible. For example, an ANSI escape sequence ofe                 <CSI>0!v  C           does not select tray 0, but rather indicates no change ofi           tray.-       3-4 DCPS Restrictions  i                 H               A workaround to this problem is to create and subsequentlyB               invoke a setup module that redefines the settoptray,I               setbottomtray, setlcittray and setmanualfeedtray PostScript <               commands within the TRN$XLATE_DICT dictionary.  C               For example, for a Compaq Laser Printer LN16, DIGITAL @               Laser Printer LN15 or LN15+, or GENICOM microLaserE               170, you should create a setup module that contains thewE               following definitions for settoptray, setbottomtray ande                setmanualfeedtray:  &                   TRN$XLATE_DICT beginR                     /settoptray        { statusdict begin 0 setpapertray end } defR                     /setbottomtray     { statusdict begin 1 setpapertray end } defR                     /setmanualfeedtray { statusdict begin 3 setpapertray end } def                   ende  C               For an HP LaserJet 4M Plus, you should create a setupP#               module that contains:2  &                   TRN$XLATE_DICT beginN                     /settoptray    { statusdict begin 3 setpapertray end } defN                     /setbottomtray { statusdict begin 0 setpapertray end } defN                     /setlcittray   { statusdict begin 1 setpapertray end } def                   end   G               PostScript tray numbers are documented in the DCPS User'se               Guide.  B         3.10 Some Printers Do Not Send Status Messages to the Host  E               Because of their internal architecture, some PostScript D               printers report status information only to the printerD               console and not to the host system with which they areC               communicating. As a result, DCPS is not aware of some_H               status conditions (for example, paper out, paper jam, pageH               too complex and cover open) and cannot report them to you.E               Instead, the DCPS queue will enter the Stalled state ifeI               DCPS subsequently attempts to communicate with the printer. G               This subsequent attempt may come during the same job that >               first experienced the problem or in a later one.  C               The following is a list of some of the printers which $               exhibit this behavior:  (                  - DEClaser 5100 printer!                  - LN17ps printero  I                                                     DCPS Restrictions 3-5                    @              - some HP LaserJet III and IV printers (but not the@              HP LaserJet III with the HP PostScript-Plus Level 2B              cartridge or the HP LaserJet IIISi if jam recovery is              disabled)  5     3.11 Printer Name Is Not Always Printed Correctlyh  B           When multinational characters are used in the PostScriptB           "printername", the printer name printed on the bottom of@           separation pages may be printed in the wrong character           set.  ?     3.12 DDIF Printing Requires DECwindows Software or DECimage           Application Services4  B           To print DDIF encoded bitonal images, DCPS requires that?           either DECwindows software or Version 3.1 of DECimageoA           Application Services (DAS) be installed on your system. 7           DAS is only available on OpenVMS VAX systems.d  :     3.13 Compatibility of NUMBER_UP and PostScript Drivers  >           PostScript files created with the LaserWriter 8.0 or?           8.1.1 driver or the Adobe[R] 2.1.1 Windows[R] driver, ?           in conjunction with the user application, may produceuE           PostScript files that do not print as expected with NUMBER_            UP greater than 1.  B           Symptoms include pages being clipped, printed outside of?           the NUMBER_UP page spots, or being improperly scaled.   4     3.14 LIST Translator Ignores PAGE_SIZE Parameter  B           The LIST translator ignores the PAGE_SIZE parameter whenD           formatting pages. It creates pages with maximum content at;           a size adequate for both A (Letter) and A4 paper:n  7              PORTRAIT ORIENTATION: 80 columns, 70 linesr9              LANDSCAPE ORIENTATION: 150 columns, 66 lines(  >           It is still possible to use PAGE_SIZE and SHEET_SIZE>           parameters together to scale the logical page onto a           different size sheet.          3-6 DCPS Restrictionst    e              ?         3.15 Embedded PJL Commands Discarded; Avoid Binary Mode   G               Drivers that create files for PJL printers, such as those B               for the DEClaser 5100 and the HP LaserJet IV family,I               include printer control commands in HP Printer Job LanguagetH               (PJL). DCPS filters out and discards that data. Therefore,H               printer options selected by such drivers do not affect the               print job.  E               When using these drivers, do NOT select binary mode. It D               will insert additional commands into the file that canH               cause incorrect behavior when printing via DCPS. The exactC               form of behavior depends on which printer is actuallypF               connected to the queue and whether or not the job passes(               through a DCPS translator.  I         3.16 Avoid STOP /QUEUE /RESET Usage for PrintServer Printer Which %              Is Rejecting Connectionsk  F               If you issue a STOP /QUEUE /RESET command for a queue toC               a DIGITAL PrintServer printer while there is a job inoE               the "Starting" state and while the printer is rejectingi@               connections (because, for example, the PrintServerA               is powered off or is booting), the queue will stop.SC               Occasionally the symbiont process will not terminate.uF               Avoid issuing this command until the PrintServer printerF               becomes available. If the job is in the "Starting" stateE               and also in the PrintServer printer's job queue, a STOP 3               /QUEUE /RESET will execute correctly.   1         3.17 No Job Trailer Page on DELETE /ENTRY   F               If you issue a DELETE /ENTRY command when the printer isI               printing the job trailer page, it is possible to delete the G               printing of this page. Also, if you issue a DELETE /ENTRY G               command for a job printing on a PrintServer printer afteroH               all the data for the file is sent, it is possible that the.               job trailer page will not print.              I                                                     DCPS Restrictions 3-7h r  s              B     3.18 Problems with PostScript Files When Printing with /COPIES  >           When you use the /COPIES qualifier with a PostScriptA           file, DCPS surrounds each file with a PostScript "save"tA           and "restore" to avoid exhausting virtual memory in thec           printer.  @           However, there are infrequent cases when the print job?           aborts with an invalid restore error message. If thisoB           occurs, use the /JOB_COUNT qualifier instead of /COPIES.  2     3.19 Problems Using PAGE_LIMIT with /JOB_COUNT  A           If you use the PAGE_LIMIT parameter with the /JOB_COUNT E           qualifier, you may get undesired results. In particular, if D           your intent is to suppress some initial pages of your job,C           DCPS will suppress them for the first copy of the job but B           print all pages of subsequent job copies. If your intentE           is to suppress some of the trailing pages of your job, DCPS C           will suppress them for the first copy of the job and omit             subsequent job copies.  A           If you want multiple copies of your job with some pageseC           suppressed, issue the PRINT command the desired number ofm;           times rather than using the /JOB_COUNT qualifier.t  ?     3.20 Setting I/O Buffers Too Small May Produce OPCOM Errorso  E           If the size of the I/O buffers (set by the SYSGEN parameteraC           MAXBUF) is too small, the print queue will be stopped and ;           the following message will be displayed to OPCOM:,  7               %SYSTEM-E-EXQUOTA, process quota exceededi  @           If this error occurs, increase the value of the SYSGEN           parameter MAXBUF.                        3-8 DCPS Restrictions  _  _                    I                                                                         4 I         _________________________________________________________________d  I                                       Other Restrictions that Affect DCPSo    I               This chapter contains information about other problems thatnI               are known to impact DCPS and patch kits (ECOs) that addresssG               some of these problems. Patch kits for supported versionstI               of OpenVMS are listed, although there may be kits available !               for other versions.   E               You can obtain these patch kits (or an update to them):   3               o  From an HP Customer Support Center   9               o  From the HP IT Resource Center (ITRC) at '                  http://www.itrc.hp.com   8         4.1 DCPS Processes Consume CPU after Time Change  H               In certain situations, DCPS symbiont processes can consumeE               excessive CPU time. For example, when the time is moved.@               forward at the Standard Time/Daylight Savings TimeH               adjustment, multithreaded processes such as DCPS went intoE               a tight CPU loop. Stopping and restarting the processesc#               resolved the problem.c  E               This problem can happen again at the next Standard TimepD               /Daylight Savings Time adjustment unless the following               patch is applied:b  C               o  VMS732_TDF-V0200, for OpenVMS Alpha V7.3-2 systems   B               o  VMS73_TDF-V0500, for OpenVMS Alpha V7.3-1 systems  @               o  VMS73_TDF-V0100, for OpenVMS Alpha V7.3 systems  G               If DTSS is used to synchronize time, the following DECnet +               patch should also be applied:a  G               o  AXP_DNVOSIECO01-V732, for OpenVMS Alpha V7.3-2 systemso  G               o  AXP_DNVOSIECO03-V731, for OpenVMS Alpha V7.3-1 systemsp  D               o  AXP_DNVOSIECO04-V73, for OpenVMS Alpha V7.3 systems  I                                   Other Restrictions that Affect DCPS 4-1p t  y              >           o  VAX_DNVOSIECO04-V73, for OpenVMS VAX V7.3 systems  7     4.2 Starting Queue Causes Invalid Device Name Error   E           When initializing and starting an autostart DCPS queue that D           uses the Raw TCP protocol, the queue manager can fail with)           an "invalid device name" error.j  F               %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%0               Message from user SYSTEM on LATESTR               %QMAN-I-QUENOTSTART, queue TEST4 could not be started on node LATEST  F               %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%0               Message from user SYSTEM on LATESTG               -QMAN-I-QUEAUTOOFF, queue TEST4 is now autostart inactive   F               %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%%0               Message from user SYSTEM on LATEST5               -SYSTEM-F-IVDEVNAM, invalid device names  5           The following patch kit fixes this problem:   @           o  VMS731_QMAN-V0100, for OpenVMS Alpha V7.3-1 systems  =     4.3 Problems Starting Queues with Multistreamed Symbiontsw  >           All sites running DCPS as a multistreamed process onC           OpenVMS V7.1 and earlier should install the Queue Manager            Remedial Update.  5           The Queue Manager remedial update kits are:j  :           o  ALPQMAN03_062, for OpenVMS Alpha V6.2 systems  8           o  VAXQMAN05_062, for OpenVMS VAX V6.2 systems  :           o  VAXQMAN03_070, for OpenVMS VAX V5.5-2 systems  C           This update corrects problems that cause the START /QUEUEdD           command to hang under certain circumstances when operatingC           with a multistreamed symbiont. The release notes providedk>           with the kit describe all the problems fixed by thisB           update. After installing this update, you need to reboot.           your system to enable these changes.  +     4-2 Other Restrictions that Affect DCPSn r  s              C               If this update is not installed, a queue running in a.D               multistreamed process that is stopped with STOP /QUEUEE               /RESET and quickly started with START /QUEUE will hang.sF               Also, the following message will sometimes be written to               OPCOM:  G                   %DCPS-F-STREAMUSE, Request 4 for Stream Id n ignored.O4                   Not consistent with symbiont state  E               To recover, issue a Ctrl/Y to return to the DCL prompt,rH               then issue a STOP /QUEUE /RESET again, wait a few seconds,F               and try to start the queue again. To avoid this problem,/               install the queue manager update.O  6         4.4 I/O Errors for Serially-Connected Printers  I               There is an OpenVMS terminal driver problem that may result H               in your printer reporting I/O problems when connected to aI               serial port of your OpenVMS system. You may see the problem_H               with OpenVMS Alpha V6.2 through V7.0, and with OpenVMS VAXI               V5.5 through V7.0, depending in part on what kind of serialo!               port you are using.U  H               The problem is that the terminal driver sometimes does notH               respond quickly enough to an XOFF request from the printerF               to prevent the printer from losing data. This problem is*               fixed in OpenVMS Alpha V7.1.  9               The following patch kit fixes this problem:g  >               o  ALPOPDR04_062, for OpenVMS Alpha V6.2 systems  H         4.5 Symbiont Aborts with Access Violation or Bad Parameter Error  D               The DCPS symbiont can abort with an ACCVIO or BADPARAMB               error, possibly also indicating the CMA (DECthreads)C               facility. Other software on your system, including HP C               TCP/IP Services for OpenVMS and anything layered upon (               DECthreads, may also fail.  ?               The problem is related to a long-standing OpenVMSoC               restriction of fewer than 10,000 days in a delta-time5D               value. POSIX-related software in particular, using theE               UNIX[R] reference date of 1 January 1970, can encounterP               this limit.i  I                                   Other Restrictions that Affect DCPS 4-3                    4           The following patch kits fix this problem:  :           o  ALPLIBR07_070, for OpenVMS Alpha V6.2 systems  C           o  VAXLIBR06_070, for OpenVMS VAX V5.5-2 and V6.2 systemst                                                                                +     4-4 Other Restrictions that Affect DCPSR U                       I                                                                         A I         _________________________________________________________________   I                                                   Raw TCP/IP Port Numberse    I               When setting up a DCPS queue using a Raw TCP/IP connection, E               check the documentation for your network interface cardYE               (NIC), print server or terminal server to determine theAD               number of its Raw TCP/IP port (if it has one). The RawB               TCP/IP port must support bidirectional communication:               between the printer and your OpenVMS system.  E               Table A-1 shows the port numbers for some commonly-used                devices.  I               Table_A-1_Raw_TCP/IP_Port_Numbers__________________________A  D                  20nn  DECserver terminal servers, where "nn" is the+                        physical port numberOG                  2501  DIGITAL LN17ps and DIGITAL Laser Printer LN17+psw"                        Emulex NICs;                  3001  DIGITAL Laser Printer LN15 and LN15+t:                        DIGITAL RapidPrint 500 print server1                  6869  Compaq Laser Printer LNC02 A                        DIGITAL Laser Printer LN20, LN40 and LNC02 @                  9100  Compaq Laser Printer LN16, LN32 and LNM40A                        GENICOM Intelliprint mL, LN and microLasery                        printersr=                        GENICOM RapidPrint MPS100 print server 1                        HP Color LaserJet printerst+                        HP LaserJet printers -                        IBM InfoPrint printerseC                        Lexmark C, Optra, S, Optra T, T and W seriess                        printers 0                        Tektronix Phaser printers1                        Xerox DocuPrint N printersoB                        HP JetDirect, Lexmark and XCD print serversI               ___9101__HP_9085_MFP_______________________________________e      I                                               Raw TCP/IP Port Numbers A-1r