____________________________________________________ DECprint Supervisor for OpenVMS (VAX and AXP) Release Notes April 1995 These release notes describe restrictions, usage hints, and other useful information about DECprint Supervisor (DCPS) for OpenVMS, Version 1.2. These release notes supersede all other documentation. Operating System and Version: OpenVMS AXP, Version 1.5 or higher, or OpenVMS VAX, Version 5.5-2 or higher Software Version: DECprint Supervisor for OpenVMS, Version 1.2 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ April 1995 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 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DEC, DEClaser, DECnet, DECprint, LN03Q, PATHWORKS, PrintServer, ReGIS, VAX, VAX DOCUMENT, VMS, OpenVMS, Alpha AXP, AXP, and the DIGITAL logo. PostScript is a trademark of Adobe Systems Incorporated, which may be registered in certain jurisdictions. TEKTRONIX is a trademark of Tektronix, Inc. Hewlett-Packard, PCL and LaserJet are trademarks of Hewlett-Packard Company. Colormate is a trademark of NEC. Proprinter is a registered trademark of International Business Machines Corp. AppleTalk, EtherTalk, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, 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................................................... vii 1 DCPS Version 1.2 Information.................. 1 1.1 Highlights of this Release................ 1 1.2 Installation Guidelines................... 2 1.3 Installation Procedure and IVP Changes.... 3 1.4 DECprint Supervisor as a Multistreamed Process................................... 4 1.4.1 Improved (Reduced) Memory Requirements and Idle Time CPU Use................... 5 1.4.2 Managing Print Queues when Running Multistreamed........................... 6 1.4.3 Queue Manager Remedial Update........... 7 1.5 Other Problems that have been Addressed... 8 1.5.1 Truncated Lines when A4 Page is Printed Landscape............................... 8 1.5.2 AppleTalk Printer Names with Multinational Characters................ 8 1.5.3 DELETE/ENTRY and "(DCc) Circuit connect failure"................................ 9 1.5.4 Speed of Printing of Certain File Types................................... 9 1.5.5 Printing to PrintServer Printers when Many Resources are Loaded............... 9 1.5.6 Handling of Communications Problems on Serial Interconnect..................... 9 1.5.7 DCPS$_PID Logical and Startup Errors.......................... 9 1.5.8 Looping when Handling Messages with ']' in Job: field........................... 10 1.5.9 Handling of Long Device Names in DCPS$STARTUP.COM........................ 10 1.5.10 Form Setup Modules and Multiple File Jobs.................................... 10 iii 1.5.11 Interrupting Busy Printers.............. 10 1.5.12 Starting Synchronization when Printing to the DEClaser 3500 (and other) Serial Port.................................... 11 1.5.13 Clarification of Configurations when using DEClaser 3500 Serial Port......... 12 1.5.14 DDIF Files with Invalid Parameter Values.................................. 13 1.5.15 Insufficient Event Flags................ 13 1.5.16 Hang when Network Connection is Lost and Jobs are Pending on PrintServer Printer................................. 13 1.6 Additional Changes........................ 14 1.7 Restrictions.............................. 17 1.8 Error Recovery when AppleTalk Network Software is not Running................... 17 1.8.1 Directly Connected Printers............. 18 1.8.2 No Unsolicited Status Messages.......... 18 1.8.3 'printername' is Not Always Printed Correctly............................... 18 1.8.4 Paper Size Names and DCPS Aliases....... 18 2 DCPS V1.1A Information........................ 19 2.1 Support for the DEClaser 3500............. 19 2.1.1 Interaction Between Communication Protocol and Native PCL Support......... 19 2.1.2 DEClaser 3500 Setup Modules............. 19 2.1.2.1 Resolution Enhancement................. 20 2.1.2.2 Toner Saver Mode....................... 20 2.1.2.3 DECimage-Lite.......................... 20 2.1.2.4 Usage Example.......................... 21 2.1.2.5 Other Useful Setup Modules............. 21 2.1.3 Selecting Statement Size Paper.......... 21 2.2 Corrected Timeout Problem With LAT Protocol on Network Cards................. 21 2.3 ANSI Translator Printing with A4 Landscape................................. 22 2.4 New logical Created by Symbiont: DCPS$_PID..................... 22 2.5 PCL Translator Handles Duplexing on PostScript Level 2 Printers............... 22 iv 2.6 DEClaser 5100 Printer Specific Information............................... 22 2.6.1 Uploading and Deleting Fonts............ 22 2.6.2 Native PCL Unavailable with EtherTalk Protocol on NIC......................... 23 2.6.3 Occasional PostScript Error with PCL Jobs on LocalTalk Port.................. 23 2.7 PrintServer Printer Specific Information............................... 23 2.7.1 Correction for Printserver ANSI Performance Problem..................... 23 2.7.2 Remote Console Aborted Jobs on PrintServer Printers.................... 24 2.7.3 Too Many Resources Loaded Prevent DCPS Symbionts from Starting ................ 24 2.8 New Format for the Log Files.............. 24 2.9 Device Control Module Cache Problem Corrected................................. 24 2.10 Problem with P2 in DCPS$EXECUTION_QUEUE.COM Fixed............ 24 3 New Features in DCPS V1.1..................... 25 3.1 New Interconnects and New Device Specification Syntax...................... 25 3.2 New Behavior for Serial Interconnect...... 25 3.3 New Logical Name, DCPS$_IGNORE_UNKNOWN_USER................. 25 3.4 ANSI Prologue File........................ 26 4 Fixes Related to DCPS Software in General..... 26 4.1 Separator Tray Logical Works on Generic and Execution Queues...................... 26 4.2 Suppressed Messages NOPAGEREGIONOP and NOSETPAGEDEVICE........................... 26 4.3 Fixed Problems Printing VFC-Format Files..................................... 27 4.4 Increased Range of PAGE_LIMIT to 999999... 27 4.5 Fixed Abort when All Message Fields Disabled.................................. 27 4.6 Fixed ANSI Jobs with "Sinking Accented Capital Letters".......................... 27 4.7 Library Search List Correctly Searched.... 27 4.8 Empty Setup Module No Longer Hangs Supervisor................................ 27 4.9 Corrected PostScript Handling in Layup.... 28 v 5 Fixes Related to Supporting Printers.......... 28 5.1 LCIT Keyword Now Recognized for PrintServer 17............................ 28 5.2 Fixed OUTPUT_TRAY=SIDE for PrintServer 17........................................ 28 5.3 Fixed Delay for Manual Feed with Apple and HP Printers............................... 28 6 Restrictions.................................. 28 6.1 Device Control Libraries Must Exist for Queue to Start............................ 28 6.2 Compatibility with DCPS V1.0 software..... 29 6.3 Compatibility with DEC Image Print-PLUS (ICPS).................................... 29 6.4 DDIF Printing Requires DECimage Application Services for VMS V3.1......... 29 6.5 Compatibility of NUMBER_UP and PostScript Drivers................................... 29 6.6 The New LIST Data Type.................... 29 6.7 PC Driver Settings to Avoid Problems with PJL and TBCP.............................. 30 6.7.1 Description of PJL and TBCP............. 30 6.7.2 Steps to Prevent Problems with DCPS V1.1.................................... 31 6.7.2.1 Preventing problems with PostScript.... 31 6.7.2.2 Preventing problems with PCL........... 32 6.8 Interaction Between Native PCL Printing and Automatic DATA_TYPE Detection......... 32 6.9 Native PCL Mode Concatenates Files........ 33 6.10 Embedded PJL Commands Discarded; Avoid Binary Mode............................... 34 6.11 Job Trailer Page Jogs with Certain Printers.................................. 34 6.12 OUTPUT=FACE_UP Goes to Wrong Tray on HP LaserJet 4SiMX............................ 34 6.13 Unreliable Communication after Errors on Some Printers............................. 35 6.14 Deleting Job when Using AppleTalk......... 35 6.15 Deleting Jobs on an AppleTalk Connected DEClaser 1152 Printer..................... 36 6.16 Apple LaserWriter Plus does not Support LPS$PERSISTENT_RESOURCES.................. 36 6.17 Native PCL Restrictions to Print Parameters................................ 36 vi 6.18 Incorrect Page Count on Native PCL Jobs on HP IIISi.................................. 37 6.19 Incorrect Sheet Count on Duplex Jobs with HP LaserJet Printers...................... 37 6.20 Communication Problem with the HP XL300 Printer................................... 37 6.21 Do Not Issue STOP/QUEUE/RESET when a PrintServer Printer is Rejecting Connections............................... 37 6.22 No Job Trailer Page on DELETE/ENTRY....... 38 6.23 Problems with PostScript Files when Printing with /COPIES..................... 38 7 Additional Information About DCPS............. 38 7.1 Interaction between Colored Separator Pages and the PrintServer 17 Input Tray Failover.................................. 38 7.2 Error Page Feature of DEClaser 5100....... 39 7.3 Printers with Auto-Sensing Features....... 40 7.4 Unique AppleTalk Node Addresses for Reliable Printing......................... 40 7.5 Printing on Unrecognized Printers......... 40 A List of Files Installed on AXP B List of Files Installed on VAX vii _________________________________________________________________ Preface The primary source of information about DECprint Supervisor (DCPS) for OpenVMS, Version 1.2 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 o DECprint Supervisor Version 1.1 New Features The New Features manual describes the enhancements and improvements that appeared in Version 1.1. These release notes provide additional detail on the following: o Product changes since Version 1.1. Some changes provide new features or new printer support. Other changes have been made to correct problems with V1.1 and V1.1A. o Restrictions in DECprint Supervisor Version 1.2. o Additional information about DECprint Supervisor ________________________ Note ________________________ The on-line New Features manual is a later version than the printed manual provided in the documentation set. The on-line manual contains more accurate information. You can find the on-line version of the manual in the following areas: - DCPS V1.2 CD-Rom - OpenVMS VAX Software Product Library - OpenVMS Alpha Software Library Package ______________________________________________________ vii For information on licensing requirements and the features available with each license, see the DECprint Supervisor Software Product Description (SPD 44.15.xx). viii 1 DCPS Version 1.2 Information This section describes the changes that are in Version 1.2 of the DECprint Supervisor. These changes address several problems with DCPS V1.1 and V1.1A. Section 2, DCPS V1.1A Information, describes the changes DCPS V1.1 to V1.1A. Some release notes in Section 2 are superseded or modified by the product changes included in Version 1.2. 1.1 Highlights of this Release The following list provides a brief description of the significant changes included in DECprint Supervisor Version 1.2. Each of these changes are described in detail 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 (runs "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 AXP 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/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. The serial/LAT back-end now waits for the printer to stop printing before it begins the new job. A new DCPS logical name can be defined to restore the old behavior, if needed. 1 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. 1.2 Installation Guidelines Follow these steps to install Version 1.2 of DECprint Supervisor: 1. Review all release notes for Version 1.2 (this entire section). 2. Stop DCPS print queues using STOP/QUEUE/NEXT or STOP /QUEUE/RESET. 3. Remove any DCPS executables from the SYS$SPECIFIC areas of the system disk. 4. Install Version 1.2 of DCPS. 5. Set the value of the logical DCPS$MAX_STREAMS in DCPS$STARTUP.COM (see Section 1.4). An example is provided in these release notes and in DCPS$STARTUP.TEMPLATE. 6. If possible, install the Queue Manager Remedial Update. If it cannot be installed at this time, make plans to install it in the near future. 2 7. Reboot your system if the Queue Manager Remedial Update is installed; otherwise, define the logical DCPS$MAX_ STREAMS on all nodes that run DCPS print queues. 8. Start all DCPS print queues. 1.3 Installation Procedure and IVP Changes The installation procedure has been improved to check for the following: 1. DCPS print queues that are not stopped. If any are found, including any DCPS print queues on any node in a cluster, the installer can terminate the installation. The number of DCPS print queues is provided, as well as a list of queues that are not stopped, if any. It is recommended that all DCPS print queues be stopped before installing a new version of the software. One or more of the following problems can occur if the queues are not stopped: o Any print queues started after the installation, including the print queue created for the IVP, may not use the new software. This is particularly true if DCPS is running as a multistreamed symbiont (see Section 1.4). o The currently running queues may use some components from the new software. These components may not be compatible, and could cause unexpected behavior. o Once print queues are started after the installation, there will be two different versions of DECprint Supervisor executing. This could cause subtle differences when printing to different print queues. 2. DCPS executable files in SYS$SPECIFIC areas of the system disk. The installation procedure installs all new files in the SYS$COMMON areas of the system disk. When a new DCPS symbiont process is started, the executable files will come from the SYS$SPECIFIC area, if found, and otherwise, the SYS$COMMON area. An incompatible set of executables could be used, resulting in unexpected behavior, including errors that keep a print queue from starting. 3 The Installation Verfication Procedure (IVP) has also been improved to correctly report the version of DCPS that is being tested. This version might be different than the version of the new software, if; o A version of the file DCPS$SMB.EXE is in SYS$SPECIFIC:[SYSEXE]. Note that if other components are in the SYS$SPECIFIC areas, those will be used. The IVP reports only the version of DCPS$SMB.EXE that is used. o There are DCPS print queues running on the same node as the IVP. If these print queues are running in a multistreamed symbiont process (see Section 1.4), then the IVP test queue might be started on a stream in a currently running process. Further, if this happens, and the disk copy of the image that is executing was purged during the installation, then the IVP will fail with the following error: %DCPS-F-FILERR, Error opening processor file for IVP queue: -DCPS-F-FILERR, DKA300$:[SYS0.][SYSEXE]DCPS$SMB.EXE;15 -DPCS-F-FILERR, IVP has failed. See Release Notes for details. Except for the case just specified, the IVP will report success even if the version of DCPS that is tested is not the version that was just installed. Installation and IVP problems can be avoided if: o You stop all DCPS print queues before the installation. o You delete DCPS files in the SYS$SPECIFIC areas of the system disk. 1.4 DECprint Supervisor as a Multistreamed Process Beginning with Version 1.2, a DECprint Supervisor process is capable of running as a multistreamed symbiont process. As a multistreamed symbiont process, one DCPS process can run more than one DCPS execution queue. A new DCPS process is not started every time a DCPS print queue is started, but only when all current processes are supporting a specified number of queues (streams). The number of queues that a DCPS process will support is determined by the value of the logical DCPS$MAX_STREAMS when the process is started. 4 DCPS Version 1.2 can be configured to support up to 32 execution queues per DCPS symbiont process. If this logical is not defined, a DCPS process will support only one (1) execution queue. The logical DCPS$MAX_STREAMS is used to specify the number of queues per DCPS symbiont process. To define this logical, specify the following command in your DCPS$STARTUP.COM file (a template is provided in DCPS$STARTUP.TEMPLATE) and substitute the number of queues per process to use. $ DEFINE/SYSTEM/EXECUTIVE DCPS$MAX_STREAMS x Execute your DCPS$STARTUP.COM file to enable this logical and start your queues with DCPS as a multistreamed process. A DCPS process terminates only when all queues associated with the process are stopped. 1.4.1 Improved (Reduced) Memory Requirements and Idle Time CPU Use 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 addresses 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: 5 1. 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. 2. 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. 3. With this release 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. 4. The maximum number of queues per process is 32. This is the limit imposed by OpenVMS. 5. 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. 6. 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. 1.4.2 Managing Print Queues when Running Multistreamed The OpenVMS Queue Manager controls when a symbiont process is created and terminated. Generally a new DCPS symbiont process is created when there are no free streams in all existing DCPS symbiont processes. As previously stated, the number of streams (queues) that a DCPS process supports is determined by the value of the logical DCPS$MAX_ STREAMS when a new process is started. A symbiont process terminates when all the queues supported by that process are stopped. 6 The set of print queues that a DCPS symbiont process supports is determined by the order in which queues are started, and by any subsequent stopping (STOP/QUEUE/RESET queuename or STOP/QUEUE/NEXT queuename) and starting (START /QUEUE queuename) of queues. Beginning with DCPS V1.1A, a logical name is defined which identifies the process ID for a queue (Section 2.4). These logicals can be used to determine the process that supports a queue and the set of queues that are supported by the same process. Although not likely, a problem observed with one queue could be the result of a problem that exists with another queue, because both queues are supported by the same process. It may not be sufficient to examine the state of one job on one queue to identify a problem. You may need to look at the state of the first job on all the queues supported by that DCPS process. A DCPS queue should not be stopped by stopping the DCPS process that supports that queue. Stopping a DCPS symbiont process with STOP/ID will stop all of the queues supported by that process. 1.4.3 Queue Manager Remedial Update All sites running the DECprint Supervisor as a multistreamed process should install the Queue Manager Remedial Update. This update applies to: - OpenVMS VAX V5.5-2 - OpenVMS VAX V6.1 - OpenVMS Alpha AXP V6.1 Contact a Digital Customer Support Center to get the update. The Queue Manager remedial update kits are: o VAXQMAN8_U2055 for OpenVMS V5.5-2 (VAX). o VAXQMAN02_061 for OpenVMS V6.1 (VAX). o AXPQMAN01_061 for OpenVMS V6.1 (Alpha AXP). This kit replaces the following images: o [SYSEXE]JBC$JOB_CONTROL.EXE o [SYS$LDR]MESSAGE_ROUTINES.EXE o [SYSEXE]PRTSMB.EXE 7 o [SYSEXE]QMAN$QUEUE_MANAGER.EXE o [SYSLIB]SMBSRVSHR.EXE 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, reboot your system needs to enable these changes. 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 queuename, then quickly started with START/QUEUE queuename, it is possible that the start request will hang. In addition, sometimes the following message will appear on 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 queuename again, wait a few seconds, and try to start the queue again. To avoid this problem, install the queue manager update. 1.5 Other Problems that have been Addressed 1.5.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 2.3. 1.5.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. 8 When multinational characters are used, the printer name printed on the bottom of separation pages may be printed in the wrong character set. 1.5.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. 1.5.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. 1.5.5 Printing to PrintServer Printers when Many Resources are Loaded In previous releases, jobs did not print to a PrintServer printer when many resources (for example, fonts and prologues) were downloaded. This problem is corrected with DCPS Version 1.2, if the PrintServer printer is also updated to PrinterServer Software S5.0-29 or later. 1.5.6 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. 1.5.7 DCPS$_PID Logical and Startup Errors With V1.1A, if a queue failed to start, the logical DCPS$_PID would be left in the system logical name tables. This no longer occurs. 9 1.5.8 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. 1.5.9 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 value supplied for P2 in 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. 1.5.10 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 includes multiple files or multiple copies of a file, the PostScript context established by this setup module could be lost and files after the first would not print as expected. This happened because, when needed, the PostScript operator 'newsheet' will be sent between files to ensure new files start on new sheets. Now, the PostScript context is saved before executing 'newsheet', and restored after executing 'newsheet'. 1.5.11 Interrupting Busy Printers 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 scheme worked well in an all-DCPS environment, but occasionally caused problems when a printer was used in a shared multi-host environment. If a printer connected through a DECserver or other network terminal server was shared among DCPS queues, LATSYM queues and/or UNIX hosts, jobs printing from the latter environments could inadvertently be canceled by the DCPS job synchronization sequence. This occurred when the LATSYM symbiont or UNIX print daemon disconnected from the printer before all pages were printed. 10 The default synchronization sequence has been changed to avoid this aggressive behavior when a PostScript printer reports that it is printing or busy. This should cause no observable change under normal circumstances when printing well-behaved PostScript documents. 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 the following system-wide logical to restore the previous functionality: $ DEFINE/SYSTEM/EXECUTIVE - _$ DCPS$_INTERRUPT_WHEN_BUSY "1" 1.5.12 Starting Synchronization when Printing to the DEClaser 3500 (and other) Serial Port Defining the logical DCPS$_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 provided in this version of DCPS to help avoid problems that have been reported in past versions. Digital recommends defining this queue logical on the host running the DCPS process when using printers of the following types and configurations: - DEClaser 3500 with the serial port (not NIC) in PS/PCL Sensing mode - Hewlett-Packard IIID with an HP PostScript Level 2 Cartridge DCPS begins a job on a serially-connected printer by synchronizing with its PostScript interpreter to ensure that the interpreter is ready to accept commands. However, some PostScript printers are not always in a state where they can recognize the synchronization control characters. In particular, some printers that support additional printer languages like HP PCL do not correctly respond to this sequence under certain circumstances. For example, the DEClaser 3500, when in PS/PCL sensing mode, inadvertently switches to PCL mode when DCPS sends a CTRL/T character to its serial port. The printer, then out of the PostScript 11 mode, does not respond, and a print job never starts (the job is stuck in the 'starting' state). The DCPS$_NO_SYNC logical tells DCPS to skip job synchronization sequences for the printer associated with the named queue. This feature is useful when using DCPS to control a printer such as the DEClaser 3500 in PS /PCL sensing mode. To disable the synchronization sequence for a print queue, use the following command: $ DEFINE/SYSTEM/EXECUTIVE DCPS$_NO_SYNC "1" The absence of the synchronization step is not generally a problem for most modern serially-connected printers because such printers use flow-control to hold-off data when the interpreter is not ready to accept data. However, the printer is more vulnerable to printing "garbage" or losing jobs if communication parameters, such as baud rate and stop bits, are not set correctly. Depending on the configuration, it's also possible to loose print jobs if the printer data cable is disconnected or the printer is powered off. The NO_SYNC logical can be used to solve reported problems printing to Hewlett-Packard Model IIID printers with HP- supplied PostScript Level 2 cartridges. Those cartridges have a known problem where they corrupt status messages they send to a host. This can cause jobs to get stuck in the "starting" state when DCPS tries to use its synchronization sequence. Digital does not recommend using this logical unless you are using one of the printers listed above or other analysis shows that the synchronization step is causing problems. 1.5.13 Clarification of Configurations when using DEClaser 3500 Serial Port When using DCPS with the DEClaser 3500 printer with the optional serial port, you must choose one of the following options: 1. Do not use the DCPS$_NO_SYNC logical. Lock the printer to PostScript mode. (On the front panel: Serial, Printer Type = STD PostScript). In this mode, 12 native PCL is not available because the printer does not respond to PJL sequences. You should use the workaround described in Section 2.6.2 to force use of the PCL 4 translator. 2. Set the serial port language sensing mode to Automatic. (On the front panel: Serial, Printer Type = PS/PCL Sensing), and define the DCPS$NO_SYNC logical. In this mode, the printer responds to PJL sequences and switches to native PCL 5 or PostScript as indicated by the datastream. 1.5.14 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. 1.5.15 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 this release. 1.5.16 Hang when Network Connection is Lost and Jobs are Pending on PrintServer Printer A DCPS print queue could hang (symbiont process would not terminate) when all the following conditions are true: - A DCPS print job is pending on the PrintServer printer; that is, the job is not the current job - The DCPS to PrintServer printer interconnect is TCP/IP - The network connection to the PrintServer printer is lost. To recover, delete the job (DELETE/ENTRY) or stop the queue (STOP/QUEUE/RESET). 13 1.6 Additional Changes DECprint Supervisor Version 1.2 also includes the following set of changes. - Printing to printers on an AppleTalk network from an OpenVMS Alpha AXP system is now supported. The AppleTalk for OpenVMS network software from PATHWORKS for OpenVMS (Macintosh) V1.3 or later must be installed and running. - 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. - Four example files in [SYSHLP.EXAMPLES.DCPS] help you send FAX messages with the DEClaser 3500 printer. These files may be used on VMS, UNIX, or DOS operating systems that do not have an application for using the DEClaser 3500 as a FAX sender. Drivers are available for Microsoft Windows 3.1 and Macintosh systems. Use these drivers send a FAX. These files may be distributed freely to driver developers and end users. These header files are sent ahead of the actual PostScript or text file that is to be faxed from the DEClaser 3500 printer. The example files will need to be modified for each application. Each of the files is heavily commented and contains additional information for how to make edits and how to use them. Also the file [SYSHLP.EXAMPLES.DCPS]FAX_3500_PRINTME.PS provides a description of how to use these files. o DL3500_SEND_FAX_PS.PS - Used for sending a PostScript file as a standard CCITT FAX transmission. This means it can send to any FAX receiver. o DL3500_SEND_FAX_PS_SENDPS.PS - Used to send a PostScript file as PostScript data suitable for other DEClaser 3500 printers or some other PostScript FAX receiver. If the receiver cannot accept the PostScript data, the call is terminated, the printer 14 re-computes the data into CCITT data format and re- dials. o DL3500_SEND_FAX_TEXT.PS - Used for sending a text file as a standard CCITT FAX transmission. This means it can send to any FAX receiver. o DL3500_SEND_FAX_TEXT_SENDPS.PS - Used to send a text file as PostScript data suitable for a DEClaser 3500 printer or other PostScript FAX receiver. If the receiver cannot accept the PostScript data, the call is terminated, the printer re-computes the data into CCITT data format, and re-dials. - 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. - 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. You can continue to use your current DCPS$STARTUP.COM configured for V1.1 or V1.1A; the examples are for convenience only. - The file SYS$STARTUP:DCPS$STARTUP.TEMPLATE has been modified to provide example definitions for both DCPS$MAX_STREAMS and DCPS$DEVCTL_CACHE. - The value LCOS is supported for the /PARAMETER keyword OUTPUT_TRAY for PrintServer 17 printers. - Beginning with DCPS Version 1.2, the executable components will attempt to ensure they are a matched set. If a mis-match occurs, an error will be reported when a queue is started. A common cause of this error is that a component of a prior (incompatible) release is in the SYS$SPECIFIC area of the system file structure, while other and newer components are installed in the SYS$COMMON area of the system file structure. The 15 error that occurs depends on which versions of which components are executing. For example: o If the executing version of DCPS$SMB.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on a OpenVMS VAX V5.5-2 system: $ start/que atk_1152 %%%%%%%%%%% OPCOM 13-FEB-1995 21:38:08.66 %%%%%%%%%%% Message from user QUEUE_MANAGE on DAHLIA %QMAN-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 13-FEB-1995 21:38:08.67 %%%%%%%%%%% Message from user QUEUE_MANAGE on DAHLIA -SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=0001A9B8, PSL=03C00000 o If the executing version of DCPS$SMBSHR.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on an OpenVMS VAX system: %%%%%%%%%%% OPCOM 13-FEB-1995 21:44:42.40 %%%%%%%%%%% Message from user SYSTEM on DAHLIA Process SYMBIONT_98: %SMBSHRMISMTCH2, Wrong version of DCPS$SMBSHR.EXE %%%%%%%%%%% OPCOM 13-FEB-1995 21:44:42.51 %%%%%%%%%%% Message from user QUEUE_MANAGE on DAHLIA %QMAN-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 13-FEB-1995 21:44:42.52 %%%%%%%%%%% Message from user QUEUE_MANAGE on DAHLIA -NONAME-F-NOMSG, Message number 064BE124 o If the executing version of DCPS$SMBSHR.EXE is V1.1A, and all other components are from Version 1.2, then the following error occurs on an OpenVMS Alpha AXP system: %%%%%%%%%%% OPCOM 1-FEB-1995 12:20:35.02 %%%%%%%%%%% Message from user QUEUE_MANAGE on DNGBAT %QMAN-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 1-FEB-1995 12:20:35.03 %%%%%%%%%%% Message from user QUEUE_MANAGE on DNGBAT -IMGACT-F-SYMVECMIS, shareable image's symbol vector table mismatch 16 - 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. - When processing a STOP/QUEUE/RESET or DELETE/ENTRY request, DCPS will wait for a given period of time for the printer to respond that a printing job is canceled before continuing with the request. This period can be between 2 and 4 minutes. 1.7 Restrictions The following section identifies some restrictions with DECprint Supervisor Version 1.2. 1.8 Error Recovery when AppleTalk Network Software is not Running 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. 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 But, if any more 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. In order to completely recover from such an error, any currently running symbiont processes that have detected that the AppleTalk network software is not running (one error message is generated per symbiont process) will have to be stopped by stopping all queues supported by that process. The AppleTalk software should then be started, and the queues restarted. To avoid this problem, the AppleTalk network software must be running before starting any DCPS print queues. 17 1.8.1 Directly Connected Printers 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, and could detect if the printer is powered on. Now, the state of a printer and the interconnect are not known until a job is printed. 1.8.2 No Unsolicited Status Messages Unsolicited status messages, for example, paper out, tray out, and cover open are not reported for the DEClaser 5100 printer and certain HP LaserJet III and IV printers. Exceptions to this include: - HP LaserJet III with the HP PostScript-Plus (Level 2) cartridge - HP LaserJet IIISi if jam recovery is disabled The DCPS queue stalls until the problem is fixed. 1.8.3 'printername' 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. 1.8.4 Paper Size Names and DCPS Aliases The following sheet sizes are industry standard aliases for the page/sheet sizes used by DCPS. The 'Alias' value may be used on the command line. The DCPS term is what is printed on the trailer page. Alias DCPS Term Com10 Business_envelope Monarch 7_envelope Statement Halfletter 18 2 DCPS V1.1A Information This section describes features and fixes that are new to DCPS V1.1A. A few of the release notes in this section are superseded or modified by the product changes included in DECprint Supervisor Version 1.2. See Section 1, DCPS Version 1.2 Information. 2.1 Support for the DEClaser 3500 DECprint Supervisor V1.1A adds support for Digital's newest desktop PostScript laser printer the DEClaser 3500. The supported interconnects include: Serial port LocalTalk port Network interface card using the LAT protocol Network interface card using the AppleTalk protocol The DEClaser 3500 printer includes a native PCL interpreter, and DCPS will send files identified as PCL directly to the printer. 2.1.1 Interaction Between Communication Protocol and Native PCL Support The optional network card supports switching to native PCL; however, the protocol must be set to autosensing. 2.1.2 DEClaser 3500 Setup Modules These modules are used for the DEClaser 3500 printer only, and exploit the features of Resolution Enhancement and Toner Saver Modes, and provide a means to download a version of DECimage-Lite to the printer. The names of the modules are: Resolution Enhancement: o DL3500_RET_DARK o DL3500_RET_MED o DL3500_RET_LIGHT o DL3500_RET_OFF Toner Saver: o DL3500_TSAVER 19 DECimage-Lite: o DL3500_DI_HC o DL3500_DI_LC o DL3500_DI_BRIGHTER o DL3500_DI_DARKER o DL3500_DI_FLAT 2.1.2.1 Resolution Enhancement The resolution enhancement feature performs smoothing to both text and graphics. The level of smoothing is increased in the "DARK" setting and decreased in the "LIGHT" setting. The trade off is that the dark setting will tend to make thin lines a little thicker and may not be desirable. The factory default setting for the printer is "MED". 2.1.2.2 Toner Saver Mode The toner saver mode renders all characters as outlines and finds dark areas of any graphics and outlines these areas as well. This feature is quite useful for draft copies of documents and will still provide a "MEDIUM" level of resolution enhancement to the page. 2.1.2.3 DECimage-Lite The DECimage-Lite modules provide five different punch settings. These are: 1. A 20% contrast boost (HC) 2. A 20% contrast attentuation (LC) 3. Increase brightness by 10% (BRIGHTER) 4. Increase darkness by 10% (DARKER) 5. Apply the special halftone without gray level adjustment (FLAT) 20 2.1.2.4 Usage Example PRINT/QUE=quename/SETUP=(DL3500_RET_DARK) filename.ext ________________________ Note ________________________ These modules are mutually exclusive. The last one listed will be the one that takes effect. ______________________________________________________ ________________________ Note ________________________ The DECimage-Lite feature collides with the RET feature of the printer. One or the other may be used, but not both. Since the default setting for the printer is to have RET on, the DECimage-Lite setup modules turn it off for the current job. ______________________________________________________ 2.1.2.5 Other Useful Setup Modules There are two resolution selection setup modules which are useable with all multiple resolution printers. These are: o RES_600X600 o RES_300X300 These modules set the device resolution to 600 dpi or 300 dpi. 2.1.3 Selecting Statement Size Paper Statement size paper is the same size as half letter size paper. To use statement size paper, issue the following print command: $ print /parameter=sheet_size=halfletter 2.2 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. 21 2.3 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. Certain supported printers have slightly smaller than average print areas when using A4 paper, which resulted in the 66th line being lost or clipped. The problem occured when the print parameters PAGE_SIZE=A4, PAGE_ORIENTATION=LANDSCAPE were used. The ANSI translator shipped with DCPS V1.1A correctly prints 66 lines of text in landscape mode on A4 paper. In order to do this, the ANSI translator changed the vertical spacing of the font used (SGR 15) and corrected the maximum printable area for A4 paper. For those who have preprinted forms where the old behavior of the translator is expected, a DCPS queue logical may be defined to enable the old behavior. Here is an example: $ DEFINE/SYSTEM DCPS$_OLD_ANSI_PAGE_SIZES TRUE 2.4 New logical Created by Symbiont: DCPS$_PID The logical name, DCPS$_PID, is defined by the symbiont when it starts executing. This allows the system manager to determine which symbiont is assigned to a given execution queue. 2.5 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. 2.6 DEClaser 5100 Printer Specific Information 2.6.1 Uploading and Deleting Fonts This section was accidently omitted in the DCPS V1.1 documentation. It is provided here. The FONT_DOWNLOADER.COM file provides help to users when they are uploading or deleting fonts from the printer's optional hard drive. This file is located in the SYS$COMMON:[SYSHLP.EXAMPLES.DCPS] directory. 22 2.6.2 Native PCL Unavailable with EtherTalk Protocol on NIC Because of a problem with the Network Interface Card (NIC), DCPS cannot switch the printer into native PCL when using the EtherTalk protocol. Users will see the error: %DCPS-W-UNDEF, undefined: Name not known - offending command is <1B> %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored A partial workaround is possible by defining Page_ limit=9999 in P4 in the call to DCPS$EXECUTION_QUEUE.COM in DCPS$STARTUP.COM. This queue setup selects a feature that forces any PCL files to be printed through the PCL translator. As a reminder, the PCL translator is PCL 4, not PCL 5. 2.6.3 Occasional PostScript Error with PCL Jobs on LocalTalk Port Occasionally when printing PCL files using the native PCL interpreter in the DEClaser 5100 printer via the LocalTalk port, the following error occurs when the PCL job ends: %DCPS-W-UNDEF, undefined: Name not known - offending command is <1B>E<1B> %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored The entire file has been printed, but the printer may hang. The front panel displays PS Localtalk as an indication of the hang. To restore normal operation, press the Reset button on the printer's front panel. 2.7 PrintServer Printer Specific Information 2.7.1 Correction for Printserver ANSI Performance Problem 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 23 2.7.2 Remote Console Aborted Jobs on PrintServer Printers If a print job was submitted to a PrintServer printers 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. 2.7.3 Too Many Resources Loaded Prevent DCPS Symbionts from Starting Because of a CPAP protocol bug, DCPS symbionts are 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. 2.8 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. 2.9 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. 2.10 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. 24 3 New Features in DCPS V1.1 This section describes features that are new to DCPS V1.1. 3.1 New Interconnects and New Device Specification Syntax This version of DCPS adds support for printing to desktop printers via AppleTalk, and to Digital PrintServer printers using TCP/IP. Be sure to review the details in the DECprint Supervisor Version 1.1 New Features document. ______________________ Reminder ______________________ 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 actual device name is stored in a logical name in the form of DCPS$_DEVICE_NAME. ______________________________________________________ 3.2 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. 3.3 New Logical Name, DCPS$_IGNORE_UNKNOWN_USER 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 and the job will print normally. Because the username cannot be found, the symbiont cannot perform the "messages=keep" or "messages=print" parameter request. 25 To keep this OPCOM message from being displayed for every job, define the logical DCPS$_IGNORE_UNKNOWN_ USER to be "TRUE". 3.4 ANSI Prologue File A new ANSI prologue is included as part of the new ANSI translator, 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 PrintServers are updated. 4 Fixes Related to DCPS Software in General This section lists problems that have been corrected since DCPS V1.0 was released. 4.1 Separator Tray Logical Works on Generic and Execution Queues Previously, the logical DCPS$_SEPARATOR_TRAY worked only on generic queues. It now works on execution queues as well. 4.2 Suppressed Messages NOPAGEREGIONOP and NOSETPAGEDEVICE These undocumented informational messages no longer occur. 26 4.3 Fixed Problems Printing VFC-Format Files Printing of VFC file with 8C carriage control now works correctly. DCPS does not support printing VFC-format files whose organization is RELATIVE or INDEXED. DCPS now detects this condition and returns a file error message. 4.4 Increased Range of PAGE_LIMIT to 999999 The prior limit for either starting or ending page was 9999. It is now 999999. 4.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 4.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. 4.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. 4.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. 27 4.9 Corrected PostScript Handling in Layup DCPS now correctly handles idtransform and setpagedevice commands in layup facility. 5 Fixes Related to Supporting Printers 5.1 LCIT Keyword Now Recognized for PrintServer 17 The parameter INPUT_TRAY=LCIT can now be used to select the large capacity input tray on the PrintServer 17 printer. 5.2 Fixed OUTPUT_TRAY=SIDE for PrintServer 17 The parameter OUTPUT_TRAY=SIDE now selects the lower tray for all members of the PrintServer family. 5.3 Fixed Delay for Manual Feed with Apple and HP Printers New code activate a delay for insertion of paper into manual feed slot with Hewlett-Packard LaserJet III, IIID and IIISi and supported Apple LaserWriter printers. 6 Restrictions The following restrictions and limitations are found in this version. 6.1 Device Control Libraries Must Exist for Queue to Start All device control libraries specified for a queue must exist for the queue to start. If a queue is defined with the following logical, the libraries SYS$LIBRARY:DCPS$DEVCTL.TLB, SYS$LIBRARY:ANSI.TLB and SYS$LIBRARY:PS.TLB must all exist as text libraries: $ define/system/exec dcps_lib - dcps$devctl, - "ansi/data=ansi", - "ps/data=post" 28 6.2 Compatibility with DCPS V1.0 software Many of the components supplied with DCPS V1.1 are not compatible with those supplied in previous versions. You may have only one version of the DCPS product installed on a host at a time. 6.3 Compatibility with DEC Image Print-PLUS (ICPS) DCPS V1.1 cannot coexist with ICPS V1.x software. DCPS V1.1 replaces this software. Installing DCPS V1.1 replaces the image SYS$LIBRARY:TRN$DDIF_IMAGE.EXE. This new image is not compatible with the ICPS software. 6.4 DDIF Printing Requires DECimage Application Services for VMS V3.1 To print DDIF encoded bitonal images, DCPS requires Version 3.1 of DECimage Application Services. 6.5 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. 6.6 The New LIST Data Type The following list outlines the features of the LIST data type. a. The LIST data type feature employs a new text-to- PostScript translator. The LIST translator is not an ANSI translator. It translates 8-bit ASCII (ISO 8859- 1) text to a convenient printable form. It does not translate escape sequences, such as those defined by ANSI PPL3, HP-PCL, or any other printer protocol. You should continue to use the ANSI data type for printing jobs that include and require translation of DEC PPL3 data and control sequences. 29 b. 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. c. The gray bars that the LIST translator uses to highlight alternate groups of lines appear extremely light or not at all on the following printer: Apple LaserWriter IIg DEClaser 5100 at resolutions above 300X300 dpi 6.7 PC Driver Settings to Avoid Problems with PJL and TBCP Recent printing protocol enhancements have introduced new variables into the networked printing environment. These are HP PJL (Print Job Language), and HP TBCP (Tagged Binary Communication Protocol). Documents created from a PC application can have these protocols included in the files. These protocols can be quite useful in some environments, but sometimes cause problems for DCPS or for printers other than the type for which the document was created. A brief description of PJL and TBCP is included below, followed by instructions to prevent problems with DCPS. 6.7.1 Description of PJL and TBCP PJL is a command language that allows job-level printer control. TBCP is a communications protocol for the serial, LAT, and parallel ports of a printer. It allows 8-bit binary data in files concurrent with the use of some control characters for communications and print job control. You cannot print TBCP to printers that do not support TBCP, or to ports other than the serial, LAT or parallel ports for printers. The DEClaser 5100 printer is the first Digital printer to support both PJL and TBCP. Some HP III series printers support PJL, and most HP IV series printers support both PJL and TBCP. When a PC application is creating files for printing to these printers, the files can include PJL and TBCP. 30 6.7.2 Steps to Prevent Problems with DCPS V1.1 When printing files can include PJL, DCPS will strip any PJL from the file. This is so DCPS can use PJL to switch print protocols in the printer, and to allow the printing of these files on printers that do not support PJL. If the interconnect to the printer is not serial or LAT, the file must not use the TBCP. DCPS does not remove TBCP characters. 6.7.2.1 Preventing problems with PostScript When the PC application is generating PostScript output use the following guidelines: 1. If the selected printer on the PC is the same as the actual printer, the only concern is whether TBCP is used. If the interconnect is serial or LAT then TBCP may be used. If the interconnect is AppleTalk, then TBCP must be disabled. Because detailed information about the printer and queue may not be available to a PATHWORKS user, DCPS recommends TBCP be disabled. Either one of the following steps may be used: o Select the Protocol "None (AppleTalk)" under the PS Options menu of the DEClaser 5100 driver. This will disable both TBCP and PJL. Note that disabling the Performance item "Binary" in the PostScript Option menu is not sufficient. The file will not include binary data, but it still includes the TBCP introducer, which will cause PostScript errors. o Disable the "Tagged Binary" item from the Advanced Options Menu of the HP 4ML PostScript driver, or other printer drivers that offer this. This will disable TBCP. The TBCP introducer is not included in the file. 2. If a file is being created for later printing to a unknown printer, it is best to avoid both TBCP and PJL. To disable TBCP and PJL, select one of the following options: o Select the Protocol "None (AppleTalk)" under the PS Options menu of the DEClaser 5100 driver. This will disable both PJL and TBCP. Also, disable the 31 Performance item "Binary". The file will not include binary data and can then be successfully printed using any communications channel. o Select a printer on the PC that does not support TBCP or PJL, for example, Digital's PrintServer printers, or the DEClaser 1152 printer. 6.7.2.2 Preventing problems with PCL When the PC application is generating PCL output, please note the following: With DCPS V1.1, all PJL commands are stripped from the file. Drivers for PCL Level 5 printers will use PJL to select advanced printing features, such as the configuration of the Resolution Enhancement hardware (RET), page protection, and print resolution. As these commands are stripped, the print job may not print as expected. Also, the PCL will be sent to the printer only if DCPS supports printing PCL directly to the printer. Otherwise, the PCL (Level 4) translator will be used. 6.8 Interaction Between Native PCL Printing and Automatic DATA_TYPE Detection Jobs that use DATA_TYPE=AUTOMATIC=PCL may print with unexpected results. In particular, files that are printed as PCL looking for a switch to PostScript may get printed entirely as PCL. This occurs if the following is true: 1. DCPS does not detect the datatype of the file by looking at the first few bytes of the file or by matching the file extention to a datatype. 2. The target printer can print PCL files as well as PostScript files. 3. DCPS supports printing using the PCL language interpreter in the printer. 4. There are no other print qualifiers that require the file to be printed using the PCL translator (for example, NUMBER_UP or PAGE_LIMIT). Under these circumstances, DCPS uses the PCL language interpreter in the printer, and does not look for a switch to PostScript. Also, the automatic language sensing feature of the printer will not be used to detect the file's switch 32 from the PCL language to the PostScript language. This is because DCPS specifies that the file's data type is PCL, and this disables any auto language sensing by the printer. Suggested workarounds include: 1. Set up the print queue to use AUTOMATIC, but select ANSI as the default data type. Generally, the text part of files that include both text and PostScript is simple ACSII text that is handled properly by both the ANSI and PCL translators. 2. Set up the print queue with a qualifier that requires the use of the PCL translator (include the page_limit qualifier as a default queue parameter). This will ensure the PCL translator is used for all PCL files. Note though that the PCL translator interprets PCL level 4. The printers for which DCPS supports printing in native PCL mode have PCL level 5 language interpreters. 6.9 Native PCL Mode Concatenates Files If the PCL language interpreter in a printer is used to print PCL files and a job includes multiple PCL files, the PCL files are concatenated. DCPS does not ensure that the files begin on new pages, or even that the last line of the first PCL file does not get printed over by the first line of the next PCL file. This can occur if: o The files do not ensure the page is ejected from the printer. To ensure PCL files print correctly, HP recommends that PCL files begin and end with the PCL reset sequence E. Files that include this sequence print correctly. o Multiple files are specified and two or more files in sequence are PCL o /COPIES is used on a PCL file o /JOB_COUNT is used and two or more PCL files are printed in sequence If PCL files get concatenated and it is not acceptable, workarounds include: o Create and use a PCL setup module to include the PCL reset sequence in the data stream before a file prints. 33 o Print using the PCL translator by specifying a parameter that forces DCPS to use the PCL translator (e.g, NUMBER_ UP, or PAGE_LIMIT) o Print the job and specify a file separation page between all files (PRINT/FLAG). 6.10 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. 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. 6.11 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: HP LaserJet IIISi HP LaserJet 4SiMX 6.12 OUTPUT=FACE_UP Goes to Wrong Tray on HP LaserJet 4SiMX If you specify /PARAMETERS=OUTPUT=FACE_UP with the Hewlett- Packard LaserJet 4SiMX, the trailer page is sent to the top tray. 34 6.13 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 DPCS 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. 6.14 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. 35 6.15 Deleting Jobs on an AppleTalk Connected DEClaser 1152 Printer Deleting a job printing on the DEClaser 1152 printer can cause the next job to hang. This can occur when all the following conditions are met: o The AppleTalk (Localtalk) port of the DEClaser 1152 is used o The deleted job leaves many pages in the printer's buffer; so the printer continues to print long after the job is deleted o The next print job starts before all the pages of the previous job complete. This next job does not print, but remains in the queue as printing and the queue eventually stalls. The problem occurs because the printer has accepted an AppleTalk connection before it is ready. The hung job must be deleted and submitted again. The job may take some time (up to 90 seconds) to delete. 6.16 Apple LaserWriter Plus does not Support LPS$PERSISTENT_RESOURCES The DCPS V1.1 feature to load the module LPS$PERSISTENT_ RESOURCES outside the PostScript server loop for desktop printers is not supported for the LaserWriter Plus. 6.17 Native PCL Restrictions to Print Parameters The following DCPS print parameters do not affect printing of PCL files on printers for which DCPS V1.1 uses native PCL capability: INPUT_TRAY OUTPUT_TRAY SHEET_SIZE PAGE_SIZE SIDES PAGE_ORIENTATION In these cases the default setting of the printer takes effect. You can manipulate PCL printer tray selection by inserting appropriate PCL escape sequences in the print file or in setup modules. 36 Alternatively, you can have these parameters affect your job by forcing translation to PostScript on the host. To force translation, use a DCPS feature that invokes layup, such as NUMBER_UP or LAYUP_DEFINITION, or by using both the PAGE_SIZE and SHEET_SIZE parameters. 6.18 Incorrect Page Count on Native PCL Jobs on HP IIISi The Hewlett-Packard LaserJet IIISi printer does not keep track of the page count while printing native PCL files. The page count reported at the end of the job, both on the trailer page and to the OpenVMS accounting system, includes only those pages printed in PostScript mode, such as the job separation pages. There is no known workaround for this problem. 6.19 Incorrect Sheet Count on Duplex Jobs with HP LaserJet Printers The Hewlett-Packard LaserJet IIID, IIISi, 4SiMX printers do not internally count physical sheets but instead count pages imaged. Therefore the "Sheets printed" data of the trailer page will reflect the number of images processed. For example, a six-page print job with burst and trailer pages enabled and /PARAMETERS=(SIDES=2) specified will show "Sheets printed" as eight when only five sheets are printed. 6.20 Communication Problem with the HP XL300 Printer If a file printed to the XL300 printer contains multiple userdata mesages that are returned in quick succession, some messages may be lost, and others returned incorrectly. Also, occasionally, messages that the DECprint Supervisor wants returned to it will get garbled. This will result in spurious messages to the user's terminal (if /NOTIFY is set). Otherwise, the job prints correctly. 6.21 Do Not Issue STOP/QUEUE/RESET when a PrintServer Printer is Rejecting Connections If you issue a STOP/QUEUE/RESET command for a queue to a PrintServer printer while there is a job in the "Starting" state and while the PrintServer 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 37 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. 6.22 No Job Trailer Page on DELETE/ENTRY If you issue a DELETE/ENTRY command is 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. 6.23 Problems with PostScript Files when Printing with /COPIES When you use the /COPIES qualifier with a PostScript file, then DCPS will surround 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. Use the /JOB_ COUNT qualifier instead of /COPIES. 7 Additional Information About DCPS This section includes general information about the DCPS product that is either not included in or supersedes information in the DECprint Supervisor information set. 7.1 Interaction between Colored Separator Pages and the PrintServer 17 Input Tray Failover PrintServer Software, Version 5.0, adds input tray failover to the PrintServer 17 series printers. This feature allows the printer to automatically switch to another input tray containing the same size media when the current tray becomes empty. This feature is enabled by default. If you currently use colored flag pages, you may want to disable this feature. To disable input tray failover, perform the following steps: 1. Edit LPS$SUPPORT:LPSDEFAULTS. 38 2. Search for the /TraySwitch parameter: /TraySwitch true % Controls input tray failover. % false = disable % true = enable 3. Change the value of the TraySwitch parameter from "true" to "false". PostScript is case sensitive; the only valid values are "true" or "false". /TraySwitch false % Controls input tray failover. % false = disable % true = enable 4. Enable the changes by issuing the reconfigure command from the remote console facility. $ MCR LPS$CONSOLE LPS> PRIV Password: LPS> RECONFIG LPS> EXIT Refer to the PrintServer Software Management Guide for additional information. 7.2 Error Page Feature of DEClaser 5100 The DEClaser 5100 printer has a feature that ejects the current sheet and then prints a PostScript Error information sheet when a PostScript interpreter error occurs. While this feature provides a powerful means for analyzing PostScript problems, it is not recommended for everyday use with the DECprint Supervisor software for the following reasons: o PostScript error pages are printed when a user enters DELETE/ENTRY to abort a print job. o PostScript error pages are printed after a not ready condition is cleared (paper supplied, jam corrected, etc.) if a job was submitted on the serial port while the printer was not ready to print. You should disable the feature called "Print Errors" through the DEClaser 5100 front panel before starting print queues with DCPS. Enable the feature only when you are interested in analyzing PostScript problems. 39 If a job fails to print because of a "Limitcheck" error, also see if "page protection required" is part of the error message. Presence of this error means the job failed because of a banding failure. 7.3 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. 7.4 Unique AppleTalk Node Addresses for Reliable Printing If you use your printer in a AppleTalk network, the address of the printer in the AppleTalk network is based on the printer's PostScript printername. If two or more printers have the same printername and are on the same zone of the AppleTalk network, the actual node names for these printers will be depend on the order in which the printers are powered up. Printers of the same product type will have the same printername until it is explicity changed. Therefore, it is necessary to change a printer's printername to ensure the printer is uniquely and consistently identified on the network. Use the tools provided with your printer, and/or your PC or Macintosh to change the name of your printer. 7.5 Printing on Unrecognized Printers The DECprint Supervisor software automatically obtains a printer's product name before printing jobs. It uses the product name to select and download device control modules that are specific to the particular printer. If you use the DCPS software with a printer whose product name it does not recognize, and the system has the DCPS-OPEN license loaded, the product name defaults to "UNRECOGNIZED", and the supervisor downloads device control modules associated with that name. Although this 40 configuration is unsupported, the modules associated with the unrecognized printer may be sufficient to permit simple printing with that device. A system manager can modify the corresponding device control modules as needed without affecting the characteristics of any of the supported printers. Device control modules are located in the following device control library: SYS$COMMON:[SYSLIB]DCPS$DEVCTL.TLB The device control modules associated with the unrecognized device are: LPS$$UNRECOGNIZED_INITPSDEVICE LPS$$UNRECOGNIZED_SETCONTEXT LPS$$UNRECOGNIZED_SETINPUTTRAY LPS$$UNRECOGNIZED_SETOUTPUTTRAY If you modify these modules for a certain printer, you should always place the modified modules in a site-specific device control library, and prepend the file specification of that library to the DCPS_LIB logical name search list. Refer to the DECprint Supervisor System Manager's Guide for more information about modifying device control library modules. 41 A _________________________________________________________________ List of Files Installed on AXP DCPS012.RELEASE_NOTES [SYS$HELP] DCPS$HELP.HLP [SYS$HELP] 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 AXP A-1 List of Files Installed on AXP COLOR-PRINTER-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] DCPS-USER-CARD.PS [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 AXP B _________________________________________________________________ List of Files Installed on VAX DCPS012.RELEASE_NOTES [SYS$HELP] DCPS$HELP.HLP [SYS$HELP] 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 B-1 List of Files Installed on VAX COLOR-PRINTER-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] DCPS-USER-CARD.PS [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] PS-PRINTING-ALL-IN-1-COMPAT.SAV [SYSHLP.EXAMPLES.DCPS]* PS-PRINTING-ALL-IN-1-COMPAT.TXT [SYSHLP.EXAMPLES.DCPS]* * Optional files for ALL-IN-1 compatibility kit B-2 List of Files Installed on VAX