PrintServer_Software_for_OpenVMS______________ Installation Guide Order Number: AA-PEAHE-TE This guide describes how to install the PrintServer Software for OpenVMS on a computer running the OpenVMS VAX or Alpha operating system. Revision/Update Information: This manual super- sedes order number AA-PEAHD-TE. Operating System and Versions:OpenVMS VAX, Version 5.5-2 and higher OpenVMS Alpha, Version 1.5 and higher Software Version: PrintServer Software for OpenVMS, Version 5.1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ Published 1991 Revised, May 1995 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1991, 1992, 1993, 1994, 1995. All Rights Reserved. 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: DEC, DECfonts, DECnet, DECprint, DECwindows, Digital, OpenVMS, PrintServer, MicroVAX, Q-bus, TK, ULTRIX, VAX, VAXcluster, VAX DOCUMENT, VAXELN, VMS, and the DIGITAL logo. Adobe and PostScript are trademarks of Adobe Systems, Incorporated, which may be registered in certain jurisdictions. UNIX is a registered trademark licensed exclusively by X/Open Complay Ltd. AIX and IBM are registered trademarks of International Business Machines Corporation. HP, HP-UX, and LaserJet are registered trademarks of Hewlett-Packard Company. Microsoft is a registered trademark of Microsoft Corporation. Windows and Windows NT are trademarks of Microsoft Corporation. Motif is a registered trademark of Open Software Foundation, Inc. NetWare and Novell are registered trademarks of Novell, Inc. OSF/1 is a registered trademark of Open Software Foundation, Inc. SCO is a trademark of Santa Cruz Operations, Inc. Sun and SunOS are registered trademarks of Sun Microsystems, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing to Install the Software 1.1 Client Connections........................... 1-1 1.2 Installation Time............................ 1-2 1.3 Privileges................................... 1-2 1.4 Disk Space................................... 1-3 1.5 Prerequisite Hardware........................ 1-3 1.6 Prerequisite Software........................ 1-5 1.7 Contents of the Software Kit................. 1-5 1.8 Obtaining Release Notes...................... 1-6 1.9 Installation Requirements.................... 1-6 1.9.1 Checking Logical Names................... 1-6 1.9.2 User Identification Code................. 1-7 1.10 Backing Up Your System Disk.................. 1-7 2 Installing the PrintServer Software 2.1 Installing the Software...................... 2-1 2.2 VMSINSTAL Errors............................. 2-9 2.2.1 Message Format........................... 2-10 2.2.2 Severity Level........................... 2-10 2.2.3 Message Descriptions..................... 2-10 iii 3 Configuring the PrintServer Printer 3.1 Invoking LPS$ADD_PRINTSERVER.COM............. 3-3 3.1.1 DECnet Node Name......................... 3-3 3.1.2 PrintServer Printer Type................. 3-4 3.1.3 DECnet Address........................... 3-4 3.1.4 Service Circuit.......................... 3-5 3.1.5 Ethernet Hardware Address................ 3-5 3.1.6 Summary of Network Database Information.............................. 3-6 3.1.7 Summary of Configuration Information..... 3-7 3.1.8 Printer Passwords........................ 3-9 3.1.9 Operator Panel Language ................. 3-10 3.1.10 Accounting Feature....................... 3-10 3.1.11 Event-Logging Feature.................... 3-10 3.1.12 Image Interpreter........................ 3-11 3.1.13 DECnet Access Restrictions............... 3-12 3.1.14 Providing Access from Internet Nodes..... 3-13 3.1.14.1 Internet Address....................... 3-13 3.1.14.2 Internet Subnet Mask................... 3-13 3.1.14.3 Internet Gateway Node Address.......... 3-13 3.1.14.4 Internet Access Restrictions........... 3-14 3.1.15 Simple Network Management Protocol....... 3-14 3.1.16 Saving Your Configuration Information.... 3-17 3.2 Enabling the Supporting Host Services........ 3-18 3.2.1 Enabling the Startup File - Standalone Node..................................... 3-18 3.2.2 Enabling the Startup File - VAXcluster Node..................................... 3-19 3.3 Configuring Multiple Supporting Hosts........ 3-19 3.4 Invoking LPS$UPGRADE_PRINTSERVER.COM......... 3-20 3.5 If You Are Upgrading, Stop and Restart Management Daemons........................... 3-21 3.6 If You Are Upgrading, Convert the NETSETUP Database..................................... 3-21 iv 4 Enabling LPD 4.1 Overview..................................... 4-1 4.2 Defining Local Print Queues.................. 4-1 4.3 Changing the Interpreter..................... 4-3 5 Booting the PrintServer Printer 5.1 Overview..................................... 5-1 5.2 Booting a PrintServer 17 Series Printer...... 5-1 5.3 Booting a PrintServer 20 Series or PrintServer 32 Series Printer ............... 5-3 5.4 Booting a PrintServer 40 Plus Printer........ 5-5 5.5 Determining and Reporting Problems........... 5-6 6 Troubleshooting the Software 6.1 If the Primary Boot Procedure Fails.......... 6-3 6.1.1 Step 1: Checking the Supporting Host Logical Names............................ 6-3 6.1.2 Step 2: Monitoring Network Events........ 6-3 6.1.2.1 Checking DECnet Phase V MOP............ 6-4 6.1.2.2 Checking the NCP Database.............. 6-5 6.1.2.3 Checking the Service Circuit........... 6-6 6.1.2.4 Enabling Network Event Reporting....... 6-7 6.1.2.5 Checking OPCOM Messages................ 6-8 6.1.2.6 Checking the Network Configuration..... 6-9 6.1.2.7 Determining If the Printer Booted...... 6-10 6.1.2.8 Shutting Down Remote Booting Services............................... 6-11 6.1.3 Step 3: Checking the Hardware Connections.............................. 6-11 6.2 If the Secondary Boot Procedure Fails........ 6-12 6.2.1 Checking that Phase V DECnet Addresses Have Been Added.......................... 6-12 6.2.2 Checking Configuration Services.......... 6-13 6.2.3 Checking the Management Client Status (LPS$SERVICES)........................... 6-13 6.2.4 Checking Management Client Connections... 6-14 6.2.5 Checking Management Client Versions...... 6-15 6.2.6 Restarting the Management Client......... 6-15 6.2.7 Examining the PrintServer Printer Event Log File................................. 6-16 v 6.3 If the Printer Boots and Crashes............. 6-18 6.4 If the Printer Displays "Ready" but Does Not Print........................................ 6-18 6.4.1 Internet Access Is Restricted ........... 6-19 6.4.2 DECnet Access Is Restricted.............. 6-19 6.4.3 Print Queues Are Not Set Up.............. 6-20 A Sample Installation Session B Files Added During Installation B.1 Utility Files................................ B-1 B.2 Informational Files.......................... B-3 B.3 Executable Files............................. B-3 B.4 PostScript Files............................. B-7 B.5 Remote Console Facility Help Pages (Files)... B-8 B.6 Data Files................................... B-10 C Obtaining the Ethernet Hardware Address C.1 Introduction................................. C-1 C.2 Obtaining the Ethernet Hardware Address from the Operator Panel........................... C-1 C.3 Obtaining the Ethernet Hardware Address from the Console Terminal ........................ C-2 C.3.1 Procedure................................ C-2 D Digital PostScript Printer Software Documentation D.1 Digital PostScript Printer Software Documentation................................ D-1 D.1.1 PrintServer Software for ULTRIX ......... D-1 D.1.2 PrintServer Software for OpenVMS ........ D-1 D.1.3 PrintServer Software for UNIX............ D-2 D.1.4 PrintServer Software for NetWare......... D-2 D.1.5 PrintServer Software for Windows......... D-2 D.1.6 PostScript Programming Documentation..... D-2 D.1.7 DECfonts Typeface Collection............. D-2 D.1.8 DECprint Supervisor Software for OpenVMS.................................. D-3 D.1.9 Digital ANSI-Compliant Level 3 Printing Protocol................................. D-3 vi Index Examples A-1 Sample Installation...................... A-1 Tables 1-1 Maximum Client Connections............... 1-2 1-2 Hardware Requirements for Installing the Software................................. 1-4 3-1 Configuration Data....................... 3-3 4-1 Queue Setup Information.................. 4-2 vii ________________________________________________________________ Preface This guide applies to PrintServer Software for OpenVMS, Version 5.1, and all subsequent maintenance releases up to the next major product release. Intended Audience This guide is for system managers who install PrintServer Software for OpenVMS, Version 5.1. You should be able to install the software, verify the installation, troubleshoot, and make any needed changes to system files. You should understand the installation utility VMSINSTAL, the network control program (NCP), and basic OpenVMS VAX and Alpha system management procedures. To install PrintServer Software for OpenVMS on a DECnet /OSI (DECnet Phase V) system, you should know the Network Control Language (NCL). Associated Products The following software products are associated with Digital's PrintServer family of printers: o PrintServer Software for: HP-UX IBM AIX Microsoft Windows NT NetWare OSF/1 Alpha SCO UNIX SCO UNIX/DECadvantage Solaris SunOS Silicon Graphics Irix vii ULTRIX o DECprint Supervisor for OpenVMS Conventions The following conventions are used throughout this guide: __________________________________________________________ Convention____Meaning_____________________________________ UPPERCASE The names of OpenVMS commands, files, and utilities are shown in uppercase letters. However, you can enter OpenVMS commands in either uppercase or lowercase letters. Italics Italics are used in examples to indicate that you are to substitute a word or value. [ ] Brackets in command syntax lines indicate that the enclosed item is optional. Courier Courier text (typewriter font) indicates user input and system output. In examples, this symbol indicates that you should press the Ctrl key while you simultaneously press another key, for example, Ctrl/Z. This symbol indicates that you should press ______________the_Return_key._____________________________ viii 1 ________________________________________________________________ Preparing to Install the Software This chapter describes the information and computing environment that you need before you install the PrintServer Software. 1.1 Client Connections Table 1-1 shows the maximum print clients, management clients, or console clients that can connect simulta- neously to a PrintServer printer. Any combination of management clients and console clients can connect to the printer. Preparing to Install the Software 1-1 Table_1-1_Maximum_Client_Connections______________________ Print Management Type_of_Printer__Clients_____Clients_____Console_Clients__ PrintServer 17 16[1] 4 5 PrintServer 16[1] 4 5 17/600 PrintServer 20 16 4 5 turbo 16 4 5 PrintServer 20[1] PrintServer 16 4 5 32[1] PrintServer 32 16 4 5 plus [1] PrintServer 40 16 4 5[2] Plus [1]The_number_of_print_client_connections_depends_on_the__ amount of memory in the printer. Base configurations have fewer connections. [2]This number includes the local console client and four remote console clients. __________________________________________________________ After the maximum number of connections is reached, the printer rejects client requests until a connection becomes available. 1.2 Installation Time Installation can take up to 20 minutes, depending on your type of media and system configuration. 1.3 Privileges You must have the following minimum privileges to install the software: o SYSPRV o SETPRV o CMKRNL 1-2 Preparing to Install the Software o WORLD VMSINSTAL disables the BYPASS privilege at the beginning of the installation procedure. 1.4 Disk Space You need 33,000 disk blocks to install the PrintServer Software. Issue the SHOW DEVICE command to display the current disk space. For example, if you intend to install the software on the system disk, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE You can install the software on a disk other than the system disk. 1.5 Prerequisite Hardware Table 1-2 describes the hardware items needed to install PrintServer Software. Preparing to Install the Software 1-3 Table 1-2 Hardware Requirements for Installing the __________Software________________________________________ Item_____________Explanation______________________________ PrintServer You can have one or more of the following printer types of PrintServer printers: PrintServer 40 Plus PrintServer 20 turbo PrintServer 20 PrintServer 32 PrintServer 32 plus PrintServer 17 PrintServer 17/600 Ethernet The supporting host configuration must controller include an Ethernet controller connected to a transceiver on the Ethernet. The supporting host must be on the same Ethernet network as the PrintServer printer.[1] Input device The supporting host system must include an input device that accommodates one of the following types of media: o TK50 cartridge o CD-ROM [1]The_PrintServer_printer_can_be_connected_to_a_different Ethernet than its supporting host when the two Ethernets are connected by a local area network (LAN) bridge that does not filter boot requests. Refer to Section 6.1.2.6. __________________________________________________________ 1-4 Preparing to Install the Software 1.6 Prerequisite Software The supporting host system must be running OpenVMS VAX, Version 5.5-2 and higher, or OpenVMS Alpha, Version 1.5 and higher. The system must be running DECnet software to run the PrintServer Software. Although the PrintServer Software can be installed on a VMS DECnet Phase V node, the PrintServer printer must be a DECnet Phase IV node. To run the remote console facility in windows mode, your system must have DECwindows Motif for OpenVMS, Version 1.1. 1.7 Contents of the Software Kit PrintServer Software is packaged in four save sets: __________________________________________________________ Save Set Name________Contents______________________________________ LPS051.A Installation procedures Release notes Help files PostScript files Utilities LPS051.B PrintServer executable files and system files LPS051.C Executable files for OpenVMS VAX platforms LPS051.D____Executable_files_for_OpenVMS_Alpha_platforms__ Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or you find that parts are missing, contact your Digital representative. Preparing to Install the Software 1-5 1.8 Obtaining Release Notes Digital recommends reading the release notes before installing the software. The VMSINSTAL procedure lets you print or display the release notes. After choosing the release notes option, you can terminate the installation dialog and run it again to install the software later. (Refer to Section 2.1.) The release notes are automatically copied to SYS$HELP. 1.9 Installation Requirements Before you invoke VMSINSTAL, make sure: o Your logical names are correctly defined. o You know the user identification code (UIC) for the LPS$SERVER account. 1.9.1 Checking Logical Names Make sure the following logical names are correctly defined: SYSUAF If SYSUAF is not defined as a logical name, define SYSUAF to point to the SYSUAF.DAT file. Otherwise, the installation assumes that the file SYSUAF.DAT is in the SYS$SYSTEM directory. $ SHOW LOGICAL SYSUAF %SHOW-S-NOTRAN, no translation for logical name SYSUAF $ DEFINE SYSUAF "file-specification" LPS$SUPPORT and LPS$ROOT If you are upgrading the software, make sure the logical names LPS$SUPPORT and LPS$ROOT are correctly defined. $ SHOW LOGICAL LPS$SUPPORT, LPS$ROOT "LPS$SUPPORT" = "SYS$SYSDEVICE:[LPS$SERVER]" (LNM$SYSTEM_TABLE) "LPS$ROOT" = "SYS$SYSDEVICE:[LPS$SERVER.]" (LNM$SYSTEM_TABLE) If the logicals are incorrectly defined, run the following command procedure: $ @SYS$STARTUP:LPS$STARTUP_SERVICES.COM LOGICALS 1-6 Preparing to Install the Software 1.9.2 User Identification Code If this is the first time you have installed the software on this system, you must supply a user identification code (UIC) for the LPS$SERVER account. The UIC contains a group number and a member number as follows: [group,member] The installation procedure provides a default UIC value of [477,477]. To select a different group number for the LPS$SERVER account, check the System Generation utility (SYSGEN) MAXSYSGROUP parameter, as follows: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW MAXSYSGROUP Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- MAXSYSGROUP 8 8 1 32768 UIC Group D Then, choose a number that is greater than the current MAXSYSGROUP value. 1.10 Backing Up Your System Disk Digital recommends that you back up the system disk before you install any software. Use the backup procedures established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management Subkit. Preparing to Install the Software 1-7 2 ________________________________________________________________ Installing the PrintServer Software This chapter explains how to install the PrintServer Software, with step-by-step instructions. This chapter also describes the conditions under which errors can occur. 2.1 Installing the Software To install the PrintServer Software, perform the following steps. To get help during this installation, enter a question mark (?) at any time. To terminate the installation, press ; the installation procedure deletes any files it has created and exits VMSINSTAL. 1. Invoke VMSINSTAL. To start the installation, invoke the VMSINSTAL command procedure from the system manager's account. $ @SYS$UPDATE:VMSINSTAL LPS051 device-name OPTIONS N Installing the PrintServer Software 2-1 The following list defines the elements of the VMSINSTAL command line: LPS051 is the save set name. device-name is the name of the device on which you plan to mount the media, such as MUA0:. OPTIONS N allows you to request release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. Review the release notes before proceeding with the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. 2. Continue the installation. The VMSINSTAL display tells you that you can enter a question mark (?) at any time for help. It displays a list of all active processes. VAX/VMS Software Product Installation Procedure V5.5-2 It is 01-DEC-1995 at 11:07. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$TE_1 TWA5: GILROY DECW$WM_1 SMITH_SM1 * Do you want to continue anyway [NO]? ? To continue the installation, enter Yes. To terminate VMSINSTAL, enter No or press . If you respond with a question mark (?), VMSINSTAL displays this explanation: 2-2 Installing the PrintServer Software 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. Furthermore, the existence of other processes may lead to interactions with VMSINSTAL that cannot be anticipated. If you continue at this point, you do so at your own risk. * Do you want to continue anyway [NO]? Y 3. Confirm system backup. VMSINSTAL asks if you are satisfied with your system backup. If you are satisfied with the backup of your system disk, press . Otherwise, enter No to terminate the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? ? If you respond with a question mark (?), VMSINSTAL displays this 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. * Are you satisfied with the backup of your system disk [YES]? Y 4. Mount the media. VMSINSTAL now asks you to mount the first distribution volume on the device you specified when you invoked the VMSINSTAL procedure. Please mount the first volume of the set on MUA0:. * Are you ready? Y %MOUNT-I-MOUNTED, LPS051 mounted on _MUA0:. The following products will be processed: LPS V5.1 Beginning installation of LPS V5.1 at 11:09 %VMSINSTAL-I-RESTORE, Restoring product save set A ... VMSINSTAL displays the name of the product that will be processed. Then it restores the contents of product save set A. Finally, VMSINSTAL asks you to select one of the release notes options. Installing the PrintServer Software 2-3 5. Select a release notes option. If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the options for reviewing the release notes. Regardless of the option you choose, VMSINSTAL copies the release notes to SYS$HELP. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2 VMSINSTAL then asks if you want to continue the installation. 6. Continue the installation. * Do you want to continue the installation [NO]?: Y To continue the installation, enter Yes; otherwise, press . In either case, the product's release notes are copied to a file in the SYS$HELP directory: SYS$HELP:LPS051.RELEASE_NOTES VMSINSTAL displays a message telling you that the release notes have been moved successfully to SYS$HELP. VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 7. Purge files. * Do you want to purge files replaced by this installation [YES]? Y VMSINSTAL asks if you want to purge files replaced by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter No in response to the question. If you respond with a question mark (?), VMSINSTAL displays this explanation: 2-4 Installing the PrintServer Software 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. If this is an upgrade, proceed to the informational messages (step 10). For a new installation, the VMSINSTAL procedure asks the following questions (steps 8 and 9). 8. Enter a user identification code (UIC) for LPS$SERVER account. This question is asked only if this is the first installation of the software on this system. You can either accept the default UIC or enter one of your own choosing within a valid range and in the proper format. The system displays the following information for choosing a UIC: This installation will create an account named LPS$SERVER. The UIC of this account will be used by the management client process to provide the PrintServer with its secondary boot files and to create event log and accounting files on this supporting host system. You must specify a unique UIC for this account. In order to maintain proper system security, please choose a UIC with a group number that does not give the account system privileges. Enter the UIC for LPS$SERVER account (include brackets) [[477,477]]: If you press in response to this question, the default UIC [477,477] is assumed. 9. Enter a default device for the LPS$SERVER directory. This question is asked only if this is the first installation of the software on this system. You can either accept the default disk device (SYS$SYSDEVICE) or enter one of your own choosing. Installing the PrintServer Software 2-5 Enter the name of one of the disk devices available on your host system. Be sure that the device you specify has at least 33,000 blocks. Enter the device name where the supporting host directory will be created [[SYS$SYSDEVICE]]: 10.Read informational messages. At this point, the installation procedure displays information about the progress of the installation. There are no further questions. If this is a new installation . . . If this is a new installation, VMSINSTAL displays messages pertaining to account creation as follows: %LPS-I-NO_MORE_QUESTIONS, No further questions will be asked during this installation. %LPS-I-ESTTIME, This installation will take approximately 20 minutes. %LPS-I-CREATE_ACCOUNT, Creating LPS$SERVER account for the PrintServer Supporting Host %VMSINSTAL-I-ACCOUNT, This installation creates an account named LPS$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier LPS$SERVER value: [000477,000477] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named LPS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %LPS-I-ADD_LOGICALS, Creating the LPS$SUPPORT and LPS$ROOT logicals. %VMSINSTAL-I-SYSDIR, This product creates system disk directory LPS$ROOT:[CAT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory LPS$ROOT:[SYS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[SYSHLP.EXAMPLES.LPS]. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... When the installation is finished, VMSINSTAL displays the following: The installation of PrintServer Software for OpenVMS has completed successfully. 2-6 Installing the PrintServer Software Next, VMSINSTAL displays information about the postinstallation procedure. This procedure is described in Chapter 3. The installation of PrintServer Software for OpenVMS has completed successfully. For both an upgrade and new installation, you must perform the following steps: * Execute SYS$MANAGER:LPS$ADD_PRINTSERVER.COM for each new PrintServer printer. * Execute SYS$MANAGER:LPS$UPGRADE_PRINTSERVER.COM for each existing PrintServer printer you want to upgrade to PostScript Level 2. * Your system-specific startup command file must call the supporting host startup file, SYS$STARTUP:LPS$STARTUP_SERVICES.COM. * Execute SYS$MANAGER:LPS$STOP_DAEMON.COM and SYS$STARTUP:LPS$STARTUP_SERVICES.COM and reboot the PrintServer printers. Failure to follow the above steps may prevent your PrintServer printers from booting. Please refer to the PrintServer Software for OpenVMS Installation Guide for further instructions. If you are performing an upgrade . . . If you are performing an upgrade, the following lines are displayed instead: %LPS-I-NO_MORE_QUESTIONS, No further questions will be asked during this installation. %LPS-I-ESTTIME, This installation will take approximately 20 minutes. %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named LPS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %LPS-I-SH_LOGICAL_EXISTS, The LPS$SUPPORT logical exists. Assume it is correct. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Installing the PrintServer Software 2-7 When the installation is finished, VMSINSTAL displays the following: The installation of PrintServer Software for OpenVMS has completed successfully. Next, VMSINSTAL displays information about the postinstallation procedure. This procedure is described in Chapter 3. The installation of PrintServer Software for OpenVMS has completed successfully. For both an upgrade and new installation, you must perform the following steps: * Execute SYS$MANAGER:LPS$ADD_PRINTSERVER.COM for each new PrintServer printer. * Execute SYS$MANAGER:LPS$UPGRADE_PRINTSERVER.COM for each existing PrintServer printer you want to upgrade to PostScript Level 2. * Your system-specific startup command file must call the supporting host startup file, SYS$STARTUP:LPS$STARTUP_SERVICES.COM. * Execute SYS$MANAGER:LPS$STOP_DAEMON.COM and SYS$STARTUP:LPS$STARTUP_SERVICES.COM and reboot the PrintServer printers. Failure to follow the above steps may prevent your PrintServer printers from booting. Please refer to the PrintServer Software for OpenVMS Installation Guide for further instructions. 2-8 Installing the PrintServer Software 11.End of the installation procedure. The following messages indicate the installation procedure is complete: %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LPS V5.1 completed at 11:33 VMSINSTAL procedure done at 11:33 VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, to continue using the system manager's account and restore these symbols, log out and log in again. Continue to the next chapters to configure the software and boot the printer. 2.2 VMSINSTAL Errors If errors occur during the installation, VMSINSTAL displays error messages. If the installation fails, the following message displays: %VMSINSTAL-E-INSFAIL, The installation of LPS051 has failed. Errors can occur during the installation if any of the following conditions exist: o Insufficient disk space is allocated. o The operating system version is incorrect. o System parameter values are insufficient for successful installation. o The VMS help library is currently in use. The following sections describe the error messages and explain how to correct any problems. Installing the PrintServer Software 2-9 2.2.1 Message Format System messages issued during the installation procedure have the following format: %LPS-s-ident, text The symbols used in the message format are explained as follows: __________________________________________________________ This Symbol . . . _________________Is_the_._._._____________________________ % Prefix to all primary messages. LPS Source designation of the messages. s Severity level of the message. ident Abbreviation of the message text. text_____________Expanded_text_of_the_message.____________ 2.2.2 Severity Level VMSINSTAL messages have one of the following severity levels: __________________________________________________________ Code__Meaning_____Explanation_____________________________ S Success The request has been completed successfully. I InformationaUser action may be required. W Warning The request may not have been completed and may require user action. E Error The system encountered an error that may be recoverable. F Fatal The system encountered a fatal error and __________________cannot_continue_processing_this_request. 2.2.3 Message Descriptions The following message descriptions are alphabetized by the ident portion of the message code. The message prefix, source designation, and severity code are not shown. 2-10 Installing the PrintServer Software ADD_LOGICALS, Creating the LPS$SUPPORT and LPS$ROOT logicals. Explanation: This is an informational message. The installation procedure is defining these logicals. User Action: None. BADACC, The existing LPS$SERVER account cannot be used. Please delete or repair it before reattempting the installation. Explanation: The installation procedure cannot find the LPS$SERVER account's default directory. The installation is aborted. User Action: Make the directory accessible. If that is not possible, delete the LPS$SERVER account and restart the installation. BADUAF, Serious problem with system authorization file. Explanation: The system authorization file (SYSUAF.DAT) could not be located, could not be accessed, or had a problem that caused the Authorize utility to fail when attempting to update it. User Action: Check to see if the SYSUAF.DAT file is accessible (see Section 1.9.1). If this file exists and the system logicals are set up, call your Digital Services representative. The software installation procedure cannot succeed until this problem is solved. CREATE_ACCOUNT, Creating LPS$SERVER account for the PrintServer Supporting Host. Explanation: This is an informational message. The LPS$SERVER account is added to the SYSUAF file. User Action: None. ESTTIME, This installation will take approximately 20 minutes. Explanation: This is an informational message. It displays the approximate time to complete the VMSINSTAL procedure. User Action: None. Installing the PrintServer Software 2-11 EXISTS, The LPS$SERVER account already exists with the default directory device-name:[LPS$SERVER]. Explanation: This is an informational message. A version of the PrintServer Software is already installed on this system. User Action: None. NO_DISK_DEVICE, Not a valid device. Explanation: The device name you selected is not valid. User Action: Enter a valid device name. NO_DISK_SPACE, LPS 5.1 requires 33,000 disk blocks for this installation. Explanation: Not enough disk blocks are available to install this software. The installation requires at least 33,000 disk blocks on the installation device. The installation procedure is automatically terminated. User Action: Make sure you have at least the specified number of free disk blocks and restart the installation. NO_MORE_QUESTIONS, No further questions will be asked during this installation. Explanation: This is an informational message. You are not asked any more questions during the installation procedure. User Action: None. NO_SH_LOGICAL, The LPS$SUPPORT logical does not exist. Explanation: The installation procedure could not find the definition for LPS$SUPPORT during an upgrade. User Action: None. The installation procedure creates one automatically. SH_LOGICAL_EXISTS, The LPS$SUPPORT logical exists. Assume it is correct. Explanation: The installation procedure found a definition for LPS$SUPPORT. User Action: No action is required if the logical defini- tion is correct (see Section 1.9.1.) 2-12 Installing the PrintServer Software UIC_ENTER_UNIQUE, Please enter a unique UIC. Explanation: The UIC value entered is already in use. User Action: Select another UIC value. UIC_INUSE, The UIC you have specified is already in use. Explanation: The UIC value entered is already in use. User Action: Select another UIC value. UIC_INVALID, The UIC you have entered is invalid. Explanation: You entered a value for a UIC using the wrong syntax. User Action: Enter a valid UIC or a question mark (?) for help. UIC_PRIVILEGED, The UIC you have chosen is privileged. Please select another. Explanation: You entered a value for a UIC that is less than the MAXSYSGROUP number. User Action: Enter a valid, non-privileged UIC or a question mark (?) for help. UPGRADE_VMS, Please install version n.n or later of OpenVMS before installing LPS 5.1 Explanation: The version of the OpenVMS VAX or Alpha operating system is not the version required for the PrintServer Software. The software requires OpenVMS VAX, Version 5.5-2 or higher, or OpenVMS Alpha, Version 1.5 or higher. User Action: Upgrade your software to the required version. WRONG_VMS, LPS 5.1 requires version n.n or later of OpenVMS. Explanation: The software requires OpenVMS VAX, Version 5.5-2 or higher or OpenVMS Alpha, Version 1.5 or higher. User Action: Upgrade your operating system to the correct version. Installing the PrintServer Software 2-13 3 ________________________________________________________________ Configuring the PrintServer Printer Before you can boot your PrintServer printer, you must add your printer to the DECnet database and set up supporting host services. This chapter explains how to perform those procedures. ________________________________________________________________ If You Are_._._.________Then_._._.___________________________See_._._._ Installing Run LPS$ADD_PRINTSERVER.COM for Table 3-1 software for each printer you want to support. and the first time Enable LPS$STARTUP_SERVICES.COM. Section 3.2 Upgrading and Run LPS$ADD_PRINTSERVER.COM for Table 3-1 adding new each new printer. Stop and restart and printers daemons. Sections Convert the NETSETUP database. 3.5 and 3.6 Upgrading Run LPS$UPGRADE_PRINTSERVER.COM Section 3.4 an existing for each existing PrintServer PrintServer printer. through 17, turbo Stop and restart daemons. Section 3.6 PrintServer Convert the NETSETUP database. 20, or PrintServer 32 printer Upgrading Stop and restart daemons. Section 3.5 software for Convert the NETSETUP database. and other existing Section 3.6 printers________________________________________________________ Before you run LPS$ADD_PRINTSERVER.COM, complete Table 3-1 for every PrintServer printer being added. Configuring the PrintServer Printer 3-1 DECnet Phase V Systems If the supporting host system is running DECnet Phase V, verify that MOP is running by issuing the following command. (Phase IV users should skip this step because NCL is not available.) $ MCR NCL SHOW MOP MOP is running if the system returns the following message and no other messages: Node 0 MOP at YYYY-MM-DD-HH:MM:SS.578+00:00.113 If the system returns errors, see Section 6.1.2.1. 3-2 Configuring the PrintServer Printer Table_3-1_Configuration_Data____________________________________ Record Information Data_Needed________________Here__________________Refer_to_._._._ 1 DECnet node name for ____________________ Section 3.1.1 PrintServer 2 PrintServer printer ____________________ Section 3.1.2 type 3 DECnet address for ____________________ Section 3.1.3 printer 4 Supporting host service ____________________ Section 3.1.4 circuit 5 PrintServer printer ____________________ Section 3.1.5 Ethernet_hardware_address_______________________________________ 3.1 Invoking LPS$ADD_PRINTSERVER.COM To start the LPS$ADD_PRINTSERVER command procedure, enter the following command: $ @SYS$MANAGER:LPS$ADD_PRINTSERVER The command procedure displays informational messages, then displays questions you need to answer. You can get help at any time during the procedure by entering a question mark (?). 3.1.1 DECnet Node Name 1 What is the DECnet node name of PrintServer printer you want to add? IMPALA Be sure to enter a DECnet Phase IV node name. Enter the DECnet node name of the printer you want to add to the DECnet database. The node name is assigned by the network manager. Format: The DECnet node name must be unique within your DECnet network and must consist of an alphanumeric string of one to six characters with at least one alphabetic character. The DECnet node name is used as the default PrintServer printer name. Configuring the PrintServer Printer 3-3 3.1.2 PrintServer Printer Type 2 Which type of PrintServer is IMPALA ? 1) PrintServer 40 or PrintServer 40 Plus 2) PrintServer 20 or turbo PrintServer 20 3) PrintServer 32 or PrintServer 32 plus 4) PrintServer 17 or PrintServer 17/600 Choose the appropriate number ([no default])? 4 Enter the type of PrintServer printer that is being configured. 3.1.3 DECnet Address LPS$ADD_PRINTSERVER.COM looks for the DECnet address in the NCP database. If it cannot find the address, the command procedure prompts you for the address: 3 What is the DECnet address of PrintServer IMPALA ? 55.495 Be sure you supply a DECnet Phase IV address. If the address has already been assigned, it is displayed as the default. Press to select the default. Definition: The DECnet address is a unique decimal number assigned to each node in the network. The DECnet address is different from the Ethernet hardware address (described in Section 3.1.5). The DECnet address is assigned to the PrintServer printer node by the network manager. Format: The format of the address is: [area-number.]node-number o area-number ranges from 1 to 63. If the area number is omitted, the default is the area number of the supporting host node. o node-number ranges from 1 to 1023. 3-4 Configuring the PrintServer Printer 3.1.4 Service Circuit LPS$ADD_PRINTSERVER.COM looks for the service circuit address in the NCP database. If it cannot find the circuit, the command procedure prompts you for the information: 4 What supporting host service circuit will be used to connect to IMPALA? SVA-0 Enter the service circuit of the supporting host system that services boot requests from the PrintServer printer being configured. Format: The service circuit has one of the following formats: dev-c dev-c-u dev-c.t dev-c-u.t The following table explains the different fields in the service circuit name: dev The device name of the Ethernet controller. c The number of the hardware controller for the device. u The circuit number included only if more than one unit is associated with the controller. t A decimal number that identifies a tributary on a multipoint circuit. This is a logical tributary number, not the tributary address used to poll the tributary. 3.1.5 Ethernet Hardware Address 5 What is the Ethernet hardware address of PrintServer IMPALA? 08-00-2B-05-15-F6 Enter the Ethernet hardware address of the PrintServer printer. Format: The Ethernet address is a series of six hexadecimal numbers, each of which range from 00 through FF. Configuring the PrintServer Printer 3-5 How to Find the Ethernet Hardware Address: If the Ethernet hardware address is not already available, you can obtain the address from the PrintServer printer (see Appendix C). 3.1.6 Summary of Network Database Information The command procedure now displays the information you have supplied for the network database: The following information will be entered into LPS$SUPPORT:LPSNETSETUP.DAT: 1) PrintServer Node Name: IMPALA 2) DECnet Address: 55.495 3) Type of printer: PrintServer 17 series 4) Service Circuit: SVA-0 5) Ethernet Hardware Address: 08-00-2B-05-15-F6 99) Quit without adding a new PrintServer printer Enter number to change (press Return if the data is correct): ________________________________________________________________ If You Enter . . . ____________The_Command_Procedure_._._._________________________ 1 to 5 Allows you to change the data you just entered. 99 Quits without adding the information to the LPSNETSETUP.DAT file. Continues and adds the information to the LPS$SUPPORT:LPSNETSETUP.DAT file and displays the following message: PrintServer data will be added to LPS$SUPPORT:LPSNETSETUP.DAT The SYS$MANAGER:LPS$NETSETUP.COM procedure is ____________invoked_to_update_the_network_database._____________ Enable Service Circuits: The command procedure reminds you to enable the service circuit serving the PrintServer printer: 3-6 Configuring the PrintServer Printer Please enable the service circuits serving the PrintServer nodes that you have just set up. You may want to add lines to LPS$NETSETUP.COM to enable service circuits automatically. Please refer to the PrintServer Software for OpenVMS Installation Guide for additional information. To enable the service circuit automatically, add the following commands to LPS$NETSETUP.COM: $ MCR NCP SET CIRCUIT circuit_name STATE OFF $ MCR NCP SET CIRCUIT circuit_name SERVICE ENABLED STATE ON To see if the service circuit is enabled, enter the following command: $ MCR NCP SHOW CIRCUIT circuit_name CHAR ________________________Note ________________________ This procedure interrupts processes that have active links on the specified circuit. _____________________________________________________ DECnet Phase V Systems: If NCP is not available on your system, use NCL commands instead of NCP commands. Refer to the DECnet/OSI Network Management Guide for information about using the DECNET_ MIGRATE tool, which converts NCP commands to NCL commands. 3.1.7 Summary of Configuration Information The LPS$ADD_PRINTSERVER.COM procedure displays the following configuration information: The following information will be entered in LPSCONFIG.IMPALA Configuring the PrintServer Printer 3-7 1) PrintServer name: IMPALA 2) Type of printer: PrintServer 17 Series 3) Password: LPS 4) Front panel language: English 5) Accounting: off 6) Event logging: on 7) Image interpreter: no 8) DECnet access restrictions: no 9) Access from Internet nodes: no 10) SNMP no 99) Quit without saving configuration Enter number to change (press Return if the data is correct:) 3-8 Configuring the PrintServer Printer ________________________________________________________________ To_Do_This_._._.________________Enter_._._._____________________ Change any information listed. The number of the item you want to change (1 to 10). The following sections explain how to change the information, such as how to enable access from Internet nodes. Quit without saving configura- 99 tion information. Add the information to the LPS$SUPPORT:LPSCONFIGDEFAULT.DAT file. Then each time you add a new printer, LPS$ADD_PRINTSERVER.COM uses the values in the configuration defaults file as the defaults. This saves you from having to enter the same information_repeatedly._________________________________________ 3.1.8 Printer Passwords What is PrintServer IMPALA's password [LPS]? If you want to change the default password, enter the new password here. If you want to use the default password, press . The printer password may be used by privileged PostScript jobs. Function: This password allows: o A print job to execute privileged PostScript commands o Access to the privileged commands of the remote console facility Refer to the PrintServer Software for OpenVMS Management Guide for more information. Configuring the PrintServer Printer 3-9 3.1.9 Operator Panel Language Select the language that you want to appear on the operator panel of your printer. (This question does not apply to the PrintServer 40 series printer.) The next question asks you to choose the language to be displayed on the PrintServer nn front panel. The languages you may choose from are the following: Dutch ... Spanish Swedish What language would you like to display on the PrintServer nn front panel? [English]? 3.1.10 Accounting Feature Do you want accounting enabled (Y=on, N=off, R=reliable [N])? Y Select whether you want the PrintServer printer to supply accounting information to every supporting host set up to receive it. The options are as follows: __________________________________________________________ Option______Meaning_______________________________________ On Send accounting data. Off Do not send accounting data. (Default) Reliable Send accounting data but stop printing if a management client is unavailable to receive the data. Choose this feature to ensure ____________complete_and_accurate_PrintServer_accounting._ 3.1.11 Event-Logging Feature Should PrintServer IMPALA enable event logging (Y/N [Y])? Y 3-10 Configuring the PrintServer Printer Choose whether to enable event logging on the PrintServer printer as follows: __________________________________________________________ Option______Meaning_______________________________________ Enabled The printer sends event messages to every (Default) supporting host set up to receive them. Disabled The printer does not send event messages to ____________the_supporting_host(s)._______________________ 3.1.12 Image Interpreter If you want to install the Image interpreter, which allows DDIF bitonal images to print faster on PostScript level 1 printers, enter Y. This question applies only if you are configuring one of the following printers: o Printserver 20 o turbo PrintServer 20 without the memory option o PrintServer 32 without the memory option You can use the Image interpreter only on printers that load PostScript level 1. The Image interpreter allows you to print 300 dpi bitonal DDIF images at 20 pages per minute for the turbo PrintServer 20 printer, and at 28 pages per minute for the PrintServer 32 printer. To access the Image interpreter, your system must be running DEC Image Print-PLUS Client software or DECprint Supervisor, Version 1.1 or higher. The Image interpreter provides faster printing of DDIF compressed images on the PrintServer 32 and turbo PrintServer 20 printers that load PostScript Level 1. Your print client software must support the Image interpreter in order to make use of this feature. Do you want to install the Image interpreter (Y/N [N])? N Configuring the PrintServer Printer 3-11 3.1.13 DECnet Access Restrictions If there are multiple supporting hosts in your network configuration, see the PrintServer Software for OpenVMS Management Guide before choosing to restrict access to the PrintServer printer. When you restrict access to the PrintServer printer, you restrict supporting host services (such as configuration services) as well as print jobs. Do you wish to restrict access to PrintServer IMPALA from specific DECnet node addresses or area numbers (Y/N [N])? ? By default, the printer allows access to any DECnet client that wishes to connect to it. If you want to restrict access from specific DECnet addresses or area numbers then answer "Y" to this question. If you answer "Y" to the question, then you will be asked to specify the DECnet area numbers or DECnet addresses of nodes allowed access to the printer and/or the DECnet area numbers or DECnet addresses of nodes denied access to the printer. Please see the PrintServer Software documentation for details. Do you wish to restrict access to PrintServer IMPALA from specific DECnet node addresses or area numbers (Y/N [N])? Y Enter the DECnet address or area number ALLOWED access to IMPALA. Press return if there are none to enter []: 33 Enter the DECnet address or area number ALLOWED access to IMPALA. Press return if there are none to enter []: Enter DECnet areas and nodes that cannot access the PrintServer printer. Use this feature to deny access to the PrintServer system from particular nodes in a DECnet area that were previously allowed access. Enter the DECnet address or area DENIED access to IMPALA. Press return if there are none to enter []: 33.505 Enter the next DECnet address or area number DENIED access to IMPALA. Press return if there are none to enter []: 3-12 Configuring the PrintServer Printer 3.1.14 Providing Access from Internet Nodes Do you want to provide an Internet address for PrintServer IMPALA (Y/N [N])? Y Enter Y to allow the printer to accept print jobs and supporting host services on the TCP/IP (Internet) network. When you enter Y, you must supply the following informa- tion: What is the Internet address of PrintServer IMPALA ? 16.122.128.10 What is the Internet subnet mask for your network? 255.255.240.0 What is the address of the Internet gateway, if one is required for accessing the PrintServer from remote clients? Press Return if none is required: Refer to the following sections for more information about each question. 3.1.14.1 Internet Address The Internet address is assigned to the printer by the network manager. The Internet address is a 32-bit number, usually expressed as four groups of numbers separated by periods; for example: 128.45.9.1 3.1.14.2 Internet Subnet Mask If you do not know the subnet mask for your network, contact your network manager. An example of an Internet subnet mask is as follows: 255.255.255.0 3.1.14.3 Internet Gateway Node Address A gateway allows the printer to accept print jobs from another Internet. Supply the Internet address of the gateway node, which you obtain from the network manager. An example of a gateway node address is: 128.46.33.45 Configuring the PrintServer Printer 3-13 3.1.14.4 Internet Access Restrictions Do you wish to restrict access to PrintServer IMPALA from specific Internet addresses or network numbers. (Y/N [N])? Y Enter Y to restrict access to the printer from Internet nodes. Supply the following information: Enter the Internet address or network number ALLOWED access to IMPALA. Press Return if there are none to enter []: 16 Enter the Internet address or network number ALLOWED access to IMPALA. Press Return if there are none to enter []: Enter the Internet address or network number DENIED access to IMPALA. Press Return if there are none to enter []: 16.122.128.10 Enter the Internet address or network number DENIED access to IMPALA. Press Return if there are none to enter []: 3.1.15 Simple Network Management Protocol The Simple Network Management Protocol (SNMP) is an Internet-standard protocol used by many network management applications to monitor network nodes. By enabling the PrintServer's optional SNMP agent, you allow the printer to be monitored by your network management applications. This option is not available for the PrintServer 40 series printer or PrintServer 20 printer. The following table shows which PrintServer configurations support SNMP. ________________________________________________________________ Amount of Printer_______________Memory______SNMP_Support?_________________ PrintServer 17 8 MB N PrintServer 17 12 MB Y PrintServer 17 16+ MB Y PrintServer 17/600 16 MB Y [1] PrintServer 17/600 20+ MB Y [1]If_SNMP_is_enabled_on_the_PrintServer_17/600_with_16_MB_of___ memory, the printer loads 29 resident fonts (instead of 43) and does not load PCL5. 3-14 Configuring the PrintServer Printer ________________________________________________________________ Amount of Printer_______________Memory______SNMP_Support?_________________ turbo PrintServer 20 12 MB Y [2] turbo PrintServer 20 16 + MB Y PrintServer 32 12 MB Y[2] PrintServer 32 plus 16 + MB Y [2]PrintServer_32_and_turbo_PrintServer_20_printers_with_12_MB__ of memory cannot load both the image interpreter and SNMP. If you_select_both,_only_SNMP_is_enabled.__________________________ The next question asks if you would like to enable SNMP (the Simple Network Management Protocol). SNMP is a standard protocol used by many network management applications to remotely monitor Internet network devices. If you answer "YES" to this question, you will be asked for additional information required to configure SNMP. Do you want to enable SNMP (Y/N [N])? Y Enter a text string that describes the printer's location []: LAB IV Enter a text string that identifies the primary contact for this printer []: HOTLINE 555-5959 The system then displays the following information: 10 SNMP: yes 10a) Printer's location: LAB IV 10b) Primary contact: HOTLINE 555-5959 10c) SNMP trap messages: no 10d) Add SNMP Community: no Current list: public, 0.0.0.0, read 99) Quit without saving configuration Enter number to change (press return if data is correct):) 10c Configuring the PrintServer Printer 3-15 SNMP Trap Messages If you enable trap messages, the printer's SNMP agent sends authentication error messages to predefined hosts on the network. These hosts are identified by their community names and Internet addresses. See Add SNMP Community for information about community names. Do you want to create one or more SNMP trap specifications (Y/N [N])? y Enter the TRAP community name. Press return if there are none to enter []: printer-manager Enter the trap Internet host address []: 16.34.56.78 Enter next TRAP community name. Press return if there are no more to enter []: Add SNMP Community You control which management nodes can access the printer's SNMP agent by specifying "communities." You provide the following information: o A community name o Internet address o The level of access provided to the management node For example, the software provides a default community named public, with an address of 0.0.0.0, and access level of "read". This means any SNMP-based management application on the network can access the printer's SNMP agent to read SNMP data. You may provide additional communities in the configuration file as follows: The default community of "public", with IP address 0.0.0.0 and read-only access has already been included in the printer's configuration file. Do you want to define additional SNMP communities (Y/N [N])? Y Enter community name. Press return if there are none to enter []: printer-manager Enter the community's Internet host address [0.0.0.0]: 192.9.200.67 Enter the community's access mode (1=READ-ONLY, 2=READ/WRITE [1])? 2 3-16 Configuring the PrintServer Printer Enter community name. Press return if there are none to enter []: ________________________Note ________________________ The configuration file uses the pound-sign character (#) to denote comments. Therefore, avoid using this character when entering text strings for SNMP configuration, such as the printer's location. _____________________________________________________ 3.1.16 Saving Your Configuration Information When you are finished adding information, press at the following prompt: Enter number to change (press return if data is correct): LPS$ADD_PRINTSERVER.COM creates the following files for you: Configuration data will be entered in LPS$SUPPORT:LPSCONFIG.IMPALA %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSCONFIG.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSDEFAULTS.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSSYSPARAMS.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSPCLDEFAULTS.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSRESOURCES.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSSETUP.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSOPTIONS.IMPALA has been created Configuring the PrintServer Printer 3-17 3.2 Enabling the Supporting Host Services Enabling LPS$STARTUP_SERVICES.COM file does the following: o Sets up the supporting host logical names LPS$SUPPORT and LPS$ROOT o Starts the management client for each PrintServer printer you have set up o If the printer is part of a cluster, establishes one node as the PrintServer supporting host node 3.2.1 Enabling the Startup File - Standalone Node If your supporting host is a standalone node, edit the system startup file. If you are running an OpenVMS VAX, Version 5.5-2 system, edit the following file: $ EDIT SYS$STARTUP:SYSTARTUP_V5.COM If you are running an OpenVMS VAX, Version 6.0 or an OpenVMS Alpha, Version 1.5 system, edit the following file: $ EDIT SYS$STARTUP:SYSTARTUP_VMS.COM Add the following command near the end of the file. Make sure that the command line to start the DECnet facility precedes this entry. $ @SYS$STARTUP:LPS$STARTUP_SERVICES If you are upgrading, this should have been completed during the previous installation. DECnet Phase V Systems If you have a DECnet Phase V system, add following entries: o Add the following entry to enable MOP booting for PrintServer printers. Without this entry, the printer does not boot. @SYS$MANAGER:LPS$NETSETUP.COM 3-18 Configuring the PrintServer Printer o Place the following entry after the LPS$NETSETUP entry: @SYS$STARTUP:NET$STARTUP NETWORK MOP 3.2.2 Enabling the Startup File - VAXcluster Node To enable the startup file in a VAXcluster, insert the following code in the clusterwide system startup command file: $ !Find the node on which the startup file is running $ ! $ cluster_member = F$GETSYI("NODENAME") $ ! $ ! Test to see if the node is the Supporting Host $ ! $ if "''cluster_member'" .eqs. "supporting-host-node-name" $ then $ @SYS$STARTUP:LPS$STARTUP_SERVICES $ endif The supporting-host-node-name is the name of the supporting host node. Be sure to enclose the name of the supporting host within quotation marks. The code invokes LPS$STARTUP_SERVICES for the cluster member where you want to run the management client. If you specify a second management client process on another member of the cluster, the following error message is displayed: LPS$START_DAEMON: Management client already exists for PrintServer node-name. 3.3 Configuring Multiple Supporting Hosts If your configuration requires multiple supporting hosts, you can configure the other supporting hosts to supply complete services or a subset of supporting host services. For example, you can configure a second supporting host to provide backup booting and management client services. For more information about setting up multiple supporting hosts, see the PrintServer Software for OpenVMS Management Guide. Configuring the PrintServer Printer 3-19 3.4 Invoking LPS$UPGRADE_PRINTSERVER.COM If you are upgrading existing level 1 printers to PostScript level 2, run LPS$UPGRADE_PRINTSERVER.COM. Invoke the command procedure as follows: $ @SYS$MANAGER:LPS$UPGRADE_PRINTSERVER The command procedure displays the following: Copyright Digital Equipment Corporation 1995. All Rights Reserved. *** Use this command procedure ONLY for existing PrintServer 17 series, *** *** turbo PrintServer 20, and PrintServer 32 printers. *** This command procedure is for upgrading existing PrintServer 17 series, turbo PrintServer 20, and PrintServer 32 printers to PostScript Level 2. This command procedure will do the following: o Create a new PostScript Level 2 defaults file (LPSDEFAULTS.printer-node-name) o Create a system parameters file (LPSSYSPARAMS.printer-node-name) o Create a PCL defaults file (LPSPCLDEFAULTS.printer-node-name) o Modify the existing configuration file (LPSCONFIG.printer-node-name) o Modify the existing resources file (LPSRESOURCES.printer-node-name) If you have previously edited the defaults file, those changes will not appear in the new file. If you want to retain those changes you must edit the new file. Depending upon your PrintServer 17 series, turbo PrintServer 20, or PrintServer 32 printer's configuration, the PostScript Level 2 image may contain additional fonts. If you had previously modified your resource file (LPSRESOURCE.printer-node-name) to load additional fonts, these modifications may no longer be necessary. Refer to the PrintServer Software for OpenVMS Management Guide. What is the DECnet node name of the PrintServer 17 series, turbo PrintServer 20 or PrintServer 32 printer you want to upgrade (press return to exit)? IMPALA %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSDEFAULTS.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSSYSPARAMS.IMPALA has been created %LPS-I-FILECREATE, The file LPS$SUPPORT:LPSPCLDEFAULTS.IMPALA has been created %LPS-I-FILECREATE, A new version of file LPS$SUPPORT:LPSCONFIG.IMPALA has been created. 3-20 Configuring the PrintServer Printer Do you want to upgrade another PrintServer 17 series, turbo PrintServer 20, or PrintServer 32 printer (Y/N [N] ?) $ 3.5 If You Are Upgrading, Stop and Restart Management Daemons The Version 5.1 components of PrintServer Software are not compatible with earlier versions. Therefore, if you are upgrading, stop all management client processes before rebooting. Otherwise, an earlier version of the management client tries to connect to a Version 5.1 PrintServer printer and exits with the following error message: Management session from node "node" rejected: incompatible versions The message is written to the LPS$SUPPORT:LPSLOG.printer- node-name file. This error may also occur if you have a PrintServer printer with two supporting hosts and you upgrade the software on only one supporting host. Perform the following steps in order for each printer: 1. After completing the VMSINSTAL procedure, stop the management daemon by entering the following command: $ @SYS$MANAGER:LPS$STOP_DAEMON.COM printer-node-name 2. Power off the printer, then on. 3. Start the management daemon by entering the following command: $ @SYS$MANAGER:LPS$START_DAEMON.COM printer-node-name 3.6 If You Are Upgrading, Convert the NETSETUP Database If you are upgrading your PrintServer Software, enter the following command: $ @SYS$MANAGER:LPS$ADD_NETSETUP -CONVERT The command converts the NETSETUP database to the Version 5.1 format. If your NETSETUP database has already been converted, or if conversion is not necessary, you receive a message that no conversion was performed. Prior to Version 5.0, the NETSETUP database is: o SYS$MANAGER:LPS$NETSETUP.COM (Version 3.nn and earlier) Configuring the PrintServer Printer 3-21 or o SYS$MANAGER:LPS$NETSETUP_V4.COM (Version 4.nn) These files contain NCP commands, which restore the DECnet database for your PrintServer printers. For Version 5.1, LPS$SUPPORT:LPSNETSETUP.DAT is the NETSETUP database and works with a new version of LPS$NETSETUP.COM. The new version of LPS$NETSETUP.COM loads the NETSETUP information into your DECnet database, using either NCP commands (for DECnet Phase IV systems) or NCL commands (for DECnet Phase V systems). 3-22 Configuring the PrintServer Printer 4 ________________________________________________________________ Enabling LPD 4.1 Overview LPD protocol support is available on all PrintServer printers. UNIX systems that use the LPD protocol to spool print jobs to remote systems require that you define a local queue to store the locally submitted jobs. Once a print job has been submitted to the local queue, the local printing system forwards the job to the PrintServer printer associated with the local queue. 4.2 Defining Local Print Queues There are several ways to set up your local print queue: o On ULTRIX and OSF systems, set up your local print queue by running lprsetup and selecting "remote" as your printer type. Table 4-1 describes the values to use. Enabling LPD 4-1 o Some UNIX systems use a special system database file (/etc/printcap) to define local print queues. Systems that use /etc/printcap require that a local print queue exist for remote spooling to another LPD-compatible system. Edit /etc/printcap to include queue setup information: labprt: \ lp=: \ sd=/var/spool/labprt: \ rm=print01: \ rp=labprt/PS: Table 4-1 explains each line in the example: Table_4-1_Queue_Setup_Information_________________________ Field____________Description______________________________ labprt: This is the name of the local print queue. lp=: No local (physical) printer device is associated with the queue. sd=/var/spool This is the local directory to be used /labprt: to spool jobs submitted to the "labprt" print queue. rm=print01: This is the Internet host name of printer. rp=labprt/ps: This is the name of the queue on the remote system where print jobs will be transferred. The "ps" specifies the PostScript interpreter. See Section 4.3 _________________to_change_the_type_of_interpreter._______ As you enter the data, make sure you: - End each line with a backslash character (\), except for the last line. - Start the name of the print queue (in this case, "labprt") start in the first column; all other lines can start in any other column. 4-2 Enabling LPD ________________________Note ________________________ There are usually several other configurable definitions for print queues on UNIX systems that use the /etc/printcap file. Many systems document the configuration options in the printcap(5) man page. Please refer to the documentation for your particular system for further information. _____________________________________________________ o To define local print queues on other UNIX systems, contact your UNIX operating system documentation for specific procedures. 4.3 Changing the Interpreter To use an interpreter other than PostScript, append the interpreter name to the remote queue name and separate them with a forward slash character (/). If you leave the field blank, the printer uses the PostScript interpreter. The following interpreters are recognized: /PCL or /HP-PCL PCL interpreter /PS PostScript interpreter /TEXT ASCII text interpreter For example, to use the PCL interpreter to process jobs on queue "labprt," specify the remote queue name as: rp=labprt/pcl: Enabling LPD 4-3 5 ________________________________________________________________ Booting the PrintServer Printer 5.1 Overview Booting allows the printer to access the software you just installed so that the printer can become part of the network. PrintServer printers can use two kinds of protocols to boot: maintenance operation protocol (MOP) or BOOTP. Because OpenVMS software supports the MOP protocol only, this chapter explains the booting process using the MOP protocol. Booting Process When you boot a PrintServer printer, the following events occur: 1. The PrintServer printer sends out a "boot assistance required" message. 2. A suitably configured supporting host node sends out a reply message that the request will be serviced. 3. The PrintServer printer receives the primary system image from the supporting host node. 4. A management client process provides the configuration and secondary image files and the defaults, system parameters, startup page, resource, and setup files. 5.2 Booting a PrintServer 17 Series Printer Power on the printer. The boot process runs automatically. The operator panel informs you of the status. Booting the PrintServer Printer 5-1 Page Count First, the page count appears in the lower right corner of the window. For example: °0000292 Self Test Then the diagnostic self tests run. 9,8,7,6,5,4,3,2,1,0 Ethernet Hardware Address The first line shows the Ethernet hardware address. The second line shows the firmware version numbers. This indicates that the primary boot is taking place. 08-00-2B-0C-48-EE x.x y.y z.z where: x.x is the controller firmware version number. y.y is the print engine firmware version number. z.z is the operator panel firmware version number. Successful Primary Boot The following display on the operator panel shows that the system file LPS_PRINTSERVER17.SYS has been loaded: 08-00-2B-0C-48-EE VAXELN V4.5 LPS17 Secondary Boot Begins When a management client process on a supporting host node connects to the printer, the following displays: VAXELN V4.5 LPS17 .... Loaded Files The printer-specific configuration file and system image files are loaded by the management client. In addition, the following files are loaded: Printer-specific defaults files Startup page file Printer-specific resource files Printer-specific setup file 5-2 Booting the PrintServer Printer Successful Secondary Boot When the software is loaded and started, the following sequence displays: Copyright 1995 Digital Equipment Corp. Ready Startup Page Next the startup page prints. During this process, the following displays: Processing Printing Ready to Print The following display indicates that the files have been loaded and the PrintServer printer is ready to print: Ready After the PrintServer printer has booted, you should be able to print. If not, see Chapter 6. 5.3 Booting a PrintServer 20 Series or PrintServer 32 Series Printer The boot process runs automatically. The operator panel informs you of the status. If You Have a PrintServer 20 Printer If you are booting a PrintServer 20 printer (not a turbo PrintServer 20 printer), with controller firmware version before Version 1.3, you must set the boot protocol by setting DIP switches inside the operator panel of the printer. The DIP switches are set for MOP booting by default. 1. Power down the printer. Open the operator panel and remove the panel covering the module card cage. (See your printer operator's guide.) 2. Locate the DIP switch on the left-center front edge of the lower module. To boot from OpenVMS systems, select MOP protocol and make sure all switches are up. Booting the PrintServer Printer 5-3 3. Replace the module card cage panel and close the operator panel. Now you are ready to boot. Boot Process for All Printers Power down the printer, then power it up. Self-Test The diagnostic tests run and the following numbers display on the PrintServer printer operator panel: 9,8,7,6,5,4,3,2,1,0 Ethernet Hardware Address The previous display is quickly replaced by: 08-00-2B-0C-48-EE x.x y.y z.z This shows the Ethernet hardware address and the firmware version numbers. where: x.x is the controller firmware version number. y.y is the print engine firmware version number. z.z is the large capacity input tray (LCIT) firmware version number. It indicates that the primary boot is taking place. Successful Primary Boot If the primary boot is successful, the following displays: 08-00-2B-0C-48-EE VAXELN V4.5 LPS This display indicates that the system file LPS_ PRINTSERVER.SYS has been loaded. Secondary Boot Begins When a management client on a supporting host node connects to the printer, the following displays: VAXELN V4.5 LPS .... 5-4 Booting the PrintServer Printer Files Loaded The printer-specific configuration file and system image files are loaded by the management client. The following files are also loaded: Printer-specific defaults file Startup page file Printer-specific resource files Printer-specific setup files Successful Secondary Boot Once the software loads, the following sequence displays: Copyright 1995 Digital Equipment Corp. Please wait ... Initializing ... Print engine is in warmup state Ready Startup Page The printer prints the startup page and displays: Processing Printing Ready to Print The following display indicates that the files have been loaded and the PrintServer printer is ready to print: Ready If the boot process fails or if you cannot print after the printer has booted, see Chapter 6 for troubleshooting procedures. 5.4 Booting a PrintServer 40 Plus Printer Power on the printer. Booting the PrintServer Printer 5-5 Enter the BOOT Command If the prompt (>>>) is displayed on the local console screen, the PrintServer printer was not installed to boot automatically. Enter the following boot command at the prompt: >>> B Primary Boot The boot process proceeds and loads the file LPS_ PRINTSERVER40.SYS. The local console display shows the printer type and "Waiting for Configuration" on the banner line. (The remote console also displays this message.) Secondary Boot When the management client has established a connection to the PrintServer printer, a message displays on the console indicating the connection has been made. The banner line reads "Loading" and reflects the loading status. Successful Secondary Boot When the boot process is complete, the console screen banner line reads "Idle." When the banner line shows the Idle status, the PrintServer printer is ready to accept print jobs. If the boot process does not complete successfully, see Section 6.1 for troubleshooting procedures. 5.5 Determining and Reporting Problems If you encounter a problem using PrintServer Software, see Chapter 6 to diagnose and solve the problem. If the problem persists, report it to Digital. Depending on the nature of the problem and the type of support you have, take one of the following actions: o Call your Digital representative if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). 5-6 Booting the PrintServer Printer o Fill out and submit a Reader's Comments form if the problem concerns the PrintServer Software documentation. A Reader's Comments form is at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number where you found the problem, as well as an exact description of the problem you found in the documentation. Booting the PrintServer Printer 5-7 6 ________________________________________________________________ Troubleshooting the Software This chapter helps you diagnose hardware and software problems. The following table helps you select the appropriate section to diagnose problems: Troubleshooting the Software 6-1 __________________________________________________________ See If_._._.________________Then_._._.______________Section___ The self-test display You have a hardware Call your does not reach 0. failure. Digital Services represen- tative. The operator panel The primary boot 6.1 display stops at: failed. 08-00-2B-0C-48-EE x.x y.y z.z The operator panel The primary boot 6.1 displays one of failed. the following error codes: 1501.0001 ?54 ?56 ?57 The operator panel The secondary boot 6.2 display stops at: failed. 08-00-2B-0C-48-EE VAXELN V4.5 LPS The operator panel The printer booted 6.3 displays one of the and crashed. following messages: Reboot PrintServer System shutdown complete- use console to halt system The operator panel The print client 6.4 displays "Ready" but cannot access the cannot_print.___________printer.__________________________ When you encounter any type of printer problem, first verify that the postinstallation procedure has been executed according to the instructions in Chapter 3. 6-2 Troubleshooting the Software 6.1 If the Primary Boot Procedure Fails Perform the procedures in the following sections to troubleshoot the problem. 6.1.1 Step 1: Checking the Supporting Host Logical Names Make sure the logical names for LPS$SUPPORT and LPS$ROOT are defined correctly. Log in to the supporting host system and enter the following command: $ SHOW LOGICAL/SYSTEM/FULL LPS$SUPPORT, LPS$ROOT "LPS$SUPPORT" [EXEC] = "device-name:[LPS$SERVER]" (LNM$SYSTEM_TABLE) "LPS$ROOT" [EXEC] = "device-name:[LPS$SERVER.]" (LNM$SYSTEM_TABLE) If the logical names are correct, go to Section 6.1.2. If the logical names are incorrect, run LPS$STARTUP_SERVICES to define them and reboot the printer. $ @SYS$STARTUP:LPS$STARTUP_SERVICES.COM LOGICALS If the printer continues to fail during the boot process, check the network environment. 6.1.2 Step 2: Monitoring Network Events If the printer issues a boot request that the supporting host never receives, then a network configuration problem could exist. You can monitor the network events to determine whether the supporting host is receiving boot requests. ________________________Note ________________________ The following sections describe network control program (NCP) parameters and the database where the parameters are stored. The examples use the NCP SET command, which affects only the volatile database. You need OPER privilege to modify the volatile database. Digital recommends you use the NCP DEFINE command, which stores NCP parameters in the NCP permanent database. You need SYSPRV privilege to modify the permanent database. _____________________________________________________ Troubleshooting the Software 6-3 For additional information regarding NCP commands, enter the following: $ MCR NCP HELP For more information, see the VMS Network Control Program Manual. To troubleshoot network events, perform the following procedure: __________________________________________________________ Step___Procedure_______________________Section____________ 1 Check DECnet Phase V MOP. 6.1.2.1 2 Check the NCP database. 6.1.2.2 3 Check the service circuit. 6.1.2.3 4 Enable network event 6.1.2.4 reporting. 5 Monitor OPCOM messages. 6.1.2.5 6 Check the network configura- 6.1.2.6 tion. 7 Determine whether the printer 6.1.2.7 has booted. 8 Detect and shut down remote 6.1.2.8 _______booting_services.__________________________________ DECnet Phase V Systems: If NCP does not work on your system, use NCL commands instead of NCP commands. Refer to the DECnet/OSI Network Management Guide for information about using the DECNET_ MIGRATE tool, which converts NCP commands to NCL commands. 6.1.2.1 Checking DECnet Phase V MOP If your system is running DECnet Phase V, perform the troubleshooting steps in this section. Verify that MOP is running by issuing the following command: $ MCR NCL SHOW MOP 6-4 Troubleshooting the Software MOP is running if the system returns the following message and no other messages: Node 0 MOP at YYYY-MM-DD-HH:MM:SS.578+00:00.113 If the system returns errors, it is possible that MOP is not running. To start MOP, issue the following command: $ @SYS$STARTUP:NET$STARTUP NETWORK MOP Depending on how your NCL startup files are configured, you may need to issue the following commands as well: $ MCR NCL NCL> CREATE NODE 0 MOP NCL> ENABLE NODE 0 MOP NCL> EXIT See the DECnet/OSI Network Management Guide for more information. 6.1.2.2 Checking the NCP Database Check that the boot host has the correct entry for the PrintServer printer in the NCP database by entering the following command: $ MCR NCP SHOW NODE printer-node-name CHARACTERISTICS The typical output from this command is as follows: $ MCR NCP SHOW NODE BULL36 CHARACTERISTICS Node Volatile Characteristics as of 8-JUN-1995 22:04:34 Remote node = 62.114 (BULL36) Service circuit = SVA-0 Hardware address = 08-00-2B-0C-7E-8B Load file = LPS$ROOT:[SYS]LPS_PRINTSERVER.SYS Access = incoming and outgoing If information is missing or incorrect, make the necessary changes by running SYS$MANAGER:LPS$NETSETUP.COM. If the NCP database continues to display incorrect information, then postinstallation data entered in the LPS$ADD_PRINTSERVER.COM procedure is incorrect. Do the following: Troubleshooting the Software 6-5 1. Be sure you have the correct service circuit name, DECnet node address, and Ethernet hardware address. 2. Run the LPS$ADD_PRINTSERVER.COM procedure. See Section 3.1. 3. Reboot the printer. If the boot process continues to fail, go to Section 6.1.2.3. 6.1.2.3 Checking the Service Circuit Check the service circuit characteristics to be sure that service is set to ENABLED for the service circuit used to boot the PrintServer printer: $ MCR NCP SHOW CIRCUIT circuit CHARACTERISTICS Supply the circuit name for your network interface (see Section 3.1.4). Check that State is set to ON and that Service is set to ENABLED. For example: $ MCR NCP SHOW CIRCUIT SVA-0 CHARACTERISTICS Circuit Volatile Characteristics as of 8-JUN-1995 23:59:23 Circuit = SVA-0 State = on Service = enabled Designated router = 55.155 Cost = 4 Maximum routers allowed = 33 Router priority = 64 Hello timer = 15 Type = Ethernet Adjacent node = 55.155 Listen timer = 90 If Service is set to DISABLED, execute the following commands. In the following example, the service circuit name is SVA-0: 6-6 Troubleshooting the Software $ MCR NCP SET CIRCUIT SVA-0 STATE OFF $ MCR NCP SET CIRCUIT SVA-0 SERVICE ENABLED STATE ON ________________________Note ________________________ This procedure will interrupt processes that have active links on the specified circuit. _____________________________________________________ 6.1.2.4 Enabling Network Event Reporting To log network events from NCP: 1. Select the events you want to display. 2. Enable reporting of the selected events. SHOW LOGGING MONITOR Command Use the following command to determine what events are selected and whether event logging is enabled: $ MCR NCP SHOW LOGGING MONITOR Logging Volatile Summary as of 8-JUN-1995 23:59:44 Logging sink type = monitor Sink Node Source Events State Name 55.499 (NASDAQ) (All sources) 0.0-9 on (All sources) 2.0-1 (All sources) 4.2-13 15-16 18-19 (All sources) 5.0-18 (All sources) 128.0-4 SET LOGGING MONITOR Command If event logging of network activity has not been enabled, use the NCP SET LOGGING MONITOR command to select and enable reporting of events: $ MCR NCP SET LOGGING MONITOR STATE ON You can supply an event number to monitor a particular type of event: o Use 0.3 to monitor automatic line service. o Use 0.7 to monitor aborted service requests. Troubleshooting the Software 6-7 To select reporting of particular events, enter the following: $ MCR NCP SET LOGGING MONITOR EVENT number To select reporting of all events, enter the following: $ MCR NCP SET LOGGING MONITOR KNOWN 6.1.2.5 Checking OPCOM Messages If OPCOM is running, the selected network events are reported on the system console and on any terminals that are appropriately enabled, and recorded in the SYS$MANAGER:OPERATOR.LOG file. 1. To determine whether OPCOM is running, enter the following command and look for a process named OPCOM: $ SHOW SYSTEM 2. If there is no process named OPCOM, start one by entering the following command: $ @SYS$SYSTEM:STARTUP OPCOM You need the SYSPRV privilege to execute this command. 3. Enable the display of network-related events: $ REPLY/ENABLE=NETWORK The following is an example of an OPCOM report for a successful load: $ %%%%%%%%%%% OPCOM 8-JUN-1995 18:06:04.66 %%%%%%%%%%% Message from user DECNET on NASDAQ DECnet event 0.3, automatic line service From node 55.499 (NASDAQ), 8-JUN-1995 18:06:04.62 Circuit SVA-0, Load, Requested, Node = 62.114 (BULL36) File = LPS$ROOT:[SYS]LPS_PRINTSERVER.SYS, Operating system Ethernet address = 08-00-2B-0C-7E-8B 6-8 Troubleshooting the Software $ %%%%%%%%%%% OPCOM 8-JUN-1995 18:06:11.53 %%%%%%%%%%% Message from user DECNET on NASDAQ DECnet event 0.3, automatic line service From node 55.499 (NASDAQ), 8-JUN-1995 18:06:11.50 Circuit SVA-0, Load, Successful, Node = 62.114 (BULL36) File = LPS$ROOT:[SYS]LPS_PRINTSERVER.SYS, Operating system Ethernet address = 08-00-2B-0C-7E-8B 4. Boot the printer and check any resulting OPCOM messages. OPCOM software detects boot requests from the printer when: o Network events are enabled. o The Ethernet hardware address for the PrintServer printer is recorded in the NCP database. When the OPCOM report indicates a "Load, Successful" status, the primary boot process has successfully completed. If the system receives no boot request from the printer, check the network configuration (see Section 6.1.2.6). 6.1.2.6 Checking the Network Configuration Some network bridges and routers can be configured to filter boot request messages. Check with your network administrator to determine if there is a bridge or router between the supporting host and the printer. ________________________Note ________________________ The first boot request message is sent to the Ethernet multicast address AB-00-00-01-00-00. Bridges and routers supplied by Digital may be configured to filter messages sent to this multicast address. _____________________________________________________ If there is a bridge or router, disable the filtering of boot request messages or place the printer and the supporting host on the same side of the bridge or router. If you change the network configuration, reboot the Troubleshooting the Software 6-9 printer. If the printer does not boot, continue with Section 6.1.2.7. 6.1.2.7 Determining If the Printer Booted If the OPCOM report shows an "aborted service request" message for your printer and indicates a device timeout, one of the following occurred: o Another system on the network has serviced the boot request. o The printer did not complete the primary boot process. For example: $ %%%%%%%%%%% OPCOM 8-JUN-1995 18:09:33.41 %%%%%%%%%%% Message from user DECNET on NASDAQ DECnet event 0.7, aborted service request From node 55.499 (NASDAQ), 8-JUN-1995 18:09:33.37 Circuit SVA-0, Line open error, Line communication error %SYSTEM-F-TIMEOUT, device timeout Node = 62.114 (BULL36), Ethernet address = 08-00-2B-0C-7E-8B To determine if the primary boot successfully completed, use the following NCP command: $ MCR NCP TELL printer-node-name SHOW EXECUTOR A typical response from a printer that has booted is shown in the following example: $ MCR NCP TELL BULL36 SHOW EXECUTOR Node Volatile Summary as of 8-JUN-1995 18:09:35.14 Executor node = 62.114 (BULL36) State = on Identification = VAXELN V4.5 LPS If the printer did not boot successfully, the following message is displayed: %NCP-F-CONNEC, unable to connect to listener -SYSTEM-F-UNREACHABLE, remote node is not currently reachable Check the hardware connections, as described in Section 6.1.3. 6-10 Troubleshooting the Software If the identification field indicates something other than VAXELN V4.5 LPS or LPSnn, then the wrong file was downloaded to the printer. Determine which system serviced the boot request and stop the booting from that system. Refer to Section 6.1.2.8. 6.1.2.8 Shutting Down Remote Booting Services If you suspect that another node serviced the boot request, determine whether that node is set up to service boot requests from the printer: $ MCR NCP TELL node-name SHOW NODE printer-node-name CHARACTERISTICS If you do not know which node is booting the printer, use the remote console facility configuration command. If the remote console facility is unsuccessful in connecting to the printer, it is possible that the printer did not boot successfully. Check the hardware connections. If the remote console facility connects to the printer, it creates a window on the terminal and displays a prompt on the third line. You can determine which node booted the printer by entering the following command: LPS> configuration The remote console facility responds with the name of boot host, which contains the name and network address of the node that serviced the printer boot request. To disable a node from booting a particular printer, enter the following commands on the booting host: $ MCR NCP CLEAR NODE printer-node-name HARDWARE ADDRESS $ MCR NCP PURGE NODE printer-node-name HARDWARE ADDRESS Reboot the printer. If the boot process fails again, go to Section 6.1.3. 6.1.3 Step 3: Checking the Hardware Connections Check all of the cables connecting the printer, the supporting host, and any network devices. If you make any changes, reboot the printer. If the boot operation still fails, call your Digital Services representative. Troubleshooting the Software 6-11 6.2 If the Secondary Boot Procedure Fails When the management client connects to PrintServer printer, it sends secondary boot files, which contain the rest of the PrintServer software. To troubleshoot management client problems, perform the following procedures: __________________________________________________________ Step___Action__________________________Section____________ 1 Make sure the Phase V DECnet 6.2.1 address has been added. 2 Make sure that configuration 6.2.2 services are provided by the supporting host. 3 Check the status of the 6.2.3 management client. 4 Determine whether the 6.2.4 management client has made a connection to the printer. 5 Check the management client 6.2.5 versions. 6 Restart the management client 6.2.6 if the connect timer has timed _______out._______________________________________________ 6.2.1 Checking that Phase V DECnet Addresses Have Been Added If you have a Phase V DECnet configuration, you may need to add DECnet addresses to the following file: SYS$SYSROOT:[SYSEXE]DECNET_LOC_NODE_DEFINITIONS.TXT Then, run the DECnet REGISTER program to read the definition file and place the DECnet addresses into a database: $ MCR DECNET_LOC_REGISTER.EXE DECNET_LOC_REGISTER> LOAD Clearing old local namespace entries prior to loading new entries Loading new local namespace node name entries Saving the new local namespace contents 6-12 Troubleshooting the Software Maximum number of node names that can be loaded: 190 Number of node names that are currently loaded: 3 DECNET_LOC_REGISTER> EXIT 6.2.2 Checking Configuration Services Make sure that the -C configuration option is included in the LPS$SUPPORT:LPSOPTIONS.printer-node-name file. This option enables the management client to provide configuration services. That is, the management client can download all files required by the PrintServer printer during the boot process. If configuration services are not enabled, run SYS$MANAGER:LPS$OPTIONS.COM and enter YES to the question about configuration services. Then stop and restart the management daemons by entering the following commands: $ @SYS$MANAGER:LPS$STOP_DAEMON.COM printer-node-name $ @SYS$MANAGER:LPS$START_DAEMON.COM printer-node-name 6.2.3 Checking the Management Client Status (LPS$SERVICES) As described in Section 3.2, make sure the management client starts automatically whenever the supporting host is rebooted by executing the SYS$STARTUP:LPS$STARTUP_ SERVICES.COM procedure from the system startup file. The LPS$STARTUP_SERVICES procedure starts a management client for every printer for which it can find an LPS$SUPPORT:LPSOPTIONS.printer-node-name file. Look in the LPS$SUPPORT:LPSLOG.printer-node-name file for related messages (see Section 6.2.7). After you start the management client, enter the SHOW SYSTEM command to check the status of the LPS$SERVICES process: Troubleshooting the Software 6-13 $ SHOW SYSTEM VAX/VMS V5.5-2 on node NASDAQ 8-JUN-1995 21:42:27.90 ... Pid Process Name State Pri I/O CPU ... ... 00000604 LPS_BULL36 HIB 5 21605 0 00:01:18.30 ... ... ________________________Note ________________________ In this example, output lines containing other processes have been removed and truncated (indicated by ellipses) to fit on one line. _____________________________________________________ Look for a process named LPS_printer-node-name in the output. If there is no process by this name on your system, enter the following command to start the management client: $ @SYS$MANAGER:LPS$START_DAEMON printer-node-name 6.2.4 Checking Management Client Connections If you are sure that the management client is running, use the remote console facility to determine its current state. To invoke the remote console facility, enter one of the following commands: __________________________________________________________ To Invoke this Interface . ..nterthe Following Command . . . __________________________________________________________ Windows $ MCR LPS$XCONSOLE Command-line $ MCR LPS$CONSOLE printer-node- ___________________________name___________________________ See the PrintServer Software for OpenVMS Management Guide for more information about the remote console facility. When the banner line contains the message "Waiting for configuration," the management client has not yet connected to the printer. An example of such a banner line for a PrintServer 20 printer follows: 6-14 Troubleshooting the Software PrintServer 20 () Privs Disabled Waiting for configuration To determine whether the printer has been configured, enter the configuration command. If the configuration host field contains the name of the configuration host, then the printer has been configured and the configuration host will download the rest of the files. If the other fields do not have the expected values, check the contents of the LPS$SUPPORT:LPSCONFIG.printer-node- name file. If you change this file, reboot the printer. 6.2.5 Checking Management Client Versions The Version 5.1 software components are not compatible with earlier versions. Therefore, if you are upgrading, stop all management client processes before rebooting. Otherwise, an earlier version of the management client would try to connect to a Version 5.1 PrintServer printer and exit with the following error message: Management session from node "node" rejected: incompatible versions The message is written to the LPS$SUPPORT:LPSLOG.printer- node-name file. This error may also occur if you have a PrintServer printer with two supporting hosts and you upgrade the software on only one supporting host. 6.2.6 Restarting the Management Client If the management client has been running for some time without being able to connect to the printer, it executes a backoff algorithm to reduce the frequency of attempts to connect to the printer. Instead of waiting for the management client to make its next attempt to connect, you can stop and restart the management client, which resets the backoff time to zero. To stop and restart the management client, enter the following commands: $ @SYS$MANAGER:LPS$STOP_DAEMON printer-node-name $ @SYS$MANAGER:LPS$START_DAEMON printer-node-name Enter the SHOW SYSTEM command to make sure that the management client has started. If the management client still fails to connect, call your Digital Services representative. Troubleshooting the Software 6-15 6.2.7 Examining the PrintServer Printer Event Log File The management client process running on the sup- porting host node records printer messages in the LPS$SUPPORT:LPSLOG.printer-node-name file. You can examine this file, using a variety of methods: o To display the file, issue the TYPE command. o If the management client is still running, the current log file is opened by the client and you cannot copy or print the file. Close the current file and open a new one, using the remote console facility's newfile command. o To make a copy of the log file, issue the following command: $ CONVERT/SHARE LPSLOG.printer-node-name LPSLOG.COPY For the printer to send event messages to the management client, event logging must be enabled. Check the LPS$SUPPORT:LPSCONFIG.printer-node-name file for the line "Logging On." If the LPSLOG.printer-node-name file is not available, then the management client sends data to the following files: LPS$SUPPORT:LPSSERVICES_ERROR.printer-node-name LPS$SUPPORT:LPSSERVICES_OUTPUT.printer-node-name If logging is not enabled, run SYS$MANAGER:LPS$CONFIG.COM and enter YES to the event-logging question. Following is an example of the printer log file: 6-16 Troubleshooting the Software lps$services.exe;18 Jun 11 17:55:33: Start management session 1 11-JUN-1995 17:56:49 Memory installed - 16M 11-JUN-1995 17:56:49 Load complete (V5.1-10) 2 11-JUN-1995 17:56:49 Print Engine is in warmup state 11-JUN-1995 17:56:49 PrintServer 17 configured from node SERVR 11-JUN-1995 17:57:50 Privileged command executed, permanent state may be changed 3 11-JUN-1995 17:57:50 Privileged command executed, permanent state may be changed 11-JUN-1995 17:57:52 Privileged command executed, permanent state may be changed 11-JUN-1995 17:57:53 Privileged command executed, permanent state may be changed 11-JUN-1995 17:58:00 Privileged command executed, permanent state may be changed 11-JUN-1995 18:00:03 Print Engine ready 11-JUN-1995 18:02:35 Session 1 (LAPS-connect@PRINCE) connect 4 The messages in this example indicate the following: 1 The time the management client started a session on the PrintServer printer. 2 The secondary boot files have been loaded successfully. 3 Files are loaded outside the PostScript server loop, namely: o LPSDEFAULTS.printer-node-name o LPSSYSPARAMS.printer-node-name (for PostScript Level 2 printers) o LPSPCLDEFAULTS.printer-node-name (for PostScript Level 2 printers) o LPSRESOURCES.printer-node-name o LPSSETUP.printer-node-name If the resource-loading file contains multiple files to be loaded at boot time, additional messages are displayed. 4 The first print client successfully connected. Troubleshooting the Software 6-17 6.3 If the Printer Boots and Crashes When the printer boots and crashes, power-cycle the printer to reboot it. This kind of problem indicates one of the following system problems: o Hardware deterioration occurred. o The wrong files were downloaded to the printer. o Files are corrupted on the supporting host disk or became corrupted in transmission. Examine the log file LPS$SUPPORT:LPSLOG.printer-node-name for information about events that may have caused the printer crash. (See Section 6.2.7.) If the printer continues to crash, call your Digital Services representative. If the printer hangs or crashes, record all information you have about the state of the printer before the crash (for example, a paper jam or messages on the operator panel). Save a copy of the LPS$SUPPORT:LPSLOG.printer- node-name file. Also, try to get a copy of the file that was being printed at the time of the crash. This information helps in diagnosing problems. Report the problem to your Digital Services representative. 6.4 If the Printer Displays "Ready" but Does Not Print If the printer completes the primary boot, receives a management connection, indicates that it is available for printing, but does not respond to the print client connection requests (that is, nothing gets printed), the problem may be specific to the print client system. The following table lists some of the problems that can prevent a print client from accessing the PrintServer printer. 6-18 Troubleshooting the Software __________________________________________________________ Problem_______________Section_____________________________ Internet access is 6.4.1 restricted. DECnet access is 6.4.2 restricted. Print queues are not 6.4.3 set_up.___________________________________________________ 6.4.1 Internet Access Is Restricted To provide printing services to clients using the Internet network, the LPS$SUPPORT:LPSCONFIG.printer-node-name file must include the Internet address and subnet mask for the printer. This information is required to accept connections from management clients, remote console clients, and print clients that use the Internet transport protocol. For further details, see the PrintServer Software for OpenVMS Management Guide. 6.4.2 DECnet Access Is Restricted If you cannot print from a particular node, check to see if access to the node has been denied in the LPS$SUPPORT:LPSCONFIG.printer-node-name file. You can obtain this information using the remote console facility permissions command. However, you cannot run the remote console facility from a node that is denied access to the PrintServer printer. If access restrictions prevent printing, the following message is displayed on the remote console screen: Connection from node-address denied access In this message, node-address is the DECnet address of the print client node that cannot print. This message is also recorded in the printer event log file. If you see this message, run SYS$MANAGER:LPS$CONFIG.COM and answer NO to the question about DECnet access restrictions. Then issue the reconfigure command from the remote console facility for the changes to take effect. Troubleshooting the Software 6-19 DECnet or Internet access restrictions are specified in the postinstallation procedure. 6.4.3 Print Queues Are Not Set Up A print queue must be set up for the PrintServer printer on the print client system to let a user on that system access the printer. Print queues are usually created at the time the print client software is installed. See the appropriate print client documentation for procedures for setting up print queues. If you still cannot print on your PrintServer printer, contact your Digital Services representative. 6-20 Troubleshooting the Software A ________________________________________________________________ Sample Installation Session Example A-1 represents the installation of the PrintServer Software. Installation messages and questions vary according to system conditions, whether this is a new installation or an update, and the options you select. This procedure is described in Section 2.1. Example A-1 Sample Installation VAX/VMS Software Product Installation Procedure V5.5-2 It is 19-JUN-1995 at 14:09. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: MUA0: * Enter installation options you wish to use (none): The following products will be processed: LPS V5.1 Beginning installation of LPS V5.1 at 14:10 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1995. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. (continued on next page) Sample Installation Session A-1 Example A-1 (Cont.) Sample Installation The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? This installation procedure will create an account named LPS$SERVER. The UIC of this account will be used by the management client process to provide the PrintServer with its secondary boot files and to create event log and accounting files on this supporting host system. You must specify a unique UIC for this account. In order to maintain proper system security, please choose a UIC with a group number that does not give the account system privileges. * Enter the UIC for LPS$SERVER account (include brackets) [[477,477]]: Enter the name of one of the disk devices available on your host system. Be sure that the device you specify has at least 33,000 free blocks. * Enter the device name where the supporting host directory will be created [[SYS$SYSDEVICE]]: %LPS-I-NO_MORE_QUESTIONS, No further questions will be asked during this installation. %LPS-I-ESTTIME, This installation will take approximately 20 minutes. %LPS-I-CREATE_ACCOUNT, Creating LPS$SERVER account for the PrintServer Supporting Host %VMSINSTAL-I-ACCOUNT, This installation creates an account named LPS$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier LPS$SERVER value [000477,000477] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named LPS$SERVER. %UAF-I-MDFYMSG, user record(s) updated %LPS-I-ADD_LOGICALS, Creating the LPS$SUPPORT and LPS$ROOT logicals. %VMSINSTAL-I-SYSDIR, This product creates system disk directory LPS$ROOT:[CAT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory LPS$ROOT:[SYS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[SYSHLP.EXAMPLES.LPS]. %VMSINSTAL-I-RESTORE, Restoring product save set B ... (continued on next page) A-2 Sample Installation Session Example A-1 (Cont.) Sample Installation %VMSINSTAL-I-RESTORE, Restoring product save set C ... The installation of PrintServer Software for OpenVMS has completed successfully. For both an upgrade and new installation, you must perform the following steps: * Execute SYS$MANAGER:LPS$ADD_PRINTSERVER.COM for each new PrintServer printer. * Execute SYS$MANAGER:LPS$UPGRADE_PRINTSERVER.COM for each existing PrintServer printer you want to upgrade to PostScript Level 2. * Your system-specific startup command file must call the supporting host startup file, SYS$STARTUP:LPS$STARTUP_SERVICES.COM. * Execute SYS$MANAGER:LPS$STOP_DAEMON.COM and SYS$STARTUP:LPS$STARTUP_SERVICES.COM and reboot the PrintServer printers. Failure to follow the above steps may prevent your PrintServer printers from booting. Please refer to the PrintServer Software for OpenVMS Installation Guide for further instructions. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LPS V5.1 completed at 14:40 VMSINSTAL procedure done at 14:40 $ Sample Installation Session A-3 B ________________________________________________________________ Files Added During Installation B.1 Utility Files During the installation of the PrintServer Software, the following utility files are added to the system: ________________________________________________________________ File____________________________Location/Description____________ LPS$ADD_PRINTSERVER.COM SYS$MANAGER Sets up the supporting host to boot and configure a PrintServer printer. LPS$ADD_NETSETUP.COM SYS$MANAGER Creates an LPSNETSETUP.DAT file, which stores DECnet data for each PrintServer printer that is installed. LPS$NETSETUP.COM SYS$MANAGER Sets up the DECnet database parameters according to LPSNETSETUP.DAT. LPS$CONFIG.COM SYS$MANAGER Produces configuration, defaults, resource-loading, and setup files for the PrintServer printer. LPS$UPGRADE_PRINTSERVER.COM SYS$MANAGER Upgrades level 1 PostScript PrintServer printers to PostScript level 2. Files Added During Installation B-1 ________________________________________________________________ File____________________________Location/Description____________ LPS$OPTIONS.COM SYS$MANAGER Creates a customized LPSOPTIONS.printer- node-name file. LPS$START_DAEMON.COM SYS$MANAGER Starts a management client process (LPS$SERVICES.EXE) for the printer-node-name provided as a parameter. LPS$STARTUP_SERVICES.COM SYS$STARTUP Defines the LPS$SUPPORT and LPS$ROOT logicals and starts a management client process for each printer node name that has been defined. LPS$STOP_DAEMON.COM SYS$MANAGER Stops the management client process for the printer node name provided as a parameter. LPS_SETOUTPUTTR. SYS$COMMON:[SYSHLP.EXAMPLES.LPS] ULTRIX device control file that selects output trays on all PrintServer printers using the -o option to lpr. Provided for mixed ULTRIX and VMS environments. LPS_SETINPUTTRA. SYS$COMMON:[SYSHLP.EXAMPLES.LPS] ULTRIX device control file that selects input trays on all PrintServer printers using the -I option to lpr. Provided for mixed ULTRIX and VMS environments. LPS$DELETE_OLD_LPS.COM SYS$UPDATE Deletes obsolete files from ________________________________older_versions_of_the_software._ B-2 Files Added During Installation B.2 Informational Files The following file provides additional information about the PrintServer Software: ________________________________________________________________ File____________________________Location/Description____________ LPS051.RELEASE_NOTES SYS$HELP PrintServer Software release ________________________________notes.__________________________ B.3 Executable Files LPS$ROOT and LPS$SUPPORT are systemwide logical names that point to [LPS$SERVER]. The installation default device is SYS$SYSDEVICE. The following executable files are added during the installation: ________________________________________________________________ File____________________________Location/Description____________ LPS$ACCTREPORT.EXE SYS$SYSTEM Reads the centralized accounting file and produces a report. LPS$SERVICES.EXE SYS$SYSTEM Run by the LPS$START_DAEMON.COM when a management client is started. LPS$CONSOLE.EXE SYS$SYSTEM Remote console facility. LPS$XCONSOLE.EXE SYS$SYSTEM DECwindows Motif remote console facility. LPS$XCONSOLE.UID SYS$SYSTEM User interface definition file for the DECwindows Motif remote console facility. LPS$PRISM.EXE SYS$SYSTEM Printer Status Manager utility. Files Added During Installation B-3 ________________________________________________________________ File____________________________Location/Description____________ LPS$PRISM.UID SYS$SYSTEM User interface definition file for PRISM. LPS_PS.EXE LPS$ROOT:[SYS] PostScript level 2 image for PrintServer 20 and 32 plus printers with at least 16 MB of memory. LPS_PS_LEV1.EXE LPS$ROOT:[SYS] PostScript level 1 image for PrintServer 20/32 printers that do not upgrade to level 2. LPS_PRINTSERVER17.SYS LPS$ROOT:[SYS] PrintServer 17 series printer primary system image file. LPS_PRINTSERVER.SYS LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers primary system image file. LPS_PRINTSERVER40.SYS LPS$ROOT:[SYS] PrintServer 40 series printer primary system image file. LPS_LNVDRIVER.EXE LPS$ROOT:[SYS] PrintServer 40 series printer LNV11 driver. LPS_PS17.EXE LPS$ROOT:[SYS] PrintServer 17 series printer PostScript level 2 image file. LPS_PS17_MIN.EXE LPS$ROOT:[SYS] Minimal PrintServer 17 printer PostScript level 2 image file for printers with 8 MB memory. LPS_PS40.EXE LPS$ROOT:[SYS] PrintServer 40 series printer PostScript image file. B-4 Files Added During Installation ________________________________________________________________ File____________________________Location/Description____________ LPS_IMAGE.EXE LPS$ROOT:[SYS] PrintServer 32 and turbo PrintServer 20 printers Image interpreter. LPS_DMA.EXE LPS$ROOT:[SYS] turbo PrintServer 20 and PrintServer 32 plus printers PostScript level 2 video driver. LPS_DMA_LEV1.EXE LPS$ROOT:[SYS] turbo PrintServer 20 and PrintServer 32 printers PostScript level 1 video driver. LPS$NEWFILE.EXE LPS$ROOT:[SYS] Updates the accounting and logging files. LPS_PANEL.DUT LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Dutch front panel. LPS_PANEL.ENG LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers English front panel. LPS_PANEL.FRE LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers French front panel. LPS_PANEL.GER LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers German front panel. LPS_PANEL.ITA LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Italian front panel. Files Added During Installation B-5 ________________________________________________________________ File____________________________Location/Description____________ LPS_PANEL.NOR LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Norwegian front panel. LPS_PANEL.POR LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Portuguese front panel. LPS_PANEL.SPA LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Spanish front panel. LPS_PANEL.SWE LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 series printers Swedish front panel. LPS_CN1_PANEL.DUT LPS$ROOT:[SYS] PrintServer 17 series printer Dutch front panel. LPS_CN1_PANEL.ENG LPS$ROOT:[SYS] PrintServer 17 series printer English front panel. LPS_CN1_PANEL.FRE LPS$ROOT:[SYS] PrintServer 17 series printer French front panel. LPS_CN1_PANEL.GER LPS$ROOT:[SYS] PrintServer 17 series printer German front panel. LPS_CN1_PANEL.ITA LPS$ROOT:[SYS] PrintServer 17 series printer Italian front panel. LPS_CN1_PANEL.NOR LPS$ROOT:[SYS] PrintServer 17 series printer Norwegian front panel. B-6 Files Added During Installation ________________________________________________________________ File____________________________Location/Description____________ LPS_CN1_PANEL.POR LPS$ROOT:[SYS] PrintServer 17 series printer Portuguese front panel. LPS_CN1_PANEL.SPA LPS$ROOT:[SYS] PrintServer 17 series printer Spanish front panel. LPS_CN1_PANEL.SWE LPS$ROOT:[SYS] PrintServer 17 series printer Swedish front panel. LPS_CN1_VE.EXE LPS$ROOT:[SYS] PrintServer 17 series printer virtual engine. LPS_CNDRIVER.EXE LPS$ROOT:[SYS] PrintServer 17 series printer driver. LPS_DMA_S.EXE LPS$ROOT:[SYS] PrintServer 17 series printer video driver. LPS_PCSI.EXE LPS$ROOT:[SYS] PrintServer 20 series and PrintServer 32 seprinters driver. LPS_20VIDEO.EXE LPS$ROOT:[SYS] PrintServer 20 printer video driver. LPS_SNMPD.EXE LPS$ROOT:[SYS] ________________________________SNMP_MIB_II_image.______________ B.4 PostScript Files The following PostScript files are added during the installation: ________________________________________________________________ File____________________________Location/Description____________ LPS_ANSI_PROLOGUE.PS LPS$SUPPORT ANSI prologue. Files Added During Installation B-7 ________________________________________________________________ File____________________________Location/Description____________ LPS_PCLFONTSAMPLE.PS SYS$COMMON:[SYSHLP.EXAMPLES.LPS] PCL font sample. LPS_PRINTING_REF_CARD.PS LPS$SUPPORT and SYS$COMMON:[SYSHLP.EXAMPLES.LPS] Printing features reference card for OpenVMS and ULTRIX systems. LPS_STARTPAGE.PS LPS$SUPPORT and SYS$COMMON:[SYSHLP.EXAMPLES.LPS] PrintServer printer startup page, listing PostScript level 2 defaults. SHOW_PSLEV1_DEFAULTS.PS SYS$COMMON:[SYSHLP.EXAMPLES.LPS] PostScript level 1 defaults page. LPS_QLTY.PS LPS$SUPPORT Test patterns for use by Digital Services. LPS_QLTY_600.PS LPS$SUPPORT Test patterns for use by Digital Services. LPS_STATUSDICT.PS SYS$COMMON:[SYSHLP.EXAMPLES.LPS] Provides PostScript extension emulation. PS_SUPPLEMENT.PS LPS$SUPPORT Provides PostScript extension ________________________________emulation.______________________ B.5 Remote Console Facility Help Pages (Files) The following help pages are added during the installa- tion: ________________________________________________________________ File____________________________Location/Description____________ LPS_ABORT.S LPS$ROOT:[CAT] Help for abort command. B-8 Files Added During Installation ________________________________________________________________ File____________________________Location/Description____________ LPS_ACCEPT.S LPS$ROOT:[CAT] Help for accept command. LPS_CONFIGURATION.S LPS$ROOT:[CAT] Help for configuration command. LPS_CONTINUOUS.S LPS$ROOT:[CAT] Help for continuous command. LPS_EXIT.S LPS$ROOT:[CAT] Help for exit command. LPS_HELP.S LPS$ROOT:[CAT] Help for help command. LPS_JOBS.S LPS$ROOT:[CAT] Help for jobs command. LPS_NETSTAT.S LPS$ROOT:[CAT] Help for netstat command. LPS_NEWFILE.S LPS$ROOT:[CAT] Help for newfile command. LPS_NEXT.S LPS$ROOT:[CAT] Help for next command. LPS_PERMISSIONS.S LPS$ROOT:[CAT] Help for permissions command. LPS_PRIVS.S LPS$ROOT:[CAT] Help for privs command. LPS_REBOOT.S LPS$ROOT:[CAT] Help for reboot command. LPS_RECONFIGURE.S LPS$ROOT:[CAT] Help for reconfigure command. LPS_REJECT.S LPS$ROOT:[CAT] Help for reject command. LPS_REPEAT.S LPS$ROOT:[CAT] Help for repeat command. LPS_SHORTHELP.S LPS$ROOT:[CAT] Brief list of all help topics LPS_SINGLE.S LPS$ROOT:[CAT] Help for single command. Files Added During Installation B-9 ________________________________________________________________ File____________________________Location/Description____________ LPS_STATUS.S LPS$ROOT:[CAT] Help for status command. LPS_VERSIONS.S LPS$ROOT:[CAT] ________________________________Help_for_versions_command.______ B.6 Data Files The following data files are created after the installa- tion: ________________________________________________________________ File____________________________Location/Description____________ LPSACCT.printer-node-name LPS$SUPPORT Accounting file created by management client if accounting is enabled. LPSCONFIG.printer-node-name LPS$SUPPORT PrintServer printer configura- tion file created by LPS$CONFIG.COM. Records PrintServer printer options for accounting, logging, and access- control parameters. Also sets the printer's name (displayed in the remote console banner line) and the printer's password. LPSCONFIGDEFAULT.DAT LPS$SUPPORT Stores user-defined defaults for LPS$CONFIG.COM. LPSDEFAULTS.printer-node-name LPS$SUPPORT Printer defaults file, created by LPS$CONFIG.COM. LPSLOG.printer-node-name LPS$SUPPORT Event log file created by management client if logging is enabled. B-10 Files Added During Installation ________________________________________________________________ File____________________________Location/Description____________ LPSNETSETUP.DAT LPS$SUPPORT Created by the LPS$ADD_ NETSETUP.COM procedure. This file contains information for setting up the DECnet database parameters. LPSOPTIONS.printer-node-name LPS$SUPPORT Options file created by LPS$OPTIONS.COM, needed to run LPS$START_DAEMON.COM. LPSPCLDEFAULTS.printer-node- LPS$SUPPORT name PCL defaults file created by LPS$CONFIG.COM LPSRESOURCES.printer-node- LPS$SUPPORT name Resource-loading file created by LPS$CONFIG.COM. LPSSETUP.printer-node-name LPS$SUPPORT PostScript setup file created by LPS$CONFIG.COM. LPSSYSPARAMS.printer-node- LPS$SUPPORT name System parameter defaults file created by ________________________________LPS$CONFIG.COM._________________ Files Added During Installation B-11 C ________________________________________________________________ Obtaining the Ethernet Hardware Address C.1 Introduction The LPS$ADD_PRINTSERVER.COM procedure for setting up the PrintServer Software requires that you supply the Ethernet hardware address for the PrintServer printer. If this information has not already been made available, you can obtain the Ethernet hardware address from the printer. o The PrintServer 17 series, PrintServer 20 series, and PrintServer 32 series printers have an operator panel from which you can obtain the Ethernet hardware address. See Section C.2 for the procedure for obtaining the Ethernet hardware address from these PrintServer printers. o The PrintServer 40 Plus printer has a console terminal that you can use to obtain the Ethernet hardware address. See Section C.3 for the procedure for obtaining the Ethernet hardware address of the PrintServer 40 Plus printer. C.2 Obtaining the Ethernet Hardware Address from the Operator Panel The operator panel displays the sequence of events during the boot process, as well as the status of the printer at any given time. To determine the Ethernet hardware address, perform the following procedures: 1. Complete the printer installation, including connecting the printer to the Ethernet network. 2. Power on the printer. Obtaining the Ethernet Hardware Address C-1 The printer begins its warm-up and power-up diagnostics sequence. The window displays a countdown sequence beginning with the number 9. 3. When the countdown reaches the number 7, press on the front panel of the printer. 9,8,7 After a few minutes, the hardware address is displayed in the format shown in the following example: 08-00-2B-0C-48-EE 1.3 1.2 1.1 Pressing halts the boot process only; the power-up diagnostics continue to run. This halt does not damage the printer. It gives you time to record the Ethernet hardware address and to complete the supporting host software installation. 4. Power the printer off, then on. C.3 Obtaining the Ethernet Hardware Address from the Console Terminal The PrintServer 40 series printers display messages on the local console terminal. Place the PrintServer printer in console mode and examine a series of Digital Ethernet Q-bus Network Adapter (DEQNA or DELQA) device registers. The PrintServer 40 printer uses a DEQNA and the PrintServer 40 Plus printer uses a DELQA. Set the Halt switch on the back panel of the MicroVAX CPU to the Enabled (on) position. See the printer installation guide for instructions on setting this switch. C.3.1 Procedure To determine the Ethernet hardware address for a PrintServer 40 series printer, perform the following procedure: 1. If the console terminal does not display the >>> prompt, press the power ON/OFF switch on the PrintServer printer to the OFF position and then to the ON position. C-2 Obtaining the Ethernet Hardware Address 2. At the >>> prompt, enter the following command: >>> E/P/W/N:5 20001920 Obtaining the Ethernet Hardware Address C-3 The system displays six output strings of the form P 2000192x FFyy. For example: P 20001920 FF08 P 20001922 FF00 P 20001924 FF2B P 20001926 FF02 P 20001928 FFD4 P 2000192A FFC3 >>> The last two characters of each output string (yy), when joined consecutively and separated by hyphens, form the PrintServer printer Ethernet hardware address. The hardware address in this example is 08-00-2B-02-D4- C3. ________________________NOTE ________________________ Set the Halt switch on the MicroVAX CPU back panel to the Disabled (off) position after obtaining the Ethernet hardware address. _____________________________________________________ C-4 Obtaining the Ethernet Hardware Address D ________________________________________________________________ Digital PostScript Printer Software Documentation D.1 Digital PostScript Printer Software Documentation This appendix lists Digital software documents and documentation kits associated with PostScript printers, and their respective order numbers. The asterisk (*) in the order number stands for the latest version of the document or kit. D.1.1 PrintServer Software for ULTRIX The following is the PrintServer Software for ULTRIX documentation. Complete documentation kit (order number: QA-0V9AB-GZ) o PrintServer Software for ULTRIX Installation Guide o PrintServer Software for ULTRIX Management Guide o User Features Cards D.1.2 PrintServer Software for OpenVMS The following is the PrintServer Software for OpenVMS documentation. Complete documentation kit (order number: QA-0V9AA-GZ) o PrintServer Software for OpenVMS Installation Guide o PrintServer Software for OpenVMS Management Guide o User Features Cards Digital PostScript Printer Software Documentation D-1 D.1.3 PrintServer Software for UNIX The following is the PrintServer Software for UNIX documentation. Complete documentation kit (order number: QA-0V9AK-GZ) o PrintServer Software for UNIX Installation Guide o PrintServer Software for UNIX Management Guide o PrintServer Software for UNIX User's Guide D.1.4 PrintServer Software for NetWare The following is the PrintServer Software for NetWare documentation. Complete documentation kit (order number: QA-0V9AG-GZ) o PrintServer Software for NetWare Installation and Management Guide D.1.5 PrintServer Software for Windows The following is the PrintServer Software for Windows documentation. Complete documentation kit (order number: QA-0V9AH-GZ) o PrintServer Software for Windows Installation Guide D.1.6 PostScript Programming Documentation o PrintServer Printers PostScript Level 2 Programmer's Supplement (order number: EK-PRTPL-PS) o PostScript Printers Programmer's Supplement (order number: AA-HL84*-TE) D.1.7 DECfonts Typeface Collection Documentation can be ordered only as part of a media kit. For ULTRIX operating systems, the order number is QA- YX6AB-H*; for VMS operating systems, the order number is QA-YX6AA-H*. The asterisk is a 5 for TK50 medium or an M for magnetic tape. o DECfonts Typeface Collection Font Kit Installation and User's Guide D-2 Digital PostScript Printer Software Documentation D.1.8 DECprint Supervisor Software for OpenVMS The following is the DECprint Supervisor Software for OpenVMS documentation. Complete documentation kit (order number: QA-09NAA-GZ) o DECprint Supervisor Software Installation Guide o DECprint Supervisor User's Guide o DECprint Supervisor System Manager's Guide o DECprint Supervisor Installation Quick Reference Guide o DECprint Supervisor User's Reference Card D.1.9 Digital ANSI-Compliant Level 3 Printing Protocol The following is the Digital ANSI-Compliant Level 3 Printing Protocol documentation. Documentation kit (order number: QA-YNCA*-GZ) o Digital ANSI-Compliant Printing Protocol Level 3 Programming Reference Manual o Digital ANSI-Compliant Printing Protocol Level 3 Programming Supplement Digital PostScript Printer Software Documentation D-3 ________________________________________________________________ Index ?54 error, 6-2 Boot protocol, selecting, ?56 error, 6-2 5-3 ?57 error, 6-2 Boot requests 1501.0001 error, 6-2 checking, 6-3 determining origin of, A__________________________ 6-11 Aborted service requests filtered, 6-9 displaying, 6-7 filtering, 1-4 troubleshooting, 6-10 from another node, 6-11 Accounting Booting services, disabling enabling, 3-10 , 6-11 reliable, 3-10 BOOTP, 5-1 Accounting file, B-10 BYPASS privilege, 1-3 Area number, 3-4 Associated products, vii C__________________________ Automatic line services, -C option, 6-13 displaying, 6-7 CD-ROM, 1-4 B Client connections ___________________________ maximum, 1-1 BOOT command, 5-6 CMKRNL privilege, 1-2 Boot procedure configuration command, PrintServer 17 series 6-11, 6-15 printer, 5-1 Configuration file, B-10 PrintServer 20 series Configuration option, 6-13 printers, 5-4 Configuration services PrintServer 32 printer, checking, 6-13 5-4 enabling, 6-13 PrintServer 40 series Console client printer, 5-5 maximum connections, 1-1 Console terminal Ethernet hardware address , C-2 Index-1 Controller firmware version numbers E__________________________ PrintServer 17 series Errors printer, 5-2 severity, 2-10 PrintServer 20 series VMSINSTAL, 2-9 printers, 5-4 Ethernet controller, 1-4 PrintServer 32 printer, Ethernet hardware address, 5-4 3-5, C-1 CONVERT/SHARE command, console terminal, C-2 6-16 displaying, 3-6 Operator panel, C-1 D__________________________ Ethernet restrictions, 1-4 DDIF bitonal images, 3-11 Event log file DECnet access copying, 6-16 checking, 6-19 creating, 6-16 enabling, 3-12, 6-19 examining, 6-16 error message, 6-19 Event logging restricting, 3-12 enabling, 3-10, 6-16 DECnet address, 3-4 Executable files, 1-5 DECnet node name, 3-3 for OpenVMS Alpha DECnet Phase V, 1-5, 3-2 platforms, 1-5 troubleshooting, 3-7, 6-4 for OpenVMS VAX platforms DECnet requirements, 1-5 , 1-5 DECwindows files, B-7 DECwindows Motif for F__________________________ OpenVMS, 1-5 Files added during Defaults file, 5-2, 5-5, installation, B-1 B-1, B-10 Firmware version numbers Device timeout, 6-10 PrintServer 17 series DIP switches, setting, 5-3 printer, 5-2 Disk device PrintServer 20 series error, 2-12 printers, 5-4 specifying, 2-5 PrintServer 32 printer, Disk space, 1-3 5-4 displaying, 1-3 Front panel firmware error, 2-12 version numbers Documentation PrintServer 17 series Digital PostScript printer, 5-2 printers, D-1 Front panel language, 3-10 Front panel language files PrintServer 17 series printer, B-6 Index-2 Front panel language files (cont'd) K__________________________ PrintServer 20 series Kit contents, 1-5 printer, B-5 PrintServer 32 series L__________________________ printer, B-5 Large capacity input tray G firmware version numbers ___________________________ PrintServer 20 series Gateway address, 3-13 printers, 5-4 PrintServer 32 printer, H__________________________ 5-4 Hardware address, 3-5, C-1 Load Complete message, PrintServer 17 series 6-17 printer, 5-2 Local Area Network bridge, PrintServer 20 series 1-4 printer, 5-4 Logical names, B-3 PrintServer 32 printer, checking, 1-6, 6-3 5-4 defining, 1-6 Hardware connections, LPS$ROOT, 1-6 checking, 6-11 LPS$SUPPORT, 1-6 Hardware requirements, 1-3 SYSUAF, 1-6 Help files, B-8 LPS$ACCTREPORT.EXE file, B-3 I LPS$ADD_NETSETUP.COM file, ___________________________ B-1 Image interpreter, 3-11 LPS$ADD_PRINTSERVER.COM Input device, 1-4 file, 3-1, B-1 Installation procedure getting help, 3-3 sample session, A-1 invoking, 3-3 Installation time, 1-2 troubleshooting, 6-5 Internet access LPS$CONFIG.COM file, B-1 enabling, 3-13 LPS$CONSOLE.EXE file, B-3 restricting, 3-14 LPS$DELETE_OLD_LPS.COM troubleshooting, 6-19 file, B-2 Internet address, 3-13 LPS$NETSETUP.COM file, Internet gateway node 3-6, 6-5, B-1 address, 3-13 LPS$OPTIONS.COM file, Internet subnet mask, 3-13 6-13, B-1 LPS$ROOT logical, 3-18 checking, 1-6, 6-3 defining, 1-6, 6-3 Index-3 LPS$SERVER account, 2-5 LPSSERVICES_ERROR.printer- error, 2-11 node-name file, 6-16 specifying a UIC for, 1-7 LPSSERVICES_OUTPUT.printer- LPS$SERVICES process, node-name file, 6-16 checking, 6-13 LPSSETUP.printer-node-name LPS$SERVICES.EXE file, file, 6-17, B-11 B-2, B-3 LPSSYSPARAMS.printer-node- LPS$STARTUP_SERVICES.COM name file, 6-17, B-11 file, 3-18, 6-13, B-2 LPS_20VIDEO.EXE file, B-7 LPS$START_DAEMON.COM file, LPS_ANSI_PROLOGUE.PS file, 3-21, 6-14, 6-15, B-2 B-7 LPS$STOP_DAEMON.COM file, LPS_CN1_PANEL.language 3-21, 6-15, B-2 files, B-6 LPS$SUPPORT logical, 3-18 LPS_command_name.S files, checking, 1-6, 6-3 B-8 defining, 1-6, 6-3 LPS_DMA.EXE file, B-5 messages, 2-12 LPS_DMA_LEV1.EXE file, B-5 LPS$UPGRADE_PRINTSERVER.COM LPS_IMAGE.EXE file, B-4 file, 3-1, 3-20, B-1 LPS_LNVDRIVER.EXE file, LPS$XCONSOLE.EXE file, B-3 B-4 LPS$XCONSOLE.UID file, B-3 LPS_PANEL.language files, LPS051.RELEASE_NOTES file, B-5 B-3 LPS_PCLFONTSAMPLE.PS file, LPS051.x, contents, 1-5 B-7 LPSACCT.printer-node-name LPS_PCSI.EXE file, B-7 file, B-10 LPS_PRINTING_REF_CARD.PS LPSCONFIG.printer-node-name file, B-8 file, 3-7, 6-15, B-10 LPS_PRINTSERVER.SYS file, LPSDEFAULTS.printer-node- 5-4, B-4 name file, 6-17, B-10 LPS_PRINTSERVER17.SYS file, LPSLOG.printer-node-name 5-2, B-4 file, 6-18, B-10 LPS_PRINTSERVER40.SYS file, LPSNETSETUP.DAT file, 3-6, 5-6, B-4 B-10 LPS_PS17.EXE file, B-4 LPSOPTIONS.printer-node- LPS_PS17_MIN.EXE file, B-4 name file, B-2, B-11 LPS_PS40.EXE file, B-4 LPSPCLDEFAULTS.printer- LPS_QLTY.PS file, B-8 node-name file, 6-17, LPS_QLTY_600.PS file, B-8 B-11 LPS_SETINPUTTRA. file, B-2 LPSRESOURCES.printer-node- LPS_SETOUTPUTTR. file, B-2 name file, 6-17, B-11 LPS_SNMPD.EXE file, B-7 LPS_STARTPAGE.PS file, B-8 Index-4 LPS_STATUSDICT.PS file, NCP DEFINE command, 6-3 B-8 NCP HELP command, 6-4 NCP PURGE NODE command, M__________________________ 6-11 Maintenance operation NCP SET CIRCUIT command, protocol 3-7, 6-6 see MOP NCP SET command, 6-3 Management client NCP SET LOGGING MONITOR checking status, 6-14, command, 6-7 6-16 NCP SHOW CIRCUIT command, connection attempts, 6-15 3-7, 6-6 enabling configuration NCP SHOW NODE command, 6-5 services, 6-13 NCP TELL command, 6-10 error, 3-19, 3-21, 6-15 Network bridges, 6-9 messages, 6-17 Network configuration starting, 3-18, 6-14, checking, 6-9 6-15 troubleshooting, 6-3 starting automatically, Network devices, checking, 3-19, 6-13 6-11 starting on a cluster, Network events displaying, 6-7 3-19 enabling, 6-7 stopping, 3-21, 6-15 logging, 6-7 troubleshooting, 6-12 monitoring, 6-3 MAXSYSGROUP parameter, 1-7 Network requests Media filtering, 6-9 mounting, 2-3 Network routers, 6-9 supported, 1-4 newfile command, 6-16 MOP, 5-1 Node name, 3-3 checking, 3-2, 6-4 Node number, 3-4 starting, 6-4 Multiple supporting hosts, O__________________________ configuring, 3-19 OPCOM, 6-8 N enabling, 6-8 ___________________________ messages, 6-8, 6-10 NCL commands, 3-7, 6-4, OpenVMS Alpha software 6-5 error, 2-13 NCL SHOW MOP command, 3-2, requirement, 1-5 6-5 system startup file, 3-18 NCP CLEAR NODE command, OpenVMS VAX software 6-11 error, 2-13 NCP database requirement, 1-5 checking, 6-5, 6-6 system startup file, 3-18 Index-5 Operating system software Primary boot process errors, 2-13 (cont'd) requirements, 1-5 PrintServer 32 printer, Operator panel 5-4 displaying the ethernet PrintServer 40 series hardware address, C-1 printer, 5-6 firmware version numbers, troubleshooting, 6-2 5-2 Primary system image files, Operator panel language, B-4 3-10 Print client Operator panel language maximum connections, 1-1 files, B-5 Print client problems OPTIONS N parameter, 2-2 troubleshooting, 6-18 Print engine firmware P__________________________ version numbers Page count, PrintServer 17 PrintServer 17 series series printer, 5-2 printer, 5-2 Password, 3-9 PrintServer 20 series PCL defaults file, B-11 printers, 5-4 PCL font sample file, B-8 PrintServer 32 printer, permissions command, 6-19 5-4 Postinstallation procedures Print queue, setting up, , 2-7 6-20 PostScript extension Printer emulation file, B-8 supported types, 1-4 PostScript level 1 defaults Printer documentation, D-1 file, B-8 Printer driver files, B-7 PostScript level 2 defaults Printing access problems file, B-8 troubleshooting, 6-18 PostScript setup file, Printing reference card, B-11 B-8 Primary boot PrintServer 17 printer checking status of, 6-10 upgrading, 3-1 error message, 6-10 PrintServer 17 series Primary boot process printer checking, 6-10 booting, 5-1 error, 6-10 finding the Ethernet errors, 6-2 hardware address, C-1 PrintServer 17 series front panel language printer, 5-2 files, B-6 PrintServer 20 series PrintServer 20 printer printers, 5-4 selecting the boot protocol, 5-3 Index-6 PrintServer 20 series Resource-loading file, printer B-1, B-11 booting, 5-4 finding the Ethernet S__________________________ hardware address, C-1 Sample installation session front panel language , A-1 files, B-5 Save sets, 1-5 PrintServer 32 printer Secondary boot process booting, 5-4 error, 6-2 PrintServer 32 series PrintServer 17 series printer printer, 5-3 finding the Ethernet PrintServer 20 series hardware address, C-1 printers, 5-4 front panel language PrintServer 32 printer, files, B-5 5-4 PrintServer 40 series PrintServer 40 series printer printer, 5-6 booting, 5-5 troubleshooting, 6-2, finding the Ethernet 6-12 hardware address, C-1 Service circuit, 3-5 PrintServer name, 3-3 checking, 3-7, 6-6 Privileges, 1-2 enabling, 3-6, 6-6 Problems, reporting, 5-6 SETPRV privilege, 1-2 PS_SUPPLEMENT.PS file, B-8 Setup file, 5-2, 5-5, B-1 R SHOW DEVICE command, 1-3 ___________________________ SHOW LOGGING MONITOR reconfigure command, 6-19 command, 6-7 Release notes, 2-2 SHOW LOGICAL command, 1-6 copying, 2-4 SHOW MAXSYSGROUP command, displaying, 1-6, 2-4 1-7 file name, 2-4 SHOW SYSTEM command, 6-8, location, 1-6, 2-4 6-13, 6-15 printing, 2-4 SHOW_PSLEV1_DEFAULTS.PS Remote console facility, file, B-8 1-5, 6-11, B-3 Software executable files, B-3 DECnet, 1-5 help files, B-8 mounting, 2-3 invoking, 6-14 operating system, 1-5 requirements, 1-5 upgrading, 3-20 REPLY/ENABLE command, 6-8 Software version Resource file, 5-2, 5-5 error, 2-13 Index-7 Startup file SYSUAF logical, 1-6 editing, 3-18 SYSUAF.DAT file enabling on a standalone error, 2-11 system, 3-18 enabling on a VAXcluster T__________________________ node, 3-19 TCP/IP error, 3-19 see Internet Startup page, 5-3, 5-5 Test patterns, B-8 Startup page file, 5-2, Time to install, 1-2 5-5, B-8 TK50 cartridge, 1-4 Supporting host logical names U setting, 3-18 ___________________________ SYS$STARTUP:SYSTARTUP_ UIC V5.COM file default, 1-7 editing, 3-19 displaying, 1-7 SYS$SYSDEVICE disk device, error, 2-13 2-5 specifying, 2-5 SYSPRV privilege, 1-2 ULTRIX nodes SYSTARTUP_V5.COM file accepting print jobs editing, 3-18 from, 3-13 SYSTARTUP_VMS.COM file, UNIX nodes 3-18 accepting print jobs System authorization file from, 3-13 error, 2-11 Upgrade restrictions, System file 3-21, 6-15 PrintServer 17 series User Identification Code printer, 5-2 See UIC PrintServer 20 series printers, 5-4 V__________________________ PrintServer 32 printer, Video driver files, B-7 5-4 VMSINSTAL, 2-1 PrintServer 40 series errors, 2-9 printer, 5-6 getting help, 2-1 System Generation utility, invoking, 2-1 1-7 terminating, 2-1 System parameter defaults file, B-11 W__________________________ System startup file, 6-13 Waiting for configuration editing, 3-18, 3-19 message, 6-14 enabling on a standalone WORLD privilege, 1-3 system, 3-18 enabling on a VAXcluster node, 3-19 Index-8