System Administration and Operations Guide for Windows NT
Version 1.2 Pub# 613P07290 July 1998 Xerox Corporation 701 South Aviation Boulevard El Segundo, CA 90245 Publication #613P07290
Copyright 1997-1998 Xerox Corporation. All rights reserved. Portions of this software also include copywritten software modules from Sun Microsystems, Digital Equipment Corporation, and Raima Corporation.
Copyright protection claimed includes all forms and matters of copyrightable material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs which are displayed on the screen, such as icons, screen displays, looks, etc.
Xerox, The Document Company, the stylized X, and all Xerox product names mentioned in this publication are trademarks of Xerox Corporation. Sun, SPARCstation, NIS, NIS+, OpenWindows, and Solaris are registered trademarks of Sun Microsystems, Inc. Microsoft, Windows NT, Windows 95, and LAN Manager are registered trademarks of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. Digital is a registered trademark of Digital Equipment Corporation. Apple and Macintosh are registered trademarks of Adobe Systems Incorporated. NetWare is a registered trademark of Novell, Incorporated. Common Desktop Environment is a copyright of the Common Operating System Environment. Other product names used herein are trademarks of their respective owners.
Changes are periodically made to this document. Changes, technical inaccuracies, and typographic errors will be corrected in subsequent editions. Printed in the United States of America. Table of contents
1. About this guide 1-1
Audience 1-1
Conventions used in this manual 1-1
Related publications 1-2 2. PrintXchange overview 2-1
Concepts and terminology 2-1
PrintXchange features and benefits 2-3
PrintXchange printing system components 2-15
Interoperability 2-22
Multinational considerations 2-24 3. System requirements 3-1
Software requirements 3-1
Network requirements 3-2
Hardware requirements 3-2 4. Recommended configuration planning 4-1
Configuration roadmap 4-1 5. Planning a PrintXchange installation 5-1
Determining components, objects, and end-user privileges 5-1 6. Installing and setting up PrintXchange on a server machine 6-1
Overview of the CD contents 6-1
Overview of the installation and set-up process for Windows NT Server 6-2
Installing Windows NT gateways from the Solaris Server package 6-33
Validating your PrintXchange installation 6-41
Using the setup PrintXchange tool 6-45
Uninstalling PrintXchange from a server machine 6-56
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT iii TABLE OF CONTENTS
7. Installing and setting up PrintXchange on a client machine 7-1
Overview of the CD contents 7-1
Overview of the installation and set-up process 7-2
Post-installation 7-11
Using the PrintXchange Client Setup tool 7-11
Uninstalling PrintXchange from a client machine 7-13 8. Managing security 8-1
Name Services 8-1
PrintXchange Name Service properties setup 8-9
Security 8-10
Access Control Lists (ACLs) 8-17
File transfer 8-23 9. Setting event notification 9-1
Event notification 9-1
Notification server 9-8
Specifying profiles 9-8 10. Configuring, starting and stopping servers 10-1
Creating and configuring servers 10-1
Preprocessor and PDL guesser 10-5 11. Creating, configuring and enabling queues, physical and logical printers 11-1
Creating queues 11-1
Creating and configuring physical printers 11-3
Creating and configuring logical printers 11-10
Enabling and testing your PrintXchange system 11-16 12. Using the CLI and GUI 12-1
Command Line Interface (CLI) 12-1
CLI syntax 12-4
Summary of command options 12-5
Graphical user interface 12-7 13. Getting status of PrintXchange objects 13-1
Understanding object states 13-2
Listing object attributes 13-6
iv PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TABLE OF CONTENTS
14. Managing jobs and documents 14-1
Printing jobs and documents 14-2
Printing a jobs after a specified time 14-5
Holding and releasing jobs 14-7
Pausing and resuming jobs 14-9
Retaining jobs 14-11
Modifying job and document attributes 14-14
Setting job priorities 14-16
Resubmitting jobs to a logical printer 14-18
Deleting job and document defaults 14-21
Modifying default job priorities 14-22
Promoting jobs 14-22
Modifying default job priorities 14-22
Deleting jobs 14-24
Canceling jobs 14-25
Discarding jobs with print deadlines 14-27
Listing a job queue 14-29
Listing names and attributes of jobs and documents 14-31
Removing all jobs from a server or queue – Cleaning objects 14-33 15. Setting and modifying object attributes 15-1
CLI modification operators 15-2
Allowed attributes for set and modify 15-3
Setting mapping attributes 15-19
Setting xxx-supported and xxx-ready attributes 15-22
Updating the OID database 15-30 16. Pausing and resuming objects 16-1
Pausing and resuming PrintXchange objects 16-2
Pausing spoolers 16-3
Resuming spoolers 16-4
Pausing queues 16-5
Resuming queues 16-6
Pausing physical printers 16-7
Resuming physical printers 16-8
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT v TABLE OF CONTENTS
17. Enabling and disabling objects 17-1
Enabling and disabling PrintXchange objects 17-2
Enabling spoolers and supervisors 17-3
Disabling spoolers and supervisors 17-4
Enabling queues 17-5
Disabling queues 17-5
Enabling physical printers 17-6
Disabling physical printers 17-7
Enabling logical printers 17-8
Disabling logical printers 17-9 18. Removing (deleting) objects 18-1
Removing (deleting) PrintXchange objects 18-1
Deleting a spooler 18-3
Deleting a supervisor 18-4
Deleting a queue 18-5
Deleting a physical printer 18-6
Deleting a logical printer 18-8
Deleting an initial-value-job 18-9
Deleting an initial-value-document 18-9 19. Creating accounting reports 19-1
Enabling accounting 19-2
Accounting profile 19-3
Using the account report writer 19-5 20. Inbound gateways 20-1
Inbound gateways 20-2
LAN Manager inbound gateway 20-10
NetWare QServer inbound gateway 20-16
NetWare client optional features 20-29
LPR inbound gateway 20-30 21. Managing printed output 21-1
Requesting a specific output device 21-1
Specifying number of copies 21-1
Specifying highlight color 21-2
vi PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TABLE OF CONTENTS
Specifying separator pages 21-3
Specifying media, input trays, and output bins 21-6
Specifying finishing 21-6
Resetting the printer 21-7 22. Troubleshooting 22-1
Troubleshooting introduction 22-1
System logging 22-10
Restrictions for e-mail notification on Windows NT 22-24
Message descriptions 22-26
Crash recovery 22-150 Appendices
A. Printers data sheets A-1
B. Server startup commands, switches and status exit codes B-1
C. Working with object databases C-1
D. SNMP query support D-1 Glossary of terms and abbreviations Index
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT vii TABLE OF CONTENTS
viii PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 1. About this guide
The PrintXchange System Administration and Operations Guide for Windows NT describes the tasks required to: Plan the configuration Install the software Configure the system Operate the system. This chapter introduces the audience, organization of the content, and conventions used in this manual. The chapter also includes a list of additional PrintXchange documentation.
Audience
The intended audience for the guide includes:: System administrators, responsible for managing the printing system environment; and Operators, responsible for running day-to-day operations.
Conventions used in this manual
The second person (“you”) is primarily used in this manual to address all users. “User” refers in general to system administrators, operators, and end users alike, and is used whenever the topic deals with general PrintXchange functions, such as “end user.” “End user” refers to any person other than the system administrator or operator, and is used whenever the topic deals with a particular system administrator function, such as defining end user privileges. Attributes are written in bold letters. Example: initial-value-job CLI commands, in examples, are written in plain text. Elsewhere, they are bold, italic. Example: The pdenable command creates an object... Variable names are written in italic. Example: [spooler_name:]job_identifier.doc_integer Text or characters that you type, such as examples of CLI commands, are written in courier new font. Example: Pdenable –h
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 1-1 ABOUT THIS GUIDE
Related publications
In addition to this guide, the following PrintXchange publications are available: PrintXchange System Administration and Operations Guide for UNIX This guide explains explaining installation and day-to-day management of the PrintXchange system in the UNIX environment. It is primarily intended for administrator and operator use. PrintXchange Command Line Interface Reference Guide This guide provides information on maintaining and operating the PrintXchange system using the Command Line Interface (CLI). It is primarily intended for system administrator use and access to advanced printing functions. PrintXchange Command Line Interface User Guide for Windows NT This guide provides information on submitting jobs to your printer using the command line on your workstation. It is available to CLI users in the Windows NT environment. PrintXchange Command Line Interface User Guide for UNIX This guide provides information on submitting jobs to your printer using the command line on your workstation. It is available to CLI users in the UNIX environment. PrintXchange Windows NT Help These are on-line help files that provide information on PrintXchange functionality. It is available to Windows NT users. PrintXchange UNIX CDE Help These are on-line help files that provide information on PrintXchange functionality. It is available to UNIX users. PrintXchange UNIX MAN pages This is a quick reference for information on PrintXchange commands. They are available to all UNIX users.
1-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2. PrintXchange overview
PrintXchange is an enterprise print system that gives system administrators and operators a set of tools for job submission and print system management. It enables end users to print documents and monitor their print jobs on their operating system platform.
Concepts and terminology
This section defines the basic concepts and terminology that you need to understand to properly manage and run the PrintXchange system. Note: The terms and concepts defined in this section are presented in a progressive manner, beginning with a description of a basic PrintXchange printing system and continuing with a description of each system component.
The basic printing system
The basic printing system uses a client/server architecture that consists of three primary components (client, server, and output device) as illustrated below. Figure 2-1. Basic printing system
Job & Device Print Data Status Requests Output Requests Jobs Client Server Device Job Ctrl (Printer) Responses Status
Client
The client initiates print and system administration operations. It serves as the user’s agent to convey print and management requests to the server. Print requests are requests to print files on an output device. Print data consists of text and/or graphics created by a user. Management requests are requests to manage printing system components, such as adding or deleting printers, or canceling print requests. Responses to the client are information from the server that arise from submitted requests.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOWINDOWS NT 2-1 PRINTXCHANGE OVERVIEW
Server
The server receives requests from the client, performs the actions required for each request operation, and returns responses to the client. From the files submitted by the client on a print request, the server creates documents and organizes the documents into jobs. A document represents a single user file to be printed. A job represents a collection of one or more documents to be printed as a unit. The job also contains instructions for printing, such as production and finishing instructions, and notification of job status. The server sends jobs and associated document print data, as well as applicable job control commands to an output device.
Output device (printer)
The output device is typically referred to as the printer. It is the physical device or hardware that is capable of rendering images or documents and producing hard copy output of the jobs that it receives from the server. The output device receives the jobs (including the print data) and job control commands from the server. Depending on its type or its set of features, the output device returns responses to the server. Output devices respond with at least a message indicating their current state.
2-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
PrintXchange features and benefits
The PrintXchange printing system expands on the basic printing system by providing support for different types of clients, and using a server system rather than a single server, as illustrated below. Figure 2-2. PrintXchange clients and servers
PrintXchange
Server System
CLI Client Reference Output Supervisor Device A GUI Spooler Client LPR LPR User GW Inbound Xerox Output Gateway Supervisor Device B LM LM Clients User GW NW NW GW User PrintXchange supports different types of clients: Command Line Interface (CLI) Graphical User Interface (GUI) Inbound gateway clients (LAN Manager, LPR, and Novell NetWare). In the PrintXchange server system, the server functions are split between two different server types: Spooler Supervisor. PrintXchange further differentiates between two types of supervisors: Reference supervisor Xerox supervisor.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-3 PRINTXCHANGE OVERVIEW
Figure 2-3. Simplified PrintXchange printing system
Print Data Disk
Server System
Spooler Server Supervisor Server Reference Xerox Job and Device Print Data Mgmt Reqs Status Requests Client Logical Responses Physica Job Data Output CLI Mgmt Requests Printer l Printer Device GUI Job Ctrl Inbound Print Requests Logical Jobs Responses Gateway Printer Job and Device s Queue Status/Events Status Requests Logical Physica Responses Job Data Printer Mgmt Reqs l Printer Output Device Job Ctrl Responses Responses
As illustrated in figure 2-3, PrintXchange also uses two different abstractions called objects to indicate the characteristics of the multiple output devices that it can support: Logical printer Physical printer. The PrintXchange system further uses the concept of queues to associate groups of logical printers with groups of physical printers. Figure 2-3 illustrates a simplified PrintXchange system with all of the primary elements.
2-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
PrintXchange client interfaces
The client interfaces enable PrintXchange users to perform printing operations, including: Submit print requests Resubmit jobs Promote jobs Cancel jobs List attributes of PrintXchange printing elements Modify jobs Pause and resume jobs. The client interfaces also allow users to perform configuration and maintenance operations, including: Create and delete PrintXchange elements Enable and disable PrintXchange elements Pause and resume PrintXchange elements Set attributes of PrintXchange printing elements Delete all jobs from a spooler or queue Shut down servers.
Command line interface (CLI)
The CLI consists of a set of commands that allow users to perform printing system operations. Users run commands by entering them in the command or terminal window. The commands include parameters that identify applicable PrintXchange printing elements (commonly referred to as “objects”) and options.
Graphical user interface (GUI)
The graphical user interface (GUI) client consists of applications that execute on the user’s Windows NT or Windows 95. The graphical nature of the GUI interface makes it easier for the novice user to perform print operations, yet allows advanced users to perform the more complex configuration and maintenance operations. The GUI client applications are: Print job submission and job control Printer information Administration Event monitor.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-5 PRINTXCHANGE OVERVIEW
Print job submission and job control This application gives users the ability to use the standard Microsoft Windows 95 and Windows NT printing interface with a PrintXchange logical printer. The application operates with either a PrintXchange NT or UNIX server. The application allows users to: Print jobs View job status Cancel jobs Pause jobs Resume jobs Set job attributes (that do not affect document formatting) prior to job submission Receive notification events about jobs View printer properties. Printer information This application runs on a Windows NT, Windows 95 or Solaris system. The Windows NT and Windows 95 platforms operate with either a PrintXchange NT or UNIX server. This application on the Solaris platform only operates with the UNIX Solaris server. The application allows users or operators access to information about the jobs and logical printers currently in the system. Users can also modify attributes of submitted jobs. More specifically, this application allows users to: List all available printers in the local domain, or in the specified domain Obtain the current capabilities, status, and supported functionality of the specified logical printer List information with the ability to filter the information Pause, resume, promote, resubmit, cancel, enable, and disable the specified job or printer if the user has the appropriate authorization Customize the information displayed Modify a previously submitted job. Administration This application runs on a Windows NT or Windows 95 system. It operates with either a PrintXchange NT or UNIX server. The application allows administrators to perform server and printer administration tasks: List all available spoolers, supervisors, queues, logical printers, physical printers, etc., in the local domain, or in the specified domain Obtain and modify attributes of system objects Create and delete system objects Access objects directly or indirectly through other objects Add and delete users to the system and set their privilege level Add and delete default event notifications for each object in the system Perform all operations available through the Printer Information application. Event monitor This application provides notification to the end user of PrintXchange events through pop-up message windows.
2-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Inbound gateway clients
PrintXchange supports job submission from LAN Manager, LPR, and Novell NetWare clients. Submitting jobs from these clients requires installation of the Gateway Services components of the PrintXchange server software. For additional details, refer to the PrintXchange Printing System Components Gateway Services section.
PrintXchange servers
In the PrintXchange server system, the server functions are split between two different server types: Spooler Supervisor.
Spooler
Through a logical printer, the spooler receives a client print request for a job that includes print data or a reference to the print data for one or more documents. The spooler then schedules the job on an appropriate physical printer associated with the specified logical printer. At the appropriate time, the spooler forwards the job to the supervisor associated with the physical printer on which the spooler scheduled the job. Note: A spooler can support multiple supervisors. The spooler also receives client management requests that apply to the spooler or to spooler elements, which include logical printers and queues. The spooler forwards to the supervisor any client management requests that may no longer apply to the spooler, such as delete job; if the spooler has already sent the job to the supervisor, it forwards a client delete job request to the supervisor. The spooler returns appropriate responses to requests from the supervisor, such as next job requests, status reports or printer jams.
Supervisor
The supervisor delivers data to output devices. The supervisor: Receives jobs from the spooler Interprets job requests for print instructions and parameters Receives print data, or a reference to it, from the spooler Passes print data and applicable job control commands to the appropriate output device Handles any responses made by the output device. The supervisor receives client management requests that apply to the supervisor or to supervisor elements, which include physical printers. It also receives client management requests forwarded by the spooler. Information sent from the supervisor to the spooler consists of management requests, such as for example, request for next job and status updates, such as job completed; and notification, such as job canceled by user.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-7 PRINTXCHANGE OVERVIEW
PrintXchange supports two types of supervisors: Reference supervisors Xerox supervisors. Reference supervisor The reference supervisor is used for printers directly controlled by PrintXchange. It supports printers connected to the host by parallel, serial, ip-socket and Digital PrintServer connections. It provides device status for serial and ip-socket connected printers using the printer’s PostScript bi-directional status interface. The reference supervisor directly controls all aspects of printing a job including: Transfers data directly to the printer. Creates and transfers separator pages Interprets and acts upon messages coming back from a printer. Xerox supervisor The Xerox supervisor provides connectivity to printers capable of supporting: RFC 1179 protocol Simple network management protocol (SNMP) Via the DocuPrint NPS and DocuSP print servers, the Xerox supervisor also provides connectivity to most of the major Xerox production printers: DocuTech 6135, 6180 (via DocuSP) FX printers 4050, 4090, 4635, 4850, 4890 (via DocuPrint NPS) The primary functions of the Xerox supervisor are: Perform job submissions using RFC 1179 lpr Perform job cancellations using RFC 1179 lprm, if possible Perform job status queries via: RFC 1179 lpq Xerox production printer statusing (XPPQ) SNMP. Perform output device (printer) status queries from: Xerox production printer statusing (XPPQ), for DocuSP only SNMP.
2-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
PrintXchange logical/physical printers and queues
The PrintXchange system uses the concept of logical printers to represent physical printers in a more user-friendly fashion. To a user, the model of the printer is not as important as the capabilities of the printer. PrintXchange provides the user with a means of submitting jobs to an entity that describes the characteristics of the output device such as duplex, color and highlight color. The PrintXchange system further uses the concept of queues to configure a set of logical printers to physical printers.
Physical and logical printers
A physical printer represents the actual output device, such as a Xerox 4230 laser printer. A logical printer indicates particular characteristics and capabilities of one or more physical printers. It is an abstraction of printer capability. It serves as a defaulting device as well as a gateway into the system. Users direct their print requests to the logical printers with the characteristics that fit their needs. The spooler channels the requests via a queue to a supervisor that supports a physical printer mapped to the specified logical printer through the queue.
Queues
A queue associates a set of jobs with a set of logical and physical printers. It serves as a pool that holds the jobs until the spooler can send them to the appropriate supervisor. Logical printers feed jobs into a queue; physical printers request jobs from a queue. A logical printer is associated with only one queue and can feed jobs into only that one queue. Similarly, a physical printer is associated with only one queue and can request jobs only from that queue.
Printer/queue associations
As the administrator, you link logical printers, physical printers, and queues to each other. The links, or associations, reflect your plan for utilizing the output devices on your site to the best advantage. Jobs submitted to a logical printer are placed in a queue and scheduled for printing on a physical printer that matches the document characteristics specified. Logical printers are mapped to physical printers through a queue. For purposes of balancing print loads, multiple similar physical printers can be mapped to a logical printer. Conversely, multiple logical printers can be mapped to a physical printer. Logical printers define default printing setups for a physical printer and enable job queue management based on the availability of the characteristics requested for a job. For example, logical printers could be created for each paper size available on a physical printer. If the printer is currently out of the requested paper size, jobs submitted to that specific logical printer will remain in a held state until this capability becomes available.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-9 PRINTXCHANGE OVERVIEW
Figure 2-5 illustrates the simple case where there is only one logical printer, one queue, and one physical printer. In this case, the logical printer serves simply as a view or representation of the physical printer to the user. The user-defined associations for this case are LP1-Q1 and PP1-Q1. These associations create an implicit relationship between LP1-PP1. Figure 2-5. Logical printer as simple representation of physical printer
Logical Printer (LP) Queue (Q) Physical Printer (PP)
LP1 PP1 Black & White Black & White Highlight Color Highlight Color Q1 Large Paper Large Paper Staple Staple
Figure 2-6 illustrates multiple logical printers feeding a queue that serves only one physical printer. In this case, the logical printers provide the user with different defaults for a job submitted to a common printer. The user-defined associations for this case are: LP1-Q1, LP2-Q1, LP3-Q1, PP1-Q1.
Figure 2-6. Logical printers serving as default mechanism
Logical Printers (LP) Queue (Q) Physical Printer (PP)
LP1 Black & White Staple
PP1 LP2 Black & White Highlight Color Q1 Highlight Color Staple Large Paper Staple LP3 Black & White Large Paper
2-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Figure 2-7 illustrates a more complex case of multiple logical printers and multiple physical printers. In this example, large paper jobs from LP1 can print on either PP1 or PP2 depending on which printer is not busy. Since PrintXchange has the intelligence to schedule jobs based on the characteristics defined in the user’s print request, it will automatically only send the LP2 Black & White Stapling jobs to PP2 since the system knows that PP1 does not have finishing capability to staple jobs. Figure 2-7. Logical printers providing load balancing
Logical Printers (LP) Queues (Q) Physical Printers (PP)
PP1 LP1 Large Paper Large Paper Black & White
Q1 PP2 LP2 Large Paper Black & White Black & White Staple Staple
PP3 Black & White LP3 Highlight Color Highlight Color Q2
LP4 Black & White
Objects and attributes
PrintXchange uses objects to represent various entities, such as server, printer, and queue. A spooler and a supervisor are both server objects; a logical printer and a physical printer are printer objects. PrintXchange objects This section on concepts and terminology has introduced you the PrintXchange objects, namely: Spooler Supervisor Queue Logical printer Physical printer Job Document.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-11 PRINTXCHANGE OVERVIEW
PrintXchange has two additional objects that enable you to set defaults on certain printing aspects of jobs and documents, such as the number of copies to be printed or the default input tray. The two objects are: Initial-value-job object that specifies defaults for jobs Initial-value-document object that specifies defaults for documents. Typically, administrators apply an initial-value-job and/or an initial- value-document object to a logical printer. When a client submits print requests to the logical printer, the logical printer applies the defaults to the jobs and documents. Users may also apply an initial- value-job and/or an initial-value-document object by specifying it with the print request. Spooler objects contain queue, logical printer, initial-value-job, and initial-value-document objects. Supervisor objects contain physical printer objects. The administrator creates the queue, logical and physical printer, and initial-value-job and initial-value document objects using create object commands. These objects, including the spooler and supervisor objects, are persistent. That is, the objects continue to exist across restarts of the system. The spooler and supervisor also contain job and document objects. PrintXchange creates the job and document objects in response to print requests. Jobs and documents exist only until the job completes printing or until the end of a specified retention period. Object attributes An object contains a collection of attributes that provide information about the object. An attribute indicates a characteristic of an object relating to its identity, physical makeup, or status. Examples of printer object attributes are: printer-name, a single-valued attribute whose value is a name that uniquely identifies a printer, whether logical or physical media-supported, a multi-valued attribute whose values identify the media that the printer supports such as iso-a4-white and iso- a4-transparent printer-state, a single-valued attribute that indicates the current status of a printer such as idle or printing. The attributes associated with an object define the configuration and behavior of the object. The spooler and supervisor servers manipulate the object representation of an entity they are operating on by setting or changing the values of the object’s attributes. A user observes the value of an attribute with a list attributes command and changes the value of an attribute with a set or modify attributes command. Attribute=value pairs Attribute names have a hyphenated format, such as default-input- tray and job-copies. An attribute=value pair indicates a particular value for the attribute. For example:
default-input-tray=top job-copies=3
2-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Administrator and operator operations
Commands enable you to manipulate PrintXchange objects. Operations are subject to access control. Only users with an appropriate access level may run certain operations. PrintXchange recognizes three access levels: End User, Operator, and Administrator. End Users have access to only certain operations. Administrators, have access to all operations. Operator access falls in between. Table 2-1 lists the operations, provides a brief description and specifies the access level and objects valid for each operation. Table 2-1. Operations summary
Operations Description Administrator Operator End user Valid objects
Cancel job Cancel previously End User Job submitted print jobs. (Job owner)
Clean Delete all jobs from the Operator Spooler, queue specified object.
Create Create objects, and set Administrator Queue, logical their attributes to the printer, physical specified values: (initial- printer, i-v-job, value-job, initial-value- i-v-doc document)
Delete Delete objects. Administrator All
Disable Disable the acceptance Operator Spooler, supervisor, of new print requests or queue, logical jobs. printer, physical printer Enable Enable the acceptance Operator Spooler, supervisor, of new print requests or queue, logical jobs. printer, physical printer List job queue List the jobs and End User Job, document requested job or document status attributes submitted to a specified logical printer associated with a queue.
List object List the names of print End User All attributes objects and the names and values of their attributes.
Modify Change the values of End User Job, document specified job or (Job document attributes. owner)
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-13 PRINTXCHANGE OVERVIEW
Table 2-1. Operations summary (continued)
Operations Description Administrator Operator End user Valid objects
Pause Pause the specified Operator End User Spooler, queue, object so that it does (job owner physical printer, job not produce further only) output.
Print Submit a print request. End User Not applicable
Promote Schedule the specified Operator Job job for printing on the next available requested printer.
Resubmit Resubmit the specified Operator End User Job, queue job, or jobs in the (job owner specified queue, to a only), specified logical printer.
Resume Resume the specified Operator End User Spooler, queue, object so that it (job owner physical printer, job continues normal only) operation.
Set attributes Set attribute values of Administrator End User All specified print objects. (job owner only) Shutdown Shut down the specified Operator Spooler, supervisor server.
2-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
PrintXchange printing system components
The first section of this chapter defined concepts and terminology used to describe a basic printing system as well as a simplified PrintXchange printing system. This section further describes the PrintXchange printing system by presenting an overall view of its primary components and then providing a closer look at the ones that were not covered in the prior section. The primary software components of the PrintXchange printing system are: Infrastructure Clients Servers.
Infrastructure
The PrintXchange infrastructure consists of facilities that provide general distributed services to all PrintXchange components. Many of the facilities function internally to the system, that is, users have no direct access to them. Example: Facilities that provide direct access to system databases or that provide communications handling in distributed systems. Such facilities do not fall within the scope of this document, and are therefore not described. Several facilities, however, require that users specify parameters dictating how certain aspects of the facilities should function in the local environment. These facilities are: Name services. Administrative users must configure the name service to allow the printing system to locate objects in the system. Security services. Administrative users must specify access levels for all users of the printing system. File transfer. Users must specify how PrintXchange should transfer files between the client and spooler and/or supervisor (or the system provides a default). Event notification. Users must specify the events that the system should report and the method for these notifications. System logging. The system automatically logs certain events to the system log.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-15 PRINTXCHANGE OVERVIEW
Client interfaces
Three types of client interfaces provide access to PrintXchange functionality: Command line interface (CLI) Graphical user interface (GUI) Inbound gateway clients. As figure 2-8 illustrates, the CLI, inbound gateway, and program application interfaces are based on the POSIX 1387.4 standard, whereby the POSIX API provides a layer between the user interface and the client core software. The GUI has a direct interface to the client core.
Figure 2-8. Client structure
CLI Inbound Gateway Clients GUI
POSIX API
Client Core
A brief description of each of the client interfaces follows.
2-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Command line interface (CLI)
The CLI consists of a set of commands that allow the user to perform the printing system operations. Users run the commands by entering them on the console window. The commands include parameters that identify applicable objects and options. Table 2-2 lists the CLI commands.
Table 2-2. CLI commands
Command Function
pdclean Remove all jobs scheduled on the specified spooler or queue.
pdcreate Create an initial-value-document, initial-value-job, printer, or queue object, and set the object attributes to the values specified in the options, if any.
pddelete Delete the specified job, initial-value-document, initial-value-job, printer, queue, or server object.
pddisable Disable the acceptance of new print jobs by the specified printer, queue, or server.
pdenable Enable the acceptance of new print jobs by the specified printer, queue, or server.
pdls List the names and values of print object attributes.
pdmod Modify or add job and/or document attributes of previously submitted jobs that have not begun printing on the physical printer.
pdpause Pause pending jobs, physical printers, queues, or spoolers
pdpr Submit a print job consisting of one or more documents to a printer supported by the print server.
pdpromote Cause a specified print job to be moved forward to print next on the logical printer to which it was submitted.
pdq Request the status of specified print jobs.
pdresubmit Request that the specified print job that has been accepted by a print server be resubmitted to another specified printer. Command that allows all jobs in a specified queue to be simultaneously resubmitted to a logical printer.
pdresume Resume a paused job, physical printer, queue, or spooler.
pdrm Cancel previously submitted print jobs.
pdset Set the attribute values for supported objects.
pdshutdown Shut down servers gracefully or immediately.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-17 PRINTXCHANGE OVERVIEW
The CLI parses the user’s command line input string and converts it to API calls. The API layer accesses infrastructure facilities, such as the object identifier database (OID) and the attribute set, to determine the validity of the input string. The PrintXchange Command Line Interface Reference Guide describes the CLI, including the command line syntax and each of the command operations and options. For information on Graphical User interfaces on Windows NT and Windows 95, and information on program applications and inbound gateway, refer to the “PrintXchange clients” section in this chapter.
Servers
As described in the section “PrintXchange servers,” the PrintXchange printing system consists of two different types of servers: spoolers and supervisors. These two servers have different primary purposes within the system. While the two types of servers have different primary functions, they also have a substantial amount of common functionality, which include startup, shutdown, and configuration. Startup An administrator may start a server via appropriate selections at Control Panel>Services at a command window: pdsplr for spooler server pdspvr for reference supervisor server pdxspvr for Xerox supervisor server. All servers require a unique name. Administrators may specify an e- mail address where a server can send any errors it encounters during the startup. Shutdown A server shuts down gracefully when an administrator requests a shut down. The server tries to put the object database in a consistent state before exiting. Any other event that causes a server shutdown may cause inconsistencies in the object database. An administrator can create, modify, and display the object database to ensure that certain server attributes exist and are correct in order for the server to start. The utilities that enable this functionality are: pdmoddb for modifying an existing object database pdshowdb for displaying some of the data in an existing object database. Configuration As part of the startup process, a server checks configuration attributes that specify certain aspects of the file system required for successful server operation, such as: Print data (spool), database, log, and accounting directory paths RPC authorization type Administrators may set the values for the configuration attributes.
2-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Spoolers
A spooler is the central element in the PrintXchange printing system; it accepts jobs from multiple clients and submits jobs to multiple supervisors. A spooler provides a common interface through which clients submit and track print jobs, and perform administrative functions. Submit and track print jobs where the spooler: Accepts print requests from multiple clients Schedules print jobs submitted by clients Stores print job data or a reference to it until a job has completed Receives requests for jobs from a supervisor and submits pending print jobs to a supervisor Supports multiple supervisors Provides information to clients for job status reporting and tracking. Perform administrative functions. The spooler accepts object management requests from multiple clients for the following object types: Document Job Initial-value-document Initial-value-job Logical printer Queue Spooler server. The spooler handles recording of job accounting information for later retrieval.
Supervisor
A supervisor provides a common interface between spoolers and output devices, through which the supervisor: Prints and tracks print jobs. The supervisor: Accepts print jobs from a spooler Causes jobs to be printed on an output device (physical printer) or forwards the job to another print system for processing. Performs administrative functions. The supervisor accepts object management requests from the spooler and management clients for the following object types: Physical printer Supervisor server.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-19 PRINTXCHANGE OVERVIEW
Example: request processing
Using a print request as an example, the following paragraphs describe the processing that the CLI client, spooler, and supervisor undergo as they satisfy the request. Overall, the processing steps identify most aspects of PrintXchange functionality that are described in more detail in the remainder of this document. Note: By default, users may only see information about jobs up until the time they are printed. After that, information about completed jobs remains only in the accounting logs. In an environment where the administrator would like users to be able to view jobs in a "completed" state, the server default-job-completion-period should be set to an appropriate time period. You can change the value via the CLI. For example, set default-job-completion-period=4 to ensure that jobs do not disappear immediately upon printing. They will remain for 4 minutes. These steps are generally listed in the order in which they occur. However, some steps actually overlap. Also, these steps only indicate the processing for a simple, correct job. 1. The user submits a request by entering the print request via the CLI or GUI. For example: pdpr -x “sides=2” File1.txt 2. The client processes the request: Parses command. The syntax is validated and attributes are verified. Provides defaults. Attributes such as printer-name- requested, job-name, transfer-method, and job-owner are given values if the user has not specified them. Checks the Name Services to get the binding information for the logical printer. Initiates a print request with an RPC to the spooler. Unless the file-reference transfer method is used, transfers the file to the spooler where it is stored in its spool area. Returns to the user. 3. The spooler validates the job: Using the UID from the RPC to authenticate the users, the spooler ensures that the user is authorized as, at least, an End User for this server. Ensures that the logical printer and its associated queue are enabled. Applies defaults for unspecified attributes from any initial- value-job and initial-value-documents. Verifies that all specified attributes are correct and compares them to the logical printer’s xxx-supported attributes to ensure that the job request can be satisfied. The spooler creates the job and document objects and enters it into the object database. Attributes such as job- identifier, submission-time and current-job-state have values provided. pdl guessing is used if document format is not specified.
2-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Applies any necessary filters to the print data and sends the print data to the output device. 4. The spooler schedules the job for printing: The supervisor for a physical printer associated with the queue, requests a job from spooler. The spooler validates that the physical printer is enabled and not paused. The spooler selects promoted jobs first, and then selects jobs based on job priority. If jobs have the same priority, it selects the oldest pending job in the queue. The spooler compares the printer’s xxx-ready attributes with the job and document attributes. If all of the requested attributes are ready, the spooler gets binding information for the physical printer from the Name Service and delivers the job to the supervisor. If the supervisor and spooler are not on the same host, the print data is transferred to the supervisor’s spool area. The spooler updates job attributes such as current-job-state and printers-assigned to indicate that the job has been delivered to a supervisor. 5. The supervisor processes the job and delivers it to a printer: Creates a “shadow” job and document object. Initiates communications with the physical printer. Updates attributes such as current-job-state and started- printing-time. If requested, creates separator pages in a format appropriate for the output device. Based on attributes such as default-input-tray, the supervisor sends command sequences to the printer to set its defaults. Applies any necessary filters to the print data and sends the print data to the output device. 6. Job processing is completed: When all print data has been sent to the printer, the reference supervisor sets attributes such as current-job- state and job-completion-time. The Xerox supervisor queries the printers for Job Status and when it is completed on the printer, it sets current-job-state and job-completion-time. The reference supervisor informs the spooler that the job is complete, deletes the “shadow” job and document objects and any spooled data. The reference supervisor requests another job from the spooler. The spooler updates the job and document attributes with the information from the supervisor and writes accounting records. Spool data is deleted but job and document objects remain until job completion period has expired.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-21 PRINTXCHANGE OVERVIEW
7. The spooler and supervisor notify users: Throughout the steps listed above, both the spooler and the supervisor identify system events such as object state changes and printer attentions, compare these events against object notification profiles, and send messages to interested end users.
Interoperability
PrintXchange includes NT as a supported server platform in addition to Sun Solaris. PrintXchange also includes clients for UNIX, Windows NT, and Windows 95. This section describes interoperability for PrintXchange components on Windows 95, Windows NT, and Sun Solaris platforms. See figure 2-9 for details. As in the UNIX environment, PrintXchange Windows 95 and NT components have complete and seamless interoperability. However, PrintXchange Windows 95 and NT components do not have complete interoperability with Sun Solaris components. Specifically, PrintXchange Windows 95 and NT clients can be configured to work with a Sun Solaris servers. However, PrintXchange Sun Solaris clients do not work with an NT server. In addition to native clients, PrintXchange offers an lpr gateway on Sun Solaris. The LAN Manager gateway provides interoperability with legacy Windows 3.x, Windows for Workgroup, and OS/2 clients. The Novell QServer gateway provides interoperability with NetWare clients. The lpr gateway for Sun Solaris works only with PrintXchange UNIX servers. The Novell QServer, lpr and LAN Manager gateways for NT can be configured to allow Windows NT network users to submit print jobs to PrintXchange printers controlled by either an NT or UNIX server.
2-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Figure 2-9. Interoperability for PrintXchange components on Windows 95, NT, and Sun Solaris platforms
95/NT
CLI
NT 95/NT Spoole r GUI
OS/2 Trans- 95/NT parent
Client WIN WIN for 3.1 LM GW GW
NW Net- GW Ware
Client LPR GW LPR UNIX
Client
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-23 PRINTXCHANGE OVERVIEW
Multinational considerations
PrintXchange is intended for worldwide distribution and use. It has been designed to be easily converted to use different code sets and to have the user visible text easily translated and incorporated back into the system. All PrintXchange software: Supports single-byte and multi-byte code sets in a code-set independent manner to provide support for ISO 8859-1 in Western Europe and several Asian multi-byte code sets. Uses formatting and collation methods that are locale sensitive. That is, the software allows formats of different types of information (date, time, and numbers) and the sorting order of different language alphabets to be set by locale. Stores locale-dependent information such as help text, error messages, property sheets, buttons, and text on icons in files whose paths depend on the locale. PrintXchange uses the X/OPEN XPG4 defined system calls and message file format. Provides support for East Asia through multi-byte code sets. Note that most of this section describes functionality that is not visible to end users.
General internationalization requirements and restrictions
PrintXchange clients and servers are to be in the same language and territory. For some languages/territories, such as Japan, two or more code sets are in use. Therefore, some code set conversion is dealt with. Conversions are restricted to those that are supported by the local iconv routine. Attribute names, such as plex and values that have OIDs or are enumerated, such as duplex, simplex and tumble are not intended to be localized in PrintXchange. Attribute values that support entry of variable text, such as the value for the job-name attribute, can be input in any supported code set. Note that this includes paths to files.
Internationalization considerations
PrintXchange does not support the wchar version of the POSIX API. The use of character set registries (e.g. IANA or OSF) to character set specification is not supported.
2-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Supported character-sets
PrintXchange supports only character sets that are single byte (8-bit) or multi-byte, null-byte-terminated strings; it does not support unicode. A component may choose to convert a string to Unicode in order to perform some operation but this conversion is local to the component. The defined character sets of PrintXchange are listed in the CLI Reference Guide under the attribute “default-character-set”. However, PrintXchange extensions to the DPA textSyntax and simpleNameSyntax provide a new value entry that enables the specification of a character set using an octet string. The new value entry is other-code-set, and will be the only value that PrintXchange servers will use. Other values are retained for compatibility with the original DPA syntax. The value other-code-set consists of two elements: octet-string and, optionally, code-set with an objectIdentifier data type. For both incoming and outgoing text attribute values, if the operational locale is not specified, then PrintXchange uses the character-set entry of the server’s locale.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-25 PRINTXCHANGE OVERVIEW
Environment variables
The environment variables listed in table 2-3 may affect the operation of the utilities PDDOMAIN, PDPATH and PDPRINTER. The utilities use the current value of environment variables as the default, unless a user specifies a different value via a utility option.
Table 2-3. Windows NT Environment variables
Variable Description
NLSPATH Determines the directory path for CLI message files only if the message files are not stored in the standard directory.
PD_OID_DB_PATH Specifies the path to the directory containing the OID database files only if the OID database is not at the default location.
PDDOMAIN Specifies the domain name used on operations that do not specify the domain-name attribute for cross domain or cross platform requests. For cross platform requests, the domain name should be prefixed with the domain type. The prefixes are: For Windows NT: winnt: or ntsecurity: For UNIX servers: file: or nis: PDPATH Consists of a colon-separated list of directories (path) that are successively tried for the file name specified in the -X attribute_filename option.
The PDPATH environment variable is processed for attribute_filename in the same way that the PATH environment variable is processed for utility names
PDPRINTER The value of this variable is used as the default printer by the print client when the attribute printer-name-requested or the option - p printer_name is unspecified.
The variable is also used to select a server for operations when an explicit server is not selected. (The server that contains this printer is viewed as the default server.)
PX_ROOT Determines the main (root) directory for PrintXchange.
Message catalog files
All error messages and screen text presented to the user are based on Resources DLL. The PrintXchange core software is developed and distributed in the US English locale. In addition, Xerox will perform and make available German, French, and Japanese localizations.
2-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTXCHANGE OVERVIEW
Infrastructure
All object names that are entered into the NameSpace are restricted to localized strings. Text used in values of the access-control-list attribute is also restricted to localized strings. Notification messages and arguments must be localizable.
Log files
All system error log files contain only a single language to simplify support and service. PrintXchange uses generic English in the ASCII code set. System log messages are not localized in PrintXchange.
Servers
Servers-common The server performs any required character set conversions. All strings within a server are in the character set of the server’s host. The spooler and the supervisor are restricted to the same character set. Spooler There are no unique internationalization aspects of the spooler. Reference supervisor All static text displayed on separator pages is read from message & Xerox Supervisor files. The supervisor assumes that all the printers it supports can print the strings in the message files without character set conversion. The PostScript prologue file used for separator sheets should be localized for several languages. The sample prologue files for ISO Latin1 encoding and EUC-JP encoding are developed and distributed within PrintXchange.
Clients
Common client Clients should determine their operational locale. If the operational locale for an operation is not specified, it defaults to the server’s locale. POSIX CLI CLI command names and options flags are not localized. GUI Text entry fields are sized with consideration to languages other than English. Inbound gateway clients There are no unique internationalization considerations for gateways.
Codeset converter DLL interface
On Windows NT, PrintXchange provides an interface to plug in the localized codeset converter routines. The converter routines use the descriptive name of object identifiers to identify the source and destination encoding names.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 2-27 PRINTXCHANGE OVERVIEW
2-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 3. System requirements
A successful installation requires careful planning, so that your end users can enjoy an efficient and productive PrintXchange system. This chapter lists the following system requirements, which you should keep in mind when planning the configuration: Software requirement Network requirement Hardware requirement. As a guideline for planning, you should meet the minimum server and client requirements for the PrintXchange system.
Software requirements
Software requirements for PrintXchange NT server installation include: Windows NT 4.0 operating system with Service Pack 3 Windows Messaging Version 4.0 or 5.0 (required if using e-mail for event notification) Windows NT SNMP service (for Xerox supervisor) Internet Explorer 3.02 or higher (for client help files) Windows NT File System – NTFS (recommended) Primary Domain Controller (recommended for PrintXchange Name Service installation). Software requirements for PrintXchange client installation include: Internet Explorer 3.02 or higher (for help files) Windows95 operating system or Windows NT 4.0 operating system with Service Pack 3
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 3-1 SYSTEM REQUIREMENTS
Network requirements
PrintXchange requires use of the Windows NT built-in TCP/IP protocol.
Gateway components
Gateway components consist of LPR, LAN Manager, and NetWare Queue Server printing software. The requirements for each of these are listed below.
LPR
The LPR printing software requires: TCP/IP protocol Windows Socket Library.
LAN Manager
The LAN Manager printing software requires: Net BEUI protocol or TCP/IP protocol.
NetWare Queue Server
The NetWare Queue Server printing software requires: Windows Socket Library NWLink IPX/SPX Compatible Transport TCP/IP protocol.
Hardware requirements
This section covers hardware requirements for loading the NT server software on an NT Server, the client software on an NT Workstation, the client software on a Windows 95 system, and NT gateway on an NT server.
Hardware full server/client configuration
The following are the hardware requirements for the server configuration: Minimum - Pentium Pro 200 MHz (64 MB RAM) Disk Space - 20 MB (for installation only). Note: You must take into account the number of jobs printed, the job retention period, and the size of the print data to figure out what size hard disk to use in your configuration. Similarly, the memory size and the processor speed depend on the number of concurrent job submissions and the number of printers connected to the server.
3-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT DETERMINING THE SYSTEM REQUIREMENTS
A very rough estimate is that the typical configuration with the minimum hardware requirements can process about 2000 small-size jobs per hour. However, there are many factors that affect performance like the size of the print jobs, the network load, and the speed of your printers.
Hardware Windows NT GUI and CLI configuration
Hardware (PrintXchange Graphical User Interface (GUI)/Command Line Interface (CLI) configuration) requirements are: Minimum - Pentium 133 MHz (32 MB RAM) Disk Space - 9 MB (installation/operation).
Hardware Windows 95 GUI and CLI configuration
Hardware (PrintXchange Graphical User Interface (GUI)/Command Line Interface (CLI) configuration) requirements are: Minimum–90 MHz (16 MB RAM) Disk Space - 9 MB (installation/operation).
Windows NT gateway configuration
The following are the hardware requirements for the Windows NT gateway configuration: Minimum - Pentium 200 MHz (64 MB RAM) Minimum Disk Space - 8 MB.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 3-3 4. Recommended configuration planning
Configuring your PrintXchange system is a four-phase process: 1. Determining your network printing system requirements; 2. Installation process; 3. Creating, configuring, and enabling queues, physical printers, and logical printers; 4. Validating your installation and configuration.
Configuration roadmap
Table 4-1 lists the chapters covering the major steps of the configuration process.
Table 4-1. Configuration roadmap
Process Step Location of Supporting Information
Determining your network printing Chapter 5 Planning a PrintXchange system requirements installation
Determining your Name Service Chapter 8 Managing security needs
Determining your Inbound Chapter 20 Inbound gateways Gateway needs
Determining Event Notification Chapter 9 Setting event notification needs
Installing and setting up server Chapter 6 Installing and setting up hosts PrintXchange on a server machine
Installing and setting up client Chapter 7 Installing and setting up hosts PrintXchange on a client machine
Configuring servers Chapter 10 Configuring, starting and stopping servers.
Creating, configuring, and Chapter 11 Creating and configuring enabling queues queues, physical and logical printers
Chapter 17 Enabling and disabling objects
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 4-1 RECOMMENDED CONFIGURATION PLANNING
Table 4-1. Configuration roadmap (continued)
Process Step Location of Supporting Information
Creating configuring and enabling Chapter 11 Creating and configuring physical printers queues, physical and logical printers
Chapter 15 Setting and modifying object attributes
Chapter 17 Enabling and disabling objects
Creating, configuring and Chapter 11 Creating and configuring enabling logical printers queues, physical and logical printers
Chapter 15 Setting and modifying object attributes
Chapter 17 Enabling and disabling objects
Validating your installation and Chapter 11 Creating and configuring configuration queues, physical and logical printers
4-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 5. Planning a PrintXchange installation
Once you have determined the system you want, you can proceed to plan the installation of PrintXchange on Windows NT.
Determining components, objects, and end user privileges
You must fully understand the components and objects that will constitute your PrintXchange system, as well as the end users who will use the system, before beginning the installation and configuration process. In planning your PrintXchange system, you should determine: 1. The components you need and where to run them. 2. The objects that will populate the server components and the associations of those objects. 3. Your end user privileges. 4. The domain and workgroup hosts where the PrintXchange Name Service will reside. This section provides some guidelines to help you make these decisions.
Determining the components
The first step in planning your PrintXchange system is to decide on the components and where to run them. PrintXchange has three basic components: 1. Clients CLI GUI 2. Servers Spooler Supervisor Inbound gateway Name Service Notification Service 3. Printers The servers are part of the PrintXchange software. Printers are already in your environment.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 5-1 PLANNING A PRINTXCHANGE INSTALLATION
Guidelines for determining components
Here are some guidelines to help you determine which components to install and where to install them: What hosts do I need? You need client hosts and server hosts. The number of hosts depends on the size of your network and the number of end users the network supports. Which clients do I need? The CLI provides the full suite of PrintXchange functionality. You should install the CLI for operators and system administrators to manage the PrintXchange system successfully. Since CLI is a command line interface accessed from the DOS prompt, it is not a recommended interface for typical users. The GUI is integrated into the Windows NT and Windows 95 operating system environments enabling setup of printers from the Microsoft add printers wizard and job submission directly within standard Microsoft applications. This component also includes an administration tool for configuring and managing PrintXchange. Note: If you do not wish to install PrintXchange client software on user’s systems, users may submit jobs using their existing LPR, LAN Manager, and Novell Netware submission software. Refer to the “Which inbound gateway do I need?” section. Which inbound gateway do I need? PrintXchange can print jobs coming from the following sources: Netware clients in a Netware 3.11 or Netware 4.x bindery printing environment. LAN Manager clients using SBM protocol from OS/2 and Windows for Workgroups LPD clients Where should I install the clients? Both the CLI client and the GUI client should be installed on every client and server host used by administrators and operators. The GUI is easier to use but there are a few administrative functions that it cannot perform, such as installation of supervisor and spooler filters. The GUI should be installed on all workstations used by end users. Installing the CLI client is optional. Although the inbound gateways are properly clients, they are better thought of as spooler utilities. It makes the most sense to install inbound gateways on the spooler’s host; this reduces network traffic and file-transfer overhead. Refer to the POSIX API documentation to determine where to install the API.
5-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PLANNING A PRINTXCHANGE INSTALLATION
How many supervisors do I need? The Reference Supervisor can support a maximum of 50 printers. The Xerox Supervisor can support a maximum of 300 printers. Reference supervisor: A PrintXchange spooler can deliver jobs to an unlimited number of supervisors and the supervisors can be arbitrarily distributed. However the following restrictions apply: If the printer is connected directly to a host (i.e., serial or parallel connection), the supervisor must be installed on that host. A supervisor can be driven by only one spooler. The number of printers that a reference supervisor can control is limited. Therefore, it may be necessary to run more than one supervisor. If the spooler and supervisor are on the same host, network file transfer overhead will be reduced, so installing supervisors on the same host as on their spooler is more efficient. Xerox supervisor: The Xerox supervisor supports printers with LPR, SNMP or Xerox DOCUSP and DOCUPRINT interfaces. It does not support serial or parallel connections nor ip socket connections. One spooler can only drive the Xerox supervisor, but a single spooler can drive multiple supervisors (both Reference and Xerox combined). Where should I install the supervisors? A supervisor must be on every host that supports a printer directly connected to its serial or parallel port. A supervisor can control network printers from any host. You can run the supervisor on the same host as the spooler if the host is sufficiently powerful. This allows the servers to share spool space and shared code object libraries. You must install all server components on all server hosts. You do not have to run supervisor and spoolers on the same host, but you must install the software for all of them. You should not install supervisors on client hosts, they needlessly tie up system resources. How many spoolers do I need? Unless a single host cannot handle the print load, it is recommended that one spooler per node be installed within a network environment. The total number of servers in the environment is dependent on many factors including: Number of printers Number of print jobs Number of users Type of applications driving a printer Types of printers Size of the machines Administrator’s span of control
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 5-3 PLANNING A PRINTXCHANGE INSTALLATION
Network topology User location Server location. PrintXchange supports multiple spoolers, and multiple spoolers allow the printing load to be distributed across multiple hosts. However, if spooler host resources are not a concern, it is preferable to have only one spooler in a configuration because such a configuration: Is more efficient overall Generates one accounting file Serves as a single source for listing printers and queues. Where should I install the spooler? The spooler is the central component of a PrintXchange system and configurations should be designed around the spooler. A spooler’s host must have sufficient spooling space for queued jobs, CPU cycles, and physical memory to handle peak printing loads. You must install all server components on all server hosts. You do not have to run both supervisor and spoolers on the same host, but you must install the software for both. Once you have determined which PrintXchange components to install and where to install them, you are ready to decide how to populate your servers and make associations among server objects.
5-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PLANNING A PRINTXCHANGE INSTALLATION
Determining the objects
The second step in planning your PrintXchange system is to decide on the objects that will populate the server components and on the associations among those objects. Some guidelines to help you determine which objects will populate the server components are: How many physical printers do I need? Make a list of the printers in your network. Verify that PrintXchange supports each of these printers by referring to the appendix, “Printer Data Sheets”. If PrintXchange does not support a particular printer, you cannot include that printer in your PrintXchange system. Verify that you have a .paf file for each supported printer. Refer to the appendix, “Printer Data Sheets”, which provides the name of the .paf file for each supported printer. Physical printers represent printers in your environment. You must have at least one physical printer per printer. Remember that one reference supervisor can support up to 50 printers and one Xerox supervisor can support 300 printers. How many logical printers do I need? Determine the xxx-supported and xxx-ready attributes of the printers from the printer data sheets in the appendix, “Printer Data Sheets”. From these attributes, design the capabilities you want to present as logical printers and determine the defaults you want to apply at the logical-printer level (these defaults are the initial-value- document and initial-value-job objects that reside in the logical printer). You need one logical printer for each group of abstracted capabilities. Figure 5-1 illustrates how one logical printer for each capability: duplex, staple and duplexstaple feeds into the 4215 queue and physical printer. Figure 5-1. Multiple capabilities feeding into a logical printer
DUPLEX LP
STAPLE LP 4215 Q 4215 PP
DUPLEXSTAPLE LP
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 5-5 PLANNING A PRINTXCHANGE INSTALLATION
Which defaults do I need? Initial-value-document objects determine document defaults at the logical-printer level (as opposed to the print-request level). Determine which document defaults you want to apply to your logical printers according to the capabilities your printers support. Initial-value-job objects determine job defaults at the logical- printer level (as opposed to the print-request level). Determine which job defaults you want to apply to your logical printers according to the capabilities your printers support End users can override logical-printer-level defaults by specifying attributes with print requests. How many queues do I need? Queues map logical printers to physical printers. Verify the physical and logical printers you have decided on. Multiple logical printers can feed a queue and multiple physical printers can feed from a queue. Logical printers cannot feed more than one queue. Physical printers cannot feed from more than one queue. Determine and verify the queues that you need to connect your logical and physical printers. Be sure you maintain synchronization between your logical printers’ capabilities (xxx- supported attributes) and your physical printers’ capabilities (xxx-supported and xxx-ready attributes). If you made these determinations about PrintXchange objects, you are ready to decide on your end users and their privilege levels.
Determining end user privileges
The third and final step of planning your PrintXchange system is to define your end users and their privilege levels. PrintXchange supports three privilege levels: 1. System administrator 2. Operator 3. End user. PrintXchange can restrict operations to users that have authorization to perform them. The server, printer, queues, i-v-jobs and i-v docs attribute access-control-list (ACL) associates a user with one of these privilege levels. You can identify end users either as individuals or as groups. Moreover, you can disable authorization for any user type, allowing them to perform certain types of operations. Some guidelines to help you determine your end users and their privilege levels are: Can I restrict access to particular printers? You can restrict access to PrintXchange printers to a list of end users or allow everyone using a PrintXchange client to print to PrintXchange printers. If you do not want to restrict access to particular printers, you should disable authentication for end users. How should I define end users?
5-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PLANNING A PRINTXCHANGE INSTALLATION
Does your environment already define groups of end users? If so, you can carry these groups over to your PrintXchange system. You can associate multiple groups of end users with an end user call, so you do not have to create a new class just for PrintXchange. Who should be the host for the PrintXchange Name Service? If you want to allow customers access to the Primary Domain Controller, then it is recommended that the PrintXchange Name Service be installed on the PDC NT Server. If you do not want to allow customer access to the Primary Domain Controller, then do not install PrintXchange Name Service on the PDC NT Server. Do I need operators? Some environments do not distinguish between daily operational tasks and administrative tasks. If your environment makes no distinction along these lines, you do not need the operator privilege level. Should security be different on different servers? When created, the server default access provides end user privileges to all users on the domain/workgroup. When create, the server default access provides administrator privileges to all users in the administrators group. For further details on security, refer to the “Managing security” chapter.
Determining the Name Service location
Who should be the host for the PrintXchange Name Service? If all users are on a single workgroup, the Name Service may reside on any host in the workgroup If all users are on the same subnet but different domains and workgroups, the Name Service may reside on any host in the subnet but a separate installation of the Name Service must exist for each domain and workgroup. If users are spread across multiple subnets on a domain, it is recommended to install the PrintXchange Name Service on the Primary Domain Controller If cross-domain printing is required, it is recommended to install the PrintXchange Name Service on the Primary Domain Controller. For further details on Name Service location, refer to the “Managing security” chapter.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 5-7 PLANNING A PRINTXCHANGE INSTALLATION
5-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6. Installing and setting up PrintXchange on a server machine
This chapter describes the CD content and explains how to install and set up the PrintXchange software on server machines, using the following packages: Windows NT Server Solaris Server. The Windows NT Server package allows you to install and set up your name service, server software, gateways, administration tool, and printing tools. Refer to the overview chapter for a description of each. The Solaris Server package allows you to install and set up your NT gateways that provide printing capability for your Windows NT and Windows 95 users in their native NetWare or LAN Manager environment. This chapter also covers the steps to uninstall PrintXchange from a server machine.
Overview of the CD contents
The Welcome option on the splash screen displays the NT software readme file. The EXPLORE CD option on the splash screen enables browsing of the CD file structure. Both CDs contain a documentation folder that contains the PDF format of the customer documentation. These files can be copied to your local hard drive.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-1 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Overview of the installation and set-up process for Windows NT Server
Installation offers you a method to conveniently install and set up the PrintXchange software on your PC running Windows NT 4.0. The installation process uses the industry standard InstallShield. Basically, the PrintXchange installation and set-up process consists of: Determining the user account where PrintXchange should be installed Setting up e-mail notification Determining the host location for PrintXchange Name Service Determining additional components: Gateways Spoolers Supervisors Administration and printing tools Setting up PrintXchange Name Service Setting up Spoolers and Supervisors Setting up NetWare gateway Setting up cross-platform print submission and management. Note: This chapter assumes an initial installation of PrintXchange. If you upgrade the software or install multiple PrintXchange servers, be aware that only one PrintXchange Name Service may be installed in the domain or workgroup. To perform an update of the PrintXchange Name Service software, the update must occur from an account on the local host where the Name Service resides. The PrintXchange installation CD must be locally or remotely attached to the local host. Note: If you are installing the Name Service, a Spooler server or Supervisor server, the installation host must have a fixed IP address. In a Dynamic Host Configuration Protocol (DHCP) environment, ensure that the installation host is always assigned the same IP address or DHCP is disabled on the host installation. To determine if the host receives its IP address from a DHCP server, check this option within the TCP/IP protocol, IP address tab in the Network properties. Within the Services menu, check whether DHCP is running. CAUTION: When installing multiple PrintXchange servers in the same domain or workgroup, you must know the name of the host running the PrintXchange Name Service before performing the second and subsequent server installations. If the PrintXchange Name Service host is up and located in the same network segment as the Primary Domain Controller (PDC) or the Name Service resides on the PDC host, the installation software will detect its presence on the network. If the Name Service host is not detected, failure to enter a host name will cause the installation process to load the Name Service on the local host. Having the Name Service on multiple hosts in the domain or workgroup will cause server naming conflicts that prohibit valid operation of the printing subsystem.
6-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Installing PrintXchange (Windows NT Server)
Follow these steps to install PrintXchange on a Windows NT server machine: 1. To install PrintXchange, insert the CD titled PrintXchange Windows NT Server into your CD drive. To install PrintXchange from the CD, click Install/Upgrade. Skip to step 3. 2. To setup PrintXchange for installation from a medium other than the CD, such as from a network server or from your hard drive: a. Click EXPLORE CD. b. Copy the contents of the CD to the appropriate medium. Note: All contents other than the Documentation and Support folders are necessary for installation. c. Double-click the SETUP.EXE file to begin the installation process. 3. At the Welcome screen, click Next. 4. At the Software License screen, click Yes.
Determining the user account
The following question will display:
Note: To install PrintXchange software, you must be logged onto an account that has Administrator Group access and various user rights. You can install the software on any existing accounts, or create the PXCAdmin account, as prompted by the system. Using the PXCAdmin account is recommended since the Windows Messaging setup of the PrintXchange e-mail notification cannot have the inbox located on a remote mail server. The inbox of the installation account must reside locally on the drive where PrintXchange is being installed. Also, the spooler, supervisor, and notification server are password protected. The password must match the password of the installation account. Anytime the account password changes, you must enter the Setup tool to synchronize the server passwords. 5. Click Yes if you want to install PrintXchange on your current account, or No if you want to create the PXCAdmin account. No is the recommended option. 6. If selected No, the system will ask if it is okay to create the PXCAdmin user account. To create the account, click OK, then log off and log back on to restart PrintXchange installation.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-3 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
7. If selected Yes, an information screen will display:
To add these access rights, click OK, then log off and log back on to restart PrintXchange installation. 8. Upon restarting the PrintXchange installation logged on as the PXCAdmin account or as a user account with the required user rights, the User Information screen will display. Type your name and your company’s name, then click Next. Next, type your Password, then click Next.
Setting up e-mail notification
If Windows Messaging is not installed and you wish to use PrintXchange e-mail notification, you may install it from your Windows NT operating system CD during the PrintXchange installation process. You may also install and configure Windows Messaging later, then run the Setup PrintXchange tool to enable for PrintXchange e-mail notification.
9. To create a Windows Messaging mail profile now, click Yes. If the Windows Messaging software is not installed, insert the Windows NT operating system CD into your CD drive.
6-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
To configure a MAPI profile, the Windows Messaging Setup Wizard will display. To configure a MAPI profile later, click No then skip to the next subsection. If you are performing an install of the Name Service or the Name Service on your domain or workgroup could not be located, the installation continues with the subsection “Determining the host location for PrintXchange Name Service.” Otherwise, installation continues with the subsection “Choosing the destination location”.
10. Select the information service(s) you want to use for PrintXchange email notification, then click Next. Microsoft Mail If selected Microsoft Mail, the following screen will display:
11. Type the path to the appropriate Microsoft Mail post office for your environment, or use the Browse function, then click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-5 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
12. Select the installation account user name, then click Next.
13. Enter your Microsoft Mail password, then click Next.
6-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Internet Mail If selected Internet Mail, the following screen will display: 14. Select the appropriate method (Modem or Network) for connecting to your Internet Mail Server, then click Next.
15. Enter a name or an IP address for the Internet Mail server, then click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-7 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
16. Select the mode for transferring messages (Off-line or Automatic), then click Next.
17. Type in the e-mail address for your mail account, then click Next.
6-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
18. Type in your mailbox account name and password for the Internet Mail Server, then click Next.
19. Enter the path for your Personal Address Book and Personal Folder to complete setup of Microsoft Mail.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-9 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Determining the host location for PrintXchange Name Service
Note: To determine the best location for your PrintXchange Name Service, refer to the “PrintXchange Name Service” section in the “Managing security” chapter. For domains If you are installing PrintXchange on a workgroup, skip to the “For workgroups” subsection. If the PrintXchange Name Service is detected on your domain, installation skips to the “Choosing the destination location” subsection. The PrintXchange Name Service Setup screen will appear if the PrintXchange Name Service is: Not installed anywhere in the entire domain; or Installed but not in the same network segment as the PDC, or installed but not on the PDC.
20. If you are certain that PrintXchange Name Service is not installed anywhere in the entire domain, click Next without entering the Host Name and skip the next step.
6-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
21. If the PrintXchange Name Service is installed on the domain but not on the PDC, or is installed on a network segment different from the PDC, then click Next. PrintXchange installation will attempt to validate that the Name Service is running on the host you specified. If the Name Service host you specified is running on a different domain or workgroup, you will be prompted again to enter the correct Name Service host name for your domain. If the installation process cannot access the host you specified, the following screen will display:
Click Yes to have the installation process record the specified host as the Name Service host location then skip to the “Choosing the destination location” subsection. Click No to return to the PrintXchange Name Service Setup screen. Note: To start any of the PrintXchange servers after installation, the Name Service host must be operating and accessible. 22. The following screen will display. If you wish to install PrintXchange on the local host rather than on the PDC, click Yes to remotely install PrintXchange Name Service on the PDC host. Click No and skip to the “Choosing the destination location” subsection.
If you are not installing the PrintXchange Name Service on the PDC host, the following screen will display:
Note: Following the warning above, PrintXchange Name Service will be installed on the local non-PDC host system. Skip to the “Choosing the destination location” subsection.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-11 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
23. If you clicked Yes, your domain and PDC names are displayed to confirm the location of the Primary Domain Controller. Click Next to remotely install PrintXchange Name Service on the PDC host.
6-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
24. Specify the destination location for PrintXchange Name Service, or accept the default destination directory, then click Next. After the remote installation of the Name Service completes, installation skips to the “Choosing the destination location” subsection. Caution: For remote installation of the PrintXchange Name Service, do not change the drive destination.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-13 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
For workgroups If the PrintXchange Name Service is detected on your workgroup, installation skips to the “Choosing the destination location” subsection. The PrintXchange Name Service Setup screen will appear if the PrintXchange Name Service is: Not installed anywhere in the entire workgroup; or Is installed on a host in the workgroup, but either the host cannot be accessed or the PrintXchange Name Service is not running.
25. If you are certain that PrintXchange Name Service is not installed anywhere in the entire workgroup, click Next without entering the Host Name to have the Name Service loaded on the local host. Skip to the “Choosing the destination location” subsection. 26. If the PrintXchange Name Service is installed on the workgroup, enter the hostname that the Name Service is running on, then click Next. PrintXchange installation will attempt to validate that the Name Service is running on the host you specified. If the Name Service host you specified is running on a different domain or workgroup, you will be prompted again to enter the correct Name Service host name for your workgroup.
6-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
If the installation process cannot access the host you specified, the following screen will display:
Click Yes to have the installation process record the specified host as the Name Service host location then skip to the “Choosing the destination location” subsection. Click No to return to the PrintXchange Name Service Setup screen. Note: To start any of the PrintXchange servers after installation, the Name Service host must be operating and accessible.
Choosing the destination location
27. Specify the destination location for installation of the PrintXchange software, then click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-15 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Determining components to install
You can select which components to install.
Typical installation Select Typical to install the most common components, including: Client (CLI, GUI) Gateway Service (LPR Print) Name Service (only when this is the only host in the domain or workgroup that will be running the Name Service) Spooler Service Supervisor Service (Reference Supervisor, Xerox Supervisor) Custom installation Select Custom to install selected sub-components within certain components. In general, the Custom selection is used in the following situations: To re-install the PrintXchange Name Service. In this case, select only the Name Service and components that were installed on the Name Service host. To load the LAN Manager Print and/or the NetWare Qserver Print gateway(s). To create a custom installation of specific components. Note: It is not recommended to use this CD to install only the Client component. Rather, use the Admin or the User package to install Client software. 28. Select the components that you wish to install.
6-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
29. To select specific sub-components within a component, click the appropriate component, then click Change…, then select the sub-component(s) of your choice.
For the Supervisor Service, Gateway service, and Client components, you can select specific sub-components, as follows: Supervisor service: Reference Supervisor Xerox Supervisor
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-17 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Gateway service: LPR Print LAN Manager Print NetWare Qserver Print
Client: Graphical User Interface and Help Command Line Interface and Help
6-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
30. Once you have selected Typical installation, or selected Custom and specified all components you wish to install, the following screen will display:
Click Next to accept the Xerox PrintXchange 1.2 folder. Otherwise, type a new folder name or select another folder from the list, then click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-19 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
31. The system will summarize all the information you specified. Click Back to change any of the information, or click Next to accept the current settings.
The system will copy files according to your selections.
6-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up PrintXchange Name Service
To enable job submission to PrintXchange printers in other domains, the PrintXchange Name Service servers on the other domains need to be registered on this Name Service.
If using PrintXchange in a Windows NT multi-domain environment and the PrintXchange name service is installed on the Primary Domain Controller host in each domain, all names are registered automatically. If you are in a Workgroup environment, mixed workgroup/domain environment, or a domain environment where the PrintXchange name servers are not installed on the PDC, refer to the “Name Service” chapter for an understanding of which PrintXchange name servers you will need to add to the registered name service list. 32. Once you have added all required names, click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-21 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up Spoolers and Supervisors
You are now ready to set up Spoolers, Reference Supervisors, and Xerox supervisors.
Setting up Spoolers
You can set up multiple Spooler servers through the following screen:
33. If you wish to set up your Spooler later, click Skip and continue to the “Setting up Reference Supervisors” section. If you saved Spooler database files from a previous install, set the base properties to the values of the existing database, then click Create to re-register the existing Spooler.
6-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
If you want to change any of the Base Properties for creating a new Spooler, change the following default(s): Spooler Name This is the Spooler Server name. Database Path This is the database directory name where the object database will be created. OID Path This is the database directory name where the OID database will be created. System Log Host Name This is the host where Spooler Application events will be delivered. You can view the events through the Windows NT Event Viewer. Note: The location of the accounting logs, the Spooler server executable file, and the spool area cannot be changed through the installation process. The value of the PX_ROOT environment variable determines the high-level directory location for each. The PX_ROOT location is the Destination Location selected for the PrintXchange installation. The accounting logs are stored in the \var\acct subdirectory. The Spooler server executable resides in the \bin subdirectory. The spool area is created in the \var\spool\
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-23 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
36. To modify properties of an existing Spooler, click any of the existing Spoolers in the list. To add Spoolers, enter the name of the new Spooler, then click Add. The following screen displays:
37. Modify properties as appropriate, then click Next to return to the Adding new Spooler server screen. 38. Click Next to set up the next PrintXchange component.
6-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up Reference Supervisors
You can set up Reference Supervisors through the following screen:
39. If you wish to set up your Reference Supervisor later, click Skip and continue to the “Setting up Xerox Supervisors” section. If you want to change any of the Base Properties for creating a new Reference Supervisor, change the displayed default(s). For a description of each property, refer to the “Setting up Spoolers” section. 40. If you want to receive e-mail notification for Reference Supervisor start up errors, complete the Mail Properties section. 41. Click Create.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-25 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
The screen will display all PrintXchange Reference Supervisor names that are already installed on your host.
42. To add additional Reference Supervisors, enter the name of the new supervisor server, then click Add. 43. Modify properties as appropriate, then click Next to return to the Adding new Reference Supervisor server screen. 44. Click Next to set up the next PrintXchange component.
6-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up Xerox Supervisors
Note: If SNMP Service is not installed on the host, you will need to install it after completing the PrintXchange installation in order to use the Xerox Supervisor.
You can set up Xerox Supervisors through the following screen:
45. If you wish to set up your Xerox Supervisor later, click Skip and continue to the “Setting up NetWare Gateway” section. If you want to change any of the Base Properties for creating a new Xerox Supervisor, change the displayed default(s). For a description of each property, refer to the “Setting up Spoolers” section. 46. If you want to receive e-mail notification for Xerox Supervisor start up errors, complete the Mail Properties section. 47. Click Create.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-27 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
The screen will display all PrintXchange Xerox Supervisor names that are already installed on your host.
48. To add additional Xerox Supervisors, enter the name of the new supervisor server, then click Add. 49. Modify properties as appropriate, then click Next to return to the Adding new Xerox Supervisor server screen. 50. Click Next to set up the next PrintXchange component.
6-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up NetWare gateway
The following is the recommended procedure for configuring the NetWare gateway: a. Install PrintXchange NetWare gateway service without setting it up. Note: Since the field entries are left blank, the component will fail to start when you restart your system. Ignore any failure messages for this component. b. On the NetWare File Server, determine the existing Print Queue(s) to be serviced by PrintXchange. If the file server is running NetWare 3.1x, follow the steps in the “Configuring NetWare 3.1x” section in the “Inbound gateways” chapter. If the file server is running NetWare 4.x with Bindery emulation Print Queue(s) to be serviced by PrintXchange, follow the steps in the “Configuring NetWare 4.x” section in the “Inbound gateways” chapter. c. Perform NetWare configuration using PCONSOLE. d. On the appropriate PrintXchange Spooler(s), define the PrintXchange logical printers you wish to connect to any NetWare queues. e. Enter the Setup PrintXchange tool to configure the NetWare gateway (refer to the “Using the Setup PrintXchange tool” section in this chapter). You can configure NetWare gateway through the following screen:
51. Click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-29 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
52. Click Next. If you do not specify a NetWare print connection, you will be asked:
53. Click Yes to set up the next PrintXchange component. Note: Once completed the software installation, access the Setup PrintXchange tool to configure the NetWare gateway (refer to the “Setting PrintXchange from a server machine” section).
6-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up cross-platform printing
You need to complete the following screen if: You installed either the PrintXchange client or gateway component(s). You want to manage Solaris PrintXchange servers through the PrintXchange Administration Tool; or You want to allow your Windows NT PrintXchange and Gateway clients to submit jobs to PrintXchange printers in the Solaris domain. Note: You may leave this screen blank now, and complete this information later, from the Setup PrintXchange tool.
54. Click Next to complete your PrintXchange installation.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-31 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
The Restart Windows may display. If installing from a local CD drive, remove the PrintXchange CD from the CD drive.
55. If SNMP is already installed on this system or you are not using a Xerox Supervisor server for this installation, select Yes, to restart your computer now. If, however, you need to install SNMP Service, select No, to perform the SNMP installation.
Installing SNMP
56. Right click the Network Neighborhood icon and select the Properties option. 57. Click the Service tab. 58. Click Add. 59. On the Select Network Service screen, highlight the SNMP service, then click OK. 60. When prompted, insert the Windows NT operating system CD into your CD drive, then click Continue. 61. When asked to restart the system, click No and apply the Windows NT Service Pack 3 prior to restarting your computer, since SNMP has dependencies on this pack. Your PrintXchange installation on your Server machine is complete. Upon restarting your computer, you should notice the following: A PrintXchange submenu extending from the Start Menu A PrintXchange directory containing the software in the noted installation directory A PrintXchange Event Monitor applet in the Control Panel User names in the User Manager for the installed Gateway Services as follows: PXLMIBG hostname (LAN Manager Gateway Service) PXLPRIBG hostname (LPR Gateway Service) PXQSIBG hostname (NetWare Gateway Service).
6-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Installing Windows NT gateways from the Solaris Server package
This CD is intended for use in environments where PrintXchange server software resides only on Solaris systems and clients in the Windows NT domain require ability to use PrintXchange controlled printers. Note: If you later expand your printing environment to include PrintXchange servers installed in the NT domain, use the Windows NT CD to upgrade existing gateways and install PrintXchange NT servers to allow existing clients to use printers controlled by the NT domain PrintXchange servers. Follow these steps to install PrintXchange gateways on a Windows NT server machine: 1. Insert the CD titled PrintXchange Solaris Server into your CD drive. To install PrintXchange from the CD, click Install/Upgrade, then skip the next step. 2. To setup PrintXchange for installation from a medium other than the CD, such as from a network server or from your hard drive: a. Click EXPLORE CD. b. Copy the i386 folder from the CD to the appropriate medium. c. Open the i386 folder on your medium. d. Double-click the SETUP.EXE file to begin the installation process. 3. At the Welcome screen, click Next. 4. At the Software License screen, click Yes. Note: To install PrintXchange NT Gateway software, you must be logged on to an account that has Administrator Group access. 5. Specify the destination location for PrintXchange, or accept the default destination directory, then click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-33 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Determining components to install
You can select which components to install.
Typical installation Select Typical to install both sub-components of the Gateway Service. Custom installation Select Custom to install only one Gateway Service.
6. Click Change…, then select the sub-component of your choice.
6-34 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
For the Gateway service, you can select specific sub-components, as follows: LAN Manager Print NetWare QServer Print
7. Once you have selected Typical installation, or selected Custom and specified all components you wish to install, the following screen will display:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-35 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Click Next to accept the Xerox PrintXchange 1.2 folder. Otherwise, type a new folder name or select another folder from the list, then click Next. 8. The system will summarize all the information you specified. Click Back to change any of the information, or click Next to accept the current settings.
The system will copy files according to your selections.
6-36 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up NetWare gateway
The following is the recommended procedure for configuring the NetWare gateway: a. Install PrintXchange NetWare gateway service without setting it up. Note: Since the field entries are left blank, the component will fail to start when you restart your system. Ignore any failure messages for this component. b. On the NetWare File Server, determine the existing Print Queue(s) to be serviced by PrintXchange. If the file server is running NetWare 3.1x, follow the steps in the “Configuring NetWare 3.1x” section in the “Inbound gateways” chapter. If the file server is running NetWare 4.x with Bindery emulation Print Queue(s) to be serviced by PrintXchange, follow the steps in the “Configuring NetWare 4.x” section in the “Inbound gateways” chapter. c. Perform NetWare configuration using PCONSOLE. d. On the appropriate PrintXchange Spooler(s), define the PrintXchange logical printers you wish to connect to any NetWare queues. e. Enter the Setup PrintXchange tool to configure the NetWare gateway (refer to the “Using the Setup PrintXchange tool” section in this chapter). You can configure the NetWare gateway through the following screen:
9. Click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-37 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
10. Click Next. If you do not specify a NetWare print connection, you will be asked:
11. Click Yes to set up the next PrintXchange component. Note: Once the software installation is complete, access the Setup PrintXchange tool to configure the NetWare gateway (refer to the “Using the Setup PrintXchange tool” section).
6-38 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Setting up cross-platform printing
You need to complete the following screen to allow your Windows NT Gateway clients to submit jobs to PrintXchange printers in the Solaris domain. Note: You may leave this screen blank now, and complete this information later, from the Setup PrintXchange tool (refer to the “Using the Setup PrintXchange tool” section).
The Restart Windows may display.
12. Click Yes to restart your computer now.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-39 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Your PrintXchange installation on your Server machine is complete. Upon restarting your computer, you should notice the following: A PrintXchange submenu extending from the Start Menu A PrintXchange directory containing the software in the noted installation directory. User names in the User Manager for the installed Gateway Services as follows: PXLMIBGhostname (LAN Manager Gateway Service) PXQSIBG hostname (NetWare Gateway Service).
6-40 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Validating your PrintXchange installation
Once you have completed installing PrintXchange, you will either be asked to restart your system, or will be notified that the software is ready to use. To validate your PrintXchange installation: 1. Check that all installed PrintXchange services are running. 2. Check the System Event Viewer for PrintXchange error messages.
Checking PrintXchange services
The Services screen lists all PrintXchange services that you have installed, and will specify these services’ status. 1. Access the Services screen through Start Settings Control Panel. 2. Locate the services with names prefixed by “PrintXchange.” If the installation requested a restart, the status of all PrintXchange processes should be “Started” upon restarting the system. If the installation indicated that the software is ready to use, you must manually start each service. Note: For Windows NT Server installation: If the PrintXchange Name Service is located on this host, start it before attempting to start any other PrintXchange services. If the PrintXchange Name Service is located on a different host, it must be running to successfully start the other PrintXchange services.
Note: The set of PrintXchange Services displayed depends on the components you selected during installation. The following are the Gateway Services: PrintXchange LAN Manager Print PrintXchange LPR Print PrintXchange NetWare QServer Print.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-41 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
For Solaris Server installation, only the following services may be displayed: PrintXchange LAN Manager Print PrintXchange NetWare QServer Print.
Notes for Windows NT Server installation: PrintXchange Name Service is only displayed if this is the sole host in your domain or workgroup where the PrintXchange Name Service is installed. PrintXchange Notification Service is loaded as part of the Spooler and supervisor components. A PrintXchange Spooler service is displayed for each Spooler created on this host. A PrintXchange Supervisor service is displayed for each Reference Supervisor created on this host. A PrintXchange Xerox Supervisor service is displayed for each Xerox Supervisor created on this host. If some protocol is set to disabled in ControlPanel>Network>Protocol, PrintXchange servers may fail to start. In this case, remove all disabled protocols from NT.
6-42 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Checking the system Event Viewer
Event Viewer is a tool you can use to monitor events in your system. This tool provides details about events that take place on your system, including events for PrintXchange services running on your system. 1. Access the system Event Viewer through Start Programs Administrative Tools. 2. On the Log menu, click Application. A list of event logs will display on the screen. 3. Ensure for the PrintXchange Source that there are no STOP logs (indicated by a red stop sign icon) or WARNING logs (indicated by a yellow circle icon with an exclamation mark). 4. For more information on a selected event, double click the event. PrintXchange information logs (indicated by a blue circle icon with an i) similar to the following are created for successful startup of each service.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-43 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Errors and warnings are logged in the following format: Each prefix corresponds to a component of the PrintXchange system. In the example below, the error message is 49-307. The prefix 49 corresponds to the LPR Inbound Gateway for Windows NT.
For more information on each error message, refer to the “Troubleshooting” chapter.
6-44 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Using the Setup PrintXchange tool
The Setup PrintXchange tool allows you to change parameters that you set during the installation procedure, and to fine-tune your PrintXchange setup. Note: Some screens may not appear on your system, depending on the set of components you installed. In order to change information on only selected screens, it is not necessary to click Next through the entire series of screens. After clicking Next on the last screen you wish to modify, you may then exit the tool by clicking Cancel on the screen that follows.
To set up PrintXchange using the Setup PrintXchange tool: 1. Log on to the account where you installed PrintXchange. 2. Access the PrintXchange Setup tool through Start Programs Xerox PrintXchange 1.2 Setup PrintXchange. The PrintXchange Administrator Account screen will display. 3. Enter your Password, then click Next. 4. If the installation account password has changed since the installation occurred or since the last time you entered the Setup PrintXchange tool, the following message will appear:
Clicking No will exit the Setup PrintXchange tool.
5. If the Windows Messaging Profile has changed since the PrintXchange Notification server installation occurred, the above message appears. To update the PrintXchange Notification server to use the most recent profile, click Yes.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-45 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
The current PrintXchange Name Service properties will display. . Refer to the “PrintXchange Name Service setup” section in the “Managing security” chapter for a description of each property.
6. Change values as appropriate then click Next.
7. A list of registered PrintXchange Name Service servers will display. To register additional domain/server names, click Add.
6-46 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
8. Once you have added all required names, click Next. If you are in a Workgroup environment, mixed workgroup/domain environment, or a domain environment where the PrintXchange name servers are not installed on the PDC, refer to the “PrintXchange Name Service” section in the “Managing security” chapter for an understanding of which PrintXchange name servers you will need to add to the registered name service list. 9. A list of current Spooler Servers on the host will display. To modify properties of existing servers, click the server’s name in the server list. Refer to the “Setting up Spoolers” section for a description of each property. To create additional Spooler servers, enter the Spooler server name, then click Add. 10. Once you have added all required names, click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-47 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
11. A list of .paf files for supported printers will display. To add support for new printers, click Add. Once you have completed adding paf files, click Next.
12. The following screen will display:
Specify the location of the .paf file(s) for the new printer(s), then click OK to install all files into the \share\cap PrintXchange software subdirectory. 13. Once you have added all required supported printers, click Next.
6-48 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
14. A list of current Reference Supervisors on the host will display. To modify properties of existing servers, click the server’s name in the server list. Refer to the “Setting up Spoolers” section for a description of each property. To create additional Reference Supervisors, enter the reference supervisor name, then click Add. 15. Once you have added all required names, click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-49 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
16. A list of current Xerox Supervisors on the host will display. To modify properties of existing servers, click the server’s name in the server list. Refer to the “Setting up Spoolers” section for a description of each property. To create additional Xerox Supervisors, enter the reference supervisor name, then click Add. 17. Once you have added all required names, click Next.
18. Modify the current LPR Print Service Properties as needed, then click Next. Refer to the “LPR inbound gateway” section of the “Inbound gateways” chapter for a description of each property.
6-50 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
19. Modify the current LAN Manager Print Service Properties as needed, then click Next. Refer to the “LAN Manager inbound gateway” section of the “Inbound gateways” chapter for a description of each property.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-51 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
20. Modify the current NetWare Print Service Properties as needed, then click Next. Refer to the “NetWare Qserver inbound gateway” section of the “Inbound gateways” chapter for a description of each property.
6-52 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
21. A list of the currently connected NetWare queue/PrintXchange logical printers will display. To create additional connections, click Add. The PrintXchange NetWare print connection screen is displayed. To delete existing connections, highlight the Queue/Printer Name in the list then click Delete. Once you have completed adding/deleting NetWare print connections, click Next.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-53 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
22. If clicked Add, the PrintXchange NetWare print connection screen will display. In the NetWare File Server Name field, enter the name of the NetWare File Server where the NetWare queue exists. 23. In the NetWare Queue Name field, enter the name of the NetWare Print Queue. 24. From the Logical printer name to be connected to the queue drop-down list, select a PrintXchange logical printer Note: When “[Local Domain]” is selected in the Logical Printer Domain Name list, logical printers which reside on the same domain as this local host will be listed in the logical printer list. To use a logical printer on a different domain, select the appropriate domain name from the Logical Printer Domain Name drop-down list then select a PrintXchange logical printer from the Logical printer name to be connected to the queue drop-down list.
25. Once you have entered all information, click Create. 26. The system will return to the “Adding new NetWare print connection” screen. Once you have completed adding/deleting NetWare print connections, click Next.
6-54 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
27. Modify the current cross-platform properties as needed, then click Next.
Your set up is complete.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 6-55 INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE
Uninstalling PrintXchange from a server machine
As part of the process to uninstall PrintXchange, you need to: Delete any PrintXchange logical printers defined on the desktop Uninstall PrintXchange software Optionally delete PrintXchange data files
Deleting PrintXchange logical printers
To delete PrintXchange logical printers: 1. Access the Printers through Start Settings Printers. 2. Delete all PrintXchange printers.
Uninstalling PrintXchange software
To uninstall PrintXchange software: 1. Access the Uninstall program through one of the following: Start Programs Xerox PrintXchange 1.2 Uninstall PrintXchange Start Settings Control Panel Add/Remove Programs Click the PrintXchange program, then click Add/Remove. 2. On the confirmation window, click Yes. 3. Once the uninstallation is complete, click OK.
Deleting PrintXchange data files
The Spooler and Supervisor databases will remain on your system until you delete the PrintXchange folder. Note: Data files do not exist if an NT Gateway installation was performed.
6-56 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7. Installing and setting up PrintXchange on a client machine
This chapter explains how to install and set up the PrintXchange software on client machines, using the following packages: Administrator User. The Administrator package allows you to install and set up the following components: Command Line Interface Print Provider / Shell Extensions Graphical Applications – Information Tool Graphical Applications – Administration Tool Help Files. The User package allows you to install the same components as the Administration package, with the exception of the Graphical Applications – Administration Tool. Refer to the overview chapter for a description of each. This chapter also covers the steps to uninstall PrintXchange from a client machine.
Overview of the CD contents
The Welcome option on the splash screen displays the NT software readme file. The EXPLORE CD option on the splash screen enables browsing of the CD file structure. Both CDs contain a documentation folder that contains the .PDF format of the customer documentation. These files can be copied to your local hard drive.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-1 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Overview of the installation and set-up process
Installation offers you a method to conveniently install and set up the PrintXchange client software on your PC running Windows NT 4.0 or Windows 95. The installation process uses the industry standard InstallShield. Basically, the PrintXchange installation and set-up process consists of: Determining the components to install Setting up PrintXchange Name Service Setting up cross-platform print.
Installing PrintXchange Client
Follow these steps to install PrintXchange on a client machine: 1. Insert the CD titled PrintXchange User or PrintXchange Administrator into your CD drive. To install PrintXchange from the CD, click Install/Upgrade. Skip to step 3. 2. To setup PrintXchange for installation from a medium other than the CD, such as from a network server or from your hard drive: a. Click EXPLORE CD. b. Copy the i386 folder from the CD to the appropriate medium. c. Open the i386 folder on your medium. d. Double-click the SETUP.EXE file to begin the installation process. 3. At the Welcome screen, click Next. 4. At the Software License screen, click Yes. 5. At the User Information screen, enter your name and your company’s name, then click Next.
7-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Determining components to install
You can select which components to install.
Typical installation Select Typical to install all the components: Command Line Interface Print Submission Graphical Applications – Information Tool Graphical Applications – Administration Tool (for the Administration package only) Help Files.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-3 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Custom installation Select Custom to install selected components. 6. If performing a re-install, skip to step 8. Select the components that you wish to install. Click the Browse… to change the default installation directory. Click Disk Space… to check for available disk space on alternate drives. Click Next to continue to step 10.
Note: The Graphical Applications – Administration Tool is not available through the User package.
7-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
7. If performing a re-install, the following screen will display. Click OK.
8. Select the components that you wish to install.
Note: The Graphical Applications – Administration Tool is not available through the User package.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-5 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Once you have selected Typical installation, or selected Custom and specified all components you wish to install, the following screen will display:
9. Click Next to accept the Xerox PrintXchange 1.2 Client folder. Otherwise, type a new folder name or select another folder from the list, then click Next.
7-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Indicating the printer network type
The following screen will display, asking you to indicate the network type where the PrintXchange printers reside. 10. Select Windows Network and UNIX Network, Windows Network only, or UNIX Network only, then click Next.
If selected Windows only, you will be asked to set up PrintXchange Name Service. If selected UNIX only, you will be asked to set up cross-platform print submission and management. If selected both Windows and UNIX, you will be asked to set up PrintXchange Name Service, followed by cross-platform print submission and management.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-7 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Setting up PrintXchange Name Service
On a Windows NT client, the software will check the Primary Domain Controller (PDC) and its network segment for the PrintXchange Name Service.
If the host running PrintXchange Name Service cannot be located, the following screen will display, asking you to enter the host name.
Notes: Windows 95 users will always be asked for the PrintXchange Name Service host. If the PrintXchange Name Service is moved to a different host after installing the software on your client machine, you must enter the PrintXchange client setup tool to change the PrintXchange Name Service host setting. This only applies if the new PNS host is not on the same subnet as the PDC. 11. At the PrintXchange Server Information, enter the host name of your PrintXchange Name Service, then click Next.
7-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Setting up cross-platform print submission and management
A user needs to complete this screen to submit jobs to any PrintXchange printers in the Solaris domain. An administrator may enter cross platform information to manage PrintXchange servers in the Solaris domain from the Administrator tool on the Windows NT or Windows 95 host.
12. Enter the name of the host running the ypserver software and enter the name of the UNIX domain where the PrintXchange printers reside, then click Next. For example: NIS: ess.mc.xerox.com YP Server: tiki
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-9 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Copying files
The following screen will display:
13. The system will summarize all the information you specified. Click Back to change any of the information, or click Next to accept the current settings. The system will copy files according to your selections.
The Restart Windows screen will display.
Your PrintXchange installation on your client machine is complete.
7-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Upon restarting your computer, you should notice the following: A Xerox PrintXchange 1.2 Client submenu extending from the Start Menu A PrintXchange directory containing the software in the noted installation directory A PrintXchange Event Monitor applet in the Control Panel.
Post-installation
Once you have installed PrintXchange on your client machine, you can access four types of on-line help, through the following: Start Programs Xerox PrintXchange 1.2 Client Administrator Tool Help Start Programs Xerox PrintXchange 1.2 Client Command Line Interface Help Start Programs Xerox PrintXchange 1.2 Client Information Tool Help Start Programs Xerox PrintXchange 1.2 Client Print Submission Tool Help The on-line help provides information on how to add logical printers, set up the desired properties for your printers, specify job display filtering options, and specify attributes for printing your jobs.
Using the PrintXchange Client Setup tool
The PrintXchange Client Setup tool allows users to change the installation values set for the PrintXchange Name Service and the Cross Platform screens. If you are using printers on an NT network, you will need to change the PrintXchange Name Service host entry if the Name Service moves to a new host. To access a different Solaris domain for job submission or printer management on a Solaris network, you will need to change the ypserver and domain entries. Note: You must have administrator rights to make changes to the Name Service and Cross Platform settings. However, current settings will be displayed regardless of access rights. To change the PrintXchange installation setup values using the PrintXchange Client Setup tool: 1. Access the PrintXchange Client Setup tool through Start Programs Xerox PrintXchange 1.2 Client PrintXchange Client Setup.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-11 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
The following screen will display the current settings set from the Name Service and Cross Platform screens.
2. To change the Name Service setting, check the box next to “Print to NT Servers” then enter the PrintXchange name service host name in the text field. To change the Cross platform setting, check the box next to “Print to Unix NIS Servers” then enter the UNIX NIS domain name in the text field, and enter the ypserver host name in the Server host name field. Refer to the “Setting up PrintXchange Name Service” and “Setting up cross-platform print submission and management” subsections of the “Installing PrintXchange Client” section for information on changing values for these screens. 3. Click OK.
Accessing printers in multiple UNIX domains
By default, users can access PrintXchange logical printers in multiple NT domains and a single UNIX domain. At any time, the user may reconfigure the client software cross platform setting to change the UNIX domain. Any logical printers defined on their desktop that belong to the old domain can no longer be accessed, until the user changes the cross platform setting back to its previous value.
7-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
Uninstalling PrintXchange from a client machine
As part of the process to uninstall PrintXchange, you need to: Delete PrintXchange logical printers defined on your desktop Uninstall PrintXchange software.
Deleting PrintXchange logical printers
To delete PrintXchange logical printers: 1. Access the Printers through Start Settings Printers. 2. Delete all PrintXchange printers.
Uninstalling PrintXchange software
To uninstall PrintXchange software: 1. Access the Uninstall program through one of the following: Start Programs Xerox PrintXchange 1.2 Client Uninstall PrintXchange Start Settings Control Panel Add/Remove Programs Click the Xerox PrintXchange 1.2 Client program, then click Add/Remove. 2. On the confirmation window, click Yes. 3. Once the uninstallation is complete, click OK.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 7-13 INSTALLING AND SETTING UP PRINTXCHANGE ON A CLIENT MACHINE
7-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8. Managing security
Underlying all basic PrintXchange components is an infrastructure that enables them to function. This chapter examines the infrastructure of PrintXchange in the Windows NT environment and covers: Name Service Security Access control lists File transfer.
Name Services
A name service contains named network objects (spoolers, supervisors, logical printers, physical printers, queues) defined by the administrator. Each object contains a reference to the network address of the server that supports it. A name service serves as the vehicle that clients use to locate and bind to a server that supports a specified named network object. A name service provides information to clients and servers: Clients use the name service to locate printers, servers, and queues defined in the printing environment. Servers use the name service to locate other servers. PrintXchange supports the following name services in the ONC RPC environment (Windows NT/95 clients and UNIX servers) and Microsoft Remote Procedure Call (MSRPC) environment (Windows NT servers and clients). In the Open Network Computing Remote Procedure Call (ONC RPC) environment, Windows clients can access ONC name space. This functionality enables the Windows client to submit requests to the UNIX server (spooler and supervisor). In the MSRPC environment, PrintXchange uses PrintXchange Name Service – a distributed naming method.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-1 MANAGING SECURITY
Installing the PrintXchange Name Service
There are two ways to install the PrintXchange Name Service (PNS). The first way is done automatically when you go through the PrintXchange Server installation. This installation requires that you log in as a PXCAdmin and that this account has domain administration privileges. If the installer does not find a PNS on your domain or workgroup, then it will ask you to enter the name of the host machine where it will install PNS. It is recommended that you choose the name of the primary domain controller (or another machine within the PDC's subnet). For additional information on installing the PNS automatically, refer to the “Determining the host location for PrintXchange Name Service” section in the “Installing and setting up PrintXchange on a server machine” chapter. However, sometimes it is not possible to get domain administration privileges, so there is an alternate way of installing PNS. The NT Server CD has a new PNS installer stored in /support/pns. You need to run this installer from the host machine where you want PNS to reside. Again, it is recommended that you use the PDC or a machine within the PDC's subnet. This installation option does not require you to use the "PXCAdmin" account, although, you must have administration privileges to the selected host machine. In order to do cross-domain printing (from one domain to another), it is required to have one PNS running on each domain. This is necessary even though you may only have clients running on one of the domains. You must take special caution to ensure that PNS is installed on a machine that is always turned on. If PNS is not running, then all the clients (and servers) on that PNS' domain will stop working. This is why you must try to install PNS on the PDC or on a machine on the same subnet as the PDC. For additional information on where to install the PrintXchange Name Service, refer to Figure 5.2: PrintXchange Name Service Access.
PrintXchange name service
You can use PrintXchange Name Service only in a distributed NT domain and workgroup based network environment. This enables servers to update RPC information without your intervention, thereby making current RPC information available to clients. Using PrintXchange Name Service also enables cross-domain object reference. A PrintXchange Name Service proxy mechanism supports this cross-domain reference and works if users are in the same NT Local Area Network (LAN) segment. Although each domain and workgroup must have its own Name Service host, each has access to the others to resolve PrintXchange names without the aid of WINS or LMHOSTS when each Name Service host resides on the same LAN segment. In general, WINS or LMHOSTS resolves NetBIOS name to its IP address and also it provides a Primary Domain Controller host name for a specific NT domain. By placing the PrintXchange Name Service on the Primary Domain Controller of each domain, an alternative registry look up table is not required. In situations where WINS or LMHOSTS is used to resolve PDC host, the destination domain PrintXchange Name Service must reside on the PDC. To access to the destination domain PDC, the origin workgroup or domain PrintXchange Name Service host must be
8-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
correctly setup to use WINS or LMHOSTS as described in the “Setting up WINS” and “Setting up LMHOSTS” sections. To enable multi-LAN communication from a domain Name Service to a workgroup Name Service or a workgroup Name Service to another workgroup Name Service, PrintXchange provides a Name Service registry function. This function also enables registry of domain Name Service hosts that do not reside on the Primary Domain Controller. PrintXchange Name Service should reside on only one machine in the domain or workgroup. PrintXchange Name Service cannot ensure consistency of the name space if multiple PrintXchange Name Services are running in a single domain or workgroup. Tables 8-1 and 8-2 along with figure 8-1 explain proper setup of the PrintXchange Name Service hosts in a multiple LAN segment environment to ensure that clients on the origin workgroup or domain have access to PrintXchange printers on the destination workgroup or domain.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-3 MANAGING SECURITY
The following table explains the name resolution methods supported for each origin and destination host combination to ensure proper access between clients and printers across domains and workgroups. The examples indicate each combination. Table 8-1. Cross-domain Name Service registration methods Destination NS host Origin NS host D3NSonPDC D2NS2 or W2NS
LMHOSTS PrintXchange registry D1NSonPDC WINS PrintXchange registry
LMHOSTS PrintXchange registry D4NS or W1NS WINS PrintXchange registry
The following table lists the proper content of each Name Service host’s registry list. In cases where WINS or LMHOSTS is a supported resolution method, the Name Service host is not shown as a registry entry. Table 8-2. PrintXchange Name Service Registry list content PrintXchange Name Service registry list Name Service host Name Service host name(s) Domain name name
D1NSonPDC, DOMAIN2 D2NS2 D3NSonPDC DOMAIN4 D4NS WORKGROUP2 W2NS
D2NS2 DOMAIN4 D4NS WORKGROUP2 W2NS
D4NS DOMAIN2 D2NS2 WORKGROUP2 W2NS
W1NS DOMAIN2 D2NS2 DOMAIN4 D4NS WORKGROUP2 W2NS
W2NS DOMAIN2 D2NS2 DOMAIN4 D4NS
Note: In the sample environment, the domains and workgroup2 have not registered the Name Service for workgroup1 because workgroup1 does not have any PrintXchange servers.
8-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
In the network example in figure 8-1, all clients will have access to all PrintXchange printers in the network if each Name Service host registry list contains the entries indicated in Table 8-2. Figure 8-1 describes a complex network environment consisting of four domains and two workgroups. Each domain and workgroup exists on its own separate subnet or LAN segment. A PrintXchange Name Service host must reside in each domain or workgroup that has clients requiring access to PrintXchange printers. The clients may consist of any combination of PrintXchange Windows NT or Windows 95 clients, and NetWare, LAN Manager, or LPR gateway clients. At least one PrintXchange Windows NT server is installed in the network. Since spoolers and supervisors can be distributed across the network, at least one spooler and one supervisor must be installed to service the entire network. Generally, the location and number of spoolers and supervisors is determined by the anticipated print submission traffic in a geographic area along with the number of physical printers expected to be controlled by a supervisor. The naming convention for hosts consists of the network type (D=domain, W=workgroup), followed by a number (1-4) to distinguish each domain or workgroup, followed by a suffix acronym that describes the type of software loaded on the host, followed by a subnet number (1-2) if the domain consists of multiple subnets. The host software acronyms are as follows: NSonPDC=PrintXchange Name Service on a Primary Domain Controller PDC= Primary Domain Controller NS= PrintXchange Name Service on a non-PDC host S=PrintXchange NT Server NTC=PrintXchange Windows NT 4.0 Client 95C=PrintXchange Windows 95 Client GWC=Gateway Client. Example: D4NS is a host on Domain4 running the PrintXchange Name Service and D2NTC2 is a PrintXchange Windows NT 4.0 client located on subnet 2 of Domain2.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-5 MANAGING SECURITY
Figure 8-1. PrintXchange NT cross-domain environment
D1NSonPDC • PrintXchange NS D2GWC1 D2NTC1 D1S1 • PrintXchange Server
NT Domain 2 NT Domain 1 Subnet 1
D2PDC D295C1 NT Domain 2 D1NTC Subnet 2 D1S • PrintXchange • PrintXchange NT 4.0 Client Spooler D2S2 D2GWC2 • PrintXchange D3NSonPDC D3NTC1 • NetWare Server D2NS2 D2NTC2 Client • PrintXchange NT 4.0 Client
NT Domain 3
Subnet 1 NT Domain 4
NT Domain 3 Subnet 2 D4PDC D4NS D4S D3S2
• PrintXchange Spooler D3NTC2 • PrintXchange Supervisor W2NS
• PrintXchange NS
W1NS • PrintXchange NS W1NTC • PrintXchange GW • PrintXchange NT 4.0 Client
NT Workgroup 2 (Printers and Clients) NT Workgroup 1 (Clients only)
W2S • PrintXchange Spooler • PrintXchange W195C Supervisor W1GWC W2NTC • PrintXchange • LAN Manager Client • PrintXchange
Windows 95 Client Windows NT Client
8-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Setting up WINS
To set up WINS, complete the following steps on the origin workgroup or domain PrintXchange Name Service host: 1. Start at the Control Panel. 2. Double click Network icon. 3. Select Protocol tab. 4. Select TCP/IP and click the Property button. 5. Select WINS address in the TCP/IP property window. 6. Key in WINS server address. Note: Ensure that the WINS servers are setup appropriately to guaranty access to the destination domain PDC.
Setting up LMHOSTS
To reflect the LMHOSTS file changes to the system, type in “nbtstat –R” command from the NT command prompt. To set up "LMHOSTS" file, complete the following steps on the origin workgroup or domain PrintXchange Name Service host: 1. Open %WINDOWS%\system32\drivers\etc directory with Explorer.
2. Copy lmhosts.sam file to lmhosts file.
3. Open the lmhosts file with the editor.
4. Put in the destination domain PDC server address with the format: " server TCP/IP address " "server name" #PRE #DOM:”domain name”
Example:
012.34.567.89 PDCHOST#PRE#DOM:DOMAINNAME
Locating the Name Service host during installation
When installing a PrintXchange Windows' NT 4.0 client or server, the installation process automatically locates the Name Service if the Name Service is installed on a Primary Domain Controller or in the same subnet as the Primary Domain Controller. Note: Name Service registration must be manually reset for all PrintXchange Windows 95 clients. In sample network 2 in Figure 8-1, D2S2 and D2NTC2 are the only Windows NT 4.0 hosts that must manually specify D2NS as their Name Service host.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-7 MANAGING SECURITY
Relocating PrintXchange Name Service In order to relocate the Name Service, you must do the following: Backup PrintXchange Name Service (PNS) data files on the host running PNS. Install PrintXchange Name Service on a new host and restore the data.
Backup PrintXchange Name Service (PNS) data files
The PNS data files are located in SystemRoot\pgr directory. SystemRoot is defined by the %SystemRoot% environment variable. Example: C:\winnt. The following steps should be followed to successfully backup the PNS data files: 1. Backup the "*.dat" files and "pgrhosts" file in the directory. 2. Then uninstall the PNS. Uninstalling the Name Service will remove all the PNS data files(*).
Installing the Name Service on a new host
Installing the Name Service on a new host, then restoring the PNS data requires the following steps: 1. Copy the “*.dat” files and “pgrhosts” you backed up in the %SystemRoot%\pgr\*.dat files directory to the new system. 2. PNS should be started via the control panel after restoring the data files. You must restart all the PrintXchange servers in the domain or the workgroup after the new PNS is started. This procedure insures that PNS restores the PNS data files itself just incase the data files are lost and the new PNS is started without the data files.
Effect of relocation on PNS settings
PNS relocation may affect the PNS setting of PrintXchange servers/clients on the network. The PNS host name is manually entered during the servers/clients installation process whenever the installation process cannot automatically find PNS on the network. PrintXchange Windows NT 4.0 Client/Server Name Service registration after Name Service host relocation must only be performed manually if the Name Service is relocated to a subnet different from the subnet where the PDC resides. Note: Name Service registration must be manually set for all PrintXchange Windows 95 clients. Manual PNS resetting may be performed on Windows NT servers via the Setup PrintXchange tool and performed on Windows NT and Windows 95 clients via the Setup PrintXchange Client tool.
8-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
PrintXchange Name Service properties setup
This section provides information on setting the properties for the PrintXchange Name Service installed component. For instruction on Name Service installation, refer to the “Installing and setting up PrintXchange on a server machine” chapter. After completing the PrintXchange Name Service installation, fine tuning the Name Service properties is performed by entering the Setup PrintXchange tool, refer to the “Installing and setting up PrintXchange on a server machine” chapter. The following dialog boxes in the Setup PrintXchange tool enable configuration of the Name Service.
PrintXchange name service properties
To set the service properties of PrintXchange name services, set the following parameters.
Base properties
Data cache period PrintXchange name service will refresh the domain name list of the network within this time period. (If a new domain is published on the network PrintXchange name service will obtain the domain name after this period).
Min: 60 (sec) Max: 259200(sec)(->3days)
Max cache copy number of PDC PrintXchange name service caches the domain name list in its own data area. The maximum number of this domain name list will be limited to this number.
Min: 2, Max:120
Data file location PrintXchange name service will store its data files in the specified directory.
Path environment uses this directory name with the format:
%EnvironmentVariable%
Default: %SytemRoot%pgr
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-9 MANAGING SECURITY
Security
Security has two components: Authentication, which ensures that users are who they claim to be. Authorization, which ensures that users have permission to perform a particular operation. The Authorization component uses the information in the access- control-list attribute for validation. One of your tasks when you initially set up your PrintXchange system is to set the privilege levels for all users. Do so by setting the value of access-control-list. Once PrintXchange is up and running, you will need to modify access-control-list as you add or remove users or change their privilege levels.
Authentication
Authentication validates that users really are who they claim to be. In a distributed environment, authentication depends on the underlying network communication services. PrintXchange authentication occurs as part of the RPC communication between clients and servers. In Windows NT-based, PrintXchange Name Service-supported network environments, PrintXchange uses Windows NT Security, a built-in MSRPC method to authenticate users which: Retrieves the user name and domain name sent from the client by means of MSRPC. Checks that the incoming user name and domain name match the values of the name and domain elements of an access- control-list entry. During the print operation, the spooler writes the user name that it retrieved during authentication into the document or job user-name attribute using the Universal Name Convention (UNC) format.
Cross-domain features
Windows NT has two cross-domain features: Trusted-domain, which is the native cross-domain facility in the Windows NT environment. In this environment, the server has a Primary Domain Controller (PDC) or Backup Domain Controller (BDC) which authenticates clients from trusted domains. Therefore, domain users and trusted domain users can be authenticated by PDC or BDC and can access a PrintXchange server easily. In the Windows NT security environment, PrintXchange authenticates a user in the following cases, and sets the job’s user-name attribute from the authenticated user name: A domain user sends operations to a server in the same domain: ntsecurity:ServerDomainName\User “ntsecurity” is the domain’s name-syntax
8-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
A domain user sends operations to a server in another domain and the server domain trusts the client domain: ntsecurity:ClientDomainName\User Excluding the above, when the user name exists in the server’s Local User Manager, and the password matches: ntsecurity:ServerComputerName\User This case has an exception, that is, when the server is the domain controller: ntsecurity:ServerDomainName\User Otherwise, user access is rejected by the server. Because the user cannot be authenticated by Windows NT Security. PrintXchange cross-domain This feature is available when the proxy-submit-supported configuration attribute is set to true. In the PrintXchange cross-domain environment, PrintXchange authenticates a user in the following cases, and sets the job’s user-name attribute from the authenticated user name: A domain user sends operations to a server in the same domain: ntsecurity:ServerDomainName\User “ntsecurity” is the domain’s name-syntax A local user sends operations to a server in the same domain or WORKGROUP: ntsecurity:ServerComputerName\User A domain user on Windows NT sends operations to a server in another domain or WORKGROUP: winnt:ClientDomainName\User “winnt” is the domain’s name-syntax A local user on Windows NT sends operations to a server in another domain or WORKGROUP: winnt:ClientComputerName\User Because Windows 95 cannot obtain a user’s domain name, the server authenticates both a domain user and a local user on Windows 95 in another domain or WORKGROUP as: win95:ClientComputerName\User “win95” is the domain’s name-syntax (NT PXC SERVER CANNOT SUPPORT NON-LOGGED IN 95 USER) On a print operation, the spooler writes the user name that it retrieved during authentication into the job’s user-name attribute in the Universal Name Convention (UNC) format.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-11 MANAGING SECURITY
Windows NT has a Guest access mechanism. When “Guest” is enabled, users who cannot be authenticated by NT Security are authenticated as: On Windows NT: winnt:ClientDefaultDomainName\User (Domain User on WindowsNT) winnt:ClientComputerName\User (Local User on WindowsNT) On Windows 95: win95:ClientComputerName\User On Windows 95: win95:ClientMachineName\User If customers want to prevent these users from submitting operations, the Guest account should not be enabled, or an appropriate server or printer ACL should be set.
In both Trusted-domain and PrintXchange cross-domain, PrintXchange authenticates a user in the following cases, and sets the job user-name attribute from the authenticated user name, as shown by the cases in Tables 8-3 and 8-4. Table 8-3. User authentication in trusted domain
Authentication Condition The server authenticates the user as:
A domain user sends operations to a ntsecurity:ServerDomainName\User server in the same domain (“ntsecurity” is the domain name-syntax)
A domain user sends operations to a ntsecurity:ClientDomainName\User server in another domain (The server domain trusts the client domain.)
The user name exists in the server ntsecurity:ServerComputerName\User Local User Manager, and the password matches ntsecurity:ServerDomainName\User Exception: when the server is the domain controller
8-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Table 8-4. User authentication in PrintXchange cross- domain
Authentication Condition The server authenticates the user as:
On a print operation, when “Guest” is Windows NT has a Guest access mechanism. enabled, users who are not domain users or who have no account in the On Windows NT: winnt:ClientDomainName\User server’s Local User Manager are (Domain User on WindowsNT) authenticated as: winnt:ClientComputerName\User (Local User on WindowsNT)
On Windows 95: win95:ClientComputerName\User
A local user sends operations to a ntsecurity:ServerComputerName\User server in the same domain. The user name exists in the server LocalUserManager, and the password matches ntsecurity:ServerDomainName\User Exception: when the server is the domain controller
A domain user on Windows NT winnt:ClientDomainName\User sends operations to a server in another domain
A local user on Windows NT sends winnt:ClientComputerName\User operations to a server in another domain
A user on Windows 95 sends The server authenticates both a domain user and a local operations to a server in another user on Windows 95 as: domain win95:ClientComputerName\User
On a print operation, when “Guest” is Windows NT has a Guest access mechanism. enabled, users who are not domain users or who have no account in the On Windows NT: server’s Local User Manager are winnt:clientDomainName\User authenticated as: (Domain User on WindowsNT) winnt:ClientComputerName\User (Local User on WindowsNT)
On Windows 95: win95:ClientComputerName\User
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-13 MANAGING SECURITY
How PrintXchange authenticates a cross-domain user
User authentication in trusted domain Users who logon the client computer locally and domain users whose domain has no trusted relationship with the server’s domain are authenticated as local account users on the server computer. PrintXchange authenticates a user and sets the job user-name attribute from the authenticated user name as:
ntsecurity:ServerName\User ntsecurity:DomainName\User
User authentication in PrintXchange PrintXchange cross-domain privileges are provided to customers cross domain who meet the following requirements: Choice 1: Do not want to establish a trusted relationship between domains. Choice 2: Want to send the job through with a Windows NT local user account from the computer on cross-domain without creating a local account on the server computer. PrintXchange cross-domain is enabled when the PrintXchange server’s proxy-submit-supported attribute is set to TRUE. When this attribute is set, all users on the cross-domain computer do not obey NT Security. PrintXchange security trusts the user information sent by the user on cross-domain. PrintXchange authenticates a user and sets the job user-name attribute from the authenticated user name as: winnt:ClientComputerName\User
8-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Selecting the cross-domain
PrintXchange supports two cross-domain, Windows NT native trusted-domain and PrintXchange cross-domain. Customer can select the appropriate facility
Trusted domain This is the default configuration of PrintXchange. PrintXchange Server/Client always obey native Windows NT security. This provides high level security. (This means PrintXchange can provide the security as high level as Windows NT can.) This is usable for customers who meet the following requirements: Choice 1: Need secure server Choice 2: Already construct NT Trusted Domain environment
PrintXchange cross domain PrintXchange cross-domain privileges are provided to customers who meet the following requirements: Choice 1: Do not want to establish a trusted relationship between domains. Choice 2: Want to send the job through with a Windows NT local user account from the computer on cross-domain without creating a local account on the server computer. PrintXchange cross-domain is enabled when the PrintXchange server’s proxy-submit-supported attribute is set to TRUE. When this attribute is set, PrintXchange security trusts the user information sent by the user on cross-domainand do not obey NT Security. This results in providing lower security than the trusted domain.
Authorization
Authorization validates that users have permission (or authority) to perform tasks they attempt to perform. Users’ privilege levels determine what they can do. Clients (users) of PrintXchange have three privilege levels: System Administrator Operator End User. The user privilege levels have an access order: An Administrator can configure objects and perform all Operator tasks. An Operator can control printing and perform all End User tasks. Table 8-5 summarizes the capabilities of each privilege level according to PrintXchange tasks.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-15 MANAGING SECURITY
Table 8-5. PrintXchange privilege levels per task
Tasks Command Description Minimum Privilege Pertinent Objects Level Clean pdclean Delete all jobs from an Operator Spooler, queue object Create pdcreate Create objects and set System administrator Logical printer, queue, physical initial attributes printer, initial-value-jobs, initial- value-documents Delete pddelete Delete objects System administrator All except documents Disable pddisable Disable the acceptance Operator Logical printer, spooler, queue, of new print requests supervisor, physical printer Enable pdenable Enable the acceptance Operator Logical printer, spooler, queue, of new print requests supervisor, physical printer List pdls List the names of print End user All attributes objects and the names and values of their attributes Modify pdmod Change the values of End user Job, document job or document attributes Pause pdpause Pause an object so that End user (job owner Job, spooler, queue, physical it does not continue only) printer operation Operator (all) Print pdpr Send a document or job End user Logical printer to print Promote pdpromote Move a document or Operator Job job to the head of its queue List job pdq List document or job End user Document, job queue status attributes Resubmit pdresubmit Move a job to another End user (document Job, queue logical printer or job owner only) Operator (all) Resume pdresume Resume a paused End user (document Spooler, queue, physical object so that it picks up or job owner only) printer, job operation where it Operator (all) stopped Cancel pdrm Cancel a print request End user Job Set pdset Set attributes of objects End user (document All attributes or job owner only) Operator (physical printers) System administrator (all) Shutdown pdshutdown Shut down a server Operator Spooler, supervisor
8-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Access Control Lists (ACLs)
Administrators may set Access Control Lists (ACLs) for all PrintXchange objects (except document and job objects). Typically, however, you set server ACLs only. The server ACL specifies the access to all objects belonging to the server that do not have an ACL. In exceptional cases, ACLs may be set for specific objects (other than servers) to further restrict access to those objects. If an object has an ACL, then the values for a given privilege-level are used. If the object ACL does not have any values for a given privilege-level, then the server ACL values for only that privilege-level are used. Therefore, you could set end user privilege-level ACL values on a logical printer to restrict submission to that printer. However, if the ACL for that logical printer did not have any administrator values, then the administrator privilege-level server ACL values would be used for administrator operation authorization on that logical printer.
Defining ACLs
PrintXchange servers have ACLs that control access to all objects within the servers. The access-control-list attribute defines server ACLs. ACLs can be defined through the GUI administrator tool or using CLI. For details on using this method, refer to the GUI online help. The access-control-list attribute is multi-valued, and each value may have up to four elements: Name Domain Name-type Privilege-level. name The name element value must be omitted when name-type=all users. When present, the name element value identifies a specific user or group as specified by the name-type element. domain The domain element is always optional. If the domain element is not specified, the server uses its (the server’s) default domain. The domain element is valid only when the name-type element is user or all-users. The domain element itself consists of two sub-elements: name-syntax (optional) name. The domain element syntax is: [name-syntax:]name The name-syntax sub-element identifies the domain type and is optional. If the domain name sub-element is the null string, then the server recognizes all domains specified by the name-syntax sub-element. If name-syntax is not specified, the server uses its (the server’s) default domain type, that is “ntsecurity:”.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-17 MANAGING SECURITY
ntsecurity This domain type is used for all users accessing PrintXchange servers in the following circumstances: The domain account is on the same domain as the server machine. The domain account is on a trusted domain (DOM2) of the server’s machine. The user name exists in the server Local User Manager, and the password matches. When server’s proxy-submit-supported configuration attribute is set to true, it means PrintXchange cross-domain, this is applicable only to the user in same domain or WORKGROUP. win95. This domain type is used for all users accessing PrintXchange servers from a Windows 95 machine. . This domain type is applicable to user who are not authenticated as ntsecurity domain type. winnt. This domain type is used for all users accessing PrintXchange servers in the following circumstances: The domain account is on a non-trusted domain (DOM3) of the server machine’s domain (DOM1) The local account is on an NT machine other than server’s machine. On UNIX only for a cross-platform Windows NT user. This domain type is applicable to users who are not authenticated as ntsecurity domain type. Any. This is a special domain type. This domain type matches all domain types – ntsecurity, win95 and winnt. Server’s default domain is defined as: When server computer joins the NT Domain, domain=ntsecurity:ServerDomainName When server computer joins the WORKGROUP, domain=ntsecurity:ServerComputerName name-type This option specifies the type of user. The legal values are: all-users user group If the name-type element is not specified, then the server uses group as the default. privilege-level This option specifies the access level of the user. The legal values are: end user operator administrator.
8-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Rules for using these options are:
If you specify name but not name-type, name-type defaults to group. If you specify neither name nor name-type, name-type defaults to all-users. If you do not specify privilege-level, privilege-level defaults to end user. If name-type=all-users, the server ignores name. This means that the server accepts any request for the specified privilege level. If name is not all-users, you must specify name. The name of the user making a server request must be: An exact match to name, if name-type=user A member of the group, if name-type=group
Creating access control lists using CLI
To create a server ACL, use the pdset command. The syntax is: pdset -c server -x “access-control-list={name domain name-type privilege-level}” spooler_name or pdset -c server -x “access-control-list={name domain name-type privilege-level}” supervisor_name field description name User’s name name-type Type of user: all-users user group privilege-level Type of access level: - end user - operator - administrator If name-type is all-users, the server ignores name. Therefore, the server accepts any request for the specified privilege level. If you do not specify name, and if you also do not specify name-type, then the server sets name-type to all-users. If name-type is other than all-users, you must specify name. Also, the name of the making the request must be: An exact match to name, if name-type=user. A member of the group, if name-type=group.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-19 MANAGING SECURITY
Default ACL
The default server ACL has two values: 1. domain=ntsecurity:ServerComputerName, name-type=all- users; privilege-level=end user 2. name=administrators; domain=ntsecurity:ServerComputerName, name-type=group, privilege-level=administrator 3. (When server joins the NT Domain) domain=ntsecurity:ServerDomainName, name-type=all- users; privilege-level=end user When you create a server, the server sets the values for its ACL (unless you set an administrator value ACL with the -A startup option). Example: To reset a server access-control-list to the default using the CLI: pdset -c server -x “access-control-list=“ spooler_name The example replaces the specified server’s ACL values with the default values listed above, regardless of what is locally correct. The default non-server ACL has no values.
ACL without privilege specification
When an ACL does not specify a privilege level, valid authorization is as follows: When a server ACL does not specify at least one Administrator privilege, please restart the server. During startup, the server shall set the following default ACL. name=administrators; domain=ntsecurity:ServerComputerName, name-type=group, privilege-level=administrator. When an ACL does not specify Operator privilege, as in the default values, a user must have Administrator privilege to perform operator or administrative operations. When an ACL does not specify End User privilege, a user must have Operator or Administrator privilege to perform End User operations.
8-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
Examples
Example 1 To specify a single value of an ACL with a CLI command: pdset -c server -x “access-control- list={name=norm}” spooler1 The example is exactly equivalent to: pdset -c server -x “access-control- list={name=norm name-type=group privilege-level=end user}” spooler1 If name is specified and name-type is not specified, name-type defaults to group. If privilege-level is not specified, it defaults to end user. Example 2 To set the ACL on “spooler1” so that members of the dpt group are operators: pdset -c server -x”access-control- list+={name=dpt privilege-level=operator}” spooler1 Example 3 To remove the user “ginger” from the approved operators for supervisor1. pdset -c server -x “access-control-list- ={name=ginger name-type=user privilege-level=operator}” supervisor1 Example 4 To make all objects on the “spooler1” server available to all users from the server’s default domain. pdset -c server -x “access-control-list+={name- type=all-users}” spooler1 Example 5 To set the ACL on “Spooler1” so that all users who are authenticated as “ntsecurity:TrustedDomain\User” are end-user. pdset -c server -x “access-control- list+={domain=ntsecurity:TrustedDomain name- type=all-users}” spooler1 Example 6 To make all objects on the “spooler1” server available to all users from any domain and any platform. pdset -c server -x “access-control- list+={domain=any: name-type=all-users}” spooler1 An operator included with the attribute type=value pairs indicates the type of modification to be done to the specified attribute. The form of the attribute type=value pairs for pdset is: attr[+ | – | =]=val, where
attr Attribute type
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-21 MANAGING SECURITY
Modification operator
You can include an operator with attribute=value pairs to indicate the type of modification to be done to the specified attribute. The three modification operators are: + (add value) When you use attribute+=value, you add a value to the attribute. This can only be used with multi-valued attributes. If you add a value that already exists, the attribute contains the same value twice. - (remove value) When you use attribute-=value, you remove a value to the attribute. If the value is not present, pdmod ignores the command. If you remove the last value for an attribute, pdmod sets the value to the server default. If a value to be removed occurs more than once. pdmod removes all occurrences. = (reset to default value) When you use attribute==value, you set the attribute value to its default. Do not include a value for when resetting to the default value.
8-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
File transfer
The file-transfer mechanism determines how a document or job gets from the client to the spooler, and from the spooler to the supervisor. PrintXchange builds file security in to file transfers by ensuring that users can access only those files for which they have read access. If the user does not have read access to the file, the print request fails. PrintXchange supports three file-transfer mechanisms: with-request The client, after checking the accessibility of the file, sends the document data to the spooler as part of the print request. The spooler copies the data into its spool directory. socket The client, after checking the accessibility of the file, sends the print request to the spooler. The spooler returns socket information, used by the client to connect and write the document data, to the socket. The spooler reads the data from the socket and writes it to its spool directory. file-reference The client, after checking the accessibility of the file, sends the print request to the spooler along with a file-path reference. The spooler copies the file into its spool directory. Note: If the user does not have read access to the file, the print request fails. When the spooler transfers document data to a supervisor on the same host, it uses the file-reference mechanism. If the spooler and supervisor are not on the same host, or if the print request does not specify a file-transfer mechanism, the spooler uses the following default algorithm: If file size <10,000 bytes, with-request is used. Otherwise, socket is used.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-23 MANAGING SECURITY
Transfer methods
When you submit a print request from a client, the client transmits the request to the spooler. The request indicates how the print data associated with the print request will reach the spooler. When processing the incoming print request, the spooler checks the transfer-method attribute to determine what it should do to receive the print data. PrintXchange supports three methods that determine how print data reaches the spooler: with-request (for jobs up to 1 MB) socket file-reference. You can set the transfer method with the CLI pdpr print request. If the print request does not specify a transfer method, the spooler uses the following algorithm to determine the default: If the file size is less than 10,000 bytes, the spooler uses the with-request transfer method. Otherwise, the spooler uses the socket transfer method. The GUI does not provide access to the transfer-method attribute. All print requests originating with the GUI use the default transfer method.
with-request transfer method
The client sends the document data to the spooler directly as part of the print request. The spooler copies the document data to its spool directory. The with-request transfer method is valid only for jobs up to 1 MB in size. The print job submission does not complete until the client completely transfers the document data to the spooler. To set a with-request transfer method: CLI: pdpr -x "transfer-method=with-request" filename GUI: This function is not accessible with the GUI.
socket transfer method
When the spooler first receives the print request, the spooler returns socket information. The client then connects and writes the document data to this socket. The spooler reads from the socket and writes the data to a file in the spooler’s spool directory. The print job submission does not complete until the client completely transfers the document data to the spooler. To set a socket transfer method: CLI: pdpr -x "transfer-method=socket" filename GUI: This function is not accessible with the GUI.
8-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING SECURITY
file-reference transfer method
The client sends a file path reference for the document to the spooler. Before returning from the print request, the spooler determines if it can reference the document. If the spooler cannot reference the document, the print request fails. To set a file-reference transfer method: x CLI: pdpr -x "transfer-method=file-reference"
Spooler-to-supervisor file transfer and default method
When the spooler transfers document data to the supervisor, the spooler determines if the supervisor is on the same host and, if so, the spooler uses the file-reference transfer method. Otherwise, the spooler uses the same algorithm that it used with the client: If the file size is less than 10,000 bytes, the spooler uses the with-request transfer method. Otherwise, the spooler uses the socket transfer method.
File security
PrintXchange ensures that users can access only files for which they have read access. If the user specified the with-request transfer method,the client checks the accessibility of the file just before including the file on initiating the print request. If the user specified socket transfer method, the client checks the accessibility of the file just before sending the file over a socket. In both cases, if the user does not have access, the print request utility fails. In addition, if the user specified the file-reference transfer method with the print request, the spooler ensures that the original user still has read access to the file. This is to ensure that the file is not modified between the time of the print request and the time the spooler copies the file.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 8-25 MANAGING SECURITY
8-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9. Setting event notification
Event notification
PrintXchange reports system problems or interesting events to users through notification services. Events are reported to the user by e- mail or an immediate message. If you request notification of a class of events, you will receive notification of all events of that class. Examples of events include: Server shutdown Normal completion of print jobs Cancellation of document by the user Printer resource needs attention. The attribute notification-profile specifies the events to be reported and the delivery method. Users can specify a notification-profile for the following objects: Printer Servers (spoolers and supervisors) Job Queue. Only an Administrator can specify notification-profile for printer, queue, and server objects as part of the create (pdcreate) or set attribute (pdset/pdmod) operations. An End User can specify profiles for a job at job submission time using the pdpr operation. Windows NT uses the following environment variables for notification: MD_PASSWORD Determines the password for mail delivery. MD_PROFILE Determines the profile for mail delivery. MD_USER Determines the user for mail delivery. The GUI includes event notification management windows to set notification profiles and preferences.
Events
Users can specify events by class or by specific events. If the notification-profile attribute specifies a class, the corresponding notification service reports all events of that class. Table 9-1 lists the events, their classes, the objects to which they apply, and the corresponding messages that are supported in PrintXchange. Note: The set of events logged varies, depending on the printer’s type and communication interface.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-1 SETTING EVENT NOTIFICATION
Table 9-1. Events
Class Object Message
aborted Recovery action for aborted events consists of the user resubmitting the job. If the job continues to be aborted, the administrator should check the service log (refer to the “Troubleshooting” chapter in this guide). document-aborted-by-server Document The server aborted the document. job-aborted-by-server Job The server aborted the print job. job-cancelled-by-operator Job The operator cancelled the print job. job-cancelled-by-user Job The user cancelled the print job. document-status report-object-created Document The object has been created. report-object-deleted Document The object has been deleted. report-object-modified Document The object has been modified. Error Recovery action for error events consists of the user resubmitting the job or retrying the operation running when the error occurred. If the error continues to recur, the administrator should check the service log (refer to the “Troubleshooting” chapter in this guide). error-job-submission-not-complete Job The server has not fully received the job. error-job-timed-out Job The spooler cannot communicate with the printer. error-no-document Server A document for this print job is not accessible to the server. error-past-discard-time Job The discard time for the print job has passed. error-other All The server has encountered some uncategorized error condition. job-attention document-aborted-by-server Document The server aborted the document. error-job-submission-not-complete Job The server has not fully received the job. error-job-timed-out Job The spooler cannot communicate with the printer. error-no-document Server A document for this print job is not accessible to the server. error-past-discard-time Job The discard time for the print job has passed. job-aborted-by-server Job The server aborted the print job. job-cancelled-by-operator Job The operator cancelled the print job. job-cancelled-by-user Job The user cancelled the print job. warning-assigned-printer-needs- Job The printer assigned to the job needs attention. attention warning-close-to-discard-time Job The retention period is near an end. warning-job-modified Job The print job was modified. warning-job-paused Job The print job has been paused. warning-job-requeued Job The server has requeued the job. job-status report-checkpoint-taken Job The server has saved a checkpoint for the job. report-file-transferred Document The client or server has completed a file transfer. report-job-assigned-to-queue Job The job has been assigned to a queue. report-job-completed Job The print job ‘MyPrintJob’ completed on printer physicalPrinteNamer at hh:mm. (hh = 00 - 23; mm = 00 - 59)
9-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING EVENT NOTIFICATION
Table 9-1. Events (continued)
Class Object Message
report-job-data-change Job The job encountered a data change on the following data: printers-assigned notification-profile current-job-state job-name job-priority job-discard-time report-job-promoted Job The print job has been promoted. report-job-resubmitted Job The print job has been resubmitted. report-job-resumed Job The print job has been resumed. report-object-created Job The object has been created. report-object-deleted Job The object has been deleted. report-object-modified Job The object has been modified. report-object-paused Job The object has been paused. report-object-resumed Job The object has been resumed. report-printing-started Job The server has begun printing the print job. report-processing-started Job The server has begun processing the print job. state-changed-job Job The job state changed to ‘...’. printer-attention warning-assigned-printer-needs- Job The printer assigned to the job needs attention. attention warning-printer-needs-attention Printer The printer needs attention. The message will include additional information on the problem: cover-open duplex-fail input-tray-fail jammed no-cassette no-drum output-bin-full output-tray-fail service-requested other warning-printer-timed-out Printer The physical printer has timed-out. warning-printer-unable-to-register Printer The physical printer could not register with the queue. warning-resource-needs-attention Printer A resource needs the attention of a key operator. printer-status report-object-created Printer The object has been created. report-object-deleted Printer The object has been deleted. report-object-modified Printer The object has been modified. report-object-paused Printer The object has been paused. report-object-resumed Printer The object has been resumed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-3 SETTING EVENT NOTIFICATION
Table 9-1. Events (continued)
Class Object Message
report-printer-data-change Printer The printer encountered a data change on the following data: printer-name printer-locations printer-state maximum-printer-speed report-printer-received-attention Printer A previous problem with the printer has been resolved. report-printer-registered Printer The printer has registered with the spooler. report-printer-unregistered Printer The printer has unregistered with the spooler. state-changed-printer Printer The printer state changed to ‘...’. queue-attention warning-queue-backlogged Queue The queue is backlogged. warning-queue-clean-aborted Queue The queue has aborted a clean operation. warning-queue-resubmit-aborted Queue The queue has aborted a resubmit operation. queue-status report-object-cleaned Queue The object has been cleaned. report-object-created Queue The object has been created. report-object-deleted Queue The object has been deleted. report-object-modified Queue The object has been modified. report-object-paused Queue The object has been paused. report-object-resumed Queue The object has been resumed. report-queue-clean-completed Queue The queue has completed a clean operation. report-queue-not-backlogged Queue The queue is no longer backlogged. report-queue-resubmit-completed Queue The print jobs in the queue have been resubmitted. state-changed-queue Queue The queue state changed to ‘...’. report report-checkpoint-taken Job The server has saved a checkpoint for the job. report-file-transferred Document The client or server has completed a file transfer. report-job-assigned-to-queue Job The job has been assigned to a queue. report-job-completed Job The print job ‘MyPrintJob’ completed on printer physicalPrinteNamer at hh:mm. (hh = 00 - 23; mm = 00 - 59) report-job-data-change Job The job encountered a data change on the following data: printers-assigned notification-profile current-job-state job-name job-priority job-discard-time report-job-discarded Job The server has discarded the job. The retention period has expired. report-job-promoted Job The print job has been promoted. report-job-resubmitted Job The print job has been resubmitted. report-job-resumed Job The print job has been resumed. report-object-cleaned Queue The object has been cleaned. Server
9-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING EVENT NOTIFICATION
Table 9-1. Events (continued)
Class Object Message
report-object-created Document The object has been created. Job Printer Queue report-object-deleted Document The object has been deleted. Job Printer Queue Server report-object-modified Document The object has been modified. Job Printer Queue Server report-object-paused Job The object has been paused. Printer Queue Server report-object-resumed Job The object has been resumed. Printer Queue Server report-printer-data-change Printer The printer encountered a data change on the following data: printer-name printer-locations printer-state maximum-printer-speed report-printer-received-attention Printer A previous problem with the printer has been resolved. report-printer-registered Printer The printer has registered with the spooler. report-printer-unregistered Printer The printer has unregistered with the spooler. report-printing-started Job The server has begun printing the print job. report-processing-started Job The server has begun processing the print job. report-queue-clean-completed Queue The queue has completed a clean operation. report-queue-not-backlogged Queue The queue is no longer backlogged. report-queue-resubmit-completed Queue The print jobs in the queue have been resubmitted. report-server-clean-completed Server The server has completed a clean operation. report-server-data-change Server The server encountered a data change: add-logical-printer set-logical-printer delete-logical-printer add-physical-printer set-physical-printer delete-physical-printer add-job set-job delete-job report-server-shutdown-started Server The server has started a shutdown operation report-server-startup-complete Server The server has started.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-5 SETTING EVENT NOTIFICATION
Table 9-1. Events (continued)
Class Object Message
server-attention error-other All The server has encountered some uncategorized error condition. warning-server-clean-aborted Server The server has aborted a clean operation. warning-other All The server has encountered some uncategorized warning condition. server-status report-object-cleaned Server The object has been cleaned.
report-object-deleted Server The object has been deleted. report-object-modified Server The object has been modified. report-object-paused Server The object has been paused. report-object-resumed Server The object has been resumed. report-server-clean-completed Server The server has completed a clean operation. report-server-data-change Server The server encountered a data change: add-logical-printer set-logical-printer delete-logical-printer add-physical-printer set-physical-printer delete-physical-printer add-job set-job delete-job report-server-shutdown-started Server The server has started a shutdown operation. report-server-startup-complete Server The server has started. state-changed-server Server The server state changed to ‘...’. state-changed state-changed-job Job The job state changed to ‘...’. state-changed-printer Printer The printer state changed to ‘...’. (when printer-state changed) The printer has been enabled. (when printer enabled) The printer has been disabled. (when printer disabled) state-changed-queue Queue The queue state changed to ‘...’. (when state changed) The queue has been enabled. (when queue enabled) The queue has been disabled. (when queue disabled) state-changed-server Server The server state changed to ‘...’. (when server-state changed) The server has been enabled. (when server enabled) The server has been disabled. (when server disabled)
9-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING EVENT NOTIFICATION
Table 9-1. Events (continued)
Class Object Message
warning warning-assigned-printer-needs- Job The printer assigned to the job needs attention. attention warning-close-to-discard-time Job The retention period is near an end. warning-job-modified Job The print job was modified. warning-job-paused Job The print job has been paused. warning-job-requeued Job The server has requeued the job. warning-other All The server has encountered some uncategorized warning condition. warning-printer-needs-attention Printer The printer needs attention. The message will include additional information on the problem: cover-open duplex-fail input-tray-fail jammed no-cassette no-drum output-bin-full output-tray-fail service-requested other warning-printer-timed-out Printer The physical printer has timed-out. warning-printer-unable-to-register Printer The physical printer could not register with the queue. warning-queue-backlogged Queue The queue is backlogged. warning-queue-clean-aborted Queue The queue has aborted a clean operation. warning-queue-resubmit-aborted Queue The queue has aborted a resubmit operation. warning-resource-needs-attention Printer A resource needs attention. warning-server-clean-aborted Server The server has aborted a clean operation.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-7 SETTING EVENT NOTIFICATION
Notification server
A notification server that runs on every host that runs a server handles notification. The notification server is not needed on a client’s host. The Service Control Manager starts the notification server when the system comes up. The notification server then waits until it receives a request for it. The notification server does not start up if the Microsoft Windows Messaging MAPI profile is not configured correctly on server hosts. Client hosts must set their configuration to receive SMTP mail or MS mail. Note: If the MAPI profile is changed while the notification server is running, changes will take effect after re-starting the notification server. There is no configuration required to use immediate message notification. Log Messages The service logging behavior of the notification server can be configured by environment variables only. If a MAPI profile is not configured on the server host, an initialization error for the e-mail component of the notification server is logged each time the notification server is started.
Specifying profiles
You can define notification profiles for servers, queues, logical and physical printers, jobs, and documents. Subsequent chapters refer you to this section to define event-notification profiles for other objects.
Specifying profiles using GUI
To display events using GUI, from the Event Monitor message window: 1. Set the notification-profile attribute element delivery-method to socket-event, 2. Set the element delivery-address to the host name or the IP address of the client. 3. The Event Monitor displays the events depending on the user selections via the notification-profile attribute. For additional information on event monitor, refer to the “Using the CLI and GUI” chapter.
9-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING EVENT NOTIFICATION
Specifying profiles using CLI
Use the pdset command to define notification profiles. The syntax is class_name used to determine the object_instance: pdset -c class_name -x "notification-profile={event-identifiers delivery-method event-comment delivery-address locale}" object_instance where: class_name object_instance server spooler_name server supervisor_name queue queue_name printer (default) logical_printer_name printer physical_printer_name job [spooler_name:]job_identifier The syntax for multiple values is: pdset -c class_name -x "notification-profile={event-identifiers delivery-method event-comment delivery-address locale} {event- identifiers delivery-method event-comment delivery-address locale}" object_instance Brief explanations of the attribute elements are below. For details on all CLI commands, refer to the PrintXchange Command Line Interface Reference Guide. The notification-profile attribute is multi-valued. Each value contains the following fields:
field description event-identifiers A list of event types or event classes. A user can obtain a list of the events by executing a list (pdls) operation on the server object for the events-supported attribute. If this field is omitted, then all events are reported for the object. delivery-method Specifies how the messages are to be delivered. The supported values are: smtp-mail (the CLI alias is email) ms-mail socket-event (the CLI alias is message) notification-service (for cross-platform support only)
electronic-mail (handled as smtp-mail). event-comment A comment included in the notification message. There is no default.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-9 SETTING EVENT NOTIFICATION
field description delivery-address The address where the notification is to be sent. For smtp-mail (email or electronic- mail) notification, the format for the address is:
-x “notification-profile += {event-identifiers=aborted state- changed-server delivery-method=smtp-mail event- comment=‘Something\’s up’ delivery-address=agreen@osprey locale=en_US.ASCII}”
9-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING EVENT NOTIFICATION
The delivery-method and delivery-address components may also be specified by using the aliases or by setting them explicitly with the -x flag, as follows (square brackets [ ] indicate optional parameters): -x “notification-profile=smtp-mail:
“ -x “notification-profile=email:“ -x “notification-profile=ms-mail:“ -x “notification-profile=socket-event: -x “notification-profile=message:“ -x “notification-profile=notification-service:“ (for cross-platform support only) -x “notification-profile=electronic-mail:“ Since notification-profile is a multi-valued attribute, events can be reported to more than one user. A value of notification- profile is needed for each user. Although only an Administrator can set notification-profile, any user can be specified for receipt of the notification messages. When specifying multiple values using the curly brace syntax, each specification must be within the curly braces and the entire specification enclosed in quotes. For example: -x “notification-profile={profile1} {profile2}” If a notification-profile is not specified when an object is created, no defaults are provided. Defaults are only supplied for missing fields within a notification-profile. If a user specifies the -N notification_method flag with the pdpr command, the client sets the event-identifiers field to a job- completed event. The event reflects a successful completion, or if anything keeps the job from completing successfully, the event is ‘report-job-completed aborted’. The other fields are filled with the values appropriate to the delivery method. For example: The example causes PrintXchange to deliver by email to bapple@xygolf messages regarding the aborted class events (job- aborted-by-server, job-cancelled-by-operator, and job-cancelled-by- user) as well as the state-changed-server event. The notification messages will include the comment “Something’s up”. pdset -c server -x “notification-profile += {event-identifiers=aborted state-changed-server delivery-method=electronic-mail event- comment=‘Something\’s up’ delivery- address=bapple@xygolf locale=en_US.ASCII}” spooler1PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 9-11 SETTING EVENT NOTIFICATION
Delivery methods
PrintXchange delivers notifications as: Electronic mail An immediate message.
Electronic mail
The server sends a message with the subject line indicating the object and event. The body of the mail note repeats this information and includes the event-comment. A sample message is as follows: Date: Mon, 21 Sep 1998 12:27:40 -0700 From: PXCAdmin Subject: Printjob 123 completed:1 Sender: PXCAdmin Content-Type: text Content-Length: 92
Object: job-identifier=123 Message: job completed Comment: The print job completed on printer root_PP at 12:00
Message
The Event monitor provides the message delivery to the client through pop-up messages. The Event Monitor is an executable program independent of other client applications (job submission, printer information, administration). When installed with the default options, the Event Monitor starts automatically during Windows startup. No windows are visible when events are not received.
9-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10. Configuring, starting and stopping servers
The first step in building a working PrintXchange system is to configure additional servers (spoolers and supervisors). If you do not need additional servers, proceed to the next chapter on “Creating and configuring queues, logical and physical printers.”
Creating and configuring servers
PrintXchange server installation in the NT environment consists of: Creating and initializing the server object database Starting the server Shutting down the server Setting the server attributes.
Creating and initializing the server object database
Server object databases are created through the server installation process and through the Setup PrintXchange tool as described in the “Installing and setting up PrintXchange on a server machine” chapter.
Starting the server
After using the installation of software or the Setup PrintXchange tool to create and initialize the server database, the next step in creating and configuring a server is to start it. On Windows NT systems, a PrintXchange server is intended to behave like an NT service. It is intended to be started up at boot time and does not require user input to be able to start up. Like typical NT services, the server can start up through Control Panel>Services. The server has two modes for startup: Service Control Manager (SCM) mode Console mode (used primarily for debugging).
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-1 CONFIGURING, STARTING AND STOPPING SERVERS
Console mode
Console mode is the command line available to Windows NT via the DOS command line, where administrators may start servers by entering the appropriate command. The syntax for starting a PrintXchange server is as follows: executable_name [-a] [-c] [-e e-mail_address] [-m e-mail_method] [-d server_database_location] [-F] server_name For a complete list of the server startup commands, refer to the “Server startup commands, switches and exit status codes” appendix. While the syntax represents a string that can be typed at a shell prompt, it is expected that, in general, servers will actually be started up by a shell script. The startup syntax will be executed from within the shell script.
Server exit codes
If the server starts up normally (i.e. no errors are encountered), then the server starts servicing client requests and processes those requests as they come in. If the server encounters an error during startup, it prints out an error message to standard error and exits with a non-zero exit status. The specific exit status values are described in the “Troubleshooting” chapter in this guide. Note: To avoid permission problems, the servers should always be run as Administrator on Windows NT.
Server startup process
The server startup process consists of the following: 1. The server does some initial internal processing. 2. The server processes the registry arguments. In SCM mode, the server gets the arguments from the following registry. HKEY_CURRENT_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\service_name\Parameters In console mode, the server gets the arguments from the command line arguments. The server processes the command line arguments according to the standard POSIX command line argument processing rules. Any unrecognized, missing, or incomplete arguments cause the server to print an error message to standard out and the system log and then exit. In console mode, the server does not get the arguments from the registry. Note: The server cannot send any mail to an e-mail address until it has processed the -e switch passed to the server. If an error occurs before the server sees the -e switch, then the error message is only sent to standard error, not to the e-mail address. Once the e-mail address has been processed, then the server sends all error messages to both standard error, system log, and the specified e- mail address.
10-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Note: The startup for the Notification server, spoolers, and supervisors is password protected. When the password of the account that created the servers is changed, you must enter the setup PrintXchange tool to change the password anytime the user account password changes. 3. The server sets the PrintXchange environment variables. The server gets parameters used for the environment variables from the following registry. HKEY_CURRENT_LOCAL_MACHINE\SOFTWARE\Xerox\PrintXchange\CurrentVersion\Environment The registry key names are used as environment variable names. Each registry key value is used as value for the PrintXchange environment variables. For information on environmental variables, refer to the “PrintXchange overview” chapter in this guide. 4. The server locks the object database lock file and opens the object database. There is a lock file associated with each server object database. Whenever a process wants to open an object database, it first tries to lock the database lock file. Only one process at a time is allowed to lock the lock file. Thus, the lock file makes sure that only one process is trying to read from or modify an object database at any given time. If the server cannot acquire the lock file, it delivers an error message and exits. 5. Once the server object database is opened, the server validates certain attributes. For certain configuration attributes, if the attribute does not exist when the server starts up, the server adds the attribute with a default value. Certain configuration attributes represent path names where the server can expect to read or write certain files. The server checks if these path names exist and whether the server has correct access to them. If necessary, the server attempts to create missing path names, if possible. If an attribute's value cannot be defaulted or some path cannot be created, the server delivers an error message and exits. For additional information on configuration attributes, their default values, and how the server processes them, refer to the PrintXchange Command Line Interface Reference Guide 6. The server changes directory to its runtime directory. The runtime directory is specified by the cfg-server-runtime-dir attribute. The runtime directory becomes the server's current directory, and all relative path names are interpreted relative to the runtime directory. 7. After checking the configuration attributes, the server checks the consistency of other attributes on different objects within the database. This consistency checking is essentially a part of crash recovery and is discussed in more detail in the “Troubleshooting” chapter in this guide. The server registers itself with the RPC service and the name service. The server also checks the consistency of the name service entries for user visible objects.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-3 CONFIGURING, STARTING AND STOPPING SERVERS
Note: The PrintXchange Name Service must be running when the server starts or the server startup will fail. 8. Finally, the server goes into a request handling loop, waiting for user requests to arrive and processing them as they come in.
NT server shutdown
Once an NT server is running, there are three ways to shut it down: 1. An administrator can send a pdshutdown command from a client window. 2. An administrator can send a shutdown request (SERVICE_CONTROL_STOP) via Control Panel->Services. Open Control Panel->Services and select a PrintXchange service name you want to shut down. Click the Stop button. 3. The administrator can send a terminate request to the server by using the Windows NT Task Manager. (This method is only available when the server is started with -F switch.)
Setting server attributes
After you have created and initialized the server object database and started the server, the next and final step in creating and configuring servers is to set server attributes. Starting servers sets most server attributes to their default values. You may want to modify some of these attribute values and customize others to tailor PrintXchange for your environment. For information on all PrintXchange attributes, refer to the PrintXchange Command Line Interface Reference Guide. In particular, however, you might want to define: Access Control Lists for security (all elements/objects) Refer to the “Managing security” chapter. Event-notification profiles (all elements/objects) Refer to the “Events” appendix. File transfer method (spoolers and supervisors) Refer to the “Attributes” appendix. Filtering (spoolers and supervisors). Refer to the “Filters” appendix. Job Completion Period (spoolers). Set the spooler default-job-completion-period if users and operators wish to display job information after jobs complete printing.
10-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Preprocessors and PDL guesser
PrintXchange uses preprocessors to effect pre-printing operations on jobs that require document data format translations. The operations may take place before the spooler schedules the job or before the supervisor sends the job to the output device. PrintXchange supports only document-level preprocessing. PrintXchange supports two types of preprocessors: Modification filter. This type of preprocessor performs document data modification without changing the document format. Modification filters are not allowed to change the document attributes based on information extracted from the document data. However, a modification filter may uniformly modify document attributes through use of the attributes-to-set element of the preprocessor-definition attribute. A filter that performs character set translation or simple text formatting belongs to this type. Translation filter. This type of preprocessor translates the document format of the document to a different format. Translation filters are not allowed to change the document attributes based on information extracted from the document data. However, a translation filter may uniformly modify document attributes through use of the attributes-to-set element of the preprocessor-definition attribute. A filter that translates the data format from TIFF to PostScript belongs to this type. Note that after preprocessing has completed, the spooler sets the document’s document-format attribute to the output-format of the last translation filter performed. In PrintXchange both spooler and supervisor support the preprocessors. PrintXchange provides a text-to-PostScript translation filter. It is the customer’s responsibility to create or to obtain other preprocessors. In addition to the preprocessors, PrintXchange Xerox spooler includes a PDL guesser that guesses the document format type of incoming document data.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-5 CONFIGURING, STARTING AND STOPPING SERVERS
Preprocessor-related attributes
Administrators use attributes to access the PrintXchange text-to- PostScript translation filter or a customer-supplied preprocessor. The attributes serve to identify preprocessors, to pass data into a preprocessor, and to indicate when preprocessing should take place. The following attributes apply to preprocessors: preprocessor-definition preprocessor-list excluded-preprocessors no-preprocessing ignore-preprocessing-failure spooler-preprocessor-list supervisor-preprocessor-list.
Preprocessor-definition
This server attribute defines an existing program or library as a preprocessor. The attribute contains the information needed to invoke the program or execute the function of the library. The preprocessor-definition attribute is a complex attribute with the syntax: preprocessor-definition= { name preprocessor-type executable-type command attributes-to-set time-out input-formats output-formats } Table 10-1 describes each of the attribute elements.
10-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Table 10-1. preprocessor-definition attribute fields
Field Name Value Description name text The unique descriptive name within the server by which an administrator references the preprocessor. preprocessor- translation-filter Type of preprocessor. PrintXchange does not support the value type modification-filter prescanner. prescanner executable- executable The type of executable for the preprocessor. In PrintXchange, only type library executable is supported for the modification-filter and translation- filter types. If an unsupported type is indicated for each preprocessor- type, the server rejects the preprocessor definition on validation. command text The name of the preprocessor executable file with applicable flag settings. If the name of the executable does not include an absolute path, PrintXchange adds a default path to generate the absolute path name. The default path name is %PX_ROOT%\bin. The extension of the executable file must be .EXE. The extension cannot be omitted in this file. The preprocessor executable file is a pre-existing translation or modification filter, such that the command options included with the command element correspond to functions already defined as part of the filter. Flags included with the command element but not defined as part of the filter have no effect. attributes-to-set ignoreAttribute Attributes to be set on a document after the preprocessor has completed. If the element has values, the caller of the preprocessor sets the attributes. In the case where several modification and/or translation filters occur in a row on the preprocessor-list, the attributes are not set until after all the filters in the list have been executed. For PrintXchange the attributes-to-set for each filter are set on the document in the order the filtering is performed. For example: preprocessor-list = F1, F2, F3 After the data has been piped through F1, F2, and F3, then the attributes-to-set defined for F1 are applied to the document, followed by the attributes-to-set for F2, then F3. time-out deltaTime A limitation time within which a preprocessing operation must complete. If the operation does NOT complete within the specified time-out, the caller terminates the preprocessor. If it is not indicated or is set to 0, it means that the operation time is not limited. input-formats List of document The document formats the filter supports as input. If the value is formats empty the filter can take any format as input. This element is valid only for modification-filter and translation-filter preprocessors. output-formats Document format The document formats that the filter supports as output. PrintXchange ignores this value for modification filters. For translation filters, one value must always be specified.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-7 CONFIGURING, STARTING AND STOPPING SERVERS
This attribute can be set using the pdset command. For example: pdset -c server -x preprocessor-definition= \ { \ name=text-to-ps \ preprocessor-type=translation-filter \ executable-type=executable \ command=" trn_textps -N\${number-up,0} -O\${content-orientation} \ -a\${top-margin} -b\${bottom-margin} -c\${left-margin} \ -d\${right-margin} -l\${length} -w\${width} \ -P\${number-pages} -t\${repeated-tab-stops}" \ attributes-to-set=‘disable-attribute-mapping=true’ \ time-out=1:00 \ input-formats=simple-text \ output-formats=PostScript \ } \ SupervisorName
Preprocessor-list
This server and printer attribute determines which preprocessors can possibly be invoked on a document. The value of preprocessor-list is an ordered list of preprocessor names to be invoked. The name element in the preprocessor-definition attribute is used as the name value.
Spooler-preprocessor-list
This document attribute determines which preprocessors can possibly be invoked on a document in the spooler. The value of spooler-preprocessor-list is an ordered list of preprocessor names to be invoked. The name element in the preprocessor-definition attribute is used as the name value.
Supervisor-preprocessor-list
This document attribute determines which preprocessors can possibly be invoked on a document in the supervisor. The value of supervisor-preprocessor-list is an ordered list of preprocessor names to be invoked. The name element in the preprocessor- definition attribute is used as the name value.
Excluded-preprocessors
This printer attribute can be used to disallow the use of certain preprocessors on the specified printer. The value of excluded- preprocessors is a list of preprocessor names. The name element in preprocessor-definition attribute is used as the name value. This attribute is ignored if the printer's preprocessor-list has values, or if the document’s spooler-preprocessor-list or supervisor- preprocessor-list has values. It is available only when the server's preprocessor-list is used.
No-preprocessing
This document and printer attribute can be used to disable preprocessing on both the spooler and supervisor.
10-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Ignore-preprocessing-failure
This document and printer attribute can be used as a flag to determine the appropriate action when a preprocessor fails for any reason. In cases of both spooler and supervisor, if the attribute is true and a preprocessor failure occurs then the job continues printing, using the original unpreprocessed document data. In the case of a spooler, if the attribute is false or the attribute is not present and a preprocessor failure occurs, then current-job-state is set to held with a job-state-reasons set to preprint-failed. The data for the offending document is rolled back to the original document data. In the case of a supervisor, if the attribute is false or the attribute is not present and a preprocessor failure occurs, then the job is aborted.
Attribute substitution for executable-type preprocessors
The command path element of the preprocessor-definition attribute contains the command that the server executes to invoke the preprocessor. The command element may also contain preprocessor-defined variables that enable users to pass data into the preprocessor via PrintXchange attribute values. The server replaces the preprocessor variables with the specified attribute values. Depending on how a preprocessor defines its variables, a command option may use a substitution field to specify attribute values for a variable. The syntax for a substitution field is: [prefix]${attribute-name[, default-value[, substitution-expression]]} The items in square brackets are optional. The default-value and substitution-expression can be empty strings. prefix Specifies a prefix for the preprocessor to map the corresponding attribute. PrintXchange recommends to use ‘-‘ and an alphabetical character (e.g. -P, -o, -O) as a prefix. Note: Some non-alphabetical characters (e.g. ‘\’, ‘”’, ‘>’) may cause processing problems for attribute substitution when they are in a prefix. attribute-name Specifies a PrintXchange attribute name. default-value Specifies the default value to be substituted if attribute-name has no value. The default-value is passed to the preprocessor as specified, except for string values. String values must be enclosed in quotes (e.g., “AAA” is passed to the preprocessor as AAA). The backslash character may be used as an escape character (e.g., “abc\”def” is passed to the preprocessor as abc”def). substitution-expression The substitution-expression serves as a means for users to customize the preprocessor options available to them. The expression is passed to the preprocessor as specified, and requires that attribute-name have a value. If attribute-name has no value, the value specified by default-value is passed to the preprocessor.
Example: ${top-margin, , -M${top-margin}, ${left-margin}, ${right- margin}, ${bottom-margin}}
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-9 CONFIGURING, STARTING AND STOPPING SERVERS
If the current values for the attributes are top-margin=4, left- margin=0, right-margin=0, and bottom-margin=4, then what is passed to the preprocessor is -M4,0,0,4. The server makes substitutions for ${...} as follows: Substitute the current value of attribute-name if: attribute-name has a defined value and substitution-expression is not present Example: ${number-up, 0} evaluates to 2 if currently number- up=2. Substitute the specified value of default-value if: attribute-name is not defined and default-value is present Example: ${number-up, 0} evaluates to 0 if number-up is not defined. Substitute the evaluated substitution-expression if: attribute-name has a defined value and substitution-expression is present Example: ${number-pages, -P} evaluates to -P if number-pages is defined. The expression evaluates to a value that is specified in above default-value field if number-pages is not defined. (Note that -P in this example indicates an option already defined for the preprocessor.)
Table 10-2 lists the attributes that can be used in command substitution fields.
Table 10-2. Attributes for command substitution fields
Object Attribute name Syntax and description
Document bottom-margin Integer. Distance, in characters, between bottom edge of page and bottom of text area.
Document copy-count PositiveInteger.
Specifies the number of copies of the document (or selected pages, if supported) to be printed.
Document default-input-tray NameOrOid.
Specifies the input tray that supervisor sets as the default before the document begins printing.
Document document-sequence- Cardinal number
10-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Table 10-2. Attributes for command substitution fields
Object Attribute name Syntax and description
Document finishing Oid
Specifies a finishing-object or sequence of finishing processes to be applied to the document.
Document footer-text Text. The footer line of each page.
Document header-text Text. The header line of each page.
Document left-margin Integer. Distance, in characters, between the left edge of the logical page and left edge of the text area.
Document length Integer. Length, in characters, of the text area.
Document number-pages Boolean. Indicates whether or not to number the pages.
Document output Oid
Identifies the output processing for the media on which the document is to be printed.
Document page-select PageSelect (only positiveInteger type supported; other value types are ignored, i.e. the default-value specified in the substitution field is used)
Specifies one or more sequences of pages to be printed. Space is used as a separator between multiple sequences.
Examples:
-P${page-select} evaluates to –P1:5 if currently page-select =1:5.
-P${page-select} evaluates to –P:5 if currently page-select =:5.
-P${page-select} evaluates to –P1: if currently page-select =1:.
-P${page-select} evaluates to –P1:3 5:7 9:11 if currently page-select ={1:3, 5:7, 9:11}.
Document print-colour-type-used ObjectIdentifier
Identifies the color specified in the document.
Document repeated-tab-stops Integer. Number of characters between tab stops.
Document right-margin Integer. Distance, in characters, between the right edge of the page and the right edge of the text area.
Document sides Sides
Specifies if the job should be printed on one or two sides of the paper.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-11 CONFIGURING, STARTING AND STOPPING SERVERS
Table 10-2. Attributes for command substitution fields
Object Attribute name Syntax and description
Document top-margin Integer. Distance, in characters, between the top of the page and the top of the text area.
Document width Integer. Maximum line width in characters.
Document content-orientation Oid. Portrait or landscape.
Document default-character-set NameOrOid
Document default-font Text
Document default-medium Oid-name or text
Document document-file-name Text
Document document-format Oid. Only the document-format element will be substituted
Document document-name Text
Document fax-resolution Oid
Specifies the resolution mode of the fax.
Document number-up Integer. The OIDs will be converted to their integer values.
Document plex Oid-name. Simplex, duplex, or tumble.
Document x-image-shift Real
Document y-image-shift Real
Job job-copies PositiveInteger.
Indicates the number of copies of the job. This client (pseudo) attribute is part of results-profile.
Job job-finishing Oid
Specifies a finishing-object or sequence of finishing processes to be applied to the job.
Job job-identifier Text
Job job-name Text
Job job-offset Oid
Indicates printer’s supported jogging capability
Job job-originating-host Text
10-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Table 10-2. Attributes for command substitution fields
Object Attribute name Syntax and description
Job job-owner Text
Job output-bin NameOrOid.
Indicates the printer output bin the job is put into. This client (pseudo) attribute is part of results-profile.
Job results-delivery- Text address Indicates the address to deliver job. This client (pseudo) attribute is part of results-profile. In 1.1, this value is supported for only outgoing fax job.
Job results-delivery- NameOrOid. method Indicates the methods for delivering job. This client (pseudo) attribute is part of results-profile. In 1.1, only out-going-fax is supported.
Printer descriptor Text
Printer printer-model Text
Printer printer-name Text
Server server-name Text
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-13 CONFIGURING, STARTING AND STOPPING SERVERS
Executing preprocessors
The rules by which the spooler executes preprocessors are as follows (the same basic algorithm applies for the supervisor; the only difference is that the supervisor uses the physical printer attribute instead of the corresponding logical printer attribute used by the spooler): If no-preprocessing on the document is true, no preprocessors are executed. If spooler-preprocessor-list on the document has a value, for each item on the list perform input/output matching and execute filters if warranted. In the case of the supervisor, supervisor- preprocessor-list is used instead of spooler-preprocessor-list. Example: preprocessor-list=F1, F2, F3, F4, F5 The input/output format matching is: Check if the document-format of the document is included in F1’s input-formats. If the document-format is not an F1 input-format, delete F1 from the list, and perform the same check for each filter in the list until a filter that includes the document format is found on the list. If the document-format is an F1 input-format, check that F1’s output-format is included in F2’s input-formats. If not included in F2, delete F2 and perform the same check for F1 and F3. If the document format is in F2, the caller performs the same check for F2 and F3. After the above operation, check if the last filter’s output- format is included in the specified logical printer’s document- formats-supported attribute or physical printer’s document- formats-ready attribute. If the output-format of the last filter in the list is not included in the printer’s corresponding attribute, the filter is deleted from the list. This operation is repeated until a filter is found whose output-format is included in the corresponding printer’s document formats attribute. If no-preprocessing on the logical printer is true, no preprocessors are executed. If preprocessor-list on the logical printer has values, perform the preprocessors in the list according to the order, except for filters that fail the document format matching. If the preprocessor-list on the logical printer does not have values, get the server’s preprocessor-list. If the server preprocessor-list has values, perform the preprocessors in the list according to the order, except for the preprocessors in the logical printer’s list of excluded-preprocessors and filters that fail the document format matching. If preprocessor-list on the server object has no value, the spooler performs no preprocessing.
10-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
In summary, when a document is submitted to a spooler or supervisor, the servers examine the following attributes in the following order. When I say "use this list" I am implying that we use all physical printers from this list that match the filtering criteria: 1. no-preprocessing (document or initial-value-document attribute): If set, do no preprocessing. If not set, go on to 2a and 2b. 2a. [SPOOLER] spooler-preprocessor-list (document attribute): If set, use this list of preprocessors, except for those that fail document format matching. 2b. [SUPERVISOR] supervisor-preprocessor-list (document attribute): If set, use this list of preprocessors, except for those that fail document format matching. 3. no-preprocessing (logical and physical printer attribute): If set, do no preprocessing. If not set, go on to 4. 4. preprocessor-list (logical and physical printer attribute): If set, use this list of preprocessors, except for those that fail document format matching. 5. preprocessor-list (spooler and supervisor attribute): If set, get excluded-preprocessors from printer; and use this list minus the preprocessors specified as excluded or preprocessors that fail document format matching.
Developing modification and translation filters
PrintXchange supports only modification and translation filters with an executable-type of program. Therefore, users must develop filters as programs. The following paragraphs highlight important aspects of developing a filter.
Data handling
The filter must receive the input data from standard input (stdin) and send the output data to standard output (stdout).
Attribute handling
The filter may need to get some attribute information on the document/job/printer/server objects. The filter can obtain attribute information via the command-line options. Filters are permitted to get attributes, but are not allowed to modify attributes except for the attributes that are set to the attributes-to-set element of preprocessor-definition.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-15 CONFIGURING, STARTING AND STOPPING SERVERS
Error handling
The filter must notify the caller of the success/failure of the filtering operation via the exit code. The following exit codes are defined for filters: FILTER_ NORMAL_COMPLETE: Completed normally FILTER_ERR_ABORTED_BY_CALLER: Caller aborted the operation FILTER_ERR_NO_MEMORY: Not enough memory to continue the operation FILTER_ERR_INVALID_ARGUMENT: Invalid command line argument FILTER_ERR_INVALID_DATA_FORMAT: Invalid input data format FILTER_ERR_SYSTEM_CALL_ERROR: System call error occurred FILTER_ERR_OTHER: Other error occurred
Terminate handling
A filter may require termination when the caller receives a cancel operation. In such cases, the caller terminates the filter. This termination mechanism depends on the operating system.
Restriction
The filter should not create any temporary files as they may not be deleted.
10-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
PrintXchange text-to-PostScript translation filter
The PrintXchange software includes one translation filter. That preprocessor translates simple-text documents to PostScript, and, optionally, performs number-up processing. This filter must be installed using the CLI and is stored during the installation procedure as
pdset -c server -x preprocessor-definition="{ name=text-to-ps preproc-type=translation-filter exec-type=executable input-formats=simple-text output-formats=PostScript command='C|/PrintXchange/bin/trn_textps.exe ${number-up,,-N${number-up}} ${content- orientation,,-O${content-orientation}} ${default-medium,,-S${default-medium}} ${width,,-w\${width}} ${top-margin,,-a${top- margin}} ${bottom-margin,,-b${bottom-margin}} ${left-margin,,-c${left-margin}} ${right- margin,,-d${right-margin}} ${length,,- l${length}} ${number-pages,,-P} ${repeated-tab- stops,,-t${repeated-tab-stops}} '}" MY_supervisor
The rules in the “Attribute substitution for executable-type preprocessors” would be applied in this example to create the following command when a document specifies number-up=2 and width=80 for the PrintXchange translation filter whose executable file name is trn_textps : PrintXchange Directory /bin/trn_textps -N2 -w80 The path to the translation filter executable command "C|/PrintXchange/bin/trn_textps.exe" assumes that PrintXchange was installed on "C:\PrintXchange".
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-17 CONFIGURING, STARTING AND STOPPING SERVERS
The attributes that are not specified in the print request are not represented or replaced with default values, while those that are specified are converted to their substitution equivalents. The text-to-PostScript translator uses 10 pitch, Courier font. It ignores default-font. In addition, if the document’s number-up attribute is either 1, 2, or 4, the filter prints 1 (with margins), 2, or 4 pages per sheet. Note that number-up of 0 or none is valid and suppresses number-up processing. The document attribute, content-orientation, affects number-up processing in the placement of the logical pages on the sheet of paper.
Table 10-3. Command options for the PrintXchange text-to- PostScript translator
Corresponding Option Description Attribute
-a top-margin The number of lines to add to the default margin at the top of the page. Valid values:
Integer >= 0
-b bottom-margin The number of lines to add to the default margin at the bottom of the page. Valid values:
Integer >= 0
-c left-margin The number of characters to add to the default margin at the left side of the page. Valid values:
Integer >= 0
-d right-margin The number of characters to add to the default margin at the right side of the page. Valid values:
Integer >= 0
-l length Lines per page, the number of rows to be printed on a page before a new page is started. Valid values:
integer > 0
-N number-up The number up value that specifies the number of page spots to be printed on the physical sheet. Valid values:
0 1 2 4
10-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CONFIGURING, STARTING AND STOPPING SERVERS
Table 10-3. Command options for the PrintXchange text-to- PostScript translator
Corresponding Option Description Attribute
-O content- Orientation value that specifies whether the page is formatted for long- or short- orientation edge printing: Valid values: landscape portrait
-P number-pages Value that specifies whether page numbers should be printed at the top of the page. This option has no arguments. The default is to not print page numbers.
-Q --- Nowrap, specifies whether lines longer than allowed for the page (either by an explicit -w setting or derived from the sheet size) should be truncated. This option takes no arguments. Its presence specifies truncation. The default is line wrap.
-S default-medium Sheet size for which the translated page should be formatted. Default values for rows and columns are derived, though they can be overridden by the -w and -l options. Valid values:
a b com10 legal 7x9 a0 b4 d letter 9x12_envelope a1 b5 d1_envelope monarch a2 b6 e postcard a3 business_envelope executive 10x13_envelope a4 c folio 10x14 a5 c4_envelope halfletter 11x14 a6 c5_envelope ledger 7_envelope
-t repeated-tab- Tab width value that expands tabs to byte positions number+1, 2*number+1, stops 3*number+1, and so on. The default value of number is 8. Tab characters in the input expand to the appropriate number of spaces to line up with the next tab setting. Valid values:
Integer > 0
-w width Characters per line, the number of columns to be printed on a line before a line wrap or truncation occurs. Valid value:
integer > 0
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 10-19 CONFIGURING, STARTING AND STOPPING SERVERS
PDL guesser
The spooler has one PDL guesser to detect the document format of the document data and set the value of the document-format attribute. Basically, the PDL guesser realized as prescanner and plugged into the system freely. However, it is embedded in the spooler for PrintXchange. When a job is submitted in the spooler, the spooler checks the document-format attribute for all documents in the job before the spooler schedules the job. If any documents have no value for document-format, the spooler calls the PDL guesser for those documents. The PDL guesser can detect the following document formats for PrintXchange: PostScript Simple Text (JIS, SJIS, EUC, ASCII) TIFF ART IV HP/GL family (HP/GL, HP/GL2, MGL) ESC/P PCL WPL. The PDL guesser uses 2048 bytes from the top of the document data to detect the format. If it can detect the document format, it sets the result in the document-format attribute for the document. The PDL guesser attempts to guess the PDL only. It does not attempt to determine if the document is a valid master of the PDL it has guessed. If the PDL guesser cannot detect the format, it sets the document- format to the value of the attribute default-document-format. If the PDL guesser can not detect the document format and default- document-format has no value, the document-format attribute remains blank. An Administrator is responsible for setting the default-document-format attribute.
10-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11. Creating, configuring and enabling queues, physical and logical printers
Once you have configured and started additional servers (spoolers and supervisors), you can then create, configure, and enable the remaining PrintXchange objects: Queues Logical printers Physical printers. Note: Spoolers and supervisors must be enabled before you can create objects.
Creating queues
The next step in building a working PrintXchange system is to create and configure queues. Queues are spooler objects, so you must have already created your spooler before creating and configuring its queues. This section deals with creating and configuring queues and covers: Creating queues Setting queue attributes. Note: You can use the PrintXchange Administrator Tool or CLI to create queues. Refer to the GUI online help for details on using the Admin Tool. Use the pdcreate command to create queues. The syntax is: pdcreate -c queue [spooler_name:]queue_name You must issue this command to create each uniquely-named queue in your PrintXchange system. The create operation fails if an object exists with the name you specify for the queue. When you create a queue, its spooler: Registers the queue with the name service Initializes the queue to the disabled state (you will enable all of your PrintXchange components in the "Enabling and testing your PrintXchange system" section). Adds the name of the queue to its queues-supported attribute. The following example creates a queue named queue1 on the spooler named spooler1: pdcreate -c queue spooler1:queue1 You can also use the [-X attribute_filename] syntax when creating queues. For more information, refer to the PrintXchange Command Line Interface Reference Guide.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-1 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting queue attributes
There are three attributes you might want to set to customize queues for your environment: 1. notification-profile (Refer to the “Creating and Configuring Servers” section, under “Defining Event Notification Profiles.”) 2. message (Refer to the PrintXchange Command Line Interface Reference Guide.) 3. descriptor (Refer to the PrintXchange Command Line Interface Reference Guide.). After creating and configuring queues, you can create and configure physical printers. In the “Planning a PrintXchange Installation” chapter, you determined how many physical printers you needed, what the physical-printer- queue associations are, and which .paf files you need. In addition, you created and customized queues by setting queue attributes.
11-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Creating and configuring physical printers
The next step in building a working PrintXchange system is to create and configure physical printers. Physical printers are supervisor objects, so you must have already created your supervisors before creating and configuring their physical printers. This section deals with creating and configuring physical printers and covers: Setting required physical printer attributes for Reference Supervisor printers Setting required physical printer attributes for Xerox Supervisor printers Creating physical printers Setting optional physical printer attributes. Note: You can use the PrintXchange Administrator Tool or CLI to create physical printers. Refer to the GUI online help for details on using the Admin Tool.
Setting required physical printer attributes (for Reference Supervisor)
A supervisor must have connectivity information about its printers to communicate with them. The printer connectivity attributes are: printer-address printer-connection-method printer-connection-level (automatically set by the printer’s attribute file) Serial parameter attributes printer-baud-rate printer-data-bits printer-stop-bits printer-input-flow-control printer-output-flow-control printer-parity printer-tcpip-port-number. The following sections explain how to set these attributes.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-3 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting the printer address
The supervisor must have a unique address for each printer. This address is obtained from the printer-address attribute. Table 11-2 lists the general forms of the printer-address attribute that the supervisor recognizes. The forms include a null, serial, parallel, or IP network socket connection. IP network socket ports may be simple node names with or without dotted domain syntax and with or without port numbers. The attribute printer-tcpip-port- number specifies the port number the supervisor uses when connecting to a printer on an ip-socket connection. The default port number is obtained from the printer’s PAF. If you specify the port number as part of the printer-address, that port number overrides the printer-tcpip-port-number attribute. The syntax for printer- address is text; however, the port number is a decimal integer. The next table indicates legal values for the printer-tcpip-port-number attribute.
Table 11-1. Printer-tcpip-port-number values
Attribute Legal Values Default printer-tcpip-port- 1024 through 65535 9100 number
Table 11-2. General forms of the printer-address attribute
Form Description NUL: Null device for testing only. This form of the printer-address (case insensitive) attribute requires that attribute printer-connection-level=1. LPT
11-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Note: If the printer-address specified ends with a “:”, but does not mathch the COM, LPT, or NUL form, the printer creation fails with an invalid argument error. If the syntax does not end in a “:”, the system assumes a host name or IP address was entered and the supervisor sets the printer-connection-method=ip-socket. If the address is invalid, the printer enable operation will fail.
Setting the printer-connection-method
You can attach printers to supervisor hosts in several ways. Desktop and mid-range printers typically have one or more connectors on the back that allow you to connect them to their source of data such as a host, terminal server, or network. This connector, along with the hardware it connects to, is the printer's interconnect. Printer-connection-method attribute A printer’s connection method is the way in which the server process can communicate with the printer. The printer-connection-method attribute specifies the appropriate connection method. The following object identifiers enumerate the supported set of connection methods: serial parallel ip-socket digital-printserver. The reference supervisor can support printers of all above connection methods simultaneously. You do not have to create a new supervisor to support a printer whose connection method is different.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-5 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting serial parameter attributes
When connecting a printer to a serial port, you are required to specify the serial parameter attributes in the next table. If you do not specify a value for the attribute printer-baud-rate, PrintXchange assumes that you have already set up the port.
Table 11-3. Serial parameter attributes
Attribute Legal values Value if attribute is initially empty printer-baud-rate 300, 1200, 2400, none 4800, 9600, 19200, 38400 printer-data-bits 5, 6, 7, 8 8 printer-stop-bits 0, 1, 2 1 printer-input-flow- none xoff control xoff cts dtr printer-output-flow- none xoff control xoff cts dtr printer-parity none none even odd mark space
11-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting required physical printer attributes (for Xerox Supervisor)
A supervisor must have connectivity information about its printers to communicate with them. The Xerox Supervisor uses RFC 1179 lpr protocol to submit jobs to the printers. When available, lprm is used to cancel jobs and lpq is used to obtain job status. Depending on the printer’s capabilities, SNMP and Xerox Production Printer statusing methods can be utilized for device and job status. Most of these attributes are specified in the printer’s PAF file and should not be modified. The printer connectivity attributes that can be modified are: printer-address device-query-channel-ready job-query-channel-ready job-cancel-channel-ready device-query-interval job-query-interval.
Setting the printer address
The supervisor must have a unique address for each printer. This address is obtained from the printer-address attribute. The printer- address format for lpr is: hostname,RemotePrinterName For example, the Xerox DocuPrint 4850 is driven by a host named ARIZONA and the printer queue name is PUMA. Therefore, the printer-address is “ARIZONA,PUMA”. Alternatively, if you have the IP address of the printer, then the printer-address is “13.240.3.16,PUMA”
Table 11-4 lists the hostname general forms of the printer-address attribute that the supervisor recognizes.
Table 11-4. General forms of the printer-address attribute
hostname Form Description name Host name without domain Example: foobar name.abc.def.hij Host name with domain Example: topper.mro1.dec.com nnn.nnn.nnn.nnn Numeric IP address Example: 16.34.144.119:9100
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-7 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting the xxx-channel-ready attributes
The applicable channel-ready attributes are located within the printer’s PAF file. The channel-ready attributes default to enabled within the PAF.
Setting the xxx-query-interval attributes
The applicable query-interval attributes are located within the printer’s PAF file. Each has a default value that determines how often the supervisor queries the printer for status.
Creating physical printers
Use the pdcreate command to create physical printers. The syntax is: pdcreate -c printer [-x extendedattributes_string ... ] [supervisor_name:]physical_printername Creating a physical printer: Creates a physical printer object in a supervisor. Registers the name of the physical printer with the name service. Causes the supervisor to update its physical-printers- supported attribute. Initializes the physical printer to the disabled state (you will enable all of your PrintXchange components in the “Enabling and testing your PrintXchange system” section of this chapter.) The queue that you associate with the new physical printer must already exist. If you specify a nonexistent queue, the command fails. Note: There are PAF creation and validation assistance tools (pdppd2paf and pdpafcheck) available if the new printer supports the PostScript PDL and you have the PostScript Printer Definition (PPD) file for that printer,. These tools are located under the bin/pdtools directory on the system where a supervisor server is installed. Please note that these tools are not officially supported and may be unavailable in the future. Example: The physical printer represents an lpr network-connected Hewlett- Packard 5SI, and feeds from the queue named q1: pdcreate -c printer -x “printer- address=123.4.5.6,PUMA” -x “associated-queue=q1” -X /usr/pd/share/cap/hp_laserjet5si_lpr.pafChicago_ xsup:pp1
11-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Setting optional physical printer attributes
You can set many optional physical printer attributes depending on the capabilities of the printers in your network. These attributes enable features such as duplex printing, separator pages, number up, and landscape printing. Some of these attributes are: job-sheets-supported job-sheets-ready document-sheets-ready sides-supported sides-ready plexes-supported content-orientations-supported. For a complete list of optional physical printer attributes, refer to the PrintXchange Command Line Interface Reference Guide. Use the pdset command to set these optional attributes. The syntax is: pdset [-x extended attribute_string ... ] physical_printer_name The following example specifies landscape and portrait printing on the PostScript physical printer named pp1: pdset -x “content-orientations- supported=landscape portrait” pp1
Setting load balancing attributes
Load balancing occurs when two or more physical printers are associated with a single queue. Sharing the load of print jobs over multiple printers ensures that printers are not under or over utilized. Whether using the Xerox or Reference supervisor, a round-robin scheme is used to determine the next available printer ready to accept a job. For the Xerox supervisor, additional criteria based on the max-concurrent-job-processing value is used to determine when a printer is ready to accept a job. In general, high speed printers have their own hard disk storage for jobs received from the host. Ensuring a steady stream of jobs to the printer will minimize printer cycle downs. The throughput of jobs to the printer can be maximized by setting an appropriate value for the max-concurrent-job-processing attribute of the physical printer. For a detailed explanation on the max-concurrent-job-processing attribute, refer to the “Attributes appendix” in the Command Line Interface Reference Guide.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-9 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Creating and configuring logical printers
The next step in building a working PrintXchange system is to create and configure logical printers. Before doing this, you must have already created and configured your servers and queues, as well as your physical printers. This section covers: Creating document and job defaults Creating logical printers Specifying the printer driver for a logical printer Defining event-notification profiles. Note: You can use the PrintXchange Administrator Tool or CLI to create logical printers. Refer to the GUI online help for details on using the Admin Tool.
Creating document and job defaults
PrintXchange offers two options for determining document and job defaults: You can apply defaults to each logical printer so that every document and job reflects those defaults. You can allow end users to apply defaults to their own documents and jobs, along with the print request. Whether you use the first or second method, or a combination of the two, you must create the document and job defaults as spooler objects. Then you can either apply them to logical printers or allow end users to apply them when they submit the print request.
Setting document and job defaults
To set document and job defaults at the logical printer level, you must do the following: 1. Locate the appropriate spooler. 2. Create the initial-value-document and/or initial-value-job objects on the spooler. The spooler then adds the names of the initial-value-document and initial-value-job objects to its server object database. 3. Create the logical printer to which you want to apply the initial- value-document and/or initial-value-job defaults. Note: You can use the PrintXchange Administrator Tool to create an initial value job and initial value document as part of the logical printer creation process. Refer to the GUI online help for details on using the Admin Tool. Provided they have proper access rights, end users can override logical printer level defaults with document and job defaults they apply with print requests.
11-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Using the pdcreate command
Use the pdcreate command to create initial-value-document and initial-value-job objects. The syntax is: pdcreate -c initial-value-document [-x extended_attribute_string] [spooler_name:]iv_doc_name or pdcreate -c initial-value-job [-x extended_attribute_string] [spooler_name:]iv_job_name You must issue this command to create each document or job default. The create operation fails if an object exists with the name you specify for the initial-value-document or initial-value-job object. Note: You can put all defaults in one initial-value-job or one initial- value-document. The following example creates an initial-value-document object named ivd_2sided that specifies two-sided printing on the spooler named main: pdcreate -c intial-value-document -x “sides=2” main:ivd_2sided This example assumes that you have at least one physical printer that supports two-sided printing. The following example creates an initial-value-job object named ivj_retain that specifies a retention period of 24 hours on the spooler named main: pdcreate -c initial-value-job -x “job-retention-period=24:00:00” main:ivj_retain Note: You can put all attributes in just one initial-value-job or initial- value-document. In the next section, Creating logical printers, you will apply initial- value-document and initial-value-job objects to logical printers by specifying the printer-initial-value-document and printer-initial- value-job attributes. You can also use the [-X attribute_filename] syntax when creating initial-value-document and initial-value-job objects. For more information, refer to the PrintXchange Command Line Interface Reference Guide.
Creating logical printers
After you have created the initial-value-document and initial-value-job objects that define document and job defaults, you are ready to create the logical printers for your PrintXchange system. Use the pdcreate command to create logical printers. The syntax is: pdcreate -c printer [-x extended_attribute_string] [spooler_name:]logical_printer_name You must issue this command to create each uniquely-named logical printer in your PrintXchange system. The create operation fails if an object exists with the name you specify for the logical printer.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-11 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Supported attributes for the logical printer
In creating logical printers, you should specify the associated queue for the logical printer. This queue should already have associations to one or more physical printers. When you invoke the create operation for the logical printer, the spooler determines the supported attributes for the logical printer by merging supported attributes of all physical printers associated with the specified queue. The spooler automatically sets the supported attributes on the logical printer only during the logical printer creation. If you add a physical printer association to the specified queue after creating the logical printer, be sure that the supported attributes for the logical printer and the new physical printer coincide, by doing either one of the following: Manually set the physical printer’s supported attributes on the logical printer. Create a new logical printer associated with the same queue. This printer now includes the supported attributes of all the queue’s associated physical printers, including the new physical printer. When you create a logical printer, its spooler: Registers the logical printer with the name service Initializes the logical printer to the disabled state (you will read about enabling all of your PrintXchange components in the next section, “Enabling and Testing Your PrintXchange System”). Adds the name of the logical printer to its logical-printers- supported attribute.
Example of a logical printer
The following example: Creates a logical printer named logical_twosided on a spooler named main Specifies a queue named q_twosided as the associated queue Sets a default job priority of 40 Applies the initial-value-document object named ivd_2sided from the earlier example Applies the initial-value-job object named ivj_retain from the earlier example: pdcreate -c printer -x “associated- queue=q_twosided” -x “max-user-job-priority=40” -x “printer-initial-value-document=ivd_2sided” - x “printer-initial-value-job=ivj_retain” main:logical_twosided
As you create logical printers, remember that PrintXchange does not maintain the synchronization of xxx-supported and xxx-ready attributes between logical and physical printers. You must do this yourself by ensuring that you have abstracted printers’ capabilities correctly to create logical printers and that you are using queues to connect logical and physical printers correctly.
11-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
You can also use the [-X attribute_filename] syntax when creating logical printers. For more information, refer to the PrintXchange Command Line Interface Reference Guide.
Specifying the printer driver for a logical printer
To ensure that users load the appropriate printer driver for PrintXchange printers, PrintXchange includes a feature that enables administrators to customize the driver installation process on the user's machine when the logical printer is added to the user's desktop via the Microsoft Control Panel Add Printers icon.
The administrator may choose either of the following processes for installing printer drivers for PrintXchange logical printers: 1. remote download of drivers on a Windows NT 4.0 system to the client systems 2. local media loading of drivers to the client systems (driver name pre-determined) 3. local media loading of driver to the client system (driver name determined by user)
Remote download of drivers to the client systems
For each spooler, a default driver server can be specified as the primary host where the printer drivers reside. This value is specified via the CLI driver-server attribute for a spooler or via the GUI driver server button in the spooler properties window. Using the GUI, the administrator can enter the logical printer properties and click the Preferred Printer Drivers button. Set the driver for autoload, then select the appropriate driver from the list of all existing Windows NT and Windows 95 drivers on the driver server. If a particular driver does not exist on the host specified for the Spooler driver server, a different driver server name specified for this specific logical printer can be set in the Preferred Printer Drivers screen. Note: If all drivers are moved from one server to another, changing the spooler driver server has no effect on existing logical printers with preferred drivers set. To change the location where PrintXchange looks for these drivers, the administrator must re-enter the preferred drivers screen for each logical printer and reselect the driver names.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-13 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Using CLI in a script program, all preferred driver values for the specific driver must be determined by the administrator. The CLI command to download the Windows NT 4.0 Docutech PostScript level 2 driver for the logical printer named DocutechPS_lp is as follows as one line: pdset -c printer -x preferred-printer- drivers={name="Xerox DocuTech 90 PS2"version=2 environment=winntx86 driver-path=\\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\PSCRIPT.DLL data-file=\\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\XRDT0904.PPD config-file=\\\\\\\\PXC- NT\\print$\\\\W32X86\\\\2\\\\PSCRPTUI.DLL help-file=\\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\PSCRIPT.HLP dependent-files=\\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\XRDT0904.PPD \\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\PSCRIPT.DLL \\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\PSCRPTUI.DLL \\\\\\\\PXC- NT\\\\print$\\\\W32X86\\\\2\\\\PSCRIPT.HLP} DocutechPS_lp It is best to place the entire preferred-printer-drivers portion of the command into an attribute file and have the pdset command access the attribute file. For example, place the attribute in the file called ppd.x in the directory path c:/path and use the following command to enable downloading of the driver to the client system: pdset -c printer -X c:/path/ppd.x DocutechPS_lp To create additional logical printers with the same attributes (including the printer driver specification), the copy-from attribute can be used in the pdcreate command. For an example of the pdcreate command, refer to the PrintXchange Command Line Interface. Note: If PrintXchange clients are unable to copy print drivers from the driver server, ensure that at least one shared NT local printer has been created on the driver server host. Download of printer drivers to PrintXchange clients relies on existence of the system share Print$ on the driver server. This share is not created by Windows NT until a local printer has been shared upon the workstation. If this share does not exist on the driver server, all client attempts to retrieve printer drivers will fail.
11-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Local media loading of drivers to the client systems (driver name pre-determined)
Note: The driver-server attribute is not applicable for this process. Using the GUI, the administrator can enter the logical printer properties and click the Preferred Printer Drivers button then manually enter the name of the driver the user should load via local media. Note: the name must be entered precisely as shown in the driver list, including any spaces between words. Using CLI, the driver name, environment and version should be specified. The CLI command to require the user to load the Windows NT 4.0 Docutech PostScript level 2 driver for the logical printer named DocutechPS_lp is as follows in one line: pdset -c printer -x preferred-printer- drivers={name="Xerox DocuTech 90 PS2" version=2 environment=winntx86} DocutechPS_lp For Windows NT 4.0, environment = winntx86 version = 2 For Windows 95, environment = win40 version = 0
Local media loading of driver to the client system (driver name determined by user)
This option requires no setup by the administrator. When the user creates the logical printer on their desktop, they load the driver they deem to be appropriate.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-15 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Enabling and testing your PrintXchange system
After you have created and configured servers, queues, physical printers, and logical printers, the next and final step in building a working PrintXchange system is to enable these components. After enabling your PrintXchange system, you should test it by submitting documents and jobs to print. This section explains how to enable PrintXchange components and covers: Using the pdenable command Enabling spoolers Enabling supervisors Enabling queues Enabling physical printers Enabling logical printers Testing your PrintXchange system. Notes: Spoolers and supervisors must be enabled before you can create objects. You can use the PrintXchange Administrator Tool to enable queues, physical printers and logical printers. Refer to the GUI online help for details on using the Admin Tool.
Using the pdenable command
For your PrintXchange system to work properly, you must enable the PrintXchange components in the order they appear in this chapter. To do this, use the pdenable command with the following syntax: pdenable [-c class_name] object_instance where: class_name object_instance server spooler_name server supervisor_name queue queue_name printer physical_printer_name printer (default) logical_printer_name You must issue this command to enable each of your PrintXchange components. For details on all PrintXchange commands, refer to the PrintXchange Command Line Interface Reference Guide.
11-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Enabling spoolers
Enabling a spooler allows it to accept print requests submitted by end users to the spooler’s logical printers, after you enable the logical printers. The following example enables a spooler named MACHINENAME_spl: pdenable -c server MACHINENAME_spl Note: You can use the PrintXchange Administrator Tool to enable a spooler. Refer to the GUI online help for details on using the Admin Tool.
Enabling supervisors
Enabling a supervisor allows it to accept print jobs for its physical printers, after you enable the physical printers. The following example enables a supervisor named MACHINENAME_sup1: pdenable -c server MACHINENAME_sup1 Note: You can use the PrintXchange Administrator Tool to enable a supervisor. Refer to the GUI online help for details on using the Admin Tool.
Enabling queues
Enabling a queue allows its spooler to accept print requests after you enable the spooler’s logical printers. The following example enables a queue named q1: pdenable -c queue q1
Enabling physical printers
Enabling a physical printer allows its supervisor to send it print jobs. Before you can enable a physical printer, the following must be true: The value of the physical printer attribute associate-queue must be the name of an existing queue. If a supervisor controls the physical printer, the printer-address attribute must have a legal value. The spooler that supports the physical printer’s supervisor must be running. When you enable a physical printer: Its supervisor adds the name of the physical printer to its physical-printers-ready attribute. The spooler supporting its supervisor adds the name of the physical printer to the physical-printers-ready attribute for the spooler and associated queue. The following example enables a physical printer named physical_2sided: pdenable -c printer physical_2sided
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 11-17 CREATING, CONFIGURING AND ENABLING QUEUES, PHYSICAL AND LOGICAL PRINTERS
Enabling logical printers
Enabling a logical printer allows its spooler to accept new print requests submitted by end users to that logical printer. Before you can enable a logical printer, the value of the logical printer attribute associate-queue must be the name of an existing queue. When you enable a logical printer, its spooler: Adds the name of the logical printer to the logical-printers- ready attribute for the spooler and associated queue. Adds the name of the logical printer to the printers-ready attribute for all associated physical printers. The following example enables a logical printer named logical_2sided: pdenable -c printer logical_2sided
Testing your PrintXchange system
Once you enable your PrintXchange system, you should perform the following tests: 1. Send at least two documents and jobs to print on all of the printers in your network: one using logical-printer-level defaults and one specifying defaults with the print request. 2. Print a document that invokes a filter, if applicable. 3. Verify the event notification, if applicable. 4. Verify the printed document or job. After enabling your system, test it by submitting documents and jobs to print. At this point, you have completed the installation and configuration of your PrintXchange system. You can now move on to managing the operations of your system.
11-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12. Using the CLI and GUI
PrintXchange supports three clients: CLI, GUI, and inbound gateways. The CLI and GUI clients will initiate more of the operation requests to the PrintXchange system than the inbound gateway clients. The CLI provides access to all of the PrintXchange functionality. The GUI provides the same functionality. However, the GUI does not allow you to set and modify some object attributes. This chapter provides only a high-level overview of the Command Line Interface (CLI) and Graphical User Interface (GUI). For detailed information on CLI, refer to the PrintXchange Command Line Interface Reference Guide. For additional information on GUI, refer to the Administration Tool.
Command Line Interface (CLI)
The PrintXchange Command Line Interface (CLI) is a set of the following seventeen commands that you enter at the Windows NT command prompt: pdaccount pdclean pdcreate pddelete pddisable pdenable pdls pdmod pdpause pdpr pdpromote pdq pdresubmit pdresume pdrm pdset pdshutdown For detailed information on each of these commands, refer to the PrintXchange Command Line Interface Reference Guide.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-1 USING THE CLI AND GUI
The CLI represents the full suite of PrintXchange functionality and is primarily an interface for system administrators and operators. Although all users have access to the CLI, their privilege level determines what they can do with it. For the minimum privilege level required for each command, refer to the “Authorization” section in the “Managing security” chapter.
Environment variables
PrintXchange commands use a subset of the environment variables to derive defaults. For a list with descriptions of environment variables for localization and for CLI refer to the Environment variables table in the “PrintXchange overview” chapter.
PDPRINTER and PDDOMAIN environment variables
The purpose of the PDPRINTER and PDDOMAIN environment variables is to enable the CLI user to type less information when using commands that require the printer name and the domain name. In general, the domain the user is submitting jobs to is the domain the user is currently logged into. If the PDDOMAIN variable is not set, CLI uses the domain the user is logged onto as the default domain. In the following examples, racehorse is a logical printer, ess.mc.xerox.com is a UNIX NIS domain, and USAES is an NT domain. pdpr -p racehorse -x domain- name=nis:ess.mc.xerox.com /etc/hosts pdq -p racehorse -x domain-name=USAES By setting the PDPRINTER and PDDOMAIN environment variables, these commands can be shortened to: pdpr /etc/hosts pdq The variables can be set either globally or temporarily. Setting the PDDOMAIN environment variable globally is primarily useful for NT CLI users that submit jobs only to the UNIX network, or NT CLI administrators and operators that only issue commands to UNIX network PrintXchange servers. If the PDDOMAIN variable is set globally, this value is used for the domain-name attribute of every CLI command. Setting the PDPRINTER environment variable globally is always recommended.
Setting the variables temporarily in a shell for Windows NT 4.0 and Windows 95
To set the variables temporarily in the shell for Windows NT 4.0 and Windows 95 you must do the following: bash shell PDPRINTER=racehorse export PDPRINTER PDDOMAIN=nis:ess.mc.xerox.com export PDDOMAIN MS-DOS shell set PDPRINTER=racehorse set PDDOMAIN=nis:ess.mc.xerox.com
Note: The prefix nis: precedes the domain name because ess.mc.xerox.com is a UNIX NIS domain. If setting the PDDOMAIN value for the USAES NT domain, only the domain name is specified.
12-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT USING THE CLI AND GUI
Setting the variables globally for Windows NT
The procedure for globally setting PDDOMAIN and PDPRINTER environment variables for Windows NT is: 1. Double-click the System icon in the control panel. 2. Select the Environment tab. 3. Select any variable in the System Variables window. 4. At the Variable field, replace the name shown with the new variable name (PDPRINTER or PDDOMAIN). 5. If setting the PDPRINTER variable, At the Value field, replace the value shown with the default logical printer name. If setting the PDDOMAIN variable, At the Value field, replace the value shown with the name of the domain where the logical printer resides. Note: If using printers in a UNIX environment, the domain name must be prefixed by nis: Examples: The following is an example for setting up a Windows NT 4.0 client for CLI printing with the default logical printer named racehorse in the UNIX NIS: domain ess.mc.xerox.com: PDPRINTER racehorse PDDOMAIN nis:ess.mc.xerox.com The following is an example for setting up a Windows NT 4.0 client for CLI printing with the default logical printer named racehorse in the NT domain USAES: PDPRINTER racehorse PDDOMAIN USAES 6. Select the Set button. The variable and its value will appear in the System Variables list. 7. Select the OK button. 8. Reboot the system for the variables to go into effect.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-3 USING THE CLI AND GUI
Setting the variables globally and Windows 95
The procedure for globally setting PDDOMAIN and PDPRINTER environment variables for Windows95 is: Add the following lines to the autoexec.bat: set PDPRINTER=
CLI syntax
Figure 12-1 shows the syntax for all PrintXchange commands.
Figure 12-1. CLI syntax
Command Option argument
command_name [-a] [-b option argument] [object_instance . . .]
Options Operand
The four syntax elements are: Command Options Option argument Operand. For more information on CLI syntax, refer to the PrintXchange Command Line Interface Reference Guide.
12-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT USING THE CLI AND GUI
Summary of command options
Table 12-1 summarizes the options you can use with the CLI commands. For detailed information on all the commands and their options, refer to the PrintXchange Command Line Interface Reference Guide.
Table 12-1. CLI command option summary
Option Command Description
-c class_name pdclean pdpause Identifies the object class. pdcreate pdresubmit pddelete pdresume pddisable pdset pdenable pdshutdown pdls
-f filename pdpr Identifies the file as a document in a print job.
-f filter text pdls pdq Specifies the selection criteria for object_instances.
-F pdls pdq Turns off all filtering. This option takes precedence over the -f filter text option.
-g pdcreate pdpr Turns off column headings on output of requested pdls pdq attributes that you specify with the -r option. pdmod pdset
-h All Provides information on using the command.
-m message_text pdclean pdpause Attaches a human-readable message to the object. pdcreate pdpromote pddelete pdresume pddisable pdrm pdenable pdset pdmod pdshutdown
-n copies pdmod pdpr Specifies the number of copies to print.
-N notification_method pdmod pdpr Specifies the method by which a user wishes to be notified of events that occur during processing.
-p printer_name pdpr pdq Specifies the printer.
-r requested_attributes pdcreate pdpr Specifies the group of attributes that the command pdls pdq writes to standard output. pdmod pdset
-r retention_period pdrm Specifies the amount of time a server should keep a job in the retained state before deleting the job.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-5 USING THE CLI AND GUI
Table 12-1. CLI command option summary (continued)
Option Command Description
-s style_name pdcreate pdpr Determines the format of standard output. pdls pdq pdmod pdset
-t job_name pdmod pdpr Specifies a new name.
-w when_time pdshutdown Specifies how much processing can occur before a server shuts down.
-x extended-attributes- All Identifies one or more attribute=value pairs. string
-X attribute_filename All Identifies one or more files containing attribute=value pairs.
12-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT USING THE CLI AND GUI
Graphical user interface
The graphical user interface (GUI) client consists of applications that execute on the user’s client Windows NT or Windows 95 PC system. There are four GUI client applications: Print job submission and job control Printer information Administration Event monitor.
Print job submission and job control
This application gives users the ability to use the standard Microsoft Windows 95 and NT printing interface with a PrintXchange print server. The application allows users to: Print jobs View job status Cancel jobs Pause jobs Resume jobs Set job attributes (that do not affect document formatting) prior to job submission Receive notification events about jobs View printer properties.
Printer information
This application runs on a Windows NT or Windows 95 system. It operates with a PrintXchange server. The application allows users or operators access to information about the jobs and logical printers currently in the system. Users can also modify attributes of submitted jobs. More specifically, this application allows users to: List all available printers in the local domain, or in the specified domain Obtain the current capabilities, status, and supported functionality of the specified logical printer List information with the ability to filter the information Pause, resume, promote, resubmit, cancel, enable, and disable the specified job or printer if the user has the appropriate authorization Customize the information display Modify a previously submitted job.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-7 USING THE CLI AND GUI
Administration
This application runs on a Windows NT or Windows 95 system. It operates with a PrintXchange server. The application allows administrators to perform server and printer administration tasks: List all available spoolers, supervisors, queues, logical printers, physical printers, etc. in the local domain, or in the specified domain Obtain and modify attributes of system objects Create and delete system objects Access objects directly or indirectly through other objects Add and delete users to the system and set their privilege level Add and delete default event notifications for each object in the system Perform all operations available through the Printer Information application.
Event Monitor
The Event Monitor provides the message delivery to the client through pop-up window messages. When installed with the default options, the Event Monitor starts automatically during Windows startup. No windows are visible when events are not received. On Windows NT and Windows 95, the Event Monitor is installed in the StartUp folder. Users who want to disable the Event Monitor take the Event Monitor icon out of the StartUp folder and reboot. To display events through the Event Monitor, the notification-profile attribute element delivery-method must be set to socket-event, and the element delivery-address set to the host name or the IP address of the client. The Event Monitor displays the events listed via the notification-profile attribute. When the client receives an event, the Event Monitor displays a pop- up message window notifying the user of the event.
12-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT USING THE CLI AND GUI
Table 12-2. Event Monitor pop-up window description
Attribute
Title Widget User Action GUI Behavior Name Default Range/Value Type s
Event Type events- No default --- supported value i Icon --- Displays report- or state-changed- events.
! Icon --- Displays warning- events. STOP Icon --- Displays aborted- and error- events.
Event Text --- Display the event ------Message (read only) message text. (See description below.)
OK Button Select Closes the Event ------button. Monitor pop-up window.
Event message components
The message window contains a message field and an OK button. The message window closes when the user selects the OK button. If the client receives additional events before the window closes, the Event Monitor spools them in the underlying infrastructure and displays them one at a time. Each event message has the following syntax:
Table 12-3. Event message components
Component Description Example
object id The object identifier of the object where the event “SELENE_lp:15” occurred.
message The description of the event. The message may “The print job include other information, such as the time and completed on hp_pp at state. 9:52”
comment The text specified in the comment field of the notification-profile attribute.
warning message A warning-resource-needs-attention message. The warning message displays only if the server provides it.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-9 USING THE CLI AND GUI
Manually starting and stopping Event Monitor
Users can manually start and stop the Event Monitor via the PrintXchange Event Monitor Control window. To manually start or stop the Event Monitor: 1. Select Start>Settings>Control Panel. 2. Select the PrintXchange Event Monitor Control icon. The system displays the PrintXchange Event Monitor Control window (). 3. Select the Start Monitor or Stop Monitor button, as applicable. Only one button is active at a time depending on the current state of the monitor. 4. Select the Close button.
Event messages
Users can specify events by class or by specific events. If the notification-profile attribute specifies a class, the corresponding notification service reports all events of that class. For a list of events, their classes, the objects to which they apply, and the corresponding messages that are supported in PrintXchange, refer to the chapter on “Setting event notification”.
12-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT USING THE CLI AND GUI
General window description
This section describes the primary elements of the Windows NT and Windows 95 PrintXchange GUI that will make it easier to understand the subsequent discussions on the GUI client applications. Figure 12-2 illustrates the primary elements of GUI windows. Figure 12-2. General window features
Menu bar Left pane Tool bar Right pane selector box icons selector box Right pane
Left pane Description Message text box Object icon window
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 12-11 USING THE CLI AND GUI
Left/right pane selector boxes identify the application tool and, as applicable, the currently opened object name. Menu bar lists menus as applicable for a given window. To select a menu option: Select a menu or press ALT+underscored character of the menu label. The GUI displays a list of menu options. Grayed out options are not selectable. Select a menu option. The GUI invokes the selected command option. Tool bar icons provide short cuts for invoking commands otherwise invoked via menu options or window elements (such as command buttons). To use the tool bar: Select an icon. The GUI invokes the selected command option. Combo boxes allow the user to choose various objects and information about those objects to be displayed in the panes displayed under the combo boxes. Details boxes provide detailed information pertaining to the selected display panes. Display panes display information pertaining to the selected combo boxes. Object icons indicate the current state of an object. To use object icons: Select an icon. The GUI activates the selected menu for the selected object icon. Open an icon. The GUI displays the properties window for the corresponding object. Description window displays messages related to objects on the active window Message window displays read-only event notifications and messages related to objects on the active window In all cases, the term select means to point at an object with the mouse cursor and click the left mouse button once. The term open means to point at an object with the mouse cursor and do a quick double click with the left mouse button.
12-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 13. Getting status of PrintXchange objects
Object status refers to information that is currently valid for a specific object, including: Current values of an object’s attributes Current state of an object Current status of an object. Getting object status refers to the capability of listing object attributes of: A specified object All objects of a specified class (unless the class is server, in which case you must specify each server name) A subset of all objects as constrained by a filter Job objects submitted to a specified logical printer (this capability is referred to as listing the job queue). As an administrator, you have the access control level to get object status for any object belonging to any user of the PrintXchange system. Generally, PrintXchange lists information only for objects for which a user has an appropriate access control level. Users with an End User access control level, for example, may list object status for only certain objects such as their own jobs. When listing object status, PrintXchange uses the value of the environment variable PDPRINTER as the default logical printer, and the spooler containing PDPRINTER as the default server.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 13-1 GETTING STATUS OF PRINTXCHANGE OBJECTS
Understanding object states
Document, job, printer, queue, and server objects each have a class- specific attribute that contains the current state of the object. Initial- value-job and initial-value-document objects do not have states. State attributes for each class are as follows: class_name state attribute document document-state job current-job-state printer printer-state queue state server server-state
Table 13-1 lists the PrintXchange object states that correspond to a given object’s state attribute. An additional attribute called enabled determines whether or not a supervisor, spooler, queue, logical printer, or physical printer is currently enabled or disabled. That is, an object that is disabled can not accept jobs. However, the object’s state attribute may indicate that the object is ready. Therefore, for example, in trying to determine why a job can’t get onto a queue whose state attribute is ready, check the value of the queue’s enabled attribute. It is likely set to disabled.
13-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GETTING STATUS OF PRINTXCHANGE OBJECTS
Table 13-1. Object states
Object State Description Document transfer-pending The spooler has not completely retrieved the document. pending The normal state for a document waiting in the spooler to be printed. processing The spooler submitted the job, including this document, to the supervisor but the supervisor has not yet begun to print the document.
completed The document has been printed.
Job pre-processing The spooler has not completely retrieved the job.
pending The normal state for a job waiting in the spooler to be printed.
processing The spooler submitted the job to the supervisor but the supervisor has not yet begun to print the job.
printing The job is printing. If the physical printer state is also printing, paper is coming out.
held The job is being held by the server, possibly due to a user request. The reason(s) for the job being held may be determined by examining the job’s job- state-reasons attribute.
paused The job has been paused; it will not be eligible for printing until the job is resumed.
retained The job is complete, but the job-retention- period has not expired. The job is still eligible to be resubmitted.
completed The job has been printed and the job- retention-period has expired. The job is no longer eligible to be resubmitted.
terminating The job has been canceled or aborted by the server and is in the process of terminating.
unknown The job state is not known, or indeterminate, or is not returned by the operation.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 13-3 GETTING STATUS OF PRINTXCHANGE OBJECTS
Table 13-1. Object states (continued)
Object State Description
Logical printer idle The logical printer is accepting jobs. This is the only state for logical printers.
Physical printer idle The printer is waiting for a job.
printing A job is printing normally.
needs-attention There is something wrong with the printer (e.g. paper out).
paused The printer has been paused; printing won’t proceed until the printer is resumed.
timed-out The printer has not been accepting data for a period in excess of the value of the printer attribute printer-timeout-period.
connecting-to-printer The supervisor is connecting to the printer and performing any printer initialization activities. If the printer remains in this state for a long time, it indicates that there is some trouble communicating with the printer or that the printer is busy with other, non-PrintXchange printing.
unknown The printer state is not known, or indeterminate, or is not returned by the operation.
Queue ready The normal state for a queue.
paused The queue has been paused; printing won’t proceed until the queue is resumed.
Server ready The normal state for a server.
terminating The server is in the process of shutting down and exiting.
paused The server has been paused; printing won’t proceed until the server is resumed.
13-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GETTING STATUS OF PRINTXCHANGE OBJECTS
Related printer-state information
The printer-state attribute identifies the current state of the printer objects: Logical printer Physical printer The following table lists the valid printer states and indicates the values supported by the reference and Xerox supervisor. Table 13-2. Valid printer states supported by the reference and Xerox supervisor
Xerox Supervisor
SNMP XPP No Device Reference Device Device Status Supervisor Status Status connecting-to-printer x x ------idle xxxx needs-attention xxx--- needs-key-operator --- x ------paused xxxx printing xxxx saturated --- x x x shutdown xxxx timed-out x x ------unknown xxxx
printer-problem-message The printer-problem-message attribute contains a text string describing a problem. hold-jobs-interrupted-by-printer-failure The hold-jobs-interrupted-by-printer-failure attribute specifies whether jobs returned to the spooler after a restart should be put in the held or pending state. The spooler uses the hold-jobs-interrupted-by-printer-failure attribute from the physical printer object if the attribute is specified there. Otherwise, the spooler uses the attribute specified for itself (the spooler). If the value of hold-jobs-interrupted-by-printer-failure is true|yes or unspecified, jobs returned to the supervisor due to crashes are put in the held state. The job’s job-state-reasons attribute would then contain the values: job-interrupted-by-printer-failure and job-hold- set. In order for the job to be rescheduled for printing, the job’s job- hold attribute must be reset to false/no. If the value of hold-jobs-interrupted-by-printer-failure is false|no, jobs returned to the supervisor due to crashes are put in the pending state. The job’s job-state-reasons attribute would be empty in this case. The job will be rescheduled for printing with no human intervention.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 13-5 GETTING STATUS OF PRINTXCHANGE OBJECTS
Listing object attributes
You can list object attributes using the CLI or GUI.
Listing object attributes using GUI
For a complete list of all object attributes you can set after object creation, refer to the “Allowed attributes to set and modify” section in the “Setting and modifying object attributes” chapter Note: The GUI does not have the capability to display attributes for initial-value-job and initial-value document objects.
Listing object attributes using CLI
To list object attributes use the following command: pdls [-c class_name] [-f filter text] [-F] [-g] [-r requested_attributes] [-s style_name] [-x extended_attribute_string ...] [-X attribute_filename ..] [object_instance ...] class_name object_instance job (default) [spooler_name:][job_identifier] document [spooler_name:][job_identifier.doc_integer] initial-value-document [spooler_name:][iv_doc_name] initial-value-job [spooler_name:][iv_job_name] queue [spooler_name:][queue_name] printer [spooler_name:][logical_printer_name] printer [supervisor_name:][physical_printer_name] server [spooler_name: …] server [supervisor_name: …] If you do not specify an object_instance, PrintXchange lists all objects of the requested class_name (except for servers) on the default server. If you specify an object_instance that does not exist, PrintXchange returns an error. If you do not specify spooler_name or supervisor_name, PrintXchange uses the name of the spooler indicated by the PDPRINTER environment variable. The pdls command does not differentiate between attributes within an object class. That is, pdls treats spooler-specific attributes and supervisor-specific attributes as server object attributes. For example: When doing pdls with spooler-specific attributes on a supervisor object, the operation considers the attributes as appropriate to the server object. Therefore, pdls returns an empty attribute set on the supervisor and does not incur any error. switch description -f Selection criteria to be used among the candidate object_instances. Refer to the PrintXchange Command Line Interface Reference Guide. -F Turn off all filtering. Refer to the PrintXchange Command Line Interface Reference Guide.
13-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GETTING STATUS OF PRINTXCHANGE OBJECTS
-r The set of attributes for pdls to write to standard output. Refer to the PrintXchange Command Line Interface Reference Guide. -s, -g The style (format) of the attribute report for pdls to write to standard output. -g indicates that the report shall not include headings. Refer to the PrintXchange Command Line Interface Reference Guide. -x, -X The means by which to specify client attributes relevant to pdls: scope=0 Use with class_name=job to specify listing of job attributes only. This is the default. scope=1 Use with class_name=job to specify listing of job and document attributes. count-limit=n Write pdls output for every n objects. Use this attribute to break a long request into several smaller ones. time-limit=n Write pdls output every n seconds. Use this attribute to break a long request into several smaller ones. -x and -X also serve as alternate ways of specifying any of the other switch options.
Listing the job queue using CLI and GUI
Job and document attributes may be listed by displaying the job queue. For additional information on listing job and document attributes, refer to the “Managing jobs and documents” chapter.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 13-7 GETTING STATUS OF PRINTXCHANGE OBJECTS
13-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14. Managing jobs and documents
This chapter explains how to handle the most common PrintXchange job and document management operations including the following: Job and document object operations include the following: Printing jobs and documents Printing a job after a specified time Holding and releasing jobs Pausing and resuming jobs Retaining jobs Modifying job and document attributes Setting job priorities Resubmitting jobs to a logical printer Deleting job and document defaults Modifying default job priorities Promoting jobs Deleting jobs Canceling jobs Discarding jobs with print deadlines Listing a job queue Listing names and attributes of jobs and documents Removing all jobs from a server or queue – Cleaning objects. This chapter explains the commands to perform these operations at a very high level. For details on all PrintXchange commands and attributes, refer to the PrintXchange Command Line Interface Reference Guide.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-1 MANAGING JOBS AND DOCUMENTS
Printing jobs and documents
The print operation creates job and document objects per your request to print one or more files. The spooler creates a job object for each print request, and a document object for each file you specify as part of a single print request. A job object, therefore, contains one or more document objects. For each job, the spooler assigns a unique job identifier (job- identifier attribute) that allows you to identify the job when running other operations, such as pausing a job.
Printing jobs and documents using GUI
To submit a print request using GUI: 1. Select Print from the File menu of your application. 2. In the Name box, select the desired logical printer. 3. Select OK. For more information on printing jobs, refer to the following Windows NT on-line help: PrintXchange Administration Tool Contents tab: Printing a job
Printing jobs and documents using CLI
To submit a print request (and thereby create job and document objects), use the following command: pdpr [-f filename] [-n copies] [-N notification_method] [-p logical_printer_name] [-t job_name] [-x extended_attribute_string] [-X attribute_filename ][filename ...] parameter description filename ... The name of the file or files you want to print. If you specify a hyphen (-), rather than filename, pdpr reads from standard input. If you specify more than one file name, each file becomes a document within a single job. If any file of a multi-document job does not exist or otherwise fails, the spooler rejects the entire job. switch description -f filename A file to include as a document in the print job. Use the -f switch with multi- document jobs to set document attributes for the specified file that are different from those for other files. -n copies The number of copies to print of the job.
14-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
-N notification_method The method by which to receive notification of events that occur during print job processing. Refer to the “Setting event notification” chapter in this guide. -p logical_printer_name The logical printer to which to submit the job. If you do not specify the -p switch, pdpr uses the logical printer identified by the value of the printer-name- requested attribute. If printer-name- requested is also unspecified, then pdpr uses the logical printer identified by the PDPRINTER environment variable. If you specify both -p and printer-name- requested on the command line, pdpr uses the lexically last logical printer name. -t job_name The print job name that you want specified for start sheets, notification, and logging. -x and -X Use these switches in the command line to set attribute values for the job and document objects. Document attributes apply to all documents whose filename follows the attribute specifications in the command line. Job attributes may be placed anywhere on the command line before the operands. Job attributes apply to all documents in the job. The add value ( + ) modification operator may be used when specifying the attribute notification-profile with pdpr. Refer to the “Setting and modifying object attributes” chapter. Other switches available for the pdpr command include: [-g] [-m message_text] [-r requested_attributes] [-s style_name] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Examples: The following example sends a file named readme.txt to the default logical printer, which is named by the PDPRINTER environment variable: pdpr readme.txt The following example sends 10 copies of the file named readme.ps to the logical printer named logical1: pdpr -x “job-copies=10” -p logical1 readme.ps
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-3 MANAGING JOBS AND DOCUMENTS
The following example sends the files named chap2.ps, chap3.ps, and chap4.ps to the default logical printer and specifies one-sided printing for chap2.ps and two-sided printing for chap3.ps and chap4.ps: pdpr -x “sides=1” -f chap2.ps -x “sides=2” chap3.ps chap4.ps The following example prints 2 copies of a job. Each job has 3 copies of
14-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Printing a job after a specified time
You can request that a job not be printed until after a specified date and time. You can specify the print after time during your initial print request or by modifying the job after it has been submitted. You may want to specify a print after time for a large job so that it will print during a low print volume period. When you set a print after time for a job, the spooler: Sets the attribute current-job-state to held. Adds the value job-print-after-specified to the attribute job- state-reasons. When the specified print after time has passed, the spooler schedules the job and changes its current-job-state to pending, assuming there is no other reason to hold the job, i.e. job-hold=yes.
Printing a job after a specified time using GUI
To print a job after a specified time: 1. Run the Administration Tool or the Information Tool. 2. Select the desired job from the appropriate printer, queue, or spooler. 3. Double-click the job to bring up the Job Properties menu. 4. Select the Advanced Tab. 5. Double-click the Controls folder. 6. Select Job Print After. 7. Invoke the "Job Print After..." Button that appears in the window. 8. Specify the desired print after time. 9. Select OK in the dialog box. 10. Select OK in the Job Properties window. For more information on printing a job after a specified time, refer to the following Windows NT on-line help: PrintXchange Administration Tool Index tab: Job Print After
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-5 MANAGING JOBS AND DOCUMENTS
Printing a job after a specified time using CLI
To print a job after a specified time with the print request, use the pdpr command. The syntax is: pdpr [-p logical_printer_name] -x “job-print-after=date_and_time” [filename ... ] To specify the print after time after the print request has been submitted, use either the pdmod or pdset command. The syntax is: pdmod -x “job-print-after=date_and_time” [spooler_name:]job_identifer or pdset -c job -x “job-print-after=date_and_time” [spooler_name:]job_identifer switch description -x or -X Set a future calendar date and time value for the job-print-after attribute. The format for date_and_time is: dd:mm:yyyy:HH:MM:SS where: dd = the day from 01 to 31 mm = the month from 01 to 12 yyyy = the year as four digits HH = the number of hours from 00 to 23 MM = the number of minutes from 00 to 59 SS = the number of seconds from 00 to 59 Examples: To print file “dpa-semantics.txt” after 7:00 pm on January 26, 1998 on the default logical printer (PDPRINTER) use: pdpr -x “job-print-after=26:01:1998:19:00:00” dpa-semantics.txt The following two examples set, after print-request submission, a print after time of 7:00 p.m. on January 25, 1998 for a job whose identifier is 4 on the spooler named main: pdmod -x “job-print-after=25:01:1998:19:00:00” main:4 pdset -c job -x “job-print- after=25:01:1998:19:00:00” main:4
14-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Holding and releasing jobs
A pending job may be held so that the spooler does not schedule it for printing, by setting the job-hold attribute to yes. When you hold a job, the spooler: Sets the attribute current-job-state to held. Adds the value job-hold-set to the attribute job-state-reasons. If you set job-hold=yes for a retained job, the job will remain in retained state. However, if and when the job is resubmitted, the job will go to held state. The job remains on hold indefinitely unless one of the following events takes place: You set the job-hold attribute to no. The spooler can then schedule the job and set its current-job-state to pending. This is assuming there is no other reason to continue holding the job (i.e. job-print-after time is set, or documents-needed). The job-discard-time that you previously set passes. The spooler then deletes the held job. You clean the associated queue or spooler. The spooler deletes all jobs in the queue or spooler, including jobs in the held state. You delete or cancel the job.
Releasing jobs using GUI
1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Double-click the job to bring up the Job Properties menu.
4. Select the Advanced Tab.
5. Double-click the Controls folder.
6. Select Job Hold.
7. To hold the job, select True as the value.
8. To release the job, select False as the value or select the box marked Unspecified.
9. Select OK in the Job Properties window.
For more information on releasing jobs, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: Pausing or resuming operation of jobs PrintXchange Administration Tool Contents tab: Changing status of selected system objects; or Index tab: resume
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-7 MANAGING JOBS AND DOCUMENTS
Holding and releasing jobs using CLI
To print a job and have it go immediately to held state, use the following syntax: pdpr [-p logical_printer_name] -x ”job-hold=yes” filename To hold a previously submitted job use the following syntax: pdmod -x "job-hold=yes" [spooler_name:]job_identifier or pdset -c job -x "job-hold=yes" [spooler_name:]job_identifier switch description -x or -X Set the attribute job-hold to yes.
To remove the hold on a job use the following command syntax: pdmod -x "job-hold=no" [spooler_name:]job_identifier or pdset -c job -x "job-hold=no" [spooler_name:]job_identifier switch description -x or -X Set the attribute job-hold to no. Examples: To print file readme.ps to the default printer but not have it scheduled for printing use: pdpr –x ”job-hold=yes” readme.ps To hold the job whose identifier is 4 on the spooler named main use: pdmod -x “job-hold=yes” main:4 or pdset -c job -x “job-hold=yes” main:4 You can release a job so that the spooler schedules it for printing. The syntax is the same as for holding jobs. To release the job held from the previous example use: pdmod -x “job-hold=no” main:4 or pdset -c job -x “job-hold=no” main:4
14-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Pausing and resuming jobs
You can pause a job only if the job is in the pending or held state (value of the current-job-state attribute). That is, the job has been completely received by the spooler, but the spooler has not yet sent the job to a supervisor for printing. When you pause a job: The associated spooler changes the value of the current-job- state attribute to paused. The associated spooler does not schedule the paused job for printing until you resume the job. You can still run operations to list the status of the job. When you resume a job: The associated spooler changes the value of the current-job- state attribute to pending or held, depending on the state of the job when you paused it: If the paused job had been in the pending state when you paused it, the spooler schedules it for an appropriate physical printer. PrintXchange then prints the job normally. If the paused job had been in the held state when you paused it, then the spooler returns it to the held state when you resume the job.
Pausing jobs using GUI
To pause a job: 1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Select the Pause icon from the Toolbar Menu.
OR
1. Select Pause from the Edit menu or from the right-click pop-up menu.
2. Select Yes in the confirmation window.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-9 MANAGING JOBS AND DOCUMENTS
Resuming jobs using GUI
To resume a job: 1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Select the Resume icon from the Toolbar Menu.
OR
1. Select Resume from the Edit menu or from the right-click pop- up menu.
2. Select Yes in the confirmation window.
For more information on pausing and resuming jobs using GUI, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: Pausing or resuming operation of jobs PrintXchange Administration Tool Contents tab: Changing status of selected system objects; or Index tab: resume
Pausing jobs using CLI
To pause a job, use the following command: pdpause -c class_name object_instance
class_name object_instance job [server_name:]job_identifier
Other switches available for the pdpause command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to PrintXchange Command Line Interface Reference Guide. Example: To pause the job “234” on the spooler named “big_spooler” with a CLI command, use: pdpause -c job big_spooler:234
14-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Resuming jobs using CLI
To resume a job, use the following command: pdresume -c class_name object_instance
class_name object_instance job [server_name:]job_identifier
Other switches available for the pdresume command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to PrintXchange Command Line Interface Reference Guide. Example: To resume the job “234” on the spooler named “big_spooler” with a CLI command, use: pdresume -c job big_spooler:234
Retaining jobs
You can retain a job for resubmission for a specified period of time after it prints or is terminated by some other event such as cancellation. You do this by specifying a retention period for the job in the job’s job-retention-period attribute. When a job completes of printing, or is otherwise terminated, if the job-retention-period is specified (as a non-zero value), the spooler: Sets the attribute current-job-state to retained Retains the job's attributes Retains each of the job's documents' attributes Retains each of the job's documents' data Once retained, a job remains in the retained state until one of the following occurs: The job is resubmitted The job's job-retention-period elapses A pdclean is performed on the job's associated queue or spooler The job is deleted via pddelete The job's job-discard-time arrives If the job's job-retention-period elapses, the spooler will delete all of the document data associated with the job and send the job to the completed state for the period of time specified by the job's job- completion-period or the server's default-job-completion-period.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-11 MANAGING JOBS AND DOCUMENTS
Retaining jobs using GUI
To retain a job using the GUI: 1. Run the Administration Tool or the Information Tool. 2. Select the desired job from the appropriate printer, queue, or spooler. 3. Double-click the job to bring up the Job Properties menu (or select the Details icon from the Toolbar Menu). 4. Select the Advanced Tab. 5. Double-click the Controls folder. 6. Select Job Retention Period. 7. Invoke the "Job Retention Period..." Button that appears in the window. 8. Specify the desired retention period. 9. Select OK in the dialog box. 10. Select OK in the Job Properties window. For more information on retaining jobs, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: Pausing or resuming operation of jobs PrintXchange Administration Tool Contents tab: Changing status of selected system objects; or Index tab: resume
Retaining jobs using CLI
You may use the pdpr, pdmod, pdset or pdrm command to retain jobs.
To specify that a job being submitted is to be retained after printing, use the following syntax:
pdpr [-p logical_printer_name] -x job-retention- period=retention_period filename
After a job is already in the spooler, but has not yet reached completed state, its retention period may be specified or modified using the following syntax:
pdmod -x job-retention-period=retention_period [spooler_name:]job_identifier
or
pdset -c job -x job-retention-period=retention_period [spooler_name:]job_identifier
14-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
To cancel a job and have it remain retained for resubmission, the following syntax may be used:
pdrm -r retention_period [spooler_name:]job_identifier
This is the equivalent of performing the following sequence:
pdmod -x job-retention-period=retention_period [spooler_name:]job_identifer
Note: If the job is already in the retained state, the pdrm command may not be used. However, the job-retention-period may be modified via the pdmod or pdset commands. switch description -x or -X Set the retention period value for the job-retention-period attribute. The format for retention_period is: [HH:]mm[:ss] where: HH = the number of hours from 00 to 23 mm = the number of minutes from 00 to 59 ss = the number of seconds from 00 to 59 Examples: To submit the file readme to the default logical printer and have it remain retained for 1 hour after it prints use: pdpr -x job-retention-period=1:00 readme
To retain the job whose identifier is 4 on the spooler named main for 2.5 hours after it prints use: pdmod -x job-retention-period=2:30 main:4 or pdset -c job -x job-retention-period=2:30 main:4 To cancel the job whose identifier is 2001 on the default spooler and retain it for 15 hours use: pdrm -r 15:00 2001
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-13 MANAGING JOBS AND DOCUMENTS
Modifying job and document attributes
You can modify job and document attributes if the job is in the preprocessing, pending, held, paused, terminating, or retained state. This is the value of the current-job-state attribute. You may not modify a job that is in the completed state. Modifying a job or document attribute does not affect the job’s order in the queue unless the job-priority attribute is modified. However, the entire job is subject to the same attribute validation that takes place on job submission. If the job or document modification would result in a job that is not valid for the queue, then PrintXchange rejects the modify operation. If you are modifying a retained job (to prepare for resubmission), attribute validation against the current printer is not performed. When the job is resubmitted, validation against the new printer will be performed.
Modifying job and document attributes using GUI
To Modify a job: Run the Administration Tool or the Information Tool. 1. Select the desired job from the appropriate printer, queue, or spooler. 2. Double-click the job to bring up the Job Properties window. 3. Select the Basic or Advanced Tab(s), as appropriate. 4. Modify the desired attribute(s). 5. Select OK. To Modify a document: 1. Run the Administration Tool or the Information Tool. 2. Select the desired job from the appropriate printer, queue, or spooler. 3. Double-click the job to bring up the Job Properties window. 4. Select the Documents Tab. 5. Double-click the desired document or select the desired document and invoke the "Properties..." button to bring up the Document Properties window. 6. Select the Basic or Advanced Tab(s), as appropriate. 7. Modify the desired attribute(s). 8. Select OK. For more information on modifying document and job attributes, refer to the following Windows NT on-line help: PrintXchange Administration Tool Contents tab: Modify attributes of a selected job
14-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Modifying job and document attributes using CLI
To modify job and/or document attributes use the following command: pdmod [-n copies] [-N notification_method] [-t job_name] [-x extended_attribute_string] [-X attribute_filename] object_instance object object_instance document spooler_name:job_identifier.doc_integer job spooler_name:job_identifier When you specify a document, .doc_integer must be at least 1 or at most the total number of documents in the job (number-of- documents attribute). Also, the operation accepts only document attributes, not job attributes. When you specify a job, the operation accepts job and document attributes, and applies document attribute changes to all documents in the job. switch description -n copies The number of copies to print of the job. -N notification_method The method by which to receive notification of events that occur during print job processing. Refer to the “Setting event notification” chapter in this guide. -t job_name The print job name that you want specified for start sheets, notification, and logging. -x and -X Use these switches in the command line to set attribute values for the job and document objects. Other switches available for the pdmod command include: [-g] [-m message_text] [-r requested_attributes] [-s style_name] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Examples: The following example changes the number of job copies to 10 for the job whose identifier is 4 on the spooler named spooler1: pdmod -n 10 spooler1:4 The following example changes the job retention period to one hour for the job whose identifier is 3 on the spooler named spooler1: pdmod -x “job-retention-period=01:00:00” spooler1:3
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-15 MANAGING JOBS AND DOCUMENTS
The following example changes the default medium to a, for the sixth document of the job whose identifier is 12 on the spooler named spooler1: pdmod -x “default-medium=a” spooler1:12.6 The following example changes the copy count to 3 of ALL documents in the job whose identifier is 20 on the spooler named spooler1: pdmod -x copy-count=3 spooler1:20
Setting job priorities
You can specify a priority for scheduling a print job. A higher value indicates a higher priority. The spooler passes over lower priority jobs in favor of higher priority jobs when scheduling the jobs for printing. Operators and administrators have the full range of job priorities from 1 to 100, while end users have a limited range of from 1 to the value of the logical printer’s max-user-job-priority attribute. If you do not specify a job-priority during submission, or if you request that the job-priority attribute be set to the default value, the following algorithm will be used to determine the priority of the job: If an initial-value-job is specified for the job or there is an initial- value-job associated with the logical printer to which the job was submitted, examine the initial-value-job’s job-priority attribute. If the job-priority is specified for the initial-value-job and its value is not greater than the logical printer’s max-user-job-priority value, then assign this priority to the job. If there is no initial-value-job associated with the job or the value of its job-priority attribute is greater than the logical printer’s max-user-job-priority, assign the value of the logical printer’s default-user-job-priority attribute, if it exists, to the job. If the logical printer has no default-user-job-priority, and if the system’s default job priority (which is 50) does not exceed the logical printer’s max-user-job-priority, assign this priority to the job. If the logical printer’s max-user-job-priority is less than 50 (the system default), assign the value of max-user-job-priority to the job.
14-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Setting job priorities using GUI
1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Double-click the job to bring up the Job Properties menu.
4. Select the Advanced Tab.
5. Double-click the Job Options folder.
6. Select Job Priority.
7. Set Job Priority to the desired value.
8. Select OK. Setting job priorities using CLI
You can use the pdpr command to submit a job with a specific job priority. The syntax is: pdpr [–p logical_printer_name] –x “job-priority=n” filename You can modify the priority of a job in the pending or retained state after it has been submitted. Use the pdmod or pdset command to modify the priority of a job after job submission. The syntax is: pdmod -x “job-priority=n” [spooler_name:]job_identifier or pdset -c job -x “job-priority=n” [spooler_name]job_identifier Examples: The following example submits the file named readme.ps to the logical printer named lp1 and assign it a job priority of 25. pdpr –p lp1 –x “job-priority=25” readme.ps The following examples change the default priority to 43 for the job whose identifier is 4 on the spooler named spooler1: pdmod -x “job-priority=43” spooler1:4 or pdset -c job -x “job-priority=43” spooler1:4 The following example requests that job 4 on the default spooler have its job priority assigned to the default value: pdmod –x “job-priority==” 4
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-17 MANAGING JOBS AND DOCUMENTS
Resubmitting jobs to a logical printer
The resubmit operation allows you to request that a spooler resubmit specified print jobs to a specified target logical printer on the same spooler. You may resubmit specified jobs or all jobs of a specified queue. As an administrator or operator, you may resubmit any job. End Users may resubmit only their own jobs. Individual documents cannot be resubmitted. Jobs that you resubmit must be completely submitted. That is, the spooler has received all files that comprise the job and the value of the attribute job-submission-complete is true. A job must also be in one of the following states (current-job-state attribute): pending, held, paused, or retained, and must not contain the value documents-needed for job-state-reasons. The resubmit operation fails if the job’s current-job-state is printing, terminating, processing, preprocessing, or completed, or if it contains the value documents-needed in its job-state-reasons attribute. When you resubmit a job, the spooler removes the specified job from its current queue and submits it to the target logical printer. To resubmit all jobs in a specified queue, first disable the queue. For additional information, refer to the “Enabling and disabling queues, physical and logical printers” chapter. Then, when you run the resubmit operation: The spooler removes all jobs that are pending, paused, or held from the specified queue and submits them to the target logical printer. The spooler returns a warning for any job(s) that it does not successfully resubmit. It is up to you then, to resubmit the individual job(s) in question.
14-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Resubmitting jobs using GUI
To resubmit a job: 1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Select Resubmit from the Edit menu or from the right-click pop- up menu.
4. In the dialog box, select the printer to which you would like the job resubmitted.
5. Select OK.
For more information on resubmitting jobs, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: Resubmitting jobs to a logical printer
To resubmit all jobs in a queue:
1. Run the Administration Tool.
2. Select the desired queue.
3. Select Resubmit from the Edit menu or from the right-click pop- up menu.
4. In the dialog box, select the printer to which you would like the job resubmitted.
5. Select OK.
For more information on resubmitting all jobs in a queue, refer to the following Windows NT on-line help: PrintXchange Administration Tool Contents tab: Resubmitting queues or jobs to a logical printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-19 MANAGING JOBS AND DOCUMENTS
Resubmitting jobs using CLI
To resubmit jobs use the following command: pdresubmit [-c class_name] target_logical_printer_name object_instance ... class_name object_instance job (default) [spooler_name:]job_identifier ... queue [spooler_name:]queue_name ...
parameter description target_logical_printer_name The logical printer to which you want to resubmit the specified job(s) Other switches available for the pdresubmit command include: [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Examples: To resubmit jobs "2000" and "2001" on the default printer to logical printer "redhighlight" with a CLI command, use: pdresubmit -c job redhighlight 2000 2001 To resubmit all the jobs in the queue "color_q" to logical printer "bluehighlight" with a CLI command, use: pdresubmit -c queue bluehighlight color_q
14-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Deleting job and document defaults
You can delete logical-printer level job and document defaults by deleting the initial-value-document and initial-value-job objects from the spooler’s object database and the name space. Note: Jobs and documents which have already been submitted to the system and had these defaults applied to them will not be modified in any way. This will only affect jobs which are submitted to the system after the initial-value objects have been deleted.
Deleting job and document defaults using GUI
This function is not available using GUI.
Deleting job and document defaults using CLI
Use the pddelete command to delete job and document defaults. The syntax is: pddelete -c initial-value-document [spooler_name:]iv_doc_name or pddelete -c initial-value-job [spooler_name:]iv_job_name The pddelete command does not remove the initial-value-document reference from the logical printer attribute printer-initial-value- document or the initial-value-job reference from the printer-initial- value-job attribute. However, when a job is printed to that logical printer the initial-value-object will be ignored. If you wish to remove defaulting only from a specific printer, you may reset the printer-initial-value-job or printer-initial-value-document attribute to no longer reference anything. In other words you may delete the attribute, rather than delete the initial–value-job or initial- value-document. Examples: The following example deletes an initial-value-document object named ivd_2sided from the default spooler, which is the spooler containing the logical printer that the pdprinter environment variable names: pddelete -c initial-value-document ivd_2sided The following example deletes an initial-value-job object named ivj_retain from the spooler named spooler1: pddelete -c initial-value-job spooler1:ivj_retain The following example removes defaulting from the printer named printer1 on the default spooler which was previously setup to use defaults from the initial-value-job ivj_retain: pdset -c printer –x printer-initial-value- job=ivj_retain printer1.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-21 MANAGING JOBS AND DOCUMENTS
Modifying default job priorities
Initial-value-document and initial-value-job objects that you associate with logical printers set defaults for all documents and jobs coming to that logical printer.
Modifying default job priorities jobs using GUI
This function is not available using GUI.
Modifying default job priorities jobs using CLI
You can use the pdset command to modify default job values, including job-priority. The syntax is: pdset -c initial-value-job -x “job-priority=n” [spooler_name:]iv_job_name Example: The following example changes the default job priority, which the initial-value-job object named ivj_priority specifies, on the spooler named spooler1 to 35: pdset -c initial-value-job -x “job-priority=35” spooler1:ivj_priority
Promoting jobs
Promoting a job moves the specified job to the beginning of the queue associated with the logical printer to which you submitted it. This causes the job to be printed before all other jobs, regardless of submission time. Promoting several jobs in the same queue creates what is effectively a last-in/first-out printing sequence. That is, the most recently promoted job is printed first. You can promote a job that you had previously promoted. The currently printing job continues normally at each of the physical printers associated with the queue containing the job to be promoted. The spooler assigns the promoted job to the first physical printer that completes its current job and that can handle the promoted job. You can promote jobs that have a current-job-state of pending, paused, or held. The queue state must be either ready or paused. The promote operation sets the job attribute job-promote-time to the current time. The promote operation fails if the spooler has already sent the job to a supervisor.
14-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Promoting jobs using GUI
To promote a job: 1. Run the Administration Tool. 2. Select the desired job from the appropriate printer, queue, or spooler. 3. Select the Promote icon from the Toolbar Menu. Or 1. Select Promote from the Edit menu or from the right-click pop- up menu. 2. Select Yes in the confirmation window. For more information on promoting jobs, refer to the following Windows NT on-line help: PrintXchange Administration Tool Index tab: promote
Promoting jobs using CLI
To promote a job use the following command: promote object_instance object object_instance (job) [spooler_name:]job_identifier
Other switches available for the pdpromote command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Example: The following example promotes the job whose identifier is 4 on the spooler named spooler1: pdpromote spooler1:4
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-23 MANAGING JOBS AND DOCUMENTS
Deleting jobs
This operation deletes the specified job, regardless of its current state. When a job is being deleted, pddelete sets the value of the job-retention-period attribute to zero, overriding its previous value, if any. Also, this utility ignores the job’s job-completion-period and the server’s default-job-completion-period attribute. This differs from pdrm which honors job-retention-period, as well as job- completion-period or default-job-completion-period. If the job has already been delivered to a supervisor, pddelete causes the spooler to send a delete-job request to the supervisor, which cancels the job. The supervisor then stops printing the job as soon as possible, after which the job is deleted from both the supervisor and spooler. The pddelete command: Sets the value of the job-retention-period to 0. Causes the spooler to send a delete-job request to the supervisor if the spooler has already sent the job to a supervisor. Adds, for accounting purposes, the value deleted-by- administrator to the job’s job-state-reasons attribute. Ignores the job’s job-completion-period and server’s default- job-completion-period attribute.
Deleting jobs using GUI
To delete a job: 1. Run the Administration Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Select the Delete icon from the Toolbar Menu.
Or
1. Select Delete from the Edit menu or from the right-click pop-up menu.
2. Select Yes in the confirmation window.
3. Select Yes in the confirmation window.
For information on deleting jobs through GUI, refer to the following Windows NT on-line help: PrintXchange Administration Tool Contents tab: Deleting a system object
14-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Deleting jobs using CLI
Use the pddelete command to delete jobs. The syntax is: pddelete -c class_name object_instance class_name object_instance job [spooler_name:]job_identifier Other switches available for the pddelete command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Example: The following example removes the job whose identifier is 4 from the spooler named spooler1: pddelete -c job spooler1:4
Canceling jobs
Canceling a job ensures that the job will not be scheduled for printing. A job can only be canceled if it has not yet finished printing (i.e. is not in the terminating, retained or completed state.) If the job’s job-retention-period attribute has a non-zero value and/or if a completion period is applicable to the job, the cancel operation does not delete the job. Instead the cancel operation: Removes the job from any printer to which it is assigned. Places the job in the retained state, where it remains for the period specified by the job-retention-period attribute. After the job-retention-period has expired, places the job in a completed state for the period of time specified by the job’s job- completion-period attribute or the server’s default-job- completion-period attribute.
Canceling jobs using GUI
To cancel a job: 1. Run the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Select the Cancel icon from the Toolbar Menu.
OR
1. Select Cancel from the Edit menu or from the right-click pop-up menu.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-25 MANAGING JOBS AND DOCUMENTS
2. Select Yes in the confirmation window.
For information on canceling jobs through GUI, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: Canceling jobs
Canceling jobs using CLI
When canceling a job using CLI, you can choose to bypass or extend the job’s current retention period by using the –r option. To cancel a job use the following command: pdrm [-r retention_period] object_instance object object_instance (job) [spooler_name:]job_identifier
switch description -r retention_period Set the retention period value for the job- retention-period attribute. The format for retention_period is: [HH:]mm[:ss] where: HH = the number of hours from 00 to 23 mm = the number of minutes from 00 to 59 ss = the number of seconds from 00 to 59 Other switches available for the pdrm command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Examples: The following command will cancel the job whose identifier is 4 from the default spooler: pdrm 4 The following command will cancel a job whose identifier is 4 from the spooler named spooler1 and retain it for 2 hours: pdrm –r 2:00 spooler1:4 The following command will cancel a job whose identifier is 4 from the spooler named spooler1 and bypass its current retention period. pdrm –r 0 spooler1:4
14-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Discarding jobs with print deadlines
You can specify that the spooler discard a job if the job does not print by a desired time. The attribute job-discard-time specifies the time. When the job discard time arrives, the spooler deletes the job whether or not it has printed and regardless of the job state. When the time specified by job-discard-time arrives, the spooler: Sets the value of the job-retention-period to 0. Causes the spooler to send a delete-job request to the supervisor if the spooler has already sent the job to a supervisor. Adds, for accounting purposes, the value deleted-by- administrator to the job’s job-state-reasons attribute. Ignores the job’s job-completion-period and server’s default- job-completion-period attribute.
Discarding jobs with print deadlines using GUI
1. Run the Administration Tool or the Information Tool.
2. Select the desired job from the appropriate printer, queue, or spooler.
3. Double-click the job to bring up the Job Properties menu.
4. Select the Advanced Tab.
5. Double-click the Controls folder.
6. Select Job Discard Time.
7. Invoke the "Job Discard Time..." Button that appears in the window.
8. Specify the desired discard time.
9. Select OK in the dialog box.
10. Select OK in the Job Properties window.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-27 MANAGING JOBS AND DOCUMENTS
Discarding jobs with print deadlines using CLI
Use the pdpr command to specify a discard time for a job being submitted. pdpr [-p logical_printer_name] -x “job-discard- time=date_and_time” [filename ... ] Use pdmod or pdset or to specify a print deadline for a job which has already been submitted. The syntax is: pdmod -x “job-discard-time=date_and_time” [spooler_name:]job_identifier or pdset -c job -x “job-discard-time=date_and_time” [spooler_name:]job_identifier switch description -x or -X Set a future calendar date and time value for the job-discard-time attribute. The format for the date and time is: dd:mm:yyyy:HH:MM:SS where: dd = the day the day from 01 to 31 mm = the month from 01 to 12 yyyy = the year as four digits HH = the number of hours from 00 to 23 MM = the number of minutes from 00 to 59 SS = the number of seconds from 00 to 59 Examples: The following example submits the file chap1.ps to the default printer, specifying that it be discarded if it does not print by 8:00 a.m. on April 1, 1998: pdpr -x “job-discard-time=01:04:1998:08:00:00”4 chap1.ps Each of the following two examples specifies that the default spooler shall discard the job whose identifier is 4 if it does not print by 9:00 p.m. on March 5, 1998: pdmod -x “job-discard-time=05:03:1998:21:00:00”4 pdset -c job -x “job-discard- time=05:03:1998:21:00:00” 4
14-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Listing a job queue
Listing the job queue allows you to see all print jobs in their print order in the queue of a specific logical printer. Use the pdq command to list a job queue.
Listing a job queue using GUI
To view the job queue in the entire domain: 1. Run the Administration Tool or the Information Tool. 2. Select the desired printer to list jobs for. 3. In the upper right menu or in the printer pop-up menu, select Jobs. For information on listing a job queue, refer to the following Windows NT on-line help: PrintXchange Printer Information Tool Contents tab: List available jobs PrintXchange Administration Tool Contents tab: Listing available system objects
Listing a job queue using CLI
To list a job queue use the following command: pdq [-f filter text] [-F] [-g] [-p logical_printer_name] [-r requested_attributes] [-s style_name] [-x extended_attribute_string ...][-X attribute_filename ...] [object_instance] ...
object object_instance job [spooler_name:]job_identifier document [spooler_name:]job_identifier.doc_integer
The first object_instance in the command line indicates the object class. job_identifier indicates job object; job_identifier.doc_integer indicates document object. The attributes (job or document attributes) that pdq lists for all object instances in the command line depend upon the object class indicated in the first object_instance. If you do not specify an object_instance, pdq lists all print jobs for the specified or default printer in the sequence they are currently scheduled to print. If you include .doc_integer with the object_instance, then pdq lists the requested attributes only for the specified document. Each specified job included in the command line may have been submitted to a different logical printer on a different server. If you request a specific object_instance and the object does not exist, pdq returns an error.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-29 MANAGING JOBS AND DOCUMENTS
Operators and administrators can list all jobs in any queue; end users can list the jobs they own.
switch description -f Selection criteria to be used among the candidate object_instances. Refer to the PrintXchange Command Line Interface Reference Guide. -F Turn off all filtering. Refer to the PrintXchange Command Line Interface Reference Guide. -p List all jobs in the queue submitted to the specified logical printer. If you specify an object_instance, pdq ignores -p. Also, pdq fails if you specify the name of a physical printer instead of a logical printer. -r The set of attributes that pdq writes to standard output. Refer to the PrintXchange Command Line Interface Reference Guide. -s, -g The style (format) of the attribute report that pdq writes to standard output. -g indicates that the report shall omit headings. Refer to the PrintXchange Command Line Interface Reference Guide. -x, -X Serve as alternate ways of specifying any of the switch options. Examples: The following example lists all jobs in the queue of the default logical printer, which is the printer named by the PDPRINT environment variable: pdq The following example lists all jobs in the queue of the logical printer named logical1: pdq -p logical1 The following example lists all attributes of the job on the default spooler whose job-identifier is 4 pdq –r all 4
14-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Listing names and attributes of jobs and documents
You can list the names and attributes of all jobs and/or documents in a spooler.
Listing names and attributes of jobs and documents using GUI
To view job attributes: 1. Double-click the desired job to bring up the Job Properties menu.
To view document attributes: 1. Double-click the job to bring up the Job Properties menu. 2. Select the Documents Tab. 3. Double-click the desired document or select the desired document and invoke the "Properties..." button to bring up the Document Properties window.
For information on listing object attributes through GUI, refer to the following Windows NT on-line help: PrintXchange Administration Tool Contents tab: Listing and modifying supported attributes of a logical/physical printer
Note: For additional information on the use of GUI to list object attributes, refer to the “Getting status of PrintXchange objects” chapter.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-31 MANAGING JOBS AND DOCUMENTS
Listing names and attributes of jobs and documents using CLI
Use the pdls command to list names and attributes of jobs and documents. The syntax for listing the names and attributes of all jobs and documents or a single job and all its documents in a spooler is: pdls [-c class_name] [-f filter_text] [-F] [-g] [-p logical_printer_name] [-r requested_attributes] [-s style_name] -x “scope=1” [-x extended_attribute_string ...][-X attribute_filename ...] object_instance The syntax for listing the names and attributes of just the jobs or a single job in a spooler is: pdls [-c class_name][-f filter text] [-F] [-g] [-p logical_printer_name] [-r requested_attributes] [-s style_name] [-x extended_attribute_string ...] [-X attribute_filename ...] object_instance
class_name object_instance job (default) [spooler_name:]job_identifier] If you do not specify [spooler_name:][job_identifier ], the command lists the names and attributes of all jobs and documents (or just all jobs) on the default spooler, which is the spooler that contains the logical printer named by the PDPRINT environment variable. If you specify a [spooler_name:][job_identifier] that does not exist, pdls returns an error. Operators and administrators can list the names and attributes of all jobs; end users can list the names and attributes of the jobs they own. Examples: The following example lists the names and attributes of all jobs on the default spooler: pdls The following example lists the job and document attributes for the job whose identifier is 4 on the spooler named spooler 1: pdls -c job -x “scope=1” spooler1:4 Note: For additional information on the use of CLI to list object attribute, refer to the “Getting status of PrintXchange objects” chapter.
14-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING JOBS AND DOCUMENTS
Removing all jobs from a server or queue - Cleaning objects
The clean operation removes all jobs from all specified queue(s) or spooler(s). You cannot clean supervisors. The clean operation is an asynchronous operation, meaning that the spooler returns to the client before the operation is complete. Clean is intended as an emergency operation for you to use to fix a problem, rather than as a regular operation that would be put into a script. You must disable a specified queue or spooler (enabled=no) when invoking the clean operation (refer to the “Enabling and disabling objects” chapter). If the specified object is not first disabled, the clean operation fails. When you perform the clean operation: The clean operation deletes all jobs associated with the object, including jobs that are retained, processing, printing, or completed. In order to delete processing or printing jobs, it sends a delete-job request to all jobs that are currently printing on it’s associated physical printers. Adds, for accounting purposes, the value deleted-by- administrator to each job’s job-state-reasons attribute. While the clean is in progress, the spooler or queue does not submit any jobs to the supervisor. The clean operation attempts to clean as much as it can, even if some jobs encounter problems. While the clean is in progress, the spooler rejects any enable requests on the spooler or queue. When the clean operation has completed, the operation uses Notification Services to deliver a clean complete event to the client.
Cleaning a spooler or queue using GUI
To clean a spooler or queue: 1. Run the Administration Tool.
2. Select the desired spooler or queue.
3. First disable the spooler or queue by selecting the Disable icon from the Toolbar Menu or by selecting Clean from the Edit menu or from the right-click pop-up menu.
4. Select Yes in the confirmation window.
5. Select the Clean icon from the Toolbar Menu.
OR
1. Select Clean from the Edit menu or from the right-click pop-up menu.
2. Select Yes in the confirmation window.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 14-33 MANAGING JOBS AND DOCUMENTS
For information on cleaning a spooler or queue through GUI, refer to the following Windows NT on-line help: PrintXchange Administrator Tool Contents tab: Cleaning a spooler or a queue Note: Selecting the Clean option will automatically disable the object. After the clean operation is complete, the object must be enabled by selecting Enable from the Selected menu.
Cleaning a spooler or queue using CLI
To clean an object use the following command: pdclean [-c class_name] object_instance ... class_name object_instance server [spooler_name:]spooler_name queue [spooler_name:]queue_name Other switches available for the pdclean command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide. Use the pddisable command to disable a spooler or queue (refer to “Enabling and disabling objects” chapter in this guide). When pdclean completes, it sends a “clean complete” event to the client. After receiving the “clean complete” event, you must use the pdenable command to re-enable the spooler or queue. Examples: The following example cleans a spooler named spooler1: pddisable -c server spooler1 pdclean -c server spooler1 The following example cleans a queue named q1: pddisable -c queue q1 pdclean -c queue q1
14-34 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15. Setting and modifying object attributes
PrintXchange has a "set attribute” and a “modify attribute” operation, each of which allows you to add or change values of print object attributes. All PrintXchange objects are valid for the set attribute operation. However, only job and document objects are valid for the modify attribute operation. For a list of object attributes that you can change with the set and modify operations, refer to the “Allowed attributes for set and modify” section. PrintXchange includes a database that contains object identifiers for all of its data entities. Users can update the OID database by creating and adding to the database their own attributes, attribute value classes, and attribute values. When you set or modify a print object’s attributes, the values you set are persistent. That is, the objects retain the set values across system restarts. When you set or modify multiple attributes at the same time, the changes to all specified attributes must succeed for the entire operation to succeed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-1 SETTING AND MODIFYING OBJECT ATTRIBUTES
CLI modification operators
The CLI pdset and pdmod operations require that you indicate via operators the kind of change you want to make to an attribute value. The operators are: + Add a new value to a multiple-value attribute. – Remove a value (if the value is the only value for the attribute, the operation sets the value to the default). = Reset the value to the default. (no operator) Replace the entire attribute value with the new one, or add the attribute if the attribute is not already present. Replace all values of a multi-valued attribute with the new value. You include the operators as part of the attribute=value pairs that you specify via the -x or -X switches in the pdset and pdmod command lines. For the -x switch, the extended_attribute_string consists of one or more attribute-value pairs. For the -X switch the file with attribute_filename contains attribute-value pair specifications. To apply an operator, add the operator before the equal sign ( = ) of an attribute=value pair. Examples: 1. To remove the user “ginger” from the list of approved operators on the supervisor “big_super”, use: pdset -c server -x "access-control-list– ={name=ginger name-type=user privilege-level=operator}" big_super 2. To add a simple-text to PostScript translation filter to an existing list of filters on the supervisor “big_super”, use: pdset -c server -x "filter- definition+={name=text-to-ps type=translation input-format=simple-text output-format=PostScript command='/usr/bin/ttp'}" big_super 3. To change the value of job-copies for job “234” on spooler “big_spooler” to 10 copies, use: pdmod -n 10 big_spooler:234 or pdmod -x “job-copies=10” big_spooler:234 or pdset -c job -x “job-copies=10” big_spooler:234 4. To reset job-copies for job “234” on spooler “big_spooler” to the default, use: pdmod -x “job-copies==” big_spooler:234 or pdset -c job -x “job-copies==” big_spooler:234
15-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
5. To replace the current value of the number-of-printers- supported attribute with the value “5” for the supervisor “big_super”, use: pdset -c server -x "number-of-printers- supported=5" big_super For more information on using the modification operators, refer to the PrintXchange Command Line Interface Reference Guide.
Allowed attributes for set and modify
PrintXchange allows you to set and modify only certain object attributes. Generally, PrintXchange does not allow you to modify the following types of attributes: Attributes that you set or that PrintXchange sets as part of object creation, such as queue-name or job-identifier Attributes that PrintXchange sets and modifies as part of normal processing, such as object state attributes (server-state, current-job-state, etc.) This section lists the attributes by object that you are allowed to set and modify after object creation. For a complete listing and description of object attributes, refer to the PrintXchange Command Line Interface Reference Guide.
Obtaining a detailed list of attributes for your job
To display a detailed list of attributes for your job, use the pdq command with the –r verbose option. This specifies that an expanded set of attributes be written to output. For example, to display the verbose set of job attributes associated with job 123 on the logical printer log_ptr_2, enter pdq –p log_ptr_2 –r verbose server1:123 If you want to display a list of attributes for your job that includes document attributes, use the pdls command with the scope=1 attribute=value pair. For instance, to display the verbose set of job and document attributes associated with the job 123, enter: pdls –c job –r verbose –x “scope=1” server1:123
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-3 SETTING AND MODIFYING OBJECT ATTRIBUTES
Server attributes
The server attributes that you can set via the CLI and/or GUI are:
Server Attributes CLI GUI Spooler and supervisor access-control-list XX availability X cancel-individual-document-supported X configuration-attributes-visible X conformance-levels-supported X descriptor XX enabled XX events-supported X file-reference-is-local-only X job-attributes-visible-to-all X locale X locales-supported X message X modify-individual-document-supported X multiple-documents-supported X notification-delivery-methods-ready X notification-delivery-methods-supported X notification-profile X X object-class X object-classes-supported X physical-printers-ready X physical-printers-supported X server-name X X server-state X X server-type X transfer-methods-supported X Spooler only attribute driver-server XX hold-jobs-interrupted-by-printer-failure X logical-printers-ready X logical-printers-supported X queues-supported X Supervisor only filter-definition X number-of-printers-supported X maximum-number-of-printers-supported X printer-connection-methods-supported X
15-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Logical and physical printer attributes
The logical and physical printer attributes that you can set after object creation via the CLI and/or GUI are:
Logical and Physical Printer Attributes CLI GUI access-control-list XX associated-queue X X associated-server X X async-events-supported X availability X binding-edge-image-shift-max-supported X X binding-edges-supported X X bsd-printer-name X character-sets-supported X composition-prepress-supported X content-orientations-supported X X descriptor X X document-formats-supported X X document-sheets-supported X X enabled X excluded-filters X fax-resolutions-supported X X finishings-supported X X fonts-supported X input-trays-supported X X job-finishing-supported X X job-offset-supported X X job-result-set-delivery-methods-supported X X job-sheets-supported X X job-cancellation-supported X job-cancel-lib-pathname X maximum-copies-supported X X maximum-printer-speed X X max-user-job-priority X X media-supported X X message X native-document-formats-ready X notification-profile X X numbers-up-supported X X object-class X output-bins-supported X X outputs-supported X X page-select-supported X
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-5 SETTING AND MODIFYING OBJECT ATTRIBUTES
Logical and Physical Printer Attributes CLI GUI plexes-supported X X preferred-drivers X X printer-address X X printer-associated-printers X printer-connection-method X X printer-error-sheets-supported X X printer-initial-value-document X printer-initial-value-job X printer-locations X X printer-model X X printer-name X X printer-problem-message X printer-realization X printers-ready X printer-state X X printer-types X sides-supported X X sys-up-date-and-time X thickening-supported X x-image-shift-range-supported X X y-image-shift-range-supported X X Logical Printer Only max-user-job-priority X X preferred-printer-drivers X X printer-initial-value-document X printer-initial-value-job X Physical Printer Only accounting-enabled X X accounting-profile X X async-events-supported X device-query-channel-ready X device-query-channels-supported X device-query-interval X device-query-lib-pathname X device-status-query-supported X character-sets-ready X document-formats-ready X X document-sheets-ready X fax-resolutions-ready X finishings-ready X X fonts-ready X
15-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Physical Printer Only CLI GUI fonts-supported X hold-jobs-interrupted-by-printer-failure X input-trays-medium X X input-trays-ready X X job-cancel-channel-ready X job-cancel-channels-supported X job-finishing-ready X X job-offset-ready X X job-query-channel-ready X job-query-channels-supported X job-query-interval X job-query-lib-pathname X job-result-set-delivery-methods-ready X X job-sheets-ready X X job-status-query-supported X job-submission-channel-ready X job-submission-channels-supported X job-submission-lib-pathname X maximum-printer-speed X X media-ready X X mib-library-path X mib-type X native-document-formats-ready X output-bins-ready X X outputs-ready X X printer-address X X printer-baud-rate X X printer-connection-level X X printer-connection-method X X printer-connect-timeout-period X printer-data-bits X X printer-error-sheets-ready X printer-input-flow-control X X printer-model X X printer-output-flow-control X X printer-parity X X printers-ready X printer-stop-bits X X printer-timeout-period X printer-tcpip-port-number X sides-ready X X
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-7 SETTING AND MODIFYING OBJECT ATTRIBUTES
Physical Printer Only CLI GUI snmp-req-community-string X X sys-up-date-and-time X
Queue attributes
The queue attributes that you can set after object creation via the CLI and/or GUI are:
Queue Attributes CLI GUI access-control-list X X associated-server X X availability X descriptor X X disable-backlogged-queue X enabled X X logical-printers-ready X logical-printers-supported X message X notification-profile X X object-class X physical-printers-ready X physical-printers-supported X queue-name X X queue-backlog-lower-bound X queue-backlog-upper-bound X state X X
15-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Job attributes
The job attributes that you can set or modify after object creation via the CLI and/or GUI are:
Job Attributes CLI GUI accounting-information X assigned-queue X completion-time X X current-job-state X X document-sheets X X impressions-completed X initial-value-job X intervening-jobs X X job-comment X X job-copies X X job-copies-completed X job-discard-time X X job-fault-count X job-finishing X X job-hold X X job-identifier X X job-identifier-for-monitor X job-identifier-on-client X job-identifier-on-printer X job-message-from-administrator X job-name X X job-offset X X job-originating-host X job-originator X X job-owner X X job-page-count X X job-print-after X X job-priority X X job-promote-time X job-retention-period X X job-sheets X X job-state-message X X job-state-reasons X X job-submission-complete X job-submission-timeout X job-to-be-billed X X media-sheets-completed X notification-profile X
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-9 SETTING AND MODIFYING OBJECT ATTRIBUTES
Job Attributes CLI GUI number-of-documents X X object-class X output-bin (of results-profile) X X pages-completed X physical-printers-requested X previous-job-state X printer-error-sheets X X printer-name-requested X X printers-assigned X X results-profile X started-printing-time X submission-time X X total-job-octets X user-name X X
Document attributes
The document attributes that you can set or modify after object creation via the CLI and/or GUI are:
Document Attributes CLI GUI binding-edge X X binding-edge-image-shift X X bottom-margin X content-orientation X X copies-completed X copy-count X X default-character-set X default-font X default-input-tray X X default-medium X X document-file-name X X document-format X document-name X X document-sequence-number X document-state X X document-type X fax-resolution X X finishing X X footer-text X header-text X initial-value-document X
15-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Document Attributes CLI GUI left-margin X length X media-used X modification-filter X no-filtering X number-pages X number-up X X object-class X octet-count X output X X page-media-select X page-order-received X page-select X plex X X repeated-tab-stops X reset-printer X right-margin X sides X X top-margin X transfer-method X translation-filter X width X x-image-shift X X y-image-shift X X
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-11 SETTING AND MODIFYING OBJECT ATTRIBUTES
Initial-value-job attributes
The initial-value-job attributes that you can set after object creation via the CLI and/or GUI are:
Initial-value-job-attributes CLI GUI
Object attributes descriptor X messages X Job Attribute-Defaults access-control-list X associated-server X document-sheets X X initial-value-job-identifier X job-comment X X job-copies X X job-discard-time X X job-finishing X X job-hold X X job-name X X job-offset X X job-print-after X X job-priority X X job-retention-period X X job-sheets X X job-to-be-billed X X object-class X output-bin X X physical-printers-requested X printer-error-sheet X X results-profile X
15-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Initial-value-document attributes
The initial-value-document attributes that you can set after object creation via the CLI and/or GUI are:
Initial-value-document-attributes CLI GUI
Object attributes descriptor X messages X Initial-value-document-attributes access-control-list X associated-server X binding-edge X X binding-edge-image-shift X X content-orientation X X copy-count X X default-character-set X default-font X default-input-tray X X default-medium X X document-file-name X document-format X document-name X document-type X finishing X X initial-value-document-identifier X number-up X X object-class X output X X page-media-select X page-select X plex X X reset-printer X sides X X x-image-shift X X y-image-shift X X
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-13 SETTING AND MODIFYING OBJECT ATTRIBUTES
Supported MIB types
The following table list the attributes supported per Management Information Base (MIB) type of object. The Xerox supervisor reads these attributes from the printer’s MIB and converts them into supported and ready attributes if the printer is an SNMP device status enabled printer. Note: The printer’s MIB supports and implementation affect the Xerox supervisors’ capability to obtain each status.
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm
Printer printer-state idle y --- y
printing y --- y
needs-attention y --- y
needs-key-operator y --- y
paused y --- n
shutdown y --- n
unknown y --- y
timed-out y --- y
printer-problem- low paper n --- y message
no paper y --- y
no cassette y --- n
input tray fail y --- n
output tray fail y --- n
bad paper size y --- n
output tray full y --- n
cover open y --- y
jammed y --- y
low toner n --- y
no toner y --- y
used toner near full n --- n
used toner full n --- n
drum life near n --- n
15-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm exhausted
drum life exhausted y --- n
no drum y --- n
duplex fail y --- n
service requested n --- y
offline n --- y
problem unknown n --- n reason
input-trays-supported 1 y --- y
2 y --- y
3 y --- y
4yny
5nny
6nny
7nny
8nny
9 n --- y
10 n --- y
manual y --- y
manual-2 n n y
manual-3 n n y
top n n y
middle n n y
bottom n n y
main n n y
side n n y
large_capacity n n y
envelope n n y
input-trays-ready * same as input-trays- y --- y supported
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-15 SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm
media-ready na-letter-white y --- y
na-legal-white y --- y
na-number-10- y --- y envelope
monarch-envelope y --- y
iso-a3-white y --- y
iso-a4-white y --- y
iso-a5-white y --- y
iso-c5-envelope y --- y
iso-designated-long- y --- y envelope
jis-b4-white y --- y
jis-b5-white y --- y
medium-a n --- y
medium-b n --- y
medium-c n --- y
medium-d n --- y
medium-e n --- y
ledger y n y
folio y n y
hagaki-white y n y
medium-default y --- y
other media defined by nny DPA
input-tray-medium * defined by y --- y combination of input- trays-supported and media-ready
output-bins-supported face-up y --- n
face-down y --- n
center y --- n
side y --- y
15-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm
mailbox-1 y --- n
mailbox-2 y --- n
mailbox-3 y --- n
mailbox-4 y --- n
mailbox-5 y --- n
mailbox-6 y --- n
mailbox-7 y --- n
mailbox-8 y --- n
mailbox-9 y --- n
mailbox-10 y --- n
stacker-1 n n y
stacker-2 n n y
stacker-3 n n y
top n n y
middle n n y
bottom n n y
left n n y
right n n y
large n n y
private n n y
1nny
2nny
3nny
4nny
5nny
6nny
7nny
8nny
9nny
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-17 SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm
10 n n y
11 n n y
12 n n y
13 n n y
14 n n y
15 n n y
16 n n y
17 n n y
18 n n y
19 n n y
20 n n y
21 n n y
22 n n y
23 n n y
24 n n y
25 n n y
output-bins-ready * same as output-bins- y --- y supported
document-formats- Document formats that ynn supported are supported on the output device
document-formats- Document formats that ynn ready are ready on the output device
native-document- Document formats that ynn formats-ready are ready to use on the output device itself
sys-up-date-and-time an appropriate value y --- n shall be given in generalizedTimeSyntax
Job current-job-status completed y --- n
job-state-reasons successful-completion y --- n
complete-with-warning y --- n
15-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-1. Attributes supported per MIB type
MAM supporting
Object Class Attribute Name Attribute Value fxopsmm fxlwomm fx1759mm
abort-by-system y --- n
job-message-from- an appropriate n --- n administrator message shall be given.
pages-completed an appropriate value ynn shall be given in cardinal syntax
total-job-octets an appropriate value n --- n shall be given.
media-sheets- an appropriate value y --- n completed shall be given in cardinal syntax.
Setting mapping attributes
Mapping attributes refer to those attributes that associate logical printers, physical printers, and queues. You submit jobs to logical printers and the spooler holds the jobs in queues until it schedules them on a physical printer. More than one logical printer can feed one queue and one queue can feed more than one physical printer. However, a specific logical printer can feed only one queue and a specific physical printer can receive jobs from only one queue. Specific attributes control the mapping among logical printers, queues, and physical printers. The table below lists the mapping attributes for each of the relevant objects. You control the mapping by setting the attribute associated-queue on logical and physical printers. PrintXchange then maintains the remaining mapping attributes. The following table describes when PrintXchange updates the attributes. You can not change the value of the associated-queue of a physical printer unless the physical printer is disabled and its state is idle. Setting associated-queue on a physical printer causes the supervisor to set printer-associated-printers on the physical printer to empty (PrintXchange initializes printer-associated-printers when you enable the physical printer). In addition, if associated-queue has had a value, the spooler associated with that value must be up or the attribute modification fails. The spooler removes the physical printer from the spooler and the queue’s physical-printers- supported attribute and from the associated logical printer’s printer- associated-printers attribute.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-19 SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-2. Printer mapping attributes
Object Attribute Description
Logical associated-queue Set by administrator. printer
printer-associated- Lists the physical printers supported by the associated queue. printers This attribute is always the same as the associated queue’s physical-printers-supported attribute.
printers-ready Lists the enabled physical printers on the associated queue.
This attribute is always the same as the associated queue’s physical-printers-ready attribute.
Queue logical-printers- Lists the logical printers that have an associated-queue attribute supported that points to this queue.
This attribute is updated when a logical printer is created or deleted and when the associated-queue attribute of a logical printer is set (either by pdset or, implicitly, by pdcreate).
logical-printers-ready Lists the enabled logical printers that have an associated-queue attribute that points to this queue.
This attribute is updated when a logical printer is enabled or disabled. Logical printer creation or deletion does not update it, since a printer must be disabled to be deleted.
physical-printers- Lists the physical printers that have an associated-queue attribute supported that points to this queue.
This attribute is updated when a physical printer is created or deleted, but is not updated by physical printer creation.
physical-printers-ready Lists the enabled physical printers that have an associated-queue attribute that points to this queue.
This attribute is updated when a physical printer is enabled or disabled. Physical printer creation or deletion does not update it, since a printer must be disabled to be deleted.
15-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-2. Printer mapping attributes (continued)
Object Attribute Description
Physical associated-queue Set by administrator. printer
printer-associated- Lists the logical printers supported by the associated-queue. printers This attribute is initialized when the physical printer is enabled. It is updated when an associated logical printer is deleted or has its associated-queue attribute modified. It is also updated if the queue is deleted.
printers-ready Lists the enabled physical printers on the associated queue.
This attribute is always the same as the associated queue’s physical-printers-ready attribute.
Server physical-printers- Lists all physical printers that are associated with all queues or supported spoolers. Spooler
printers-ready Lists the enabled physical printers that are associated with all queues or spoolers.
This attribute is always the same as the associated queue’s physical-printers-ready attribute.
logical-printers- Lists all logical printer registered in the spooler. supported
logical-printers-ready Lists all enabled logical printers on the spooler.
Supervisor physical-printers- Lists all physical printers on the supervisor. supported
printers-ready Lists all enabled physical printers on the supervisor.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-21 SETTING AND MODIFYING OBJECT ATTRIBUTES
Setting xxx-supported and xxx-ready attributes
PrintXchange supports a number of attributes with names of the form xxx-supported and xxx-ready, such as document-formats- supported and document-formats-ready. These attributes are generally associated with printers, both logical and physical. Refer to the list of logical and printer attributes in the “Allowed attributes for set and modify” section. PrintXchange uses the xxx-supported and xxx-ready attributes to: Indicate the capabilities of a particular printer (output device) to help you choose an appropriate printer Ensure that a server rejects a job requiring a particular capability that the specified printer (output device) does not support. An xxx-supported attribute indicates that the feature is supported by at least one associated printer, but not necessarily right now. An xxx-ready attribute indicates that a physical printer supports the feature and the physical printer can use the feature right now without human intervention: Only physical printers support xxx-ready attributes. Both physical and logical printers support xxx-supported attributes; a logical printer uses them when a job is submitted, a physical printer when a logical printer is enabled. Generally, the xxx-supported and xxx-ready attributes have identical values, but some features require an operator’s intervention to become operational. For example, someone may have to replace a paper tray so that a particular medium becomes available. In this case the spooler accepts the job but does not print it until an operator replaces the paper tray and sets the corresponding physical printer attribute to ready. The physical printer creation process sets most of the xxx- supported and xxx-ready attributes to appropriate and identical values. However, as the administrator, you can modify these attributes. For example, if a printer has the capability to print envelopes but you decide not to stock envelopes, you can remove envelopes from the media-supported attribute. When you enable a logical printer, each of its xxx-supported attributes that have no value inherit the xxx-supported attribute values from its associated physical printer(s). If you set a logical printer xxx-supported attribute before the enable, the value is not changed; but if it was empty, it acquires values from the corresponding xxx-supported attribute of the associated physical printer(s). You can change xxx-supported and physical printer xxx-ready attributes to set local policy. Note, however, that PrintXchange does not check to ensure that an xxx-ready attribute value is included on the corresponding xxx-supported attribute. Therefore, you should make sure that every xxx-ready value is included in the corresponding xxx-supported attribute. The following tables associate job or document attributes with printer or server attributes that the spooler uses to accept or schedule a job. Note that where there is no xxx-ready attribute for a corresponding xxx-supported attribute, the spooler uses the already assigned xxx- supported value to schedule the job on the printer.
15-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
If you are modifying a retained job (to prepare for resubmission), attribute validation does not take place for the current logical printer. When the job is resubmitted to a logical printer that feeds appropriate physical printers, validation for the new printer will be performed.
Table 15-3. Job attributes matched to printer attributes
Printer Attribute
Job Attribute Attribute spooler uses for Attribute spooler uses for accepting scheduling
document-sheets document-sheets-supported document-sheets-ready
job-copies* maximum-copies-supported maximum-copies-supported
job-finishing job-finishings-supported job-finishings-ready
job-offset job-offsets-supported job-offsets-ready
job-sheets job-sheets-supported job-sheets-ready
output-bin* output-bins-supported output-bins-ready
physical-printers-requested printer-associated-printers printer-associated-printers
printer-error-sheet ** printer-error-sheets-ready
results-delivery-method* job-result-set-delivery-methods- job-result-set-delivery-methods- supported supported
* results-delivery-method, job-copies, and output-bin are elements of the attribute results-profile and should not be set as values for the job-attribute-visible-to-all server attribute. This is used in conjunction with the document-copy- count attribute. Refer to Copy-count attribute notes in Table 15-4, “Document attributes matched to printer attributes.”
**The spooler does not do acceptance checking for printer-error-sheet (even though there is a corresponding printer attribute (printer-error-sheets-supported).
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-23 SETTING AND MODIFYING OBJECT ATTRIBUTES
Table 15-4. Document attributes matched to printer attributes
Printer Attribute Document Attribute Attribute spooler uses for Attribute spooler uses for accepting scheduling
Binding-edge binding-edges-supported binding-edges-supported Binding-edge-image-shift binding-edge-image-shift-max- binding-edge-image-shift-max- supported supported Copy-count* maximum-copies-supported maximum-copies-supported Content-orientation content-orientations-supported content-orientations-supported default-character-set character-sets-supported character-sets-ready default-font fonts-supported fonts-ready default-input-tray input-trays-supported input-trays-ready default-medium media-supported media-ready document-format document-formats-supported. document-formats-ready. fax-resolution fax-resolutions-supported fax-resolutions-ready finishing finishings-supported finishings-ready gamut-mapping-method-used gamut-mapping-methods-supported gamut-mapping-methods-ready highlight-colour highlight-colours-supported highlight-colours-ready highlight-colour-rendering- highlight-colour-rendering- highlight-colour-rendering-algorithms- algorithm algorithms-supported supported highlight-colour-mismatch- highlight-colours-supported highlight-colours-ready action highlight-mapping-colour highlight-mapping-colours-supported highlight-mapping-colours-supported number-up numbers-up-supported numbers-up-supported output outputs-supported outputs-ready page-select page-select-supported page-select-supported plex plexes-supported plexes-supported print-colour-type-used print-colour-types-supported print-colour-types-ready sides sides-supported sides-ready thickening-specification thickening-supported thickening-supported x-image-shift x-image-shift-range-supported x-image-shift-range-supported y-image-shift y-image-shift-range-supported y-image-shift-range-supported
* Used in conjunction with job-copies attribute for each document (copy-count x job-copies) must be <= maximum-copies supported.
15-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
Print data processing attributes
In processing the print request and the associated print data, the spooler applieswhen applicablecertain attribute values that affect how it processes print data. This section discusses the relevant print data processing attributes, and presents the attributes in the following groupings: Document formats Imaging parameters.
Document formats
The document format identifies data syntax used to encode the final printed form of a document. Commonly used document formats include simple-text, PostScript, and PCL. PrintXchange uses several attributes to determine the document format of a specific document and to determine whether or not the destination output device supports the specified document format. The attributes are: document-format (document attribute) document-formats-supported (logical and physical printer attribute) document-formats-ready (physical printer attribute) native-document-formats-ready (physical printer attribute) The spooler sends a document to a supervisor only if the physical printer’s document-formats-ready attribute matches the document’s document-format attribute. The physical printer’s document- formats-supported and document-formats-ready attributes must include the value of a document’s document-format attribute. The printer attribute file you specified when creating a physical printer sets the document-formats-supported and document-formats- ready values that are valid for the corresponding output device. If a document format is listed on a printer’s document-formats- ready attribute, but not on the printer’s native-document-formats- ready attribute, then there must be a translation filter that translates the document format to one of the printer’s native formats. If there is no such filter, PrintXchange aborts the remainder of the job. You should install the proper filters to bridge the gap between the formats supported by the output device (native-document-formats-ready) and the physical printer object (document-formats-ready). If document-format is empty and the physical printer’s native- document-formats-ready attributes only value is PostScript, the supervisor: Looks at the first two bytes. If the bytes are %!, the supervisor assumes that the document is PostScript and sends it directly to the printer. Look at the first three bytes. If the bytes are ^D%!, the supervisor assumes that the document format is PostScript and sends the document directly to the printer. If neither of the two checks is true, the supervisor assumes that the document is simple-text and translates it to PostScript.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-25 SETTING AND MODIFYING OBJECT ATTRIBUTES
If document-format is empty and the printer’s native-document- formats-ready attribute includes values other than PostScript (or in addition to), the supervisor simply sends the document directly to the printer. No special processing is provided for automatic document format as a value included on a printer’s native-document-formats-ready attribute.
Imaging parameters
Imaging parameters refer to attributes that affect the image of the print data on the output page. The attributes are the following document attributes: default-character-set default-font sides and plex content-orientations-supported and number up x-image-shift and y-image-shift page-select page-media-select page-order-received. Default-character-set The default-character-set attribute identifies a coded character set that the spooler uses for the pages of a document that require a coded character set specification. On job submission, the spooler checks for a match with the logical printer’s character-sets-supported attribute. If there is no match, the spooler rejects the print request. The spooler checks for a match with the physical printer’s character-sets-ready attribute. If there is no match, the spooler leaves the job pending. The reference supervisor is capable of handling print data streams of any character set. It does not make assumptions about character width, lexicographic order, null string-termination, or case conversion when transporting document data to a printer. For certain printers, the supervisor sends a command to the printer that causes the specified character set to be active while printing the document. To set the default-character-set: GUI: This function is not accessible with the GUI. CLI: pdset -c document -x "default-character-set=value" [spooler_name:]job_identifier.doc_integer value refers to the object identifier for the character set. For a complete listing the character sets, refer to the PrintXchange Command Line Interface Reference Guide.
15-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
default-font The default-font document attribute identifies the font that the spooler uses for document pages that do not otherwise specify a font. On job submission, the spooler checks for a match with the logical printer’s fonts-supported attribute. If there is no match, the spooler rejects the print request. The spooler checks for a match with the physical printer’s fonts- ready attribute. If there is no match, the spooler leaves the job pending. The supervisor ignores the default-font attribute. To set the default-font: GUI: This function is not accessible with the GUI. CLI: pdset -c document -x "default-font=value" [spooler_name:]job_identifier.doc_integer Refer to the PrintXchange Command Line Interface Reference Guide. sides and plex Two document attributes determine the placement of the image on the output page: sides plex On job submission, the spooler checks for a match with the logical printer’s corresponding sides-supported or plexes-supported attribute. If there is no match, the spooler rejects the print request. The spooler checks for a match with the physical printer’s corresponding sides-ready or plexes-supported attribute. If there is no match, the spooler leaves the job pending. sides - The sides attribute specifies if the job should be printed on one or two sides of the paper. The default is the printer default. To set the sides attribute: GUI: This function is not accessible with the GUI. CLI: pdset -c document -x "sides=2" [spooler_name:]job_identifier.doc_integer Refer to the PrintXchange Command Line Interface Reference Guide. plex - The plex attribute indicates whether the page images should be conditioned for eventual 1- or 2-sided printing. That is, printing that will take into account extra space for binding margins. The three values for plex are: simplex, document pages to be conditioned for 1-sided printing duplex, document pages to be conditioned for 2-sided printing (head-to-head printing) tumble, document pages to be conditioned for 2-sided printing (head-to-toe printing)
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-27 SETTING AND MODIFYING OBJECT ATTRIBUTES
Figure 15-1 illustrates the difference between plex and tumble 2-sided printing. PrintXchange supports the plex attribute only for certain printers. For more information, refer to the “Printer data sheets” appendix.
Figure 15-1. Plex and tumble printing
Duplex (Head-to-head printing)
Binding Binding edge on edge on left right
Back Side y=0 y=0 Front Side
Tumble (Head-to-toe printing)
y=0 Binding Binding edge on top edge on top
Back Side y=0 Front Side
content-orientations-supported Two attributes determine the orientation and number of page images and number-up on the output page: content-orientations-supported (logical and physical printer attribute) number-up (document attribute) On job submission, the spooler checks for a match with the logical printer’s corresponding content-orientations-supported or numbers-up-supported attribute. If there is no match, the spooler rejects the print request. The spooler checks for a match with the physical printer’s corresponding content-orientations-supported or numbers-up- supported attribute. If there is no match, the spooler leaves the job pending.
15-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES
content-orientations-supported The content-orientations-supported attribute identifies the content orientations supported by the logical and physical printer. The valid values are: portrait landscape reverse-portrait reverse-landscape. The content orientation and number-up values work together to determine the positioning of the image on the page. The following figure shows the content orientation with number-up=0.
Figure 15-2. Number-up printing
portrait reverse-portrait landscape reverse-landscape
number-up The number-up attribute specifies the number of page-images to impose on one side of a sheet: none or 0 (this value suppresses any spooler default) simple-1-up or 1 simple-2-up or 2 simple-4-up or 4 The value none (or 0). x-image-shift and y-image-shift The x-image-shift and y-image-shift attributes cause page images to be shifted in position with respect to the media on which the page images are to be rendered. The direction of the shift is parallel to the corresponding x- or y-axis of the Reference Coordinate System (RCS). You can use these attributes to enable a user/client to request a different margin, possibly to correct a misalignment. The sign of the attribute value indicates the direction of shift. A positive value indicates that the shift is in the positive x- or y- direction, and a negative value indicates that the shift is in the negative x- or y- direction. The shift direction is the same for all pages, regardless of the value of the plex attribute. The physical and logical printer attributes x-image-shift-range- supported and y-image-shift-range-supported identify the range supported by the printer. The spooler compares x-image-shift against x-image-shift-range- supported and ensures that x-image-shift is greater than or equal to the lower bound and less than or equal to the upper bound. The same rule applies to y-image-shift and y-image-shift-range- supported.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-29 SETTING AND MODIFYING OBJECT ATTRIBUTES
Updating the OID database
PrintXchange consists of data entities that specify the function of the printing system, including: Objects that the printing system supports (spooler, supervisor, queue, logical printer, physical printer, job, document, initial-value-job, initial-value-document) Object-classes that group specific objects by certain general categories (server, printer, job, document, initial-value-job, initial- value document) Operations that may be applied to supported objects (create, delete, clean, remove, pause, resume, enable, disable, set, modify, print, list, promote, resubmit, shutdown) Attributes that describe the characteristics and states of an object (server-name, current-job-state, default-font, highlight- mapping-colour, etc.) Attribute syntaxes that identify attribute data types (booleanSyntax, cardinalSyntax, finishingSyntax, nameOrOidSyntax) Attribute value classes that identify categories of values for attributes (medium, highlight-colour, input-tray,…) Attribute values of a given value class that identify a specific object characteristic (na-letter-white for medium value class, red for highlight-colour value class.) Event classes that identify categories of values for events (aborted, error, warning, report, state-changed,…) Events of a given event class that indicate the effect of an operation on an object (error-past-discard-time, report-job- promoted, warning-resource-needs-attention,…) PrintXchange uniquely identifies each and every data entity with an object identifier (OID). The object identifier has a name with a format represented by the following example: id-att-printer-state The object identifier name has an equivalent integer value with dot ( . ) delimiters (called the decimal OID) with a format represented by the following example: 1.0.10175.1.3.2.8. PrintXchange includes a database that contains object identifiers for all of its data entities. With PrintXchange, users can update the OID database by creating and adding to the database their own attributes, attribute value classes, and attribute values.
15-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SETTING AND MODIFYING OBJECT ATTRIBUTES pdaddoid utility
The pdaddoid utility enables users to create attributes, attribute value classes, and attribute values, and add them to the OID database. The pdaddoid utility has the following command line syntax: pdaddoid -f inputFile [-h] (help switch) -O OIDpath [-p] [-v] Attributes created by users will be accessible only via the CLI.
Input file switch [-f inputFile]
The -f switch tells pdaddoid to add the attributes, attribute value classes, and/or attribute values defined in the inputFile into the OID database. Each of the inputFile entries must have the following format with the -odecimalOID on a separate line:
Help switch [-h]
The -h switch tells pdaddoid to print out a usage message. If the -h switch is specified, then pdaddoid only prints out the usage message and does not do anything else, even if other switches have also been specified.
OID database path switch -O OIDpath
The required -O switch tells pdaddoid where the object identifier database files are located if they are not located in the standard directory. The standard directories for the database files are: %PX-ROOT%\share\oid
Preview switch [-p]
The -p switch tells pdaddoid to process the input file to check for validity of the entries but without adding anything to the database.
Verbose switch [-v]
The -v switch tells pdaddoid to display the following items for each entry as it adds the entry to the database: line :
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 15-31 SETTING AND MODIFYING OBJECT ATTRIBUTES pdshowoid utility
The pdshowoid utility enables users to display any attributes in the OID database. The pdshowoid utility has the following command line syntax: pdshowoid -r attributeNames [-h] (help switch) [-O OIDpath]
List requested attributes switch -r attributeNames
The -r switch tells pdshowoid to display a listing of information in the OID database for specified attributes. The user may specify the complete attribute name or an abbreviation or a decimal OID. For example: pdshowoid -r attribute-1 or pdshowoid -r attr-1 pdshowoid –r “attribute-1 attr-1 1.123.55.12.17.3.0”
OID database path switch [-O OIDpath]
The pdshowoid utility also takes -O flag (optional) for the oid database path. However, unlike pdaddoid, if the OID database path is not explicitly specified, it uses the default path. %PX-ROOT%\share\oid
Help switch [-h]
The -h switch tells pdshowoid to print out a usage message. If the -h switch is specified, then pdshowoid only prints out the usage message and does not do anything else, even if other switches have also been specified. Note: Contact Technical Support for assistance using all OID utilities.
15-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 16. Pausing and resuming objects
This chapter discusses the most common server-management operations and covers pausing and resuming objects: Servers (Spoolers) Queues Physical printer. This chapter explains the commands used to perform these operations at a very high level. For more information on all PrintXchange commands and attributes, refer to the PrintXchange Command Line Interface Reference Guide. Pausing an object causes the object to stop output. A paused object can continue to accept new requests. You can also run other operations on a paused object such as listing its status, or setting or modifying its attributes. Resuming an object causes the object to continue normal operations for producing output.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 16-1 PAUSING AND RESUMING OBJECTS
Pausing and resuming PrintXchange objects
Administrators and operators can pause and resume objects using CLI commands or the GUI Administration Tool. Refer to the GUI online help for details on using this method.
Pausing objects using GUI
To pause an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Spoolers, Supervisors, Queue, or Physical Printers). 3. Select the object to pause. 4. Invoke the Pause button.
Resuming objects using GUI
To resume an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Spoolers, Supervisors, Queue, or Physical Printers). 3. Select the object to pause. 4. Invoke the Resume button.
Pausing and resuming objects using CLI
To pause an object use the following command: pdpause [-c class_name] object_instance To resume an object use the following command: pdresume [-c class_name] object_instance
class_name object_instance server spooler_name queue queue_name printer (default) physical_printer_name job [spooler_name:]job_identifier Other switches available for the pdpause and pdresume commands include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] For more information, refer to the PrintXchange Command Line Interface Reference Guide.
16-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PAUSING AND RESUMING OBJECTS
Pausing spoolers
A paused spooler stops submitting jobs to supervisors. However, the spooler continues to accept new print requests for its associated logical printers. When you pause a spooler, the spooler: Changes the value of its server-state attribute to paused Continues to accept requests for other operations such as listing its status, or setting or modifying its attributes. Pausing a spooler does not affect any of the spooler objects (logical printers, queues, and jobs) in any way.
Pausing a spooler using GUI
To pause a spooler using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Spoolers). 3. Select the object to pause. 4. Invoke the Pause button.
Pausing a spooler using CLI
To pause a spooler named spooler1 with a CLI command, use: pdpause -c server spooler1
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 16-3 PAUSING AND RESUMING OBJECTS
Resuming spoolers
A resumed spooler resumes distributing print jobs to all of its associated supervisors. When you resume a spooler, the spooler changes the value of its server-state attribute to ready.
Resuming a spooler using GUI
To resume an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Spoolers). 3. Select the object to pause. 4. Invoke the Resume button.
Resuming a spooler using CLI
To resume the spooler named spooler1 with a CLI command, use: pdresume -c server spooler1
16-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PAUSING AND RESUMING OBJECTS
Pausing queues
A paused queue causes the associated spooler to stop submitting jobs to the queue’s associated physical printers. However, the spooler continues to accept new print requests for the queue’s associated logical printers. When you pause a queue: The queue’s associated spooler changes the value of the queue’s state attribute to paused. You can still run operations on the queue such as list its status, or set or modify its attributes. Pausing a queue does not affect any of its associated logical printers or jobs in any way.
Pausing a queue using GUI
To pause an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Queue). 3. Select the object to pause. 4. Invoke the Pause button.
Pausing a queue using CLI
To pause the queue “color_q” with a CLI command, use: pdpause -c queue color_q
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 16-5 PAUSING AND RESUMING OBJECTS
Resuming queues
A resumed queue causes the associated spooler to resume submitting jobs to the queue’s associated physical printers. When you resume a queue, the queue’s associated spooler changes the value of the queue’s state attribute to ready.
Resuming a queue using GUI
To resume an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Queue,). 3. Select the object to pause. 4. Invoke the Resume button.
Resuming a queue using CLI
To resume the queue “color_q” with a CLI command, use: pdresume -c queue color_q
16-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PAUSING AND RESUMING OBJECTS
Pausing physical printers
A paused physical printer causes the spooler associated with the physical printer’s supervisor to stop scheduling jobs for the physical printer. When you pause a physical printer: The physical printer stops a currently printing job as soon as the physical printer can do so. When you resume the physical printer, it prints the paused job from where it left off. If the physical printer is not printing a job when you pause it, it does not start printing a job until you resume it. The physical printer’s printer-state attribute is changed to paused.
Pausing a physical printer using GUI
To pause an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Physical Printers). 3. Select the object to pause. 4. Invoke the Pause button.
Pausing a physical printer using CLI
To pause the physical printer “highcap” with a CLI command, use: pdpause -c printer highcap or pdpause highcap
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 16-7 PAUSING AND RESUMING OBJECTS
Resuming physical printers
A resumed physical printer starts the paused printer. When you resume a physical printer: The physical printer resumes printing its currently assigned print job, if any, from the point where it stopped printing the job. The physical printer’s printer-state attribute is changed to printing or idle.
Resuming a physical printer using GUI
To resume an object using GUI: 1. Run the Administration Tool 2. In the right menu, select the appropriate type of object (Physical Printers). 3. Select the object to pause. 4. Invoke the Resume button.
Resuming a physical printer using CLI
To resume the physical printer “highcap” with a CLI command, use: pdresume -c printer highcap or pdresume highcap
16-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17. Enabling and disabling objects
This chapter discusses the most common server-management operations and covers enabling and disabling the following objects: Servers (Spoolers, Supervisors) Queues Physical printers Logical printers. This chapter explains the commands to use to perform these operations at a very high level. For details on all PrintXchange commands and attributes, refer to the PrintXchange Command Line Interface Reference Guide. Enabling an object allows the object to accept new print requests or jobs. Disabling an object prevents the object from accepting new print requests or jobs. Although an object is disabled, you can still run other operations on the object such as listing its status, or setting or modifying its attributes.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17-1 ENABLING AND DISABLING OBJECTS
Enabling and disabling PrintXchange objects
Administrators can enable and disable objects using CLI commands or the GUI Administrator Tool. Refer to the GUI online help for details on using this method.
Enabling objects using GUI
1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Spoolers, Supervisors, Queues, Logical Printers, or Physical Printers). 3. Select the object to enable. 4. Invoke the enable button.
Disabling objects using GUI
1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Spoolers, Supervisors, Queues, Logical Printers, or Physical Printers). 3. Select the object to disable. 4. Invoke the disable button.
Enabling and disabling objects using CLI
To enable an object: pdenable [-c class_name] object_instance To disable an object: pddisable [-c class_name] object_instance
class_name object_instance server spooler_name server supervisor_name queue queue_name printer (default) logical_printer_name printer (default) physical_printer_name Other switches available for the pdenable and pddisable commands include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] Refer to the PrintXchange Command Line Interface Reference Guide.
17-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT ENABLING AND DISABLING OBJECTS
Enabling spoolers and supervisors
An enabled spooler accepts new client print requests that are directed to any of its associated logical printers. Note: In addition to an enabled spooler, the specified logical printer and its associated queue must also be enabled in order to accept print jobs. An enabled supervisor accepts new jobs for printing on any of its associated physical printers (if a specified physical printer is itself enabled).
Enabling spoolers and supervisors using GUI
To enable a spooler or supervisor using the GUI: 1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Spoolers or Supervisors). 3. Select the object to enable. 4. Invoke the enable button.
Enabling spoolers and supervisors using CLI
To enable the spooler named spooler1 with a CLI command, use: pdenable -c server spooler1 To enable the supervisor “big_super” with a CLI command, use: pdenable -c server big_super
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17-3 ENABLING AND DISABLING OBJECTS
Disabling spoolers and supervisors
A disabled spooler rejects all new client print requests that are directed to any of its associated logical printers. When you disable a spooler, the spooler continues to: Schedule and deliver previously submitted jobs to physical printers for printing Accept requests for other operations such as listing its status, or setting or modifying its attributes A disabled supervisor rejects all new jobs for printing on any of its associated physical printers. When you disable a supervisor, the supervisor continues to: Complete printing any jobs already on the supervisor. Accept requests for other operations such as listing its status, or setting or modifying its attributes.
Disabling spoolers and supervisors using GUI
To disable a spooler using the GUI: 1. Run the Administration Tool 2. In the right menu, select the desired type of object (Spoolers or Supervisors). 3. Select the object to disable. 4. Invoke the disable button.
Disabling spoolers and supervisors using CLI
To disable the spooler named spooler1 with a CLI command, use: pddisable -c server spooler1 To disable the supervisor “big_super” with a CLI command, use: pddisable -c server big_super
17-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT ENABLING AND DISABLING OBJECTS
Enabling queues
An enabled queue allows its associated spooler to accept new print requests for all of the queue’s associated logical printers. Note: In addition to an enabled queue, the designated logical printer and spooler must also be enabled in order to accept jobs.
Enabling queues using GUI
To enable a queue using the GUI: 1. Run the Administration Tool 2. In the right menu, select the desired type of object (Queue). 3. Select the object to enable. 4. Invoke the enable button.
Enabling queues using CLI
To enable the queue “color_q” with a CLI command, use: pdenable -c queue color_q
Disabling queues
A disabled queue causes its associated spooler to reject new print requests for any of the queue’s associated logical printers. Disabling a queue does not cause any changes to the associated logical printers. That is, the disable operation does not affect the current value of any logical printer’s printer-state attribute.
Disabling queues using GUI
To disable a queue using the GUI: 1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Queue). 3. Select the object to disable. 4. Invoke the disable button.
Disabling queues using CLI
To disable the queue “color_q” with a CLI command, use: pddisable -c queue color_q
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17-5 ENABLING AND DISABLING OBJECTS
Enabling physical printers
An enabled physical printer allows its associated supervisor to request new print jobs for that physical printer. Note: In addition to the physical printer to be enabled, the supervisor must be enabled in order to accept jobs for the physical printer. Also, the spooler that supports the physical printer’s supervisor must be running. When you successfully enable a physical printer: The associated supervisor adds the name of the physical printer to the supervisor’s physical-printers-ready attribute. The spooler supporting the relevant supervisor adds the name of the physical printer to the physical-printers-ready attribute for the spooler and for the associated queue. Before you can enable a physical printer, the following conditions must be true: The value of the physical printer attribute associated-queue must be the name of a queue that exists. The attribute printer-address must have a valid value. The –X filename.paf must be specified during creation of the printer to ensure that all required settings have values. Required attributes specified by the paf include the following: The attribute printer-model. If the type of supervisor is Xerox, additional attributes are specified in the .paf file and automatically set. The job-submission-channels-supported attribute describes the type of lpr (RFC 1179) that is supported for the printer. If the device provides the capability of obtaining the status of the printer using SNMP, lpq, or Xerox production printing status the attribute device-status-query-supported is set to true. If the printer provides the capability of canceling the job (e.g. lprm), the attribute job-cancel-supported is set to true. If the device provides the capability of obtaining the status of jobs using SNMP or Xerox production printing status the attribute job- status-query-supported is set to true Through the GUI or CLI, each channel can be enabled or disabled and the query interval period for each channel can be set to a different value. The associated attributes are: Device-query-channel-ready Device-query-interval Job-query-channel-ready Job-query-interval Job-cancel-channel-ready.
17-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT ENABLING AND DISABLING OBJECTS
Enabling physical printers using GUI
To enable a physical printer using the GUI: 1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Physical Printers). 3. Select the object to enable. 4. Invoke the enable button.
Enabling physical printers using CLI
To enable the physical printer “highcap” with a CLI command, use: pdenable -c printer highcap
Disabling physical printers
A disabled physical printer causes its associated supervisor to reject new print jobs for that physical printer. Before you can disable a physical printer, the spooler that supports the physical printer’s supervisor must be running. When you successfully disable a physical printer: The physical printer completes any currently printing jobs. The associated supervisor deletes the name of the physical printer from the supervisor’s physical-printers-ready attribute. The spooler supporting the relevant supervisor deletes the name of the physical printer from the physical-printers-ready attribute for the spooler and for the associated queue.
Disabling physical printers using GUI
To disable a physical printer using the GUI: 1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Physical Printers). 3. Select the object to disable. 4. Invoke the disable button.
Disabling physical printers using CLI
To disable the physical printer “highcap” with a CLI command, use: pddisable -c printer highcap
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17-7 ENABLING AND DISABLING OBJECTS
Enabling logical printers
An enabled logical printer allows its associated spooler to accept new print requests directed to that logical printer. Note: In addition to the logical printer being enabled, the associated queue and server must be in order to accept print jobs. Before you can enable a logical printer, the value of the logical printer attribute associated-queue must be the name of a queue that exists. When you successfully enable a logical printer, the associated spooler: Adds the name of the logical printer to the logical-printers- ready attribute for the associated spooler and for the associated queue Adds the name of the logical printer to the printers-ready attribute for all associated physical printers.
Enabling logical printers using GUI
To enable a logical printer using the GUI: 1. Run the Administration Tool. 2. In the right menu, select the desired type of object (Logical Printers). 3. Select the object to enable. 4. Invoke the enable button.
Enabling logical printers using CLI
To enable the logical printer “redhighlight” with a CLI command, use: pdenable -c printer redhighlight or pdenable redhighlight
17-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT ENABLING AND DISABLING OBJECTS
Disabling logical printers
A disabled logical printer causes its associated spooler to reject new print requests directed to that logical printer. When you successfully disable a logical printer, the associated spooler : Removes the name of the logical printer from the logical- printers-ready attribute for the associated spooler and for the associated queue. Removes the name of the logical printer from the printers-ready attribute on its associated physical printers.
Disabling logical printers using GUI
To disable a logical printer using the GUI: 1. Run the Administration Tool. 2. 3. In the right menu, select the desired type of object (Logical Printers). 4. Select the object to disable. 5. Invoke the disable button.
Disabling logical printers using CLI
To disable the logical printer “redhighlight” with a CLI command, use: pddisable -c printer redhighlight or pddisable redhighlight
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 17-9 ENABLING AND DISABLING OBJECTS
17-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18. Removing (deleting) objects
This chapter discusses the most common server-management operations and covers removing (deleting) the following: Servers (Spoolers) Queues Physical printers Logical printers Initial-value-job Initial-value-document. As your system grows and changes, you will find cause to remove objects. Removing an object deletes all information regarding that object from the object database. You can use the CLI or the GUI to remove all objects including servers, jobs, and documents. Note: For procedures on deleting jobs and documents, refer to the “Managing jobs and documents” chapter. This chapter explains the commands used to perform these operations at a very high level. For details on all commands and attributes, refer to the PrintXchange Command Line Interface Reference Guide.
Removing (deleting) PrintXchange objects
PrintXchange has several operations that allow you to remove or delete objects: Delete any object. This operation deletes the object from the database. Delete all jobs contained in a spooler or queue. (pdclean) This operation deletes the specified job, regardless of its current state, its job-retention-period, job-completion-period (if specified) and default-job-completion-period. If the job is currently printing, the supervisor stops printing the job as soon as possible, after which the job is deleted from both the supervisor and spooler. This section covers the following topics: Deleting a spooler Deleting a supervisor Deleting a queue Deleting a physical printer Deleting a logical printer Deleting an initial-value-job
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18-1 REMOVING (DELETING) OBJECTS
Deleting an initial-value-document.
Deleting objects using GUI
Administrators can remove objects using the GUI Administration Tool. Refer to the GUI online help for details on using this method. The GUI instructions for deleting each object appear following each object description.
Deleting objects using CLI
Deleting objects removes them from the corresponding spooler’s or supervisor’s object database, and removes them from the name space where applicable. All objects, except documents, are valid objects for a delete operation. Specific examples for deleting each object re listed with each object description. To delete an object, use the following command: pddelete [-c class_name] object_instance …
class_name object_instance server spooler_name server supervisor_name queue queue_name printer (default) logical_printer_name printer physical_printer_name
job [spooler_name:]job_identifier initial-value-job spooler_name:iv_job_name initial-value-document spooler_name:iv_doc_name Other switches available for the pddelete command include: [-m message_text] [-x extended_attribute_string] [-X attribute_filename] Refer to the PrintXchange Command Line Interface Reference Guide.
18-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT REMOVING (DELETING) OBJECTS
Deleting a spooler
To delete a spooler, you must first disable it. If there are jobs on the spooler, you must first delete all jobs on the spooler (you can use the pdclean operation on the spooler). The delete spooler operation: Deletes all spooler objects (logical printers, queues, initial-value- documents, initial-value-jobs and the spooler itself) from the spooler’s object database. Removes the spooler, and its queues and logical printers from the name service. Causes all physical printers associated with the spooler to be disassociated by setting the associated-queue and printer- associated-printers attributes to empty.. Deletes the spooler’s object database. Causes the spooler to exit.
Deleting a spooler using GUI
To delete a spooler using the GUI: 1. Run the Administration tool. 2. In the right menu, select the desired type of object (Spoolers). 3. Select the spooler to delete. 4. If the spooler is not disabled invoke the disable button. 5. If the spooler contains jobs, invoke the clean button. 6. Invoke the delete button when there are no jobs in the spooler.
Deleting a spooler using CLI
Use the pddisable command to disable the spooler. The syntax is: pddisable -c server spooler_name Use the pdclean command to remove all jobs from the spooler. The syntax is: pdclean -c server spooler_name Use the pddelete command to delete the spooler. The syntax is: pddelete -c server spooler_name The following example deletes a spooler named spooler1: pddisable -c server spooler1 pdclean -c server spooler1 pddelete -c server spooler1
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18-3 REMOVING (DELETING) OBJECTS
Deleting a supervisor
To delete a supervisor, you must first disable it. Also, you can not delete a supervisor that is currently processing jobs. Therefore, you must first delete all jobs on the supervisor by issuing a pddelete for all jobs in the supervisor via the spooler or allow all currently printing jobs on the supervisor to complete. The delete supervisor operation: Deletes all supervisor objects (physical printers and the supervisor itself) from the supervisor’s object database Removes the supervisor and its physical printers from the name service. Causes the supervisor to notify the spooler to update affected queues and logical printers by removing its physical printers from all mapping attributes (printer-associated-printers, printers- ready, physical-printers-supported, physical-printers-ready). Deletes the supervisor’s object database. Causes the supervisor to exit.
Deleting a supervisor using GUI
To delete a supervisor using the GUI: 1. Run the Administration tool. 2. In the right menu, select the desired type of object (Supervisors). 3. Select the supervisor to delete. 4. If the supervisor is not disabled invoke the disable button. 5. Invoke the delete button.
Deleting a supervisor using CLI
Use the pddisable command to disable the supervisor. The syntax is: pddisable -c server supervisor_name Use the pddelete command to delete the supervisor. The syntax is: pddelete -c server supervisor_name The following example deletes a supervisor named sup1: pddisable -c server sup1 pddelete -c server sup1
18-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT REMOVING (DELETING) OBJECTS
Deleting a queue
The delete operation for a queue does the following: Disables all logical printers that feed the queue. Removes the queue name from its spooler’s queues-supported attribute. Causes the supervisor to asynchronously set the following attributes to empty for each physical printer associated with the deleted queue. printer-associated-printers associated-queue The supervisor also updates its printers-ready attribute and disables all physical printers associated with the queue. Removes the queue name from the spooler server object database and from the name service. If the supervisor is not running when you delete the queue, it performs its updates when you restart it. Deleting a queue is a three-step process: 1. Disable the queue. 2. Remove all jobs from the queue. 3. Delete the queue.
Deleting a queue using GUI
To delete a queue using the GUI: 1. Run the administration tool. 2. In the right menu, select the desired type of object (Queues). 3. Select the queue to delete. 4. If the queue is not disabled invoke the disable button. 5. If the queue contains jobs, invoke the clean button. 6. Invoke the delete button when there are no jobs in the queue.
Deleting a queue using CLI
Use the pddisable command to disable the queue. The syntax is: pddisable -c queue queue_name Use the pdclean command to remove all jobs from the queue. The syntax is: pdclean -c queue queue_name Use the pddelete command to delete the queue. The syntax is: pddelete -c queue queue_name
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18-5 REMOVING (DELETING) OBJECTS
The following example deletes a queue named q1: pddisable -c queue q1 pdclean -c queue q1 pddelete -c queue q1
Deleting a physical printer
To delete a physical printer, you must first disable it. You can not delete a physical printer if the printer has any active jobs so you must delete any jobs currently active on the printer or wait for active jobs to complete after disabling the printer. In addition, the spooler supporting this physical printer must be running for the operation to succeed. The delete operation: Removes the physical printer from the supervisor’s object database. Removes the physical printer object from the name service. Updates physical-printers-supported on the supervisor by removing the deleted physical printer. Causes the supervisor to notify the spooler to update any affected queues and logical printers by removing the physical printers from all mapping attributes. The spooler: Updates printers-ready and printer-associated-printers for the logical printer. Updates physical-printers-supported on the spooler and queue. If the specified printer is the only physical printer associated with a queue, the operation causes the spooler not to schedule any jobs in that queue until another physical printer is associated with it. If the queue is associated with other physical printers and the user who submitted the job did not set the physical- printers-requested attribute to the deleted physical printer, then the spooler delivers jobs to one of the other physical printers. Otherwise, the job will not print and the physical- printers-requested attribute on the job must be modified to empty or to another physical printer associated with the queue. Deleting a physical printer is a three-step process: 1. Disable the physical printer. 2. Cancel any jobs currently active, or wait for any active jobs to complete. 3. Delete the physical printer.
18-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT REMOVING (DELETING) OBJECTS
Deleting a physical printer using GUI
To delete a physical printer using the GUI: 1. Run the Administration tool. 2. In the right menu, select the desired type of object (Physical Printers). 3. Select the physical printer to delete. 4. If the physical printer is not disabled invoke the disable button. 5. Invoke the delete button.
Deleting a physical printer using CLI
Use the pddisable command to disable the physical printer. The syntax is: pddisable -c printer physical_printer_name Use the pddelete command to delete the physical printer. The syntax is: pddelete -c printer physical_printer_name The following example deletes a physical printer named physical1: pddisable -c printer physical1 pddelete -c printer physical1
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18-7 REMOVING (DELETING) OBJECTS
Deleting a logical printer
This operation does not affect jobs submitted through the specified logical printer and, therefore, may result in the job’s printer-name- requested attribute referencing non-existent logical printers. Before a logical printer can be deleted, you must first disable the logical printer. The delete operation: Removes the logical printer from the spooler’s object database. Updates the logical-printers-supported attribute for the associated queue and server by removing its name. Updates all associated physical printers to remove the logical printer from the associated physical printer’s printer-associated- printers attributes. Removes the logical printer entry from the Name Service. Deleting a logical printer is a two-step process: 1. Disable the logical printer. 2. Delete the logical printer
Deleting a logical printer using GUI
To delete a logical printer using the GUI: 1. Run the Administration tool. 2. In the right menu, select the desired type of object (Logical Printers). 3. Select the logical printer to delete. 4. If the logical printer is not disabled invoke the disable button. 5. Invoke the delete button.
Deleting a logical printer using CLI
Use the pddisable command to disable the logical printer. The syntax is: pddisable -c printer logical_printer_name Use the pddelete command to delete the logical printer. The syntax is: pddelete -c printer logical_printer_name The following example deletes a logical printer named logical1: pddisable -c printer logical1 pddelete -c printer logical1
18-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT REMOVING (DELETING) OBJECTS
Deleting an initial-value-job
This operation will delete the initial-value-job from the spooler’s object database. Note: If the deleted initial-value-job is associated with a logical printer via the printer-initial-value-job attribute, this attribute is not updated. However, print requests can be submitted through the printer. No defaulting will occur.
Deleting an initial-value-job using GUI
Note: You cannot delete initial-value-job objects with the GUI.
Deleting an initial-value-job using CLI
Use the pddelete command to delete an initial-value-job. The syntax is: pddelete -c initial-value-job spooler_name:iv_job_name The following example deletes an initial value job named ivj1 on a spooler named spool1: pddelete -c initial-value-job spool1:ivj1
Deleting an initial-value-document
This operation will delete the initial-value-job from the spooler’s object database. Note: If the deleted initial-value-document is associated with a logical printer via the printer-initial-value-document attribute, this attribute is not updated. However, print requests can be submitted through the printer. No defaulting will occur.
Deleting an initial-value-job using GUI
Note: You cannot delete initial-value-document objects with the GUI.
Deleting an initial-value-job using CLI
Use the pddelete command to delete an initial-value-document. The syntax is: pddelete -c initial-value-document spooler_name:iv_doc_name The following example deletes an initial value document named ivd1 on spooler name spool1: pddelete -c initial-value-document spool1:ivd1
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 18-9 REMOVING (DELETING) OBJECTS
18-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 19. Generating accounting reports
One of the features of PrintXchange is the ability to generate accounting reports. Accounting is the collection of accountable job and document information that is collected when a job terminates for any reason, such as when it is canceled, aborted, or completed printing. The information is then written by the spooler to a data file. The pdaccount utility reads the accounting file and generates the information in simple text. Users can use the text representation of the accounting log with spreadsheets. The spooler creates the accounting files in the path %PXCROOT%\var\acct where %PXCROOT% is the directory where PrintXchange is installed. The file’s name is of the form: spooler_name.YYYYMMDD or spooler_name.current where: spooler_name = the name of the spooler collecting the data YYYY = the four-digit year MM = the month from 01 to 12 DD = the day from 01 to 31 current = represents the current day’s accounting log. The current file is renamed to < spooler_name>.yyyymmdd at midnight.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 19-1 GENERATING ACCOUNTING REPORTS
Enabling accounting
Logging of accounting data is the default state of a PrintXchange spooler. However, you can disable logging of accounting data for a specific physical printer. To enable or disable accounting, use the CLI pdset command or the Administration GUI to change the value of the accounting-enabled attribute.
Enabling or disabling accounting using GUI
To enable accounting using the Administration GUI: Bring up the property sheet for the physical printer. Select the Details button. A details window will appear. Select the Accounting tab. Select the Enable Accounting field. A checkmark signifies accounting is enabled. Removing the checkmark signifies accounting is disabled. Select OK to set.
Enabling accounting using CLI
To enable accounting, use the CLI pdset command to change the value of the accounting-enabled attribute. To enable logging of accounting data for a specific physical printer: pdset -c printer -x “accounting-enabled=yes” physical_printer_name The following example enables accounting on the physical printer named physical4: pdset -c printer -x ”accounting-enabled=yes” physical4
Disabling accounting using CLI
To disable accounting, use the CLI pdset command to change the value of the accounting-enabled attribute. To disable logging of accounting data for a specific physical printer: pdset -c printer -x “accounting-enabled=no” physical_printer_name The following example disables accounting on the physical printer named physical4: pdset -c printer -x ”accounting-enabled=no” physical4
19-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GENERATING ACCOUNTING REPORTS
Accounting profile
As the system administrator, you can construct an accounting profile for a physical printer with the accounting-profile attribute. The accounting profile identifies the job and document attributes that the spooler collects for the accounting log. Users may specify any job and document attributes with the accounting-profile attribute.
Constructing an accounting profile using GUI
To construct an accounting profile using the Administration GUI: Bring up the property sheet for the physical printer. Select the Details button. A details window will appear. Select the Accounting tab. In the Profiling Attributes section, select the desired attributes Select OK to set.
Constructing an accounting profile using CLI
To construct an accounting profile using the CLI: pdset -c printer -x “accounting-profile=job- identifier submission-time job-name job-owner number-of-documents document-file-name copies- completed printers-assigned document-sequence- number” physical printer If the accounting-profile attribute is not specified, the spooler collects data for the attributes contained in the spooler’s attribute default-accounting-profile. The default job and document attributes for default-accounting-profile are listed in Table 19-1.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 19-3 GENERATING ACCOUNTING REPORTS
Table 19-1. Accounting attributes
Job Attributes accounting-information job-sheets completion-time job-state-reasons delivery-method (results-profile) job-to-be-billed document-sheets media-consumed impressions-completed media-sheets-completed job-comment number-of-documents job-copies-completed pages-completed job-fault-count printer-name-requested job-finishing printers-assigned job-identifier started-printing-time job-name submission-time job-originator total-job-octets job-owner user-name Document Attributes copies-completed number-up document-file-name plex document-format print-colour-type-used document-type finishing
The accounting log entry for a canceled job consists of the attributes contained in default-accounting-profile.
19-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GENERATING ACCOUNTING REPORTS
Using the accounting report writer
The PrintXchange pdaccount utility program serves as a report writer that converts the accounting log records into a simple text file consisting of lines of tab-separated text fields. The output text file produced by pdaccount includes a record for every job that has been finished. The first line in the output file contains the names of the attributes of the collected data. If the user changes the accounting profile attributes in the middle of an accounting log period, the output file lists the names of the new attribute set. The output file lists only job attributes by default. Each job record is delimited by a
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 19-5 GENERATING ACCOUNTING REPORTS
-e end-date Specifies the last date that will be included in the report. If not specified, the end-date will be the latest log found. The date is used to select the log started on the specified date. Data logged on the day after the specified date but before the creation of the next day’s log will also be included. The format of end-date is yyyymmdd. -h Displays a usage statement for pdaccount. -g Do not display name of attributes in the report. -o outfile Specifies the name of the file where the output will be written. If not specified, the report is written to standard output (sttdout). -O Specifies the OID database path. If this path is omitted, the default path is: %PXC_ROOT%\share\oid
where %PXC_ROOT% is defined to be the directory where PrintXchange is installed. -p Specifies the accounting log path. If this path is omitted, the default path is: %PXC_ROOT%\var\acct where %PXC_ROOT% is defined to be the directory when PrintXchange is installed. -s start-date Specifies the first date that will be included in the report. If not specified, the start date will be the earliest log found. Data logged on any date before the specified date will not be included.
The format for start-date is yyyymmdd. spooler_name Specifies the name of the spooler that is a component of the log file name. The following example generates an account report named report1, for the spooler named spooler1 for the period beginning on March 5, 1998 and ending on March 7, 1998 and deletes the processed logs: pdaccount -d -s 19980305 -e 19980307 -o report1 spooler1
19-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20. Inbound gateways
The inbound gateways enable legacy clients access to PrintXchange servers. The gateways connect two domains, the legacy client domain with the PrintXchange server domain. PrintXchange inbound gateways support: Prior releases of PrintXchange LPR extensions plus production printing and Fuji Xerox extensions. LAN Manager clients (LAN Manager inbound gateway). The LAN Manager gateway supports SMB protocol compatible with OS/2 and Windows For Workgroup. NetWare clients (NetWare QServer inbound gateway). The NetWare QServer inbound gateway enables NetWare clients in a traditional NetWare printing environment (i.e., non-NDPS) to submit print jobs to the PrintXchange system. Common features of the gateways include: The inbound gateway software is loosely coupled with the PrintXchange spooler. It can either reside on the same hardware platform with the spooler, or reside on a separate machine. The NT gateway processes run on top of the NT operating system. An NT gateway can connect to both an NT and UNIX PrintXchange spooler. Microsoft RPC is the communication protocol with an NT PrintXchange spooler. Operations and attributes supported by the gateways are confined to the subset available in the native client environment. Typically this represents a small subset of DPA user operations/attributes. No system administration capability is offered from the gateways. The NT gateways support multiple client connections at the same time. The maximum number of client connection is configurable. The gateway acts as a proxy for its client network environment. Users from the client network environment share the same level of access as the gateway.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-1 INBOUND GATEWAYS
Inbound gateways
Inbound gateways for Windows NT depend on the following PrintXchange modules and communication environments: 1. PrintXchange client stubs (POSIX-API, Common Client Module). Since an inbound gateway submits DPA operations through the POSIX API, the following client stub module is required. It contains POSIX-API stub (dpa.lib) and common client modules (cmcl.lib) called CC-Layer. pddpa.dll pdcmcl.dll 2. NT infrastructure modules (used directly and through client stubs). Since an inbound gateway submits DPA operations using POSIX-API to a PrintXchange server, the gateway requires the PrintXchange client stubs under POSIX-API. An inbound gateway requires the PrintXchange installation process to install the libraries for the dynamic link version. A gateway calls both pdinfra.dll and pdcore.dll dynamically to use specific libraries: pdinfra.dll pdcore.dll 3. Network transport communication modules for each client environment. An inbound gateway requires a suitable network communication module as listed in the following table.
Table 20-1. Communication modules
Gateway Required Communication Modules
px_lpribg Windows Sockets Library (Windows NT)
TCP/IP Protocol (Windows NT)
px_lmibg NetBEUI Protocol (Windows NT)
px_qsibg pdgwncp.dll (NetWare Core Control)
Windows Sockets Library (Windows NT)
NWLink IPX/SPX Compatible Transport (Windows NT)
TCP/IP Protocol (Windows NT)
20-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Inbound gateway names
Service name In the Windows NT environment, service application modules are managed by the Service Control Manager (SCM). An inbound gateway registers itself to the SCM as a service with a service name. The service name is shown in the SCM GUI box as a Service name. [Control Panel->Services] The PrintXchange inbound gateways use the following names: PrintXchange LPR Print PrintXchange LAN Manager Print PrintXchange NetWare QServer Print. Abbreviation name The inbound gateway name is required in various locations such as in the directory, and inside gateway modules. The inbound gateway names for these purposes are abbreviated as follows: px_lpribg (LPR inbound gateway) px_lmibg (LAN Manager inbound gateway) px_qsibg (QServer inbound gateway) These abbreviations may be used in Error message reporting.
Administration and configuration
This section lists properties and parameters relating to the inbound gateway services and to configuration information common to the inbound gateways with the exception of the UNIX LPR inbound gateway.
Base Properties
The base properties for PrintXchange Print Service include: Max number of job retries This parameter specifies the number of times the gateway tries to re- submit the print job on a submission recoverable error. Disk usage quota You can set the minimum space that is left on the local disk area. When a gateway is going to receive a new job, the gateway checks the remaining disk space and compares it with this value. The gateway does not receive the next job data file if the remaining space is less than this parameter value. All inbound gateways use the default value, if the value is out of range.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-3 INBOUND GATEWAYS
Copy module files Copy the inbound gateway module files to suitable directories according to the PrintXchange policy. For all inbound gateways: pdgwmap.dll (common mapper library) pdgwbe.dll (common POSIX-API back end) For the LPR inbound gateway: pdlpribg.exe pdlpribg.mdl (for PrintXchange Message Library) printcap (text file) For the LAN Manager inbound gateway: pdlmibg.exe pdmon.dll (for Windows NT Spool Subsystem) pdlmibg.mdl (for PrintXchange Message Library) For the QServer inbound gateway: pdqsibg.exe pdgwncp.dll (NetWare Core Protocol) pdqsibg.mdl (for PrintXchange Message Library) Directory contents location Creation of the inbound gateway local spool directories is based on gateway configuration information. The PrintXchange root directory is defined as an environment variable called %PX_ROOT%. The root directory is also registered with the NT registry. An inbound gateway uses two directory types under the PrintXchange root directory: Local spool directories The installation process creates a spool directory for the inbound gateway: %PX_ROOT%\var\spool\px_lpribg %PX_ROOT%\var\spool\px_lmibg %PX_ROOT%\var\spool\px_qsibg When a gateway starts up, it creates its own spool directories; one for each supported logical printer (for LPR and LAN Manager inbound gateways), for example: %PX_ROOT%\var\spool\px_lpribg\logicalPrinterName\ The QServer inbound gateway creates a spool directory for each supported NetWare queue. Configuration data directory An inbound gateway may use its own configuration file. The installation process copies the configuration file to the corresponding directory, as follows: %PX_ROOT%\share\data\px_lpribg The printcap file for the LPR inbound gateway is stored in this directory.
20-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Register configuration information Register configuration information to the specified registry. The section on Inbound gateway names lists registry parameters common to all inbound gateways. Refer to the “Administration and configuration” for each respective section for list registry parameters specific to the LAN Manager, QServer, and LPR for NT inbound gateways. Set account name Set the inbound gateway process owner (account) name. Since an inbound gateway service behaves as a proxy client against the PrintXchange service, the gateway service has to start up as an end user process that belongs to the target PrintXchange domain containing a target PrintXchange spooler. The PrintXchange installation process creates a user account for the gateway that consists of a static gateway prefix for each gateway service and local machine name on which the gateway will run. Example: For inbound gateway lpribg installed to a PC called pxserver, the inbound gateway user name becomes “PXLPRIBGPXSERVER”. Generally, the format of the account name is: PX + gatewayAbbreviationName + machineName The installation process automatically creates the user’s password using the machine name. The inbound gateway account name provides the following benefits: It provides a means to identify the gateway name based on the value of the user-name attribute because the PrintXchange security library sets the process owner account to the attribute value automatically on job creation. The accounting tool can use the user-name attribute to categorize the job list for each gateway. The PrintXchange administrator can know the location of the target gateway service from the machine-name part of the user- name attribute. Note: To perform proper accounting, the user-name attribute should be queried for jobs submitted in the spooler’s native environment. For jobs submitted from an inbound gateway, the job-owner attribute should be used for accounting.
Startup and shutdown
An inbound gateway service can be controlled by the Windows NT Service Control Manager (SCM) because it behaves as a Windows NT service. When an inbound gateway service is registered with the SCM, it starts up automatically with auto-startup. Otherwise, users can start an inbound gateway service by manually using the Service Control Manager GUI. Users can stop an inbound gateway service by manually using the Service Control Manager GUI. Otherwise, although gateway services try to finish processing jobs when the Windows NT system is going to shut down, its effort may be unsuccessful. In this case, gateways try to correct their own state and the jobs’ state when the gateways next start up.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-5 INBOUND GATEWAYS
Cross domain/cross platform support
The inbound gateways can communicate and submit jobs to PrintXchange servers that reside in another domain than in which the gateway host resides. At the same time, the inbound gateways can communicate and submit jobs to PrintXchange servers on a platform other than the platform on which the gateways reside. Cross platform support applies to the LAN Manager, QServer and LPR inbound gateways for submission to UNIX PrintXchange servers. Cross platform support requires that the domain names used by the gateways include the following prefixes to recognize the RPC (MSRPC or ONC-RPC) environment of the target logical printer. The prefixes are: For Windows NT servers: winnt: or ntsecurity: For UNIX servers: nis: Example: nis:nisDomainName There is one restriction on naming logical printers (as illustrated in figure 20-1): The same logical printer name may not be used more than once in the same domain.
Figure 20-1. Using the same logical printer name
MS-RPCPrintxchange ONC-RPC Objects
UNIX WindowsNT (NIS, DNS,.)
Domain A Domain B Domain A Domain X LP-1 LP-1 LP-1 LP-1 LP-1 LP-22 LP-32 LP-42 LP-32 LP-23 LP-33 LP-43 LP-33: : : :
20-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Modifying a gateway service configuration
Users can modify an inbound gateway configuration after the gateway installation is successfully completed. To modify the gateway configuration, as the PXCAdmin, you have to do following three steps. 1. Stop the target gateway service. 2. Modify the configuration information. 3. Start the gateway service again. When modifying the gateway configuration, you have to take care of the configuration file (including printcap file). The LPR inbound gateway uses the printcap file to manage the supported logical printer name and other information you can modify the gateway configuration by editing the printcap file directly.
Security
The installation process creates a local user account on the host machine for an inbound gateway being installed. The user acccount consists of the PrintXchange prefix, inbound gateway name, and the host machine name—all in uppercase characters. For example: PXQSIBGWINDSTAR Where PX is the prefix, QSIBG is the gateway name, and WINDSTAR is the host machine name. The installation process also sets a password to the name of the host machine, also in uppercase characters. It is your responsibility as system administrator to change the password, if desired, after installation to ensure a secure system. The inbound gateway account on the remote PrintXchange server must have the same password as on the local system. Therefore, if you change the password on the local system, then you must also change the password on the remote PrintXchange server. You may change the inbound gateway account from a user account to a domain account. PrintXchange provides varying levels of security based on the server and gateway configuration. Table 20-2 lists the security options that you may set. Table 20-3 describes the security tags given in table 20-2, where the S-n tags indicate secure submissions and P-n tags indiacate proxy submissions. Since all local users may already have End User level access rights in the PrintXchange default setting, you may not be required to add the ACL for S-1, S-2, and S-3 cases. If the server belongs to a domain, both the domain user group and the local user group on the server have access right to the local PrintXchange server objects in the default setting. If the server belongs to a workgroup, the local user group has access rights to the local PrintXchange server objects in the PrintXchange system.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-7 INBOUND GATEWAYS
Table 20-2. Client/server security configurations
Inbound gateway account
Workgroup-1 NT Domain-A NT Domain-A PrintXchange server Local User Local User Domain User
Workgroup-1 S-1 S-1, P-1 S-1, P-2
Workgroup-2 S-1, P-1 S-1, P-1 S-1, P-2
NT Domain-A S-1, P-1 S-1 S-3
NT Domain-A (PDC or S-2, P-1 S-2 S-3 BDC)*
NT Domain-B (trusted N/A S-1, P-1 S-4, P-2 w/A)
NT Domain-B (PDC or N/A S-2, P-1 S-4, P-2 BDC)
NT Domain-C (non- N/A S-1, P-1 S-1, P-2 trusted w/A)
NT Domain-C (PDC or N/A S-2, P-1 S-2, P-2 BDC)
Cross Platform P-1 P-1 P-2
* PDC = Primary Domain Controller BDC = Backup Domain Controller
20-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-3. Security options
Tag Resolution
Secure
S-1 Create a local account with the same name and password as gateway account on the server host.
Set access-control-list to the server for a new local account. “{domain=ntsecurity:ServerComputerName user=GWUser name-type=user privilege-level=end-user}”
S-2 Create a domain account with the same name and password as gateway account in the server domain.
Set access-control-list to the server for a new domain account. “{domain=ntsecurity:ServerDomainName user=GWUser name-type=user privilege-level=end-user}”
S-3 Set access-control-list to the server for a gateway account. “{domain=ntsecurity:ServerDomainName user=GWUser name-type=user privilege-level=end-user}”
S-4 Set access-control-list to the server for a gateway account. “{domain=ntsecurity:GWDomainName user=GWUser name-type=user privilege-level=end-user}”
Proxy
P-1 Set proxy-submit-supported to true.
Set access-control-list to the server for a gateway account. “{domain=winnt:GWComputerName user=GWUser name-type=user privilege- level=end-user}”
P-2 Set proxy-submit-supported to true.
Set access-control-list to the server for a gateway account. “{domain=winnt:GWDomainName user=GWUser name-type=user privilege- level=end-user}”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-9 INBOUND GATEWAYS
LAN Manager inbound gateway
This section describes the printing functionality provided for the LAN Manager inbound gateway (LM-IBG).
Overview
The LM-IBG provides a job submission method from regular Windows clients to the PrintXchange spooler. Figure 20-2 illustrates a LAN Manager inbound gateway printing system.
Figure 20-2. LAN Manager inbound gateway components
Windows NT machine PrintXchange Spooler
LAN Manager Client PC LAN Manager IBG
Windows NT Client PC LAN Manager Client PC
20-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Figure 20-2 illustrates that: The LM-IBG is located on a Windows NT machine. Users may submit print jobs from a Windows environment not having any unique PrintXchange software to a PrintXchange server. Print jobs submitted from client PCs are passed to the PrintXchange spooler through the LM-IBG. The server machine on which the LM-IBG resides can also be a local client machine. The LM-IBG supports the following Windows clients: Windows 3.1 Windows 95 Windows NT. For the LAN Manager inbound gateway, access to PrintXchange logical printers is achieved by using the printer GUI that Windows NT provides. When you want to list available printers from printer GUI, the LAN Manager inbound gateway looks up the Domain Name registry key in the NT registry and lists available PrintXchange logical printers from one or more domains previously specified by the administrator in the NT registry. The function of the LAN Manager is equivalent to the LPR gateway without TCPIP environments/configurations. It is also equivalent to a shared NT network printer. You can create a PrintXchange corresponding to the logical printer in PrintXchange. This is not a shared NT network printer. You can choose a device for the logical printer the same way you choose one for a shared NT network printer.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-11 INBOUND GATEWAYS
How to set up LAN Manager inbound gateway
1. Start "PrintXchange LAN Manager Print" service on the Services Control Manager Window. (It may have already started automatically. It depends on Windows NT Spool Subsystem and PrintXchange Name Service.) 2. Open Control Panel window of NT. 3. Open Printers window in Control Panel. 4. Open Add Printer Wizard window in Printers. 5. Select My Computer and click Next 6. Click the Add port button, then Printer Ports window opens. 7. Select PrintXchange Port, then the PrintXchange Port window. It displays Now Searching. (Select and click Now Searching or select and click New Port button) 8. PrintXchange printer name window appears with pull down window for PrintXchange logical printers. 9. Select a logical printer and click the OK button. 10. Click Next button on the Add Printer Wizard. 11. Select a suitable printer from displayed list and click Next. 12. Install a printer driver if necessary. 13. Fill a printer name and click Next. 14. Select Shared and fill a shared printer name 15. Click the Finish button, then the Add Printer Wizard window disappears. 16. You can see a new printer icon in Printers window with new printer name. Windows NT or Windows 95 client Win 3.Xcan see this shared printer in the network and can set it as network printer. Notes: LAN Manager-IBG can support one PrintXchange domain at a time. LAN Manager-IBG uses local NT domain, which LM-IBG runs on, as default domain. After a domain change, all printers defined in the previous domain are no longer accessible. When setting up the gateway to access PrintXchange printers in the UNIX network, the domain is set from the Cross-platform print submission and management screen. The domain can be changed using the PrintXchange Setup tool. The system must be re-started for the domain change to go into effect. When setting up the gateway to access PrintXchange printers in the NT network, the domain is set from the PrintXchange Name Service screen. The domain can be changed using the PrintXchange Setup tool. The system must be re-started for the domain change to go into effect.
20-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Administration and configuration
The tuning parameters control LAN Manager inbound gateway behavior. The tuning parameters are recorded in the Windows NT PrintXchange LAN Manager Print Service Properties. You set all configuration and tuning parameters. If a parameter has no value or it is out of range, then the LAN Manager inbound gateway uses the default value if possible.
Base Properties
Max number of job retries default: 0 Times Disk usage quota default: 5000 (KB)
Tuning Parameters
The LAN Manager inbound gateway limits the number of print threads to avoid keeping resources to itself. The LAN Manager print thread is created when the user submits a job to a PrintXchange printer, and exits when it receives a return value from the PrintXchange spooler. Maximum number of threads default: 16
Cross domain/cross platform support
LAN Manager inbound gateway extracts the domain name from the “DomainName” registry key as one of configuration parameters. You can specify the domain name which the target PrintXchange logical printer belongs to. As administrator, you can specify a single domain name among Windows NT workgroup and Windows NT domain and also nis domain. Only nis domain case requires you to set “nis:” prefix with a domain name in the DomainName registry.
Basic operation
Figure 20-3. LAN Manager Inbound gateway printing model
Spoolss.exe PrintXchange pdlmibg.exe Spooler
PrinterA PortA pdmondll Client
PrinterB PortB pdmdll
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-13 INBOUND GATEWAYS
The LAN Manager inbound gateway consists of the following components: Spoolss.exe: Windows NT process to support printing. pdmon.dll: one of LM-IBG components. It is attached to the spoolss.exe at execution. pdlmibg.exe: one of LM-IBG component. The printing model process is as follows: 1. Client sends a job to the LM-IBG printer 2. Spoolss.exe gets the job. The job is stored in spool directory. 3. Spoolss.exe communicates with pdlmibg.exe. 4. pdlmibg.exe sets attributes. 5. pdlmibg.exe submits the job to PrintXchange spooler.
LAN Manager inbound gateway startup and stop
The Service Control Manager (SCM) controls LM-IBG start up. When the inbound gateway starts up, it behaves as follows: The start routine performs the following: 1. Get the tuning parameters from the Windows NT PrintXchange LAN Manager Print Service Properties Setup Window and Windows NT Environment variables. 2. Create the spool directory. If the directory for the PrintXchange logical printer does not exist, then the gateway creates it. The LM-IBG expects the spool path directory (%PX_ROOT%\var\spool\px_lmibg) to exist. 3. Check for incomplete jobs in the spool directory. If any exist, the LM-IBG deletes them. If pre-processed files exist in the spool directory, the LM-IBG processes them. 4. Enable itself to receive new jobs from clients. The Service Control Manager also controls a LM-IBG stop. When the LM-IBG is stopped, it: Disables itself, keeping it from receiving new jobs Immediately stops processing jobs
Port
To print a job on a PrintXchange printer, you must add the PrintXchange port and create an NT printer using the Add Printer wizard. A PrintXchange port has a one-to-one correspondence with a PrintXchange logical printer; they both have the same name. If a PrintXchange logical printer was added or deleted at the PrintXchange spooler, it is reflected the next time the user runs the add port operations.
20-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Print job submission
The print job submission process is as follows: 1. The Windows NT spool subsystem receives a job from a LAN Manager client. A user can confirm this by checking the printer status (Start > Settings > Printers > double click on specific printer). 2. The LM-IBG collects print attributes from the job for the PrintXchange spooler. 3. The LM-IBG adds default attributes: job-name. The LAN Manager job name extracted from the job. job-owner. The LAN Manager user name extracted from the job. This attribute is used for accounting. user-name. Value set by the infrastructure library and used for authentication. copy-count. The value is always 1. printer-name-requested. The port name associated with the PrintXchange logical printer. document-content. Job data file name, including the full path. operation-locale. The locale name indicating the PrintXchange name service domain name. 5. The attributes job-name, job-owner, printer-name- requested, and document-content may contain multi-byte characters. Specifically, they may contain Shift-JIS code in the Japanese version. The LM-IBG then submits the job to the PrintXchange spooler. If the submit operation is successful, the LM-IBG deletes the job from the NT spool subsystem. The LM-IBG does not support a cancel job operation after the gateway submits the job to the PrintXchange spooler. 6. If the LM-IBG receives an error on the job submission, then it deletes the job and raises an error event. If the error is recoverable, the LM-IBG resubmits the job based on the RetryCount parameter.
Internationalization
The LM-IBG can work on Windows NT 4.0 (multinational). But window messages and event massages depend on the existence of message files. The LM-IBG includes Japanese and English message files. In the Japanese version, the character code of attributes is Shift-JIS.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-15 INBOUND GATEWAYS
NetWare QServer inbound gateway
This section describes the printing functionality provided for the QServer inbound gateway in PrintXchange.
Overview
The NetWare QServer inbound gateway enables NetWare clients in a traditional NetWare printing environment (i.e., non-NDPS) to submit print jobs to the PrintXchange system. NetWare clients submit print jobs to the NetWare print queue using native NetWare submission methods. The QServer gateway running on a PrintXchange server machine: Connects to the NetWare file server where the print queue resides Logs in to the file server as a NetWare Print Server and behaves as Queue Server Retrieves print jobs Forwards the jobs to the PrintXchange spooler Waits for the job completion event and removes the print job from the NetWare queue. Figure 20-4 shows the QServer inbound gateway configuration on the network. The QServer gateway works on a Windows NT machine as a Windows NT service. Since the gateway is loosely coupled with the PrintXchange spooler, it can run on the remote machine and can deliver jobs to a spooler.
Figure 20-4. QServer inbound gateway network configuration
NetWare Server WindowsNT Machine File Server QS IBG
IPX/NCP Protocol
IPX/NCP Protocol
NetWare Client
Note: The NetWare inbound gateway supports Bindery Mode only (not NDS mode).
20-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
How to set up NetWare Queue
To set up NetWare queue, follow the following sequence of installation steps:
To configure NetWare 3.1X follow these steps:
Configuration overview Step 1. Start PCONSOLE and select the file server you want to use. Step 2. Create the print server (name entered as the PrintXchange Queue Server Name). Step 3. Select and configure the print queue (name entered as the PrintXchange NetWare Queue). Step 4. (optional) Select and configure additional print queues.
To start PCONSOLE and select file server
Step 1. Log in to the network, type PCONSOLE and press Enter. Step 2. Choose Change Current File Server from the Available Options menu. A list of file servers is displayed. Step 3. Select the file server on which you want to install the PrintXchange print server and press Enter. If the name of the file server you want is not displayed, press the Insert key to get a list of file servers. Step 4. Log in to the file server. Step 5. Press the Esc key to return to the Available Options menu.
To create the print server
Step 1. Choose Print Server Information from the Available Options menu, and press Enter. A list of existing print servers is displayed. Step 2. Press the Insert key. The New Print Server Name box is displayed. Step 3. Type the name of the print server into the entry box. Note: When configuring the PrintXchange NetWare QServer Print component of Gateway Service, this name must be entered as the Queue Server Name. Step 4. Press Enter to add the print server name to the Print Servers list. Note: PrintXchange does not support setting a password for the Print Server. Step 5. Press the Esc key to return to the Available Options menu.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-17 INBOUND GATEWAYS
To select and configure print queues
To forward jobs from an existing NetWare queue to the PrintXchange system, the print server defined for PrintXchange must be assigned to the print queue. Step 1. Choose Print Queue Information from the Available Options menu, and press Enter. A list of existing print queues is displayed. Step 2. Select the Print Queue name and press Enter. Note: When configuring the PrintXchange NetWare QServer Print component of Gateway Service, this name must be entered as a PrintXchange NetWare Queue. Step 3. From the Print Queue Information menu, choose Print Server Configuration, then press Enter to enter the Print Server Configuration menu. Step 4. Choose Queue Servers, then press Enter. Step 5. Press the Insert key. The list of Queue Server Candidates is displayed. Step 6. Select the print server you created, and press Enter. The PrintXchange print server appears in the Queue Servers list. Step 7. Press Esc twice to return to the Print Queues list. Step 8. To configure additional queues that will submit jobs to PrintXchange printers, repeat steps 2 through 7. When finished, press Esc twice to exit PCONSOLE.
Configuring NetWare 4.x
Configuration overview Step 1. Start PCONSOLE and select the bindery emulation file server you want to use. Step 2. In bindery emulation, create the print server (name entered as the PrintXchange Queue Server Name). Step 3. Select and configure the bindery emulation print queue (name entered as the PrintXchange NetWare Queue). Step 4. (optional) Select and configure additional bindery emulation print queues.
Start PCONSOLE and select file server
Step 1. Log in to the network as ADMIN. Step 2. Type PCONSOLE and press Enter. Step 3. An Available Options menu appears, press the F4 key for the Bindery Mode. Choose Change Current NetWare Server from the Available Options menu. A list of file servers is displayed. Select the file server on which you want to install the PrintXchange print server and press Enter. If the name of the file server you want is not displayed, press the Insert key to get a list of file servers. Step 4. Log in to the file server. Step 5. Press the Esc key to return to the Available Options menu.
20-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Create the print server
Step 1. Choose Print Servers from the Available Options menu, and press Enter. A list of existing print servers is displayed. Step 2. Press the Insert key. The New Print Server Name box is displayed. Step 3. Type the name of the print server into the entry box. Note: When configuring the PrintXchange NetWare QServer Print component of Gateway Service, this name must be entered as the Queue Server Name. Step 4. Press Enter to add the print server name to the Print Servers list. Note: PrintXchange does not support setting a password for the Print Server. Step 5. Press the Esc key to return to the Available Options menu.
Selecting and configuring print queues
To forward jobs from an existing NetWare queue to the PrintXchange system, the print server defined for PrintXchange must be assigned to the print queue. Step 1. Choose Print Queues from the Available Options menu, and press Enter. A list of existing print queues is displayed. Step 2. Select the Print Queue name and press Enter. Note: When configuring the PrintXchange NetWare QServer Print component of Gateway Service, this name must be entered as a PrintXchange NetWare Queue. Step 3. From the Print Queue Information menu, choose Print Servers, then press Enter to enter the Print Servers menu. Step 4. Press the Insert key. The list of Print Server Candidates is displayed. Step 5. Select the print server you created, and press Enter. The PrintXchange print server appears in the Print Servers list. Step 6. Press Esc twice to return to the Print Queues list. Step 7. To configure additional queues that will submit jobs to PrintXchange printers, repeat steps 2 through 6. When finished, press Esc twice to exit PCONSOLE.
Administration and configuration
The tuning parameters control QServer inbound gateway behavior. The tuning parameters are recorded in the Windows NT PrintXchange NetWare Print Service Properties. You set all configuration and tuning parameters. If a parameter has no value or it is out of range, then the QServer inbound gateway uses the default value if possible.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-19 INBOUND GATEWAYS
Base Properties
The base properties for the QServer inbound gateway include: Max number of job retries Max number of job retries default: 0 Times Disk usage quota Disk usage quota default: 5000 (KB) All inbound gateways use the default value, if the value is out of range.
Queue Properties
Queue server name The QServer inbound gateway is registered to the NetWare server using this name. This parameter is mandatory. The inbound gateway terminates after it notifies of an uncompleted-installation event if this parameter does not exist.
Tuning Parameters
Job Retry interval time When the capacity of the spool directory is not enough to spool job data, the QServer inbound gateway aborts receiving the job, then after a time interval retries to receive the job. The Job Retry interval time should be set between 180 and 300 seconds. The gateway uses the default value, if the value is out of range. Job retry interval time default: 180 (sec) Maximum number of threads The QServer inbound gateway limits the number of print threads to avoid keeping resources to itself. Since this number is applied to each NetWare queue, the maximum number of print threads in the QServer inbound gateway is equal to the product of this value and the supported number of NetWare queues. In other words, the QServer inbound gateway can process this value of print jobs at the same time for each target queue. The range is 1- 16. Maximum number of threads default: 5 SAP interval time The QServer inbound gateway periodically uses SAP (Service Advertising Protocol) to get the information from the NetWare server on the network. This parameter defines the time of this interval. SAP interval time range is between 30 and 180 seconds. SAP interval time default: 60 (sec) Query interval time The QServer inbound gateway periodically queries whether there are jobs in the target NetWare queue. This parameter defines the time of this interval. Query range is between 1 and 180 seconds. Query interval time default: 15 (sec)
20-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Reconnect interval time When the QServer inbound gateway starts up, the gateway tries to connect to the target NetWare queue based on its configuration parameter. Even if the gateway fails to connect at starting up, it tries to reconnect periodically. This parameter defines the time of this interval. Reconnect interval time range is between 180 and 300 seconds. Reconnect interval time default: 300 (sec)
Domain mapping parameters
The QServer inbound gateway contains mapping information between the NetWare domain and the PrintXchange domain. For each supported NetWare queue, a set of configuration parameters provides the mapping information. NetWare file server name This parameter specifies the NetWare file server name to which the target queue belongs. The QServer inbound gateway expects the installation process to get the target NetWare file server name and to set it in the following registry. Value: %NetWare File Server Name% Default: (Max length: 47 bytes + ‘\0’) NetWare queue name This parameter specifies the target NetWare queue name on the NetWare file server specified with the FileServerName registry key. The QServer inbound gateway expects the installation process to get the target NetWare queue name and to set it in the following registry. Value: %NetWare Queue Name% Default: (Max length: 63 bytes + ‘\0’) PrintXchange logical printer name This parameter specifies the target PrintXchange logical printer name. The QServer inbound gateway expects the installation process to get the target printer name and to set it in the following registry. Value: %PrintXchange Logical Printer Name% Default: (Max length: 255 bytes) Domain name This parameter indicates the PrintXchange Name service domain. Value: (set by administrator) Default: NULL
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-21 INBOUND GATEWAYS
Basic operation
Since the gateway service is provided as a Windows NT service, it keeps the Windows NT service policy. The gateway also keeps the PrintXchange policy because gateway is one of the PrintXchange services. This gateway service is registered to NetWare Server as a PSERVER. Based on the configuration information, the QServer inbound gateway connects to the target queue of the NetWare file server and processes jobs in the target queue. That is, configuration information contains a mapping table between the NetWare queue and the PrintXchange logical printer name.
Figure 20-5. NetWare QServer functionality of gateway service
NetWare File Server Printxchange QServer Printxchange Gateway Service Spooler (Server)
FS1 #1, #6 NetWare FS1 #4 Client Q1 Q1 Translate to PXC-LP1 #2 PXC-LP1 POSIX-API representation Q2 FS1 PXC-LP2 Q2 #3 PXC-LP2
Qn Wait for job completion event FS2 PXC-LPn Q1 PXC-LP6 #5
FS21
Q1
Printxchange Notification Server
The gateway plays a role in NetWare QServer functionality as described in figure 20-5. The QServer inbound gateway processes jobs in the following sequence after the connection to the target queue has been established. 1. Poll jobs to target queue periodically. 2. Retrieve a job from the queue if the queue has some jobs. 3. Translate a job into ISO DPA via POSIX API representation 4. Submit print job to the specified PrintXchange logical printer. 5. Wait for the job completion event from the PrintXchange notification server. 6. Send job-completed event to NetWare client if requested. 7. Delete the job from the target NetWare queue.
20-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
QServer inbound gateway startup and shutdown
Startup The inbound gateway service starts up automatically when the Windows NT is booted. When the gateway starts up, it behaves as follows. 1. Get tuning parameters from the Windows NT PrintXchange NetWare QServer Print Service Properties. 2. Get configuration parameters from the Windows NT PrintXchange NetWare QServer Service Properties. 3. Do recovery action if necessary. 4. Set up the client: 4.1. Query the network for all available NetWare file server addresses via SAP broadcast. 4.2. Spawns off one thread per each configured print queue. 4.3. Create NCP connection with each NetWare target queue. 4.4. Log in as a Print Server using Bindery Login. 4.5. Attach the QServer inbound gateway to the target queue. 5. Start to poll for jobs. When startup is successfully completed, the QServer inbound gateway starts to poll the NetWare queue for new jobs in each thread until the gateway is stopped or the service connection is lost. If the connection is lost in the recoverable reason, the Qserver inbound gateway tries to connect again.
Shutdown The Gateway Service terminates and its process terminates in the following conditions: 1. A fatal error occurs at startup or during normal operation. Configuration parameter missing without applicable default value. Repeated NCP calls fail, which may indicate a communication driver stack problem. System resource problems that may require system reboot. 2. The Gateway Service is stopped manually via Service Control Manager. Once the shutdown process starts, the inbound gateway performs the following actions in sequence: 1. Stop polling for new jobs. 2. Close the connection to the NetWare file server, if possible. 3. Exit all children threads. 4. Log shutdown event into PrintXchange Logging System. 5. Exit itself.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-23 INBOUND GATEWAYS
Print job submission
Once the start up scenario is successfully completed, the QServer inbound gateway starts to provide the print service according to the configuration. NetWare clients can place a print job into a print queue on the NetWare file server using a NetWare client print command or from an application, such as a word processing application. The QServer inbound gateway processes print jobs based on the following scenario. 1. Poll new jobs to the target NetWare queue using NCP Service Queue Job Request packet. 2. Get the job information if there is a ready state job in the queue. Otherwise, periodically poll new jobs forever. Get the job description using the NCP Read Queue Job Entry request packet to check whether the job is new or old. Add [Spooling] into the job description to record the job status in the QServer inbound gateway if it is a new job. This information is put back to the NetWare queue. Process the job based on the recovery scenario described in the next recovery section. 3. Retrieve the job file and store it in the local spool directory. 4. After the job has been spooled completely, the gateway creates a print operation using gateway mapper functions then submits the job to the PrintXchange logical printer. 5. The QServer inbound gateway translates and adds the following attributes: job-name. Job name extracted from the job description field in Queue Job Entry information from NetWare QMS using NCP ReadQueueJob request packet. job-owner. Job owner extracted from the jobDescription field in Queue Job Entry information from NetWare QMS using NCP ReadQueueJob request packet. domain-name. Domain name of the target PrintXchange logical printer. user-name. Value set by the PrintXchange infrastructure security library automatically and used for authentication. copy-count. Copy count extracted from the numberOfCopies field in Queue Job Entry information from NetWare QMS using NCP ReadQueueJob request packet. printer-name-requested. PrintXchange logical printer name associated with the target NetWare queue on NetWare File Server. operation-locale. Set locale of the local machine on which the QServer inbound gateway is running. document-content. Job data file name that includes full path. This name is created by the QServer inbound gateway from the NetWare job number and the local time when the QServer inbound gateway starts to receive the job data.
20-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
notification-profile. The QServer inbound gateway creates a socket to wait for a report-job-completed event from the PrintXchange notification server. job-identifier-on-client. The QServer inbound gateway creates the client identifier from the client job number, queue name, and file server name like “1234:QueueName:ServerName”. 6. Once job submission is completed, gateway changes the prefix of Job Description field from [Spooling] to [Printing]. This information is put back to the NetWare queue. 7. Wait for the job completion event from the PrintXchange notification server. This event name is report-job-completed. 8. Send an NCP Finish Queue Job request to QMS to complete the job cycle after the inbound gateway gets the job completion event. The job entry in the NetWare queue is then removed by QMS. 9. Go to the polling phase again.
Cancel operation
In the NetWare traditional printing environment, a print job can be deleted before the job is completed. A print queue operator can delete a print job at the PCONSOLE for the NetWare 3.x and with NetWare Administrator for the NetWare 4.x using delete key. The print job can also be removed using NCP calls from a submission application if the application offers this feature. The job can be canceled the same as the native way before the QServer inbound gateway starts to service the job. Once the QServer inbound gateway starts to service the job, it may be unable to cancel the job. There is no way the QServer inbound gateway knows the job is canceled directly. The QServer inbound gateway periodically checks whether the servicing job still exists on the queue. The cancel operation is successful before the QServer inbound gateway finishes to retrieve the job data completely. Once the QServer inbound gateway submits the job to the PrintXchange spooler, the cancel operation depends on the job state in the PrintXchange server.
Job recovery operation
The QServer inbound gateway uses temporary files and a job information string to preserve the job processing state information.
Temporary file There are two kind of temporary files: Job data file to be spooled Job attribute file, which contains nothing currently and is used to indicate the job state. A job data file is created on starting to retrieve a job. Its file name is created from NetWare job number that is unique in the queue and time stamps of starting to spool the job. The file has a “.in” extension.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-25 INBOUND GATEWAYS
A job attribute file is created when the job spooling is completed. Its file name has the same body with a “.attr” extension. The job data file is also renamed by changing the extension to “out”. Once the job submission to the PrintXchange spooler is successfully completed, the job attribute file is deleted. The job data file is deleted by an appropriate PrintXchange module, such as a spooler or supervisor if the gateway runs on the same machine as the spooler. Otherwise, the gateway deletes job datafiles.
Job information string For a job recovery operation, the QServer inbound gateway uses the job description field of the NetWare queue, and adds the job information string before the original string with the following format:
[
The possible values of the job_state are:
Spooling, during spooling
Printing, between submitting the job and getting the job completed event
The QServer inbound gateway changes the job description using the NCP Change Queue Job Entry Request call. The NetWare user can then see the job description on the PConsole window.
Recovery operation When a QServer inbound gateway starts up, it checks all local spool directories and it deletes all uncompleted temporary files based on the following rules: The files contain a “.in” extension. The files contain a “.attr” extension. The files countain a “.out”, if the corresponding “.attr” files exist. When the QServer inbound gateway queries-jobs from QMS, QMS could assign a new job to the gateway or QMS could give the gateway a job that has already been served but failed to complete and went back to a ready state. When the inbound gateway encounters a job that has already been processed (by detecting the information string in the description field), it checks the job state and then proceeds accordingly. If the state is Spooling, the inbound gateway does all operations as for a new job. If the state is Printing, the inbound gateway creates a string for job-identifier-on-client and submits a list object attributes (LOA) operation to the PrintXchange server to get the job state. The QServer inbound gateway does a suitable recovery action based on the job state.
20-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Authentication and access control
PrintXchange users must be authenticated and authorized to access PrintXchange objects and operations. The QServer inbound gateway supports a proxy user model for the authentication process. The inbound gateway starts with the Service Control Manager, which is Windows NT service, by using the access right of one of the PrintXchange users. The user has the access right to the PrintXchange server as an End User (Administrator access rights are not required), and is the owner of the gateway process. This gateway user’s name is set automatically in the user-name attribute by PrintXchange. When the gateway is installed, the installation process registers this user name. The NetWare client name is set in the job-owner attribute.
Internationalization
The NetWare server manages the whole information using the EUC code set internally. When the server replies to the client request, the code is changed based on the environment. However, there is no need to consider the NetWare locale. The QServer inbound gateway depends on the local environment. The QServer inbound gateway can work on Windows NT 4.0 (multinational). The messages are dependent on the provided message files. The QServer gateway provides both English and Japanese message files.
Service advertisement
The QServer inbound gateway service is advertised to the NetWare client in an indirect way through the NetWare native service advertisement scheme. The NetWare file server advertises the associated queue using SAP to the network. At setup time, you map the target PrintXchange logical printer to a NetWare print queue. The NetWare clients can then know of available printers supported by the QServer inbound gateway.
Translations
Command is the basic data structure of an inbound gateway operation, and command translation is the basic gateway functionality. Since there is no direct interaction between the NetWare client and the QServer inbound gateway, the gateway- interprets each print job in the print queue to be a print request. The QServer inbound gateway translates NetWare attributes to PrintXchange attributes and adds some attributes from the configuration parameters. The inbound gateway uses the POSIX- API interface to submit the jobs to the PrintXchange spooler. Table 20-4 lists the NetWare to PrintXchange attribute translations.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-27 INBOUND GATEWAYS
Table 20-4. Attribute translation from NetWare to PrintXchange
NetWare Attribute PrintXchange Description Attribute
N/A operation-locale Based on the local environment on which the gateway is running. In the remote case, locale may be different from that of the PrintXchange server. Job Description field job-owner Job owner name for accounting. In NCP Read Queue Job job-owner=ibg-qs:NetWareUserName Entry packet Job Description field job-name In NCP Read Queue Job Entry packet N/A domain-name Domain name of the target PrintXchange logical printer. N/A user-name Account name of the QServer inbound gateway service process owner created by the PrintXchange installation process. This attribute is set by the PrintXchange Security library, not by the inbound gateway. (NetWare queue name) printer-name-requested PrintXchange logical printer name registered in configuration information. numberOfCopies field Job copies Copy count. In NCP Read Queue Job Entry packet Job number, queue name, file job-identifier-on-client Created from the NetWare job number, queue name, and file server name server name:
20-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
NetWare client optional features
NetWare client provides some optional features in printing such as banner sheet, tab size, form feed and notification of job-completed. Current NetWare QServer inbound gateway partially supports some of these features.
Notification of job completed event
NetWare clients can receive a job-completed event from the NetWare server if the notification flag is set in print job. In this case, QServer inbound gateway sends the following message to the client via a pop- up window which displays one of the following messages on the client screen: 1. job completed normally "Job [job-name] has been printed." 2. job is paused by the administrator "Job [job-name] has been paused." 3. job has aborted for any reason. "Job [job-name] has been paused." 4. job has been spooled in the PrintXchange spooler, but it has been waiting to be printed more than 10 minutes. In this case, QServer inbound gateway does not send any other event to NetWare client. "Job [job-name] has been in pending state."
Output Property
NetWare client has output properties such as formfeed, tab and copy count. QServer inbound gateway only supports copy count feature. The other features are not supported.
Other features
QServer inbound gateway does not support other features such as banner-sheet, keep print data in queue option and defer-printing.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-29 INBOUND GATEWAYS
LPR inbound gateway
This section describes the printing functionality provided for the inbound line printing daemon (LPD) protocol gateway in PrintXchange. LPD protocol for printing systems is described in RFC 1179. Documented here are key PrintXchange interfaces utilized, and interfaces exposed to the PrintXchange coalition. Also included are the relationships to the X/Open PSIS, protocol extensions therein, and this implementation. References to this chapter include: X/Open PSIS Version 5.0 RFC-1179.
Overview
The LPR inbound gateway is a piece of PrintXchange software that provides on-demand protocol translation from the LPD protocol to an arbitrary printing paradigm. In the case of PrintXchange, this means LPD print protocol into ISO DPA. As illustrated in Figure 20-6, the LPR inbound gateway works on Windows NT 4.x machines. The gateway is coupled loosely with the PrintXchange spooler. The LPR inbound gateway receives LPD protocol requests from LPD clients, translates them into ISO DPA functions, and returns responses.
Figure 20-6. LPR inbound gateway component
WindowsNT machine LPD client machine LPR IBG
LPD Protocol
Because the LPR Inbound gateway conflicts with TCP/IP Print Server service, which is one of the Windows NT native services to provide LPD service, the TCP/IP Print Server service has to be stopped before the LPR-IBG starts.
20-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
How to install the LPR inbound gateway
The LPR inbound gateway may be installed on a different machine from the machine hosting the PrintXchange spooler. The LPR inbound gateway consists of the following files and gateway common libraries: pdlpribg.exe stored in %PX_ROOT%\bin pdlpribg.mdl stored in %PX_ROOT%\messages printcap. On lpr inbound gateway installation, corresponding information is stored in the Windows NT registry. The registry key name is: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ px_lpribg
Administration and configuration
Since the lpr inbound gateway is designed to provide a generalized translation service from LPD protocol to "whatever", the protocol adapter requires that an additional parameter be stored in the Windows NT Print Service Properties window. You can invoke the LPR inbound gateway from the Windows NT Service Control Manager.
Base Properties
Max number of job retries default: 0 Times Disk usage quota default: 5000 (KB)
Tuning Parameters
The LAN Manager inbound gateway limits the number of print threads to avoid keeping resources to itself. The LAN Manager print thread is created when the user submits a job to a PrintXchange printer, and exits when it receives a return value from the PrintXchange spooler. Maximum number of threads default: 16
Configuration files
The LPR inbound gateway uses the printcap configuration file with the parameters listed in Table 20-5. The file location is %PX_ROOT%\share\data\px_lpribg. The LPR inbound gateway also uses the PrintXchange Name Service Properties to record other parameters, such as those that are common to inbound gateways).
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-31 INBOUND GATEWAYS
Printcap Only the capabilities listed in table 20-5 are available in printcap, although standard capabilities are defined in printcap.
Table 20-5. Printcap capabilities
Entry Type Default value Description
Supported RFC 1179 entries
lo Text string lock Name of lock file
rm Text string NULL Machine name for remote printer
rp Text string lp Remote printer name argument
sd Text string %PrintXchange%\\spoo\\lpd Spool directory
st Text string status Status file name
sh Boolean false Suppress printing of burst page header
hl Boolean false Print the burst page list
PrintXchange LPR inbound gateway extensions
OP Text string none Printer name in the PrintXchange system
DM Text string none Domain name of the printer name in the PrintXchange environment
CD Text string none Locale
OP is the logical printer name provided by the PrintXchange spooler. It may contain multi-bytes code. Lpd client only supports ASCII code in a control file. However, PrintXchange supports multi-bites code. So, LPR inbound gateway exchanges the printer name of control files into the printer name of PrintXchange spooler according to printcap entry. DM is the domain name where the printer name belongs. PrintXchange logical printer belongs to the domain in the PrintXchange world. Logical printer is the unique inside the same domain. CD is the locale. The LPR inbound gateway supports locale to print the job. The locale supported depends on that supported by the target spooler. The possible values of CD are LOCALE_CC_ASCII, LOCALE_US_LATIN1, LOCALE_JP_SJIS, LOCALE_JP_EUC. The LPR inbound gateway sets the PrintXchange locale attribute with the CD value via the POSIX API.
20-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
The printcap sample (printcap.smpl) file is located at: %PX_ROOT%\share\data\px_lpribg\printcap.smpl Each time the printcap file is created or changed the user must Stop and ReStart the LPR Inbound Gateway from the WinNT Service Control Manager to have the changes take effect. CAUTION: It is recommended that you create a printcap file based on the printcap.smpl using the editor (Word Pad etc.). Printcap is copied as printcap.smpl by the PrintXchange Installer. The information must appear exactly as it does in the sample, use tabs not spaces or the printer will not print. :sd= You must create spool directories described as “sd” in each entry. :lo=lock:sh:\ :OP=(printer’s name registered in PrintXchange world):\ :DM=domain name of OP registered in PrintXchange world):
:CD= LOCALE_CC_ASCII LOCALE_US_LATIN1 LOCALE JP_SJIS LOCALE_JP_EUC
The following printcap file example sends information to a spooler running on NT. NTComputer_IBGW1:\ :sd=C\:\\PrintXchange\\var\\spool\\px_lpribg\\computer_ibgw1 :lo=lock:sh:\ :OP=PXCNT logical printer_lp:\ :DM=yourdomain:\ :CD=LOCALE_US_LATIN1:
Advantage between control file entries and printcap entries
The LPR inbound gateway takes priority entries of control file over entries in printcap.
Cross domain/cross platform support
To enable cross-domain submissions, you have to specify the domain name for each logical printer object in the printcap file with the DM entry (see Table 20-6). To enable cross platform submission, you also have to specify the domain name for each logical printer object in the printcap file DM entry. The domain name entry must be prefixed with: For an NT PrintXchange server: winnt: or ntsecurity: Examples: :DM=winnt:YOUR DOMAIN -- Cross Domain :DM=nis/YOUR DOMAIN -- Cross Platform
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-33 INBOUND GATEWAYS
The following printcap file example sends information in a cross- domain submission to a spooler running on UNIX. UNIXComputer_IBGW2:\ :sd=C\:\\PrintXchange\\var\\spool\\px_lpribg\\computer_ibgw1 :lo=lock:sh:\ :OP=PXC UNIX logical printer_lp:\ :DM=nis/yourdomain:\ :CD=LOCALE_US_LATIN1:
Basic operation
The LPR inbound gateway provides translation from LPD protocol into ISO DPA via the POSIX API. The LPR inbound gateway consists of three primary functions. Receive LPD protocol commands (lpr, lpq, lprm) Execute PrintXchange commands corresponding to LPD protocol commands Process events for system logging and for the PrintXchange spooler. All jobs that LPR inbound gateway receives correctly are processed completely without data loss. At least 16 lpd clients can submit jobs at the same time.
Figure 20-7. Architecture of the LPR inbound gateway
WindowsNT
Service Control System Logging Manager
LPD Client
main Event Processing lpr/lpq Odyssey Spooler /lprm Execute Request Reception DPA Oti
JOBS lpr inbound gateway
LPD protocol requests
LPR inbound gateway startup
When inbound gateway starts up, it behaves as follows. 1. Get tuning parameters from the Windows NT PrintXchange Name Service Properties. 2. Get the list of available printers via the PrintXchange command. 3. Check incomplete jobs in the specified spool. 4. Submit jobs, if available.
20-34 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
5. Receive new commands from LPD clients. You can stop the LPR inbound gateway immediately via the Windows NT Service Control Manager. The LPR inbound gateway does not stop by itself even if the target spooler is forced to shut down, because the LPR inbound gateway may support the target spooler that works on the other machine.
Internationalization
RFC 1179 defines that character codes used in the line printer daemon be ASCII. However, the LPR inbound gateway supports other character codes, since some LPD clients use other character codes such as Shift-JIS. In a control file, it is possible to encode the file name and user name in Shift-JIS. The file name and user name correspond to attributes job-name and job-owner (job-originator) of DPA. The PrintXchange spooler may support multi-byte codes for the logical/physical printer name. Because RFC 1179 does not allow the user to use other character codes except ASCII, the LPR inbound gateway has to translate the code. If the PrintXchange spooler does not use multi-byte codes for printer name, LPD does not care the printer name.
Restrictions
Note the following restrictions: RFC 1179 defines that all characters be ASCII in a control file. However some LPD clients use other character codes, such as shift-JIS, in control files. If the LPR inbound gateway detects a character other than ASCII, it translates the code to “_”(0x5F). Do not start the TCP/IP Print Server Service because the LPR inbound gateway uses the same TCP/IP port number. Do not use a second Ethernet card. Because Windows NT gets an IP address from a machine name, it does not have the second name for another Ethernet card. The maximum number of data files in a job is 832, depending on the naming rule of the BSD 4.3 implementation ( ‘s’ - ‘d’ + 1) * 2 * 26 = 832 ).
Translations
The adapter implements protocol translations as defined in the X/Open XDPA (PSIS). The PSIS forms the reference to which all translation occurs. Table 20-6 shows how LPR inbound gateway requests are translated to PrintXchange commands and attributes.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 20-35 INBOUND GATEWAYS
This page intentionally left blank.
20-36 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
Job and File Messages
CF_CLASS1 C C(ClassName) class name: (banner) (job) (hostname) -C (none) job-comment
CF_HOST H H(Hostname) host submitting job: 1(job) (hostname) (none) (none) job-originating-host
CF_INDENT I I(indent) indent spaces: (job) (none) (none) (none) (currently ignored)
CF_JOBNAME1 J J(Jobname) name of job: (banner) (job) (1st file -J -t job-name name)
CF_JOBCOPIES number of copies: (job) (1) -#
CF_PRINT_BANNER1 L L(User) User name: (banner) (job) (user) (none) (none) (currently ignored) don't use banner: (job) -h -o nobanner
CF_MAIL M M(user) User to mail when done: (job) None -m -m notification-profile
CF_SOURCE_NAME N N(name) source of data file: (file) (file name) (none) (none) document-name
CF_USER P P(name) requesting user: (job) (user) (none) (none) job-originator, job-owner
CF_SYMLINK S S(dev) (inode) file info: (file) None -s (default) (no mapping)
CF_TITLE2 T T(title) title: (for pr) (file) None -T (none) (currently ignored)
CF_UNLINK U U(file) unlink file: (file) (data file) (none) (none) (no mapping) unlink source file when done: None -r (none) (file)
CF_WIDTH W W(width) column width: (for pr) (job) None -w -w (currently ignored)
CF_FONT_TROFF_R3 1 1(file) Times Roman font file: (roff)(job) None -1 (none) (no mapping)
CF_FONT_TROFF_I3 2 2(file) Times Italic font file: (roff)(job) None -2 (none) (no mapping)
CF_FONT_TROFF_B3 3 3(file) Times Bold font file: (roff)(job) None -3 (none) (no mapping)
CF_FONT_TROFF_S3 4 4(file) Times Special font file: (roff)(job) None -4 (none) (no mapping)
Print Messages
CF_PRINT_CIF c c(file) print/plot file as CIF data None -c -T cif document-format
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-37 INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_PRINT_DVI d d(file) print file as DVI data None -d -T dvi document-format
CF_PRINT_ASCII f f(file) print file as ASCII (default) (none) -T ascii document-format
CF_PRINT_PLOT g g(file) print file as plot data None -g -T plot document-format
Print Messages (continued)
CF_KERBERIZED k k... for Kerberos ??? ??? ??? ??? ???
CF_PRINT_CAT_V l l(file) print file converting non- None -l -y catv_filter document-format printables -o nofilebreak
CF_PRINT_DROFF n n(file) print file as ditroff output None -n -T ditroff document-format
CF_PRINT_PS o o(file) print file as PostScript None -o -T ps document-format -T Postscript
CF_PRINT_PR p p(file) print file thru "pr" None -p -T pr document-format
CF_PRINT_FORT r r(file) print file as fortran None -f -T fortran document-format
CF_PRINT_TROFF t t(file) print file as troff output None -t -T troff document-format
CF_PRINT_RAS v v(file) print file as raster image None -v -T raster document-format
CF_PRINT_PLDM z z... for Palladium ??? ??? ??? ??? (???)
Sun Protocol Extensions
CF_SYSV_OPTION4 O O(option_list) for SVR4 LP -o option None (none) -o option_list (currently ignored)
CF_SYSV_FEATURE 5 5(opt)(value) for SVR4 LP features None (none) (not an option)
CF_SYSV_FORM 5f 5f(form) for SVR4 Forms None (none) -f form_name (currently ignored)
CF_SYSV_HANDLING 5H 5H(handling) for SVR4 Handling None (none) -H (currently ignored)
CF_SYSV_NOTIFICATION 5p 5p(method:end) for SVR4 Notification None (none) -p (currently ignored)
CF_SYSV_PAGES 5P 5P(pagelist) for SVR4 Pages None (none) -P page_list page-select
CF_SYSV_PRIORITY 5q 5q(priority) for SVR4 Priority None (none) -q priority job-priority
20-38 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_SYSV_CHARSET 5S 5S(char set) for SVR4 Charset None (none) -S char_set (currently ignored)
CF_SYSV_TYPE 5T 5T(type) for SVR4 Type None (none) -T input_type document-format
CF_SYSV_MODE 5y 5y(mode) for SVR4 Mode None (none) -y filter_mode (currently ignored)
DEC Protocol Extensions
CF_DEC_INPUT_TRAY < <(tray) Input tray selection None -< (upper|lower| (none) default-input-tray manual|...)
CF_DEC_OUTPUT_BIN > <(bin) Output bin selection None -> (bin) (none) output-bin
DEC Protocol Extensions (continued)
CF_DEC_NUMBER_UP G G(nup) Number up None -G (nup) (none) number-up
CF_DEC_SIDES_PLEX K K(sides/plex) Sides None -K (sides/plex) (none) sides, plex
CF_DEC_ORIENTATION4 O O(orientation) Page orientation None -O (orientation) (none) content-orientation
Xerox Protocol Extensions—DocuSP
CF_CLASS2 C C" (doc-format) "5 Document format, doc-format= None -C -o document-format= ps PostScript postscript PostScript ascii simple-text tiff TIFF pcl PCL
CF_CLASS C C" (orientation) " Document orientation, None -C -o content-orientation= orientation= portrait portrait landscape landscape
CF_CLASS C C" (simplex)" One-sided printing None -C -o sides=1
CF_CLASS C C" (duplex)" Two-sided printing None -C -o sides=2
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-39 INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" (tumble)" Head-to-toe printing None -C -o sides=2, plex=tumble
CF_CLASS C C" (mediumsize)" Medium size, mediumsize= None -C -o default-medium= usletter na-letter-white uslegal na-legal-white usledger ledger-white a0 iso-a0-white a1 iso-a1-white a2 iso-a2-white a3 iso-a3-white a4 iso-a4-white a5 iso-a5-white a6 iso-a6-white a7 iso-a7-white a8 iso-a8-white a9 iso-a9-white a10 iso-a10-white isob0 iso-b0-white isob1 iso-b1-white isob2 iso-b2-white isob3 iso-b3-white isob4 iso-b4-white isob5 iso-b5-white isob6 iso-b6-white isob7 iso-b7-white isob8 iso-b8-white isob9 iso-b9-white isob10 iso-b10-white jisb0 jis-b0-white jisb1 jis-b1-white jisb2 jis-b2-white jisb3 jis-b3-white jisb4 jis-b4-white jisb5 jis-b5-white jisb6 jis-b6-white jisb7 jis-b7-white jisb8 jis-b8-white jisb9 jis-b9-white jisb10 jis-b10-white
20-40 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" Media custom option None -C -o (no mapping) (media=
CF_CLASS C C" (mediaType= Media custom option None -C -o (no mapping)
CF_CLASS C C" (mediatSize= Media custom option None -C -o (no mapping)
CF_CLASS C C" (mediaColor= Media custom option None -C -o (no mapping)
CF_CLASS C C" (mediaWeight Media custom option None -C -o (no mapping) =
CF_CLASS C C" (opacity= Miscellaneous option None -C -o (no mapping) transparency| opaque)"
CF_CLASS C C" (font)" Font name None -C -o (no mapping)
CF_CLASS C C" (xshift=x)" Shift the page in the x direction None -C -o x-image-shift=x
CF_CLASS C C" (yshift=x)" Shift the page in the y direction None -C -o y-image-shift=y
CF_CLASS C C" (xshift2=x)" Shifts the back side of the page None -C -o (no mapping) in the x direction
Xerox Protocol Extensions—DocuSP (continued)
CF_CLASS C C" (yshift2=x)" Shift the back side of the page in None -C -o (no mapping) the y direction
CF_CLASS C C" (prefinish= Media prefinish option None -C -o (no mapping)
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-41 INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" (bind=left) " Binding None -C -o finishing=bind
CF_CLASS C C" (staple) " Document stapling, staple= None -C -o finishing= staple staple
CF_CLASS C C" (stitch)" Document stapling None -C -o finishing=staple
CF_CLASS C C" (stitch=how)" Document stapling, how= None -C -o finishing= singleportrait staple-top-left singlelandscape staple-bottom-left duallandscape staple-dual-left
CF_CLASS C C" (uncollate) " Collation None -C --- output=no-page-collate
CF_CLASS C C" (booklet) " Finishing None -C --- finishing=saddle-stitch
CF_CLASS C C" (slipsheet)" Slipsheet option None -C -o document-sheets=doc-set-start- copies-separate
CF_CLASS C C" (pagestoprint Pages option None -C -o (no mapping) =
CF_CLASS C C" (account= Account option None -C -o (no mapping)
CF_CLASS C C" (hipentry= LCDS index option None -C -o (no mapping)
CF_CLASS C C" (recipient= Recipient option None -C -o (no mapping)
CF_CLASS C C" (res= Resolution option None -C -o (no mapping)
CF_CLASS C C" (outputbin)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (inputbin)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (thicken)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (offenhance)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (onenhance)" Miscellaneous option None -C -o (no mapping)
20-42 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
Xerox Protocol Extensions—DocuSP (continued)
CF_CLASS C C" (bp)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (ep)" Miscellaneous option None -C -o (no mapping)
CF_CLASS C C" (diagnostic)" Miscellaneous option None -C -o (no mapping)
Xerox Protocol Extensions—DocuPrint
CF_CLASS2 C C" (doc-format) "5 Document format, doc-format= None -C --- document-format= ps PostScript ps2 PostScript postscript PostScript ascii simple-text pcl PCL interpress Interpress ip Interpress
CF_CLASS C C" (orientation) " Document orientation, None -C --- content-orientation= orientation= portrait portrait reverse-portrait inverseportrait, iportrait landscape landscape reverse-landscape inverselandscape, ilandscape
CF_CLASS C C" (simplex)" One-sided printing None -C --- sides=1
CF_CLASS C C" (duplex)" Two-sided printing None -C --- sides=2
CF_CLASS C C" (tumble)" Head-to-toe printing None -C --- sides=2, plex=tumble
CF_CLASS C C" (order)" Page order, order= None -C --- page-order-received= 1ton first-to-last nto1 last-to-first
CF_CLASS C C" (mediumsize)" Medium size, mediumsize= None -C --- default-medium= usletter na-letter-white uslegal na-legal-white a4 iso-a4-white
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-43 INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" Media custom option None -C --- (no mapping) (media=
CF_CLASS C C" (
Xerox Protocol Extensions—DocuPrint (continued)
CF_CLASS C C" (font)" Font name None -C --- (no mapping)
CF_CLASS C C" (size)" Font size None -C --- (no mapping)
CF_CLASS C C" (fontsize)" Font size None -C --- (no mapping)
CF_CLASS C C" (xshift=x)" Shift the page in the x direction None -C --- x-image-shift=x
CF_CLASS C C" (yshift=x)" Shift the page in the y direction None -C --- y-image-shift=y
CF_CLASS C C" (hc=color) " Highlight colour,color= None -C --- highlight-colour= red red blue blue green green cyan cyan magenta magenta yellow yellow cardinal cardinal royalblue royalblue ruby ruby violet violet black black customName customName
CF_CLASS C C" (mc=color)" highlight mapping color, color None -C --- highlight-mapping-colour, values values are same as for same as for highlight-colour highlight colour, color
CF_CLASS C C" highlight color rendering None -C --- highlight-colour-rendering- (hcr=rendering)" alorighm, rendering= algorithm= automatic automatic colortohighlight colourToHighlight colortables colourTables presentation presentation pictorial pictorial
20-44 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" (hcm=action)" highlight color mismatch action, None -C --- highlight-colour-mismatch-action= action= abort abort ignore ignore operator operator
CF_CLASS C C" (thick=x))" thickening, x= None -C --- thickening-specification= 01 thickening-entire-documents 10 thickening-bit-map-images
CF_CLASS C C" (drilled) " Media prefinish option None -C --- (no mapping)
Xerox Protocol Extensions—DocuPrint (continued)
CF_CLASS C C" (staple) " Document stapling, staple= None -C --- finishing= staple staple nostaple none
CF_CLASS C C" (stitch)" Document stapling, stitch= None -C --- finishing= stitch staple nostitch none
CF_CLASS C C" Decomp service option None -C --- (no mapping) (disposition=<>)"
CF_CLASS C C" Decomp service option None -C --- (no mapping) (backgroundform =<>)"
CF_CLASS C C" (bf=<>)" Decomp service option None -C --- (no mapping)
Fuji Xerox Protocol Extensions—LaserPress 4150PSII
CF_CLASS C C" (input-tray)" Specify the input tray, input-tray= None -C --- default-input-tray= INTRAY1, intray1 1 INTRAY2, intray2 2 INTRAY3, intray3 3 INMF, inmf manual
CENTER output-bin=cente-binr
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-45 INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" (input-tray)" Specify the input tray that has the None -C --- default-medium= media size., input-tray= A3, a3 iso-a3-white B4, b4 jis-b4-white A4, a4 iso-a4-white B5, b5 jis-b5-white A4SEF, a4sef (no mapping) A4LEF, a4lef (no mapping) B5SEF, b5sef (no mapping) B5LEF, b5lef (no mapping)
CF_CLASS C C" (mediasize)" Media size, mediasize= None -C --- default-medium= LETTER, letter na-letter-white LEGAL, legal na-legal-white
Fuji Xerox Protocol Extensions—Able3321
CF_CLASS C C" (mediasize)" Media size, mediasize= None -C --- default-medium= A3, a3 iso-a3-white B4, b4 jis-b4-white A4, a4 iso-a4-white B5, b5 jis-b5-white A5, a5 iso-a5-white LETTER, letter na-letter-white LEGAL, legal na-legal-white
CF_CLASS C C" (input-tray)" Input tray, input-tray= None -C --- default-input-tray= INTRAY%n, intray%n n (1<= n =< 4) INMF, inmf manual
CF_CLASS C C" (input-tray)" Input tray, input-tray=output-bin None -C --- output-bin SIDE, side side/center CENTER, center mailbox-n (1<= n =< 20) MBOX%n, mbox%n
CF_CLASS C C" (plex)" plex= None -C --- plex= DUP, dup duplex TUMBLE, tumble tumble SIMP, simp simplex
CF_CLASS C C" (collate)" collate = no-page- -C --- output= COLLATE, collate collate page-collate
20-46 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INBOUND GATEWAYS
Table 20-6. lpr inbound gateway translations
Name Key Usage Description Default LPR option LP option Attribute set
CF_CLASS C C" (staple)" Staple, staple= None -C --- finishing= STAPLETL staple-top-left STAPLETD staple-dual-top STAPLETR staple-top-right STAPLELD staple-dual-left STAPLERD staple-dual-right STAPLEBL staple-bottom-left STAPLEBD staple-dual-bottom STAPLEBR staple-bottom-right
Notes: 1 CF_CLASS, CF_JOBNAME, CF_PRINTER_BANNER will all appear together or not at all. 2 CF_TITLE will only appear if the print type is CF_PRINT_PR. 3 CF_FONT_TROFF_* will only appear if the print type is either CF_PRINT_DVI, CF_PRINT_DROFF, or CF_PRINT_TROFF. The "Print message" will be repeated # of copies times for each file in a job. 1 -# -n 4 CF_SYSV_OPTION and CF_DEC_ORIENTATION conflict and only the orientation is currently processed. 5 The LPR -C option for the Xerox extensions always requires quotes and parentheses, and uses a comma as a separator when multiple values are specified: lpr -C"(duplex)" lpr -C"(duplex, staple)". The LP -o option for the Xerox extensions does not use parentheses, requires quotes only when multiple values are specified, and uses a space as a separator: lp -o duplex lp -o "duplex staple"
PRINTXCHANGE 1.11 SYSTEM ADMISTRATION AND OPERATIONS GUIDE 20-47 INBOUND GATEWAYS
20-48 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 21. Managing printed output
This chapter describes parameters related to managing the process that takes place at the output device to produce the printed output using PrintXchange. The printed output attributes allow you to request a specific output device and to specify: number of copies highlight color separator pages output bins input trays media finishing.
Requesting a specific output device
The physical-printers-requested attribute identifies the physical printer or printers that will be the only candidates for printing the job. The spooler checks for a match against the logical printer’s physical- printers-supported attribute
Specifying number of copies
The attributes that specify the number of copies to be printed are: job-copies (job attribute) copy-count (document attribute) maximum-copies-supported (logical and physical printer attribute). The spooler uses the following test to determine the validity of the job-copies and copy-count values in multiple document jobs: For each document in a job, the spooler ensures that the product of job-copies and copy-count is less than maximum-copies- supported if maximum-copies-supported is set. If a document fails the test during print submission, the spooler rejects the document. If the spooler had already accepted a job and the user is trying to set or modify copy-count on a particular document and it fails the test, then the spooler rejects the set or modifies the operation. When trying to set or modify job-copies on a previously submitted job, the spooler ensures that each document in the job passes the test. If any document fails, then the spooler rejects the request.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 21-1 MANAGING PRINTED OUTPUT
Specifying highlight color
The attributes that relate to highlight color are only used with highlight color printers: highlight-colour (document attribute) highlight-colours-supported (logical and physical printer attribute) highlight-colour-mismatch-action (document attribute) highlight-colour-rendering-algorithm (document attribute) highlight-colour-rendering-algorithms-supported (logical and physical printer attribute) highlight-mapping-colour (document attribute) highlight-mapping-colours-supported (logical and physical printer attribute) thickening-specification (document attribute) thickening-supported (logical and physical printer attribute) The document attribute highlight-colour-mismatch-action determines how PrintXchange handles highlight color jobs when there is a mismatch between the color specified for the document and the highlight color supported or ready at the printer (highlight- colours-supported and highlight-colours-ready). The possible values for highlight-colour-mismatch-action are: ignore - the spooler ignores the highlight color mismatch and continues to accept and schedule the document/job for printing. operator - operator intervention is required to resolve the mismatch; the spooler: Rejects the document/job if the matching highlight color is not supported Accepts but does not schedule the document/job if the matching highlight color is supported but is not ready . abort - the spooler rejects the document/job if: The matching highlight color is not supported. The matching highlight color is supported but is not ready. (No value specified) - the spooler: Rejects the document/job if the matching highlight color is not supported Accepts but does not schedule the document/job if the matching highlight color is supported but is not ready.
21-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING PRINTED OUTPUT
Specifying separator pages
Reference supervisor The reference supervisor creates both job and document sheets. Job sheets are printed using the undocumented attribute, paf-job- separator-format. If that attribute is not specified, even though it (although it always should be since it is included in printer attribute files, then no separator pages will be printed. Document sheets are printed using the printer’s native document format that is in use for the document being printed. For example, if a job specifies printing document sheets, and a simple-text document will be printed on a PostScript printer (through the use of the simple- text-to-PostScript translation filter), then the document sheets will be printed using PostScript. This reduces otherwise aggravating PDL- switching overhead. On a PostScript printer, separator pages are tastefully formatted. Note that this formatting information may include additional information. On any other printer, the separator page will begin with a distinctive horizontal bar of characters, followed by the attribute information printed in the upper left corner of the page using the default font. The information is formatted such that it fits on A5 paper (148mm X 210mm) assuming a fixed pitch font with 10 characters per inch. The supervisor uses the ASCII form-feed character (octal 014) to eject simple-text separator pages. It uses the "showpage" operator to eject and print PostScript separator pages. Separator sheets are always printed on a separate sheet of paper, even if the document is printed on both sides of the paper. If any of the attribute values printed on a separator sheet require static text, that text will be read from a message file to facilitate internationalization. For example, if a start sheet says: Submitted at: xxxxxxxxxxxxxx, the “Submitted at:” will be read from a message file. Xerox supervisor The Xerox supervisor creates job sheets and document sheets with the same separator page layout as the reference supervisor. Users have to set attribute job-sheet and document-sheet to enable separator page printing since the default is not separator page. The separator sheet format is derived from the document attribute document-format of the first document. This means its format may differ from the original document format if the document has run through any filters. Currently in this version of PrintXchange, internationalization is not facilitated, the separator page is a hard coded to the US English only.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 21-3 MANAGING PRINTED OUTPUT
job sheets
PrintXchange supports the following values for the job-sheets attribute: none job-copy-start: A start sheet in front of every copy of the job job-copy-wrap: A start sheet and end sheet for every copy of the job. Note: If more than one copy of a job has been requested, there will not be “whole-job” sheets that surround the entire job, just separators for each copy. Job sheets are usually a site policy. That is, if you want job separator sheets, you must remove none as a value of the job-sheets- supported printer attribute and ensure that all logical printers have an initial-value-job that provides a default for job-sheets. Then the user cannot override the site policy by specifying none as a value for job-sheets. The values of the following attributes are printed on a job start sheet: job-name job-identifier job-owner job-originating-host printer-name-requested printers-assigned submission-time job-comment job-message-from-administrator. The values of the following attributes will be printed on a job end sheet: job-name job-identifier job-owner completion-time. (Does not appear on jobs printed from a Xerox supervisor.) Also, the following information will be printed on both the job start and end sheets: “Product name” string read from a message file (truncated to forty bytes) Name and version number of the operating system. “Burst" pages, that is, print over the perforation at the beginning of each job, are not supported in PrintXchange. Only jobs that complete successfully or complete with errors get an end job sheet. Jobs that are cancelled or that are aborted due to errors do not get an end job sheet.
21-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING PRINTED OUTPUT
Document sheets
The values supported for the job attribute document-sheets are: none doc-set-start-copies-separate: A separator sheet precedes every copy of the document. For example: pdpr -x “document-sheets = doc-set-start-copies-separate” file1 The names and values of the following attributes are printed on a document start sheet: document-name document-sequence-number job-name job-owner document-file-name document-format default-font default-input-tray number-up sides reset-printer. Also, on printers capable of printing PostScript, the following information may be printed on the document start sheet: “Product” string that represents the manufacturers name for the product (for example, LaserJet III Si or PrintServer 32) “Printername” string that represents the name of the printer in the local environment (for example, “Bob’s HP3Si”) In most PostScript implementations, the factory setting for “printername” is the same as for “product”. However, users familiar with PostScript can change the printername string. PrintXchange suppresses the printername string if it is identical to the product string.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 21-5 MANAGING PRINTED OUTPUT
Specifying media, input trays, and output bins
There are two common ways to select media for printing: By input tray By media type. The supervisor supports the input-trays-ready and input-trays- supported attributes only to the extent that you can set their values by way of a printer attributes file. The supplied printer attributes files contain suitable lists of trays that are supported for their respective printer models.
Selecting media by input tray
The reference supervisor can select input media by input tray. It uses the document attribute default-input-tray for determining from which tray to pull blank media.
Selecting media by media type
The reference supervisor can select input media by media type, if that media type is associated with an input tray with the printer attribute input-trays-medium. The association must be set up by you or an operator by assigning values to the input-trays-medium attribute. If a document specifies both default-input-tray and default- medium, the medium takes precedence. If default-medium is specified but input-trays-medium has not been specified, the job is printed without selecting a tray.
Selecting output bins
The supervisor sets the default output bin when a job begins processing. All well-behaved documents that comprise the job are deposited in the specified output bin. Some documents, especially those originating on PCs, contain output tray selection command sequences. The supervisor does not intercept or redefine these commands. Therefore, such jobs or portions of such jobs may draw from trays or be deposited in bins other than the ones specified in the attributes output-bin and default-input-tray.
Specifying finishing
The document-finishing attribute specifies a sequence of processes to be applied to the document, such as stapling, saddle stitch, edge stitch, punch, cover, and bind. The finishing processing is controlled by the printer. The supervisor contains no support for any finishing options.
21-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT MANAGING PRINTED OUTPUT
Resetting the printer
The document attribute reset-printer is only applicable to jobs printed from the Reference supervisor. It indicates that the printer should be reset between documents within a job (the printer is always reset between jobs). This attribute causes the reset sequence to be sent to the printer after its associated document. For example, to condition a PostScript printer with font data, use a command such as the following : pdpr -p lp1 -x “reset-printer=no” -f fonts.dat - x “reset-printer=yes” file.ps Printing document auxiliary sheets requires a printer reset so if the job has a value for the attribute document-sheets, the printer will always be reset between documents regardless of the value of reset- printer. Also, document attributes that would cause the printer to be reconfigured, such as sides, trays, and bins, also require that the printer be reset. Therefore, if the document following a document with reset-printer=no specifies document attributes that are different, the reset is ignored.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 21-7 MANAGING PRINTED OUTPUT
21-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22. Troubleshooting
This chapter describes some of the PrintXchange elements that can help users determine the cause of some PrintXchange problems. The topics included are: Troubleshooting introduction System logging Restrictions for e-mail notification on Windows NT Error messages Crash recovery. Note: This chapter includes troubleshooting related information for both Windows NT and UNIX environments.
Troubleshooting introduction
Troubleshooting is the process that enables users to determine the cause of a problem, given specific system behavior, and to invoke the appropriate action to correct the problem. PrintXchange does not yet have a formal troubleshooting process. However, there are several steps that users can take to determine the cause of a problem, and from there determine a course of action. Topics covered in this section are: Checking object states Checking certain attributes Doing job diagnostics Checking UNIX files. Subsequent sections in this chapter provide information on system logging, describe error messages, and discuss crash recovery.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-1 TROUBLESHOOTING
Object states
Document, job, printer, queue, and server objects have attributes that contain the current state of the object. Initial-value-job and initial- value-document objects do not have states. The attributes are: document-state (for document objects) current-job-state (for job objects) printer-state (for printer objects) state (for queue objects) server-state (for server objects) Table 22-1 lists the PrintXchange object states that correspond to a given object’s state attribute. An additional attribute called enabled determines whether or not a supervisor, spooler, queue, logical printer, or physical printer is currently enabled or disabled. That is, an object that is disabled can not accept jobs. However, the object’s state attribute may indicate that the object is ready. Therefore, for example, in trying to determine why a job can’t get onto a queue whose state attribute is ready, check the value of the queue’s enabled attribute. It is likely set to disabled.
Table 22-1. Object states
Object State Description
Document transfer-pending The spooler has not completely retrieved the document.
pending The normal state for documents waiting in the spooler to be printed.
processing The spooler submitted the job, including this job, to the supervisor but the supervisor has not yet begun to print the document.
printing Not supported.
completed The document has been printed.
Job pre-processing The spooler has not completely retrieved the job.
pending The normal state for jobs waiting in the spooler to be printed.
processing The spooler submitted the job to the supervisor but the supervisor has not yet begun to print the job.
printing The job is printing. If the physical printer state is also printing, paper is coming out.
held A user set the job-hold attribute to true. The job will not be printed until the user sets the attribute to false.
paused The job has been paused; it will not continue until the job is resumed.
completed A transitory state indicating that the job has been printed and the job-retention- period has expired.
retained The job is complete, but the job-retention-period has not expired.
22-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-1. Object states
Object State Description
terminating The job has been canceled or aborted by the server and is in the process of terminating.
unknown The job is not known, or indeterminate, or is not returned by the operation.
Logical idle The logical printer is accepting jobs. This is the only state for logical printers. printer
Physical idle The printer is waiting for a job. printer
printing A job is printing normally.
needs-attention A job is printing but the printer has informed the supervisor that something is wrong with the printer (e.g. paper out).
paused The printer has been paused; printing won’t start until the printer is resumed.
shutdown Unsupported state.
timed-out The printer has not been accepting data for a period in excess of the value of the printer attribute printer-timeout-period.
connecting-to- The supervisor is connecting to the printer and performing any printer printer initialization activities. If the printer remains in this state for a long time, it indicates that there is some trouble communicating with the printer or that the printer is busy with other, non-PrintXchange printing.
unknown The printer is not known, or indeterminate, or is not returned by the operation.
Queue ready The normal state for a queue.
paused The queue has been paused; printing won’t start until the queue is resumed.
Server ready The normal state for a server.
terminating The server is in the process of shutting down and exiting.
paused The server has been paused; printing won’t start until the server is resumed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-3 TROUBLESHOOTING
Attributes
Be aware of the following attributes: printer-address. PrintXchange does not do any error checking on the value of the printer-address attribute. Users must be sure to enter a valid address for the printer port. The only way that users can learn that they may have entered an invalid value is when PrintXchange tries to connect to the printer and it fails. document-format. Users should make sure that the applicable physical printer’s document-formats-supported, document- formats-ready, and native-document-formats-ready match the document’s document-format attribute. If the attributes don’t match, problems printing from the inbound gateway. The attributes must also match when users create different physical printer objects for the PostScript and PCL versions of the same printer model. Also, if a job continues in the pending state even after jobs subsequently submitted get printed, it may be because one or more of the destination physical printer’s xxx-ready attributes do not match the corresponding xxx-supported attributes of the logical printer to which the job was submitted. Remember that a job is printed only when the physical printer’s xxx-ready attributes completely match the associated logical printer’s xxx-supported attributes. The job diagnostics utility, pddiagjob, can check xxx-ready and xxx- supported attributes (refer to the section on Job diagnostics).
22-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Job diagnostics
The pddiagjob utility allows users to determine why a pending job does not print. The utility applies primarily to jobs whose current- job-state is pending, held, and paused. The utility may be used with jobs in other states, in which case the utility checks the job but does not generate error messages. The utility runs via the CLI on both the UNIX and NT platforms. Note, though, that on the NT the utility requires the BASH shell and also requires the LANG environment variable for non-US English locales.
pddiagjob operation
UNIX systems The utility command is: pddiagjob [serverName:][jobID] .... pddiagjob -h (lists help message) pddiagjob -V (lists software version number) If serverName is not specified, the utility uses the server associated with the PDPRINTER environment variable. If jobID is not specified, the utility checks all pending, held, and paused jobs in the spooler. Note that multiple jobs can be specified. Windows NT/Windows 95 systems The GUI application command is: pddiagjob When the user invokes the command at the Windows NT/Windows 95 console window, the utility displays the windows illustrated in Figure 22-1.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-5 TROUBLESHOOTING
Figure 22-1. Diagnostic utility Windows NT/Windows 95 window
The window features are: Server radio buttons Default. If set, the utility uses the server associated with the PDPRINTER environment variable. If the PDPRINTER environment variable is not available, this option button and default server name field is disabled. Other. If set, the user must specify the PrintXchange server name. Jobs radio buttons All. If set, the utility checks all pending, held, and paused jobs in the spooler. Specific. If set, the user must specify one or more job identifiers. The utility checks only the specified jobs. Version button. When selected, the utility displays version information of the pddiagjob utility. Diag… button. When selected, the utility executes the job diagnostics.
22-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Utility diagnostics
The pddiagjob utility checks for: Intervening jobs Job being paused Job being held Spooler being paused Queue being paused If queue has any physical printers As follows, for every physical printer associated with the queue (or as specified with physical-printers-requested if specified with the job): Supervisor being disabled Physical printer being paused Physical printer being disabled Physical printer being busy Physical printer needing attention Physical printer being timed out Presence of a job submission library (Xerox supervisor only) Presence of a job submission channel (Xerox supervisor only) xxx-ready attributes against job/document attributes xxx-supported attributes against job/document attributes. For jobs in the pending, held, or paused state, the utility displays: Spooler name Queue name Physical printer names for each job Reasons why the job is not printing. For jobs in states other than pending, held, or paused, the utility displays the job state and the following additional information: For completed state: job-completion-period, job-state- reasons, and job-state-message (if present) For retained state: job-retention-period, job-state-reasons, and job-state-message (if present) For processing or printing state: printer-state and assigned printer (if present) For other job states: job-state-reasons (if present) and job- state-message (if present) The pddiagjob utility considers a printer busy if the printer-state is saturated, printing, or connecting-to-printer.
Limitations
For image-shift (realSyntax) attributes, the utility it checks only integer values, so it ignores any fractions.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-7 TROUBLESHOOTING
Example
Command: pddiagjob 24 Results: Job Identifier: 24 Job name: ExitScript Assigned spooler: miles_spl Assigned queue: Penelope Physical printer(s): Laertes Odysseus Eumaeus The job is not printing for the following reason(s): The queue has 7 intervening job(s) to schedule before this job. Printer "Laertes" is disabled. Printer "Odysseus" does not support "simple-text" in its "document-formats-ready" attribute. Printer "Odysseus" does not support "4" in its "numbers-up- supported" attribute. Printer "Eumaeus" is disabled. Printer "Eumaeus" does not support "2" in its "sides-ready" attribute. Printer "Eumaeus" does not support "duplex" in its "plexes- supported" attribute.
22-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Windows NT/Windows 95 systems The utility results are displayed as illustrated below.
Figure 22-2. Windows NT/Windows 95 diagnostic utility results
UNIX files
On PrintXchange systems running under UNIX, some PrintXchange components require an entry in certain UNIX files, as follows: inetd.conf This file requires entries for the ProtoServer, Notification Server, and inbound gateway. The effect of omitting an entry for one of these PrintXchange components may be: For ProtoServer, repeated name space errors. For Notification Server, failure in the delivery of event messages. For inbound gateway, failure to print inbound gateway jobs or inclusion of inbound gateway job in the queue. nsswitch.conf This file includes an entry that specifies the name service search order. The inclusion of an appropriate entry for this file is not required since PrintXchange defaults to the search order of Local File and then NIS. printers.conf For Local File naming, this file is required to include an entry for each PrintXchange object (spooler, supervisor, queue, logical printer, and physical printer). Name service errors occur if the file does not include an entry for a PrintXchange object. Note: When both printers.conf file and NIS map have the same entry, the GUI will display the same item twice. This occurs when a System Administrator creates a printer for which an entry was not
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-9 TROUBLESHOOTING
added into NIS. To avoid display of the same item twice, remove the entry from the printer.conf file on that particular machine.
System logging
The PrintXchange service log facility logs server messages for purposes of serviceability. Customer field support personnel and product developers will be the primary users of the log files produced by the facility. Non-server PrintXchange components (including clients, inbound gateways, and notification server) use the standard system logging on the UNIX and NT platforms as described in the “Standard system logging” section.
Service log facility
The service log facility uses configuration attributes to specify logging functions for a server. The service log facility also provides environment variables equivalent to the server configuration attributes that non-server components may use for logging. However, this capability is available for developer use only.
Configuration attributes for logging
The configuration attributes used for logging are: system-logging-enabled system-log-file-path max-number-of-system-logs system-log-severity system-log-size. system-logging-enabled This attribute specifies whether or not logging is enabled for the entire server. If yes, the server logs messages of the severity levels specified with the system-log-severity attribute. The default is yes. system-log-file-path This attribute specifies the path for the log file. The valid values are: stdout (the standard output file) stderr (the standard error file) syslog, as specified for the syslog system logging facility: For UNIX, the file specified in the /etc/syslog.conf file (syslog) For NT, the Event Viewer if so configured syslog is the default. Absolute file path Relative file path (the service log facility offsets the relative file path from the server runtime directory specified with the server’s cfg-server-runtime-dir attribute); the relative file path is the typical value for the attribute.
22-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
When the attribute value is an absolute or relative file path, the service log facility uses the path to create a log file with a unique file name having the following format: path.mmdd.hhmmss Where: path = absolute or relative file path value of system-log-file-path mm = month 01 – 12 dd = day 01 – 31 hh = hour, based on the 24 hour clock time ss = seconds max-number-of-system-logs This attribute specifies the maximum number of log files to maintain. If a new log file is required (because the size of the current file has reached the value specified with the system-log-size attribute), then the service log facility checks if the number of existing log files matches the maximum specified with max-number-of-system-logs. If it does, the facility deletes the oldest log file before creating the new log file. Otherwise, the facility simply creates the new log file. Additionally, when this attribute is modified, the service log facility immediately checks if the maximum number of log files according to the new value is exceeded. If so, the facility deletes the oldest log files until the number reaches the maximum. Decreasing the value of max-number-of-system-logs is one way of potentially decreasing disk usage. The special value 0 indicates no limit. This attribute is ignored if stdout, stderr, or syslog is the value set for the system-log-file-path attribute.
system-log-severity This attribute specifies the set of severity levels to be logged. There are four user levels: Error Warning Audit Debug The default value specifies Error, Warning, and Status levels. system-log-size This attribute specifies the maximum size (in bytes) of a log file. If the next message logged would cause the log file size to exceed the value of this attribute, the service log facility creates a new log instead of appending the message to the current log. If the log size is modified to a value that exceeds the size of the current log, the service log facility closes the current log and creates a new one. All previously closed logs maintain their current size, but all subsequently created logs will be of the new size. The special value 0 indicates no limit. This attribute is ignored if stdout, stderr, or syslog is the value set for the system-log-file-path attribute.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-11 TROUBLESHOOTING
Using the service log facility
Using the service log facility consists of setting applicable values for the server logging configuration attributes. Examples Figure 22-3 lists a possible serviceability configuration. The spooler is logging user-level messages (i.e. error, warning, audit, and debug). The messages are being stored in log files with names beginning with “svclog”. These files are stored in the /var/spool/pd/nesbitt_spl directory as svclog.0123-172751-385, etc. Service logging is enabled. Since the maximum number of log files is set to 5 and the maximum size is set to 3,000,000 bytes, service logs occupy a maximum of 15,000,000 bytes on disk at any given time.
Figure 22-3. Logging configuration attributes—example 1
%pdls -c s -r "c-s-r-d c-l-se c-l-si c-l-f-p c-l-e c-l-m-n-o-l" nesbitt_spl nesbitt_spl: system-server-runtime-dir = /var/spool/pd/nesbitt_spl nesbitt_spl: system-log-severity = error warning audit debug nesbitt_spl: system-log-size = 3000000 nesbitt_spl: system-log-file-path = svclog nesbitt_spl: system-log-enabled = yes nesbitt_spl: max-number-of-system-logs = 5
Figure 22-4 shows a pdset command that resets max-number-of- system-logs to 3. Note that since the value has been decreased from 5, the service log facility deletes any files that are over the limit. So, for example, if there are 5 service logs on disk, 2 will be deleted. Thus, 6,000,000 bytes of disk space would be freed.
Figure 22-4. Logging configuration attributes—example 2
%pdset -c s -x c-l-m-n-o-l=3 nesbitt_spl %pdls -c s -r "c-s-r-d c-l-se c-l-si c-l-f-p c-l-e c-l-m-n-o-l" nesbitt_spl nesbitt_spl: cfg-server-runtime-dir = /var/spool/pd/nesbitt_spl nesbitt_spl: system-log-severity = error warning audit debug nesbitt_spl: system-log-size = 3000000 nesbitt_spl: system-log-file-path = svclog nesbitt_spl: system-logging-enabled = yes nesbitt_spl: max-number-of-system-logs = 3
Figure 22-5 illustrates log entries for the user-level and developer- level messages.
Figure 22-5. Log fragment
D 15 Fri Jan 23 17:18:46 1998 | Printer is requesting a job. I 15 pa.c:691 4726.746477 | lock1 global PA mutex PA_RequestJob I 6 pa_procs.c:601 4726.876018 | PA__globalData.uNewTask = 1
22-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Figure 22-6 and Figure 22-7 describe the elements of user-level and developer-level log messages. Note that all developer-level message information is for developer use only and not intended for customers. Figure 22-6. User-level log message format
D 15 Fri Jan 23 17:18:46 1998 [userName] | Printer is requesting a job. | | | | | | | | | | | | | | Specific Message Text | | | Name of user who | | | invoked operation | | | (if applicable) | | | | | Date and Time | Thread ID | | Severity Level
Figure 22-7. Developer-level log message format
I 6 pa_procs.c:601 4726.876018 | PA__globalData.uNewTask = 1 | | | | | | | | | | | | | | | | | | | | Specific Message Text | | | | | | | | | | | | | | | | | Micro Seconds | | | | | | | | | | | | | | Seconds Past Midnight | | | | | | | | | | | Line Number | | | | | | | | Source File | | | | | Thread ID | | Severity Level
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-13 TROUBLESHOOTING
Standard system logging
Non-server PrintXchange components use standard system logging on Windows NT and UNIX. Also, a server can use standard system logging if the user sets the system-log-file-path attribute to syslog. The following subsections describe standard system logging on Windows NT and UNIX. The following section on Server logging events lists logging messages and indicates the mapping between the service log facility severity levels and the NT and UNIX message types and priorities.
Standard system logging on Windows NT
System logging enables the PrintXchange components to write messages into an event log file that users can access. Users can manipulate and view the event log file via standard Windows NT utilities (e.g., Event Viewer Application) or via the Win32 event logging API. Users can use the contents of the event log file for diagnostics and/or debugging. PrintXchange writes the log messages into an “Application” event log file that is one of the standard Windows NT event log files. Therefore, to see the PrintXchange log with the Event Viewer, select Application in the Event Viewer Log menu. The system default Application event-log file path is %SystemRoot%\system32\config\AppEvent.Evt Users can specify a different Application event log file path using the Save As… function of the Event Viewer Log menu. On selecting Detail… from the Event Viewer View menu, the Event Viewer displays the following information: Date: mm/dd/yy Time: hh:mm:ss PM/AM User: N/A Computer: Hostname of machine on which the PrintXchange server is running Event ID: 1 (always) Source: "PrintXchange" Type: Information, Warning, or Error Category: None (always) Description: (Refer to the Server exit status table in this chapter). Data: None The log file data should be set in the registry via the installation process or via the Registry Editor for the machine for which the event log is written. If users plan to write logs into a remote host’s event log file, the remote host’s name should be set in the registry via the installation process or via the Registry Editor for the machine on which the PrintXchange server runs. Registry Key: HKEY_LOCAL_MACHINE\Software\Xerox\PrintXchange\CurrentVer sion\SystemLog Value: SystemLogHost: REG_SZ: Computer-name If the registry key is not set, PrintXchange writes the system log into the local event log file.
22-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
The system log data should be set in the registry, and the message- resource-DLL should be installed at the host that reads the event log file. The message localization of the event log file is not done in the Windows NT way of switching the message resource DLL. Instead, it is done at the time of writing. The events logged include descriptions generated by the services or other system components.
Standard system logging on UNIX
PrintXchange components use the UNIX syslog daemon to log component events. The syslog daemon enables the servers to write messages into a log file that users can access. Users can manipulate and view the log file via standard UNIX facilities. Users can use the contents of the log file as an audit trail. LOG_LPR is the UNIX facility to use when using syslog. The configuration file /etc/syslog.conf contains the error conditions that the server tracks, a priority, and the location or locations where the server logs the errors. The priority level indicates the type of event or condition: Informational messages Non-error conditions that may require special handling Warning messages Errors Critical conditions (such as device error) Conditions needing immediate correction (such as corrupted database) Panic condition Debug messages. Typically, the messages are written to /var/adm/messages or to the system console. Users, however, can specify different destinations for specific events. The events or conditions logged include messages generated by the server, kernel, or other system processes.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-15 TROUBLESHOOTING
Server logging events
The table below lists the server logging events for the service log facility user severity levels: Error Warning Status Audit Debug. The table indicates the mapping that takes place from the facility severity level to the Windows NT message type and UNIX priority when the system-log-file-path attribute is set to syslog.
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
(Refer to the Numbered error messages section (messages with prefix 8022.) Error Error LOG_ERR
(Refer to the Numbered error messages section (messages with prefix 8022.) Warning Warning LOG_WARNING
"[JobID
"Acceptance of new print jobs on printer
"Acceptance of new print jobs on queue
"Acceptance of new print jobs on server
"Addition of a document to job
"Attribute modification of document
"Attribute modification of initial-value-document
"Attribute modification of initial-value-job
"Attribute modification of job
"Attribute modification of printer
"Attribute modification of queue
"Attribute modification of server
"Cancellation of document
"Cancellation of job
"Closing of job
"Configuration attribute
"Configuration attribute
"Creation of initial-value-document
22-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Creation of initial-value-document
"Creation of initial-value-job
"Creation of printer
"Creation of queue
"Deletion of document
"Deletion of initial-value-document
"Deletion of initial-value-job
"Deletion of job
"Deletion of printer
"Deletion of queue
"Deletion of server
"Enumeration of jobs for printer
"Initial-value-document
"Initial-value-document
"Initial-value-job
"Initial-value-job
"Interruption of job
"Job
"Listing of attributes for documents has started." Audit Information LOG_INFO
"Listing of attributes for initial-value-documents has started." Audit Information LOG_INFO
"Listing of attributes for initial-value-jobs has started." Audit Information LOG_INFO
"Listing of attributes for initial-value-jobs has started." Audit Information LOG_INFO
"Listing of attributes for jobs has started." Audit Information LOG_INFO
"Listing of attributes for printers has started." Audit Information LOG_INFO
"Listing of attributes for queues has started." Audit Information LOG_INFO
"Listing of attributes for servers has started." Audit Information LOG_INFO
"Listing of attributes for servers has started." Audit Information LOG_INFO
"Logical printer
"Logical printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-17 TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Modification for document
"Modification for job
"Pausing of printer
"Pausing of queue
"Pausing of server
"Pausing of server
"Pausing printing of job
"Physical printer
"Physical printer
"Print submission on printer
"Printer
"Printer
"Promotion of job
"Queue
"Queue
"Rejection of new print jobs on printer
"Rejection of new print jobs on queue
"Rejection of new print jobs on server
"Removal of all jobs in queue
"Removal of all jobs in server
"Resubmission of job
"Resubmission of queue
"Resuming of printer
"Resuming of queue
"Resuming of server
"Resuming printing of job
Audit Information LOG_INFO
"Shutdown of server
"Spooler
22-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Spooler
"Spooler
"Spooler
"Supervisor
"Supervisor
"Supervisor
"Supervisor
"Acceptance of new print jobs on printer
"Acceptance of new print jobs on queue
"Acceptance of new print jobs on server
"Addition of a document to job
"Attribute modification of document
"Attribute modification of initial-value-document
"Attribute modification of initial-value-job
"Attribute modification of job
"Attribute modification of printer
"Attribute modification of queue
"Attribute modification of server
"Cancellation of document
"Cancellation of job
"Closing of job
"Creation of initial-value-job
"Creation of printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-19 TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Creation of queue
"Deletion of document
"Deletion of initial-value-document
"Deletion of initial-value-job
"Deletion of job
"Deletion of printer
"Deletion of queue
"Deletion of server
"Enumeration of jobs for printer
"Interruption of job
"Job
"Job
"Job
"Listing of attributes for documents has successfully completed." Debug Information LOG_INFO
"Listing of attributes for initial-value-documents has successfully completed." Debug Information LOG_INFO
“Listing of attributes for initial-value-jobs has successfully completed.” Debug Information LOG_INFO
"Listing of attributes for initial-value-jobs has successfully completed." Debug Information LOG_INFO
"Listing of attributes for jobs has successfully completed." Debug Information LOG_INFO
"Listing of attributes for printers has successfully completed." Debug Information LOG_INFO
"Listing of attributes for queues has successfully completed." Debug Information LOG_INFO
"Listing of attributes for servers has successfully completed." Debug Information LOG_INFO
"Modification for document
"Modification for job
"Pausing of printer
"Pausing of queue
"Pausing of server
"Pausing printing of job
"Print submission on printer
"Printer
22-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Printer
"Printer
"Printer
"Printer
"Printer
"Promotion of job
"Queue
"Rejection of new print jobs on printer
"Rejection of new print jobs on queue
"Rejection of new print jobs on server
"Removal of all jobs in queue
"Removal of all jobs in server
"Resubmission of job
"Resubmission of queue
"Resuming of printer
"Resuming of queue
"Resuming of server
"Resuming printing of job
"Server
"Server
"Shutdown of server
"The spool space available is
“
"Spooler
"Spooler
"Spooler
"Spooler
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-21 TROUBLESHOOTING
Table 22-2. Server logging events
Severity UNIX Message NT Type Level Priority
"Supervisor
"Supervisor
"Supervisor
"Supervisor
22-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Notification server logging events
The table below lists the error messages that the notification server may deliver to the standard error or system log. For developers only: The NT type and UNIX priority map to the service log facility severity levels as follows: NT Error and UNIX LOG_ERR map to severity level Error NT Warning and UNIX LOG_WARNING map to severity level Warning NT Information maps to severity level Audit
Table 22-3. Log messages
NT UNIX Problem Recovery Message Type Priority
Refer to the section on Error LOG_ERR Refer to the section on Numbered error messages Numbered error messages (messages with prefix 58.) (messages with prefix 58.)
“ready to serve requests” Information --- Server finished N/A startup successfully.
“service has stopped normally” Information --- Server stopped N/A normally.
(Refer to Chapter 3 messages Warning LOG_WARNING (Refer to Chapter 3 messages with prefix 58.) with prefix 58.)
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-23 TROUBLESHOOTING
Restrictions for e-mail notification on Windows NT
This section lists the necessary conditions for using e-mail notification on Windows NT. These conditions must be satisfied to ensure proper operation of the e-mail notification. In case the conditions were not met and the system is hung, resolve the problem, then restart the PrintXchange notification server.
SMTP (Internet Mail) notification
When configuring the Internet Mail property in MAPI profile, the operator must specify:
Valid personal information in “Full name” and “E-mail address” section under the “General” tab.
Valid server name in the “Internet Mail Server” section under the “General” tab.
Valid mail server account name in the “Account name” section under the “General” tab.
Valid password for logging on the mail server as the account above in the “Password” section under the “General” tab. The operator must NOT check “Work off-line and use Remote Mail” under the “Connection” tab. If hostname was specified in “Internet Mail Server” (not IP address), the hostname must be resolved into IP address by some means of IP address resolution available on the Windows NT environment, such as DNS or hosts file. The mail server must be up and SMTP server (sendmail on UNIX) and POP server must be running on the mail server at any time while PrintXchange is operating. The mail server must be network-reachable from the machine where PrintXchange is operating at any time while PrintXchange is operating. The user must NOT change the password of the mail server account at any time while PrintXchange is operating. To change the password, follow these steps:
Stop PrintXchange notification server.
Re-configure the password in MAPI profile.
Re-start PrintXchange notification server. Leave any other MAPI profile sections as initial value (default).
22-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
MS-Mail notification
When configuring the Microsoft mail property in MAPI profile, the operator must specify:
Valid postoffice path under the “connection” tab.
Valid mailbox name and password under the “Logon” tab. The operator must check the “When logging on, automatically enter password” box under the “Logon” tab. The operator must check the “Enable outgoing mail delivery” box under the “Delivery” tab. The operator must NOT check any box under the “LAN configuration” tab. If the postoffice is located on the network drive, it must be accessible from the machine where PrintXchange is operating. Access permission for the postoffice must be granted for “PXCAdmin”. The operator must NOT change the mailbox password at any time while PrintXchange is operating. Leave any other MAPI profile sections as initial value (default).
MS Exchange notification
When configuring the Microsoft Exchange Server mail property in MAPI profile, the operator must specify:
Valid MS Exchange server name in the “MS Exchange server” section under the MAPI profile “General” tab.
Valid MS Exchange mailbox name available on the server in “Mailbox” section under the MAPI profile “General” tab. MS Exchange must be up and network reachable from the machine where PrintXchange is operating at any time while PrintXchange is operating. Leave any other MAPI profile sections as initial value (default).
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-25 TROUBLESHOOTING
Message descriptions
This section provides information on: Numbered error messages Reference supervisor errors Exit status.
Numbered error messages
The message descriptions are given in sequence by error number. The error numbers have the following format: prefix-sequenceNumber The following table lists the error number prefixes. Each prefix indicates the PrintXchange component that generates the error. The sequence number identifies an error within each prefix group.
Table 22-4. Error code prefixes
Prefix Component
1 Server (document objects)
4 Server (initial-value-document objects)
5 Server (initial-value-job objects)
6 Server (job objects)
7 Server (infrastructure)
12 Server (logical printer and physical printer objects)
13 Server (queue objects)
14 Server (infrastructure)
16 Server (spooler and supervisor objects)
18 Server (infrastructure)
20 Server (infrastructure)
30 Server (infrastructure)
49 LPR inbound gateway for NT
52 LAN Manager inbound gateway for NT
56 QServer inbound gateway for NT
58 Notification server
59 Accounting
22-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-4. Error code prefixes
Prefix Component
60 Object database utilities
61 OID database utilities
62 Job diagnostics
63 CLI client
65 CLI Name Service
80 GUI Client
81 GUI Name Service
8019 API client
8022 Logging
Note: If the event viewer indicates that NT spooler could not start due to dependency on PrintXchange Name Service, contact technical support. CAUTION: When pdprintinfo is executed on a remote UNIX machine with the display option, avoid inducing a crash by setting the DISPLAY variable to the local machine.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-27 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 1-101 "Unable to create a This error may be caused The request Check the available memory document in the by a memory corruption in is not and retry the operation. If the database." the server, a lack of processed. problem persists, contact available disk space or a technical support. lack of available virtual memory. 1-102 "Unable to delete a This error may be caused The request Retry the operation. If the document from the by a memory corruption in is not problem persists, contact database." the server or a corruption in processed. technical support. the object database. 1-103 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact document." the server, a corruption in processed. technical support. the object database or a lack of virtual memory. 1-104 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the by a memory corruption in is not problem persists, contact document." the server, or a corruption processed. technical support. in the object database. 1-105 "Unable to set This error may be caused The request Retry the operation. If the attributes on the by a memory corruption in is not problem persists, contact document." the server, a lack of processed. technical support. available disk space or a lack of available virtual memory. 1-106 "Unable to unlock the This error may be caused The request Retry the operation. If the document." by a memory corruption in is not problem persists, contact the server, or a corruption processed. technical support. in the object database. 1-107 "Unable to obtain a This error may be caused The request Retry the operation. If the write lock for the by a memory corruption in is not problem persists, contact document." the server, or a corruption processed. technical support. in the object database. 1-108 "An error occurred This error may be caused The request Retry the operation. If the while retrieving the by a memory corruption in is not problem persists, contact document state." the server or a lack of processed. technical support. available virtual memory 1-109 "The file transfer The requested deletion may The request Check the spelling of the file agent failed to delete have contained an incorrect is not name and the file path before the document data." file name or file path. processed. retrying the operation. If the problem persists, contact technical support.
22-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 1-110 "The file transfer This error may be caused The request Retry the operation. If the agent failed to by using file reference is not problem persists, contact transfer the document transfer method on a file processed. technical support. data." that is not accessible to the server. In addition, this error also may be caused by a memory corruption in the server or a lack of available virtual memory. 1-111 "The document This error may be caused The request Retry the operation. If the descriptor passed to by a memory corruption in is not problem persists, contact the server is invalid." the server. processed. technical support. 1-112 “The document state This error may be caused The request Retry the operation. If the is invalid.” by a memory corruption in is not problem persists, contact the server. processed. technical support. 1-113 "The function call This error may be caused The request Retry the operation. If the failed due to an by a memory corruption in is not problem persists, contact invalid parameter." the server. processed. technical support. 1-114 "The function call This error may be caused The request Retry the operation. If the failed due to an by a memory corruption in is not problem persists, contact invalid fourth the server. processed. technical support. parameter." 1-115 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact specified initial value the server, a corruption in processed. technical support. document." the object database or a lack of virtual memory. 1-116 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the initial by a memory corruption in is not problem persists, contact value document." the server, or a corruption processed. technical support. in the object database. 1-117 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the job." by a memory corruption in is not problem persists, contact the server, a corruption in processed. technical support. the object database or a lack of virtual memory. 1-118 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the job." by a memory corruption in is not problem persists, contact the server, or a corruption processed. technical support. in the object database. 1-119 "Unable to set This error may be caused The request Retry the operation. If the attributes on the job." by a memory corruption in is not problem persists, contact the server, a lack of processed. technical support. available disk space or a lack of available virtual memory. 1-120 "Unable to unlock the This error may be caused The request Retry the operation. If the job." by a memory corruption in is not problem persists, contact the server, or a corruption processed. technical support. in the object database.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-29 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 1-121 "Unable to obtain a This error may be caused The request Retry the operation. If the write lock for the job." by a memory corruption in is not problem persists, contact the server, or a corruption processed. technical support. in the object database. 1-122 "Unable to modify/set This error may be caused The request Retry the operation. If the document attributes." by a memory corruption in is not problem persists, contact the server, a corruption in processed. technical support. the object database or a lack of virtual memory. 1-123 "The modify operation This error may be caused The request Retry the operation. If the failed in the by a memory corruption in is not problem persists, contact supervisor." the server or a lack of processed. technical support. available virtual memory. 1-124 "The document This error may be caused The request Retry the operation. If the attribute set is by a memory corruption in is not problem persists, contact missing the required the server. processed. technical support. attribute document- sequence-number." 1-125 "The document is This error may be caused The request Retry the operation. If the missing the required by a memory corruption in is not problem persists, contact attribute document- the server. processed. technical support. content."
1-126 "The document This error may be caused The request Retry the operation. If the parameter attribute by a memory corruption in is not problem persists, contact set is missing the the server. processed. technical support. required attribute job- identifier." 1-127 "The document This error may be caused The request Retry the operation. If the attribute set is by a memory corruption in is not problem persists, contact missing the required the server. processed. technical support. attribute transfer- method." 1-128 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact printer." the server, or a corruption processed. technical support. in the object database. 1-129 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact attribute set facility." the server. processed. technical support. 1-130 "An unknown error This error may be caused The request Retry the operation. If the has occurred in the by a memory corruption in is not problem persists, contact document object the server. processed. technical support. library." 1-131 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact generic utilities the server. processed. technical support. facility."
22-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 1-132 "The document is in This error may be caused The request Retry the operation. If the an unknown state." by a memory corruption in is not problem persists, contact the server. processed. technical support. 1-133 "A system error has This error may be caused The request Retry the operation. If the occurred." by a memory corruption in is not problem persists, contact the server. processed. technical support. 1-134 "The document failed This error may be caused The request Retry the operation. If the to delete some by a memory corruption in is not problem persists, contact attributes before the server. processed. technical support. sending an event." 1-135 "An error has This error may be caused The request Retry the operation. If the occurred in the event by a memory corruption in is not problem persists, contact handler." the server. processed. technical support. 1-136 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact internal job facility." the server. processed. technical support. 1-137 "An error has This error may be caused The request Retry the operation. If the occurred in the event by a memory corruption in is not problem persists, contact notification agent." the server. processed. technical support. 1-138 "There was not The disk space required for The request Check the available disk enough disk space to this operation is insufficient. is not space and retry the operation. spool the document processed. If the problem persists, data." contact technical support. 1-139 "The server could not There is no available space The request Wait for some existing jobs to spool the document to spool the document. is not complete and retry the data because the processed. operation. If the problem spool threshold has persists, contact technical been reached." support. 4-101 "The initial value The initial value document The request Resubmit the document using document identifier is name may already exist. is not another name. If the problem invalid." processed. persists, contact technical support. 4-102 "An error has This error may be caused The request Check the availability of the occurred during by a memory corruption in is not virtual memory and retry the initialization of the the server or a lack of processed. operation. If the problem initial value available virtual memory. persists, contact technical document." support. 4-103 "An internal error has This error may be caused The request Check the availability of the occurred in the initial by a memory corruption in is not virtual memory and retry the value document." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 4-104 "A system error has This error may be caused The request Check the availability of the occurred." by a memory corruption in is not virtual memory and the the server, a lack of processed. available disk space in the available virtual memory or database (or spool partitions) a lack of disk space. before retrying the operation. If the problem persists, contact technical support.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-31 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 4-105 "An error has This error may be caused The request Check the availability of the occurred in the object by a memory corruption in is not virtual memory and the database facility." the server or a corruption in processed. available disk space in the the object database. It may database (or spool partitions) also be caused by a lack of before retrying the operation. available virtual memory or If the problem persists, a lack of disk space. contact technical support. 4-106 "An error has This error may be caused The request Check the availability of the occurred in the by a memory corruption in is not virtual memory and retry the attribute set facility." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 4-107 "An error has This error may be caused The request Check the availability of the occurred in the by a memory corruption in is not virtual memory and retry the attribute set facility; the server or a lack of processed. operation. If the problem however, the available virtual memory. persists, contact technical operation completed support. successfully!" 4-108 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact Common Server the server. processed. technical support. Utilities facility."
4-109 "There is insufficient This error may be caused The request Check the availability of the memory on the server by a lack of available virtual is not virtual memory and retry the to perform the memory. processed. operation. If the problem requested operation." persists, contact technical support. 4-110 "The requested initial The requested initial value The request Check the spelling of the value document was document does not exist on is not initial value document and not found." the server or may exist processed. retry the operation. If the under a different name. problem persists, contact technical support. 4-111 "The requested initial A document with the same The request Choose another name for the value document name has been found on is not initial value document and already exists." the server. processed. retry the operation. If the problem persists, contact technical support. 4-112 "The requested The initial value document The request Check the spelling of the initial reference initial value does not exist. is not value document and retry the document was not processed. operation. If the problem found." persists, contact technical support. 4-113 "The initial value This error may be caused The request Retry the operation. If the document was not by a memory corruption in is not problem persists, contact locked." the server or a corruption in processed. technical support. the object database.
22-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 4-114 "The requested initial This error may be caused The request Retry the operation. If the value document is by a memory corruption in is not problem persists, contact already locked." the server or a corruption in processed. technical support. the object database.
4-115 "Unable to obtain a This error may be caused The request Retry the operation. If the lock for the initial by a memory corruption in is not problem persists, contact value document." the server or a corruption in processed. technical support. the object database. 4-116 "An invalid attribute This error may be caused The request Retry the operation. If the set was passed to the by a memory corruption in is not problem persists, contact object database the server. processed. technical support. facility." 4-117 "A transaction error This error may be caused The request Retry the operation. If the has occurred in the by a memory corruption in is not problem persists, contact object database." the server or a corruption in processed. technical support. the object database. 5-101 "The initial value job The initial value job name The request Retry the operation. If the identifier is invalid." may already exist. is not problem persists, contact processed. technical support. 5-102 "An error has This error may be caused The request Retry the operation. If the occurred during by a memory corruption in is not problem persists, contact initialization of the the server or a lack of processed. technical support. initial value job." available virtual memory.
5-103 "An internal error has This error may be caused The request Retry the operation. If the occurred in the initial by a memory corruption in is not problem persists, contact value job." the server or a lack of processed. technical support. available virtual memory. 5-104 "A system error has This error may be caused The request Check the memory on the occurred." by a memory corruption in is not server and retry the operation. the server. processed. If the problem persists, contact technical support. 5-105 "An error has This error may be caused The request Check the possible causes occurred in the object by a memory corruption in is not above and retry the operation. database facility." the object database, a lack processed. If the problem persists, of available disk space or a contact technical support. lack of available virtual memory. 5-106 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact attribute set facility." the server or a lack of processed. technical support. available virtual memory. 5-107 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact attribute set facility; the server or a lack of processed. technical support. however, the available virtual memory. requested operation completed successfully!"
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-33 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 5-108 "An error has This error may be caused The request Check the memory on the occurred in the by a memory corruption in is not server and retry the operation. Common Server the server. processed. If the problem persists, Utilities facility." contact technical support. 5-109 "There is insufficient This error may be caused The request Check the available virtual memory on the server by a lack of available virtual is not memory on the server and to perform the memory. processed. retry the operation. If the requested operation." problem persists, contact technical support. 5-110 "The requested initial The initial value job name The request Check the spelling of the value job was not may have been entered is not initial value job and retry the found." incorrectly or may not exist. processed. operation. If the problem persists, contact technical support. 5-111 "The requested initial An initial value job with the The request Choose another name for the value job already same name has been found is not initial value job and retry the exists." on the server. processed. operation. If the problem persists, contact technical support. 5-112 "The requested The initial value job The request Check the spelling of the reference initial value reference does not exist on is not initial value job and retry the job was not found." the server. processed. operation. If the problem persists, contact technical support. 5-113 "The initial value job This error may be caused The request Retry the operation. If the was not locked." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 5-114 "The requested initial This error may be caused The request Retry the operation. If the value job is already by a memory corruption in is not problem persists, contact locked." the server or a corruption in processed. technical support. the object database. 5-115 "Unable to obtain a This error may be caused The request Retry the operation. If the lock for the initial by a memory corruption in is not problem persists, contact value job." the server or a corruption in processed. technical support. the object database. 5-116 "An invalid attribute This error may be caused The request Check the object database set was passed to the by a memory corruption in is not and retry the operation. If the object database the server. processed. problem persists, contact facility." technical support. 5-117 "A transaction error This error may be caused The request Check the object database has occurred in the by a memory corruption in is not and retry the operation. If the object database." the server or a corruption in processed. problem persists, contact the object database. technical support. v6-101 "The job-owner This error may be caused The request Retry the operation. If the attribute in the by a memory corruption on is not problem persists, contact common arguments the server. processed. technical support. must contain a host name."
22-34 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-102 "The document is This error may be caused The request Retry the operation. If the missing the required by a memory corruption on is not problem persists, contact attribute copy-count." the server. processed. technical support.
6-103 "The document This error may be caused The request Retry the operation. If the descriptor is missing by a memory corruption on is not problem persists, contact the required attribute the server. processed. technical support. document-sequence- number." 6-104 "The job attribute set This error may be caused The request Retry the operation. If the is missing the by a memory corruption on is not problem persists, contact required attribute job- the server. processed. technical support. identifier." 6-105 "The job-owner This error may be caused The request Retry the operation. If the attribute must be by a memory corruption on is not problem persists, contact specified or contained the server. processed. technical support. in the common arguments." 6-106 "The job is missing This error may be caused The request Retry the operation. If the the required attribute by a memory corruption on is not problem persists, contact job-owner." the server. processed. technical support. 6-107 "The job is missing This error may be caused The request Retry the operation. If the the required attribute by a memory corruption on is not problem persists, contact job-state." the server. processed. technical support.
6-108 "The document is This error may be caused The request Retry the operation. If the missing the required by a memory corruption on is not problem persists, contact attribute octet-count." the server. processed. technical support.
6-109 "A printer name must This error may be caused The request Retry the operation. If the be specified." by a memory corruption on is not problem persists, contact the server. processed. technical support. 6-110 "The job is missing This error may be caused The request Retry the operation. If the the required attribute by a memory corruption on is not problem persists, contact printer-name." the server. processed. technical support.
6-111 "The job is missing This error may be caused The request Retry the operation. If the the required attribute by a memory corruption on is not problem persists, contact printers-assigned." the server. processed. technical support. 6-112 "A required attribute This error may be caused The request Retry the operation. If the was not found in the by a memory corruption on is not problem persists, contact attribute set." the server. processed. technical support. 6-113 "Job modification The necessary modification The request Retry the operation. If the error: No attributes were not entered. is not problem persists, contact modification attributes processed. technical support. were provided."
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-35 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-114 "Unable to perform The job has been closed The request Retry the operation. If the the requested and is not responding to the is not problem persists, contact operation; the job is request. processed. technical support. already closed." 6-115 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact document." the server, a corruption in processed. technical support. the object database or a lack of available virtual memory. 6-116 "The document state The document state The request Retry the operation. If the transition has failed." transition did not complete is not problem persists, contact successfully. processed. technical support. 6-117 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the by a memory corruption in is not problem persists, contact document." the server or a corruption in processed. technical support. the object database. 6-118 "Unable to unlock the This error may be caused The request Retry the operation. If the document." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 6-119 "Unable to obtain a This error may be caused The request Retry the operation. If the write lock for the by a memory corruption in is not problem persists, contact document." the server or a corruption in processed. technical support. the object database. 6-120 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the initial by a memory corruption in is not problem persists, contact value job." the server, a corruption in processed. technical support. the object database or a lack of available virtual memory. 6-121 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the initial by a memory corruption in is not problem persists, contact value job." the server or a corruption in processed. technical support. the object database. 6-122 "An error has This error may be caused The request Retry the operation. If the occurred while by a memory corruption in is not problem persists, contact attempting to cancel the server. processed. technical support. the job." 6-123 "Unable to create a This error may be caused The request Retry the operation. If the job in the database." by a memory corruption in is not problem persists, contact the server, a corruption in processed. technical support. the object database or a lack of available disk space. 6-124 "Unable to delete the This error may be caused The request Retry the operation. If the job from the by a memory corruption in is not problem persists, contact database." the server or a corruption in processed. technical support. the object database.
22-36 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-125 "Unable to generate a This error may be caused The request Retry the operation. If the new job identifier." by a memory corruption in is not problem persists, contact the server. processed. technical support. 6-126 "Unable to generate a This error may be caused The request Retry the operation. If the new document by a memory corruption in is not problem persists, contact number." the server. processed. technical support. 6-127 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the job." by a memory corruption in is not problem persists, contact the server, a corruption in processed. technical support. the object database or a lack of available virtual memory. 6-128 "Unable to set the This error may be caused The request Check the available virtual attributes on the job." by a memory corruption in is not memory and the available the server, a corruption in processed. disk space in the database (or the object database, a lack spool partitions) before of available disk space or a retrying the operation. If the lack of available virtual problem persists, contact memory. technical support. 6-129 "Unable to unlock the This error may be caused The request Retry the operation. If the job." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 6-130 "Unable to obtain a This error may be caused The request Retry the operation. If the write lock for the job." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 6-131 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact printer." the server, a corruption in processed. technical support. the object database or a lack of available virtual memory. 6-132 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the by a memory corruption in is not problem persists, contact printer." the server or a corruption in processed. technical support. the object database. 6-133 "The queue manager This error may be caused The request Check available virtual failed to add the job by a memory corruption in is not memory and retry the to the requested the server or a lack of processed. operation. If the problem queue." available virtual memory. persists, contact technical support. 6-134 "The queue manager This error may be caused The request Retry the operation. If the failed to delete the job by a memory corruption in is not problem persists, contact from the requested the server. processed. technical support. queue." 6-135 "Unable to report job This error may be caused The request Retry the operation. If the modification to the by a memory corruption in is not problem persists, contact queue manager." the server. processed. technical support.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-37 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-136 "Unable to report job This error may be caused The request Retry the operation. If the state change to the by a memory corruption in is not problem persists, contact queue manager." the server. processed. technical support. 6-137 "The queue was This error may be caused The request Retry the operation. If the unable to promote the by a memory corruption in is not problem persists, contact requested job." the server. processed. technical support. 6-138 "Unable to obtain This error may be caused The request Retry the operation. If the attributes for the by a memory corruption in is not problem persists, contact server." the server, a corruption in processed. technical support. the object database or a lack of available virtual memory. 6-139 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock for the by a memory corruption in is not problem persists, contact server." the server or a corruption in processed. technical support. the object database. 6-140 "An error has This error may be caused The request Check the available virtual occurred in the by a memory corruption in is not memory and retry the internal job facility" the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 6-141 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact attribute set facility." the server processed. technical support. 6-142 "An error has This error may be caused The request Check the available virtual occurred in the object by a memory corruption in is not memory and the available database facility." the server, a corruption in processed. disk space in the database (or the object database, a lack spool partitions) before of available disk space or a retrying the operation. If the lack of available virtual problem persists, contact memory. technical support. 6-143 "An error has This error may be caused The request Retry the operation. If the occurred in the timer by a memory corruption in is not problem persists, contact agent." the server. processed. technical support. 6-144 "An error has This error may be caused The request Check the available virtual occurred in the by a memory corruption in is not memory and retry the generic utilities the server or a lack of processed. operation. If the problem facility." available virtual memory. persists, contact technical support. 6-145 "An error has This error may be caused The request Check the available virtual occurred in the by a memory corruption in is not memory and retry the generic utilities the server or a lack of processed. operation. If the problem facility; copy failed." available virtual memory. persists, contact technical support. 6-146 "An error has This error may be caused The request Check the available virtual occurred in the event by a memory corruption in is not memory and retry the notification agent." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support.
22-38 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-147 "An error has This error may be caused The request Check the available virtual occurred in the timer by a memory corruption in is not memory and retry the agent." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 6-148 "A transaction error This error may be caused The request Retry the operation. If the has occurred in the by a memory corruption in is not problem persists, contact object database." the server or a corruption in processed. technical support. the object database.
6-149 "The job object This error may be caused The request Retry the operation. If the manager was unable by a memory corruption in is not problem persists, contact to obtain a queue the server or a corruption in processed. technical support. name from the the object database. printer." 6-150 "An invalid state This error may be caused The request Retry the operation. If the transition was by a memory corruption in is not problem persists, contact requested." the server. processed. technical support. 6-151 "An unknown error This error may be caused The request Retry the operation. If the occurred while by a memory corruption in is not problem persists, contact performing the the server. processed. technical support. requested state transition." 6-152 "The job is not in a The specified operation The request Consult the System valid state to perform cannot be applied to the job is not Administration and Operation the requested in its current state. processed. Guide for the valid object operation." states. The operation may succeed later when the object transitions to a valid state. 6-153 "The queue is not in a The specified operation The request Consult the System valid state to perform cannot be applied to the is not Administration and Operation the requested queue in its current state. processed. Guide for the valid object operation." states. 6-154 "The queue assigned This error may be caused The request Verify that the queue does not to the requested job by a memory corruption in is not already exist and recreate the cannot be found in the server. It may also processed. queue. If the problem the database." occur after job recovery. persists, contact technical support. 6-155 "The job cannot be This error may be caused The request Retry the operation. If the found in the queue to by a memory corruption in is not problem persists, contact which it was the server. processed. technical support. assigned." 6-156 "Unable to process This error may be caused The request Check the available virtual internal state by a memory corruption in is not memory and retry the transitions." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-39 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-157 "An error has This error may be caused The request Check the available virtual occurred while by a memory corruption in is not memory and retry the processing the the server or a lack of processed. operation. If the problem modification available virtual memory. persists, contact technical attributes." support. 6-158 "The event sent to the The job will not process an The request Retry the operation. If the job came from an event from an invalid is not problem persists, contact invalid printer." printer. processed. technical support. 6-159 "The required job This error may be caused The request Retry the operation. If the attributes job- by attributes missing from is not problem persists, contact identifier and the job. processed. technical support. physical-printer-name were not passed to the supervisor." 6-160 "The job submitter This error may be caused The request Check the available virtual failed to add the job by a memory corruption in is not memory and retry the to the list." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support.
6-161 "An error has This error may be caused The request Check the available virtual occurred in the event by a memory corruption in is not memory and retry the handler." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 6-162 "The job failed to This error may be caused The request Retry the operation. If the delete some of its by a memory corruption in is not problem persists, contact attributes before the server. processed. technical support. sending an event." 6-163 "Unable to delete the This error may be caused The request Retry the operation. If the job from the by a memory corruption in is not problem persists, contact database." the server or a corruption in processed. technical support. the object database. 6-164 "Document Processor This error may be caused The request Retry the operation. If the callback failed to by an internal server error is not problem persists, contact perform or a corruption in the object processed. technical support. AddDocument database. notification." 6-165 "Document Processor This error may be caused The request Retry the operation. If the callback failed to by an internal server error is not problem persists, contact perform CloseJob or a corruption in the object processed. technical support. notification." database. 6-166 "Document Processor This error may be caused The request Retry the operation. If the callback failed to by an internal server error is not problem persists, contact reset the job request or a corruption in the object processed. technical support. list." database.
22-40 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-167 "Document Processor This error may be caused The request Retry the operation. If the failed due to an by a corruption in the job is not problem persists, contact invalid job identifier or object. processed. technical support. invalid job." 6-168 "Document Processor This error may be caused The request Retry the operation. If the failed due to an by a corruption in the is not problem persists, contact invalid document." document object. processed. technical support.
6-169 "Document Processor This error may be caused The request Retry the operation. If the was not in the correct by an internal server error is not problem persists, contact state for this or a corruption in the object processed. technical support. operation." database. 6-170 "Document Processor This error may be caused The request Check the available virtual failed due to an by a memory corruption in is not memory and retry the internal job error." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 6-171 "Document Processor This error may be caused The request Check the available virtual failed due to an by a memory corruption in is not memory and retry the internal document the server or a lack of processed. operation. If the problem error." available virtual memory. persists, contact technical support. 6-172 "Document Processor This error may be caused The request Retry the operation. If the failed because the by a memory corruption in is not problem persists, contact time limit for the server or a lack of processed. technical support. performing the available virtual memory. request was exceeded." 6-173 "Document Processor An attempt was made to The request None failed because it does modify job or document is not not support this attributes on the supervisor. processed. request." This feature is not supported. 6-174 "There is insufficient This error may be caused The request Retry the operation. If the memory on the server by a memory corruption in is not problem persists, contact to perform the the server or a lack of processed. technical support. requested operation." available virtual memory. 6-175 "Document Processor This error may be caused The request Retry the operation. If the failed due to a system by a memory corruption in is not problem persists, contact error." the server. processed. technical support. 6-176 "Document Processor This error may be caused The request Check the available virtual failed due to an by a memory corruption in is not memory and retry the unknown error." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-41 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 6-177 "Document Processor This error may be caused The request Enter a valid document failed due to an by a memory corruption in is not number and retry the invalid document the server or a lack of processed. operation. If the problem number." available virtual memory. persists, contact technical support. 6-178 "Document Processor Modification on a restricted The request Retry the operation. If the failed due to an attribute is not allowed. is not problem persists, contact invalid modification processed. technical support. attribute." 6-179 "Document Processor Modification on a restricted The request Retry the operation. If the failed due to an attribute is not allowed. is not problem persists, contact unsupported processed. technical support. modification attribute." 6-180 "There is insufficient This error may be caused The request Check the available virtual memory on the server by a memory corruption in is not memory and retry the to perform the the server or a lack of processed. operation. If the problem requested operation." available virtual memory. persists, contact technical support. 6-183 "An unknown error This error may be caused The request Retry the operation. If the occurred during by a memory corruption in is not problem persists, contact processing of the the server. processed. technical support. user request." 7-103 "
22-42 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 7-110 "
7-111 "
7-113 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-43 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 7-117 "
22-44 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 7-128 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-45 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 7-146 "
7-174 "
22-46 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 7-179 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-47 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 12-101 "The printer is already An attempt was made to The request None disabled." disable an already disabled is not printer. processed. 12-102 "The printer is already An attempt was made to The request None enabled." enable an already enabled is not printer. processed. 12-103 "An error has This error may be caused The request Retry the operation. If the occurred in an by a memory corruption in is not problem persists, contact attribute set facility." the server or a lack of processed. technical support. available virtual memory. 12-104 "Unable to register The user has attempted to The request Retry the operation using a printer object with the create a physical printer is not different name. If the name service." using an existing logical processed. problem persists, contact printer name. technical support. 12-105 "The printer must be The printer has not been The request Disable the printer and retry disabled before disabled. is not the operation. If the problem deletion." processed. persists, contact technical support. 12-106 "An error has This error may be caused The request Retry the operation. If the occurred in the printer by a memory corruption in is not problem persists, contact action facility." the server or a lack of processed. technical support. available virtual memory. 12-107 "A data processing This error may be caused The request Retry the operation. If the operation has failed." by a memory corruption in is not problem persists, contact the server or a lack of processed. technical support. available virtual memory. 12-108 "The requested Forced creation is not The request The existing printer should be printer already exists; supported. is not deleted and then recreated. forced creation is not processed. available." 12-109 "There is insufficient This error may be caused The request Retry the operation. If the memory on the server by a memory corruption in is not problem persists, contact to perform the the server, a corruption in processed. technical support. requested operation." the object database, a lack of available disk space or a lack of available virtual memory. 12-110 "An event was An event has been ignored. The request None ignored." is not processed. 12-111 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact internal printer the server, a lack of processed. technical support. facility." available disk space or a lack of available virtual memory. 12-112 "The client passed an The argument that was The request Retry the operation. If the invalid argument." passed by the client is is not problem persists, contact invalid. processed. technical support.
22-48 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 12-113 "The state transition The state transition is The request Retry the operation. If the requested is invalid." invalid. is not problem persists, contact processed. technical support. 12-114 "Unable to obtain a This error may be caused The request Retry the operation. If the lock for the printer." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 12-115 "Unable to obtain a This error may be caused The request Retry the operation. If the lock for the queue." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 12-116 "Unable to obtain a This error may be caused The request Retry the operation. If the lock for the server." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 12-117 "The printer must be The printer has not been The request Disable the printer. disabled before disabled. is not moving to a new processed. queue." 12-118 "The access control This error may be caused The request Retry the operation. If the list is missing in the by a memory corruption in is not problem persists, contact argument or on the the server. processed. technical support. server." 12-119 "The printer is The user attempted to The request Specify the printer-model missing the required create a physical printer is not attribute. attribute printer- without specifying the processed. model." printer-model attribute. 12-120 "The printer has no The user attempted to The request Add an associated-queue associated-queue." enable a physical printer is not attribute using a pdset that does not have an processed. command. associated-queue attribute. 12-121 "The printer was not The requested printer does The request None found." not exist. is not processed. 12-122 "An error has This error may be caused The request Retry the operation. If the occurred in the name by a problem with the is not problem persists, contact space facility." protoserver. processed. technical support. 12-123 "The requested There is no need to create The request None printer already this printer. is not exists." processed. 12-124 "A required object This error may be caused The request Retry the operation. If the could not be found in by a memory corruption in is not problem persists, contact the object database the server or a corruption in processed. technical support. facility." the object database. 12-125 "An error has This error may be caused The request Retry the operation. If the occurred in the object by a memory corruption in is not problem persists, contact database facility." the server or a corruption in processed. technical support. the object database.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-49 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 12-126 "The maximum No more printers may be The request Check the values of the number of printers added. is not number-of-printers-supported supported has been processed. and maximum-number-of- reached. printers-supported attributes. 12-127 "The event handler This error may be caused The request Retry the operation. If the failed to send an by a memory corruption in is not problem persists, contact event." the server. processed. technical support. 12-128 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact attribute set facility." the server, a lack of processed. technical support. available disk space or a lack of available virtual memory. 12-129 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact internal server the server, a lack of processed. technical support. facility." available disk space or a lack of available virtual memory. 12-130 "The internal state The state is invalid. The request Retry the operation. If the given is out of is not problem persists, contact bounds." processed. technical support. 12-131 "This operation is A printer cannot perform The request Check the command syntax unsupported for this operation. is not to ensure that the operation printers." processed. and object names are valid. 12-132 "Unable to update the This error may be caused The request Retry the operation. If the logical printer." by a memory corruption in is not problem persists, contact the server, a lack of processed. technical support. available disk space or a lack of available virtual memory. 12-133 "The updating This error may be caused The request Retry the operation. If the process for the new by a memory corruption in is not problem persists, contact physical printers has the server, a lack of processed. technical support. failed." available disk space or a lack of available virtual memory. 12-134 "The updating This error may be caused The request Retry the operation. If the process for the new by a memory corruption in is not problem persists, contact associated queue has the server, a lack of processed. technical support. failed." available disk space or a lack of available virtual memory. 12-135 "The updating This error may be caused The request Retry the operation. If the process for the old by a memory corruption in is not problem persists, contact physical printers has the server, a lack of processed. technical support. failed." available disk space or a lack of available virtual memory.
22-50 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 12-136 "The updating This error may be caused The request Retry the operation. If the process for the old by a memory corruption in is not problem persists, contact associated queue has the server, a lack of processed. technical support. failed." available disk space or a lack of available virtual memory. 12-137 "The updating This error may be caused The request Retry the operation. If the process for the other by a memory corruption in is not problem persists, contact objects has failed." the server, a lack of processed. technical support. available disk space or a lack of available virtual memory. 12-138 "The value of default- The former attribute value The request Lower the value of the user-job-priority cannot be greater than the is not default-user-job-priority cannot be greater latter. processed. attribute and retry the than the value of operation. If the problem max-user-job- persists, contact technical priority." support. 12-139 "Supervisor cannot An attempt was made to The request Modify the associated-queue connect to more than enable a physical printer is not attribute of the physical one spooler." that has an associated processed. printer. queue that is on a different spooler than the other physical printers on the supervisor. The supervisor can only connect to one spooler. 12-140 "The printer has no The user attempted to The request Add a printer-address printer-address." enable a physical printer is not attribute using a pdset that does not have a processed. command. printer-address attribute. 13-101 "The requested The queue does not exist. The request Set up the queue and retry the reference queue was is not operation. If the problem not found." processed. persists, contact technical support. 13-102 "The requested There is already a queue by The request Choose another name and queue already exists." that name on the server. is not retry the operation. If the processed. problem persists, contact technical support. 13-103 "An internal error This error may be caused The request Check the availability of the occurred during by a memory corruption in is not virtual memory and the operation." the server, lack of available processed. available disk space in the virtual memory or lack of database (or spool partitions) available disk space. before retrying the operation. If the problem persists, contact technical support. 13-104 "The queue was not The queue does not exist The request Create a queue and retry the found in the system." on the server. is not operation. If the problem processed. persists, contact technical support.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-51 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 13-105 "The queue must be The system will not allow The request Disable the queue and retry disabled before enabled queues to be is not the operation. If the problem deletion." deleted. processed. persists, contact technical support. 13-106 "The queue is already There is no need to disable The request None disabled." the queue. It may either be is not enabled or deleted. processed. 13-107 "The queue is already The queue has been The request None enabled." enabled previously. is not processed. 13-108 "The queue is already The queue has been The request None paused." paused previously. is not processed. 13-109 "The queue is already The queue has been The request None resumed." resumed previously. is not processed. 13-110 "All jobs have not The remaining jobs need to The request Delete the remaining jobs and been deleted from the be deleted before is not retry the operation. If the queue." proceeding. processed. problem persists, contact technical support. 13-111 “The queue is The queue is unavailable at The request Wait for the queue to be currently being this time due to the cleaning is not cleaned and proceed. cleaned.” process. processed. 13-112 "The queue is The queue is unavailable at The request Wait for the jobs to be currently resubmitting this time due to the is not resubmitted and proceed. jobs." resubmission process. processed. 13-113 "The queue is in an The queue is disabled or The request Enable the queue and invalid state to otherwise unavailable to is not proceed. perform the perform the operation. processed. requested operation." 13-114 "Unable to register This error may be caused The request Retry the operation. If the queue object with by a problem with the is not problem persists, contact name service." protoserver. processed. technical support. 13-115 "The requested The creation operation is The request None queue already exists; not necessary. is not forced creation is not processed. available." 13-116 "The queue must be The queue cannot be The request Disable the queue and disabled before cleaned while in the is not proceed. performing the clean enabled or auto-disabled processed. operation." state. 13-117 "The queue must be The queue cannot perform The request Disable the queue and disabled before the resubmit operation is not proceed. performing the while in the enabled or processed. resubmit operation." auto-disabled state. 13-118 "WARNING: Some The job resubmission The request Resubmit the jobs. jobs did not resubmit process is incomplete. is not successfully. processed. Resubmit the jobs individually to determine cause."
22-52 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 13-119 "A queue by that The server does not allow The request Rename the queue and name already exists. duplicate queue names. is not proceed. Please use another processed. name." 13-121 "The value of queue- The system requires that The request Modify the value of the lower backlog-lower-limit the value of the upper limit is not limit to be lower than the cannot be greater be greater than the value of processed. intended upper limit, or raise than the value of the lower limit. the upper limit to be higher queue-backlog- than the lower limit. upper-limit." 14-101 "Printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-53 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-114 " Job
22-54 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-129 "Queue
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-55 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-142 "Filter item
22-56 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-151 "The continuation The server encountered an The request Contact technical support. context is invalid." invalid continuation context is not for the list operation (pdq or processed. pdls). This may be due to an error in the client application program or a memory corruption in the server. 14-152 "The credential is The user is unknown to the The request The user must be added to invalid." system. is not the access control list. processed. 14-153 "The document The specified document is The request Verify the job identifier and number is invalid." unknown to the server. is not the document number. processed. 14-155 "The operation is The physical printer is not The request The requested operation is invalid for the able to process the is not not valid for the physical physical printer." requested operation. processed. printer. 14-156 "The operation is The logical printer is not The request The requested operation is invalid for the logical able to process the is not not valid for the logical printer. printer." requested operation. processed. 14-157 "The operation is The document is not able to The request The requested operation is invalid for the process the requested is not not valid for the document. document." operation. processed. 14-158 "The operation is The initial value document The request The requested operation is invalid for the initial is not able to process the is not not valid for the initial value value document." requested operation. processed. document. 14-159 "The operation is The job is not able to The request The requested operation is invalid for the job." process the requested is not not valid for the job. operation. processed. 14-160 "The operation is The initial value job is not The request The requested operation is invalid for the initial able to process the is not not valid for the initial value value job." requested operation. processed. job. 14-161 "The operation is The queue is not able to The request The requested operation is invalid for the queue." process the requested is not not valid for the queue. operation. processed. 14-162 "The operation is The spooler is not able to The request The requested operation is invalid for the process the requested is not not valid for the spooler. spooler." operation. processed. 14-163 "The operation is The supervisor is not able The request The requested operation is invalid for the to process the requested is not not valid for the supervisor. supervisor." operation. processed. 14-164 "Unknown object The object class is The request Contact technical support. class." unknown or unsupported. is not processed. 14-165 "Queue
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-57 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-166 "Job
22-58 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-175 "The authentication The server encountered The request Contact technical support. information is invalid." invalid authentication is not information. This may be processed. due to an error in the client application program or a memory corruption in the server. 14-178 "The scope is invalid." The server encountered an The request Retry the operation using 0 or invalid scope for the list is not 1. (pdq, pdls) operation. The processed. valid values for scope are zero (0) and one (1). 14-179 "The object The object identification has The request Contact technical support. identification syntax is improper syntax for a is not invalid." specified object class. This processed. may be due to an error in the client application program or a memory corruption in the server. 14-180 "The time limit is Time limit must be greater The request Verify the time-limit value. invalid." than 0 seconds. is not processed. 14-182 "Unable to obtain The server could not obtain The request Contact technical support. attributes for the initial initial value document is not value document." attributes that are needed processed. to process this operation. This may be due to a memory corruption in the server or a corruption in the object database. 14-183 "Unable to obtain a The server needs to obtain The request Contact technical support. read lock for the initial a read lock in order to read is not value document." any information about the processed. object. However, an error occurred getting the lock. This may be due to a memory corruption in the server. 14-184 "Unable to obtain The server could not obtain The request Contact technical support. attributes for the initial initial value job attributes is not value job." that are needed to process processed. this operation. This may be due to a memory corruption in the server or a corruption in the object database.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-59 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-185 "Unable to obtain a The server needs to obtain The request Contact technical support. read lock for the initial a read lock in order to read is not value job." any information about the processed. object. However, an error occurred getting the lock. This may be due to a memory corruption in the server or a corruption in the object database. 14-187 "Unable to obtain the The server could not obtain The request Contact technical support. default values for the the default values for job is not job attributes." attributes that are need to processed. process this operation. This may be due to a memory corruption in the server or a corruption in the object database. 14-191 "Job priority value The value of the job-priority The request Set the job-priority attribute to
14-194 "The AddDocument The server received an The request Contact technical support. request does not AddDocument request is not contain a document without a document processed. description." description. This may be due to an error in the client application program or a memory corruption in the server.
14-195 "The printer is The server failed to retrieve The request Contact technical support. missing the required the required printer is not attribute associated- attribute, associated-queue. processed. queue." Either the object database is corrupted or an unknown error occurred in the attribute set facility.
22-60 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-196 "An individual Only the document The request Check the requested document cannot be attributes can be applied to is not attributes and the object modified with job an individual document. processed. instance. attributes." Job attributes can be used only if ALL of the documents in the job are to be modified.
14-197 "GetOrderedJobs The server received the The request Contact technical support. operation accepts GetOrderedJobs request is not only one printer." with more than one printer processed. specified. This may be due to an error in the client application program or a memory corruption in the server.
14-198 "No physical printers The server could not find a The request Find a printer that supports are supported for the printer that supports the is not the most similar attribute specified job/doc specified attribute and processed. value by entering “pdls -c attributes." value. printer -r
14-201 "The job has no The server received a print The request Contact technical support. documents." request without a document is not description. This may be processed. due to an error in the client application program or a memory corruption in the server.
14-202 "The job is missing The server must check the The request Contact technical support. the required attribute current-job-state attribute in is not current-job-state." order to process the processed. request. This attribute was not found. Either the object database is corrupted or an unknown error has occurred in the attribute set facility. 14-203 "No more document The job has been closed; The request Contact technical support. submissions are no more document is not allowed on job
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-61 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-204 "No modification The server received a The request Contact technical support. attributes were ModifyJob request without a is not specified." list of attributes to modify. processed. This may be due to an error in the client application program or a memory corruption in the server. 14-205 "Modification of The server does not The request Reissue the ModifyJob individual documents support modification of an is not command with the proper job is not supported." individual document. The processed. identifier. modification must be applied to the entire job. 14-206 "Multiple documents This server does not The request Print one document at a time are not supported by support multiple documents is not by issuing a separate print this server." in a single print job. processed. command for each document. 14-207 "The user has no The user does not have The request Check the access control list operation rights." sufficient operation rights is not for the privilege level of the for this operation. processed. user. 14-208 "The printer name is For the print operation, the The request Contact technical support. missing." server received a print is not request without a printer processed. name. This may be due to an error in the client application program or a memory corruption in the server. For the set operation, the server was not able to read the printer- name-requested attribute in order to process the set operation. This may be due to a corruption in the database or a memory error in the server. 14-209 "This request cannot The requested operation The request Reissue the command with be submitted to a can only be submitted to a is not the proper logical printer physical printer." logical printer. processed. name. 14-210 "A null object The server encountered a The request Contact technical support. identification was null object identification. is not passed in." This may be due to an error processed. in the client application program or a memory corruption in the server. 14-211 "Printer
22-62 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-214 "Initial value job An attempt was made to The request Create an initial value job
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-63 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-225 "Invalid operation; The queue associated with The request Verify that the printer’s queue
14-226 "Invalid operation; If performing a pdresubmit The request If performing a pdresubmit
14-227 " Invalid operation; The user submitted a print The request Verify that the printer’s server
14-233 "Job
14-234 "Initial value job The specified initial value The request Verify the initial value job
22-64 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-235 "Document
14-240 "The job has not been The server could not find The request Use the following command found in the the specified job in the is not line to check the status of the database." database. The object may processed. job: pdls -c job
14-241 "The printer has not The server could not find The request Use the following command been found in the the specified printer in the is not line to check the status of the database." database. The object may processed. job: pdls -c print
14-243 "The attribute The specified attribute The request Check the supported values
14-244 "Attribute
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-65 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-245 " Attribute
14-247 "The printer is not The server received a print The request Use the following command supported by this request for a printer it does is not line to view the supported server." not support. processed. printers: pdls -c printer
14-250 "Initial value job The server encountered an The request Verify the initial value job
14-251 "Document
14-252 "Initial value The server encountered an The request Verify the initial value document
14-253 "Printer
14-254 "Queue
14-255 "Server
14-256 "None of the values The specified values are The request Use the pdls command to for
22-66 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 14-257 "The attribute The specified values are The request Use the pdls command to
14-258 "The user has The user does not have The request Check the access control list insufficient operation sufficient operation rights is not for the privilege level of the rights on the initial on this initial value processed. user (pdls -c i-v-d -r a-c-l value document document.
14-259 "The user has The user does not have The request Check the access control list insufficient operation sufficient operation rights is not for the privilege level of the rights on the initial on this initial value job. processed. user (pdls -c i-v-j -r a-c-l value job
16-101 "The server is already The disable command has The request N/A disabled." already been used on the is not server. processed. 16-102 "The server is already The enable command has The request N/A enabled." already been used on the is not server. processed. 16-103 "An error has This error may be caused The request Check the available virtual occurred in the by a memory corruption in is not memory and retry the attribute set facility." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 16-104 "Unable to obtain This error may be caused The request Check the available virtual attributes on the by a memory corruption in is not memory and retry the server." the server, a corruption in processed. operation. If the problem the object database or a persists, contact technical lack of available virtual support. memory. 16-105 "Unable to obtain the This error may be caused The request Retry the operation. If the thread handle." by a memory corruption in is not problem persists, contact the server. processed. technical support. 16-106 "Unable to lock the This error may be caused The request Retry the operation. If the thread on the server." by a memory corruption in is not problem persists, contact the server. processed. technical support. 16-107 "Unable to obtain a This error may be caused The request Retry the operation. If the read lock on the by a memory corruption in is not problem persists, contact server." the server or a corruption in processed. technical support. the object database.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-67 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 16-108 "Unable to set the This error may be caused The request Check the available disk state on the server." by a memory corruption in is not space in the database (or the server, corruption in the processed. spool partitions) and the object database, a lack of available virtual memory available disk space or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-109 "Unable to set This error may be caused The request Check the available disk attributes on the by a memory corruption in is not space in the database (or server." the server, corruption in the processed. spool partitions) and the object database, a lack of available virtual memory available disk space, or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-110 "Unable to set the This error may be caused The request Retry the operation. If the thread priority on the by a memory corruption in is not problem persists, contact server." the server. processed. technical support. 16-111 "Unable to signal This error may be caused The request Retry the operation. If the thread condition on by a memory corruption in is not problem persists, contact the server." the server. processed. technical support. 16-112 "Unable to start a This error may be caused The request Retry the operation. If the new thread on the by a memory corruption in is not problem persists, contact server." the server or a corruption in processed. technical support. the object database. 16-113 "Unable to unlock the This error may be caused The request Retry the operation. If the server." by a memory corruption in is not problem persists, contact the server or a corruption in processed. technical support. the object database. 16-114 "Unable to unlock the This error may be caused The request Retry the operation. If the thread on the server." by a memory corruption in is not problem persists, contact the server. processed. technical support. 16-115 "Unable to obtain a This error may be caused The request Retry the operation. If the write lock on the by a memory corruption in is not problem persists, contact server." the server or a corruption in processed. technical support. the object database. 16-116 "An error has This error may be caused The request Check the available virtual occurred in the by a memory corruption in is not memory and retry the common server utility the server or a lack of processed. operation. If the problem facility." available virtual memory. persists, contact technical support. 16-117 "A transaction error This error may be caused The request Check the available disk has occurred in the by a memory corruption in is not space in the database (or common server utility the server, corruption in the processed. spool partitions) and the facility." object database, a lack of available virtual memory available disk space, or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-118 "An internal error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact document processor." the server. processed. technical support.
22-68 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 16-119 "The function call This error may be caused Retry the operation. If the The request failed due to an by a memory corruption in problem persists, contact is not invalid attribute in the the server. technical support. processed. document processor." 16-120 "There is insufficient This error may be caused Check the available memory The request memory on the server by a problem with the and retry the operation. If the is not to perform the protoserver. problem persists, contact processed. requested operation." technical support. 16-121 "The document This error may be caused The request Retry the operation. If the processor is not in a by a memory corruption in is not problem persists, contact running state." the server. processed. technical support. 16-122 "A system error has This error may be caused Retry the operation. If the The request occurred." by a memory corruption in problem persists, contact is not the server. technical support. processed. 16-123 "An error has This error may be caused The request Retry the operation. If the occurred in the by a memory corruption in is not problem persists, contact document processor." the server. processed. technical support. 16-124 "The specified This error may be caused The request Retry the operation. If the operation is invalid." by a memory corruption in is not problem persists, contact the server. processed. technical support. 16-125 "The requested This error may be caused The request Retry the operation. If the attribute modification by a memory corruption in is not problem persists, contact is invalid." the server. processed. technical support. 16-126 "An error has This error may be caused Check the available virtual The request occurred in the by a memory corruption in memory and retry the is not generic utilities the server or a lack of operation. If the problem processed. facility." available virtual memory. persists, contact technical support. 16-127 "The operation failed This error may be caused The request Retry the operation. If the due to an invalid by a memory corruption in is not problem persists, contact argument." the server. processed. technical support. 16-128 "The operation failed This error may be caused The request Check the available virtual due to an internal by a memory corruption in is not memory and retry the function error." the server or a lack of processed. operation. If the problem available virtual memory. persists, contact technical support. 16-129 "The operation failed An invalid shutdown request The request Retry the operation. If the due to an invalid caused the operation to fail. is not problem persists, contact shutdown request." processed. technical support. 16-130 "The operation failed An invalid server state The request Retry the operation. If the because the server is caused the operation to fail. is not problem persists, contact in an invalid state." processed. technical support. 16-131 "The requested event This error may be caused The request Retry the operation. If the is invalid for the by a memory corruption in is not problem persists, contact current state." the server. processed. technical support. 16-132 "The server cannot The requested delete The request After deleting the jobs in the be deleted while there command is invalid while is not database, the server may be are jobs in the jobs are in the database. processed. deleted. database." 16-133 "The server must be This error may be caused The request Disable the server and retry disabled prior to this by a memory corruption in is not the operation. operation." the server. processed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-69 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 16-134 "An error has This error may be caused The request Check the available disk occurred in the object by a memory corruption in is not space in the database (or database facility." the server, corruption in the processed. spool partitions) and the object database, a lack of available virtual memory available disk space, or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-135 "An error has This error may be caused The request Check the available disk occurred in the print by a memory corruption in is not space in the database (or agent." the server or a lack of processed. spool partitions) and the available virtual memory. available virtual memory before retrying the operation. If the problem persists, contact technical support. 16-136 "The server failed to This error may be caused The request Check the available disk pause the print by a memory corruption in is not space in the database (or agent." the server, corruption in the processed. spool partitions) and the object database, a lack of available virtual memory available disk space, or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-137 "The server failed to This error may be caused The request Check the available disk resume the print by a memory corruption in is not space in the database (or agent." the server, corruption in the processed. spool partitions) and the object database, a lack of available virtual memory available disk space, or a before retrying the operation. lack of available virtual If the problem persists, memory. contact technical support. 16-138 "The specified server The server has not been The request Create a server and retry the was not found." created. is not operation. processed. 16-139 "The supervisor The supervisor does not The request None server does not support the type of is not support the requested operation requested. processed. operation." 16-140 "There is insufficient This error may be caused The request Check the available memory memory on the server by a problem with the is not and retry the operation. If the to perform the protoserver. processed. problem persists, contact requested operation." technical support. 16-141 "There is no queue in This error is caused by a The request Set up a queue, submit jobs the server." missing queue during a is not on the queue and then pdclean operation. There processed. perform a pdclean operation. should be at least one queue on the server when performing this operation.
22-70 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 16-142 "The attribute This error is caused by Lower the value of the The request
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-71 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 18-109 "There is a missing This error may be caused The request Retry the operation. If the argument, printer by a memory corruption in is not problem persists, contact name or server name the server. processed. technical support. in VS LOA." 18-110 "There is a missing This error may be caused The request Retry the operation. If the argument, printer by a memory corruption in is not problem persists, contact name or server name the server. processed. technical support. in VS LOA Continuation." 18-111 "There is a missing This error may be caused The request Retry the operation. If the argument, printer by a memory corruption in is not problem persists, contact name or server name the server. processed. technical support. in VS LOA Abort." 18-112 "There is a missing This error may be caused Retry the operation. If the The request argument, printer by a memory corruption in problem persists, contact is not name or server name the server. technical support. processed. in VS LOA Send Event." 18-113 "The supervisor is not The supervisor may not be The request Check the state of the responding." running or may not be is not supervisor. Restart the functioning properly. processed. supervisor (if necessary) and retry the operation. If the problem persists, contact technical support. 18-114 "Unable to connect to The connection to the The request Check the state of the the supervisor; supervisor has failed. is not supervisor. Restart the supervisor may have processed. supervisor (if necessary) and crashed." retry the operation. If the problem persists, contact technical support. 18-115 "An internal error has This error may be caused The request Retry the operation. If the occurred in the object by a memory corruption in is not problem persists, contact database facility." the server, a corruption in processed. technical support. the object database, a lack of available disk space or a lack of available virtual memory. 18-116 "The supervisor has An authorization error has The request Check the authorization on not processed the occurred. is not the supervisor and retry the request due to an processed. operation. If the problem authorization error." persists, contact technical support. 20-101 "An unknown error This error may be caused The request Check the available memory has occurred in the by a memory corruption in is not and retry the operation. If the attribute set facility." the server or a lack of processed. problem persists, contact available virtual memory. technical support. 30-101 "There is insufficient This error may be caused The request Check the available virtual memory on the server by a lack of available virtual is not memory and retry the to perform the memory. processed. operation. If the problem requested operation." persists, contact technical support.
22-72 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 30-102 "An unknown error This error may be caused The request Check the available memory occurred during by a memory corruption in is not and retry the operation. If the processing of the the server or a lack of processed. problem persists, contact user request." available virtual memory. technical support. 49-103 "PrintXchange lpr This error is caused by a The request Check to see if the Windows inbound gateway Windows NT system error. is not NT installation is correct. failed to start.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-73 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 49-304 "An invalid request This error is caused by an Check to see which machine The request
22-74 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 49-401 "Unable to create cf The creation operation The request Ensure that the disk space is and df names in could not be performed due is not adequate and the pathname
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-75 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 52-206 "Unable to write data A memory allocation The request Restart the LAN Manager via a named-pipe." corruption may have is not inbound gateway. occurred. processed. 52-207 "The port
22-76 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 52-220 "Unable to retrieve The LAN Manager inbound The request Ensure that the spooler is the PrintXchange gateway may have been is not running. printer status via port unable to communicate with processed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-77 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 56-201 "Unable to allocate There is not enough The request Close any other applications memory for the object memory available in the is not that may be running on the
22-78 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 56-303 "Unable to retrieve The value may not be set in The request Ensure that the registry key is the value of the the registry key. is not set in the registry and restart registry key
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-79 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 56-405 "Unable to retrieve The network might be busy The request Retry the operation. If the the NetWare File or the NetWare server may is not problem persists, contact Server addresses be down. processed. technical support. due to a network problem. The QServer inbound gateway will retry later." 56-406 "Unable to retrieve The network might be busy The request Retry the operation. If the the address for or the NetWare server may is not problem persists, contact NetWare file server be down. processed. technical support.
22-80 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 56-412 "Unable to start the The target queue is not The request Check the target queue service for queue serviced by the queue is not configuration using a
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-81 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 56-502 "Unable to set This error may be caused The request Restart the QServer inbound attribute
22-82 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 58-105 Unable to initialize the The Notification Server Events will Check to see if the notification OID facility. could not initialize the be server is running. Object Identifier facility. undelivered. 58-106 Unable to initialize the The Notification Server Events will Check to see if the notification I18N facility. could not initialize the be server is running. Internationalization facility to undelivered. convert messages across locales. 58-107 Unable to initialize the The Notification Server Events will Check to see if the notification e-mail facility. could not initialize the be server is running. system’s e-mail facility. undelivered. Check if Eudora mail facility is installed on the server. If so, enter Eudora. From the Tools command line option, select the MAPI option. In the MAPI option screen, set “Use Eudora MAPI server” to “never”. 58-108 Unable to initialize the The Notification Server Events will Check to see if the notification socket-event facility: could not initialize the be server is running. errno =
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-83 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 58-117 Unable to register the The Notification Server Events will Check to see if the notification RPC. could not register a Remote be server is running. Procedure Call. undelivered. 58-118 Unable to start a The Notification Server Events will Check to see if the notification thread. could not launch a thread. be server is running and the undelivered. system is functioning properly. 58-119 Unable to lock a The Notification Server Events will Check to see if the notification mutex object. could not get a Mutual be server is running and the Exclusion lock on an object. undelivered. system is functioning properly. 58-120 Unable to initialize an The Notification Server Events will Check to see if the notification event object: errno = could not initialize an event be server is running.
22-84 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 59-105 “Unable to process This error may be caused The request Retry the operation. If the data due to an by a memory corruption in is not problem persists, contact unknown error.” the server. processed. technical support. 59-106 “The start date An invalid start date has The request Enter the start date using the
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-85 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 59-116 “Unable to close the During processing of the The request Retry the operation. If the accounting log for the accounting logs, the utility is not problem persists, contact date
22-86 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 60-113 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-87 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 60-131 "
22-88 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 60-160 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-89 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-104 "
61-105 "
22-90 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-125 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-91 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-130 "
22-92 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-136 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-93 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-144 "
61-149 "
61-150 "
22-94 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 61-156 "
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-95 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 62-111 "Unable to retrieve The pddiagjob utility could The request Make sure the job identifier is current job state for not retrieve the job state for is not valid. If user is not the job job
22-96 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 63-104 "An internal error has This is caused by a The request Retry the operation. If the occurred." software problem such as is not problem persists, contact caused by unexpected processed. technical support. failures of system functions. 63-105 "The assignment When using the –x flag, the The request Correct the assignment operator is missing." option argument should is not operator. have the form
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-97 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 63-117 "The left hand side of There are no characters left The request Correct the filter expression. the expression is of one of the logical is not missing." operators (|| or &&). processed. 63-118 "The requested An object instance is The request Add an instance to the operation requires an required for this operation; is not command. instance." none were found. processed. 63-119 "The requested The name of the executable The request Rename the executable using operation is does not match the known is not the correct name. unknown." POSIX operation names. processed. 63-120 "The file was not The attribute file was not The request Correct the attribute filename found." found in the directory or is not or path environment path environment specified. processed. (PDPATH). 63-121 "A qualifier for an There are two possible The request Remove the qualifiers or use attribute assignment causes: either 1) a is not another valid command. is not valid." compulsory qualifier was processed. used with commands other than pdset or pdmod, or 2) a value qualifier was used with commands other than pdset, pdmod, pdpr, or pdcreate. 63-123 "The requested The promote operation may The request Retry the operation using a operation does not only be used to promote a is not single job identifier. allow multiple jobs." single job. processed.
65-101 "A Win32 error has An unexpected Win32 API If the Profile Contact technical support. occurred:
22-98 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 65-103 "A C Runtime error An unexpected C Runtime If the Profile Restart the Profile and Group has occurred:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-99 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 65-109 "The pdc preload file The Profile and Group The Profile Correct the line in the Profile is invalid:
22-100 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 80-104 "The client was The client tool was unable The request Reinstall the client software. unable to perform to initialize due to an is not system initialization." incorrect configuration of processed. the client software. Some required files are missing. 80-105 "The help file registry The help file cannot be The request Reinstall the client software. key was not found." displayed because some is not registry entries are missing. processed. 80-106 "The help file was not The help file cannot be The request Reinstall the client software. found." displayed because a is not corresponding help file is processed. missing. 80-107 "Unable to invoke the Unable to invoke the The request Reinstall the client software external tool specified tool. is not with the specified software
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-101 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 80-118 "This value already Duplicate attributes cannot The request N/A exists in the be added to the supported is not supported list." attribute list. processed. 80-119 "The delivery address A delivery address was not The request Specify the delivery address. was not specified." specified while adding an is not event. processed. 80-120 "The user name was The user name was not The request Specify the user name. not specified." specified while adding is not access rights. processed. 80-121 "The domain name The domain name was not The request Specify the domain name. was not specified." specified while adding is not access rights. processed. 80-122 "The supervisor was There must be a supervisor The request Create a supervisor in the not found in this in the domain in order to is not domain and retry the domain." connect a physical printer to processed. operation. a queue. 80-123 "No duplicates are An attempt was made to The request N/A allowed in the access add a duplicate entry to the is not control list." access rights. processed. 80-124 "The queue cannot An attempt was made to The request Delete all associated logical be deleted until all delete a queue that had is not printers and retry the associated logical associated logical printers. processed. operation. printers have been deleted." 80-125 "The printer port The specified printer port The request Check the format of the format is invalid. The does not have a valid is not printer port. general form is format. processed.
22-102 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 81-102 "Internal error: The name service The request Contact technical support. Unable to initialize the infrastructure has been is not name service client." initialized in client mode, but processed. the requested operation requires server mode initialization. 81-103 "Unable to perform Unable to perform the The request Contact technical support. the requested requested operation due to is not operation due to invalid parameters on the processed. invalid parameters on name service. the name service." 81-104 "The specified The specified domain or The request Ensure that the specified domain or workgroup workgroup may not exist, or is not domain or workgroup exists does not support the the PrintXchange name processed. and that the PrintXchange name service." service may not be running name service is running. on the specified domain or workgroup. 81-106 "Internal error: A The software has issued a The request Contact technical support. name service call call to the name service is not was issued prior to before initializing it. processed. initialization." 81-107 "The name service is There is insufficient virtual The request Close other memory- unable to allocate memory to perform the is not consuming applications and memory for the operation. processed. retry the operation (or reboot requested operation." the client machine). If problem persists, reboot the name server machine. 81-108 "The specified object This error may occur when The request Check to see if the desired was not found on the attempting to access a is not object exists on the name name service." printer in a domain that is processed. service by enumerating the no longer configured. This objects. error will also occur if the PrintXchange Name Service has been moved or the host it resides on is down. 81-110 "The associated The server object The request Contact technical support. object was not found referenced by the printer or is not on the name service." queue object does not exist processed. in the name space. 81-111 "The name service is The name service is not The request If this message was received unavailable." running on the domain or is not while referencing a foreign workgroup. processed. domain or workgroup, ensure that the name service is running on that domain or workgroup. Otherwise, ensure that the system registry entry for the name service points correctly to the name server address.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-103 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 81-112 "Unable to perform An internal error has The request Restart the client software or the requested occurred within the name is not the name service. If the operation for the service. processed. problem persists, contact name service." technical support. 81-113 "The requested An unsupported operation The request Contact technical support. operation is not was submitted against the is not supported on the name service. processed. name service." 8019-101 "The operation failed This error occurs when The request Look for errors in values of due to invalid there is an invalid is not attributes or flags and correct parameters in parameter passed into a processed. them.
22-104 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-112 "There is no current DPAOpenDocument called The request Retry the operation. If the document control with init_code is not problem persists, contact block." DPA_INIT_FROM_CURRE processed. technical support. NT_DCB but no current document exists. 8019-113 "There is no highest DPAOpenDocument called The request Retry the operation. If the document control with init_code is not problem persists, contact block." DPA_INIT_FROM_HIGHES processed. technical support. T_DCB but no current document exists. 8019-114 "The initialization DPAOpenDocument called The request Retry the operation. If the code is unknown." with an init_code that is not is not problem persists, contact defined. processed. technical support. 8019-116 "The attribute The user attempted to set The request Correct the object class (-c
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-105 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-129 "The directory or file The user does not have The request Check and/or modify the
22-106 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-147 "The attribute The matching rule that was The request Check the relational operator
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-107 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-157 "The attribute An attempt was made to The request Ensure that the attribute is
22-108 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-170 "The requester's The requester’s operation The request Modify the requester’s operation rights are rights need to be modified is not operation rights and retry the insufficient." to perform the requested processed. operation. If the problem operation. persists, contact technical support. 8019-171 "The supplied The privilege attribute The request Ensure that the client privilege attribute certificate in is not software is compatible with certificate is invalid." CommonArguments is processed. the server software. invalid. 8019-172 "The supplied The syntax of the identifier The request Contact technical support. identification is is incorrect. is not invalid." processed. 8019-173 "The supplied The server was not able to The request Check to see if the object identification is locate the object instance. is not exists on the server. unknown." processed. 8019-174 "The object already An operation was invoked The request Ensure that the object name exists." that attempted to create an is not does not already exist. object with the same name processed. as an existing object. 8019-175 "The server is busy." The server is presently too The request Retry the operation later. busy to perform the is not requested operation but processed. may be able to do so after a short while. 8019-176 "The server is The server is currently The request Retry the operation later or unavailable." unavailable. is not contact technical support. processed. 8019-177 "The operation is too The operation requested is The request Reduce the complexity and complex." too syntactically or is not retry the operation. If the semantically complex. processed. problem persists, contact technical support. 8019-178 "The resource limits This error may occur when The request Lower the threshold or free have been a very large object is being is not space on the server. exceeded." created or copied. processed. 8019-179 "An unclassified This error may be caused The request Retry the operation. If the server error has by a memory corruption in is not problem persists, contact occurred." the server. processed. technical support. 8019-180 "The are too many The user specified more The request Reduce the number of list items in the list." items in a list than are is not items. supported by the server. processed. 8019-181 "A requested A compulsory attribute The request Ensure that the value is compulsory resource cannot be satisfied because is not available and retry the is not available." the value requested is not processed. operation. If the problem available. persists, contact technical support. 8019-182 "The cancel The user cannot cancel an The request Locate a server that supports document operation individual document within a is not document cancellation. is not supported." document job. processed. 8019-183 "The modify The user cannot modify an The request Locate a server that supports document operation individual document within a is not document modification. is not supported." multiple document job. processed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-109 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-184 "The printing of The user cannot print The request The documents must be multiple documents is multiple documents within a is not printed as separate jobs. not supported." single job. processed. 8019-185 "A supplied A component of an The request Contact technical support. parameter value is argument was specified to a is not not supported." DPA operation that is not an processed. attribute with a value not supported by the server. 8019-186 "The supplied An invalid checkpoint was The request Contact technical support. checkpoint is invalid." supplied to the RESUME is not DPA operation. A processed. checkpoint value becomes invalid if it is altered or corrupted. 8019-187 "The requested The DPA operation The request Contact technical support. operation is not requested is not currently is not supported." supported by the server. processed. This error may be caused by attempting a symbolic link between pdinterrupt and another command. 8019-188 "The supplied An invalid continuation The request Contact technical support. continuation context context was supplied to the is not is invalid." list operation. processed. 8019-189 "The pause limit has Either a pause or interrupt The request Resume some of the jobs been exceeded." request was made to the is not before pausing new ones. server in excess of the processed. number of jobs that may be paused. The server may define this limit on a per- printer or per-server basis. 8019-190 "The requested The print job referred by the The request Wait until the job is modifications are not job identifier is executing is not processed. allowed." and cannot be modified at processed. this time. 8019-191 "The requester's The user’s access rights The request Check the access control list update rights are are insufficient for modifying is not for the privilege level of the insufficient." this object. processed. user. 8019-192 "The previous Additional operations are The request Wait until the previous operation is not allowed until the is not operation has finished. incomplete." previous operation has processed. finished. 8019-193 "The requested Cancellation not possible The request None cancellation is not because the job has already is not possible." completed. processed. 8019-195 "A job number has In a cancel or modify The request Ensure that there is a job not been specified." operation the job identifier is not identifier set for the operation. was not specified. processed. 8019-196 "An object instance No object instance was The request Ensure that the command has not been specified. is not contains an object instance. specified." processed.
22-110 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-197 "There are no more There are no more The request Contact technical support. object instances instances left to return by is not available." DPAGetObjectInstance. processed. 8019-198 "A logical printer or This error may be caused The request Set the PDPRINTER server name was not by entering a pdpr or pdq is not environment variable or specified." command without processed. specify a value for -p or specifying the printer name specify the server name as or by entering a CLI part of the object instance. command that contains a job object without specifying a server name. A printer name may not have been found in the PDPRINTER environment variable. This error may also occur when the object instance specified in the call to DPAGetObjectInstance is not found in the set of returned instances. 8019-199 "There are no more There are no more The request Contact technical support. warnings or errors." warnings or errors left to is not return by processed. DPAGetNextWarningOrErr or. 8019-200 "The attribute is An internal API error has The request Contact technical support. unknown." occurred. is not processed. 8019-201 "The request is DPACloseRequest was The request Contact technical support. already closed." called with a handle that is not has already been closed. processed. 8019-202 "An extended error An internal API error has The request Contact technical support. condition has occurred. is not occurred." processed. 8019-203 "The object identifier An OID set by the user or The request Contact technical support. is unknown." returned by the server is not is not known by the client. processed. 8019-204 "The required routine A function has been The request Contact technical support. has not been requested that is not is not implemented." implemented. processed. 8019-205 "An internal error has This error may occur when The request Retry the operation and check occurred." the server is too busy to is not to see that the server is respond. processed. running. If the problem persists, contact technical support. 8019-206 "Unable to open the The object identifier The request Check PD_OID_DB_PATH or object identifier database is not available. is not the default Object Identifier database." processed. database path. 8019-208 "The request handle An unexpected failure of the The request Contact technical support. initialization has attribute set calls has is not failed." occurred when calling processed. DPAOpenRequest.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-111 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8019-212 "The document An unexpected failure of the The request Contact technical support. handle initialization attribute set calls has is not has failed." occurred when calling processed. DPAOpenRequest. 8019-215 "The specified file A proper file name was not The request Ensure that the file specified name is a directory." provided. is not is actually a file and not a processed. directory. 8022-101 "Spooler
22-112 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-111 "Printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-113 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-120 "Creation of initial The creation operation for The request Retry the operation. If the value job
22-114 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-129 "Deletion of server The deletion operation for The request Retry the operation. If the
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-115 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-138 "Listing of attributes The listing of attributes for The request Retry the operation. If the for documents has documents has not is not problem persists, contact not completed completed successfully for processed. technical support. successfully. the stated reason.
22-116 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-148 "Addition of a The addition of a document The request Retry the operation. If the document to job
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-117 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-158 "Resuming of job The resuming of the The request Retry the operation. If the
22-118 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-166 "Attribute modification The attribute modification of The request Retry the operation. If the of queue
8022-173 "Supervisor: There The Xerox supervisor was The request Check to see if the printer was no response to not able to receive a is not device is running. The printer the SNMP request on response from the printer processed. address and/or community printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-119 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-174 "Supervisor: An The Xerox supervisor on The request Check to see if the physical SNMP SNMP was unable to is not printer is running. The printer communication error communicate with the processed. address, community string, or has occurred in printer device. Either the printer device may also be printer
22-120 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-261 "Creation of initial The creation operation for The request Retry the operation. If the value document the specified server has not is not problem persists, contact
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-121 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-269 "Deletion of printer The deletion operation for The request Retry the operation. If the
22-122 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-278 "Enumeration of jobs The enumeration of new The request Retry the operation. If the for printer
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-123 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-288 "Modification of job The modification of the The request Retry the operation. If the
22-124 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-298 "Resuming of queue The resuming of the The request Retry the operation. If the
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-125 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-307 "Attribute modification The attribute modification of The request Retry the operation. If the of printer
22-126 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-330 "JobID
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-127 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-336 "JobID
22-128 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-340 "Database recovery: An initial-value-document The system Check to see if any logical Initial-value- object was corrupted in the deleted this printers were affected by document object database. It had to be object completing the following
If any printers are returned from this query, take one of the following three actions to correct the situation.
1. Create an initial-value- document with the name
2. Modify the value of the printer-initial-value-document attribute on these printers to use another initial-value- document that exists on the server
3. Modify the value of the printer-initial-value-document attribute on these printers so that an initial-value-document is not used. For example: pdset –c printer –x "printer-initial-value- document=="
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-129 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-341 "Database recovery: An initial-value-job object The system Check to see if any logical Initial-value-job object was corrupted in the deleted this printers were affected by
1. Create an initial-value-job with the name
2. Modify the value of the printer-initial-value-job attribute on these printers to use another initial-value-job that exists on the server
3. Modify the value of the printer-initial-value-job attribute on these printers so that an initial-value-job is not used. For example: pdset –c printer –x "printer-initial-value- job=="
22-130 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-344 "Database recovery: A queue object was The system Recreate the queue. Queue object
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-131 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-348 "Database recovery: An unidentified initial-value- The system Check to see if any logical An unidentified initial- document object was deleted an printers were affected by value-document corrupted in the database. object completing the following object has been It had to be deleted in order during operation: deleted from the for the database to be system pdls –c printer –r printer- initial-value-document
If any initial-value-documents are missing from this query, take one of the following three actions to correct the situation.
1. Recreate the missing initial-value-document.
2. Modify the value of the printer-initial-value-document attribute on these printers to use another initial-value- document that exists on the server
3. Modify the value of the printer-initial-value-document attribute on these printers so that an initial-value-document is not used. For example: pdset –c printer –x "printer-initial-value- document=="
22-132 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-349 "Database recovery: An unidentified initial-value- The system Check to see if any logical An unidentified initial- job object was corrupted in deleted an printers were affected by value-job object has the database. It had to be object completing the following been deleted from the deleted in order for the during operation:
If any initial-value-jobs are missing from this query, take one of the following three actions to correct the situation.
1. Recreate the missing initial-value-job.
2. Modify the value of the printer-initial-value-job attribute on these printers to use another initial-value-job that exists on the server
3. Modify the value of the printer-initial-value-job attribute on these printers so that an initial-value-job is not used. For example: pdset –c printer –x "printer-initial-value- job=="
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-133 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-352 "Database recovery: An unidentified queue The system List all the queues in the An unidentified queue object was corrupted in the deleted an server to identify the missing object has been database. It had to be object queue; then recreate the deleted from the deleted in order for the during missing queue.
22-134 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-358 "Database recovery: An attribute of a job object The system Set the attribute to the The
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-135 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-364 "Database recovery: An unidentified attribute of The system Check all the attributes by An unidentified an initial-value-document deleted an completing the following attribute of the initial- object was corrupted in the attribute operation: value-document database. It had to be during pdls –c initial-value- document -r all object
22-136 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-367 "Database recovery: An unidentified attribute of a The system Check all the attributes by An unidentified print object was corrupted deleted an completing the following attribute of the printer in the database. It had to attribute operation: object
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-137 TROUBLESHOOTING
Table 22-5. Error number, message, explanation, system response, and required action
ERROR MESSAGE EXPLANATION SYSTEM REQUIRED ACTION NUMBER RESPONSE 8022-372 "Xerox Supervisor: The Xerox supervisor was The request Check to see if the printer Unable to resolve not able to resolve the to enable address was registered in the printer address specified printer address the physical host database. Then delete
22-138 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Reference supervisor errors
The following paragraphs discuss how the reference supervisor handles errors of the following types: Abnormal job completion Stall monitoring Printer attention conditions Non-obvious behavior
Abnormal job completion
When the reference supervisor detects an error while printing a job, it sends a job-completed event to the spooler. The supervisor also sets values into the printer attributes printer-state and printer- problem-message and the job attributes job-state-reasons and job-state-message. The following table lists five conditions that the reference supervisor can detect and how it sets the relevant attributes. Note that these conditions always result in the spooler setting current-job-state to one of the following states: retained for later resubmission; user intervention is required. pending; the supervisor automatically submits the job to the same physical printer when the condition is corrected
Table 22-6. Abnormal job completion conditions
Condition Behavior Description
1. Document error If the job ends because the supervisor received an error in the document (e.g. unknown operator in PostScript), then the job ends as follows: job-state-reasons: completed-with-errors job-state-message: the error message from the printer (this message cannot be localized; it’s the text returned from the printer) current-job-state: retained
Note that the supervisor can detect this condition only if communications are bi- directional with the printer.
2. Connection lost If the job ends because of an unexpected error communicating with the physical device after successfully starting the job on the printer: job-state-reasons: completed-with-errors job-state-message: the message provided by the communications backend current-job-state: retained
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-139 TROUBLESHOOTING
Table 22-6. Abnormal job completion conditions
Condition Behavior Description
3. Internal error If the job ends because of an unexpected internal error (e.g. failure of internal interfaces or operating system calls): job-state-reasons: aborted-by-system, printer-unavailable printer-state idle printer-problem-message: Internal error job-state-message: Internal error current-job-state: pending
The supervisor also logs this situation to the system log (see Section 3.5) and provides additional information. The assumption is that a very serious error occurred, and the reliability of the supervisor is suspect.
The supervisor disables the printer. Operator intervention is required to repair the condition and enable the physical printer. Enabling the printer causes the supervisor to clear the printer-problem-message.
4. Printer access error The job ends because the supervisor detected a "fatal" communications configuration error when attempting a connection to the output device. job-state-reasons: aborted-by-system, printer-unavailable printer-state: idle printer-problem-message: the message provided by the communications backend job-state-message: the message provided by the communications backend current-job-state: pending
The supervisor also logs this situation to the system log (see Section 3.5) and provides additional information. Again, note that this situation causes the supervisor to disable the printer. Operator intervention is required to repair the condition and enable the physical printer.
5. Job completion error If the job ends because of an unexpected error with the physical device, but the error occurs after all the document data has been sent to the printer and the supervisor is "completing" the job (including printing a job end page): job-state-reasons: completed-with-warnings job-state-message: message from the communications backend current-job-state: retained
22-140 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Stall monitoring
The reference supervisor detects and reports unexpected inactivity in the input/output to/from the printer while printing a job. This stalled condition can be the result of a problem with: A problem with the interconnect or network. An unreported problem in the printer, like paper out or paper jam. The printer takes a long time to image a complex page. In some cases, a stalled condition "takes care of itself". For example, when a complex page is finally printed and operation continues. In other cases, operator intervention is required. For example, when putting a fresh supply of paper in the printer. During the normal processing of a job, each time the supervisor sends data response timer is in effect restarted. At some point during job processing if a printer fails to respond to an operation within the amount of time specified by the printer attribute printer- timeout-period, a printer-state-change event is reported with the printer-state attribute set to the value timed-out. When the printer again starts responding, the printer response timer is in effect restarted and a printer-state-change event is reported with the printer-state attribute returned with the value set to reflect the current state of the printer, typically printing. The stall monitor timeout value, printer-timeout-period, is expressed in seconds. Although that attribute does not have a default value, the reference supervisor uses 300 seconds if no value has been specified. If an administrator enters 0 for the attribute value, then the supervisor does not monitor I/O activity on the printer. An administrator can modify the value of printer-timeout-period on a per-printer basis using a command of the following form:
pdset -c printer -x "printer-timeout- period=00:05:00"
Printer attention conditions
If, while printing a job, the supervisor detects that the printer needs attention (e.g. the printer has run out of paper); it reports a state- changed-printer event and sets the value of the printer-state attribute to needs-attention. In addition, the supervisor sets the printer attribute printer-problem-message to contain additional information, if any. Note: Notification for the event warning-resource-needs-attention is not being raised. When the printer runs out of paper while a job is printing, the printer-state is set to “needs-attention” but notification is not raised.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-141 TROUBLESHOOTING
Non-obvious behavior
This section lists reference supervisor behavior that may not be obvious. 1. Host connection to printer occurs not before print job submission. The PrintXchange supervisor deliberately does not attempt to make a connection with physical printer devices upon supervisor startup. The problems associated with attempting such connections are numerous and undesirable. The supervisor makes contact with physical printers ONLY upon printing print jobs. This convention helps assure that system startups proceed normally regardless of whether physical printer devices are connected, disconnected, powered-up, powered-down, ready, off-line, etc. 2. Printer-models-supported The PrintXchange supervisor does not maintain a printer-models- supported list. Administrators specify a printer attributes file upon creating each physical printer object. The attributes file specifies a printer model name for that physical printer, but those attributes must be specified for each physical printer, even if they are of the same model. 3. Document Data Overrides Job and Document Attributes Many document files produced by popular applications contain device-specific command sequences for selecting fonts, trays, and other options. Documents that contain such command sequences will cause one of the following to happen: Document prints, but it uses fonts, trays, and options specified in the document, rather than job or document attributes specified with the job (or as part of initial-value- job, initial-value-document attributes for the printer). Document does not print because it selects options that the printer does not supply or support. An error results at the printer that might or might not be reported back to the host, depending on the printer's capabilities and connection method/level. 4. The PrintXchange supervisor does not remove or redefine printer-option command sequences that exist in document data. Users need to be forewarned about such documents, and may need instruction on how to create printer-independent documents.
Exit status
Server exit status
When a server exits, it always returns an exit status. The following table lists all the different exit statuses and a brief description of each. The exit status values are used as a coarse-grained guide to why the server exited. They are beneficial primarily in the case where an error message cannot be delivered for some reason. Ordinarily, a user will be more concerned with the actual error message delivered than the exit status of the server.
22-142 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-7. Server exit status
Exit Status Description
0 Normal server termination via a shutdown request or a SIGTERM signal.
1 Server could not set its locale.
2 Server could not locate its message file.
3 Server could not determine the host name on which it is running.
4 Server could not initialize the threads sub-system.
5 Server could not allocate any dynamic memory.
6 Server detected an error in the parameters passed to it.
7 Server did not have permission to access some directory.
8 Server could not lock the object database.
9 Server could not open or access the object database.
10 Server detected an error in checking/setting a configuration attribute.
11 Server could not successfully run all initialization routines.
12 Server could not register with the name service.
13 Server could not register with the RPC service.
14 Server could not determine its IP address.
15 Server could not establish a signal handler.
16 Server could not initialize the logging subsystem.
17 Server could not fork a child process.
18 Server could not recover the database.
19 Server could not initialize the Mail Delivery system.
20 Server detected an error in the EMail Method parameters passed to it. (NT version only)
99 Server could not register with the Service Control Manager.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-143 TROUBLESHOOTING
Database utilities exit status
The exit status values are used as a coarse-grained guide to why the utility exited. They are beneficial primarily in the case where an error message cannot be delivered for some reason. Ordinarily, a user will be more concerned with the actual error message than the exit status of the utility. In the following table, the error statuses are the same for all database utilities (pdmakedb, pdmoddb, pdshowdb) unless the description names a specific utility.
Table 22-8. Database utilities exit status
Exit Status Description
0 Normal utility exit, no error encountered.
1 A utility detected an error in the parameters passed to it.
2 A utility could not allocate any dynamic memory.
3 A utility could not lock the object database.
4 The pdmakedb utility was asked to create an object database that already exists.
5 The pdmakedb utility could not create an object database.
6 A utility could not open or access an object database.
7 A utility could not locate its message file.
8 A utility could not set its locale.
9 A utility could not initialize the threads sub-system.
10 A utility could not determine its current directory.
11 The pdmakedb or pdmoddb utility determined that the value for a specified path name was too long.
12 The pdmakedb or pdmoddb utility encountered some error while trying to validate user supplied attributes.
13 A utility encountered an error while trying to display the attributes on the server object
22-144 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Crash recovery
Crash refers to the condition where any component of the PrintXchange print system has become inoperable such that the component: Is no longer capable of carrying out its function or responding to external requests Needs to be restarted Crash recovery refers to a series of actions taken by the PrintXchange print system in returning the system to a functional and consistent state with no or minimal data loss.
Server startup
As the spooler and supervisor are starting up from a crash or a normal shutdown, they go through a series of initialization and recovery actions to get the system back to a functional and consistent state. The state of the server upon completion of these actions will be the same as the state at shutdown, or a state as close as possible to the state prior to the crash. As part of the startup action, the servers generate the state-changed- server event indicating state changes, resulting in notification of the server created and server started (if the -F switch is set there is also notification for server initialized and server registered). Physical printer state As part of the startup, the spooler and its associated supervisor(s) go through a process of resynchronization. During this process, the supervisor puts the physical printers associated with a queue into the unknown state. Once resynchronization is established, the supervisor puts the physical printer into the appropriate state.
Note that after a supervisor crash and before the recovery, PrintXchange does not update queue, physical printer, and spooler attribute values to reflect the crash. That is, physical printers associated with the crashed supervisor may appear to be available even though they are not.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-145 TROUBLESHOOTING
Database recovery
In very rare cases, the persistent object database used by a PrintXchange server may become corrupt. This is often caused by an unexpected system crash due to kernel crash or power failure. The database corruption should not happen when the server is shut down normally. If the server is restarted after a crash, the server automatically performs a database integrity check to see if the database has become damaged. The database integrity check goes through the entire database to see if there is any evidence of damaged data within the database. The user may also force the database integrity check at startup even after a normal shutdown with the -c switch in the startup command. The user may wish to do this if the user suspects that the database is somehow corrupt. For example, if the server continues to crash without any indication, the user may want to force the database integrity check during restart. Although the -c switch can be used at each startup, the user should be aware that the database integrity check increases the startup time. If the database integrity check discovers that the database is corrupt, the server attempts to repair the database. In doing so, the server first copies the corrupt database to the object database /backup directory. The server then creates a clean new database in the object database directory and the good data is copied from the corrupt database into the new database. The server logs information on any repairs it makes into the syslog log file. This enables the system administrator to see which objects and attributes required repair and to check that the data is still valid. It should be noted that even after the database has been repaired by the server, the resultant database may still have corrupt data or loss of data. In order to prevent start up of the server with the corrupt database, the server discontinues its startup and exit if it had to repair the database at all. In such cases the server exits with the following message to the console: pdsplr: corrupt object database has been recovered. To acknowledge, please restart using the following command line: pdsplr -a -F server _name. All subsequent startups fail until the user adds the -a switch in the command line. This -a switch forces the server to restart so that the system administrator can check the attributes of server objects to see if the data is correct. After the -a switch is given, a subsequent startup succeeds without the switch until the database becomes corrupt again.
22-146 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Job and document recovery
PrintXchange, in general, does not lose the job once the job has been fully received by the spooler. However, if a crash occurs to a component within PrintXchange, certain actions take place depending on the processing occurring at the time of the crash. The following paragraphs describe these actions.
Spooler or client crash while the job is submitted to the spooler
In this situation: The spooler does not continue to process jobs that it has not fully received by the spooler at the time of a spooler crash. A job is considered fully received by the spooler only if the job is properly closed, and if the spooler has retrieved all of the document data. That is, the job’s current-job-state is not in the pre-processing state, job-submission-complete is not false, and job-state-reasons is not documents-needed. If the spooler has not fully received the job at the time it crashes, the spooler puts the job into the completed state upon its subsequent restart and does not print it. In this case, job-state- reasons includes submission-interrupted. Note: If the spooler crashed during the creation of the job, there may be no record of the job upon crash recovery by the spooler. The spooler does not process those jobs whose document data includes a partially retrieved document. This case is possible with transfer-method value socket where the spooler retrieves the document data asynchronously. In this case, the spooler puts the job into the completed state, and job- state-reasons includes submission-interrupted. The spooler may hold an incomplete job if the client crashes during submission of the job and the document data is complete for each job. This happens if some of the documents have been received by the spooler and all of the document data for those existing documents has been retrieved. If the job is still in the pre- processing state or the attribute job-submission-complete is still false by the 20-minute time-out period, the spooler puts the job in the held state with job-state-reasons of submission- interrupted and job-hold-set. The user can release the job for processing by setting the job-hold attribute to false.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-147 TROUBLESHOOTING
Spooler or supervisor crash during processing or printing
In this situation: If the supervisor is controlling a printer, the supervisor returns the job to the spooler upon restart after a crash of a supervisor or a spooler. During the recovery process, the job (current-job-state) may temporarily be in the unknown state. The administrator has an option of controlling whether such jobs returned by the supervisor should be put into the held or pending state. This is achieved through the use of a logical printer or spooler attribute called hold-jobs-interrupted-by-printer-failure. If the value of hold-jobs-interrupted-by-printer-failure is true or unspecified, jobs returned by the supervisor due to crashes are put into the held state. In this case, the job-state-reasons attribute contains job-interrupted-by-printer-failure and job-hold-set. Users can release the job by setting the job-hold attribute to false. If the hold-jobs-interrupted-by-printer-failure is false, the job is put into the pending state and is rescheduled for processing. The job-state-reasons attribute is empty in this case. The spooler uses the hold-jobs-interrupted-by-printer-failure attribute from the physical printer object if the attribute is specified there. Otherwise the spooler uses the attribute from the server object. Each time the supervisor returns the job due to a crash of the supervisor or a spooler, a read-only attribute called job-fault-count is incremented. The administrator can control how many times the job can be retried through the use of a server configuration attribute called cfg-max-job-fault-count.If job-fault-count exceeds cfg-max- job-fault-count, the job is put into the held state regardless of the value of hold-jobs-interrupted-by-printer-failure. When the job is put into the held state, job-state-reasons includes job-interrupted-by-printer-failure, job-hold-set, and max-job- fault-count-exceeded. Users can release the job by setting the job- hold attribute to false.
22-148 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Job-state-reasons and attributes associated with crash recovery
Table 22-9 lists the job-state-reasons associated with crash recovery of the job. Table 22-10 lists the attributes associated with crash recovery of the job.
Table 22-9. job-state-reasons for crash recovery
job-state-reasons Comments
submission-interrupted The job submission was interrupted due to spooler or client failure. The job can either be in the held or completed state: If all of the document data can be retrieved by the spooler, the spooler puts the job into the held state and adds job-hold-set to job-state-reasons. If the spooler cannot retrieve any of the document data, then it puts the job into the completed state and adds aborted-by- system to job-state-reasons.
aborted-by-system A PSIS-defined value of job-state-reasons that indicates that the job processing or printing was interrupted by failure of the server or the printer controlled by the supervisor.
The job will be in unknown state when this job-state-reasons is set. The spooler eventually put the job into held or pending state depending on the value of the hold-jobs-interrupted-by-printer- failure attribute.
job-interrupted-by-printer-failure A job-state-reasons that indicates that the job has been returned by the supervisor due to spooler or supervisor crash and that the job is put into the held state.
max-job-fault-count-exceeded A job-state-reasons that indicates that the job has been faulted and returned by the supervisor several times and that the job-fault- count exceeded the cfg-max-job-fault-count. The job is automatically put onto held state regardless of the hold-jobs- interrupted-by-printer -failure attribute. This job-state-reasons value is used in conjunction with job-interrupted-by-printer- failure.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-149 TROUBLESHOOTING
Table 22-10. Attributes associated with job crash recovery
Attributes Object Comments
job-fault-count Job An attribute of the job object indicating the number of times the job processing or printing was interrupted by the server due to server or printer failure.
This attribute is a descriptive attribute that is settable only by the spooler. The spooler resets the attribute to zero when the job is resubmitted while at retained state. This attribute is included in the default profile for the accounting record.
cfg-max-job-fault-count Spooler This server object configuration attribute specifies the maximum allowable number of times the job can be faulted.
If the job processing or printing was faulted due to server or printer failure, and the job-fault-count exceeds this number, the job is automatically put into held state regardless of the hold-jobs-interrupted-by-printer-failure attribute.
This is a prescriptive attribute that is settable by users. If the attribute is unspecified, then the spooler puts the job into the held or pending state depending on the value of the hold- jobs-interrupted-by-printer-failure attribute.
default-job-completion- Spooler This server object configuration attribute specifies the minimum period period of time the server keeps the job in the completed state.
This is a prescriptive attribute that is settable by users. If the attribute is unspecified, then the spooler deletes the job immediately upon transitioning it to the completed state.
Xerox supervisor crash recovery
To conform with PSIS, the DP recovers each printer and the jobs submitted to that printer, one printer at a time. The DP creates and registers the printer, and then queries for the job status to collect the latest information of those jobs submitted to that printer. The current-job-state would be printing with job-state-reasons being cascaded. The DP then updates the FE accordingly. The Xerox supervisor supports only job-level-recovery, and it does not maintain any persistency. Thus is if the server crashes during job submission, the FE will resubmit the whole job.
22-150 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
LAN Manager inbound gateway recovery
If the operating system crashes or shuts down while processing jobs exist, the LM-IBG recovers these jobs at the next startup. The LM- IBG: Writes a message (using the PrintXchange logging library) and deletes the job when the error originates in the job itself and the job could not be printed if it were resubmitted. Resubmits the job when the error originates in the system and the job could print if the situation improves. The job status of a recovery job as shown on Windows NT (Start > Settings > Printers > double click on the specific printer) is Connecting. When situation improves on retrying, the job status changes to Printing.
LPR inbound gateway on NT recovery
When the LPR inbound gateway starts, incomplete jobs are in the spool directory (as specified in installation). The gateway tries to submit the remaining jobs. If control files corresponding to the data files remain in the spool directory, the job should be submitted. Otherwise, the spooler deletes the control files or data files because of incomplete jobs.
Accounting
In rare cases, an accounting record for a job may be duplicated due to a crash of a spooler. Such duplicate accounting records resulting from a crash may be identified by examining the started-printing- time and/or the completion-time; the value for these attributes in the duplicate records should be identical. In contrast, each duplicate or multiple accounting record for a job due to resubmission has different values for started-printing-time and completion-time.
Notification
In rare cases, event notification may be duplicated due to a crash of the server.
Client recovery
The CLI is not persistent. Therefore, no crash recovery is necessary. The UNIX GUI will restart when the CDE subsystem comes up after a crash if the appropriate modifications are made to CDE initialization files. Refer to CDE documentation for details.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-151 TROUBLESHOOTING
Operations
Table 22-11 describes the result of an operation if the server (spooler and/or supervisor) handling the operation crashes during the operation. Note: In rare cases, the operation may have been completed by the server, but the client may not have received the return from the operation. As a result, users may be notified that the operation did not complete when in fact the operation was completed by the server.
Table 22-11. Operation results on crash recovery
Operation Object Result
pdclean Spooler Upon subsequent restart of the spooler, the spooler does not continue with Queue the operation. All jobs cancelled prior to a spooler crash are not restored, and remain cancelled.
pdcreate All (except spooler, All changes are rolled back to the state prior to the operation. That is, the supervisor) object is not created.
pddelete Spooler The operation continues upon subsequent restart. Supervisor
Physical printer All changes are rolled back to the state prior to the operation. That is, the Logical printer object will still exist. Queue Initial-value-document Initial-value-job
Job Depending on the progress made by the server, the operation either rolls Document back or continues to completion upon subsequent restart.
pddisable Spooler All changes are rolled back to the state prior to the operation. That is, the Supervisor object remains enabled if it was enabled prior to the operation. Physical printer Logical printer Queue
pdenable Spooler All changes are rolled back to the state prior to the operation. That is, the Supervisor object remains disabled if it was disabled prior to the operation. Physical printer Logical printer Queue
pdls All N/A. No changes as a result of the operation. Note: Continuation context is still valid upon restart.
pdmod Job All changes are rolled back to the state prior to the operation.
pdpause Spooler All changes are rolled back to the state prior to the operation. Queue
Physical printer Depending on the progress made by the server, the operation either rolls back or continues to completion upon subsequent restart.
pdpr See the job recovery section.
pdpromote Job All changes are rolled back to the state prior to the operation.
pdq All N/A. No changes as a result of the operation. Note: Continuation context is still valid upon restart.
22-152 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT TROUBLESHOOTING
Table 22-11. Operation results on crash recovery
Operation Object Result
pdresubmit Spooler Resubmitting jobs from server or queue: Upon subsequent restart of the Queue spooler, the spooler does not continue with the operation. All jobs resubmitted prior to a spooler crash remain resubmitted to the new printer, and they are not restored to the original printer.
Job Resubmitting single job: The job is restored in the original state. The job is not resubmitted.
pdresume Spooler All changes are rolled back to the state prior to the operation. Queue
Physical printer Depending on the progress made by the server, the operation either rolls back or continues to completion upon subsequent restart.
pdrm Job Depending on the progress made by the server, the operation either rolls back or continues to completion upon subsequent restart.
pdset All All changes are rolled back to the state prior to the operation.
pdshutdown Spooler All changes are rolled back to the state prior to the operation. Supervisor
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT 22-153 A. Printers data sheets
This appendix includes a printer data sheet of each printer that can be enabled for PrintXchange supervisors.
Supported output devices
Table A-1 lists the printers and other output devices that PrintXchange supports. The table entries indicate the following: RS = Reference supervisor XS = Xerox supervisor x = Supported connectivity -- = Unsupported connectivity (blank) = To be determined
Table A-1. Output device connectivity
Printer Spvr. Parallel Serial IP-Socket Lpr Lpq Lprm SNMP Other
Printers
DEC Laser3500 RS x x x --
DEC Laser5100 RS x x x ------
Digital DEClaser 2100 RS x x -- --
Digital LA75 RS x ------
Digital LG08 RS x x ------
Digital LN17 RS/XS x x x x -- --
Digital PrintServer 17 RS/XS ------x CPAP
Digital ScriptPrinter RS -- x -- --
HP 6Lxi
HP 4000
HP Color LaserJet RS/XS x x x x ------
HP DeskJet 1600CM RS/XS x x x x ------
HP DesignJet 755CM RS/XS x x x x ------
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-1 PRINTER DATA SHEETS
Table A-1. Output device connectivity
Printer Spvr. Parallel Serial IP-Socket Lpr Lpq Lprm SNMP Other
HP LaserJet 4plus RS/XS x x x x ------
HP LaserJet 4si RS x x x --
HP LaserJet 5Si RS/XS x x x x ------
HP LaserJet 5si Mopier
HP LaserJet IIISi RS x x x ------
Lexmark 4039 10plus RS x x x --
Lexmark 4079 plus RS x x ------
Lexmark Optra C RS/XS x x x x ------
Lexmark Optra E RS x x -- --
Lexmark Optra Lx RS/XS x x x x ------
Lexmark Optra Lxi+ RS/XS x x x x ------
Lexmark Optra N RS/XS x x x x ------
Lexmark Optra Rt+ RS/XS x x x x ------
Lexmark Optra S RS/XS x x x x ------
QMS 2060
QMS 2425
QMS 4060
Sun SPARCprinter E RS x x x --
Xerox 4215 MRP RS/XS x x x x ------
Xerox 4219 MRP RS x x x --
Xerox 4220 MRP RS x x x --
Xerox 4230 MRP RS/XS x x x x ------
Xerox 4235 RS x x -- --
Xerox 4505 RS x x ------
Xerox 4508
Xerox 4510 RS x x ------
Xerox 4512
A-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Table A-1. Output device connectivity
Printer Spvr. Parallel Serial IP-Socket Lpr Lpq Lprm SNMP Other
Xerox 4520 RS/XS x x x x ------
Xerox 4700 II RS x x -- --
Xerox 4915 XS ------x ------
Xerox 4925 XS ------x ------
Xerox C55
Xerox Document Centre 20
Xerox Document Centre 35
Xerox Document Centre 230
Xerox DocuPrint 180 NPS XS ------x -- x -- Proprietary job status
Xerox DocuPrint 4050 XS ------x -- x -- Proprietary NPS job status
Xerox DocuPrint 4090 XS ------x -- x -- Proprietary NPS job status
Xerox DocuPrint 4517 RS/XS x x x x -- --
Xerox DocuPrint 4635 XS ------x -- x -- Proprietary NPS job status
Xerox DocuPrint 4850 XS ------x -- x -- Proprietary NPS job status
Xerox DocuPrint 4890 XS ------x -- x -- Proprietary NPS job status
Xerox DocuPrint N17 RS/XS x x x x -- -- x
Xerox DocuPrint N24 RS/XS x x x x -- -- x
Xerox DocuPrint N32 RS/XS x x x x -- -- x
Xerox DocuPrint N40 RS/XS x x x x -- -- x
Xerox DocuTech 6135 XS ------x -- x -- Proprietary job and printer status
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-3 PRINTER DATA SHEETS
Table A-1. Output device connectivity
Printer Spvr. Parallel Serial IP-Socket Lpr Lpq Lprm SNMP Other
Xerox DocuTech 6180 XS ------x -- x -- Proprietary job and printer status
Xerox DP96
Xerox LaserPress 4150 RS x x -- PS II
Xerox LaserPress 4161 RS x x -- PS II
Xerox N24
Network Print Server boxes
Axis - PrintPoint 560/100
HP Jetdirect EX Plus3 Print Server (J2590a or J2593A)
Lantronix EPS4P1-01
Lexmark - MarkNet Xle - Model 202
Milan - MIL3111FTX
Netque Pro2
A-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer data sheets
Data sheets are available for the following printers: Generic lp printer Generic lpr printer Generic lpr/snmp printer Generic PostScript printer Generic PCL printer Digital DEClaser 2100 PCL5 Digital DEClaser 2150 Level 1 PS DEC Laser3500 Level 2 PS PCL5 DEC Laser5100 Level 2 PS PCL5 Digital LA75 Digital LG08 Digital LN17 Level 2 PS lpr PCL5 Digital PrintServer 17 Level 2 PS lpr PCL5 Digital ScriptPrinter Level 1 PS HP Color LaserJet Level 2 PS lpr PCL5 HP DeskJet 1600CM Level 2 PS lpr PCL5 HP DesignJet 755CM Level 2 PS HP LaserJet 4Mplus Level 2 PS lpr PCL5
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-5 PRINTER DATA SHEETS
HP LaserJet 4si Level 2 PS PCL5 HP LaserJet 5Si Level 2 PS lpr PCL5 HP LaserJet IIISi Level 1 PS /L\ Level 2 PS PCL5 Lexmark 4039 10plus Level 2 PS PCL5 Lexmark 4079 plus Level 2 PS Lexmark Optra C Level 2 PS lpr PCL5 Lexmark Optra E PCL5 Lexmark Optra Lx Level 2 PS lpr PCL5 Lexmark Optra Lxi+ Level 2 PS lpr PCL5 Lexmark Optra N Level 2 PS lpr PCL5 Lexmark Optra Rt+ Level 2 PS lpr PCL5 Lexmark Optra S 1250 Level 2 PS lpr PCL6
A-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Lexmark Optra S 1650 Level 2 PS lpr PCL6 Lexmark Optra S 2450 Level 2 PS lpr PCL6 Sun SPARCprinter E Level 2 PS PCL5 Xerox 4215 MRP Level 2 PS lpr PCL5 Xerox 4219 MRP Level 2 PS PCL5 Xerox 4220 MRP Level 2 PS lpr PCL5 Xerox 4230 MRP Level 2 PS lpr PCL5 Xerox 4235 Level 1 PS PCL4 Xerox 4505 PCL5 Xerox 4510 PCL5 Xerox 4517 Level 2 PS lpr PCL5 Xerox 4520 Level 2 PS lpr PCL5
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-7 PRINTER DATA SHEETS
Xerox 4700II Level 1 PS PCL4 Xerox 4915 lpr Xerox 4925 lpr Xerox Document Centre 230 lpr Xerox DocuPrint 180 NPS lpr Xerox DocuPrint 4050 NPS lpr Xerox DocuPrint 4090 NPS lpr Xerox DocuPrint 4635 NPS lpr Xerox DocuPrint 4850 NPS lpr Xerox DocuPrint 4890 NPS lpr Xerox DocuPrint N17 Level 2 PS lpr PCL5 Xerox DocuPrint N24 Level 2 PS lpr PCL5 Xerox DocuPrint N32 Level 2 PS lpr PCL5 Xerox DocuPrint N40 Level 2 PS lpr PCL5 Xerox DocuTech 6135 lpr Xerox DocuTech 6180 lpr
A-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Data sheets are currently being prepared for the following additional printers: HP 6L HP 4000 HP LaserJet5si Mopier Lexmark Optra S 1620 Lexmark Optra S 2420 QMS 2060 QMS 2425 QMS 4060 Xerox 4508 Xerox 4512 Xerox C55 Xerox Document Centre 20 Xerox Document Centre 35 Xerox DP96 Data sheets are also currently being prepared for the following network print server boxes: Axis - PrintPoint 560/100 HP Jetdirect EX Plus3 Print Server Lantronix EPS4P1-01 Lexmark - MarkNet Xle - Model 202 Milan - MIL3111FTX Netque Pro2
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-9 PRINTER DATA SHEETS
Printer Data Sheet: Generic lp
Printer attribute file name: printer-model: PXC_Generic_lp.paf 1179 lp printer
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript simple-text PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5 job-query-interval = 00:01:00
Printer conditions recognized:
Implementation notes:
A-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Generic lpr
Printer attribute file name: printer-model: PXC_Generic_lpr.paf 1179 lpr printer
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-11 PRINTER DATA SHEETS
Printer Data Sheet: Generic lpr / snmp
Printer attribute file name: printer-model: PXC_Generic_lpr_snmp.paf 1179 lpr and 1759 snmp printer
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a 1179-job-submission n/a snmp-device-status n/a printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5 device-query-interval = 00:00:10
Printer conditions recognized:
Implementation notes:
A-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Generic PostScript
Printer attribute file name: printer-model: PXC_Generic_PS.paf PostScript Printer
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a ip- socket 1 parallel 2 serial 1 printer-tcpip-port-number: See Note 1.
xxx-supported attributes: document-formats-supported = PostScript simple-text sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript sides-ready = 1[2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Set the tcpip port number with the printer-address attribute.
Example: pdset -x “printer-address=HostName:Port”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-13 PRINTER DATA SHEETS
Printer Data Sheet: Generic PCL
Printer attribute file name: printer-model: PXC_Generic_PCL.paf PCL Printer
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a ip- socket 1 parallel 2 serial 1 printer-tcpip-port-number: See Note 1.
xxx-supported attributes: document-formats-supported = PCL simple-text sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL sides-ready = 1[2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Set the tcpip port number with the printer-address attribute.
Example: pdset -x “printer-address=HostName:Port” 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “sides-ready+=2” PrinterName
A-14 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 2100 PCL5
Printer attribute file name: printer-model: Digital_DEClaser2100_PCL5.paf LN05 DEClaser 2100
maximum-printer-speed: printer-connection-method: printer-connection-level: 5 ppm parallel 2 serial 3 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = main output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = main output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-15 PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 2150 Level 1 PS
Printer attribute file name: printer-model: Digital_DEClaser2150_Level1PS.paf LN05 DEClaser 2150
maximum-printer-speed: printer-connection-method: printer-connection-level: 5 ppm parallel 2 serial 3 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = main output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = main output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes:
A-16 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 3500 Level 2 PS
Printer attribute file name: printer-model: Digital_DEClaser3500_Level2PS.paf DEC Laser3500
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 10001
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top main manual [bottom] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top main manual [bottom] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “top” tray. 2. Configure the network card using the printer Control Panel. 3. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-17 PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 3500 PCL5
Printer attribute file name: printer-model: Digital_DEClaser3500_PCL5.paf DEC Laser3500
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 10001
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top main manual [bottom] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top main manual [bottom] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “top” tray. 2. Configure the network card using the printer Control Panel. 3. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-18 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 5100 Level 2 PS
Printer attribute file name: printer-model: Digital_DEClaser5100_Level2PS.paf DEC Laser5100
maximum-printer-speed: printer-connection-method: printer-connection-level: 8 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 10001
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top main manual [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top main manual [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “top” tray. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-19 PRINTER DATA SHEETS
Printer Data Sheet: Digital DEClaser 5100 PCL5
Printer attribute file name: printer-model: Digital_DEClaser5100_PCL5.paf DEC Laser5100
maximum-printer-speed: printer-connection-method: printer-connection-level: 8 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 10001
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top main manual [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top main manual [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “top” tray. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-20 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital LA75
Printer attribute file name: printer-model: Digital_LA75.paf Digital LA75 plus printer-connection-method: maximum-printer-speed: printer-connection-level: 60 cps parallel 2
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = DEC-PPL simple-text input-trays-supported = “” output-bins-supported = “” sides supported = 1 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = DEC-PPL simple-text native-document-formats-ready = DEC-PPL input-trays-ready = “” output-bins-ready = “” sides-ready = 1 print-colour-types-ready = black-and-white
other attributes:
Printer conditions recognized:
Implementation notes: 1. The LA75 is a pin-feed matrix printer. Input trays and output bins have no meaning.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-21 PRINTER DATA SHEETS
Printer Data Sheet: Digital LG08
Printer attribute file name: printer-model: Digital_LG08.paf Digital LG08 printer-connection-method: maximum-printer-speed: printer-connection-level: 600 lpm parallel 2 serial 1 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = DEC-PPL simple-text input-trays-supported = “” output-bins-supported = “” sides supported = 1 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = DEC-PPL simple-text native-document-formats-ready = DEC-PPL input-trays-ready = “” output-bins-ready = “” sides-ready = 1 print-colour-types-ready = black-and-white
other attributes:
Printer conditions recognized:
Implementation notes: 1. The LG08 is a pin-feed line printer. Input trays and output bins have no meaning.
A-22 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital LN17 Level 2 PS
Printer attribute file name: printer-model: Digital_LN17_Level2PS.paf Digital LN17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 3 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top side [bottom] [large-capacity] [envelope] output-bins-supported = top [large] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top side [bottom] [large-capacity] [envelope] output-bins-ready = top [large] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “side” tray 2. The output catch tray is the “large” output tray. 3. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-23 PRINTER DATA SHEETS
Printer Data Sheet: Digital LN17 lpr
Printer attribute file name: printer-model: Digital_LN17_lpr.paf Digital LN17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-read y= none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-24 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital LN17 PCL5
Printer attribute file name: printer-model: Digital_LN17_PCL5.paf Digital LN17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top side [bottom] [large-capacity] [envelope] output-bins-supported = top [large] sides-supported = 1 [2] plexes-supported = simplex print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top side [bottom] [large-capacity] [envelope] output-bins-ready = top [large] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “side” tray 2. The output catch tray is the “large” output tray. 3. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-25 PRINTER DATA SHEETS
Printer Data Sheet: Digital PrintServer 17 Level 2 PS
Printer attribute file name: printer-model: Digital_PrintServer17_Level2PS.paf Digital PrintServer 17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm digital-printserver 5
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Common Printer Access Protocol 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “sides-supported+=2” PrinterName
A-26 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital PrintServer 17 lpr
Printer attribute file name: printer-model: Digital_PrintServer17_lpr.paf Digital PrintServer 17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-27 PRINTER DATA SHEETS
Printer Data Sheet: Digital PrintServer 17 PCL5
Printer attribute file name: printer-model: Digital_PrintServer17_PCL5.paf Digital PrintServer 17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm digital-printserver 5
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Common Printer Access Protocol 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x sides-supported+=2 PrinterName
A-28 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Digital ScriptPrinter Level 1 PS
Printer attribute file name: printer-model: Digital_LN03R_Level1PS.paf LN03R ScriptPrinter
maximum-printer-speed: printer-connection-method: printer-connection-level: 5 ppm serial 1
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = main output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = main output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-29 PRINTER DATA SHEETS
Printer Data Sheet: HP Color LaserJet Level 2 PS
Printer attribute file name: printer-model: HP_ColorLaserJet_Level2PS.paf HP Color LaserJet
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm ip-socket 1 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top [side] [manual] output-bins-supported = top side sides-supported = 1 print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top [side] [manual] output-bins-ready = top side sides-ready = 1 print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
A-30 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP Color LaserJet lpr
Printer attribute file name: printer-model: HP_ColorLaserJet_lpr.paf HP Color LaserJet
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-31 PRINTER DATA SHEETS
Printer Data Sheet: HP Color LaserJet PCL5
Printer attribute file name: printer-model: HP_ColorLaserJet_PCL5.paf HP Color LaserJet
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top [side] [manual] output-bins-supported = top side sides-supported = 1 print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top [side] [manual] output-bins-ready = top side sides-ready = 1 print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
A-32 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP DeskJet 1600CM Level 2 PS
Printer attribute file name(s): printer-model(s): HP_DeskJet1600CM_Level2PS.paf HP DeskJet 1600CM
maximum-printer-speed: printer-connection-method: printer-connection-level: 8 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top manual [large-capacity] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top manual [large-capacity] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-33 PRINTER DATA SHEETS
Printer Data Sheet: HP DeskJet 1600CM lpr
Printer attribute file name(s): printer-model(s): HP_DeskJet1600CM_lpr.paf HP DeskJet 1600CM
maximum-printer-speed: printer-connection-method: printer-connection-level: 8 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
A-34 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP DeskJet 1600CM PCL5
Printer attribute file name(s): printer-model(s): HP_DeskJet1600CM_PCL5.paf HP DeskJet 1600CM
maximum-printer-speed: printer-connection-method: printer-connection-level: 8 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top manual [large-capacity] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top manual [large-capacity] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-35 PRINTER DATA SHEETS
Printer Data Sheet: HP DesignJet 755CM Level 2 PS
Printer attribute file name(s): printer-model(s): HP_DesignJet755CM_Level2PS.paf HP DesignJet 755CM
maximum-printer-speed: printer-connection-method: printer-connection-level: n/a ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white full-colour
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white full-colour
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
A-36 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 4plus Level 2 PS
Printer attribute file name: printer-model: HP_LaserJet4plus_Level2PS.paf HP LaserJet 4plus, 4Mplus
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top main manual [bottom] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top main manual [bottom] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-37 PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 4plus lpr
Printer attribute file name: printer-model: HP_LaserJet4plus_lpr.paf HP LaserJet 4plus, 4Mplus
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
A-38 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 4plus PCL5
Printer attribute file name: printer-model: HP_LaserJet4plus_PCL5.paf HP LaserJet 4plus, 4Mplus
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top main manual [bottom] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top main manual [bottom] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-39 PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 4Si Level 2 PS
Printer attribute file name: printer-model: HP_LaserJet4Si_Level2PS.paf HP LaserJet 4Si , 4Si MX
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [envelope] output-bins-supported = top side sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [envelope] output-bins-ready = top side sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. If output stacker is installed, it is “side” output bin. 3. If high-capacity paper feeder is installed, it is “bottom” input tray. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=envelope PrinterName
A-40 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 4Si PCL5
Printer attribute file name: printer-model: HP_LaserJet4Si_PCL5.paf HP LaserJet 4Si, 4Si MX
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [envelope] output-bins-supported = top side sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [envelope] output-bins-ready = top side sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. If output stacker is installed, it is “side” output bin. 3. If high-capacity paper feeder is installed, it is “bottom” input tray. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=envelope PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-41 PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 5Si Level 2 PS
Printer attribute file name: printer-model: HP_LaserJet5Si_Level2PS.paf HP LaserJet 5Si, 5Si MX
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom side manual [large-capacity] [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom side manual [large-capacity] [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-42 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 5Si lpr
Printer attribute file name: printer-model: HP_LaserJet5Si_lpr.paf HP LaserJet 5Si, 5Si MX
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-43 PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet 5Si PCL5
Printer attribute file name: printer-model: HP_LaserJet5Si_PCL5.paf HP LaserJet 5Si, 5Si MX
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom side manual [large-capacity] [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom side manual [large-capacity] [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-44 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet IIISi Level 1 PS / Level 2 PS
Printer attribute file name: printer-model: HP_LaserJetIIISi_Level1PS.paf HP LaserJet IIISi HP_LaserJetIIISi_Level2PS.paf
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=envelope” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-45 PRINTER DATA SHEETS
Printer Data Sheet: HP LaserJet IIISi PCL5
Printer attribute file name: printer-model: HP_LaserJetIIISi_PCL5.paf HP LaserJet IIISi
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=envelope” PrinterName
A-46 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark 4039 10plus Level 2 PS
Printer attribute file name: printer-model: Lexmark_4039plus_Level2PS.paf Lexmark 4039 10plus
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-47 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark 4039 10plus PCL5
Printer attribute file name: printer-model: Lexmark_4039plus_PCL5.paf Lexmark 4039 10plus
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
A-48 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark 4079 plus Level 2 PS
Printer attribute file name: printer-model: Lexmark_4079plus_Level2PS.paf Lexmark 4079 plus
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm parallel 2 serial 3 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Color ink jet
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-49 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra C Level 2 PS
Printer attribute file name: printer-model: Lexmark_OptraC_Level2PS.paf Lexmark Optra C
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top side [bottom] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top side [bottom] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “side” tray. 2. The side output tray is manually activated. 3. Configure the network card using the printer Control Panel. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
A-50 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra C lpr
Printer attribute file name: printer-model: Lexmark_OptraC_lpr.paf Lexmark Optra C
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-51 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra C PCL5
Printer attribute file name: printer-model: Lexmark_OptraC_PCL5.paf Lexmark Optra C
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top side [bottom] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white full-colour job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top side [bottom] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white full-colour job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The multi-purpose feeder is the “side” tray. 2. The side output tray is manually activated. 3. Configure the network card using the printer Control Panel. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
A-52 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra E PCL5
Printer attribute file name: printer-model: Lexmark_OptraE_PCL5.paf Lexmark Optra E
maximum-printer-speed: printer-connection-method: printer-connection-level: 6 ppm parallel 2 serial 1 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top manual [bottom] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top manual [bottom] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. PCL5 only. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-53 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lx Level 2 PS
Printer attribute file name: printer-model: Lexmark_OptraLx_Level2PS.paf Lexmark Optra Lx
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-54 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lx lpr
Printer attribute file name: printer-model: Lexmark_OptraLx_lpr.paf Lexmark Optra Lx
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-55 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lx PCL5
Printer attribute file name: printer-model: Lexmark_OptraLx_PCL5.paf Lexmark Optra Lx
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-56 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lxi+ Level 2 PS
Printer attribute file name: printer-model: Lexmark_OptraLxiPlus_Level2PS.paf Lexmark Optra Lxi+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-57 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lxi+ lpr
Printer attribute file name: printer-model: Lexmark_OptraLxiPlus_lpr.paf Lexmark Optra Lxi+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-58 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Lxi+ PCL5
Printer attribute file name: printer-model: Lexmark_OptraLxiPlus_PCL5.paf Lexmark Optra Lxi+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [side] [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [side] [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=side” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-59 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra N Level 2 PS
Printer attribute file name: printer-model: Lexmark_OptraN_Level2PS.paf Lexmark Optra N
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom side manual [large-capacity] [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom side manual [large-capacity] [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-60 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra N lpr
Printer attribute file name: printer-model: Lexmark_OptraN_lpr.paf Lexmark Optra N
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-61 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra N PCL5
Printer attribute file name: printer-model: Lexmark_OptraN_PCL5.paf Lexmark Optra N
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom side manual [large-capacity] [envelope] output-bins-supported = top side sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom side manual [large-capacity] [envelope] output-bins-ready = top side sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
A-62 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Rt+ Level 2 PS
Printer attribute file name: printer-model: Lexmark_OptraRtPlus_Level2PS.paf Lexmark Optra Rt+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [large-capacity] [envelope] [side] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [large-capacity] [envelope] [side] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray. 2. The front output tray is manually activated. 3. Configure the network card using the printer Control Panel. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-63 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Rt+ lpr
Printer attribute file name: printer-model: Lexmark_OptraRtPlus_lpr.paf Lexmark Optra Rt+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-64 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra Rt+ PCL5
Printer attribute file name: printer-model: Lexmark_OptraRtPlus_PCL5.paf Lexmark Optra Rt+
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [large-capacity] [envelope] [side] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [large-capacity] [envelope] [side] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The rear feeder is the “side” tray. 2. The front output tray is manually activated. 3. Configure the network card using the printer Control Panel. 4. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-65 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1250 Level 2 PS
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1250_Level2PS.paf Lexmark Optra S 1250
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 manual [2] [3] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 manual [2] [3] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
Example: pdset -x default-input-tray+=“2 3” PrinterName
A-66 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1250 lpr
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1250_lpr.paf Lexmark Optra S 1250
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-67 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1250 PCL6
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1250_PCL6.paf Lexmark Optra S 1250
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 manual [2] [3] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready =PCL input-trays-ready = 1 manual [2] [3] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
Example: pdset -x default-input-tray+=bottom PrinterName
A-68 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1650 Level 2 PS
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1650_Level2PS.paf Lexmark Optra S 1650
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 manual [2] [3] [4] [envelope] output-bins-supported = top [stacker-1] [stacker-2] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 manual [2] [3] [4] [envelope] output-bins-ready = top [stacker-1] [stacker-2] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate Example: pdset -x input-tray-supported+=“2 3 4” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-69 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1650 lpr
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1650_lpr.paf Lexmark Optra S 1650
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-70 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 1650 PCL6
Printer attribute file name(s): printer-model(s): Lexmark_OptraS1650_PCL6.paf Lexmark Optra S 1650
maximum-printer-speed: printer-connection-method: printer-connection-level: 16 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 manual [2] [3] [4] [envelope] output-bins-supported = top [stacker-1] [stacker-2] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 manual [2] [3] [4] [envelope] output-bins-ready = top [stacker-1] [stacker-2] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate
Example: pdset -x input-tray-supported+=“2 3 4” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-71 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 2450 Level 2 PS
Printer attribute file name(s): printer-model(s): Lexmark_OptraS2450_Level2PS.paf Lexmark Optra S 2450
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 3 manual [4] [5] [envelope] output-bins-supported = top [stacker-1] [stacker-2] [stacker-3] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 3 manual [4] [5] [envelope] output-bins-ready = top [stacker-1] [stacker-2] [stacker-3] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate Example: pdset -x output-bins-supported = “top stacker-1 stacker-2” PrinterName
A-72 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 2450 lpr
Printer attribute file name(s): printer-model(s): Lexmark_OptraS2450_lpr.paf Lexmark Optra S 2450
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-73 PRINTER DATA SHEETS
Printer Data Sheet: Lexmark Optra S 2450 PCL6
Printer attribute file name(s): printer-model(s): Lexmark_OptraS2450_PCL6.paf Lexmark Optra S 2450
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 2 3 manual [4] [5] [envelope] output-bins-supported = top [stacker-1] [stacker-2] [stacker-3] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 3 manual [4] [5] [envelope] output-bins-ready = top [stacker-1] [stacker-2] [stacker-3] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate Example: pdset -x output-bins-supported = “top stacker-1 stacker-2” PrinterName
A-74 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Sun SPARCprinter E Level 2 PS
Printer attribute file name: printer-model: SUN_SPARCprinterE_Level2PS.paf Sun SPARCprinter E
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 4 parallel 2 serial 3 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top manual [bottom] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top manual [bottom] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-75 PRINTER DATA SHEETS
Printer Data Sheet: Sun SPARCprinter E PCL5
Printer attribute file name: printer-model: SUN_SPARCprinterE_PCL5.paf Sun SPARCprinter E
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 9100
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top manual [bottom] [envelope] output-bins-supported = top sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top manual [bottom] [envelope] output-bins-ready = top sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
A-76 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4215 MRP Level 2 PS
Printer attribute file name: printer-model: Xerox_4215_Level2PS.paf Xerox 4215 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 15 ppm ip-socket 1 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom manual [large-capacity] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom manual [large-capacity] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The front output tray is manually activated. 2. Configure the network card using rarp, then telnet
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-77 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4215 MRP lpr
Printer attribute file name: printer-model: Xerox_4215_lpr.paf Xerox 4215 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 15 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-78 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4215 MRP PCL5
Printer attribute file name: printer-model: Xerox_4215_PCL5.paf Xerox 4215 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 15 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom manual [large-capacity] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom manual [large-capacity] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. The front output tray is manually activated. 2. Configure the network card using rarp, then telnet
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-79 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4219 MRP Level 2 PS
Printer attribute file name: printer-model: Xerox_4219_Level2PS.paf Xerox 4219 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top middle bottom manual output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top middle bottom manual output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Wait for “manual feed” display before inserting paper.
A-80 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4219 MRP PCL5
Printer attribute file name: printer-model: Xerox_4219_PCL5.paf Xerox 4219 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top middle bottom manual output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top middle bottom manual output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. Wait for “manual feed” display before inserting paper.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-81 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4220 MRP Level 2 PS
Printer attribute file name: printer-model: Xerox_4220_Level2PS.paf Xerox 4220 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 3 side [4] output-bins-supported = top side [stacker-1] sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 3 side [4] output-bins-ready = top side [stacker-1] sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=4” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-sheet inserter is “side” 3. The printer output bins map to the values of output-bins-supported and output-bins-ready as follows: high capacity stacker is “stacker-1”
A-82 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4220 MRP lpr
Printer attribute file name: printer-model: Xerox_4220_lpr.paf Xerox 4220 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-83 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4220 MRP PCL5
Printer attribute file name: printer-model: Xerox_4220_PCL5.paf Xerox 4220 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 2 3 side [4] output-bins-supported = top side [stacker-1] sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 3 side [4] output-bins-ready = top side [stacker-1] sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=main” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-sheet inserter is “side” 3. The printer output bins map to the values of output-bins-supported and output-bins-ready as follows: high capacity stacker is “stacker-1”
A-84 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4230 MRP Level 2 PS
Printer attribute file name: printer-model: Xerox_4230_Level2PS.paf Xerox 4230 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 3 4 side output-bins-supported = top side [stacker-1] sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 3 4 side output-bins-ready = top side [stacker-1] sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x output-bins-supported+=“top side stacker-1” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-sheet inserter is “side” 3. The printer output bins map to the values of output-bins-supported and output-bins-ready as follows: high capacity stacker is “stacker-1”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-85 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4230 MRP lpr
Printer attribute file name: printer-model: Xerox_4230_lpr.paf Xerox 4230 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-86 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4230 MRP PCL5
Printer attribute file name: printer-model: Xerox_4230_PCL5.paf Xerox 4230 MRP
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 2 3 4 side output-bins-supported = top side [stacker-1] sides-supported = 1 2 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 3 4 side output-bins-ready = top side [stacker-1] sides-ready = 1 2 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x output-bins-supported+=“top side stacker-1” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-sheet inserter is “side” 3. The printer output bins map to the values of output-bins-supported and output-bins-ready as follows: high capacity stacker is “stacker-1”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-87 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4235 Level 1 PS
Printer attribute file name: printer-model: Xerox_4235_Level1PS.paf Xerox 4235
maximum-printer-speed: printer-connection-method: printer-connection-level: 35 ppm serial 3 parallel 2 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top middle bottom large-capacity output-bins-supported = top large sides-supported = 1 2 print-colour-types-supported=black-and-white job-sheets-supported=none job-copy-start job-copy-wrap document-sheets-supported=none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top middle bottom large-capacity output-bins-ready = top large sides-ready = 1 2 print-colour-types-ready=black-and-white job-sheets-ready=none job-copy-start job-copy-wrap document-sheets-ready=none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
A-88 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4235 PCL4
Printer attribute file name: printer-model: Xerox_4235_PCL4.paf Xerox 4235
maximum-printer-speed: printer-connection-method: printer-connection-level: 35 ppm serial 1 parallel 2 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top middle bottom large-capacity output-bins-supported = top large sides-supported = 1 2 print-colour-types-supported=black-and-white job-sheets-supported=none job-copy-start job-copy-wrap document-sheets-supported=none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top middle bottom large-capacity output-bins-ready = top large sides-ready = 1 2 print-colour-types-ready=black-and-white job-sheets-ready=none job-copy-start job-copy-wrap document-sheets-ready=none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-89 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4505 PCL5
Printer attribute file name: printer-model: Xerox_4505_PCL5.paf Xerox 4505
maximum-printer-speed: printer-connection-method: printer-connection-level: 5 ppm parallel 2 serial 1 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = main [large-capacity] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = main [large-capacity] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. The 4510 emulates PCL5 only.
2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate Example: pdset -x input-trays-supported+=large-capacity PrinterName
A-90 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4510 PCL5
Printer attribute file name: printer-model: Xerox_4510_PCL5.paf Xerox 4510
maximum-printer-speed: printer-connection-method: printer-connection-level: 10 ppm parallel 2 serial 1 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = main output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = main output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
Printer conditions recognized:
Implementation notes: 1. The 4510 emulates PCL5 only.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-91 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4517 Level 2 PS
Printer attribute file name: printer-model: Xerox_4517_Level2PS.paf Xerox 4517
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 3 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top side [middle] [bottom] [envelope] output-bins-supported = top [large] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top side [middle] [bottom] [envelope] output-bins-ready = top [large] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
A-92 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4517 lpr
Printer attribute file name: printer-model: Xerox_4517_lpr.paf Xerox 4517
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-93 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4517 PCL5
Printer attribute file name: printer-model: Xerox_4517_PCL5.paf Xerox 4517
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top side [middle] [bottom] [envelope] output-bins-supported = top [large] sides-supported = 1 [2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top side [middle] [bottom] [envelope] output-bins-ready = top [large] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=bottom” PrinterName
A-94 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4520 Level 2 PS
Printer attribute file name: printer-model: Xerox_4520_Level2PS.paf Xerox 4520
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top middle bottom manual [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top middle bottom manual [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-95 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4520 lpr
Printer attribute file name: printer-model: Xerox_4520_lpr.paf Xerox 4520
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-96 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4520 PCL5
Printer attribute file name: printer-model: Xerox_4520_PCL5.paf Xerox 4520
maximum-printer-speed: printer-connection-method: printer-connection-level: 20 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2501
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top middle bottom manual [large-capacity] [envelope] output-bins-supported = top sides-supported = 1 print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top middle bottom manual [large-capacity] [envelope] output-bins-ready = top sides-ready = 1 print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Configure the network card using the printer Control Panel. 2. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x “input-trays-supported+=large-capacity” PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-97 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4700 II Level 1 PS
Printer attribute file name: printer-model: Xerox_4700II_Level1PS.paf Xerox 4700 II
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm serial 3 parallel 2 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = top bottom [large-capacity] output-bins-supported = large sides-supported = 1 print-colour-types-supported=black-and-white full-colour job-sheets-supported=none job-copy-start job-copy-wrap document-sheets-supported=none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = top bottom [large-capacity] output-bins-ready = large sides-ready = 1 print-colour-types-ready=black-and-white full-colour job-sheets-ready=none job-copy-start job-copy-wrap document-sheets-ready=none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=large-capacity PrinterName
A-98 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4700 II PCL4
Printer attribute file name: printer-model: Xerox_4700II_PCL4.paf Xerox 4700 II
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm serial 1 parallel 2 printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top bottom [large-capacity] output-bins-supported = large sides-supported = 1 print-colour-types-supported=black-and-white full-colour job-sheets-supported=none job-copy-start job-copy-wrap document-sheets-supported=none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = top bottom [large-capacity] output-bins-ready = large sides-ready = 1 print-colour-types-ready=black-and-white full-colour job-sheets-ready=none job-copy-start job-copy-wrap document-sheets-ready=none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=large-capacity PrinterName
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-99 PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4915 lpr
Printer attribute file name: printer-model: Xerox_4915_lpr.paf Xerox 4915
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white full-colour
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white full-colour
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
A-100 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox 4925 lpr
Printer attribute file name: printer-model: Xerox_4925_lpr.paf Xerox 4925
maximum-printer-speed: printer-connection-method: printer-connection-level: 12 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing = 5
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-101 PRINTER DATA SHEETS
Printer Data Sheet: Xerox Document Centre 230 lpr
Printer attribute file name: printer-model: Xerox_DocumentCentre230_lpr.paf Xerox Document Centre 230
maximum-printer-speed: printer-connection-method: printer-connection-level: 30 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 10
Printer conditions recognized:
Implementation notes:
A-102 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 180 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint180NPS_lpr.paf Xerox DocuPrint 180 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 180 ppm 1179-job-submission n/a xpp-job-status 1179-job-cancel printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the supported media values by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-103 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 4050 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint4050NPS_lpr.paf Xerox DocuPrint 4050 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 50 ppm 1179-job-submission n/a xpp-job-status 1179-job-cancel printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the supported media values by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer.
A-104 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 4090 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint4090NPS_lpr.paf Xerox DocuPrint 4090 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 92 ppm 1179-job-submission n/a xpp-job-status 1179-job-cancel printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the supported media values by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-105 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 4635 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint4635NPS_lpr.paf Xerox DocuPrint 4635 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 135 ppm 1179-job-submission n/a xpp-job-status 1179-job-cancel printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the supported media values by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer.
A-106 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 4850 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint4850NPS_lpr.paf Xerox DocuPrint 4850 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 50 ppm 1179-job-submission n/a printer-tcpip-port-number: n/a xpp-job-status 1179-job-cancel
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape highlight-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown black highlight-colour-rendering-algorithms-supported = automatic colourToHighlight colourTables presentation pictorial highlight-mapping-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown black media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white highlight-colour
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 highlight-colours-ready = black variable (printer dependent, only one other supported value) media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white highlight-colour
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the media values supported by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer. 4. The attribute highlight-colours-supported is set to all the highlight color values supported by this printer. Update the attribute with the highlight color values supported at each site. 5. Set attribute highlight-colours-ready to color values currently loaded (black plus one highlight color).
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-107 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint 4890 NPS lpr
Printer attribute file name: printer-model: Xerox_DocuPrint4890NPS_lpr.paf Xerox DocuPrint 4890 NPS
maximum-printer-speed: printer-connection-method: printer-connection-level: 92 ppm 1179-job-submission n/a printer-tcpip-port-number: n/a xpp-job-status 1179-job-cancel
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL Interpress sides-supported = 1 2 plexes-supported = simplex duplex tumble content-orientations-supported = portrait landscape reverse-portrait reverse-landscape highlight-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown black highlight-colour-rendering-algorithms-supported = automatic colourToHighlight colourTables presentation pictorial highlight-mapping-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown black media-supported = iso-a4-white na-letter-white na-legal-white thickening-supported = entire-document bitmap-images finishings-supported = none [staple] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white highlight-colour
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL Interpress sides-ready = 1 2 highlight-colours-ready = black variable (printer dependent, only one other supported value) media-ready = na-letter-white na-legal-white finishings-ready = none [staple] print-colour-types-ready = black-and-white highlight-colour
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 2. The attribute media-supported is set to all the media values supported by this printer. Update the attribute with the media values supported at each site. 3. Set the attribute media-ready to the media values currently loaded on the printer. 4. The attribute highlight-colours-supported is set to all the highlight color values supported by this printer. Update the attribute with the highlight color values supported at each site. 5. Set attribute highlight-colours-ready to color values currently loaded (black plus one highlight color).
A-108 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N17 Level 2 PS
Printer attribute file name: printer-model: Xerox_DocuPrintN17_Level2PS.paf Xerox DocuPrint N17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 side [2] [3] [envelope] output-bins-supported = top [stacker-1] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 side [2] [3] [envelope] output-bins-ready = top [stacker-1] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“2 3” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-109 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N17 lpr
Printer attribute file name: printer-model: Xerox_DocuPrintN17_lpr.paf Xerox DocuPrint N17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
A-110 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N17 PCL5
Printer attribute file name: printer-model: Xerox_DocuPrintN17_PCL5.paf Xerox DocuPrint N17
maximum-printer-speed: printer-connection-method: printer-connection-level: 17 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 side [2] [3] [envelope] output-bins-supported = top [stacker-1] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 side [2] [3] [envelope] output-bins-ready = top [stacker-1] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“2 3” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-111 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N24 Level 2 PS
Printer attribute file name: printer-model: Xerox_DocuPrintN24_Level2PS.paf Xerox DocuPrint N24
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 side manual [3] [4] [5] [envelope] output-bins-supported = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
A-112 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N24 lpr
Printer attribute file name: printer-model: Xerox_DocuPrintN24_lpr.paf Xerox DocuPrint N24
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-113 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N24 PCL5
Printer attribute file name: printer-model: Xerox_DocuPrintN24_PCL5.paf Xerox DocuPrint N24
maximum-printer-speed: printer-connection-method: printer-connection-level: 24 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 2 side manual [3] [4] [5] [envelope] output-bins-supported = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
A-114 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N32 Level 2 PS
Printer attribute file name: printer-model: Xerox_DocuPrintN32_Level2PS.paf Xerox DocuPrint N32
maximum-printer-speed: printer-connection-method: printer-connection-level: 32 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 side manual [3] [4] [5] [envelope] output-bins-supported = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-115 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N32 lpr
Printer attribute file name: printer-model: Xerox_DocuPrintN32_lpr.paf Xerox DocuPrint N32
maximum-printer-speed: printer-connection-method: printer-connection-level: 32 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
A-116 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N32 PCL5
Printer attribute file name: printer-model: Xerox_DocuPrintN32_PCL5.paf Xerox DocuPrint N32
maximum-printer-speed: printer-connection-method: printer-connection-level: 32 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = top middle [bottom] [main] [large-capacity] output-bins-supported = top side sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-117 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N40 Level 2 PS
Printer attribute file name: printer-model: Xerox_DocuPrintN40_Level2PS.paf Xerox DocuPrint N40
maximum-printer-speed: printer-connection-method: printer-connection-level: 40 ppm ip-socket 3 parallel 2 serial 3 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PostScript simple-text input-trays-supported = 1 2 side manual [3] [4] [5] [envelope] output-bins-supported = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text native-document-formats-ready = PostScript input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
A-118 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N40 lpr
Printer attribute file name: printer-model: Xerox_DocuPrintN40_lpr.paf Xerox DocuPrint N40
maximum-printer-speed: printer-connection-method: printer-connection-level: 40 ppm 1179-job-submission n/a
printer-tcpip-port-number: n/a
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap job-copy-end document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL native-document-formats-ready = PostScript PCL print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap job-copy-end document-sheets-ready = none doc-set-start-copies-separate
other attributes: max-concurrent-job-processing = 1
Printer conditions recognized:
Implementation notes:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-119 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuPrint N40 PCL5
Printer attribute file name: printer-model: Xerox_DocuPrintN40_PCL5.paf Xerox DocuPrint N40
maximum-printer-speed: printer-connection-method: printer-connection-level: 40 ppm ip-socket 1 parallel 2 serial 1 printer-tcpip-port-number: 2000
xxx-supported attributes: document-formats-supported = PCL simple-text input-trays-supported = 1 2 side manual [3] [4] [5] [envelope] output-bins-supported = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-supported = 1[2] print-colour-types-supported = black-and-white job-sheets-supported = none job-copy-start job-copy-wrap document-sheets-supported = none doc-set-start-copies-separate
xxx-ready attributes: document-formats-ready = PCL simple-text native-document-formats-ready = PCL input-trays-ready = 1 2 side manual [3] [4] [5] [envelope] output-bins-ready = top side [stacker-1] [stacker-2] [stacker-3] [mailbox-1 thru mailbox-10] sides-ready = 1 [2] print-colour-types-ready = black-and-white job-sheets-ready = none job-copy-start job-copy-wrap document-sheets-ready = none doc-set-start-copies-separate
other attributes:
Printer conditions recognized:
Implementation notes: 1. Attribute values in square brackets are printer options. These values are not included in the printer attribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.
Example: pdset -x input-trays-supported+=“3 4 5” PrinterName 2. The printer input trays map to the values of input-trays-supported and input-trays-ready as follows: multi-bypass feeder is “side”
A-120 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuTech 6135 lpr
Printer attribute file name: printer-model: Xerox_DocuTech6135_lpr.paf Xerox DocuTech 6135
maximum-printer-speed: printer-connection-method: printer-connection-level: 135 ppm 1179-job-submission n/a xpp-job-status printer-tcpip-port-number: xpp-device-status n/a 1179-job-cancel
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL TIFF sides-supported = 1 2 plexes-supported = simplex duplex tumble outputs-supported = no-page-collate page-collate media-supported = na-letter-white na-legal-white ledger iso-a0-white iso-a1-white iso-a2-white iso-a3-white iso-a4-white iso-a5-white iso-a6-white iso-a7-white iso-a8-white iso-a9-white iso-a10-white iso-b0-white iso- b1-white iso-b2-white iso-b3-white iso-b4-white iso-b5-white iso-b6-white iso-b7-white iso-b8-white iso-b9- white iso-b10-white jis-b0-white jis-b1-white jis-b2-white jis-b3-white jis-b4-white jis-b5-white jis-b6-white jis- b7-white jis-b8-white jis-b9-white jis-b10-white content-orientations-supported = portrait landscape document-sheets-supported = doc-set-start-copies-separate finishings-supported = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL TIFF sides-ready = 1 2 outputs-ready = no-page-collate page-collate document-sheets-ready = doc-set-start-copies-separate media-ready = na-letter-white na-legal-white finishings-ready = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00 device-query-interval=00:05:00
Implementation notes: 1. The booklet maker is saddle-stitch finishing. The singlePortrait stapling is staple or staple-top-left finishing. The singleLandscape stapling is staple-bottom-left finishing. The dualLandscape stapling is staple-dual-left finishing. 2. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 3. The attribute media-supported is set to all the media values supported by this printer. Update the attribute with the media values supported at each site. 4. Set the attribute media-ready to the media values currently loaded on the printer.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT A-121 PRINTER DATA SHEETS
Printer Data Sheet: Xerox DocuTech 6180 lpr
Printer attribute file name: printer-model: Xerox_DocuTech6180_lpr.paf Xerox DocuTech 6180
maximum-printer-speed: printer-connection-method: printer-connection-level: 180 ppm 1179-job-submission n/a xpp-job-status printer-tcpip-port-number: xpp-device-status n/a 1179-job-cancel
xxx-supported attributes: document-formats-supported = PostScript simple-text PCL TIFF sides-supported = 1 2 plexes-supported = simplex duplex tumble outputs-supported = no-page-collate page-collate media-supported = na-letter-white na-legal-white ledger iso-a0-white iso-a1-white iso-a2-white iso-a3-white iso-a4-white iso-a5-white iso-a6-white iso-a7-white iso-a8-white iso-a9-white iso-a10-white iso-b0-white iso- b1-white iso-b2-white iso-b3-white iso-b4-white iso-b5-white iso-b6-white iso-b7-white iso-b8-white iso-b9- white iso-b10-white jis-b0-white jis-b1-white jis-b2-white jis-b3-white jis-b4-white jis-b5-white jis-b6-white jis- b7-white jis-b8-white jis-b9-white jis-b10-white content-orientations-supported = portrait landscape document-sheets-supported = doc-set-start-copies-separate finishings-supported = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind] x-image-shift-range-supported = -432:432 y-image-shift-range-supported = -364:364 print-colour-types-supported = black-and-white
xxx-ready attributes: document-formats-ready = PostScript simple-text PCL TIFF sides-ready = 1 2 outputs-ready = no-page-collate page-collate document-sheets-ready = doc-set-start-copies-separate media-ready = na-letter-white na-legal-white finishings-ready = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind] print-colour-types-ready = black-and-white
other attributes: max-concurrent-job-processing=20 job-query-interval=00:01:00 device-query-interval=00:05:00
Implementation notes: 1. The booklet maker is saddle-stitch finishing. The singlePortrait stapling is staple or staple-top-left finishing. The singleLandscape stapling is staple-bottom-left finishing. The dualLandscape stapling is staple-dual-left finishing. 2. Attribute values in square brackets are printer options. If the printer option is not installed, remove these values with pdset or during pdcreate. Example: pdset -x “finishings-supported-=staple staple-top-left” PrinterName 3. The attribute media-supported is set to all the media values supported by this printer. Update the attribute with the media values supported at each site. 4. Set the attribute media-ready to the media values currently loaded on the printer.
A-122 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT B. Server startup commands, switches and exit status codes
This appendix covers the following functions for PrintXchange: Server startup commands Server startup commands switches Server startup commands exit status codes.
Server startup commands
To avoid permission problems, always run the servers as Superuser (root). The command syntax for starting a PrintXchange server is: executable_name [-a] [-c] [-d ODBpath] [-e emailAddress] [-F] serverName [-O srcOIDpath] where, executable_name Name of the executable file that contains the code for the server: pdsplr for spoolers pdspvr for reference supervisors pdxspvr for Xerox supervisors serverName Name of the server and corresponding object database. -a Acknowledge data loss switch required for server startups after the server had to repair the object database as part of a crash recovery. -c Optional switch to force a database integrity check at startup after a normal shutdown. -d ODBpath Location of the object database if it is other than the default. -e EmailAddress Optional switch to specify an email address for delivery of startup error messages. -F Optional switch to specify that the server should run in the foreground. ServerName Name of the server and corresponding object database. -O Location of OID database if it is other than the default.
The next section provides additional information about switches -a, -c, -d, -e, and -F.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT B-1 SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES
Server startup command switches
All of the server startup command switches are optional, except for the -a switch, which is required, only after a server undergoes a crash recovery.
-a = Acknowledge data loss switch
The -a switch is a required switch only for server startups taking place after the server had to repair the object database as part of a crash recovery. Requiring the -a switch in the startup command serves to remind you to check that attribute values of server objects are correct, and thereby prevent you from starting the server with a possibly corrupt database. An error message indicates that you need to use the -a switch to start the server. After the server restarts, check the syslog file on /var/adm/messages for messages stating that data was corrupted, if any. Additional information on database recovery may be found in the “Troubleshooting” chapter of this guide.
-c = Check database integrity switch
The -c switch is an optional switch that forces a database integrity check at startup after a normal shutdown. (The server automatically checks the database integrity when it restarts after a crash.) You may want to use the -c switch if you suspect that the database is somehow corrupt. Additional information on database recovery may be found in the “Troubleshooting” chapter of this guide. The database integrity check increases the server startup time.
-d ODBpath = Server database location switch
The server requires a server name on startup so that it can locate its object database. By default, the server assumes that the object database resides in a standard location for all server object databases (/var/pd/odb). You have the option of creating a server database in a non-standard location. If the object database for a particular server exists in a non- standard location, then use the -d switch with the startup command to specify where the database resides. The -d switch specifies only the directory in which the server object database exists. The server startup command passes the database name itself with the serverName parameter. Example: pdsplr -d /opt/otherdir myserver where: /opt/otherdir is the ODBpath parameter for the -d switch, and myserver is the serverName parameter for the server command pdsplr In this example, the full path name to the object database is /opt/otherdir/myserver.
B-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES
The object database is actually a directory itself that contains several data files. Conceptually, however, you can think of the database as a single entity.
-e emailAddress = Email address switch
The -e switch is an optional switch that specifies an email address for delivery of server startup errors. When the server encounters an error during startup, the server: Delivers an error message to standard error Writes the error message to syslog If you specify an email address with the -e switch, the server also sends the error message to the specified email address. For example, the following command attempts to start the server myserver, whose object database does not yet exist: pdsplr -e [email protected] myserver When the server encounters the error, it prints the following message to standard error:
Error starting print server “myserver” on “achilles” due to the following:
pdsplr: database does not exist:
./myserver
The -e switch causes the server to send an email message, such as the following, to [email protected]:
Date: Mon, 12 Jan 1998 14:34:22 -0800 From: Superuser (root)@msn.com (0000-Admin(0000)) Subject: PrintXchange Server Startup Failure Sender: [email protected] Apparently-To: [email protected] Content-Type: text
Error starting print server “myserver” on “achilles” due to the following:
pdsplr: database does not exist:
./myserver
Achilles, in this case, is the name of the host machine. The server delivers email on a best effort basis. If for some reason the server cannot deliver the message, the server ignores the email problem. The server sends email messages only in case of unrecoverable errors, so the server normally exits very soon after sending the error message.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT B-3 SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES
-F
By default: The server connects to the service control manager. The default condition means that the server is not attached to a terminal and the server cannot be halted by a control-C command. If a user requires the server to run in the command prompt (typically for debugging purposes), the user must specify the -F switch, because the server can not determine automatically whether a user requires console mode or SCM mode. If the server is started up from a command prompt without the -F switch, the server will not start properly and it will fail.
Source OID path switch [-O srcOIDpath]
The server requires a server name on startup so that it can locate its object database. By default, the server assumes that the object database resides in a standard location for all server object databases (/var/pd/odb). When creating the servers in the GUI, the database path and OID path can be specified. They can later be changed via the GUI or by specifying pdmoddb –d for database path and -O for OID path. The default value for the database path is %PX_ROOT%\var\odb. The default value for the OID path is %PX_ROOT%\share\oid.
-m email_method
Specifies the email method (SMTP or MSMAIL). This is optional.
O (OIDDataBaseLocation)
The -O switch identifies the location of the OID database. The OID database is needed by the server to check the characteristics of certain attributes. A path name that references a legal OID database should be specified for the scrOIDpath. If an OID database does not exist in the location specified by scrOIDpath, the server prints an error message and exits. If the –O switch is not specified, the source OID path name defaults to NT %PX_ROOT%\share. On a correctly installed system, this path name should contain a legal OID database.
B-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES
Server startup exit status codes
If the server starts up normally (the server does not encounter any errors), then the server starts waiting on client requests and processes those requests as they come in. If the server encounters an error during startup, it prints out an error message to standard error and exits with a non-zero exit status. The exit status codes are:
0 Normal server termination via a shutdown request or a SIGTERM signal.
1 Server could not set its locale.
2 Server could not locate its message file.
3 Server could not determine the host name on which it is running.
4 Server could not initialize the threads sub-system.
5 Server could not allocate any dynamic memory.
6 Server detected an error in the parameters passed to it.
7 Server did not have permission to access some directory.
8 Server could not lock the object database.
9 Server could not open or access the object database.
10 Server detected an error in checking/setting a configuration attribute.
11 Server could not successfully run all initialization routines.
12 Server could not register with the name service.
13 Server could not register with the RPC service.
14 Server could not determine its IP address.
15 Server could not establish a signal handler.
16 Server could not initialize the logging subsystem.
17 Server could not fork a child process.
18 Server could not recover the database.
19 Server could not initialize the Mail Delivery system.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT B-5 SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES
20 Server detected an error in the Email Method parameters passed to it. (NT version only)
30 Server detected an illegal value type in the parameters in the registry.
31 Server could not get the server name from the registry.
32 Server could not get a configuration value form the registry.
33 Server detected an error in the parameters in the registry.
99 exit status code means that server detected a system error.
The “Troubleshooting” chapter in this guide lists the server startup error messages.
B-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C. Working with object databases
This appendix covers the following functions: Managing the object database Modifying an existing object database (pdmoddb) Displaying object database data (pdshowdb) Object data utilities exit status codes.
Managing the object database
Every PrintXchange server has an object database (ODB) associated with it. The object database stores all PrintXchange object (printers, queues, jobs, etc.) information that exists in the system. The object database provides persistency such that the server does not lose any important information across restarts. This section describes the set of utilities that allow you to create and/or modify an object database. The utilities are: pdmoddb for modifying an existing object database pdshowdb for displaying data in an existing object database. The utilities allow you to create a server database and initialize the required attributes to allow the server to start. Once the server comes up, creations or modifications to other objects in the database take place internally through the normal use of the CLI client commands or the client GUI. The required attributes include configuration attributes that indicate the location of certain files used for PrintXchange processing, as well as the type of RPC authentication that the server will use: cfg-spool-path cfg-server-runtime-dir cfg-src-oid-path cfg-src-odb-path cfg-acct-log-file-path cfg-rpc-auth-type The utilities also allow you to set the values of some attributes that are not considered to be configuration attributes, including: server-type access-control-list The server-type attribute determines whether the database is for a spooler or a supervisor server. The utility is the only way by which you can set the attribute server-type. Once you create a database of a particular server type, you cannot change it.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-1 WORKING WITH OBJECT DATABASES
The access-control-list attribute is valid on all types of objects. The database utilities allow the value of the server object's access- control-list attribute to be set and or modified.
Modifying an existing object database (pdmoddb)
The pdmoddb utility is used to modify an existing object database. The modifications are made only to the attributes of the server object within the object database. The pdmoddb routine modifies attributes as specified by the user and also adds any default attributes that are missing from the server object and are not specified by the user. The pdmoddb utility can only be used to modify an existing object database. If pdmoddb is asked to create a database that appears not to exist, it returns an error message and exits. pdmoddb also returns an error if it attempts to access a database in use by a running server. The pdmoddb utility has the following command line syntax: pdmoddb [-a acctLogPath] [-A adminACL] [-d ODBpath] [-h] (help switch) [-n serverName] [-O srcOIDpath] [-r serverAuthType] [-R runtimeDir] [-t serverType] [-s spoolDir] [-v] (verbose switch) Note that all the switches are optional. If a switch is specified, pdmoddb modifies the corresponding attribute. If a switch is not specified, pdmoddb leaves the corresponding attribute unmodified unless it does not exist at all on the server object, then pdmoddb adds the attribute with a default value. The -d and -h switches behave the same as with other database commands. The -a, -A, -O, -r, -R, and -s switches behave the same way except that the default syntax specified below is also supported. The switch [-t serverType] for pdmoddb is available to the PrintXchange system itself and only for NT; it is not available to the end user or on UNIX systems. If the switch is not specified for pdmoddb, the system assumes you are modifying a spooler server. This switch controls PXC retrieval of NT registry information. It does not change the type of an existing server.
C-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT WORKING WITH OBJECT DATABASES
Syntax for specifying default values
The pdmoddb utility allows a special syntax for setting attributes to their default values. For the -a, -A, -O, -r, -R, and -s switches, if the value specified is an equals sign (=), pdmoddb sets the attribute to its default value. For example, passing "-a =" to pdmoddb, sets the value of the cfg- acct-log-file-path attribute to its default value, /var/pd/acct/
Database name switch [-n serverName]
This switch tells pdmoddb what the name of an existing object database is. If the database specified by the switch does not exist, then pdmoddb prints an error message and exits. If -n is not specified, pdmoddb uses
Verbose switch [-v]
This switch tells pdmoddb to print out various informational messages.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-3 WORKING WITH OBJECT DATABASES
Displaying object database data (pdshowdb)
The pdshowdb utility is used to show the values of certain configuration attributes on the server object. It can be used by an administrator to interrogate the object database when the server is not running. The pdshowdb utility does not modify any of the attributes on the server object and does not change the object database in any way. The format that pdshowdb uses to print out the server object attributes is the same format used by pdmoddb when the -v switch is specified. The pdshowdb utility has the following command line syntax: pdshowdb [-d ODBpath] [-e] [-h] (help switch) [-n serverName] [-t serverType]
Server ODB path switch [-d ODBpath]
This switch behaves the same way as it does for pdmoddb.
Server executable file path switch [-e]
This switch outputs the absolute file path of the server executable file from the cfg-exec-file-path attribute. The output format is:
Help switch [-h]
The –h switch tells pdshowdb to print out a usage message. If the –h switch is specified, then pdshowdb only prints out the usage message and does not do anything else, even if other switches have also been specified..
Database name switch [-n serverName]
This switch behaves the same way as it does for pdmoddb.
Server type switch [-t serverType]
This switch allows PrintXchange to retrieve NT registry information.
Exit status description
When any of the database utilities exits, it always returns an exit status. For a list of all the different exit statuses and a brief description of each, refer to the “Troubleshooting” chapter in this guide.
C-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT WORKING WITH OBJECT DATABASES
Database utility error messages
For a list of the error messages that the database utilities may display, refer to the “Troubleshooting” chapter in this guide. Table C-1 describes each of the switches.
ODB utility command line switches All of the object database utility command line switches are optional. In most cases, the switch sets a server attribute. The following table lists the switches, and provides a brief description, the corresponding server attribute, and the utilities for which they are valid.
Table C-1. ODB utility command line switches
Switch Description Attribute Utility
-a acctLogPath File path for the accounting log cfg-acct-log-file- pdmoddb path
-A adminACL Set administrator access access-control-list pdmoddb
-d ODBpath File path for the object database pdmoddb files pdshowdb
-D srcODBpath Location of the source object cfg-src-odb-path database
-e execFilePath Absolute path to the executable file cfg-exec-file-path pdshowdb used to start the server
-h Utility usage message n/a pdmoddb pdshowdb
-L locale Server locale locale
-n serverName Name of the object database and server-name pdmoddb of the corresponding server pdshowdb
-O srcOIDpath Location of the OID database cfg-src-oid-path pdmoddb pdshowdb
-r serverAuthType RPC authentication type cfg-rpc-auth-type pdmoddb
-R runtimeDir Location of the server’s runtime cfg-server-runtime- pdmoddb directory dir
-s spoolDir Location where the server spools cfg-spool-path pdmoddb documents to be printed
-t serverType Type of object database: spooler server-type or supervisor
-v Prints processing messages and n/a pdmoddb server attribute values
-a acctLogpath Server accounting log path switch
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-5 WORKING WITH OBJECT DATABASES
Description: The -a switch specifies the location of the server accounting log files. You can use any legal UNIX directory path name for acctLogPath. The directory to which acctLogPath points does not have to exist at the time you run pdmoddb. The server creates the directory (if possible) when the server starts up (although the server does not attempt to create any of the parent directories, if they do not exist). Default: If the –a switch is not specified, the accounting log directory defaults to: /var/pd/acct Attribute: cfg-acct-log-file-path
-A adminACL Administrator access control list switch Description: The -A switch specifies the initial administrator of the server object. You can add other values for administrators as well as operators and users once the server is operational and responding to DPA requests. The -A switch causes pdmoddb to create or modify the server access-control-list attribute with the value specified by the value of adminACL. The format of admin_acl is: {name =admin_name [name_type=name_type]} where admin_name and name-type adhere to the parameter definitions for access-control-list as described in the PrintXchange Command Line Interface Reference Guide. Default: If the –A switch is not specified, the utility creates a default ACL. The default ACL has two values: 1. domain=
-d ODBpath Server ODB path switch Description: The -d switch specifies the location of the object database files. Your UID must have write permission for the path specified as ODBpath. If the directory does not exist or the utility cannot write to it, pdmoddb prints an error message and exit. If the directory does not exist or the utility cannot read it, pdshowdb displays an error message and exits. Default: /var/pd/odb Attribute: The pdmoddb and pdshowdb utilities operate (create, modify, or display) on the object database in the directory specified by the -d switch (or in /var/pd/odb if -d is not specified). The name of the database is as specified by the -n switch (or as specified by the default database name if -n is not specified).
C-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT WORKING WITH OBJECT DATABASES
The object database is actually a directory itself that contains several data files. Conceptually, however, you can think of the database as a single entity.
-D srcODBpath Source ODB path switch Description: The -D switch specifies the location of the source object database (ODB). The source ODB database is part of the PrintXchange software installation and servers as the template for creating an object database The switch parameter srcODBpath must be the path name that references the empty, source ODB database; it cannot reference a previously created ODB database. If an ODB source database does not exist in the location specified by srcODBpath or if the database is not empty, utility prints an error message and exits. Default: /usr/pd/share/odb Attribute: cfg-src-odb-path
-e execFilePath Server executable file path switch and command switch (only applies to pdshowdb) Description: The -e switch displays the absolute path and the spooler or supervisor executable file that starts the server. When used with pdshowdb, it displays the absolute path and the server’s executable file that starts the server. Attribute: cfg-exec-file-path
-h Help switch Accounting log path switch Description: The -h switch causes pdmoddb and pdshowdb to print a usage message. If you specify the -h switch, then the utility only prints the usage message and does not do anything else, even if you specify other switches. Default: None Attribute: n/a
-L locale Locale switch Description: The -L switch sets the locale attribute on the server object with the value specified by locale. The locale syntax is: ll_CC.charset where: ll= language CC= country charset= character set You must enter the locale value in upper- and lower- case characters because the value is case sensitive. Default: Current process locale Attribute: locale
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-7 WORKING WITH OBJECT DATABASES
-n serverName Database name switch Description: The -n switch specifies the name of the object database. This name is also the name of the server. The name serverName may consist of any of the following characters: A – Z a – z 0 – 9 hyphen ( - ) underscore ( _ ) Must be no longer than 255 characters Must be a legal UNIX file name (because one or more directories will be created in the file system using the supplied name) The -n switch works together with the -t switch to identify the name of the server as well as the type of server: spooler or supervisor. If the database specified by the -n switch does not exist, pdmoddb and pdshowdb print an error message and exit. The same is true if you do not specify the -n switch and the database with the default name does not exist. Default: -t switch is only needed for NT Attributes: server-name server-type
-O srcOIDpath Source OID path switch Description: The -O switch specifies the location of the OID database. The server and pdmoddb or pdshowdb need the OID database to check the characteristics of certain attributes. The path name srcOIDpath should reference a legal OID database. If an OID database does not exist in the location specified by srcOIDpath, and pdmoddb print an error message and exit. Default: /usr/pd/share/oid Attribute: cfg-src-oid-path
-r serverAuthType Server RPC authentication switch Description: The -r switch specifies which of the RPC authentication types the server will use. The only legal value for serverAuthType is SYS. Default: SYS Attribute: cfg-rpc-auth-type
C-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT WORKING WITH OBJECT DATABASES
-R runtimeDir Server runtime directory switch Description: The -R switch specifies the location of the server's runtime directory. When the server starts, it changes the current directory to its runtime directory. The server interprets all paths that it encounters relative to the server's runtime directory. The runtime directory runtimeDir can be any legal UNIX directory path name. The directory to which runtimeDir points does not have to exist at the time you run pdmoddb. The server creates the directory (if possible) when the server starts up (although the server does not attempt to create any of the parent directories, if they do not exist). Default: /var/spool/pd/serverName (serverName is as specified with the -n switch) Attribute: cfg-server-runtime-dir
-s spoolDir Server spool directory switch Description: The -s switch specifies the location where the server spools documents to be printed. The spool directory spoolDir can be any legal UNIX directory path name. The directory to which spoolDir points does not have to exist at the time you run pdmoddb. The server creates the directory (if possible) when the server starts up (although the server does not attempt to create any of the parent directories, if they do not exist). Default: /var/spool/pd/serverName (serverName is as specified with the -n switch) Attribute: cfg-spool-path
-t serverType Server type switch Description: The -t switch specifies the type of object database, spooler or supervisor. You must create an object database of the appropriate type for the server that will use the database. The legal values for serverType are: SPL for a spooler SUP for a supervisor. Refer to the discussion for the -n switch. Default: SPL (spooler database) Attribute: server-type
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-9 WORKING WITH OBJECT DATABASES
-v Verbose switch Accounting log path switch Description: The -v switch causes pdmoddb to print various messages as it validates any attributes passed on the command line. For example, if you specify the -A, -r and -v switches on the command line, the following messages appear: Validating requested server attributes: Checking attribute: access-control-list Checking attribute: cfg-rpc-auth-type All requested server attributes are valid
The -v switch also causes pdmoddb to print the values of all the server attributes after pdmoddb finishes creating or modifying the object database. The following is an example of the output from pdmoddb:
Current server attributes:
achilles_spl:server-state = ready achilles_spl:server-internal-state = 2 achilles_spl:object-classes-supported = server achilles_spl:enabled = FALSE achilles_spl:conformance-levels-supported = level-1 level-1M level-2 level-2M achilles_spl:cfg-src-odb-path = /usr/pd/share/odb achilles_spl:cfg-src-oid-path = /usr/pd/share/oid achilles_spl:cfg-spool-path = /var/spool/pd/achilles_spl achilles_spl:cfg-server-runtime-dir = /var/spool/pd/achilles_spl achilles_spl:cfg-acct-log-file-path = /var/pd/acct/achilles_spl achilles_spl:access-control-list = administrator:sysadmin achilles_spl:server-type = spooler achilles_spl:cfg-rpc-auth-type = SYS achilles_spl:cfg-max-log-backups = 4 achilles_spl:cfg-days-to-keep-acct-logs = 3 achilles_spl:cfg-safe-size-for-acct-logs =1000000 achilles_spl:cfg-time-for-new-acct-log = 03:15:00
Note: The configuration attributes are primarily internal attributes. Typically you will not have to access them.
Default: Nothing printed, except for error messages Attribute: n/a
C-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT WORKING WITH OBJECT DATABASES
Object database utilities exit status codes
When any of the object database utilities exits, it always returns an exit status. The server uses the exit status values as a coarse- grained guide to why the utility exited. The status codes are beneficial primarily in the case where an error message cannot be delivered for some reason. Ordinarily, you will be more concerned with the actual error message than with the exit status of the utility. For addition information on error messages, refer to the “Troubleshooting” chapter. In the following list, the error statuses are the same for all utilities unless the description names a specific utility. 0 - Normal utility exit, no error encountered. 1 - A utility detected an error in the given parameters. 2 - A utility could not allocate any dynamic memory. 3 - A utility could not lock the object database. 4 - The utility was asked to create an object database that already exists. 5 - The utility could not create an object database. 6 - A utility could not open or access an object database. 7 - A utility could not locate its message file. 8 - A utility could not set its locale. 9 - A utility could not initialize the threads subsystem. 10 - A utility could not determine its current directory. 11 - The pdmoddb utility determined that the value for a specified path name was too long. 12 - The pdmoddb utility encountered some error while trying to validate user-supplied attributes. 13 - A utility encountered an error while trying to display the server object attributes. 14 – A utility detected an error converting to normalized file path format. 15 – A wrong key name is entered when accessing NT registry. 16 – S18N facility failed. 17 – A function returns success. 18 – Failed to access the NT registry. 19 – An unknown error is encountered when accessing NT registry. 20 – OID (Object Identification Database) initialization failed.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT C-11 WORKING WITH OBJECT DATABASES
C-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D. SNMP query support
When using SNMP for device status, PrintXchange queries the printer directly to obtain values for physical printer attributes such as: input-trays-supported input-trays-ready media-ready input-tray-medium output-bins-supported. PrintXchange also uses SNMP MIB data to update the printer and job status. PrintXchange supports the following MIBs: Fuji Xerox OPS MIB RFC 1759 Printer MIB.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-1 SNMP QUERY SUPPORT
The following table lists the mappings of supported MIB entries to PrintXchange attributes:
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
Printer printer-state idle y y
printing y y
needs-attention y y
needs-key-operator y y
paused y n
shutdown y n
unknown y y
timed-out y y
printer-problem- low paper n y message
no paper y y
no cassette y n
input tray fail y n
output tray fail y n
bad paper size y n
output tray full y n
cover open y y
jammed y y
low toner n y
no toner y y
used toner near full n n
used toner full n n
drum life near nn exhausted
drum life exhausted y n
no drum y n
duplex fail y n
D-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SNMP QUERY SUPPORT
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
service requested n y
offline n y
problem unknown nn reason
input-trays- 1yy supported
2yy
3yy
4yy
5ny
6ny
7ny
8ny
9ny
10 n y
manual y y
manual-2 n y
manual-3 n y
top n y
middle n y
bottom n y
main n y
side n y
large_capacity n y
envelope n y
input-trays-ready * same as input- yy trays-supported
media-ready na-letter-white y y
na-legal-white y y
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-3 SNMP QUERY SUPPORT
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
na-number-10- yy envelope
monarch-envelope y y
iso-a3-white y y
iso-a4-white y y
iso-a5-white y y
iso-c5-envelope y y
iso-designated-long- yy envelope
jis-b4-white y y
jis-b5-white y y
medium-a n y
medium-b n y
medium-c n y
medium-d n y
medium-e n y
ledger y y
folio y y
hagaki-white y y
medium-default y y
other media defined ny by DPA
input-tray-medium * defined by yy combination of input- trays-supported and media-ready
output-bins- face-up y n supported
face-down y n
center y n
side y y
D-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SNMP QUERY SUPPORT
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
mailbox-1 y n
mailbox-2 y n
mailbox-3 y n
mailbox-4 y n
mailbox-5 y n
mailbox-6 y n
mailbox-7 y n
mailbox-8 y n
mailbox-9 y n
mailbox-10 y n
stacker-1 n y
stacker-2 n y
stacker-3 n y
top n y
middle n y
bottom n y
left n y
right n y
large n y
private n y
1ny
2ny
3ny
4ny
5ny
6ny
7ny
8ny
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-5 SNMP QUERY SUPPORT
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
9ny
10 n y
11 n y
12 n y
13 n y
14 n y
15 n y
16 n y
17 n y
18 n y
19 n y
20 n y
21 n y
22 n y
23 n y
24 n y
25 n y
output-bins-ready * same as output- yy bins-supported
document-formats- Document formats yn supported that are supported on the output device
document-formats- Document formats yn ready that are ready on the output device
native-document- Document formats yn formats-ready that are ready to use on the output device itself
sys-up-date-and- an appropriate value yn time shall be given in generalizedTimeSynt ax
D-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SNMP QUERY SUPPORT
Table D-1. Attributes supported per MIB type MIB support
Object Class Attribute Name Attribute Value Fuji Xerox OPS MIB RFC 1759 Printer MIB
Job current-job-status completed y n
job-state-reasons successful- yn completion
complete-with- yn warning
abort-by-system y n
job-message-from- an appropriate nn administrator message shall be given.
pages-completed an appropriate value yn shall be given in cardinal syntax
total-job-octets an appropriate value nn shall be given.
media-sheets- an appropriate value yn completed shall be given in cardinal syntax.
Generic printer support
The PrintXchange MAM library provides the capability of getting the printer state from generic printers using the standard printer MIB (as defined by RFC 1759). However, the implementations of the MIB database and the agent behavior are slightly different depending on the printer. When making device status requests, the PrintXchange library obtains as many of the printer attributes listed in Table D-1 as it can get, compares them to the current values given by the supervisor back end, and returns only those attributes whose values changed. If the PrintXchange does not receive an answer to the device status request from a remote printer, the library reports the printer-state attribute with the timed-out value. The library keeps other attributes with the current status, except for printer-problem-message, which it removes. The PrintXchange library uses the following MIB objects to translate printer status information to Printxchange attributes: hrDeviceType hrDeviceStatus hrPrinterStatus hrPrinterDetectedErrorState
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-7 SNMP QUERY SUPPORT
prtInputType prtInputEntry prtInputDimUnit prtInputMediaDimFeedDirChosen prtInputMediaDimXFeedDirChosen prtInputStatus prtOutputStatus Note: The set of trays for input-trays-ready is determined by the MIB prtInoutStatus=0,2,4,6,8,10,12, or 14. MIB prtOutputStatus set to either of the same values also determines the set of trays for output- bins-ready. printer-state The PrintXchange library uses hrDeviceStatus, hrPrinterStatus, and hrPrinterDetectedErrorState to determine the value of the printer- state attribute as shown in Table D-2.
Table D-2. Printer state translation
hrDeviceStatus hrPrinterStatus hrPrinterDetectedErrorState printer-state
RUNNING PRINTING don't care printing
RUNNING except PRINTING don't care idle
WARNING don't care offline idle
WARNING don't care except offline needs-attention
DOWN WARMUP don't care idle
DOWN except WARMUP noToner or serviceRequested needs-key- operator
DOWN except WARMUP except noToner and needs-attention serviceRequested
TESTING don't care don't care idle
UNKNOWN(other) don't care don't care unknown
* When the prnter does not timed-out answer SNMP requests, the PrintXchange library changes printer-state to timed-out.
printer-problem-message The PrintXchange library uses the MIB object hrPrinterDetectedErrorState to determine the value of the printer- problem-message attribute. The hrPrinterDetectedErrorState object is an octetString, with each bit representing an individual problem. The library determines one or more values for printer-problem- message based on the bit settings. The possible printer-problem- message values are one or more of the followiing (the attribute is multi-valued): cover open jammed low paper low toner
D-8 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SNMP QUERY SUPPORT
no paper no toner offline service requested input-trays-supported/input-trays-ready The PrintXchange library uses prtInputEntry, prtInputType, and prtInputStatus to determine the value of the input-trays-supported and input-trays-ready attributes. Depending on the sequence order of prtInputEntry and prtInputType entries present in the MIB table, the PrintXchange library determines the value of the input-trays-supported attribute as shown in Table D-3.
Table D-3. Input tray translation
Sequential entry in MIB Table input-trays-supported value
prtInputEntry (auto type input tray)
1st 1
2nd 2
3rd 3
4th 4
5th 5
6th 6
7th 7
8th 8
9th 9
10th 10
prtInputType (value sheetFeedManual(5); manual type input tray)
1st manual
2nd manual-2
3rd manual3
Example: MIB Input Tray Entry input-trays-supported value
1st: auto type input tray 1 2nd: auto type input tray 2 3rd: manual type input tray manual 4th: auto type input tray 3 5th: manual type input tray manual-2 6th: auto type input tray 4
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-9 SNMP QUERY SUPPORT
7th: manual type input tray manual-3 8th: manual type input tray* 5* 9th: auto type input tray 6
Note: The 8th entry in the example is a fourth entry for a manual type input tray. In this case (and for any subsequent manual input tray entries), the PrintXchange library sets the next available input tray value between 1 and 10. prtInputStatus is a member of prtInputEntry that represents the status of an input tray. Each prtInputStatus entry corresponds to an individual input tray as represented by prtInputEntry. Depending on the value of prtInputStatus for each input tray, the PrintXchange library sets the input-trays-ready attribute value. The following prtInputStatus values indicate the setting of the input-trays-ready attribute: 0 Available and idle 2 Available and standby 4 Available and active 6 Available and busy 8 Available and idle with non-critical alerts 10 Available and standby with non-critical alerts 12 Available and active with non-critical alerts 14 Available and busy with non-critical alerts media-ready The PrintXchange library uses the following MIB objects to determine the value of the media-ready attribute: prtInputDimUnit prtInputMediaDimFeedDirChosen prtInputMediaDimXFeedDirChosen prtInputStatus The four objects are members of prtInputEntry. Note that the value of fxIOTInputTrayMedium represents the name of the medium installed in the input tray. The PrintXchange library compares the value of prtInputDimUnit, prtInputMediaDimFeedDirChosen, and prtInputMediaDimXFeedDirChosen with the size of the Printxchange- supported media. The library then adds any matching values to the media-ready attribute depending on the value of prtInputStatus. If the value of prtInputStatus shows “available”, then the library adds the medium value to the media-ready attribute. If the library finds no matches, it adds the medium-default to the media-ready attribute if it is available. input-trays-medium The library sets the value of input-trays-medium with any of the media that it identifies as described above for media-ready. output-bins-supported/output-bins-ready The PrintXchange library uses prtOutputEntry and prtOutputStatus to determine the value of the output-bins-supported and output-bins- ready attributes. Depending on the sequence order of prtOutputEntry entries present in the MIB table, the PrintXchange library determines the value of the output-bins-supported attribute.
D-10 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT SNMP QUERY SUPPORT
The prtOutputEntry is mapped to output-bins-supported value 1, second entry is mapped to value 2 and so on.
Table D-4. Output bin translation
prtOutputEntry in MIB Table output-bins-supported value
1st 1
2nd 2
3rd 3
4th 4
5th 5
6th 6
7th 7
8th 8
9th 9
10th 10
11th 11
12th 12
13th 13
14th 14
15th 15
16th 16
17th 17
18th 18
19th 19
20th 20
21th 21
22th 22
23th 23
24th 24
25th 25
prtOutputStatus is a member of prtOutputEntry that represents the status of an output bin. Each prtOutputStatus entry corresponds to an individual output bin as represented by prtOutputEntry. Depending on the value of prtOutputStatus for each output bin, the PrintXchange library sets the output-bins- ready attribute value. The following prtOutputStatus values indicate the setting of the output-bins-ready attribute:
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT D-11 SNMP QUERY SUPPORT
Available and idle Available and standby Available and active Available and busy Available and idle with non-critical alerts Available and standby with non-critical alerts Available and active with non-critical alerts Available and busy with non-critical alerts Parse trap Trap data generated by a generic printer does not include the information to be able to be translated into Printxchange attribute values. Therefore the MIB attribue mapping parse trap is almost same thing as for the device status. The PrintXchange library expects to be given the current printer attributes of the designated printer. In the parse trap, the library compares the given attributes with the attributes obtained by the device status. The PrintXchange library creates event report information from the result of device status and returns the information to the supervisor back end.
D-12 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT Glossary of terms and abbreviations
This glossary includes standard definitions of terms and abbreviations commonly used in the PrintXchange environment and in this document.
Terms and abbreviations
ACL access control list. List of entities (such as users, operators, administrators, and servers) used to determine whether a certain entity has authorization to perform some operation or function.
Administrator A class of user that is enforced by security. An administrator sets policy and can create, modify, and delete persistent print system objects, such as printers and servers. This term is synonymous with System Administrator. See also Operator and End User.
API application program interface
Attribute A property or characteristic of an object. An information item, consisting of a type designation and one or more values, associated with a specific object.
Authentication The process of identifying and verifying the user making a request by checking and validating the user’s credentials.
Authorization The process whereby an access policy determines whether an entity (authenticated or unauthenticated) may perform a particular operation.
BDC backup domain controller
BSD Berkeley software distribution
CDE Common Desktop Environment
CLI command line interface
Client In a PrintXchange client-server environment, a software agent with which an end-user can submit print requests or management requests.
DCE Distributed Computing Environment
DPA document printing application
DPA protocol A method of communication used in the exchange between client and server as specified in the ISO DPA standard.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GLOSSARY-1 GLOSSARY OF TERMS AND ABBREVIATIONS
DSC Document Structuring Conventions
EBCDIC extended binary coded decimal interchange code
Fan in Several logical printers feeding one queue, creating a “fan-in” configuration.
Fan out Each queue can schedule jobs to more than one physical printer, creating a “fan-out” configuration.
FIFO first in first out
FTP File Transfer Protocol
GUI graphical user interface
I/O input/output
ISO DPA A standard for document printing as defined in International Standards Organization’s Document Printing Application Standard 10175.
LAN local area network
locale An explicit model and definition of a native-language environment. A program’s locale defines its codesets, date and time formatting conventions, monetary conventions, decimal formatting conventions, and collation order.
localization The process of adapting software for specific languages or regions. Localization involves providing the necessary translations, format definitions, tables, and other data to prepare an internationalized product for local requirements.
logical printer A named object of class printer that is used to group one or more physical printer objects for load balancing and/or to specify alternative default attributes to those specified by the physical printer object.
LPD line printing daemon
LPD Protocol Line printer daemon protocol for printing systems used by the Berkeley versions of the UNIX operating system. It is described in RFC 1179.
LPR line printer
MAPI messaging application program interface
MSMAIL Microsoft mailing system
MSRPC Microsoft Word remote procedure call. The communication protocol with a Windows NT PrintXchange spooler.
Multinationalization The process of both developing a product so that it can be readily customized for different markets (internationalization) and taking the product and creating an instance for a specific target market (nationalization).
GLOSSARY-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GLOSSARY OF TERMS AND ABBREVIATIONS
Name service A set of capabilities provided throughout a network environment by servers, which allows client applications access to names of user- defined and system-defined objects.
NIS network information service
NLS national language support
Notification Result and error reporting by a server to the client that had requested its services. Generally, the mechanisms needed to implement notification are provided by the system infrastructure. In most system environments, electronic mail can be used as a crude means for notification.
NPS network printing system
NT new technology
Object A collection of attributes that are used to inform about or describe a named physical or logical entity. In the PrintXchange distributed print system, objects adhere to the ISO DPA standard
OID object identifier
ONC Open Network Computing
ONC+ Open Network Computing Plus
Operator A class of user, defined by POSIX and X/OPEN, enforced by security. An operator can perform day-to-day operations, such as pausing and resuming jobs and printers, disabling and enabling printers.
OS operating system
OSF Open Software Foundation
Output device A printer. A physical device or hardware that is capable of rendering images or documents. A marking engine. Synonym: physical device.
PCL printer control language
PDC primary domain controller
PDL page description language
Physical device Synonym: output device. See output device.
Physical printer An ISO DPA and POSIX software object of class printer. A named printer object that represents an output device such as laser printing hardware or a rendering system. May also mean both physical printer and output device together.
PJL Print Job Language
POSIX The IEEE standards body that is chartered with standardizing portable operating system interfaces for UNIX. In this document, POSIX refers to the operating system interface standard for printing.
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GLOSSARY-3 GLOSSARY OF TERMS AND ABBREVIATIONS
PSIS Printing System Interoperability Specification
PXC PrintXchange
Queue A spooler object that partitions logical and physical printers. A given printer may only exist in a single queue, thus queues partition printers into disjoint sets. The default PrintXchange spooler configuration is a single queue. Within a queue, a logical printer may be associated with one or more of the physical printers of the queue. The default association is to all of the physical printers.
Additionally, queues impose an ordering on the jobs submitted to the logical printers of the queue. This imposed ordering is known as selection order. The algorithm for this ordering is configurable (FIFO, shortest job first, etc.).
RPC remote procedure call
SCM service control Manager
Security service A service provided throughout a network environment by servers, which is used to control client access to other network services. Access is granted by a two-stage process. The stages are authentication and authorization. Authentication guarantees the identity of the client, and authorization ensures that a client has permission to access a service.
Server A software component that manages printing facilities on behalf of a client or clients on the same computer or over a network. For PrintXchange, the term is generally used to refer to the print server that is either the spooler or the supervisor, but not both. Specifically, the spooler is a print server to the various API, CLI, and GUI clients that access it directly. However, the spooler is also a client of the supervisor for which the supervisor is a print server to the spooler
SMTP simple mail transfer protocol
SNMP simple network management protocol. A simple protocol by which management information for a network element may be inspected or altered by logically remote users (RFC 1157).
SPL spooler
Spooler An ISO DPA and POSIX object of class server. A specialization of a server object. A named server that accepts PrintXchange operations from print clients and schedules print jobs on appropriate printer supervisors. The typical spooler is multi- threaded and is capable of processing multiple print operations concurrently.
GLOSSARY-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GLOSSARY OF TERMS AND ABBREVIATIONS
Supervisor An ISO DPA and POSIX object of class server. A specialization of a server object. A static process or software to drive a specific printer for the printing of print jobs. A supervisor is entirely responsible for interpreting the job request. This includes interpreting the content of the file(s) and reconciling the instructions provided in the print request parameters with the contents of the file. The supervisor has complete control over the printing of the job, including the loading of fonts, forms, and other electronic resources into the printer, as well as transferring the file(s) to the printer.
TCP/IP transmission control protocol/Internet protocol
UID user identifier
UNC universal name convention
User A class of user, defined by POSIX, that is enforced by security. A user (unprivileged) that submits print jobs and gets status.
VM virtual memory
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT GLOSSARY-5 GLOSSARY OF TERMS AND ABBREVIATIONS
GLOSSARY-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT Index
Solaris Server, 6-1 User, 7-1 A Windows NT Server, 6-1 Access Control Lists, 8-17 character sets, 2-25 access-control-list, C-2 clean, 2-13 accounting cleaning attributes, 19-4 objects, 14-33 enabling, 19-2 spooler, 14-33 profile, 19-3 spoolers, 14-34 report writer, 19-5 CLI, 2-5, 2-17, 12-1 accounting-profile, 19-3 command options, 12-5 ACLs, 8-17 modification operators, 15-2 default values, 8-20 syntax, 12-4 defining, 8-17 client interfaces, 2-5, 2-16 without privilege specification, 8-20 clients, 2-1, 2-27 administration application, 12-8 installing, 5-2 administrator operations, 2-13 codeset converter DLL interface, 2-27 application command line interface, 2-5, 2-17 administration, 12-8 Command Line Interface, 12-1 event monitor, 12-8 command options, 12-5 print job submission and job control, 12-7 components, 2-1 printer information, 12-7 concepts, 2-1 associated-queue, 15-19 configuration attributes, 2-11, 2-12 process, 4-1 allowed, 15-3 Console mode, 10-2 document, 15-10 content-orientations-supported, 15-28 initial-value-document, 15-13 conventions, 1-1 initial-value-job, 15-12 copies, 21-1 job, 15-9 crash recovery, 22-150 listing, 13-6, 14-31 accounting, 22-156 logical printer, 15-5 client, 22-156 mapping, 15-19 database, 22-151 physical printer, 15-5 document, 22-152 pre-processor-related, 10-6 job, 22-152 print data processing, 15-25 job state reasons, 22-154 queue, 15-8 LAN Manager inbound gateway, 22-156 server, 15-4 notification, 22-156 substitution, 10-9 operations, 22-157 xxx-ready, setting, 15-22 server startup, 22-150 xxx-supported, setting, 15-22 Xerox supervisor, 22-155 authentication, 8-10 create, 2-13 cross-domain features, 8-10 cross-platform printing authorization, 8-15 setting up, 6-31, 6-39, 7-9 current-job-state, 14-5, 14-7, 14-9, 14-22 B D balancing load, 11-9 data sheet, A-1 database utilities C exit status, 22-149 default job priorities cancel job, 2-13 modifying, 14-22 canceling jobs, 14-25 default transfer method, 8-25 CD contents default-character-set, 15-26 Administrator, 7-1
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INDEX-1 INDEX default-font, 15-27 event monitor application, 12-8 default-job-completion-period, 14-24, 14-27 event notification, 9-1 defining ACLs, 8-17 events, 9-1 delete, 2-13 excluded-preprocessors, 10-8 deleting exit status document defaults, 14-21 database utilities, 22-149 initial-value-document, 18-9 server, 22-147 initial-value-job, 18-9 exit status codes, B-5 job defaults, 14-21 jobs, 14-24 logical printers, 6-56, 7-13, 18-8 F physical printer, 18-6 features and benefits, 2-3 PrintXchange data files printers, 6-56 file security, 8-25 PrintXchange objects, 18-1 file transfer, 8-23 queues, 18-5 file-reference transfer method, 8-25 spoolers, 18-3 filters, 10-15 supervisors, 18-4 attribute handling, 10-15 delivery methods, 9-12 data handling, 10-15 electronic mail, 9-12 error handling, 10-16 message, 9-12 restriction, 10-16 descriptor, 11-2 terminate handling, 10-16 determining components, 5-1 text-to-PostScript translation, 10-17 guidelines, 5-2 finishing, 21-6 determining the objects, 5-5 device status query, 2-8 disable, 2-13 G disabling generic printer, support, D-7 logical printers, 17-9 graphical user interface, 12-7 physical printers, 17-7 GUI, 2-5, 12-7 PrintXchange objects, 17-2 window description, 12-11 queues, 17-5 spoolers, 17-4 supervisors, 17-4 H discarding jobs, 14-27 document defaults hardware requirements, 3-2 deleting, 14-21 highlight color, 21-2 document formats, 15-25 highlight-colour, 21-2 documentation, 1-2 highlight-colour-mismatch-action, 21-2 documents highlight-colour-rendering-algorithm, 21-2 attributes, 15-10 highlight-colour-rendering-algorithms-supported, 21-2 creating defaults, 11-10 highlight-colours-ready, 21-2 listing names and attributes, 14-31 highlight-colours-supported, 21-2 modifying attributes, 14-14 highlight-mapping-colour, 21-2 printing, 14-2 highlight-mapping-colours-supported, 21-2 document-sheets, 21-5, 21-7 holding jobs, 14-7 DocuPrint NPS print server, 2-8 DocuSP print server, 2-8 I ignore-preprocessing-failure, 10-9 E imaging parameters, 15-26 e-mail notification inbound gateway clients, 2-7 restrictions, 22-24 inbound gateways, 20-2 setting up, 6-4 administration and configuration, 20-3 enable, 2-13 LAN Manager, 20-10 enabling LPR, 20-30 logical printers, 17-8 modifying configuration, 20-7 physical printers, 17-6 names, 20-3 PrintXchange objects, 17-2 QServer, 20-16 queues, 17-5 security, 20-7 spoolers, 17-3 startup and shutdown, 20-5 supervisors, 17-3 infrastructure, 2-15, 2-27 end user privileges, 5-6, 5-7 initial-value-document environment variables, 2-26, 12-2 attributes, 15-13 error messages deleting, 18-9 error code prefixes, 22-26 initial-value-job reference supervisor, 22-144 attributes, 15-12
INDEX-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INDEX
deleting, 18-9 port, 20-14 input trays, 21-6 print job submission, 20-15 input-trays-medium, 21-6 startup and stop, 20-14 input-trays-ready, 21-6 LAN Manager inbound gateway input-trays-supported, 21-6 set up, 20-12 installing list job queue, 2-13 SNMP, 6-32 list object attributes, 2-13 installing PrintXchange listing a job queue, 14-29 client, 7-2 listing names and attributes, 14-31 determining components, on a client, 7-3 listing the job queue, 13-7 determining components, on a server, 6-16 load balancing, 11-9 name service, manually, 8-2 log files, 2-27 on a client, 7-2 logical printers, 2-9 on a Windows NT Server, 6-2 attributes, 15-5 on Windows NT server, 6-3 creating, 11-11 post-installation, 7-11 creating and configuring, 11-10 setting up name service, 6-21, 7-8 deleting, 6-56, 7-13, 18-8 installing Windows NT gateways, 6-33 disabling, 17-9 international considerations, 2-24 enabling, 11-18, 17-8 supported attributes, 11-12 lpq, 2-8 J lpr, 2-8 job cancellation, 2-8 LPR, 20-30 job defaults administration and configuration, 20-31 deleting, 14-21 basic operation, 20-34 job diagnostics, 22-5 cross domain/cross platform support, 20-33 job priorities inbound gateway, install, 20-31 modifying, 14-22 install, 20-31 job queue internationalization, 20-35 listing, 13-7, 14-29 restrictions, 20-35 Job resume, 14-10, 14-11 translations, 20-35 job status query, 2-8 lprm, 2-8 job submission, 2-8 job-copies, 21-1 M job-copies-supported, 21-1 job-count, 21-1 Management Information Base types, 15-14 job-discard-time, 14-27 MAPI profile, 9-8 job-hold, 14-7 mapping attributes job-print-after-specified, 14-5 setting, 15-19 job-retention-period, 14-24, 14-25, 14-27 media, 21-6 jobs message, 11-2 attributes, 15-9 message catalog files, 2-26 canceling, 14-25 MIB types, 15-14 creating defaults, 11-10 modification and translation filters, 10-15 deleting, 14-24 modify, 2-13 discarding, 14-27 modifying document attributes, 14-14 holding and releasing, 14-7 modifying job attributes, 14-14 listing names and attributes, 14-31 multinational considerations, 2-24 modifying attributes, 14-14 clients, 2-27 pausing and resuming, 14-9 codeset converter DLL interface, 2-27 printing, 14-2 environmen variables, 2-26 printing, after a specified time, 14-5 infrastructure, 2-27 promoting, 14-22 internationalization requirements, 2-24 resubmitting, 14-18 log files, 2-27 retaining, 14-11 message catalog files, 2-26 setting priorities, 14-16 servers, 2-27 job-sheets, 21-4 supported character sets, 2-25 job-state-reasons, 14-5 job-submission-complete, 14-18 N L Name Services, 8-1 manual installation, 8-2 LAN Manager, 20-10 names of jobs and documents, 14-31 administration and configuration, 20-13 NetWare client basic operation, 20-13 optional features, 20-29 internalization, 20-15 NetWare gateway
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INDEX-3 INDEX
setting up, 6-37 pdaccount utility, 19-1, 19-5 setting up, 6-29 pdaddoid utility, 15-31 NetWare queue pdclean, 14-34, 18-3, 18-5 set up, 20-17 pdcreate, 11-8, 11-11 NetWare queue inbound gateway pddelete, 14-21, 14-24, 14-25, 18-3, 18-4, 18-5, 18-7, set up, 20-17 18-8, 18-9 network requirements, 3-2 pddiag operation, 22-5 no-preprocessing, 10-8 pddiagjob utility, 22-7 notification profiles pddisable, 14-34, 17-4, 17-7, 17-9, 18-3, 18-4, 18-5, 18-7, specifying, 9-8 18-8 notification server, 9-8 pdenable, 11-16, 14-34, 17-3, 17-7, 17-8 notification server logging events, 22-23 PDL guesser, 10-5, 10-20 notification-profile, 9-1, 9-9, 11-2 pdls, 14-32 number-up, 15-28 pdmod, 14-6, 14-17, 14-28 pdmoddb utility, C-2 pdpr, 14-3, 14-6, 14-28 O pdq, 14-29 -O source OID path switch, B-4 pdresume, 14-10, 14-11 object attributes pdrm, 14-24 listing, 13-6 pdset, 9-9, 11-9, 14-6, 14-17, 14-22, 14-28, 19-2 object database pdshowdb utility, C-4 displaying, C-4 pdshowoid utility, 15-32 managing, C-1 physical printers, 2-9 modifying, C-2 attributes, 15-5 object database utilities creating, 11-8 exit status codes, C-11 deleting, 18-6 object states, 22-2 disabling, 17-7 object status, 13-1 enabling, 11-17, 17-6 objects, 2-11 load balancing, 11-9 cleaning, 14-33 pausing, 16-7 ODB utility command line switches, C-5 resuming, 16-8 OID database setting attributes for Reference Supervisor, 11-3 pdaddoid utility, 15-31 setting attributes for Xerox supervisor, 11-7 updating, 15-30 setting channel ready, 11-8 operation setting optional attributes, 11-9 cancel job, 2-13 setting printer address, 11-4, 11-7 clean, 2-13 setting printer-connection-method, 11-5 create, 2-13 setting serial parameter attributes, 11-6 delete, 2-13 physical-printers-requested, 21-1 disable, 2-13 physical-printers-supported, 15-19, 21-1 enable, 2-13 plex, 15-27 list job queue, 2-13 preprocessor-definition, 10-6 list object attributes, 2-13 preprocessor-list, 10-8 modify, 2-13 preprocessor-related attributes, 10-6 pause, 2-14 preprocessors, 10-5 print, 2-14 executing, 10-14 promote, 2-14 print, 2-14 resubmit, 2-14 print job submission and job control application, 12-7 resume, 2-14 printer data sheet, A-1 set attributes, 2-14 printer data sheets, A-5 shutdown, 2-14 printer information application, 12-7 operator operations, 2-13 printer-address, 11-4, 11-7 output bins, 21-6 printer-associated-printers, 15-19 output devices, 2-2 printer-baud-rate, 11-6 supported, A-1 printer-connection-method, 11-5 printer-initial-value-document, 14-21 printer-initial-value-job, 14-21 P printer-name-requested, 14-3 printers, 2-2 paf-job-separator-format, 21-3 printer-tcpic-port-number, 11-4 pause, 2-14 printing pausing documents, 14-2 physical printers, 16-7 jobs, 14-2 queues, 16-5 printing jobs after a specified time, 14-5 spoolers, 16-3 printing system pausing jobs, 14-9 clients, 2-1 pausing PrintXchange objects, 16-2
INDEX-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INDEX
components, 2-1, 2-15 resuming, 16-6 output devices, 2-2 setting attributes, 11-2 printers, 2-2 servers, 2-2 Printxchange R determining end user privileges, 5-7 reference supervisor, 2-8, 5-3 PrintXchange error messages, 22-144 attributes, 2-12 releasing jobs, 14-7, 14-9 client interfaces, 2-5, 2-16 relocating PrintXchange name service, 8-8 determining components, 5-1, 5-2 removing from server or queue determining end user privileges, 5-6 jobs, 14-33 determining the objects, 5-5 requirements enabling, 11-16 hardware, 3-2 infrastructure, 2-15 network, 3-2 installation on a client, 7-2 software, 3-1 installation on a client, overview, 7-2 system, 3-1 installation on a Windows NT server, overview, 6-2 reset-printer, 21-7 installation on Windows NT server, 6-3 restrictions installation validation, 6-41 e-mail notification, 22-24 logical printers, 2-9 resubmit, 2-14 objects, 2-11 resubmitting jobs, 14-18 physical printers, 2-9 resume, 2-14 queues, 2-9 resuming servers, 2-7, 2-18 physical printers, 16-8 setting up, 6-45, 7-11 PrintXchange objects, 16-2 spoolers, 2-19 queues, 16-6 supervisors, 2-19 spoolers, 16-4 system requirements, 3-1 RFC 1179 protocol, 2-8 testing, 11-16, 11-18 uninstalling from a client, 7-13 uninstalling from a server, 6-56 S PrintXchange data files security, 8-10 deleting, 6-56 separator pages, 21-3 PrintXchange name service, 8-2 server manual installation, 8-2 exit status, 22-147 properties, setup, 8-9 logging events, 22-16 relocating, 8-8 spooler, 2-7 setting up, 6-21, 7-8 startup command switches, B-2 PrintXchange objects startup commands, B-1 disabling, 17-2 startup exit status codes, B-5 enabling, 17-2 supervisor, 2-7 pausing, 16-2 server attributes removing (deleting), 18-1 setting, 10-4 resuming, 16-2 server exit codes, 10-2 priorities, 14-16 server object database promote, 2-14 creating and initializing, 10-1 promoting jobs, 14-22 server shutdown, 10-4 publications, 1-2 server startup process, 10-2 servers, 2-2, 2-7, 2-18, 2-27 Q attributes, 15-4 creating and configuring, 10-1 QServer, 20-16 server-type, C-1 administration/configuration, 20-19 service log facility, 22-10 authentication and access control, 20-27 set attributes, 2-14 basic operation, 20-22 setting job priorities, 14-16 cancel operation, 20-25 setting mapping attributes, 15-19 job recovery operation, 20-25 setting server attributes, 10-4 print job submission, 20-24 setting up e-mail notification, 6-4 startup and shutdown, 20-23 setting up PrintXchange, 6-45, 7-11 queues, 2-9 Setup PrintXchange tool, client, 7-11 attributes, 15-8 Setup PrintXchange tool, server, 6-45 creating, 11-1 setting up PrintXchange on a client deleting, 18-5 overview, 7-2 disabling, 17-5 setting up PrintXchange on a server enabling, 11-17, 17-5 overview, 6-2 pausing, 16-5 Setup PrintXchange tool, client, 7-11
PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT INDEX-5 INDEX
Setup PrintXchange tool, server, 6-45 thickening-specification, 21-2 shutdown, 2-14 thickening-supported, 21-2 sides, 15-27 transfer methods, 8-24 SNMP troubleshooting query support, D-1 error messages, 22-26 SNMP, 6-32 job diagnostics, 22-5 socket transfer method, 8-24 notification server logging events, 22-23 software requirements, 3-1 pddiag operation, 22-5 Solaris Server package, 6-33 server logging events, 22-16 spooler, 2-7 service log facility, 22-10 cleaning, 14-33 standard system logging, 22-14 spooler-preprocessor-list, 10-8 system logging, 22-10 spoolers, 2-19 UNIX files, 22-9 cleaning, 14-34 utility diagnostics, 22-7 deleting, 18-3 disabling, 17-4 enabling, 11-17, 17-3 U pausing, 16-3 understanding object states, 13-2 resuming, 16-4 uninstalling PrintXchange setting up, 6-22 from a client, 7-13 Spooler-to-supervisor file transfer method, 8-25 from a server, 6-56 standard system logging, 22-14 starting the server, 10-1 startup command switches, B-2 V startup commands, B-1 validating PrintXchange installation, 6-41 status query, 2-8 supervisor, 2-7 reference, 2-8, 5-3 W Xerox, 2-8, 5-3 supervisor-preprocessor-list, 10-8 Windows NT gateways supervisors, 2-19 installing, 6-33 deleting, 18-4 with-request transfer method, 8-24 disabling, 17-4 enabling, 11-17, 17-3 X Reference, setting up, 6-25 setting up, 6-22 Xerox supervisor, 2-8, 5-3, 17-6 Xerox, setting up, 6-27 x-image-shift, 15-29 support, generic printer, D-7 XPPQ, 2-8 system requirements, 3-1 Y T y-image-shift, 15-29 terminology, 2-1
INDEX-6 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR WINDOWS NT