_____________________________________________ DECprint Printing Services Software Installation Guide AA-PBZEA-TE This manual describes how to install the DECprint Printing Services software and how to configure print queues for printing. Revision/Update Information: This is a new manual. Operating System and Versions: VAX/VMS, Versions 5.3 and later Software Version: DECprint Printing Services for VMS Version 4.0 digital equipment corporation maynard, massachusetts _____________________________________________ First Printing, October 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © by Digital Equipment Corporation 1990. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, COMPACTape, DDIF, DEClaser, DECnet, DECprint, DECserver, LN03, LN03 Image, LN03 PLUS, LN03R, PrintServer, PrintServer 20, PrintServer 40, PrintServer 40 Plus, Q-bus, ReGIS, ScriptPrinter, TK, UNIBUS, VAXBI, VAX, VAXcluster, VAXstation II, VAXstation II/GPX, VMS, and the DIGITAL Logo CG Triumvirate is a trademark of AGFA Compugraphic Division. ITC Souvenir is a registered trademark of International Typeface Corporation. LaserJet is a registered trademark of Hewlett-Packard Company. PCL is a registered trademark of Hewlett-Packard Company. POSTSCRIPT is a registered trademark of Adobe Systems, Inc. Swiss is a trademark of Bitstream Inc. Tektronix is a registered trademark of Tektronix, Inc. The document is available on CDROM. This document was prepared using VAX DOCUMENT, Version 1.2 ________________________________________________________________ Contents About This Guide......................................... vii 1 Overview 1.1 Printers Supported by DECprint Printing Services........................................ 1-1 1.2 Capabilities of DECPrint Printing Services Software........................................ 1-2 1.2.1DEClaser 2150/2250 Printers .................. 1-3 1.2.2PrintServer Printers ......................... 1-4 1.2.3LN03 Image Printers .......................... 1-5 1.2.4ScriptPrinter Printers ....................... 1-7 1.3 Printing System Compatibility................... 1-7 1.3.1Upgrading PrintServer Client Software ........ 1-7 1.3.2Upgrading ScriptPrinter and LN03 Image Software..................................... 1-8 iii 2 Preinstallation Requirements 2.1 Hardware Requirements........................... 2-1 2.1.1DEClaser 2150/2250 and ScriptPrinter Hardware Requirements................................. 2-2 2.1.2PrintServer Hardware Requirements ............ 2-3 2.1.3LN03 Image Printer Hardware Requirements ..... 2-3 2.2 Software Requirements........................... 2-3 2.3 DECprint Printing Services Software Distribution Kit............................................. 2-3 3 Installing the Software 3.1 VMSINSTAL Conventions........................... 3-2 3.2 Installation Procedure.......................... 3-3 3.2.1Choosing Release Notes Options ............... 3-5 3.2.2Purging Files ................................ 3-5 3.2.3Selecting a Logical Definition for LPS$LAYUP.................................... 3-6 3.2.4Selecting ALL-IN-1 Compatibility Kit ......... 3-6 3.2.5Installation Verification Procedure Check .... 3-7 3.2.6Translator Installation Check ................ 3-8 3.2.7Completing the Installation Procedure ........ 3-8 3.2.8Installation Verification Procedure .......... 3-9 3.3 Starting the DECprint Printing Services Printing System.......................................... 3-10 3.4 Upgrading Printer Software...................... 3-11 3.5 Testing the Printers and Queues................. 3-11 4 PostInstallation Procedures 4.1 Installing Serial Printers...................... 4-1 4.1.1Changing the ScriptPrinter Communication Speed........................................ 4-2 4.1.2Baud Rate Limitations ........................ 4-2 4.1.3Changing the Default Settings ................ 4-3 iv 4.2 Requirements for Installing DEClaser Printers... 4-4 4.3 Requirements for Installing PrintServer Printers........................................ 4-4 4.3.1Installing a PrintServer Client System ....... 4-5 4.3.1.1 Including the PrintServer Node Name in CPS$STARTUP............................. 4-5 4.3.1.2 Defining the PrintServer Network Nodes .. 4-5 4.3.1.3 Deleting the PrintServer Startup File ... 4-6 4.4 Installing the LN03 Image Printer............... 4-6 4.5 Setting the Printer Name........................ 4-7 4.6 Setting the Printer Timeout Using PostScript Operators....................................... 4-8 4.7 Making DECserver Connections for Serial Printers........................................ 4-9 4.7.1DECserver Connections ........................ 4-10 4.7.2DECserver Port Characteristics ............... 4-11 4.7.3Editing the LAT Protocol Startup and Configuration File........................... 4-13 4.7.4LAT Groups ................................... 4-14 5 Initializing Print Queues 5.1 Types of Printer Queues......................... 5-1 5.2 Starting the System Queue Manager............... 5-2 5.3 Defining Print Queues........................... 5-2 5.3.1Copying the Printer Startup Command File ..... 5-3 5.3.2Editing the Printer Startup File ............. 5-3 5.3.3Defining a Device Control Library Logical Name......................................... 5-4 5.3.3.1 Defining a Library Search List .......... 5-5 5.3.3.2 Preserving Custom Device Control Modules................................. 5-6 5.4 Setting Up Execution Queues..................... 5-7 5.4.1Specifying the Device Name for Parameter p2 .. 5-8 5.5 Setting Up Generic Queues....................... 5-11 5.6 Changing the Default Parameters for a Queue..... 5-12 v 5.6.1Syntax for Parameters Associated with a Queue........................................ 5-13 5.6.2Syntax Errors in Parameters Associated with a Queue........................................ 5-13 5.6.3Order of Defaulting for Parameters ........... 5-14 5.7 Changing the Default Qualifiers for a Queue..... 5-15 6 System Messages 6.1 Message Format.................................. 6-1 6.2 Severity Level.................................. 6-2 6.3 Message Descriptions............................ 6-2 A Sample Installation Session B Sample Startup Command File C Installation Verification Output D New Files and Libraries D.1 New Files....................................... D-1 D.2 Device Control Library.......................... D-4 D.3 Files For PrintServer Software Upgrade Procedure....................................... D-5 vi E Troubleshooting Procedures E.1 The Printer Is Not Printing Any Jobs............ E-1 E.1.1Newly Installed Printer ...................... E-2 E.1.2The Printer Has Stopped Printing ............. E-7 E.2 Printing Is Slower Than Expected................ E-8 E.3 Layup Definition Files Are Not Found............ E-9 E.4 Printer Is Not Printing in Network Environment..................................... E-9 E.4.1Determining Which Host Controls the Printer .. E-10 E.4.2Troubleshooting the Printer .................. E-13 E.4.2.1 Regaining Control of the DECserver Port.................................... E-13 E.4.3Common DECserver Error Messages .............. E-14 E.5 Eliminating Login Dialog on Serial Printers..... E-16 E.6 PrintServer Troubleshooting Procedures.......... E-17 E.6.1Printer Is Not Printing Jobs ................. E-17 Index Examples 5-1 Library Logical Name Definition.................. 5-5 5-2 Setting Up an Execution Queue.................... 5-9 5-3 Setting Up a PrintServer Execution Queue......... 5-10 5-4 Setting Up a Generic Queue....................... 5-12 A-1 Sample Installation.............................. A-1 B-1 Sample Printer Startup Command File.............. B-1 E-1 Determining Printer Host......................... E-12 vii Figures 1-1 LN03 Image Printer Software...................... 1-6 C-1 Printed IVP Output-ANSI Data Page................ C-3 C-2 Printed IVP Output-ReGIS Data Page............... C-5 C-3 Printed IVP Output-TEK4014 Data Page............. C-7 C-4 Printed IVP Output-PostScript.................... C-9 C-5 Printed IVP Output-HP PCL........................ C-11 Tables 1 Conventions...................................... xi 1-1 Supported Printers............................... 1-2 4-1 Communication Switch Default Settings............ 4-2 4-2 LN03 Image Printer SYSGEN Values................. 4-6 4-3 Printer-Required DECserver Port Characteristics.................................. 4-11 4-4 DECserver Port Characteristics................... 4-12 4-5 DECserver Server Characteristics................. 4-12 5-1 Parameter Values for Execution Queues............ 5-7 5-2 Parameter Values for Generic Queues.............. 5-11 D-1 New Files........................................ D-1 D-2 PrintServer Client Files To Delete............... D-5 D-3 PrintServer Client Files To Retain............... D-6 viii ________________________________________________________________ About This Guide Intended Audience The DECprint Printing Services Software Installation Guide is intended for use by system managers responsible for installing the DECprint Printing Services software and for defining and maintaining the print queues. The system manager installing DECprint Printing Services software should be familiar with procedures and commands in the DECprint Printing Services System Manager's Guide. If you are installing the DECprint Printing Services software, you should be familiar with the VMSINSTAL utility for installing VMS software. Network printer installation requires some knowledge of DECnet network management. And, if you are installing serial printers on DECservers, you should have some knowledge of DECserver software management. vii Document Structure This manual contains the following chapters and appendixes: _ Chapter 1 lists the printers supported by DECprint Printing Services software, and the capabilities of each printer. _ Chapter 2 lists the hardware and software prerequisites to installing the DECprint Printing Services software. Read this chapter before you run the VMSINSTAL utility to install DECprint Printing Services software. _ Chapter 3 contains the procedures for installing the DECprint Printing Services software. The procedures for starting the printer system and and testing the printer are also included. _ Chapter 4 describes procedures to perform after you run VMSINSTAL, to set up certain types of printers and printer configurations. This chapter is helpful for installing a new PostScript printer. _ Chapter 5 describes procedures for defining and starting print queues at your site. _ Chapter 6 lists the error and status messages you might encounter during installation of DECprint Printing Services, and explains how to respond to them. _ Appendix A shows a sample installation procedure. _ Appendix B shows a sample printer startup command file. _ Appendix C shows the Installation Verification Procedure (IVP) test files, which you may print after installation to test the printing system. _ Appendix D lists the files and libraries created during the installation procedure. _ Appendix E describes troubleshooting procedures for solving problems with the printer system. viii Associated Documents The following documents are associated with the DECprint Printing Services software: _ DECprint Printing Services System Manager's Guide _ DECprint Printing Services Software Installation Guide _ Installation Guide: VAX PrintServer Supporting Host _ Management Guide: VAX PrintServer Supporting Host _ User's Guide: PrintServer Client for ULTRIX _ PostScript Programmer's Supplement _ PostScript Language Reference Manual _ PostScript Translators Reference Manual for ReGIS and Tektronix 4010/4014 _ Digital ANSI-Compliant Printing Protocol Level 3 Programming Reference Manual _ Digital ANSI-Compliant Printing Protocol Level 3 Programming Supplement _ VMS DCL Dictionary _ Introduction to VMS System Management _ VAX/VMS System Messages and Recovery Procedures Reference Manual _ VAX/VMS System Manager's Reference Manual _ Guide to Maintaining a VMS System _ DEClaser 2100 Printer Operator's Guide _ DEClaser 2200 Printer Operator's Guide _ DEClaser 2200 Printer Installation Guide _ LN03R ScriptPrinter Installation Guide _ LN03R ScriptPrinter Operator's Guide ix _ DECserver 100 Terminal Server Operator's Guide _ DECserver 200 Management Guide _ DECserver 500 Management Guide _ Guide to Terminal Server Manager _ VMS LAT Control Program (LATCP) Manual The DECprint Printing Services software documentation is available in the form of a documentation kit with order number AA-YNCAA-GZ. x Conventions Table 1 lists the conventions that are used throughout this document: Table 1 Conventions _____________________________________________________________ Convention__Meaning__________________________________________ UPPERCASE Uppercase characters indicate DCL commands, CHARACTERS qualifiers, and parameters. italics Italic characters used in command examples indicate that you are to substitute a word or value of your choice. bold Bold characters are PostScript operators or error message prefix strings. | | red ink The red ink in examples indicates information you | should enter as part of the procedure. [] Square brackets indicate that the enclosed item is optional. Indicates a control key sequence. Press the key labeled Ctrl while you simultaneously press another key, represented by x. This symbol indicates that you should press the ____________Return_key.______________________________________ xi 1 ________________________________________________________________ Overview This chapter provides an overview of Digital's PostScript printers and the software features of the DECprint Printing Services software, as follows: _ Printers supported by DECprint Printing Services software, Section 1.1 _ Capabilities of the DECprint Printing Services software, Section 1.2 _ Differences between installing DECprint Printing Services and installing existing printer system software, Section 1.3 1.1 Printers Supported by DECprint Printing Services The DECprint Printing Services software supports the printers listed in Table 1-1. Overview 1-1 Table 1-1 Supported Printers _____________________________________________________________ Maximum Printer Pages Simplex Product Model per or Name________Number___Minute___Duplex___Comm._Interface_______ ScriptPrinteLN03R 8 Simplex Serial LN03 Image LN03Q 8 Simplex Special PrintServer LPS20 20 Duplex Ethernet 20 PrintServer LPS40 40 Simplex Ethernet 40 PrintServer LPS40 40 Simplex Ethernet 40 Plus Plus DEClaser LN05R 8 Simplex Serial 2150[1] DEClaser LN06R 8 Duplex Serial 2250[1] _____________________________________________________________ [1]DEClaser 2150 represents the DEClaser 2100 printer with the PostScript upgrade cartridge. DEClaser 2250 represents the DEClaser 2200 printer with the PostScript upgrade cartridge. _____________________________________________________________ 1.2 Capabilities of DECPrint Printing Services Software Digital's PostScript printers support PostScript printing through laser printing technology, to produce high-quality printouts. Through DECprint Printing Services, Digital's PostScript printers print DDIF bitonal image files, Adobe's PostScript page description language, and the ANSI/sixel, ReGIS, Tektronix 4010/4014, and PCL data syntaxes. Translator software converts these files into PostScript code. Using DECprint Printing Services software, you can submit print jobs from the PRINT command line or by using the VMS system service $SNDJBC in an application program to print user files. The PRINT command line consists of the standard VMS DCL PRINT command with appropriate qualifiers. Several 1-2 Overview parameters for the /PARAMETERS qualifier are defined to extend printing functions. User notification of printer status is available through the /NOTIFY qualifier. You can enhance the print job by including setup modules. PostScript setup modules allow you to redefine the PostScript environment; ANSI setup modules can send ANSI escape sequences to affect ANSI print jobs. For more information, refer to DECprint Printing Services System Manager's Guide. DECprint Printing Services emulates the printing features of the LN03 printer, allowing LN03 printer customers to replace or upgrade their LN03 printer to PostScript printers without loss of print capabilities. To aid in this product migration, Digital offers the SoftFonts products for emulating font cartridges on PostScript printer. Refer to the DECprint Printing Services User's Guide for more information on the FONTS_USED parameter to the PRINT command. Installing DECprint Printing Services does not require printer hardware to be installed previously. Be sure to create and define an execution queue for each printer, however, before attempting to print on one of these printers. The following sections describe each type of printer and its | special characteristics. | | 1.2.1 DEClaser 2150/2250 Printers | | DEClaserEClaser 2150 and 2250 printers are desktop printers for | printerscript printing. The DEClaser 2150 is the base DEClaser | | 2100 with the PostScript cartridge installed inthe memory | slot in the front of the printer. The DEClaser 2250 is the | base DEClaser 2200 with the PostScript cartridge installed | in the memory slot. These two printers feature manual media | feeding, and envelope printing using an envelope cassette. | They are compatible replacements for a ScriptPrinter | printer. As such, they are equipped with a serial interface | suitable for direct hardware connection to the system or for | connection to a DECserver device on the Ethernet. | | The DEClaser 2250 printer provide these additional features | over the DEClaser 2150: | | _ Duplex printing | | _ Optional power envelope feeder | | _ Two input tray slots | Overview 1-3 | For information about using these features, refer to the | DECprint Printing Services User's Guide. | | Installing Software for DEClaser Printers | | To use this manual for installing the DECprint Printing | Services software to support a DEClaser 2150 or DEClaser | 2250 printer, follow the sections listed below: | | 1 To prepare for installing the DECprint Printing Services | software to support a new DEClaser printer, follow the | instructions in Chapter 2. Section 2.1.1 lists hardware | requirements specific to the DEClaser printers. | | 2 Run VMSINSTAL to install the DECprint Printing Services | software, as described in Chapter 3. | | 3 In the case of a DEClaser printer connected to a DECserver | port for network access, follow the instructions in | Section 4.7. | | 4 To create and modify print queues and set up the printing | software, refer to Chapter 5. | 1.2.2 PrintServer Printers PrintServertServer 20, PrintServer 40, and PrintServer 40 Plus printersers are high-speed network printers with multiple input trays and output trays. PrintServer 20 printers support duplex printing; the PrintServer 40 and PrintServer 40 Plus printers support simplex printing only. Every PrintServer printer is a node on an Ethernet network and communicates with other nodes in the network. The nodes that access PrintServer printers using DECprint Printing Services software are referred to as "PrintServer clients". The client nodes running DECprint Printing Services must also be running DECnet to access the PrintServer printer. The supporting host is the network node that performs boot services and printer management services for PrintServer printers. The node that functions as the supporting host can also be a PrintServer client, but this is not a requirement. Refer to Installation Guide: VAX PrintServer Supporting Host for information about installing the PrintServer Supporting Host software. See the Management Guide: VAX PrintServer Supporting Host for information about PrintServer Supporting Host management. 1-4 Overview Installing Software for PrintServer Printers To install the DECprint Printing Services software on a client system on the network, follow the procedures described in the sections listed below: 1 Prepare for the software installation as described in Chapter 2. Specific PrintServer hardware requirements are described in Section 2.1.2. 2 Run VMSINSTAL to install the DECprint Printing Services software, as described in Chapter 3. 3 Before you start the DECprint Printing Services queue, make sure that the supporting host software is installed and has been booted on the supporting host node (refer to the Installation Guide: VAX PrintServer Supporting Host). and enter the PrintServer node name and address in the DECnet node database. Refer to Section 4.3. 4 Specific procedures for installing DECprint Printing Services to support PrintServer printers are described in Section 4.3. 5 Create or modify print queues as described in Chapter 5, to customize the printer environment on the client system. 1.2.3 LN03 Image Printers LN03hImage3 Image printer is a desktop printer for image printersing. The LN03 Image printer receives a bit map over a very high-speed interface to print an image. This printer is capable of printing image files much faster than the other printers supported by DECprint Printing Services. A PostScript interpreter produces bitmap information from PostScript code to print the data on the LN03 Image printer. Serial printers are connected to the host system either by a DECserver port or by direct serial line interface. The LN03 Image printer software consists of the following components: _ LN03 Image Services software _ LN03 Image Support software _ DECprint Printing Services Overview 1-5 Figure 1-1 LN03 Image Printer Software Figure 1-1 illustrates the operations for printing different types of file data syntaxes on the LN03 Image printer. As illustrated in Figure 1-1, the following types of file data syntax require processing by one or more software components: _ PostScript files _ Digital Data Interchange Format (DDIF) bitonal image files _ File requiring a translator (ANSI, ReGIS, Tektronix 4010/4014, and HP PCL data syntax) Installing Software for LN03 Image Printers To install the DECprint Printing Services software to print on an LN03 Image printer, follow the instructions in the following list: 1 Before you initiate the DECprint Printing Services software, be sure to install the LN03 Image Support and Image Services software, and start the queues. 2 Prepare the system by following the instructions in Chapter 2. Specific hardware requirements for an LN03 Image printer are described in Section 2.1.3. 3 Run VMSINSTAL to install the DECprint Printing Services software, as described in Chapter 3. 4 Specific instructions for installing DECprint Printing Services software to support LN03 Image printers are described in Section 4.4. You must adjust certain system parameters. The SYSGEN parameters you must change, and recommended values, are listed in Table 4-2. 5 Before you start the queue, follow the directions in Chapter 4 to create or modify print queues and customize your printing system. 1-6 Overview 1.2.4 ScriptPrinter Printers ScriptPrinterPrinter printer is a desktop printer for PostScript printersing. It can serve as a local printer for a VMS system, accepting PostScript files without translation. ScriptPrinter printers are connected to the host system either by a DECserver port or by direct serial line interface. Installing Software for ScriptPrinter Printers To install a new ScriptPrinter printer, follow the installa- tion procedures in the following sections: 1 Prepare for the software installation by reading Chapter 2 for serial printers. In particular, refer to Section 2.1.1. 2 Run VMSINSTAL to install the DECprint Printing Services software, as described in Chapter 3. 3 Specific instructions for installing the DECprint Printing Services software to support ScriptPrinter printers are described in Section 4.1. To install a ScriptPrinter printer on a DECserver port for network access, refer to Section 4.7. 4 Follow the instructions in Chapter 4 to initialize or modify print queues and to customize the printing system. | 1.3 Printing System Compatibility | | The DECprint Printing Services software replaces the VAX | PrintServer Client Version 3.0 and the VAX ScriptPrinter | Version 2.1 software products. | | 1.3.1 Upgrading PrintServer Client Software | | PrintServerver client installation for DECprint Printing | printersces requires you to run VMSINSTAL, create the printer | | startup file, edit the system startup file, and execute the | startup command file. In order to use DECprint Printing | Services Version 4.0, the supporting host system must be | running PrintServer Supporting Host Version 3.0 and higher. | | Sites upgrading from the PrintServer Client software | should note the following differences from that software's | installation procedure: | | 1 New method of specifying queue structure. Overview 1-7 | The DECprint Printing Services software kit includes | a template file for specifying generic and execution | queues. The resulting startup file is preserved during | subsequent software installations. Refer to Chapter 4 for | instructions. | | Old LPS$STARTUP.COM files are not compatible with DECprint | Printing Services Version 4.0. | | 2 Enter PrintServer node name in startup file. | | In CPS$STARTUP.COM, parameter P2 (/ON device name) in | CPS$EXECUTION_QUEUE.COM must be the PrintServer node name. | (Refer to Chapter 4 for instructions.) | | 1.3.2 Upgrading ScriptPrinter and LN03 Image Software | | ScriptPrinterently using ScriptPrinter printers and LN03 Image | andpLN03ers are running ScriptPrinter Version 2.1 software. For | Imageese sites, you only need to run VMSINSTAL to upgrade from | printers current software to DECprint Printing Services Version | | 4.0. The ScriptPrinter Version 2.1 startup command file is | compatible with DECprint Printing Services software. | | The CPS$STARTUP.COM from ScriptPrinter Version 2.1 software | does not require modification, unless printers or queues are | being changed. The new software introduces no significant | new installation or startup considerations for existing | ScriptPrinter sites. 1-8 Overview 2 ________________________________________________________________ Preinstallation Requirements This chapter describes the hardware environment and software requirements for installing DECprint Printing Services on the host system, as follows: _ Hardware requirements, Section 2.1 _ Specific hardware requirements for ScriptPrinter and DEClaser printers, Section 2.1.1 _ Specific hardware requirements for PrintServer printer software installation, Section 2.1.2 _ Specific hardware requirements for LN03 Image printing, Section 2.1.3 _ Software prerequisites for installing DECprint Printing Services, Section 2.2 2.1 Hardware Requirements The following hardware requirements are common to sites using DECprint Printing Services to drive Digital's PostScript printers: _ The appropriate input device to hold the distribution media. The DECprint Printing Services software is distributed in the following forms of media: _ 1600 BPI magnetic tape | _ TK50 COMPACTape cartridge | | _ CDROM (Compact Disc) Preinstallation Requirements 2-1 _ Appropriate communications hardware for the printer configuration (as described in this chapter). _ Adequate disk space for installation and for operation of the DECprint Printing Services software. In addition, each type of printing device supported by DECprint Printing Services requires special hardware, as | described in the following sections. | | 2.1.1 DEClaser 2150/2250 and ScriptPrinter Hardware | Requirements | | DEClaserEClaser and ScriptPrinter printers are serial printers, | andwhich are connected to the host system either by a DECserver | ScriptPrintery direct serial line interface, using one of the | onlyollowing: | | _ DHV11 (Q-bus) | | _ DZV11 (Q-bus) | | _ DLV11 (Q-bus) | | _ DHU11 | | _ DMZ32 (UNIBUS) | | The DMZ32 interface, revision E and lower, requires that | the transmit and receive speed for printers be no more | than 4800 baud. | | _ DMF32 (UNIBUS) | | _ DMB32 (VAXBI) | | _ CVAX serial line interface (CXA16, CXB16, CXY08, DZQ11) | | CSA0 (printer port 0 on VAXstation II and VAXstation | II/GPX systems) is not a supported interface for serial | printers. | | For DEClaser printers, this interface requires an H8571-A | adapter (refer to the DEClaser 2200 Printer Installation | Guide). | | _ VS2000 serial line interface | | _ DECserver interface | | DECserver configuration for serial printers is described | in Section 4.7. | 2-2 Preinstallation Requirements | 2.1.2 PrintServer Hardware Requirements | | PrintServerou can run DECprint Printing Services software on the | onlylient system to print files on a PrintServer printer; the | | PrintServer printer must be installed on the Ethernet. 2.1.3 LN03 Image Printer Hardware Requirements LN03hImage3 Image printer requires one of the following Q-bus onlynterfaces: _ LNV21-AA dual-sized controller for BA123/BA23 enclosures (BC27H-15 cable) _ LNV21-SA or LNV21-SF quad-sized controller for BA213 enclosure (BC27P-15 cable) 2.2 Software Requirements | To install DECprint Printing Services software, the host | system must be running VMS Version 5.3 and higher. | | Serial serial printers on DECserver devices, ensure that the | printersrver software is installed and running before you start | on the printer queues. | DECserversntServer printers, ensure that the PrintServer | PrintServer | Supporting Host Version 3.0 and higher is installed and | running on at least one node in the network. The PrintServer | node should be included in the DECnet node database for the | client system before you start the printer queue. DECnet-VAX | software (Versions 5.3 and higher) must be running on the | client system. | | LN03oImage LN03 Image printer, set system parameters as | described in Section 4.4, and install LN03 Image support | software and image services software kits before you start | the printer queue. 2.3 DECprint Printing Services Software Distribution Kit Check the contents of the DECprint Printing Services Software Distribution Kit against the bill of materials. You should have the following items in the distribution kit: _ Software labeled VMS DECprint Printing Services software, Version 4.0. _ Digital ANSI-Compliant Printing Protocol Level 3 Programming Reference Manual Preinstallation Requirements 2-3 _ Digital ANSI-Compliant Printing Protocol Level 3 Programming Supplement _ DECprint Printing Services System Manager's Guide _ DECprint Printing Services User's Guide 2-4 Preinstallation Requirements 3 ________________________________________________________________ Installing the Software This chapter describes how to install DECprint Printing Services software on a VAX-based VMS system, using the VMSINSTAL utility. If you are not familiar with the VMSINSTAL utility, read the Guide to VAX/VMS Software Installation. The procedures described in this chapter include: _ Running VMSINSTAL for DECprint Printing Services, Section 3.2 _ Procedures for starting the new printer software, Section 3.3 _ Procedures for upgrading DECprint Printing Services software, Section 3.4 _ Testing the DECprint Printing Services software, printer, and queues, Section 3.5 Perform the following steps before you begin the installation procedure: 1 Read through the installation procedures, preparing the information you must supply as you install the software and define the printer queues. 2 If you have a previous version of ScriptPrinter software and you have modified CPS$DEVCTL.TLB, extract any site-specific device control library modules from CPS$DEVCTL.TLB and copy them to a directory that is unaffected by the installation procedure. You should create your own device control libraries for custom device control modules. The installation procedure replaces the device control library CPS$DEVCTL.TLB. (Refer to Section 5.3.3.2 for more information.) Installing the Software 3-1 3 Make a backup copy of the software distribution media. 4 Mount the distribution media on an appropriate input | device. | | 5 Check that you have enough disk space: | | _ For installation (with ALL-IN-1) 6500 blocks (3.3 M | | bytes) | | Without ALL-IN-1, 4500 blocks (2.3 M bytes) | | _ For permanent storage (without ALL-IN-1) 3000 blocks | | (1.5 M bytes) | | With ALL-IN-1 compatibility kit: 5000 blocks (2.5 M | bytes) 6 Log in to the system manager's account. 3.1 VMSINSTAL Conventions The VMSINSTAL procedure is interactive. The system prompts you for information, and responds with instructions, statements, queries, and messages. Instructions guide you through the procedure or provide you with information relevant to subsequent queries. Messages inform you of the status and progress of the installation procedure. Queries are preceded by an asterisk (*) and may be followed by default responses enclosed in brackets ([]). Enter your response, followed by . Press to enter the default response. If you are not sure of the response, enter a question mark (?). VMSINSTAL displays explanatory text and repeats the prompt. VMSINSTAL messages are documented in the Guide to VAX/VMS Software Installation. Messages specific to the installation of DECprint Printing Services software are found in Chapter 6. The DECprint Printing Services Release Notes are included on the software distribution media. 3-2 Installing the Software 3.2 Installation Procedure Note This section does not reproduce all text you will see on your screen during the installation procedure. A sample VMSINSTAL procedure is shown in Appendix A. Invoke the VMSINSTAL procedure as follows: $ @SYS$UPDATE:VMSINSTAL CPS040 device-id [OPTIONS N] In this command line, you supply the following information: CPS040 refers to the DECprint Printing Services software saveset. device-id is the device on which the distribution media is mounted. This may be a tape or disk device. [OPTIONS N] invokes the release notes option, allowing you to display or save a copy of the release notes. This portion of the command line is optional. If you omit this option, the Release Notes question (Section 3.2.1) is omitted from the VMSINSTAL dialog and the release notes are automatically copied to SYS$HELP. Next, VMSINSTAL displays a banner line, the date and time, the statement that you can enter a question mark (?) at any time for help, and one or more warning messages if appropriate. You can continue the installation or exit to modify the conditions causing the warning messages. If you are not currently logged in to the SYSTEM account, the following message is displayed: VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. If DECnet software is running, the following message is displayed: %VMSINSTAL-W-DECNET, Your DECnet network is up and running. If processes are running on the system while VMSINSTAL is running, the following type of message is displayed: %VMSINSTAL-W-ACTIVE, The following processes are still active: process-name Installing the Software 3-3 When any of these messages are displayed, the following query allows you to terminate VMSINSTAL and correct the situation if necessary: * Do you want to continue anyway [NO]? Enter YES to continue. DECnet software does not have to be running during the software installation procedures. If you answer NO, the VMSINSTAL procedure is terminated immediately. If you enter a question mark (?), the following explanation is displayed: The above conditions may cause VMSINSTAL to function improperly. In particular, problems may occur with file ownership if you are not logged into the SYSTEM account. You are then asked: * Are you satisfied with the backup of your system disk [YES]? Enter YES to continue or NO to exit VMSINSTAL to make a backup and run VMSINSTAL again. If you enter a question mark (?) in response to this question, VMSINSTAL displays the following explanation: VMSINSTAL attempts to ensure that a power failure or system crash will not corrupt your system disk. However, for absolute safety we recommend that you back it up before installing new products. Please see the documentation for more information on crashes during installation. If the distribution medium is mountable, VMSINSTAL then asks for confirmation that the distribution media has been mounted. Please mount the first volume of the set on device-id: * Are you ready? Enter YES when ready. VMSINSTAL displays the name and version of the product being installed, the start time of the installation, and confirmation of the restoration of each saveset on the distribution media. 3-4 Installing the Software The following products will be processed: CPS V4.0 Beginning installation of CPS V4.0 at 13:45 %VMSINSTAL-I-RESTORE, Restoring product saveset A 3.2.1 Choosing Release Notes Options If you specified OPTIONS N in the VMSINSTAL command line, the following release notes options are displayed: Release Notes Options: (1) Display release notes (2) Print release notes (3) Both 1 and 2 (4) Copy release notes to SYS$HELP (5) Do not display, print or copy release notes If you select 1, the release notes are displayed on your terminal and are copied to CPS040.RELEASE_NOTES in SYS$HELP. If you select 2, the release notes are queued to SYS$PRINT for printing, and copied to CPS040.RELEASE_NOTES in SYS$HELP. If you select 3, the release notes are displayed on your terminal, queued to SYS$PRINT, and copied to CPS040.RELEASE_ NOTES in SYS$HELP. If you select 4, the release notes are copied to CPS040.RELEASE_ NOTES in SYS$HELP. If you select 5, the release notes are not printed, displayed, or copied to SYS$HELP. If you did not include the OPTIONS N portion of the VMSINSTAL command line, the following message is displayed: %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP 3.2.2 Purging Files VMSINSTAL asks if you want to purge any files that are being replaced. * Do you want to purge files replaced by this installation [YES]? Enter YES if you want to save disk space or NO if you think the files may still be of use. Installing the Software 3-5 If you enter a question mark (?) in response to this query, the following message is displayed: During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. VMSINSTAL checks to see if the amount of disk space required for the installation is available. If the space is not available, a message indicates the amount of disk space that is required, and the installation is aborted. Otherwise, the installation continues. 3.2.3 Selecting a Logical Definition for LPS$LAYUP Next, the installation procedure looks for a logical definition of LPS$LAYUP in the system table in executive mode. If a definition exists, the following message is displayed: %CPS-I-LAYUPDEF, LPS$LayUp is already defined -CPS-I-LAYUPDEF, This installation will use its value If an LPS$LAYUP definition does not exist, the proce- dure asks you to specify one. Press to select SYS$SYSROOT:[SYSHLP.EXAMPLES.CPS] as the default, or type a disk directory specification. * Full definition for LPS$LayUp [SYS$SYSROOT:[SYSHLP.EXAMPLES.CPS]]: % VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.CPS] | 3.2.4 Selecting ALL-IN-1 Compatibility Kit | | In this question, the VMSINSTAL procedure allows you to | install the ALL-IN-ONE compatibility kit at a later. The | ALL-IN-ONE compatibility kit allows you to print files from | ALL-IN-1 software. | | If you want this option, the following files are optionally | copied to [SYSHLP.EXAMPLES.CPS]: | | _ PS-PRINTING-ALL-IN-1-COMPAT.SAV, which contains the | | software saveset, including a PostScript file with | instructions for installing the saveset. 3-6 Installing the Software | _ PS-PRINTING-ALL-IN-1-COMPAT.TXT, an ASCII text file with | | instructions for installing the ALL-IN-1 compatibility | kit. | | * Do you want to install the ALL-IN-1 Compatibility | Kit? [Y]? | | Enter YES if you want the optional ALL-IN-1 compatibility | kit. If you enter NO, the DECprint Printing Services software | will not include this function. If you enter a question mark | (?) in response to this query, the following explanation is | displayed: | | 1900 blocks, provides scripts for PostScript printing | 3.2.5 Installation Verification Procedure Check VMSINSTAL checks to see if the queue manager is running on your system. If the queue manager is not present, the Installation Verification Procedure (IVP) is not run, and the following messages are displayed on your screen: %CPS-I-NOQUEMGR, System queue manager is not running -CPS-I-NOQUEMGR, IVP will NOT run. Installation continuing ... The queue manager must be running if you want the instal- lation to run an Installation Verification Procedure (IVP). (Refer to Section 3.2.8.) If necessary, VMSINSTAL creates a disk directory for the IVP files: %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CPS]. If the directory already exists, the following message is also displayed: %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.CPS] already exists VMSINSTAL also creates a disk directory for the example files: %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.CPS] Installing the Software 3-7 If the directory already exists, the following message is displayed: %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.CPS] already exists Then VMSINSTAL displays the following message on your screen: %CPS-I-NOQUES, No further questions will be asked. As it restores each saveset, VMSINSTAL reports on its progress: VMSINSTAL-I-RESTORE, Restoring product saveset B ... VMSINSTAL-I-RESTORE, Restoring product saveset C ... This operation may require up to 20 minutes to complete. 3.2.6 Translator Installation Check At this point, VMSINSTAL installs the translators. Before installing a translator, VMSINSTAL checks the image identification of the translator on the system and in the kit. VMSINSTAL installs the translator from the kit unless its version number is lower than the version number of the translator already installed. In this case, the procedure issues an informational message such as this %CPS-I-TRNNOTREP, The ReGIS translator in the kit is already installed The VMSINSTAL message specifies the translator name, in this case, ReGIS. 3.2.7 Completing the Installation Procedure VMSINSTAL then displays a message on your screen reminding you to perform the following procedures: Please remember to copy SYS$StartUp:CPS$StartUp.Template to SYS$StartUp.Com. Then edit this file following the instructions to create your queues. Finally execute this file to establish and start the queues. Also remember to edit SYS$Manager:SyStartUp_V5.Com to establish your queues at system startup time. If you use LAT devices, this file should be executed after the LAT devices are created. If you use PrintServers, this file should be executed after DECnet is running. If you use both types of printers, both of the above conditions should be satisfied before the startup file is executed. These procedures are described in Chapter 4 and Chapter 5. 3-8 Installing the Software VMSINSTAL now moves files from the temporary locations used during installation to their permanent directories. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 3.2.8 Installation Verification Procedure The IVP verifies that the installation procedure was successful. The installation verification procedure (IVP) runs automatically and queues the test files in [SYSTEST.CPS] to the temporary print queue CPS$IVP_TEST. Note The IVP test files are not automatically printed. The IVP creates a temporary print queue (CPS$IVP_TEST) and creates print jobs in the temporary queue. The print jobs are processed, but no paper is produced. When the IVP creates print jobs on the temporary queue, the | following messages are displayed: | | %CPS-I-IVP. Beginning IVP... | JOB CPS$IVP_POST (queue CPS$IVP_TEST, entry 61) started on CPS$IVP_TEST | JOB CPS$IVP_ANSI (queue CPS$IVP_TEST, entry 62) started on CPS$IVP_TEST | JOB CPS$IVP_REGIS (queue CPS$IVP_TEST, entry 63) started on CPS$IVP_TEST | JOB CPS$IVP_TEK4014 (queue CPS$IVP_TEST, entry 64) started on CPS$IVP_TEST | JOB CPS$IVP_PCL (queue CPS$IVP_TEST, entry 64) started on CPS$IVP_TEST | The test procedure automatically deletes the temporary queue after the IVP runs. You can print the IVP files later (refer to Section 3.5). VMSINSTAL issues an informational message when the IVP is completed: IVP successful for VMS DECprint Printing Services Software V4.0 VMSINSTAL issues its final messages: Installation of CPS V4.0 completed at 14:04 VMSINSTAL procedure done at 14:08 $ When VMSINSTAL is complete, follow the instructions in the VMSINSTAL dialog. The final steps of the installation | procedure are described in Chapter 4. | Installing the Software 3-9 | 3.3 Starting the DECprint Printing Services Printing System | | To start a printer and print files, perform the following | steps after you run VMSINSTAL. | | 1 Prepare the printer and printer software, as described in | the section appropriate to the printer being installed: | | _ ScriptPrinter printer: Section 4.1 | | _ DEClaser printer: Section 4.2 | | _ PrintServer printer: Section 4.3 | | _ LN03 Image printer printer: Section 4.4 | | _ ScriptPrinter or DEClaser printer with a DECserver | | connection: Section 4.7 | | 2 Create the CPS$STARTUP.COM file from the distributed | CPS$STARTUP.TEMPLATE file (see Chapter 5.) This step | is not necessary if you have ScriptPrinter Version 2.1 | software. | | 3 Edit the system startup file SYS$MANAGER:SYSTARTUP_V5.COM | to include a call to CPS$STARTUP.COM, if the system | startup file does not already include this call. Look | for the following command: | | $ @SYS$STARTUP:CPS$STARTUP | | If this command is not included in the system startup | file, add it. | | Note that an existing PrintServer site may have a system | startup file with the following command: | | $ @SYS_STARTUP:LPS$STARTUP | | For PrintServer sites, delete this command and insert the | correct call to CPS$STARTUP, as shown above. | | This change to the system startup file is not necessary if | you have ScriptPrinter Version 2.1 software. | | 4 After exiting from the editor, invoke the printer startup | command file with the following command: | | $ @SYS$STARTUP:CPS$STARTUP | 3-10 Installing the Software 3.4 Upgrading Printer Software If you have an existing PostScript printer and DECprint Printing Services software, you can add and delete printers from your system, or add and delete execution or generic queues, without running VMSINSTAL. To upgrade your printer software, follow these steps: 1 Stop the queues you want to change, using the following command: $ STOP/QUEUE/NEXT queue-name[:] 2 Make any changes needed to SYS$STARTUP:CPS$STARTUP.COM, adding and deleting the definitions for the desired execution and generic queues (see Chapter 5). 3 If you are deleting a queue, check to see that no jobs are waiting in the queue to be printed. Use the following commands to check the queue and to delete the queue: $ SHOW/QUEUE/ALL queue-name[:] $ DELETE/QUEUE queue-name[:] 4 Before starting DECprint Printing Services software, you should power cycle (turn off and on) any serial printers. This clears resources and allows the reloading of new prologues. 5 Invoke the startup command file with the following command: $ @SYS$STARTUP:CPS$STARTUP The startup procedure then initializes and starts your queues. 3.5 Testing the Printers and Queues After the installation is complete, you can test the printers. Print the following installation verification procedure (IVP) files from SYS$COMMON:[SYSTEST.CPS]: _ CPS$IVP_ANSI.DAT _ CPS$IVP_POST.DAT _ CPS$IVP_REGIS.DAT | _ CPS$IVP_TEK4014.DAT Installing the Software 3-11 | _ CPS$IVP_PCL.DAT | | Remember to use the appropriate /DATA_TYPE parameter, | indicated in the filename following the underscore, for each | of the files. For example to print CPS$IVP_REGIS.DAT, use the | following PRINT command: | | $ PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=REGIS)- | /NOTIFY SYS$COMMON:[SYSTEST.CPS]CPS$IVP_REGIS.DAT | | Sample output is shown in Appendix C. 3-12 Installing the Software | | | | | | 4 | ________________________________________________________________ | | PostInstallation Procedures | | | | | This chapter describes printer-related operations to be | performed after the DECprint Printing Services software is | installed. These operations are required for sites that are | installing the Common Print Symbiont (CPS) for the first | time, and for installing new printers to be supported by | DECprint Printing Services. | | This chapter discusses the following procedures: | | _ Setting serial printer communication speeds, Section 4.1 | | _ Setting up the DEClaser 2150/2250 printers, Section 4.2 | | _ Setting up the PrintServer printer environment, Section 4.3 | | _ Setting up the system parameters for LN03 Image printers, | | Section 4.4 | | _ Setting the printer name, Section 4.5. | | _ Setting serial printer timeout value, Section 4.6 | | _ Configuring serial printers for network access, Section 4.7 | | 4.1 Installing Serial Printers | | Serialial printers require you to set up the communication | printers and timeout values for the printer device. (Hardware | | requirements for installing serial printers are described in | Section 2.1.1.) | | PostInstallation Procedures 4-1 | 4.1.1 Changing the ScriptPrinter Communication Speed | | ScriptPrintergs of the two switchpacks, SP1 (left) and | SP2 (right), on the back of the printer, determine the | communication mode. Table 4-1 lists the expected settings | for the software installation of the ScriptPrinter. | | Table 4-1 Communication Switch Default Settings | | _____________________________________________________________ | Switch_Setting__________Switch_Setting_______________________ | | SP1-1 Off SP2-1 Off | | SP1-2 On SP2-2 Off | | SP1-3 Off SP2-3 Off | | SP1-4 On SP2-4 Off | | SP1-5 Off SP2-5 Off | | SP1-6__Off______________SP2-6__Off___________________________ | | These settings correspond to 9600 baud, XON/OFF flow control | enabled, 8 bits, and no parity. | | Press the top of the switch for On and the bottom of | the switch for Off. Refer to the LN03R ScriptPrinter | Operator's Guide for additional information about setting | the communication DIP switches. | | Once the ScriptPrinter printer is installed, you can | determine its communication setting by pressing the self-test | button on the back of the printer and reading the power-up | summary sheet. | | 4.1.2 Baud Rate Limitations | | Serialn choosing a baud rate other than the default of 9600 | printers consider the following limitations: | | _ VMS drivers do not support baud rates of 3600 and 7200 | | baud. | | _ DMZ32 serial interfaces, Revision E and lower, require a | | speed of 4800 baud or less. 4-2 PostInstallation Procedures | _ Each DECserver device runs at an optimal speed for | | printers. The DECserver devices that can be used | with DECprint Printing Services and the recommended | communications speed for each are listed in the Software | Product Description (SPD). | | If you selected an improper speed, the printer will not | operate. | | Power-cyle (turn off and then turn on) the printer to enable | the new communications settings. | | 4.1.3 Changing the Default Settings | | Serialrun a serial printer at a different communication speed | printersthe default rate of 9600 baud, proceed as follows: | | 1 Stop the execution queue that drives the printer. | | $ STOP/QUEUE/NEXT execution-queue-name | | 2 Turn off the power to the printer. | | ScriptPrinter printer to the appropriate baud rate. For a | ScriptPrinter printer, the communication DIP switches are | located on the back of the printer unit to the appropriate | baud rate. Refer to the ScriptPrinter Operator's Guide for | information about setting the communication DIP switches | for your printer. | | DEClasert the communications settings for the DEClaser 2150/2250 | printers through the printer front panel. Menu INTERFACE: | baud allows you to check and change the baud rate for | these printers. Refer to the DEClaser 2100 Printer | Operator's Guide or the DEClaser 2200 Printer Operator's | Guide for instructions. | | ScriptPrintere execution queue definition for the printer con- | figured in the printer startup file SYS$STARTUP:CPS$STARTUP.COM. | Parameter p6 is reserved for communication speed (not | required for printers on DECserver devices). When | multiple hosts access the printer, be sure to make these | adjustments on each host system. | | ScriptPrinter power to the printer. Wait for the printer to | eject the power-up test page and then check the test page | to ensure that the desired settings are reflected on the | test page. PostInstallation Procedures 4-3 | SerialInvoke CPS$STARTUP by issuing the following DCL command: | printers | $ @SYS$STARTUP:CPS$STARTUP | | 4.2 Requirements for Installing DEClaser Printers | | You must change the factory default settings on the front | panel of the DEClaser 2150/2250 printer, so that it will work | with the DECprint Printing Services software. This section | summarizes the front panel settings. Refer to the DEClaser | 2100 Printer Operator's Guide or the DEClaser 2200 Printer | Operator's Guide. for help on operating the front panel and | checking the PostScript cartridges. | | Caution You must turn the printer off before installing or | removing the PostScript cartridges. Failure to observe this | can destroy the cartridges. | | 1 Make sure the PostScript cartridges are installed in your | printer and the cartridges are installed in their correct | slot. | | 2 For the SETUP: Interface menu, make sure the following | features are set to the values listed below: | | _ I/F: Serial comm is selected | | _ The correct baud rate is selected | | _ Parity is set to no | | _ Flow Control is set to xon/xoff | | _ Data bits is set to eight | | _ Stop bits is set to one | | 3 For the MISCELLANEOUS menu, make sure TIMEOUT=INF. | 4.3 Requirements for Installing PrintServer Printers PrintServertServer 20, PrintServer 40, and PrintServer 40 Plus printers are network printers, requiring the VMS DECnet software to be running on the VMS systems on which the DECprint Printing Services software is running. (Hardware required for installing the PrintServer printer is described in Section 2.1.2.) 4-4 PostInstallation Procedures 4.3.1 Installing a PrintServer Client System The following procedures allow the DECprint Printing Services software to access PrintServer printers. 4.3.1.1 Including the PrintServer Node Name in CPS$STARTUP In the procedure for editing CPS$STARTUP, include the printer node name in the execution queue definition, as described in Section 5.3.2. For printers in a VAXcluster, be sure to include the SCS node name of the system on which you are installing DECprint Printing Services. The Network Control Program (NCP) database for DECnet should have an entry for each PrintServer printer accessible from the system. 4.3.1.2 Defining the PrintServer Network Nodes The system manager can provide you with a registered DECnet node name and node address. Run the NCP program and add the printer node to the network database. Use the following commands to define a PrintServer network node: $ MCR NCP NCP> SET NODE node-name ADDRESS node-address NCP> DEFINE NODE node-name ADDRESS node-address NCP> EXIT $ | In the NCP commands, you supply the following variables: | | node-name Printer node name | | node- Printer node address | address | | For example, type the following commands to add the printer | ABLE (DECnet address 5.85) to the network database: | | $ MCR NCP | NCP> SET NODE ABLE ADDRESS 5.85 | NCP> DEFINE NODE ABLE ADDRESS 5.85 | NCP> EXIT | $ | PostInstallation Procedures 4-5 4.3.1.3 Deleting the PrintServer Startup File The existing LPS$STARTUP.COM file is no longer used and is not compatible with DECprint Printing Services. Delete this file after you edit CPS$STARTUP.COM. To delete this file, follow these procedures: 1 Delete existing PrintServer printer queues. 2 Add new print queues to CPS$STARTUP.COM for PrintServer printers. 3 Edit SYS$MANAGER:SYSTARTUP_V5.COM, removing the reference to SYS$MANAGER:LPS$STARTUP.COM. 4 If you have any customized definitions in the LPS$STARTUP.COM file, copy them to SYS$STARTUP:CPS$STARTUP.COM. 5 Delete LPS$STARTUP.COM. (This function can be performed by calling the example command file CPS$NUKE.COM.) 4.4 Installing the LN03 Image Printer | LN03oImageall the LN03 Image printer, you must install the | Printer Image Support software and LN03 Image Services software | | before you start the DECprint Printing Services print queues. | (The hardware required for installing and running an LN03 | Image printer is described in Section 2.1.3.) | | You must also adjust system parameters before running | DECprint Printing Services to support LN03 Image printers, as | described in this section. The LN03 Image printer requires that the following SYSGEN parameters be set to at least the minimum values listed in Table 4-2. Table 4-2 LN03 Image Printer SYSGEN Values _____________________________________________________________ SYSGEN Parameter________Minimum_Value_______________________________ PROCSECTCNT 64 WSMAX 10000 VIRTUALPAGECNT 25000 (continued on next page) 4-6 PostInstallation Procedures Table 4-2 (Cont.) LN03 Image Printer SYSGEN Values _____________________________________________________________ SYSGEN Parameter________Minimum_Value_______________________________ NPAGEDYN 500000 NPAGEVIR_________2000000_____________________________________ To check the values, enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW parameter Supply a parameter name for parameter. If you need to change a SYSGEN value, Digital suggests that you modify SYS$SPECIFIC:[SYSEXE]MODPARAMS.DAT and then use the AUTOGEN command procedure to change the values. For example, to change the WSMAX parameter, perform the following steps: 1 Edit SYS$SPECIFIC:[SYSEXE]MODPARAMS.DAT and add the following: MIN_WSMAX=10000 2 Issue the following AUTOGEN commands to install the new WSMAX parameter on the system when you reboot the system: $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT Refer to the Guide to VAX/VMS Software Installation for more information on the AUTOGEN command procedure. 4.5 Setting the Printer Name Serialsome cases, messages reference a printer name. You can printersde your printer with a unique name. For PrintServer printers, the printer name is set through the server management software (refer to the Management Guide: VAX PrintServer Supporting Host for instructions). For serial printers, the printer name is stored in non- volatile memory, to be inserted into these error messages. PostInstallation Procedures 4-7 To set the printer name, edit a copy of the file LPS$SET_ PRINTER_NAME.PS found in SYS$MANAGER to include the desired name and password. (The default password for ScriptPrinter printers is "LN03R". For DEClaser printers, the default password is "0".) Select a printer name of 31 characters or less. Then submit the file for printing as a PostScript job: $ PRINT/QUEUE=queue-name- /PARAMETER=(DATA_TYPE=POSTSCRIPT) LPS$SET_PRINTER_NAME.PS Without the printer name set, a message contains the default printer name printer-name in the following message: %CPS-I-TRAYSUBST, Output will be delivered to the only tray on printer-name With the printer name set, the message contains the name you selected for your printer, "David's printer" for example, and reads: %CPS-I-TRAYSUBST, Output will be delivered to the only tray on David's printer Edit and submit a copy of LPS$SET_PRINTER_NAME.PS for each printer requiring a unique name. 4.6 Setting the Printer Timeout Using PostScript Operators PrintServertServer printers, the timeout value is set in supporting host management software (refer to Management Guide: VAX PrintServer Supporting Host). DEClaserEClaser printers, the timeout value is set by the front panel controls, documented in the DEClaser 2100 Printer Operator's Guide or the DEClaser 2200 Printer Operator's Guide. Serial printer aborts a print job if it does not receive data printers period of 40 seconds. This value may be changed with the settimeouts PostScript operator. A file has been provided in the installation kit and is left in SYS$MANAGER:, which can be used to change the timeout value to zero (0), which means no timeout. The file name is LPS$SET_TIMEOUT.PS. Note Digital recommends that you change the timeout value to zero for printing on the ScriptPrinter. 4-8 PostInstallation Procedures In order to change the timeout (including setting it back to the original value) you must specify the printer password and exit the server loop of the printer. The default password is the string "LN03R" for ScriptPrinter or "0" for DEClaser printers and is specified in LPS$SET_TIMEOUT.PS. serverdict begin (LN03R) exitserver Include the correct password for your printer. Then submit the file for printing as a PostScript job: $ PRINT/QUEUE=queue-name- /PARAMETER=(DATA_TYPE=POSTSCRIPT) LPS$SET_TIMEOUT.PS A page is printed to indicate that the timeout was success- fully changed. It may be necessary to change the timeout if the ANSI translator takes more than 40 seconds to load one LN03 font. In this case, the printer aborts the job in progress. Setting the timeout to zero (0) gives an infinite timeout value. Note Changing the password may require an additional 30 seconds to load each ANSI print file. | | 4.7 Making DECserver Connections for Serial Printers | | Serial information in Section 4.7.1 through Section 4.7.4 | printerses to the ScriptPrinter and the DEClaser 2150 and | | 2250 printers. They do not apply to the LN03 Image printer, | the PrintServer 20, PrintServer 40, or PrintServer 40 Plus | printers. | | Multiple systems on the same Ethernet can access the serial | printer if the following prerequisites are met: | | _ The printer is connected to a DECserver. | | _ Every host system using the printer is running DECprint | | Printing Services software. Failure can occur if the | printers are accessed by any means other than through | DECprint Printing Services software. | | _ The SHOW QUEUE command does not display the queues for | | network printers. | | _ The system does not provide print job scheduling or load- | | balancing among printers. PostInstallation Procedures 4-9 | _ The system does not provide a centralized queue. | | Implementation of shared printer access has the following | implications: | | _ There is no centralized accounting for the printer. Each | | system maintains separate accounting information for the | printing performed by that system. | | _ Multiple systems running DECprint Printing Services | | software contend for the same printer. | | _ There is no centralized print queue for the printer. | | 4.7.1 DECserver Connections | | The serial PostScript printers are made network-accessible | through a DECserver connection to the Ethernet. For this | configuration, you must make the following changes to the | system startup procedure: | | _ Set the necessary DECserver port and server characteris- | | tics for the printer. | | Note DECprint Printing Services supplies an example command | file for this purpose. This command file sets the | characteristics for a DECserver with the Terminal Server | Manager (TSM) software, and records data in the TSM | database. (TSM is a software product available from | Digital.) | | The command file is: | | SYS$COMMON:[SYSHLP.EXAMPLES.CPS]CPS$CONFIG-PRINTER-PORT.COM | | This command file provides examples of characteristics for | DECserver 100, DECserver 200, and DECserver 500 devices. | | _ Make the necessary changes to SYS$MANAGER:STARTLAT.COM. | | This file is used by LTLOAD.COM, the command procedure | that starts the local area transport (LAT) protocol and | configures applications devices for remote printers. | 4-10 PostInstallation Procedures 4.7.2 DECserver Port Characteristics Table 4-3 lists the DECserver port characteristics required for dedicated printing. Table 4-3 Printer-Required DECserver Port Characteristics _____________________________________________________________ Characteristic_____________DECserver_Port____________________ ACCESS REMOTE AUTOBAUD DISABLED AUTOCONNECT DISABLED AUTOPROMPT DISABLED BREAK DISABLED BROADCAST DISABLED FLOW CONTROL XON INPUT FLOW CONTROL[1] ENABLED OUTPUT FLOW CONTROL[1] ENABLED INACTIVITY LOGOUT DISABLED LOSS NOTIFICATION DISABLED MESSAGE CODES DISABLED QUEUING ENABLED VERIFICATION DISABLED _____________________________________________________________ [1]Characteristic not supported by the DECserver 500. _____________________________________________________________ Note On many versions of DECserver devices, QUEUING is not a port characteristic, but is a server characteristic whose default is ENABLED. PostInstallation Procedures 4-11 In addition, check that the following DECserver port characteristics match the DIP switch settings on the back of your printer. Table 4-4 DECserver Port Characteristics _____________________________________________________________ Character 8 size Parity None Input speed 9600 Output_speed__9600___________________________________________ | Check the following DECserver server characteristics | | | Table 4-5 DECserver Server Characteristics | | _____________________________________________________________ | Queue limits 0 | | Service Refer to Section 4.7.4 | groups_______________________________________________________ | To change DECserver terminal server and port characteristics, you need privileged status. Once you have privileged status, use the DEFINE PORT and SET PORT commands. The DEFINE command changes the port's characteristics in the server's permanent database. These changes do not take effect until the next login for the port. SET commands take effect immediately, but only alter the port's characteristics for the current session. For example, to change the INPUT SPEED and OUTPUT SPEED values on PORT_6 to 19200 baud (on a DECserver 200), issue | the following commands from the console server manager: | | LOCAL> SET PRIVILEGED | PASSWORD> password | | LOCAL> SET PORT 6 SPEED 19200 | LOCAL> DEFINE PORT 6 SPEED 19200 | 4-12 PostInstallation Procedures _ For a detailed description of DECserver 100 commands and how to change them, refer to the DECserver 100 Terminal Server Operator's Guide. _ For DECserver 200 terminal server commands, refer to the DECserver 200 Management Guide. _ For DECserver 500 terminal server commands, refer the DECserver 500 Management Guide for additional required DEFINE commands. 4.7.3 Editing the LAT Protocol Startup and Configuration File | | The SYS$MANAGER:STARTLAT.COM file defines host node service | characteristics. Before you start the print queues, make sure | the LAT driver is running and ports are available. Note Commands referenced in this section are LATCP commands. For more information on LATCP commands, refer to the VMS LAT Control Program (LATCP) Manual. Edit STARTLAT.COM and add the following command to create an applications port on the host node (service node) that will support your printer: CREATE PORT LTAd:/NOLOG/APPLICATION In this command format, you supply the number of the applications port for d, which must be a unique number from 1 | to 9999. | | Note The DECserver device may be dedicated to the printer or | may be shared with terminal lines. In the latter case, | it is prudent to assign a very high port number to the | printer. Since the terminal connections on the DECserver | are established dynamically among the lowest available ports, | the assignment of a higher port number for the printer can | help secure the port for the printer and prevent interference | from terminal line connections. In STARTLAT.COM, add the following command to associate the applications port with a remote port on a server: SET PORT LTAd:/NODE=server_name/PORT=port_n_name/QUEUE/APPLICATION PostInstallation Procedures 4-13 In the command format, you supply the following values: LTAd: is the name of the applications port. server_ is the name assigned to the DECserver device. name port_n_ is the DECserver port name. name The following example associates applications port LTA9000: with the port named PORT_7 on a remote DECserver 200 named LN03RDS: SET PORT LTA9000:/NODE=LN03RDS/PORT=PORT_7/QUEUE/APPLICATION | As an alternative, you can define the LAT connection for | the printer in the CPS$STARTUP.COM file. You may prefer | this method of definition if the DECserver is dedicated to | printing services, since doing so makes it easier to solve | problems with this configuration. However, if the DECserver | supports terminals as well as the printer, you may prefer to | define the port in the LAT startup file. 4.7.4 LAT Groups | | To make a successful LAT connection, the following must have | at least one LAT group in common: _ On the DECserver: Port authorized groups current groups _ On the service node: enabled groups If you did not set up these groups correctly, you receive the following error message when a print job is submitted: %CPS-E-LRJACCESSDENIED, Access denied You can use LATCP commands to include the necessary LAT group designations. For additional information refer to the VMS LAT Control Program (LATCP) Manual. 4-14 PostInstallation Procedures 5 ________________________________________________________________ Initializing Print Queues This chapter describes the procedures for creating, starting, and modifying print queues. The following operations are discussed in this chapter: _ Types of print queues, Section 5.1 _ Starting the queue manager, Section 5.2 _ Creating CPS$STARTUP.COM, Section 5.3 _ Setting up execution queues, Section 5.4 _ Setting up generic queues, Section 5.5 _ Changing default queue parameters, Section 5.6 _ Changing default queue qualifiers, Section 5.7 _ Note The information in this chapter is necessary for completing the installation of the DECprint Printing Services software and for managing the resulting printing system. Therefore, the chapter is included in both the DECprint Printing Services Software Installation Guide and the DECprint Printing Services System Manager's Guide. 5.1 Types of Printer Queues A printer queue can be either an execution queue or a generic queue. Execution queues schedule jobs for processing by the symbiont and deliver the print files to an output device. An execution queue is associated with a particular device. Initializing Print Queues 5-1 Generic queues, rather than being associated with a specific device, point to the execution queues. Generic queues can be associated with more than one execution queue and can distribute print jobs among them, or they can be used to associate specific DECprint Printing Services functions with a print job. The default PRINT qualifier values assumed for execution and generic printer queues can be set in the CPS$STARTUP.COM file. Refer to Section 5.7. In addition, each queue may have print parameters that are associated with the queue. You can modifying these parameter values in CPS$STARTUP.COM. Refer to Section 5.6 for more information about modifying queue parameters. 5.2 Starting the System Queue Manager The system job queue manager must be started before you can use any queue management commands or submit print jobs. The START/QUEUE/MANAGER command is generally included in the system startup procedure. It starts the system queue manager that controls submitting of the job, starting print queues, and scheduling print jobs. You need to issue this command only if the command is not there or if the queue file becomes corrupted and a new queue file must be created. The default file specification for the file containing the queue management information is SYS$SYSTEM:JBCSYSQUE.DAT. 5.3 Defining Print Queues The procedures in this chapter are required for new printer installation and for initial installation of the DECprint Printing Services software. For sites with existing printer systems, you can modify the printer startup file to create new print queues and to modify existing print queues. The DECprint Printing Services software requires a startup command file (CPS$STARTUP.COM) in order to run. You must also change the system startup file SYS$MANAGER:SYSTARTUP_V5.COM. These operations affect system files and should be performed by a system manager or cluster manager. 5-2 Initializing Print Queues 5.3.1 Copying the Printer Startup Command File DECprint Printing Services software provides you with a tem- plate for a printer startup file, SYS$STARTUP:CPS$STARTUP.TEMPLATE. If you do not have an existing CPS$STARTUP.COM file, you must copy the template file and edit it to reflect your own queue structure. Copy the printer startup template file using the COPY command as follows: $ COPY SYS$COMMON:[SYS$STARTUP]CPS$STARTUP.TEMPLATE - SYS$COMMON:[SYS$STARTUP]CPS$STARTUP.COM 5.3.2 Editing the Printer Startup File Edit the CPS$STARTUP.COM file to reflect your own queue structure, including: 1 A logical name for the device control library. Refer to Section 5.3.3. 2 Execution print queues. Refer to Section 5.4. 3 Generic print queues. Refer to Section 5.5. The printer startup template file contains a sample device control library definition, a sample execution queue definition and two sample generic queue definitions. Find this section of the template file and edit the queue definitions to match your print queue structure. Section 5.3.3 through Section 5.5 show portions of text from the CPS$STARTUP.TEMPLATE command file. Text after an exclamation mark (!) to the end of the line denotes a comment, which the startup procedure does not execute. Following the examples and instructions provided in CPS$STARTUP.COM, use an editor of your choice and edit the file to define the queue structure for the system. Note that instructions follow the examples in the template file. When you remove comment flags to enable a command in this file, be sure to remove all occurrences of the comment flags ($!) in the command line, include those on the continued command line. Note Do not change the order of commands in CPS$STARTUP.COM. The first part of the printer startup command file is necessary to create the proper environment for running DECprint Printing Services software. Initializing Print Queues 5-3 The first part of the startup file includes a call to another file, CPS$REQUIRED.COM, as shown: $ @sys$startup:cps$required CPS$REQUIRED.COM does the following: _ Checks to see if the queue manager is running _ Checks privileges _ Installs the DDIF translator if necessary _ Defines the default form CPS$DEFAULT _ Defines the LPS$LAYUP logical name 5.3.3 Defining a Device Control Library Logical Name The startup procedure defines the DECprint Printing Services device control library logical name. It is necessary to change this part of the CPS$STARTUP.COM file if you use site- specific setup modules that require additional device control library definitions or if you add ANSI setup modules. Example 5-1 shows the section of the printer startup command file for defining a library logical name. The template shows an example of the library logical name definition for a device control library search list, followed by the standard library logical name definition for DECprint Printing Services software. You can edit the definition to add site-specific device control libraries to the search list, if necessary. (Refer to Section 5.3.3.1.) 5-4 Initializing Print Queues Example 5-1 Library Logical Name Definition $!+---------- $! Define your device control library logical name here. The first $! "define/system" (commented out) is an example of how to define a $! search list of device control libraries. Note that CPS$devctl $! should always be first in the list. $! $! define /system /exec /nolog cps_lib cps$devctl, "ansi/data=ansi", - $! "ps/data=post" $! $ $ define /system /exec /nolog cps_lib cps$devctl $ $!----------- 5.3.3.1 Defining a Library Search List If you have ANSI setup modules or customized PostScript setup modules in your own libraries, you must include a library search list for the device control library definition in the CPS$STARTUP.COM file. Set up a library search order by including site- specific device control libraries after the CPS$DEVCTL library. Include a command line of the following form to define a device control library search list: $ DEFINE/SYSTEM/EXEC/NOLOG logical-name search-list In the command line, you specify the following information: logical- is the name that you assign to the library search name list. Use this logical name in the definition for the execution queue in this same file (see parameter p3 in Section 5.4). search- is the list of libraries to be searched. For each list library that includes the /DATA_TYPE qualifier, enclose the library name and the qualifier in quotation marks. If you do not use the /DATA_TYPE qualifier, you do not need to enclose the library name in quotation marks. The default data type for a library is PostScript. Initializing Print Queues 5-5 Example The following example defines MY_LIB as the library logical name. Three libraries contain PostScript modules, the standard device control library CPS$DEVCTL, PS1, and PS2. One library, ANSI1, contains ANSI setup modules. The following command sets up the library search order: CPS$DEVCTL, PS1, ANSI1, PS2. Always include the printer standard device control library first in the list. For example: $ DEFINE/SYS/EXEC/NOLOG MY_LIB - CPS$DEVCTL,"PS1/DATA_TYPE=POST","ANSI1/DATA_TYPE=ANSI",PS2 | Note You must stop and start all execution queues to use a new | logical definition of the device control library. If you | change only the contents of a library, it is not necessary to | stop and start the queues. | 5.3.3.2 Preserving Custom Device Control Modules The | installation of DECprint Printing Services software creates | a new version of the supplied device control library | CPS$DEVCTL.TLB in SYS$LIBRARY. If you answered YES to purging | in the installation procedure in Section 3.2.2, existing | device control libraries have been purged. Digital recommends that, in order to add device control modules, you create a new library and refer to it in the library search list. This will simplify the process of upgrading your printing software. PrintServersupgrade existing PrintServer Client software to onlyECprint Printing Services, the existing device control library (LPS$DEVCTL.TLB) will be deleted. Check the existing device control library at this point for custom definitions. Copy the custom device control library definitions to a custom device control library, and add that library definition to the DEFINE command in CPS$STARTUP.COM. Note Do not change the standard device control modules in the standard CPS$DEVCTL library. 5-6 Initializing Print Queues 5.4 Setting Up Execution Queues SYS$STARTUP:CPS$STARTUP.COM calls the SYS$STARTUP:CPS$EXECUTION_ QUEUE.COM file once to initialize and start each execution queue. You should create an execution queue for each PostScript printer. To create your own execution queue structure, you call CPS$EXECUTION_QUEUE.COM once for each queue, supplying your selections for parameters p1 to p8 in the place provided in the CPS$STARTUP.COM file. Table 5-1 shows the parameter values to set up execution queues. Table 5-1 Parameter Values for Execution Queues _____________________________________________________________ Parameter_Value______________________________________________ p1 (re- Name of execution queue. quired) p2 (re- Name of device that the execution queue drives quired) (used with /ON qualifier of INITIALIZE/QUEUE command). For PrintServer printers, this is the printer node name. Refer to Section 5.4.1. p3 (op- Library logical name: the logical name for the tional) standard device control library or for a library search list (default is CPS$DEVCTL). p4 (op- Execution queue parameter defaults (used with tional) DEFINE LPS$queue-name_PARAMETER). Refer to Section 5.6. p5 (op- Value to override or add to THE /DEFAULT qualifier. tional) Refer to Section 5.7. p6 (op- For serial printers, communication speed; default tional) is 9600 baud. For all other printers, this parameter is ignored. p7 (op- Value for SET DEVICE qualifier. For example, tional) to set a printer to SPOOLED status, include "/SPOOLED=(queue-name, disk-device-name)". (continued on next page) Initializing Print Queues 5-7 | Table 5-1 (Cont.) Parameter Values for Execution Queues | | _____________________________________________________________ | Parameter_Value______________________________________________ | | p8 (op- Verify on/off. Enables SET VERIFY for the command | tional) procedure. The default setting is NOVERIFY, to | save log file space and console log space. If p8 | contains 1, then SET VERIFY is enabled. (Refer to | VMS DCL Dictionary for more information about SET | __________[NO]VERIFY.)_______________________________________ 5.4.1 Specifying the Device Name for Parameter p2 In parameter p2, you specify the node name and device name of the printer that the execution queue drives. The device name must reflect the following information, | depending on the printer configuration: | | _ TxAn: for a serial printer on a serial line (n). | | _ LTAn: for a serial printer on a DECserver port (n). | | _ LDAn: for the LN03 Image printer on line n). | | _ scsnode::device-name: for a printer in a VAXcluster | | environment, where scsnode is the VAXcluster SCS node name | and device-name is the printer identifier, as described | above. | | _ node-name:: for a PrintServer printer, where node-name is | | the printer node name. | | _ scsnode::node-name:: for a PrintServer printer in a | | VAXcluster system, where scsnode is the VAXcluster SCS | node name, and node-name is the PrintServer node name. | | Note Using the single colon and double colon conventions in the | device specification is important for distiguishing between | the name of a physical device (single colon) as opposed to a | node name (double colon). Device Characteristics and Parameter p2 CPS$EXECUTION_QUEUE.COM sets device characteristics for LAT devices and serial communications devices. Parameter p2 provides the device name for the SET TERMINAL and SET DEVICE commands in this command file. If p2 is a logical name, the command file translates this name. To prevent logical name 5-8 Initializing Print Queues translation, provide an underscore (_) prefix for your device name in p2. Execution Queue Examples Example 5-2 shows how to use the parameters from Table 5-1 to set up an execution queue for a ScriptPrinter printer, which, by default, prints jobs with two pages on one side of a sheet of paper (NUMBER_UP=2), and uses the form type MYFORM. Example 5-2 Setting Up an Execution Queue $ @SYS$STARTUP:CPS$EXECUTION_QUEUE - 1 2UP - ! P1 - execution queue name 2 FOO::TTB4: - ! P2 - device name 3 CPS_LIB - ! P3 - logical name for your library search list 4 "NUMBER_UP=2" - ! P4 - defines a default queue parameter "/DEFAULT=(FLAG,FORM=MYFORM,NOFEED)" - 5- ! P5 - value to override/add to default qualifiers 6 "" - ! P6 - communication speed /SPOOL=(2UP,DISK1$:) 7- ! P7 - set device qualifier 8 ! P8 - verify on/off 1 Parameter p1 is the name of the execution queue 2UP where the print jobs execute. 2 Parameter p2, FOO::TTB4:, specifies the device TTB4 on node FOO that this execution queue drives. (For a VAXcluster printer, FOO is the SCS node name.) 3 Parameter p3 provides the value CPS_LIB as the logical name for the library search list. You define the search list and associate it with CPS_LIB elsewhere in the same CPS$STARTUP command file. 4 Parameter p4, "NUMBER_UP=2", is the default value for the execution queue. 5 Parameter p5, "/DEFAULT=(FLAG,FORM=MYFORM,NOFEED)", adds the printing of a flag page before each file and defines the default form for jobs in this execution queue. Initializing Print Queues 5-9 6 Parameter p6, "" (null string), does not change the default communication speed of 9600 baud. To change the communication speed to 4800 baud, for example, replace the null string ("") with 4800. (This parameter applies to serial printers only.) 7 Parameter p7, /SPOOL=(2UP,DISK1$:), changes the NOSPOOLED default SET DEVICE characteristic to SPOOLED. This | function applies to serial printers only. | | 8 Parameter p8, the value for SET VERIFY, is unchanged. Example 5-3 shows how to use the parameters from Table 5-1 to set up an execution queue for a PrintServer printer, which, by default, prints jobs on two sides of a sheet of paper (/PARAM=SIDES=2). Example 5-3 Setting Up a PrintServer Execution Queue $ @SYS$STARTUP:CPS$EXECUTION_QUEUE - 1 LPS20$BULL09 - ! P1 - execution queue name 2 BULL09:: - ! P2 - device name (PrintServer node name) 3 CPS_LIB - ! P3 - logical name for your library search list 4 "/PARAM=SIDES=2" - ! P4 - defines a default queue parameter 5 "" - ! P5 - value to override/add to default qualifiers 6 "" - ! P6 - communication speed 7 "" - ! P7 - set device qualifier 8 "" ! P8 - verify on/off 1 Parameter p1 is the name of the execution queue 2UP where the print jobs execute (LPS20$BULL09). 2 Parameter p2, BULL09:: specifies the printer node name. PrintServer queues are conventionally defined using the printer type (LPS20 or LPS40) in order to prevent users from submitting print jobs with printer-specific requirements (such as duplex) from being queued to the wrong type of printer. 3 Parameter p3 provides the value CPS_LIB as the logical name for the library search list. You define the search list and associate it with CPS_LIB elsewhere in the same CPS$STARTUP command file. 4 Parameters p5 through p8 are not used. 5-10 Initializing Print Queues 5.5 Setting Up Generic Queues SYS$STARTUP:CPS$STARTUP.COM calls the SYS$STARTUP:CPS$GENERIC_ QUEUE.COM file to initialize and start generic queues. To define the generic queue structure, fill in your selections for the parameters listed in Table 5-2 in the place provided in the startup file. Table 5-2 Parameter Values for Generic Queues _____________________________________________________________ Parameter_Value______________________________________________ p1 (re- Name of the generic queue quired) p2 (re- Names of the execution queues into which the quired) generic queue can send jobs (used with /GENERIC qualifier). You must supply at least one execution queue name for each generic queue definition. p3 (op- Generic queue parameter defaults. tional) p4 (op- Value to override or add to /DEFAULT qualifier. tional) | | p5 (op- Verify on/off; controls DCL command SET VERIFY. | tional) p6 Reserved to Digital. p7 Reserved to Digital. p8________Reserved_to_Digital._______________________________ Generic Queue Example Example 5-4 shows how to use the parameters listed in Table 5-2 to set up a generic queue for ReGIS print jobs. This generic queue feeds print jobs to either of two ScriptPrinter execution queues. Initializing Print Queues 5-11 Example 5-4 Setting Up a Generic Queue $ @SYS$STARTUP:CPS$GENERIC_QUEUE - 1 LN03R_REGIS - ! P1 - generic queue name 2 "LN03R_TTB4,LN03R_TTB7" - ! P2 - execution queue names 3 "DATA_TYPE=REGIS" ! P3 - default queue parameter 1 Parameter p1, LN03R_REGIS, names the generic queue to which you can send your ReGIS print jobs. 2 Parameter p2 names two execution queues, LN03R_TTB4 and LN03R_TTB7, to which the generic queue sends ReGIS print jobs for execution. 3 Parameter p3, "DATA_TYPE=REGIS" provides ReGIS as the PRINT/PARAMETERS default data syntax for the generic queue. 5.6 Changing the Default Parameters for a Queue A number of printer parameters can be set either from the PRINT command or associated by default with a queue. You can edit the DECprint Printing Services startup file, creating systemwide parameters for each queue, with default parameters. For example, you can set up a generic queue for printing ReGIS files for printer TTB4, by adding the following definition to SYS$STARTUP:CPS$STARTUP.COM: @sys$startup:cps$generic-queue - ! ReGIS queue REGIS_TTB4 - ! P1 - Generic queue name TTB4 - ! P2 - /GENERIC = execution queues "DATA_TYPE=REGIS" ! P3 - Default queue parameters During the execution of CPS$STARTUP.COM, LPS$GENERIC_ QUEUE.COM defines the systemwide logical name CPS$REGIS_ TTB4_PARAMETER with DATA_TYPE=REGIS. Then execute the printer startup command file: $ @SYS$STARTUP:CPS$STARTUP.COM 5-12 Initializing Print Queues 5.6.1 Syntax for Parameters Associated with a Queue Parameters specified by the LPS$queue-name_PARAMETER logical must follow the same rules as those entered with the PRINT/PARAMETERS command. However, parameters containing special characters or delimiters are enclosed in double quotation marks ("") in the PRINT command and are not enclosed in extra double quotation marks in the CPS$queue- name_PARAMETER systemwide logical. | For example, in the following PRINT command, you must enclose | the FONTS_USED parameter and arguments in double quotation | marks: | | $ PRINT/PARAMETER=(PAGE_ORIENTATION=LANDSCAPE,- | "FONTS_USED=(CGTIMES8-10-12_MCS,CGTRIUM8-10-12_MCS)",NUMBER_UP=2) | | However, in the following logical name definition, you | must not enclose the FONTS_USED parameter and arguments in | additional double quotation marks: | | @sys$startup:cps$generic_queue - ! ANSI queue | ANSI_TTB4 - ! P1 - Generic queue name | TTB4 - ! P2 - /GENERIC = execution queues | "PAGE_ORIENTATION=LANDSCAPE,-" | "FONTS_USED=(CGTIMES8-10-12_MCS,CGTRIUM8-10-12_MCS),NUMBER_UP=2" | ! P3 - Default queue parameters | | CPS$GENERIC_QUEUE.COM creates the systemwide logical name | CPS$ANSI_TTB4_PARAMETER. This logical name has the following | default print parameters: | | _ PAGE_ORIENTATION=LANDSCAPE | | _ FONTS_USED=(CGTIMES8-10-12_MCS,CGTRIUM8-10-12_MCS) | | _ NUMBER_UP=2 | 5.6.2 Syntax Errors in Parameters Associated with a Queue If you type a parameter in CPS$STARTUP.COM incorrectly, the print symbiont does not translate that parameter and following parameters; the previous parameters are not affected. The symbiont generates an error message that is displayed on your screen and printed on the job trailer page for every print job sent to the associated queue. Those parameters that are not translated will take the standard default settings. Initializing Print Queues 5-13 Example of Syntax Error and Associated Error Message In the following example, there is an extra "L" in the argument to the PAGE_ORIENTATION parameter. Therefore, the print symbiont ignores the second and third parameters, PAGE_ ORIENTATION and SHEET_COUNT. Only the value DATA_TYPE is retained by the symbiont. @SYS$STARTUP:CPS$TEK$PRINT - ! Tektronix 4010/4014 queue TEK4014_TTB4 - ! P1 - Generic queue name TTB4 - ! P2 - /GENERIC = execution queues "DATA_TYPE=TEK4014,PAGE_ORIENTATION=LLANDSCAPE,SHEET_COUNT=5" ! P3 - Default queued parameters For every print job for this queue, an error message similar to the following appears on the screen and on the job trailer page in the message section: 10-APR-1989 15:21 %LPS-E-PARSYNERR, Syntax error in the /PARAMETERS qualifier at or near PAGE_O=LLANDSCAPE) 5.6.3 Order of Defaulting for Parameters The default parameters for a generic queue supersede the defaults defined for the execution queue. However, if there is a syntax error in the translation of the generic queue's logical name, the execution queue's logical name is translated and overrides the values set by the generic queue. The symbiont also uses the execution queue default parameters when the print job is submitted directly to the execution queue or to a generic queue that has no logical name associated with it. Parameters set by the /PARAMETERS qualifier to the PRINT command override any defaults set for the queue. The symbiont selects default values for parameters, from highest to lowest priority, as follows: 1 Parameters specified in the PRINT command. 2 For the DATA_TYPE parameter, tagged files specify the data type. 3 Generic queue defaults specified in the CPS$STARTUP.COM file. 4 Execution queue defaults specified in the CPS$STARTUP.COM.file. 5 Built-in defaults: _ DATA_TYPE=ANSI or DDIF (for tagged files) 5-14 Initializing Print Queues _ INPUT_TRAY=not defined _ LAYUP_DEFINITION=not defined _ MESSAGES=NOMESSAGES _ NUMBER_UP=not defined _ OUTPUT_TRAY=not defined _ PAGE_LIMIT=no limit _ PAGE_ORIENTATION=PORTRAIT _ PAGE_SIZE=(Same as SHEET_SIZE) _ SHEET_COUNT=settable for printer _ SHEET_SIZE=Refer to the DECprint Printing Services User's Guide for the defaulting rules. _ SIDES=n (as set by printer) _ TAB=NOTAB 5.7 Changing the Default Qualifiers for a Queue By default, the printer startup command procedure creates printer queues with the following qualifiers: _ /SEPARATE=(BURST,TRAILER,NORESET) _ /DEFAULT=(NOFEED) _ /FORM=CPS$DEFAULT You can redefine the default values associated with these qualifiers in the startup command file, CPS$STARTUP.COM. Include the values you require in parameter p5 of the execution queue definition (see Example 5-2). If you include more than one qualifier, enclose the values in double quotation marks (as in, "values"). For example, you can define the following default qualifiers: _ /SEPARATE=(FLAG) _ /DEFAULT=(FEED) _ /FORM=MYFORM To define these default qualifier values, use the following qualifier in CPS$STARTUP.COM at p5: /DEFAULT=(FLAG,FEED,FORM=MYFORM) Initializing Print Queues 5-15 After you edit CPS$STARTUP.COM and exit from the editor, you can start the print queues, as described in Section 3.3. 5-16 Initializing Print Queues 6 ________________________________________________________________ System Messages This chapter contains the system messages issued by the DECprint Printing Services software installation procedure. Refer to the Guide to VAX/VMS Software Installation for explanations of messages issued by VMSINSTAL. Refer to the VAX/VMS System Messages and Recovery Procedures Reference Manual for explanations of messages issued by the Authorize Utility. 6.1 Message Format System messages issued during the installation procedure have | one of the following formats: | | %BACKUP-s-ident, text | %CPS-s-ident,text | %CREATE-s-ident, text | %VMSINSTALL-s-ident, text | In each message, the following information is provided: % is the prefix to all primary messages. - is the prefix to all continuation messages. s is the severity level of the message. (Refer to Section 6.2.) ident is an abbreviation of the message text. text is the expanded text of the message. System Messages 6-1 6.2 Severity Level The severity levels of DECprint Printing Services system messages are as follows: _____________________________________________________________ Code_Meaning_________________________________________________ S Success-successful completion of the request. I Informational-may or may not require user action. W Warning-request may not have completed and may require user action. E Error-system encountered an error that may be recover- able. F Fatal-system encountered a fatal error and cannot _____continue_processing_the_request.________________________ 6.3 Message Descriptions The following message descriptions are alphabetized by the ident portion of the messages code. The message prefix, | source designation, and severity code are not shown. | | ACTIVE, The following processes are still active: | | Explanation: VMSINSTAL has detected other processes running | on the system; they are displayed on lines following this | message. The existence of other processes may interfere with | VMSINSTAL in unexpected ways. | | User Action: VMSINSTAL allows you to exit in order to log out | the processes, if necessary. | | BADSPEC, File spec AI1TXT cannot be parsed | | Explanation: The ALL-IN-ONE compatibility kit requires a file | PS-PRINTING-ALL-IN-1-COMPAT.TXT, which does not exist. | | User Action: After the VMSINSTAL procedure is finished, | provide adequate disk space to restore all product savesets | (at least 7500 disk blocks). Start the installation procedure | again. 6-2 System Messages CLEANING_UP, Restoring system and network, DO NOT USE CTRL/Y. Explanation: System parameters that were changed up to the point of failure are being restored to their original values. User Action: Do not use Ctrl/Y; it may prevent the complete | restoration of system parameters. | | DECNET, Your DECnet network is up and running. | | Explanation: The DECnet network software is up and running on | the system. | | User Action: No action is required. | | EXISTS, directory already exists | | Explanation: The VMSINSTAL procedure creates appropriate disk | directories for DECprint Printing Services software restored | from the distribution media. This message indicates that the | appropriate disk directories are already defined. | | User Action: No action is required. | | INSNPAGEVIR, NPAGEVIR current-NPAGEVIR insufficient, need at | least required-NPAGEVIR | | Explanation: The specified SYSGEN parameter current-NPAGEVIR | has an insufficient value. The LN03 Image printer will not be | able to run with this value. | | User Action: Using SYSGEN, change the NPAGEVIR value to the | value recommended in required-NPAGEVIR and reboot the system. | | INSPAGEDYN, PAGEDYN current-PAGEDYN insufficient, need at least | required-PAGEDYN | | Explanation: The specified SYSGEN parameter current-PAGEDYN | has an insufficient value. The LN03 Image printer will not be | able to run with this value. | | User Action: Using SYSGEN, change the PAGEDYN value to the | value recommended in required-PAGEDYN and reboot the system. System Messages 6-3 | INSPROCSECTCNT, PROCSECTCNT current-PROCSECTCNT insufficient, | need at least required-PROCSECTCNT | | Explanation: The specified SYSGEN parameter current- | PROCSECTCNT has an insufficient value. The LN03 Image printer | will not be able to run with this value. | | User Action: Using SYSGEN, change the PROCSECTCNT value to | the value recommended in required-PROCSECTCNT and reboot the | system. | | INSVIRTUALPAGECNT, VIRTUALPAGECNT current-VIRTUALPAGECNT | insufficient, need at least required-VIRTUALPAGECNT | | Explanation: The specified SYSGEN parameter (current- | VIRTUALPAGECNT) has an insufficient value. The LN03 Image | printer will not be able to run unless the value is at least | required-VIRTUALPAGECNT. | | User Action: Using SYSGEN, change the VIRTUALPAGECNT value to | the value recommended in required-VIRTUALPAGECNT and reboot | the system. | | INSWSMAX, WSMAX current-WSMAX insufficient, need at least | required-WSMAX | | Explanation: The specified SYSGEN parameter (current-WSMAX | has an insufficient value. The LN03 Image printer requires a | value of at least required-WSMAX. | | User Action: Using SYSGEN, change the WSMAX value to the | value recommended in required-WSMAX and reboot the system. INVRES, Invalid response, please type YES or NO. Explanation: The only responses accepted for this prompt are YES and NO. A response other than one of these was entered. | User Action: Enter YES or NO. | | IVLOGNAM, invalid logical name | | Explanation: The command line to start VMSINSTAL contained an | invalid logical name for device-id. | | User Action: This message terminates the VMSINSTAL procedure. | Check the logical that you specified in the VMSINSTAL command | line and be sure to use the appropriate device-id. 6-4 System Messages | IVP, Beginning IVP... | | Explanation: VMSINSTAL is running the Installation Verification | Procedure to check the software installation. | | User Action: No action is required. LAYUPDEF, This installation will use its value Explanation: The installation uses the existing logical name for LPS$LAYUP. | User Action: None; informational message only. | | MOVEFILES, Files will now be moved to their target directo- | ries . . . | | Explanation: The VMSINSTAL procedure is copying distributed | software to the appropriate disk directories. | | User Action: No action is required. | | NOFILE, New file file-name does not exist | | Explanation: The distributed file-name has not been restored | to the appropriate disk directory. | | User Action: As a result of a previous error, the required | files cannot be copied to the disk directory. Exit VMSINSTAL | and correct the cause of the problem. Run VMSINSTAL again to | obtain the missing files. NO_QUEMAN, This product requires the queue management facility to install. Explanation: The queue manager could not be found. The installation procedure is aborted. User Action: Start the queue manager. For information refer to VAX/VMS System Manager's Reference Manual or Guide to Maintaining a VMS System. NOQUEMGR, IVP will NOT be run. Installation continuing . . . Explanation: The queue manager is not running on your system. The installation will continue, but the Installation | Verification Procedure cannot run. | | User Action: You can run VMSINSTAL again to test the IVP, or | submit the files for printing after the software is installed | (refer to Section 3.5.) System Messages 6-5 | NOQUES, No further questions will be asked | | Explanation: The VMSINSTAL procedure will complete from this | point without requiring input from your terminal. | | User Action: No action is required. | | NOSAVESET, Saveset n cannot be restored. | | Explanation: The saveset indicated by n cannot be restored to | disk. | | User Action: This message is accompanied by other messages | that explain the cause of this problem. If disk space | is insufficient, the VMSINSTAL procedure will complete | unsuccessfully. Ensure that at least 7500 disk blocks are | available for installing this product and start the VMSINSTAL | procedure again. NO_SPACE, This product requires decimal-number blocks of disk space to install. Explanation: There are not enough free disk blocks to install this software. The installation procedure is aborted. User Action: Ensure that you have at least the specified | number of free disk blocks and restart the installation. | | NOTSYSTEM, You are not logged in to the SYSTEM account. | | Explanation: You are running VMSINSTAL from a process that | does not have SYSTEM privileges. | | User Action: The lack of SYSTEM privileges may cause problems | with file ownership during the installation process. You | should exit VMSINSTAL and log in to a SYSTEM account before | attempting to run VMSINSTAL. | | OPENOUT, error opening file-spec as output | | Explanation: Files cannot be restored from the distribution | media to the disk. | | User Action: Previous messages were displayed to indicate | a problem with the VMSINSTAL procedure. After the VMSINSTAL | procedure exits, check the disk space quota to ensure that | at least 7500 disk blocks are available for restoring | the distributed software. Run VMSINSTAL again when the | prerequisites are fulfilled. 6-6 System Messages RELMOVED, The product's release notes have been successfully moved to SYS$HELP. Explanation: The release notes for this software have been moved into SYS$HELP. | User Action: No action is required. | | RESTORE, Restoring product saveset n | | Explanation: VMSINSTAL has begun restoring the software from | the distribution media. | | User Action: No action is required. | | SYSDIR, This product creates system disk directory directory. | | Explanation: The VMSINSTAL procedure has created the | specified directory for restoring the software. | | User Action: No action is required. TRNNOTREP, The translator-name translator in the kit was NOT installed Explanation: The current translator (ANSI, ReGIS, or Tektronix 4010/4014) is an equivalent or newer version than the version in the kit. Therefore, the current version of the translator is not replaced. | User Action: No action is required. | | UNEXPECTED, Installation terminated due to unexpected event. | | Explanation: The VMSINSTAL procedure is terminated because of | problems. The cause of this message is probably indicated in | previous messages from the VMSINSTAL procedure. | | User Action: Determine the cause of the error and correct | the problem. Ensure that enough disk space is available for | restoring the software. Then run VMSINSTAL again to install | the software. System Messages 6-7 A ________________________________________________________________ Sample Installation Session Example A-1 shows a sample installation of the VMS DECprint Printing Services Software, Version 4.0. Example A-1 Sample Installation | @sys$update:vmsinstal cps040 kits$: | | VAX/VMS Software Product Installation Procedure V5.3 | | It is 21-SEP-1990 at 11:24 | | Enter a question mark (?) at any time for help. | | %VMSINSTAL-W-DECNET, Your DECnet network is up and running. | | %VMSINSTAL-W-ACTIVE, The following processes are still active: | Gazelle | Hyacinth | Jaguar | | * Are you satisfied with the backup of your system disk [YES]? Y | | The following products will be processed: | | CPS V4.0 | | Beginning installation of CPS V4.0 at 11:31 | | %VMSINSTAL-I-RESTORE, Restoring product saveset A ... | | %VMSINSTAL-I-RELMOVED, The product's release notes have been | successfully moved to SYS$HELP. | | * Do you want to purge files replaced by this installation [YES]?Y (continued on next page) Sample Installation Session A-1 | Example A-1 (Cont.) Sample Installation | | %CPS-I-LAYUPDEF, LPS$LayUp is already defined | -CPS-I-LAYUPDEF, This installation will use its value | | %VMSINSTAL-I-SYSDIR, This product creates system disk directory | VMI$ROOT:[SYSTEST.CPS]. | %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.CPS] already exists | | %VMSINSTAL-I-SYSDIR, This product creates system disk directory | VMI$ROOT:[SYSHLP.EXAMPLES.CPS]. | %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.CPS] already exists | | %CPS-I-NOQUES, No further questions will be asked | %VMSINSTAL-I-RESTORE, Restoring product saveset B ... | %CPS-I-TRNNOTREP, The ANSI translator in the kit was NOT installed | | Software installer: | | Please remember to copy SYS$StartUp:CPS$StartUp.Template to | SYS$StartUp:CPS$StartUp.Com. Then edit this file following | the instructions to create your queues. Finally execute | this file to establish and start the queues. Also remember | to edit SYS$Manager:SyStartUp_V5.Com to establish your queues | at system startup time. | | If you use LAT devices, this file should be executed after the | LAT devices are created. If you use PrintServers, this file | should be executed after DECnet is running. If you use both | types of printers, both of the above conditions should be | satisfied before the startup file is executed. | | %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target | directories... | | %CPS-I-IVP, Beginning IVP... | Job CPS$IVP_POST (queue CPS$IVP_TEST, entry 359) started on | CPS$IVP_TEST | Job CPS$IVP_ANSI (queue CPS$IVP_TEST, entry 360) started on | CPS$IVP_TEST | Job CPS$IVP_REGIS (queue CPS$IVP_TEST, entry 361) started on | CPS$IVP_TEST | Job CPS$IVP_TEK4014 (queue CPS$IVP_TEST, entry 362) started on | CPS$IVP_TEST | Job CPS$IVP_PCL (queue CPS$IVP_TEST, entry 362) started on | CPS$IVP_TEST (continued on next page) A-2 Sample Installation Session | Example A-1 (Cont.) Sample Installation | | IVP successful for VMS DECprint Printing Services Software V4.0 | Installation of CPS V4.0 completed at 12:43 | | VMSINSTAL procedure done at 12:44 | Sample Installation Session A-3 B ________________________________________________________________ Sample Startup Command File Example B-1 shows the printer startup file template: | | Example B-1 Sample Printer Startup Command File | | $! CPS$Startup.Com is the startup file that is executed to startup CPS. It is | $! template driven to allow you to fully specify the queue structure yet at the | $! same time allow Digital to update the software without disturbing your | $! customizations. | $! | $! Version: V4.0 | $! | $! The first part of the file is mandatory and MUST be executed FIRST. The | $! second part is for your customizations. | $ | $! Protect against environment running in. | $ set symbol /scope=(nolocal, noglobal) | $ | $ @sys$startup:cps$required | $ if .not. $status then exit | $ | $! | $! Modify definition of PSM$ANNOUNCE here. Just remember it will effect | $! all queues on the system. | $! | $! def/sys/exe psm$announce "DECprint printing services system" | $!+---------- | $! Define your device control library logical name here. The first | $! "define/system" (commented out) is an example of how to define a | $! search list of device control libraries. Note that CPS$devctl (continued on next page) Sample Startup Command File B-1 | Example B-1 (Cont.) Sample Printer Startup Command File | $! should always be first in the list. | $! | $! define /system /exec /nolog cps_lib cps$devctl, "ansi/data=ansi", - | $! ps/data=post" | $! | $ | $ define /system /exec /nolog cps_lib cps$devctl | $ | $!----------- | $ | $!+---------- | $! If a printer is connected via a DECserver (LAT), you may want to consider | $! defining the application port here instead of in Sys$manager:ltload.com | $! to keep everything in one place. Here is an example of a port definition: | $! | $! run sys$system:latcp | $! crea port lta1 /application /nolog | $! set port lta1 /node=YOUR_DECSERVER_NAME_HERE /port=port_3 /application - | /queue | $!----------- | $ | $!+---------- | $! Enter your queue structure below this line | $!---------- | $ | $! Here is a sample queue structure: One execution queue on device Tzz0:, | $! and two generic queues (one ANSI, one PostScript). Modify these | $! commands and add additional ones to reflect your desired queue structure. | $ | $ on error then continue | $ @sys$startup:cps$execution_queue - | cps - ! P1 - Execution queue name | tzz0: - ! P2 - Serial Device name or - | PrintServer node name | cps_lib - ! P3 - Logical name for library(ies) | ""- ! P4 - Default queue parameters | ""- ! P5 - Default queue qualifiers | ""- ! P6 - Communication speed - | (serial devices only) | ""- ! P7 - Device characteristics | "" ! P8 - Verify on/off | $ (continued on next page) B-2 Sample Startup Command File | Example B-1 (Cont.) Sample Printer Startup Command File | $ on error then continue | $ @sys$startup:cps$generic_queue - ! ANSI queue | cps_ansi - ! P1 - Generic queue name | cps - ! P2 - Execution queue name(s) | "data=ansi" - ! P3 - Default queue parameters | ""- ! p4 - reserved | "" ! P5 - Verify on/off | $ | $ on error then continue | $ @sys$startup:cps$generic_queue - ! PostScript queue | cps_ps - ! P1 - Generic queue name | cps - ! P2 - Execution queue name(s) | "data=post" - ! P3 - Default queue parameters | ""- ! p4 - reserved | "" ! P5 - Verify on/off | $ | $ exit | $! Parameter definition and example for execution and generic queues. | $! | $! CPS$execution_queue.com: | $! | $! P1 is the queue name. | $! | $! P2 is the device name for /On. For example: | $! txa0: ! For a ScriptPrinter on a serial line | $! lta1: ! For a ScriptPrinter on a DECserver port | $! lda1: ! For the LN03 Image Printer | $! foo::txa4: ! Txa4 on node foo - for clusters | $! iguana:: ! PrintServer node name (must not be - | used on a cluster) | $! foo::iguana:: ! PrintServer node name for clusters | $! | $! P3 is the logical name for the /library qualifier. If you want to | $! have a library list to pick up your custom library, you must define | $! a logical name that defines the libraries. See cps_lib in this file | $! for an example. | $! | $! P4 is used to define the queue defaults for /Parameter. For example, | $! a queue might be default to make 2 copies with room to punch holes. | $! Here is what would be supplied to do make that the queue default: | $! "sheet_count=2, layup_def=lps$holes" | $! (continued on next page) Sample Startup Command File B-3 | Example B-1 (Cont.) Sample Printer Startup Command File | $! P5 is used to override, or specify other qualifiers to init/que. Here | $! are some examples: | $! /wsquota=10000 ! Needed for the LN03 Image Printer | $! "/form=my_form /schedule=size" | $! | $! P6 is used to specify the device speed for a serial line. Note that | $! it has no effect for LAT devices. The default is 9600. If you | $! have a DMZ32, you should set the speed to 4800. | $! | $! P7 is used to specify other device characteristics. For example, if | $! you want the device spooled, you would say: | $! /spooled=(my_queue, my_disk) | $! | $! P8 is used to set VERIFY on/off; Specify "1" to set VERIFY on. | $! | $! CPS$Generic_queue.com: | $! | $! P1 is the queue name. | $! | $! P2 is list of execution queues for /GENERIC. For example: | $! "queue1, queue2" | $! | $! P3 is used to define the queue defaults for /Parameter. For example, | $! a queue might be default to make 2 copies with room to punch holes. | $! Here is what would be supplied to do make that the queue default: | $! "sheet_count=2, layup_def=lps$holes" | $! | $! P4 is used to override, or specify other qualifiers to init/que. | $! | $! P5 is used to set VERIFY on/off; Specify "1" to set VERIFY on. | B-4 Sample Startup Command File | | | | | | C | ________________________________________________________________ | | Installation Verification Output | | | | | The Installation Verification Procedure (IVP) for the | VMS DECprint Printing Services Software, Version, 4.0, | does not print on paper. However, IVP files exist in | SYS$COMMON:[SYSTEST.CPS]. You can print these files on your | printer to verify correct queue configuration and printer | operation. | | For instructions on how to print these files, see Section 3.5. | | Figure C-1 through Figure C-4 are copies of the printed | output files from the Installation Verification Procedure | (IVP). Check your printer output carefully against these | copies. The flag and trailer pages are not included here, | because they vary according to the user and system performing | the installation. Resolve any differences in the data output | with your Digital Customer Services representative. Installation Verification Output C-1 | Figure C-1 is a reproduction of the ANSI data syntax test | file. Print this file using the following command: | | $PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=ANSI)/NOTIFY - | SYS$COMMON:[SYSTEST.CPS]CPS$IVP_ANSI.DAT | C-2 Installation Verification Output Installation Verification Output C-3 Figure C-2 is a reproduction of the ReGIS data syntax test file. Print this file using the following command: $PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=REGIS)/NOTIFY - SYS$COMMON:[SYSTEST.CPS]CPS$IVP_REGIS.DAT C-4 Installation Verification Output Installation Verification Output C-5 Figure C-3 is a reproduction of the TEK4014 data syntax test file. Print this file using the following command: $PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=TEK4014)/NOTIFY - SYS$COMMON:[SYSTEST.CPS]CPS$IVP_TEK4014.DAT C-6 Installation Verification Output Installation Verification Output C-7 Figure C-4 is a reproduction of the PostScript data syntax test file. Note that this IVP test file includes the printer model name; therefore, the exact appearance of this page differs from one printer model to the next. Print this file using the following command: $PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=POSTSCRIPT)/NOTIFY - SYS$COMMON:[SYSTEST.CPS]CPS$IVP_POST.DAT C-8 Installation Verification Output Installation Verification Output C-9 Figure C-5 is a reproduction of the Hewlett-Packard Corporation's PCL data syntax test file. Print this file using the following command: $PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=PCL)/NOTIFY - SYS$COMMON:[SYSTEST.CPS]CPS$IVP_PCL.DAT C-10 Installation Verification Output Installation Verification Output C-11 D ________________________________________________________________ New Files and Libraries During the installation of the DECprint Printing Services software, new files and libraries are added to the system. This appendix lists the following files: _ New files added during installation, Section D.1 _ The new device control library, Section D.2 _ The files you must delete when upgrading PrintServer client software, Section D.3 D.1 New Files For systems with a the printing system that is not upgrading from ScriptPrinter Version 2.1, Table D-1 lists the files added to the specified directories during the installation procedure. Table D-1 New Files ________________________________________________________________ File_Name__________________Directory____________________________ CPS$SMB.EXE SYS$COMMON[SYSLIB] CPS$MSG.EXE SYS$COMMON[SYSLIB] CPS$DEVCTL.TLB SYS$COMMON[SYSLIB] CPS$EXECUTION_QUEUE.COM SYS$COMMON[SYSLIB] (continued on next page) New Files and Libraries D-1 Table D-1 (Cont.) New Files ________________________________________________________________ File_Name__________________Directory____________________________ CPS$GENERIC_QUEUE.COM SYS$STARTUP CPS$REQUIRED.COM SYS$STARTUP CPS$STARTUP.TEMPLATE SYS$STARTUP | | TRN$ANSI_PS.EXE SYS$SHARE | | TRN$DDIF_PS.EXE SYS$SHARE | | TRN$REGIS_PS.EXE SYS$SHARE | | TRN$TEK4014_PS.EXE SYS$SHARE | | TRN$PCL_PS.EXE SYS$SHARE CPS$IVP.COM SYS$COMMON:[SYSTEST] CPS$IVP_ANSI.DAT SYS$COMMON:[SYSTEST.CPS] CPS$IVP_REGIS.DAT SYS$COMMON:[SYSTEST.CPS] CPS$IVP_TEK4014.DAT SYS$COMMON:[SYSTEST.CPS] CPS$IVP_POST.DAT SYS$COMMON:[SYSTEST.CPS] | | CPS$IVP_PCL.DAT SYS$COMMON:[SYSTEST.CPS] LPS$IVP_LAYUPDEF.DAT SYS$COMMON:[SYSTEST.CPS] LPS$SINGLEHOLES.LUP SYS$COMMON:[SYSHLP.EXAMPLES.CPS] LPS$DOUBLEHOLES.LUP SYS$COMMON:[SYSHLP.EXAMPLES.CPS] LPS$HOLES.LUP SYS$COMMON:[SYSHLP.EXAMPLES.CPS] LPS$NUP.LUP SYS$COMMON:[SYSHLP.EXAMPLES.CPS] (continued on next page) D-2 New Files and Libraries | Table D-1 (Cont.) New Files | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | LPS$IVP_LAYUPDEF.DAT [SYSHLP.EXAMPLES.CPS] | | CPS040.RELEASE_NOTES SYS$COMMON:[SYSHLP] | | CPS$HELP.HLP SYS$COMMON:[SYSHLP] | | CPS$COMMON_PORT_ SYS$COMMON:[SYSHLP.EXAMPLES.CPS] | SETTINGS.COM CPS$CONFIG_PRINTER_ SYS$COMMON:[SYSHLP.EXAMPLES.CPS] PORT.COM CPS$DS100-PORT- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] SETTINGS.COM CPS$DS200-PORT- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] SETTINGS.COM CPS$DS500-PORT- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] SETTINGS.COM CPS$GET-DS100-PORT- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] GROUPS.COM CPS$SET-DS-GROUPS.COM SYS$COMMON:[SYSHLP.EXAMPLES.CPS] CPS$SET-DS100-GROUPS.COM SYS$COMMON:[SYSHLP.EXAMPLES.CPS] | | CPS$SAVE-DS500-PORT.COM SYS$COMMON:[SYSHLP.EXAMPLES.CPS] | | LPS$SET_TIMEOUT.PS SYS$COMMON:[SYSMGR] | | LPS$SET_PRINTER_NAME.PS SYS$COMMON:[SYSMGR] | | Optional Files for ALL-IN-1 Compatibility Kit (continued on next page) New Files and Libraries D-3 | Table D-1 (Cont.) New Files | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | PS-PRINTING-ALL-IN-1- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] | COMPAT.SAV | | PS-PRINTING-ALL-IN-1- SYS$COMMON:[SYSHLP.EXAMPLES.CPS] | COMPAT.TXT______________________________________________________ | The system help library was also modified as a result of this installation. D.2 Device Control Library The device control library supplied in the DECprint Printing Services Software Distribution Kit contains PostScript modules used to control the operation of the PostScript printers. This library (CPS$DEVCTL.TBL) is located in the SYS$COMMON:[SYSLIB] directory, defined as SYS$LIBRARY. The library contains the following modules: _ LPS$DECMCSENCODING | _ LPS$ERRORHANDLER | | _ LPS$FINDFONT_ISOLATIN1_DECMCS_V40 _ LPS$ISOLATIN1ENCODING _ LPS$$CHECKPROLOGUE _ LPS$$EXITSERVERLOOP _ LPS$$FLUSHPAGES _ LPS$$GETSHEETCOUNT _ LPS$$LN03_SETCONTEXT _ LPS$$LN03_SETINPUTTRAY _ LPS$$LN03_SETOUTPUTTRAY _ LPS$$LN03Q_INITPSDEVICE _ LPS$$LN03Q_LOADSERVER _ LPS$$LN03Q_SETPAPERSIZE | _ LPS$$LN03R_INITPSDEVICE | | _ LPS$$LPS_GETSHEETINFO D-4 New Files and Libraries | _ LPS$$LPS_JOBJOG | | _ LPS$$LPS_LOADDICT | | _ LPS$$LPS_SETCONTEXT | | _ LPS$$LPS_SETINPUTTRAY | | _ LPS$$LPS_SETOUTPUTTRAY | _ LPS$$LOADDICT | | _ LPS$$NEWSHEET | | _ LPS$$PRINTERTYPE _ LPS$$SETNUMBERUP _ LPS$$SETPAGELIMIT _ LPS$$SETPAGEORIENTATION _ LPS$$SETPAGESIZE _ LPS$$SETSHEETCOUNT _ LPS$$SETSHEETSIZE _ LPS$$SETSIDES _ LPS$$SYSTEMPAGES _ LPS$$VMSTATUS | D.3 Files For PrintServer Software Upgrade Procedure | | PrintServerowing files were provided as a result of VAX | printersServer Client V3.0 installation and may be deleted after | onlyou install DECprint Printing Services. | | Table D-2 PrintServer Client Files To Delete | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | LPS$SMB.EXE SYS$SYSTEM | | LPS$MSG.EXE SYS$MESSAGE | | LPS$DEVCTL.TLB SYS$SHARE (continued on next page) New Files and Libraries D-5 | Table D-2 (Cont.) PrintServer Client Files To Delete | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | LPS$STARTUP.COM SYS$MANAGER or SYS$STARTUP | | TRN$LAYUPDEF_PS.EXE SYS$SHARE | | LPS$FONT_METRICS.TLB SYS$SHARE | | LPSVC030.RELEASE_NOTES SYS$HELP | | LPS$IVP.COM SYS$SYSROOT:[SYSTEST] | | LPS$IVP_ANSI.DAT SYS$SYSROOT:[SYSTEST.LPSVC] | | LPS$IVP_REGIS.DAT SYS$SYSROOT:[SYSTEST.LPSVC] | | LPS$IVP_TEK4014.DAT SYS$SYSROOT:[SYSTEST.LPSVC] | | LPS$IVP_LAYUPDEF.DAT_______SYS$SYSROOT:[SYSTEST.LPSVC]__________ | | The following files are common to PrintServer Client software | and DECprint Printing Services software. Do not delete these | files. | | Table D-3 PrintServer Client Files To Retain | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | TRN$ANSI_PS.EXE SYS$SHARE | | TRN$REGIS_PS.EXE SYS$SHARE | | TRN$TEK4014_PS.EXE SYS$SHARE | | LPS$SINGLEHOLES.LUP LPS$LAYUP | | LPS$DOUBLEHOLES.LUP LPS$LAYUP | | LPS$HOLES.LUP LPS$LAYUP (continued on next page) D-6 New Files and Libraries | Table D-3 (Cont.) PrintServer Client Files To Retain | | ________________________________________________________________ | File_Name__________________Directory____________________________ | | LPS$NUP.LUP________________LPS$LAYUP____________________________ | | New Files and Libraries D-7 E ________________________________________________________________ Troubleshooting Procedures This appendix contains troubleshooting procedures for diag- nosing error conditions on the printer system. Section E.1 through Section E.5 describe printer problems and trou- bleshooting procedures for serial printers and LN03 Image printers. Refer to Section E.6 for information about troubleshooting problems on PrintServer printers. | When a printer problem occurs, information is available if | you have included the /NOTIFY qualifier on the PRINT command | line. This may indicate the cause of the failure. Refer to | the messages chapter in the DECprint Printing Services User's | Guide for an explanation and recovery procedures. | | In case of any printer problem, your first step is to examine | the console output and the operations command procedure | (OPCOM) printer messages. If your terminal is not running | OPCOM, enable it with REPLY/ENABLE, start the symbiont again | (if necessary), and then read the printer messages. This | procedure requires OPER privileges. E.1 The Printer Is Not Printing Any Jobs ScriptPrinter,n discusses steps to take when your printer does DEClaser,int or when your printer has stopped printing. andELN03 the following command: Image print$rSHOW QUEUE/FULL queue-name[:] If "Not Available" is displayed, the terminal port or the printer may have a problem. "Not Available" displays when the symbiont sends a Ctrl/T sequence to the printer and the printer does not respond. This action usually resets the printer. The printer should respond with a status message Troubleshooting Procedures E-1 back to the symbiont. Until the symbiont receives a status message, "Not Available" is displayed. Check that the port specified in the startup file is the physical port to which the printer is connected. An OPCOM message of DEVICE UNAVAILABLE implies that the printer is unable to acknowledge any queries from the system. Check for the following: _ Bad communication line _ Incorrect port baud rate setting _ Wrong switch settings on the LN03R ScriptPrinter _ Excessive line noise resulting in lost response from the printer _ No power to the printer _ Bad cable _ Incorrect bits/character, wrong parity, or both An OPCOM message of NOT READY occurs at the same time and for the same reasons as DEVICE UNAVAILABLE. If the correct files are present, and the jobs are still not printing, call your Digital Customer Services representative. E.1.1 Newly Installed Printer In Section E.1.1, steps 1 through 7 apply to the ScriptPrinter and DEClaser printers. For the LN03 Image printer, go directly to step 4. Step 1: Press the test button for a summary sheet ScriptPrinters a ScriptPrinter, press the test button, which is onlyhe white button with a T in a circle on the back panel of the printer. If pressing the test button produces a summary sheet, go on to STEP 2, to check the printer hardware and software configurations. If the printer does not produce a test page, check the printer hardware. _ Is the power on? _ Is the printer on line? _ What is the status of the print engine? E-2 Troubleshooting Procedures Recheck the hardware installation procedure (refer to Section 4.2. DEClaserEClaser printers, press the ONLINE button on the front onlyanel so that the display shows PS OFFLINE. Press the TEST button to get a test page. Check the test page to make sure that the PostScript cartridge has been properly installed. If the summary page appears only in Courrier, then the font cartridge (the PostScript cartridge installed in the right- hand slot) is bad. If the test page is not printed, or the printer does not respond to the front panel, or the front panel does not display PS OFFLINE, do the following: 1 Turn the printer off and check for presence and correct installation of the two PostScript cartridges in the two slots on the front of the printer. (Note that power to the printer must be turned off in order to properly insert and remove PostScript cartridges.) 2 Check the graphic indicators on the front panel. Is the power on? Is the printer on line? What is the status of the print engine? 3 Recheck the hardware installation procedure. (Refer to Section 4.2.) 4 If all this fails to provide a solution to the problem, call your Digital Customer Service representative. Step 2: Check the printer hardware and software configurations Step 2 applies to the ScriptPrinter and DEClaser printers. It does not apply to the LN03 Image printer. Default configuration settings on the printer and in the software associated with the printer must be the same. To check the agreement, do the following: 1 Check the printed summary sheet to verify that the settings are consistent with the printer configuration switch settings: _ Paper size: letter (U.S.) or A4 (Europe) _ Communication: 9600 baud (or appropriate baud rate) _ Eight bits, no parity (required) Troubleshooting Procedures E-3 _ XON/XOFF protocol (required) See Table 4-1 for the default configuration switch settings. Power cycle the printer (turn it off and then on) so that the switches take effect. Refer to the printer operator's guide for information on how to change these settings. Note The DMZ32 printer interface, Revision E1 and lower, runs only at 4800 baud, and the DECserver 200 can run at 19200 baud. 2 For the ScriptPrinter printer, check the terminal device characteristics, by issuing this command on the node of the device: $ SHOW TERMINAL device-name[:] The variable device_name is the device name in the printer startup file in parameter p2 of the execution queue definition. The printer startup file CPS$STARTUP.COM is located in SYS$STARTUP. Check for the following characteristics: _ Eight bits _ Parity: None _ Input: 9600 baud _ Output: 9600 baud The summary sheet and the terminal settings should be the same. Refer to the SET TERMINAL command in the VMS DCL Dictionary for information on changing the system's interpretation of the device characteristics. If your printer interface runs at a different speed, make sure you set the configuration switch settings and the terminal device characteristics the same. For a DEClaser printer, refer to Section 4.2 for the correct front panel settings. 3 For a DEClaser printer, make sure the connector on the DEClaser printer is an H8571E. (Refer to the DEClaser 2200 Printer Installation Guide.) Hardware requirements for installing DEClaser printers are described in Section 2.1.1. E-4 Troubleshooting Procedures 4 Check the baud rate setting in the printer startup command file. If you did not enter a baud rate in parameter p6 of the execution queue definition, the startup procedure sets the printer speed at 9600 baud. For information on how to change default settings, see Section 4.1.3. 5 If your printer uses a DECserver on a local area Ethernet, check the DECserver port and server characteristics to verify that they also match. Changing DECserver characteristics requires privileges. Refer to the user's manual for your particular DECserver for information on how to check and change DECserver port and server data transmission characteristics. For DECserver port characteristics required when you use a port dedicated to printing, see Section 4.7. If the settings agree and the job still does not print, go on to step 3. Step 3: Check communications software | Serialt the operation of the communications equipment by | printerspting to send data directly to the device. For example, | onlyssue the SET HOST/DTE command or copy a PostScript file | | to the printer device. Use the commands in the following | example: | | $ SET HOST/DTE LTA9092: | Connection established, type ^\ to exit | Ctrl/T | %%[ status: idle ]%% | ^\ | $ COPY TT: LTA9092: | showpage | Ctrl/Z | $ | Step 4: Check CPS$STARTUP.COM AllMake sure that the CPS$STARTUP.COM file reflects your printers queue needs and that the changes are appropriate for your printer. To check the printer execution queue characteristics, perform the following instruction, inserting the name of the printer execution queue: $ SHOW QUEUE/FULL exec-queue-name Troubleshooting Procedures E-5 For example, the characteristics for the printer execution queue TXA1_LN03R on host EDEN are as follows: $ SHOW QUEUE/FULL TXA1_LN03R Printer queue TXA1_LN03R, on EDEN::TXA1: /BASE_PRIORITY=4 /FORM=CPS$DEFAULT /LIBRARY=CPS$DEVCTL /OWNER=[SYSTEM] /PROCESSOR=CPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(BURST,TRAILER) $ Specifically, check the following: _ Make sure that /PROCESSOR=CPS$SMB. _ Check that /FORM is as above or reflects changes made to the printer startup command file and is suitable for the operation of your printer. _ Make sure that the /LIBRARY qualifier is the same as parameter p3 in CPS$STARTUP.COM, and that the library logical name has been defined. If the queue characteristics do not match those in CPS$STARTUP.COM, stop the printer execution queue. Next, execute the CPS$STARTUP.COM file: $ @SYS$STARTUP:CPS$STARTUP Check the execution queue characteristics again. If the characteristics are correct and the job still does not print, go to step 6. Step 6: Check queue logical defaulting AllCheck the queue logical names (/PARAMETERS) in CPS$STARTUP.COM printersrameter p4 of the execution queue definition and parameter p3 of the generic queue definition. These parameters provide values for the LPS$queue-name_PARAMETER logical names. For information, see Section 5.6. Step 7: Check the queue configurations AllThe values provided in CPS$STARTUP.COM are not validated, but printersy passed as parameters to the appropriate VMS commands and utilities. Therefore, the VMS commands and utilities detect and report any errors directly. Refer to the VAX/VMS System Messages and Recovery Procedures Reference Manual for an explanation of error messages issued by the following DCL commands: E-6 Troubleshooting Procedures _ INITIALIZE/QUEUE _ SET TERMINAL _ SET DEVICE Note To debug DCL command procedures and record the information in a file, you can use the following commands: $ SET HOST 0/LOG $ SET VERIFY Or, set parameter p8 in the execution queue definition in CPS$STARTUP.COM to 1. (Refer to Table 5-1.) E.1.2 The Printer Has Stopped Printing When your printer stops printing, follow these steps: _ If your printer fails consistently, follow the steps in Section E.1.1. _ If your printer fails occasionally, follow the steps in this section. After checking all messages, including the notification messages from the PRINT command, the console output, and the OPCOM log, go on to step 1 if the cause of the problem is not apparent. Step 1: Print the IVP data sheets AllPrint the following Installation Verification Procedure (IVP) printers from SYS$COMMON:[SYSTEST.CPS]: _ CPS$IVP_ANSI.DAT _ CPS$IVP_DDIF.DAT _ CPS$IVP_POST.DAT _ CPS$IVP_REGIS.DAT | _ CPS$IVP_TEK4014.DAT | | _ CPS$IVP_PCL.DAT Remember to use the appropriate DATA_TYPE parameter value, indicated in the file name following the underscore, for each of the files. For example to print CPS$IVP_REGIS.DAT, use the following PRINT command: Troubleshooting Procedures E-7 $ PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=REGIS)- /NOTIFY SYS$COMMON:[SYSTEST.CPS]CPS$IVP_REGIS.DAT If the files are not printed, go to step 2, to check the files for user error. If any one of the IVP files is not printed, check to see if the translator execution files exist, using the following command: $ DIR SYS$SHARE:TRN$*.* | Directory SYS$COMMON:[SYSLIB] | | TRN$ANSI_PS.EXE; TRN$DDIF_PS.EXE; TRN$REGIS_PS.EXE; | TRN$TEK4014_PS.EXE; TRN$PCL_PS.EXE; | | Total of 4 files. | If the correct files are present, go on to step 2. If any files are missing, reinstall the DECprint Printing Services software. Step 2: Check files for user error AllIf a particular file fails to print, examine the trailer page printersthe print job for messages indicating the cause of the failure. For an explanation of, and recovery procedures for the error messages, see the system messages chapter of the DECprint Printing Services User's Guide. If the file is a PostScript file, an error exists in either the PostScript file or in the application that generated the PostScript file. If the application is supplied by Digital, submit a Software Performance Report. If the file is other than a PostScript file, an error exists in the translation process. If the translator is supplied by Digital, submit a Software Performance Report. E.2 Printing Is Slower Than Expected AllSlower printing speeds can result from the printing of jobs printerse following instances: _ Complex ANSI jobs from applications _ Complex PostScript jobs _ ANSI translator prologue mismatch E-8 Troubleshooting Procedures Complex ANSI jobs include those that make use of many downloaded fonts on a page. These jobs always take longer to print. Serial serial printers, a 30-second delay before the printing printersSI jobs indicates an ANSI prologue mismatch between the ANSI translator and the print job. On a serial printer, power cycle the printer (turn it off and then on) to cause loading of the appropriate prologue. The first ANSI print job will be delayed for loading the prologue, but subsequent ANSI print jobs will be printed more efficiently. If your printer is connected to multiple nodes running different versions of Common Print Symbiont (CPS) software, power cycling the printer may not eliminate the 30- second delay. The node that connects to the printer first persistently loads its prologue. The other nodes must load the prologue with every print job. To eliminate the delay in this case, every node should run the same version of the DECprint Printing Services software. E.3 Layup Definition Files Are Not Found DECprint Printing Services software places the following sam- ple layup definition files in SYS$SYSDEVICE:[SYSHLP.EXAMPLES.CPS]: _ LPS$HOLES.LUP _ LPS$SINGLEHOLES.LUP _ LPS$DOUBLEHOLES.LUP _ LPS$NUP.LUP Make sure that the logical layup definition, LPS$LAYUP, points to SYS$SYSDEVICE:[SYSHLP.EXAMPLES.CPS] or to the directory that contains the .LUP sample files on all nodes in the cluster. E.4 Printer Is Not Printing in Network Environment Serialetwork environment allows several separately managed printersms to access the same serial printer. Therefore, when onlyhe printer is not printing, you must determine which node has control of the printer, to troubleshoot the printer. The remaining sections discuss the following steps in troubleshooting the printer in a network environment: 1 Determining the node that controls the printer _ Determine printing node Troubleshooting Procedures E-9 _ Determine DECserver and DECserver port name _ Check port and system server names _ Determine host controlling printer at DECserver or over the network 2 Troubleshooting the printer _ Follow procedures in Section E.1 _ Check port characteristics 3 Other troubleshooting hints _ DEVICE UNAVAILABLE status _ Common error messages with their probable causes E.4.1 Determining Which Host Controls the Printer Serialform the following steps to determine which host has printersol of the printer. onlytep 1: Determine your printing node To determine which node runs your printer, issue the following command, inserting the name of the print queue you use: $ SHOW QUEUE/FULL queue-name From the first line of the following sample display, you determine that FIERY is the node that runs your printer and LTA546 is the application port associated with the print queue: Printer queue LN03R3, on FIERY::LTA546, mounted form CPS$DEFAULT (stock=DEFAULT) /BASE_PRIORITY=4 /FORM=CPS$DEFAULT (stock=DEFAULT) /NOENABLE_GENERIC /LIBRARY=CPS$DEVCTL lowercase /OWNER=[SYSTEM] /PROCESSOR=CPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(BURST,TRAILER) $ Perform steps 2 and 3 on the node (FIERY) that runs the printer. E-10 Troubleshooting Procedures Step 2: Determine DECserver and DECserver port name to which the printer is connected Look in SYS$MANAGER:STARTLAT.COM. The SET PORT command associates the application port (LTAd) with a specific port (/PORT=port_name) on the server (/SERVER=server_name). CREATE PORT LTA546: /NOLOG /APPLICATION ! LN03R3 SET PORT LTA546: /APPLICATION /QUEUE /NODE=TAS204 /PORT=PORT_7 Note The port must be set with queuing enabled (/QUEUE) and as an application port (/APPLICATION). Make sure that SYSTARTUP_V5.COM includes @LTLOAD. Step 3: Check port and server system names Ensure that port and server system settings are the same as those in SYS$MANAGER:STARTLAT.COM. Use the LATCP SHOW PORT command to look at the application port (LTAd) as follows: $ RUN SYS$SYSTEM:LATCP LCP>SHOW PORT lta546 Local Port Name = LTA546: application Specified Remote Node Name = TAS204 Specified Remote Port Name = PORT_7 Actual Remote Node Name = TAS204 Actual Remote Port Name = PORT_7 Link Name = LAT$LINK Step 4: Determine which host controls the printer You can determine which host controls the printer by logging in to a terminal that is connected directly to the DECserver or by connecting to the DECserver over the network. At the DECserver terminal At the DECserver terminal, issue the following command: LOCAL> SHOW SESSIONS PORT port_number The first line of the display shows the port number, the user name of the port, the port mode (local or service), and the session number. Example E-1 shows a SHOW SESSIONS PORT command on a DECserver 200 that tells you that a remote system HAILEY controls Port 7. Troubleshooting Procedures E-11 Example E-1 Determining Printer Host Local> SHOW SESSIONS PORT 7 Port 7: (Remote) Connected Current Session 1 -Session 1: Hailey Connected Pasthru Over the network Use either the network control program (NCP) or Terminal Server Manager (TSM) to connect to the DECserver over the network. To use NCP, issue the following commands: _ To determine the type of service_circuit, for example UNA-0 or QNA-0, use the following commands: $ MCR NCP NCP> SHOW KNOWN CIRCUITS _ To determine the 48-bit Ethernet address (for example, 08-00-2B-05-C7-05), use the following commands: $ MCR LATCP LCP> SHOW SERVERS $ MCR NCP NCP> CONNECT VIA service-circuit - PHYSICAL ADDRESS 00-00-00-00-00-00 After entering the NCP CONNECT command, press until you get the pound sign (#) prompt. At this prompt type the password (ACCESS) to get the Local> prompt: # username: username Local> After making your connection and logging in to the DECserver console, give the following commands: Local> SET PRIVILEGED Password> Local> SHOW SESSIONS PORT_7 This password is SYSTEM by default. See Example E-1 for a sample output of this command. E-12 Troubleshooting Procedures If your system runs the TSM software, issue the following commands: $ RUN SYS$SYSTEM:TSM$MAIN TSM> USE SERVER tas204 TSM> SET PRIVLEDGED Password> TSM> SHOW SESSIONS PORT_7 The password is SYSTEM by default. See Example E-1 for a sample output from this command. Note To run the TSM program you need read access to the TSM management directory file and OPER privileges. For more information, refer to the Guide to Terminal Server Manager. E.4.2 Troubleshooting the Printer After determining which system controls the printer port, follow these steps. Step 1: Check port characteristics Compare the DECserver port characteristics with those listed in Table 4-3. To view the port characteristics, issue the SHOW PORT command at the Local> prompt or the TSM> prompt. Step 2: Use procedures in Section E.1 The manager of the system, determined by following the steps in Section E.4.1, should start with the following: _ For a new printer - Section E.1.1 _ For a printer that has stopped printing - Section E.1.2 If you follow these procedures and the printer is not printing, go to step 2. E.4.2.1 Regaining Control of the DECserver Port You may need to disconnect a symbiont process that controls the port connected to the printer. For example, an earlier version of The ScriptPrinter software does not disconnect once it gains control of the port. Disconnect the symbiont process with the following command: Local> SET PRIVILEGED Password> Local> LOGOUT PORT port_number Troubleshooting Procedures E-13 You need privileged status on the DECserver to execute this command. E.4.3 Common DECserver Error Messages Seriallowing is a list of common error messages received in a printersrk environment. | only | _ CPS$_LRJINUSE, Port or service in use | | This message usually occurs on a DECserver port when port_ name is not set with the queuing parameter (/QUEUE) enabled, or when the queue limit is too small. The DECserver configuration file STARTLAT.COM should contain a line similar to the following: SET PORT LTAxxx:/NODE=server/PORT=port_name- - /QUEUE/APPLICATION | _ CPS$_LRJNOTOFFERED, Service is not offered on the | | requested port This message usually occurs when the access mode is not set to REMOTE on the DECserver port. Use the SET and DEFINE commands as follows to set the access mode for the port: Local> SET PORT port_name ACCESS REMOTE Local> DEFINE PORT port_name ACCESS REMOTE | _ CPS$_LRJACCESSDENIED, Access denied | | This message usually occurs when the group code specified | in STARTLAT.COM does not match one of the groups on the | DECserver connected to the printer. Thus, the printer | software does not have access to the DECserver port. The | DECserver configuration file STARTLAT.COM should contain a | line similar to the following: | | SET NODE/GROUP=group_list/ENABLE | Compare groups, /GROUP= group_list, set in STARTLAT.COM | with those set on the DECserver (SHOW PORT command). | | _ CPS$_CONTERMINATED, Connection abnormally terminated E-14 Troubleshooting Procedures | This message occurs when communication to the DECserver is interrupted. This results in a stopped queue. Check the following: _ Power is supplied to the DECserver _ Printer port is not logged off _ DECserver is plugged into the transceiver, DELNI, or DESTA _ All connections from DECserver to the Ethernet cable are working _ CPS$_CONTIMEOUT, Connection timed out, server not available, or incorrect server name specified This message occurs when the server name is not recog- nized. This problem may indicate the collision of user terminal space and the printer port. Verify that the server name connected to the printer port is correct. Compare the server name specified in the DECserver configuration file STARTLAT.COM with the server name on the DECserver. STARTLAT.COM should contain a line similar to the following: SET PORT LTAxxx:/NODE=server_name/PORT=port_name - /QUEUE/APPLICATION Use the SHOW PORT command to find the server name associated with the printer port: Local> SHOW PORT port_name | _ CPS$_CONAPPLICATION, Connection request is not to a LAT | | applications port This message usually occurs on a DECserver port when the LTAxxx is not reserved as an applications port, and an interactive terminal is connected to the port that is requested by the printer. The DECserver configuration file STARTLAT.COM should contain a line similar to the following with the /APPLICATION parameter. SET PORT LTAxxx:/NODE=server-name/PORT=port-name/QUEUE/APPLICATION To avoid this problem, specify a higher port number for | the printer. | | _ CPS$_LRJNAMEUNKNOWN, Port Name is unknown Troubleshooting Procedures E-15 This message occurs when the port name specified in the DECserver configuration file STARTLAT.COM is not known on the server. Compare the port name specified in the DECserver configuration file STARTLAT.COM with the printer port name associated with the server. STARTLAT.COM should contain a line similar to the following: SET PORT LTAxxx:/NODE=server_name/PORT=port_name/QUEUE/APPLICATION Find the name of the printer port associated with the server, by issuing the following command: Local> SHOW SERVER server_name | _ CPS$_LRJDELETED, Queue entry deleted by server This message occurs when someone manually terminates your | connection to the DECserver. | | _ CPS$_LRJILLEGAL, Illegal request parameter | | This message indicates that an internal printer error has occurred. Submit a Software Performance Report. Note For more information, refer to the system messages chapter in the DECprint Printing Services System Manager's Guide or to the troubleshooting guide for your DECserver. E.5 Eliminating Login Dialog on Serial Printers Serial serial printer transmits unsolicited data to the host printersm when power-up initialization occurs. The VMS operating onlyystem normally interprets unsolicited data from a terminal device as a login request. The printer software startup file sets the SECURE_SERVER terminal characteristic for all printer terminal devices on the host system. SECURE_SERVER prevents the VMS host and the printer from engaging in a potentially endless login dialog. To eliminate login dialog, set terminal characteristics for terminal devices by using the following in this order: 1 SYSGEN AUTOCONFIGURE 2 SYSTARTUP_V5 3 CPS$EXECUTION_QUEUE.COM E-16 Troubleshooting Procedures AUTOCONFIGURE uses SYSGEN parameters to set default terminal characteristics for all terminal devices on the system. Your system will not encounter the login dialog problem if SECURE_SERVER is set at this time. The SYSGEN parameter that accomplishes this is TTY_DEFCHAR2. Refer to the Guide to VAX/VMS Software Installation for information on setting SYSGEN parameters. The system startup procedure may also set terminal char- acteristics. Since this command file executes prior to the printer startup file, your system will be less vulnerable to the login dialog problem if SECURE_SERVER is set for printer terminal devices within the SYSTARTUP_V5 file. CPS$EXECUTION_QUEUE.COM (the printer execution queue command file) sets the SECURE_SERVER terminal characteristic for printer terminal devices by default. This file is provided in the software kit. If your printer is configured on a DECserver in a local area Ethernet, set the DECserver port and the terminal server characteristics for the printer to minimize login dialog. Refer to Section 4.7.2 for DECserver port characteristics. E.6 PrintServer Troubleshooting Procedures PrintServerowing troubleshooting procedures are provided to onlyiagnose error conditions that can occur during installation of DECprint Printing Services software for PrintServer printers. E.6.1 Printer Is Not Printing Jobs | | If the Printer is not printing, check the OPCOM messages. If | the cause of the failure is not immediately apparent, perform | the following steps: Step 1: Check the PrintServer device queue characteristics. Execute the following instruction, inserting the name of the PrintServer device queue: $ SHOW QUEUE dev-queue-name/FULL For example, the characteristics for the PrintServer device queue LPS40$FANG on node VIPER are as follows: $ SHOW QUEUE LPS40$FANG/FULL Troubleshooting Procedures E-17 | Printer queue LPS40$FANG, on VIPER::FANG, mounted form CPS$$FORM | (stock=DEFAULT) | /BASE_PRIORITY=4 /FORM=CPS$DEFAULT /LIBRARY=CPS_LIB /OWNER=[SYSTEM] | /PROCESSOR=CPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) | /SEPARATE=(FLAG,TRAILER) | $ | | If the queue characteristics do not match, delete the | device queue and all generic queues that point to it. Then | execute the CPS$STARTUP.COM file. CPS$STARTUP is located in | SYS$STARTUP:. For example: $ STOP/RESET/QUEUE generic-queue-1 $ STOP/RESET/QUEUE other-generic-queues $ STOP/RESET/QUEUE LPS40$pserver-name $ DELETE/QUEUE generic-queue-1 $ DELETE/QUEUE other-generic-queues | $ DELETE/QUEUE LPS40$pserver-name | $ @SYS$MANAGER:CPS$STARTUP Recheck the queue characteristics. If they are correct and the job still does not print, refer to the Management Guide: VAX PrintServer Supporting Host for further information. E-18 Troubleshooting Procedures ___________________________________________________________ Index B DECserver (Cont.) Baud rate limitations, 4-2 port characteristics required for printing, C 4-11 Changing terminal server, 4-10 default queue parameters, Default qualifiers, 5-12 changing, 5-15 default queue qualifiers, Defining library search 5-15 list, 5-5 Communications setting, for Device control modules, ScriptPrinter, 4-2 customized, 5-6 Conventions, xi Device name, specifying, CPS$STARTUP 5-8 editing, 5-3 DIP switch communication renaming, 5-3 settings Custom device control changing the default, 4-3 modules, 5-6 default, 4-2 Disk space requirements, D 3-2 DECserver Index-1 E J Ethernet use, serial Job not printing, E-17 printers, 4-9 Job queue manager Execution queues, 5-1, 5-7 starting, 5-2 defining /ON qualifier, L 5-8 example, 5-9 LAT protocol file, editing F the, 4-13 LAT startup file, 4-10 Files, added during Library, added during installation, D-1 installation, D-4 G Library search list, in startup file, 5-5 Generic queues, 5-2 LN03 Image printer defining, 5-11 overview, 1-5 example, 5-11 software requirements, I 2-3 SYSGEN parameters, 4-6 Image printer, overview, LN03R 1-5 See ScriptPrinter, 1-7 Installation procedure LPS$LAYUP logical, 3-6 messages (See Messages) M files created during, D-1 Messages, 6-1 library created during, descriptions, 6-2 to 6-7 D-4 format, 6-1 questions, 3-3 severity level, 6-2 sample session, A-1 Installation procedure N questions, 3-9 Installation requirements New files and libraries, hardware, 2-1 D-1 software, 2-3 Not ready status, E-2 Installation verification O output, C-1 /ON qualifier, 5-8 Index-2 OPCOM messages Queue (Cont.) new printer, E-1 See print queue not ready status, E-2 Queue logical names, E-6 P default, 5-12 parameters Port characteristics, 4-11 defaulting order, 5-14 Postinstallation syntax, 5-13 requirements redefining, 5-12 printer startup file, 5-3 Queue qualifiers, default, Preinstallation 5-15 requirements, 2-1 Queue structure Printer defining execution queues hardware requirements, , 5-7 2-1 defining generic queues, queues, 5-1 5-11 software requirements, R 2-3 Printer name Reducing login dialog, E-16 how to set, 4-7 Reinstallation requirements Printer queue , 3-11 commands, 5-2 S parameters default, 5-14 ScriptPrinter syntax errors, 5-13 overview Printer queues communications changing default settings, how to parameters, 5-12 determine, 4-2 execution, 5-1 speed, changing, 4-2 generic, 5-2 Serial printers parameters use on Ethernet, 4-9 syntax, 5-13 Software Printer startup file, capabilities, 1-2 editing the, 5-3 distribution kit, 2-3 Q START/QUEUE/MANAGER command Queue , 5-2 Startup file Index-3 Startup file (Cont.) System startup file, defining execution queues editing the, 3-10 , 5-7 T defining generic queues, 5-11 Troubleshooting procedures Supported printers, 1-1 jobs not printing, E-1, SYSGEN parameters, checking E-17 and changing, 4-6 network environment, E-9 System messages U See Messages Upgrading procedures, 3-11 V VMSINSTAL conventions, 3-2 installation questions, 3-3 to 3-9 Index-4