system administration and operations guide for unix of contents iv printxchange system...

Version 1.2Pub# 613P07240July 1998

System Administration and OperationsGuide for Unix

Xerox Corporation701 South Aviation BoulevardEl Segundo, CA 90245

Publication #613P07240

� Copyright 1997-1998 Xerox Corporation. All rights reserved.Portions of this software also include copywritten software modulesfrom Sun Microsystems, Digital Equipment Corporation, and RaimaCorporation.

Copyright protection claimed includes all forms and matters ofcopyrightable material and information now allowed by statutory orjudicial law or hereinafter granted, including without limitation,material generated from the software programs which are displayedon the screen, such as icons, screen displays, looks, etc.

Xerox, The Document Company, the stylized X, and all Xeroxproduct names mentioned in this publication are trademarks of XeroxCorporation. Sun, SPARCstation, NIS, NIS+, OpenWindows, andSolaris are registered trademarks of Sun Microsystems, Inc.Microsoft, Windows NT, Windows 95, and LAN Manager areregistered trademarks of Microsoft Corporation. IBM is a registeredtrademark of International Business Machines Corporation. Digital isa registered trademark of Digital Equipment Corporation. Apple andMacintosh are registered trademarks of Adobe SystemsIncorporated. NetWare is a registered trademark of Novell,Incorporated. Common Desktop Environment is a copyright of theCommon Operating System Environment. Other product namesused herein are trademarks of their respective owners.

Changes are periodically made to this document. Changes, technicalinaccuracies, and typographic errors will be corrected in subsequenteditions. Printed in the United States of America.

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX iii

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-16

Interoperability 2-23

Multinational considerations 2-24

3. Determining the system requirements 3-1

Software requirements 3-1

Network requirements 3-1

Hardware requirements 3-2

4. Recommended configuration planning 4-1

Determining your network printing system requirements 4-1

Installation process 4-2

Creating and configuring queues, physical printers, and logical printers 4-2

Enabling queues, physical printers, logical printers, and inbound gateways 4-2

Validating your installation and configuration 4-3

Configuration roadmap 4-3

5. Planning a PrintXchange installation 5-1

Planning printers and queue associations 5-1

Planning security 5-4

Planning naming services 5-5

Planning the component software installation 5-11

TABLE OF CONTENTS

iv PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

6. Installing and setting up PrintXchange on a server machine 6-1

Overview of the installation sequence 6-1

Solaris packages description 6-2

PrintXchange package description 6-3

PrintXchange Installation sequence 6-5

Required installation of Solaris operating system packages 6-6

PrintXchange Solaris installation/removal 6-7

7. Managing security 7-1

Name Services 7-1

Security 7-2

Access Control Lists (ACLs) 7-5

File transfer 7-13

8. Setting event notification 8-1

Event notification 8-1

9. Configuring, starting and stopping servers 9-1

Process/configuration flow 9-2

Configuration information summary sheet 9-3

Creating, starting, and enabling servers 9-4

Shutting down and restarting a server 9-6

10. Creating and configuring queues, physical printers and logical printers 10-1

General information on objects (queues, physical printers, logical printers) 10-1

Creating and enabling a queue 10-3

Creating and enabling a physical printer 10-4

Creating and enabling a logical printer 10-7

Other optional CLI operations 10-9

Defining Access Control List (ACL) 10-10

Defining event-notification profiles 10-12

Defining text-to-PostScript translation filter 10-13

11. Using the CLI and GUI 11-1

Command Line Interface (CLI) 11-2

CLI syntax 11-3

Summary of command options 11-4

TABLE OF CONTENTS

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX v

Graphical User Interface (GUI) 11-6

12. Getting status of PrintXchange objects 12-1

Understanding object states 12-1

Listing object attributes 12-5

13. Managing jobs and documents 13-1

Printing jobs and documents 13-2

Printing a job after a specified time 13-5

Holding and releasing jobs 13-7

Pausing and resuming jobs 13-9

Retaining jobs 13-13

Modifying job and document attributes 13-15

Setting job priorities 13-18

Resubmitting jobs to a logical printer 13-20

Deleting job and document defaults 13-22

Modifying default job priorities 13-23

Promoting jobs 13-24

Deleting jobs 13-25

Canceling jobs 13-26

Discarding jobs with print deadlines 13-28

Listing a job queue 13-29

Listing names and attributes of jobs and documents 13-33

Removing all jobs from a server or queue – Cleaning objects 13-34

14. Setting and modifying object attributes 14-1

CLI modification operators 14-2

Allowed attributes for set and modify 14-3

Setting mapping attributes 14-23

Setting xxx-supported and xxx-ready attributes 14-26

Updating the OID database 14-34

15. Pausing and resuming objects 15-1

Pausing and resuming PrintXchange objects 15-2

Pausing spoolers 15-4

Resuming spoolers 15-4

Pausing queues 15-5

TABLE OF CONTENTS

vi PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

Resuming queues 15-5

Pausing physical printers 15-6

Resuming physical printers 15-7

16. Enabling and disabling objects 16-1

Enabling and disabling PrintXchange objects 16-2

Enabling spoolers and supervisors 16-5

Disabling spoolers and supervisors 16-6

Enabling queues 16-7

Disabling queues 16-7

Enabling physical printers 16-8

Disabling physical printers 16-9

Enabling logical printers 16-10

Disabling logical printers 16-11

17. Removing (deleting) objects 17-1

Removing (deleting) PrintXchange objects 17-1

Deleting spoolers 17-3

Deleting a supervisor 17-5

Deleting a queue 17-6

Deleting a physical printer 17-7

Deleting a logical printer 17-9

Deleting an initial-value-job 17-10

Deleting an initial-value-document 17-10

18. Generating accounting reports 18-1

Enabling accounting 18-2

Accounting profile 18-3

Using the accounting report writer 18-4

19. Inbound gateways 19-1

LPR inbound gateway 19-1

20. Managing printed output 20-1

Requesting a specific output device 20-1

Specifying number of copies 20-1

Specifying highlight color 20-2

Specifying separator pages 20-3

TABLE OF CONTENTS

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX vii

Specifying media, input trays, and output bins 20-6

Specifying finishing 20-7

Resetting the printer 20-7

21. Troubleshooting 21-1

Troubleshooting introduction 21-1

System logging 21-10

Restrictions for e-mail notification on Windows NT 21-24

Message descriptions 21-26

Crash recovery 21-150

Appendices

A. Printers data sheets A-1

B. Server startup commands, switches and exit status codes B-1

C. Working with object databases C-1

D. Printers.conf file D-1

E. SNMP query support E-1

Glossary of terms and abbreviations

Index

TABLE OF CONTENTS

viii PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX 1-1

1. About this guide

The PrintXchange System Administration and Operations Guide forUNIX 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 listof additional PrintXchange documentation.

Audience

The intended audience for the guide includes::

� System administrators, responsible for managing the printingsystem 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 addressall users.

“User” refers in general to system administrators, operators, and endusers alike, and is used whenever the topic deals with generalPrintXchange functions, such as “end user.”

“End user” refers to any person other than the system administratoror operator, and is used whenever the topic deals with a particularsystem 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 enables 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 CLIcommands, are written in courier new font. Example:

pdenable –h

ABOUT THIS GUIDE

1-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

Related publications

In addition to this guide, the following PrintXchange publications areavailable:

� PrintXchange System Administration and Operations Guide forWindows NT

This guide explains installation and day-to-day management ofthe PrintXchange system in the Windows NT environment. It isprimarily intended for administrator and operator use.

� PrintXchange Command Line Interface Reference Guide

This guide provides information on maintaining and operating thePrintXchange system using the Command Line Interface (CLI). Itis primarily intended for system administrator use and access toadvanced printing functions.

� PrintXchange Command Line Interface User Guide for WindowsNT

This guide provides information on submitting jobs to your printerusing the command line on your workstation. It is available toCLI users in the Windows NT environment.

� PrintXchange Command Line Interface User Guide for UNIX

This guide provides information on submitting jobs to your printerusing the command line on your workstation. It is available toCLI users in the UNIX environment.

� PrintXchange Windows NT Help

These are on-line help files that provide information onPrintXchange functionality. It is available to Windows NT users.

� PrintXchange UNIX CDE Help

These are on-line help files that provide information onPrintXchange functionality. It is available to UNIX users.

� PrintXchange UNIX MAN pages

This is a quick reference for information on PrintXchangecommands. They are available to all UNIX users.


2. PrintXchange overview

PrintXchange is an enterprise print system that gives systemadministrators and operators a set of tools for job submission andprint system management. It enables end users to print documentsand monitor their print jobs on their operating system platform.

Concepts and terminology

This section defines the basic concepts and terminology that youneed to understand to properly manage and run the PrintXchangesystem.

Note : The terms and concepts defined in this section are presentedin a progressive manner, beginning with a description of a basicPrintXchange printing system and continuing with a description ofeach system component.

The basic printing system

The basic printing system uses a client/server architecture thatconsists of three primary components (client, server, and outputdevice) as illustrated below.

Figure 2-1. Basic printing system

Client

The client initiates print and system administration operations. Itserves as the user’s agent to convey print and management requeststo the server.

Print requests are requests to print files on an output device. Printdata consists of text and/or graphics created by a user.

Management requests are requests to manage printing systemcomponents, such as adding or deleting printers, or canceling printrequests.

Responses to the client are information from the server that arisefrom submitted requests.

ServerClient

Responses

Print DataJob & Device

StatusRequests

JobsJob Ctrl

OutputDevice(Printer)

Requests

Status

PRINTXCHANGE OVERVIEW


Server

The server receives requests from the client, performs the actionsrequired for each request operation, and returns responses to theclient.

From the files submitted by the client on a print request, the servercreates documents and organizes the documents into jobs. Adocument represents a single user file to be printed. A jobrepresents a collection of one or more documents to be printed as aunit. The job also contains instructions for printing (such asproduction and finishing instructions), and notification of job status.

The server sends jobs and associated document print data as well asapplicable job control commands to an output device.

Server daemons

In the UNIX environment, in addition to the spooler and supervisorservers, PrintXchange software includes the following daemonprograms that work on behalf of the client utilities and serverprograms:

� Protoserver (rpc.pts)

� Notification Server (pdntfs)

� Console Notification Daemon (pdconntf).

The protoserver daemon serves as the server registration and lookupagent for spoolers and supervisors running on a host. Clients mustfirst communicate with a host’s protoserver to acquire the remoteprocedure call (RPC) binding information of servers specified in anoperation. The protoserver registers itself on a host using a fixedregistered program number.

The notification server intercepts and distributes notificationmessages issued by spoolers and supervisors. It is responsible forsending e-mail or displaying messages on the GUI message areawhen significant events occur.

The console notification daemon is required when you wantnotification messages to appear in the Command DesktopEnvironment (CDE) system console window.

Only one copy of each of these daemons runs on a host at a time.The protoserver and notification server daemons run automaticallyunder control of the inetd.conf file, to include commands that startthese daemons when requests arrive. The console notificationdaemon is started once during the system start up procedure.

Output device (printer)

The output device is typically referred to as the printer. It is thephysical device or hardware that is capable of rendering images ordocuments and producing hard copy output of the jobs that itreceives from the server.

The output device receives the jobs (including the print data) and jobcontrol commands from the server. Depending on its type or its setof features, the output device returns responses to the server.Output devices respond with at least a message indicating theircurrent state.



PrintXchange features and benefits

The PrintXchange printing system expands on the basic printingsystem by providing support for different types of clients, and using aserver system rather than a single server, as illustrated below.

Figure 2-2. PrintXchange clients and servers

PrintXchange supports different types of clients:

� Command Line Interface (CLI)

� Graphical User Interface (GUI)

� Application Programming Interface (API)

� Inbound gateway clients (LAN Manager, LPR, Novell NetWare).

In the PrintXchange server system, the server functions are splitbetween two different server types:

� Spooler

� Supervisor.

PrintXchange further differentiates between two types of supervisors:

� Reference supervisor

� Xerox supervisor.

CLI Client

ReferenceSupervisor

Spooler

OutputDevice A

Server System

XEROXSupervisor

OutputDevice B

GUI Client

Inbound GatewayClients

PrintXchange

LPRUSER

LPRGW



Figure 2-3. Simplified PrintXchange printing system

As illustrated in the figure above, PrintXchange also uses twodifferent abstractions called objects to indicate the characteristics ofthe multiple output devices that it can support:

� Logical printer

� Physical printer.

The PrintXchange system further uses the concept of queues toassociate groups of logical printers with groups of physical printers.Figure 2-3 illustrates a simplified PrintXchange system with all of theprimary elements.

Print Data

OutputDevice

Client� CLI� GUI� Inbound

Gateways

Responses

Mgmt RequestsJob Data

Spooler Server

Queue

LogicalPrinter

LogicalPrinter

LogicalPrinter

Server System

Jobs

Responses

SupervisorServer� Reference� Xerox

Print Requests

Job Ctrl

OutputDevice

Physical Printer

Physical Printer

Job Ctrl

Job Data

Responses

Responses

Responses

Mgmt Reqs

Mgmt ReqsPrint Data

Disk

Status/Events



PrintXchange clients

Four types of client interfaces provide access to a PrintXchangesystem:

� Command Line Interface (CLI)

� Graphical User Interface (GUI)

� Inbound gateway.

The client interfaces enable PrintXchange users to perform printingoperations, including:

� Submit print request

� Resubmit job

� Promote job

� Cancel job

� List object attributes

� Modify job

� Pause and resume job.

The client interfaces also allow users to perform configuration andmaintenance operations, including:

� Create and delete object

� Enable and disable object

� Pause and resume object

� Set object attributes

� Clean object (delete all jobs from a specified object)

� Shut down object.

Command line interface (CLI)

The CLI consists of a set of commands that allow users to performprinting system operations. Users run commands by entering themin the command or terminal window. The commands includeparameters that identify applicable objects and options.

Graphical user interface (GUI)

The GUI operates within the Common Desktop Environment (CDE)defined by Open Software Foundation (OSF); it uses the Motif�windowing system and its conventions.

The graphical nature of the interface makes it easier for the noviceuser to perform print operations, yet allows advanced users toperform more complex configuration and maintenance operations.



Figure 2-4 illustrates the GUI window, which enables a user to submita print request. Various buttons, check boxes, text entry fields, dropdown lists, and icons enable a user to specify the print files and printparameters.

Figure 2-4. Print job window

Besides the print job window, the GUI provides:

� Print information windows that allow users to set default jobattributes, to list job attributes, and to run operations onsubmitted jobs such as pause, promote, and cancel.

� Administration windows that allow users to manage spoolers,queues, printers, and jobs. Server and printer administrationtasks include:

� List all available spoolers, supervisors, queues, logicalprinters, physical printers, etc., in the local domain, or in thespecified 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 privilegelevel

� Add and delete default event notifications for each object inthe system

� Perform all operations available through the PrinterInformation application.

Based on the user’s window selection and entries, the GUI displaysother windows or performs an operation.



Inbound gateway

The inbound gateways allow users of legacy print applications (lp andlpr systems) using RFC 1179 (BSD) protocol to submit print requestsfor printing on an output device in the PrintXchange system. The lprinbound gateway maps information between the BSD protocol andthe PrintXchange protocol.

PrintXchange inbound gateways support:

� LPD clients (LPR inbound gateway). The LPR gateway offersthe equivalent functionality of the UNIX LPR inbound gateway.The PrintXchange supports the PrintXchange 1.0 LPRextensions plus production printing and Fuji Xerox extensions.

� A LAN Manager inbound gateway supports SMB protocolcompatible with OS/2 and Windows for Workgroup.

� A QServer Inbound gateway enables NetWare clients in atraditional NetWare printing environment (i.e., non-NDPS) tosubmit print jobs to the PrintXchange system.

Common features of the gateway include:

� The inbound gateway software is loosely coupled with thePrintXchange spooler. It can either reside on the same hardwareplatform with the spooler, or reside on a separate machine.

The NT gateway processes run on top of the NT operatingsystem. They do not run on UNIX.

� An NT gateway can connect to an NT PrintXchange spooler.Binding between the gateway and the spooler is static. It occursupon gateway configuration. Microsoft RPC is thecommunication protocol with an NT PrintXchange spooler.

ONC RPC is the communication protocol used by the LPRinbound gateway with the UNIX PrintXchange spooler.

� Operations and attributes supported by the gateway are confinedto the subset available in the native client environment. Typicallythis 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 sametime. The maximum number of client connections isconfigurable. The gateway acts as a proxy for its client networkenvironment. Users from the client network environment sharethe same level of access as the gateway.



PrintXchange servers

In the PrintXchange server system, the server functions are splitbetween two different server types:

� Spooler

� Supervisor.

Spooler

Through a logical printer, the spooler receives a client print requestfor a job that includes print data or a reference to the print data forone or more documents. The spooler then schedules the job on anappropriate physical printer associated with the specified logicalprinter.

At the appropriate time, the spooler forwards the job to the supervisorassociated with the physical printer on which the spooler scheduledthe job.

Note: A spooler can support multiple supervisors.

The spooler also receives client management requests that apply tothe spooler or to spooler elements, which include logical printers andqueues. The spooler forwards to the supervisor any clientmanagement requests that may no longer apply to the spooler, suchas delete job; if the spooler has already sent the job to thesupervisor, it forwards a client delete job request to the supervisor.

The spooler returns appropriate responses to requests from thesupervisor, such as next job requests, status reports, 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 theappropriate output device

� Handles any responses made by the output device.

The supervisor receives client management requests that apply tothe supervisor or to supervisor elements, which include physicalprinters. It also receives client management requests forwarded bythe spooler.

Information sent from the supervisor to the spooler consists ofmanagement requests, such as request for next job and statusupdates, such as job completed; and notification, such as jobcanceled by user.

PrintXchange supports two types of supervisors:

� Reference supervisors

� Xerox supervisors.



Reference supervisor The reference supervisor is used for printers directly controlled byPrintXchange. 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 printersusing the printer’s PostScript bi-directional status interface.

The reference supervisor directly controls all aspects of printing a jobincluding:

� 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 supports the DocuPrint NPS and DocuSP printservers, thus providing connectivity to most of the major Xeroxproduction printers. The Xerox supervisor functions are:

� Job submission using RFC 1179 lpr

� Job cancellation using RFC 1179 lprm

� Job status query using RFC 1179 lpq, Xerox production printerstatusing (XPPQ)

� Device status query using Xerox production printer statusing(XPPQ).

Xerox supervisor The Xerox supervisor provides connectivity to printers capable ofsupporting:

� RFC 1179 protocol

� Simple network management protocol (SNMP)

Via the DocuPrint NPS and DocuSP print servers, the Xeroxsupervisor also provides connectivity to most of the major Xeroxproduction 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

For additional information on SNMP query support, refer to the“SNMP query support” appendix in this guide.



PrintXchange logical/physical printers and queues

The PrintXchange system uses the concept of logical printers torepresent physical printers in a more user-friendly fashion. To auser, the model of the printer is not as important as the capabilities ofthe printer. PrintXchange provides the user with a means ofsubmitting jobs to an entity that describes the characteristics of theoutput device such as duplex, color and highlight color.

The PrintXchange system further uses the concept of queues toconfigure a set of logical printers to physical printers.

Physical and logical printers

A physical printer represents the actual output device, such as aXerox 4230 laser printer.

A logical printer indicates particular characteristics and capabilitiesof one or more physical printers. It is an abstraction of printercapability. It serves as a defaulting device as well as a gateway intothe system.

Users direct their print requests to the logical printers with thecharacteristics that fit their needs. The spooler channels therequests via a queue to a supervisor that supports a physical printermapped to the specified logical printer through the queue.

Queues

A queue associates a set of jobs with a set of logical and physicalprinters. It serves as a pool that holds the jobs until the spooler cansend them to the appropriate supervisor.

Logical printers feed jobs into a queue; physical printers request jobsfrom a queue. A logical printer is associated with only one queue andcan feed jobs into only that one queue. Similarly, a physical printer isassociated with only one queue and can request jobs only from thatqueue.

Printer/queue associations

As the administrator, you link logical printers, physical printers, andqueues to each other. The links, or associations, reflect your plan forutilizing the output devices on your site to the best advantage.

Jobs submitted to a logical printer are placed in a queue andscheduled for printing on a physical printer that matches thedocument characteristics specified.

Logical printers are mapped to physical printers through a queue.For purposes of balancing print loads, multiple similar physicalprinters can be mapped to a logical printer. Conversely, multiplelogical printers can be mapped to a physical printer. Logical printersdefine default printing setups for a physical printer and enable jobqueue management based on the availability of the characteristicsrequested for a job. For example, logical printers could be createdfor each paper size available on a physical printer. If the printer iscurrently out of the requested paper size, jobs submitted to thatspecific logical printer will remain in a held state until this capabilitybecomes available.



Figure 2-5 illustrates the simple case where there is only one logicalprinter, one queue, and one physical printer. In this case, the logicalprinter serves simply as a view or representation of the physicalprinter to the user. The user-defined associations for this case areLP1-Q1 and PP1-Q1. These associations create an implicitrelationship between LP1-PP1.

Figure 2-5. Logical printer as simple representation ofphysical printer

Figure 2-6 illustrates multiple logical printers feeding a queue thatserves only one physical printer. In this case, the logical printersprovide the user with different defaults for a job submitted to acommon 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) Physical Printer (PP)

LP1

Black & WhiteStaple

LP2

Highlight ColorStaple

Q1

LP3

Black & WhiteLarge Paper

Queue (Q)

PP1

Black & WhiteHighlight ColorLarge Paper

Staple

Logical Printer (LP) Physical Printer (PP)

LP1Black & WhiteHighlight ColorLarge Paper

Staple

PP1Black & WhiteHighlight ColorLarge Paper

Staple

Q1

Queue (Q)



Figure 2-7 illustrates a more complex case of multiple logical printersand multiple physical printers. In this example, large paper jobs fromLP1 can print on either PP1 or PP2 depending on which printer is notbusy. Since PrintXchange has the intelligence to schedule jobsbased on the characteristics defined in the user’s print request, it willautomatically only send the LP2 Black & White Stapling jobs to PP2since the system knows that PP1 does not have finishing capability tostaple jobs.

Figure 2-7. Logical printers providing load balancing

Logical Printers (LP) Physical Printers (PP)

LP1Large Paper

LP2Black & White

Staple

LP3Highlight Color

PP1Large Paper

Black & White

PP2Large Paper

Black & WhiteStaple

PP3Black & WhiteHighlight Color

Q1

Q2

LP4Black & White

Queues (Q)



Objects and attributes

PrintXchange uses objects to represent various entities, such asserver, printer, and queue. A spooler and a supervisor are bothserver objects; a logical printer and a physical printer are printerobjects.

PrintXchange objects This section on concepts and terminology hasintroduced you to the PrintXchange objects, namely:

� Spooler

� Supervisor

� Queue

� Logical printer

� Physical printer

� Job

� Document.

PrintXchange has two additional objects that enable you to setdefaults on certain printing aspects of jobs and documents, such asthe number of copies to be printed or the default input tray. The twoobjects are:

� Initial-value-job object that specifies defaults for jobs

� Initial-value-document object that specifies defaults fordocuments.

Typically, administrators apply an initial-value-job and/or an initial-value-document object to a logical printer. When a client submitsprint requests to the logical printer, the logical printer applies thedefaults to the jobs and documents. Users may also apply an initial-value-job and/or an initial-value-document object by specifying it withthe print request.

Spooler objects contain queue, logical printer, initial-value-job, andinitial-value-document objects. Supervisor objects contain physicalprinter objects. The administrator creates the queue, logical andphysical printer, and initial-value-job and initial-value documentobjects using create object commands. These objects, including thespooler and supervisor objects, are persistent. That is, the objectscontinue 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 toprint requests. Jobs and documents exist only until the jobcompletes printing or until the end of a specified retention period.

Object attributes An object contains a collection of attributes that provide informationabout the object. An attribute indicates a characteristic of an objectrelating to its identity, physical makeup, or status. Examples ofprinter object attributes are:

� printer-name , a single-valued attribute whose value is a namethat uniquely identifies a printer, whether logical or physical

� media-supported , a multi-valued attribute whose values identifythe media that the printer supports such as iso-a4-white and iso-a4-transparent

� printer-state , a single-valued attribute that indicates the currentstatus of a printer such as idle or printing .



The attributes associated with an object define the configuration andbehavior of the object. The spooler and supervisor serversmanipulate the object representation of an entity they are operatingon by setting or changing the values of the object’s attributes. A userobserves the value of an attribute with a list attributes command andchanges the value of an attribute with a set or modify attributescommand.

Attribute=value pairs Attribute names have a hyphenated format, such as default-input-tray and job-copies . An attribute=value pair indicates a particularvalue for the attribute. For example:

default-input-tray=topjob-copies=3

Administrator and operator operations

Commands enable you to manipulate PrintXchange objects.Operations are subject to access control. Only users with anappropriate access level may run certain operations.

PrintXchange recognizes three access levels: End User, Operator,and Administrator. End Users have access to only certainoperations. Administrators, have access to all operations. Operatoraccess falls in between.

Table 2-1 lists the operations, provides a brief description andspecifies 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 previouslysubmitted print jobs.

End User(Jobowner)

Job

Clean Delete all jobs from thespecified object.

Operator Spooler, queue

Create Create objects, and settheir attributes to thespecified values: (initial-value-job, initial-value-document)

Administrator Queue, logicalprinter, physicalprinter, i-v-job, i-v-doc

Delete Delete objects. Administrator All

Disable Disable the acceptanceof new print requests orjobs.

Operator Spooler, supervisor,queue, logicalprinter, physicalprinter

Enable Enable the acceptanceof new print requests orjobs.

Operator Spooler, supervisor,queue, logicalprinter, physicalprinter



Table 2-1. Operations summary (continued)

Operations Description Administrator Operator End user Valid objects

List job queue List the jobs andrequested job ordocument statusattributes submitted to aspecified logical printerassociated with aqueue.

End User Job, document

List objectattributes

List the names of printobjects and the namesand values of theirattributes.

End User All

Modify Change the values ofspecified job ordocument attributes.

End User(Jobowner)

Job, document

Pause Pause the specifiedobject so that it doesnot produce furtheroutput.

Operator End User(job owneronly)

Spooler, queue,physical printer, job

Print Submit a print request. End User Not applicable

Promote Schedule the specifiedjob for printing on thenext availablerequested printer.

Operator Job

Resubmit Resubmit the specifiedjob, or jobs in thespecified queue, to aspecified logical printer.

Operator End User(job owneronly),

Job, queue

Resume Resume the specifiedobject so that itcontinues normaloperation.

Operator End User(job owneronly)

Spooler, queue,physical printer, job

Set attributes Set attribute values ofspecified print objects.

Administrator End User(job owneronly)

All

Shutdown Shut down the specifiedserver.

Operator Spooler, supervisor



PrintXchange printing system components

The first section of this chapter defined concepts and terminologyused to describe a basic printing system as well as a simplifiedPrintXchange printing system. This section further describes thePrintXchange printing system by presenting an overall view of itsprimary components and then providing a closer look at the ones thatwere not covered in the prior section.

The primary software components of the PrintXchange printingsystem are:

� Infrastructure

� Clients

� Servers.

Infrastructure

The PrintXchange infrastructure consists of facilities that providegeneral distributed services to all PrintXchange components.

Many of the facilities function internally to the system, that is, usershave no direct access to them.

Example: Facilities that provide direct access to system databasesor that provide communications handling in distributed systems.Such facilities do not fall within the scope of this document, and aretherefore not described.

Several facilities, however, require that users specify parametersdictating how certain aspects of the facilities should function in thelocal environment. These facilities are:

� Name services . Administrative users must configure the nameservice to allow the printing system to locate objects in thesystem.

� Security services . Administrative users must specify accesslevels for all users of the printing system.

� File transfer . Users must specify how PrintXchange shouldtransfer files between the client and spooler and/or supervisor (orthe system provides a default).

� Event notification . Users must specify the events that thesystem should report and the method for these notifications.

� System logging . The system automatically logs certain eventsto the system log.



Client interfaces

Three types of client interfaces provide access to PrintXchangefunctionality:

� Command line interface (CLI)

� Graphical user interface (GUI)

� Inbound gateway.

As figure 2-8 illustrates, the CLI, inbound gateway, and programapplication interfaces are based on the POSIX 1387.4 standard,whereby the POSIX API provides a layer between the user interfaceand the client core software. The GUI has a direct interface to theclient core.

Figure 2-8. Client structure

A brief description of each of the client interfaces follows.

POSIXAPI

GUI

Client Core

InboundGatewayClients

CLI



Command line interface (CLI)

The CLI consists of a set of command that allow the user to performthe printing system operations. Users run the commands by enteringthem on the console window. The commands include parametersthat identify applicable objects and options. Table 2-2 lists the CLIcommands.

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 tothe 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 printingon the physical printer.

pdpause Pause pending jobs, physical printers, queues, or spooler.

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 wassubmitted.

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 anotherspecified printer. Command that allows all jobs in a specified queue to be simultaneously resubmitted toa 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.



The CLI parses the user’s command line input string and converts itto API calls. The API layer accesses infrastructure facilities, such asthe object identifier database (OID) and the attribute set, to determinethe validity of the input string.

The PrintXchange Command Line Interface Reference Guidedescribes the CLI, including the command line syntax and each ofthe command operations and options.

For information on Graphical User interfaces on Windows NT,Windows 95, and UNIX, and information on program applications andinbound gateway, refer to the “PrintXchange clients” section earlier inthis chapter.

Servers

As described in the section “PrintXchange servers,” the PrintXchangeprinting system consists of two different types of servers: spoolersand supervisors. These two servers have different primary purposeswithin the system.

While the two types of servers have different primary functions, theyalso have a substantial amount of common functionality, whichinclude startup, shutdown, and configuration.

Startup Servers are started at the command prompt or via a shell scriptspecifying the following executable names and appropriate flags.

For a complete list of the server startup commands, refer to the“Server startup commands, switches and exit status codes”appendix.

Shutdown A server shuts down gracefully when an administrator requests ashut down. The server tries to put the object database in aconsistent state before exiting.

Any other event that causes a server shutdown may causeinconsistencies in the object database. An administrator can create,modify, and display the object database to ensure that certain serverattributes exist and are correct in order for the server to start. Theutilities that enable this functionality are:

� pdmakedb for creating an object database

� pdmoddb for modifying an existing object database

� pdshowdb for displaying some of the data in an existing objectdatabase.

Configuration As part of the startup process, a server checks configurationattributes that specify certain aspects of the file system required forsuccessful 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.



Spoolers

A spooler is the central element in the PrintXchange printing system;it accepts jobs from multiple clients and submits jobs to multiplesupervisors.

A spooler provides a common interface through which clients submitand 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 hascompleted

� Receives requests for jobs from a supervisor and submitspending print jobs to a supervisor

� Supports multiple supervisors

� Provides information to clients for job status reporting andtracking.

� Perform administrative functions. The spooler accepts objectmanagement requests from multiple clients for the followingobject types:

� Document

� Job

� Initial-value-document

� Initial-value-job

� Logical printer

� Queue

� Spooler server.

The spooler handles recording of job accounting information forlater retrieval.

Supervisor

A supervisor provides a common interface between spoolers andoutput 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 (physicalprinter) or forwards the job to another print system forprocessing.

� Performs administrative functions. The supervisor accepts objectmanagement requests from the spooler and management clientsfor the following object types:


� Supervisor server.



Example: request processing

Using a print request as an example, the following paragraphsdescribe the processing that the CLI client, spooler, and supervisorundergo as they satisfy the request.

Overall, the processing steps identify most aspects of PrintXchangefunctionality that are described in more detail in the remainder of thisdocument.

Note : By default, users may only see information about jobs up untilthe time they are printed. After that, information about completedjobs remains only in the accounting logs. In an environment wherethe administrator would like users to be able to view jobs in a"completed" state, the server default-job-completion-period shouldbe set to an appropriate time period. You can change the value viathe CLI. For example, set default-job-completion-period=4 toensure that jobs do not disappear immediately upon printing. Theywill remain for 4 minutes.

These steps are generally listed in the order in which they occur.However, some steps actually overlap. Also, these steps onlyindicate the processing for a simple, correct job.

1. The user submits a request by entering the print request via theCLI or GUI. For example:

pdpr -x “sides=2” File1.txt

2. The client processes the request:

� Parses command. The syntax is validated and attributes areverified.

� Provides defaults. Attributes such as printer-name-requested , job-name , transfer-method, and job-owner aregiven values if the user has not specified them.

� Checks the Name Services to get the binding information forthe logical printer.

� Initiates a print request with an RPC to the spooler.

� Unless the file-reference transfer method is used, transfersthe 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, thespooler ensures that the user is authorized as, at least, anEnd User for this server.

� Ensures that the logical printer and its associated queue areenabled.

� Applies defaults for unspecified attributes from any initial-value-job and initial-value-documents.

� Verifies that all specified attributes are correct and comparesthem to the logical printer’s xxx-supported attributes toensure that the job request can be satisfied.

� The spooler creates the job and document objects andenters it into the object database. Attributes such as job-identifier , submission-time and current-job-state havevalues provided.

� pdl guessing is used if document format is not specified.



� Applies any necessary filters to the print data and sends theprint data to the output device.

4. The spooler schedules the job for printing:

� The supervisor for a physical printer associated with thequeue, requests a job from spooler.

� The spooler validates that the physical printer is enabled andnot paused.

� The spooler selects promoted jobs first, and then selects jobsbased on job priority. If jobs have the same priority, it selectsthe oldest pending job in the queue.

� The spooler compares the printer’s xxx-ready attributes withthe job and document attributes. If all of the requestedattributes are ready, the spooler gets binding information forthe physical printer from the Name Service and delivers thejob to the supervisor.

� If the supervisor and spooler are not on the same host, theprint data is transferred to the supervisor’s spool area.

� The spooler updates job attributes such as current-job-stateand printers-assigned to indicate that the job has beendelivered 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 appropriatefor the output device.

� Based on attributes such as default-input-tray , thesupervisor sends command sequences to the printer to setits defaults.

� Applies any necessary filters to the print data and sends theprint data to the output device.

6. Job processing is completed:

� When all print data has been sent to the printer, thereference supervisor sets attributes such as current-job-state and job-completion-time .

� The Xerox supervisor queries the printers for Job Status andwhen it is completed on the printer, it sets current-job-stateand job-completion-time .

� The Xerox supervisor informs the spooler that the job iscomplete, deletes the “shadow” job and document objectsand any spooled data.

� The Xerox supervisor requests another job from the spooler.

� The spooler updates the job and document attributes with theinformation from the supervisor and writes accountingrecords.

� Spool data is deleted but job and document objects remainuntil job completion period has expired.



7. The spooler and supervisor notify users:

� Throughout the steps listed above, both the spooler and thesupervisor identify system events such as object statechanges and printer attentions, compare these eventsagainst object notification profiles, and send messages tointerested end users.

Interoperability

PrintXchange includes NT as a supported server platform in additionto Sun Solaris. PrintXchange also includes clients for UNIX,Windows NT, and Windows 95. This section describesinteroperability for PrintXchange components on Windows 95, NT,and Sun Solaris platforms. As in the UNIX environment,PrintXchange Windows 95 and NT components have complete andseamless interoperability. However, PrintXchange Windows 95 andNT components do not have complete interoperability with SunSolaris components. Specifically, PrintXchange Windows 95 and NTclients can be configured to work with a Sun Solaris servers.However, PrintXchange Sun Solaris clients do not work with an NTserver.

In addition to native clients, PrintXchange offers an lpr gateway onSun Solaris. PrintXchange also provides lpr and LAN Managerinbound gateways and Novell qserver gateways on the NT platform:

� The lpr gateway provides interoperability with the older UNIXprinting systems.

� The LAN Manager gateway provides interoperability with legacyWindows 3.x, Windows for Workgroup, and OS/2 clients.

� The Novell qserver gateway provides interoperability withNetware clients.

The lpr gateway for Sun Solaris works only with PrintXchange UNIXservers. The Novell QServer, lpr and LAN Manager gateways for NTcan be configured to allow Windows NT network users to submit printjobs to PrintXchange printers controlled by either an NT or UNIXserver.



Multinational considerations

PrintXchange is intended for worldwide distribution and use. It hasbeen designed to be easily converted to use different code sets andto have the user visible text easily translated and incorporated backinto the system.

All PrintXchange software:

� Supports single-byte and multi-byte code sets in a code-setindependent manner to provide support for ISO 8859-1 inWestern 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 ofinformation (date, time, and numbers) and the sorting order ofdifferent language alphabets to be set by locale.

� Stores locale-dependent information such as help text, errormessages, property sheets, buttons, and text on icons in fileswhose paths depend on the locale. PrintXchange uses theX/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 visibleto end users.

General internationalization requirements and restrictions

PrintXchange clients and servers are to be in the same language andterritory. For some languages/territories, such as Japan, two or morecode sets are in use. Therefore, some code set conversion is dealtwith. Conversions are restricted to those that are supported by thelocal iconv routine.

Attribute names, such as plex and values that have OIDs or areenumerated, such as duplex , simplex and tumble are not intendedto be localized in PrintXchange.

Attribute values that support entry of variable text, such as the valuefor 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 characterset specification is not supported.



Supported character-sets

PrintXchange supports only character sets that are single byte (8-bit)or multi-byte, null-byte-terminated strings; it does not supportunicode. A component may choose to convert a string to Unicode inorder to perform some operation but this conversion is local to thecomponent.

The defined character sets of PrintXchange are listed in the CLIReference Guide under the attribute “default-character-set”.

However, PrintXchange extensions to the DPA textSyntax andsimpleNameSyntax provide a new value entry that enables thespecification of a character set using an octet string. The new valueentry is other-code-set , and will be the only value that PrintXchangeservers will use. Other values are retained for compatibility with theoriginal DPA syntax. The value other-code-set consists of twoelements: octet-string and, optionally, code-set with anobjectIdentifier data type.

For both incoming and outgoing text attribute values, if theoperational locale is not specified, then PrintXchange uses thecharacter-set entry of the server’s locale.

Environment variables

The environment variables listed in table 2-3 may affect the operationof the utilities PDPATH and PDPRINTER. The utilities use thecurrent value of environment variables as the default, unless a userspecifies a different value via a command option.

PrintXchange uses the remaining environment variables forlocalization. These variables may affect the behavior of theCommand Line Interface.

Table 2-3. UNIX Environment variables

Variable Description

LANG Determines the locale category for any locale category notspecifically selected via an environment variable starting with LC_.

The LANG and LC_ variables determine the language for messagesand instructions, collating sequences, date formats, etc., used todetermine the locale, that is, the user language, territory, andcharacter set.

LC_ALL Overrides any values for locale categories specified by the settingof LANG or any environment variables beginning with LC_.

LC_COLLATE Determines the locale category for character collation informationwithin bracketed REs and for sorting. LC_COLLATE determinesthe behavior of range expressions, equivalence classes, and multi-character collating elements.



Table 2-3. UNIX Environment variables (continued)

Variable Description

LC_CTYPE Determines the locale category for character handling functions.LC_CTYPE determines the:

� Interpretation of sequences of bytes of text data as characters(e.g., single- versus multi-byte characters)

� Classification of characters (e.g., alpha, digit, graph)

� Behavior of character classes.

LC_MESSAGES Determines the locale category for processing affirmative andnegative responses, and the language and cultural conventions inwhich messages should be written.

The language and cultural conventions of diagnostic andinformative messages whose format is unspecified should beaffected by the setting of LC_MESSAGES.

LC_NUMERIC Determines the locale category for numeric formatting information(e.g., the thousands separator and radix character).

LC_TIME Determines the locale category for date and time formattinginformation.

Note that the CLI and API do not use this variable. Both interfacesuse the format: dd:mmm:yy:HH:MM:SS ±h from Zulu time.

NLSPATH Determines the directory path for CLI message files only if themessage files are not stored in the standard directory.

PDPATH Consists of a colon-separated list of directories (path) that aresuccessively tried for the file name specified in the -Xattribute_filename option.

The PDPATH environment variable is processed forattribute_filename in the same way that the PATH environmentvariable is processed for utility names

PDPRINTER The value of this variable is used as the default printer by the printclient when the attribute printer-name-requested or the option - pprinter_name is unspecified.

The variable is also used to select a server for operations when anexplicit server is not selected. (The server that contains this printeris viewed as the default server.)



Message catalog files

All error messages and screen text presented to the user are basedon Resources DLL. The PrintXchange core software is developedand distributed in the US English locale.

In addition, Xerox will perform and make available German, French,and Japanese localizations.

On UNIX, the US English message catalog files are to be installed inthe following directory:

usr/lib/locale/$LANG/LC_MESSAGES (Solaris)

Infrastructure

All object names that are entered into the NameSpace are restrictedto localized strings.

Text used in values of the access-control-list attribute is alsorestricted to localized strings.

Notification messages and arguments must be localizable.

Log files

All system error log files contain only a single language to simplifysupport and service. PrintXchange uses generic English in the ASCIIcode set. System log messages are not localized in PrintXchange.

Servers

Servers-common The server performs any required character set conversions. Allstrings within a server are in the character set of the server’s host.

The spooler and the supervisor are restricted to the same characterset.

Spooler There are no unique internationalization aspects of the spooler.

Reference supervisor& Xerox Supervisor

All static text displayed on separator pages is read from messagefiles. The supervisor assumes that all the printers it supports canprint the strings in the message files without character setconversion.

The PostScript prologue file used for separator sheets should belocalized for several languages. The sample prologue files for ISOLatin1 encoding and EUC-JP encoding are developed and distributedwithin PrintXchange.



Clients

Common client Clients should determine their operational locale. If the operationallocale for an operation is not specified, it defaults to the server’slocale.

POSIX CLI CLI command names and options flags are not localized.

GUI Text entry fields are sized with consideration to languages other thanEnglish.

Inbound gateway clients There are no unique internationalization considerations for gateways.


3. System requirements

The earlier chapters provided an overview of PrintXchangecomponents and the infrastructure that enables those components.In addition you explored PrintXchange clients: GUI, inboundgateways, and CLI.

A successful PrintXchange installation requires careful planning. Atthis point, you are ready to plan your PrintXchange installation. Youshould plan well so that you and your end users can enjoy anefficient and productive PrintXchange system. This chapteraddresses how to determine system requirements when planning theconfiguration:

� Software requirement

� Network requirement

� Hardware requirement.

As a guideline for planning, you should meet the minimum server andclient requirements for the PrintXchange system.

Software requirements

Software requirements for PrintXchange installation include:

� Solaris 2.5.1 operating system and recommended patch kit orSolaris 2.6

� Solaris Common Desktop Environment (CDE).

Note : CDE is required to access the PrintXchange GUI.

Packages from the Solaris operating system installation CD:

� SUNWfns Federated Naming system

� SUNWfnspr FNS Support for Printer Context (Solaris 2.5.1only)

� SUNWisolc Conversion for ISO Latin character sets.

Network requirements

Network requirements for PrintXchange include TCP/IP (Localnaming or NIS).

SYSTEM REQUIREMENTS


Hardware requirements

The following are the hardware requirements for the three typicalPrintXchange configurations.

Hardware full server/client configuration

Hardware (PrintXchange full server/client configuration) requirementsare:

� Minimum - Sun SPARCstation 5 (32 MB RAM)

� Recommended - Sun Ultra-1 SPARC (128 MB RAM)

� Disk Space - 20 MB (installation), 1 GB (operation).

Note: You must take into account the number of jobs printed, the jobretention period, and the size of the print data to figure out what sizehard disk to use in your configuration. Similarly, the memory size andthe processor speed depend on the number of concurrent jobsubmissions and the number of printers connected to the server.

Hardware CLI configuration

Hardware (PrintXchange Command Line Interface(CLI) clientconfiguration) requirements are:

� Minimum - SPARCstation 2 (32 MB RAM)

� Recommended - SPARCstation 5 (32 MB RAM)

� Disk Space - 3 MB (installation/operation).

Hardware GUI and CLI configuration

Hardware (PrintXchange Graphical User Interface (GUI)/CommandLine Interface (CLI) configuration) requirements are:

� Minimum - SPARCstation 5 (32 MB RAM)

� Recommended - SPARCstation 5 (64 MB RAM)

� Disk Space - 12 MB (installation/operation).


4. Recommended configurationplanning

Configuring your PrintXchange system is a five-phase process:

1. Determining your network printing system requirements;

2. Installation process;

3. Creating and configuring queues, physical printers, and logicalprinters;

4. Enabling queues, physical printers, logical printers, and inboundgateways; and

5. Validating your installation and configuration.

This chapter list the steps required in the first and second phase.Subsequent chapters describe each of the remaining steps in detail.

Determining your network printing system requirements

This phase consists of the following steps:

1. Determine the hosts for the PrintXchange software.

2. Determine the types and number of clients you need.

3. Determine the printers you have in your network.

4. Determine how many supervisors you need to control thephysical printers.

5. Determine where to install the clients, supervisors, and spooler.

6. Identify the .paf files that you need to create physical printers.

7. Verify that PrintXchange supports those printers from the printerdata sheets in the appendix, “Printer Data Sheets”.

8. Determine how many physical printers you need in yourPrintXchange system.

9. Determine the xxx-supported and xxx-ready attributes of theprinters from the printer data sheets in the appendix, “PrinterData Sheets”, to define your printer capabilities.

10. Abstract the printer capabilities that you want to offer to your endusers into groups that will become your logical printers.

11. Determine the document and job defaults you want to apply tological printers.

12. Map logical printers and physical printers via queues.

13. Determine your end users and their privilege levels.

14. Determine your NIS name service needs.

RECOMMENDED CONFIGURATION PLANNING


Installation process

This phase consists of installing the PrintXchange softwarecomponents appropriate for your environment:

1. Create a spooler to handle print requests and manage logicalprinters and queues.

2. Create one or more supervisors to manage physical printers.

Creating and configuring queues, physical printers, and logical printers


1. Create queues to store pending documents and jobs, and toconnect your logical printers and physical printers.

2. Create a physical printer to represent each printer.

3. Determine initial-value-job and initial-value-document objects tocontrol document and job defaults at the logical-printer level.

4. Determine event notification profiles.

5. Create logical printers based on the abstract capabilities of yourprinters, and the defaults and event notification profiles youdetermine.

Enabling queues, physical printers, logical printers, and inbound gateways


1. Enable queues.

2. Enable physical printers.

3. Enable logical printers.

4. Enable the inbound gateway.



Validating your installation and configuration

This phase consists of testing your PrintXchange system once it isenabled.

1. Send at least two documents and jobs to print on all of theprinters in your network: one using logical-printer-level defaultsand one specifying values 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.

Configuration roadmap

Table 4-1 lists the chapters covering the major steps of theconfiguration process.

Table 4-1. Configuration roadmap

Process Step Location of SupportingInformation

Determining your network printingsystem requirements

Chapter 5

Determining your Name Serviceneeds

Chapter 7 Managing security

Determining your InboundGateway needs

Chapter 19 Inbound gateways

Determining Event Notificationneeds

Chapter 8 Setting event notification

Installing and setting up serverhosts

Chapter 6 Installing and setting upPrintXchange on a server machine

Configuring servers Chapter 9 Configuring, starting andstopping servers.

Creating, configuring, andenabling queues

Chapter 10 Creating and configuringqueues, physical and logical printers

Chapter 16 Enabling and disablingobjects



Table 4-1. Configuration roadmap (continued)

Process Step Location of SupportingInformation

Creating configuring and enablingphysical printers


Chapter 14 Setting and modifying objectattributes


Creating, configuring andenabling logical printers




Validating your installation andconfiguration


Creating configuring and enablingphysical printers




Creating, configuring andenabling logical printers




Validating your installation andconfiguration



5. Planning a PrintXchangeinstallation

Once you have determined the system you want, you can proceed toplan the installation of PrintXchange on UNIX.

Planning printers and queue associations

Logical printers feed queues and queues feed physical printers.Users submit print jobs to logical printers. Each logical printersupplies print jobs to a queue. Queues schedule print jobs to one ormore physical printers.

The mapping between logical printers, queues, and physical printersis the first thing that you should consider when planning aPrintXchange installation.

The “PrintXchange overview” chapter describes printer/queueassociations, and illustrates several configurations for logical printers,queues, and physical printers. This section describes these in termsof planning and installation. Essentially, Chapter 2 illustrates threetypes of printer/queue configurations:

� One-to-one

� Fan-in

� Fan-out

One-to-one configuration

The simplest PrintXchange configuration has one logical printer, onequeue, and one physical printer. The configuration is called one-to-one:

Figure 5-1. One-to-one configuration

This configuration is simple to set up and understand. However, youmust provide any special job or document handling with the job.

LogicalPrinter

Queue PhysicalPrinter

PLANNING A PRINTXCHANGE INSTALLATION


Fan-in configuration

Several logical printers can feed a queue, creating a fan-inconfiguration:

Figure 5-2. Fan-in configuration

Since each logical printer can have associated initial-value-job andinitial-value-document objects, you can use this configuration toprovide defaults to the print jobs submitted through them.

For example, one logical printer might have an associated initial-value-document object with the sides attribute set to 2 and anotherlogical printer would have an associated initial-value-document withthe sides attribute set to 1. Jobs submitted through the first logicalprinter would be printed on two sides and jobs submitted through thesecond logical printer would be printed on one side without any userspecification.

Providing defaults for print jobs through logical printers can make jobsubmission easier for users.

Initial-value-document AInitial-value-job A

Initial-value-document BInitial-value-job B

Initial-value-document CInitial-value-job C

LogicalPrinter 2

LogicalPrinter 1

LogicalPrinter 3

Queue PhysicalPrinter



Fan-out configuration

Each queue can schedule jobs to more than one physical printer,creating a fan-out configuration:

Figure 5-3. Fan-out configuration

The fan-out configuration balances the print load across severalactual printers. The spooler schedules jobs in the queue to the firstavailable printer and, on the whole, jobs are printed sooner.However, this configuration tends to work well only if the actualprinting devices are physically close, as in a print room, and havesimilar capabilities.

PhysicalPrinter 2

Initial-value-document AInitial-value-job A

Initial-value-document BInitial-value-job B

Initial-value-document CInitial-value-job C

LogicalPrinter 2

LogicalPrinter 1

LogicalPrinter 3

Queue

PhysicalPrinter 1

PhysicalPrinter 3



Planning security

PrintXchange can restrict printing operations and functions toauthorized users. PrintXchange defines three privilege levels forusers:

� End Users

� Operators

� Administrators.

The PrintXchange server attribute access-control-list associates auser with one of the privilege levels. Users can either be identifiedindividually by their user name, or by membership in a group. Inaddition, you can disable authorization for any class, allowing anyoneto perform the operations of that class.

Since authentication is based on a shared password file,PrintXchange security imposes the restriction that all componentsmust be installed in the same NIS domain. PrintXchange securityallows ignoring authentication by user-type, so it is possible to allow,for example, end users from another domain to use PrintXchangeprinters. However, if the security has been configured to allow an un-authenticated privilege level, there are no further restrictions; if un-authenticated access is allowed to one end user, it is allowed to all.

The “Managing security” chapter in this guide provides detailedinformation about the privilege levels and the access-control-listattribute.

Questions to consider when planning security

Listed below are some questions to consider when planningPrintXchange security:

Do you want to restrict printing?

You can either restrict access to PrintXchange printers to a list ofusers, or you can allow anyone who has the client software installedto print. If controlling access to printers is not a requirement, it iseasier to disable authentication for the End User privilege level.

How do you currently define users?

If your installation already has defined groups for various types ofusers, it will be easier to carry this usage over into PrintXchange.You can associate multiple groups with a user class; it is notnecessary to create a new class just for PrintXchange.

Do you need operators?

The PrintXchange privilege levels are hierarchical: Everything anoperator can do, an administrator can also do. In many installations,it may not be necessary to differentiate between day-to-dayoperational tasks and administrative tasks. In this case, you canignore the Operator privilege level.



Should security be different on different servers?

Every PrintXchange server has an access control list. However:

� End User access to the printers is defined only by the spooler

� You should define the Administrator and Operator privilege levelsidentically on spoolers and supervisors.

Would you like to allow access to all Windows NT or Windows95 clients in any domain?

Both Windows NT and Windows 95 clients do not have defaultaccess to print using the UNIX PrintXchange server. For setup ofWindows NT and Windows 95 client access, refer to the accesscontrol list examples in the PrintXchange Command Line InterfaceReference Guide.

Planning name services

The name space contains the named network objects (spoolers,supervisors, logical and physical printers, and queues) that youcreate. Each object contains a reference to the network address ofthe server that supports it.

Clients and servers access the name space to locate and bind to theserver that supports a specified network object. When a client orserver requires the binding of a printer name or a server name, ituses the name service to obtain this information. The name servicelooks up the requested name and returns the requested binding tothe client. The RPC mechanism uses the returned binding to connectto the server.

Name services

PrintXchange supports two name services that manage the namespace:

� Local File NameSpace

� Network Information Service (NIS).

The ProtoServer works in conjunction with the name space for LocalFile and NIS naming to enable a server to access name spaceinformation while PrintXchange is running.



Local File NameSpace

The Local File NameSpace works in a single, standalone systemconfiguration or in a distributed environment:

� In a standalone configuration, the client and servers (spooler andsupervisor) reside on the same workstation in an Open NetworkComputing (ONC) environment. That is, when you createprinting objects, the name service makes their bindinginformation immediately available; when you delete them, thename service immediately removes their binding information.

� In a network configuration in an ONC environment that does nothave a network-oriented name service such as NI, you must useLocal File naming.

� In an NIS environment, you can use Local File in conjunction withthe network-oriented name service for redundancy when thenetwork is down or for privacy.

The Local File naming scheme stores RPC binding printerconfiguration information in the file /etc/printers.conf. A separateinstance of the file exists on each host system. Due to problemsupdating the file, multiple hosts cannot share the file (using symlinks,for example).

For additional information on printers.conf file, refer to the"Printers.conf file“ appendix in this guide.

The server startup process automatically generates the printers.conffile if the server attempts to add an entry to the local file and the localfile does not already exist. Also, the servers compare their objectdatabase to the local file and add objects to the name space if theyare in the database but not in the local file.

Since the object create operation updates the Local File naming onlyon the host where you executed the operation, the information is notavailable to clients or servers on other hosts. Therefore, when usingLocal File naming in a distributed environment, it makes more senseto create the configuration file in advance and copy it to all hostsrunning clients or servers.

You can create the printers.conf file with an editor. Or, you cancreate the file by creating all print objects from a single host.However, in the second case, since you do not create servers withthe create operation, you must manually add the server entries to thefile for each different host. You must to update the file on all hosts ifyou delete an object.

For Local File naming:

� The printers.conf file must exist in the /etc directory and it musthave the access rights of rw-r--r--.

� The file owner should be root.



Network Information Service (NIS)

ONC connectivity of UNIX workstations uses the NIS NameSpace.NIS is a distributed name service that uses administrative mapsamong several machines. NIS updates the maps that are distributedthroughout the network from a centralized location in an automaticand reliable fashion.

NIS uses the same objects and syntax in printer configuration entriesas for the Local File case. However, NIS provides a means foradministering and distributing that same printer configuration data toan entire domain.

The most important difference between using Local File and usingNIS is that PrintXchange cannot modify an NIS entry. Instead, youmust manually update an NIS entry in a human-readable NIS file.You must either have the authority to make changes to the NIS file orhave a proxy admin with such authority to make the changes.

The NIS name service requires a coordinated update of configurationchanges. That is, you must add an object’s name to the NIS filebefore you create the PrintXchange object. However, unlike theLocal File case in which you have to update the local file in each ofmultiple hosts, you need to update data in only one place with NIS.

Creating NIS entries or making configuration changes

Use the following procedure to initially create the NIS entries andwhenever you make any configuration changes:

1. To create or modify, as applicable, the ASCII file printers.confwith the same syntax as defined in the section Making ONC RPCbinding entries.

2. To copy the file onto the NIS master where you keep the ASCIIfiles you use to create maps.

3. To modify the printers.conf section of the NIS makefile to includeentries to generate the map, and to push the map to slaves, ifapplicable for your site. (Refer the example below.)

4. To run the NIS Makefile to create the map(printers.conf.byname), and to push the map to slaves ifapplicable.

Pushing the map to a slave fails if the slave does not alreadyhave the map. Therefore, to initially place the map on a slave, dothe following:

a. Tar the maps from the run of the Makefile.

b. Ftp the tar file to the slave.

c. Untar the maps in the appropriate location.

When all slaves have the initial map, running the NIS Makefileautomatically pushes subsequent maps to the slaves andthereby propagates the configuration data.



Example

The example below shows a Makefile entry for theprinters.conf.byname map on the NIS master. DOM is the NISdomainname.

Note: In the Makefile, ALL leading white space must be tabs.

/Variables from the Makefile/

DIR=<path to where the ASCII files are kept>DOM=`domainname`NOPUSH = ""ALIASES=$DIR/aliasesYPDIR=/usr/etc/ypYPDBDIR=/var/ypYPPUSH="$(YPDIR)/yppush"MAKEDBM=$(YPDIR)/makedbm -bREVNETGROUP=$(YPDIR)/revnetgroup < /var/yp/files/netgroupSTDETHERS=$(YPDIR)/stdethersSTDHOSTS=$(YPDIR)/stdhostsMKNETID=$(YPDIR)/mknetidMKALIAS=$(YPDIR)/mkalias

/Printers.conf section of Makefile/

## Printers.conf file for SPSD IFT# installed on CP10WS 7/29/96 BPDPRINTERSCONF=$(DIR)/printers.conf

# @(#)Makefile.yp 1.4 95/09/21 SunSoft modified by davem#$(DOM)/printers.conf.time: $(PRINTERSCONF) -@if [ -f $(PRINTERSCONF) ]; then \ (sed -e '/^#/d' -e s/#.*$$// -e 's/[ ][ ]*$$//' \ -e '/\\$$/s/\\$$/ /' $(PRINTERSCONF) $(CHKPIPE))\ |( awk '/ $$/ {printf "%s", $$0} !/ $$/ {print}' $(CHKPIPE))\ |( sed -e 's/[ ][ ]*/ /g' -e 's/:[ ]*:/:/' \ $(CHKPIPE))\ | awk -F: '{n=split($$1, nm, "|"); for (i=1; i<=n; i++) \ print nm[i], $$0}' \ | $(MAKEDBM) - $(YPDBDIR)/$(DOM)/printers.conf.byname ; \ touch $(DOM)/printers.conf.time; \ touch printers.conf.time; \ echo "updated printers.conf"; \ if [ ! $(NOPUSH) ]; then\ $(YPPUSH) -d $(DOM) printers.conf.byname; \ fi ; \ if [ ! $(NOPUSH) ]; then\ echo "pushed printers.conf";\ fi ; \ else \ echo "couldn't find $(DIR)/printers.conf"; \ fi

## Dependency#printers.conf: $(DOM)/printers.conf.time$(DIR)/printers.conf:#



ProtoServer

The ProtoServer works in conjunction with the name space for LocalFile and NIS naming.

The name service automatically starts the ProtoServer when needed.However, you need to update the file /etc/inetd.conf with the followingline so that the name service can automatically execute theProtoServer:

� On Solaris:

� 105004/1 tli rpc/* wait nobody /usr/sbin/rpc.pts rpc.pts

Changing the name service default

PrintXchange, by default, searches the Local File and then NIS. Tochange this default search order that the system uses, create anentry in the system file: /etc/nsswitch.conf.

The syntax is simple. For example, to get behavior that is the sameas the default behavior, add a line of the form:

printers: files nis

The line must begin with the printers: key. The separatorfollowing can be either space(s) or tabs. The remainder of the lineconsists of a space-separated list of tokens. PrintXchange currentlyrecognizes two different tokens. The two tokens are:

� files

� nis.

If the printers’ entry does not exist in the nsswitch.conf file, or if theparsing code encounters some syntactic anomalies, PrintXchangeuses the default search order.

Because PrintXchange cannot modify NIS entries, if there are noprevious entries in any name service and the default search ordershows nis as the first entry (e.g., printers: nis files ), then thespooler cannot put any new data into NIS and a name service failureoccurs.

To make these changes to the nsswitch.conf file, you must havesuperuser (root) administrator privilege.



NameSpace usage considerations

Local file naming must be used if the site is not using either NIS.When printing objects are created, their binding information isimmediately available; when they are deleted, their bindinginformation is immediately removed. Keep in mind that the usershould not use a machine in local mode while its objects areregistered in NIS.

Since pdcreate only updates the local file naming on the host wherethe pdcreate was executed, the information is not available to clientsor servers on other hosts. Therefore, when using local file naming ina distributed environment, it makes more sense to create theconfiguration file in advance and copy it to all hosts that run clients orservers. The file can be created with an editor or by creating all printobjects from a single host. However, since servers are not createdwith pdcreate , the file must be initialized with the server entries byhand. The file will need to updated on all hosts if an object is deleted.

Since the NIS naming is not dynamic, the configuration must bedefined in advance and used with the NIS makefile utility. Again, theNIS database will need to be updated if objects are deleted.



Planning the component software installation

PrintXchange is a transparent distributed system. The logicalconfiguration described by the relationship between clients, logicalprinters, queues, and physical printers can be implemented innumerous physical configurations; there is no functional differencebetween a PrintXchange system with all the servers on one host anda system where all the servers are on different hosts.

This section provides information that will help you plan thedistribution of software components of the PrintXchange system.

PrintXchange software components

PrintXchange consists of various installable software components forclients and servers:

� Client components

� CLI client

� CLI on-line manual pages

� GUI client

� GUI help files

� Inbound gateway client.

� Server components

� Server core

� Spooler



� Core components

� Utilities

� Printer Attribute Files.

Note : The following system error happens when runningPrintXchange software on Solaris 2.5.1 systems which do not havethe Solaris recommended patch kit installed:

ld.so.1 <binary>:fatal:libresolv.so.2: can’t open file:…

Where <binary> is a PrintXchange executable like“/usr/pd/sbin/pdmakedb”



Network configurations

The configuration possibilities for PrintXchange are numerous.

In a single, standalone system, client and server software may resideand run on the same host.

Figure 5-4. Single, standalone system

In a network printing environment, client and server software resideand run on separate workstations.

Figure 5-5. Printing system in network environment

Host

� Client� Spooler� Supervisor

Printer

Printer

Host A

� Client

Host D(Server)

� Spooler� Supervisor

Host C

� Client

Host B

� Client



The spooler and supervisor may run independently on separatehosts.

Figure 5-6. Client-multiple server system

PrintXchange can service a complex network environment.

Figure 5-7. Complex network environment

Printer1

Host A

� Client

Host D(Server)

� Spooler

Host C

� Client

Host B

� Client

Host E(Server)

Supervisor1

Supervisor2

Printer2

Printer3

TCP/IP Network

SpoolerHostwith

Inbound GatewayClient

ReferenceSupervisor

Host

Printer1

Printer3

Printer2

ClientHost D

ClientHost E BSD Printer

XeroxSupervisor

Host

ClientHost C

ClientHost A

ClientHost B

lp/lprHost



Directory structure

The following list shows the directory structure for the PrintXchangefiles.

� /etc

� printers.conf (for use by Local File name space)

� nsswitch.conf

� inetd.conf

� /etc/dt� GUI action link files

� /etc/rc3.d� Startup scripts

� /usr

� /usr/pd

� /usr/pd/bin

� CLI executables

� GUI executables

� Filter definitions

� /usr/pd/lib� Server executables

� Client notification executable

� Client, server, and gateway libraries

� /usr/pd/dt� GUI action, icon, and help files

� /usr/pd/sbin� Utility executables (pdmakedb, pdmoddb, pdshowdb,

pdaccount)

� /usr/pd/share� Static data

� /usr/pd/share/cap

� Printer attribute files (paf)

� /usr/pd/share/messages/default

� Static data (catalog files)

� /usr/sbin� Protoserver executable (rpc.pts)

� Inbound gateway client executable

� /usr/lib/print� Inbound gateway libraries

� /var

� /var/spool/pd� Dynamic data (spool directories)

� /var/pd� Dynamic data (log, accounting, and ODB directories)



Installing software components

Some guidelines for installing PrintXchange software componentsare:

� You can install client components on all PrintXchange hosts,though you may choose to install only the CLI client componentson server hosts.

� Typically, you will not install server components on client hosts.However, if you choose to install server components on a client,aside from taking up system resources, the host remains as justa client unless you run a server process.

� You will install all server components onto each server host.However, you can choose not to run a server process in order tomaintain server hosts as different server types. That is, do notrun the supervisor process to maintain a spooler-only host; donot run the spooler process to maintain a supervisor-only host.

The following sections provide additional guidelines that may helpyou determine where to install specific software components.

Installing spoolers

The spooler is the central component of a PrintXchange system andconfigurations should be designed around it. A spooler’s host musthave sufficient spooling space for queued jobs and CPU cycles andphysical memory to handle peak printing loads.

PrintXchange supports multiple spoolers, and multiple spoolers allowthe printing load to be distributed across multiple hosts. However, ifspooler host resource is not a concern, it is preferable to have onlyone spooler in a configuration which allows:

� More efficient overall

� One accounting file

� One source for listing printers and queues.

We recommend one spooler per node within a network environment.The total number of servers in the environment is dependent onmany factors including:

� Number of printers

� Number of print jobs

� Number of users

� Type of applications driving the printers

� Types of printers

� Size of machines

� Administrator’s span of control

� Network topology

� User location

� Server location.



Table 5-1. Spooler required system resources

CPU Less than 100 jobs/hour — 100megahertz100 to 500 jobs/hour — 200 megahertz500 to 2000 jobs/hour — 400 megahertz

Physical memory At least 4 megabytes wired memory

Page file At least 15 megabytes

Disk space forsoftware installation

3.14159 megabytes

Disk space fordocument spooling

Depends on maximum job size andmaximum queue length

Disk space for objectdatabase

3.33333 megabytes plus 50 kilobytestimes the maximum queue length

Installing reference supervisors

A PrintXchange spooler can deliver jobs to an unlimited number ofsupervisors and the supervisors can be arbitrarily distributed.However keep the following restrictions in mind:

� If the printer is connected directly to a host (serial or parallel), thesupervisor 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 islimited to 50, so it may be necessary to run more than onesupervisor.

If the spooler and supervisor are on the same host, network filetransfer overhead will be reduced. Therefore, installing supervisorson the same host as their spooler is more efficient.

efficient.

Installing Xerox supervisors

The Xerox supervisor delivers print jobs to other hosts running thelp/lpr printing system or to printers that accepts the BSD protocoldirectly. The overhead per print job using the Xerox supervisor is lowand, again, network traffic and file transfer overhead will be reducedif the Xerox supervisor is installed on the spooler’ host.

The number of printers that a Xerox supervisor can control is limitedto 300.



Installing the inbound gateway

The inbound gateway is used to print jobs coming from users of lp/lprutilities, or from applications that use the BSD protocol. If all printingoriginates from PrintXchange clients, there is no need to install theinbound gateway. A single inbound gateway can handle all inboundjobs and can deliver print jobs to multiple spoolers.

Although the inbound gateway is a client, it is better thought of as aspooler utility. It makes the most sense to install the inboundgateway on the spooler’s host; this will reduce network traffic and file-transfer overhead.

Installing the NT inbound gateways

The NT Inbound Gateways allow native LAN Manager and NetWareclients in an NT domain to submit print jobs to the Solaris domainPrintXchange printers. The Solaris Server Package CD should beinstalled on an NT Server host in each NT domain where native LANManager and/or NetWare clients will use PrintXchange printers.

Refer to the NT SAOG chapter on “Installing and setting upPrintXchange on a server machine” for details on how to install thesoftware on the NT Server host. Refer to the NT SAOG chapter on“Inbound gateways” for an understanding of the gateways and how toconfigure them.

Installing clients

Administrator and operator’s hosts

Hosts that will be used by administrators and operators should installboth the CLI client and the GUI client. The GUI is easier to use butthere are a few administrative functions that it cannot perform, suchas installation of supervisor filters.

End user’s hosts

Workstations used by end users should have the CLI client installed.Many UNIX applications allow user specification of the command tobe executed for printing, and installation of the CLI client will allowpdpr to be executed. If you want to use the PrintXchange GUIClient, you should also install CDE.


6. Installing and setting upPrintXchange on a server machine

This chapter describes how to install the PrintXchange software, andcovers the following topics:

� Overview of the installation sequence

� Solaris packages description

� PrintXchange package description

� PrintXchange installation sequence

� Required installation of Solaris operating system packages

� PrintXchange Solaris installation/removal

� Removing PrintXchange.

Overview of the installation sequence

The specifics of the installation process vary depending on thecomponents being installed. PrintXchange is supported on Solaris2.5.1 and 2.6. It may be installed as a client or as a server.

The client software is comprised of a command line interface (CLI)client and a graphical user interface (GUI) client. The GUI client isoptional. To install as a server, install the desired client softwarefollowed by the additional server software.

Each package is described in the “PrintXchange PackageDescription” section. Installation instructions are divided into twosections:

� Solaris 2.5.1

� Solaris 2.6.

INSTALLING AND SETTING UP PRINTXCHANGE ON A SERVER MACHINE


Solaris packages description

This section describes the required packages that must be installedon Solaris systems from the Solaris installation CD.

SUNWfns - Federated Naming System

This package contains the core XFN naming functionality in Solaris.This is the basis of all naming support in PrintXchange and isrequired for proper PrintXchange operation.

SUNWfnspr - FNS Support For Printer Context (Solaris 2.5.1 only)

This package contains the federated naming support for handlingprinter related configuration data underneath the XFN API. In Solaris2.6 and higher, this package support is incorporated in the SUNWfnspackage.

SUNWisolc - (Solaris 2.5.1 and 2.6)

This package contains support for XSH4 conversion for ISO Latincharacter sets.



PrintXchange package description

The following packages are to be installed from the PrintXchangeinstallation media. They contain all the PrintXchange specificdeliverables.

This section describes the required PrintXchange packages inalphabetical order. All packages that must be installed are includedin the PrintXchange CD.

PXCclient - PrintXchange CLI client

Requires: PXCcore

Description: This package contains the PrintXchange ClientCommand Line Interface and Application ProgrammerInterface. These are the primary interfaces any useror application will access to interact with PrintXchange.

PXCcore - PrintXchange core components

Requires: No requirements needed

Description: This package contains some core PrintXchangecomponents. This primarily includes an OID DB andshare libraries that implement core PrintXchangefunctionality that is common to all areas of the product.

PXCibgw – PrintXchange Inbound gateway

Requires: PXCcore and PXCclient

Description: This package contains PrintXchange inbound gateway– in.bsd-gw, used to print jobs coming from users oflp/lpr utilities or from applications that use BSDprotocol.

PXCman - PrintXchange on-line manual pages

Requires: PXCcore

Description: This package contains all of the on-line manual pagesfor the various PrintXchange commands.

PXCpaf - PrintXchange Printer Attribute files

Requires: PXCcore

Description: This package contains all of the PrintXchange PrinterAttribute files.



PXCsplr - PrintXchange spooler

Requires: PXCcore, PXCsvrcor

Description: This package contains the PrintXchange spooler. Thespooler is a server component that is at the heart ofPrintXchange. It is the repository for all of the printjobs/documents, as well as the logical printers andqueues.

PXCsuperv - PrintXchange reference supervisor


Description : This package contains the PrintXchange referencesupervisor. The supervisor implements all interactionwith the actual output devices.

PXCsvrcor - PrintXchange core server components

Requires: PXCcore

Description: This package contains some core PrintXchange serverspecific components. These components implementinterfaces that are common to the variousPrintXchange servers.

PXCutils - PrintXchange Utilities

Requires: PXCcore

Description: This package contains some PrintXchange utilities.Currently the only utility in this package is dynamicattribute oid utility.

PXCxspvr - PrintXchange Xerox supervisor


Description: This package contains the PrintXchange Xeroxsupervisor. The supervisor implements all interactionwith the actual output devices.

Graphic User Interface packages

This section describes the PrintXchange Graphic User Interface(GUI) packages that must be installed.

PXCdtusr – PrintXchange end user GUI software

Requires: PXCcore, PXCclient

Description: This package contains end user PrintXchange GUIs.



PXCdtush – PrintXchange end user GUI help files

Requires: PXCcore, PXCdtusr

Description: This package contains end user PrintXchange GUIhelp files.

PXCdtadm – PrintXchange administrator GUI software

Requires: PXCcore, PXCclient

Description: This package contains administrator PrintXchangeGUIs.

PXCdtadmh – PrintXchange administrator GUI help files

Requires: PXCcore, PXCdtadm

Description: This package contains administrator PrintXchange GUIhelp files.

PrintXchange installation sequence

The PrintXchange installation sequence is:

1. Name service configuration

2. Security Service configuration

3. Client software installation

4. Spooler software installation

5. Supervisor software installation

6. Additional language installation

7. Gateway installation.



Required installation of Solaris operating system packages

PrintXchange installation requires both Solaris operating systempackages (located on the Solaris Operating System CD) andPrintXchange packages (located on the PrintXchange CD) to beinstalled.

Required Solaris 2.5.1 Operating System Packages

The following must be installed on your system:

� SUNWfns Federated Naming System

� SUNWfnspr FNS Support For Printer Context

� SUNWisolc Conversion for ISO Latin character sets.

Issue the following command to determine if the above packages arealready installed:

pkginfo -i | grep SUNW

Required Solaris 2.6 Operating System Packages

The following must be installed on your system:

� SUNWfns Federated Naming System

� SUNWisolc XSH4 conversion for ISO Latin character sets.

Issue the following command to determine if the above packages arealready installed:

pkginfo -i | grep SUNW



PrintXchange Solaris installation/removal

To install all PrintXchange packages, it is recommended that you usethe “Automated Solaris Installation/Removal Scripts.” You may alsoinstall and remove PrintXchange manually.

Automated Solaris installation/removal scripts

The recommended automated script may be accessed as follows:

1. Login to your SUN SPARCstation system as a user with rootprivileges.

2. Insert the PrintXchange CDROM in a CD reader attached to theSun SPARCstation.

3. Issue the following command:

cd/cdrom/pxc_*/solaris_*

4. Use the provided readme file within the CD as a reference.5. Issue the following command:

InstallPXC

6. Follow the instructions on your screen.

Manual Solaris installation/removal scripts

Note : You can install all PrintXchange packages at once using thefollowing procedure. For installation of specific packages refer to theappropriate package you want to install and follow the on screeninstructions.

1. Become a superuser (root).

pkgadd -d location_of_packages PXCcore PXCutilsPXCsvrcor PXCsplr PXCsuperv PXCxspvr PXCpafPXCclient PXCman PXCibgw PXCdtusr PXCdtusrhPXCdtadm PXCdtadmh:

2. Press ENTER.

3. Answer "Y" to all questions..

Client or Server Installation on Solaris 2.5.1 or 2.6

All PrintXchange packages are located in the “package directory” onthe PrintXchange installation CD.

1. Login as superuser (root).

Note: The PXCcore package must be installed prior to theinstallation of all other PrintXchange packages.



2. Type the following commands to install the PrintXchange basicCLI client for a client or server, replacing “package directory” withthe path of the PrintXchange package directory:

pkgadd -d package directory PXCcore PXCclientPXCman

3. Press ENTER.

You will be notified of the successful installation of the packages.

4. Type the following command to install printer attribute filesneeded for printer administration:

pkgadd -d package directory PXCpaf

Note : This software is used with the client software on theadministrator's system and is mandatory for server installation.

Additional GUI installation on Solaris 2.5.1 or 2.6

Type the following commands to install PrintXchange as a server,replacing “package directory” with the path of the PrintXchangepackage directory:

pkgadd -d package directory PXCdtusr PXCdtusrhPXCdtadm PXCdtadmh

Note : After installing Solaris GUI packages via pkgadd command(pkdadd –d PXCdtusr), .the following error message appears “Can’topen display”. Although “pkgadd” still displays the message, thefunctionality is correct.

Server Additional Installation on Solaris 2.5.1 or 2.6

Type the following commands to install PrintXchange as a server,replacing “package directory” with the path of the PrintXchangepackage directory:

pkgadd -d package directory PXCsvrcor PXCsplrPXCsuperv PXCxspvr PXCibgw

Note : When prompted to continue installation of scripts foruse with superuser (root), enter "y" for yes.

Removing PrintXchange

To remove PrintXchange from UNIX, do the following:

1. Become superuser (root).

pkgrm PXCman PXCpaf PXCsuperv PXCxspvr PXCsplrPXCdtadm PXCdtadmh PXCdtusr PXCdtusrh PXCibgwPXCclient PXCsvrcor PXCutils PXCcore

2. Press ENTER.

You will see a message informing you about the package youcurrently removed.



3. Confirm that you want to remove each package by answering "Y"to all questions.

4. Press ENTER.

Once removed, you will be informed of the successful removal ofcertain packages.

Note : You may be asked whether you want to continue with theremoval of the PrintXchange packages. The options are:

Y = RemoveN = Not to remove? = HelpQ = Quit the uninstall process

A final message will let you know of the successful removal of thelast PXC package you designated.


7. Managing security

Underlying all basic PrintXchange components is an infrastructurethat enables them to function. This chapter examines theinfrastructure of PrintXchange and covers:

� NIS name service

� Security

� Access control lists

� Defining event notification

� File transfer.

Name Services

A name service:

� Contains named network objects (spoolers, supervisors, logicalprinter, physical printers, queues) defined by the administrator,each object contains a reference to the network address of theserver that supports it.

� Serves as the vehicle that clients use to locate and bind to aserver 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, andqueues defined in the printing environment.

� Servers use the name service to locate others servers.

PrintXchange supports two name services for UNIX clients andservers in the ONC RPC environment:

� Network Information Service (NIS), a distributed naming method.

� The UNIX server ProtoServer works in conjunction with the namespace for Local File and NIS naming to enable a server to accessname space information while PrintXchange is running.

Note : If both local file naming and NIS are used, make sure that thenames are unique and avoid duplicate names. Distributingprinters.conf file to all users and using it for NIS will cause duplicationin name service entries. The names in the /etc/printers.conf.fileshould be different than the names in the NIS server. If every oneuses the NIS defined object, then there is no need for local filenaming.

For additional information on naming files, refer to the “Printers.conffile” appendix.

MANAGING SECURITY


Security

Security has two components:

� Authentication which ensures that users are who they claim tobe.

� Authorization which ensures that users have permission toperform a particular operation.

Both components use the information in the access-control-listattribute for validation. One of your tasks when you initially set upyour PrintXchange system is to set the privilege levels for all users.Do so by setting the value of access-control-list . OncePrintXchange is up and running, you will need to modify access-control-list as you add or remove users or change their privilegelevels.

Note : name-type=netgroup restricts specific users to specifichosts, so it is probably an option you would use for operators andadministrators.

Authentication

Authentication is the key to security. Authorization to allow a user todo an operation is meaningless if the system does not reliably identifythe user. In a distributed application, authentication generallydepends on the underlying network communication services.

Authentication in PrintXchange occurs as part of the RPCcommunication between the client and the server.

PrintXchange uses only ONC RPC and relies upon the ONC RPCbuilt-in authentication methods. The authentication methodsupported by PrintXchange is defined in the RPC-binding entry withinthe NameSpace. The only authentication method supported byPrintXchange is sys , the standard UNIX authentication.

The user identifier (UID) is sent to the server as part of the RPC. Ifsys authentication succeeds, the server looks up the UID in thedomain’s password file and the returned value is used for comparisonagainst the entries in the PrintXchange server’s access-control-list(ACL) attribute. On a print operation the user-name retrieved by thespooler during authentication is used as the name portion of the job’suser-name attribute value. The name-syntax portion of this value isomitted.

If sys authentication fails, the operation is considered to be cross-domain. In the PrintXchange cross-domain environment, the user isauthenticated using PrintXchange proxy authentication. The username, user domain, hostname, and host domain provided by thePrintXchange proxy authentication are used for comparison againstthe entries in the PrintXchange server’s access-control-list (ACL)attribute. On a print operation, the job’s user-name attribute is setaccording to the following cases:

� A local user (/etc/passwd account):

onc-file:user@hostname

where “hostname” is identical to the value returned by the UNIXuser command hostname(1) when run on the client machine.

MANAGING SECURITY


� An NIS domain user printing to a server in a different NISdomain:

onc-nis:user@domain

where “domain” is identical to the value contained in the/etc/defaultdomain file on the client machine.

Note : The proxy user domain value is used for matching against theACL domain value if the ACL domain value name-syntax is onc-fileor onc-nis . If the client is run by a local user (/etc/passwd account),the proxy user domain is onc-file:hostname . If it is run by a NISuser, the proxy user domain is onc-nis:domain .

The proxy host domain value is used for matching against the ACLdomain value if the ACL domain value name-syntax is dns . If theclient is run on a machine supporting DNS (i.e. a /etc/resolv.confexists), the proxy host domain is dns:hostname.domain , where thehostname portion is the value returned by running the UNIX usercommand hostname(1) on the client machine and the domainportion is the “domain” value contained in the /etc/resolv.conf file onthe client machine.

Since authentication uses the password database, PrintXchangedoes not support cross network domain authentication. Therefore,cross-domain submissions are authorized solely based on theaccess-control-lists, allowing access to users from domains otherthan that of the server. In other words, by default, only users local tothe server have access to the server. In order to allow cross-domainsubmission, the system administrator must enter an ACL for theserver object allowing access to users from the foreign domain. Forthe correct syntax, refer to the section on “Creating ACLs” in thischapter.

Authorization

Authorization validates that users have permission (or authority) toperform tasks they attempt to perform. Users’ privilege levelsdetermine what they can do. Clients (users) of PrintXchange havethree privilege levels:

� System Administrator

� Operator

� End user.

The user privilege levels have an access order:

� An Administrator can configure objects and perform all Operatortasks.

� An Operator can control printing and perform all End user tasks.

A fourth category of PrintXchange users is local-root. This is the rootuser (i.e., UID 0) on the server’s host. A local-root user hasAdministrator privileges for all objects regardless of the value of theaccess-control-list attribute. Also, local-root is the only categorythat can start servers.

Table 7-1 summarizes the capabilities of each privilege levelaccording to PrintXchange tasks.

MANAGING SECURITY


Table 7-1. PrintXchange privilege levels per task

Tasks Command Description Minimum PrivilegeLevel

Pertinent Objects

Clean pdclean Delete all jobs from anobject

Operator Spooler, queue

Create pdcreate Create objects and setinitial attributes

System administrator Logical printer, queue, physicalprinter, initial-value-jobs, initial-value-documents

Delete pddelete Delete objects System administrator All except documents

Disable pddisable Disable the acceptanceof new print requests

Operator Logical printer, spooler, queue,supervisor, physical printer

Enable pdenable Enable the acceptanceof new print requests

Operator Logical printer, spooler, queue,supervisor, physical printer

Listattributes

pdls List the names of printobjects and the namesand values of theirattributes

End user All

Modify pdmod Change the values of jobor document attributes

End user Job, document

Pause pdpause Pause an object so thatit does not continueoperation

End user (job owneronly)

Operator (all)

Job, spooler, queue, physicalprinter

Print pdpr Send a document or jobto print

End user Logical printer

Promote pdpromote Move a document or jobto the head of its queue

Operator Job

List jobqueue

pdq List document or jobstatus attributes

End user Document, job

Resubmit pdresubmit Move a job to anotherlogical printer

End user (documentor job owner only)

Operator (all)

Job, queue

Resume pdresume Resume a paused objectso that it picks upoperation where itstopped

End user (documentor job owner only)

Operator (all)

Spooler, queue, physicalprinter, job

MANAGING SECURITY


Access Control Lists (ACLs)

Administrators may set Access Control Lists (ACLs) for allPrintXchange objects (except document and job objects). Typically,however, you set server ACLs only. The server ACL specifies theaccess to all objects belonging to the server that do not have an ACL.

In exceptional cases, ACLs may be set for specific objects (otherthan servers) to further restrict access to those objects.

If an object has an ACL, then the values for a given privilege-levelare used. If the object ACL does not have any values for a givenprivilege-level, then the server ACL values for only that privilege-levelare used. Therefore, you could set end user privilege-level ACLvalues on a logical printer to restrict submission to that printer.However, if the ACL for that logical printer did not have anyadministrator values, then the administrator privilege-level serverACL values would be used for administrator operation authorizationon that logical printer.

Defining ACLs

PrintXchange objects have ACLs that control access to objects. Theaccess-control-list attribute defines server ACLs.

Use the pdset command to create a server ACL. The syntax is:

pdset -c class -x “access-control-list={name= valuename-type= value domain= value privilege-level= value }” object_name

Brief explanations of the attribute parameters are below. For detailson all CLI commands, refer to the PrintXchange Command LineInterface Reference Guide.

name This option specifies the user’s name.

name-type This option specifies the type of user. The legal values are:

� all-users

� user

� group

� netgroup.

domain This option specifies the domain name

privilege-level This option specifies the access level of the user. The legal valuesare:

� end user

� operator

� administrator.

MANAGING SECURITY


The following examples illustrate setting an ACL:

� The following example first removes access from all users to“printer1” and then grants end user access to the “odyssey”group:

pdset -c printer

-x access-control-list-=”{name-type=all-users}”

-x “access-control-list+=”{name=odyssey

name-type=group privilege-level=end-user}”

printer1

� This example specifies that user ID mary has access to spooler1:

pdset -c server-x access-control-list=”{name=mary}” spooler1

Since this example does not specify name-type , name-typedefaults to group , and since it does not specify privilege-level ,privilege-level defaults to end-user .

This is equivalent to:

pdset -c server-x access-control-list=”{name=maryname-type=group privilege-level=end-user}” spooler1

� This example removes the user ID tom from the operatorprivilege level on supervisor1:

pdset -c server-x access-control-list-=”{name=tomname-type=user privilege-level=operator}” supervisor1

� This example makes spooler1 available to all users of anydomain:

pdset -c server -x access-control-list="{\

name-type=all-users \

domain=any:}" spooler1

� Example of cross-platform cross-domain printing where all winntusers in xeroxcsg domain can access print devices of spooler1server:



domain=winnt:xeroxcsg}" spooler1

� Example of providing access to printer1 to mary in midwestdomain:

pdset -c printer -x access-control-list="{\

name=mary \

domain=midwest}" printer1

MANAGING SECURITY


Rules for using these options are:

� If you specify name but not name-type , name-type defaults togroup .

� If you specify neither name nor name-type , name-type defaultsto all-users .

� If you do not specify privilege-level , privilege-level defaults toend-user .

� If name-type=all-users , the server ignores name . This meansthat the server accepts any request for the specified privilegelevel.

� 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

� A member of the netgroup, if name-type=netgroup

Note : name-type=netgroup restricts specific users to specifichosts, so it is probably an option you would use for operators andadministrators.

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={namedomain name-type privilege-level}” spooler_name

or

pdset -c server -x “access-control-list={namedomain name-type privilege-level}”supervisor_name

field description

name User’s name

name-type Type of user:all-usersusergroupnetgroup

privilege-level Type of access level:end useroperatoradministrator

� If name-type is all-users , the server ignores name .Therefore, the server accepts any request for the specifiedprivilege level.

� If you do not specify name , and if you also do not specifyname-type , then the server sets name-type to all-users .

MANAGING SECURITY


If name-type is other than all-users , you must specify name .Also, the name of the user (as determined by looking up the UIDin a password file) making the request must be:

� An exact match to name , if name-type =user .

� A member of the group, if name-type =group .

� A member of the netgroup, if name-type =netgroup .

It is likely that you will use the netgroup value of name-typeprimarily for Operator and Administrator privilege levels, since it canrestrict specific users to specific hosts.

Creating access control lists using GUI

To create access control lists:

1. Run the pdprintadmin application.

2. Select User Administration from the Tools menu.

3. Select the object type: Spoolers or Supervisors.

4. Select the privilege-level (shown as User Class in the window).

MANAGING SECURITY


5. Select the name-type :

� Select Everyone for name-type=all-users , or

� Select Specified Users, select the Add... button, then selectthe name-type (shown as User Type in the window).

6. Enter the name .

7. Select OK.

MANAGING SECURITY


Default ACL

The default ACL has two values:

1. name-type=all-users ; privilege-level=end-user

2. name=sysadmin ; name-type=group , privilege-level=administrator

When you create a server, the server sets the two values for its ACL(unless you set an administrator value ACL with the -A startupoption).

If the domain does not include a group named sysadmin, the local-root user needs to set the server’s ACL to a locally correct value.

Example: To reset access-control-list to the default using the CLI:

pdset -c server -x “access-control-list=“spooler_name

The example replaces the specified object’s ACLs with the twodefault values listed above, regardless of what is locally correct.

ACL without privilege specification

When an ACL does not specify a privilege level, valid authorization isas follows:

� When an ACL does not specify Administrator privilege, only local-root has authority to perform administrative operations.

� When an ACL does not specify Operator privilege, as in thedefault values, a user must have Administrator privilege toperform operator or administrative operations.

� When an ACL does not specify End-user privilege, a user musthave Operator or Administrator privilege to perform End-useroperations.

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=groupprivilege-level=end-user}” spooler1

If name is specified and name-type is not specified, name-typedefaults to group . If privilege-level is not specified, it defaults toend-user .

Example 2 To set the ACL on “spooler1” so that only members of the dpt groupare operators. Since this operation wipes out any existing values onthe ACL, only local-root can delete the server:

pdset -c server -x”access-control-list={name=dpt}” spooler1

Example 3 To remove the user “ginger” from the approved operators forsupervisor1.

pdset -c server -x “access-control-list-={name=ginger name-type=userprivilege-level=operator}” supervisor1

Example 4 : To make all objects on the “spooler1” server available to all users.

pdset -c server -x “access-control-list+={name-type=all-users}” spooler1

An operator included with the attribute type= value pairs indicatesthe type of modification to be done to the specified attribute. The formof the attribute type= value pairs for pdset is:

attr[+ | – | =]=val, where

attr Attribute type

MANAGING SECURITY


Modification operator

You can include an operator with attribute=value pairs to indicate thetype of modification to be done to the specified attribute. The threemodification 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 avalue that already exists, the attribute contains the same valuetwice.

� - (remove value)

When you use attribute-=value, you remove a value to theattribute. If the value is not present, pdmod ignores thecommand. If you remove the last value for an attribute, pdmodsets the value to the server default. If a value to be removedoccurs more than once. pdmod removes all occurrences.

� = (reset to default value)

When you use attribute==value, you set the attribute value to itsdefault. Do not include a value for when resetting to the defaultvalue.

MANAGING SECURITY


File transfer

The file-transfer mechanism determines how a document or job getsfrom the client to the spooler, and from the spooler to the supervisor.PrintXchange builds file security in to file transfers by ensuring thatusers can access only those files for which they have read access. Ifthe 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 thedocument data to the spooler as part of the print request. Thespooler copies the data into its spool directory.

� socket

The client, after checking the accessibility of the file, sends theprint request to the spooler. The spooler returns socketinformation, used by the client to connect and write the documentdata, to the socket. The spooler reads the data from the socketand writes it to its spool directory.

� file-reference

The client, after checking the accessibility of the file, sends the printrequest to the spooler along with a file-path reference. The spoolercopies the file into its spool directory.

Note : If the user does not have read access to the file, the printrequest fails.

When the spooler transfers document data to a supervisor on thesame host, it uses the file-reference mechanism. If the spooler andsupervisor are not on the same host, or If the print request does notspecify a file-transfer mechanism, the spooler uses the followingdefault algorithm:

If file size <10,000 bytes, with-request is used.

Otherwise socket is used.

MANAGING SECURITY


Transfer methods

When you submit a print request from a client, the client transmits therequest to the spooler. The request indicates how the print dataassociated with the print request will reach the spooler. Whenprocessing the incoming print request, the spooler checks thetransfer-method attribute to determine what it should do to receivethe print data.

PrintXchange supports three methods that determine how print datareaches 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. Ifthe print request does not specify a transfer method, the spooler usesthe following algorithm to determine the default:

� If the file size is less than 10,000 bytes, the spooler uses thewith-request transfer method.

� Otherwise, the spooler uses the socket transfer method.

� The GUI does not provide access to the transfer-methodattribute. All print requests originating with the GUI use thedefault transfer method.

with-request transfer method

The client sends the document data to the spooler directly as part ofthe print request. The spooler copies the document data to its spooldirectory. The with-request transfer method is valid only for jobs upto 1 MB in size. The print job submission does not complete until theclient 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 returnssocket information. The client then connects and writes the documentdata to this socket. The spooler reads from the socket and writes thedata to a file in the spooler’s spool directory. The print job submissiondoes not complete until the client completely transfers the documentdata to the spooler.

To set a socket transfer method:

� CLI:

pdpr -x "transfer-method=socket" filename

� GUI:


MANAGING SECURITY


file-reference transfer method

The client sends a file path reference for the document to thespooler. Before returning from the print request, the spoolerdetermines if it can reference the document. If the spooler cannotreference the document, the print request fails.

To set a file-reference transfer method: x

� CLI:

pdpr -x "transfer-method=file-reference"< filename >

<filename> gives an absolute path.

� GUI:


Spooler-to-supervisor file transfer and default method

When the spooler transfers document data to the supervisor, thespooler determines if the supervisor is on the same host and, if so,the spooler uses the file-reference transfer method. Otherwise, thespooler uses the same algorithm that it used with the client:

� If the file size is less than 10,000 bytes, the spooler uses thewith-request transfer method.

� Otherwise, the spooler uses the socket transfer method.

File security

PrintXchange ensures that users can access only files for which theyhave read access.

If the user specified the with-request transfer method,the clientchecks the accessibility of the file just before including the file oninitiating the print request. If the user specified socket transfermethod, the client checks the accessibility of the file just beforesending the file over a socket. In both cases, if the user does nothave access, the print request utility fails. In addition, if the userspecified the file-reference transfer method with the print request,the spooler ensures that the original user still has read access to thefile. This is to ensure that the file is not modified between the time ofthe print request and the time the spooler copies the file.

MANAGING SECURITY



8. Setting event notification

Event notification

PrintXchange reports system problems or interesting events to usersthrough notification services. Events are reported to the user by e-mail or an immediate message. If you request notification of a classof 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 reportedand the delivery method. Users can specify a notification-profile forthe 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 setattribute (pdset/pdmod) operations. An End User can specify profilesfor a job at job submission time using the pdpr operation.

Events

Users can specify events by class or by specific events. If thenotification-profile attribute specifies a class, the correspondingnotification service reports all events of that class. Table 8-1 lists theevents, their classes, the objects to which they apply, and thecorresponding messages that are supported in PrintXchange.

Note : The set of events logged varies, depending on the printer typeand communication interface.

SETTING EVENT NOTIFICATION


Table 8-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, theadministrator 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-statusreport-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-attentiondocument-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-attention

Job The printer assigned to the job needs 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-statusreport-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)



Table 8-1. Events (continued)


report-job-data-change Job The job encountered a data change on the followingdata:

printers-assignednotification-profilecurrent-job-statejob-namejob-priorityjob-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-attentionwarning-assigned-printer-needs-attention


warning-printer-needs-attention Printer The printer needs attention. The message will includeadditional information on the problem:

cover-openduplex-failinput-tray-failjammedno-cassetteno-drumoutput-bin-fulloutput-tray-failservice-requestedother

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-statusreport-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.





report-printer-data-change Printer The printer encountered a data change on thefollowing data:

printer-nameprinter-locationsprinter-statemaximum-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-attentionwarning-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-statusreport-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 ‘...’.reportreport-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 followingdata:

printers-assignednotification-profilecurrent-job-statejob-namejob-priorityjob-discard-time

report-job-discarded Job The server has discarded the job. The retentionperiod 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

ServerThe object has been cleaned.





report-object-created DocumentJobPrinterQueue

The object has been created.

report-object-deleted DocumentJobPrinterQueueServer

The object has been deleted.

report-object-modified DocumentJobPrinterQueueServer

The object has been modified.

report-object-paused JobPrinterQueueServer

The object has been paused.

report-object-resumed JobPrinterQueueServer

The object has been resumed.

report-printer-data-change Printer The printer encountered a data change on thefollowing data:

printer-nameprinter-locationsprinter-statemaximum-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-printerset-logical-printerdelete-logical-printeradd-physical-printerset-physical-printerdelete-physical-printeradd-jobset-jobdelete-job

report-server-shutdown-started Server The server has started a shutdown operationreport-server-startup-complete Server The server has started.





server-attentionerror-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-statusreport-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-printerset-logical-printerdelete-logical-printeradd-physical-printerset-physical-printerdelete-physical-printeradd-jobset-jobdelete-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-changedstate-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)





warningwarning-assigned-printer-needs-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-openduplex-failinput-tray-failjammedno-cassetteno-drumoutput-bin-fulloutput-tray-failservice-requestedother

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.



Notification server

Notification is handled by a notification server that runs on every hostthat runs a server; the notification server is not needed on a client’shost.

The notification server is expected to start automatically by addingthe following line to /etc/inetd.conf:

105005/1 tli rpc/* wait root /usr/pd/lib/pdntfspdntfs

The notification server automatically exits after 120 seconds of idletime. Administrators should use SIGTERM rather than SIGKILL whenstopping the notification server manually.

The notification server tries to open the object database(hostname.ntfy) in the standard directory at startup. If it fails, thenotification server exits.

To use immediate message notification, the “ttsession” process mustbe running on the client’s host. This process generally resides in/usr/openwin/bin on Solaris. Also, the administrator has to run xhost+ serverName on the console of the CLI or GUI client, and restart theinetd daemon.

There is no configuration required to use immediate messagenotification for socket-event.

To use email notification, the sendmail daemon must be running onthe server’s host. For CLI clients, the notify console daemonpdconntf must be running on the client host.

The notification server uses the following startup parameters forservice logging configuration:

� -l <severity> Specifying severity.

� -f <log file path> Specifying log file path.

If both startup parameters and environment variables are provided,the startup parameters take precedence. For details on servicelogging, refer to the “Troubleshooting” chapter in this guide.



Specifying profiles

You can define notification profiles for servers, queues, logical andphysical printers, jobs, and documents using the GUI or CLI.Subsequent chapters refer you to this section to define event-notification profiles for other objects.

Specifying profiles using GUI

The GUI includes event notification management windows to setnotification profiles and preferences.

To specify profiles:


2. Select Event Notification in the Tools menu.

3. Select the E-Mail or Screen tab.

4. Enter all relevant field values for the corresponding deliverymethod, E-Mail (email ) or Screen (message ).

5. Select Close .



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-identifiersdelivery-method event-comment delivery-address locale}”object_instance…

where:

class_name object_instance

server spooler_nameserver supervisor_namequeue queue_nameprinter (default) logical_printer_nameprinter physical_printer_namejob [spooler_name:]job_identifier

The syntax for multiple values is:

pdset -c class_name -x "notification-profile={event-identifiersdelivery-method event-comment delivery-address locale} {event-identifiers delivery-method event-comment delivery-addresslocale}" object_instance

Brief explanations of the attribute elements are below. For details onall CLI commands, refer to the PrintXchange Command LineInterface Reference Guide.

The notification-profile attribute is multi-valued. Each valuecontains the following fields:

field description

event-identifiers A list of event types or event classes. A usercan obtain a list of the events by executing alist (pdls) operation on the server object forthe events-supported attribute. If this fieldis omitted, then all events are reported for theobject.

delivery-method Specifies how the messages are to bedelivered. The supported values are:

� smtp-mail (the CLI alias is email )

� notification-service , default (the CLIalias is message )

� socket-event

The delivery method electronic-mail is alsosupported for PrintXchange 1.0 backwardcompatibility. The notification serverhandles the electronic-mail delivery methodin the same way as smtp-mail .

event-comment A comment included in the notificationmessage. There is no default.



field description

delivery-address The address where the notification is to besent.

� For smtp-mail (email or electronic-mail ) notification, the format for theaddress is:

<user>@<mail domain name>

For example: “[email protected]”

If no address is specified for smtp-mail ,the current user is the default.

� For notification-service (message )notification, the format of the address is:

<ip address> or the host name

For example:

“13.1.97.25” or “huffalump”

If no address is specified fornotification-service, the local host(current node) is the default.

� For socket-event the format of theaddress is:

hostname:portaddress

For example: “gladiolus:2000” or“13.240.96.194:2000”

There is no default address for socket-event . The user must provide anappropriate delivery-address in thecommand line.

locale Specifies the locale the server uses whenconstructing the message. If omitted, theclient provides the appropriate value.

notification-profile A complex attribute specified in the CLI withcurly-brace syntax. For example:

-x “notification-profile += {event-identifiers=aborted state-changed-server delivery-method=smtp-mail event-comment=‘Something\’s up’ delivery-address=agreen@ospreylocale=en_US.ASCII}”



The delivery-method and delivery-address components mayalso be specified by using the aliases or by setting them explicitlywith the -x flag, as follows (square brackets [ ] indicate optionalparameters):

-x “notification-profile=smtp-mail[:<address>]“-x “notification-profile=email[:<address>]“

-x “notification-profile=notification-service[:<address>]”-x “notification-profile=message:[<address>]“

-x “notification-profile=socket-event:<address>”

-x “notification-profile=electronic-mail[:<address>]“

Since notification-profile is a multi-valued attribute, events canbe reported to more than one user. A value of notification-profile is needed for each user. Although only an Administratorcan set notification-profile , any user can be specified forreceipt of the notification messages. When specifying multiplevalues using the curly brace syntax, each specification must bewithin the curly braces and the entire specification enclosed inquotes: For example:

-x “notification-profile={profile1} {profile2}”

If a notification-profile is not specified when an object is created, nodefaults are provided. Defaults are only supplied for missing fieldswithin a notification-profile .

If a user specifies the -N notification_method flag with the pdprcommand, the client sets the event-identifiers field to ‘report-job-completed aborted’. The other fields are filled with the valueappropriate to the delivery method.

For example : The example causes PrintXchange to deliver by emailto agreen@osprey 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 notificationmessages 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=agreen@osprey locale=en_US.ASCII}”spooler1



Delivery methods

PrintXchange delivers notifications as:

� Electronic mail

� An immediate message.

Electronic mail

The server sends a message with the subject line indicating theobject and event. The body of the mail note repeats this informationand includes the event-comment . A sample message is as follows:

Date: Mon, 21 Sep 1998 12:27:40 -0700From: [email protected] (Super User)Subject: PrintXchange notification - root_spl:1Sender: [email protected]: 1.0Content-Type: text/plain; charset=“us-ascii”Content-Transfer-Encoding: 7bitContent-Length: 85

Object: root_spl:1Message: The print job completed on printer root_PP at 12:00

Note : The PrintXchange Solaris server handles only mail addresseshaving an RFC-822 syntax (aka Internet mail addresses).

Message

The result of the notification-service (message ) delivery methoddiffers by client type:

CLI clients For a CLI client PrintXchange delivers the message by writing themessage to the console of the client’s host. Therefore, the user musthave a console window to see the messages.

Note, however, that for messages to appear in a console window ofthe CLI client, two actions have to take place:

� You have to run xhost + serverName at the console so that theCLI can receive the messages.

� The pdconntf (pd-console-notify) daemon has to run on the clientto enable the CLI to display the messages in a console window.The daemon starts automatically at boot time when the clientmachine starts up.

Note : Note that the pdconntf daemon could be started multipletimes on the same system. This causes pdconntf to sendmultiple copies of status messages to the system console.

GUI Clients For the GUI client, events cause PrintXchange to update the GUI. Ifthe status of an object has changed and user intervention is needed,PrintXchange modifies the icon for that object to indicate to users thattheir attention may be required. Up-to-date information on an objectis available via the GUI client while the application is running.



Note : Note that, as for the CLI client, you have to run xhost +serverName at the console so that the GUI can receivemessages.


9. Configuring, starting andstopping servers

This chapter describes the procedures for configuring, starting andstopping servers. Installing PrintXchange on UNIX is done via anautomated UNIX shell script located on:

/usr/pd/install_scripts

For a complete description of the configuration process used in theUNIX shell script, refer to the “Configuration information summarysheet” in this chapter. The process includes:

� start_servers

� enable_servers

� create_printers

� display_gui

� S40PXC.servers.

In addition, details on stopping, shutting down and restarting thePrintXchange system are described.

Details on creating and enabling other PrintXchange objects aredescribed in the following chapter, “Creating and configuring queues,physical printers and logical printers.”

CONFIGURING, STARTING AND STOPPING SERVERS


Process/configuration flow

[Select any valid name for your server]

1. Create server object database

� Start server

� Enable server.

[Select any valid name for your queue]

2. Create queue

� Enable queue.

[Select any valid name for your Physical printer]

3. Create Physical printer

� Enable Physical printer.

[Select any valid name for your Logical printer]

4. Create Logical printer

� Enable Logical printer.

5. Ready to print!

Note : Valid names for queues, logical printers, physical printers,servers (spoolers and supervisors) must be unique within thedomain. For example: Hosts “able” and “baker” may not each have aqueue with the same name “color_q”.

Valid object names may consist only of the following characters:

� A – Z

� a – z

� 0 – 9

� hyphen ( - )

� underscore ( _ ).



Configuration information summary sheet

This configuration information summary sheet will assist you in following the flowof this chapter.

Create and start servers

Using shell script: # usr/pd/install_scripts/start_servers

Using CLI: # /usr/pd/sbin/pdmakedb –n <spooler_name>

# /usr/pd/sbin/pdmakedb –t SUP –n ref_sup_name>

# /usr/pd/sbin/pdmakedb –t SUP <xerox_sup_name>

# /usr/pd/lib/pdsplr <spooler_name>

# /usr/pd/lib/pdspvr <ref_sup_name>

# /usr/pd/lib/pdxspvr <xerox_sup_name>

Enable servers

Using shell script: # /usr/pd/install_scripts/enable_servers

Using CLI: # /usr/pd/sbin/pdenable -c server <spooler_name>

# /usr/pd/sbin/pdenable -c server <ref_sup_name>

# /usr/pd/sbin/pdenable -c server <xerox_sup_name>

Create and enable queue, physical printer, and logical printer, in that order

Using shell script: # /usr/pd/install_scripts/create_printers

Using CLI: # /usr/pd/sbin/pdcreate -c queue <spooler_name>:<queue_name>

# /usr/pd/sbin/pdenable -c queue <spooler_name>:<queue_name>

# /usr/pd/sbin/pdcreate -c printer \

-x printer-address=<printer_address> \

-x associated-queue=<queue_name> \

-X /usr/pd/share/cap/ HP_ColorLaserJet_Level2PS.paf\<ref_sup_name>:<physical_printer_name>

# /usr/pd/sbin/pdenable -c printer <ref_sup_name>:<physical_printer_name>

# /usr/pd/sbin/pdcreate -c printer \

-x associated-queue=<queue_name> \<spooler_name>:<logical_printer_name>

# /usr/pd/sbin/pdenable -c printer <spooler_name>:<logical_printer_name>



Creating, starting, and enabling servers

This section explains creating, starting, and enabling servers whichapplies to all servers:

� Spooler



Creating a server consists of three steps:

1. Creating the object database for the server object. The section“Managing the object database” in the “Working with objectdatabases” appendix, provides details on managing the objectdatabase, which includes creating, modifying, and displaying theobject database.

2. Starting the server by running the server executable. The“Starting the database” section provides details on the optionsavailable for the server executable commands.

3. Enabling the server. The “Enabling and disabling servers”section provides details on this step.

Creating the object database (pdmakedb)

Use the pdmakedb utility to create an object database. Creating theobject database also creates the server object. You must create anobject database before you can start (run) the corresponding serverthat uses the database.

� To create a spooler database, select any name for your spooler:<spooler_name>= floor1_spl, and enter:

/usr/pd/sbin/pdmakedb –n floor1_spl

� To create a Reference supervisor database, select any name foryour supervisor: <ref_sup_name>= floor1_sup, and enter:

/usr/pd/sbin/pdmakedb –t SUP –n floor1_sup

� To create a Xerox supervisor database, select any name for yourXerox supervisor: <xerox_sup_name>= floor1_ xsup, andenter:

/usr/pd/sbin/pdmakedb -t SUP -n floor1_ xsup

The pdmakedb utility creates an object database that initiallycontains a single object, the corresponding server object. The nameof the database is also the name of the server object (note the -nswitch). The utility adds default attributes to the server object, plusany attributes you specify via the pdmakedb switches.

The pdmakedb utility displays an error message and exits if thedatabase you specify already exists.

For detailed information on the pdmakedb utility, refer to the“Working with object databases” appendix in this guide.



Starting servers

Starting a server consists of running an executable file for eachserver type. The startup syntax represents a string that you can typeat a shell prompt. Generally, however, you will start servers via ashell script, and the host will execute the startup syntax from withinthe shell script. The shell script is part of the startup scripts that youcreate and that execute normally when a UNIX system reboots. The“Managing jobs and documents” chapter provides guidelines forcreating scripts.

� To start a spooler named floor1_spl , enter:

/usr/pd/lib/pdsplr floor1_spl

� To start a Reference supervisor named floor1_sup , enter:

/usr/pd/lib/pdspvr floor1_sup

� To start a Xerox supervisor named floor1_ xsup , enter:

/usr/pd/lib/pdxspvr floor1_ xsup

A PrintXchange server behaves like a UNIX daemon. It starts up atboot time via the shell script and does not require user input to beable to start up. Like typical UNIX daemons, the server starts up inthe background and runs relative to a runtime directory.

Server startup exit status codes

If the server starts up normally, without encountering any errors, thenthe server starts waiting on client requests and processes thoserequests as they come in. If the server encounters an error duringstartup, it prints out an error message to standard error and exits witha non-zero exit status. For details on server start-up exit statuscodes, refer to the “Server startup exit status codes” in the “Serverstartup commands, switches, and status codes” appendix.

Enabling servers

Once a server database is created and started you must enable thespooler, Reference supervisor and Xerox supervisor.

� To enable a spooler named floor1_spl, enter:

/usr/pd/sbin/pdenable -c server floor1_spl

� To enable a Reference supervisor named floor1_sup, enter:

/usr/pd/sbin/pdenable -c server floor1_sup

� To enable a Xerox supervisor named floor2_xsup, enter:

/usr/pd/sbin/pdenable -c server floor1_ xsup

Create and enable queue, physical printer, and logical printer, in that order

Details on creating and enabling PrintXchange objects, queues,physical and logical printers, are described in the following chapter,“Creating and configuring queues, physical printers and logicalprinters.”



Shutting down and restarting a server

Shutting down a server

Once a server is running, there are two primary ways to shut it down:

� An administrator can send a shutdown request via thepdshutdown command.

� An administrator can use the start/stop script to shutdown ALLPrintXchange servers.

� A privileged user can send it a UNIX signal that would cause it toexit.

If the server receives a shutdown request or it receives the UNIXSIGTERM signal, the server attempts to gracefully shut down. Thisincludes attempting to put the object database in a consistent statebefore exiting. The shutdown request also allows the server to delaywhen it attempts to shut down.

If the server receives a signal other than SIGTERM and that signalcauses it to exit (e.g. SIGKILL, SIGQUIT, SIGINT, etc), then theserver does not attempt to clean up before exiting. This can causethe object database to end up in a non-consistent state.

The next time the server starts, it tries to correct any inconsistenciesthat it finds in the object database. There may be, however, attributeswith values that are inconsistent with others. It is important,therefore, that every effort be made to shut servers down cleanly viathe pdshutdown command or the SIGTERM signal.

Shutting down a server using CLI

Use the following command to shut down a server:

pdshutdown [-c server] [-w when_time ]server_name

when_time:

nowafter-current (default)after-all

Example:

/usr/pd/sbin/pdshutdown -w now server_name

Other switches available for the pdshutdown command include:

� [-m message_text]

� [-x extended_attribute_string]

� [-X attribute_filename]

For more information, refer to the PrintXchange Command LineInterface Reference Guide.



Shutting down all servers using start/stop script

Use the following command to shut down all servers:

/etc/rc3.d/S40PXC.servers stop

Shutting down a server using GUI

To shut down a server:

1. Run the /usr/pd/bin/pdprintadmin application.

2. Select the Servers tab.

3. Select the specific server.

4. Select the Shutdown command from the Selected menu.

The GUI Shutdown command uses the default when_time value:after-current.

GUI Shutdown command The behavior of a server on a shutdown depends on the type ofserver:

Spoolers A spooler first disables itself and stops accepting print requests fromclients. It then shuts down depending on the type of shutdown:

� now . The spooler shuts down immediately. Jobs alreadysubmitted complete printing.

� after-current . The spooler shuts down after the completion ofjobs that are processing, printing, or undergoing submission to asupervisor.

� after-all . The spooler shuts down after the completion of allpending jobs.

Supervisors A supervisor first disables itself and rejects any new jobs from thespooler. It then shuts down depending on the type of shutdown:

� now . The supervisor deletes all jobs on all associated printersand then shuts down immediately.

� after-current . The supervisor shuts down after the completion ofjobs that are processing or printing.

� after-all . The supervisor shuts down after the completion of jobsthat are processing or printing (same as after-current).

When the server finally shuts down, it attempts to do so gracefully,which includes attempting to put the object database in a consistentstate before exiting. This applies to both spoolers and supervisors.



Restarting a server

Restarting a server using CLI

To restart a server, run the appropriate executable for the specificserver (pdsplr , pdspvr , or pdxspvr ). The restarted server will havethe same objects and attributes as before the shutdown.

On a restart the server attempts to correct any inconsistencies that itfinds in the object database. During the restart, if the server detectsa corrupted database, it displays a message requesting you restart itusing the -a switch. Try starting the server again using the-a switch.

Restarting all servers using start/stop script

/etc/rc3.d/S40PXC.servers start

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNX 10-1

10. Creating and configuringqueues, physical printers

and logical printers

General information on objects (queues, physical printers, logical printers)

Creating print objects is one of your initial tasks when setting up thePrintXchange system. As you create an object and set its attributevalues, you build the object database that PrintXchange uses toperform the operations that enable you to manage your PrintXchangesystem and that result in the ultimate aim of PrintXchange; printedoutput of print requests.

Enabling print objects is the next task you perform during thePrintXchange installation process. The “Enabling and disablingobjects” chapter discusses the most common server-managementoperations and covers enabling and disabling the objects in day–to-day operations and maintenance of PrintXchange.

You can use the CLI or the GUI to create objects other than servers,jobs, and documents. However, you can remove all objects,including servers, jobs, and documents.

Any object you create with the “create operation” is permanent orpersistent. That is, the object continues to exist across re-initializations of the print system or any of its components.

PrintXchange initializes newly created queues, logical printers, andphysical printers in the disabled state.

The valid objects for a create operation are:

� Queue


� Logical printer


� Initial-value-document.

In an NIS environment, an entry must already exist in the namespace for the create operation to succeed when creating a queue,physical printer, or logical printer object.

CREATING AND CONFIGURING QUEUES, PHYSICAL PRINTERS AND LOGICAL PRINTERS


Creating objects through CLI

To create a new queue, logical printer, or physical printer:

pdcreate [-c class_name] [-x extended_attribute_string] [-Xattribute_filename] object_instance …


queue [spooler_name:]queue_nameprinter (default) [spooler_name:]logical_printer_nameprinter [supervisor_name:]physical_printer_nameinitial-value-job [spooler_name:]iv_job_nameinitial-value-document [spooler_name:]iv_doc_name

If you do not specify spooler_name, PrintXchange uses thedefault spooler associated with the logical printed specified withthe PDPRINTER environment variable.

switch description

-x and -X Use these switches in the command line to setattribute values for the new objects. You canuse the add value ( + ) modification operator withattribute=value pairs as described in the “Settingand modifying object attributes” chapter.

� You must use the -X switch when creatinga physical printer to specify thecorresponding printer attribute file(printer_model.paf).

� You may use the -X switch to specify a filethat contains predefined attributes that youwant to set for the new object.

Other switches available for the pdcreate command include:

� [-g]


� [-r requested_attributes]

� [-s style_name]

Refer to the PrintXchange Command Line Interface ReferenceGuide.

The CLI also allows you create an object by copying anotherobject using the client attribute copy-from . For moreinformation, refer to the PrintXchange Command Line InterfaceReference Guide.

Name space considerations

When you create a queue, logical printer, or physical printer object,the create operation registers the object with the name space. Thecreate operation fails if an object of the same name and of the sameobject class already exists in the name space.

Note : Creating one of these objects in the NIS environment requiresyou to manually add the object name into the NIS name space fileand propagate the information throughout the NIS servers operatingin that domain before invoking the create object operation.



Creating and enabling a queue

When creating a queue, the associated spooler:

� Registers the queue with the name service (refer to the “Namespace considerations” section at the beginning of this chapter)

� Initializes the new queue as disabled (sets the queue attributeenabled=no ); you must run the enable operation to enable thenew queue

� Adds the name of the new queue to the spooler queues-supported attribute.

Creating a queue

To create a queue, select any valid name for your queue,queue_name=color_q, and enter:

/usr/pd/sbin/pdcreate -c queue<spooler_name> : <queue_name>

or

/usr/pd/sbin/pdcreate -c queuefloor1_spl:color_q

Enabling a queue

To enable a queue, enter::

/usr/pd/sbin/pdenable -c queue<spooler_name> : <queue_name>

or

/usr/pd/sbin/pdenable -c queuefloor1_spl:color_q



Creating and enabling a physical printer

PrintXchange requires the name of the new physical printer’sassociated queue before you can enable the physical printer.Though you can set the corresponding associated-queue attributesubsequent to the object creation, the recommendation is to specify itwith the create operation.

Before you can create a physical printer, you must have a printerattribute file (paf) for the printer. The appendix “Printer data sheets”includes the data sheets that correspond to the printer attribute filesfor all of the currently supported printers. You can determine theappropriate printer attribute file for your new physical printer by theprinter model, since the names of printer attribute files have theformat:

printer_model.paf

Note that for reference supervisor, separate printer attribute files existfor PostScript and PCL of the same printer model. If your printeraccepts both PostScript and PCL, you must create two separatephysical printer objects—each with the corresponding printer attributefile.

Xerox supervisor, however, does not follow the above conventionand does not need separate printer attribute files or printer objects.Also the name of the printer attribute files for Xerox supervisor havethe format:

printer_model_lp/lpr.paf

If a printer attribute file does not already exist for your new printer,you may try using a printer attribute file for a printer similar to yournew one. Note, however, that the printer model in the attribute filewould not correspond to your new printer. The only way of changingthe printer model is by your editing the printer attribute file itself.

There are PAF creation and validation assistance tools available ifyour new printer supports the PostScript PDL and you have obtainedthe PostScript Printer Definition (PPD) file from the printer vendor.These tools are located under the sbin/pdtools directory on thesystem where a supervisor server is installed. Note that these toolsare not officially supported and may be unavailable in the future.Refer to the PAFTOOLS txt file for instructions on how these toolsshould be used.

As an administrator, you may modify physical printer attributes at anytime. Changes to printer connectivity attributes, however, take effectonly when the printer transitions from disabled to enabled.

When you create a physical printer, the associated supervisor:

� Registers the physical printer with the name service.

� Initializes the new physical printer as disabled (sets the physicalprinter attribute enabled=no ); you must run the enable operationto enable the new physical printer.

� Adds the name of the new physical printer to the supervisor’sphysical-printer-supported attribute.

� Sets the physical printer’s xxx-supported and xxx-readyattributes specified in the printer attribute file.

Setting the associated queue If you specify associated-queue with the create operation, thespecified queue must exist or the operation fails.



Setting the printer address A reference supervisor requires a unique value of the printer-addressattribute for a printer connected to it. The attribute printer-addressmust have a value when you enable the physical printer; otherwise,the enable operation fails.

The following table lists the general forms of the printer-addressattribute that the reference supervisor recognizes. The formsindicate a null, serial, parallel, or IP network socket connection. IPnetwork socket ports may be simple node names with or withoutdotted domain syntax, and with or without port numbers. The syntaxfor printer-address is text. However, the port number is a decimalinteger.

Table 10-1. General forms for printer-address attribute

Form Description

/dev/null Null device, for testing only. This form of the printer-address attribute requires that attribute printer-connection-level=1

/dev/bpp<n>/dev/mcpp<n>

Parallel port n.

Examples for locally-connected parallel port:

LPT1:

/dev/bpp0

/dev/pts<n> Serial port n.

Examples for locally-connected serial port:

COM2:

/dev/pts1

/dev/tty<aa> Serial port aa.

Example: for locally-connected serial port:

/dev/ttya or /dev/ttyb

This form of the printer-address attribute requires thatattribute printer-connection-level=1

name[:port] Host name without domain and, optionally, port*.

Example: foobar

name.abc.def.hij[:port] Host name with domain and, optionally, port*.

Example: topper.mro1.dec.com

nnn.nnn.nnn.nnn[:port] Numeric IP address and, optionally, port*.

Example: 16.34.144.119:9100

A Xerox supervisor requires a unique value of the printer-addressattribute for a printer connected to it. The attribute printer-addressmust have a value when you enable the physical printer; otherwise,the enable operation fails.

Xerox supervisor uses BSD connection method. The correspondingprinter address for this type of connection requires:

� Network print server’s TCP/IP host name or IP address

� Network printer name of the above print server, which on somesystems is known as the lpr print-queue name

[Extension value is no longer required]



Creating a physical printer

To create a physical printer:

� Select any valid name for your physical printer,<physical_printer_name> =color_pp

� Select a queue, <queue_name> =color_q

� Select a Printer Attribute File (PAF) that describes your printermodel from the available list in /usr/pd/share/cap directory,<PAF>=HP_ColorLaserJet_Level2PS.paf

� Select printer address: i.e. printer_address=133.245.555.222

� Then enter:

/usr/pd/sbin/pdcreate -c printer \

-x printer-address= <printer_address> \

-x associated-queue= <queue_name> \

-X /usr/pd/share/cap/ <PAF> \

<supervisor_name>:<physical_printer_name>

or


-x printer-address=133.245.555.222 \

-x associated-queue=color_q \

-X /usr/pd/share/cap/HP_ColorLaserJet_Level2PS.paf \

floor1_sup:color_pp

Setting load balancing attributes

Load balancing occurs when two or more physical printers areassociated with a single queue. Sharing the load of print jobs overmultiple printers ensures that printers are not under or over utilized.Whether using the Xerox or Reference supervisor, a round-robinscheme is used to determine the next available printer ready toaccept a job. For the Xerox supervisor, additional criteria based onthe max-concurrent-job-processing value is used to determine whena printer is ready to accept a job. In general, high speed printers havetheir own hard disk storage for jobs received from the host. Ensuringa steady stream of jobs to the printer will minimize printer cycledowns. The throughput of jobs to the printer can be maximized bysetting an appropriate value for the max-concurrent-job-processingattribute of the physical printer.

For a detailed explanation on the max-concurrent-job-processingattribute, refer to the “Attributes” in the Command Line InterfaceReference Guide.



Enabling a physical printer

To enable a physical printer, enter:

/usr/pd/sbin/pdenable -c printer<supervisor_name> : <physical_printer_name>

or

/usr/pd/sbin/pdenable -c printerfloor1_sup:color_pp

Creating and enabling a logical printer

PrintXchange requires the name of the new logical printer’sassociated queue before you can enable the logical printer. Thoughyou can set the corresponding associated-queue attributesubsequent to the object creation, the recommendation is to specify itwith the create operation.

You may also specify initial-value-job and initial-value-documentobjects to set job and document defaults for the logical printer withthe printer-initial-value-job and printer-initial-value-documentattributes. You may set the attributes with the create operation orwith the set operation after the object creation.

When you create a logical printer, the associated spooler:

� Registers the logical printer with the name service (refer to the“Name space considerations” section in this chapter).

� Initializes the new logical printer as disabled (sets the logicalprinter attribute enabled=no ); you must run the enable operationto enable the new logical printer.

Also, if you specify printer-initial-value-job or printer-initial-value-document , the corresponding object must exist or the operation fails.



Creating a logical printer

To create a logical printer:

� Select any valid name for your logical printer,<logical_printer_name> =color

� Select a queue, <queue_name> =color_q

� Then enter:


-x associated-queue= <queue_name> \ \<spooler_name>:<logical_printer_name>

or


-x associated-queue=color_q \

floor1_spl:color

Enabling a logical printer

To enable a physical printer, enter:

/usr/pd/sbin/pdenable -c printer <spooler_name> :<logical_printer_name>

or

/usr/pd/sbin/pdenable -c printerfloor1_spl:color



Other optional CLI operations

Creating initial-value-job and initial-value-document objects

Initial-value-job and initial-value-document objects are passiveobjects. That is, they are not subject to operations such aspause/resume, enable/disable. They serve essentially asrepositories of a specified set of attributes. You can apply the sameinitial-value-job or initial-value-document object to a logical printer orinclude it as part of the print request. In either case, the objectsremain unchanged. The objects are subject to change only whenyou modify their attributes.

When you create an initial-value-job or initial-value-document object,the associated spooler adds the name of the new objects to its objectdatabase.

Example :

To create the initial-value-job and initial-value-document objects“ivj_retain” and “ivd_2sided” on the spooler “big_spooler_spl” with aCLI command, use:

/usr/pd/sbin/pdcreate -c initial-value-job -x“job-retention-period=24:00:00”big_spooler_spl:ivj_retain

/usr/pd/sbin/pdcreate -c initial-value-document-x “sides=2” big_spooler_spl:ivd_2sided

In the examples, the spooler will set the job-retention-period to 24hours and set sides=2 for 2-sided document printing on jobsrequested that are requested to use the initial-value-job and initial-value-document objects.

CLI Examples

Example 1: To create the physical printer “highcap_pp” with a CLI command forthe Lexmark 4039 10plus Level 2 PS printer on the referencesupervisor “ref_spvr_sup” with printer address “/dev/pts/1”,associated queue “largejob_q”, and with “large-capacity” as anadditional value for the input-trays-supported and input-trays-ready attributes , use:

/usr/pd/sbin/pdcreate -c printer -X/usr/pd/share/cap/Lexmark_4039plus_Level2PS.paf-x printer-address=/dev/pts/1-x associated-queue=largejob_q-x input-trays-supported+=large-capacity-x input-trays-ready+=large-capacityref_spvr_sup:highcap_pp

The printer data sheet for the Lexmark 4039 10plus Level 2 PSprinter lists “large-capacity” as an optional input tray. Because it isoptional, the printer attribute file does not include the value for theinput-trays-supported and input-trays-ready attributes. You mustadd the value for the optional tray to the attributes to make the trayavailable for your site. The example shows that you can add thevalue via the create operation. You may also add the value via theset operation subsequent to the physical printer creation.



Example 2: This example shows how you can create physical printer objects fortwo departments that share the same BSD printserver “calypso”,which contains the printer name “coyote”, that is associated with thequeue “speedy_q”. The two departments have different servers withXerox supervisors “xerox_1_xsup” and “xerox_2_xsup” that feed thesame physicalprinter.

/usr/pd/sbin/pdcreate -c printer -X/usr/pd/share/cap/Xerox_DocuTech6135_lpr.paf-x printer-address =calypso,coyote-x associated-queue=speedy_qxerox_1_xsup:dept1_coyote

and

/usr/pd/sbin/pdcreate -c printer -X/usr/pd/share/cap/Xerox_DocuTech6135_lpr.paf-x printer-address =calypso,coyote-x associated-queue=speedy_qxerox_2_xsup:dept2_coyote

Defining Access Control List (ACL)

PrintXchange objects have ACLs that control access to objects. Theaccess-control-list attribute defines server ACLs.

Use the pdset command to create a server ACL. The syntax is:

pdset -c class -x “access-control-list={name= valuename-type= value domain= value privilege-level= value }” object_name

Brief explanations of the attribute parameters are below. For detailson all CLI commands, refer to the PrintXchange Command LineInterface Reference Guide.

name This option specifies the user’s name.

name-type This option specifies the type of user. The legal values are:

� all-users

� user

� group

� netgroup.

domain This option specifies the domain name

privilege-level This option specifies the access level of the user. The legal valuesare:

� end-user

� operator

� administrator.



The following examples illustrate setting an ACL:

� The following example first removes access from all users to“printer1” and then grants end-user access to the “odyssey”group:

pdset -c printer

-x access-control-list-=”{name-type=all-users}”

-x “access-control-list+=”{name=odyssey

name-type=group privilege-level=end-user}”

printer1

� This example specifies that user ID mary has access to spooler1:

pdset -c server-x access-control-list=”{name=mary}” spooler1

Since this example does not specify name-type , name-typedefaults to group , and since it does not specify privilege-level ,privilege-level defaults to end-user .

This is equivalent to:

pdset -c server-x access-control-list=”{name=maryname-type=group privlege-level=end-user}” spooler1

� This example removes the user ID tom from the operatorprivilege level on supervisor1:

pdset -c server-x access-control-list-=”{name=tomname-type=user privilege-level=operator}” supervisor1

� This example makes spooler1 available to all users of anydomain:



domain=any:}" spooler1

� Example of cross-platform cross-domain printing where all winntusers in xeroxcsg domain can access print devices of spooler1server:



domain=winnt:xeroxcsg}" spooler1

� Example of providing access to printer1 to mary in midwestdomain:

pdset -c printer -x access-control-list="{\

name=mary \

domain=midwest}" printer1



Defining event-notification profiles

PrintXchange reports specific system events or classes of events tousers either via electronic mail or immediate message. If you requestnotification of a class of events, you receive notification of all eventsof that class.

Use the pdset command to define notification profiles. You candefine notification profiles for servers, queues, logical and physicalprinters, jobs.

The syntax is class_name used to determine the object_instance:

pdset -c class_name -x "notification-profile={event-identifiersdelivery-method event-comment delivery-address locale}"object_instance

where:


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-identifiersdelivery-method event-comment delivery-address locale} {event-identifiers delivery-method event-comment delivery-addresslocale}" object_instance

For details on all CLI commands, refer to the PrintXchangeCommand Line Interface Reference Guide.



Defining text-to-PostScript translation filter

The PrintXchange software includes one translation filter. Thatpreprocessor translates simple-text documents to PostScript, and,optionally, performs number-up processing. This filter is storedduring the installation procedure as /usr/pd/bin/trn_textps

The translation filter should be set on the server, for a printer thatdoes not support simple-text printing.

PrintXchange supports a few attributes that are used primarily withsimple-text documents. These attributes include: bottom-margin ,footer-text , left-margin , length , number-pages , repeated-tab-stops , right-margin , top-margin , width , and content-orientation .Administrators can set up the preprocessor-definition attribute withcommand option substitutions that relate PrintXchange attributes totranslator options.

The following example shows how you can use the command optionsfor the PrintXchange text-to-PostScript translation filter. For detailedinformation on the complete command syntax, refer to thePrintXchange Command Line Interface Reference Guide.

Note : The 'command' component must be expressed as one line oftext and cannot be broken into substrings as the example mightsuggest. The example has been separated into parts to make itmore readable.

/usr/pd/bin/pdset -c server \

-x preprocessor-definition="{name=text-to-ps \

preprocessor-type=translation-filter \

executable-type=executable \

input-formats=simple-text \

output-formats=PostScript \

command='"/usr/pd/bin/trn_textps" \${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}}'\}" \-x preprocessor-list=text-to-ps \<server_name>



Creating objects through GUI

Queue, logical or physical printer To create a new queue, logical printer, or physical printer through theGUI


2. Select System Components Manager from the Tools menu.

3. Highlight a server object

4. Select the Add New… button for the corresponding object.

5. Add all applicable information for all windows, as applicable, forthe new object, then select OK or Finish .

Initial-value-job/document object To create a new initial-value-job and initial-value-document objectthrough the GUI:


2. Select the Logical Printers tab.

3. Highlight a logical printer and select its properties

4. Select the Default Settings tab.

5. Enter values for all job and/or document attributes, as applicable,

6. Save and close the window.

The GUI applies the default settings to the initial-value-job or initial-value-document object specified by the corresponding printer-initial-value-job or printer-initial-value-document attribute of the selectedlogical printer.

If the attribute values are empty, the GUI creates new initial-value-joband/or initial-value-document objects, depending on the attributesyou set. The GUI assigns the new initial-value-job and initial-value-document objects the default names:

� logicalPrinterName_IVJ_DEFAULT

� logicalPrinterName_IVD_DEFAULT

The GUI uses the default names to set the attributes for the selectedlogical printer:

� printer-initial-value-job = logicalPrinterName_IVJ_DEFAULT

� printer-initial-value-document =logicalPrinterName_IVD_DEFAULT



Creating a physical printer

Setting the Printer Attribute File The supervisor needs to know the name of the Printer Attribute Filewhich corresponds to the printer model, in order to provide printerspecific features.

Setting the printer connection method With PrintXchange, the term connection methods refers to the set ofways in which the server process can communicate with a physicalprinter device. The printer-connection-method attribute specifiesthe appropriate connection method to be used with the printer. Newobject identifiers enumerate the supported set of connectionmethods:

� Serial

� Parallel

� IP-Socket

� Digital PrintServer

� BSD.

Setting the serial parameter attributes Connecting a printer to a serial port requires that you specify severalcommunications parameters (refer to the table below). If you do notspecify the attribute printer-baud-rate, PrintXchange assumes thatyou have set up the correctly port in advance. However, if you dospecify printer-baud-rate, the supervisor sets the other attributes tovalues you specified or to the values listed in the following table if theattributes are initially empty.

Table 10-2. Serial parameter attributes

Attribute Valid values Value used ifattribute

is initially empty

printer-baud-rate 300, 1200, 2400,4800, 9600, 19200,38400

none

printer-data-bits 5, 6, 7, 8 8

printer-stop-bits 0, 1, 2 1

printer-input-flow-control

nonexoffctsdtr

xoff

printer-output-flow-control

nonexoffctsdtr

xoff

printer-parity noneevenoddmarkspace

none



Setting Network Address Used for IP-Socket and Digital PrintServer connections only: NetworkAddress refers to TCP/IP address or corresponding network name ofthe device printer in your network. Port value is optional and shouldnot be entered if Printer Attribute File is specified.

Setting Port Value For IP-Socket connection only: Port value is optional and should notbe entered if Printer Attribute File is specified.

Setting Host Machine Used for BSD connection only: Host machine refers to TCP/IPaddress or corresponding network name of a printserver, servicing adevice printer.

Setting Network Printer Used for BSD connection only: Network printer refers to the lpr print-queue name within the printserver.

Setting Extension Used for BSD connection only: Extension values are no longer beingutilized.

Setting Serial/Parallel Port Value For Serial & Parallel connection only: Machine specific Portnumber/value of the serial or parallel ports.

Testing your PrintXchange system

Once you enable your PrintXchange system, you should perform thefollowing tests:

1. Send at least two documents and jobs to print on all of theprinters in your network: one using logical-printer-level defaultsand one specifying values 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.

You have completed the installation and configuration of yourPrintXchange system.


11. Using the CLI and GUI

PrintXchange supports three clients: CLI, GUI, and inboundgateways.

The CLI and GUI clients will initiate more of the operation requests tothe PrintXchange system than the inbound gateway clients. The CLIprovides access to all of the PrintXchange functionality. The GUIprovides the same functionality. However, the GUI does not allowyou to set and modify some object attributes.

This chapter provides only a high-level overview of the CommandLine Interface (CLI) and Graphical User Interface (GUI). For detailedinformation on CLI, refer to the PrintXchange Command LineInterface Reference Guide.

USING THE CLI AND GUI


Command Line Interface (CLI)

The PrintXchange Command Language Interface (CLI) is a set of thefollowing seventeen commands that you enter at the UNIX consolewindow:

� 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 thePrintXchange Command Line Interface Reference Guide.

The CLI represents the full suite of PrintXchange functionality and isprimarily an interface for system administrators and operators.Although all users have access to the CLI, their privilege leveldetermines what they can do with it. For the minimum privilege levelrequired for each command, refer to the “Authorization” section in the“Managing security” chapter.

Environment variables

PrintXchange commands use a subset of the environment variablesto derive defaults. For a list with descriptions of the environmentvariables for localization and for CLI, refer to the Environmentvariables table in the “PrintXchange overview” chapter.



CLI syntax

The syntax for all PrintXchange commands has the format shown infigure 11-1.

Figure 11-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 PrintXchangeCommand Line Interface Reference Guide.



Summary of command options

Table 11-1 summarizes the options you can use with the CLIcommands. For detailed information on all the commands and theiroptions, refer to the PrintXchange Command Line InterfaceReference Guide.

Table 11-1. CLI command option summary

Option Command Description

-c class_name pdclean pdpausepdcreate pdresubmitpddelete pdresumepddisable pdsetpdenable pdshutdownpdls

Identifies the object class.

-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 pdprpdls pdqpdmod pdset

Turns off column headings on output of requestedattributes that you specify with the -r option.

-h All Provides information on using the command.

-m message_text pdclean pdpausepdcreate pdpromotepddelete pdresumepddisable pdrmpdenable pdsetpdmod pdshutdown

Attaches a human-readable message to the object.

-n copies pdmod pdpr Specifies the number of copies to print.

-Nnotification_method

pdmod pdpr Specifies the method by which a user wishes to be notifiedof events that occur during processing.

-p printer_name pdpr pdq Specifies the printer.

-rrequested_attributes

pdcreate pdprpdls pdqpdmod pdset

Specifies the group of attributes that the command writes tostandard output.



Table 11-1. CLI command option summary (continued)

Option Command Description

-rretention_period

pdrm Specifies the amount of time a server should keep a job inthe retained state before deleting the job.

-s style_name pdcreate pdprpdls pdqpdmod pdset

Determines the format of standard output.

-t job_name pdmod pdpr Specifies a new name.

-w when_time pdshutdown Specifies how much processing can occur before a servershuts down.

-x extended-attributes-string

All Identifies one or more attribute=value pairs.

-Xattribute_filename

All Identifies one or more files containing attribute=value pairs.



Graphical user interface (GUI)

The GUI client consists of applications that execute on the user’sworkstation in common Desktop Environment (CDE). Therefore, auser must be logged into a CDE session before executing any GUIclient. Depending on the user category of the user (End User,Operator, or Administrator), the GUI client enables only certainfunctionality.

GUI client applications

The name of the GUI client three applications are:

� pdprint

� pdprintinfo

� pdprintadmin .

pdprint This is the basic application for job submission.It opens a job print submission window (if -s is not set) that allowsusers to specify files to print and to specify job and documentattributes.. The command syntax is:

pdprint [ file_name | file-dir ] [-a] [-ddestination_printer ] [-e] [-h] [-n copy_count ][-s] [-u job_ name]

file_name | file_dir Submits the specified file file_name or all filesin the specified directory file_dir for printing; ifthe file name is “ - “, then pdprint is to readfrom standard input

-a Formats the input file into the man page formatbefore sending the file to print.

-d destination_printer Specifies the default printer for submission.

-e Deletes the source file after submission iscomplete.

-h Displays a help.

-n copy_count Specifies the number of job copies.

-s Prints silently; takes all the defaults from thecommand line or environment variables, anddoes not display the GUI print submissionwindow.

-u job_name Specifies the name of the job (job-nameattribute); defaults to the file name or to thename of the first file of a multi-document job.

Environment variables that specify defaults are:

� LPDEST - Same as -d switch to specify the default printer.

� DTPRINTFILEREMOVE - Same as the -e switch.

� DTPRINTSILENT - Same as the -s switch.

� DTPRINTUSERFILENAME - Same as the -u flag.

Users can also run PDPRINT by dragging a document icon anddropping it on a logical printer icon.



pdprintinfo This application opens a window that allows users to managesubmitted jobs. The printer information window allows users to queryor change logical printer and submitted job attributes. The commandsyntax is:

pdprintinfo [ printer_name ]

printer_name Specifying a logical printer name causespdprintinfo to open that printer, and display awindow for that printer instead of the domainview of all logical printers.

CAUTION: When pdprintinfo is executed on a remote machine withthe display option, avoid inducing a crash by setting the DISPLAYvariable to the local machine.

pdprintadmin This application opens a window that allows access to theAdministration tool. The Administration tool allows users withappropriate access levels to manage PrintXchange systemcomponents (servers, queues, logical printers, and physical printers).

An administration tool, the System Components Managerprovides a systematic process for initially setting up a system.

The command syntax is:

pdprintadmin [ object_name ]

object_name Specifying an object name causes pdprintadminto open that object, and display a window for thatobject instead of the domain view. Valid objectsare spoolers, queues, logical printers, andphysical printers.



General window description

The window that follows illustrates the primary elements of GUIwindows:

Figure 11-2. Global window features

� Application/object identifier identifies the application tool and,where applicable, the currently opened object name.

� Menu bar lists menus as applicable for a given window. Toselect a menu option

� Select a menu or press ALT+underscored character of menulabel. The GUI displays a list of menu options. Grayed outoptions are not selectable.

� Select a menu option. The GUI invokes the selectedcommand option.

� Tool bar icons provide short cuts for invoking commandsotherwise invoked via menu options or window elements (suchas command buttons). To use the tool bar:

� Select an icon. The GUI invokes the selected commandoption.

Menu bar

Tool bar icons

Tab window

Object icon

Status window

Application/object identifier



� Tab window identifies the active window. To display a tabwindow:

� Select a tab. The GUI brings the selected tab window to thetop of the display.

� Object icons indicate the current state of an object. To useobject icons

� Select an icon. The GUI activates the Selected menu for theselected object icon.

� Open an icon. The GUI displays the properties window forthe corresponding object.

� Status window displays read-only event notifications andmessages related to objects on the active window

In all cases, the term select means to point at an object with themouse cursor and click the left mouse button once. The term openmeans to point at an object with the mouse cursor and do a doubleclick with the left mouse button.


12. Getting status ofPrintXchange objects

Object status refers to information that is currently valid for a specificobject, 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 attributesof:

� A specified object

� All objects of a specified class (unless the class is server, in whichcase 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 capabilityis referred to as listing the job queue).

As an administrator, you have the access control level to get objectstatus for any object belonging to any user of the PrintXchangesystem. Generally, PrintXchange lists information only for objects forwhich a user has an appropriate access control level. Users with anEnd User access control level, for example, may list object status foronly certain objects such as their own jobs.

When listing object status, PrintXchange uses the value of theenvironment variable PDPRINTER as the default logical printer, andthe spooler containing PDPRINTER as the default server.

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

job

printer

queue

server

document-state

current-job-state

printer-state

state

server-state

GETTING STATUS OF PRINTXCHANGE OBJECTS


Table 12-1 lists the PrintXchange object states that correspond to agiven object’s state attribute.

An additional attribute called enabled determines whether or not asupervisor, spooler, queue, logical printer, or physical printer iscurrently enabled or disabled. That is, an object that is disabled cannot accept jobs. However, the object’s state attribute may indicatethat the object is ready . Therefore, for example, in trying todetermine why a job can’t get onto a queue whose state attribute isready , check the value of the queue’s enabled attribute. It is likelyset to disabled.

Table 12-1. Object states (continued)

Object State Description

Document transfer-pending The spooler has not completely retrievedthe document.

pending The normal state for a document waiting inthe spooler to be printed.

processing The spooler submitted the job, includingthis document, to the supervisor but thesupervisor has not yet begun to print thedocument.

completed The document has been printed.

Job pre-processing The spooler has not completely retrievedthe job.

pending The normal state for a job waiting in thespooler to be printed.

processing The spooler submitted the job to thesupervisor but the supervisor has not yetbegun to print the job.

printing The job is printing. If the physical printerstate is also printing , paper is coming out.

held The job is being held by the server,possibly due to a user request. Thereason(s) for the job being held may bedetermined by examining the job’s job-state-reasons attribute.

paused The job has been paused; it will not beeligible for printing until the job is resumed.

retained The job is complete, but the job-retention-period has not expired. The job is stilleligible to be resubmitted.

completed The job has been printed and the job-retention-period has expired. The job isno longer eligible to be resubmitted.

terminating The job has been canceled or aborted by



Table 12-1. Object states (continued)


the server and is in the process ofterminating.

unknown The job state is not known, orindeterminate, or is not returned by theoperation.

Logical printer idle The logical printer is accepting jobs. This isthe 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’tproceed until the printer is resumed.

timed-out The printer has not been accepting data fora period in excess of the value of theprinter attribute printer-timeout-period .

connecting-to-printer The supervisor is connecting to the printerand performing any printer initializationactivities. If the printer remains in this statefor a long time, it indicates that there issome trouble communicating with theprinter or that the printer is busy with other,non-PrintXchange printing.

unknown The printer state is not known, orindeterminate, or is not returned by theoperation.

Queue ready The normal state for a queue.

paused The queue has been paused; printing won’tproceed until the queue is resumed.

Server ready The normal state for a server.

terminating The server is in the process of shuttingdown and exiting.

paused The server has been paused; printing won’tproceed until the server is resumed.



Related printer-state information

The printer-state attribute identifies the current state of the printerobjects:

� Logical printer


The following table lists the valid printer states and indicates thevalues supported by the reference and Xerox supervisor.

Table 12-2. Valid printer states supported by the referenceand Xerox supervisor

Xerox Supervisor

ReferenceSupervisor

SNMPDeviceStatus

XPPDeviceStatus

No DeviceStatus

connecting-to-printer x x --- ---

idle x x x x

needs-attention x x x ---

needs-key-operator --- x --- ---

paused x x x x

printing x x x x

saturated --- x x x

shutdown x x x x

timed-out x x --- ---

unknown x x x x

printer-problem-message The printer-problem-message attribute contains a text stringdescribing a problem.

hold-jobs-interrupted-by-printer-failure The hold-jobs-interrupted-by-printer-failure attribute specifieswhether jobs returned to the spooler after a restart should be put inthe held or pending state.

The spooler uses the hold-jobs-interrupted-by-printer-failureattribute from the physical printer object if the attribute is specifiedthere. Otherwise, the spooler uses the attribute specified for itself(the spooler).

If the value of hold-jobs-interrupted-by-printer-failure is true |yesor unspecified, jobs returned to the supervisor due to crashes are putin the held state. The job’s job-state-reasons attribute would thencontain 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 pendingstate. The job’s job-state-reasons attribute would be empty in thiscase. The job will be rescheduled for printing with no humanintervention.



Listing object attributes

You can list object attributes using the CLI or GUI.

Listing object attributes using GUI

To list object attributes:

1. Run the pdprint , pdprintinfo , or pdprintadmin application.

2. Select an object from the appropriate window.

3. Select Properties from the Selected menu.

4. View Properties window for corresponding object attributes, thenselect the Other tab of the properties level to view other attributesfor the same object.

Note: The GUI does not have the capability to display attributes forinitial-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 ...]


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 objectsof the requested class_name (except for servers) on the defaultserver. If you specify an object_instance that does not exist,PrintXchange returns an error.

If you do not specify spooler_name or supervisor_name, PrintXchangeuses the name of the spooler indicated by the PDPRINTERenvironment variable.

The pdls command does not differentiate between attributes within anobject class. That is, pdls treats spooler-specific attributes andsupervisor-specific attributes as server object attributes. Forexample: When doing pdls with spooler-specific attributes on asupervisor object, the operation considers the attributes asappropriate to the server object. Therefore, pdls returns an emptyattribute set on the supervisor and does not incur any error.

switch description

-f Selection criteria to be used among the candidateobject_instances. Refer to the PrintXchange CommandLine Interface Reference Guide.

-F Turn off all filtering. Refer to the PrintXchange CommandLine Interface Reference Guide.

-r The set of attributes for pdls to write to standard output.Refer to the PrintXchange Command Line InterfaceReference Guide.

-s, -g The style (format) of the attribute report for pdls to writeto standard output. -g indicates that the report shall notinclude headings. Refer to the PrintXchange CommandLine Interface Reference Guide.

-x, -X The means by which to specify client attributesrelevant to pdls:

scope=0 Use with class_name=job to specifylisting of job attributes only. This is thedefault.

scope=1 Use with class_name=job to specifylisting of job and document attributes.



count-limit= n Write pdls output for every n objects.Use this attribute to break a longrequest into several smaller ones.

time-limit= n Write pdls output every n seconds.Use this attribute to break a longrequest into several smaller ones.

-x and -X also serve as alternate ways of specifying anyof the other switch options.

Listing the job queue using CLI and GUI

Job and document attributes may be listed by displaying the jobqueue. For additional information on listing job and documentattributes, refer to the “Managing jobs and documents” chapter.


13. Managing jobs and documents

This chapter explains how to handle the most common PrintXchangejob 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 avery high level. For details on all PrintXchange commands andattributes, refer to the PrintXchange Command Line InterfaceReference Guide.

MANAGING JOBS AND DOCUMENTS


Printing jobs and documents

The print operation creates job and document objects per yourrequest to print one or more files. The spooler creates a job objectfor each print request, and a document object for each file youspecify 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 runningother operations, such as pausing a job.

Printing jobs and documents using GUI

To submit a print request using GUI:

1. Run the pdprint application.

2. Enter values for all print submission window fields, as desired.

3. Select the Print button.

Printing jobs and documents using CLI

To submit a print request (and thereby create job and documentobjects), use the following command:

pdpr [-f filename] [-n copies] [-N notification_method][-p logical_printer_name] [-t job_name] [-xextended_attribute_string] [-X attribute_filename ][filename ...]

parameter description

filename ... The name of the file or files you want toprint. If you specify a hyphen (-), ratherthan filename, pdpr reads from standardinput.

If you specify more than one file name,each file becomes a document within asingle job. If any file of a multi-documentjob does not exist or otherwise fails, thespooler rejects the entire job.

switch description

-f filename A file to include as a document in theprint job. Use the -f switch with multi-document jobs to set documentattributes for the specified file that aredifferent from those for other files.

-n copies The number of copies to print of the job.

-N notification_method The method by which to receivenotification of events that occur duringprint job processing. Refer to the“Setting event notification” chapter in thisguide.



-p logical_printer_name The logical printer to which to submit thejob. If you do not specify the -p switch,pdpr uses the logical printer identifiedby the value of the printer-name-requested attribute. If printer-name-requested is also unspecified, thenpdpr uses the logical printer identifiedby the PDPRINTER environmentvariable.

If you specify both -p and printer-name-requested on the command line, pdpruses the lexically last logical printername.

-t job_name The print job name that you wantspecified for start sheets, notification,and logging.

-x and -X Use these switches in the command lineto set attribute values for the job anddocument objects.

Document attributes apply to alldocuments whose filename follows theattribute specifications in the commandline. Job attributes may be placedanywhere on the command line beforethe operands. Job attributes apply to alldocuments in the job.

The add value ( + ) modification operatormay be used when specifying theattribute notification-profile with pdpr .Refer to the “Setting and modifyingobject attributes” chapter.

Other switches available for the pdpr command include:

� [-g]



� [-s style_name]


Examples:

The following example sends a file named readme.txt to the defaultlogical printer, which is named by the PDPRINTER environmentvariable:

pdpr readme.txt

The following example sends 10 copies of the file named readme.psto the logical printer named logical1:

pdpr -x “job-copies=10” -p logical1 readme.ps

The following example sends the files named chap2.ps, chap3.ps,and chap4.ps to the default logical printer and specifies one-sidedprinting for chap2.ps and two-sided printing for chap3.ps andchap4.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 3copies of <file1> and 6 copies of <file2>. This shows how copy-countdiffers from job-copies:

pdpr –n 2 –x “copy-count=3” –f <file1> -x “copy-count6” <file2>

The following example sends 10 copies of the file named readme.psto the logical printer named logical1 and applies the initial-value-document object named ivd_bluehighlight:

pdpr -n 10 -p logical1 -x “initial-value-document=ivd_bluehighlight” readme.ps

The following example sends four copies of the job to be named“guide” to the logical printer named logical1 on the default spooler.The default spooler is the spooler which contains the logical printernamed by the PDPRINTER environment variable. The job namedguide contains two files: the title page named tp and the body of theguide named body. The title page requires one-sided printing, whilethe body requires two-sided printing:

pdpr -n 4 -p logical1 -t guide -x “sides=1” -ftp -x “sides=2” -f body

The following example sends the job named “readme” to the defaultlogical printer; the job will be sent to in the held state and remains inthis state until the job-hold attribute is set to no:

pdpr -x “job-hold=yes” readme

The following example submits the job named readme.ps to thedefault logical printer; the print request specifies the file-referencemethod of file-transfer, which is useful for large jobs, because it doesnot write the file to the spool directory:

pdpr -x “transfer-method=file-reference”readme.ps



Printing a job after a specified time

You can request that a job not be printed until after a specified dateand time. You can specify the print after time during your initial printrequest 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 willprint 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 spoolerschedules 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:


2. Enter file(s) to print.

3. Select the Details button.

4. Select the Controls button.

5. Enter the desired print after time.

6. Select the OK button.

7. Select the Print button.

Or

To specify a print after a time for a previously submitted job:

1. Run the pdprintinfo or pdprintadmin application.

2. Double-click the desired job.

3. Select the Settings tab.


5. Check the print after time check box.

6. Enter the desired print after time.




Printing a job after a specified time using CLI

To print a job after a specified time with the print request, use thepdpr 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 beensubmitted, 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 thejob-print-after attribute. The format fordate_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 onthe 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, aprint after time of 7:00 p.m. on January 25, 1998 for a job whoseidentifier 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



Holding and releasing jobs

A pending job may be held so that the spooler does not schedule itfor 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 inretained state. However, if and when the job is resubmitted, thejob will go to held state.

The job remains on hold indefinitely unless one of the followingevents takes place:

� You set the job-hold attribute to no . The spooler can thenschedule the job and set its current-job-state to pending . Thisis 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. Thespooler then deletes the held job.

� You clean the associated queue or spooler. The spooler deletesall jobs in the queue or spooler, including jobs in the held state.

� You delete or cancel the job.

Releasing jobs using GUI

Note : You may not hold a job using GUI. You may, however,release a job:

1. Run the pdprintinfo application.

2. Select the Submitted Jobs tab.

3. Select a held job.

4. Select Resume from the Selected menu.

Holding and releasing jobs using CLI

To print a job and have it go immediately to held state, use thefollowing 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 scheduledfor 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



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 beencompletely received by the spooler, but the spooler has not yet sentthe 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 forprinting 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 thejob when you paused it:

If the paused job had been in the pending state when youpaused it, the spooler schedules it for an appropriate physicalprinter. 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 thejob.



Pausing jobs using GUI

To pause a job:



3. Select the desired job.

4. Select the Pause command from the Selected menu.



Resuming jobs using GUI

To resume a job:



3. Select the desired paused job.

4. Select the Resume command from the Selected menu.

Pausing jobs using CLI

To pause a job, use the following command:

pdpause -c class_name object_instance


job [server_name:]job_identifier

Other switches available for the pdpause command include:




For more information, refer to PrintXchange Command Line InterfaceReference Guide.

Example :

To pause the job “234” on the spooler named “big_spooler” with aCLI command, use:

pdpause -c job big_spooler:234



Resuming jobs using CLI

To resume a job, use the following command:

pdresume -c class_name object_instance


job [server_name:]job_identifier

Other switches available for the pdresume command include:




For more information, refer to PrintXchange Command Line InterfaceReference Guide.

Example :

To resume the job “234” on the spooler named “big_spooler” with aCLI command, use:

pdresume -c job big_spooler:234



Retaining jobs

You can retain a job for resubmission for a specified period of timeafter it prints or is terminated by some other event such ascancellation. You do this by specifying a retention period for the jobin the job’s job-retention-period attribute.When a job completes of printing, or is otherwise terminated, if thejob-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 thefollowing 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 ofthe document data associated with the job and send the job to thecompleted state for the period of time specified by the job's job-completion-period or the server's default-job-completion-period .

Retaining jobs using GUI

To retain a job using the GUI:


2. Select the Details ... button.


4. Enter the retention period.


or



3. Select and open a job.

4. Select the Settings tab.


6. Enter the retention period.

7. Close the window.



Retaining jobs using CLI

You may use the pdpr , pdmod , pdset or pdrm command to retainjobs.

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 reachedcompleted state, its retention period may be specified or modifiedusing 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

To cancel a job and have it remain retained for resubmission, thefollowing 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 commandmay not be used. However, the job-retention-period may be modifiedvia the pdmod or pdset commands.

switch description

-x or -X Set the retention period value forthe job-retention-period attribute. The formatfor retention_period is:

[HH:]mm[:ss]

where:


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 itremain 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 for2.5 hours after it prints use:

pdmod -x job-retention-period=2:30 main:4

orpdset -c job -x job-retention-period=2:30 main:4

To cancel the job whose identifier is 2001 on the default spooler andretain it for 15 hours use:

pdrm -r 15:00 2001

Modifying job and document attributes

You can modify job and document attributes if the job is in thepreprocessing , pending , held , paused , terminating , or retainedstate. This is the value of the current-job-state attribute. You maynot modify a job that is in the completed state.

Modifying a job or document attribute does not affect the job’s orderin the queue unless the job-priority attribute is modified. However,the entire job is subject to the same attribute validation that takesplace on job submission. If the job or document modification wouldresult in a job that is not valid for the queue, then PrintXchangerejects the modify operation.

If you are modifying a retained job (to prepare for resubmission),attribute validation against the current printer is not performed. Whenthe job is resubmitted, validation against the new printer will beperformed.



Modifying job and document attributes using GUI

To modify job and/or document attributes:



3. Select and open the desired job (to modify the job itself or one ofits documents).

4. To modify job attributes and/or document attributes for a single-document job:

� Select the Settings tab.

� Change job and/or document attributes as applicable.

5. To modify document attributes for individual documents in amultiple-document job:� Select the Files tab.

� Select and open the document.

� Change document attributes as applicable.

5. Close the window.



Modifying job and document attributes using CLI

To modify job and/or document attributes use the followingcommand:

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_integerjob spooler_name:job_identifier

When you specify a document, .doc_integer must be at least 1 orat most the total number of documents in the job (number-of-documents attribute). Also, the operation accepts onlydocument attributes, not job attributes.

When you specify a job, the operation accepts job and documentattributes, and applies document attribute changes to alldocuments in the job.

switch description

-n copies The number of copies to print of the job.

-N notification_method The method by which to receivenotification of events that occur duringprint job processing. Refer to the“Setting event notification” chapter in thisguide.

-t job_name The print job name that you wantspecified for start sheets, notification,and logging.

-x and -X Use these switches in the command lineto set attribute values for the job anddocument objects.

Other switches available for the pdmod command include:

� [-g]



� [-s style_name]


Examples:

The following example changes the number of job copies to 10 forthe 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 hourfor the job whose identifier is 3 on the spooler named spooler1:

pdmod -x “job-retention-period=01:00:00” spooler1:3



The following example changes the default medium to a, for the sixthdocument of the job whose identifier is 12 on the spooler namedspooler1:

pdmod -x “default-medium=a” spooler1:12.6

The following example changes the copy count to 3 of ALLdocuments in the job whose identifier is 20 on the spooler namedspooler1:

pdmod -x copy-count=3 spooler1:20

Setting job priorities

You can specify a priority for scheduling a print job. A higher valueindicates a higher priority. The spooler passes over lower priorityjobs in favor of higher priority jobs when scheduling the jobs forprinting.

Operators and administrators have the full range of job priorities from1 to 100, while end users have a limited range of from 1 to the valueof the logical printer’s max-user-job-priority attribute.

If you do not specify a job-priority during submission, or if you requestthat the job-priority attribute be set to the default value, the followingalgorithm 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 wassubmitted, examine the initial-value-job’s job-priority attribute. Ifthe job-priority is specified for the initial-value-job and its valueis not greater than the logical printer’s max-user-job-priorityvalue, then assign this priority to the job.

� If there is no initial-value-job associated with the job or the valueof its job-priority attribute is greater than the logical printer’smax-user-job-priority , assign the value of the logical printer’sdefault-user-job-priority attribute, if it exists, to the job.

� If the logical printer has no default-user-job-priority , and if thesystem’s default job priority (which is 50) does not exceed thelogical printer’s max-user-job-priority , assign this priority to thejob.

If the logical printer’s max-user-job-priority is less than 50 (thesystem default), assign the value of max-user-job-priority to the job.

Setting job priorities using GUI

This function is not available using GUI.



Setting job priorities using CLI

You can use the pdpr command to submit a job with a specific jobpriority. 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 stateafter it has been submitted. Use the pdmod or pdset command tomodify 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 thelogical 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 jobwhose 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 haveits job priority assigned to the default value:

pdmod –x “job-priority==” 4



Resubmitting jobs to a logical printer

The resubmit operation allows you to request that a spooler resubmitspecified print jobs to a specified target logical printer on the samespooler. You may resubmit specified jobs or all jobs of a specifiedqueue. As an administrator or operator, you may resubmit any job.End Users may resubmit only their own jobs. Individual documentscannot be resubmitted.

Jobs that you resubmit must be completely submitted. That is, thespooler has received all files that comprise the job and the value ofthe attribute job-submission-complete is true . A job must also bein one of the following states (current-job-state attribute): pending ,held , paused , or retained , and must not contain the valuedocuments-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 itcontains the value documents-needed in its job-state-reasonsattribute.

When you resubmit a job, the spooler removes the specified job fromits current queue and submits it to the target logical printer.

To resubmit all jobs in a specified queue, first disable the queue. Foradditional information, refer to the “Enabling and disabling queues,physical and logical printers” chapter. Then, when you run theresubmit operation:

� The spooler removes all jobs that are pending , paused , or heldfrom the specified queue and submits them to the target logicalprinter.

� The spooler returns a warning for any job(s) that it does notsuccessfully resubmit. It is up to you then, to resubmit theindividual job(s) in question.

Resubmitting jobs using GUI

To resubmit a job:



3. Select a job.

4. Select Resubmit To... in the Selected menu.

5. Select the desired target logical printer.


To resubmit all jobs in a queue:


2. Select the Queues tab.

3. Select a queue.

4. Select Resubmit To ... in the Selected menu.

5. Select the desired target logical printer.




Resubmitting jobs using CLI

To resubmit jobs use the following command:

pdresubmit [-c class_name] target_logical_printer_nameobject_instance ...


job (default) [spooler_name:]job_identifier ...

queue [spooler_name:]queue_name ...

parameter description

target_logical_printer_name The logical printer to which youwant to resubmit the specifiedjob(s)

Other switches available for the pdresubmit command include:




Examples:

To resubmit jobs "2000" and "2001" on the default printer to logicalprinter "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



Deleting job and document defaults

You can delete logical-printer level job and document defaults bydeleting the initial-value-document and initial-value-job objects fromthe spooler’s object database and the name space.

Note : Jobs and documents which have already been submitted tothe system and had these defaults applied to them will not bemodified in any way. This will only affect jobs which are submitted tothe system after the initial-value objects have been deleted.

Deleting job and document defaults 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-documentreference 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 logicalprinter the initial-value-object will be ignored.

If you wish to remove defaulting only from a specific printer, you mayreset the printer-initial-value-job or printer-initial-value-documentattribute to no longer reference anything. In other words you maydelete the attribute, rather than delete the initial–value-job or initial-value-document.

Examples:

The following example deletes an initial-value-document objectnamed ivd_2sided from the default spooler, which is the spoolercontaining the logical printer that the pdprinter environment variablenames:

pddelete -c initial-value-document ivd_2sided

The following example deletes an initial-value-job object namedivj_retain from the spooler named spooler1:

pddelete -c initial-value-job spooler1:ivj_retain

The following example removes defaulting from the printer namedprinter1 on the default spooler which was previously setup to usedefaults from the initial-value-job ivj_retain :

pdset -c printer –x printer-initial-value-job=ivj_retain printer1.



Modifying default job priorities

Initial-value-document and initial-value-job objects that youassociate with logical printers set defaults for all documents and jobscoming to that logical printer.

Modifying default job priorities jobs 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 theinitial-value-job object named ivj_priority specifies, on the spoolernamed 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 thequeue associated with the logical printer to which you submitted it.This causes the job to be printed before all other jobs, regardless ofsubmission time. Promoting several jobs in the same queue createswhat is effectively a last-in/first-out printing sequence. That is, themost recently promoted job is printed first. You can promote a jobthat you had previously promoted.

The currently printing job continues normally at each of the physicalprinters associated with the queue containing the job to be promoted.The spooler assigns the promoted job to the first physical printer thatcompletes 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 thecurrent time.

The promote operation fails if the spooler has already sent the job toa supervisor.

Promoting jobs using GUI

To promote a job:



3. Select a job.

4. Select Promote in the Selected menu.

Promoting jobs using CLI

To promote a job use the following command:

promote object_instance


(job) [spooler_name:]job_identifier

Other switches available for the pdpromote command include:





Example:

The following example promotes the job whose identifier is 4 on thespooler named spooler1:

pdpromote spooler1:4



Deleting jobs

This operation deletes the specified job, regardless of its currentstate. When a job is being deleted, pddelete sets the value of thejob-retention-period attribute to zero, overriding its previous value,if any. Also, this utility ignores the job’s job-completion-period andthe server’s default-job-completion-period attribute. This differsfrom 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, pddeletecauses the spooler to send a delete-job request to the supervisor,which cancels the job. The supervisor then stops printing the job assoon as possible, after which the job is deleted from both thesupervisor 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 thesupervisor 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:




4. Select Cancel job in the Selected menu.

Deleting jobs using CLI

Use the pddelete command to delete jobs. The syntax is:

pddelete -c class_name object_instance



Other switches available for the pddelete command include:







Example:

The following example removes the job whose identifier is 4 from thespooler 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 notin the terminating , retained or completed state.)

If the job’s job-retention-period attribute has a non-zero valueand/or if a completion period is applicable to the job, the canceloperation 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 theperiod specified by the job-retention-period attribute.

� After the job-retention-period has expired, places the job in acompleted 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:




4. Select Cancel job in the Selected menu.



Canceling jobs using CLI

When canceling a job using CLI, you can choose to bypass or extendthe job’s current retention period by using the –r option.

To cancel a job use the following command:

pdrm [-r retention_period] 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 forretention_period is:

[HH:]mm[:ss]

where:


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:





Examples:

The following command will cancel the job whose identifier is 4 fromthe default spooler:

pdrm 4

The following command will cancel a job whose identifier is 4 fromthe 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 fromthe spooler named spooler1 and bypass its current retention period.

pdrm –r 0 spooler1:4



Discarding jobs with print deadlines

You can specify that the spooler discard a job if the job does not printby a desired time. The attribute job-discard-time specifies the time.When the job discard time arrives, the spooler deletes the jobwhether 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 thesupervisor 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


Discarding jobs with print deadlines using CLI

Use the pdpr command to specify a discard time for a job beingsubmitted.

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 whichhas 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 thejob-discard-time attribute. The format for thedate 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


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. onApril 1, 1998:

pdpr -x “job-discard-time=01:04:1998:08:00:00”4chap1.ps

Each of the following two examples specifies that the default spoolershall discard the job whose identifier is 4 if it does not print by 9:00p.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

Listing a job queue

Listing the job queue allows you to see all print jobs in their printorder in the queue of a specific logical printer. Use the pdqcommand to list a job queue.

Listing a job queue using GUI

To view the job queue in the entire domain:





To view the job queue for a particular queue or logical printer:


2. Select the Queues or Logical Printers tab.

3. Select the desired object.

4. Select Properties in the Selected menu.




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] ...



document [spooler_name:]job_identifier.doc_integer

The first object_instance in the command line indicates the objectclass. job_identifier indicates job object;job_identifier.doc_integer indicates document object. Theattributes (job or document attributes) that pdq lists for all objectinstances in the command line depend upon the object classindicated in the first object_instance.

If you do not specify an object_instance, pdq lists all print jobsfor the specified or default printer in the sequence they arecurrently scheduled to print.

If you include .doc_integer with the object_instance, then pdqlists the requested attributes only for the specified document.

Each specified job included in the command line may have beensubmitted to a different logical printer on a different server.

If you request a specific object_instance and the object does notexist, pdq returns an error.

Operators and administrators can list all jobs in any queue; endusers can list the jobs they own.

switch description

-f Selection criteria to be used among thecandidateobject_instances. Refer to the PrintXchangeCommand Line Interface Reference Guide.

-F Turn off all filtering. Refer to the PrintXchangeCommand Line Interface Reference Guide.

-p List all jobs in the queue submitted to thespecifiedlogical printer. If you specify an object_instance,pdq ignores -p. Also, pdq fails if you specify thename of a physical printer instead of a logicalprinter.

-r The set of attributes that pdq writes to standardoutput. Refer to the PrintXchange CommandLine Interface Reference Guide.



-s, -g The style (format) of the attribute report that pdqwrites to standard output. -g indicates that thereport shall omit headings. Refer to thePrintXchange Command Line InterfaceReference Guide.

-x, -X Serve as alternate ways of specifying any of theswitch options.

Examples:

The following example lists all jobs in the queue of the default logicalprinter, which is the printer named by the PDPRINT environmentvariable:

pdq

The following example lists all jobs in the queue of the logical printernamed logical1:

pdq -p logical1

The following example lists all attributes of the job on the defaultspooler whose job-identifier is 4

pdq –r all 4



Listing names and attributes of jobs and documents

You can list the names and attributes of all jobs and/or documents ina spooler.

Listing names and attributes of jobs and documents using GUI


2. Double-click the logical printer or queue containing the job.


Or




Note : For additional information on the use of GUI to list objectattributes, refer to the “Getting status of PrintXchange objects”chapter.

Listing names and attributes of jobs and documents using CLI

Use the pdls command to list names and attributes of jobs anddocuments. The syntax for listing the names and attributes of all jobsand documents or a single job and all its documents in a spooler is:

pdls [-c class_name] [-f filter_text] [-F] [-g] [-plogical_printer_name][-r requested_attributes] [-s style_name]-x “scope=1” [-x extended_attribute_string ...][-Xattribute_filename ...] object_instance

The syntax for listing the names and attributes of just the jobs or asingle job in a spooler is:

pdls [-c class_name][-f filter text] [-F] [-g] [-plogical_printer_name][-r requested_attributes] [-s style_name][-x extended_attribute_string ...] [-X attribute_filename ...]object_instance


job (default) [spooler_name:]job_identifier]

If you do not specify [spooler_name:][job_identifier ], thecommand lists the names and attributes of all jobs anddocuments (or just all jobs) on the default spooler, which is thespooler that contains the logical printer named by the PDPRINTenvironment variable. If you specify a[spooler_name:][job_identifier] that does not exist, pdls returns anerror.

Operators and administrators can list the names and attributes ofall jobs; end users can list the names and attributes of the jobsthey own.



Examples:

The following example lists the names and attributes of all jobs on thedefault spooler:

pdls

The following example lists the job and document attributes for thejob 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 objectattribute, refer to the “Getting status of PrintXchange objects”chapter.

Removing all jobs from a server or queue - Cleaning objects

The clean operation removes all jobs from all specified queue(s) orspooler(s). You cannot clean supervisors. The clean operation is anasynchronous operation, meaning that the spooler returns to theclient before the operation is complete.

Clean is intended as an emergency operation for you to use to fix aproblem, rather than as a regular operation that would be put into ascript.

You must disable a specified queue or spooler (enabled=no ) wheninvoking the clean operation (refer to the “Enabling and disablingobjects” chapter). If the specified object is not first disabled, theclean 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 , orcompleted . In order to delete processing or printing jobs, itsends a delete-job request to all jobs that are currently printingon 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 notsubmit any jobs to the supervisor. The clean operation attemptsto clean as much as it can, even if some jobs encounterproblems.

� While the clean is in progress, the spooler rejects any enablerequests on the spooler or queue.

� When the clean operation has completed, the operation usesNotification Services to deliver a clean complete event to theclient.



Cleaning a spooler or queue using GUI

To clean a spooler or queue:


2. Select the Servers or Queues tab, as appropriate.

3. Select the desired object.

4. Select Clean in the Selected menu.

Note : Selecting the Clean option will automatically disable theobject. After the clean operation is complete, the object must beenabled 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 ...


server [spooler_name:]spooler_namequeue [spooler_name:]queue_name

Other switches available for the pdclean command include:





Use the pddisable command to disable a spooler or queue (refer to“Enabling and disabling objects” chapter in this guide). Whenpdclean completes, it sends a “clean complete” event to the client.After receiving the “clean complete” event, you must use thepdenable 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. Setting and modifyingobject attributes

PrintXchange has a "set attribute” and a “modify attribute” operation,each of which allows you to add or change values of print objectattributes.

All PrintXchange objects are valid for the set attribute operation.However, only job and document objects are valid for the modifyattribute operation. For a list of object attributes that you canchange with the set and modify operations, refer to the “Allowedattributes for set and modify” section.

PrintXchange includes a database that contains object identifiers forall of its data entities. Users can update the OID database by creatingand adding to the database their own attributes, attribute valueclasses, and attribute values.

When you set or modify a print object’s attributes, the values you setare persistent. That is, the objects retain the set values acrosssystem restarts.

When you set or modify multiple attributes at the same time, thechanges to all specified attributes must succeed for the entireoperation to succeed.

SETTING AND MODIFYING OBJECT ATTRIBUTES


CLI modification operators

The CLI pdset and pdmod operations require that you indicate viaoperators 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 theattribute, 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, oradd the attribute if the attribute is not already present.

Replace all values of a multi-valued attribute with thenew value.

You include the operators as part of the attribute=value pairs that youspecify via the -x or -X switches in the pdset and pdmod commandlines. For the -x switch, the extended_attribute_string consists of oneor more attribute-value pairs. For the -X switch the file withattribute_filename contains attribute-value pair specifications.

To apply an operator, add the operator before the equal sign ( = ) ofan attribute=value pair.

Examples:

1. To remove the user “ginger” from the list of approved operatorson the supervisor “big_super”, use:

pdset -c server -x "access-control-list–={name=ginger name-type=userprivilege-level=operator}" big_super

2. To add a simple-text to PostScript translation filter to an existinglist of filters on the supervisor “big_super”, use:

pdset -c server -x "filter-definition+={name=text-to-pstype=translation input-format=simple-textoutput-format=PostScriptcommand='/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 thedefault, use:

pdmod -x “job-copies==” big_spooler:234orpdset -c job -x “job-copies==”big_spooler:234



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 thePrintXchange Command Line Interface Reference Guide.

Allowed attributes for set and modify

PrintXchange allows you to set and modify only certain objectattributes. Generally, PrintXchange does not allow you to modify thefollowing types of attributes:

� Attributes that you set or that PrintXchange sets as part of objectcreation, such as queue-name or job-identifier

� Attributes that PrintXchange sets and modifies as part of normalprocessing, such as object state attributes (server-state ,current-job-state , etc.)

This section lists the attributes by object that you are allowed to setand modify after object creation.

For a complete listing and description of object attributes, refer to thePrintXchange 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 pdqcommand with the –r verbose option. This specifies that anexpanded set of attributes be written to output.

For example, to display the verbose set of job attributes associatedwith 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 includesdocument attributes, use the pdls command with the scope=1attribute=value pair.

For instance, to display the verbose set of job and documentattributes associated with the job 123, enter:

pdls –c job –r verbose –x “scope=1” server1:123



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 X Xadd-document-operations X

availability X

cancel-individual-document-supported X

cancel-job-operations X

close-job-operations X

configuration-attributes-visible X

conformance-levels-supported X

create-job-operations X

delete-operations X

descriptor X Xdisable-operations X

domain-name N/A

enable-operations X

enabled X

events-supported X

file-reference-is-local-only X

job-attributes-visible-to-all Xlist-of-managers X

loa-abort-operations X

loa-cont-operations X

loa-operations X

locale X

locales-supported X

max-number-of-system-logs X

message Xmodify-individual-document-supported X

multiple-documents-supported Xnotification-delivery-methods-ready X

notification-delivery-methods-supported X

notification-profile X Xobject-class X

object-classes-supported X

pause-operations X

physical-printers-ready X



Server attributes CLI GUI

Spooler and supervisor

preprocessor-definition X

preprocessor-list X

proxy-submit-supported N/A

resume-operations X

send-event-operations X

server-hostname X

server-name X

server-operating-system X

server-state X

server-type X

server-version X

set-operations X

shutdown-operations X

system-log-file-path X

system-log-severity X

system-log-size X

system-logging-enabled X

transfer-methods-supported X

Spooler Only CLI GUI

clean-operations X

days-to-keep-acct-logs X

default-accounting-profile X

default-document-format X

default-job-completion-period X

driver-server X

goj-cont-operations X

goj-operations X

hold-jobs-interrupted-by-printer-failure Xlogical-printer-ready X

logical-printer-supported X

modify-job-operations X

pause-job-operations X

promote-job-operations X

queues-supported X

resubmit-job-operations X

resume-job-operations X



Supervisor Only CLI GUI

maximum-number-of-printers-supported X

number-of-printers-supported Xprinter-connection-methods-supported X

Logical and physical printer attributes

The logical and physical printer attributes that you can set after objectcreation via the CLI and/or GUI are:

Logical and Physical Printer Attributes CLI GUI

access-control-list Xassociated-queue X X

associated-server Xavailability Xbinding-edge-image-shift-max-supported Xbinding-edges-supported Xcharacter-sets-supported Xcontent-orientations-supported X X

descriptor X X

document-formats-supported X X

document-sheets-supported X X

domain-name

enabled Xexcluded-preprocessors Xfax-resolutions-supported Xfinishings-supported X X

fonts-supported Xhighlight-colours-rendering-algorithms-supported

X

highlight-colours-supported Xhighlight-mapping-colours-supported Xignore-preprocessing-failure Xinput-trays-supported X X

job-finishing-supported Xjob-offset-supported Xjob-result-set-delivery-methods-supported Xjob-sheets-supported X X

list-of-managers Xmaximum-copies-supported X X

maximum-printer-speed Xmedia-supported Xmessage Xnative-document-formats-ready X



Logical and Physical Printer Attributes CLI GUI

no-preprocessing Xnotification-profile X X

numbers-up-supported X X

object-class Xoutput-bins-supported X X

outputs-supported Xplexes-supported X X

preprocessor-list Xprint-colour-types-supported Xprinter-associated-printers Xprinter-error-sheets-supported Xprinter-locations X X

printer-name Xprinter-problem-message Xprinter-realization Xprinters-ready Xprinter-state Xsides-supported Xthickening-supported Xx-image-shift-range-supported X X

y-image-shift-range-supported X X

Logical Printer Only

default-document-format X

default-user-job-priority X

jobs-pending X

max-user-job-priority Xpreferred-printer-drivers Xprinter-initial-value-document X X

printer-initial-value-job X X



Physical Printer Only(applicable to Xerox and Reference

supervisor)

accounting-enabled Xaccounting-profile Xasync-events-supported Xcharacter-sets-ready Xdocument-formats-ready X X

document-sheets-ready X X

fax-resolutions-ready Xfinishings-ready X X

fonts-ready Xhighlight-colours-ready Xhold-jobs-interrupted-by-printer-failure Xinput-trays-medium Xinput-trays-ready X X

job-finishing-ready Xjob-offset-ready Xjob-sheets-ready X X

job-result-set-delivery-methods-ready Xjob-sheets-ready Xmaximum-printer-speed Xmedia-ready Xnative-document-formats-ready Xoutput-bin-sorter-available-count Xoutput-bins-ready X X

outputs-ready Xprint-colour-types-ready Xprinter-connect-timeout-period Xprinter-address X X

printer-connection-method X X

printer-error-sheets-ready Xprinter-model Xprinter-stop-bits X X

printer-tcpip-port-number X X

sides-ready X X

sys-up-date-and-time X



Physical Printer Only(applicable to Xerox supervisor)

device-query-channel-ready Xdevice-query-channel-supported Xdevice-query-interval Xdevice-query-library-name Xdevice-status-query-supported Xdocuprint-job-pool-version Xjob-cancel-channel-ready Xjob-cancel-channels-supported Xjob-cancellation-supported Xjob-cancel-library-name Xjob-query-channel-ready Xjob-query-channel-supported Xjob-query-interval Xjob-query-library-name Xjob-status-query-supported Xjob-submission-channel-ready Xjob-submission-channels-supported Xjob-submission-library-name Xmax-concurrent-job-processing Xmib-library-name Xmib-type Xnumber-job-on-device Xprinter-cartridge-type Xprinter-drum-level Xprinter-drum-threshold Xprinter-ink-or-toner-level Xprinter-ink-or-toner-threshold Xprinter-paper-level Xprinter-paper-threshold Xsnmp-req-community-string Xwait-for-all-document-preprocessing-to-complete

X



Physical Printer Only(applicable to Reference supervisor)

printer-baud-rate X X

printer-connection-level X X

printer-data-bits X X

printer-input-flow-control X X

printer-output-flow-control X X

printer parity X X

printer-stops-bits X X

printer-timeout-period X X

Queue attributes

The queue attributes that you can set after object creation via the CLIand/or GUI are:

Queue Attributes CLI GUI

access-control-list Xassociated-server Xavailability Xdescriptor X X

disable-backlogged-queue Xdomain-name

enabled Xjobs-pending X

Queue Attributes CLI GUI

list-of-managers Xlogical-printers-ready Xlogical-printers-supported Xmessage Xnotification-profile X X

object-class Xphysical-printers-ready Xphysical-printers-supported Xqueue-name Xqueue-backlog-lower-limit Xqueue-backlog-upper-limit Xstate X



Job attributes

The job attributes that you can set or modify after object creation viathe CLI and/or GUI are:

Job Attributes CLI GUI

accounting-information Xassigned-queue Xcompletion-time Xcurrent-job-state Xdocument-sheets X X

domain-name

impressions-completed Xinitial-value-job Xintervening-jobs Xjob-collate-preserved Xjob-comment X X

job-completion-period

job-copies X X

job-copies-completed Xjob-discard-time Xjob-fault-count Xjob-finishing Xjob-hold X X

job-identifier Xjob-identifier-for-monitor Xjob-identifier-on-client Xjob-identifier-on-device Xjob-message-from-administrator Xjob-name X X

job-offset Xjob-originating-host Xjob-originator Xjob-owner Xjob-page-count Xjob-print-after X Xjob-priority Xjob-promote-time Xjob-retention-period X X

job-sheets X X

job-state-message Xjob-state-reasons Xjob-submission-channel used Xjob-submission-complete X



Job Attributes CLI GUI

job-submission-timeout Xjob-to-be-billed Xmedia-consumed Xmedia-sheets-completed Xnotification-profile X X

number-of-documents Xobject-class Xoutput-bin (of results-profile) X X

pages-completed Xphysical-printers-requested X X

previous-job-state Xprinter-error-sheets Xprinter-name-requested Xprinters-assigned Xresults-delivery-address Xresults-delivery-method Xresults-profile Xresults-set-comment Xstarted-printing-time Xsubmission-time Xtotal-job-octets Xuser-name Xwait-for-all-document-preprocessing-to-complete

X



Document attributes

The document attributes that you can set or modify after objectcreation via the CLI and/or GUI are:

Document Attributes CLI GUI

binding-edge Xbinding-edge-image-shift Xbottom-margin Xcontent-orientation X X

copies-completed Xcopy-count X X

default-character-set Xdefault-font Xdefault-input-tray X X

default-medium X X

document-file-name Xdocument-format X X

document-name Xdocument-sequence-number Xdocument-state Xdocument-type Xdomain-name

fax-resolution Xfinishing X X

footer-text Xheader-text Xhighlight-colour Xhighlight-colour-mismatch-action Xhighlight-colour-rendering-algorithm Xhighlight-mapping-colour Xinitial-value-document Xleft-margin Xlength Xmodification-filter Xno-preprocessing Xnumber-pages Xnumber-up X X

object-class Xoctet-count Xoutput Xpage-count Xpage-media-select Xpage-order-received X



Document Attributes CLI GUI

page-select Xplex Xrepeated-tab-stops Xreset-printer Xright-margin Xsides X X

spooler-preprocessor-list Xsupervisor-preprocessor-list Xthickening-specification Xtop-margin Xtransfer-method Xwidth Xx-image-shift X X

y-image-shift X X



Initial-value-job attributes

The initial-value-job attributes that you can set after object creationvia the CLI and/or GUI are:

Initial-value-job-attributes CLI GUI

Object Attributes

descriptor Xmessages X

Job Attribute-Defaults

access-control-list Xassociated-server Xdocument-sheets X X

domain-name

initial-value-job-identifier Xjob-collate-preserved Xjob-comment Xjob-copies X X

job-discard-time Xjob-finishing Xjob-hold Xjob-message-to-operator Xjob-name Xjob-offset Xjob-print-after Xjob-priority Xjob-retention-period X X

Initial-value-job-attributes CLI GUI

Job attribute-Defaults

job-sheets X X

job-to-be-billed Xlist-of-managers Xobject-class Xoutput-bin X X

physical-printers-requested X X

printer-error-sheet Xresults-delivery-address Xresults-delivery-method Xresults-set-comment Xresults-profile X



Initial-value-document attributes

The initial-value-document attributes that you can set after objectcreation via the CLI and/or GUI are:

Initial-value-document-attributes CLI GUI

Object Attributes

descriptor Xmessages X


access-control-list Xassociated-server Xbinding-edge Xbinding-edge-image-shift Xbottom-margin Xcontent-orientation X X

copy-count X X

default-character-set Xdefault-font Xdefault-input-tray X X

default-medium X X

document-file-name Xdocument-format X X

document-name Xdocument-type Xdomain-name

finishing X X

footer-text X

Initial-value-document-attributes CLI GUI


highlight-colour Xhighlight-colour-mismatch-action Xhighlight-colour-rendering-algorithm Xhighlight-mapping-colour Xheader-text Xinitial-value-document-identifier Xleft-margin Xlength Xlist-of-managers Xnumber-up X X

object-class Xoutput Xpage-media-select X



page-order-received Xplex Xrepeated-tab-stops Xreset-printer Xright-margin Xsides X X

spooler-preprocessor-list Xsupervisor-preprocessor-list Xthickening-specification X X

top-margin Xwidth Xx-image-shift Xy-image-shift X X



Supported MIB types

The following table list the attributes supported per ManagementInformation Base (MIB) type of object. The Xerox supervisorreads these attributes from the printer’s MIB and converts theminto supported and ready attributes if the printer is an SNMPdevice status enabled printer.

Note: The printer’s MIB supports and implementation affect theXerox supervisors capability to obtain each status.

Table 14-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-message

low paper n --- y

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




MAM supporting


exhausted

drum life exhausted y --- n

no drum y --- n

duplex fail y --- n

service requested n --- y

offline n --- y

problem unknownreason

n --- n

input-trays-supported 1 y --- y

2 y --- y

3 y --- y

4 y n y

5 n n y

6 n n y

7 n n y

8 n n y

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-supported

y --- y




MAM supporting


media-ready na-letter-white y --- y

na-legal-white y --- y

na-number-10-envelope

y --- y

monarch-envelope y --- y

iso-a3-white y --- y



iso-c5-envelope y --- y

iso-designated-long-envelope

y --- y

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 byDPA

n n y

input-tray-medium * defined bycombination of input-trays-supported and

media-ready

y --- y

output-bins-supported face-up y --- n

face-down y --- n

center y --- n

side y --- y




MAM supporting


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

1 n n y

2 n n y

3 n n y

4 n n y

5 n n y

6 n n y

7 n n y

8 n n y

9 n n y




MAM supporting


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-supported

y --- y

document-formats-supported

Document formats thatare supported on the

output device

y n n

document-formats-ready

Document formats thatare ready on the output

device

y n n

native-document-formats-ready

Document formats thatare ready to use on the

output device itself

y n n

sys-up-date-and-time an appropriate valueshall be given in

generalizedTimeSyntax

y --- n

Job current-job-status completed y --- n

job-state-reasons successful-completion y --- n

complete-with-warning y --- n




MAM supporting


abort-by-system y --- n

job-message-from-administrator

an appropriatemessage shall be

given.

n --- n

pages-completed an appropriate valueshall be given incardinal syntax

y n n

total-job-octets an appropriate valueshall be given.

n --- n

media-sheets-completed

an appropriate valueshall be given incardinal syntax.

y --- n

Setting mapping attributes

Mapping attributes refer to those attributes that associate logicalprinters, physical printers, and queues.

You submit jobs to logical printers and the spooler holds the jobs inqueues until it schedules them on a physical printer. More than onelogical printer can feed one queue and one queue can feed morethan one physical printer. However, a specific logical printer can feedonly one queue and a specific physical printer can receive jobs fromonly one queue.

Specific attributes control the mapping among logical printers,queues, and physical printers. The table below lists the mappingattributes for each of the relevant objects. You control the mappingby setting the attribute associated-queue on logical and physicalprinters. PrintXchange then maintains the remaining mappingattributes. The following table describes when PrintXchange updatesthe attributes.

You can not change the value of the associated-queue of a physicalprinter unless the physical printer is disabled and its state is idle.Setting associated-queue on a physical printer causes thesupervisor to set printer-associated-printers on the physical printerto empty (PrintXchange initializes printer-associated-printers whenyou enable the physical printer). In addition, if associated-queuehas had a value, the spooler associated with that value must be up orthe attribute modification fails. The spooler removes the physicalprinter from the spooler and the queue’s physical-printers-supported attribute and from the associated logical printer’s printer-associated-printers attribute.



Table 14-2. Printer mapping attributes

Object Attribute Description

Logicalprinter

associated-queue Set by administrator.

printer-associated-printers

Lists the physical printers supported by the associated queue.

This attribute is always the same as the associated queue’sphysical-printers-supported attribute.

printers-ready Lists the enabled physical printers on the associated queue.

This attribute is always the same as the associated queue’sphysical-printers-ready attribute.

Queue logical-printers-supported

Lists the logical printers that have an associated-queue attributethat points to this queue.

This attribute is updated when a logical printer is created or deletedand 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-queueattribute 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 printermust be disabled to be deleted.

physical-printers-supported

Lists the physical printers that have an associated-queue attributethat points to this queue.

This attribute is updated when a physical printer is created ordeleted, but is not updated by physical printer creation.

physical-printers-ready Lists the enabled physical printers that have an associated-queueattribute that points to this queue.

This attribute is updated when a physical printer is enabled ordisabled. Physical printer creation or deletion does not update it,since a printer must be disabled to be deleted.



Table 14-2. Printer mapping attributes (continued)

Object Attribute Description

Physicalprinter

associated-queue Set by administrator.

printer-associated-printers

Lists the logical printers supported by the associated-queue .

This attribute is initialized when the physical printer is enabled. It isupdated when an associated logical printer is deleted or has itsassociated-queue attribute modified. It is also updated if the queueis deleted.

printers-ready Lists the enabled physical printers on the associated queue.


Server

Spooler

physical-printers-supported

Lists all physical printers that are associated with all queues orspoolers.

printers-ready Lists the enabled physical printers that are associated with all queuesor spoolers.


logical-printers-supported

Lists all logical printer registered in the spooler.

logical-printers-ready Lists all enabled logical printers on the spooler.

Supervisor physical-printers-supported

Lists all physical printers on the supervisor.

printers-ready Lists all enabled physical printers on the supervisor.



Setting xxx-supported and xxx-ready attributes

PrintXchange supports a number of attributes with names of the formxxx-supported and xxx-ready , such as document-formats-supported and document-formats-ready . These attributes aregenerally associated with printers, both logical and physical. Refer tothe list of logical and printer attributes in the “Allowed attributes forset and modify” section.

PrintXchange uses the xxx-supported and xxx-ready attributes to:

� Indicate the capabilities of a particular printer (output device) tohelp you choose an appropriate printer

� Ensure that a server rejects a job requiring a particular capabilitythat the specified printer (output device) does not support.

An xxx-supported attribute indicates that the feature is supported byat least one associated printer, but not necessarily right now. Anxxx-ready attribute indicates that a physical printer supports thefeature and the physical printer can use the feature right now withouthuman intervention:

� Only physical printers support xxx-ready attributes.

� Both physical and logical printers support xxx-supportedattributes; a logical printer uses them when a job is submitted, aphysical printer when a logical printer is enabled.

Generally, the xxx-supported and xxx-ready attributes haveidentical values, but some features require an operator’s interventionto become operational. For example, someone may have to replacea paper tray so that a particular medium becomes available. In thiscase the spooler accepts the job but does not print it until an operatorreplaces the paper tray and sets the corresponding physical printerattribute to ready.

The physical printer creation process sets most of the xxx-supported and xxx-ready attributes to appropriate and identicalvalues. However, as the administrator, you can modify theseattributes. For example, if a printer has the capability to printenvelopes but you decide not to stock envelopes, you can removeenvelopes from the media-supported attribute.

When you enable a logical printer, each of its xxx-supportedattributes that have no value inherit the xxx-supported attributevalues from its associated physical printer(s). If you set a logicalprinter xxx-supported attribute before the enable, the value is notchanged; but if it was empty, it acquires values from thecorresponding xxx-supported attribute of the associated physicalprinter(s).

You can change xxx-supported and physical printer xxx-readyattributes to set local policy. Note, however, that PrintXchange doesnot check to ensure that an xxx-ready attribute value is included onthe corresponding xxx-supported attribute. Therefore, you shouldmake sure that every xxx-ready value is included in thecorresponding xxx-supported attribute.

The following tables associate job or document attributes with printeror server attributes that the spooler uses to accept or schedule a job.Note that where there is no xxx-ready attribute for a correspondingxxx-supported attribute, the spooler uses the already assigned xxx-supported value to schedule the job on the printer.



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 appropriatephysical printers, validation for the new printer will be performed.

Table 14-3. Job attributes matched to printer attributes

Printer Attribute

Job Attribute Attribute spooler uses foraccepting

Attribute spooler uses forscheduling

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-supported

job-result-set-delivery-methods-supported

* results-delivery-method, job-copies , and output-bin are elements of the attribute results-profile and should not beset 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 14-4, “Document attributes matched to printer attributes.”

**The spooler does not do acceptance checking for printer-error-sheet (even though there is a corresponding printerattribute (printer-error-sheets-supported ).



Table 14-4. Document attributes matched to printer attributes

Printer AttributeDocument Attribute Attribute spooler uses for

acceptingAttribute spooler uses for

schedulingBinding-edge binding-edges-supported binding-edges-supportedBinding-edge-image-shift binding-edge-image-shift-max-

supportedbinding-edge-image-shift-max-supported

Copy-count* maximum-copies-supported maximum-copies-supportedContent-orientation content-orientations-supported content-orientations-supporteddefault-character-set character-sets-supported character-sets-readydefault-font fonts-supported fonts-readydefault-input-tray input-trays-supported input-trays-readydefault-medium media-supported media-readydocument-format document-formats-supported. document-formats-ready.fax-resolution fax-resolutions-supported fax-resolutions-readyfinishing finishings-supported finishings-readygamut-mapping-method-used gamut-mapping-methods-supported gamut-mapping-methods-readyhighlight-colour highlight-colours-supported highlight-colours-readyhighlight-colour-rendering-algorithm

highlight-colour-rendering-algorithms-supported

highlight-colour-rendering-algorithms-supported

highlight-colour-mismatch-action

highlight-colours-supported highlight-colours-ready

highlight-mapping-colour highlight-mapping-colours-supported highlight-mapping-colours-supportednumber-up numbers-up-supported numbers-up-supportedoutput outputs-supported outputs-readypage-select page-select-supported page-select-supportedplex plexes-supported plexes-supportedprint-colour-type-used print-colour-types-supported print-colour-types-readysides sides-supported sides-readythickening-specification thickening-supported thickening-supportedx-image-shift x-image-shift-range-supported x-image-shift-range-supportedy-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-copiessupported.

Print data processing attributes

In processing the print request and the associated print data, thespooler applies�when applicable�certain attribute values that affecthow it processes print data. This section discusses the relevant printdata processing attributes, and presents the attributes in the followinggroupings:

� Document formats

� Imaging parameters.



Document formats

The document format identifies data syntax used to encode the finalprinted form of a document. Commonly used document formatsinclude simple-text, PostScript, and PCL.

PrintXchange uses several attributes to determine the documentformat of a specific document and to determine whether or not thedestination output device supports the specified document format.The attributes are:

� document-format (document attribute)

� document-formats-supported (logical and physical printerattribute)

� document-formats-ready (physical printer attribute)

� native-document-formats-ready (physical printer attribute)

The spooler sends a document to a supervisor only if the physicalprinter’s document-formats-ready attribute matches the document’sdocument-format attribute. The physical printer’s document-formats-supported and document-formats-ready attributes mustinclude the value of a document’s document-format attribute. Theprinter attribute file you specified when creating a physical printersets 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 translatesthe document format to one of the printer’s native formats. If there isno such filter, PrintXchange aborts the remainder of the job. Youshould install the proper filters to bridge the gap between the formatssupported 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 attribute’s only value is PostScript, thesupervisor:

� Looks at the first two bytes. If the bytes are %!, the supervisorassumes that the document is PostScript and sends it directly tothe printer.

� Look at the first three bytes. If the bytes are ^D%!, the supervisorassumes that the document format is PostScript and sends thedocument directly to the printer.

� If neither of the two checks is true, the supervisor assumes thatthe document is simple-text and translates it to PostScript.

If document-format is empty and the printer’s native-document-formats-ready attribute includes values other than PostScript (or inaddition to), the supervisor simply sends the document directly to theprinter.

No special processing is provided for automatic document format asa value included on a printer’s native-document-formats-readyattribute.



Imaging parameters

Imaging parameters refer to attributes that affect the image of theprint data on the output page. The attributes are the followingdocument 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 setthat the spooler uses for the pages of a document that require acoded character set specification.

� On job submission, the spooler checks for a match with thelogical printer’s character-sets-supported attribute. If there isno match, the spooler rejects the print request.

� The spooler checks for a match with the physical printer’scharacter-sets-ready attribute. If there is no match, the spoolerleaves the job pending.

The reference supervisor is capable of handling print data streams ofany character set. It does not make assumptions about characterwidth, lexicographic order, null string-termination, or case conversionwhen transporting document data to a printer.

For certain printers, the supervisor sends a command to the printerthat causes the specified character set to be active while printing thedocument.

To set the default-character-set :

� 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 acomplete listing the character sets, refer to the PrintXchangeCommand Line Interface Reference Guide.

default-font The default-font document attribute identifies the font that the spooleruses for document pages that do not otherwise specify a font.

� On job submission, the spooler checks for a match with thelogical 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 jobpending.

The supervisor ignores the default-font attribute.



To set the default-font:

� GUI:


� CLI:

pdset -c document -x "default-font=value"[spooler_name:]job_identifier.doc_integer


sides and plex Two document attributes determine the placement of the image onthe output page:

� sides

� plex

On job submission, the spooler checks for a match with the logicalprinter’s corresponding sides-supported or plexes-supportedattribute. If there is no match, the spooler rejects the print request.

The spooler checks for a match with the physical printer’scorresponding sides-ready or plexes-supported attribute. If there isno match, the spooler leaves the job pending.

sides - The sides attribute specifies if the job should be printed onone or two sides of the paper. The default is the printer default.

To set the sides attribute:

� GUI:


� CLI:

pdset -c document -x "sides=2"[spooler_name:]job_identifier.doc_integer


plex - The plex attribute indicates whether the page images shouldbe conditioned for eventual 1- or 2-sided printing. That is, printing thatwill 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)

Figure 14-1 illustrates the difference between plex and tumble2-sided printing. PrintXchange supports the plex attribute only forcertain printers. For more information, refer to the “Printer datasheets” appendix.



Figure 14-1. Plex and tumble printing

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 printerattribute)

� number-up (document attribute)

On job submission, the spooler checks for a match with the logicalprinter’s corresponding content-orientations-supported ornumbers-up-supported attribute. If there is no match, the spoolerrejects the print request.

The spooler checks for a match with the physical printer’scorresponding content-orientations-supported or numbers-up-supported attribute. If there is no match, the spooler leaves the jobpending.

content-orientations-supported The content-orientations-supported attribute identifies the contentorientations supported by the logical and physical printer. The validvalues are:

Bindingedge on left

Front Sidey=0

Bindingedge on

right

Back Side y=0

Bindingedge on top

Front Sidey=0

Bindingedge on top

Back Side

y=0

Duplex(Head-to-head printing)

Tumble(Head-to-toe printing)



� portrait

� landscape

� reverse-portrait

� reverse-landscape.

The content orientation and number-up values work together todetermine the positioning of the image on the page. The followingfigure shows the content orientation with number-up=0 .

Figure 14-2. Number-up printing

number-up The number-up attribute specifies the number of page-images toimpose on one side of a sheet:

� none or 0 (this value suppresses any spooler default)

� simple-1-up or 1



The value none (or 0).

x-image-shift and y-image-shift The x-image-shift and y-image-shift attributes cause page imagesto be shifted in position with respect to the media on which the pageimages are to be rendered. The direction of the shift is parallel to thecorresponding x- or y-axis of the Reference Coordinate System(RCS).

You can use these attributes to enable a user/client to request adifferent margin, possibly to correct a misalignment.

The sign of the attribute value indicates the direction of shift. Apositive value indicates that the shift is in the positive x- or y-direction, and a negative value indicates that the shift is in thenegative x- or y- direction. The shift direction is the same for allpages, 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 rangesupported 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 equalto the lower bound and less than or equal to the upper bound. Thesame rule applies to y-image-shift and y-image-shift-range-supported .

portrait reverse-portrait landscape reverse-landscape



Updating the OID database

PrintXchange consists of data entities that specify the function of theprinting 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 generalcategories (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 anobject (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 forattributes (medium, highlight-colour, input-tray,…)

� Attribute values of a given value class that identify a specificobject characteristic (na-letter-white for medium value class, redfor 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 anoperation on an object (error-past-discard-time, report-job-promoted, warning-resource-needs-attention,…)

PrintXchange uniquely identifies each and every data entity with anobject identifier (OID). The object identifier has a name with a formatrepresented 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 bythe following example: 1.0.10175.1.3.2.8.

PrintXchange includes a database that contains object identifiers forall of its data entities. With PrintXchange, users can update the OIDdatabase by creating and adding to the database their own attributes,attribute value classes, and attribute values.



pdaddoid utility

The pdaddoid utility enables users to create attributes, attribute valueclasses, 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 valueclasses, and/or attribute values defined in the inputFile into the OIDdatabase. Each of the inputFile entries must have the followingformat:

<Type> <Name> <Syntax> <m/sValued> <r/wAccess> <objectClass> [valueClass]

[-o decimalOID]

Help switch [-h]

The -h switch tells pdaddoid to print out a usage message. If the -hswitch is specified, then pdaddoid only prints out the usage messageand does not do anything else, even if other switches have also beenspecified.

OID database path switch -O OIDpath

The required -O switch tells pdaddoid where the object identifierdatabase files are located if they are not located in the standarddirectory. The standard directories for the database files are:

/usr/pd/share/oid

Preview switch [-p]

The -p switch tells pdaddoid to process the input file to check forvalidity of the entries but without adding anything to the database.

Verbose switch [-v]

The -v switch tells pdaddoid to display the following items for eachentry as it adds the entry to the database:

line <input file line number> : <attribute/value/valueClass name> OID : <decimal oid> Type : <attribute/value/valueClass> Syntax : <syntax> Object : <valid object list> R/W : <read/write> M/S : <multi or single value>



pdshowoid utility

The pdshowoid utility enables users to display any attributes in theOID 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 theOID database for specified attributes.

The user may specify the complete attribute name or an abbreviationor a decimal OID. For example:

pdshowoid -r attribute-1or

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 oiddatabase path. However, unlike pdaddoid, if the OID database pathis not explicitly specified, it uses the default path.

/usr/pd/share/oid

Help switch [-h]

The -h switch tells pdshowoid to print out a usage message. If the -hswitch is specified, then pdshowoid only prints out the usagemessage and does not do anything else, even if other switches havealso been specified.

Note : Contact Technical Support for assistance using all OID utilities.


15. Pausing and resuming objects

This chapter discusses the most common server-managementoperations and covers pausing and resuming objects:

� Servers (Spoolers)

� Queues


This chapter explains the commands used to perform theseoperations at a very high level. For more information on allPrintXchange commands and attributes, refer to the PrintXchangeCommand Line Interface Reference Guide.

Pausing an object causes the object to stop output. A paused objectcan continue to accept new requests. You can also run otheroperations on a paused object such as listing its status, or setting ormodifying its attributes.

Resuming an object causes the object to continue normal operationsfor producing output.

PAUSING AND RESUMING OBJECTS


Pausing and resuming PrintXchange objects

Administrators and operators can pause and resume objects usingCLI commands or the GUI.

Pausing objects using GUI

To pause a spooler, a queue, or a physical printer:


2. Select the Servers , Queues , or Physical Devices tab.

3. Select the specific object.




Resuming objects using GUI

To resume a spooler, a queue, or a physical printer:


2. Select the Servers , Queues , or Physical Devices tab.



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


server spooler_name

queue queue_name

printer (default) physical_printer_name


Other switches available for the pdpause and pdresume commandsinclude:







Pausing spoolers

A paused spooler stops submitting jobs to supervisors. However,the spooler continues to accept new print requests for its associatedlogical 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 listingits status, or setting or modifying its attributes.

Pausing a spooler does not affect any of the spooler objects (logicalprinters, queues, and jobs) in any way.

Pausing a spooler using GUI

To pause a spooler using the GUI:


2. Select the Server tab.



Pausing a spooler using CLI

To pause a spooler named spooler1 with a CLI command, use:

pdpause -c server spooler1

Resuming spoolers

A resumed spooler resumes distributing print jobs to all of itsassociated supervisors.

When you resume a spooler, the spooler changes the value of itsserver-state attribute to ready.

Resuming a spooler using GUI

To resume a spooler using the GUI:





Resuming a spooler using CLI

To resume the spooler named spooler1 with a CLI command, use:

pdresume -c server spooler1



Pausing queues

A paused queue causes the associated spooler to stop submittingjobs to the queue’s associated physical printers. However, thespooler continues to accept new print requests for the queue’sassociated logical printers.

When you pause a queue:

� The queue’s associated spooler changes the value of thequeue’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 printersor jobs in any way.

Pausing a queue using GUI

To pause a queue using the GUI:


6. Select the Queue tab.



Pausing a queue using CLI

To pause the queue “color_q” with a CLI command, use:

pdpause -c queue color_q

Resuming queues

A resumed queue causes the associated spooler to resumesubmitting jobs to the queue’s associated physical printers.

When you resume a queue, the queue’s associated spooler changesthe value of the queue’s state attribute to ready.

Resuming a queue using GUI

To resume a queue using the GUI:







Resuming a queue using CLI

To resume the queue “color_q” with a CLI command, use:

pdresume -c queue color_q

Pausing physical printers

A paused physical printer causes the spooler associated with thephysical printer’s supervisor to stop scheduling jobs for the physicalprinter.

When you pause a physical printer:

� The physical printer stops a currently printing job as soon as thephysical printer can do so. When you resume the physicalprinter, it prints the paused job from where it left off. If thephysical printer is not printing a job when you pause it, it does notstart printing a job until you resume it.

� The physical printer’s printer-state attribute is changed topaused .

Pausing a physical printer using GUI

To pause a physical printer using the GUI:


2. Select the Physical Devices tab.



Pausing a physical printer using CLI

To pause the physical printer “highcap” with a CLI command, use:

pdpause -c printer highcap

or

pdpause highcap



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 printjob, if any, from the point where it stopped printing the job.

� The physical printer’s printer-state attribute is changed toprinting or idle.

Resuming a physical printer using GUI

To resume a physical printer using the GUI:





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. Enabling and disabling objects

This chapter discusses the most common server-managementoperations and covers enabling and disabling the following objects:

� Servers (Spoolers, Supervisors)

� Queues


� Logical printers.

This chapter explains the commands to use to perform theseoperations at a very high level. For details on all PrintXchangecommands and attributes, refer to the PrintXchange Command LineInterface Reference Guide.

Enabling an object allows the object to accept new print requests orjobs.

Disabling an object prevents the object from accepting new printrequests or jobs. Although an object is disabled, you can still runother operations on the object such as listing its status, or setting ormodifying its attributes.

ENABLING AND DISABLING OBJECTS


Enabling and disabling PrintXchange objects

Administrators can enable and disable objects using CLI commandsor the GUI Administrator Tool. Refer to the GUI online help fordetails on using this method.

Enabling objects using GUI

To enable an object:


2. Select the Servers , Queues , Logical Printers , or PhysicalDevices tab.


4. Select the Enable command from the Selected menu.



Disabling objects using GUI

To disable an object:




4. Select the Disable command from the Selected menu.



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


server spooler_nameserver supervisor_namequeue queue_nameprinter (default) logical_printer_nameprinter(default) physical_printer_name

Other switches available for the pdenable and pddisable commandsinclude:







Enabling spoolers and supervisors

An enabled spooler accepts new client print requests that aredirected to any of its associated logical printers.

Note : In addition to an enabled spooler, the specified logical printerand its associated queue must also be enabled in order to acceptprint jobs.

An enabled supervisor accepts new jobs for printing on any of itsassociated physical printers (if a specified physical printer is itselfenabled).

Enabling spoolers and supervisors using GUI

To enable a spooler or supervisor using the GUI:





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



Disabling spoolers and supervisors

A disabled spooler rejects all new client print requests that aredirected to any of its associated logical printers.

When you disable a spooler, the spooler continues to:

� Schedule and deliver previously submitted jobs to physicalprinters for printing

� Accept requests for other operations such as listing its status, orsetting or modifying its attributes

A disabled supervisor rejects all new jobs for printing on any of itsassociated 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, orsetting or modifying its attributes.

Disabling spoolers and supervisors using GUI

To disable a spooler using the GUI:





Disabling spoolers and supervisors using CLI

To disable the spooler named spooler1 with a CLI command, use:


To disable the supervisor “big_super” with a CLI command, use:

pddisable -c server big_super



Enabling queues

An enabled queue allows its associated spooler to accept new printrequests for all of the queue’s associated logical printers.

Note : In addition to an enabled queue, the designated logical printerand spooler must also be enabled in order to accept jobs.

Enabling queues using GUI

To enable a queue using the GUI:





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 printrequests for any of the queue’s associated logical printers.

Disabling a queue does not cause any changes to the associatedlogical printers. That is, the disable operation does not affect thecurrent value of any logical printer’s printer-state attribute.

Disabling queues using GUI

To disable a queue using the GUI:





Disabling queues using CLI

To disable the queue “color_q” with a CLI command, use:

pddisable -c queue color_q



Enabling physical printers

An enabled physical printer allows its associated supervisor torequest new print jobs for that physical printer.

Note : In addition to the physical printer to be enabled, the supervisormust be enabled in order to accept jobs for the physical printer.

Also, the spooler that supports the physical printer’s supervisor mustbe running.

When you successfully enable a physical printer:

� The associated supervisor adds the name of the physical printerto the supervisor’s physical-printers-ready attribute.

� The spooler supporting the relevant supervisor adds the name ofthe physical printer to the physical-printers-ready attribute forthe spooler and for the associated queue.

Before you can enable a physical printer, the following conditionsmust be true:

� The value of the physical printer attribute associated-queuemust 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 printerto ensure that all required settings have values. Required attributesspecified by the paf include the following:

� The attribute printer-model.

� If the type of supervisor is Xerox, additional attributes arespecified in the .paf file and automatically set.

� The job-submission-channels-supported attribute describesthe type of lpr (RFC 1179) that is supported for the printer.

� If the device provides the capability of obtaining the status of theprinter using SNMP, lpq, or Xerox production printing status theattribute 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 jobsusing 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 disabledand the query interval period for each channel can be set to adifferent value. The associated attributes are:

� Device-query-channel-ready

� Device-query-interval

� Job-query-channel-ready

� Job-query-interval

� Job-cancel-channel-ready.



Enabling physical printers using GUI

To enable a physical printer using the GUI:





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 toreject new print jobs for that physical printer.

Before you can disable a physical printer, the spooler that supportsthe 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 physicalprinter from the supervisor’s physical-printers-ready attribute.

� The spooler supporting the relevant supervisor deletes the nameof the physical printer from the physical-printers-ready attributefor the spooler and for the associated queue.

Disabling physical printers using GUI

To disable a physical printer using the GUI:





Disabling physical printers using CLI

To disable the physical printer “highcap” with a CLI command, use:

pddisable -c printer highcap



Enabling logical printers

An enabled logical printer allows its associated spooler to acceptnew print requests directed to that logical printer.

Note : In addition to the logical printer being enabled, the associatedqueue and server must be in order to accept print jobs.

Before you can enable a logical printer, the value of the logical printerattribute associated-queue must be the name of a queue that exists.

When you successfully enable a logical printer, the associatedspooler:

� Adds the name of the logical printer to the logical-printers-ready attribute for the associated spooler and for the associatedqueue

� Adds the name of the logical printer to the printers-readyattribute for all associated physical printers.

Enabling logical printers using GUI

To enable a logical printer using the GUI:





Enabling logical printers using CLI

To enable the logical printer “redhighlight” with a CLI command, use:

pdenable -c printer redhighlight

or

pdenable redhighlight



Disabling logical printers

A disabled logical printer causes its associated spooler to rejectnew print requests directed to that logical printer.

When you successfully disable a logical printer, the associatedspooler :

� Removes the name of the logical printer from the logical-printers-ready attribute for the associated spooler and for theassociated queue.

� Removes the name of the logical printer from the printers-readyattribute on its associated physical printers.

Disabling logical printers using GUI

To disable a logical printer using the GUI:





Disabling logical printers using CLI

To disable the logical printer “redhighlight” with a CLI command, use:

pddisable -c printer redhighlight

or

pddisable redhighlight


17. Removing (deleting) objects

This chapter discusses the most common server-managementoperations and covers removing (deleting) the following objects:

� Servers (Spoolers)

� Queues

� Physical printers

� Logical printers


� Initial-value-document.

As your system grows and changes, you will find cause to removeobjects. Removing an object deletes all information regarding thatobject from the object database. You can use the CLI or the GUI toremove 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 theseoperations at a very high level. For details on all PrintXchangecommands and attributes, refer to the PrintXchange Command LineInterface Reference Guide.

Removing (deleting) PrintXchange objects

PrintXchange has several operations that allow you to remove ordelete objects:

� Delete any object. This operation deletes the object from thedatabase.

� Delete all jobs contained in a spooler or queue. (pdclean )

This operation deletes the specified job, regardless of its currentstate, 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 jobas soon as possible, after which the job is deleted from both thesupervisor 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

REMOVING (DELETING) OBJECTS


� Deleting an initial-value-document.

Deleting objects using GUI

You can use the Graphical User Interface to remove objects. TheGUI instructions for deleting each object appear following each objectdescription.

To delete supervisors, spoolers, queues, logical printers, andphysical printers:



3. Select the relevant object.

4. Select Delete from the Selected menu.



Deleting objects using CLI

Deleting objects removes them from the corresponding spooler’s orsupervisor’s object database, and removes them from the namespace where applicable.

All objects, except documents, are valid objects for a deleteoperation. Specific examples for deleting each object re listed witheach object description.

To delete an object, use the following command:

pddelete [-c class_name ] object_instance …


server spooler_nameserver supervisor_namequeue queue_nameprinter (default) logical_printer_nameprinter physical_printer_name

job [spooler_name:]job_identifierinitial-value-job spooler_name:iv_job_nameinitial-value-document spooler_name:iv_doc_name

Other switches available for the pddelete command include:





Deleting spoolers

To delete a spooler, you must first disable it. If there are jobs on thespooler, you must first delete all jobs on the spooler (you can use thepdclean 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 thespooler’s object database.

� Removes the spooler, and its queues and logical printers fromthe name service.

� Causes all physical printers associated with the spooler to bedisassociated 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:


2. Select the Spooler tab.



Note: You must delete all jobs on the spooler before you can deletea spooler.

To delete all jobs from the spooler:



3. Select the relevant – spooler.

4. If the spooler is not disabled, select Disable from the Selectedmenu.

5. Select Clean from the Selected menu.

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. Thesyntax 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:


pdclean -c server spooler1

pddelete -c server spooler1



Deleting a supervisor

To delete a supervisor, you must first disable it. Also, you can notdelete a supervisor that is currently processing jobs. Therefore, youmust first delete all jobs on the supervisor by issuing a pddelete forall jobs in the supervisor via the spooler or allow all currently printingjobs on the supervisor to complete. The delete supervisor operation:

� Deletes all supervisor objects (physical printers and thesupervisor itself) from the supervisor’s object database.

� Removes the supervisor and its physical printers from the nameservice.

� Causes the supervisor to notify the spooler to update affectedqueues and logical printers by removing its physical printers fromall 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:


2. Select the Supervisor tab.



Deleting a supervisor using CLI

Use the pddisable command to disable the supervisor. The syntaxis:

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



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-supportedattribute.

� Causes the supervisor to asynchronously set the followingattributes to empty for each physical printer associated with thedeleted queue.

� printer-associated-printers

� associated-queue

The supervisor also updates its printers-ready attribute anddisables all physical printers associated with the queue.

� Removes the queue name from the spooler server objectdatabase and from the name service.

� If you previously added the queue name in an NIS environment,you must manually remove the object from the NIS Name Spacedatabase (printers.conf.byname) and propagate the informationthroughout the NIS servers operating in the domain.

If the supervisor is not running when you delete the queue, itperforms 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:


2. Select the queue tab.



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. Thesyntax is:

pdclean -c queue queue_name

Use the pddelete command to delete the queue. The syntax is:

pddelete -c queue queue_name



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 notdelete a physical printer if the printer has any active jobs so you mustdelete any jobs currently active on the printer or wait for active jobs tocomplete after disabling the printer. In addition, the spoolersupporting this physical printer must be running for the operation tosucceed. The delete operation:

� Removes the physical printer from the supervisor’s objectdatabase.

� Removes the physical printer object from the Name Space.

� If you previously added the queue name in an NIS environment,you have to manually remove the object from the NIS NameSpace database (printers.conf.byname) and propagate theinformation throughout the NIS servers operating in the domain.

� Updates physical-printers-supported on the supervisor byremoving the deleted physical printer.

� Causes the supervisor to notify the spooler to update anyaffected queues and logical printers by removing the physicalprinters from all mapping attributes. The spooler:

� Updates printers-ready and printer-associated-printersfor the logical printer.

� Updates physical-printers-supported on the spooler andqueue.

� If the specified printer is the only physical printer associatedwith a queue, the operation causes the spooler not toschedule any jobs in that queue until another physical printeris associated with it.

If the queue is associated with other physical printers and theuser 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 physicalprinters. Otherwise, the job will not print and the physical-printers-requested attribute on the job must be modified toempty or to another physical printer associated with thequeue.

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 tocomplete.

3. Delete the physical printer.



Deleting a physical printer using GUI

To delete a physical printer using the GUI:





Deleting a physical printer using CLI

Use the pddisable command to disable the physical printer. Thesyntax is:

pddisable -c printer physical_printer_name

Use the pddelete command to delete the physical printer. Thesyntax is:

pddelete -c printer physical_printer_name

The following example deletes a physical printer named physical1:

pddisable -c printer physical1

pddelete -c printer physical1



Deleting a logical printer

This operation does not affect jobs submitted through the specifiedlogical printer and, therefore, may result in the job’s printer-name-requested attribute referencing non-existent logical printers. Beforea logical printer can be deleted, you must first disable the logicalprinter. The delete operation:

� Removes the logical printer from the spooler’s object database.

� Updates the logical-printers-supported attribute for theassociated queue and server by removing its name.

� Updates all associated physical printers to remove the logicalprinter from the associated physical printer’s printer-associated-printers attributes.

� Removes the logical printer entry from the Name Service.

� If you previously added the queue name in an NIS environment,you have to manually remove the object from the NIS NameSpace database (printers.conf.byname) and propagate theinformation throughout the NIS servers operating in the domain.

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:





Deleting a logical printer using CLI

Use the pddisable command to disable the logical printer. Thesyntax is:

pddisable -c printer logical_printer_name

Use the pddelete command to delete the logical printer. The syntaxis:

pddelete -c printer logical_printer_name

The following example deletes a logical printer named logical1:

pddisable -c printer logical1

pddelete -c printer logical1



Deleting an initial-value-job

This operation will delete the initial-value-job from the spooler’sobject database.

Note: If the deleted initial-value-job is associated with a logicalprinter via the printer-initial-value-job attribute, this attribute is notupdated. However, print requests can be submitted through theprinter. 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 syntaxis:

pddelete -c initial-value-job spooler_name:iv_job_name

The following example deletes an initial value job named ivj1 on aspooler 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 objectdatabase.

Note: If the deleted initial-value-document is associated with alogical printer via the printer-initial-value-document attribute, thisattribute is not updated. However, print requests can be submittedthrough the printer. No defaulting will occur.

Deleting an initial-value-job using GUI

Note: You cannot delete initial-value-document objects with theGUI.

Deleting an initial-value-job using CLI

Use the pddelete command to delete an initial-value-document. Thesyntax is:

pddelete -c initial-value-document spooler_name:iv_doc_name

The following example deletes an initial value document named ivd1on spooler name spool1:

pddelete -c initial-value-document spool1:ivd1


18. Generating accounting reports

One of the features of PrintXchange is the ability to generateaccounting reports. Accounting is the collection of accountable joband document information that is collected when a job terminates forany reason, such as when it is canceled, aborted, or completedprinting. The information is then written by the spooler to a data file.

The pdaccount utility reads the accounting file and generates theinformation in simple text. Users can use the text representation ofthe accounting log for further processing (for example: download tospreadsheets or use awk scripts to create reports).

The spooler creates files in the directory var/pd/acct or the directoryspecified by the -a switch when using pdmakedb. The file's name isof 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. Thecurrent file is renamed to< spooler_name>.yyyymmdd at midnight.

GENERATING ACCOUNTING REPORTS


Enabling accounting

Logging of accounting data is the default state of a PrintXchangespooler. However, you can disable logging of accounting data for aspecific physical printer. To enable or disable accounting, use theCLI pdset command or the GUI to change the value of theaccounting-enabled attribute.

Enabling or disabling accounting using GUI

The GUI does not support modifying the accounting-enabledattribute

Enabling accounting using CLI

To enable accounting, use the CLI pdset command to change thevalue of the accounting-enabled attribute.

� To enable logging of accounting data for a specific physicalprinter:

pdset -c printer -x “accounting-enabled=yes”physical_printer_name

The following example enables accounting on the physical printernamed physical4:

pdset -c printer -x ”accounting-enabled=yes”physical4

Disabling accounting using CLI

To disable accounting, use the CLI pdset command to change thevalue of the accounting-enabled attribute.

� To disable logging of accounting data for a specific physicalprinter:

pdset -c printer -x “accounting-enabled=no”physical_printer_name

The following example disables accounting on the physical printernamed physical4:

pdset -c printer -x ”accounting-enabled=no”physical4



Accounting profile

As the system administrator, you can construct an accounting profilefor a physical printer with the accounting-profile attribute. Theaccounting profile identifies the job and document attributes that thespooler collects for the accounting log.

Users may specify any job and document attributes with theaccounting-profile attribute.

Constructing an accounting profile using GUI

The Administration GUI does not support modifying the accounting-profile attribute

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-ownernumber-of-documents document-file-name copies-completed printers-assigned document-sequence-number” physical printer

If the accounting-profile attribute is not specified, the spoolercollects data for the attributes contained in the spooler’s attributedefault-accounting-profile . The default job and document attributesfor default-accounting-profile are listed in Table 18-1.

Table 18-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



Table 18-1. Accounting attributes (continued)

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 attributescontained in default-accounting-profile .

Using the accounting report writer

The PrintXchange pdaccount utility program serves as a reportwriter that converts the accounting log records into a simple text fileconsisting of lines of tab-separated text fields.

The output text file produced by pdaccount includes a record forevery job that has been finished. The first line in the output filecontains the names of the attributes of the collected data. If the userchanges the accounting profile attributes in the middle of anaccounting log period, the output file lists the names of the newattribute set.

The output file lists only job attributes by default. Each job record isdelimited by a <CR>. The output will list the attributes as follows:

j1-attr1 j1-attr2 ... j1-attrN <CR>

j2-attr1 j2-attr2 ... j2-attrN <CR>

jn-attr1 jn-attr2 ... jn-attrN <CR>

The user may specify whether document attributes should beincluded in the output. If the output includes document attributes, theoutput lists the attributes as follows:

j-attr1 j-attr2 ... j-attrN d1-attr1 d1-attr2 ...d1-attrN <CR>

<ntabs> d2-attr1 d2-attr2 ...d2-attrN <CR>

<ntabs> dN-attr-1 dN-attr-2 ...dN-attrN

where <ntabs>=number of j attributes:

All job attributes appear first, followed by all attributes for thefirst document in the job, followed by all attributes forsubsequent documents in the job one per line.

The output from pdaccount is intended to be used with aspreadsheet application such as Microsoft Excel.

The pdaccount utility is installed with the spooler. It has thefollowing syntax:



pdaccount [-a] [-d] [-e end-date] [-h] [-o outfile] [-O oid-database-path] [-g][-p accounting-log-path] [-s start-date] spooler_name

where

switch description

-a Indicates that the output is to include both joband document attributes. If not specified, theoutput includes job attributes only.

-d Deletes the accounting files after they havebeen processed. Note, this option only deletesfiles that have been processed by this run ofpdaccount . Other accounting files are leftalone.

-e end-date Specifies the last date that will be included in the report. If notThe 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 outputwill be written. If not specified, the report iswritten to standard output (sttdout).

-O Specifies the OID database path. If this path isomitted, the default path is:

/usr/pd/share

-p Specifies the accounting log path. If this path isomitted, the default path is:

/var/pd/acct

-s start-date Specifies the first date that will be included in thereport. If not specified, the start date will be theearliest log found. Data logged on any datebefore the specified date will not be included.

The format for start-date is yyyymmdd.

spooler_name Specifies the name of the spooler that is acomponent 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 report1spooler1


19. Inbound gateways

The inbound gateways enable legacy clients access to PrintXchangeservers. The gateways connect two domains, the legacy clientdomain with the PrintXchange server domain.

PrintXchange inbound gateways support LPD clients (LPR inboundgateway) for UNIX and Windows NT. The LPR gateway offers theequivalent functionality as the UNIX LPR inbound gateway.PrintXchange supports previous versions of the PrintXchange LPRextensions plus production printing and Fuji Xerox extensions.

LPR inbound gateway

This section describes the printing functionality provided for in theinbound BSD print protocol gateway for UNIX. Documented here arekey PrintXchange interfaces utilized. Also included are therelationships to the X/Open PSIS, protocol extensions therein, andthis implementation. Inbound gateways:LPR for UNIX

References to this chapter include:

� X/Open PSIS Version 5.0

� RFC-1179.

Inbound gateway overview

The BSD print protocol adaptor is a piece of software that provideson-demand protocol translation from the BSD print protocol to anarbitrary printing paradigm. In the case of PrintXchange, this meansBSD print protocol into ISO DPA.

Installation

The protocol adaptor is designed to start on demand, translate, andexit. Under Solaris the protocol adaptor is implemented under thebinary file:

/usr/sbin/in.bsd-gw

and a loadable translation object located in

/usr/lib/print/bsd-adaptor/bsd_dpa.so

/usr/pd/lib/libpdgwmap.so

/usr/pd/lib/libpdgwbe.so

The binary is configured to start dynamically via inetd by adding theconfiguration line:

printer stream tcp nowait root /usr/sbin/in.bsd-gw in.bsd-gw

to the file: /etc/inetd.conf. The translation object is loaded duringnormal adaptor operation.

INBOUND GATEWAYS


Because the protocol adaptor requires inetd to be configured to listenfor BSD protocol requests, the existing printing solution on thesystem may have to be deconfigured.

� Under Solaris, this requires deconfiguration of the ServiceAccess Facility (SAF) pertaining to LP.

� Under UNIX 4.0 and other UNIX systems, this requires that "lpd"be killed, and removed from the system startup. The entire lp/lprset of utilities will then not work properly and should not be usedon the inbound gateway host.

After modifying /etc/inetd.conf, inetd needs to be restarted.Therefore, do a "kill -HUP (inetd)", which causes inetd to re-read theconfiguration files.

When configuring printers, each logical printer defined inPrintXchange should be defined in the bundled printing solution as aremote printer, with the server being the system hosting the spoolerin which the logical printer resides.

Administration and configuration

Since the adaptor is designed to provide a generalized translationservice from BSD protocol to "whatever", the protocol adaptorrequires that an additional parameter be stored in the name servicewith each logical printer configured. This parameter, "spooling-type",contains the name of the printing paradigm the translation is to occurfor. For PrintXchange, this is the string "dpa". So, a printers.confentry might look like:

printer:paddr=...:spooling-type=dpa:...

As printers are normally removed from the system, their entire NSentry is removed, so no additional work is required during printerremoval.

Deinstallation

Remove the adaptor by removing the /etc/inetd.conf entry. Also, killthe process with "kill -1 pid" (of inetd).

Basic operation

The protocol adaptor is broken down into essentially two parts. Thefirst part "front-end adaptor" consists of a small piece of code thataccepts BSD print protocol on the wire and makes calls to the backhalf based on the wire protocol request made. In PrintXchange, theback half "protocol translator" provides translation into ISO DPA viathe POSIX API. At this time the interface between the front half andback half is private. The adaptor should be viewed as one completeprogram that accepts BSD protocol in, translating requests to ISODPA, and returning appropriate BSD responses.

INBOUND GATEWAYS


Translations

The adaptor implements protocol translation as defined in the X/OpenXDPA (PSIS). The PSIS forms the reference to which all translationoccurs.

Appendixes C and D of the PSIS are meant to describe the mappingof BSD Job control file attributes to ISO DPA attributes; however,these sections of the PSIS appear unclear and incomplete. Uponcompletion of the translation portion of this protocol adaptor, the PSISwill need to be updated to contain a clearer, more accuratedescription of the control file message translations.

PRINTXCHANGE SYSTEM ADMNISTRATION AND OPERATIONS GUIDE FOR UNIX 19-4

Table 19-1. 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 filename)

-J -t job-name

CF_JOBCOPIES number of copies: (job) (1) -# job copies

CF_PRINT_BANNER1 L L(User) User name: (banner) (job)don't use banner: (job)

(user) (none)-h

(none)-o nobanner

(currently ignored)

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)unlink source file when done:(file)

(data file)None

(none)-r

(none)(none)

(no mapping)

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

INBOUND GATEWAYS




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

CF_KERBERIZED k k... for Kerberos ??? ??? ??? ??? (blah)

CF_PRINT_CAT_V l l(file) print file converting non-printables None -l -y catv_filter-o nofilebreak

document-format

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-T Postscript

document-format

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

CF_SYSV_CHARSET 5S 5S(char set) for SVR4 Charset None (none) -S char_set (currently ignored)

INBOUND GATEWAYS




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|manual|...)

(none) default-input-tray

CF_DEC_OUTPUT_BIN > <(bin) Output bin selection None -> (bin) (none) output-bin

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

Xerox Protocol Extensions-DocuSP

CF_DEC_ORIENTATION4 O O(orientation) Page orientation None -O (orientation) (none) content-orientation

CF_CLASS2 C C" (doc-format)"5

Document format, doc-format=pspostscriptasciitiff (DocuSP only)pclinterpress (DocuPrint only)ip (DocuPrint only)lcds (not supported)

None -C -o document-format=PostScriptPostScriptsimple-textTIFFPCLInterpressInterpressLCDS

CF_CLASS C C" (orientation) " Document orientation,orientation=portraitinverseportrait, iportraitlandscapeinverselandscape, ilandscape

None -C -o content-orientation=portraitreverse-portraitlandscapereverse-landscape

CF_CLASS C C" (staple) " Document stapling, staple=staplenostaple (DocuPrint only)

None -C -o finishing=staple-top-left---

CF_CLASS C C" (order)" Page order, order=1tonnto1

None -C -o page-order-received=first-to-lastlast-to-first

CF_CLASS C C" (simplex)" One-sided printing None -C -o sides=1

INBOUND GATEWAYS




CF_CLASS C C" (duplex)" Two-sided printing None -C -o sides=2

CF_CLASS C C" (tumble)" Head-to-toe printing None -C -o sides=2, plex=tumble

CF_CLASS C C" (mediumsize)" Medium size, mediumsize=usletter (DocuPrint only)uslegal (DocuPrint only)a4 (DocuPrint only)

The following values are forDocuSP only:

USLetterUSLegalusledgera0a1a2a3a4a5a6a7a8a9a10isob0isob1isob2isob3isob4isob5isob6isob7isob8isob9isob10jisb0jisb1jisb2jisb3jisb4jisb5jisb6jisb7jisb8jisb9

None -C -o default-medium=na-letter-whitena-legal-whiteiso-a4-white

na-letter-whitena-legal-whiteledger-whiteiso-a0-whiteiso-a1-whiteiso-a2-whiteiso-a3-whiteiso-a4-whiteiso-a5-whiteiso-a6-whiteiso-a7-whiteiso-a8-whiteiso-a9-whiteiso-a10-whiteiso-b0-whiteiso-b1-whiteiso-b2-whiteiso-b3-whiteiso-b4-whiteiso-b5-whiteiso-b6-whiteiso-b7-whiteiso-b8-whiteiso-b9-whiteiso-b10-whitejis-b0-whitejis-b1-whitejis-b2-whitejis-b3-whitejis-b4-whitejis-b5-whitejis-b6-whitejis-b7-whitejis-b8-whitejis-b9-white

INBOUND GATEWAYS




jisb10 jis-b10-white

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" (font)" Font name None -C -o (no mapping)

CF_CLASS C C" (bind=edge) " Binding edge, edge=topbottomleftright

None -C -o binding-edge=top-edgebottom-edgeleft-edgeright-edge

CF_CLASS C C" (stitch=how)" Document stapling, how=singleportraitsinglelandscapeduallandscape

None -C -o finishing=staple-top-leftstaple-bottom-leftedge-stitch

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" (signature)" Signature option None -C -o number-up=simple-2-up

CF_CLASS C C" (slipsheet)" Slipsheet option None -C -o job-sheets=job-copy-wrap

CF_CLASS C C" (prefinish=<option>) "

Media prefinish option None -C -o (no mapping)

CF_CLASS C C" (pagestoprint=<CARDINAL><CARDINAL>)"

Pages option None -C -o (no mapping)

CF_CLASS C C"(media=<size>:<type>:< color>:<weight>)"

Media custom option None -C -o (no mapping)

CF_CLASS C C" (mediaType=<type>) "


INBOUND GATEWAYS




CF_CLASS C C" (mediatSize=<size>) "


CF_CLASS C C" (mediaColor=<color>) "


CF_CLASS C C" (mediaWeight=<weight>) "


CF_CLASS C C" (opacity=transparency|opaque)"

Miscellaneous option None -C -o (no mapping)

CF_CLASS C C" (xshift2=x)" Shifts the back side of the pagein the x direction

None -C -o (no mapping)

CF_CLASS C C" (yshift2=x)" Shift the back side of the page inthe y direction

None -C -o (no mapping)

CF_CLASS C C" (account=<text>)"

Account option None -C -o (no mapping)

CF_CLASS C C" (hipentry=<CARDINAL>)"

LCDS index option None -C -o (no mapping)

CF_CLASS C C" (recipient=<name>)"

Recipient option None -C -o (no mapping)

CF_CLASS C C" (res=<CARDINAL>)"

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)

INBOUND GATEWAYS




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)

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=pspostscriptasciitiff (DocuSP only)pclinterpress (DocuPrint only)ip (DocuPrint only)lcds (not supported)

None -C --- document-format=PostScriptPostScriptsimple-textTIFFPCLInterpressInterpressLCDS

CF_CLASS C C" (orientation) " Document orientation,orientation=portraitinverseportrait, iportraitlandscapeinverselandscape, ilandscape

None -C --- content-orientation=portraitreverse-portraitlandscapereverse-landscape

CF_CLASS C C" (staple) " Document stapling, staple=staplenostaple (DocuPrint only)

None -C --- finishing=staple-top-left---

CF_CLASS C C" (order)" Page order, order=1tonnto1

None -C --- page-order-received=first-to-lastlast-to-first

CF_CLASS C C" (simplex)" One-sided printing None -C --- sides=1

CF_CLASS C C" (duplex)" Two-sided printing None -C --- sides=2

INBOUND GATEWAYS




CF_CLASS C C" (tumble)" Head-to-toe printing None -C --- sides=2, plex=tumble

CF_CLASS C C" (mediumsize)" Medium size, mediumsize=usletter (DocuPrint only)uslegal (DocuPrint only)a4 (DocuPrint only)

The following values are forDocuSP only:

USLetterUSLegalusledgera0a1a2a3a4a5a6a7a8a9a10isob0isob1isob2isob3isob4isob5isob6isob7isob8isob9isob10jisb0jisb1jisb2jisb3jisb4jisb5jisb6jisb7jisb8jisb9jisb10

None -C --- default-medium=na-letter-whitena-legal-whiteiso-a4-white

na-letter-whitena-legal-whiteledger-whiteiso-a0-whiteiso-a1-whiteiso-a2-whiteiso-a3-whiteiso-a4-whiteiso-a5-whiteiso-a6-whiteiso-a7-whiteiso-a8-whiteiso-a9-whiteiso-a10-whiteiso-b0-whiteiso-b1-whiteiso-b2-whiteiso-b3-whiteiso-b4-whiteiso-b5-whiteiso-b6-whiteiso-b7-whiteiso-b8-whiteiso-b9-whiteiso-b10-whitejis-b0-whitejis-b1-whitejis-b2-whitejis-b3-whitejis-b4-whitejis-b5-whitejis-b6-whitejis-b7-whitejis-b8-whitejis-b9-whitejis-b10-white

INBOUND GATEWAYS




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" (font)" Font name None -C --- (no mapping)

CF_CLASS C C" (hc=color) " Highlight colour,color=redbluegreencyanmagentayellowcardinalroyalbluerubyvioletblackcustomName

None -C --- highlight-colour=redbluegreencyanmagentayellowcardinalroyalbluerubyvioletblackcustomName

CF_CLASS C C" (mc=color)" highlight mapping color, colorvalues are same as forhighlight colour, color

None -C --- highlight-mapping-colour, valuessame as for highlight-colour

CF_CLASS C C"(hcr=rendering)"

highlight color renderingalorighm, rendering=

automaticcolortohighlightcolortablespresentationpictorial

None -C --- highlight-colour-rendering-algorithm=automaticcolourToHighlightcolourTablespresentationpictorial

CF_CLASS C C" (hcm=action)" highlight color mismatch action,action=

abortignoreoperator

None -C --- highlight-colour-mismatch-action=abortignoreoperator

CF_CLASS C C" (stitch)" Document stapling, stitch=stitchnostitch

None -C --- finishing=staple-top-left---

INBOUND GATEWAYS




CF_CLASS C C" (thick=x))" thickening, x=0110

None -C --- thickening-specification=thickening-entire-documentsthickening-bit-map-images

CF_CLASS C C" (drilled) " Media prefinish option None -C --- (no mapping)

CF_CLASS C C"(media=<size>:<type>:<paper color>:<weight>)"

Media custom option None -C --- (no mapping)

CF_CLASS C C" (<n>x<m>) " Media custom option 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"(disposition=<>)"

Decomp service option None -C --- (no mapping)

CF_CLASS C C"(backgroundform=<>)"

Decomp service option None -C --- (no mapping)

CF_CLASS C C" (bf=<>)" Decomp service option None -C --- (no mapping)

Fuji Xerox Protocol Extensions-CM ICS

CF_CLASS C C" (mediumsize)" Medium size, mediumsize=A4B4B5A3letter

None -C --- default-medium=iso-a4-whiteiso-b4-whiteiso-b5-whiteiso-a3-whitena-letter-white

CF_CLASS C C"(mediumtypee)"

Medium type, mediumtype =OHPthickAtsugami

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=y)" Shift the page in the y direction None -C --- y-image-shift=y

INBOUND GATEWAYS




CF_CLASS C C" (xshiftn=x)" Shift the page in the x direction None -C --- x-image-shift=-x

CF_CLASS C C" (yshiftn=y)" Shift the page in the y direction None -C --- y-image-shift=-y

CF_CLASS C C"(res=<CARDINAL>)"

Resolution option None -C --- (no mapping)

CF_CLASS C C" (inv)" Reverse image format file withblack and white

None -C --- (no mapping)

Fuji Xerox Protocol Extensions-LaserPress 4150PSII

CF_CLASS C C" (input-tray)" Specify the input tray, inpuy-tray=INTRAY1, intray1INTRAY2, intray2INTRAY3, intray3INMF, inmfCENTER

None -C --- default-input-tray

CF_CLASS C C" (input-tray)" Specify the input tray which hasthe media size., inpuy-tray=A3, a3B4, b4A4, a4B5, b5A4SEF, a4sefA4LEF, a4lefB5SEF, b5sefB5LEF, b5lef

None -C --- input-trays-medium

CF_CLASS C C" (mediasize)" Media size, mediasize=LETTER, letterLEGAL, legal

None -C --- default-medium=na-letter-whitena-legal-white

INBOUND GATEWAYS




Fuji Xerox Protocol Extensions-Able3321

CF_CLASS C C" (mediasize)" Media size, mediasize=A3, a3B4, b4A4, a4B5, b5A5, a5LETTER, letterLEGAL, legal

None -C --- default-medium=iso-a3-whiteiso-b4-whiteiso-a4-whiteiso-b5-whiteiso-a5-whitena-letter-whitena-legal-white

CF_CLASS C C" (input-tray)" Input tray, input-tray=INTRAY%n, intray%nINMF, inmf


CF_CLASS C C" (input-tray)" Input tray, input-tray= output-binSIDE, sideCENTER, centerMBOX%n, mbox%n


CF_CLASS C C" (plex)" plex=DUP, dupTUMBLE, tumbleSIMP, simp

None -C --- plex=duplextumblesimplex

CF_CLASS C C" (collate)" collate =COLLATE, collate

no-page-collate

-C --- output=page-collate

CF_CLASS C C" (staple)" Staple, staple=STAPLETLSTAPLETDSTAPLETRSTAPLELDSTAPLERDSTAPLEBLSTAPLEBDSTAPLEBR

None -C --- finishing=staple-top-left

staple-top-right

staple-bottom-left

satple-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 -# -n4 CF_SYSV_OPTION and CF_DEC_ORIENTATION conflict and only the orientation is currently processed.

INBOUND GATEWAYS


5 The LPR -C option for the Xerox extensions always requires quotes and parentheses, and uses a comma as a separator when multiple values arespecified:

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 aseparator:

lp -o duplexlp -o "duplex staple"

INBOUND GATEWAYS



20. Managing printed output

This chapter describes parameters related to managing the processthat takes place at the output device to produce the printed outputusing PrintXchange. The printed output attributes allow you torequest 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 physicalprinter 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 printerattribute).

The spooler uses the following test to determine the validity of thejob-copies and copy-count values in multiple document jobs:

For each document in a job, the spooler ensures that the product ofjob-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 spoolerrejects the document. If the spooler had already accepted a job andthe user is trying to set or modify copy-count on a particulardocument and it fails the test, then the spooler rejects the set ormodifies the operation.

MANAGING PRINTED OUTPUT


Specifying highlight color

The attributes that relate to highlight color are only used with highlightcolor printers:

� highlight-colour (document attribute)

� highlight-colours-supported (logical and physical printerattribute)

� highlight-colour-mismatch-action (document attribute)

� highlight-colour-rendering-algorithm (document attribute)

� highlight-colour-rendering-algorithms-supported (logical andphysical printer attribute)

� highlight-mapping-colour (document attribute)

� highlight-mapping-colours-supported (logical and physicalprinter attribute)

� thickening-specification (document attribute)

� thickening-supported (logical and physical printer attribute)

The document attribute highlight-colour-mismatch-actiondetermines how PrintXchange handles highlight color jobs whenthere is a mismatch between the color specified for the documentand 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 andcontinues to accept and schedule the document/job for printing.

� operator - operator intervention is required to resolve themismatch; the spooler:

� Rejects the document/job if the matching highlight color is notsupported

� Accepts but does not schedule the document/job if thematching 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 notsupported

� Accepts but does not schedule the document/job if thematching highlight color is supported but is not ready.



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 attributefiles, then no separator pages will be printed.

Document sheets are printed using the printer’s native documentformat that is in use for the document being printed. For example, ifa job specifies printing document sheets, and a simple-text documentwill be printed on a PostScript printer (through the use of the simple-text-to-PostScript translation filter), then the document sheets will beprinted 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 additionalinformation. On any other printer, the separator page will begin witha distinctive horizontal bar of characters, followed by the attributeinformation printed in the upper left corner of the page using thedefault font. The information is formatted such that it fits on A5 paper(148mm X 210mm) assuming a fixed pitch font with 10 charactersper inch.

The supervisor uses the ASCII form-feed character (octal 014) toeject simple-text separator pages. It uses the "showpage" operatorto eject and print PostScript separator pages. Separator sheets arealways printed on a separate sheet of paper, even if the document isprinted on both sides of the paper.

If any of the attribute values printed on a separator sheet requirestatic text, that text will be read from a message file to facilitateinternationalization. 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 withthe same separator page layout as the reference supervisor. Usershave to set attribute job-sheet and document-sheet to enableseparator page printing since the default is not separator page. Theseparator sheet format is derived from the document attributedocument-format of the first document. This means its format maydiffer from the original document format if the document has runthrough any filters. Currently in this version of PrintXchange,internationalization is not facilitated, the separator page is a hardcoded to the US English only.



job sheets

PrintXchange supports the following values for the job-sheetsattribute:

� 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 ofthe job.

Note: If more than one copy of a job has been requested, there willnot be “whole-job” sheets that surround the entire job, just separatorsfor each copy.

Job sheets are usually a site policy. That is, if you want job separatorsheets, you must remove none as a value of the job-sheets-supported printer attribute and ensure that all logical printers havean initial-value-job that provides a default for job-sheets . Then theuser cannot override the site policy by specifying none as a value forjob-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 endsheet:

� job-name

� job-identifier

� job-owner

� completion-time. (Does not appear on jobs printed from aXerox supervisor.)

Also, the following information will be printed on both the job start andend sheets:

� “Product name” string read from a message file (truncated toforty bytes)

� Name and version number of the operating system.

“Burst" pages, that is, print over the perforation at the beginning ofeach job, are not supported in PrintXchange.

Only jobs that complete successfully or complete with errors get anend job sheet. Jobs that are cancelled or that are aborted due toerrors do not get an end job sheet.



Document sheets

The values supported for the job attribute document-sheets are:

� none

� doc-set-start-copies-separate : A separator sheet precedesevery 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 adocument 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 followinginformation may be printed on the document start sheet:

� “Product” string that represents the manufacturers name for theproduct (for example, LaserJet III Si or PrintServer 32)

� “Printername” string that represents the name of the printer in thelocal environment (for example, “Bob’s HP3Si”)

In most PostScript implementations, the factory setting for“printername” is the same as for “product”. However, users familiarwith PostScript can change the printername string. PrintXchangesuppresses the printername string if it is identical to the productstring.



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 valuesby way of a printer attributes file. The supplied printer attributes filescontain suitable lists of trays that are supported for their respectiveprinter models.

Selecting media by input tray

The reference supervisor can select input media by input tray. Ituses the document attribute default-input-tray for determining fromwhich tray to pull blank media.

Selecting media by media type

The reference supervisor can select input media by media type, ifthat media type is associated with an input tray with the printerattribute input-trays-medium . The association must be set up byyou or an operator by assigning values to the input-trays-mediumattribute.

If a document specifies both default-input-tray and default-medium , the medium takes precedence. If default-medium isspecified but input-trays-medium has not been specified, the job isprinted without selecting a tray.

Selecting output bins

The supervisor sets the default output bin when a job beginsprocessing. All well-behaved documents that comprise the job aredeposited in the specified output bin.

Some documents, especially those originating on PCs, contain outputtray selection command sequences. The supervisor does notintercept or redefine these commands. Therefore, such jobs orportions of such jobs may draw from trays or be deposited in binsother than the ones specified in the attributes output-bin anddefault-input-tray .



Specifying finishing

The document finishing attribute specifies a sequence of processesto be applied to the document, such as stapling, saddle stitch, edgestitch, punch, cover, and bind.

The finishing processing is controlled by the printer. The supervisorcontains no support for any finishing options.

Resetting the printer

The document attribute reset-printer is only applicable to jobsprinted from the Reference supervisor. It indicates that the printershould be reset between documents within a job (the printer isalways reset between jobs). This attribute causes the resetsequence to be sent to the printer after its associated document.For example, to condition a PostScript printer with font data, use acommand 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 thejob has a value for the attribute document-sheets , the printer willalways be reset between documents regardless of the value of reset-printer .

Also, document attributes that would cause the printer to bereconfigured, such as sides, trays, and bins, also require that theprinter be reset. Therefore, if the document following a documentwith reset-printer=no specifies document attributes that aredifferent, the reset is ignored.


21. Troubleshooting

This chapter describes some of the PrintXchange elements that canhelp 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 forboth Windows NT and UNIX environments.

Troubleshooting introduction

Troubleshooting is the process that enables users to determine thecause of a problem, given specific system behavior, and to invokethe 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 determinethe 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 systemlogging, describe error messages, and discuss crash recovery.

TROUBLESHOOTING


Object states

Document, job, printer, queue, and server objects have attributes thatcontain 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 21-1 lists the PrintXchange object states that correspond to agiven object’s state attribute.

An additional attribute called enabled determines whether or not asupervisor, spooler, queue, logical printer, or physical printer iscurrently enabled or disabled. That is, an object that is disabled cannot accept jobs. However, the object’s state attribute may indicatethat the object is ready . Therefore, for example, in trying todetermine why a job can’t get onto a queue whose state attribute isready , check the value of the queue’s enabled attribute. It is likelyset to disabled.

Table 21-1. Object states


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 thesupervisor 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 yetbegun to print the job.

printing The job is printing. If the physical printer state is also printing , paper is comingout.

held A user set the job-hold attribute to true . The job will not be printed until the usersets 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.

TROUBLESHOOTING


Table 21-1. Object states


terminating The job has been canceled or aborted by the server and is in the process ofterminating.

unknown The job is not known, or indeterminate, or is not returned by the operation.

Logicalprinter

idle The logical printer is accepting jobs. This is the only state for logical printers.

Physicalprinter

idle The printer is waiting for a job.

printing A job is printing normally.

needs-attention A job is printing but the printer has informed the supervisor that something iswrong 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 theprinter attribute printer-timeout-period .

connecting-to-printer

The supervisor is connecting to the printer and performing any printerinitialization activities. If the printer remains in this state for a long time, itindicates that there is some trouble communicating with the printer or that theprinter 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.

TROUBLESHOOTING


Attributes

Be aware of the following attributes:

� printer-address . PrintXchange does not do any error checkingon the value of the printer-address attribute. Users must besure to enter a valid address for the printer port. The only waythat users can learn that they may have entered an invalid valueis when PrintXchange tries to connect to the printer and it fails.

� document-format . Users should make sure that the applicablephysical printer’s document-formats-supported , document-formats-ready , and native-document-formats-ready match thedocument’s document-format attribute. If the attributes don’tmatch, problems printing from the inbound gateway.

The attributes must also match when users create different physicalprinter objects for the PostScript and PCL versions of the sameprinter model.

Also, if a job continues in the pending state even after jobssubsequently submitted get printed, it may be because one or moreof the destination physical printer’s xxx-ready attributes do not matchthe corresponding xxx-supported attributes of the logical printer towhich the job was submitted. Remember that a job is printed onlywhen the physical printer’s xxx-ready attributes completely matchthe associated logical printer’s xxx-supported attributes. The jobdiagnostics utility, pddiagjob, can check xxx-ready and xxx-supported attributes (refer to the section on Job diagnostics).

TROUBLESHOOTING


Job diagnostics

The pddiagjob utility allows users to determine why a pending jobdoes not print. The utility applies primarily to jobs whose current-job-state is pending , held , and paused . The utility may be usedwith jobs in other states, in which case the utility checks the job butdoes 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 alsorequires 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 associatedwith 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 bespecified.

Windows NT/Windows 95 systems The GUI application command is:

pddiagjob

When the user invokes the command at the Windows NT/Windows95 console window, the utility displays the windows illustrated inFigure 21-1.

TROUBLESHOOTING


Figure 21-1. Diagnostic utility Windows NT/Windows 95window

The window features are:

� Server radio buttons

� Default . If set, the utility uses the server associated with thePDPRINTER environment variable. If the PDPRINTERenvironment variable is not available, this option button anddefault server name field is disabled.

� Other . If set, the user must specify the PrintXchange servername.

� Jobs radio buttons

� All . If set, the utility checks all pending , held , and pausedjobs in the spooler.

� Specific . If set, the user must specify one or more jobidentifiers. The utility checks only the specified jobs.

� Version button. When selected, the utility displays versioninformation of the pddiagjob utility.

� Diag… button. When selected, the utility executes the jobdiagnostics.

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 specifiedwith 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 supervisoronly)

� 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 utilitydisplays 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 assignedprinter (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 issaturated , printing , or connecting-to-printer .

Limitations

For image-shift (realSyntax) attributes, the utility it checks onlyinteger values, so it ignores any fractions.

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 thisjob.

� 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.

TROUBLESHOOTING


Windows NT/Windows 95 systems The utility results are displayed as illustrated below.

Figure 21-2. Windows NT/Windows 95 diagnostic utility results

UNIX files

On PrintXchange systems running under UNIX, some PrintXchangecomponents 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 omittingan entry for one of these PrintXchange components may be:

� For ProtoServer, repeated name space errors.

� For Notification Server, failure in the delivery of eventmessages.

� For inbound gateway, failure to print inbound gateway jobs orinclusion of inbound gateway job in the queue.

� nsswitch.conf This file includes an entry that specifies thename service search order. The inclusion of an appropriate entryfor this file is not required since PrintXchange defaults to thesearch order of Local File and then NIS.

� printers.conf For Local File naming, this file is required toinclude an entry for each PrintXchange object (spooler,supervisor, queue, logical printer, and physical printer). Nameservice errors occur if the file does not include an entry for aPrintXchange object.

Note: When both printers.conf file and NIS map have the sameentry, the GUI will display the same item twice. This occurs when aSystem Administrator creates a printer for which an entry was not

TROUBLESHOOTING


added into NIS. To avoid display of the same item twice, remove theentry from the printer.conf file on that particular machine.

System logging

The PrintXchange service log facility logs server messages forpurposes of serviceability. Customer field support personnel andproduct developers will be the primary users of the log files producedby the facility.

Non-server PrintXchange components (including clients, inboundgateways, and notification server) use the standard system loggingon the UNIX and NT platforms as described in the “Standard systemlogging” section.

Service log facility

The service log facility uses configuration attributes to specify loggingfunctions for a server.

The service log facility also provides environment variablesequivalent to the server configuration attributes that non-servercomponents may use for logging. However, this capability isavailable 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 theentire server. If yes, the server logs messages of the severity levelsspecified 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 filepath from the server runtime directory specified with the server’scfg-server-runtime-dir attribute); the relative file path is thetypical value for the attribute.

TROUBLESHOOTING


When the attribute value is an absolute or relative file path, theservice log facility uses the path to create a log file with a unique filename having the following format:

path.mmdd.hhmmss

Where:

path = absolute or relative file path value of system-log-file-pathmm = month 01 – 12dd = day 01 – 31hh = hour, based on the 24 hour clock timess = 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 hasreached the value specified with the system-log-size attribute), thenthe service log facility checks if the number of existing log filesmatches the maximum specified with max-number-of-system-logs .If it does, the facility deletes the oldest log file before creating the newlog file. Otherwise, the facility simply creates the new log file.

Additionally, when this attribute is modified, the service log facilityimmediately checks if the maximum number of log files according tothe new value is exceeded. If so, the facility deletes the oldest logfiles until the number reaches the maximum. Decreasing the valueof max-number-of-system-logs is one way of potentially decreasingdisk usage.

The special value 0 indicates no limit.

This attribute is ignored if stdout , stderr , or syslog is the value setfor the system-log-file-path attribute.

system-log-severity This attribute specifies the set of severity levels to be logged. Thereare 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 thenext message logged would cause the log file size to exceed thevalue of this attribute, the service log facility creates a new log insteadof appending the message to the current log.

If the log size is modified to a value that exceeds the size of thecurrent log, the service log facility closes the current log and creates anew one. All previously closed logs maintain their current size, but allsubsequently 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 setfor the system-log-file-path attribute.

TROUBLESHOOTING


Using the service log facility

Using the service log facility consists of setting applicable values forthe server logging configuration attributes.

Examples Figure 21-3 lists a possible serviceability configuration. The spooler islogging 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_spldirectory as svclog.0123-172751-385, etc. Service logging is enabled.Since the maximum number of log files is set to 5 and the maximumsize is set to 3,000,000 bytes, service logs occupy a maximum of15,000,000 bytes on disk at any given time.

Figure 21-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_splnesbitt_spl: system-server-runtime-dir = /var/spool/pd/nesbitt_splnesbitt_spl: system-log-severity = error warning audit debugnesbitt_spl: system-log-size = 3000000nesbitt_spl: system-log-file-path = svclognesbitt_spl: system-log-enabled = yesnesbitt_spl: max-number-of-system-logs = 5

Figure 21-4 shows a pdset command that resets max-number-of-system-logs to 3. Note that since the value has been decreasedfrom 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 21-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_splnesbitt_spl: cfg-server-runtime-dir = /var/spool/pd/nesbitt_splnesbitt_spl: system-log-severity = error warning audit debugnesbitt_spl: system-log-size = 3000000nesbitt_spl: system-log-file-path = svclognesbitt_spl: system-logging-enabled = yesnesbitt_spl: max-number-of-system-logs = 3

Figure 21-5 illustrates log entries for the user-level and developer-level messages.

Figure 21-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_RequestJobI 6 pa_procs.c:601 4726.876018 | PA__globalData.uNewTask = 1

TROUBLESHOOTING


Figure 21-6 and Figure 21-7 describe the elements of user-level anddeveloper-level log messages. Note that all developer-levelmessage information is for developer use only and not intended forcustomers.

Figure 21-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 21-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

TROUBLESHOOTING


Standard system logging

Non-server PrintXchange components use standard system loggingon Windows NT and UNIX. Also, a server can use standard systemlogging if the user sets the system-log-file-path attribute to syslog .

The following subsections describe standard system logging onWindows NT and UNIX. The following section on Server loggingevents lists logging messages and indicates the mapping betweenthe service log facility severity levels and the NT and UNIX messagetypes and priorities.

Standard system logging on Windows NT

System logging enables the PrintXchange components to writemessages into an event log file that users can access. Users canmanipulate and view the event log file via standard Windows NTutilities (e.g., Event Viewer Application) or via the Win32 eventlogging API. Users can use the contents of the event log file fordiagnostics and/or debugging.

PrintXchange writes the log messages into an “Application” event logfile that is one of the standard Windows NT event log files.Therefore, to see the PrintXchange log with the Event Viewer, selectApplication in the Event Viewer Log menu. The system defaultApplication event-log file path is

%SystemRoot%\system32\config\AppEvent.Evt

Users can specify a different Application event log file path using theSave As… function of the Event Viewer Log menu.

On selecting Detail… from the Event Viewer View menu, the EventViewer displays the following information:

Date: mm/dd/yyTime: hh:mm:ss PM/AM

User: N/A

Computer: Hostname of machine on which the PrintXchangeserver is

running

Event ID: 1 (always)Source: "PrintXchange"Type: Information, Warning, or ErrorCategory: 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 installationprocess or via the Registry Editor for the machine for which the eventlog is written.

If users plan to write logs into a remote host’s event log file, theremote host’s name should be set in the registry via the installationprocess or via the Registry Editor for the machine on which thePrintXchange server runs.

Registry Key:HKEY_LOCAL_MACHINE\Software\Xerox\PrintXchange\CurrentVersion\SystemLog Value: SystemLogHost: REG_SZ: Computer-name

If the registry key is not set, PrintXchange writes the system log intothe local event log file.

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 logfile. The message localization of the event log file is not done in theWindows NT way of switching the message resource DLL. Instead, itis done at the time of writing.

The events logged include descriptions generated by the services orother system components.

Standard system logging on UNIX

PrintXchange components use the UNIX syslog daemon to logcomponent events. The syslog daemon enables the servers to writemessages into a log file that users can access. Users canmanipulate and view the log file via standard UNIX facilities. Userscan 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 conditionsthat the server tracks, a priority, and the location or locations wherethe 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 corrupteddatabase)

� Panic condition

� Debug messages.

Typically, the messages are written to /var/adm/messages or to thesystem console. Users, however, can specify different destinationsfor specific events.

The events or conditions logged include messages generated by theserver, kernel, or other system processes.

TROUBLESHOOTING


Server logging events

The table below lists the server logging events for the service logfacility user severity levels:

� Error

� Warning

� Status

� Audit

� Debug.

The table indicates the mapping that takes place from the facilityseverity level to the Windows NT message type and UNIX prioritywhen the system-log-file-path attribute is set to syslog .

Table 21-2. Server logging events

MessageSeverity

LevelNT Type

UNIXPriority

(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 <job identifier> Doc <document number>]: Execution of filterscompleted successfully."

Audit Information LOG_INFO

"Acceptance of new print jobs on printer <printer name> has started." Audit Information LOG_INFO

"Acceptance of new print jobs on queue <queue name> has started." Audit Information LOG_INFO

"Acceptance of new print jobs on server <server name> has started." Audit Information LOG_INFO

"Addition of a document to job <job name> has started." Audit Information LOG_INFO

"Attribute modification of document <document name> has started." Audit Information LOG_INFO

"Attribute modification of initial-value-document <initial value document> hasstarted."


"Attribute modification of initial-value-job <initial value job> has started." Audit Information LOG_INFO

"Attribute modification of job <job name> has started." Audit Information LOG_INFO

"Attribute modification of printer <printer name> has started." Audit Information LOG_INFO

"Attribute modification of queue <queue name> has started." Audit Information LOG_INFO

"Attribute modification of server <server name> has started." Audit Information LOG_INFO

"Cancellation of document <document name> has started." Audit Information LOG_INFO

"Cancellation of job <job name> has started." Audit Information LOG_INFO

"Closing of job <job name> has started." Audit Information LOG_INFO

"Configuration attribute <attribute name> was modified." Audit Information LOG_INFO

"Configuration attribute <attribute name> was set to <attribute value>." Audit Information LOG_INFO

"Creation of initial-value-document <initial value document> on <servername> has started."


TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Creation of initial-value-document <initial value document> on <servername> has successfully completed."


"Creation of initial-value-job <initial value job> on <server name> has started." Audit Information LOG_INFO

"Creation of printer <printer name> on <server name> has started." Audit Information LOG_INFO

"Creation of queue <queue name> on <server name> has started." Audit Information LOG_INFO

"Deletion of document <document name>has started." Audit Information LOG_INFO

"Deletion of initial-value-document <initial value document> has started." Audit Information LOG_INFO

"Deletion of initial-value-job <initial value job> has started." Audit Information LOG_INFO

"Deletion of job <job name> has started." Audit Information LOG_INFO

"Deletion of printer <printer name> has started." Audit Information LOG_INFO

"Deletion of queue <queue name> has started." Audit Information LOG_INFO

"Deletion of server <server name> has started." Audit Information LOG_INFO

"Enumeration of jobs for printer <printer name> has started." Audit Information LOG_INFO

"Initial-value-document <initial value document> created on <server name>." Audit Information LOG_INFO

"Initial-value-document <initial value document> deleted from <servername>."


"Initial-value-job <initial value job> created on <server name>." Audit Information LOG_INFO

"Initial-value-job <initial value job> deleted from <server name>." Audit Information LOG_INFO

"Interruption of job <job name> has started." Audit Information LOG_INFO

"Job <job name> deleted from <server name>." Audit Information LOG_INFO

"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 name> associated with queue <queuename>."


"Logical printer <logical printer name> not associated with a queue." Audit Information LOG_INFO

TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Modification for document <document name> has started." Audit Information LOG_INFO

"Modification for job <job name> has started." Audit Information LOG_INFO

"Pausing of printer <printer name> has started." Audit Information LOG_INFO

"Pausing of queue <queue name> has started." Audit Information LOG_INFO

"Pausing of server <server name> has started." Audit Information LOG_INFO

"Pausing of server <server name> has started." Audit Information LOG_INFO

"Pausing printing of job <job name> has started." Audit Information LOG_INFO

"Physical printer <physical printer name> associated with queue <queuename>."


"Physical printer <physical printer name> not associated with a queue." Audit Information LOG_INFO

"Print submission on printer <printer name> has started." Audit Information LOG_INFO

"Printer <printer name> created on <server name>." Audit Information LOG_INFO

"Printer <printer name> deleted from <server name>." Audit Information LOG_INFO

"Promotion of job <job name> has started." Audit Information LOG_INFO

"Queue <queue name> created on <server name>." Audit Information LOG_INFO

"Queue <queue name> deleted from <server name>." Audit Information LOG_INFO

"Rejection of new print jobs on printer <printer name> has started." Audit Information LOG_INFO

"Rejection of new print jobs on queue <queue name> has started." Audit Information LOG_INFO

"Rejection of new print jobs on server <server name> has started." Audit Information LOG_INFO

"Removal of all jobs in queue <queue name> has started." Audit Information LOG_INFO

"Removal of all jobs in server <server name> has started." Audit Information LOG_INFO

"Resubmission of job <job name> to <printer name> has started." Audit Information LOG_INFO

"Resubmission of queue <queue name> to <printer name> has started." Audit Information LOG_INFO

"Resuming of printer <printer name> has started." Audit Information LOG_INFO

"Resuming of queue <queue name> has started." Audit Information LOG_INFO

"Resuming of server <server name> has started." Audit Information LOG_INFO

"Resuming printing of job <job name> has started." Audit Information LOG_INFO


"Shutdown of server <server name> has started." Audit Information LOG_INFO

"Spooler <spooler name> has successfully communicated with supervisor<supervisor name>."


TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Spooler <spooler name> shutdown has started. All current jobs will beaborted as soon as possible."


"Spooler <spooler name> shutdown has started. Shutdown will complete assoon as all currently printing jobs are finished."


"Spooler <spooler name> shutdown has started. Shutdown will complete assoon as all printable jobs are finished."


"Supervisor <supervisor name> has successfully communicated with spooler<spooler name>."


"Supervisor <supervisor name> shutdown has started. All current jobs will beaborted as soon as possible."


"Supervisor <supervisor name> shutdown has started. Shutdown willcomplete as soon as all currently printing jobs are finished."


"Supervisor <supervisor name> shutdown has started. Shutdown willcomplete as soon as all printable jobs are finished."


"Acceptance of new print jobs on printer <printer name> has successfullycompleted."

Debug Information LOG_INFO

"Acceptance of new print jobs on queue <queue name> has successfullycompleted."


"Acceptance of new print jobs on server <server name> has successfullycompleted."


"Addition of a document to job <job name> has successfully completed." Debug Information LOG_INFO

"Attribute modification of document <document name> has successfullycompleted."


"Attribute modification of initial-value-document <initial value document> hassuccessfully completed."


"Attribute modification of initial-value-job <initial value job> has successfullycompleted."


"Attribute modification of job <job name> has successfully completed." Debug Information LOG_INFO

"Attribute modification of printer <printer name> has successfully completed." Debug Information LOG_INFO

"Attribute modification of queue <queue name> has successfully completed." Debug Information LOG_INFO

"Attribute modification of server <server name> has successfully completed." Debug Information LOG_INFO

"Cancellation of document <document name> has successfully completed." Debug Information LOG_INFO

"Cancellation of job <job name> has successfully completed." Debug Information LOG_INFO

"Closing of job <job name> has successfully completed." Debug Information LOG_INFO

"Creation of initial-value-job <initial value job> on <server name> hassuccessfully completed."


"Creation of printer <printer name> on <server name> has successfullycompleted."


TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Creation of queue <queue name> on <server name> has successfullycompleted."


"Deletion of document <document name> has successfully completed." Debug Information LOG_INFO

"Deletion of initial-value-document <initial value document> has successfullycompleted."


"Deletion of initial-value-job <initial value job> has successfully completed." Debug Information LOG_INFO

"Deletion of job <job name> has successfully completed." Debug Information LOG_INFO

"Deletion of printer <printer name> has successfully completed." Debug Information LOG_INFO

"Deletion of queue <queue name> has successfully completed." Debug Information LOG_INFO

"Deletion of server <server name> has successfully completed." Debug Information LOG_INFO

"Enumeration of jobs for printer <printer name> has successfully completed." Debug Information LOG_INFO

"Interruption of job <job name> has successfully completed." Debug Information LOG_INFO

"Job <job name> has been canceled." Debug Information LOG_INFO

"Job <job name> has completed on printer <printer name>." Debug Information LOG_INFO

"Job <job name> is processing on printer <printer name>." Debug Information LOG_INFO

"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 <document name> has successfully completed." Debug Information LOG_INFO

"Modification for job <job name> has successfully completed." Debug Information LOG_INFO

"Pausing of printer <printer name> has successfully completed." Debug Information LOG_INFO

"Pausing of queue <queue name> has successfully completed." Debug Information LOG_INFO

"Pausing of server <server name> has successfully completed." Debug Information LOG_INFO

"Pausing printing of job <job name> has successfully completed." Debug Information LOG_INFO

"Print submission on printer <printer name> has successfully completed." Debug Information LOG_INFO

"Printer <printer name> has reported status on processed jobs to thespooler."


TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Printer <printer name> is no longer accepting jobs." Debug Information LOG_INFO

"Printer <printer name> is not accepting new print jobs." Debug Information LOG_INFO

"Printer <printer name> is now ready to process jobs." Debug Information LOG_INFO

"Printer <printer name> is requesting a job." Debug Information LOG_INFO

"Printer <printer name> status has changed." Debug Information LOG_INFO

"Promotion of job <job name> has successfully completed." Debug Information LOG_INFO

"Queue <queue name> is not accepting new print jobs." Debug Information LOG_INFO

"Rejection of new print jobs on printer <printer name> has successfullycompleted."


"Rejection of new print jobs on queue <queue name> has successfullycompleted."


"Rejection of new print jobs on server <server name> has successfullycompleted."


"Removal of all jobs in queue <queue name> has successfully completed." Debug Information LOG_INFO

"Removal of all jobs in server <server name> has successfully completed." Debug Information LOG_INFO

"Resubmission of job <job name> to <printer name> has successfullycompleted."


"Resubmission of queue <queue name> to <printer name> has successfullycompleted."


"Resuming of printer <printer name> has successfully completed." Debug Information LOG_INFO

"Resuming of queue <queue name> has successfully completed." Debug Information LOG_INFO

"Resuming of server <server name> has successfully completed." Debug Information LOG_INFO

"Resuming printing of job <job name> has successfully completed." Debug Information LOG_INFO

"Server <server name> is not accepting new print jobs." Debug Information LOG_INFO

"Server <server name> status has changed." Debug Information LOG_INFO

"Shutdown of server <server name> has successfully completed." Debug Information LOG_INFO

"The spool space available is <number> bytes." Debug Information LOG_INFO

“<executable>: The server database integrity check has completedsuccessfully.”

Status Information LOG_INFO

"Spooler <spooler name> created." Status Information LOG_INFO

"Spooler <spooler name> deleted." Status Information LOG_INFO

"Spooler <spooler name> has started." Status Information LOG_INFO

"Spooler <spooler name> shutdown has completed." Status Information LOG_INFO

TROUBLESHOOTING



MessageSeverity

LevelNT Type

UNIXPriority

"Supervisor <supervisor name> created." Status Information LOG_INFO

"Supervisor <supervisor name> deleted." Status Information LOG_INFO

"Supervisor <supervisor name> has started." Status Information LOG_INFO

"Supervisor <supervisor name> shutdown has completed." Status Information LOG_INFO

TROUBLESHOOTING


Notification server logging events

The table below lists the error messages that the notification servermay deliver to the standard error or system log.

For developers only: The NT type and UNIX priority map to theservice 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 levelWarning

� NT Information maps to severity level Audit

Table 21-3. Log messages

MessageNT

TypeUNIX

PriorityProblem Recovery

Refer to the section onNumbered error messages(messages with prefix 58.)

Error LOG_ERR Refer to the section on Numbered error messages(messages with prefix 58.)

“ready to serve requests” Information --- Server finishedstartupsuccessfully.

N/A

“service has stopped normally” Information --- Server stoppednormally.

N/A

(Refer to Chapter 3 messageswith prefix 58.)

Warning LOG_WARNING (Refer to Chapter 3 messages with prefix 58.)

TROUBLESHOOTING


Restrictions for e-mail notification on Windows NT

This section lists the necessary conditions for using e-mailnotification on Windows NT. These conditions must be satisfied toensure proper operation of the e-mail notification. In case theconditions 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, theoperator must specify:

� Valid personal information in “Full name” and “E-mailaddress” section under the “General” tab.

� Valid server name in the “Internet Mail Server” section underthe “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 accountabove in the “Password” section under the “General” tab.

� The operator must NOT check “Work off-line and use RemoteMail” under the “Connection” tab.

� If hostname was specified in “Internet Mail Server” (not IPaddress), the hostname must be resolved into IP address bysome means of IP address resolution available on the WindowsNT environment, such as DNS or hosts file.

� The mail server must be up and SMTP server (sendmail onUNIX) and POP server must be running on the mail server at anytime while PrintXchange is operating.

� The mail server must be network-reachable from the machinewhere PrintXchange is operating at any time while PrintXchangeis operating.

� The user must NOT change the password of the mail serveraccount at any time while PrintXchange is operating. To changethe 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).

TROUBLESHOOTING


MS-Mail notification

� When configuring the Microsoft mail property in MAPI profile, theoperator 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, automaticallyenter password” box under the “Logon” tab.

� The operator must check the “Enable outgoing mail delivery” boxunder the “Delivery” tab.

� The operator must NOT check any box under the “LANconfiguration” tab.

� If the postoffice is located on the network drive, it must beaccessible 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 anytime while PrintXchange is operating.


MS Exchange notification

� When configuring the Microsoft Exchange Server mail property inMAPI profile, the operator must specify:

� Valid MS Exchange server name in the “MS Exchangeserver” 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 themachine where PrintXchange is operating at any time whilePrintXchange is operating.


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 prefixindicates the PrintXchange component that generates the error.

The sequence number identifies an error within each prefix group.

Table 21-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)


16 Server (spooler and supervisor objects)




49 LPR inbound gateway for NT

52 LAN Manager inbound gateway for NT

56 QServer inbound gateway for NT

58 Notification server

59 Accounting

TROUBLESHOOTING


Table 21-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 startdue to dependency on PrintXchange Name Service, contact technicalsupport.

CAUTION: When pdprintinfo is executed on a remote UNIX machinewith the display option, avoid inducing a crash by setting theDISPLAY variable to the local machine.

TROUBLESHOOTING


Table 21-5. Error number, message, explanation, systemresponse, and required action

ERRORNUMBER

MESSAGE EXPLANATION SYSTEMRESPONSE

REQUIRED ACTION

1-101 "Unable to create adocument in thedatabase."

This error may be causedby a memory corruption inthe server, a lack ofavailable disk space or alack of available virtualmemory.

The requestis notprocessed.

Check the available memoryand retry the operation. If theproblem persists, contacttechnical support.

1-102 "Unable to delete adocument from thedatabase."

This error may be causedby a memory corruption inthe server or a corruption inthe object database.


Retry the operation. If theproblem persists, contacttechnical support.

1-103 "Unable to obtainattributes for thedocument."

This error may be causedby a memory corruption inthe server, a corruption inthe object database or alack of virtual memory.



1-104 "Unable to obtain aread lock for thedocument."

This error may be causedby a memory corruption inthe server, or a corruptionin the object database.



1-105 "Unable to setattributes on thedocument."




1-106 "Unable to unlock thedocument."




1-107 "Unable to obtain awrite lock for thedocument."




1-108 "An error occurredwhile retrieving thedocument state."

This error may be causedby a memory corruption inthe server or a lack ofavailable virtual memory



1-109 "The file transferagent failed to deletethe document data."

The requested deletion mayhave contained an incorrectfile name or file path.


Check the spelling of the filename and the file path beforeretrying the operation. If theproblem persists, contacttechnical support.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

1-110 "The file transferagent failed totransfer the documentdata."

This error may be causedby using file referencetransfer method on a filethat is not accessible to theserver. In addition, thiserror also may be causedby a memory corruption inthe server or a lack ofavailable virtual memory.



1-111 "The documentdescriptor passed tothe server is invalid."

This error may be causedby a memory corruption inthe server.



1-112 “The document stateis invalid.”




1-113 "The function callfailed due to aninvalid parameter."




1-114 "The function callfailed due to aninvalid fourthparameter."




1-115 "Unable to obtainattributes for thespecified initial valuedocument."




1-116 "Unable to obtain aread lock for the initialvalue document."




1-117 "Unable to obtainattributes for the job."




1-118 "Unable to obtain aread lock for the job."




1-119 "Unable to setattributes on the job."




1-120 "Unable to unlock thejob."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

1-121 "Unable to obtain awrite lock for the job."




1-122 "Unable to modify/setdocument attributes."




1-123 "The modify operationfailed in thesupervisor."

This error may be causedby a memory corruption inthe server or a lack ofavailable virtual memory.



1-124 "The documentattribute set ismissing the requiredattribute document-sequence-number."




1-125 "The document ismissing the requiredattribute document-content."




1-126 "The documentparameter attributeset is missing therequired attribute job-identifier."




1-127 "The documentattribute set ismissing the requiredattribute transfer-method."




1-128 "Unable to obtainattributes for theprinter."




1-129 "An error hasoccurred in theattribute set facility."




1-130 "An unknown errorhas occurred in thedocument objectlibrary."




1-131 "An error hasoccurred in thegeneric utilitiesfacility."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

1-132 "The document is inan unknown state."




1-133 "A system error hasoccurred."




1-134 "The document failedto delete someattributes beforesending an event."




1-135 "An error hasoccurred in the eventhandler."




1-136 "An error hasoccurred in theinternal job facility."




1-137 "An error hasoccurred in the eventnotification agent."




1-138 "There was notenough disk space tospool the documentdata."

The disk space required forthis operation is insufficient.


Check the available diskspace and retry the operation.If the problem persists,contact technical support.

1-139 "The server could notspool the documentdata because thespool threshold hasbeen reached."

There is no available spaceto spool the document.


Wait for some existing jobs tocomplete and retry theoperation. If the problempersists, contact technicalsupport.

4-101 "The initial valuedocument identifier isinvalid."

The initial value documentname may already exist.


Resubmit the document usinganother name. If the problempersists, contact technicalsupport.

4-102 "An error hasoccurred duringinitialization of theinitial valuedocument."



Check the availability of thevirtual memory and retry theoperation. If the problempersists, contact technicalsupport.

4-103 "An internal error hasoccurred in the initialvalue document."





This error may be causedby a memory corruption inthe server, a lack ofavailable virtual memory ora lack of disk space.


Check the availability of thevirtual memory and theavailable disk space in thedatabase (or spool partitions)before retrying the operation.If the problem persists,contact technical support.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

4-105 "An error hasoccurred in the objectdatabase facility."

This error may be causedby a memory corruption inthe server or a corruption inthe object database. It mayalso be caused by a lack ofavailable virtual memory ora lack of disk space.







4-107 "An error hasoccurred in theattribute set facility;however, theoperation completedsuccessfully!"




4-108 "An error hasoccurred in theCommon ServerUtilities facility."




4-109 "There is insufficientmemory on the serverto perform therequested operation."

This error may be causedby a lack of available virtualmemory.



4-110 "The requested initialvalue document wasnot found."

The requested initial valuedocument does not exist onthe server or may existunder a different name.


Check the spelling of theinitial value document andretry the operation. If theproblem persists, contacttechnical support.

4-111 "The requested initialvalue documentalready exists."

A document with the samename has been found onthe server.


Choose another name for theinitial value document andretry the operation. If theproblem persists, contacttechnical support.

4-112 "The requestedreference initial valuedocument was notfound."

The initial value documentdoes not exist.


Check the spelling of the initialvalue document and retry theoperation. If the problempersists, contact technicalsupport.

4-113 "The initial valuedocument was notlocked."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

4-114 "The requested initialvalue document isalready locked."




4-115 "Unable to obtain alock for the initialvalue document."




4-116 "An invalid attributeset was passed to theobject databasefacility."




4-117 "A transaction errorhas occurred in theobject database."




5-101 "The initial value jobidentifier is invalid."

The initial value job namemay already exist.



5-102 "An error hasoccurred duringinitialization of theinitial value job."




5-103 "An internal error hasoccurred in the initialvalue job."







Check the memory on theserver and retry the operation.If the problem persists,contact technical support.


This error may be causedby a memory corruption inthe object database, a lackof available disk space or alack of available virtualmemory.


Check the possible causesabove and retry the operation.If the problem persists,contact technical support.





5-107 "An error hasoccurred in theattribute set facility;however, therequested operationcompletedsuccessfully!"




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

5-108 "An error hasoccurred in theCommon ServerUtilities facility."



Check the memory on theserver and retry the operation.If the problem persists,contact technical support.

v5-109 "There is insufficientmemory on the serverto perform therequested operation."



Check the available virtualmemory on the server andretry the operation. If theproblem persists, contacttechnical support.

5-110 "The requested initialvalue job was notfound."

The initial value job namemay have been enteredincorrectly or may not exist.


Check the spelling of theinitial value job and retry theoperation. If the problempersists, contact technicalsupport.

5-111 "The requested initialvalue job alreadyexists."

An initial value job with thesame name has been foundon the server.


Choose another name for theinitial value job and retry theoperation. If the problempersists, contact technicalsupport.

5-112 "The requestedreference initial valuejob was not found."

The initial value jobreference does not exist onthe server.


Check the spelling of theinitial value job and retry theoperation. If the problempersists, contact technicalsupport.

5-113 "The initial value jobwas not locked."




5-114 "The requested initialvalue job is alreadylocked."




5-115 "Unable to obtain alock for the initialvalue job."




5-116 "An invalid attributeset was passed to theobject databasefacility."



Check the object databaseand retry the operation. If theproblem persists, contacttechnical support.




Check the object databaseand retry the operation. If theproblem persists, contacttechnical support.

v6-101 "The job-ownerattribute in thecommon argumentsmust contain a hostname."

This error may be causedby a memory corruption onthe server.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-102 "The document ismissing the requiredattribute copy-count."




6-103 "The documentdescriptor is missingthe required attributedocument-sequence-number."




6-104 "The job attribute setis missing therequired attribute job-identifier."




6-105 "The job-ownerattribute must bespecified or containedin the commonarguments."




6-106 "The job is missingthe required attributejob-owner."




6-107 "The job is missingthe required attributejob-state."




6-108 "The document ismissing the requiredattribute octet-count."




6-109 "A printer name mustbe specified."




6-110 "The job is missingthe required attributeprinter-name."




6-111 "The job is missingthe required attributeprinters-assigned."




6-112 "A required attributewas not found in theattribute set."




6-113 "Job modificationerror: Nomodification attributeswere provided."

The necessary modificationattributes were not entered.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-114 "Unable to performthe requestedoperation; the job isalready closed."

The job has been closedand is not responding to therequest.



6-115 "Unable to obtainattributes for thedocument."

This error may be causedby a memory corruption inthe server, a corruption inthe object database or alack of available virtualmemory.



6-116 "The document statetransition has failed."

The document statetransition did not completesuccessfully.



6-117 "Unable to obtain aread lock for thedocument."




6-118 "Unable to unlock thedocument."




6-119 "Unable to obtain awrite lock for thedocument."




6-120 "Unable to obtainattributes for the initialvalue job."




6-121 "Unable to obtain aread lock for the initialvalue job."




6-122 "An error hasoccurred whileattempting to cancelthe job."




6-123 "Unable to create ajob in the database."

This error may be causedby a memory corruption inthe server, a corruption inthe object database or alack of available disk space.



6-124 "Unable to delete thejob from thedatabase."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-125 "Unable to generate anew job identifier."




6-126 "Unable to generate anew documentnumber."




6-127 "Unable to obtainattributes for the job."




6-128 "Unable to set theattributes on the job."

This error may be causedby a memory corruption inthe server, a corruption inthe object database, a lackof available disk space or alack of available virtualmemory.


Check the available virtualmemory and the availabledisk space in the database (orspool partitions) beforeretrying the operation. If theproblem persists, contacttechnical support.

6-129 "Unable to unlock thejob."




6-130 "Unable to obtain awrite lock for the job."








6-132 "Unable to obtain aread lock for theprinter."




6-133 "The queue managerfailed to add the jobto the requestedqueue."



Check available virtualmemory and retry theoperation. If the problempersists, contact technicalsupport.

6-134 "The queue managerfailed to delete the jobfrom the requestedqueue."




6-135 "Unable to report jobmodification to thequeue manager."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-136 "Unable to report jobstate change to thequeue manager."




6-137 "The queue wasunable to promote therequested job."




6-138 "Unable to obtainattributes for theserver."




6-139 "Unable to obtain aread lock for theserver."




6-140 "An error hasoccurred in theinternal job facility"



Check the available virtualmemory and retry theoperation. If the problempersists, contact technicalsupport.


This error may be causedby a memory corruption inthe server






Check the available virtualmemory and the availabledisk space in the database (orspool partitions) beforeretrying the operation. If theproblem persists, contacttechnical support.

6-143 "An error hasoccurred in the timeragent."








6-145 "An error hasoccurred in thegeneric utilitiesfacility; copy failed."




6-146 "An error hasoccurred in the eventnotification agent."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-147 "An error hasoccurred in the timeragent."








6-149 "The job objectmanager was unableto obtain a queuename from theprinter."




6-150 "An invalid statetransition wasrequested."




6-151 "An unknown erroroccurred whileperforming therequested statetransition."




6-152 "The job is not in avalid state to performthe requestedoperation."

The specified operationcannot be applied to the jobin its current state.


Consult the SystemAdministration and OperationGuide for the valid objectstates. The operation maysucceed later when the objecttransitions to a valid state.

6-153 "The queue is not in avalid state to performthe requestedoperation."

The specified operationcannot be applied to thequeue in its current state.


Consult the SystemAdministration and OperationGuide for the valid objectstates.

6-154 "The queue assignedto the requested jobcannot be found inthe database."

This error may be causedby a memory corruption inthe server. It may alsooccur after job recovery.


Verify that the queue does notalready exist and recreate thequeue. If the problempersists, contact technicalsupport.

6-155 "The job cannot befound in the queue towhich it wasassigned."




6-156 "Unable to processinternal statetransitions."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-157 "An error hasoccurred whileprocessing themodificationattributes."




6-158 "The event sent to thejob came from aninvalid printer."

The job will not process anevent from an invalidprinter.



6-159 "The required jobattributes job-identifier andphysical-printer-namewere not passed tothe supervisor."

This error may be causedby attributes missing fromthe job.



6-160 "The job submitterfailed to add the jobto the list."




6-161 "An error hasoccurred in the eventhandler."




6-162 "The job failed todelete some of itsattributes beforesending an event."




6-163 "Unable to delete thejob from thedatabase."




6-164 "Document Processorcallback failed toperformAddDocumentnotification."

This error may be causedby an internal server erroror a corruption in the objectdatabase.



6-165 "Document Processorcallback failed toperform CloseJobnotification."




6-166 "Document Processorcallback failed toreset the job requestlist."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-167 "Document Processorfailed due to aninvalid job identifier orinvalid job."

This error may be causedby a corruption in the jobobject.



6-168 "Document Processorfailed due to aninvalid document."

This error may be causedby a corruption in thedocument object.



6-169 "Document Processorwas not in the correctstate for thisoperation."




6-170 "Document Processorfailed due to aninternal job error."




6-171 "Document Processorfailed due to aninternal documenterror."




6-172 "Document Processorfailed because thetime limit forperforming therequest wasexceeded."




6-173 "Document Processorfailed because it doesnot support thisrequest."

An attempt was made tomodify job or documentattributes on the supervisor.This feature is notsupported.


None





6-175 "Document Processorfailed due to a systemerror."




6-176 "Document Processorfailed due to anunknown error."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

6-177 "Document Processorfailed due to aninvalid documentnumber."



Enter a valid documentnumber and retry theoperation. If the problempersists, contact technicalsupport.

6-178 "Document Processorfailed due to aninvalid modificationattribute."

Modification on a restrictedattribute is not allowed.



6-179 "Document Processorfailed due to anunsupportedmodificationattribute."

Modification on a restrictedattribute is not allowed.







6-183 "An unknown erroroccurred duringprocessing of theuser request."




7-103 "<executable>:Unable to access thedirectory: <path>"

This is a general access ()error.


Check the specified directory.If the problem persists,contact technical support.

7-104 "<executable>:Unable to change thedirectory: <path>"

The system call, chdir(),has failed.



7-105 "<executable>:Unable to create thedirectory: <path>"

Unable to create thedirectory specified.



7-106 "<executable>:Unable to create achild process."

Unable to create a childprocess.


Reboot the system. If theproblem persists, contacttechnical support.

7-107 "<executable>:Unable to determinethe current directory."

The system call, getcwd()failed.



7-108 "<executable>:Unable to get the IPaddress of the host."

The system call,gethostbyname() failed.


Check the host name andmachine configuration for theIP address.

7-109 "<executable>:Unable to initialize theobject database."

Unable to set the databasedirectories due to a lack ofmemory or system error.


Contact technical support.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

7-110 "<executable>:Unable to initialize theserver due to thefollowing: <path>"

This error may be causedby an invalid OID pathspecified via the -O flag.


Check the command linesyntax and the environmentvariable PD_OID_DB_PATH.If the problem persists,contact technical support.

7-111 "<executable>:Unable to initialize theRPC facility."

A system error hasoccurred.


Check system resources. Ifthe problem persists, contacttechnical support.

7-113 "<executable>:Unable to obtain alock for the server inthe database:<database path> /<server name>"

A database error hasoccurred.



7-114 "<executable>:Unable to lock theserver lock file:<path/lock filename>."

A system call has failed. The requestis notprocessed.


7-115 "<executable>:Unable to open theobject database dueto the following:<reason>"

An unknown database errorhas occurred.



7-116 "<executable>:Unable to open theserver lock file:<path/lock filename>"

Unable to open the serverlock file since another utilityis already running.


Check to see if the pdmakedbutilities and pdaccount arerunning. Make sure that aserver with the same name isnot currently running.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

7-117 "<executable>:Unable to registerwith the name servicedue to the following:<reason>"

A general name serviceerror has occurred.


Make sure the name servicecontains the server name.For UNIX platforms: Makesure that the “printers” entry in/etc/nsswitch.conf file iscorrect. If the NIS nameservice is being used, makesure the NIS server containsthe server name. If problempersists, contact technicalsupport.

For NT platforms: Make surethe Program Registry Groupcontains the server name.Once this is verified, removethe server entry from thename space using the“namerm” command. Forexample, the command“namerm –a –c spoolertulip_spl” will delete all logicalprinters and queuesassociated with the spooler(spooler tulip_spl) and thespooler itself from the namespace.

7-118 "<executable>:Unable to registerwith the RPC servicedue to the following:<reason>"

A general RPC serviceerror has occurred.



7-119 "Unable to registerthe RPC transports."

The RPC facility is notavailable or there is anetwork problem.


Check network configuration.If the problem persists,contact technical support.

7-120 "<executable>:Unable to determinethe file type: errno =<error number> :<path>"

The system call, stat(),failed.



7-121 "<executable>:Unable to unlock thedatabase serverobject: <databasepath> / <servername>"




7-127 "<executable>:Unable to access theobject databasedirectory: <databasepath>"

The request failed since itcould not find the serverdatabase directory .



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

7-128 "<executable>: Thedatabase does notexist: <databasepath> / <servername>"

The server database maynot exist (or an invalid -dpath may have beenentered).


Ensure that the databaseexists and that the -d pathwas entered correctly. If theproblem persists, contacttechnical support.

7-130 "An error hasoccurred starting theprint server <errornumber> on <hostname> due to thefollowing: <reason>"

This is the body of an e-mail error message.


Refer to the error messagespecified.

7-132 "PrintXchange ServerStartup failure."

The server has failed tostart properly due to



7-134 "<executable>:Unable to determinesystem host name:errno = <errornumber><hostname>"

A system error hasoccurred.



7-136 "<executable>: Anerror has occurredwhile calling the I18Nlibrary."

A PrintXchange sub-moduleerror has occurred.



7-137 "<executable>: Anerror has occurredwhile setting thelocale <locale>"

The system call, setlocale(),failed.



7-138 "<executable>: Theserver may becurrently running. Ifthis is the case, theserver lock file hasalready been locked:<lock file>."

The lock file has beenopened by other utilities ora server with a same name.


Check to see if the pdmakedbutilities and pdaccount arerunning. Make sure that aserver with the same name isnot currently running.

7-141 "<executable>:Unable to access therequested directory:<path>"

Search permission hasbeen denied.


Check the path and thepermissions for the requesteddirectory.

7-142 "There are noavailable dynamicprogram numbers."

A system error occurredwhile trying to register anRPC.



7-143 "<executable>: Thereis insufficient memoryon the server toperform therequested operation."



Reboot the system andrestart PrintXchange. If theproblem persists, contacttechnical support.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

7-146 "<executable>: Thespecified pathname isnot absolute: <path>"

A relative pathname hasbeen entered.


Change the command optionusing an absolute path andrestart PrintXchange.

7-147 "<executable>: Therequested file is not adirectory: <path>"

The user has passed anillegal pathname.


Change the command optionusing an absolute path andrestart PrintXchange.

7-158 "<executable>: Anerror has occurred inthe thread facility."




7-161 "<executable>: Thisis an unexpectedserver type for theserver: <servername>"

An invalid server name ordatabase has been used.


Correct the server name. Ifthe problem persists, contacttechnical support.

7-163 "<executable>: Anunknown error hasoccurred."

An unknown system errorhas occurred.



7-164 "<executable>: Thelocale is unknown."

The locale does not exist inthe server database.



7-165 "The server name isunknown."

The sever failed to createthe server name.



7-166 "<executable>: Theserver type isunknown for server:<server name>"

An invalid server name ordatabase has been used.


Correct the server name. Ifthe problem persists, contacttechnical support.

7-174 "<executable>: The<server name> iscurrently running."

A server with the samename is already running.


Check the server name. If theproblem persists, contacttechnical support.

7-175 "<executable>: Thecorrupt objectdatabase has beenrecovered. Toacknowledge, pleaserestart using thefollowing commandline: <command>"

The server has recoveredits database.


Restart with therecommended command lineoption.

7-176 "<executable>:Unable to set theserver attributes."

A database or memoryerror has occurred.



7-177 "<executable>:Unable to retrieve theserver attributes."

A database or memoryerror has occurred.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

7-179 "<executable>: The<environment root> isnot found in theenvironmentvariables."

This error is caused byimproper installation or anincorrect registryconfiguration.


Check the registry. If theproblem persists, contacttechnical support.

7-184 "<executable>: Adatabase error hasoccurred."




7-188 "<executable>: Anerror has occurred inthe attribute setfacility."




7-190 "<executable>: Anerror has occurred inthe file nameconversion utility."




7-201 "<executable>:Unable to create the.databaseOpen file."



7-205 "<executable>:Unable to recoverserver object from acrash."

The PrintXchange serverhas failed to recover.



7-206 "<executable>:Unable to set aserver event."



7-208 "<executable>: Thecorrupt objectdatabase has beenrecovered. Toacknowledge, pleaserestart <executable>from the \ “Services \”by passing \”-a \”option in the \”StartupParameters\”

The server has recoveredits database.


Restart with therecommended command lineoption.

7-213 "<executable>:Unable to delete anentry in the namespace. Pleaseremove <objectname> <name spaceenvironment>."

Could not delete serverentry from name space.



7-214 "<executable>:Unable to create anentry in the namespace. Pleaseremove <objectname> <name spaceenvironment>."

Could not delete serverentry from name space.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

12-101 "The printer is alreadydisabled."

An attempt was made todisable an already disabledprinter.


None

12-102 "The printer is alreadyenabled."

An attempt was made toenable an already enabledprinter.


None

12-103 "An error hasoccurred in anattribute set facility."




12-104 "Unable to registerprinter object with thename service."

The user has attempted tocreate a physical printerusing an existing logicalprinter name.


Retry the operation using adifferent name. If theproblem persists, contacttechnical support.

12-105 "The printer must bedisabled beforedeletion."

The printer has not beendisabled.


Disable the printer and retrythe operation. If the problempersists, contact technicalsupport.

12-106 "An error hasoccurred in the printeraction facility."




12-107 "A data processingoperation has failed."




12-108 "The requestedprinter already exists;forced creation is notavailable."

Forced creation is notsupported.


The existing printer should bedeleted and then recreated.





12-110 "An event wasignored."

An event has been ignored. The requestis notprocessed.

None

12-111 "An error hasoccurred in theinternal printerfacility."




12-112 "The client passed aninvalid argument."

The argument that waspassed by the client isinvalid.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

12-113 "The state transitionrequested is invalid."

The state transition isinvalid.



12-114 "Unable to obtain alock for the printer."




12-115 "Unable to obtain alock for the queue."




12-116 "Unable to obtain alock for the server."




12-117 "The printer must bedisabled beforemoving to a newqueue."

The printer has not beendisabled.


Disable the printer.

12-118 "The access controllist is missing in theargument or on theserver."




12-119 "The printer ismissing the requiredattribute printer-model."

The user attempted tocreate a physical printerwithout specifying theprinter-model attribute.


Specify the printer-modelattribute.

12-120 "The printer has noassociated-queue."

The user attempted toenable a physical printerthat does not have anassociated-queue attribute.


Add an associated-queueattribute using a pdsetcommand.

12-121 "The printer was notfound."

The requested printer doesnot exist.


None

12-122 "An error hasoccurred in the namespace facility."

This error may be causedby a problem with theprotoserver.



12-123 "The requestedprinter alreadyexists."

There is no need to createthis printer.


None

12-124 "A required objectcould not be found inthe object databasefacility."








TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

12-126 "The maximumnumber of printerssupported has beenreached.

No more printers may beadded.


Check the values of thenumber-of-printers-supportedand maximum-number-of-printers-supported attributes.

12-127 "The event handlerfailed to send anevent."








12-129 "An error hasoccurred in theinternal serverfacility."




12-130 "The internal stategiven is out ofbounds."

The state is invalid. The requestis notprocessed.


12-131 "This operation isunsupported forprinters."

A printer cannot performthis operation.


Check the command syntaxto ensure that the operationand object names are valid.

12-132 "Unable to update thelogical printer."




12-133 "The updatingprocess for the newphysical printers hasfailed."




12-134 "The updatingprocess for the newassociated queue hasfailed."




12-135 "The updatingprocess for the oldphysical printers hasfailed."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

12-136 "The updatingprocess for the oldassociated queue hasfailed."




12-137 "The updatingprocess for the otherobjects has failed."




12-138 "The value of default-user-job-prioritycannot be greaterthan the value ofmax-user-job-priority."

The former attribute valuecannot be greater than thelatter.


Lower the value of thedefault-user-job-priorityattribute and retry theoperation. If the problempersists, contact technicalsupport.

12-139 "Supervisor cannotconnect to more thanone spooler."

An attempt was made toenable a physical printerthat has an associatedqueue that is on a differentspooler than the otherphysical printers on thesupervisor. The supervisorcan only connect to onespooler.


Modify the associated-queueattribute of the physicalprinter.

12-140 "The printer has noprinter-address."

The user attempted toenable a physical printerthat does not have aprinter-address attribute.


Add a printer-addressattribute using a pdsetcommand.

13-101 "The requestedreference queue wasnot found."

The queue does not exist. The requestis notprocessed.

Set up the queue and retry theoperation. If the problempersists, contact technicalsupport.

13-102 "The requestedqueue already exists."

There is already a queue bythat name on the server.


Choose another name andretry the operation. If theproblem persists, contacttechnical support.

13-103 "An internal erroroccurred duringoperation."

This error may be causedby a memory corruption inthe server, lack of availablevirtual memory or lack ofavailable disk space.



13-104 "The queue was notfound in the system."

The queue does not existon the server.


Create a queue and retry theoperation. If the problempersists, contact technicalsupport.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

13-105 "The queue must bedisabled beforedeletion."

The system will not allowenabled queues to bedeleted.


Disable the queue and retrythe operation. If the problempersists, contact technicalsupport.

13-106 "The queue is alreadydisabled."

There is no need to disablethe queue. It may either beenabled or deleted.


None

13-107 "The queue is alreadyenabled."

The queue has beenenabled previously.


None

13-108 "The queue is alreadypaused."

The queue has beenpaused previously.


None

13-109 "The queue is alreadyresumed."

The queue has beenresumed previously.


None

13-110 "All jobs have notbeen deleted from thequeue."

The remaining jobs need tobe deleted beforeproceeding.


Delete the remaining jobs andretry the operation. If theproblem persists, contacttechnical support.

13-111 "The queue iscurrently beingcleaned."

The queue is unavailable atthis time due to the cleaningprocess.


Wait for the queue to becleaned and proceed.

13-112 "The queue iscurrently resubmittingjobs."

The queue is unavailable atthis time due to theresubmission process.


Wait for the jobs to beresubmitted and proceed.

13-113 "The queue is in aninvalid state toperform therequested operation."

The queue is disabled orotherwise unavailable toperform the operation.


Enable the queue andproceed.

13-114 "Unable to registerqueue object withname service."




13-115 "The requestedqueue already exists;forced creation is notavailable."

The creation operation isnot necessary.


None

13-116 "The queue must bedisabled beforeperforming the cleanoperation."

The queue cannot becleaned while in theenabled or auto-disabledstate.


Disable the queue andproceed.

13-117 "The queue must bedisabled beforeperforming theresubmit operation."

The queue cannot performthe resubmit operationwhile in the enabled orauto-disabled state.


Disable the queue andproceed.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

13-118 "WARNING: Somejobs did not resubmitsuccessfully.Resubmit the jobsindividually todetermine cause."

The job resubmissionprocess is incomplete.


Resubmit the jobs.

13-119 "A queue by thatname already exists.Please use anothername."

The server does not allowduplicate queue names.


Rename the queue andproceed.

13-121 "The value of queue-backlog-lower-limitcannot be greaterthan the value ofqueue-backlog-upper-limit."

The system requires thatthe value of the upper limitbe greater than the value ofthe lower limit.


Modify the value of the lowerlimit to be lower than theintended upper limit, or raisethe upper limit to be higherthan the lower limit.

14-101 "Printer <printername> is alreadydisabled."

The user is attempting todisable a printer that isalready disabled.


None

14-102 "Queue <queuename> is alreadydisabled."

The user is attempting todisable a queue that isalready disabled.


None

14-103 "Server <servername> is alreadydisabled."

The user is attempting todisable a server that isalready disabled.


None

14-104 "Printer <printername> is alreadyenabled."

The user is attempting toenable a printer that isalready enabled.


None

14-105 "Queue <queuename> is alreadyenabled."

The user is attempting toenable a queue that isalready enabled.


None

14-106 "Server <servername> is alreadyenabled."

The user is attempting toenable a server that isalready enabled.


None

14-107 "Printer <printername> is alreadypaused."

The user is attempting topause a printer that isalready paused.


None

14-108 "Queue <queuename> is alreadypaused."

The user is attempting topause a queue that isalready paused.


None

14-109 "Server <servername> is alreadypaused."

The user is attempting topause a server that isalready paused.


None

14-110 "Job <job name> isalready paused."

The user is attempting topause a job that is alreadypaused.


None

14-111 "Printer <printername> is alreadyresumed."

The user is attempting toresume a printer that hasalready been resumed.


None

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-112 "Queue <queuename> is alreadyresumed."

The user is attempting toresume a queue that hasalready been resumed.


None

14-113 "Server <servername> is alreadyresumed."

The user is attempting toresume a server that hasalready been resumed.


None

14-114 " Job <job name> isalready resumed.”

The user is attempting toresume a job that hasalready been resumed.


None


An unknown system errorhas occurred in the attributeset facility.



14-116 "Attribute <attributename> is invalid forthe document."

The specified attribute isnot a document attribute.


Verify that the attribute is validfor the object class.

14-117 "Attribute <attributename> is invalid forthe initial valuedocument."

The specified attribute isnot applicable for the initialvalue document.


Verify that the attribute is validfor the initial value document.

14-118 Attribute <attributename> is invalid forthe initial value job.

The specified attribute isnot an initial value jobattribute.


Verify that the attribute is validfor the initial value job.

14-119 Attribute <attributename> is invalid forthe job.

The specified attribute isnot a job attribute.


Verify that the attribute is validfor the job.

14-120 Attribute <attributename> is invalid forthe printer.

The specified attribute isnot a printer attribute.


Verify that the attribute is validfor the printer.

14-121 Attribute <attributename> is invalid forthe queue.

The specified attribute isnot a queue attribute.


Verify that the attribute is validfor the queue.

14-122 Attribute <attributename> is invalid forthe server.

The specified attribute isnot a server attribute.


Verify that the attribute is validfor the server.

14-123 Attribute <attributename> is invalid forthis operation.

The specified attribute isinvalid for the requestedoperation.


Verify that the attribute is validfor the requested operation.

14-124 Value <value> is outof range <range>.

The specified value is not inthe specified range.


Verify that the value is validfor the range.

14-125 "Attribute not found orcorrupt."

An expected attribute is notpresent due to an error inthe system or clientapplication.



14-126 "The server type isinvalid."

The server type contains anunexpected value.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-127 "The queue cannotbe enabled atcreation."

Enabling the queue duringthe create operation is notsupported by the server.


Create the queue; thenenable it.

14-128 "The printer cannotbe enabled atcreation."

Enabling the printer duringthe create operation is notsupported by the server.


Create the printer; thenenable it.

14-129 "Queue <queuename> must bedisabled beforedeletion."

Unable to delete an enabledqueue.


Disable the queue prior todeletion.

14-130 "Printer <printername> must bedisabled beforedeletion."

Unable to delete an enabledprinter.


Disable the printer prior todeletion.

14-131 "Server <servername> must bedisabled beforedeletion."

Unable to delete an enabledserver.


Disable the server prior todeletion.

14-132 "Unable to obtain thedefault values for thedocument attributes."

The default values for thedocument attributes couldnot be obtained due to amemory corruption in thesystem or an error in theclient application.



14-133 "An unknown errorhas occurred."

A system error hasoccurred. The informationregarding the error is notpresent.



14-134 "Filter item <filter itemname> is invalid forthe queue."

An attribute in the filterexpression is not a queueattribute.


Verify that the filter item isappropriate for the queue.

14-135 "Filter item <filter itemname> is invalid forthe printer."

An attribute in the filterexpression is not a printerattribute.


Verify that the filter item isappropriate for the printer.

14-136 "Filter item <filter itemname> is invalid forthe server."

An attribute in the filterexpression is not a serverattribute.


Verify that the filter item isappropriate for the server.

14-137 "Filter item <filter itemname> is invalid forthe document."

An attribute in the filterexpression is not adocument attribute.


Verify that the filter item isappropriate for the document.

14-138 "Filter item <filter itemname> is invalid forthe initial valuedocument."

An attribute in the filterexpression is not an initialvalue document attribute.


Verify that the filter item isappropriate for the initial valuedocument.

14-139 "Filter item <filter itemname> is invalid forthe initial value job."

An attribute in the filterexpression is not an initialvalue job attribute.


Verify that the filter item isappropriate for the initial valuejob.

14-140 "Filter Item <filter itemname> is invalid forthe job."

An attribute in the filterexpression is not a jobattribute.


Verify that the filter item isappropriate for the job.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-141 "Filter item <filter itemname> is invalid forthis operation."

An attribute in the filterexpression is not applicableto the current operation.


Verify the filter expression.

14-142 "Filter item <filter-item-name> is notsingle-valued.

An attribute in the filterexpression is a single-valued attribute and cannotbe assigned multiplevalues.


Verify the filter expression.

14-143 "A filter item containsan invalid type."

The server encountered aninvalid or an unsupportedattribute type in the filterexpression. The objectidentifier database may notbe up to date or there maybe a memory corruption.



14-144 "Forced creation isnot available."

The object with thespecified name alreadyexists. The system cannotcreate another object of thesame object class with thesame name.


First delete the existingobject, then create a new one.


An unknown error hasoccurred in the genericutilities facility.



14-146 "The documentcontent isinconsistent with thetransfer method."

The server hasencountered anunsupported transfermethod (or invaliddocument content). Thismay be due to an error inthe client applicationprogram or a memorycorruption in the server.



14-147 "An attribute value iscorrupt."

The server encountered acorrupted attribute value.This may be due to eitherobject database corruptionor memory corruption.



14-148 "Attribute <attributename> is not multi-valued.

The specified attribute isnot a multi-valued attributeand cannot be assignedmore than one value.


Verify the attribute type.

14-149 "The object class forGetOrderedJobs isinvalid."

The server encountered aninvalid object class for theGetOrderedJobs (or pdq)operation. This may be dueto an error in the clientapplication program or amemory corruption in theserver. The only validobject class for thisoperation is printer.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-150 "The scope option isvalid for jobs only."

The scope option wasspecified for an object otherthan a job.


Check the command linesyntax.

14-151 "The continuationcontext is invalid."

The server encountered aninvalid continuation contextfor the list operation (pdq orpdls). This may be due toan error in the clientapplication program or amemory corruption in theserver.



14-152 "The credential isinvalid."

The user is unknown to thesystem.


The user must be added tothe access control list.

14-153 "The documentnumber is invalid."

The specified document isunknown to the server.


Verify the job identifier andthe document number.

14-155 "The operation isinvalid for thephysical printer."

The physical printer is notable to process therequested operation.


The requested operation isnot valid for the physicalprinter.

14-156 "The operation isinvalid for the logicalprinter."

The logical printer is notable to process therequested operation.


The requested operation isnot valid for the logical printer.

14-157 "The operation isinvalid for thedocument."

The document is not able toprocess the requestedoperation.


The requested operation isnot valid for the document.

14-158 "The operation isinvalid for the initialvalue document."

The initial value documentis not able to process therequested operation.


The requested operation isnot valid for the initial valuedocument.

14-159 "The operation isinvalid for the job."

The job is not able toprocess the requestedoperation.


The requested operation isnot valid for the job.

14-160 "The operation isinvalid for the initialvalue job."

The initial value job is notable to process therequested operation.


The requested operation isnot valid for the initial valuejob.

14-161 "The operation isinvalid for the queue."

The queue is not able toprocess the requestedoperation.


The requested operation isnot valid for the queue.

14-162 "The operation isinvalid for thespooler."

The spooler is not able toprocess the requestedoperation.


The requested operation isnot valid for the spooler.

14-163 "The operation isinvalid for thesupervisor."

The supervisor is not ableto process the requestedoperation.


The requested operation isnot valid for the supervisor.

14-164 "Unknown objectclass."

The object class isunknown or unsupported.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-165 "Queue <queuename> is currentlynot available."

The queue is not availablefor the requested operation.


The operation may besuccessful when the queuebecomes available.

14-166 "Job <jobidentification> is in aninvalid state(preprocessing) forthis operation.




14-167 "Job <jobidentification> is in aninvalid state(processing) for thisoperation.




14-168 "Job <jobidentification> is in aninvalid state (printing)for this operation.




14-169 "Job <jobidentification> is in aninvalid state(terminating) for thisoperation.




14-170 "Job <jobidentification> is in aninvalid state(interrupted) for thisoperation.




14-171 "Job <jobidentification> is in aninvalid state(retained) for thisoperation.




14-172 "Job <jobidentification> is in aninvalid state(canceled) for thisoperation.




14-173 "Job <jobidentification> is in aninvalid state(unknown) for thisoperation.




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-174 "Job <jobidentification> is in aninvalid state(completed) for thisoperation.




14-175 "The authenticationinformation is invalid."

The server encounteredinvalid authenticationinformation. This may bedue to an error in the clientapplication program or amemory corruption in theserver.



14-178 "The scope is invalid." The server encountered aninvalid scope for the list(pdq, pdls) operation. Thevalid values for scope arezero (0) and one (1).


Retry the operation using 0 or1.

14-179 "The objectidentification syntax isinvalid."

The object identification hasimproper syntax for aspecified object class. Thismay be due to an error inthe client applicationprogram or a memorycorruption in the server.



14-180 "The time limit isinvalid."

Time limit must be greaterthan 0 seconds.


Verify the time-limit value.

14-182 "Unable to obtainattributes for the initialvalue document."

The server could not obtaininitial value documentattributes that are neededto process this operation.This may be due to amemory corruption in theserver or a corruption in theobject database.



14-183 "Unable to obtain aread lock for the initialvalue document."

The server needs to obtaina read lock in order to readany information about theobject. However, an erroroccurred getting the lock.This may be due to amemory corruption in theserver.



14-184 "Unable to obtainattributes for the initialvalue job."

The server could not obtaininitial value job attributesthat are needed to processthis operation. This may bedue to a memory corruptionin the server or a corruptionin the object database.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-185 "Unable to obtain aread lock for the initialvalue job."

The server needs to obtaina read lock in order to readany information about theobject. However, an erroroccurred getting the lock.This may be due to amemory corruption in theserver or a corruption in theobject database.



14-187 "Unable to obtain thedefault values for thejob attributes."

The server could not obtainthe default values for jobattributes that are need toprocess this operation.This may be due to amemory corruption in theserver or a corruption in theobject database.



14-191 "Job priority value<value> exceedsprinter’s upper limit of<value>.”

The value of the job-priorityattribute must be less thanor equal to the max-user-job-priority attribute value ofthe requested printer.


Set the job-priority attribute toa value less than or equal tothe max-user-job-priorityattribute value for therequested printer.

14-192 "The attribute default-user-job-priority<attribute value>exceeds the attributemax-user-job-priority<attribute value>."

The default user job prioritymust be less than or equalto the max-user-job-priorityof the requested printer.


Set the default-user-job-priority to a value less than orequal to the max-user-job-priority value for therequested printer.

14-193 "Mandatory attribute<attribute name> wasomitted."

A mandatory attribute wasnot found.



14-194 "The AddDocumentrequest does notcontain a documentdescription."

The server received anAddDocument requestwithout a documentdescription. This may bedue to an error in the clientapplication program or amemory corruption in theserver.



14-195 "The printer ismissing the requiredattribute associated-queue."

The server failed to retrievethe required printerattribute, associated-queue.Either the object databaseis corrupted or an unknownerror occurred in theattribute set facility.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-196 "An individualdocument cannot bemodified with jobattributes."

Only the documentattributes can be applied toan individual document.Job attributes can be usedonly if ALL of thedocuments in the job are tobe modified.


Check the requestedattributes and the objectinstance.

14-197 "GetOrderedJobsoperation acceptsonly one printer."

The server received theGetOrderedJobs requestwith more than one printerspecified. This may be dueto an error in the clientapplication program or amemory corruption in theserver.



14-198 "No physical printersare supported for thespecified job/docattributes."

The server could not find aprinter that supports thespecified attribute andvalue.


Find a printer that supportsthe most similar attributevalue by entering “pdls -cprinter -r <correspondingprinter attribute> -s line<supervisor name>:” Thenresubmit the print job usingone of the supported values.

14-200 "Cancellation ofindividual documentsis not supported."

The user is attempting tocancel a document in a job.The user must cancel theentire job.


Cancel the entire job with thefollowing command line:pdrm [spooler name:] <job id>

14-201 "The job has nodocuments."

The server received a printrequest without a documentdescription. This may bedue to an error in the clientapplication program or amemory corruption in theserver.



14-202 "The job is missingthe required attributecurrent-job-state."

The server must check thecurrent-job-state attribute inorder to process therequest. This attribute wasnot found. Either the objectdatabase is corrupted or anunknown error has occurredin the attribute set facility.



14-203 "No more documentsubmissions areallowed on job <jobidentifier>."

The job has been closed;no more documentsubmissions are allowed.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-204 "No modificationattributes werespecified."

The server received aModifyJob request without alist of attributes to modify.This may be due to an errorin the client applicationprogram or a memorycorruption in the server.



14-205 "Modification ofindividual documentsis not supported."

The server does notsupport modification of anindividual document. Themodification must beapplied to the entire job.


Reissue the ModifyJobcommand with the proper jobidentifier.

14-206 "Multiple documentsare not supported bythis server."

This server does notsupport multiple documentsin a single print job.


Print one document at a timeby issuing a separate printcommand for each document.

14-207 "The user has nooperation rights."

The user does not havesufficient operation rightsfor this operation.


Check the access control listfor the privilege level of theuser.

14-208 "The printer name ismissing."

For the print operation, theserver received a printrequest without a printername. This may be due toan error in the clientapplication program or amemory corruption in theserver. For the setoperation, the server wasnot able to read the printer-name-requested attribute inorder to process the setoperation. This may be dueto a corruption in thedatabase or a memory errorin the server.



14-209 "This request cannotbe submitted to aphysical printer."

The requested operationcan only be submitted to alogical printer.


Reissue the command withthe proper logical printername.

14-210 "A null objectidentification waspassed in."

The server encountered anull object identification.This may be due to an errorin the client applicationprogram or a memorycorruption in the server.



14-211 "Printer <printername> alreadyexists."

An attempt was made tocreate a printer whichalready exists.


Create a printer using adifferent name.

14-212 "Queue <queuename> alreadyexists."

An attempt was made tocreate a queue whichalready exists.


Create a queue using adifferent name.

14-213 "Job <job identifier>already exists."

An attempt was made tocreate a job which alreadyexists.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-214 "Initial value job<initial value jobname> alreadyexists."

An attempt was made tocreate an initial value jobwhich already exists.


Create an initial value jobusing a different name.

14-215 "Document <jobidentifier.documentnumber> alreadyexists."

An attempt was made tocreate a document whichalready exists.



14-216 "Initial valuedocument <initialvalue documentname> alreadyexists."

An attempt was made tocreate an initial valuedocument which alreadyexists.


Create an initial valuedocument using a differentname.

14-217 "Server <servername> alreadyexists."

An attempt was made tocreate a server whichalready exists.







14-219 "An error hasoccurred using theobject identifierdatabase."

An error has occurred in theobject identifier database.


Restart the server. If theproblem persists, reinstall theobject identifier database.






The server could not readprinter attributes that arerequired to process therequest. This may be dueto a corruption in the objectdatabase or a memoryerror.



14-223 "Invalid operation;printer <printername> is disabled."

The user submitted orresubmitted a print requestto a disabled printer. Theprinter must be enabled inorder to accept any printjobs.


The user may submit orresubmit a print request to anavailable printer.

14-224 "An error hasoccurred retrieving aprinter-realizationattribute or value."

The server could not readthe printer-realizationattribute that is required toprocess this request. Thismay be due to a corruptionin the database or amemory error in the server.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-225 "Invalid operation;queue <queuename> is disabled."

The queue associated withthe requested printer iscurrently disabled. Thequeue must be enabled inorder to accept any printjobs.


Verify that the printer’sassociated queue is enabled.

14-226 "Invalid operation;<queue name> isenabled."

If performing a pdresubmitoperation, the queue shouldbe disabled prior toresubmission of multiplejobs. However, the queuemay remain enabled if jobsare resubmitted individually.If performing a pdcleanoperation, keep in mind thatan enabled queue cannotbe cleaned.


If performing a pdresubmitoperation, disable the queueand reissue the resubmitrequest (or submit jobsindividually). If performing apdclean operation, disable thequeue and reissue the cleanrequest.

14-227 " Invalid operation;server <servername> is disabled."

The user submitted a printrequest to a printer on adisabled server. The servermust be enabled before itcan accept new print jobs.


Verify that the printer’sassociated server is enabled.

14-228 "Invalid operation;<server name> isenabled."

When performing a pdcleanoperation, keep in mind thatan enabled server cannotbe cleaned.


Disable the server andreissue the clean request.

14-229 "The requestedserver is not licensedfor network use."

The server is unavailable;there is no valid license foraccess by a host on thenetwork.



14-230 "The Solaristhr_setconcurrency()call has failed."

An internal error hasoccurred.



14-231 "An unknown eventhas been specified."

The server encountered anunknown or unsupportedevent.



14-232 "Queue <queuename> was notfound."

The specified queue wasnot found.


Verify the queue name.

14-233 "Job <job identifiername> was notfound."

The specified job was notfound.


Verify the job identifier.

14-234 "Initial value job<initial value jobname> was notfound."

The specified initial valuejob was not found.


Verify the initial value jobname.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-235 "Document <jobidentifier.documentnumber> was notfound."

The specified documentwas not found.


Verify the job identifier anddocument number.

14-236 "Initial valuedocument <initialvalue documentname> was notfound."

The specified initial valuedocument was not found.


Verify the initial valuedocument name.

14-237 "Server <servername> was notfound."

The specified server wasnot found.


Verify the server name.

14-238 "Printer <printername> was notfound."

The specified printer wasnot found.


Verify the printer name.

14-239 "Object identifier<object identifiername> of unknownclass was not found."

The server encountered anunknown object identifier.This may be due to acorruption in the databaseor a memory error in theserver.


Verify the object identifiername.

14-240 "The job has not beenfound in thedatabase."

The server could not findthe specified job in thedatabase. The object mayhave been deleted.


Use the following commandline to check the status of thejob: pdls -c job <jobidentifier>.

14-241 "The printer has notbeen found in thedatabase."

The server could not findthe specified printer in thedatabase. The object mayhave been deleted.


Use the following commandline to check the status of thejob: pdls -c print <printername>.

14-242 "An unknown errorhas occurred in theSecurity facility."

An internal error occurred inthe security facility.



14-243 "The attribute<attribute name> withthe value <attributevalue> is notsupported by printer<printer name>."

The specified attributevalue is not supported bythe specified printer.


Check the supported valuesof the attribute of the specifiedprinter and then reissue thecommand with a validattribute value.

14-244 "Attribute <attributename> is notsupported by printer<printer name>."

The user specified a logicalprinter attribute in a requestto a physical printer, or theuser specified a physicalprinter attribute in a requestto a logical printer.


Verify that the attribute issupported by the logical orphysical printer.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-245 " Attribute <attributename> is notsupported by server<server name>."

The user specified aspooler attribute in arequest to the supervisor, orthe user specified asupervisor attribute in arequest to the spooler.


Verify that the attribute issupported by the spooler orsupervisor.

14-247 "The printer is notsupported by thisserver."

The server received a printrequest for a printer it doesnot support.


Use the following commandline to view the supportedprinters: pdls -c printer<spooler name>.

14-248 "The requestedtransfer method is notsupported by thisserver."

This server does notsupport the requestedtransfer method.


Check the transfer-method-supported attribute on theserver and reissue the printrequest using one for thesupported transfer methods.

14-249 "Job <job identifier>is invalid."

The server encountered aninvalid job for the listoperation.



14-250 "Initial value job<initial value jobidentifier> is invalid."

The server encountered aninvalid initial value job forthe list operation.


Verify the initial value jobidentifier.

14-251 "Document <jobidentifier.documentnumber> is invalid."

The server encountered aninvalid document for the listoperation.


Verify the job identifier anddocument number.

14-252 "Initial valuedocument <initialvalue documentname> is invalid."

The server encountered aninvalid initial valuedocument for the listoperation.


Verify the initial valuedocument name.

14-253 "Printer <printername> is invalid."

The server encountered aninvalid printer for the listoperation.


Verify the printer name.

14-254 "Queue <queuename> is invalid."

The server encountered aninvalid queue for the listoperation.


Verify the queue name.

14-255 "Server <servername> is invalid."

The server encountered aninvalid server name for thelist operation.



14-256 "None of the valuesfor <attribute name>are supported byprinter <printername>."

The specified values arenot supported by thespecified printer.


Use the pdls command toview the printer’s supportedattributes (pdls -c printer -r all-s line <printer name>).

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

14-257 "The attribute<attribute name> withthe value <value> isnot supported byserver <servername>."

The specified values arenot supported by thespecified server.


Use the pdls command toview the server’s supportedvalues for this attribute (pdls -c server -r <attribute name><server name>).

14-258 "The user hasinsufficient operationrights on the initialvalue document<initial valuedocument name>."

The user does not havesufficient operation rightson this initial valuedocument.


Check the access control listfor the privilege level of theuser (pdls -c i-v-d -r a-c-l<spooler name>:).

14-259 "The user hasinsufficient operationrights on the initialvalue job <initial valuejob name>."

The user does not havesufficient operation rightson this initial value job.


Check the access control listfor the privilege level of theuser (pdls -c i-v-j -r a-c-l<spooler name>:).

16-101 "The server is alreadydisabled."

The disable command hasalready been used on theserver.


N/A

16-102 "The server is alreadyenabled."

The enable command hasalready been used on theserver.


N/A





16-104 "Unable to obtainattributes on theserver."




16-105 "Unable to obtain thethread handle."




16-106 "Unable to lock thethread on the server."




16-107 "Unable to obtain aread lock on theserver."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

16-108 "Unable to set thestate on the server."

This error may be causedby a memory corruption inthe server, corruption in theobject database, a lack ofavailable disk space or alack of available virtualmemory.


Check the available diskspace in the database (orspool partitions) and theavailable virtual memorybefore retrying the operation.If the problem persists,contact technical support.

16-109 "Unable to setattributes on theserver."

This error may be causedby a memory corruption inthe server, corruption in theobject database, a lack ofavailable disk space, or alack of available virtualmemory.



16-110 "Unable to set thethread priority on theserver."




16-111 "Unable to signalthread condition onthe server."




16-112 "Unable to start anew thread on theserver."




16-113 "Unable to unlock theserver."




16-114 "Unable to unlock thethread on the server."




16-115 "Unable to obtain awrite lock on theserver."




16-116 "An error hasoccurred in thecommon server utilityfacility."




16-117 "A transaction errorhas occurred in thecommon server utilityfacility."




16-118 "An internal error hasoccurred in thedocument processor."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

16-119 "The function callfailed due to aninvalid attribute in thedocument processor."








16-121 "The documentprocessor is not in arunning state."








16-123 "An error hasoccurred in thedocument processor."




16-124 "The specifiedoperation is invalid."




16-125 "The requestedattribute modificationis invalid."








16-127 "The operation faileddue to an invalidargument."




16-128 "The operation faileddue to an internalfunction error."




16-129 "The operation faileddue to an invalidshutdown request."

An invalid shutdown requestcaused the operation to fail.



16-130 "The operation failedbecause the server isin an invalid state."

An invalid server statecaused the operation to fail.



16-131 "The requested eventis invalid for thecurrent state."




16-132 "The server cannotbe deleted while thereare jobs in thedatabase."

The requested deletecommand is invalid whilejobs are in the database.


After deleting the jobs in thedatabase, the server may bedeleted.

16-133 "The server must bedisabled prior to thisoperation."



Disable the server and retrythe operation.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION





16-135 "An error hasoccurred in the printagent."




16-136 "The server failed topause the printagent."




16-137 "The server failed toresume the printagent."




16-138 "The specified serverwas not found."

The server has not beencreated.


Create a server and retry theoperation.

16-139 "The supervisorserver does notsupport the requestedoperation."

The supervisor does notsupport the type ofoperation requested.


None





16-141 "There is no queue inthe server."

This error is caused by amissing queue during apdclean operation. Thereshould be at least onequeue on the server whenperforming this operation.


Set up a queue, submit jobson the queue and thenperform a pdclean operation.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

16-142 "The attribute<number-of-printers-supported> cannotexceed <maximum-number-of-printers-supported>."

This error is caused bysetting the number-of-printers-supported attributeto be greater than themaximum-number-of-printers-supported valueusing the pdset command.The maximum-number-of-printers-supported value is50 for the Referencesupervisor and 300 for theXerox supervisor.


Lower the value of thenumber-of-printers-supportedattribute and retry theoperation. If the problempersists, contact technicalsupport.

18-101 "Unable to obtain theprinters-assignedattribute from thejob."

This error may be causedby a memory corruption inthe server, a corruption inthe object database or by alack of available virtualmemory.



18-102 "Unable to convertthe distinguishedname stringsequence to simplename."

This error may be causedby a memory corruption inthe server or by a lack ofavailable virtual memory.











18-105 "The virtualsupervisor setfunction only modifiesjob or documentobjects."

The set function is not ableto modify other objects. The request

is notprocessed.


18-106 "The virtualsupervisor deletefunction only deletesjob or documentobjects."

The delete function is notable to delete other objects.



18-107 "The virtualsupervisor pausefunction only pausesjob or documentobjects."

The pause function is notable to pause other objects.



18-108 "The virtualsupervisor resumefunction only resumesjob or documentobjects."

The resume function is notable to resume otherobjects.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

18-109 "There is a missingargument, printername or server namein VS LOA."




18-110 "There is a missingargument, printername or server namein VS LOAContinuation."




18-111 "There is a missingargument, printername or server namein VS LOA Abort."




18-112 "There is a missingargument, printername or server namein VS LOA SendEvent."




18-113 "The supervisor is notresponding."

The supervisor may not berunning or may not befunctioning properly.


Check the state of thesupervisor. Restart thesupervisor (if necessary) andretry the operation. If theproblem persists, contacttechnical support.

18-114 "Unable to connect tothe supervisor;supervisor may havecrashed."

The connection to thesupervisor has failed.


Check the state of thesupervisor. Restart thesupervisor (if necessary) andretry the operation. If theproblem persists, contacttechnical support.

18-115 "An internal error hasoccurred in the objectdatabase facility."




18-116 "The supervisor hasnot processed therequest due to anauthorization error."

An authorization error hasoccurred.


Check the authorization onthe supervisor and retry theoperation. If the problempersists, contact technicalsupport.

20-101 "An unknown errorhas occurred in theattribute set facility."








TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

30-102 "An unknown erroroccurred duringprocessing of theuser request."




49-103 "PrintXchange lprinbound gatewayfailed to start. <lpdservice error> : <reason>."

This error is caused by aWindows NT system error.


Check to see if the WindowsNT installation is correct.

49-104 "Unable to open theregistry key."

This error occurs when theregistry key value is none.The default value of the keyis used.


Set the registry key(SOFTWARE\\Xerox\\PrintXchange\\CurrentVersion\\Gateway\\Common or lpribg) in themachine using theRegistryEditor.

49-105 "Unable to retrievethe registry value<registry value>."

This error occurs when theregistry key value is none.The default value of the keyis used.


Set the registry key(SOFTWARE\\Xerox\\PrintXchange\\CurrentVersion\\Gateway\\Common or lpribg) in themachine using theRegistryEditor.

49-106 "Unable to access<lock file name> forthe following reason:<reason>."

The lpr inbound gatewaywas not able to access thelock file. The lock file isusually on the%PrintXchange%\var\spool\PrintName.


Modify the security of the lockfile and the lpr inboundgateway spool directory.

49-107 "<spool directoryname>: Unable tocreate spool directory<spool directoryname> for thefollowing reason<reason>."

This error occurs when thelpr inbound gateway is notable to create a directoryspecified in the printcap file.


Modify the access rights inthe lpr inbound gateway spooldirectory or modify the spooldirectory in the printcap file.

49-209 "The CreateThreadfunction has failed."

This error occurs when thesystem resource is full.


Close any other applicationsthat may be running.

49-212 "The thread limit hasbeen reached."

The lpr inbound gateway isnot able to perform moreoperations than the threadlimit number.


Wait until the resourcebecomes available or changethe parameter of Maxthreadin the registry key(SOFTWARE\\Xerox\\PrintXchange\\CurrentVersion\\Gateway\\lpribg).


This error may be causedby a memory corruption.


Close any other applicationsthat may be running.

49-303 "An invalid request<operation> has beengenerated from<client host name>."

This error is caused by aninvalid command numbersent by the client. Theavailable numbers are from1 to 5.


Check to see which clientmachine sent the invalidrequest.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

49-304 "An invalid request<operation> has beengenerated."

This error is caused by aninvalid command number.The available numbers arefrom 1 to 5.


Check to see which machinesent the invalid request.

49-306 "The connection hasbeen lost."

This error occurs when athe client machine cancelsthe sending of print data orwhen the connection cableis disconnected.


If this error persists, checkthe connection cable.

49-307 "Unable to open theprintcap file for thefollowing reason:<reason>."

This error happens whenthe lpr inbound gateway isnot able to open theprintcap file.


Check the security of theprintcap file in the%PX_ROOT%\share\data\px_lpribg directory.

49-308 "<printer name> : Noprinter device isavailable."

This error signifies that theKP entry in the printcap fileis “none”.


Add the KP entry in theprintcap file.

49-309 "The requester'saddress is invalid."

The IP address of the clientis not formatted correctly.


Check the IP address of theclient machine.

49-310 "The host name forthe address<address> isunknown."

The lpr inbound gatewaycannot convert the IPaddress to a host name.The host name may not beregistered in the DNS orhost file.


Check the DNS entry and thehost file.

49-312 "The printer <printername> is unknown."

This error occurs when theclient specifies anonexistent printer entry.


Specify the correct printerentry.

49-313 "<printer name> :Unable to access<spool directory> forthe following reason:<reason>."

The lpr inbound gateway isunable to access the spooldirectory.


Check the security of thespool directory.

49-314 "Unable to rename<file name> for thefollowing reason:<reason>."

An error has occurred whilehandling the file.


None.

49-315 "<data file name> isan illegal pathnamefor the followingreason: <reason>."

The same file name alreadyexists.


Delete the file or cancel thejob corresponding to the file(or wait for the job to beprinted out).

49-316 "A write error hasoccurred writing to file<file name>."

An error occurred whilesaving the print data.


Resubmit the print command.

49-317 "A protocol error hasoccurred."

The requested operationhas caused an lpd protocolerror (RFC1179).


None.

49-318 "The spool directoryis full."

There is not enoughavailable disk space for therequested operation.


Check the available diskspace for the spool directory.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

49-401 "Unable to create cfand df names in<pathname>."

The creation operationcould not be performed dueto an incorrect path or lackof disk space.


Ensure that the disk space isadequate and the pathnameis correct.

49-402 "Unable to create thehandle to the mapperin <operation>."

This error is caused bymemory corruption.


Check to see if the lprinbound gateway wasinstalled correctly.

49-403 "Unable to set theattribute <operation>in <attribute name>."

This error is caused by amemory corruption.


Restart the lpr inboundgateway.

49-404 "Unable to create the<object name>operation."

This error is caused byinsufficient memory.



49-405 "Unable to destroythe <object name>operation."




49-406 "Unable to set thefilter during <objectname> operation."




49-407 "Unable to retrievethe result during<object name>operation."

This error occurs when theresource is insufficient.



49-408 "Unable to perform<operation> to<printer name> forthe following reason:<reason>."

This error is generatedwhen the lpr inboundgateway is unable toperform the requestedoperation.


Check the printer status forthe error reason specified.

49-409 "Unable to print <jobname> from <username> @ <hostname> to <printername> for thefollowing reason:<reason>."

This error is generatedwhen the lpr inboundgateway is unable toperform a print operation.


Check the printer statusregarding the error reasonspecified.




Close any other applicationsthat may be running on thesystem and restart the LANManager inbound gateway.

52-202 "Unable to create aservice thread."

A memory or resourcefailure may have occurred. The request

is notprocessed.

Restart the LAN Managerinbound gateway.

52-203 "Unable to create anamed-pipe for theservice function."

A memory or resourcefailure may have occurred.



52-204 "Unable to connect anamed-pipe for theservice function."




52-205 "Unable to read datavia a named-pipe."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

52-206 "Unable to write datavia a named-pipe."

A memory allocationcorruption may haveoccurred.



52-207 "The port <portname> alreadyexists."

The port has already beenassigned.


Try using another printer port.

52-208 "Unable to create aspool directory."

This error may be causedby a lack of available diskspace.


Delete some files that are nolonger needed and restart theLAN Manager inboundgateway.

52-209 "Unable to add port<port name>."

Either the port is alreadyassigned or it does notexist.


Ensure that the port exists.

52-210 "The specified port<port name> was notfound."

The requested printer portmay not exist.



52-211 "Unable to delete port<port name>."

The requested printer portmay not exist.



52-212 "Unable to list theport status for port<port name>."

The LAN Manager inboundgateway was unable tocommunicate with spooler.


Ensure that the spooler isrunning.

52-213 "Unable to create aprint thread function."




52-214 "Unable to retrieve anew pipe name forport <port name>."




52-215 "Unable to create anamed-pipe for theprint function. Pipename = <pipename>."




52-216 "Unable to connect anamed-pipe for theprint function. Portname = <portname>."




52-217 "The print job functionfailed. Port name =<port name>."

The gateway was unable tosubmit a job to the spooler.



52-218 "Unable to print job<job name> to thespooler for thefollowing reason:<reason>."

The gateway was unable tosubmit a job to the spooler.



52-219 "Unable to listPrintXchange printersfor the followingreason: <reason>."

The LAN Manager inboundgateway may have beenunable to communicate withspooler.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

52-220 "Unable to retrievethe PrintXchangeprinter status via port<port name> for thefollowing reason:<reason>."

The LAN Manager inboundgateway may have beenunable to communicate withspooler.



52-401 "Unable to open theprint data file."

The print data file could notbe opened.



52-402 "Unable to open theattribute file."

The attribute file could notbe opened.



52-403 "Unable to print a job.Port name = <portname>, job name =<job name>."

The print job could not becompleted.


Check the port name and jobname. Retry the operation. Ifthe problem persists, contacttechnical support.

52-404 "Unable to receivedata."

The data was not received. The requestis notprocessed.


52-405 "Unable to connect tothe PrintXchangeLAN Manager Printservice."

The server was not able toconnect to the print service.



52-406 "Unable to retrievejob information for job<job name>."

The job information couldnot be retrieved for thespecified job name.



52-407 "Unable to set jobinformation for job<job name>."

The job information couldnot be set for the specifiedjob.



52-408 "An unknown errorhas occurred."

Some type of unspecifiederror has occurred.



56-102 "PrintXchangeNetWare QServerprint service failed tostart up."

This error may be causedby a network or NetWareserver problem.

TheNetWareQServerprint servicedid not start.

Ensure that the configurationis correct and restart theQServer.

56-104 "Unable to start theprint service forqueue <queue name>on file server <servername>:<reason>."

This error may be causedby a system resourcefailure such asCreateThread() orResumeThread().


Check the system resourcefor the server and restart theQServer inbound gateway.

56-106 "The recoveryoperation has notcompleted; howeverthe QServer Gatewayhas continued to startup."

The recovery operation isincomplete.



56-107 "Unable to delete<number> temporaryfiles in spool directory<directory name>."



Restart the QServer inboundgateway.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

56-201 "Unable to allocatememory for the object<object name>."

There is not enoughmemory available in theserver.


Close any other applicationsthat may be running on thesystem and restart theQServer inbound gateway.

56-202 "Unable to resume aprint thread for queue<queue name> on fileserver <servername>."




56-203 "The pathname forobject <object name>exceeds thelimitation."

The pathname is too long. The requestis notprocessed.

Check the pathname, enter ashorter pathname and restartthe QServer inboundgateway.

56-204 "Unable to createdirectory <directoryname> due to<reason>."

This error may be causedby the use of invalid accessrights, an invalid path or alack of available disk space.



56-205 "Unable to delete file<file name> due to<reason>."

This error may be causedby another applicationreferencing the file or someother system error.

The requestis completedwith a dustfile.

Restart the QServer inboundgateway. The dust file will bedeleted when the QServerinbound gateway is restarted.

56-206 "A serious systemerror has occurred.The print service hasstopped for queue<queue name> on fileserver <servername>."

A system error hasoccurred in the thread.

None Ensure that the systemresource is adequate andrestart the QServer inboundgateway.

56-207 "Unable to allocatememory for the<object name>object."

There is not enoughmemory available in theserver.


Close any other applicationsthat may be running on thesystem and restart the QServer inbound gateway.

56-208 "Unable to create thethread <threadname>."

The thread could not becreated.



56-209 "There is not enoughdisk space to spoolthe data file for job<job name>."

The disk space required forthis operation is insufficient.


Check the available diskspace and retry the operation.If the problem persists,contact technical support.

56-210 "A file accessproblem hasoccurred. The job willbe processed later."

The file is not accessible. The requestis notprocessed.


56-301 "Unable to open theregistry key <registrykey name>."

This error is caused byinvalid configurationinformation in the registrysystem on the server.


Check the registry key,correct it as necessary, andrestart the QServer inboundgateway.

56-302 "Unable to query theregistry key <registrykey name>."

The key may not be set inthe registry.


Ensure that the registry key isset in the registry and restartthe QServer inboundgateway.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

56-303 "Unable to retrievethe value of theregistry key <registrykey name>."

The value may not be set inthe registry key.


Ensure that the registry key isset in the registry and restartthe QServer inboundgateway.

56-304 "The queues are notregistered correctly.Please check thequeue configuration."

There is no queue to beserviced by the QServerinbound gateway in itsconfiguration information.

TheQServerinboundgateway willstop.

Register the NetWare Queueinformation correctly andrestart the QServer inboundgateway.

56-305 "Retrieved the invalidvalue of registry key<registry key name>.The default value hasbeen used."

The wrong registry key wasentered.


Check the registry key valueand restart the QServerinbound gateway.

56-306 "A queue entry hasbeen ignored underregistry key <registrykey name> becauseof an invalid value<value>."

The wrong registry keyvalue was entered.



56-307 "Unable to retrievethe value of theregistry key <registrykey name>. Thedefault value hasbeen used."

The value may not be setproperly in the registry key.



56-308 "The registeredqueue number<number ofregistered queues>exceeds thesupported queuenumber <number ofsupported queues>."

The value may not be setproperly in the registry key.



56-401 "Unable to initialize asuitable WindowsSockets library."

This error may be causedby a memory corruptionwhen there is noWinsock32.dll on the path.


Check the Winsock32.dlllibrary file and restart theQServer inbound gateway.

56-402 "A systemconfiguration errorhas occurred."

The QServer inboundgateway uses the NWLinkIPX/SPX CompatibleTransport Driver tocommunicate with NetWareservers. The driver may notbe installed correctly.


Check the NWLink IPX/SPXCompatible Transport Driverand restart QServer inboundgateway.

56-404 "Unable to retrievethe NetWare FileServer address dueto a lack of response.The QServer inboundgateway will retrylater."

The network might be busyor the NetWare server maybe down.


Make sure the NetWareserver is running.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

56-405 "Unable to retrievethe NetWare FileServer addressesdue to a networkproblem. TheQServer inboundgateway will retrylater."




56-406 "Unable to retrievethe address forNetWare file server<server name>. TheQServer inboundgateway will retrylater."




56-407 "Unable to initializethe NCP (NetWareCore Protocol)Driver."

This error may be causedby a memory corruption inthe pdgwncp.dll module.


Check the system resourceand the pdgwncp.dll andrestart the QServer inboundgateway.

56-408 "Unable to login toNetWare file server<server name>. TheQServer inboundgateway hasterminated for queue<queue name>."

The NetWare server maynot be running or the targetqueue configuration mayhave been changed.


Ensure that the NetWareserver is running and restartthe QServer inboundgateway.

56-409 "Unable to login toNetWare File Server<server name> dueto a network problem.The QServer inboundgateway will retrylater."




56-410 "Unable to login toNetWare file server<server name>because the queueserver name <queueserver name> isinvalid."

The gateway QServername which is registeredunder the /Gateway/qsibg/registry key may beincorrect.


Ensure that the QServername is consistent with thetarget NetWare Queue Servername.

56-411 "Unable to start theservice for queue<queue name> on fileserver <servername> because thetarget queue name isinvalid."

The queue name isincorrect.


Check the queue name,correct it, and restart theQServer inbound gateway.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

56-412 "Unable to start theservice for queue<queue name> on fileserver <servername> because thetarget queue is notserviced by queueserver <queue servername>."

The target queue is notserviced by the queueserver in the NetWareserver.


Check the target queueconfiguration using aNetWare Administration Toolsuch as PCONSOLE andrestart the QServer inboundgateway.

56-413 "Unable to attach toqueue <queue name>on server <servername>. The QServergateway hasterminated for queue<queue name>."

An error has occurred in thenetwork or the system whileattaching the gateway to theNetWare queue.


Check the condition of thenetwork and the systemresource. Restart theQServer inbound gateway.

56-414 "Unable to attach toqueue <queue name>on server <servername> due to anetwork problem.The QServer inboundgateway will retrylater."

A network problem hasoccurred while attemptingto attach to the queue.



56-415 "Unable to query ajob for queue <queuename> on server<server name>. TheQServer inboundgateway will retrylater."

The job may not be locatedon the specified queue orserver.



56-416 "An error hasoccurred whileretrieving a job forqueue <queue name>on server <servername>."

A network problemoccurred while retrieving ajob from the queue.


Check the condition of thenetwork and the targetNetWare server. Restart theQServer inbound gateway.

56-417 "Unable to retrieve ajob from queue<queue name> onserver <servername>."

The job may not be locatedon the specified queue orserver.



56-418 “Unable to login toNetWare file server%1$s because thepassword of queueserver %2$s isinvalid.”

The message is displayed ifthe queue server object ofNetWare has a passwordand because the passwordmust be NULL.


NetWare Qserver inboundgateway requires theadministrator to delete thepassword for the NetWarequeue server and re-start thegateway.

56-501 "Unable to create theprint operation. Job<job name> has beenaborted."




TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

56-502 "Unable to setattribute <attributename>. Job <jobname> has beenaborted."




56-503 "The <operationname> operation hasfailed due to<reason>."

The job may no longer existor the spooler may not berunning.



56-504 "The LOA operationhas failed to retrievethe job status for job<job name>."

The job may no longer existor the PrintXchange spoolermay not be running.



56-505 "Unable to retrievethe job identifier onthe PrintXchangeserver."

The spooler may not berunning.



56-506 "Job <job name> wasaborted by thePrintXchange server."

This error may be due to ajob submission or job datafile problem.



56-507 "Unable to wait forthe job-completedevent for job <jobname> due to anEvent NotificationSystem error<error>."

Possible notificationproblem


Ensure that the notificationprocess is running.

56-509 "Job <job name> hasbeen paused by aPrintXchangeadministrator."

The job is currently in apaused state.


Contact the administrator.

58-101 Unable to initialize theWindows socket.

The Notification Server wasunable to use the WindowsSocket facility fornotification messages ofdelivery-method=socket.

The socketevent will beundelivered.

Check to see if the notificationserver is running.

58-102 Unable to determinethe system name:errno = <errornumber>.

The Notification Server wasunable to determine theserver’s system name.

Events willbeundelivered.Check tosee if thenotificationserver isrunning.

58-103 The system name istoo long.

The Notification Server hasdetermined that the systemname of the server exceedsa known limit.

Events willbeundelivered.


58-104 There is insufficientmemory on the serverto perform therequested operation.

The Notification Servercould not allocate enoughmemory to perform anotification-related function.


Check to see if the notificationserver is running and thesystem is functioningproperly.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

58-105 Unable to initialize theOID facility.

The Notification Servercould not initialize theObject Identifier facility.



58-106 Unable to initialize theI18N facility.

The Notification Servercould not initialize theInternationalization facility toconvert messages acrosslocales.



58-107 Unable to initialize thee-mail facility.

The Notification Servercould not initialize thesystem’s e-mail facility.



Check if Eudora mail facility isinstalled on the server. If so,enter Eudora. From the Toolscommand line option, selectthe MAPI option. In the MAPIoption screen, set “UseEudora MAPI server” to“never”.

58-108 Unable to initialize thesocket-event facility:errno = <errornumber>.

The Notification Servercould not initialize thesocket facility.



58-109 Unable to locate thedatabase directory<directory name>.

The Notification Servercould not find the databasedirectory used for storingevents.


Check to see if the notificationserver is running and thedatabase facilities arecorrectly installed.

58-110 Unable to locate thedatabase sourcedirectory <directoryname>.

The Notification Servercould not find the databasesource directory.



58-111 Unable to access thedatabase directories.

The Notification Servercould not find the databasedirectories.



58-112 Unable to create theobject database.

The Notification Servercould not create the eventdatabase used for storingnotification events.



58-113 Unable to open theobject database.

The Notification Servercould not open the eventdatabase.



58-114 Unable to initializename service: errno =<error number>.

The Notification Servercould not initialize with theNaming Service facility.



58-115 Unable to registerwith name service:errno = <errornumber>.

The Notification Servercould not register itself withthe Naming Service facility.



58-116 Unable to initialize theRPC.

The Notification Servercould not initialize a RemoteProcedure Call.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

58-117 Unable to register theRPC.

The Notification Servercould not register a RemoteProcedure Call.



58-118 Unable to start athread.

The Notification Servercould not launch a thread.



58-119 Unable to lock amutex object.

The Notification Servercould not get a MutualExclusion lock on an object.



58-120 Unable to initialize anevent object: errno =<error number>.

The Notification Servercould not initialize an eventobject.



58-121 The environmentvariable <variable> isnot set.

The Notification Serverfound that a necessaryenvironment variable wasnot set.



58-122 Unable to logon as<domain> <username> : errno =<error number>.

The Notification Servercould not log itself onto theExchange facility.



58-124 Unable to start aprocess: errno =<error number>.

The Notification Servercould not start a process.



58-126 The service hasshutdown improperly:status = <status>.

The Notification Serverencountered an error duringshutdown.

TheNotificationServer maynot haveshutdown ina propermanner.

Check to see if the notificationserver has shut downproperly.

59-101 “Unable to readaccountinginformation becausethe data appears tobe corrupted.”

Data in one of theaccounting logs cannot beread successfully.


If command was used on anumber of multiple logs (i.e.Command did not specifystart/end date), retrycommand specifying specificdates.

59-102 “There is insufficientmemory to performthe requestedoperation.”

There is no more memoryavailable on the server.



59-103 “A problem has beenencountered usingthe OID database.”

Data in the accounting logscannot be translated usingthe Object Identifierdatabase.


Verify that the ObjectIdentifier database isconsistent by looking in theObject Identifier databasepath. Retry the operation. Ifthe problem persists, contacttechnical support.

59-104 “Unable to read theaccounting file.”

The utility is unable to readthe data from theaccounting log.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

59-105 “Unable to processdata due to anunknown error.”




59-106 “The start date<date> is invalid. Thecorrect format isYYYYMMDD.”

An invalid start date hasbeen entered.


Enter the start date using thecorrect format and retry theoperation. If the problempersists, contact technicalsupport.

59-107 “The end date <date>is invalid. The correctformat isYYYYMMDD.”

An invalid end date hasbeen entered.


Enter the end date using thecorrect format and retry theoperation. If the problempersists, contact technicalsupport.

59-108 “The month <month>specified from thedate <date> isinvalid.”

An invalid month has beenentered.


Enter the month using thecorrect format and retry theoperation. If the problempersists, contact technicalsupport.

59-109 “The day <day>specified from thedate <date> isinvalid.”

The day entered isincorrect.


Enter the day using thecorrect format and retry theoperation. If the problempersists, contact technicalsupport.

59-111 “Unable to open thefile <file name> toappend moreaccountinginformation.”

The file specified by the -oswitch may be read only, orthe file could not be written.


If the file exists, ensure it haswrite permission or ensurethe directory that the file willbe written to has writepermissions. Retry theoperation. If the problempersists, contact technicalsupport.

59-112 “Unable to processthe environmentvariables duringinitialization or theserver name may beinvalid.”

This error occurs only in theNT environment. Theserver has previously beendeleted using the pddeletecommand or the enteredserver does not exist.


Verify the server name is validand retry the operation. If theproblem persists, contacttechnical support. If theserver was deleted, use theinstallation utility to install theserver and then retry theoperation.

59-113 “The server name isinvalid.”

The server name that wasentered is invalid.



59-114 “The pathnamespecified for theaccounting logs isinvalid.”

The pathname specified viathe -p switch is not a validpath.


Verify that the pathname iscorrect and retry theoperation. If the problempersists, contact technicalsupport.

59-115 “Unable to find theaccounting logs forserver <servername>.”

The utility could not findaccounting logs for thespecified server.


Verify that the accountingpath is correct and retry theoperation. If the problempersists, contact technicalsupport.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

59-116 “Unable to close theaccounting log for thedate <date>.”

During processing of theaccounting logs, the utilitywas unable to close the logfile for the specified date.



59-117 “Unable to delete theaccounting log for thedate <date>.”

The utility was unable todelete the log specified bythe date.



59-119 “The user is notauthorized to openthe log file for thedate <date>.”

The user running the utilityis not an administrator oroperator.



59-120 “Unable to open theaccounting log for thedate <date>.”

The accounting log is notaccessible for therequested date.



59-121 “There are noaccounting logsavailable.”

No logs were found for thespecified dates.


If there are supposed to beaccounting logs, verify theaccounting path. In addition,verify that the accounting logsfor the specified date exist.

60-102 "A requested attributewas not found."

A requested attribute wasnot found from the objectidentification database.


Retry the operation using thecorrect attribute name.

60-103 "A requested attributeis invalid for theobject class."

A requested attribute is notvalid for server object.


Retry the operation using thecorrect server attribute.

60-104 "A requested attributeis invalid for the setoperation."

A requested attribute is notvalid for set operation.


Retry the operation using thecorrect attribute.

60-105 "There is a requestedattribute which mustbe single-valued."

One of the requestedattributes should be single-valued. Only multiplevalues have been entered.


Retry the operation using asingle-value for the requestedattribute.

60-106 "A requested attributecontains an invalidvalue type."

One of the requestedattributes has an invalidvalue type.


Retry the operation using thecorrect value type.

60-107 "<executable>: TheRPC authenticationtype is unrecognizedor unsupported:<type>."

The specified authenticationtype is either unrecognizedor unsupported.


Retry the operation using thecorrect RPC authenticationtype.

60-108 "<executable>: Therequested option isinvalid: <flag>."

The specified flag is invalid. The requestis notprocessed.

Retry the operation using thecorrect flag.

60-109 "<executable>: Therequested server typeis invalid: <type>."

An incorrect server typevalue has been used.


Use either "SUP"(supervisor)or "SPL"(spooler) for theserver type value.

60-110 "<executable>: Thefollowing syntax is notsupported: <option> =."

The "=" sign is invalid forthis option.


Retry using a valid value forthis option (instead of "=").

60-111 "<executable>: Thedate/time attributevalue is invalid."

The mktime() system callhas failed.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

60-113 "<executable>:Unable to delete thedatabase:<database>."




60-114 "<executable>:Unable to determinethe current workingdirectory."

The getcwd() system callhas failed.



60-115 "<executable>:Unable to obtain thehost IP address."

The host address was notfound.



60-116 "<executable>:Unable to obtain alock for the databaselock file: <lock filename>."

The system call has failed. The requestis notprocessed.


60-117 "<executable>:Unable to open thedatabase lock file:<lock file name>."

This error may be causedby a memory corruption inthe server or a databasecorruption.



60-122 "<executable>: Thedatabase is corrupt:<database name>."




60-123 "<executable>:Unable to access thedatabase directory:<directory>."

An incorrect database pathmay have been used. Thiserror may be caused by amemory corruption in theserver or a corruption in theobject database.


Check the database path andretry using the correct value.If the problem persists,contact technical support.

60-124 "<executable>: Thedatabase alreadyexists: <databasename>."

The database alreadyexists.


N/A

60-125 "<executable>:Unable to locate thedatabase: <databasename>."

The database could not beopened since it could notfind the database.


Check the database path andretry using the correct value.If the problem persists,contact technical support.

60-127 "<executable>:Unable to locate thedata file for the I18Nlibrary."




60-128 "<executable>: Anerror has occurred inthe I18N library."




60-129 "<executable>: Thespecified attributesare invalid for theserver."

One of the specifiedattributes is not valid for thisoperation.


Retry the operation using thecorrect option and value.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

60-131 "<executable>: Theserver lock file hasalready been locked:<lock file name>."

The lock file has beenopened by other utilities ora server with the samename.


Check to see if the pdmakedbutilities and pdaccount arerunning. In addition, check tosee if a server with the samename is running.

60-132 "<executable>: Thereis insufficient diskspace to completethe requestedoperation."

A database could not becreated due to lack of diskspace.


Retry the operation afterenough space is available.

60-133 "<executable>: Thereis insufficient virtualmemory to completethe requestedoperation."



Reboot or contact technicalsupport.

60-134 "<executable>: TheOID database iscorrupt: <databasename>."




60-135 "<executable>:Unable to locate theOID database:<database name>."




60-138 "<executable>: Therequested pathnameis too long:<pathname>."

The pathname that hasbeen entered is too long.


Retry the operation using ashorter pathname.

60-139 "<executable>: The<option name> optionrequires anargument."

The specified optionrequires an argument.


Retry the operation using thecorrect option value.

60-144 "<executable>: Therequested servername is too long:<server name>."

The server name is toolong.


Retry the operation using ashorter server name.

60-145 "<executable>:Unable to access thesource databasedirectory:<directory>."

The source databasedirectory could not befound.


Retry the operation using thecorrect path for the database.

60-146 "<executable>:Unable to initializethreads."

A PrintXchange sub-moduleinitialization error hasoccurred.



60-148 "<executable>: Oneof the specifiedattributes was notfound."

An unrecognized attributehas been found.



60-159 "<executable>: Theentry for the -A optionis invalid."

Incorrect syntax was usedwhen entering a value forthe -A option.


Retry the operation using thecorrect syntax.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

60-160 "<executable>: Aperiod (.) is notallowed in the servername."

A period should not be usedwithin a server name.


Retry the operation withoutthe period in the server name.

60-161 "<executable>: Anerror has occurred inthe file access facility:<path>"




60-162 "<executable>: Anerror has occurred inthe attribute setfacility."




60-163 "<executable>: Anerror has occurredgenerating an AccessControl List."




60-164 "<executable>:Unable to open theOID database."

The Object Identifierdatabase could not beopened.


Retry the operation using thecorrect Object Identifierdatabase path.

60-165 "<executable>:Unable to find arequired attribute inthe OID database."




60-166 "<executable>: Anerror has occurred inthe database facility."




60-167 "<executable>:Unable to make acopy of thedatabase."




60-168 "<executable>: Aninitialization error hasoccurred in the OIDdatabase facility."

This error may be causedby an invalid OID pathspecified via the -O flag.


Check the command linesyntax and the environmentvariable PD_OID_DB_PATH.If the problem persists,contact technical support.

61-101 "<executable>: The<option name> optionrequires anargument."

The specified optionrequires an argument.


Check the command syntaxand restart the program.

61-102 "<executable>: Thedatabase iscorrupted!!!”

The Object Identifierdatabase is in aninconsistent state andcannot be accessed.

Theprogram isterminated.

Reinstall the database files(DPAOIDs.dbm,DPAOIDs_C.dbm,DPAOIDs_l.dbm,oid_cvrt.dbm).

61-103 "<executable>: Thedatabase iscorrupted!!! -- <errorcode>."

The object identifierdatabase is in aninconsistent state andcannot be accessed.


Reinstall the database files(DPAOIDs.dbm,DPAOIDs_C.dbm,DPAOIDs_l.dbm,oid_cvrt.dbm). If the problempersists, contact technicalsupport.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-104 "<executable>: Anerror has occurredwhile creating abackup file for<database filename>."

The utility program createsback up database filesbefore writing to them. Anerror has occurred whilemaking a back up copy ofthe specified file.


Remove the *.bak file and tryagain.

61-105 "<executable>: Anerror has occurredwhile creating anobject identifier for<object identifiername>.Continuing..."

The utility programencountered an unknowninternal error while trying tocreate an object identifierfor the givenattribute/attribute-value/value-class.

The currententry isignored andthe utilitycontinues tothe nextentry in theinput file.

Reinstall the database filesand restart the program.

61-106 "<executable>:Unable to obtain adatabase lock at<database file path>."

The program was unable toaccess the database lock.Another program may beaccessing the database orthe lock file. ".pd.lck" maybe missing in the indicateddirectory.


Terminate all PrintXchangeservers that share this objectidentifier database. Check tosee if ".pd.lck" exists in theindicated database directoryand restart the program. Ifthe problem persists, contacttechnical support.

61-118 "The attribute name isunknown."

The specified attribute isunknown to the system.

Displays theerrormessageandcontinues tothe nextattribute.

Correct the attribute nameand restart the program.

61-120 "<value> error(s)has/have occurred."

This error messageprovides the number oferrors that have occurredwhile modifying the objectidentifier database.

N/A N/A

61-124 "<executable>: Errorin line <line number>.The name <objectidentifier name>already exists in thedatabase. Entryignored."

The line indicated specifiesan attribute that alreadyexists. A duplicate name isnot allowed.


Correct the name field of theindicated line and rerun theprogram.

61-124 "<executable>: Error<line number> : OID<decimalOID>already exists inthe database. Entryignored."

The line indicated specifiesan attribute that alreadyexists. A duplicate objectidentifier name is notallowed.


Correct the name field of theindicated line and restart theprogram.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-125 "<executable>: Errorin line <line number>.The decimal objectidentifier <decimalobjectidentifier>alreadyexists in thedatabase. Entryignored."

The line indicated specifiesan object identifier thatalready exists. A duplicatedecimal object identifier isnot allowed.

The currententry isignored andthe utilitycontinues tothe nextentry in theinput file..

Correct the object identifier ofthe indicated line and restartthe program.

61-126 "<executable>: Errorin line <line number>.The length of field<field number>exceeds thecharacter limit. Itmust be less than orequal to <maximumfield length>."

The indicated field in theline exceeds the maximumlength as shown.


Correct the indicated field inthe specified line and restartthe program.

61-127 "<executable>: Errorin line <line number>:<data> is not a validread/write mode."

The indicated line specifiesan invalid read/write mode.


Correct the read/write modeof the indicated line andrestart the program.

61-128 "<executable>: Errorin line <line number>.The syntax <syntaxname> is notsupported. Entryignored."

The indicated line specifiesan unsupported syntax.


Correct the syntax of theindicated line and restart theprogram.

61-129 "<executable>: Errorin line <line number>.There is/are <numberof arguments>argument(s)specified; <requirednumber ofarguments>argument(s)was/were expected.Entry ignored."

The indicated line ismissing one or morearguments.


Correct the indicated line andrestart the program.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-130 "<executable>: Errorin line <line number>.There are <number ofarguments> or morearguments specified;<required number ofarguments>argument(s)was/were expected.Entry ignored."

The indicated line containsmore arguments thanexpected.


Correct the indicated line andrestart the program.

61-131 "<executable>: Thespecified path<database path> isnot a valid objectidentifier databasepath."

The specified path is not avalid object identifierdatabase path.


Restart the programspecifying a valid objectidentifier database path.

61-132 "<executable>: Errorin line <line number>:<data> is not a validmulti/single mode.Entry ignored."

Whether the attribute issingle-valued or multi-valued, it is incorrectlyspecified in the indicatedline.


Correct the multi/single valuefield of the indicated line andrestart the program.

61-133 "<executable>: Errorin line <line number>.The name <name>contains invalidcharacters."

The name in the indicatedline contains characters thatare invalid for the namefield.


Correct the name field in theindicated line.

61-134 "<executable>: Errorin line <line number>:<data> is not a validobject identifier type "

The indicated line specifiesan invalid object identifiertype.


Correct the object identifiertype in the indicated line andrestart the program.

61-135 "<executable>: Errorin line <line number>.The optionalargument <optionalargument> is invalid."

The indicated line specifiesan invalid optionalargument.


Correct the optional argumentin the indicated line andrestart the program.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-136 "<executable>: Errorin line <line number>.The line lengthexceeds the limit of<maximum number ofcharacters>characters. Entryignored."

The indicated line exceedsthe maximum characterlimit.


Edit the indicated line andrestart the program.

61-137 "<executable>: The<environmentvariable name> is notset."

The required environment isnot set up.


Set the specified environmentvariable.

61-138 "<executable>: Errorin line <line number>.The name lengthexceeds the limit. Itmust be less than orequal to <maximumname length>. Entryignored."

The indicated line specifiesa name that exceeds themaximum character limit.


Shorten the name and restartthe program.

61-139 "<executable>: Anerror has occurredwhile opening theobject identifierdatabase."

An unspecified erroroccurred while opening thedatabase.


Check to see if the objectidentifier database exists.

61-140 "<executable>: Anerror has occurredwhile opening the file<file name>."

An error has occurred whileopening the indicated file.The file may not exist or theuser may not have readaccess to the file.


Check to see if the file existsand ensure that the user hasread access to the file.

61-141 "<executable>: Anerror has occurredwhile opening theobject identifierdatabase file.<error>:<databasefile name>."

An error occurred openingthe indicated database file.


Check to see if the file exists.

61-142 "<executable>: Out ofspace for dynamicobject identifiers.Only <number> moreobject identifier(s)may be added sincethe last addition."

There is no more room toadd dynamic objectidentifiers. The maximumallowed is 2M.


It is very unlikely that theorganization has added 2Mdynamic object identifiers.Restore the database files bycopying *.dbm.bak to *.dbm.

61-143 "<executable>: Out ofspace for dynamicvalue classes. Only<number> morevalue classes may beadded since the lastaddition."

There is no more room toadd dynamic value classes.The maximum allowed is30K.


It is very unlikely that theorganization has added 30Kdynamic value classes.Restore the database files bycopying *.dbm.bak to *.dbm.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-144 "<executable>: Thesystem is out ofmemory."

The system is out ofmemory.


Restore the database files bycopying *.dbm.bak to *.dbm.Reboot the system andrestart the program.

61-146 "<executable>: Therequired argumentshave not beenspecified."

The user did not specify therequired command lineargument.


Check the command syntaxand restart the program.

61-147 "<executable>: A fatalerror has occurred:The program wasunable to restore thedatabase files."

After encountering an error,the program tried to restorethe database files but wasunable to do so.


Restore the database filesmanually by copying*.dbm.bak to *.dbm.

61-148 "<executable>: Anunknown error hasoccurred. Error code= <error code>"

An unknown internal errorhas occurred.


Restore the database files bycopying *.dbm.bak to *.dbmand restart the program. Ifthe problem persists, contacttechnical support.

61-149 "<executable>: Anunknown error hasoccurred."

An unknown internal errorhas occurred.



61-150 "<executable>: Anunknown error hasoccurred in the FAfacility."

An unknown internal errorhas occurred in the FAfacility.



61-151 "<executable>: Anunknown error hasoccurred in thePDBM facility. Errorcode = <number> --<detailed message>."

An unknown internal erroroccurred in the PDBMfacility.



61-152 "<executable>: Anunknown error hasoccurred in the THRfacility."

An unknown internal erroroccurred in the THR facility.



61-153 "<executable>: Errorin line <line number>.The value class<name> is unknown.Entry ignored."

The specified value class isunknown to the system.The value class must beassigned before it isreferenced.


Correct the value class ordefine the value class prior tothe indicated line. Thenrestart the program.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

61-156 "<executable>: Errorin line<line number> :<data> contains anunsupported objectclass. Entry ignored."

The indicated line specifiesan unsupported objectclass.


Correct the object class list ofthe indicated line and restartthe program.

62-101 "Invalid execution ofpddiagjob."

The pddiagjob utility wasexecuted using the shell dotcommand (". pddiagjob[arguments]"). This is aninvalid way of executing thisutility.


Retry the command using justthe utility name ("pddiagjob[arguments]").

62-102 "Unable to accessbinary <binaryname>."

A required binary ismissing.


Make sure the specifiedbinary is installed on thesystem.

62-103 "No server has beenspecified."

No server name wasspecified in the commandline and PDPRINTERenvironment variable is notset.


Retry the command andspecify the server name inaddition to the job ID or setthe PDPRINTER environmentvariable.

62-104 "Unable to accessserver <servername>."

The pddiagjob utility couldnot communicate to thespecified server.


Make sure the specifiedserver is running (do "pdls -cserver <server name>") andretry the command.

62-105 "Unable to accessprinter <printername>."

The pddiagjob utility couldnot communicate to thespecified printer.


Make sure the specifiedprinter is available (do "pdls -cprinter <printer name>") andretry the command. IfPDPRINTER environmentvariable is used make sure itcontains a valid printer name.

62-106 "Unable to accessqueue <queuename>."

The pddiagjob utility couldnot communicate to thespecified queue.


Make sure the specifiedqueue is available (do "pdls -cqueue <queue name>") andretry the command.

62-107 "Unable to access job<job identifier>."

The pddiagjob utility couldnot access the specifiedjob.


Make sure the specified job isavailable (do "pdls <servername>:<job identifier>") andretry the command.

62-108 "Unable to accessdocument <jobidentifier . documentname>."

The pddiagjob utility couldnot access the specifieddocument.


Make sure the specifieddocument is available (do"pdls -c document <servername>:<jobidentifier.document number>")and retry the command.

62-109 "Invalid job identifier<job identifiername>."

An invalid job identifier wasspecified.


Retry the command using avalid job ID.

62-110 "Job <job identifier>not found in spooler<server name>."

The specified job identifierdoes not exist in thespooler.


Make sure the spooler nameand job identifier are valid andretry the command.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

62-111 "Unable to retrievecurrent job state forjob <job identifier>;user may not haveaccess."

The pddiagjob utility couldnot retrieve the job state forthe specified job. This couldhappen if user is not the jobowner.


Make sure the job identifier isvalid. If user is not the jobowner and also not anadministrator then jobattributes that are visible arethe ones defined in the "job-attributes-visible-to-all"attribute of the spooler.

62-112 "Unable to retrieveassigned queue forjob <job identifier>;user may not haveaccess."

The pddiagjob utility couldnot retrieve the assignedqueue for the specified job.This could happen if user isnot the job owner.


Make sure the job identifier isvalid. If user is not the jobowner and also not anadministrator then jobattributes that are visible arethe ones defined in the "job-attributes-visible-to-all"attribute of the spooler.

62-113 "Unable to retrieveserver state forspooler <servername>; user may nothave access."

The pddiagjob utility couldnot retrieve the server statefor the specified spooler.


Make sure the specifiedspooler is running. Also makesure the user is included inthe "access-control-list"attribute of the spooler.

62-114 "Unable to retrievequeue state for queue<queue name>; usermay not haveaccess."

The pddiagjob utility couldnot retrieve the queue statefor the specified queue.


Make sure the specifiedqueue is available. Also makesure the user is included inthe "access-control-list"attribute of the queue.

62-115 "Unable to retrievephysical printer statefor printer <printername>; user may nothave access."

The pddiagjob utility couldnot retrieve the printer statefor the specified printer.


Make sure the specifiedprinter is available. Also makesure the user is included inthe "access-control-list"attribute of the printer.

62-116 "The requestedoption is invalid:<flag>."

An invalid flag was specifiedfor pddiagjob utility.


Use “pddiagjob -h” for thecorrect syntax and retry.

63-101 "The requestedattributes are invalid."

The option flag specified isnot defined for therequested operation.


Consult the manual or invokethe command with the –h flagto review valid flags.

63-103 "The flag <flag> isinvalid."

When using the –r flag orthe ‘requested-attributes’attribute and the value usedis either brief, verbose,none, or all, multiple valuesare not permitted. If thecommand is not pdls orpdq, then using a list ofspecific attributes is notpermitted. The values brief,verbose, none, or all cannotbe mixed with specificattributes. An attributeassignment is also notpermitted (e.g. –r printer-name=joe).


Correct the –r or therequested-attribute value.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

63-104 "An internal error hasoccurred."

This is caused by asoftware problem such ascaused by unexpectedfailures of system functions.



63-105 "The assignmentoperator is missing."

When using the –x flag, theoption argument shouldhave the form <attribute-name>[+|-|=]=[<value>].This error will occur if somepart of the assignmentoperator ([+|-|=]=) ismissing.


Correct the assignmentoperator.

63-106 "The value qualifier isinvalid."

A value qualifier ([+|-|=])was used to set the ‘filter’,‘requested-attributes’, or‘attributes’ attribute.


Do not use value qualifiers forthese attributes.

63-107 "The default does notallow valueassignment."

When using the –x flag, avalue was specified after anassignment specifyingdefault (= operator).Default assignments do nottake values.


Correct the assignmentexpression.

63-108 "An assignment hasbeen made withoutan attribute."

When using the –x flag, noattribute was found after acompulsory qualifier (- or =).



63-109 "An assignment hasbeen made without avalue."

A value was not found afteran attribute assignment orfilter relational operator.



63-110 "The filter assignmentis incomplete."

A filter expression ismissing a value or operator.


Correct the filter expression.

63-111 "The NOT operator ismissing aparenthesis."

A NOT operator (!) in a filterexpression should befollowed by an expressionwithin the parenthesis.



63-112 "There is insufficientmemory on the clientto perform therequested operation."



Close all unused applications.

63-113 "The string isincomplete."

An assignment or filterexpression endedunexpectedly.


Correct the assignment orfilter expression.

63-114 "There is an error inthe filter syntax."

Relational and logicaloperators are not allowed infilter expressions.


Correct the relational orlogical operators in the filterexpression.

63-115 "A parenthesis orbracket is missing."

A closing parenthesis orbracket is missing.


Add the missing parenthesisor bracket.

63-116 "The NOT expressionis incomplete."

There is no filter expressionwithin the parenthesiscorresponding to a NOToperator.


Correct the NOT expression.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

63-117 "The left hand side ofthe expression ismissing."

There are no characters leftof one of the logicaloperators (|| or &&).



63-118 "The requestedoperation requires aninstance."

An object instance isrequired for this operation;none were found.


Add an instance to thecommand.

63-119 "The requestedoperation isunknown."

The name of the executabledoes not match the knownPOSIX operation names.


Rename the executable usingthe correct name.

63-120 "The file was notfound."

The attribute file was notfound in the directory orpath environment specified.


Correct the attribute filenameor path environment(PDPATH).

63-121 "A qualifier for anattribute assignmentis not valid."

There are two possiblecauses: either 1) acompulsory qualifier wasused with commands otherthan pdset or pdmod, or 2)a value qualifier was usedwith commands other thanpdset, pdmod, pdpr, orpdcreate.


Remove the qualifiers or useanother valid command.

63-123 "The requestedoperation does notallow multiple jobs."

The promote operation mayonly be used to promote asingle job.


Retry the operation using asingle job identifier.

65-101 "A Win32 error hasoccurred: <errornumber><location>."

An unexpected Win32 APIfailure has occurred.

If the Profileand GroupRegistry wasprocessingrequests,The requestis notprocessed.If it wasinitializing,the Profileand GroupRegistrystops.


65-102 " A WinSock errorhas occurred: <errornumber><location>."

An unexpected WinSockfailure has occurred.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

65-103 "A C Runtime errorhas occurred: <errornumber><location>."

An unexpected C Runtimeerror has occurred.


Restart the Profile and GroupRegistry. If the problempersists, contact technicalsupport.

65-104 "An internal error hasoccurred:<location><read lockstate><write lockstate>."

A Profile and GroupRegistry error has occurred.The internal state of theapplication is inconsistent.


Restart the Profile and GroupRegistry. If the problempersists, contact technicalsupport.

65-105 "An object <objectname> has beenduplicated for class<object class>. Thelatter one is ignored."

The Profile and GroupRegistry already containsan object with the samename. This may occurwhen the user edits theProfile and Group Registrydata file.

The Profileand GroupRegistryignores theduplicateobjectdefinition.

Remove the duplicatedobject.

65-106 "Unable to delete theobject name <objectname> for class<object class>."

The Profile and GroupRegistry is not able todelete the specified objectfrom its on memory cache.

Thespecifiedobject will bedeletedduring thenext restart.

Restart the Profile and GroupRegistry.

65-107 "Unable to overwritethe object name<object name> forclass <object class>."

The Profile and GroupRegistry is not able torestore the specified object.

Thespecifiedobject will berestoredduring thenext restart.

Restart the Profile and GroupRegistry.

65-108 "Unable to resolvethe host name: <hostname>."

The Profile and GroupRegistry is not able toretrieve the IP address ofthe host.


Check the host name and themachine TCP/IP setting.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

65-109 "The pdc preload fileis invalid: <errorstring>."

The Profile and GroupRegistry host file containsan error in one of the lines.

The Profileand GroupRegistryignores theline thatcontains theerror.

Correct the line in the Profileand Group Registry host file.

65-110 "In domainconfiguration, theProfile and GroupRegistry only runs onthe Primary DomainController."

The machine being used isnot the Primary DomainController for the domain.

The Profileand GroupRegistrystops.

Remove the Profile andGroup Registry from thismachine and install it on thePrimary Domain Controller forthe domain.

65-111 "The Profile andGroup Registry isalready running in thisworkgroup on<machine name>."

The Profile and GroupRegistry is already runningin this workgroup. Only onePrintXchange NameService can operate in aworkgroup at a time.

The Profileand GroupRegistrystops.

Ensure that only one Profileand Group Registry is runningin the workgroup.

65-112 "This machine doesnot support theprotocol sequence<protocol sequencename>."

The specified protocolsequence is not supported.

The Profileand GroupRegistryignores theprotocolsequence.

Remove the protocolsequence from the registrykey. If the protocol sequenceis “ncach-ip-tcp”, installTCP/IP on the machine.

65-113 "The specifiedprotocol sequencename <protocolsequence name> isinvalid."

The specified protocolsequence is invalid.

The Profileand GroupRegistryignores theprotocolsequence.

Remove the protocolsequence from the registrykey.


An internal error hasoccurred in the clientsoftware.



80-102 "Incorrect versions ofthe OLE systemDynamic LinkLibraries have beeninstalled."

The client tool was unableto initialize due to theversion mismatch betweenthe OLE system DynamicLink Library. This is causedby an incorrectconfiguration of theoperating system.


Reinstall the operatingsystem.

80-103 "Microsoft InternetExplorer 3.01 (or laterversion) has not beeninstalled."

The client tool was unableto initialize due to theversion mismatch ofdependent Dynamic LinkLibraries. Microsoft InternetExplorer 3.01 or latershould be installed.


Install Microsoft InternetExplorer 3.01 (or laterversion).

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

80-104 "The client wasunable to performsystem initialization."

The client tool was unableto initialize due to anincorrect configuration ofthe client software. Somerequired files are missing.


Reinstall the client software.

80-105 "The help file registrykey was not found."

The help file cannot bedisplayed because someregistry entries are missing.



80-106 "The help file was notfound."

The help file cannot bedisplayed because acorresponding help file ismissing.



80-107 "Unable to invoke theexternal tool<external toolname>."

Unable to invoke thespecified tool.


Reinstall the client softwarewith the specified softwareoption.

80-108 "The <object name>is already <state>."

The specified object isalready in the requestedstate.


N/A

80-109 "The <object name>is not <state>."

The specified object is notin the state required for therequested operation.


Ensure that the object state isappropriate for the operation.

80-110 "The <object name>is not disabled. Itmust be disabled tobe <status>."

The requested operationrequires the object to be ina disabled state.


Disable the object and retrythe operation.

80-111 "The default settingsdialog cannot beopened because the<initial-value-job orinitial-value-document> does notexist."

Unable to open the defaultsettings dialog because thecorresponding initial-value-job or initial-value-document does not exist.


Select the refresh button andretry the operation.

80-112 "The printerconnection methodsare invalid."

The connection methodwas not specified whilecreating the physical printer.


Specify the connectionmethod and retry theoperation.

80-113 "No attribute valueswere selected."

No attribute values werespecified while modifyingthe supported attributes of aprinter.


Specify the attribute valuesand retry the operation.

80-114 "The specified valueis invalid."

An invalid numeric valuewas specified whenmodifying the supportedattributes of a printer.


Specify a valid numeric valueand retry the operation.

80-115 "The specified valuesare out of range."

The specified values areoutside of the acceptablerange.


Check the range of the valuesand retry the operation.

80-116 "Please enter a timebetween <start time>and <end time>."

The specified time isoutside of the acceptabletime range.


Check the range of thespecified time and retry theoperation.

80-117 "The past time cannotbe specified."

The past time is not allowedfor the specified attribute.


Check the specified time andretry the operation.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

80-118 "This value alreadyexists in thesupported list."

Duplicate attributes cannotbe added to the supportedattribute list.


N/A

80-119 "The delivery addresswas not specified."

A delivery address was notspecified while adding anevent.


Specify the delivery address.

80-120 "The user name wasnot specified."

The user name was notspecified while addingaccess rights.


Specify the user name.

80-121 "The domain namewas not specified."

The domain name was notspecified while addingaccess rights.


Specify the domain name.

80-122 "The supervisor wasnot found in thisdomain."

There must be a supervisorin the domain in order toconnect a physical printer toa queue.


Create a supervisor in thedomain and retry theoperation.

80-123 "No duplicates areallowed in the accesscontrol list."

An attempt was made toadd a duplicate entry to theaccess rights.


N/A

80-124 "The queue cannotbe deleted until allassociated logicalprinters have beendeleted."

An attempt was made todelete a queue that hadassociated logical printers.


Delete all associated logicalprinters and retry theoperation.

80-125 "The printer portformat is invalid. Thegeneral form is<printer portformat>."

The specified printer portdoes not have a validformat.


Check the format of theprinter port.

80-126 "The printer addressformat is invalid. Thegeneral form is<printer addressformat>."

The specified printeraddress does not have avalid format.


Check the format of theprinter address.

80-127 "The specified PAFfile does not apply forthe supervisor'<supervisor name>'(type = <supervisortype>). Please selecta different PAF file."

The type of PAF fileselected does not matchthe supervisor type.


Select a PAF file type thatmatches the supervisor type.

80-128 "The PAF file '<filepath>' does notexist."

The specified PAF file doesnot exist.


Ensure that the correct filepath name is specified for thePAF file.

80-129 "The supervisor type'<supervisor type>' isnot supported."

An attempt was made toaccess a physical printerassociated with anunknown supervisor type.


Check to see if thesupervisor-type attribute hasthe correct value.

81-101 "The PrintXchangename service data fileis corrupted."

The name server cannotrecover the name data fromthe recovery file.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

81-102 "Internal error:Unable to initialize thename service client."

The name serviceinfrastructure has beeninitialized in client mode, butthe requested operationrequires server modeinitialization.



81-103 "Unable to performthe requestedoperation due toinvalid parameters onthe name service."

Unable to perform therequested operation due toinvalid parameters on thename service.



81-104 "The specifieddomain or workgroupdoes not support thename service."

The specified domain orworkgroup may not exist, orthe PrintXchange nameservice may not be runningon the specified domain orworkgroup.


Ensure that the specifieddomain or workgroup existsand that the PrintXchangename service is running.

81-106 "Internal error: Aname service callwas issued prior toinitialization."

The software has issued acall to the name servicebefore initializing it.



81-107 "The name service isunable to allocatememory for therequested operation."

There is insufficient virtualmemory to perform theoperation.


Close other memory-consuming applications andretry the operation (or rebootthe client machine). Ifproblem persists, reboot thename server machine.

81-108 "The specified objectwas not found on thename service."

This error may occur whenattempting to access aprinter in a domain that isno longer configured. Thiserror will also occur if thePrintXchange NameService has been moved orthe host it resides on isdown.


Check to see if the desiredobject exists on the nameservice by enumerating theobjects.

81-110 "The associatedobject was not foundon the name service."

The server objectreferenced by the printer orqueue object does not existin the name space.



81-111 "The name service isunavailable."

The name service is notrunning on the domain orworkgroup.


If this message was receivedwhile referencing a foreigndomain or workgroup, ensurethat the name service isrunning on that domain orworkgroup. Otherwise,ensure that the systemregistry entry for the nameservice points correctly to thename server address.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

81-112 "Unable to performthe requestedoperation for thename service."

An internal error hasoccurred within the nameservice.


Restart the client software orthe name service. If theproblem persists, contacttechnical support.

81-113 "The requestedoperation is notsupported on thename service."

An unsupported operationwas submitted against thename service.



8019-101 "The operation faileddue to invalidparameters in<attributename>:<value>."

This error occurs whenthere is an invalidparameter passed into afunction but may also bedue to an error in the valueof an attribute (or flag)specified by the user.


Look for errors in values ofattributes or flags and correctthem.

8019-102 "There is insufficientmemory on the clientto perform therequested operation."

An allocation function wascalled and failed.


Close any other applicationsthat may be running and retrythe command.

8019-103 "The requestedfunction for theoperation is invalid."

An error may have occurredin the client program.Either DPAPushDocumentor OpenDocument wascalled with an operationother than PRINT orDPAOpenFilter was calledwith an operation other thanLIST_OBJECT_ATTRIBUTES or PDQ.


Check operation code in theDPAOpenRequest.

8019-104 "The attribute<attribute name> isunknown."

The attribute was not foundin the Object Identifierdatabase.


Check thePD_OID_DB_PATHenvironment variable ordefault Object Identifierdatabase directory. Inaddition, check the spelling ofthe attribute.

8019-108 "The attribute<attribute name>contains a non-unique valueabbreviation:<abbreviation>."

The abbreviated valuespecified is ambiguous andcannot be used to match asingle Object Identifiername.


Choose an abbreviation thatmore accurately matches thedesired value and will notmatch others in the list.

8019-110 "The locale <locale>is unknown."

This error will occur if therewas either no locale foundin the environment or if theObject Identifier databasewas not found for the localespecified by theenvironment.


Ensure that the locale is setcorrectly and that the ObjectIdentifier database exists forthat locale.

8019-111 "The requestedoperation isunknown."

DPAOpenRequest calledwith an incorrect operationcode.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-112 "There is no currentdocument controlblock."

DPAOpenDocument calledwith init_codeDPA_INIT_FROM_CURRENT_DCB but no currentdocument exists.



8019-113 "There is no highestdocument controlblock."

DPAOpenDocument calledwith init_codeDPA_INIT_FROM_HIGHEST_DCB but no currentdocument exists.



8019-114 "The initializationcode is unknown."

DPAOpenDocument calledwith an init_code that is notdefined.



8019-116 "The attribute<attribute name> isinvalid for the objectclass <object class>."

The user attempted to setan attribute that does notcorrespond to the objectclass selected.


Correct the object class (-cflag) or the attribute.

8019-117 "The attribute<attribute name> isinvalid for therequested operation."

The attribute does notcorrespond to this operationin the Object Identifierdatabase.


Check the attribute and theoperation.

8019-118 "The attributeabbreviation<abbreviation> is notunique."

The attribute abbreviation isambiguous and cannot beused to match a singleattribute name.


Choose an abbreviation thatmore accurately matches thedesired attribute and will notmatch others in the list.

8019-119 "The attribute<attribute name>does not allow themultiple values<values>."

The user attempted to setmore than one value for thisattribute.


Check the attribute and thevalue.

8019-120 "The requestedattribute <attributename> is invalid forthe class <objectclass>."

A value in the ‘requested-attributes’ attribute or –r flagdoes not correspond to theclass specified


Check the class and theattribute.

8019-121 "The attribute has notbeen set."

DPAAppendValue wascalled without first callingDPASetAttributeType.



8019-122 "The attribute<attribute name> hasa value <value>which is unknown."

The user attempted to setan attribute to a value thatis unknown.


Check the value and attribute.

8019-124 "Unable to definemultiple NOT filters."

DPASetFilterItem calledmore than once for a NOTfilter.



8019-125 "The requested filteroperation isunknown."

DPAOpenFilter called withan unknown logicaloperator.



8019-126 "The requested filterrelation is unknown."

DPASetFilterItem wascalled with an unknownrelational operator.


Modify the filter relation.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-129 "The directory or file<variable> is notaccessible to theuser."

The user does not havepermissions for thespecified file or directory.


Check and/or modify thepermissions on the directoryor file as necessary.

8019-130 "The directory or file<variable> was notfound."

The specified file ordirectory was not found.


Check the file and/or directoryto make sure it’s there.

8019-131 "The class <attributeclass> is invalid; theattributes are of class<attribute class>."

The value for ‘class’attribute, –c flag, or defaultclass does not correspondto attributes alreadyspecified.


Ensure that all the attributesare valid for the class.

8019-133 "The instance syntaxis invalid."

The syntax of the instancespecified is incorrect: startswith a colon, or does notmatch the class specified.


Ensure that the instance doesnot start with a colon and thatit matches the class.

8019-134 "There is no currentdocument."

DPAPushDocument wascalled without first callingDPAOpenDocument.



8019-135 "The physical printer<physical printername> was notfound."

The physical printerspecified was not found inthe namespace.


Check the namespaceenvironment and its spellingfor the printer.

8019-136 "The printer <printername> was notfound."

The printer specified wasnot found in thenamespace.


Check the namespaceenvironment and its spellingfor the printer.

8019-137 "The server <servername> was notfound."

The server specified wasnot found in thenamespace.


Check the namespaceenvironment and its spellingfor the server.

8019-139 "The queue <queuename> was notfound."

The queue specified wasnot found in thenamespace.


Check the namespaceenvironment and its spellingfor the queue.

8019-141 "The operation isinvalid for the class ofobject."

The requested operationcannot be performed on thespecified object.


Check the class attribute, the–c flag, or the name of theobject to make sure that theyare valid for this command.

8019-142 "The requester'saccess rights areinsufficient."

The user does not haveaccess rights to thespecified object.


Check the object name toobtain access to the specifiedobject.

8019-143 "Unable to interruptthe job."

The job has alreadyinterrupted another job andcannot do so again.


Try interrupting at a later time.

8019-144 "The operation isinvalid for the currentobject state."

The object is not in anappropriate state for therequested operation.


Modify the object state andretry the operation. If theproblem persists, contacttechnical support.

8019-145 "The attribute syntax<attribute value> isinvalid."

The syntax for the specifiedattribute value has beenentered incorrectly.


Check for data corruption inthe network.

8019-146 "The attribute<attribute name> isundefined."

The specified attribute hasnot been understood by theserver.


Check for data corruption inthe network.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-147 "The attribute<attribute name>does not match thevalue <attributevalue>."

The matching rule that wasused in a filter is not definedfor the specified attribute.


Check the relational operatorin the filter to make sure it’svalid for the specifiedattribute.

8019-148 "The attribute<attribute name> withthe value <attributevalue> exceeds themaximum sizeconstraint."

The specified attribute typeexceeds the maximumvalue for the attribute.


Check the value of theattribute to make sure it doesnot exceed the maximumvalue supported.

8019-149 "The attribute<attribute name> withthe value <attributevalue> alreadyexists."

The attribute or valuealready exists in the object.


Decide whether or not thevalue should be replaced,then delete or replace theattribute value.

8019-150 "The attribute<attribute name> isunsupported."

The specified attribute isnot supported by the server.


Ensure that the attributespecified is supported.

8019-151 "The modification ofthe attribute <attributename> is invalid."

The attribute may not bemodified as requested.


Check the attribute.

8019-152 "The attribute<attribute name> withthe value <attributevalue> is inconsistentwith other attributes."

The attributes in the sameprint job must be consistent.This error may occur whilemodifying a job when twoattributes contain conflictinginformation.


Check the attribute valueassignments forinconsistencies within thecurrent or previouscommands.

8019-153 "The attribute<attribute> with thevalue <attributevalue> is undefined."

The specified attributevalue assignment has notbeen understood by theserver.


Check the attribute andattribute value.

8019-154 "The attribute<attribute> with thevalue <attributevalue> isunsupported."

The specified attribute isnot supported by theobjects specified.


Check the attribute andattribute value to ensure thatthey are supported by theobjects specified.

8019-155 "The modification ofthe non-compulsoryattribute <attributename> to value<attribute value> isinvalid."

Either the attribute added toa non-compulsory attributeis not valid or the userattempted to modify a jobattribute when specifying adocument.


Check the attribute.

8019-156 "The per-job attribute<attribute name> isinadmissible."

A job attribute wassubmitted as the argumentof a DPA operation that wasnot the first in a series ofnetwork operations.


This may be caused by asystem problem.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-157 "The attribute<attribute name> isnot multi-valued."

An attempt was made tosupply more than oneelement for, or add anothervalue to, the valuecomponent of a single-valued attribute.


Ensure that the attribute ismulti-valued.

8019-158 "The mandatoryattribute <attributename> has beenomitted."

An attribute that is requiredfor the command wasomitted.


Ensure that all mandatoryattributes have been set forthe operation.

8019-159 "The attribute<attribute name> isinvalid for the objectclass."

An attribute was set thatdoes not correspond to thespecified class attribute or –c flag.


Check the attribute againstthe –c flag value or classattribute value.

8019-160 "The requesteddocument is notavailable."

The document is notavailable due to atemporary access problem.


Check the document beingprinted to ensure that it is notcurrently being used.

8019-161 "The documentreferent has beenmodified."

The document specified tobe printed was modifiedafter the server wassupposed to have printed it.


Ensure that the document willnot be modified before theserver is supposed to print it.

8019-162 "Access to thereferenced documenthas been denied."

The access rights of theuser are insufficient for thespecified document.


Ensure that the files printedusing the file-referencetransfer method have accessrights for the server.

8019-163 "The requesteddocument isunknown."

The document has alreadybeen deleted.


Ensure that the document tobe printed is not deletedbefore it prints.

8019-164 "There are nodocuments containedin the job."

The user attempted to printa job without anydocuments.


Ensure that the documentsare specified for a PRINTrequest.

8019-165 "A printer error hasoccurred."

An error has occurred onthe printer associated withthe print job.



8019-166 "The printer needsattention."

The printer associated withthe job needs attention.


Fix the printer problem andretry the operation. If theproblem persists, contacttechnical support.

8019-167 "The printer needskey operatorattention."

The printer associated withthe job needs key operatorattention.



8019-168 "The suppliedauthentication isinappropriate."

The user’s securitycredentials are insufficientfor the level of protectionrequested.


Ensure that the user’scredentials are sufficient forthe requested operation.

8019-169 "The suppliedcredentials areinvalid."

The user’s securitycredentials are invalid.


Ensure that the clientsoftware is compatible withthe server software.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-170 "The requester'soperation rights areinsufficient."

The requester’s operationrights need to be modifiedto perform the requestedoperation.


Modify the requester’soperation rights and retry theoperation. If the problempersists, contact technicalsupport.

8019-171 "The suppliedprivilege attributecertificate is invalid."

The privilege attributecertificate inCommonArguments isinvalid.


Ensure that the clientsoftware is compatible withthe server software.

8019-172 "The suppliedidentification isinvalid."

The syntax of the identifieris incorrect.



8019-173 "The suppliedidentification isunknown."

The server was not able tolocate the object instance.


Check to see if the objectexists on the server.

8019-174 "The object alreadyexists."

An operation was invokedthat attempted to create anobject with the same nameas an existing object.


Ensure that the object namedoes not already exist.

8019-175 "The server is busy." The server is presently toobusy to perform therequested operation butmay be able to do so after ashort while.


Retry the operation later.

8019-176 "The server isunavailable."

The server is currentlyunavailable.


Retry the operation later orcontact technical support.

8019-177 "The operation is toocomplex."

The operation requested istoo syntactically orsemantically complex.


Reduce the complexity andretry the operation. If theproblem persists, contacttechnical support.

8019-178 "The resource limitshave beenexceeded."

This error may occur whena very large object is beingcreated or copied.


Lower the threshold or freespace on the server.

8019-179 "An unclassifiedserver error hasoccurred."




8019-180 "The are too manyitems in the list."

The user specified moreitems in a list than aresupported by the server.


Reduce the number of listitems.

8019-181 "A requestedcompulsory resourceis not available."

A compulsory attributecannot be satisfied becausethe value requested is notavailable.


Ensure that the value isavailable and retry theoperation. If the problempersists, contact technicalsupport.

8019-182 "The canceldocument operationis not supported."

The user cannot cancel anindividual document within adocument job.


Locate a server that supportsdocument cancellation.

8019-183 "The modifydocument operationis not supported."

The user cannot modify anindividual document within amultiple document job.


Locate a server that supportsdocument modification.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-184 "The printing ofmultiple documents isnot supported."

The user cannot printmultiple documents within asingle job.


The documents must beprinted as separate jobs.

8019-185 "A suppliedparameter value isnot supported."

A component of anargument was specified to aDPA operation that is not anattribute with a value notsupported by the server.



8019-186 "The suppliedcheckpoint is invalid."

An invalid checkpoint wassupplied to the RESUMEDPA operation. Acheckpoint value becomesinvalid if it is altered orcorrupted.



8019-187 "The requestedoperation is notsupported."

The DPA operationrequested is not currentlysupported by the server.This error may be causedby attempting a symboliclink between pdinterruptand another command.



8019-188 "The suppliedcontinuation contextis invalid."

An invalid continuationcontext was supplied to thelist operation.



8019-189 "The pause limit hasbeen exceeded."

Either a pause or interruptrequest was made to theserver in excess of thenumber of jobs that may bepaused. The server maydefine this limit on a per-printer or per-server basis.


Resume some of the jobsbefore pausing new ones.

8019-190 "The requestedmodifications are notallowed."

The print job referred by thejob identifier is executingand cannot be modified atthis time.


Wait until the job isprocessed.

8019-191 "The requester'supdate rights areinsufficient."

The user’s access rightsare insufficient for modifyingthis object.


Check the access control listfor the privilege level of theuser.

8019-192 "The previousoperation isincomplete."

Additional operations arenot allowed until theprevious operation hasfinished.


Wait until the previousoperation has finished.

8019-193 "The requestedcancellation is notpossible."

Cancellation not possiblebecause the job has alreadycompleted.


None

8019-195 "A job number hasnot been specified."

In a cancel or modifyoperation the job identifierwas not specified.


Ensure that there is a jobidentifier set for the operation.

8019-196 "An object instancehas not beenspecified."

No object instance wasspecified.


Ensure that the commandcontains an object instance.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-197 "There are no moreobject instancesavailable."

There are no moreinstances left to return byDPAGetObjectInstance.



8019-198 "A logical printer orserver name was notspecified."

This error may be causedby entering a pdpr or pdqcommand withoutspecifying the printer nameor by entering a CLIcommand that contains ajob object without specifyinga server name. A printername may not have beenfound in the PDPRINTERenvironment variable. Thiserror may also occur whenthe object instancespecified in the call toDPAGetObjectInstance isnot found in the set ofreturned instances.


Set the PDPRINTERenvironment variable orspecify a value for -p orspecify the server name aspart of the object instance.

8019-199 "There are no morewarnings or errors."

There are no morewarnings or errors left toreturn byDPAGetNextWarningOrError.



8019-200 "The attribute isunknown."

An internal API error hasoccurred.



8019-201 "The request isalready closed."

DPACloseRequest wascalled with a handle thathas already been closed.



8019-202 "An extended errorcondition hasoccurred."

An internal API error hasoccurred.



8019-203 "The object identifieris unknown."

An OID set by the user orreturned by the server is notknown by the client.



8019-204 "The required routinehas not beenimplemented."

A function has beenrequested that is notimplemented.




This error may occur whenthe server is too busy torespond.


Retry the operation and checkto see that the server isrunning. If the problempersists, contact technicalsupport.

8019-206 "Unable to open theobject identifierdatabase."

The object identifierdatabase is not available.


Check PD_OID_DB_PATH orthe default Object Identifierdatabase path.

8019-208 "The request handleinitialization hasfailed."

An unexpected failure of theattribute set calls hasoccurred when callingDPAOpenRequest.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8019-212 "The documenthandle initializationhas failed."

An unexpected failure of theattribute set calls hasoccurred when callingDPAOpenRequest.



8019-215 "The specified filename is a directory."

A proper file name was notprovided.


Ensure that the file specifiedis actually a file and not adirectory.

8022-101 "Spooler <spoolername> failed startupdue to <reason>."

The spooler has failed tostart for the stated reason.

Rejects therequest.

Restart the spooler.

8022-102 "Supervisor<supervisor name>failed startup due to<reason>."

The supervisor has failed tostart for the stated reason.

Rejects therequest.

Restart the supervisor.

8022-103 "Spooler <spoolername> could notcommunicate withsupervisor<supervisor name>."

The spooler was unable tocommunicate with thesupervisor.

Rejects therequest.

Check the connectionbetween the spooler and thesupervisor.

8022-104 "Supervisor<supervisor name>could notcommunicate withspooler <spoolername>."

The supervisor was unableto communicate with thespooler.

Rejects therequest.

Check the connectionbetween the spooler and thesupervisor.

8022-105 "Spooler <spoolername> could notcommunicate with thenotification server."

The spooler was unable tocommunicate with thenotification server.

Rejects therequest.

Check the connectionbetween the spooler and theserver.

8022-106 "The notificationserver could notestablishcommunication withserver <servername>."

The notification servercould not establishcommunication with thespecified server.

Rejects therequest.


8022-107 "Printer <printername> requires a keyoperator."

The printer associated withthe job requires keyoperator attention.



8022-108 "Printer <printername> is out ofpaper."

The specified printer is outof paper.


Add paper to the specifiedprinter and retry theoperation. If the problempersists, contact technicalsupport.

8022-109 "Printer <printername> is jammed."

The specified printer isjammed.


Fix the printer jam and retrythe operation. If the problempersists, contact technicalsupport.

8022-110 "There is a problemwith printer <printername>. Please notifythe key operator."

The specified printer hasencountered an unspecifiedproblem.


Correct the problem and retrythe operation. If the problempersists, contact technicalsupport.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-111 "Printer <printername> is out oftoner."

The specified printer is outof toner.


Add toner to the specifiedprinter and retry theoperation. If the problempersists, contact technicalsupport.

8022-112 "The queue thresholdhas been reached forqueue <queuename>. There aremore pending jobsthan allowed."

The queue is disabled whenit reaches the maximumnumber (value of queue-backlog-upper-limit) of jobsallowed.


Wait until the number of jobsin the queue drops below theminimum number (value ofqueue-backlog-lower-limit) ofjobs allowed. The queue willbe automatically enabled atthis time.

8022-113 "Queue <queuename> is no longerfull."

The number of jobs in thespecified queue no longerexceeds the maximumlevel.

The queueisautomatically enabled.

None

8022-114 "The queue thresholdhas been reached forqueue <queue name>and has beendisabled. There aremore pending jobsthan allowed."

The queue is disabled whenit reaches the maximumnumber (value of queue-backlog-upper-limit) of jobsallowed.


Wait until the number of jobsin the queue drops below theminimum number (value ofqueue-backlog-lower-limit) ofjobs allowed. The queue willbe automatically enabled atthis time.

8022-115 "Cancellation ofdocument <documentname> has notcompletedsuccessfully.<reason>."

The specified documenthas not completedsuccessfully for the statedreason.



8022-116 "Cancellation of job<job name> has notcompletedsuccessfully.<reason>."

The specified job has notcompleted successfully forthe stated reason.



8022-117 "Removal of all jobsin queue <queuename> has notcompletedsuccessfully.<reason>."

The removal operation forthe specified queue has notcompleted successfully forthe stated reason.



8022-118 "Removal of all jobsin server <servername> has notcompletedsuccessfully.<reason>."

The removal operation forthe specified server has notcompleted successfully forthe stated reason.



8022-119 "Creation of initialvalue document<document name> on<server name> hasnot completedsuccessfully.<reason>."

The creation operation forthe specified server has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-120 "Creation of initialvalue job <initial valuename> on <servername> has notcompletedsuccessfully.<reason>."




8022-121 "Creation of printer<printer name> on<server name> hasnot completedsuccessfully.<reason>."




8022-122 "Creation of queue<queue name> on<server name> hasnot completedsuccessfully.<reason>."




8022-123 "Deletion ofdocument <documentname> has notcompletedsuccessfully.<reason>."

The deletion operation forthe specified server has notcompleted successfully forthe stated reason.



8022-124 "Deletion of initialvalue document<document name>has not completedsuccessfully.<reason>."

The deletion operation forthe specified document hasnot completed successfullyfor the stated reason.



8022-125 "Deletion of initialvalue job <initial valuejob name> has notcompletedsuccessfully.<reason>."

The deletion operation forthe specified initial value jobhas not completedsuccessfully for the statedreason.



8022-126 "Deletion of job <jobname> has notcompletedsuccessfully.<reason>."

The deletion operation forthe specified job has notcompleted successfully forthe stated reason.



8022-127 "Deletion of printer<printer name> hasnot completedsuccessfully.<reason>."

The deletion operation forthe specified printer has notcompleted successfully forthe stated reason.



8022-128 "Deletion of queue<queue name> hasnot completedsuccessfully.<reason>."

The deletion operation forthe specified queue has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-129 "Deletion of server<server name> hasnot completedsuccessfully.<reason>."




8022-130 "Rejection of newprint jobs on printer<printer name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified printerhas not completedsuccessfully for the statedreason.



8022-131 "Rejection of newprint jobs on queue<queue name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified queuehas not completedsuccessfully for the statedreason.



8022-132 "Rejection of newprint jobs on server<server name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified serverhas not completedsuccessfully for the statedreason.



8022-133 "Acceptance of newprint jobs on printer<printer name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedprinter has not completedsuccessfully for the statedreason.



8022-134 "Acceptance of newprint jobs on queue<queue name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedqueue has not completedsuccessfully for the statedreason.



8022-135 "Acceptance of newprint jobs on server<server name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedserver has not completedsuccessfully for the statedreason.



8022-136 "Enumeration of jobsfor printer <printername> has notcompletedsuccessfully.<reason>."

The enumeration of newprint jobs for the specifiedprinter has not completedsuccessfully for the statedreason.



8022-137 "Interruption of job<job name> has notcompletedsuccessfully.<reason>."

The interruption of thespecified job has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-138 "Listing of attributesfor documents hasnot completedsuccessfully.<reason>."

The listing of attributes fordocuments has notcompleted successfully forthe stated reason.



8022-139 "Listing of attributesfor initial valuedocuments has notcompletedsuccessfully.<reason>."

The listing of attributes forinitial value documents hasnot completed successfullyfor the stated reason.



8022-140 "Listing of attributesfor initial value jobshas not completedsuccessfully.<reason>."

The listing of attributes forinitial value jobs has notcompleted successfully forthe stated reason.



8022-141 "Listing of attributesfor jobs has notcompletedsuccessfully.<reason>."

The listing of attributes forjobs has not completedsuccessfully for the statedreason.



8022-142 "Listing of attributesfor printers has notcompletedsuccessfully.<reason>."

The listing of attributes forprinters has not completedsuccessfully for the statedreason.



8022-143 "Listing of attributesfor queues has notcompletedsuccessfully.<reason>."

The listing of attributes forqueues has not completedsuccessfully for the statedreason.



8022-144 "Listing of attributesfor servers has notcompletedsuccessfully.<reason>."

The listing of attributes forservers has not completedsuccessfully for the statedreason.



8022-145 "Modification ofdocument <documentname> has notcompletedsuccessfully.<reason>."

The modification of thespecified document has notcompleted successfully forthe stated reason.



8022-146 "Modification of job<job name> has notcompletedsuccessfully.<reason>."

The modification of thespecified job has notcompleted successfully forthe stated reason.



8022-147 "Print submission onprinter <printername> has notcompletedsuccessfully.<reason>."

The print submissionoperation for the specifiedprinter has not completedsuccessfully for the statedreason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-148 "Addition of adocument to job <jobname> has notcompletedsuccessfully.<reason>."

The addition of a documentto the specified job has notcompleted successfully forthe stated reason.



8022-149 "Closing of job <jobname> has notcompletedsuccessfully.<reason>."

The closing of the specifiedjob has not completedsuccessfully for the statedreason.



8022-150 "Pausing of printer<printer name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified printer has notcompleted successfully forthe stated reason.



8022-151 "Pausing of queue<queue name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified queue has notcompleted successfully forthe stated reason.



8022-152 "Pausing of server<server name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified server has notcompleted successfully forthe stated reason.



8022-153 "Pausing of job <jobname> has notcompletedsuccessfully.<reason>."

The pausing of thespecified job has notcompleted successfully forthe stated reason.



8022-154 "Promotion of job<job name> has notcompletedsuccessfully.<reason>."

The promotion of thespecified job has notcompleted successfully forthe stated reason.



8022-155 "Resuming of printer<printer name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified printer has notcompleted successfully forthe stated reason.



8022-156 "Resuming of queue<queue name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified queue has notcompleted successfully forthe stated reason.



8022-157 "Resuming of server<server name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified server has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-158 "Resuming of job<job name> has notcompletedsuccessfully.<reason>."

The resuming of thespecified job has notcompleted successfully forthe stated reason.



8022-159 "Resubmission of job<job name> to<server name> hasnot completedsuccessfully.<reason>."

The resubmission of thespecified job to thespecified server has notcompleted successfully forthe stated reason.



8022-160 "Resubmission ofqueue <queue name>to <server name> hasnot completedsuccessfully.<reason>."

The resubmission of thespecified queue to thespecified server has notcompleted successfully forthe stated reason.



8022-161 "Attribute modificationof document<document name>has not completedsuccessfully.<reason>."

The attribute modification ofthe specified document hasnot completed successfullyfor the stated reason.



8022-162 "Attribute modificationof initial valuedocument <initialvalue documentname> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified initial valuedocument has notcompleted successfully forthe stated reason.



8022-163 "Attribute modificationof initial value job<initial value jobname> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified initial value jobhas not completedsuccessfully for the statedreason.



8022-164 "Attribute modificationof job <job name>has not completedsuccessfully.<reason>."

The attribute modification ofthe specified job has notcompleted successfully forthe stated reason.



8022-165 "Attribute modificationof printer <printername> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified printer has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-166 "Attribute modificationof queue <queuename> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified queue has notcompleted successfully forthe stated reason.



8022-167 "Attribute modificationof server <servername> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified server has notcompleted successfully forthe stated reason.



8022-168 "Shutdown of server<server name> hasnot completedsuccessfully.<reason>."

The shutdown operation ofthe specified server has notcompleted successfully forthe stated reason.



8022-170 "Supervisor: Unableto open file <filename>."

The Xerox supervisor wasnot able to find the MAMlibrary file name in the filepath.


Install the MAM library file onthe path and delete thephysical printer. Recreate thephysical printer. If theproblem persists, contacttechnical support.

8022-171 "Supervisor: AnSNMP error hasoccurred in printer<printer name>."

The Xerox supervisor wasnot able to establish theSNMP session to thespecified printer.


Check to see if the printeraddress, community string, orprinter device is valid. Thendelete the physical printer andrecreate it. If the problempersists, contact technicalsupport.

8022-172 "Supervisor: Unableto resolve printeraddress <printeraddress>."

The Xerox supervisor wasnot able to resolve thespecified printer addresswith the appropriatetransport address. Theprinter address may beinvalid.


Check to see if the printeraddress was registered in thehost database. Then deletethe physical printer andrecreate it. If the problempersists, contact technicalsupport.

8022-173 "Supervisor: Therewas no response tothe SNMP request onprinter <printername>."

The Xerox supervisor wasnot able to receive aresponse from the printerdevice. Either the device isnot enabled or the printer-state of the physical printerobject has changed to“timed out”.


Check to see if the printerdevice is running. The printeraddress and/or communitystring may also be invalid.After fixing one of the aboveproblems, delete the physicalprinter and recreate it. If theproblem persists, contacttechnical support.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-174 "Supervisor: AnSNMPcommunication errorhas occurred inprinter <printername>."

The Xerox supervisor onSNMP was unable tocommunicate with theprinter device. Either thephysical printer is notenabled or the printer-stateof the printer has changedto “timed-out”.


Check to see if the physicalprinter is running. The printeraddress, community string, orprinter device may also beinvalid. After fixing one of theabove problems, reset thephysical printer. If theproblem persists, contacttechnical support.

8022-175 "Supervisor: Unableto retrieve themessage string<message string>."

The Xerox supervisor wasunable to retrieve themessage string frommessage file.


Check to see if the messagefiles xrssnmp.dll orxrssnmp.cat are located in themessage directory. Ifnecessary, add the messagefiles to the directory. Thendelete the physical printer andrecreate it. If the problempersists, contact technicalsupport.

8022-176 "Supervisor: Thereare no values in theMIB Database<object identifier>."

The Xerox supervisor wasunable to retrieve a valuefrom the physical printereven though the SNMPagent on the deviceseemed to be working. Thephysical printer state mayhave changed to “timed-out”.


Reset the printer. If theproblem persists, contacttechnical support.

8022-257 "Cancellation ofdocument <documentname> has notcompletedsuccessfully.<reason>."

The specified documenthas not completedsuccessfully for the statedreason.



8022-258 "Cancellation of job<job name> has notcompletedsuccessfully.<reason>."

The specified job has notcompleted successfully forthe stated reason.



8022-259 "Removal of all jobsin queue <queuename> has notcompletedsuccessfully.<reason>."

The removal operation forthe specified queue has notcompleted successfully forthe stated reason.



8022-260 "Removal of all jobsin server <servername> has notcompletedsuccessfully.<reason>."

The removal operation forthe specified server has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-261 "Creation of initialvalue document<document name> on<server name> hasnot completedsuccessfully.<reason>."




8022-262 "Creation of initialvalue job <initial valuename> on <servername> has notcompletedsuccessfully.<reason>."




8022-263 "Creation of printer<printer name> on<server name> hasnot completedsuccessfully.<reason>."




8022-264 "Creation of queue<queue name> on<server name> hasnot completedsuccessfully.<reason>."




8022-265 "Deletion ofdocument <documentname> has notcompletedsuccessfully.<reason>."




8022-266 "Deletion of initialvalue document<document name>has not completedsuccessfully.<reason>."

The deletion operation forthe specified document hasnot completed successfullyfor the stated reason.



8022-267 "Deletion of initialvalue job <initial valuejob name> has notcompletedsuccessfully.<reason>."

The deletion operation forthe specified initial value jobhas not completedsuccessfully for the statedreason.



8022-268 "Deletion of job <jobname> has notcompletedsuccessfully.<reason>."

The deletion operation forthe specified job has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-269 "Deletion of printer<printer name> hasnot completedsuccessfully.<reason>."

The deletion operation forthe specified printer has notcompleted successfully forthe stated reason.



8022-270 "Deletion of queue<queue name> hasnot completedsuccessfully.<reason>."

The deletion operation forthe specified queue has notcompleted successfully forthe stated reason.



8022-271 "Deletion of server<server name> hasnot completedsuccessfully.<reason>."




8022-272 "Rejection of newprint jobs on printer<printer name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified printerhas not completedsuccessfully for the statedreason.



8022-273 "Rejection of newprint jobs on queue<queue name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified queuehas not completedsuccessfully for the statedreason.



8022-274 "Rejection of newprint jobs on server<server name> hasnot completedsuccessfully.<reason>."

The rejection of new printjobs for the specified serverhas not completedsuccessfully for the statedreason.



8022-275 "Acceptance of newprint jobs on printer<printer name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedprinter has not completedsuccessfully for the statedreason.



8022-276 "Acceptance of newprint jobs on queue<queue name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedqueue has not completedsuccessfully for the statedreason.



8022-277 "Acceptance of newprint jobs on server<server name> hasnot completedsuccessfully.<reason>."

The acceptance of newprint jobs for the specifiedserver has not completedsuccessfully for the statedreason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-278 "Enumeration of jobsfor printer <printername> has notcompletedsuccessfully.<reason>."

The enumeration of newprint jobs for the specifiedprinter has not completedsuccessfully for the statedreason.



8022-279 "Interruption of job<job name> has notcompletedsuccessfully.<reason>."

The interruption of thespecified job has notcompleted successfully forthe stated reason.



8022-280 "Listing of attributesfor documents hasnot completedsuccessfully.<reason>."

The listing of attributes fordocuments has notcompleted successfully forthe stated reason.



8022-281 "Listing of attributesfor initial valuedocuments has notcompletedsuccessfully.<reason>."

The listing of attributes forinitial value documents hasnot completed successfullyfor the stated reason.



8022-282 "Listing of attributesfor initial value jobshas not completedsuccessfully.<reason>."

The listing of attributes forinitial value jobs has notcompleted successfully forthe stated reason.



8022-283 "Listing of attributesfor jobs has notcompletedsuccessfully.<reason>."

The listing of attributes forjobs has not completedsuccessfully for the statedreason.



8022-284 "Listing of attributesfor printers has notcompletedsuccessfully.<reason>."

The listing of attributes forprinters has not completedsuccessfully for the statedreason.



8022-285 "Listing of attributesfor queues has notcompletedsuccessfully.<reason>."

The listing of attributes forqueues has not completedsuccessfully for the statedreason.



8022-286 "Listing of attributesfor servers has notcompletedsuccessfully.<reason>."

The listing of attributes forservers has not completedsuccessfully for the statedreason.



8022-287 "Modification ofdocument <documentname> has notcompletedsuccessfully.<reason>."

The modification of thespecified document has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-288 "Modification of job<job name> has notcompletedsuccessfully.<reason>."

The modification of thespecified job has notcompleted successfully forthe stated reason.



8022-289 "Print submission onprinter <printername> has notcompletedsuccessfully.<reason>."

The print submissionoperation for the specifiedprinter has not completedsuccessfully for the statedreason.



8022-290 "Addition of adocument to job <jobname> has notcompletedsuccessfully.<reason>."

The addition of a documentto the specified job has notcompleted successfully forthe stated reason.



8022-291 "Closing of job <jobname> has notcompletedsuccessfully.<reason>."

The closing of the specifiedjob has not completedsuccessfully for the statedreason.



8022-292 "Pausing of printer<printer name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified printer has notcompleted successfully forthe stated reason.



8022-293 "Pausing of queue<queue name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified queue has notcompleted successfully forthe stated reason.



8022-294 "Pausing of server<server name> hasnot completedsuccessfully.<reason>."

The pausing of thespecified server has notcompleted successfully forthe stated reason.



8022-295 "Pausing of job <jobname> has notcompletedsuccessfully.<reason>."

The pausing of thespecified job has notcompleted successfully forthe stated reason.



8022-296 "Promotion of job<job name> has notcompletedsuccessfully.<reason>."

The promotion of thespecified job has notcompleted successfully forthe stated reason.



8022-297 "Resuming of printer<printer name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified printer has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-298 "Resuming of queue<queue name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified queue has notcompleted successfully forthe stated reason.



8022-299 "Resuming of server<server name> hasnot completedsuccessfully.<reason>."

The resuming of thespecified server has notcompleted successfully forthe stated reason.



8022-300 "Resuming of job<job name> has notcompletedsuccessfully.<reason>."

The resuming of thespecified job has notcompleted successfully forthe stated reason.



8022-301 "Resubmission of job<job name> to<server name> hasnot completedsuccessfully.<reason>."

The resubmission of thespecified job to thespecified server has notcompleted successfully forthe stated reason.



8022-302 "Resubmission ofqueue <queue name>to <server name> hasnot completedsuccessfully.<reason>."

The resubmission of thespecified queue to thespecified server has notcompleted successfully forthe stated reason.



8022-303 "Attribute modificationof document<document name>has not completedsuccessfully.<reason>."

The attribute modification ofthe specified document hasnot completed successfullyfor the stated reason.



8022-304 "Attribute modificationof initial valuedocument <initialvalue documentname> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified initial valuedocument has notcompleted successfully forthe stated reason.



8022-305 "Attribute modificationof initial value job<initial value jobname> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified initial value jobhas not completedsuccessfully for the statedreason



8022-306 "Attribute modificationof job <job name>has not completedsuccessfully.<reason>."

The attribute modification ofthe specified job has notcompleted successfully forthe stated reason.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-307 "Attribute modificationof printer <printername> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified printer has notcompleted successfully forthe stated reason.



8022-308 "Attribute modificationof queue <queuename> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified queue has notcompleted successfully forthe stated reason.



8022-309 "Attribute modificationof server <servername> has notcompletedsuccessfully.<reason>."

The attribute modification ofthe specified server has notcompleted successfully forthe stated reason.



8022-310 "Shutdown of server<server name> hasnot completedsuccessfully.<reason>."

The shutdown operation ofthe specified server has notcompleted successfully forthe stated reason.



8022-325 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to lackof memory."




8022-326 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to lackof disk space."

This error may be causedby a lack of disk space.


Check the availability of thedisk space and retry theoperation. If the problempersists, contact technicalsupport.

8022-327 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to aninternal error."

This error may be causedby a PrintXchange systemerror.



8022-328 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to asystem call error."

This error may be causedby a system call failure.



8022-329 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to anunspecified filter."

The file name for executinga filter is not specified.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-330 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausethe path name(including thecommand options) offilter <filter name> istoo long."

The length of a file namefor executing filter <filtername> is over themaximum (255 bytes). Orin Windows NT the lengthof a command line includingthe command options forfilter <filter name> revised isover the maximum (4095bytes).



8022-331 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausethe command option<option> of filter<filter name> is toolong."

The length of a commandoption <option> in acommand line for filter<filter name> is over themaximum (4095 bytes).



8022-332 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausethe specified attributename <attributename> of filter <filtername> is too long."

The length of an attributename <attribute name> in acommand line for filter<filter name> is over themaximum (100 characters).



8022-333 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausefilter <filter name>doesn’t exist."

The file name for executingthe filter <filter name>doesn’t exist in thespecified directory.



8022-334 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation due to asystem error whileinvoking filter <filtername>."

A system call for invokingthe filter <filter name>failed.



8022-335 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausefilter <filter name>terminatedabnormally with thefollowing error <errorcode>."

The filter <filter name>terminated abnormally withan exit code <error code>.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-336 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausefilter <filter name>terminatedabnormally."

The filter <filter name>terminated abnormally withno exit code.



8022-337 "JobID <job identifier>Doc <documentnumber>: Unable toperform the preprintoperation becausethe filter operationtimed out."

The filter operation timedout.



8022-338 "Database recovery:Document object <jobidentifier>.<documentnumber> has beendeleted from the<database>database."

A document object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.

The systemdeleted thisobjectduringsystemrestart.

Ensure that the loss of thisobject does not cause anyproblems for thecorresponding job.Occasionally, the job will needto be manually deleted aswell.

8022-339 "Database recovery:Generic object<object> has beendeleted from the<database>database."

A generic object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.


None. However, an eventnotification may have beenlost.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-340 "Database recovery:Initial-value-document object<ivdoc object> hasbeen deleted from the<database>database."

An initial-value-documentobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check to see if any logicalprinters were affected bycompleting the followingoperation:pdls –c printer –f printer-initial-value-document=<ivdoc object><serverName>:

If any printers are returnedfrom this query, take one ofthe following three actions tocorrect the situation.

1. Create an initial-value-document with the name<ivdoc object> on the server<serverName>. The printersreturned by the above querywill then use this newlycreated initial-value-document.

2. Modify the value of theprinter-initial-value-documentattribute on these printers touse another initial-value-document that exists on theserver <serverName>. Forexample:pdset –c printer –xprinter-initial-value-document=<ivdName><printerName>

3. Modify the value of theprinter-initial-value-documentattribute on these printers sothat an initial-value-documentis not used. For example:pdset –c printer –x"printer-initial-value-document==" <printerName>

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-341 "Database recovery:Initial-value-job object<ivjob object> hasbeen deleted from the<database>database."

An initial-value-job objectwas corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check to see if any logicalprinters were affected bycompleting the followingoperation:pdls –c printer –f printer-initial-value-job==<ivjobobject> <serverName>:

If any printers are returnedfrom this query, take one ofthe following three actions tocorrect the situation.

1. Create an initial-value-jobwith the name <ivjob object>on the server <serverName>.The printers returned by theabove query will then use thisnewly created initial-value-job.

2. Modify the value of theprinter-initial-value-jobattribute on these printers touse another initial-value-jobthat exists on the server<serverName>. For example:pdset –c printer –xprinter-initial-value-job=<ivjobName><printerName>

3. Modify the value of theprinter-initial-value-jobattribute on these printers sothat an initial-value-job is notused. For example:pdset –c printer –x"printer-initial-value-job==" <printerName>

8022-342 "Database recovery:Job object <jobidentifier> has beendeleted from the<database>database."

A job object was corruptedin the database. It had tobe deleted in order for thedatabase to be recoveredand the server to bestarted.


None. However, a job mayhave been lost.

8022-343 "Database recovery:Printer object <printerobject> has beendeleted from the<database>database."

A printer object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.


Recreate the printer.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-344 "Database recovery:Queue object <queueobject> has beendeleted from the<database>database."

A queue object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.


Recreate the queue.

8022-345 "Database recovery:Server object <serverobject> has beendeleted from the<database>database."

A server object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.


Recreate the server.

8022-346 "Database recovery:An unidentifieddocument object hasbeen deleted from the<database>database."

An unidentified documentobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.

The systemdeleted anobjectduringsystemrestart.

None. However, a documentmay have been lost.

8022-347 "Database recovery:An unidentifiedgeneric object hasbeen deleted from the<database>database."

An unidentified genericobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-348 "Database recovery:An unidentified initial-value-documentobject has beendeleted from the<database>database."

An unidentified initial-value-document object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.


Check to see if any logicalprinters were affected bycompleting the followingoperation:pdls –c printer –r printer-initial-value-document<serverName>:

Then complete the followingoperation for each initial valuedocument:pdls –c initial-value-document<serverName>:<ivdName>

If any initial-value-documentsare missing from this query,take one of the following threeactions to correct thesituation.

1. Recreate the missinginitial-value-document.

2. Modify the value of theprinter-initial-value-documentattribute on these printers touse another initial-value-document that exists on theserver <serverName>. Forexample:pdset –c printer –xprinter-initial-value-document=<ivdName><printerName>

3. Modify the value of theprinter-initial-value-documentattribute on these printers sothat an initial-value-documentis not used. For example:pdset –c printer –x"printer-initial-value-document==" <printerName>

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-349 "Database recovery:An unidentified initial-value-job object hasbeen deleted from the<database>database."

An unidentified initial-value-job object was corrupted inthe database. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check to see if any logicalprinters were affected bycompleting the followingoperation:pdls –c printer –r printer-initial-value-job<serverName>:

Then complete the followingoperation for each initial valuejob:pdls –c initial-value-job<serverName>:<ivjName>

If any initial-value-jobs aremissing from this query, takeone of the following threeactions to correct thesituation.

1. Recreate the missinginitial-value-job.

2. Modify the value of theprinter-initial-value-jobattribute on these printers touse another initial-value-jobthat exists on the server<serverName>. For example:pdset –c printer –xprinter-initial-value-job=<ivdName> <printerName>

3. Modify the value of theprinter-initial-value-jobattribute on these printers sothat an initial-value-job is notused. For example:pdset –c printer –x"printer-initial-value-job==" <printerName>

8022-350 "Database recovery:An unidentified jobobject has beendeleted from the<database>database."

An unidentified job objectwas corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


None. However, a job mayhave been lost.

8022-351 "Database recovery:An unidentified printerobject has beendeleted from the<database>database."

An unidentified printerobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


List all the printers in theserver to identify the missingprinter; then recreate themissing printer.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-352 "Database recovery:An unidentified queueobject has beendeleted from the<database>database."

An unidentified queueobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


List all the queues in theserver to identify the missingqueue; then recreate themissing queue.

8022-353 "Database recovery:An unidentified serverobject has beendeleted from the<database>database."

An unidentified serverobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Recreate the server.

8022-354 "Database recovery:The <attribute>attribute of thedocument object <jobidentifier>.<documentnumber> has beendeleted from the<database>database."

An attribute was corruptedin the database. It had tobe deleted in order for thedatabase to be recoveredand the server to bestarted.

The systemdeleted thisattributeduringsystemrestart.

Set the attribute to theappropriate value.

8022-355 "Database recovery:The <attribute>attribute of thegeneric object<object> has beendeleted from the<database>database."

An attribute of a genericobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



8022-356 "Database recovery:The <attribute>attribute of the initial-value-documentobject <object> hasbeen deleted from the<database>database."

An attribute of an initial-value-document object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.



8022-357 "Database recovery:The <attribute>attribute of the initial-value-job object<object> has beendeleted from the<database>database."

An attribute of an initialvalue job object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-358 "Database recovery:The <attribute>attribute of the jobobject <object> hasbeen deleted from the<database>database."

An attribute of a job objectwas corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



8022-359 "Database recovery:The <attribute>attribute of the printerobject <object> hasbeen deleted from the<database>database."

An attribute of a printerobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



8022-360 "Database recovery:The <attribute>attribute of the queueobject <object> hasbeen deleted from the<database>database."

An attribute of a queueobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



8022-361 "Database recovery:The <attribute>attribute of the serverobject <object> hasbeen deleted from the<database>database."

An attribute of a serverobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.



8022-362 "Database recovery:An unidentifiedattribute of thedocument object <jobidentifier>.<documentnumber>has beendeleted from the<database>database."

An unidentified attribute of adocument object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.

The systemdeleted anattributeduringsystemrestart.

Check all the attributes bycompleting the followingoperation:pdls –c document -r all<serverName>:<jobidentifier>.<documentnumber>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c document -x<attribute>=<value><serverName>:<jobidentifier>.<documentnumber>

8022-363 "Database recovery:An unidentifiedattribute of thegeneric object<object> has beendeleted from the<database>database."

An unidentified attribute of ageneric object wascorrupted in the database.It had to be deleted in orderfor the database to berecovered and the server tobe started.



TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-364 "Database recovery:An unidentifiedattribute of the initial-value-documentobject <object> hasbeen deleted from the<database>database."

An unidentified attribute ofan initial-value-documentobject was corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c initial-value-document -r all<serverName>:<ivdocName>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c initial-value-document -x<attribute>=<value><serverName>:<ivdocName>

8022-365 "Database recovery:An unidentifiedattribute of the initial-value-job object<object> has beendeleted from the<database>database."

An unidentified attribute ofan initial-value-job objectwas corrupted in thedatabase. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c initial-value-job -r all<serverName>:<ivjobName>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c initial-value-job-x <attribute>=<value><serverName>:<ivjobName>

8022-366 "Database recovery:An unidentifiedattribute of the jobobject <object> hasbeen deleted from the<database>database."

An unidentified attribute of ajob object was corrupted inthe database. It had to bedeleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c job -r all<serverName>:<jobidentifier>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c job -x<attribute>=<value><serverName>:<jobidentifier>

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-367 "Database recovery:An unidentifiedattribute of the printerobject <object> hasbeen deleted from the<database>database."

An unidentified attribute of aprint object was corruptedin the database. It had tobe deleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c printer -r all<printerName>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c printer -x<attribute>=<value><printerName>

8022-368 "Database recovery:An unidentifiedattribute of the queueobject <object> hasbeen deleted from the<database>database."

An unidentified attribute of aqueue object was corruptedin the database. It had tobe deleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c queue -r all<queueName>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c queue -x<attribute>=<value><queueName>

8022-369 "Database recovery:An unidentifiedattribute of the serverobject <object> hasbeen deleted from the<database>database."

An unidentified attribute of aserver object was corruptedin the database. It had tobe deleted in order for thedatabase to be recoveredand the server to bestarted.


Check all the attributes bycompleting the followingoperation:pdls –c server -r all<serverName>

Check to see if there are anymissing attributes and setthem to the appropriate valueby completing the followingoperation:pdset –c server -x<attribute>=<value><serverName>

8022-370 "Xerox Supervisor:Unable to open file<file name>."

The Xerox supervisor wasnot able to find the MAMlibrary file name in the filepath.

The requestto enablethe physicalprinter is notprocessed.

Install the MAM library file onthe path and delete thephysical printer. Recreate thephysical printer. If theproblem persists, contacttechnical support.

8022-771 "Xerox Supervisor:An SNMP error hasoccurred in printer<printer address> infunction <functionname>."

The Xerox supervisor wasnot able to establish theSNMP session to thespecified printer.


Check to see if the printeraddress, community string, orprinter device are valid. Thendelete the physical printer andrecreate it. If the problempersists, contact technicalsupport.

TROUBLESHOOTING



ERRORNUMBER


REQUIRED ACTION

8022-372 "Xerox Supervisor:Unable to resolveprinter address<printer address>."

The Xerox supervisor wasnot able to resolve thespecified printer addresswith the appropriatetransport address. Theprinter address may beinvalid.


Check to see if the printeraddress was registered in thehost database. Then deletethe physical printer andrecreate it. If the problempersists, contact technicalsupport.

8022-373 "Xerox Supervisor:There was noresponse to theSNMP request onprinter <printeraddress>."

The Xerox supervisor wasnot able to receive aresponse from the printerdevice. Either the device isnot enabled or the printer-state of the physical printerobject has changed to“timed out”.

Either therequest toenable thephysicalprinter is notprocessedor the printerstate of thephysicalprinter is“timed-out”.

Check to see if the printerdevice is running. The printeraddress and/or communitystring may also be invalid.After fixing one of the aboveproblems, delete the physicalprinter and recreate it. If theproblem persists, contacttechnical support.

8022-374 "Xerox Supervisor:An SNMPcommunication errorhas occurred inprinter <printeraddress> with errorcode: <error code>."

The Xerox supervisor onSNMP was unable tocommunicate with theprinter device. Either thephysical printer is notenabled or the printer-stateof the printer has changedto “timed-out”.

Either therequest toenable thephysicalprinter is notprocessedor the printerstate of thephysicalprinter is“timed-out”.

Check to see if the physicalprinter is running. The printeraddress, community string, orprint device may also beinvalid. After fixing one of theabove problems, reset thephysical printer. If theproblem persists, contacttechnical support.

8022-375 "Xerox Supervisor:Unable to retrieve themessage string<function name>."

The Xerox supervisor wasunable to retrieve themessage string frommessage file.


Check to see if the messagefiles xrssnmp.dll orxrssnmp.cat are located in themessage directory. Ifnecessary, add the messagefiles to the directory. Thendelete the physical printer andrecreate it. If the problempersists, contact technicalsupport.

8022-376 "Xerox Supervisor:There are no valuesin the MIB Database<printer address>."

The Xerox supervisor wasunable to retrieve a valuefrom the physical printereven though the SNMPagent on the deviceseemed to be working. Thephysical printer state mayhave changed to “timed-out”.


Reset the printer. If theproblem persists, contacttechnical support.

TROUBLESHOOTING


Reference supervisor errors

The following paragraphs discuss how the reference supervisorhandles 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, itsends a job-completed event to the spooler. The supervisor alsosets values into the printer attributes printer-state and printer-problem-message and the job attributes job-state-reasons andjob-state-message .

The following table lists five conditions that the reference supervisorcan detect and how it sets the relevant attributes. Note that theseconditions always result in the spooler setting current-job-state toone of the following states:

� retained for later resubmission; user intervention is required.

� pending ; the supervisor automatically submits the job to thesame physical printer when the condition is corrected

Table 21-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 cannotbe 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 physicaldevice after successfully starting the job on the printer:

� job-state-reasons: completed-with-errors

� job-state-message: the message provided by the communicationsbackend


TROUBLESHOOTING


Table 21-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 internalinterfaces 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) andprovides additional information. The assumption is that a very serious erroroccurred, and the reliability of the supervisor is suspect.

The supervisor disables the printer. Operator intervention is required to repairthe condition and enable the physical printer. Enabling the printer causes thesupervisor to clear the printer-problem-message .

4. Printer access error The job ends because the supervisor detected a "fatal" communicationsconfiguration 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 communicationsbackend

� job-state-message: the message provided by the communicationsbackend

� current-job-state: pending

The supervisor also logs this situation to the system log (see Section 3.5) andprovides additional information. Again, note that this situation causes thesupervisor to disable the printer. Operator intervention is required to repair thecondition and enable the physical printer.

5. Job completion error If the job ends because of an unexpected error with the physical device, but theerror occurs after all the document data has been sent to the printer and thesupervisor is "completing" the job (including printing a job end page):

� job-state-reasons: completed-with-warnings

� job-state-message: message from the communications backend


TROUBLESHOOTING


Stall monitoring

The reference supervisor detects and reports unexpected inactivity inthe input/output to/from the printer while printing a job. This stalledcondition 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, whenputting a fresh supply of paper in the printer.

During the normal processing of a job, each time the supervisorsends data response timer is in effect restarted. At some pointduring job processing if a printer fails to respond to an operationwithin the amount of time specified by the printer attribute printer-timeout-period, a printer-state-change event is reported with theprinter-state attribute set to the value timed-out.

When the printer again starts responding, the printer response timeris in effect restarted and a printer-state-change event is reported withthe printer-state attribute returned with the value set to reflect thecurrent state of the printer, typically printing .

The stall monitor timeout value, printer-timeout-period , isexpressed in seconds. Although that attribute does not have adefault value, the reference supervisor uses 300 seconds if no valuehas been specified. If an administrator enters 0 for the attributevalue, then the supervisor does not monitor I/O activity on the printer.

An administrator can modify the value of printer-timeout-period ona 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 needsattention (e.g. the printer has run out of paper); it reports a state-changed-printer event and sets the value of the printer-stateattribute to needs-attention . In addition, the supervisor sets theprinter attribute printer-problem-message to contain additionalinformation, if any.

Note : Notification for the event warning-resource-needs-attention isnot being raised. When the printer runs out of paper while a job isprinting, the printer-state is set to “needs-attention” but notification isnot raised.

TROUBLESHOOTING


Non-obvious behavior

This section lists reference supervisor behavior that may not beobvious.

1. Host connection to printer occurs not before print job submission.The PrintXchange supervisor deliberately does not attempt tomake a connection with physical printer devices upon supervisorstartup. The problems associated with attempting suchconnections are numerous and undesirable. The supervisormakes contact with physical printers ONLY upon printing printjobs. This convention helps assure that system startups proceednormally regardless of whether physical printer devices areconnected, disconnected, powered-up, powered-down, ready,off-line, etc.

2. Printer-models-supportedThe PrintXchange supervisor does not maintain a printer-models-supported list. Administrators specify a printer attributes file uponcreating each physical printer object. The attributes file specifiesa printer model name for that physical printer, but those attributesmust be specified for each physical printer, even if they are of thesame model.

3. Document Data Overrides Job and Document AttributesMany document files produced by popular applications containdevice-specific command sequences for selecting fonts, trays,and other options. Documents that contain such commandsequences will cause one of the following to happen:

� Document prints, but it uses fonts, trays, and optionsspecified in the document, rather than job or documentattributes 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 theprinter does not supply or support. An error results at theprinter that might or might not be reported back to the host,depending on the printer's capabilities and connectionmethod/level.

4. The PrintXchange supervisor does not remove or redefineprinter-option command sequences that exist in document data.Users need to be forewarned about such documents, and mayneed instruction on how to create printer-independentdocuments.

Exit status

Server exit status

When a server exits, it always returns an exit status. The followingtable lists all the different exit statuses and a brief description ofeach. The exit status values are used as a coarse-grained guide towhy the server exited. They are beneficial primarily in the casewhere an error message cannot be delivered for some reason.Ordinarily, a user will be more concerned with the actual errormessage delivered than the exit status of the server.

TROUBLESHOOTING


Table 21-7. Server exit status

Exit Status Description

0 Normal server termination via a shutdown request or aSIGTERM 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 isrunning.

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 configurationattribute.

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 parameterspassed to it. (NT version only)

99 Server could not register with the Service Control Manager.

TROUBLESHOOTING


Database utilities exit status

The exit status values are used as a coarse-grained guide to why theutility exited. They are beneficial primarily in the case where an errormessage cannot be delivered for some reason. Ordinarily, a user willbe more concerned with the actual error message than the exit statusof the utility.

In the following table, the error statuses are the same for all databaseutilities (pdmakedb, pdmoddb, pdshowdb) unless the descriptionnames a specific utility.

Table 21-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 alreadyexists.

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 pathname was too long.

12 The pdmakedb or pdmoddb utility encountered some error while trying tovalidate user supplied attributes.

13 A utility encountered an error while trying to display the attributes on the serverobject

TROUBLESHOOTING


Crash recovery

Crash refers to the condition where any component of thePrintXchange print system has become inoperable such that thecomponent:

� Is no longer capable of carrying out its function or responding toexternal requests

� Needs to be restarted

Crash recovery refers to a series of actions taken by thePrintXchange print system in returning the system to a functional andconsistent state with no or minimal data loss.

Server startup

As the spooler and supervisor are starting up from a crash or anormal shutdown, they go through a series of initialization andrecovery actions to get the system back to a functional andconsistent state. The state of the server upon completion of theseactions will be the same as the state at shutdown, or a state as closeas 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 theserver created and server started (if the -F switch is set there is alsonotification for server initialized and server registered).

Physical printer state As part of the startup, the spooler and its associated supervisor(s) gothrough a process of resynchronization. During this process, thesupervisor puts the physical printers associated with a queue into theunknown state. Once resynchronization is established, the supervisorputs 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 spoolerattribute values to reflect the crash. That is, physical printersassociated with the crashed supervisor may appear to be availableeven though they are not.

TROUBLESHOOTING


Database recovery

In very rare cases, the persistent object database used by aPrintXchange server may become corrupt. This is often caused byan unexpected system crash due to kernel crash or power failure.The database corruption should not happen when the server is shutdown normally.

If the server is restarted after a crash, the server automaticallyperforms a database integrity check to see if the database hasbecome damaged. The database integrity check goes through theentire database to see if there is any evidence of damaged datawithin the database.

The user may also force the database integrity check at startup evenafter 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 issomehow corrupt. For example, if the server continues to crashwithout any indication, the user may want to force the databaseintegrity check during restart. Although the -c switch can be used ateach startup, the user should be aware that the database integritycheck 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 serverfirst copies the corrupt database to the object database /backupdirectory. The server then creates a clean new database in theobject database directory and the good data is copied from thecorrupt database into the new database.

The server logs information on any repairs it makes into the sysloglog file. This enables the system administrator to see which objectsand attributes required repair and to check that the data is still valid.

It should be noted that even after the database has been repaired bythe server, the resultant database may still have corrupt data or lossof data. In order to prevent start up of the server with the corruptdatabase, the server discontinues its startup and exit if it had torepair the database at all. In such cases the server exits with thefollowing message to the console:

pdsplr: corrupt object database has been recovered. Toacknowledge, please restart using the following command line:pdsplr -a -F server _name.

All subsequent startups fail until the user adds the -a switch in thecommand line. This -a switch forces the server to restart so that thesystem administrator can check the attributes of server objects to seeif the data is correct. After the -a switch is given, a subsequentstartup succeeds without the switch until the database becomescorrupt again.

TROUBLESHOOTING


Job and document recovery

PrintXchange, in general, does not lose the job once the job hasbeen fully received by the spooler. However, if a crash occurs to acomponent within PrintXchange, certain actions take placedepending on the processing occurring at the time of the crash. Thefollowing 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 fullyreceived by the spooler at the time of a spooler crash.

A job is considered fully received by the spooler only if the job isproperly closed, and if the spooler has retrieved all of thedocument data. That is, the job’s current-job-state is not in thepre-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 itssubsequent 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, theremay be no record of the job upon crash recovery by the spooler.

� The spooler does not process those jobs whose document dataincludes a partially retrieved document.

This case is possible with transfer-method value socket wherethe spooler retrieves the document data asynchronously. In thiscase, 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 crashesduring submission of the job and the document data is completefor each job.

This happens if some of the documents have been received bythe spooler and all of the document data for those existingdocuments has been retrieved. If the job is still in the pre-processing state or the attribute job-submission-complete isstill false by the 20-minute time-out period, the spooler puts thejob in the held state with job-state-reasons of submission-interrupted and job-hold-set . The user can release the job forprocessing by setting the job-hold attribute to false .

TROUBLESHOOTING


Spooler or supervisor crash during processing or printing

In this situation:

If the supervisor is controlling a printer, the supervisor returns the jobto the spooler upon restart after a crash of a supervisor or a spooler.During the recovery process, the job (current-job-state ) maytemporarily be in the unknown state.

The administrator has an option of controlling whether such jobsreturned by the supervisor should be put into the held or pendingstate. This is achieved through the use of a logical printer or spoolerattribute called hold-jobs-interrupted-by-printer-failure .

If the value of hold-jobs-interrupted-by-printer-failure is true orunspecified, jobs returned by the supervisor due to crashes are putinto the held state. In this case, the job-state-reasons attributecontains 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 isput into the pending state and is rescheduled for processing. Thejob-state-reasons attribute is empty in this case.

The spooler uses the hold-jobs-interrupted-by-printer-failureattribute from the physical printer object if the attribute is specifiedthere. Otherwise the spooler uses the attribute from the serverobject.

Each time the supervisor returns the job due to a crash of thesupervisor or a spooler, a read-only attribute called job-fault-countis incremented. The administrator can control how many times thejob can be retried through the use of a server configuration attributecalled 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 thevalue of hold-jobs-interrupted-by-printer-failure .

When the job is put into the held state, job-state-reasons includesjob-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 .

TROUBLESHOOTING


Job-state-reasons and attributes associated with crash recovery

Table 21-9 lists the job-state-reasons associated with crashrecovery of the job.

Table 21-10 lists the attributes associated with crash recovery of thejob.

Table 21-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, thespooler puts the job into the held state and adds job-hold-set tojob-state-reasons .

� If the spooler cannot retrieve any of the document data, then itputs 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 thejob processing or printing was interrupted by failure of the server orthe printer controlled by the supervisor.

The job will be in unknown state when this job-state-reasons isset. The spooler eventually put the job into held or pending statedepending 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 returnedby the supervisor due to spooler or supervisor crash and that thejob is put into the held state.

max-job-fault-count-exceeded A job-state-reasons that indicates that the job has been faultedand returned by the supervisor several times and that the job-fault-count exceeded the cfg-max-job-fault-count . The job isautomatically put onto held state regardless of the hold-jobs-interrupted-by-printer -failure attribute. This job-state-reasonsvalue is used in conjunction with job-interrupted-by-printer-failure .

TROUBLESHOOTING


Table 21-10. Attributes associated with job crashrecovery

Attributes Object Comments

job-fault-count Job An attribute of the job object indicating the number of times thejob processing or printing was interrupted by the server due toserver or printer failure.

This attribute is a descriptive attribute that is settable only bythe spooler. The spooler resets the attribute to zero when thejob is resubmitted while at retained state. This attribute isincluded in the default profile for the accounting record.

cfg-max-job-fault-count Spooler This server object configuration attribute specifies themaximum allowable number of times the job can be faulted.

If the job processing or printing was faulted due to server orprinter failure, and the job-fault-count exceeds this number,the job is automatically put into held state regardless of thehold-jobs-interrupted-by-printer-failure attribute.

This is a prescriptive attribute that is settable by users. If theattribute is unspecified, then the spooler puts the job into theheld or pending state depending on the value of the hold-jobs-interrupted-by-printer-failure attribute.

default-job-completion-period

Spooler This server object configuration attribute specifies the minimumperiod of time the server keeps the job in the completed state.

This is a prescriptive attribute that is settable by users. If theattribute is unspecified, then the spooler deletes the jobimmediately upon transitioning it to the completed state.

Xerox supervisor crash recovery

To conform with PSIS, the DP recovers each printer and the jobssubmitted to that printer, one printer at a time. The DP creates andregisters the printer, and then queries for the job status to collect thelatest information of those jobs submitted to that printer. Thecurrent-job-state would be printing with job-state-reasons beingcascaded . The DP then updates the FE accordingly.

The Xerox supervisor supports only job-level-recovery, and it doesnot maintain any persistency. Thus is if the server crashes during jobsubmission, the FE will resubmit the whole job.

TROUBLESHOOTING


LAN Manager inbound gateway recovery

If the operating system crashes or shuts down while processing jobsexist, the LM-IBG recovers these jobs at the next startup. The LM-IBG:

� Writes a message (using the PrintXchange logging library) anddeletes the job when the error originates in the job itself and thejob could not be printed if it were resubmitted.

� Resubmits the job when the error originates in the system andthe 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) isConnecting . When situation improves on retrying, the job statuschanges to Printing .

LPR inbound gateway on NT recovery

When the LPR inbound gateway starts, incomplete jobs are in thespool directory (as specified in installation). The gateway tries tosubmit the remaining jobs. If control files corresponding to the datafiles remain in the spool directory, the job should be submitted.Otherwise, the spooler deletes the control files or data files becauseof incomplete jobs.

Accounting

In rare cases, an accounting record for a job may be duplicated dueto a crash of a spooler. Such duplicate accounting records resultingfrom a crash may be identified by examining the started-printing-time and/or the completion-time ; the value for these attributes in theduplicate records should be identical.

In contrast, each duplicate or multiple accounting record for a job dueto resubmission has different values for started-printing-time andcompletion-time .

Notification

In rare cases, event notification may be duplicated due to a crash ofthe 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 acrash if the appropriate modifications are made to CDE initializationfiles. Refer to CDE documentation for details.

TROUBLESHOOTING


Operations

Table 21-11 describes the result of an operation if the server (spoolerand/or supervisor) handling the operation crashes during theoperation. Note: In rare cases, the operation may have beencompleted by the server, but the client may not have received thereturn from the operation. As a result, users may be notified that theoperation did not complete when in fact the operation was completedby the server.

Table 21-11. Operation results on crash recovery

Operation Object Result

pdclean SpoolerQueue

Upon subsequent restart of the spooler, the spooler does not continue withthe operation. All jobs cancelled prior to a spooler crash are not restored,and remain cancelled.

pdcreate All (except spooler,supervisor)

All changes are rolled back to the state prior to the operation. That is, theobject is not created.

pddelete SpoolerSupervisor

Physical printerLogical printerQueueInitial-value-documentInitial-value-job

JobDocument

The operation continues upon subsequent restart.

All changes are rolled back to the state prior to the operation. That is, theobject will still exist.

Depending on the progress made by the server, the operation either rollsback or continues to completion upon subsequent restart.

pddisable SpoolerSupervisorPhysical printerLogical printerQueue

All changes are rolled back to the state prior to the operation. That is, theobject remains enabled if it was enabled prior to the operation.

pdenable SpoolerSupervisorPhysical printerLogical printerQueue

All changes are rolled back to the state prior to the operation. That is, theobject remains disabled if it was disabled prior to the operation.

pdls All N/A. No changes as a result of the operation. Note: Continuation context isstill valid upon restart.

pdmod Job All changes are rolled back to the state prior to the operation.

pdpause SpoolerQueue

Physical printer

All changes are rolled back to the state prior to the operation.


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 isstill valid upon restart.

TROUBLESHOOTING


Table 21-11. Operation results on crash recovery

Operation Object Result

pdresubmit SpoolerQueue

Job

Resubmitting jobs from server or queue: Upon subsequent restart of thespooler, the spooler does not continue with the operation. All jobsresubmitted prior to a spooler crash remain resubmitted to the new printer,and they are not restored to the original printer.

Resubmitting single job: The job is restored in the original state. The job isnot resubmitted.

pdresume SpoolerQueue

Physical printer



pdrm Job Depending on the progress made by the server, the operation either rollsback or continues to completion upon subsequent restart.

pdset All All changes are rolled back to the state prior to the operation.

pdshutdown SpoolerSupervisor


PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX A-1

A. Printers data sheets

This appendix includes a printer data sheet of each printer that can beenabled for PrintXchange supervisors.

Supported output devices

Table A-1 lists the printers and other output devices that PrintXchangesupports. 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 -- -- --

PRINTER DATA SHEETS

A-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX



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

PRINTER DATA SHEETS




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 Centre20



Xerox DocuPrint 180 NPS XS -- -- -- x -- x -- Proprietaryjob status

Xerox DocuPrint 4050NPS

XS -- -- -- x -- x -- Proprietaryjob status



Xerox DocuPrint 4517 RS/XS x x x x -- --







Xerox DocuPrint N17 RS/XS x x x x -- -- x




Xerox DocuTech 6135 XS -- -- -- x -- x -- Proprietaryjob andprinterstatus

PRINTER DATA SHEETS




Xerox DocuTech 6180 XS -- -- -- x -- x -- Proprietaryjob andprinterstatus

Xerox DP96

Xerox LaserPress 4150PS II

RS x x --

Xerox LaserPress 4161PS II

RS x x --

Xerox N24

Network Print Server boxes

Axis - PrintPoint 560/100

HP Jetdirect EX Plus3Print Server (J2590a orJ2593A)

Lantronix EPS4P1-01

Lexmark - MarkNet Xle -Model 202

Milan - MIL3111FTX

Netque Pro2

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

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

PRINTER DATA SHEETS



� Level 2 PS

� lpr

� PCL6


� 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

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 N17

� Level 2 PS

� lpr

� PCL5


� Level 2 PS

� lpr

� PCL5


� Level 2 PS

� lpr

� PCL5


� Level 2 PS

� lpr

� PCL5

� Xerox DocuTech 6135 lpr

� Xerox DocuTech 6180 lpr

PRINTER DATA SHEETS


Data sheets are currently being prepared for the following additionalprinters:

� HP 6L

� HP 4000

� HP LaserJet5si Mopier



� 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 followingnetwork 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

PRINTER DATA SHEETS


Printer Data Sheet: Generic lp

Printer attribute file name:

PXC_Generic_lp.paf

printer-model:

1179 lp printer

maximum-printer-speed:

n/a

printer-tcpip-port-number:

n/a

printer-connection-method:

1179-job-submission

printer-connection-level:

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:

PRINTER DATA SHEETS


Printer Data Sheet: Generic lpr


PXC_Generic_lpr.paf

printer-model:

1179 lpr printer


n/a


n/a


1179-job-submission


n/a








native-document-formats-ready = PostScript PCL




other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Generic lpr / snmp


PXC_Generic_lpr_snmp.paf

printer-model:

1179 lpr and 1759 snmp printer


n/a


n/a


1179-job-submission

snmp-device-status


n/a

n/a












other attributes:


device-query-interval = 00:00:10



PRINTER DATA SHEETS


Printer Data Sheet: Generic PostScript


PXC_Generic_PS.paf

printer-model:

PostScript Printer


n/a


See Note 1.


ip- socketparallelserial


121


document-formats-supported = PostScript simple-text

sides-supported = 1 [2]


job-sheets-supported = none job-copy-start job-copy-wrap



document-formats-ready = PostScript simple-text

native-document-formats-ready = PostScript

sides-ready = 1[2]


job-sheets-ready = none job-copy-start job-copy-wrap


other attributes:



1. Set the tcpip port number with the printer-address attribute.

Example: pdset -x “printer-address=HostName:Port”

PRINTER DATA SHEETS


Printer Data Sheet: Generic PCL


PXC_Generic_PCL.paf

printer-model:

PCL Printer


n/a


See Note 1.


ip- socketparallelserial


121


document-formats-supported = PCL simple-text






document-formats-ready = PCL simple-text

native-document-formats-ready = PCL

sides-ready = 1[2]




other attributes:



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 printerattribute 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

PRINTER DATA SHEETS


Printer Data Sheet: Digital DEClaser 2100 PCL5


Digital_DEClaser2100_PCL5.paf

printer-model:

LN05 DEClaser 2100


5 ppm


n/a


parallelserial


23



input-trays-supported = main

output-bins-supported = top

sides-supported = 1







input-trays-ready = main

output-bins-ready = top

sides-ready = 1




other attributes:



PRINTER DATA SHEETS


Printer Data Sheet: Digital DEClaser 2150 Level 1 PS


Digital_DEClaser2150_Level1PS.paf

printer-model:

LN05 DEClaser 2150


5 ppm


n/a


parallelserial


23





sides-supported = 1









sides-ready = 1




other attributes:



PRINTER DATA SHEETS





printer-model:

DEC Laser3500


12 ppm


10001


ip-socketparallelserial


121



input-trays-supported = top main manual [bottom] [large-capacity] [envelope]


sides-supported = 1







input-trays-ready = top main manual [bottom] [large-capacity] [envelope]


sides-ready = 1




other attributes:



1. The multi-purpose feeder is the “top” tray.

2. Configure the network card using the printer Control Panel.


Example: pdset -x “input-trays-supported+=large-capacity” PrinterName

PRINTER DATA SHEETS





printer-model:

DEC Laser3500


12 ppm


10001




121



input-trays-supported = top main manual [bottom] [large-capacity] [envelope]


sides-supported = 1







input-trays-ready = top main manual [bottom] [large-capacity] [envelope]


sides-ready = 1




other attributes:







PRINTER DATA SHEETS





printer-model:

DEC Laser5100


8 ppm


10001




121



input-trays-supported = top main manual [large-capacity] [envelope]


sides-supported = 1







input-trays-ready = top main manual [large-capacity] [envelope]


sides-ready = 1




other attributes:




2. Attribute values in square brackets are printer options. These values are not included in theprinter attribute file. If the printer option is installed, add the value to the attribute with pdset orduring pdcreate.


PRINTER DATA SHEETS


Printer Data Sheet: Digital LA75


Digital_LA75.paf

printer-model:

Digital LA75 plus


60 cps


n/a


parallel


2


document-formats-supported = DEC-PPL simple-text

input-trays-supported = “”

output-bins-supported = “”

sides supported = 1



document-formats-ready = DEC-PPL simple-text

native-document-formats-ready = DEC-PPL

input-trays-ready = “”

output-bins-ready = “”

sides-ready = 1


other attributes:



1. The LA75 is a pin-feed matrix printer. Input trays and output bins have no meaning.

PRINTER DATA SHEETS


Printer Data Sheet: Digital LG08


Digital_LG08.paf

printer-model:

Digital LG08


600 lpm


n/a


parallelserial


21


document-formats-supported = DEC-PPL simple-text

input-trays-supported = “”

output-bins-supported = “”

sides supported = 1



document-formats-ready = DEC-PPL simple-text

native-document-formats-ready = DEC-PPL

input-trays-ready = “”

output-bins-ready = “”

sides-ready = 1


other attributes:



1. The LG08 is a pin-feed line printer. Input trays and output bins have no meaning.

PRINTER DATA SHEETS


Printer Data Sheet: Digital LN17 Level 2 PS


Digital_LN17_Level2PS.paf

printer-model:

Digital LN17


17 ppm


2501




123



input-trays-supported = top side [bottom] [large-capacity] [envelope]

output-bins-supported = top [large]








input-trays-ready = top side [bottom] [large-capacity] [envelope]

output-bins-ready = top [large]

sides-ready = 1 [2]




other attributes:



1. The multi-purpose feeder is the “side” tray

2. The output catch tray is the “large” output tray.



PRINTER DATA SHEETS


Printer Data Sheet: Digital LN17 lpr


Digital_LN17_lpr.paf

printer-model:

Digital LN17


17 ppm


n/a


1179-job-submission


n/a










job-sheets-read y= none job-copy-start job-copy-wrap job-copy-end


other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Digital LN17 PCL5


Digital_LN17_PCL5.paf

printer-model:

Digital LN17


17 ppm


2501




121



input-trays-supported = top side [bottom] [large-capacity] [envelope]



plexes-supported = simplex







input-trays-ready = top side [bottom] [large-capacity] [envelope]


sides-ready = 1 [2]




other attributes:



1. The multi-purpose feeder is the “side” tray

2. The output catch tray is the “large” output tray.



PRINTER DATA SHEETS


Printer Data Sheet: Digital PrintServer 17 Level 2 PS


Digital_PrintServer17_Level2PS.paf

printer-model:

Digital PrintServer 17


17 ppm


n/a


digital-printserver


5



input-trays-supported = top bottom

output-bins-supported = top side








input-trays-ready = top bottom

output-bins-ready = top side

sides-ready = 1 [2]




other attributes:



1. Common Printer Access Protocol


Example: pdset -x “sides-supported+=2” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: Digital PrintServer 17 lpr


Digital_PrintServer17_lpr.paf

printer-model:



17 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Digital PrintServer 17 PCL5


Digital_PrintServer17_PCL5.paf

printer-model:



17 ppm


n/a


digital-printserver


5



input-trays-supported = top bottom









input-trays-ready = top bottom


sides-ready = 1 [2]




other attributes:



1. Common Printer Access Protocol


Example: pdset -x sides-supported+=2 PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: Digital ScriptPrinter Level 1 PS


Digital_LN03R_Level1PS.paf

printer-model:

LN03R ScriptPrinter


5 ppm


n/a


serial


1





sides-supported = 1









sides-ready = 1




other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: HP Color LaserJet Level 2 PS


HP_ColorLaserJet_Level2PS.paf

printer-model:

HP Color LaserJet


10 ppm


9100




123



input-trays-supported = top [side] [manual]


sides-supported = 1

print-colour-types-supported = black-and-white full-colour






input-trays-ready = top [side] [manual]


sides-ready = 1

print-colour-types-ready = black-and-white full-colour



other attributes:



1. The rear feeder is the “side” tray


Example: pdset -x “input-trays-supported+=side” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: HP Color LaserJet lpr


HP_ColorLaserJet_lpr.paf

printer-model:

HP Color LaserJet


10 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: HP Color LaserJet PCL5


HP_ColorLaserJet_PCL5.paf

printer-model:

HP Color LaserJet


10 ppm


9100




121



input-trays-supported = top [side] [manual]


sides-supported = 1







input-trays-ready = top [side] [manual]


sides-ready = 1




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: HP DeskJet 1600CM Level 2 PS

Printer attribute file name(s):

HP_DeskJet1600CM_Level2PS.paf

printer-model(s):

HP DeskJet 1600CM


8 ppm


9100




423



input-trays-supported = top manual [large-capacity]


sides-supported = 1







input-trays-ready = top manual [large-capacity]


sides-ready = 1




other attributes:



1. Attribute values in square brackets are printer options. These values are not included in the printerattribute file. If the printer option is installed, add the value to the attribute with pdset or during pdcreate


PRINTER DATA SHEETS


Printer Data Sheet: HP DeskJet 1600CM lpr


HP_DeskJet1600CM_lpr.paf

printer-model(s):

HP DeskJet 1600CM


8 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: HP DeskJet 1600CM PCL5


HP_DeskJet1600CM_PCL5.paf

printer-model(s):

HP DeskJet 1600CM


8 ppm


9100




121



input-trays-supported = top manual [large-capacity]


sides-supported = 1







input-trays-ready = top manual [large-capacity]


sides-ready = 1




other attributes:





PRINTER DATA SHEETS


Printer Data Sheet: HP DesignJet 755CM Level 2 PS


HP_DesignJet755CM_Level2PS.paf

printer-model(s):

HP DesignJet 755CM


n/a


9100




121



input-trays-supported = top


sides-supported = 1





input-trays-ready = top


sides-ready = 1





PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 4plus Level 2 PS


HP_LaserJet4plus_Level2PS.paf

printer-model:

HP LaserJet 4plus, 4Mplus


12 ppm


9100




423



input-trays-supported = top main manual [bottom] [envelope]









input-trays-ready = top main manual [bottom] [envelope]


sides-ready = 1 [2]




other attributes:





Example: pdset -x “input-trays-supported+=bottom” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 4plus lpr


HP_LaserJet4plus_lpr.paf

printer-model:



12 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 4plus PCL5


HP_LaserJet4plus_PCL5.paf

printer-model:



12 ppm


9100




121



input-trays-supported = top main manual [bottom] [envelope]









input-trays-ready = top main manual [bottom] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 4Si Level 2 PS


HP_LaserJet4Si_Level2PS.paf

printer-model:

HP LaserJet 4Si , 4Si MX


17 ppm


9100




423



input-trays-supported = top bottom manual [envelope]


sides-supported = 1 2







input-trays-ready = top bottom manual [envelope]


sides-ready = 1 2







2. If output stacker is installed, it is “side” output bin.

3. If high-capacity paper feeder is installed, it is “bottom” input tray.


Example: pdset -x input-trays-supported+=envelope PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 4Si PCL5


HP_LaserJet4Si_PCL5.paf

printer-model:

HP LaserJet 4Si, 4Si MX


17 ppm


9100




121














sides-ready = 1 2







2. If output stacker is installed, it is “side” output bin.

3. If high-capacity paper feeder is installed, it is “bottom” input tray.


Example: pdset -x input-trays-supported+=envelope PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 5Si Level 2 PS


HP_LaserJet5Si_Level2PS.paf

printer-model:



24 ppm


9100




423



input-trays-supported = top bottom side manual [large-capacity] [envelope]









input-trays-ready = top bottom side manual [large-capacity] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 5Si lpr


HP_LaserJet5Si_lpr.paf

printer-model:



24 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet 5Si PCL5


HP_LaserJet5Si_PCL5.paf

printer-model:



24 ppm


9100




121














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet IIISi Level 1 PS / Level 2 PS


HP_LaserJetIIISi_Level1PS.paf

HP_LaserJetIIISi_Level2PS.paf

printer-model:

HP LaserJet IIISi


17 ppm


9100




423














sides-ready = 1 [2]








Example: pdset -x “input-trays-supported+=envelope” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: HP LaserJet IIISi PCL5


HP_LaserJetIIISi_PCL5.paf

printer-model:

HP LaserJet IIISi


17 ppm


9100




121














sides-ready = 1 [2]








Example: pdset -x “input-trays-supported+=envelope” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: Lexmark 4039 10plus Level 2 PS


Lexmark_4039plus_Level2PS.paf

printer-model:

Lexmark 4039 10plus


10 ppm


9100




423



input-trays-supported = top bottom manual [side] [large-capacity] [envelope]









input-trays-ready = top bottom manual [side] [large-capacity] [envelope]


sides-ready = 1 [2]









PRINTER DATA SHEETS


Printer Data Sheet: Lexmark 4039 10plus PCL5


Lexmark_4039plus_PCL5.paf

printer-model:

Lexmark 4039 10plus


10 ppm


9100




121














sides-ready = 1 [2]









PRINTER DATA SHEETS


Printer Data Sheet: Lexmark 4079 plus Level 2 PS


Lexmark_4079plus_Level2PS.paf

printer-model:

Lexmark 4079 plus


10 ppm


n/a


parallelserial


23



input-trays-supported = top


sides-supported = 1







input-trays-ready = top


sides-ready = 1






1. Color ink jet

PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra C Level 2 PS


Lexmark_OptraC_Level2PS.paf

printer-model:

Lexmark Optra C


12 ppm


9100




423



input-trays-supported = top side [bottom]


sides-supported = 1







input-trays-ready = top side [bottom]


sides-ready = 1




other attributes:



1. The multi-purpose feeder is the “side” tray.

2. The side output tray is manually activated.




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra C lpr


Lexmark_OptraC_lpr.paf

printer-model:

Lexmark Optra C


12 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra C PCL5


Lexmark_OptraC_PCL5.paf

printer-model:

Lexmark Optra C


12 ppm


9100




121



input-trays-supported = top side [bottom]


sides-supported = 1







input-trays-ready = top side [bottom]


sides-ready = 1




other attributes:



1. The multi-purpose feeder is the “side” tray.

2. The side output tray is manually activated.




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra E PCL5


Lexmark_OptraE_PCL5.paf

printer-model:

Lexmark Optra E


6 ppm


n/a


parallelserial


21



input-trays-supported = top manual [bottom]


sides-supported = 1







input-trays-ready = top manual [bottom]


sides-ready = 1




other attributes:



1. PCL5 only.



PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lx Level 2 PS


Lexmark_OptraLx_Level2PS.paf

printer-model:

Lexmark Optra Lx


16 ppm


9100




423



input-trays-supported = top manual [side] [large-capacity] [envelope]









input-trays-ready = top manual [side] [large-capacity] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lx lpr


Lexmark_OptraLx_lpr.paf

printer-model:

Lexmark Optra Lx


16 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lx PCL5


Lexmark_OptraLx_PCL5.paf

printer-model:

Lexmark Optra Lx


16 ppm


9100




121



input-trays-supported = top manual [side] [large-capacity] [envelope]









input-trays-ready = top manual [side] [large-capacity] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lxi+ Level 2 PS


Lexmark_OptraLxiPlus_Level2PS.paf

printer-model:

Lexmark Optra Lxi+


16 ppm


9100




423














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lxi+ lpr


Lexmark_OptraLxiPlus_lpr.paf

printer-model:

Lexmark Optra Lxi+


16 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Lxi+ PCL5


Lexmark_OptraLxiPlus_PCL5.paf

printer-model:

Lexmark Optra Lxi+


16 ppm


9100




121














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra N Level 2 PS


Lexmark_OptraN_Level2PS.paf

printer-model:

Lexmark Optra N


24 ppm


9100




423














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra N lpr


Lexmark_OptraN_lpr.paf

printer-model:

Lexmark Optra N


24 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra N PCL5


Lexmark_OptraN_PCL5.paf

printer-model:

Lexmark Optra N


24 ppm


9100




121














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Rt+ Level 2 PS


Lexmark_OptraRtPlus_Level2PS.paf

printer-model:

Lexmark Optra Rt+


16 ppm


9100




423



input-trays-supported = top bottom manual [large-capacity] [envelope] [side]









input-trays-ready = top bottom manual [large-capacity] [envelope] [side]


sides-ready = 1 [2]




other attributes:



1. The rear feeder is the “side” tray.

2. The front output tray is manually activated.




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Rt+ lpr


Lexmark_OptraRtPlus_lpr.paf

printer-model:

Lexmark Optra Rt+


16 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra Rt+ PCL5


Lexmark_OptraRtPlus_PCL5.paf

printer-model:

Lexmark Optra Rt+


16 ppm


9100




121



input-trays-supported = top bottom manual [large-capacity] [envelope] [side]









input-trays-ready = top bottom manual [large-capacity] [envelope] [side]


sides-ready = 1 [2]




other attributes:



1. The rear feeder is the “side” tray.





PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra S 1250 Level 2 PS


Lexmark_OptraS1250_Level2PS.paf

printer-model(s):

Lexmark Optra S 1250


12 ppm


9100




323



input-trays-supported = 1 manual [2] [3] [envelope]









input-trays-ready = 1 manual [2] [3] [envelope]


sides-ready = 1 [2]




other attributes:




Example: pdset -x default-input-tray+=“2 3” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra S 1250 lpr


Lexmark_OptraS1250_lpr.paf

printer-model(s):



12 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Lexmark Optra S 1250 PCL6


Lexmark_OptraS1250_PCL6.paf

printer-model(s):



12 ppm


9100




121



input-trays-supported = 1 manual [2] [3] [envelope]








native-document-formats-ready =PCL

input-trays-ready = 1 manual [2] [3] [envelope]


sides-ready = 1 [2]




other attributes:




Example: pdset -x default-input-tray+=bottom PrinterName

PRINTER DATA SHEETS





printer-model(s):



16 ppm


9100




323



input-trays-supported = 1 manual [2] [3] [4] [envelope]

output-bins-supported = top [stacker-1] [stacker-2]








input-trays-ready = 1 manual [2] [3] [4] [envelope]

output-bins-ready = top [stacker-1] [stacker-2]

sides-ready = 1 [2]




other attributes:




Example: pdset -x input-tray-supported+=“2 3 4” PrinterName

PRINTER DATA SHEETS





printer-model(s):



16 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS





printer-model(s):



16 ppm


9100




121



input-trays-supported = 1 manual [2] [3] [4] [envelope]

output-bins-supported = top [stacker-1] [stacker-2]








input-trays-ready = 1 manual [2] [3] [4] [envelope]

output-bins-ready = top [stacker-1] [stacker-2]

sides-ready = 1 [2]




other attributes:




Example: pdset -x input-tray-supported+=“2 3 4” PrinterName

PRINTER DATA SHEETS





printer-model(s):



24 ppm


9100




323



input-trays-supported = 1 2 3 manual [4] [5] [envelope]

output-bins-supported = top [stacker-1] [stacker-2] [stacker-3]








input-trays-ready = 1 2 3 manual [4] [5] [envelope]

output-bins-ready = top [stacker-1] [stacker-2] [stacker-3]

sides-ready = 1 [2]




other attributes:




Example: pdset -x output-bins-supported = “top stacker-1 stacker-2” PrinterName

PRINTER DATA SHEETS





printer-model(s):



24 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS





printer-model(s):



24 ppm


9100




121



input-trays-supported = 1 2 3 manual [4] [5] [envelope]

output-bins-supported = top [stacker-1] [stacker-2] [stacker-3]








input-trays-ready = 1 2 3 manual [4] [5] [envelope]

output-bins-ready = top [stacker-1] [stacker-2] [stacker-3]

sides-ready = 1 [2]




other attributes:




Example: pdset -x output-bins-supported = “top stacker-1 stacker-2” PrinterName

PRINTER DATA SHEETS


Printer Data Sheet: Sun SPARCprinter E Level 2 PS


SUN_SPARCprinterE_Level2PS.paf

printer-model:

Sun SPARCprinter E


12 ppm


9100




423



input-trays-supported = top manual [bottom] [envelope]









input-trays-ready = top manual [bottom] [envelope]


sides-ready = 1 [2]









PRINTER DATA SHEETS


Printer Data Sheet: Sun SPARCprinter E PCL5


SUN_SPARCprinterE_PCL5.paf

printer-model:

Sun SPARCprinter E


12 ppm


9100




121



input-trays-supported = top manual [bottom] [envelope]









input-trays-ready = top manual [bottom] [envelope]


sides-ready = 1 [2]









PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4215 MRP Level 2 PS


Xerox_4215_Level2PS.paf

printer-model:

Xerox 4215 MRP


15 ppm


2000




123



input-trays-supported = top bottom manual [large-capacity]


sides-supported = 1







input-trays-ready = top bottom manual [large-capacity]


sides-ready = 1




other attributes:




2. Configure the network card using rarp, then telnet <host> 2002.



PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4215 MRP lpr


Xerox_4215_lpr.paf

printer-model:

Xerox 4215 MRP


15 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4215 MRP PCL5


Xerox_4215_PCL5.paf

printer-model:

Xerox 4215 MRP


15 ppm


2000




121



input-trays-supported = top bottom manual [large-capacity]


sides-supported = 1







input-trays-ready = top bottom manual [large-capacity]


sides-ready = 1




other attributes:




2. Configure the network card using rarp, then telnet <host> 2002.



PRINTER DATA SHEETS





printer-model:

Xerox 4219 MRP


20 ppm


2000




123



input-trays-supported = top middle bottom manual


sides-supported = 1







input-trays-ready = top middle bottom manual


sides-ready = 1






1. Wait for “manual feed” display before inserting paper.

PRINTER DATA SHEETS




Xerox_4219_PCL5.paf

printer-model:

Xerox 4219 MRP


20 ppm


2000




121



input-trays-supported = top middle bottom manual


sides-supported = 1







input-trays-ready = top middle bottom manual


sides-ready = 1






1. Wait for “manual feed” display before inserting paper.

PRINTER DATA SHEETS





printer-model:

Xerox 4220 MRP


20 ppm


2000




121



input-trays-supported = 1 2 3 side [4]

output-bins-supported = top side [stacker-1]








input-trays-ready = 1 2 3 side [4]

output-bins-ready = top side [stacker-1]

sides-ready = 1 2




other attributes:




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”

PRINTER DATA SHEETS




Xerox_4220_lpr.paf

printer-model:

Xerox 4220 MRP


20 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS




Xerox_4220_PCL5.paf

printer-model:

Xerox 4220 MRP


20 ppm


2000




121



input-trays-supported = 1 2 3 side [4]









input-trays-ready = 1 2 3 side [4]


sides-ready = 1 2




other attributes:




Example: pdset -x “input-trays-supported+=main” PrinterName



PRINTER DATA SHEETS





printer-model:

Xerox 4230 MRP


30 ppm


2000




121



input-trays-supported = 1 2 3 4 side









input-trays-ready = 1 2 3 4 side


sides-ready = 1 2




other attributes:




Example: pdset -x output-bins-supported+=“top side stacker-1” PrinterName



PRINTER DATA SHEETS




Xerox_4230_lpr.paf

printer-model:

Xerox 4230 MRP


30 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS




Xerox_4230_PCL5.paf

printer-model:

Xerox 4230 MRP


30 ppm


2000




121



input-trays-supported = 1 2 3 4 side









input-trays-ready = 1 2 3 4 side


sides-ready = 1 2




other attributes:




Example: pdset -x output-bins-supported+=“top side stacker-1” PrinterName



PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4235 Level 1 PS



printer-model:

Xerox 4235


35 ppm


n/a


serial

parallel


3

2



input-trays-supported = top middle bottom large-capacity

output-bins-supported = top large


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




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 DATA SHEETS


Printer Data Sheet: Xerox 4235 PCL4


Xerox_4235_PCL4.paf

printer-model:

Xerox 4235


35 ppm


n/a


serial

parallel


1

2



input-trays-supported = top middle bottom large-capacity

output-bins-supported = top large


print-colour-types-supported=black-and-white






input-trays-ready = top middle bottom large-capacity

output-bins-ready = top large

sides-ready = 1 2

print-colour-types-ready=black-and-white



other attributes:




PRINTER DATA SHEETS




Xerox_4505_PCL5.paf

printer-model:

Xerox 4505


5 ppm


n/a


parallelserial


21



input-trays-supported = main [large-capacity]


sides-supported = 1







input-trays-ready = main [large-capacity]


sides-ready = 1






1. The 4510 emulates PCL5 only.


Example: pdset -x input-trays-supported+=large-capacity PrinterName

PRINTER DATA SHEETS




Xerox_4510_PCL5.paf

printer-model:

Xerox 4510


10 ppm


n/a


parallelserial


21





sides-supported = 1









sides-ready = 1






1. The 4510 emulates PCL5 only.

PRINTER DATA SHEETS





printer-model:

Xerox 4517


17 ppm


2501




123



input-trays-supported = top side [middle] [bottom] [envelope]









input-trays-ready = top side [middle] [bottom] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4517 lpr


Xerox_4517_lpr.paf

printer-model:

Xerox 4517


17 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS




Xerox_4517_PCL5.paf

printer-model:

Xerox 4517


17 ppm


2501




121



input-trays-supported = top side [middle] [bottom] [envelope]









input-trays-ready = top side [middle] [bottom] [envelope]


sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS





printer-model:

Xerox 4520


20 ppm


2501




121



input-trays-supported = top middle bottom manual [large-capacity] [envelope]


sides-supported = 1







input-trays-ready = top middle bottom manual [large-capacity] [envelope]


sides-ready = 1




other attributes:






PRINTER DATA SHEETS




Xerox_4520_lpr.paf

printer-model:

Xerox 4520


20 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS




Xerox_4520_PCL5.paf

printer-model:

Xerox 4520


20 ppm


2501




121



input-trays-supported = top middle bottom manual [large-capacity] [envelope]


sides-supported = 1







input-trays-ready = top middle bottom manual [large-capacity] [envelope]


sides-ready = 1




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4700 II Level 1 PS


Xerox_4700II_Level1PS.paf

printer-model:

Xerox 4700 II


30 ppm


n/a


serial

parallel


3

2



input-trays-supported = top bottom [large-capacity]

output-bins-supported = large

sides-supported = 1

print-colour-types-supported=black-and-white full-colour






input-trays-ready = top bottom [large-capacity]

output-bins-ready = large

sides-ready = 1

print-colour-types-ready=black-and-white full-colour



other attributes:





PRINTER DATA SHEETS


Printer Data Sheet: Xerox 4700 II PCL4


Xerox_4700II_PCL4.paf

printer-model:

Xerox 4700 II


30 ppm


n/a


serial

parallel


1

2



input-trays-supported = top bottom [large-capacity]

output-bins-supported = large

sides-supported = 1

print-colour-types-supported=black-and-white full-colour






input-trays-ready = top bottom [large-capacity]

output-bins-ready = large

sides-ready = 1

print-colour-types-ready=black-and-white full-colour



other attributes:





PRINTER DATA SHEETS




Xerox_4915_lpr.paf

printer-model:

Xerox 4915


12 ppm


n/a


1179-job-submission


n/a








other attributes:




PRINTER DATA SHEETS




Xerox_4925_lpr.paf

printer-model:

Xerox 4925


12 ppm


n/a


1179-job-submission


n/a








other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Xerox Document Centre 230 lpr


Xerox_DocumentCentre230_lpr.paf

printer-model:

Xerox Document Centre 230


30 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuPrint 180 NPS lpr


Xerox_DocuPrint180NPS_lpr.paf

printer-model:

Xerox DocuPrint 180 NPS


180 ppm


n/a


1179-job-submissionxpp-job-status1179-job-cancel


n/a


document-formats-supported = PostScript simple-text PCL Interpress


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



document-formats-ready = PostScript simple-text PCL Interpress

sides-ready = 1 2

media-ready = na-letter-white na-legal-white

finishings-ready = none [staple]


other attributes:

max-concurrent-job-processing=20

job-query-interval=00:01:00



1. Attribute values in square brackets are printer options. If the printer option is not installed, remove thesevalues 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 theattribute with the media values supported at each site.

3. Set the attribute media-ready to the media values currently loaded on the printer.

PRINTER DATA SHEETS





printer-model:



50 ppm


n/a




n/a














sides-ready = 1 2




other attributes:








PRINTER DATA SHEETS





printer-model:



92 ppm


n/a




n/a














sides-ready = 1 2




other attributes:








PRINTER DATA SHEETS





printer-model:



135 ppm


n/a




n/a














sides-ready = 1 2




other attributes:








PRINTER DATA SHEETS





printer-model:



50 ppm

printer-tcpip-port-number: n/a




n/a


document-formats-supported = PostScript simple-text PCL Interpresssides-supported = 1 2plexes-supported = simplex duplex tumblecontent-orientations-supported = portrait landscape reverse-portrait reverse-landscapehighlight-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown

blackhighlight-colour-rendering-algorithms-supported = automatic colourToHighlight colourTables presentation

pictorialhighlight-mapping-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet

brown blackmedia-supported = iso-a4-white na-letter-white na-legal-whitethickening-supported = entire-document bitmap-imagesfinishings-supported = none [staple]x-image-shift-range-supported = -432:432y-image-shift-range-supported = -364:364print-colour-types-supported = black-and-white highlight-colour


document-formats-ready = PostScript simple-text PCL Interpresssides-ready = 1 2highlight-colours-ready = black variable (printer dependent, only one other supported value)media-ready = na-letter-white na-legal-whitefinishings-ready = none [staple]print-colour-types-ready = black-and-white highlight-colour

other attributes:






2. The attribute media-supported is set to all the media values supported by this printer. Update theattribute with the media values supported at each site.


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).

PRINTER DATA SHEETS





printer-model:



92 ppm

printer-tcpip-port-number: n/a




n/a


document-formats-supported = PostScript simple-text PCL Interpresssides-supported = 1 2plexes-supported = simplex duplex tumblecontent-orientations-supported = portrait landscape reverse-portrait reverse-landscapehighlight-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet brown

blackhighlight-colour-rendering-algorithms-supported = automatic colourToHighlight colourTables presentation

pictorialhighlight-mapping-colours-supported = red blue green cyan magenta yellow cardinal royalblue ruby violet

brown blackmedia-supported = iso-a4-white na-letter-white na-legal-whitethickening-supported = entire-document bitmap-imagesfinishings-supported = none [staple]x-image-shift-range-supported = -432:432y-image-shift-range-supported = -364:364print-colour-types-supported = black-and-white highlight-colour


document-formats-ready = PostScript simple-text PCL Interpresssides-ready = 1 2highlight-colours-ready = black variable (printer dependent, only one other supported value)media-ready = na-letter-white na-legal-whitefinishings-ready = none [staple]print-colour-types-ready = black-and-white highlight-colour

other attributes:








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).

PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuPrint N17 Level 2 PS


Xerox_DocuPrintN17_Level2PS.paf

printer-model:

Xerox DocuPrint N17


17 ppm


2000




323



input-trays-supported = 1 side [2] [3] [envelope]

output-bins-supported = top [stacker-1]

sides-supported = 1[2]







input-trays-ready = 1 side [2] [3] [envelope]

output-bins-ready = top [stacker-1]

sides-ready = 1 [2]




other attributes:




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”

PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuPrint N17 lpr


Xerox_DocuPrintN17_lpr.paf

printer-model:

Xerox DocuPrint N17


17 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuPrint N17 PCL5


Xerox_DocuPrintN17_PCL5.paf

printer-model:

Xerox DocuPrint N17


17 ppm


2000




121



input-trays-supported = 1 side [2] [3] [envelope]

output-bins-supported = top [stacker-1]








input-trays-ready = 1 side [2] [3] [envelope]

output-bins-ready = top [stacker-1]

sides-ready = 1 [2]




other attributes:




Example: pdset -x input-trays-supported+=“2 3” PrinterName


PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N24


24 ppm


2000




323



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]








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]




other attributes:




Example: pdset -x input-trays-supported+=“3 4 5” PrinterName


PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N24


24 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N24


24 ppm


2000




121














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N32


32 ppm


2000




323














sides-ready = 1 [2]




other attributes:



1. Attribute values in square brackets are printer options. These values are not included in the printer attributefile. If the printer option is installed, add the value to the attribute with pdset or during pdcreate.



PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N32


32 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N32


32 ppm


2000




121



input-trays-supported = top middle [bottom] [main] [large-capacity]











sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N40


40 ppm


2000




323














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N40


40 ppm


n/a


1179-job-submission


n/a












other attributes:




PRINTER DATA SHEETS





printer-model:

Xerox DocuPrint N40


40 ppm


2000




121














sides-ready = 1 [2]




other attributes:






PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuTech 6135 lpr


Xerox_DocuTech6135_lpr.paf

printer-model:

Xerox DocuTech 6135


135 ppm


n/a


1179-job-submissionxpp-job-statusxpp-device-status1179-job-cancel


n/a


document-formats-supported = PostScript simple-text PCL TIFFsides-supported = 1 2plexes-supported = simplex duplex tumbleoutputs-supported = no-page-collate page-collatemedia-supported = na-letter-white na-legal-white ledger iso-a0-white iso-a1-white iso-a2-white iso-a3-whiteiso-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-whitecontent-orientations-supported = portrait landscapedocument-sheets-supported = doc-set-start-copies-separatefinishings-supported = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind]x-image-shift-range-supported = -432:432y-image-shift-range-supported = -364:364print-colour-types-supported = black-and-white


document-formats-ready = PostScript simple-text PCL TIFFsides-ready = 1 2outputs-ready = no-page-collate page-collatedocument-sheets-ready = doc-set-start-copies-separatemedia-ready = na-letter-white na-legal-whitefinishings-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=20job-query-interval=00:01:00device-query-interval=00:05:00


1. The booklet maker is saddle-stitch finishing. The singlePortrait stapling is staple or staple-top-leftfinishing. The singleLandscape stapling is staple-bottom-left finishing. The dualLandscape stapling isstaple-dual-left finishing.




PRINTER DATA SHEETS


Printer Data Sheet: Xerox DocuTech 6180 lpr


Xerox_DocuTech6180_lpr.paf

printer-model:

Xerox DocuTech 6180


180 ppm


n/a


1179-job-submissionxpp-job-statusxpp-device-status1179-job-cancel


n/a


document-formats-supported = PostScript simple-text PCL TIFFsides-supported = 1 2plexes-supported = simplex duplex tumbleoutputs-supported = no-page-collate page-collatemedia-supported = na-letter-white na-legal-white ledger iso-a0-white iso-a1-white iso-a2-white iso-a3-whiteiso-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-whitecontent-orientations-supported = portrait landscapedocument-sheets-supported = doc-set-start-copies-separatefinishings-supported = [staple] [staple-top-left] [staple-bottom-left] [staple-dual-left] [saddle-stitch] [bind]x-image-shift-range-supported = -432:432y-image-shift-range-supported = -364:364print-colour-types-supported = black-and-white


document-formats-ready = PostScript simple-text PCL TIFFsides-ready = 1 2outputs-ready = no-page-collate page-collatedocument-sheets-ready = doc-set-start-copies-separatemedia-ready = na-letter-white na-legal-whitefinishings-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=20job-query-interval=00:01:00device-query-interval=00:05:00


1. The booklet maker is saddle-stitch finishing. The singlePortrait stapling is staple or staple-top-leftfinishing. The singleLandscape stapling is staple-bottom-left finishing. The dualLandscape stapling isstaple-dual-left finishing.




PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX B-1

B. Server startup commands,switches and exit status codes

This appendix covers the following functions:

� 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 forthe 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 serverstartups after the server had to repair the objectdatabase as part of a crash recovery.

-c Optional switch to force a database integrity check atstartup after a normal shutdown.

-d ODBpath Location of the object database if it is other thanthe default.

-e EmailAddress Optional switch to specify an email address for deliveryof startup error messages.

-F Optional switch to specify that the server should run inthe foreground.

-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.

SERVER STARTUP COMMANDS, SWITCHES AND EXIT STATUS CODES

B-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

Server startup command switches

All of the server startup command switches are optional, except forthe -a switch, which is required, only after a server undergoes acrash recovery.

-a = Acknowledge data loss switch

The -a switch is a required switch only for server startups takingplace after the server had to repair the object database as part of acrash recovery. Requiring the -a switch in the startup commandserves to remind you to check that attribute values of server objectsare correct, and thereby prevent you from starting the server with apossibly corrupt database.

An error message indicates that you need to use the -a switch to startthe server. After the server restarts, check the syslog file on/var/adm/messages for messages stating that data was corrupted, ifany.

The “Troubleshooting” chapter in this guide provides additionalinformation on database recovery.

-c = Check database integrity switch

The -c switch is an optional switch that forces a database integritycheck at startup after a normal shutdown. (The server automaticallychecks the database integrity when it restarts after a crash.) Youmay want to use the -c switch if you suspect that the database issomehow corrupt. The “Troubleshooting” chapter in this guideprovides additional information on database recovery.

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 itsobject database. By default, the server assumes that the objectdatabase resides in a standard location for all server objectdatabases (/var/pd/odb).

You have the option of creating a server database in a non-standardlocation. If the object database for a particular server exists in a non-standard location, then use the -d switch with the startup command tospecify where the database resides.

The -d switch specifies only the directory in which the server objectdatabase exists. The server startup command passes the databasename itself with the serverName parameter.

Example:

pdsplr -d /opt/otherdir myserver

where: /opt/otherdir is the ODBpath parameter for the -d switch, andmyserver is the serverName parameter for the server command

pdsplr

In this example, the full path name to the object database is/opt/otherdir/myserver.



The object database is actually a directory itself that contains severaldata files. Conceptually, however, you can think of the database as asingle entity.

-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 OIDdatabase is needed by the server to check the characteristics ofcertain attributes. A path name that references a legal OID databaseshould be specified for the scrOIDpath. If an OID database does notexist in the location specified by scrOIDpath, the server prints anerror message and exits.

If the –O switch is not specified, the source OID path name defaultsto /usr/pd/share. On a correctly installed system, this path nameshould contain a legal OID database.

-e emailAddress = Email address switch

The -e switch is an optional switch that specifies an email address fordelivery of server startup errors. When the server encounters anerror 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 alsosends the error message to the specified email address.

For example, the following command attempts to start the servermyserver, whose object database does not yet exist:

pdsplr -e [email protected] myserver

When the server encounters the error, it prints the following messageto 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 asthe following, to [email protected]:

Date: Mon, 12 Jan 1998 14:34:22 -0800From: Superuser (root)@abc.com (0000-Admin(0000))Subject: PrintXchange Server Startup FailureSender: [email protected]: [email protected]: textError 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 reasonthe server cannot deliver the message, the server ignores the emailproblem. The server sends email messages only in case ofunrecoverable errors, so the server normally exits very soon aftersending the error message.

-F

By default:

The server starts in the background.

The default condition means that the server is not attached to aterminal and the server cannot be halted by a control-C command.

If the server is started up from a shell command line, the shell promptis returned and the user is able to continue typing in the shell whilethe server is running in the background. Running in the backgroundis the ordinary behavior for a UNIX daemon. If a user requires theserver to run in the foreground (usually for debugging reasons), theuser can specify the -F switch.

Source OID path switch [-O srcOIDpath]

The -O switch tells pdmakedb where the OID database is. The OIDdatabase is needed by pdmakedb and the server to check thecharacteristics of certain attributes. A path name that references alegal OID database should be specified for srcOIDpath. If an OIDdatabase does not exist in the location specified by srcOIDpath,pdmakedb prints an error message and exits.

If the -O switch is not specified, the source OID path name defaultsto:

/usr/pd/share/oid

On a correctly installed system, this path name should contain a legalOID database. The source OID path name is stored in the cfg-src-oid-path attribute on the server object.



Server startup exit status codes

If the server starts up normally (the server does not encounter anyerrors), then the server starts waiting on client requests andprocesses those requests as they come in. If the server encountersan error during startup, it prints out an error message to standarderror and exits with a non-zero exit status.

The exit status codes are:

0 Normal server termination via a shutdown request ora 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 itis 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 toit.

7 Server did not have permission to access somedirectory.

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 aconfiguration attribute.

11 Server could not successfully run all initializationroutines.

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 Invalid e-mail method was encountered.

The “Troubleshooting” chapter in this guide lists the server startuperror messages.

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX C-1

C. Working with object databases

This appendix covers the following functions:

� Managing the object database

� Creating the object database (pdmakedb )

� 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 PrintXchangeobject (printers, queues, jobs, etc.) information that exists in thesystem. The object database provides persistency such that theserver does not lose any important information across restarts.

This section describes the set of utilities that allow you to createand/or modify an object database.

The utilities are:

� pdmakedb for creating an object database

� 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 therequired attributes to allow the server to start. Once the servercomes up, creations or modifications to other objects in the databasetake place internally through the normal use of the CLI clientcommands or the client GUI.

The utilities also allow you to set the values of some attributes thatare not considered to be configuration attributes, including:

� server-type

� access-control-list

The server-type attribute determines whether the database is for aspooler or a supervisor server. The pdmakedb command is the onlyway by which you can set the attribute server-type . Once youcreate a database of a particular server type, you cannot change it.

The access-control-list attribute is valid on all types of objects. Thedatabase utilities allow the value of the server object's access-control-list attribute to be set and or modified.

WORKING WITH OBJECT DATABASES

C-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

Creating the object database ( pdmakedb )

Use the pdmakedb utility to create an object database. Creating theobject database also creates the server object. You must create anobject database before you can start (run) the corresponding serverthat uses the database.

� To create a spooler database, enter:

/usr/pd/sbin/pdmakedb –n spooler_name

� To create a Reference supervisor database, enter:

/usr/pd/sbin/pdmakedb –t SUP –n refsup_name

� To create a Xerox supervisor database, enter:

/usr/pd/sbin/pdmakedb xerox_sup_name

The pdmakedb utility creates an object database that initially containsa single object, the corresponding server object. The name of thedatabase is also the name of the server object (note the -n switch).The utility adds default attributes to the server object, plus anyattributes you specify via the pdmakedb switches.

The pdmakedb utility displays an error message and exits if thedatabase you specify already exists.

The pdmakedb utility has the following command line syntax:

pdmakedb

[-a acctLogPath]

[-A adminACL]

[-d ODBpath]

[-D srcODBpath]

[-e execFilePath]

[-h] (help switch)

[-L locale]

[-n serverName]

[-O srcOIDpath]

[-r serverAuthType]

[-R runtimeDir]

[-s spoolDir]

[-t serverType]

[-v] (verbose switch)

All command line switches are optional. PrintXchange provides adefault value for any switch that you do not specify on the commandline.

Table C-1 in this appendix describes each of the switches.



Modifying an existing object database ( pdmoddb )

Use the pdmoddb command to modify an existing object database.The pdmoddb command modifies the attributes you specify on thecommand line if the attribute already exists in the database. If thespecified attribute does not exist, the pdmoddb command createsthe attribute and assigns the specified value. The command alsoadds any default attributes that do not already exist and that you donot specify on the command line.

The pdmoddb command cannot be used to modify a database thatis in use by an operating server. The corresponding server must beshut down before pdmoddb can access the database file.

The pdmoddb command displays an error message and exits if thedatabase you specify does not exist.

The pdmoddb command has the following command line syntax:

pdmoddb[-a acctLogPath] or [-a =][-A adminACL] or [-A =][-d ODBpath][-h] (help switch)[-n serverName][-O srcOIDpath] or [-O =][-r serverAuthType] or [-r =][-R runtimeDir] or [-R =][-s spoolDir] or [-s =][-v] (verbose switch)

All command line switches are optional. If you do not specify aswitch, pdmoddb leaves the corresponding attribute unmodified. If acorresponding attribute does not exist for the server object,pdmoddb adds the attribute with the default value.

The pdmoddb command allows a special syntax for settingattributes to their default values. For the -a, -A, -O, -r, -R, and -s,switches, if the value specified is an equals sign (=),pdmoddb setsthe attribute to its default value. Example:

pdmoddb -a =

The example changes the accounting log file path for the defaultserver from the current value to the default value.

Table C-1 in this appendix describes each of the switches.



Displaying object database data ( pdshowdb )

Use the pdshowdb command to interrogate the object databasewhen the server is not running. The pdshowdb command displaysthe values of all the attributes currently set on the server objectincluding both configuration and non-configuration attributes, andinternal as well as user visible attributes. The command does notchange the object database in any way.

When the server is running, pdshowdb command will not be able tointerrogate the database since the database is in use and thereforelocked.

The format that pdshowdb uses to display the server objectattributes is the same format used by pdmoddb with the -v switchset.

The pdshowdb command has the following command line syntax:

pdshowdb[-d ODBpath][-e executableDirectory][-h] (help switch)[-n serverName][-O srcOIDpath] or [-O =]

ODB command line switches All of the object database command line switches are optional. Inmost cases, the switch sets a server attribute. The following tablelists the switches, and provides a brief description, the correspondingserver attribute, and the utilities for which they are valid.

Table C-1. ODB command line switches

Switch Description Command

-a acctLogPath File path for the accounting log pdmoddb

-A adminACL Set administrator access pdmoddb

-d ODBpath File path for the object databasefiles

pdmoddbpdshowdb

-D srcODBpath Location of the source objectdatabase

-e execFilePath Absolute path to the executable fileused to start the server

pdshowdb

-h Command usage message pdmoddbpdshowdb

-L locale Server locale



Table C-1. ODB command line switches (continued)

Switch Description Command

-n serverName Name of the object database andof the corresponding server

pdmakedbpdmoddbpdshowdb

-O srcOIDpath Location of the OID database pdmakedbpdmoddbpdshowdb

-r serverAuthType RPC authentication type pdmakedbpdmoddb

-R runtimeDir Location of the server’s runtimedirectory

pdmakedbpdmoddb

-s spoolDir Location where the server spoolsdocuments to be printed

pdmakedbpdmoddb

-t serverType Type of object database: spooleror supervisor

pdmakedb

-v Prints processing messages andserver attribute values

pdmakedbpdmoddb

-a acctLogpath Server accounting log path switch

Description : The -a switch specifies the location of the serveraccounting log files. You can use any legal UNIXdirectory path name for acctLogPath. The directory towhich acctLogPath points does not have to exist at thetime you run pdmakedb or pdmoddb . The servercreates the directory (if possible) when the serverstarts up (although the server does not attempt tocreate any of the parent directories, if they do notexist).

Default: If the –a switch is not specified, the accounting logdirectory defaults to:

/var/pd/acct

-A adminACL Administrator access control list switch

Description : The -A switch specifies the initial administrator of theserver object. You can add other values foradministrators as well as operators and users once theserver is operational and responding to DPA requests.

The -A switch causes pdmakedb and pdmoddb tocreate or modify the server access-control-listattribute with the value specified by the value ofadminACL. The format of admin_acl is:

{name=admin_name [name_type=name_type]}

where admin_name and name-type adhere to theparameter definitions for access-control-list asdescribed in the PrintXchange Command LineInterface Reference Guide.



Default: If the –A switch is not specified, the utility creates adefault ACL. The default ACL has two values:

1. domain=<name_syntax:name> name-type=all-users; privilege-level=end-user

2. name=sysadmin; domain=<name_syntax:name>name-type=group; privilege-level=administrator.

-d ODBpath Server ODB path switch

Description : The -d switch specifies the location of the objectdatabase files. Your UID must have write permissionfor the path specified as ODBpath.

If the directory does not exist or the command cannotwrite to it, pdmakedb and pdmoddb print an errormessage and exit.

If the directory does not exist or the command cannotread it, pdshowdb displays an error message andexits.

Default: /var/pd/odb

Attribute: The pdmakedb , pdmoddb , and pdshowdb utilitiesoperate (create, modify, or display) on the objectdatabase in the directory specified by the -d switch (orin /var/pd/odb if -d is not specified). The name of thedatabase is as specified by the -n switch (or asspecified by the default database name if -n is notspecified). For example, for:

pdmakedb -n myServer -d /var/tmp

The full path name for the object database is/var/tmp/myServer.

The object database is actually a directory itself thatcontains 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 sourceobject database (ODB). The source ODB database ispart of the PrintXchange software installation andservers as the template for creating an objectdatabase. Without the source ODB database,pdmakedb is not able to create an object database.

The switch parameter srcODBpath must be the pathname that references the empty, source ODBdatabase; it cannot reference a previously createdODB database. If an ODB source database does notexist in the location specified by srcODBpath or if thedatabase is not empty, pdmakedb prints an errormessage and exits.

Default: /usr/pd/share/odb



-e execFilePath Server executable file path switch and command switch (only appliesto pdshowdb )

Description : The -e switch displays the absolute path and thespooler or supervisor executable file that starts theserver.

When used with pdshowdb , it displays the absolute pathand the server’s executable file that starts the server.

-h Help switch Accounting log path switch

Description : The -h switch causes pdmakedb , pdmoddb , andpdshowdb to print a usage message.

If you specify the -h switch, then the command onlyprints the usage message and does not do anythingelse, even if you specify other switches.

Default: None

-L locale Locale switch

Description : The -L switch sets the locale attribute on the serverobject with the value specified by locale. The localesyntax is:

ll_CC.charset

where:

ll= languageCC= countrycharset= character set

You must enter the locale value in upper- and lower-case characters because the value is case sensitive.

Default: Current process locale

-n serverName Database name switch

Description : The -n switch specifies the name of the objectdatabase. This name is also the name of the server.The name serverName may consist of any of thefollowing 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 ormore directories will be created in the file systemusing the supplied name)

The -n switch works together with the -t switch toidentify the name of the server as well as the type ofserver: spooler or supervisor.

If the database specified by the -n switch alreadyexists, pdmakedb prints an error message and exits.



The same is true if you do not specify the -n switch andthe database with the default name already exists.

If the database specified by the -n switch does not exist,pdmoddb and pdshowdb print an error message andexit. The same is true if you do not specify the -n switchand the database with the default name does not exist.

Default: -t switch is only needed for NT

-O srcOIDpath Source OID path switch

Description : The -O switch specifies the location of the OIDdatabase. The server and pdmakedb or pdmoddbor pdshowdb need the OID database to check thecharacteristics of certain attributes. The path namesrcOIDpath should reference a legal OID database.

If an OID database does not exist in the locationspecified by srcOIDpath, pdmakedb and pdmoddbprint an error message and exit.

Default: /usr/pd/share/oid

-r serverAuthType Server RPC authentication switch

Description : The -r switch specifies which of the RPC authenticationtypes the server will use. The only legal value forserverAuthType is SYS.

Default: SYS

-R runtimeDir Server runtime directory switch

Description : The -R switch specifies the location of the server'sruntime directory. When the server starts, it changesthe current directory to its runtime directory. Theserver interprets all paths that it encounters relative tothe server's runtime directory. The runtime directoryruntimeDir can be any legal UNIX directory path name.

The directory to which runtimeDir points does not haveto exist at the time you run pdmakedb or pdmoddb .The server creates the directory (if possible) when theserver starts up (although the server does not attemptto create any of the parent directories, if they do notexist).

Default: /var/spool/pd/serverName (serverName is as specifiedwith the -n switch)



-s spoolDir Server spool directory switch

Description : The -s switch specifies the location where the serverspools documents to be printed. The spool directoryspoolDir can be any legal UNIX directory path name.

The directory to which spoolDir points does not have toexist at the time you run pdmakedb or pdmoddb .The server creates the directory (if possible) when theserver starts up (although the server does not attemptto create any of the parent directories, if they do notexist).

Default: /var/spool/pd/serverName (serverName is as specifiedwith the -n switch)

-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 appropriatetype for the server that will use the database. Thelegal values for serverType are:

� SPL for a spooler

� SUP for a supervisor.

Refer to the discussion for the -n switch.

Default: SPL (spooler database)



-v Verbose switch Accounting log path switch

Description : The -v switch causes pdmakedb and pdmoddb toprint various messages as it validates any attributespassed on the command line. For example, if youspecify the -A, -r and -v switches on the command line,the following messages appear:

Validating requested server attributes:Checking attribute: access-control-listChecking attribute: cfg-rpc-auth-typeAll requested server attributes are valid

The -v switch also causes pdmakedb and pdmoddbto print the values of all the server attributes afterpdmakedb and pdmoddb finish creating or modifyingthe object database. The following is an example ofthe output from pdmakedb /pdmoddb :

Current server attributes:

achilles_spl:server-state = readyachilles_spl:server-internal-state = 2achilles_spl:object-classes-supported = serverachilles_spl:enabled = FALSEachilles_spl:conformance-levels-supported = level-1

level-1Mlevel-2level-2M

achilles_spl:cfg-src-odb-path = /usr/pd/share/odbachilles_spl:cfg-src-oid-path = /usr/pd/share/oidachilles_spl:cfg-spool-path = /var/spool/pd/achilles_splachilles_spl:cfg-server-runtime-dir =

/var/spool/pd/achilles_splachilles_spl:cfg-acct-log-file-path =

/var/pd/acct/achilles_splachilles_spl:access-control-list =administrator:sysadminachilles_spl:server-type = spoolerachilles_spl:cfg-rpc-auth-type = SYSachilles_spl:cfg-max-log-backups = 4achilles_spl:cfg-days-to-keep-acct-logs = 3achilles_spl:cfg-safe-size-for-acct-logs =1000000achilles_spl:cfg-time-for-new-acct-log = 03:15:00

Note : The configuration attributes are primarily internalattributes. Typically you will not have to access them.

Default: Nothing printed, except for error messages



Object database utilities exit status codes

When any of the object database utilities exits, it always returns anexit status. The server uses the exit status values as a coarse-grained guide to why the command exited. The status codes arebeneficial primarily in the case where an error message cannot bedelivered for some reason. Ordinarily, you will be more concernedwith the actual error message than with the exit status of thecommand. For addition information on error messages, refer to the“Troubleshooting” chapter.

In the following list, the error statuses are the same for all utilitiesunless the description names a specific command.

� 0 - Normal command exit, no error encountered.

� 1 - A command detected an error in the given parameters.

� 2 - A command could not allocate any dynamic memory.

� 3 - A command could not lock the object database.

� 4 - The pdmakedb command was asked to create an objectdatabase that already exists.

� 5 - The pdmakedb command could not create an objectdatabase.

� 6 - A command could not open or access an object database.

� 7 - A command could not locate its message file.

� 8 - A command could not set its locale.

� 9 - A command could not initialize the threads subsystem.

� 10 - A command could not determine its current directory.

� 11 - The pdmakedb or pdmoddb command determined that thevalue for a specified path name was too long.

� 12 - The pdmakedb or pdmoddb command encountered someerror while trying to validate user-supplied attributes.

� 13 - A command encountered an error while trying to display theserver object attributes.

� 14 – A command detected an error converting to normalized filepath 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 NTregistry.

� 20 – OID (Object Identification Database) initialization failed.

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX D-1

D. Printers.conf file

Making ONC RPC binding entries

Local file and NIS naming use entries in ONC entry binding format toidentify printing objects.

The syntax of the ONC entry binding format is similar to that used in/etc/printcap and /etc/remote except that the ONC entry bindingformat uses different keynames.

The syntax for a printer-configuration is:

ONCEntry::=NameList{: KeyValuePair}+

NameList::=PrimaryName{‘|’ Alias}+

KeyValuePair::=Name={ValueDP | ...}

ValueDP::=Hostname, ProgramNumber, ProgramVersion,Authentication, SubType, ServerName[, ProtoServer], spooling-type

where:

{...}+ = one or more

| = or

‘|’ = the symbol |

[...] = optional

PRINTERS.CONF FILE

D-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

Parameter Description

ONCEntry A printer table entry that consists of a PrimaryName, optional Aliases, andone or more KeyValuePairs.

PrimaryName of Object The primary name for identifying an object.

Aliases Zero or more aliases of the object (optional).

KeyValuePair An attribute that consists of an attribute name and its value. Here we showonly the values of type ValueDP.

ValueDP Server bindings for:

printer address binding (paddr)

server address binding (saddr)

queue address binding (qaddr)

Hostname Name of the host machine that holds the object and its associated server.

ProgramNumber RPC program number of either a server or ProtoServer. A server programnumber may be one that a server creates dynamically, or it may be thespecial one for a spooler.

ProgramVersion RPC version number of either the server or ProtoServer.

Authentication RPC authentication method that is used (such as sys, des, kerb; Odysseysupports sys only)

SubType Describes the object:

lp = Logical printer object

pp = Physical printer object

qu = Queue object

sl = Spooler server object

sv = Supervisor server object

ServerName Name of the server associated with the object.

ProtoServer Optional. If the parameter value is 1, then the ProtoServer is used; if thevalue is 0, the ProtoServer is not used. The value of this field must be 1 forlocal file and NIS naming.

Spooling-type The name of the printing paradigm for which an inbound gateway translationis to occur. The valid value is: dpa.

PRINTERS.CONF FILE

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX D-3

Example 1: printer-configuration elmtree:paddr=papers,105004,1,sys,lp,woden, 1:spooling-type=dpa

In this example:

elmtree is the name of the object, and it contains printer addressbinding information.

The printer address binding information includes the RPC bindinginformation with an RPC hostname of papers, with a program numberof 105004 (the ProtoServer’s RPC number) and a program versionnumber of 1.

The elmtree object has RPC authentication method of sys.

elmtree is a logical printer object that has an associated serverobject named woden.

The ProtoServer is used on the UNIX host machine (papers) todetermine the proper RPC Dynamic Program Number that will beused to connect to the spooler server (woden).

dpa is the printing paradigm for inbound gateway jobs.

For a configuration that consists of two clients running on hostA andhostB, a spooler with two logical printers and a single queue onhostC, and a supervisor with two physical printers on hostD, thecomplete configuration file would be:

spooler1:saddr=hostC,105004,1,sys,sl,spooler1,1

superv1:saddr=hostD,105004,1,sys,sv,superv1,1

lp1:paddr=hostC,105004,1,sys,lp,spooler1,1:spooling-type=dpa

lp2:paddr=hostC,105004,1,sys,lp,spooler1,1:spooling-type=dpa

q1:qaddr=hostC,105004,1,sys,qu,spooler1,1

pp1:paddr=hostD,105004,1,sys,pp,superv1,1

pp2:paddr=hostD,105004,1,sys,pp,superv1,1

This configuration file would need to be present on all four hosts in alocal file naming environment or used to update the NIS database inan NIS environment.

Note that in a local file environment, PrintXchange does not use thenaming component of ONC, but the system still relies on ONC RPC.

Example 2: The NameSpace entry syntax corresponding to a BSD printer entryis:

bsdaddr=HostName[,RemotePrinterName[,ProtocolConformance]]

RemotePrinterName is the name of the BSD printer that correspondsto the value of the attribute bsd-printer-name .

ProtocolConformance values are 1179, Solaris, Xerox, and DEC.

Example:

bsdaddr=keno,elmtree

PRINTERS.CONF FILE

D-4 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX E-1

E. SNMP query support

When using SNMP for device status, PrintXchange queries theprinter 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 jobstatus. PrintXchange supports the following MIBs:

� Fuji Xerox OPS MIB

� RFC 1759 Printer MIB.

The following table lists the mappings of supported MIB entries toPrintXchange attributes:

Table E-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-message

low paper n y

no paper y y

no cassette y n

input tray fail y n

output tray fail y n

bad paper size y n

SNMP QUERY SUPPORT

E-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX


MIB support


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 nearexhausted

n n

drum life exhausted y n

no drum y n

duplex fail y n

service requested n y

offline n y

problem unknownreason

n n

input-trays-supported

1 y y

2 y y

3 y y

4 y y

5 n y

6 n y

7 n y

8 n y

9 n y

10 n y

manual y y

manual-2 n y

SNMP QUERY SUPPORT



MIB support


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-trays-supported

y y

media-ready na-letter-white y y

na-legal-white y y

na-number-10-envelope

y y

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-envelope

y y

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

SNMP QUERY SUPPORT



MIB support


folio y y

hagaki-white y y

medium-default y y

other media definedby DPA

n y

input-tray-medium * defined bycombination of input-trays-supported andmedia-ready

y y

output-bins-supported

face-up y n

face-down y n

center y n

side y y

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

SNMP QUERY SUPPORT



MIB support


left n y

right n y

large n y

private n y

1 n y

2 n y

3 n y

4 n y

5 n y

6 n y

7 n y

8 n y

9 n y

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

SNMP QUERY SUPPORT



MIB support


25 n y

output-bins-ready * same as output-bins-supported

y y

document-formats-supported

Document formatsthat are supported onthe output device

y n

document-formats-ready

Document formatsthat are ready on theoutput device

y n

native-document-formats-ready

Document formatsthat are ready to useon the output deviceitself

y n

sys-up-date-and-time

an appropriate valueshall be given ingeneralizedTimeSyntax

y n

Job current-job-status completed y n

job-state-reasons successful-completion

y n

complete-with-warning

y n

abort-by-system y n

job-message-from-administrator

an appropriatemessage shall begiven.

n n

pages-completed an appropriate valueshall be given incardinal syntax

y n

total-job-octets an appropriate valueshall be given.

n n

media-sheets-completed

an appropriate valueshall be given incardinal syntax.

y n

SNMP QUERY SUPPORT


Generic printer support

The PrintXchange MAM library provides the capability of getting theprinter state from generic printers using the standard printer MIB (asdefined by RFC 1759). However, the implementations of the MIBdatabase and the agent behavior are slightly different depending onthe printer.

When making device status requests, the PrintXchange libraryobtains as many of the printer attributes listed in Table E-1 as it canget, compares them to the current values given by the supervisorback end, and returns only those attributes whose values changed.

If the PrintXchange does not receive an answer to the device statusrequest from a remote printer, the library reports the printer-stateattribute with the timed-out value. The library keeps other attributeswith the current status, except for printer-problem-message , whichit removes.

The PrintXchange library uses the following MIB objects to translateprinter status information to Printxchange attributes:

� hrDeviceType

� hrDeviceStatus

� hrPrinterStatus

� hrPrinterDetectedErrorState

� prtInputType

� prtInputEntry

� prtInputDimUnit

� prtInputMediaDimFeedDirChosen

� prtInputMediaDimXFeedDirChosen

� prtInputStatus

� prtOutputStatus

Note: The set of trays for input-trays-ready is determined by the MIBprtInoutStatus=0,2,4,6,8,10,12, or 14. MIB prtOutputStatus set toeither of the same values also determines the set of trays for output-bins-ready.

SNMP QUERY SUPPORT


printer-state The PrintXchange library uses hrDeviceStatus, hrPrinterStatus, andhrPrinterDetectedErrorState to determine the value of the printer-state attribute as shown in Table E-2.

Table E-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 andserviceRequested

needs-attention

TESTING don't care don't care idle

UNKNOWN(other) don't care don't care unknown

* When the prnter does notanswer SNMP requests, thePrintXchange library changesprinter-state to timed-out .

timed-out

printer-problem-message The PrintXchange library uses the MIB objecthrPrinterDetectedErrorState to determine the value of the printer-problem-message attribute. The hrPrinterDetectedErrorState objectis 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 ismulti-valued):

� cover open

� jammed

� low paper

� low toner

� no paper

� no toner

� offline

� service requested

SNMP QUERY SUPPORT


input-trays-supported/input-trays-ready The PrintXchange library uses prtInputEntry, prtInputType, andprtInputStatus to determine the value of the input-trays-supportedand input-trays-ready attributes.

Depending on the sequence order of prtInputEntry and prtInputTypeentries present in the MIB table, the PrintXchange library determinesthe value of the input-trays-supported attribute as shown in TableE-3.

Table E-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

SNMP QUERY SUPPORT


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


7th: manual type input tray manual-3

8th: manual type input tray* 5*


Note: The 8th entry in the example is a fourth entry for a manualtype input tray. In this case (and for any subsequent manual inputtray entries), the PrintXchange library sets the next available inputtray value between 1 and 10.

� prtInputStatus is a member of prtInputEntry that represents thestatus of an input tray. Each prtInputStatus entry corresponds toan individual input tray as represented by prtInputEntry.Depending on the value of prtInputStatus for each input tray, thePrintXchange library sets the input-trays-ready attribute value.The following prtInputStatus values indicate the setting of theinput-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 determinethe value of the media-ready attribute:

� prtInputDimUnit

� prtInputMediaDimFeedDirChosen

� prtInputMediaDimXFeedDirChosen

� prtInputStatus

The four objects are members of prtInputEntry. Note that the valueof fxIOTInputTrayMedium represents the name of the mediuminstalled in the input tray.

The PrintXchange library compares the value of prtInputDimUnit,prtInputMediaDimFeedDirChosen, andprtInputMediaDimXFeedDirChosen with the size of the Printxchange-supported media. The library then adds any matching values to themedia-ready attribute depending on the value of prtInputStatus. If

SNMP QUERY SUPPORT


the value of prtInputStatus shows “available”, then the library addsthe medium value to the media-ready attribute.

If the library finds no matches, it adds the medium-default to themedia-ready attribute if it is available.

input-trays-medium The library sets the value of input-trays-medium with any of themedia that it identifies as described above for media-ready .

output-bins-supported/output-bins-ready The PrintXchange library uses prtOutputEntry and prtOutputStatus todetermine the value of the output-bins-supported and output-bins-ready attributes.

� Depending on the sequence order of prtOutputEntry entriespresent in the MIB table, the PrintXchange library determines thevalue of the output-bins-supported attribute.

The prtOutputEntry is mapped to output-bins-supported value 1,second entry is mapped to value 2 and so on.

Table E-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

SNMP QUERY SUPPORT


Table E-4. Output bin translation

prtOutputEntry in MIB Table output-bins-supported value

22th 22

23th 23

24th 24

25th 25

� prtOutputStatus is a member of prtOutputEntry that representsthe status of an output bin. Each prtOutputStatus entrycorresponds to an individual output bin as represented byprtOutputEntry. Depending on the value of prtOutputStatus foreach output bin, the PrintXchange library sets the output-bins-ready attribute value. The following prtOutputStatus valuesindicate the setting of the output-bins-ready attribute:

� 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 theinformation to be able to be translated into Printxchange attributevalues. Therefore the MIB attribue mapping parse trap is almostsame thing as for the device status. The PrintXchange library expectsto be given the current printer attributes of the designated printer. Inthe parse trap, the library compares the given attributes with theattributes obtained by the device status.

The PrintXchange library creates event report information from theresult of device status and returns the information to the supervisorback end.

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX GLOSSARY-1

Glossary of terms andabbreviations

This glossary includes standard definitions of terms andabbreviations commonly used in the PrintXchange environment andin this document.

Terms and abbreviations

ACL access control list. List of entities (such as users, operators,administrators, and servers) used to determine whether a certainentity has authorization to perform some operation or function.

Administrator A class of user that is enforced by security. An administrator setspolicy and can create, modify, and delete persistent print systemobjects, such as printers and servers. This term is synonymouswith 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 requestby checking and validating the user’s credentials.

Authorization The process whereby an access policy determines whether anentity (authenticated or unauthenticated) may perform a particularoperation.

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 withwhich an end-user can submit print requests or managementrequests.

DCE Distributed Computing Environment

DPA document printing application

DPA protocol A method of communication used in the exchange between clientand server as specified in the ISO DPA standard.

GLOSSARY OF TERMS AND ABBREVIATIONS

GLOSSARY-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

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 InternationalStandards Organization’s Document Printing Application Standard10175.

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 formattingconventions, monetary conventions, decimal formattingconventions, and collation order.

localization The process of adapting software for specific languages or regions.Localization involves providing the necessary translations, formatdefinitions, tables, and other data to prepare an internationalizedproduct for local requirements.

logical printer A named object of class printer that is used to group one or morephysical printer objects for load balancing and/or to specifyalternative default attributes to those specified by the physicalprinter object.

LPD line printing daemon

LPD Protocol Line printer daemon protocol for printing systems used by theBerkeley versions of the UNIX operating system. It is described inRFC 1179.

LPR line printer

MAPI messaging application program interface

MSMAIL Microsoft mailing system

MSRPC Microsoft Word remote procedure call. The communication protocolwith a Windows NT PrintXchange spooler.

Multinationalization The process of both developing a product so that it can be readilycustomized for different markets (internationalization) and takingthe product and creating an instance for a specific target market(nationalization).



Name service A set of capabilities provided throughout a network environment byservers, 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 hadrequested its services. Generally, the mechanisms needed toimplement notification are provided by the system infrastructure. Inmost system environments, electronic mail can be used as a crudemeans for notification.

NPS network printing system

NT new technology

Object A collection of attributes that are used to inform about or describe anamed physical or logical entity. In the PrintXchange distributedprint 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 bysecurity. An operator can perform day-to-day operations, such aspausing and resuming jobs and printers, disabling and enablingprinters.

OS operating system

OSF Open Software Foundation

Output device A printer. A physical device or hardware that is capable ofrendering 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 namedprinter object that represents an output device such as laserprinting hardware or a rendering system. May also mean bothphysical printer and output device together.

PJL Print Job Language

POSIX The IEEE standards body that is chartered with standardizingportable operating system interfaces for UNIX. In this document,POSIX refers to the operating system interface standard forprinting.



PSIS Printing System Interoperability Specification

PXC PrintXchange

Queue A spooler object that partitions logical and physical printers. Agiven printer may only exist in a single queue, thus queues partitionprinters into disjoint sets. The default PrintXchange spoolerconfiguration is a single queue. Within a queue, a logical printermay be associated with one or more of the physical printers of thequeue. The default association is to all of the physical printers.

Additionally, queues impose an ordering on the jobs submitted tothe logical printers of the queue. This imposed ordering is knownas 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 areauthentication and authorization. Authentication guarantees theidentity of the client, and authorization ensures that a client haspermission to access a service.

Server A software component that manages printing facilities on behalf of aclient or clients on the same computer or over a network. ForPrintXchange, the term is generally used to refer to the print serverthat 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 alsoa client of the supervisor for which the supervisor is a print server tothe spooler

SMB server message block

SMTP simple mail transfer protocol

SNMP simple network management protocol. A simple protocol by whichmanagement information for a network element may be inspectedor altered by logically remote users (RFC 1157).

SPL spooler

Spooler An ISO DPA and POSIX object of class server. A specialization ofa server object. A named server that accepts PrintXchangeoperations from print clients and schedules print jobs onappropriate printer supervisors. The typical spooler is multi-threaded and is capable of processing multiple print operationsconcurrently.



Supervisor An ISO DPA and POSIX object of class server. A specialization ofa server object. A static process or software to drive a specificprinter for the printing of print jobs. A supervisor is entirelyresponsible for interpreting the job request. This includesinterpreting the content of the file(s) and reconciling the instructionsprovided in the print request parameters with the contents of thefile. The supervisor has complete control over the printing of thejob, including the loading of fonts, forms, and other electronicresources into the printer, as well as transferring the file(s) to theprinter.

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. Auser (unprivileged) that submits print jobs and gets status.

VM virtual memory

PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX INDEX-1

Index

AAccess Control Lists, 7-5access-control-list, C-1accounting

attributes, 18-3enabling, 18-2profile, 18-3report writer, 18-4

accounting-profile, 18-3ACLs, 7-5

default values, 7-10defining, 7-5, 10-10without privilege specification, 7-10

administrator operations, 2-14application

pdprint, 11-6associated-queue, 10-4, 10-7, 14-23attributes, 2-13

allowed, for set and modify, 14-3document, 14-13initial-value-document, 14-16initial-value-job, 14-15job, 14-11listing, 12-5, 13-33logical printer, 14-6mapping, 14-23physical printer, 14-6print data processing, 14-28queue, 14-10server, 14-4xxx-ready, 14-26xxx-supported, 14-26

authentication, 7-2authorization, 7-3automated installation script, 6-7automated removal script, 6-7

Bbalancing load, 10-6binding entries, D-1bsd-printer-name, D-3

Ccancel job, 2-14canceling jobs, 13-26changing name service default, 5-9character sets, 2-25clean, 2-14cleaning

objects, 13-34

spooler, 13-35CLI, 2-5, 2-18, 11-2

command options, 11-4creating objects, 10-2modification operators, 14-2syntax, 11-3

clientCommand Line Interface, 2-5graphical user interface, 2-5inbound gateway, 2-5

client interfaces, 2-17clients, 2-1, 2-5, 2-28

installation, 5-17command line interface, 2-5, 2-18Command Line Interface, 2-5, 11-2command options, 11-4component software

installation, 5-11components, 2-1concepts, 2-1configuration

fan-in, 5-2fan-out, 5-3one-to-one, 5-1process, 4-3

content-orientations-supported, 14-32conventions, 1-1copies, 20-1crash recovery, 21-150

accounting, 21-156client, 21-156database, 21-151document, 21-152job, 21-152job state reasons, 21-154LAN Manager inbound gateway, 21-156notification, 21-156operations, 21-157server startup, 21-150Xerox supervisor, 21-155

create, 2-14creating objects

through CLI, 10-2creating the object database, 9-4current-job-state, 13-5, 13-7, 13-9, 13-24

Ddata sheet, A-1database utilities

exit status, 21-149default job priorities

modifying, 13-23default transfer method, 7-15

INDEX

INDEX-2 PRINTXCHANGE SYSTEM ADMINISTRATION AND OPERATIONS GUIDE FOR UNIX

default-character-set, 14-30default-font, 14-30default-job-completion-period, 13-25, 13-28defining ACLs, 7-5, 10-10defining event notification profiles, 10-12, 10-13delete, 2-14deleting

document defaults, 13-22initial-value-document, 17-10initial-value-job, 17-10job defaults, 13-22jobs, 13-25logical printers, 17-9physical printers, 17-7queues, 17-6spoolers, 17-3supervisors, 17-5

delivery methodselectronic mail, 8-13message, 8-13

determining your network printing system requirements,4-1

device status query, 2-9disable, 2-14disabling

logical printers, 16-11physical printers, 16-9PrintXchange objects, 16-2queues, 16-7spoolers, 16-6supervisors, 16-6

discarding jobs, 13-28document defaults

deleting, 13-22document formats, 14-29documentation, 1-2documents

attributes, 14-13listing names and attributes, 13-33modifying attributes, 13-15printing, 13-2

document-sheets, 20-5, 20-7DocuPrint NPS print server, 2-9DocuSP print server, 2-9

Ee-mail notification

restrictions, 21-24enable, 2-14enabling

logical printers, 16-10physical printers, 16-8PrintXchange objects, 16-2queues, 16-7spoolers, 16-5supervisors, 16-5

environment variables, 2-25, 11-2error messages

error code prefixes, 21-26reference supervisor, 21-144

event notification, 8-1event notification profiles

defining, 10-12, 10-13events, 8-1exit status

codes, B-5database utilities, 21-149server, 21-147

Ffeatures and benefits, 2-3file security, 7-15file transfer, 7-13file-reference transfer method, 7-15finishing, 20-7

Ggeneric printer, support, E-7graphical user interface, 2-5, 11-6Graphical User Interface, 2-5GUI, 2-5, 11-6

window description, 11-8

Hhardware requirements, 3-2highlight color, 20-2highlight-colour, 20-2highlight-colour-mismatch-action, 20-2highlight-colour-rendering-algorithm, 20-2highlight-colour-rendering-algorithms-supported, 20-2highlight-colours-ready, 20-2highlight-colours-supported, 20-2highlight-mapping-colour, 20-2highlight-mapping-colours-supported, 20-2holding jobs, 13-7

Iimaging parameters, 14-30inbound gateway, 2-5inbound gateway

installation, 5-17inbound gateways, 2-7

enabling, 4-2LPR, 19-1

infrastructure, 2-16, 2-27initial-value-document

attributes, 14-16creating, 10-9deleting, 17-10

initial-value-jobattributes, 14-15creating, 10-9deleting, 17-10

input-trays-medium, 20-6input-trays-ready, 20-6input-trays-supported, 20-6installation

clients, 5-17component software, 5-11inbound gateway, 5-17reference supervisors, 5-16software components, 5-15spoolers, 5-15the process, 4-2Xerox supervisors, 5-16

installation of Solaris operating system packages

INDEX


required, 6-6installation script

automated, 6-7manual, 6-7

international considerations, 2-24

Jjob cancellation, 2-9job defaults

deleting, 13-22job diagnostics, 21-5job priorities

modifying, 13-23job queue

listing, 12-7, 13-29job resume, 13-11, 13-12job status query, 2-9job submission, 2-9job-copies, 20-1job-copies-supported, 20-1job-count, 20-1job-discard-time, 13-28job-hold, 13-7job-print-after-specified, 13-5job-retention-period, 10-9, 13-25, 13-26, 13-28jobs

attributes, 14-11canceling, 13-26deleting, 13-25discarding, 13-28holding and releasing, 13-7listing names and attributes, 13-33modifying attributes, 13-15pausing and resuming, 13-9printing, 13-2printing, after a specified time, 13-5promoting, 13-24resubmitting, 13-20retaining, 13-13setting priorities, 13-18

job-sheets, 20-4job-state-reasons, 13-5job-submission-complete, 13-20

Llist job queue, 2-15list object attributes, 2-15listing a job queue, 13-29listing names and attributes, 13-33listing the job queue, 12-7load balancing, 10-6Local File NameSpace, 5-6log files, 2-27logical printer

attributes, 14-6logical printers

deleting, 17-9disabling, 16-11enabling, 16-10

logical printers, 2-10, 10-1creating, 10-7, 10-8creating and configuring, 4-2creating and enabling, 10-7, 10-8enabling, 4-2, 10-7, 10-8

lpq, 2-9lpr, 2-9LPR, 19-1

administration and configuration, 19-2basic opeation, 19-2deinstallation, 19-2installation, 19-1translations, 19-3

lprm, 2-9

Mmanual installation script, 6-7manual removal script, 6-7mapping attributes

setting, 14-23message catalog files, 2-27MIB types, 14-18modify, 2-15modifying

document attributes, 13-15job attributes, 13-15

multinational considerations, 2-24clients, 2-28environmen variables, 2-25infrastructure, 2-27internationalization requirements, 2-24log files, 2-27message catalog files, 2-27servers, 2-27supported character sets, 2-25

Nname service default

changing, 5-9name services

planning, 5-5Name Services, 7-1name space considerations, 10-2names of jobs and documents, 13-33network configurations, 5-12Network Information Service, 5-7network requirements, 3-1NIS, 5-7notification profiles

specifying, 8-9notification server, 8-8notification server logging events, 21-23notification-profile, 8-1, 8-10number-up, 14-32

O-O source OID path switch, B-4object attributes

listing, 12-5object database

creating, C-2displaying, C-4managing, C-1modifying, C-3

object database utilitiesexit status codes, C-11

object states, 21-2object status, 12-1

INDEX


objects, 2-13cleaning, 13-34

ODB command line switches, C-4OID database, 14-34

pdaddoid utility, 14-35updating, 14-34

ONC RPC binding entries, D-1operation

cancel job, 2-14clean, 2-14create, 2-14delete, 2-14disable, 2-14enable, 2-14list job queue, 2-15list object attributes, 2-15modify, 2-15pause, 2-15print, 2-15promote, 2-15resubmit, 2-15resume, 2-15set attributes, 2-15shutdown, 2-15

operator operations, 2-14output devices, 2-2

supported, A-1output-bin, 20-6

Ppackages

Graphic User Interface (GUI), 6-4PrintXchange Inbound gateway, 6-3PXCclient, 6-3PXCcore, 6-3PXCdtusr, 6-4PXCibgw, 6-3PXCman, 6-3PXCpaf, 6-3PXCsplr, 6-4PXCsuperv, 6-4PXCsvrcor, 6-4PXCutils, 6-4PXCxspvr, 6-4

paddr, D-2paf-job-separator-format, 20-3pause, 2-15pausing

jobs, 13-9physical printers, 15-6PrintXchange objects, 15-2queues, 15-5spoolers, 15-4

pdaccount utility, 18-1, 18-4pdaddoid utility, 14-35pdclean, 13-35, 17-4, 17-6pddelete, 13-22, 13-25, 17-4, 17-5, 17-6, 17-8, 17-9,

17-10pddiag operation, 21-5pddiagjob utility, 21-7pddisable, 13-35, 16-6, 16-9, 16-11, 17-4, 17-5, 17-6,

17-8, 17-9pdenable, 13-35, 16-5, 16-9, 16-10pdls, 13-33pdmakedb command, C-2

pdmod, 13-6, 13-19, 13-28pdmoddb command, C-3pdpr, 13-3, 13-6, 13-28pdprint application, 11-6pdprintinfo

pause job, 13-10resume job, 13-11

pdq, 13-29, 13-31pdresume, 13-11, 13-12pdrm, 13-25pdset, 7-5, 8-10, 10-10, 10-12, 13-6, 13-19, 13-23, 13-28,

18-2pdshowdb command, C-4pdshowoid utility, 14-36physical printer

attributes, 14-6physical printers, 2-10, 10-1

creating, 10-4, 10-6, 10-7, 10-15creating and configuring, 4-2creating and enabling, 10-4, 10-6, 10-7, 10-15deleting, 17-7disabling, 16-9enabling, 4-2, 10-4, 16-8load balancing, 10-6pausing, 15-6resuming, 15-7

physical-printers-requested, 20-1physical-printers-supported, 14-23, 20-1planning

name services, 5-5security, 5-4

plex, 14-31print, 2-15printer associations, 5-1printer data sheet, A-1printer data sheets, A-5printer-address, 10-5printer-associated-printers, 14-23printer-baud-rate, 10-15printer-connection-method, 10-15printer-initial-value-document, 10-7, 13-22printer-initial-value-job, 10-7, 13-22printer-name-requested, 13-3printers, 2-2printing

documents, 13-2jobs, 13-2

printing jobs after a specified time, 13-5printing system

clients, 2-1components, 2-1, 2-16output devices, 2-2printers, 2-2server daemons, 2-2servers, 2-2

PrintXchangeattributes, 2-13client interfaces, 2-17clients, 2-5directory structure of files, 5-14infrastructure, 2-16logical printers, 2-10network configurations, 5-12objects, 2-13physical printers, 2-10queues, 2-10

INDEX


removing, 6-8servers, 2-8, 2-19software components, 5-11spoolers, 2-20system requirements, 3-1testing the system, 10-16

PrintXchange objectsdisabling, 16-2enabling, 16-2pausing, 15-2removing (deleting), 17-1resuming, 15-2

priorities, 13-18promote, 2-15promoting jobs, 13-24ProtoServer, 5-9publications, 1-2PXCclient, 6-3PXCcore, 6-3PXCdtusr, 6-4PXCibgw, 6-3PXCman, 6-3PXCpaf, 6-3PXCsplr, 6-4PXCsuperv, 6-4PXCsvrcor, 6-4PXCutils, 6-4PXCxspvr, 6-4

Qqaddr, D-2queue associations, 5-1queues, 2-10, 10-1

attributes, 14-10creating, 10-3creating and configuring, 4-2creating and enabling, 4-2, 10-3, 16-7deleting, 17-6disabling, 16-7enabling, 4-2, 10-3, 16-7pausing, 15-5resuming, 15-5

Rreference supervisor, 2-9

error messages, 21-144installation, 5-16

releasing jobs, 13-7removal script

automated, 6-7manual, 6-7

removing (deleting) PrintXchange objects, 17-1removing from server or queue

jobs, 13-34removing PrintXchange, 6-8requirements

hardware, 3-2network, 3-1software, 3-1system, 3-1

reset-printer, 20-7restrictions

e-mail notification, 21-24resubmit, 2-15

resubmitting jobs, 13-20resume, 2-15resuming

jobs, 13-9physical printers, 15-7PrintXchange objects, 15-2queues, 15-5spoolers, 15-4

retaining jobs, 13-13RFC 1179 protocol, 2-9

Ssaddr, D-2security, 7-2

planning, 5-4separator pages, 20-3server

exit status, 21-147logging events, 21-16spooler, 2-8supervisor, 2-8

server daemons, 2-2servers, 2-2, 2-8, 2-19, 2-27

attributes, 14-4creating, 9-4creating and starting, 9-4enabling, 9-5restarting, 9-6shutting down, 9-6starting, 9-4, 9-5startup command switches, B-2startup commands, B-1startup exit status codes, B-5

server-type, C-1service log facility, 21-10set attributes, 2-15setting job priorities, 13-18setting mapping attributes, 14-23shutdown, 2-15shutting down servers, 9-6sides, 14-31SNMP, 2-9SNMP, query support, E-1socket transfer method, 7-14software requirements, 3-1Solaris operating system packages

required installation, 6-6Solaris packages

description, 6-2SUNWfns, 6-2SUNWfnspr, 6-2SUNWisolc, 6-2

spooler, 2-8cleaning, 13-35

spoolers, 2-20deleting, 17-3disabling, 16-6enabling, 16-5installation, 5-15pausing, 15-4resuming, 15-4

Spooler-to-supervisor file transfer method, 7-15standard system logging, 21-14startup command switches, B-2startup commands, B-1

INDEX


status query, 2-9SUNWfns, 6-2SUNWfnspr, 6-2SUNWisolc, 6-2supervisor, 2-8

reference, 2-9Xerox, 2-9

supervisors, 2-20deleting, 17-5disabling, 16-6enabling, 16-5

support, generic printer, E-7system requirements, 3-1

Tterminology, 2-1thickening-specification, 20-2thickening-supported, 20-2transfer methods, 7-14troubleshooting

error messages, 21-26job diagnostics, 21-5notification server logging events, 21-23pddiag operation, 21-5server logging events, 21-16service log facility, 21-10standard system logging, 21-14

system logging, 21-10UNIX files, 21-9utility diagnostics, 21-7

Uunderstanding object states, 12-1

Vvalidating installation and configuration, 4-3

Wwith-request transfer method, 7-14

XXerox supervisor, 2-9, 16-8

installation, 5-16x-image-shift, 14-33XPPQ, 2-9

Yy-image-shift, 14-33