DECprint_Supervisor_for_OpenVMS_____________________ Release Notes June 1997 These release notes describe restrictions, usage hints, and other useful information for DECprint Supervisor for OpenVMS, Version 1.4. Revision/Update Information: These release notes supersede all other documentation. Operating System & Versions: OpenVMS VAX Version 6.1 or higher OpenVMS Alpha Version 6.1 or higher Software Version: DECprint Supervisor for OpenVMS, Version 1.4 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ June 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1997. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, DEC, DEClaser, DECnet, DECprint, DIGITAL, LN03Q, OpenVMS, PATHWORKS, PrintServer, ReGIS, VAX, VAX DOCUMENT, VMS, and the DIGITAL logo. PostScript is a trademark of Adobe Systems Incorporated, which may be registered in certain jurisdictions. AppleTalk, EtherTalk, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, Inc. MultiNet is a registered trademark of Cisco Systems, Inc. Hewlett-Packard, PCL and LaserJet are trademarks of Hewlett-Packard Company. Proprinter is a registered trademark of International Business Machines Corp. Optra is a registered trademark of Lexmark International, Inc. Colormate is a trademark of NEC. TEKTRONIX is a trademark of Tektronix, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... ix 1 DCPS Version 1.4 Information 1.1 DCPS Version 1.4 Highlights................... 1-1 1.2 DCPS Version 1.4 Fixes........................ 1-1 1.2.1 Only One Bin Gets a Separator Page if Collating without OUTPUT_TRAY ............ 1-2 1.2.2 LN17ps Printer Hangs in Processing State..................................... 1-2 1.2.3 Output may be Clipped on the LN17ps....... 1-2 1.2.4 Erroneous TRAYSUBST messages.............. 1-3 1.2.5 Required Device Control Module Not Found for PrintServer Printers ................. 1-3 1.2.6 Erroneous Connection Termination Error for DEClaser 5100 ............................ 1-3 1.2.7 PrintServer Printer Hangs when Network Connection is Lost and Jobs are Pending .......................................... 1-3 1.2.8 Problems with VFC Files Containing Large Control Fields ........................... 1-4 1.2.9 ANSI Text not Wrapped Properly when Using a Form.................................... 1-4 1.3 DCPS Version 1.4 Changes...................... 1-4 1.3.1 Support for Raw TCP/IP Connections........ 1-4 1.3.2 "IP_CPAP" Replaces "TCPIP" Connection Type...................................... 1-5 1.3.3 Automatic Stopping and Restarting of Queues During Installation................ 1-6 1.3.4 Support for Cisco MultiNet For OpenVMS Software.................................. 1-6 1.3.5 New Paper Sizes........................... 1-7 iii 1.3.6 Device Control Modules Changed for All Printers ................................. 1-7 1.3.7 Support for Indexed and Relative Files.... 1-7 1.3.8 ALL-IN-1 Compatibility Kit Removed........ 1-8 1.3.9 DCPS User Card Removed.................... 1-8 2 DCPS Restrictions 2.1 Job Remains in Starting State for Raw TCP/IP Queue......................................... 2-1 2.2 Connection Terminations for Raw TCP/IP Queue......................................... 2-1 2.3 NOT_READY Warnings for Unavailable Raw TCP/IP Printer....................................... 2-2 2.4 Translators do not Generate Color PostScript.................................... 2-2 2.5 Job Trailer Page Jogs with Certain Printers... 2-3 2.6 Unable to Perform ANSI Tray Selection for Certain Printers ............................. 2-3 2.7 AppleTalk Queues Do Not Start or Jobs Remain in Starting State ............................ 2-3 2.8 Some Printers Do Not Send Status Messages to the Host...................................... 2-4 2.9 Printer Name is Not Always Printed Correctly..................................... 2-5 2.10 DDIF Printing Requires DECwindows Software or DECimage Application Services................. 2-5 2.11 Compatibility of NUMBER_UP and PostScript Drivers....................................... 2-5 2.12 LIST Translator Ignores PAGE_SIZE Parameter... 2-5 2.13 Embedded PJL Commands Discarded; Avoid Binary Mode.......................................... 2-5 2.14 Unreliable Communication after Errors on Some Printers ..................................... 2-6 2.15 Deleting Job when Using AppleTalk............. 2-6 2.16 Avoid STOP/QUEUE/RESET Usage for PrintServer Printer which is Rejecting Connections........ 2-7 2.17 No Job Trailer Page on DELETE/ENTRY........... 2-7 2.18 Problems with PostScript Files when Printing with /COPIES ................................. 2-7 2.19 Problems Using PAGE_LIMIT with /JOB_COUNT..... 2-7 2.20 Printers with Auto-Sensing Features........... 2-8 iv 2.21 Setting I/O Buffers Too Small May Produce OPCOM Errors.................................. 2-8 2.22 Cannot Start Queue for PrintServer Printer.... 2-8 3 OpenVMS Restrictions that Affect DCPS 3.1 Problems Starting Queues with Multistreamed Symbionts..................................... 3-1 3.2 Problem Starting Queues for LAT- and Direct-Connected Printers..................... 3-2 3.3 I/O Errors for Serially-Connected Printers.... 3-3 3.4 Symbiont Aborts with Insufficient Dynamic Memory Error.................................. 3-3 3.5 Symbionts Aborts with Access Violation or Bad Parameter Error .............................. 3-3 4 Printer-Specific Information 4.1 Hewlett-Packard LaserJet 4MV Printer.......... 4-1 4.1.1 Support for B5 Paper Sizes................ 4-1 4.2 Hewlett-Packard LaserJet 5SiMX Printer........ 4-2 4.2.1 Support for B5 Paper Sizes................ 4-2 4.3 Lexmark Optra Rt+............................. 4-2 4.3.1 Support for B5 Paper Sizes................ 4-2 5 DCPS Version 1.3 Information 5.1 DCPS Version 1.3 Highlights................... 5-1 5.2 DCPS Version 1.3 Fixes........................ 5-1 5.2.1 Repeated Messages for Queue with Invalid LAT Device ............................... 5-1 5.2.2 Erroneous Connection Termination Error for DEClaser 5100 ............................ 5-1 5.2.3 Queue Stalls Indefinitely While Printing End of Document .......................... 5-2 5.2.4 DCPS Installation Repeatedly Gets %DCL-W-SYMOVF Errors ..................... 5-2 5.2.5 Symbiont Termination when All Message Fields Disabled .......................... 5-2 5.2.6 Online Help Fixed and Expanded............ 5-2 5.2.7 Gray Bars from the LIST Translator Are More Visible ............................. 5-2 v 5.2.8 Automatic Scaling When Queue Has PAGE_SIZE and SHEET_SIZE Parameters ................ 5-3 5.2.9 Job Log and Job Trailer Pages Sent to Specified Output Tray .................... 5-3 5.3 DCPS Version 1.3 Changes...................... 5-4 5.3.1 New C6 Paper Size......................... 5-4 5.3.2 Device Control Modules Changed for UNRECOGNIZED Printer ..................... 5-4 6 DCPS Version 1.2 Information 6.1 DCPS Version 1.2 Highlights................... 6-1 6.2 DCPS Version 1.2 Fixes........................ 6-2 6.2.1 Truncated Lines when A4 Page is Printed Landscape................................. 6-2 6.2.2 AppleTalk Printer Names with Multinational Characters................................ 6-3 6.2.3 DELETE/ENTRY and "(DCc) Circuit connect failure".................................. 6-3 6.2.4 Speed of Printing of Certain File Types... 6-3 6.2.5 Handling of Communications Problems on Serial Interconnect....................... 6-3 6.2.6 DCPS$queuename_PID Logical and Startup Errors.................................... 6-4 6.2.7 Looping when Handling Messages with ']' in Job: field................................ 6-4 6.2.8 Handling of Long Device Names in DCPS$STARTUP.COM.......................... 6-4 6.2.9 Form Setup Modules and Multiple File Jobs...................................... 6-4 6.2.10 Interrupting Busy Printers When a Job Starts.................................... 6-4 6.2.11 Suppressing PostScript Synchronization when a Job Starts......................... 6-5 6.2.12 DDIF Files with Invalid Parameter Values.................................... 6-5 6.2.13 Insufficient Event Flags.................. 6-5 6.2.14 PostScript Operator findfont Has Been Modified.................................. 6-5 6.2.15 OUTPUT_TRAY=LCOS Not Supported for PrintServer 17 Printers................... 6-6 6.3 DCPS Version 1.2 Changes...................... 6-6 vi 6.3.1 Running DECprint Supervisor as a Multistreamed Process..................... 6-6 6.3.2 AppleTalk Interconnect Supported on OpenVMS Alpha Systems..................... 6-6 6.3.3 DCPS Includes Files for the DEClaser 3500 FAX Option................................ 6-6 6.3.4 The Network Printer Setup Utility Updated................................... 6-6 6.3.5 Logical to Enable Device Control Library Caching................................... 6-6 6.3.6 DCPS$STARTUP.TEMPLATE Updated............. 6-7 6.3.7 Executable Components Check for Compatible Versions.................................. 6-7 6.3.8 Reducing the Amount of Memory and Idle Time CPU.................................. 6-7 7 DCPS Version 1.1A Information 7.1 DCPS Version 1.1A Fixes....................... 7-1 7.1.1 Corrected Timeout Problem With LAT Protocol on Network Cards................. 7-1 7.1.2 ANSI Translator Printing with A4 Landscape................................. 7-1 7.1.3 PCL Translator Handles Duplexing on PostScript Level 2 Printers............... 7-1 7.1.4 Correction for ANSI Performance Problem on PrintServer Printers...................... 7-2 7.1.5 Remote Console Aborted Jobs on PrintServer Printers.................................. 7-2 7.1.6 New Format for the Log Files.............. 7-2 7.1.7 Device Control Module Cache Problem Corrected................................. 7-2 7.1.8 Problem with P2 in DCPS$EXECUTION_QUEUE.COM Fixed............ 7-2 7.2 DCPS Version 1.1A Changes .................... 7-3 7.2.1 Process ID Logical Created by Symbiont.... 7-3 vii 8 DCPS Version 1.1 Information 8.1 DCPS Version 1.1 New Features................. 8-1 8.1.1 New Interconnects and New Device Specification Syntax...................... 8-1 8.1.2 Native PCL Accessible on Some Printers.... 8-1 8.1.3 Suprressing the OPCOM Message "User Name Not Found"................................ 8-2 8.1.4 Device Control Library Cache Feature...... 8-2 8.1.5 ANSI Prologue File........................ 8-3 8.2 DCPS Version 1.1 Fixes........................ 8-3 8.2.1 Separator Tray Logical Works on Generic and Execution Queues...................... 8-3 8.2.2 Suppressed Messages NOPAGEREGIONOP and NOSETPAGEDEVICE........................... 8-3 8.2.3 Fixed Problems Printing VFC Files......... 8-3 8.2.4 Increased Range of PAGE_LIMIT to 999999... 8-4 8.2.5 Fixed Abort when All Message Fields Disabled.................................. 8-4 8.2.6 Fixed ANSI Jobs with "Sinking Accented Capital Letters".......................... 8-4 8.2.7 Library Search List Correctly Searched.... 8-4 8.2.8 Empty Setup Module No Longer Hangs Supervisor................................ 8-4 8.2.9 Corrected PostScript Handling in Layup.... 8-4 8.2.10 LCIT Keyword Now Recognized for PrintServer 17............................ 8-4 8.2.11 Fixed OUTPUT_TRAY=SIDE for PrintServer 17........................................ 8-5 8.2.12 Fixed Delay for Manual Feed with Apple and Hewlett-Packard Printers.................. 8-5 8.3 DCPS Version 1.1 Changes...................... 8-5 8.3.1 Support for Non-DIGITAL Printers.......... 8-5 8.3.2 Enhancements to the PCL Translator........ 8-5 8.3.3 LN03 Image Printer........................ 8-6 8.3.4 The State of a Printer Is Not Known Until a Job Prints ............................. 8-7 8.3.5 New Behavior for Serial Interconnect...... 8-7 viii A List of Files Installed on Alpha Systems B List of Files Installed on VAX Systems ix _________________________________________________________________ Preface Introduction The primary source of information about DECprint Supervisor (DCPS) for OpenVMS, Version 1.4 is the following set of software manuals: o DECprint Supervisor for OpenVMS Software Installation Guide o DECprint Supervisor for OpenVMS System Manager's Guide o DECprint Supervisor for OpenVMS User's Guide Release Notes Contents These release notes provide detail on the following: o Product changes since previous versions. Some changes provide new features or new printer support. Other changes have been made to correct problems with earlier versions. o Restrictions in DECprint Supervisor Version 1.4. o Additional information about DECprint Supervisor SPD Contents For information on licensing requirements and the features available with each license, see the DECprint Supervisor Software Product Description (SPD 44.15.xx). ix 1 _________________________________________________________________ DCPS Version 1.4 Information 1.1 DCPS Version 1.4 Highlights The following list provides a brief description of the significant changes included in DECprint Supervisor Version 1.4. You can find more information for several of these changes elsewhere in these release notes. o Communication with printers via Raw TCP/IP Sockets o Support for the following printers: Hewlett-Packard LaserJet 4MV Hewlett-Packard LaserJet 5M (monochrome version) Hewlett-Packard LaserJet 5SiMX Lexmark Optra Rt+ o Automatic stopping and restarting of active DCPS queues during installation o Support for Cisco MultiNet for OpenVMS Software for IP connectivity o Revised hardcopy documentation o A minimum supported OpenVMS version of 6.1 1.2 DCPS Version 1.4 Fixes This section lists problems that have been corrected in DCPS V1.4. DCPS Version 1.4 Information 1-1 1.2.1 Only One Bin Gets a Separator Page if Collating without OUTPUT_TRAY If the default output tray for the LN17ps was set to the collator and a SHEET_COUNT=n parameter for the print job was specified without also specifying the OUTPUT_TRAY=xxx parameter, only one copy of any separator page (job burst, flag, or trailer page) would be generated. Further, such pages would be delivered to random bins. 1.2.2 LN17ps Printer Hangs in Processing State When the LN17ps collator was specified as the default output tray and the input tray was MANUAL_FEED, the printer would hang when the specified SHEET_COUNT was greater than one. This error occurred most often while printing trailer pages. On some occasions, a blank data sheet was sent to the collator just prior to the printer hanging. This problem is attributed to both a bug in the LN17ps printer and in DCPS V1.3. With the DCPS V1.4 fix, you are unlikely to see this problem. 1.2.3 Output may be Clipped on the LN17ps Printer output on the LN17ps might have been clipped when the following conditions were met: o you specified an INPUT_TRAY value of FRONT or MULTIPURPOSE o you specified a sheet size o the imageable area of the requested sheet size was larger than the console-specified size for the manual tray To avoid such clipping, use INPUT_TRAY=MANUAL_FEED. When you specify an INPUT_TRAY value of FRONT or MULTIPURPOSE for the LN17ps along with a sheet size, DCPS V1.4 now requires you to specify the sheet size that matches the console-specified manual size. 1-2 DCPS Version 1.4 Information 1.2.4 Erroneous TRAYSUBST messages Erroneous DCPS-I-TRAYSUBST messages may have occurred for specific output trays for the following printers: ___________________________________________________________ Output Printer_____Tray________Substitution_Reported______________ LN17ps Top OCT LN17ps Upper OCT LPS17 LCOS 2 LPS32 LCOS 4 LPS40_______LCOS________4__________________________________ The correct tray was selected even though the erroneous TRAYSUBST message was issued. 1.2.5 Required Device Control Module Not Found for PrintServer Printers If the first job submitted to a DIGITAL PrintServer printer contained an invalid parameter, a "Required device control module LPS$$INITPSDEVICE not found" error message was issued and the print queue stopped. This error occurred only if the first job printed contained an invalid parameter. This error did not occur with desktop printers. 1.2.6 Erroneous Connection Termination Error for DEClaser 5100 DCPS was unable to communicate with the DEClaser 5100 via the NIC card, and would instead consistently fail with CONTERMINATED errors. This problem was erroneously believed to have been fixed in DCPS V1.3, as reported in Section 5.2.2. 1.2.7 PrintServer Printer Hangs when Network Connection is Lost and Jobs are Pending A DCPS print queue could hang when all the following conditions were true: o A DCPS print job was pending (that is, not the current job) on the DIGITAL PrintServer printer o The DCPS to PrintServer printer interconnect was TCP/IP DCPS Version 1.4 Information 1-3 o The network connection to the PrintServer printer was lost This was fixed in DCPS V1.4 by enabling the KEEPALIVE option for such TCP/IP connections. However, if your system is configured for unusually long KEEPALIVE timeouts, you may continue to see this problem. If so, you may recover by deleting the job (DELETE/ENTRY) or stoping the queue (STOP/QUEUE/RESET). 1.2.8 Problems with VFC Files Containing Large Control Fields If you printed a VFC-formatted file that utilized a fixed- length control field larger than two (2) bytes, the DCPS symbiont could abort with an access violation (ACCVIO) or other error. 1.2.9 ANSI Text not Wrapped Properly when Using a Form If you printed ANSI text with a form that specified the /WRAP qualifier, the input records were sometimes broken into output line segments that exceeded the usable line width implied by the form. 1.3 DCPS Version 1.4 Changes This section describes the DCPS V1.4 changes 1.3.1 Support for Raw TCP/IP Connections DCPS V1.4 adds the ability to communicate with printers via raw TCP/IP sockets. Raw TCP is a network protocol that utilizes the TCP/IP protocol directly without any additional interpretation of the TCP data stream. It is supported by many printer Network Interface Cards (NICs), print servers, and terminal servers. There are other printer protocols that layer upon TCP/IP, including CPAP (Common Printer Access Protocol), LPD, and Telnet. DCPS uses CPAP to communicate with DIGITAL PrintServer printers. DCPS does not support LPD or Telnet. To communicate with your printer using raw TCP/IP, the NIC, print server, or terminal server that you use to connect your printer to the network must provide a raw TCP/IP port. Further, this raw TCP/IP port must support bidirectional communication between the printer and your OpenVMS system. DCPS does not work with unidirectional ports, such as those 1-4 DCPS Version 1.4 Information found on the NICs for the DEClaser 3500 and 5100 printers, the RapidPrint 200, and Hewlett-Packard JetDirect cards that interface with the printer via its XIO (versus MIO) slot. To create a DCPS queue that uses a raw TCP/IP connection, edit DCPS$STARTUP.COM similarly to how you would create DCPS queues that use other types of connections. Refer to the DECprint Supervisor for OpenVMS System Manager's Guide and comments in DCPS$STARTUP.COM for the required syntax and other information. Check the documentation for your NIC, print server, or terminal server to determine the number of its raw TCP port (if it has one). Some common values are: 9100 Hewlett-Packard JetDirect, XCD, and Lexmark NICs 2501 Emulex NICs 20nn DECservers, where "nn" is the physical port number 3001 RapidPrint 500 print server If your printer is connected to a print server or terminal server using a serial line, check to ensure that the baud rate, flow control, parity, etc. of the server is set to the requirements of your printer. Ensure that your TCP software is started before you start a DCPS queue that uses TCP. If you have trouble starting the queue, you can enable an operator terminal with the REPLY/ENABLE command, or examine the operator log file (SYS$MANAGER:OPERATOR.LOG) for additional information. Note that if you specify the wrong port number for the printer, DCPS is unable to communicate with the printer. However, because the symptoms are no different than if the printer were busy, offline, etc., you do not receive any indication that the port number is illegal. 1.3.2 "IP_CPAP" Replaces "TCPIP" Connection Type In previous DCPS versions, a "tcpip/..." syntax was used in DCPS$STARTUP.COM to specify communication with a DIGITAL PrintServer printer via TCP/IP. DCPS Version 1.4 Information 1-5 In DCPS V1.4, a new "ip_cpap/..." syntax is introduced to replace the "tcpip/..." syntax. CPAP (Common Printer Access Protocol) is the network protocol supported by DIGITAL PrintServer printers, and is just one of many TCP /IP printer-related network protocols. The "tcpip/..." syntax is no longer recommended because of its ambiguity, though DCPS continues to support it. 1.3.3 Automatic Stopping and Restarting of Queues During Installation When you begin the installation of DCPS, the software scans for existing queues and notes which ones are "active". Active queues are ones that are not stopped (for example, idle, busy, etc.). If any active queues are found, their names and status are displayed, and you are then asked to decide if the installation procedure should automatically stop and later restart them. If you do not want the installation procedure to automatically stop them, you are given the options of aborting the installation or continuing with the queues active. Continuing is NOT recommended. If you choose to allow the installation procedure to stop the active queues it listed, it does so after all other installation questions are asked. If the installation is successful, the listed queues are restarted after the IVP runs. If the installation aborts, is interrupted, etc., they are NOT restarted. 1.3.4 Support for Cisco MultiNet For OpenVMS Software DCPS now supports your use of either DIGITAL TCP/IP Services for OpenVMS software or Cisco MultiNet for OpenVMS software to provide IP connectivity. In DCPS versions V1.3 and earlier, only the former was supported. Refer to the DECprint Supervisor SPD for more information and specific version requirements. 1-6 DCPS Version 1.4 Information 1.3.5 New Paper Sizes DCPS supports several new paper sizes, as listed in the table below. You can specify these new sizes as the logical PAGE_SIZE value for any printer, and as the physical SHEET_ SIZE value for the printers listed below. _________________________________________________________________ Size_Name_______Size_(mm)______Size_(inches)__Printers___________ 9_ENVELOPE 98.4 x 225.4 3.875 x 8.875 Lexmark Optra Rt+ DOUBLEPOSTCARD 148 x 200 5.827 x 7.874 HP4MV, HP5SiMX SUPER_B_________297_x_432______11.7_x_17______HP4MV,_HP5SiMX_____ 1.3.6 Device Control Modules Changed for All Printers The device control modules for all printers were changed, to reduce negative interactions with PC- and Macintosh- generated files. This was done primarily by changing the way in which DCPS uses PostScript dictionaries in the printer. However, if your applications place many definitions in PostScript's "userdict" dictionary, it is possible that these changes may have a negative impact on your print jobs. The four device control modules for "unrecognized" printers were also changed. If you made any changes to previous versions of these DIGITAL-supplied modules, you may need to rework your changes. See the DECprint Supervisor for OpenVMS System Manager's Guide and comments in the LPS$$UNRECOGNIZED_* modules for more information. 1.3.7 Support for Indexed and Relative Files DCPS now allows you to print files that utilize an indexed, relative, or sequential file organization. In DCPS versions V1.1 through V1.3, you received a BADFILEORG error if you attempted to print an indexed or relative file. Indexed and relative files are accessed sequentially, by their primary index and relative record number respectively. This new capability is consistent with the TYPE command. ________________________ Note ________________________ Indexed and relative files frequently contain binary data. Attempting to print files containing such DCPS Version 1.4 Information 1-7 unprintable binary data can give unpredictable and probably undesirable results. ______________________________________________________ 1.3.8 ALL-IN-1 Compatibility Kit Removed The ALL-IN-1 compatibility kit, and the option to install it, is no longer part of the DCPS kit for OpenVMS VAX systems. The ALL-IN-1 product now provides the printer support that was provided by the compatibility kit in earlier versions of DCPS. The compatibility kit was never necessary for OpenVMS Alpha systems. 1.3.9 DCPS User Card Removed The DCPS kit no longer includes a User Card, either in hardcopy format or online. If you installed a previous version of DCPS, the online version of this card (SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]DCPS-USER-CARD.PS) will exist in the DCPS examples directory. The information on the card is still correct, though no longer complete. 1-8 DCPS Version 1.4 Information 2 _________________________________________________________________ DCPS Restrictions The following sections identify the current restrictions that exist with DECprint Supervisor. See Chapter 4 for printer-specific restrictions. 2.1 Job Remains in Starting State for Raw TCP/IP Queue If you set up a DCPS queue that uses a raw TCP/IP connection, and specify an incorrect TCP port number for the printer, any print jobs that you submit to the queue will remain in a starting state. DCPS cannot determine that you have provided an incorrect port number, because the network failure that it receives is no different than if the printer had been busy or offline. Check the documentation for your printer, network interface card, print server, or terminal server to determine the correct TCP port number to use. The TCP port number may also be listed in Section 1.3.1, in Chapter 4, or in the DECprint Supervisor for OpenVMS System Manager's Guide. Note that a print job in a raw TCP/IP queue may remain in a starting state for other reasons as well. 2.2 Connection Terminations for Raw TCP/IP Queue You may get CONTERMINATED errors for long print jobs when using raw TCP/IP connections. For jobs that consist of a single file or only use the native PostScript capability of the printer (for example, they do not use native PCL), these errors are most likely to occur at the end of the job, with job trailer pages (if specified for the queue) and print job accounting (if enabled) being lost. For other jobs, these errors may occur in the middle of the job, with subsequent documents as well as the trailer pages and accounting information being lost. DCPS requeues the terminated jobs, placing them in a Holding state so that DCPS Restrictions 2-1 you can reprint them once you resolve the termination problem. Some network devices, including the Hewlett-Packard JetDirect cards, drop a TCP/IP connection if they do not receive any input from the host system within a specified amount of time. This is a feature, meant to prevent host software from monopolizing the device. DCPS, however, waits for the printer to acknowledge that previous documents are printed before switching from PostScript to some other native printer language and also before printing a trailer page and gathering accounting information. Even though the printer may be busy, the NIC may not receive any more input from DCPS before the timeout is reached. If your NIC allows you to alter the TCP/IP idle timeout value, you can work around this problem by disabling or increasing the timeout. Check your NIC documentation to determine if this is possible, and how to do it. Then release any requeued jobs for which desired output was lost, and delete the other requeued jobs. Note that it is the length of a job in time (versus size) that is important. For example, a very small PostScript program can take a very long time to print. Hence, it is difficult to predict how large a timeout is adequate. 2.3 NOT_READY Warnings for Unavailable Raw TCP/IP Printer If a job is queued to a printer that uses a raw TCP/IP connection, and the printer is busy or offline, you will get NOT_READY warning messages for the printer. If you believe or determine that the printer is busy, you can ignore these messages. DCPS cannot, unfortunately, differentiate between the printer being busy, offline, or otherwise unavailable. 2.4 Translators do not Generate Color PostScript The translators provided with DCPS (for example, ReGIS) do not generate color PostScript commands, even if your source file contains color information. The colors are instead translated to various shades of gray. 2-2 DCPS Restrictions 2.5 Job Trailer Page Jogs with Certain Printers With certain printers, when job jogging is enabled to separate jobs by offsetting them, jogging occurs between the body of a job and its trailer page. This is because the printer treats the trailer page as though it were a separate print job. Printers known to exhibit this behavior are: LN17ps Hewlett-Packard LaserJet IIISi Hewlett-Packard LaserJet 4SiMX 2.6 Unable to Perform ANSI Tray Selection for Certain Printers An attempt to print an ANSI file containing a tray selection escape sequence might fail, depending on which printer you are using. If so, the job aborts with a PostScript configuration error, with the offending command being "setpapertray". A workaround to this problem is to create and subsequently invoke a setup module that redefines the settoptray, setbottomtray, and setlcittray PostScript commands within the TRN$XLATE_DICT dictionary. For example, for an HP LaserJet 4M Plus, you should create a setup module that contains the following definitions for settoptray, setbottomtray and setlcittray: TRN$XLATE_DICT begin /settoptray { statusdict begin 3 setpapertray end } def /setbottomtray { statusdict begin 0 setpapertray end } def /setlcittray { statusdict begin 1 setpapertray end } def end 2.7 AppleTalk Queues Do Not Start or Jobs Remain in Starting State The first print queue in the process to use AppleTalk fails with the following error and the queue does not start: %DCPS-W-ATK_FOR_VMS, Error connecting to AppleTalk for VMS driver DCPS Restrictions 2-3 If other queues using the AppleTalk interconnect are started on that same process this error is not reported. These queues will start, but jobs on these queues remain in the "starting" state. If a queue using the AppleTalk interconnect is started before the AppleTalk network software is running, then the queue might start but will not be functional. This occurs when DCPS is running as a multistreamed symbiont and another print queue is running in the same process. To recover from such an error, stop all queues supported by any currently running symbiont processes that have detected that the AppleTalk network software is not running (one error message is generated per symbiont process). Restart the AppleTalk software and the queues. To avoid this problem, run the AppleTalk network software before starting any DCPS print queues. 2.8 Some Printers Do Not Send Status Messages to the Host Some PostScript printers, because of their internal architecture, report status information only to the printer console and not to the host system with which they are communicating. As a result, DCPS is not aware of some status conditions (for example, paper out, paper jam, page too complex, cover open, etc.) and cannot report them to you. Instead, the DCPS queue will enter the Stalled state if DCPS subsequently attempts to communicate with the printer. This subsequent attempt may come during the same job that first experienced the problem or in a later one. The following is a list of some of the printers which exhibit this behavior: - DEClaser 5100 printer - LN17ps printer - some HP LaserJet III and IV printers (but not the HP LaserJet III with the HP PostScript-Plus Level 2 cartridge or the HP LaserJet IIISi if jam recovery is disabled) 2-4 DCPS Restrictions 2.9 Printer Name is Not Always Printed Correctly When multinational characters are used in the PostScript "printername", the printer name printed on the bottom of separation pages may be printed in the wrong character set. 2.10 DDIF Printing Requires DECwindows Software or DECimage Application Services To print DDIF encoded bitonal images, DCPS requires that either DECwindows software or Version 3.1 of DECimage Application Services (DAS) be installed on your system. DAS is only available on OpenVMS VAX systems. 2.11 Compatibility of NUMBER_UP and PostScript Drivers PostScript files created with the LaserWriter 8.0 or 8.1.1 driver or the Adobe 2.1.1 Windows driver in conjunction with the application may produce PostScript files that do not print as expected with NUMBER_UP greater than 1. Symptoms include pages being clipped, printed outside of the NUMBER_UP page spots, or being improperly scaled. 2.12 LIST Translator Ignores PAGE_SIZE Parameter The LIST translator ignores the PAGE_SIZE parameter when formatting pages. It creates pages with maximum content at a size adequate for both A (Letter) and A4 paper: PORTRAIT ORIENTATION: 80 columns, 70 lines LANDSCAPE ORIENTATION: 150 columns, 66 lines It is still possible to use PAGE_SIZE and SHEET_SIZE parameters together (with the DCPS-PLUS license) to scale the logical page onto a different size sheet. 2.13 Embedded PJL Commands Discarded; Avoid Binary Mode Drivers that create files for PJL printers, such as those for the DEClaser 5100 and the HP LaserJet IV family, include printer control commands in Hewlett-Packard Printer Job Language (PJL). DCPS filters out and discards that data. Therefore, printer options selected by such drivers do not affect the print job. DCPS Restrictions 2-5 When using these drivers, do NOT select binary mode. It will insert additional commands into the file that can cause incorrect behavior when printing via DCPS. The exact form of behavior depends on which printer is actually connected to the queue and whether or not the job passes through a DCPS translator. 2.14 Unreliable Communication after Errors on Some Printers Unexpected errors can occur at the end of a print job when printing to some printers using the AppleTalk interconnect. The printers which can exhibit problems include the LaserWriter Pro 600, LaserWriter Pro 630, the LaserWriter IIg, and the LaserWriter IIf. Generally, the unexpected error occurs when an explainable error occurred during the print job; for example, a PostScript error which causes the PostScript interpreter to "Flush to the EOJ", or a timeout error while waiting for manual feed. The behavior a user may see includes one of more of the following: o A second PostScript error or timeout error occurs o DCPS unexpectedly loses communication with the printer o The job trailer page (if specified) may not print o The page count in the accounting file is not correct o A delay of up to one minute before the job completes. The user's part of the print job prints as expected. The unexpected error occurs during the end of job processing (for example, getting the page count or the job trailer page printed) done by the DECprint Supervisor. Once the offending job is complete, subsequent jobs print as expected. No system operator intervention is needed. 2.15 Deleting Job when Using AppleTalk When printing using an AppleTalk interconnect, a request to delete a job (DELETE/ENTRY) is accomplished by closing the connection to the printer. The AppleTalk protocol does not provide for interrupting the PostScript interpreter; therefore, the printer will continue to print page descriptions that are contained in its buffer before it stops printing the job. A job trailer page will not be printed. 2-6 DCPS Restrictions 2.16 Avoid STOP/QUEUE/RESET Usage for PrintServer Printer which is Rejecting Connections If you issue a STOP/QUEUE/RESET command for a queue to a DIGITAL PrintServer printer while there is a job in the "Starting" state and while the printer is rejecting connections (because, for example, the PrintServer is powered off or is booting), the queue will stop. Occasionally the symbiont process will not terminate. Avoid issuing this command until the PrintServer printer becomes available. If the job is in the "Starting" state and also in the PrintServer printer's job queue, a STOP/QUEUE/RESET will execute correctly. 2.17 No Job Trailer Page on DELETE/ENTRY If you issue a DELETE/ENTRY command when the printer is printing the job trailer page, it is possible to delete the printing of this page. Also, if you issue a DELETE/ENTRY command for a job printing on a PrintServer printer after all the data for the file is sent, it is possible that the job trailer page will not print. 2.18 Problems with PostScript Files when Printing with /COPIES When you use the /COPIES qualifier with a PostScript file, DCPS surrounds each file with a PostScript "save" and "restore" to avoid exhausting virtual memory in the printer. However, there are infrequent cases when the print job aborts with an invalid restore error message. If this occurs, use the /JOB_COUNT qualifier instead of /COPIES. 2.19 Problems Using PAGE_LIMIT with /JOB_COUNT If you use the PAGE_LIMIT parameter with the /JOB_COUNT qualifier, you are apt to get undesired results. In particular, if your intent is to suppress some initial pages of your job, DCPS will suppress them for the first copy of the job but print all pages of subsequent job copies. If your intent is to suppress some of the trailing pages of your job, DCPS will suppress them for the first copy of the job and omit subsequent job copies. DCPS Restrictions 2-7 If you want multiple copies of your job with some pages suppressed, issue the PRINT command the desired number of times rather than using the /JOB_COUNT qualifier. 2.20 Printers with Auto-Sensing Features Some printers, such as the DEClaser 5100 and the HP LaserJet 4SiMX, can sense the data type of a print job. Such printers allow you to specify how and whether the auto-sensing feature is enabled, per interconnect channel, through the front panel. For most printers that offer this feature, the DECprint Supervisor software works properly when the printer is set to "PostScript" mode, or to "Automatic" mode. You must 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 4 and the DECprint Supervisor for OpenVMS System Manager's Guide for additional information. 2.21 Setting I/O Buffers Too Small May Produce OPCOM Errors If the size of the I/O buffers, set by the SYSGEN parameter MAXBUF, is too small, the print queue will be stopped, and the following message will be displayed to OPCOM: %SYSTEM-E-EXQUOTA, process quota exceeded If this error occurs, increase the value of the SYSGEN parameter MAXBUF. 2.22 Cannot Start Queue for PrintServer Printer Because of a CPAP protocol bug in some versions of DIGITAL PrintServer Software, DCPS symbionts can be given a badly formatted packet in response to a resource query. The bad packet prevents a symbiont from starting. The problem is triggered by loading enough resources to require more than one packet describing the resources loaded to be returned. The suggested workaround is to load fewer resources. Empirical testing has found the limit to be 7 fonts. This problem is fixed in version S5.0-29 and later of the PrintServer Software. 2-8 DCPS Restrictions 3 _________________________________________________________________ OpenVMS Restrictions that Affect DCPS This section contains information about OpenVMS problems that are known to impact DECprint Supervisor and remedial patch kits ("ECOs") that address some of these problems. You can obtain these remedial patch kits (or an update to them) o From a DIGITAL Customer Support Center o Using ftp, starting with path ftp.service.digital.com/public/vms o Using the World Wide Web, starting at http://www.openvms.digital.com and following the menus to locate the DIGITAL Patch Services 3.1 Problems Starting Queues with Multistreamed Symbionts All sites running the DECprint Supervisor as a multistreamed process should install the Queue Manager Remedial Update. The Queue Manager remedial update kits are: o ALPQMAN04_070, for OpenVMS Alpha V6.1 through V7.0 o VAXQMAN03_070, for OpenVMS VAX V5.5-2 through V7.0 This update corrects problems that cause the START/QUEUE command to hang under certain circumstances when operating with a multistreamed symbiont. The release notes provided with the kit describe all the problems fixed by this update. After installing this update, you need to reboot your system to enable these changes. OpenVMS Restrictions that Affect DCPS 3-1 If this update is not installed you may encounter the following problem. If a queue running in a multistreamed process is stopped with STOP/QUEUE/RESET, then quickly started with START/QUEUE, it is possible that the start request will hang. In addition, sometimes the following message will be written to OPCOM: %DCPS-F-STREAMUSE, Request 4 for Stream Id x ignored. Not consistent with symbiont state To recover, issue a Ctrl/Y to return to the DCL prompt, then issue a STOP/QUEUE/RESET again, wait a few seconds, and try to start the queue again. To avoid this problem, install the queue manager update. 3.2 Problem Starting Queues for LAT- and Direct-Connected Printers There is an OpenVMS V7.0 terminal driver problem that may hinder you in using DCPS with LAT- and direct-connected printers. The symptom is that the associated queue cannot be started, with messages like the following being written to OPCOM: %%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.73 %%%%%%%%%%% Message from user SYSTEM on FUNYET Queue SYS$PRINT: %DCPS-E-UNSUPPORTED, unsupported operation or function %%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.74 %%%%%%%%%%% Message from user QUEUE_MANAGE on FUNYET %QMAN-I-QUENOTSTART, queue SYS$PRINT could not be started on node FUNYET %%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.74 %%%%%%%%%%% Message from user QUEUE_MANAGE on FUNYET -SYSTEM-F-ABORT, abort The failure may be constant or intermittent. If you subsequently attempt to start the queue, you may succeed. The following patch kits fix this problem: o ALPTTDR02_070, for OpenVMS Alpha V7.0 systems o VAXTTDR01_070, for OpenVMS VAX V7.0 systems 3-2 OpenVMS Restrictions that Affect DCPS 3.3 I/O Errors for Serially-Connected Printers There is an OpenVMS terminal driver problem that may result in your printer reporting I/O problems when connected to a serial port of your OpenVMS system. You may see the problem with OpenVMS Alpha V6.2 through V7.0, and with OpenVMS VAX V5.5 through V7.0, depending in part on what kind of serial port you are using. The problem is that the terminal driver sometimes does not respond quickly enough to an XOFF request from the printer to prevent the printer from losing data. This problem is fixed in OpenVMS Alpha V7.1. The ALPOPDR02_070 patch kit provides a fix for some OpenVMS Alpha V7.0 systems. 3.4 Symbiont Aborts with Insufficient Dynamic Memory Error There is a DECthreads problem on OpenVMS VAX V7.0 and V7.1 systems that results in the DCPS symbiont aborting with an INSFMEM error. The DCPS symbiont consumes an increasing amount of memory over time, eventually aborting when it attempts to obtain more than the available dynamic memory. The probability of the symbiont aborting increases with each new print job that it processes. The VAXCMAR01_071 patch kit fixes this problem. 3.5 Symbionts Aborts with Access Violation or Bad Parameter Error The DCPS symbiont can abort with an ACCVIO or BADPARAM error, possibly also indicating the CMA (DECthreads) facility, beginning 19 May 1997. Other software on your system, including DIGITAL TCP/IP Services for OpenVMS and anything layered upon DECthreads, may also fail after this date. The problem is related to a long-standing OpenVMS restriction of fewer than 10,000 days in a delta-time value. POSIX-related software in particular, using the UNIX reference date of 1 January 1970, can encounter this limit on and after 19 May 1997. Refer to the OpenVMS web pages (www.openvms.digital.com) for more information about the "Delta-Time Limit". OpenVMS Restrictions that Affect DCPS 3-3 The following patch kits fix this problem: o ALPLIBR05_070, for OpenVMS Alpha V6.1 to V7.0 systems o VAXLIBR06_070, for OpenVMS VAX V5.5 to V7.0 systems 3-4 OpenVMS Restrictions that Affect DCPS 4 _________________________________________________________________ Printer-Specific Information The following sections provide information about using DCPS with specific printers. The DECprint Supervisor for OpenVMS System Manager's Guide and DECprint Supervisor for OpenVMS User's Guide contain additional printer-specific information. 4.1 Hewlett-Packard LaserJet 4MV Printer 4.1.1 Support for B5 Paper Sizes The 4MV printer supports both the JIS and ISO standards for B5 paper sizes. For this printer, the JIS size is regarded as paper while the ISO size is regarded as an envelope. In DCPS, there is only one B5 option for specifying sheet size. DCPS handles the two B5 sizes as follows: ___________________________________________________________ Parameter________Config._____Result________________________ SHEET_SIZE=B5 ISO is Pages print in tray xxx with loaded in ISO image area tray xxx SHEET_SIZE=B5 JIS is DCPS reports "B5 medium not loaded in loaded in printer_name" tray xxx INPUT_TRAY=xxx, ISO or JIS Pages print in tray xxx with SHEET_SIZE=B5 is loaded ISO image area, regardless of (xxx is MANUAL_ in tray the B5 variant FEED) xxx INPUT_TRAY=xxx, ISO or JIS Pages print in tray xxx with SHEET_SIZE=B5 is loaded the correct image area for (xxx is in tray each B5 variant anything but xxx MANUAL_FEED)_______________________________________________ Printer-Specific Information 4-1 4.2 Hewlett-Packard LaserJet 5SiMX Printer 4.2.1 Support for B5 Paper Sizes The 5SiMX printer supports both the JIS and ISO standards for B5 paper sizes. DCPS handles the two B5 sizes as described in Section 4.1.1. 4.3 Lexmark Optra Rt+ 4.3.1 Support for B5 Paper Sizes The Optra Rt+ printer supports both the JIS and ISO standards for B5 paper sizes. DCPS handles the two B5 sizes as described in Section 4.1.1. 4-2 Printer-Specific Information 5 _________________________________________________________________ DCPS Version 1.3 Information 5.1 DCPS Version 1.3 Highlights The following list provides a brief description of the significant changes included in DECprint Supervisor Version 1.3. You can find more information for several of these changes elsewhere in these release notes. o Support for the DIGITAL LN17ps High Performance Network Printer, utilizing either the LAT or Appletalk interface. o Support for the DIGITAL Colorwriter LSR 2000 printer, utilizing the Appletalk interface. o Fixes for some problems in previous versions of DCPS. o Other changes from previous versions. 5.2 DCPS Version 1.3 Fixes This section lists problems that have been corrected in DCPS V1.3. 5.2.1 Repeated Messages for Queue with Invalid LAT Device A DCPS queue started with autostart would repeatedly display the following message when the associated LTA device was incorrectly defined: %DCPS-F-LRJNAMEUNKNOWN, Port name is unknown 5.2.2 Erroneous Connection Termination Error for DEClaser 5100 DCPS was unable to communicate with the DEClaser 5100 via the NIC card, and would instead consistently fail with CONTERMINATED errors. DCPS Version 1.3 Information 5-1 5.2.3 Queue Stalls Indefinitely While Printing End of Document A DCPS queue would sometimes go into a Stalled state while or just before printing the last sheet of a document, and would never resume printing. 5.2.4 DCPS Installation Repeatedly Gets %DCL-W-SYMOVF Errors When the DCPS installation procedure scanned for existing DCPS print queues, it would repeatedly generate the error message shown below if your system contained a logical name (for example, SYS$PRINT) and a queue name that were identical. The installation would never complete, and you would have to abort it by typing Ctrl/Y. %DCL-W-SYMOVF, no room for symbol definitions - delete some symbols 5.2.5 Symbiont Termination when All Message Fields Disabled If the job controller was started with all message fields disabled, the DCPS symbiont would terminate with a %STR- F-STRTOOLON message whenever it attempted to generate a -DCPS-I-JOB_ID message containing additional job identification information. A message similar to the following would be sent to OPCOM: %%%%%%%%%%% OPCOM 21-MAR-1996 20:28:01.70 %%%%%%%%%%% Message from user SYSTEM on DANTOO Process SYMBIONT_15: %F-STRTOOLON, string is too long (greater than 65535) Symbiont terminations caused by disabled message fields were erroneously believed to have been completely fixed in DCPS V1.1, as reported in Section 8.2.5. 5.2.6 Online Help Fixed and Expanded Some minor errors in the PRINT_PARAMETERS online help were fixed. In addition, online help about the LN17ps and Colorwriter LSR 2000 printers was added. 5.2.7 Gray Bars from the LIST Translator Are More Visible Gray bars generated by the LIST translator to highlight alternate groups of lines are now more visible for the DEClaser 5100 printer at resolutions above 300x300 dpi and for the Apple LaserWriter IIg printer. 5-2 DCPS Version 1.3 Information 5.2.8 Automatic Scaling When Queue Has PAGE_SIZE and SHEET_SIZE Parameters DCPS now assumes an implicit NUMBER_UP=1 when all of the following conditions exist: o The DCPS-PLUS license is installed. o Queue default parameters for both PAGE_SIZE and SHEET_ SIZE have been set to different sizes. o Your PRINT command does not specify these parameters: - PAGE_SIZE - SHEET_SIZE - INPUT_TRAY o NUMBER_UP and LAYUP_DEFINITION are not specified for the queue or in your print command. NUMBER_UP=1 scales the logical page size to fit on the physical sheet size. This fix results in the same behavior as specifying different values for PAGE_SIZE and SHEET_SIZE on the command line without specifying NUMBER_UP or LAYUP_ DEFINITION. In previous versions of DCPS, the implicit scaling was assumed for command line parameters but not for queue parameters. A workaround in those versions was to include an explicit NUMBER_UP=1 with the queue parameters. 5.2.9 Job Log and Job Trailer Pages Sent to Specified Output Tray The job log and job trailer pages, if any, are now normally directed to the output tray you specified with the OUTPUT_ TRAY parameter. However, if DCPS reports a NOOUTTRAY, OUTTRAYNOTAVL, or OUTTRAYMISMATCH error when initially attempting to select the specified output tray, the job log and trailer pages are instead directed to the printer's default output tray so that you get an indication of the problem. In previous versions of DCPS, the job log and trailer pages were always sent to the printer's default output tray for non-PrintServer printers. For example, it was previously documented that use of OUTPUT_TRAY=FACE_UP for the HP LaserJet 4SiMX printer would not direct the trailer page DCPS Version 1.3 Information 5-3 to the face-up output tray. This restriction no longer exists. 5.3 DCPS Version 1.3 Changes 5.3.1 New C6 Paper Size DCPS now supports the C6 (326mm x 460mm) paper size. You can specify C6 as the logical PAGE_SIZE value for any printer, and as the physical SHEET_SIZE value for the LN17ps printer. 5.3.2 Device Control Modules Changed for UNRECOGNIZED Printer The four device control modules for "unrecognized" printers, as well as those for other printers, were changed. If you made any changes to previous versions of these DIGITAL-supplied modules, you may need to rework your changes. See the DECprint Supervisor for OpenVMS System Manager's Guide and comments in the LPS$$UNRECOGNIZED_* modules for more information. 5-4 DCPS Version 1.3 Information 6 _________________________________________________________________ DCPS Version 1.2 Information This chapter describes the changes that are in Version 1.2 of the DECprint Supervisor. 6.1 DCPS Version 1.2 Highlights The following list provides a brief description of the significant changes included in DECprint Supervisor Version 1.2. You can find more information for several of these changes elsewhere in these release notes. o DCPS Version 1.2 requires less memory and pagefile space. This is achieved by allowing a supervisor process to control multiple print queues (run "multistreamed"). This allows a system to have far fewer DCPS supervisor processes, and thus alleviates memory and pagefile consumption. o DCPS Version 1.2 reduces idle queue processor overhead by allowing supervisor processes to control multiple print queues, thereby reducing the number of supervisor processes and the overhead imposed by each. o DCPS now supports printing to printers on an AppleTalk network from OpenVMS Alpha systems. o AppleTalk printer names may now be specified with 8-bit accented characters. o The ANSI translator has been fixed and no longer abnormally truncates lines when printing with A4 page sizes in landscape orientation. o When printing to serial- and LAT-connected printers, DCPS is less aggressive on job startup. Previously, DCPS could cause a print job from a UNIX host or LATSYM to abort if the job had completed on that host, but was still printing at the printer. DCPS now waits for the printer to stop printing before it begins the new job. DCPS Version 1.2 Information 6-1 A new DCPS logical can be defined to restore the old behavior, if needed. o Previous versions of DCPS could hang, especially on AppleTalk connected printers, if a job name contained the "]" character. This problem is corrected in this release. o Under rare circumstances, DCPS V1.1 and V1.1A could exit with the following message "%DCPS-F-INSEF, insufficient event flags". This problem is corrected in this release. o New system logicals are now recognized for changing DCPS modes and behaviors to other than the defaults. o The startup template command procedure, DCPS$STARTUP.TEMPLATE has been updated to show how to configure the print supervisor for multistreamed operation. o The kit installation procedure and IVP have been enhanced to check for and report running DCPS queues and components that might cause unpredictable behavior during an upgrade. o This release also contains several other corrections and minor enhancements to the product. 6.2 DCPS Version 1.2 Fixes This section describes problems that have been fixed in DCPS Version 1.2. 6.2.1 Truncated Lines when A4 Page is Printed Landscape Beginning with Version V1.1A the ANSI translator used a modified definition of the size of the printing area for an A4 page printed landscape. However, this new definition sometimes caused lines to be abnormally truncated. This problem has been fixed. See Section 7.1.2. 6-2 DCPS Version 1.2 Information 6.2.2 AppleTalk Printer Names with Multinational Characters If an AppleTalk printer name includes multinational characters (for example, accented characters), DCPS did not properly handle these names and could not find the printer on the AppleTalk network. The characters supplied for the /ON qualifer use the DECMCS character set. These characters had to be converted to the Macintosh character set to be used on the AppleTalk network. With Version 1.2, this conversion now occurs. When multinational characters are used, the printer name printed on the bottom of separation pages may be printed in the wrong character set. 6.2.3 DELETE/ENTRY and "(DCc) Circuit connect failure" At apparently random times, it was possible for a PrintServer printer to display the a "(DCc) Circuit connect failure" error and stop responding to print requests. This problem occured as a result of a DELETE/ENTRY command if the job number on the PrintServer printer was 100 or greater. DCPS now correctly handles DELETE/ENTRY and no longer causes this error. 6.2.4 Speed of Printing of Certain File Types Changes have be made to improve how files with variable length records are handled by the symbiont. These changes can improve the speed at which these files print. 6.2.5 Handling of Communications Problems on Serial Interconnect In previous releases, there could be a delay of up to 4 minutes to free the system resources associated with a serial device. This could occur when a STOP/QUEUE /RESET command was issued when a job was printing, but a communication problem had occurred. When such a delay occurred, the queue could not be restarted soon after it had been stopped. Now when a communication problem is detected, the system resources are freed more quickly, and a print queue can be restarted soon after it is stopped. DCPS Version 1.2 Information 6-3 6.2.6 DCPS$queuename_PID Logical and Startup Errors With V1.1A, if a queue failed to start, the logical DCPS$queuename_PID would be left in the system logical name tables. This no longer occurs. 6.2.7 Looping when Handling Messages with ']' in Job: field DCPS now properly handles PostScript printer messages with a ']' character in the job name. Parsing such a message in previous versions would result in an infinite loop. This was most likely to be noticed when printing to a printer on an AppleTalk network. 6.2.8 Handling of Long Device Names in DCPS$STARTUP.COM DCPS V1.1A did not properly account for the SCSNODE name when determining the value for the /ON qualifier from the P2 value supplied to DCPS$EXECUTION_QUEUE.COM by DCPS$STARTUP.COM. If the node's SCSNODE name was less then 6 characters, an error could occur when the queue was started. This has been fixed. 6.2.9 Form Setup Modules and Multiple File Jobs A setup module specified by the /SETUP qualifier of a form is sent to the printer just once at the beginning of a print job if the setup module is PostScript. If the job included multiple files or copies of a file, the PostScript context established by this setup module could be lost and the rest of the files would not print as expected. This happened because, when needed, DCPS sends the PostScript 'newsheet' operator between files to ensure new files start on new sheets. The PostScript context is now saved before executing 'newsheet', and restored after executing 'newsheet'. 6.2.10 Interrupting Busy Printers When a Job Starts Previous versions of DCPS, when used with serially- connected printers, used an aggressive synchronization sequence to gain control of the printer's PostScript interpreter. This is no longer the case, as it occasionally caused problems when a printer was used in a shared multi- host environment. 6-4 DCPS Version 1.2 Information However, if you rely on DCPS's previous ability to abort errant PostScript jobs on one queue by starting a job on another queue, you can define a DCPS logical to restore the previous functionality, as described in the DECprint Supervisor for OpenVMS System Manager's Guide. 6.2.11 Suppressing PostScript Synchronization when a Job Starts Defining the logical DCPS$queuename_NO_SYNC causes the DCPS symbiont to avoid using its usual synchronization sequence on serially-connected printers. This includes printers that use LAT protocol on built-in Network Interface Cards (NICs). It has no effect when using printers connected via other interconnects. This logical is supported by Versions 1.2 and later of DCPS to help avoid problems that have been reported in past versions. 6.2.12 DDIF Files with Invalid Parameter Values The DDIF translators have been modified to handle files with invalid values for some parameters. Specifically, if the value for either the "PixelPath" or "LineProgression" parameter is invalid, then the default value for that parameter is assumed. 6.2.13 Insufficient Event Flags Under some circumstances, DCPS V1.1 and V1.1A exits with the following message: %DCPS-F-INSEF, insufficient event flags This problem might occur with LAT-connected printers when more than one host attempts a connection to the printer at the same time. This problem is corrected in Version 1.2. 6.2.14 PostScript Operator findfont Has Been Modified The example file [SYSHLP.EXAMPLES.DCPS]PS_SUPPLEMENT.PS has been changed. The re-definition of the PostScript operator 'findfont' has been modified to minimize naming conflicts with other definitions of the keyword 'findfont'. Also, if PS_SUPPLEMENT.PS is loaded more than once, the 'findfont' operator is not re-defined, and previous problems due to recursion no longer occur. The redefinition of the PostScript operator 'findfont' has been modified to minimize naming conflicts with other definitions of the keyword 'findfont'. Also, if PS_SUPPLEMENT.PS is loaded DCPS Version 1.2 Information 6-5 more than once, the 'findfont' operator is not redefined, and previous problems due to recursion no longer occur. 6.2.15 OUTPUT_TRAY=LCOS Not Supported for PrintServer 17 Printers You can now use the OUTPUT_TRAY=LCOS parameter to select the large capacity output stacker on PrintServer 17 printers. 6.3 DCPS Version 1.2 Changes This section describes changes in DCPS Version 1.2. 6.3.1 Running DECprint Supervisor as a Multistreamed Process Beginning with Version 1.2, a DECprint Supervisor process is capable of running as a multistreamed symbiont process. 6.3.2 AppleTalk Interconnect Supported on OpenVMS Alpha Systems Printing to printers on an AppleTalk network from an OpenVMS Alpha system is now supported. The AppleTalk for OpenVMS network software from PATHWORKS for OpenVMS (Macintosh) V1.3 or later must be installed and running. 6.3.3 DCPS Includes Files for the DEClaser 3500 FAX Option DCPS includes example files for the the DEClaser 3500 printer's FAX features. 6.3.4 The Network Printer Setup Utility Updated The Network Printer Setup Utility has been updated. The kit can be found in SYS$COMMON:[SYSHLP.EXAMPLES.DCPS.NETPRINT] in the file NETPRX11.ZIP. The new version works with V5.0A and V5.1 of PATHWORKS for OpenVMS (LAN Manager). This version of the Network Printer Setup Utility is also supplied on the PATHWORKS Unsupported Utilities Kit. 6.3.5 Logical to Enable Device Control Library Caching The system logical DCPS$DEVCTL_CACHE (with no queue name specified) can be defined to specify that device control library caching is enabled for all DCPS print execution queues on that system. Also see Section 8.1.4. 6-6 DCPS Version 1.2 Information 6.3.6 DCPS$STARTUP.TEMPLATE Updated The file SYS$STARTUP:DCPS$STARTUP.TEMPLATE has been modified to provide example definitions for both DCPS$MAX_ STREAMS and DCPS$DEVCTL_CACHE. 6.3.7 Executable Components Check for Compatible Versions Beginning with DCPS Version 1.2, the executable components attempt to ensure they are a matched set. If a mis-match occurs, DCPS reports an error when the queue starts. 6.3.8 Reducing the Amount of Memory and Idle Time CPU DCPS V1.1 and V1.1A use considerably more memory than previous versions of DCPS. This use of memory can become a significant problem when many DCPS queues are started on a system. DCPS Version 1.2 and later address this problem by reducing the peak memory requirements of DCPS and by allowing DCPS to run multistreamed. Also, beginning with DCPS V1.1, DECthreads is used to implement the numerous functions of DCPS. All processes that use DECthreads execute periodically to determine if any threads can run. Even when no jobs are printing, DECthreads causes a DCPS process to run to determine if any threads can run. If there are many DCPS queues started on a system, the scheduling and periodic execution of all these processes can use a significant amount of CPU time. This problem is resolved by running DCPS as a multistreamed process, thereby reducing the number of symbiont processes that must execute. Also, DCPS symbiont processes never get swapped out of memory because they periodically execute. There are several factors to consider to determine an appropriate number of queues per DCPS symbiont process including: o DCPS Version 1.2 must be configured to support at least four execution queues to reduce the memory requirements to that of DCPS V1.0C. o You can reduce the number of process slots taken by DCPS by increasing the number of queues per process. This will free up process slots. By reducing the number of DCPS symbiont processes, you reduce the number of DECthread processes that must run periodically, which improves system performance. DCPS Version 1.2 Information 6-7 o With Version 1.2 and later of DCPS, even though a DECprint Supervisor process can be configured to support more than one execution queue, DCPS can translate only one file at a time. To avoid contention for translators, when a stream (queue) in a process needs a translator that is already in use, the translator for that stream is started in a separate temporary process. This can impact performance if your site primarily uses one translator, and print queues are generally busy. To reduce the likelihood of a impact on performance, choose a smaller value for DCPS$MAX_STREAMS. o The maximum number of queues per process is 32. This limit is imposed by the OpenVMS queue manager. o If DCPS is configured to support only one print queue per process (the default), DCPS Version 1.2 uses less memory than V1.1 or V1.1A, but more memory than DCPS V1.0C. o A DECprint Supervisor process running multiple print queues represents a potential single point of failure. If the supervisor process fails, or someone stops the process, then several queues are affected. 6-8 DCPS Version 1.2 Information 7 _________________________________________________________________ DCPS Version 1.1A Information This chapter describes fixes and changes that are new to DCPS V1.1A. 7.1 DCPS Version 1.1A Fixes This section describes problems that have been fixed in DCPS Version 1.1A. 7.1.1 Corrected Timeout Problem With LAT Protocol on Network Cards A problem occurred on DCPS print queues connected to printers using the LAT protocol on a network card. If the printer was turned off for a long period of time, say for the night, and a job was submitted while the printer was off, the queue would stop with a fatal timeout message. This behavior has been corrected and printing will resume when the printer is turned on. 7.1.2 ANSI Translator Printing with A4 Landscape All versions of the ANSI translator prior to DCPS V1.1A had a problem printing 66 lines of text in landscape mode on A4 paper. The translator has been fixed by altering the vertical spacing and printable area that it uses. If you use preprinted forms that depend on the translator's old behavior, you can define a DCPS logical to retain that behavior. See the DECprint Supervisor for OpenVMS System Manager's Guide for more information. 7.1.3 PCL Translator Handles Duplexing on PostScript Level 2 Printers The PCL translator now generates PostScript code that will print correctly on PostScript Level 2 printers when the file includes a duplex escape sequence. DCPS Version 1.1A Information 7-1 7.1.4 Correction for ANSI Performance Problem on PrintServer Printers There is a version skew problem in the PrinterServer ANSI prologue file in DCPS V1.1 and the version number stored in the resource file. The problem may cause the ANSI prologue to be downloaded for each ANSI print job. To correct the problem issue the following command: @SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]UPDATE-ANSI-PROLOGUE 7.1.5 Remote Console Aborted Jobs on PrintServer Printers If a print job was submitted to a PrintServer printer with DCPS V1.1, and aborted via the remote console, the job would be requeued. This problem is fixed in DCPS V1.1A so the print job is deleted from the queue. 7.1.6 New Format for the Log Files There were several problems with the log file mechanism in DCPS V1.0, V1.0B, and V1.0C. These problems were fixed in DCPS V1.1, but not communicated to you. The new log file mechanism clearly displays control characters and formats data in an easy-to-read format. However, programs that read the log file may not operate properly. 7.1.7 Device Control Module Cache Problem Corrected In DCPS V1.1, if there was more than one device control library, and DCPS$DEVCTL.TLB was not the first library in the library search list, and caching was enabled, the symbiont issued an error message stating that the required device control modules could not be found and stopped the queue. This problem is fixed in DCPS V1.1A. 7.1.8 Problem with P2 in DCPS$EXECUTION_QUEUE.COM Fixed With DCPS V1.1, device names supplied in P2 for DCPS$EXECUTION_QUEUE.COM were turned into logical names if their length exceeded 31 characters. In DCPS V1.1A, device names are not treated as logical names until 39 characters, the maximum size for the /ON qualifier. 7-2 DCPS Version 1.1A Information 7.2 DCPS Version 1.1A Changes 7.2.1 Process ID Logical Created by Symbiont The logical name, DCPS$queuename_PID, is defined by the symbiont when it starts executing. DCPS Version 1.1A Information 7-3 8 _________________________________________________________________ DCPS Version 1.1 Information This chapter describes changes to DCPS Version 1.1. 8.1 DCPS Version 1.1 New Features This section describes the new features in DCPS Version 1.1. 8.1.1 New Interconnects and New Device Specification Syntax DCPS Version 1.1 adds support for printing to desktop printers via AppleTalk, and to DIGITAL PrintServer printers using TCP/IP. Refer to the DECprint Supervisor for OpenVMS System Manager's Guide for the details. ________________________ Note ________________________ The device specification syntax allows a device name to be longer than 39 characters. Those device names that are longer than 39 characters display as "DCPS$" for the value of the /ON qualifier. The device name is stored in a logical named DCPS$queuename_DEVICE_NAME. ______________________________________________________ 8.1.2 Native PCL Accessible on Some Printers DCPS V1.1 can print PCL jobs, including those which specify PCL Level 5 commands, directly to certain printers without using PCL-to-PostScript translation. Version 1.1 uses the native PCL capability of those printers when a job requires no PostScript processing. Not all printers that provide PCL emulation are supported by DCPS in this manner. Printers that are supported for native PCL printing are listed here: o DEClaser 5100 DCPS Version 1.1 Information 8-1 o DIGITAL PrintServer 17, with PrintServer Supporting Host V5.0 software and at least 12MB memory o DIGITAL PrintServer 17/600, with PrintServer Supporting Host V5.0 software and at least 12MB memory o Hewlett-Packard LaserJet 3Si with PostScript option o Hewlett-Packard LaserJet 4M o Hewlett-Packard LaserJet 4ML o Hewlett-Packard LaserJet 4MP o Hewlett-Packard LaserJet 4SiMX 8.1.3 Suprressing the OPCOM Message "User Name Not Found" When DCPS is executing in a cluster environment where the UAF files are different between cluster members, an OPCOM message is displayed and the job prints normally: %%%%%%%%%%% OPCOM 1-JAN-1994 18:43:55.87 %%%%%%%%%%% Message from user SYSTEM on LITERA Queue SHARIE: %DCPS-W-USERNOTFOUND, user name FOO not found, no log files created -RMS-E-RNF, record not found Because the username cannot be found, the symbiont cannot perform the "MESSAGES=KEEP" or "MESSAGES=PRINT" parameter request. To keep this OPCOM message from being displayed for every job, define the logical DCPS$queuename_IGNORE_UNKNOWN_USER to be one (1). 8.1.4 Device Control Library Cache Feature DCPS V1.1 has a new device control library caching feature that optimizes the retrieval of certain commonly-used PostScript device control modules. Refer to the DECprint Supervisor for OpenVMS System Manager's Guide for the details. 8-2 DCPS Version 1.1 Information 8.1.5 ANSI Prologue File A new ANSI prologue is included as part of the new ANSI translator in DCPS V1.1 and is also available as a separate file. The file is located at SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]LPS_ANSI_PROLOGUE.PS. The prologue is incompatible with the previous ANSI translators. A PostScript printer can hold only one version of an ANSI prologue. To minimize performance problems, after installing the DCPS V1.1 software, power-cycle non- PrintServer printers to force the DECprint Supervisor software to persistently load the new prologue. To update the ANSI translator prologue on your PrintServer Supporting Host system, enter the following command: @SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]UPDATE-ANSI-PROLOGUE.COM Then reboot your PrintServer printer. This .COM file assumes that the DECprint Supervisor software is installed on your supporting host system. In addition, all PrintServer printers are updated. 8.2 DCPS Version 1.1 Fixes This section lists problems that have been corrected since DCPS V1.0 was released. 8.2.1 Separator Tray Logical Works on Generic and Execution Queues Previously, the logical DCPS$queuename_SEPARATOR_TRAY worked only on generic queues. It now works on execution queues as well. 8.2.2 Suppressed Messages NOPAGEREGIONOP and NOSETPAGEDEVICE These undocumented informational messages no longer occur. 8.2.3 Fixed Problems Printing VFC Files Printing a VFC-formatted file with a print file carriage control code of hex 8C now works correctly. DCPS does not support printing VFC-formatted and other files whose organization is RELATIVE or INDEXED. DCPS now detects this condition and returns a file error message. DCPS Version 1.1 Information 8-3 8.2.4 Increased Range of PAGE_LIMIT to 999999 The prior limit for either starting or ending page was 9999. It is now 999999. 8.2.5 Fixed Abort when All Message Fields Disabled DCPS will no longer terminate with the %STR-F-STRTOOLON message if job controller is started with all message content disabled using the following command: $ SET MESSAGE/NOTEXT/NOFACILITY/NOIDENT/NOSEVERITY 8.2.6 Fixed ANSI Jobs with "Sinking Accented Capital Letters" The error with the ANSI data type in which accented capital letters such as Á and É would print lower than surrounding characters on some types of printers has been fixed. 8.2.7 Library Search List Correctly Searched With DCPS V1.0, if you defined the SYS$LIBRARY logical to be a search list, the DECprint Supervisor software failed to find site-specific device control libraries placed in site-specific library directories. DCPS V1.1 corrects this problem. The supervisor correctly searches all directory elements of the SYS$LIBRARY logical name for specified device control libraries. 8.2.8 Empty Setup Module No Longer Hangs Supervisor DCPS V1.0 queues would stall and the supervisor would hang in an infinite compute loop if it was instructed to load a setup module with no contents. The DCPS V1.1 supervisor does not exhibit this behavior. 8.2.9 Corrected PostScript Handling in Layup DCPS now correctly handles idtransform and setpagedevice commands in the layup facility. 8.2.10 LCIT Keyword Now Recognized for PrintServer 17 You can now use the INPUT_TRAY=LCIT parameter to select the large capacity input tray on the PrintServer 17 printer. 8-4 DCPS Version 1.1 Information 8.2.11 Fixed OUTPUT_TRAY=SIDE for PrintServer 17 The parameter OUTPUT_TRAY=SIDE now selects the lower tray for all members of the PrintServer family. 8.2.12 Fixed Delay for Manual Feed with Apple and Hewlett-Packard Printers New code activates a delay for insertion of paper into manual feed slot with Hewlett-Packard LaserJet III, IIID and IIISi and supported Apple LaserWriter printers. 8.3 DCPS Version 1.1 Changes 8.3.1 Support for Non-DIGITAL Printers The DCPS Version 1.1 software adds support for additional non-DIGITAL printers if you install the DCPS-Open license. The following printers are among those supported by DCPS Version 1.1: o Hewlett-Packard printers - LaserJet 4M, 4ML, 4MP, 4SiMx Native PCL mode supported - LaserJet IIISi printer PostScript Level 2 option - PaintJet XL300 Provides color printing o Apple LaserWriter Printers - Pro 600, Pro 630 See the DECprint Supervisor SPD for a complete list of supported printers. 8.3.2 Enhancements to the PCL Translator The PCL-to-PostScript translator has been modified to include the following features. o The following escape sequence has been implemented: &l9D This escape sequence sets the line spacing to 9 lines per inch. DCPS Version 1.1 Information 8-5 o The following escape sequence has been implemented: &l5H This escape sequence selects an input tray. The command will execute the intermediate PostScript operator 'setlcittray', which by default selects the PostScript tray corresponding to the number 3. See the DECprint Supervisor for OpenVMS User's Guide for more information about redefining PCL tray selection operators. o The top and left offset commands are implemented. o Executing the command to set both the left and right margin to 0 has changed to give the behavior observed on the LaserJet IID; specifically, the margins are set to give the maximum width for the selected page size. o The LaserJet IID does not require that a raster begin with the begin raster command. The translator has been made compatible with the IID, although it is recommended that a raster begin with the begin raster command. o The PCL translator issues a PostScript save operation before executing any PostScript and a PostScript restore operation when the translated file finishes printing. All virtual memory used by the translator is recovered. 8.3.3 LN03 Image Printer The DCPS Version 1.1 software does not support the LN03 Image Printer (LN03Q). If you rely on this type of printer, it is recommended that you use the DECprint Printing Services (CPS) Version 4.1 product to drive the printers. An alternative to the LN03 Image Printer is the PrintServer image printing technology. DCPS Version 1.1, when used with PrintServer Software Version 5.0 or later, takes advantage of any image-printing enhancements in your PrintServer printer. Image printing requires the DCPS-Plus license. 8-6 DCPS Version 1.1 Information 8.3.4 The State of a Printer Is Not Known Until a Job Prints Beginning with DCPS V1.1, the functions that are performed when a queue is started have become consistent. regardless of the interconnect. Specifically, when a queue is started there is no attempt to make a connection to the printer. This is to minimize the possibility that a queue will not start. This is particularly important because there should be no errors or delays when queues are started while a system is booting. This change primarily affects printers directly connected to a system (TTAn or TXAn device). Previous versions of DCPS attempted a connection to a directly connected printer when the queue was started and could detect if the printer was powered on. Now, the state of a printer and the interconnect are not known until a job is printed. 8.3.5 New Behavior for Serial Interconnect When communications problems arise on the serial interconnect, the symbiont will keep listening for up to 4 minutes before disconnecting from the printer. Therefore, under some conditions, the serial device is not released immediately after a STOP/QUEUE/RESET command is issued. DCPS Version 1.1 Information 8-7 A _________________________________________________________________ List of Files Installed on Alpha Systems DCPS014.RELEASE_NOTES [SYSHLP] DCPS$HELP.HLP [SYSHLP] DCPS$SMBSHR.EXE [SYSLIB] DCPS$SMB.EXE [SYSEXE] DCPS$MSG.EXE [SYSMSG] DCPS$TRNPRC.EXE [SYSLIB] DCPS$BE_SERIAL.EXE [SYSLIB] DCPS$BE_CPAP.EXE [SYSLIB] DCPS$BE_APPLETALK.EXE [SYSLIB] TRN$DDIF_PS.EXE [SYSLIB] TRN$DDIF_IMAGE.EXE [SYSLIB] TRN$ANSI_PS.EXE [SYSLIB] TRN$PROPRINTER_PS.EXE [SYSLIB] TRN$PCL_PS.EXE [SYSLIB] TRN$LIST_PS.EXE [SYSLIB] TRN$REGIS_PS.EXE [SYSLIB] TRN$TEK4014_PS.EXE [SYSLIB] DCPS$DEVCTL.TLB [SYSLIB] DCPS$STARTUP.TEMPLATE [SYS$STARTUP] DCPS$REQUIRED.COM [SYS$STARTUP] DCPS$EXECUTION_QUEUE.COM [SYS$STARTUP] DCPS$GENERIC_QUEUE.COM [SYS$STARTUP] DCPS$IVP.COM [SYSTEST] DCPS$IVP_ANSI.DAT [SYSTEST.DCPS] DCPS$IVP_POST.DAT [SYSTEST.DCPS] DCPS$IVP_PCL.DAT [SYSTEST.DCPS] DCPS$IVP_PROPRINTER.DAT [SYSTEST.DCPS] DCPS$IVP_LIST.DAT [SYSTEST.DCPS] DCPS$IVP_REGIS.DAT [SYSTEST.DCPS] DCPS$IVP_TEK4014.DAT [SYSTEST.DCPS] LPS$SINGLEHOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$DOUBLEHOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$HOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$NUP.LUP [SYSHLP.EXAMPLES.DCPS] List of Files Installed on Alpha Systems A-1 COLOR-PRINTER-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] COLORWRITER-2000-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] PROPRINTER-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] FULL-A4-LANDSCAPE.LUP [SYSHLP.EXAMPLES.DCPS] CPS_TO_DCPS_STARTUP.COM [SYS$STARTUP] LPS_ANSI_PROLOGUE.PS [SYSHLP.EXAMPLES.DCPS] UPDATE-ANSI-PROLOGUE.COM [SYSHLP.EXAMPLES.DCPS] FONT_DOWNLOADER.COM [SYSHLP.EXAMPLES.DCPS] LPS$SET_PRINTER_NAME.PS [SYSHLP.EXAMPLES.DCPS] LPS$SET_TIMEOUT.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_CONFIG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_DEVPARAM.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_STARTPG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_NOSTRTPG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_PRNTCNFG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_PSCRIPT.PS [SYSHLP.EXAMPLES.DCPS] FAX_3500_PRINTME.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_PS.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_PS_SENDPS.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_TEXT.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_TEXT_SENDPS.PS [SYSHLP.EXAMPLES.DCPS] DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT [SYSLIB] LPS$STATUSDICT.PS [SYSHLP.EXAMPLES.DCPS] CONFIDENTIAL.PS [SYSHLP.EXAMPLES.DCPS] INSTALL-PS-SUPPLEMENT.COM [SYSHLP.EXAMPLES.DCPS] PS_SUPPLEMENT.PS [SYSHLP.EXAMPLES.DCPS] NETPRX11.ZIP [SYSHLP.EXAMPLES.DCPS.NETPRINT] README.TXT [SYSHLP.EXAMPLES.DCPS.NETPRINT] UNZIP50.EXE [SYSHLP.EXAMPLES.DCPS.NETPRINT] A-2 List of Files Installed on Alpha Systems B _________________________________________________________________ List of Files Installed on VAX Systems DCPS014.RELEASE_NOTES [SYSHLP] DCPS$HELP.HLP [SYSHLP] DCPS$SMBSHR.EXE [SYSLIB] DCPS$SMB.EXE [SYSEXE] DCPS$MSG.EXE [SYSMSG] DCPS$TRNPRC.EXE [SYSLIB] DCPS$BE_SERIAL.EXE [SYSLIB] DCPS$BE_CPAP.EXE [SYSLIB] DCPS$BE_APPLETALK.EXE [SYSLIB] TRN$DDIF_PS.EXE [SYSLIB] TRN$DDIF_IMAGE.EXE [SYSLIB] TRN$ANSI_PS.EXE [SYSLIB] TRN$PROPRINTER_PS.EXE [SYSLIB] TRN$PCL_PS.EXE [SYSLIB] TRN$LIST_PS.EXE [SYSLIB] TRN$REGIS_PS.EXE [SYSLIB] TRN$TEK4014_PS.EXE [SYSLIB] DCPS$DEVCTL.TLB [SYSLIB] DCPS$STARTUP.TEMPLATE [SYS$STARTUP] DCPS$REQUIRED.COM [SYS$STARTUP] DCPS$EXECUTION_QUEUE.COM [SYS$STARTUP] DCPS$GENERIC_QUEUE.COM [SYS$STARTUP] DCPS$IVP.COM [SYSTEST] DCPS$IVP_ANSI.DAT [SYSTEST.DCPS] DCPS$IVP_POST.DAT [SYSTEST.DCPS] DCPS$IVP_PCL.DAT [SYSTEST.DCPS] DCPS$IVP_PROPRINTER.DAT [SYSTEST.DCPS] DCPS$IVP_LIST.DAT [SYSTEST.DCPS] DCPS$IVP_REGIS.DAT [SYSTEST.DCPS] DCPS$IVP_TEK4014.DAT [SYSTEST.DCPS] LPS$SINGLEHOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$DOUBLEHOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$HOLES.LUP [SYSHLP.EXAMPLES.DCPS] LPS$NUP.LUP [SYSHLP.EXAMPLES.DCPS] List of Files Installed on VAX Systems B-1 COLOR-PRINTER-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] COLORWRITER-2000-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] PROPRINTER-FULL-PAGE.LUP [SYSHLP.EXAMPLES.DCPS] FULL-A4-LANDSCAPE.LUP [SYSHLP.EXAMPLES.DCPS] CPS_TO_DCPS_STARTUP.COM [SYS$STARTUP] LPS_ANSI_PROLOGUE.PS [SYSHLP.EXAMPLES.DCPS] UPDATE-ANSI-PROLOGUE.COM [SYSHLP.EXAMPLES.DCPS] FONT_DOWNLOADER.COM [SYSHLP.EXAMPLES.DCPS] LPS$SET_PRINTER_NAME.PS [SYSHLP.EXAMPLES.DCPS] LPS$SET_TIMEOUT.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_CONFIG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_DEVPARAM.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_STARTPG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_NOSTRTPG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_PRNTCNFG.PS [SYSHLP.EXAMPLES.DCPS] DCW1000_PSCRIPT.PS [SYSHLP.EXAMPLES.DCPS] FAX_3500_PRINTME.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_PS.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_PS_SENDPS.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_TEXT.PS [SYSHLP.EXAMPLES.DCPS] DL3500_SEND_FAX_TEXT_SENDPS.PS [SYSHLP.EXAMPLES.DCPS] DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT [SYSLIB] DCPS$COMMON-PORT-SETTINGS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$CONFIG-PRINTER-PORT.COM [SYSHLP.EXAMPLES.DCPS] DCPS$DS100-PORT-SETTINGS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$DS200-PORT-SETTINGS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$DS500-PORT-SETTINGS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$GET-DS100-PORT-GROUPS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$SET-DS-GROUPS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$SET-DS100-GROUPS.COM [SYSHLP.EXAMPLES.DCPS] DCPS$SAVE-DS500-PORT.COM [SYSHLP.EXAMPLES.DCPS] DCPS$DELETE-LPS-CLIENT.COM [SYSHLP.EXAMPLES.DCPS] LPS$STATUSDICT.PS [SYSHLP.EXAMPLES.DCPS] CONFIDENTIAL.PS [SYSHLP.EXAMPLES.DCPS] INSTALL-PS-SUPPLEMENT.COM [SYSHLP.EXAMPLES.DCPS] PS_SUPPLEMENT.PS [SYSHLP.EXAMPLES.DCPS] NETPRX11.ZIP [SYSHLP.EXAMPLES.DCPS.NETPRINT] README.TXT [SYSHLP.EXAMPLES.DCPS.NETPRINT] UNZIP50.EXE [SYSHLP.EXAMPLES.DCPS.NETPRINT] B-2 List of Files Installed on VAX Systems