Advanced Printing Software System Administration and Operation Guide September 2002 Product Version: Operating System and Version: Advanced Printing Software Version 1.2 Tru64 UNIX Version 5.1B or higher This manual describes how to configure and manage Advanced Printing Software on systems running the Tru64 UNIX operating system.
© 2002 Hewlett-Packard Company UNIX® is a trademark of The Open Group. PrintXchange® is a trademark of Xerox Corporation. All other product names mentioned herein may be the trademarks of their respective companies. Advanced Printing Software is based on Xerox PrintXchange technology developed and marketed by Xerox Corporation. Confidential computer software. Valid license from Compaq Computer Corporation, a wholly owned subsidiary of Hewlett-Packard Company, required for possession, use, or copying.
Contents About This Manual 1 Advanced Printing Software Overview 1.1 Terminology . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 1.1.1 Clients and Servers . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 1.1.1.1 Client Programs .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 1.1.1.2 Server Programs .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 1.1.
2.1.3.2 2.1.3.3 2.1.4 2.1.5 2.2 2.3 2.4 2.5 3 Local File Name Service .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Network Information Service . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . LDAP Name Service . . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Creating an LDAP Client Username and Password . . .. . .. . Creating or Modifying the apx.conf File . . .. . .. . .. . .. . . .. . .. . .. . .. . Protoserver Daemon ..
.3.6 5.3.6.1 5.3.6.2 Customizing the Advanced Printing Cluster Environment Relocating Resources . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Using the apx_caa_setup Script to Manage CAA Resource Profiles . . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 5.3.6.2.1 Displaying CAA Printing Resource Profiles . . .. . .. . 5.3.6.2.2 Creating a CAA Printing Resource Profile .. . .. . .. . 5.3.6.2.3 Modifying a CAA Printing Resource Profile . . .. . .. . 5.3.6.2.
.2.1.5 Setting the TCP/IP Port Number .. . .. . .. . .. . . .. . .. . .. . .. . 6.2.1.6 Using Unsupported Printers . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.2.2 Examples for Creating Physical Printers . .. . .. . . .. . .. . .. . .. . 6.2.3 Setting Optional Attributes for Physical Printers . .. . .. . .. . 6.2.4 Enabling a Physical Printer . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.2.5 Disabling a Physical Printer .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 6.
8 Document Data Filtering 8.1 8.1.1 8.1.2 8.1.3 8.1.4 8.1.5 8.2 9 Types of Filters . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Filter-Related Attributes . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Command Text Processing .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Invoking a Filter . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Error Handling .. . .. . .. . . .. . .. . .. . ..
12.2.1 PostScript Documents Print PostScript Program Code . .. . 12.2.2 Physical Printer Is Hung in Connecting State . . .. . .. . .. . .. . 12.2.3 Jobs Remain in Pending State . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 12.3 System Errors and Error Information .. . . .. . .. . .. . .. . . .. . .. . .. . .. . 12.3.1 Console Notification Does Not Work . .. . .. . .. . .. . . .. . .. . .. . .. . 12.3.2 Locating System Error Information . . .. . .. . .. . .. . . .. . .. . .. . .. .
10–3 10–4 10–5 10–6 10–7 11–1 11–2 11–3 11–4 11–5 C–1 C–2 C–3 C–4 C–5 C–6 C–7 C–8 C–9 C–10 C–11 C–12 C–13 C–14 C–15 C–16 C–17 C–18 C–19 C–20 C–21 C–22 C–23 C–24 C–25 C–26 C–27 C–28 C–29 C–30 Sun Protocol Extensions to Advanced Printing Software . .. . .. . DIGITAL Protocol Extensions .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . Xerox Protocol Extensions - DocuSP and DocuPrint to Advanced Printing Software . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. .
C–31 C–32 C–33 C–34 C–35 C–36 C–37 C–38 C–39 C–40 C–41 C–42 C–43 C–44 C–45 C–46 C–47 C–48 C–49 C–50 C–51 C–52 C–53 C–54 C–55 C–56 C–57 C–58 C–59 C–60 C–61 C–62 C–63 C–64 C–65 C–66 C–67 C–68 C–69 C–70 C–71 C–72 C–73 x Contents Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Prin
C–74 C–75 C–76 C–77 C–78 C–79 C–80 C–81 C–82 C–83 C–84 C–85 C–86 C–87 C–88 C–89 C–90 C–91 C–92 C–93 C–94 C–95 C–96 C–97 C–98 C–99 C–100 C–101 C–102 C–103 C–104 C–105 C–106 C–107 C–108 C–109 C–110 C–111 C–112 C–113 C–114 C–115 C–116 Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet:
C–117 C–118 C–119 C–120 C–121 C–122 C–123 C–124 C–125 C–126 C–127 C–128 C–129 C–130 C–131 C–132 C–133 C–134 C–135 C–136 C–137 C–138 xii Contents Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Printer Data Sheet: Print
About This Manual This manual describes how to configure and administer Advanced Printing Software on systems running the HP Tru64 UNIX operating system. Audience This manual is intended for system administrators or print system operators. Administrators should have knowledge of the operating system concepts and commands and the hardware and software configuration of their systems. Related Software Advanced Printing Software features PrintXchange technology developed and marketed by Xerox Corporation.
Chapter 10 Describes how to configure and manage an LPD inbound gateway. Chapter 11 Describes how to configure and manage an LPD Outbound Gateway. Chapter 12 Describes common problems that might be encountered with Advanced Printing Software. Appendix A Provides a brief description of the settable object attributes. Appendix B Describes the format of the ONC binding entries used by the naming services. Appendix C Contains the printer data sheets for the supported printers.
/usr/doc/readers_comment.txt Please include the following information along with your comments: • The full title of the manual and the order number. (The order number appears on the title page of printed and PDF versions of a manual.) • The section numbers and page numbers of the information on which you are commenting. • The version of Tru64 UNIX that you are using. • If known, the type of processor that is running the Tru64 UNIX software.
1 Advanced Printing Software Overview Advanced Printing Software is a flexible, distributed, client/server print system for the Tru64 UNIX operating system. This print system includes the following features: • A set of client and server programs that work together to manage and perform print-related functions. • A set of tools for administrators and operators to manage printing in a network environment. • Utility programs for end users to print their documents and monitor their print jobs.
1.1.1.1 Client Programs Client programs allow users to initiate print, list, and system administration operations. Upon receipt of a request, a server performs the operation and sends a result back to the client. Depending on the request, the result could be a simple acknowledgment, an error code, or a set of requested information, such as a formatted list of print jobs.
• Queue • Job • Document • Initial-value-job • Initial-value-document Some attributes are assigned values by the system when you create an object. Many of those attributes are read only; you cannot set their values. Other attributes, those that can be defined or modified by you and other print system users, are called read-write attributes. The print system supports a great number of attributes; however, you need not be familiar with all of them.
• Remove job • Resubmit job • List job queue • Modify job • Promote job Some operations are intended for use by end-users, while others are intended solely for administrative purposes. Most operations apply to only certain objects, while some apply to all. For example, administrators use the create operation to create new printers, queues, and initial-value objects. Users create jobs and documents by using the print operation.
1.1.5 Documents and Jobs Documents are files that users print. Some documents are formatted in a printer language, such as PCL or PostScript, by an application or by a printer driver. They can also be simple text files with little or no formatting information. A request to print one or more documents creates a job in the system. The print system assigns the job and its documents unique identifiers that are used for tracking and management.
the printing software. For example, you need to set the sides-supported and sides-ready attributes of a physical printer so that users can print two-sided documents . Physical printers, logical printers, spoolers, and supervisors treat supported and ready attributes as described in the following list: • Physical printers have both xxx-supported and xxx-ready attributes.
In addition to the objects mentioned, each server database holds a server object that it uses to store attributes that describe the server, such as its name, whether it is a supervisor or spooler, the names of printers and queues it supports, and so forth. 1.1.10 User Classes and Access Control To place limits on which users are permitted to manage the Advanced Printing Software, the print system defines distinct classes of users and the operations that each class can perform.
1.2.1.1 End-User Interface The CLI accesses all print, list, and job removal programs that end users access. In addition to the CLI, end users can use the pdprint and pdprintinfo GUI interfaces to perform these functions. The installation procedure integrates the pdprint and pdprintinfo GUIs into the CDE desktop, making them the default print and print information actions. 1.2.1.
Clients make requests to submit print jobs to named printers. The spooler puts the job in a queue associated with the printer and applies initial-value-job and initial-value-document attributes to the job and its documents, respectively. The spooler stores the job’s document files in a spool directory, where it is accessed by or delivered to a supervisor. When the associated physical printer is ready to accept the job, the spooler transfers the job to the supervisor for printing. 1.2.2.
The notification server distributes notification messages issued by spoolers and supervisors. It is responsible for sending e-mail or displaying messages on the GUI message areas when significant events occur. The console notification daemon, pdconntf, is required when you want notification messages to appear in the CDE system console window. Only one copy of each of these daemons runs on a host at a time.
2 Planning an Installation A successful Advanced Printing Software installation requires careful planning.
printers to facilitate cabling but run the spooler on a server host elsewhere in your building or site. When you use more than one host to run print system components, you need to distribute the names of the objects you create to all hosts that use them. 2.1.
printer that always prints text documents one-up in portrait mode, and another that prints such documents two-up in landscape mode with line numbers. By associating each of these logical printers with one queue, the system directs the documents submitted to the one or more physical printers associated with that queue. Fan-in and fan-out queues can be used together to provide a high degree of flexibility and convenience. 2.1.
2.3 Event Notification The print system architecture provides methods for notifying end-users, operators, and administrators when events occur in the printing system. See Chapter 9 for more information. 2.4 Security Security features can be used to control access to job data and management functions. These features perform authentication and authorization checks on every operation request to ensure that only authorized users obtain access to Advanced Printing Software.
Refer to Chapter 5 for information on creating and configuring servers. Refer to Chapter 11 for information on creating and configuring the LPD Outbound Gateway. 2. Create and configure queues and printers. Refer to Chapter 6 for information about creating and configuring logical printers, physical printers, and queues. 3. Set up name service. Refer to Chapter 3 for more information on setting up the naming service that you will use to support your system. 4. Set up security.
3 Managing the Name Space The name space contains the names and network addresses of the objects (spoolers, supervisors, logical and physical printers, and queues) that you create. The name service entry for each object contains information that includes the address of the server that supports it. Clients and servers use the name service to locate and bind to the server that supports a specified network object.
# # Local namespace datafile for Advanced Printing Software # bulldog_sup:\ :saddr=bulldog.gandalf.xyz.com,105004,1,sys,sv,bulldog_sup,1: bulldog_spl:\ :saddr=bulldog.gandalf.xyz.com,105004,1,sys,sl,bulldog_spl,1: bulldog1:\ :paddr=bulldog.gandalf.xyz.com,105004,1,sys,pp,bulldog_sup,1: bulldog_q:\ :qaddr=bulldog.gandalf.xyz.com,105004,1,sys,qu,bulldog_spl,1: bulldog_log:\ :paddr=bulldog.gandalf.xyz.com,105004,1,sys,lp,bulldog_spl,1:\ :spooling-type=dpa: cc3:\ :paddr=bulldog.gandalf.xyz.
NIS requires a coordinated update of configuration changes. That is, you must add an object name to the NIS file before you create the print system object. However, unlike the Local File Name Service where you have to update the local file in each of multiple hosts, you need to update data in only one place with NIS. To distribute the names and locations of printers, servers, and queues to hosts that are set up as NIS clients, gather one or more printers.
This command produces output similar to the following; one line of information for each server, printer, and queue listed in the master map: WS_sharie_PP:paddr=wstent.gandalf.xyz.com,105004,1,sys,pp,wstent_sup,1: ws_lg_queue:qaddr=wstent.gandalf.xyz.com,105004,1,sys,qu,wstent_spl,1: WS_cross_PP:paddr=wstent.gandalf.xyz.com,105004,1,sys,pp,wstent_sup,1: WS_cress_PP:paddr=wstent.gandalf.xyz.com,105004,1,sys,pp,wstent_sup,1: wstent_sup:saddr=wstent.gandalf.xyz.
# cat /etc/printers.conf printers.conf.NIS > printers.conf Reconcile the entries in the resulting printers.conf file by removing duplicates and stale entries, and then use the Makefile.printers file to update the map as described in the previous procedure. 3.3 LDAP Name Service The LDAP Name Service offers an advantage over NIS by dynamically updating the name space when print objects are created or deleted. This section describes what is required to set up the LDAP client. To set up the LDAP client: 1.
LDAP_path = ou=organizational unit,o=organization • name-services – Describes the name services the print system uses and the order in which they are used. In this example, local file, NIS, and LDAP are used. Lookups for print objects are done in the local file (/etc/printers.conf), in the printers.conf.byname NIS map, and then in the LDAP directory server. • LDAP_hosts – Lists up to three hosts on which the LDAP directory services are running.
3.4.1 Protoserver Daemon The protoserver is a print system daemon that works with the name services to enable a server process to access name and binding information of print system objects. The protoserver is the primary RPC server in the print system. Clients and servers on remote hosts contact the protoserver on a server host to determine the RPC binding information for other print system server processes. The print system installation procedure adds a line to the /etc/inetd.
4 Managing Security This chapter describes the options available to implement a security policy on Advanced Printing Software. Security options protect against unauthorized access to administrative functions and protect print jobs and print data from being accessed, copied, rerouted, or deleted by unauthorized users. This chapter describes the following security features: • System Security (Section 4.1) — Provides an overview of the security features and a description of how security works.
4.2 Authorization Advanced Printing Software authorization is based on associating a user with a privilege level. There are three user levels defined for print system users: • End user — A user that only prints through the print system. This is the least privileged user. • Operator — A user that controls the printers in a facility. Operators have privileges that allow them to pause and resume printers and servers, requeue jobs, and shut down servers.
• Enable or disable a server, queue, or printer. • Pause or resume a server, queue, physical printer, or any job. • Promote a job. • Set or modify xxx–ready attributes. • Shut down a spooler or supervisor. 4.2.3 Administrator Operations Some print system installations might not have operators, but instead might have only end users and administrators. In these cases, the administrators perform the day-to-day print and job management functions.
Table 4–1: access-control-list Attribute Fields (cont.) Field Description netgroup privilege-level Type of access level: end-user operator administrator Table 4–2 shows the properties of the name field of the access-controllist attribute and gives their meanings. Table 4–2: Name Field Properties Property Description name=name The named user from any client host in the domain. name=name@host The named user from the saved name within the server’s DNS domain.
Table 4–3: access-control-list Attribute Name-Type Field Properties (cont.) Property Value of Name User Affected name-type=group name is a valid group on the server All users who are members of the named group. The server looks up the user name associated with the request in the group map or file (as specified in /etc/svc.conf) and verifies that the user is a member of that group. name-type=netgroup A valid netgroup All users who are members of the named netgroup.
red_spl • Use the following command line to remove operator jones from a supervisor ACL: # pdset -c server \ -x a-c-l-="{name=jones name-type=user \ privilege-level=operator }" blue_sup Perform the following steps to create or modify an ACL using the pdprintadmin GUI:: 1. From the Tools menu, choose User Administration. 2. From the Components box, select a spooler or supervisor server. 3. From the Users box, select the User Class you want to add: Administrator, Operator, or Normal User. 4.
5 Creating and Managing Servers This chapter describes how to create and manage Advanced Printing Software spoolers and supervisors. The chapter is divided into the following sections: • Creating Servers (Section 5.1) – Describes the steps you need to perform to create servers for your print system. • Configuring Server Object Attributes (Section 5.2) – Describes the attributes that can be set on the servers. • Configuring Servers in a TruCluster Environment (Section 5.
5.1.1 Creating an Object Database Use the pdmakedb command to create an object database. You must create an object database before you can start the server process. The pdmakedb command creates an object database that initially contains a single object, the corresponding server object. The name of the database is also the name of the server object. Note the -n option. The command adds default attributes to the server object, plus any attributes you specify by using the options.
-v Prints messages as it validates attributes provided on the command line. The pdmakedb command provides a default value for any option that you do not specify on the command line. The following examples show how to use pdmakedb to create spoolers and supervisors. You must create object databases from the root account. When you need to add users to the ACL, you can use the methods described in the Section 4.3 of this book.
-n serverName Specifies the name of the object database and the corresponding server. 5.1.3 Modifying an Existing Object Database Use the pdmoddb command to modify an existing object database. This command modifies the attributes you specify on the command line if the attribute already exists in the database. If the specified attribute does not exist, the pdmoddb command creates the attribute and assigns the specified value.
-v Prints messages as it validates attributes provided on the command line. 5.1.4 Backing Up Object Databases You should make routine backups of your print system object databases to protect against inadvertent data loss or data corruption. If a failure occurs and your object databases become inaccessible or corrupt, you can restore the system from a recent backup and avoid the need to recreate your print system environment from scratch.
Table 5–1: Server Object Attributes (cont.) Attributes Description job-attributes-visibable-to-all Lists job and documentation attributes that are visible to nonowners of the job with the pdls and pdq commands. message A test string indicating the sate of the server. notification-profile Specifies the events for users notification and specifies the notification method. job-completion-period Specifies the amount of time the spooler maintains job objects after jobs are completed and retained.
command line sets, as visible, those attributes that are required to have pdls display the job owner, job size, and the submission time of the job: # pdset -c server \ -x job-attributes-visible-to-all+="job-owner submission-time \ total-job-octets" \ blue_sup • To add the user smith to the list of approved operators on the supervisor blue_sup, use the following command line: # pdset -c server -x "access-control-list+=\ {name=smith name-type=user privilege-level=operator}" blue_sup 5.
profile representing servers and supervisors that are created in your print environment. Any spooler or supervisor that you create is placed in the apx-default resource. You can create additional resource profiles and move spoolers and supervisors from the apx-default resource profile into them. 5.3.2 apx-default.
/usr/pd/scripts/pd_get_started script or the pdmakedb, pdsplr, and pdspvr commands. When the new server is created, it becomes a part of the apx-default resource profile. 5.3.6 Customizing the Advanced Printing Cluster Environment You can customize your CAA print environment by relocating resource profiles, creating new resource profiles, and modifying and deleting resource profiles. The following subsections describe these topics. 5.3.6.
• Initialize CAA printing resource profile The following shows the main menu of the apx_caa_setup script: Advanced Printing Software Cluster Setup *** MAIN MENU *** 1 Display CAA printing resources 2 Create CAA printing resource 3 Modify CAA printing resource 4 Delete CAA printing resource 5 Initialize CAA resources for Advanced Printing 6 Exit Enter the number that corresponds to your choice:[6] 5.3.6.2.
supervisors from the apx-default resource profile.
apx-default: daffy_spl daffy_sup Modify which resource? 3 Modify CAA map entry "orange"? ([y]/n) Enter the names of one or more Advanced Printing spooler or supervisors to be associated with the resource "orange": orange: orange_spl orange_sup blue_spl blue_sup Modifying resource orange... 5.3.6.2.
spoolers and supervisors running. - Deletes resource profiles and action scripts associated with printing resources defined in the /var/pd/config/apx_caa_map.conf file. - Creates a new, empty /var/pd/config/apx_caa_map.conf file. - Registers the apx-default resource. Do you want to initialize anyway? (y/[n]) 5.3.7 Configuring a Printer to Run on One Member Some printers are directly connected to the serial or parallel port of a host. These printers must be controlled by a supervisor running on that host.
The /sbin/init.d/apx start and /sbin/init.d/apx stop commands start and stop the LPD Inbound Gateway. 5.4 Managing Servers This section describes the administrative tasks that you perform on spoolers and supervisors. These tasks include starting and stopping, pausing and resuming, enabling and disabling, and possibly deleting servers. 5.4.1 Server States The server attributes server-state and enabled determine the state of a server process.
server starts up in the background and runs relative to a runtime directory. When you start a spooler or supervisor, you must do so from the root account. 5.4.3 Starting a Spooler The command syntax for starting a print system spooler is: /usr/pd/lib/pdsplr [-a] [-c] [-d ODBpath] [-e emailAddress] [ serverName] -a Rquired only for server startups taking place after the server had to repair the object database as part of a crash recovery.
/usr/pd/lib/pdspvr [-a] [-c] [-d ODBpath] [-e emailAddress] [ serverName] -a Required option for a server startup taking place after the server had to repair the object database as part of a crash recovery. -c Forces a database integrity check at startup after a normal shutdown. You might want to use the -c option if you suspect that the database is corrupt. (The server automatically checks the database integrity when it restarts after a crash.
-m message text Allows you to include a message when the server is enabled. The message can be retrieved with a pdls command. The following example shows how to use the pdenable command to enable a spooler (red_spl): # pdenable -c server red_spl 5.4.7 Disabling a Server Use the pddisable command to disable a server. When a spooler is disabled, all previously submitted jobs are scheduled and delivered to physical printers, while all requests for new jobs are rejected.
5.4.8 Removing Jobs from a Server There are two commands available to remove jobs from a server; pddelete and pdclean. The pdclean command removes all jobs on a server. The pddelete command removes one or more named jobs from a server. 5.4.8.1 Removing Named Jobs from a Server Use the pddelete command to delete one or more named jobs from a server. pddelete -c job job_id The following example shows how to use the pddelete command: Delete job 155 on spooler blue_spl: # pddelete -c job blue_spl:155 5.4.8.
5.4.9 Pausing Spoolers Use the pdpause command to pause a spooler. A supervisor cannot be paused. When a spooler is paused, it will not submit jobs to supervisors, but the logical printers associated with the spooler continue to accept new jobs. The pdpause command has the following syntax: pdpause -c server [-m message_txt] [-x extended_attribute_string] [-X attribute_filename] server_name -m message_txt Allows you to include a message when the server is paused.
5.4.11 Shutting Down a Server Use the pdshutdown command to shut down a server process. Both spoolers and supervisors disable themselves when this command is issued and then shut down by the method specified by the value of the when_time option. The shut down operation is asynchronous. Do not use pdshutdown in scripts unless the scripts use other commands to monitor the commands progress.
5.4.12 Deleting a Server Use the pddelete command to delete a server. When you delete a server, you should consider the following: If the server is a spooler: • The server must be disabled and all jobs currently on the spooler must be deleted. • Supervisors set the associated-queue and printer-associatedprinters attributes to empty on all physical printers associated with the spooler.
6 Creating and Managing Queues and Printers This chapter describes: • Creating and managing queues (Section 6.1) • Creating and managing physical printers (Section 6.2) • Creating and managing logical printers (Section 6.3) • Specifying job defaults and creating default objects (Section 6.4) For detailed descriptions of the commands used in this section, refer to the Advanced Printing Software Command Reference Guide. 6.
• The following command creates the queue named production_q and associate it with the spooler named red_spl: # pdcreate -c queue red_spl:production_q 6.1.1 Enabling a Queue Use the pdenable command to enable a queue. When you enable a queue, the queue accepts print jobs. The pdenable command has the following command-line syntax: pdenable -c queue [-m message text] [-x extended_attribute_string] [-X attribute_filename] queue_name 6.1.2 Disabling a Queue Use the pddisable command to disable a queue.
6.1.5 Setting Limits for Queue Backlog Events You can set the limits at which the queue is considered backlogged and not backlogged. You can also control whether the spooler disables and enables a queue when the number of jobs reaches these limits. By setting the queue-backlog-upper-limit attribute and the queue-backlog-lower-limit attribute, you specify the number of pending jobs in a queue that causes an event to be delivered. When the upper limit number is reached, you receive a notification message.
queue-name ---------production_q • logical-printers-ready physical-printers-ready ---------------------- ----------------------colorPS hpcolorPS To list all of the attributes of the queue mail_q, use the following command: # pdls -c queue -r all -s line mail_q This command produces the following output: mail_q: mail_q: mail_q: mail_q: mail_q: mail_q: object-class = queue queue-name = mail_q associated-server = red_spl enabled = no availability = none state = ready 6.
• printer-connection-method — Serial, parallel, ip-socket, bsd, or digital-printserver connections are supported The printer attribute files include default values for the printer-model, printer-connection-level, and printer-tcpip-port-number attributes. You can include values for the other attributes when you create the physical printer, or you can set or modify the values after you create the printer. 6.2.1.
6.2.1.2 Setting the Printer Connection Method Printer hardware can be attached to a supervisor host in several ways. Desktop and mid range printers typically have one or more connectors on the back that allow them to be connected to their source of data such as a host, a terminal server, or a network. Such a connector, and the hardware it connects to, is called the printer interconnect.
6.2.1.3 Setting Printer Connection Level Some printers use more features that a connection offers than do others. For example, some printers provide status messages on a serial back channel while others do not. To provide support for a broad range of connection types, the print system uses the printer-connection-level attribute. The recognized values are 0 through 5, as listed in Table 6–2. Table 6–2: Printer Connection Level Values Value Description 0 None specified. Use system default.
set up the port in advance. If you do specify printer-baud-rate, the supervisor sets the other attributes to values you specified or to the values listed in Table 6–3, if the attributes are initially empty. Table 6–3: Serial Port Parameter Values Attribute Values Default Value printer-baud-rate 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 Uses the physical port settings.
The generic files do not specify network port information. If the printer has a network connection, set the printer-connection-level, printer-connection-method, and printer-tcpip-port-number attributes and specify the printer-address. See for information on how to set the printer-address.
Note that the printer data sheet for the Lexmark 4039 10plus Level 2 PS printer lists large-capacity as an optional input tray. Because it is optional, the printer attribute file does not include the value for the input-trays-supported and input-trays-ready attributes. You must add the value for the optional tray to the attributes to make the tray available for your site. The example shows that you can add the value during the create operation.
Use the pdenable command to enable a physical printer. When you enable a physical printer: • The queue named in the associated-queue attribute must already exist. • The printer is added to the physical-printers-ready attribute for the supervisor, spooler, and queue.
• The output device stops printing as soon as possible. • The spooler associated with the printer does not schedule new jobs while the printer is in the paused state. If the printer is not printing when paused, it still requires a resume operation (pdresume) to start printing again.
• If the specified printer is the only physical printer associated with a queue, the spooler stops scheduling jobs in that queue until it is associated with another physical printer. The pddelete command has the following command-line syntax: pddelete [-c class_name] [-x extended_attribute_string] [-X attribute_filename printer_name] The following example shows how to delete the printer, hpcolorPS: # pddelete hpcolorPS 6.
6.3.1 Example for Creating a Logical Printer The following example shows how to create the logical printer doc2 with the associated queue production_q on the spooler red_spl. # pdcreate -c printer \ -x "associated-queue=production_q" red_spl:doc2 6.3.2 Setting Optional Logical Printer Attributes A number of attributes can be set to realize the maximum capabilities of your printers.
The pdenable command has the following command-line syntax: pdenable [-c printer] [-m message_txt] [-x extended_attribute_string] [-X attribute_filename printer_name] The following example shows how to enable the logical printer log_printer_1 on the default server. #pdenable log_printer_1 6.3.3.2 Disabling a Logical Printer Use the pddisable command to disable a logical printer.
lpx0001: printer-associated-printers = px3 pr1 lpx0001: printers-ready = px3 pr1 • To display only the associated-queue attribute for logical printer lpx0001, issue the following command: #pdls -c printer -r associated-queue lpx0001 associated-queue ----------------px0001 6.3.3.4 Displaying Jobs Submitted to Logical Printers Use the pdq command to generate a list of jobs that have been submitted to a logical printer.
• To display a brief list of the attributes of jobs submitted to lpx0001 issue the following command. # pdq -p lpx0001 -r brief -s line amanda:16: job-identifier = amanda:16 amanda:16: job-name = voicemail.txt amanda:16: current-job-state = processing amanda:16: intervening-jobs = 0 amanda:16: printer-name-requested = lpx0001 amanda:16: printers-assigned = pr1 amanda:19: job-identifier = amanda:19 amanda:19: job-name = net.Form.
• initial-value-document, which contains document attributes with default values The default values reflect capabilities of the physical printer that is the intended destination of a job. Therefore, you should first create the physical printer and set the desired printer attributes before creating the initial-value-job and initial-value-document objects.
JobDefaults1 the printed output includes start sheets for jobs. This might be the typical case and you might therefore associate JobDefaults1 to the relevant logical printer: # pdset -c printer \ -x ’printer-initial-value-job=JobDefault1’ \ [spooler_name:]logical_printer_name However, you might be aware that there would be times when start sheets might not be desired, so you create initial-value-job object JobDefaults2 with the attribute job-sheets=none.
The pdprintadmin GUI application provides access to the default settings of a logical printer. You can create initial-value-job and initial-value-document objects through the default settings if the logical printer does not already have initial-value-job and initial-value-document objects applied to it.
printer’s programming documentation to find the escape sequences required and add them to a printer setup module. To create a printer setup module: 1. Create the printer setup file in a user directory. 2. Create a new directory and copy the printer setup file into it. For example, /usr/local/pd/setup. 3.
7 Managing Jobs and Documents You need to consider various aspects of jobs and documents to be able to manage them properly in Advanced Printing Software. Generally, three types of attributes reflect the different aspects of job and document management: • Attributes that affect the job or document object itself without regard to the data that is to appear on the printed output. These attributes include setting the input and the output trays to be used on the print device.
For a detailed description of the commands discussed in this chapter, refer to the reference page for the command. 7.1.1 Printing a Job A print operation creates the job object and the document objects from your print request to print one or more files. The spooler creates a job object for each print request and a document object for each file a user specifies as part of a single print request. A job object, therefore, contains one or more document objects.
You might want to specify a print date and time for a large job so that it prints during a low print volume period. To specify a date and time, use the following syntax: dd:mm:yyyy:hh:mm:ss When you set a print date and time for a job, the spooler: • Sets the current-job-state attribute to held. • Adds the job-print-after-specified value to the attribute job-state-reasons. When the specified print date and time has passed, the spooler schedules the job and changes current-job-state to pending.
The following examples show how to use the pdls command to display job attributes and values: • To lists the printer attributes of printers lab200 and mimi: # pdls -c printer lab200 mimi • To list all queues on the default spooler: # pdls -c queue • To list the job and document attributes for job status on spooler blu_spl: # pdls -c job -x "scope=1" blu_spl:status 7.1.
7.1.5 Modifying Job and Document Attributes You can use the pdset and the pdmod commands to modify job and document attributes. The pdset command sets, adds, or removes values of writable attributes of printers, queues, servers, jobs, documents, and initial-value objects. Changes you make to the attribute values of an object are persistent; they remain in place even after the system is restarted. The specified attribute values will be set for every object you include as a command operand.
The job you are modifying does not lose its position in the queue; however, a resource check of the entire job or document attributes takes place again if you resubmit the print job. The pdmod command has the following syntax: pdmod [-g] [-m message_text] [-n copies] [-N notification_method] [-r requested_attributes] [-s style_name] [-t job_name] [-x extended_attribute_string... ] [-X attribute_filename... ] [ server_name: ] job_id [ .
7.1.7 Resubmitting a Job You can resubmit a submitted job for printing to a different printer on the same spooler. A job must be in any of the following states to be resubmitted: • Pending • Held • Paused • Retained • Terminating (provided the state does not contain documents-needed for the job-state-reasons attribute) You cannot resubmit a job whose state is completed, processing, or printing. The pdresubmit command has the following syntax: pdresubmit logical_printer_name job_id [ job_id2]...
Note that the pdresubmit command is asynchronous. The command returns a prompt before the server completes the operation. 7.1.8 Promoting a Job You can move a job to the front of the queue. The job will be printed before jobs that have not been promoted, regardless of submission time. While you can promote only one job at a time, promoting several jobs in the same queue causes the most recently promoted job to be printed first.
# pdpause -c job -m "Job will be printed later"\ spooler1:11224 7.1.10 Resuming a Job You can resume paused jobs with the pdresume command. When you resume a paused job, the job becomes available for scheduling and printing. The pdresume command has the following syntax: pdresume -c class_name [-m message_text] [ server_name:] job_id The following example shows how to use the pdresume command: • To resume job 11224: # pdresume -c job spooler1:11224 7.1.
# pdset -x ’job-hold=no’ sx0001_spl:2002 # pdmod -x ’job-hold=no’ sx0001_spl:2002 7.1.12 Retaining a Job You can cause the spooler to retain a job for a specified period after the job completes printing. A retained job is available for possible resubmitting or examination. When you retain a job, the spooler: • Retains the job object, its attributes, and its documents, even after the job has completed. • Sets the current-job-state attribute to retained.
• To discard job 3021 at 5:00 p.m. on January 2, 2002 enter one of the following commands: # pdmod -x "job-retention-period=02:01:2002:17:00:00" 3021 # pdset -c job \ -x "job-retention-period=02:01:2002:17:00:00" 3021 7.1.
• Send e-mail notification when the semantics.txt file completes printing: # pdpr -N email semantics.
8 Document Data Filtering Often, document data needs to be modified before it can be printed. For example, simple text documents need to be translated into PostScript before they can be printed on a PostScript printer. Or, documents using the EBCDIC character set might need to be converted to the ASCII character set before they can be printed on common desktop printers.
There is no difference in how the two types of filter programs are written, and the supervisor does not verify that they are used properly. Both modification and translation filtering can be applied to a document. When this occurs, the modification filter receives the original document data, the output of the modification filter is piped to the translation filter, and the output from the translation filter is sent by the supervisor to the printer.
Field Value Description output-format Document format The document format the filter produces on output. command text The command that the server executes to invoke the filter. To use a filter, it must be defined in the supervisor. An administrator defines filters by setting the filter-definition attribute with the pdset command.
filtering. The print system does not verify that the filter specified is known to the supervisor when the document is submitted. translation-filter Document Attribute Users can specify the translation-filter document attribute to override the automatic invocation of a translation filter when more than one filter is available that can perform the specified translation.
no value and a default value is not specified, the supervisor replaces #{...} with an empty string. Examples: 1. "-N${number-up,0}" Evaluates to "-N2" if number-up has the value "2". 2. "-N${number-up,0}" Evaluates to "-N0" if number-up is not defined. 3. "${number-pages,,-P}" Evaluates to "-P" if number-pages is defined, but to an empty string ("") if number-pages is not defined.
Table 8–1: Document Attributes Used in Command Substitution Fields Attribute Name Syntax Description bottom-margin Integer Distance, in characters, between bottom edge of page and bottom of text area. content-orientation Oid Portrait or landscape. default-character-set NameOrOid The character set name of the document. default-font Text A font name. default-medium Oid-name or Text Requested media name. document-format Oid The document’s page description language.
For example, if the command for a translation filter is /usr/pd/my-filter -d${document-format} and the command for a modification filter is /usr/pd/your-filter -o${content-orientation} -n${number-up} and a user requests modification and translation, a child process would be executed with a command such as the following: /usr/pd/my-filter -simple-text|/usr/pd/your-filter -oportrait -n2 8.1.
job-state-message attribute, and through an error page that is printed on the target physical printer. When an error occurs, the job is put into the retained state on the spooler. 8.1.5 Creating a Filter Program Filter programs must adhere to the following rules: • The program must read from stdin. • The program msut write only document data to stdout. No error messages or other messages are allowed. • The program must not emit printer control strings.
${top-margin,,-a${top-margin}} \ ${bottom-margin,,-b${bottom-margin}} \ ${left-margin,,-c${left-margin}} \ ${right-margin,,-d${right-margin}} -l \ ${length} -w${width} \ ${number-pages,,-P} \ ${repeated-tab-stops,,-t \ ${repeated-tab-stops}}" }’ red_sup The rules of substitution described in Table 8–2 are applied in the following example.
Table 8–2: Text-to-PostScript Translator Command Options (cont.) Option Corresponding Attribute Description -l document-length Lines per page, the number of rows to be printed on a page before a new page is started. Valid values: Integer > 0 -N number-up The number-up value that specifies the number of page spots to be printed on the physical sheet.
Table 8–2: Text-to-PostScript Translator Command Options (cont.) Option Corresponding Attribute Description -t repeated-tab-stops Tab width value that expands tabs to byte positions number+1, 2*number+1, 3*number+1, and so on. The default value of number is 8. Tab characters in the input expand to the appropriate number of spaces to line up with the next tab setting.
9 Setting Event Notification Advanced Printing Software reports system problems and events through notification services. Notification services deliver messages by electronic mail or to the system console. The notification-profile attribute specifies the events that are reported as well as the delivery method of the reports.
9.3 Notification Event Classes You can specify events individually or by a class of events. When a notification-profile attribute specifies a class, the notification server reports all events of that class. The following classes of events are supported: • aborted — A job was stopped, cancelled, or aborted.
9.3.2 Queue Notification Events Class Event Message report report-queue-clean-complete The queue has completed a clean operation. report-queue-clean-aborted The queue has aborted a clean operation. report-queue-resubmit-aborted The queue has aborted a resubmit operation. report-queue-not-backlogged The queue is no longer backlogged. state-changed state-changed-queue The state of the queue has changed. warning warning-queue-backlogged The queue is backlogged. 9.3.
Class Event Message report report-file-transferred The file transfer for the job has been completed. report-job-completed The print job has completed successfully. report-job-discarded The print job has been discarded. report-job-promoted The print job has been promoted. report-job-resumed The print job has been resumed report-processing-started The server has begun processing the job. state-changed state-changed-job The state of the job has changed.
10 LPD Inbound Gateway Client Daemon The Inbound Gateway client daemon allows users to submit print requests using lp and lpr commands to print system printers. In addition, the LPD Inbound Gateway client daemon also allows applications and PC integration software access to Advanced Printing Software even if they are only capable of printing to the LPD based printing system. 10.
it allows users to submit print jobs using either the lpr or lpd client or Advanced Printing CLI and GUI clients. To direct incoming lpd print jobs to Advanced Printing printers, you must create printcap entries on the print server host that associate LPD printers (specified with the lpr requests) with Advanced Printing logical printers. Such printcap entries declare the printer as a gateway printer.
10.2 Cancelling Advanced Printing Jobs When you use the lpq command to view jobs on a gateway printer, the output shows you all jobs queued to the printer, regardless of whether they were submitted through the gateway. In the output from the lpq command, a job entry number of 000 indicates that the job is a native Advanced Printing job, one that was submitted using the pdpr command or the pdprint GUI, not an LPD job. You cannot cancel native Advanced Printing jobs with the lprm command.
Table 10–1: LPD to Advanced Printing Software Job Mapping Usage Description lpr Option lp Options Print System Attribute C(ClassName) Class name: (banner) (job) -C None job-comment H(Hostname) Host submitting job: 1(job) None None job-originatinghost J(Jobname) Name of job: (banner) (job) -J -t job-name M(user) User to mail when done: (job) -m -m notificationprofile N(name) source of data None file: (file) None document-name P(name) requesting user: (job) None None job-origi
Table 10–2: LPD to Advanced Printing Software Print Message Mapping Usage Description lpr Option lp Option Print System Attribute c(file) Print/plot as CIF data -c -T cif document-format d(file) Print as DVI data -d -T dvi document-format f(file) Print as ASCII (none) -T ascii document-format g(file) Print as plot data -g -T plot document-format l(file) Print converting non-printables -l -y catv_filter document-format -o nofilebreak n(file) Print as ditroff output -n -T ditrof
Table 10–3: Sun Protocol Extensions to Advanced Printing Software CF Key Description lpr Option lp Options Print System Attribute O(option_list) For SVR4 LP -o option None -o option_list Ignored 5(opt)(value) For SVR4 LP features None Not an option 5f(form) For SVR4 Forms None -f form_name 5H(handling) For SVR4 Handling None -H -f form_name Ignored 5p(method:end) For SVR4 Notification None -p Ignored 5P(pagelist) For SVR4 Pages None -P page_list page-select 5q(priority) For
______________________ NOTE ______________________ Xerox extensions that are not supported by the Advanced Printing Software are listed as (no mapping) in the Print System Attribute column of the following table. Any jobs that are submitted specifying these unsupported extensions will not print. The user that submits a job using an unsupported extension receives a mail message stating that the option selected is not supported and therefore the job did not print.
Table 10–5: Xerox Protocol Extensions - DocuSP and DocuPrint to Advanced Printing Software (cont.
______________________ NOTE ______________________ Xerox extensions that are not supported by the Advanced Printing Software are listed as (no mapping) in the Print System Attribute column of the following table. Any jobs that are submitted specifying these unsupported extensions will not print. The user that submits a job using an unsupported extension receives a mail message stating that the option selected is not supported and therefore the job did not print.
Table 10–6: Xerox Protocol Extensions to Advanced Printing Software- DocuSP Only (cont.
Table 10–6: Xerox Protocol Extensions to Advanced Printing Software- DocuSP Only (cont.
______________________ NOTE ______________________ Xerox extensions that are not supported by the Advanced Printing Software are listed as (no mapping) in the Print System Attribute column of the following table. Any jobs that are submitted specifying these unsupported extensions will not print. The user that submits a job using an unsupported extension receives a mail message stating that the option selected is not supported and therefore the job did not print.
Table 10–7: Xerox Protocol Extensions to Advanced Printing Software - DocuPrint Only (cont.
11 LPD Outbound Gateway Supervisor The LPD Outbound Gateway supervisor, pdspvlpr, transfers print job requests to remote servers and printers using the Line Printer Daemon (LPD) protocol. To do this, it converts Advanced Printing Software jobs and their attributes to an LPD request and sends the request to a specified LPD server.
11.2 Creating a Physical Printer The LPD supervisor supports the bsd printer connection method. For each print system physical printer object you create, you need to specify the remote machine and the remote printer name of the LPD printer queue. The LPD supervisor needs to know the name of the printer to communicate properly with it. The supervisor uses the printer-address attribute to determine the name of the LPD printer.
• Media selecting , except when using the Xerox extensions on a Xerox DocuSP or DocuPrint printer. • Connection attributes, such as printer-baud-rate, printer-stop-bits, printer-data-bits, printer-parity, printer-input-flow-control, printer-output-flow-control, and printer-connection-level, are ignored by the LPD supervisor. The only valid value for printer-connection-method is bsd. 11.
Table 11–3: DIGITAL Protocol Extensions Print System Attribute Key Usage Description Default default-input-tray < <(tray) Input tray selection None -I (upper|lower|manual|...
Table 11–4: Xerox Protocol Extensions - DocuSP and DocuPrint (cont.
Table 11–5: Xerox Protocol Extensions - DocuSP Only Print System Attribute Key Usage Description Default lpr Option binding-edge= top-edge bottomedge left-edge right-edge C C" (bind=edge) " Binding edge, edge= top bottom left right None -C finishing= staple-bottom-left edge-stitch C C" (stitch=how)" Document stapling, how= None singlelandscape duallandscape -C output=no-pagecollate C C" (uncollate) " Collation None -C finishing=saddlestitch C C" (booklet) " Finishing None -C num
12 Troubleshooting This chapter describes some of the common problems that might be encountered in Advanced Printing Software and describes what steps can be taken to correct the problems. 12.1 Solving Server Problems This section contains descriptions of server errors that can occur during normal print system operation.
12.1.2 Servers Running But Nothing Works Use the procedure in Section 12.1.1 to determine which components are running, and which of those respond to the rpcinfo -u or -t commands. If the protoserver does not respond, perform the following procedure to restart the print system: 1. Verify that the /var/pd/pts directory is owned by nobody: # ld -ld /var/pd/pts 2. Kill all pdspvr, pdsplr, and pdspvlpr processes. # kill -9 3. Send a hangup signal to inetd process: # 4. kill -HUP ‘cat /var/run/inetd.
2. Make sure the server is not actively printing jobs to printers by verifying that the physical printers are not in the printing state. 3. Check for any paused jobs on printers. The supervisor will not shut down when jobs are paused unless you specify -w now with the pdshutdown command. 4. If you still cannot stop the supervisor process, determine the supervisor’s PID and use kill -9 to terminate it.
Re-issue the job and specify document-format=PostScript. 12.2.2 Physical Printer Is Hung in Connecting State If an output device cannot be accessed when a job is assigned to it, the physical printer object will remain in the connecting-to-printer state. There are several reasons for this: • The printer is busy printing other jobs. • The printer is off line. • The printer is powered off. • The network path to the printer is inaccessible.
12.3.1 Console Notification Does Not Work If you do not receive any notification messages on the console, or if mail notification messages are not being sent, determine if the console notification daemon, pdconntf, is running by performing the following steps: 1. Determine if the daemon is running: # ps aux | grep pdconntf 2. If it is not running, try running it from a terminal window: # /usr/pd/lib/pdconntf 12.3.
The following types of information are stored in the system log files: Advanced Printing Software servers report when an object is created, deleted, enabled, or disabled in the lpr.log file at the info level. Advanced Printing Software servers report errors in the lpr.log file at priority levels err, warning, notice, and alert. Command-line utilities, CDE GUIs, and the inbound gateway daemon report certain error and informational conditions in /var/adm/syslog.dated/current/lpr.log on their respective hosts.
A Attribute Descriptions This chapter describes the object attributes that can be read or set by end users, operators, or administrators of the print system. This chapter is organized by object. Each section describes the attributes that support a specific object. A.1 Server ObjectAttributes The following attributes are related to both supervisors and spoolers. access-control-list Specifies the privilege level of specified authorized print system users within and across domains.
job-completion-period Specifies the period of time that jobs on the server can be maintained and marked completed. Note that spool files are not maintained and completed jobs cannot be reprinted. locale Contains the locale specification that the server uses when performing internationalization tasks such as constructing error, notification, and logging messages. This attribute is set by the server from the locale environment variable.
server-hostname Contains the name of the server host. If the server is running on a cluster, this attribute holds the default cluster alias. server-name Identifies the name of the server. This attribute is set when the server is created. server-state Identifies the state of the server. The server states include ready, paused, and terminating. server-type Specifies the type of server. Server types include spooler and supervisor.
maximum-number-of- printers-supported will fail. printer-connection-methods-supported Indicates the means by which a printer can be attached to a server host. A.2 Printer Object Attributes associated-queue Identifies the queue associated with the printer. associated-server Identifies the name of the server with which the object is associated. The attribute is set by object when it is created. availability Indicates the general availability of an object.
enabled Indicates whether the specified object is enabled to accept print requests from clients. Objects are enabled or disabled with the pdenable or pddisable command. finishings-supported Identifies the per-document finishings supported on the printer. fonts-supported Identifies the font resources supported by the printer. highlight-colour-rendering-algorithms-supported Indicates the highlight color-rendering algorithms supported by the printer.
Valid values: none or 0, simple-1–up or 1, simple-2–up or 2, simple-4–up or 4. object-class Identifies the class of the specific object. output-bins-supported Identifies the output bins supported by the printer. Valid values: top, middle, bottom, side, face-up, left, right, large. Unlike several other xxx-supported attributes, you cannot add values to the output-bins-supported attribute using the CLI += operator. Nor can you remove individual items using the -= operator.
printer-multiple-copy-mode Enables making multiple copies of a document at the printer. This setting should be used only with printers that have a hard disk that can store the entire contents of a document. When set false, or not defined (the default), the supervisor sends document data to the printer for each requested copy. printer-name Unique name that identifies the printer. This attribute is set when the printer is created.
A.2.1 Logical Printer Object Attributes hold-jobs-interrupted-by-printer-failure Specifies whether jobs returned to the spooler after a restart should be placed in the held or pending state. Valid values: true or yes for the held state, false or no for the pending state. printer-initial-value-document Identifies an initial-value document object in the server for use on this logical printer. The printer’s initial-value document is used if the document does not specify an initial-value document.
finishings-ready Identifies the per-document finishings ready on this printer. Valid values: staple, staple-top-left, staple-bottom-left, staple-top-right, staple-bottom-right, staple-dual-left, saddle-stitch, edge-stitch, punch, cover-bind. fonts-ready Identifies the font resources ready on the printer. highlight-colours-ready Identifies the highlight colors ready on the printer. Valid values: red, blue, green, cyan, magenta, yellow, cardinal, royalblue, ruby, violet, or name.
printer-connection-level Identifies the level of connectivity supported by the printer. Valid values: 0 – Not specified (use system default), 1 – Output only (unidirectional ), 2 – Output only (status bits returned), 3 – Bidirectional (no synchronized session control), 4 – Bidirectional (synchronized session control). printer-connection-method Indicates how the printer is connected to the server host. Valid values: serial, parallel, ip-socket, digitalprinterserver, and bsd.
printer-timeout-period Identifies the period of time, in seconds, that a server waits for a response from a printer before setting printer-state to timed-out. sides-ready Indicates the value of sides ready for the printer. Valid values: 1, 2. A.3 Queue Object Attributes associated-server Identifies the server associated with the queue. This attribute is set when the queue is created. availability Indicates the general availability of the queue.
physical-printers-ready Identifies the associated physical printers that are enabled. physical-printers-supported Identifies the physical printers that are supported by the queue. queue-backlog-lower-limit Lower bound limit for backlogged queue. When the number of pending jobs decreases to match the specified value of the lower bound limit, the queue is declared not backlogged, and the report-queue-not-backlogged event is generated. queue-backlog-upper-limit Upper bound limit for backlogged queue.
document-sheets Specifies if the server inserts document start sheets at the beginning of each document of a job. Valid values: none and doc-set-start-copies-separate. initial-value-job Identifies an initial value job object to be used for attribute defaulting. The job initial value job supercedes a printer initial value job. intervening-jobs Indicates the number of jobs to be printed before a job is scheduled. It is set to 0 when the job is at the top of its queue.
job-message-from-administrator Provides a message intended to indicate to a user the reason for action taken on the job. job-name Provides a readable string for the print job intended to be printed on start sheets, notification, and logging. If the user does not specify a job name, the name of the first file is used. job-originating-host Provides an attribute used by the LPD Inbound Gateway and contains the name of the host that originated the job.
cancelled-by-user, cancelled-by-operator, aborted-by-system (cancelled-by-shutdown, printer-unavailable, wrong-printer, bad-job), logfile-pending, and logfile-transferring. job-submission-complete Indicates that all documents in a job have been submitted. notification-profile Specifies the job events for user notification and specifies the notification delivery method. number-of-documents Indicates the number of documents in a job. object-class Specifies the class as job.
A.5 Document Object Attributes additional-production-instructions Specifies lpd processing options that are not representable as attributes. Intended for use only by Inbound and Outbound Gateways. binding-edge Specifies the edge of the sheet that will be bound. Valid values: bottom-edge, right-edge, top-edge, left-edge. bottom-margin Specifies the distance, in characters, between the bottom edge of the logical page and the bottom edge of the text area when held in the intended reading orientation.
document-format Specifies the print format of the document. document-name Specifies a meaningful name for the document. The attribute is set by the client to be the file name or it can be set when the job is submitted to print. document-sequence-number Specifies the sequence number of a document within a job. document-state Identifies the state of a document. Valid values: transfer-pending, pending, processing, completed, printing.
initial-value-document Specifies an initial value document object to be used for attribute defaulting. The document initial-value-document superscedes a printer initial-value-document attribute. left-margin Specifies the distance, in characters, between the left edge of the logical page and the left edge of the text area when held in the intended reading orientation. length Specifies the length of the text area in characters.
Valid values: unknown, first-to-last, last-to-first. page-select Specifies one or more sequences of pages to be printed. plex Specifies whether page images are conditioned for one or two sided printing. Valid values: simplex, duplex, tumble. printer-setup-module Specifies one or more files used to set up printer modes or functions prior to printing a document. repeated-tab-stops Specifies the number of characters between tab stops.
x-image-shift Causes the page image to shift in position with respect to the medium on which page images are rendered. The direction of the shift is parallel to the x axis of the image. y-image-shift Causes the page image to shift in position with respect to the medium on which page images are rendered. The direction of the shift is parallel to the y axis of the image.
B ONC Binding Entries B.1 ONC Binding Entries Local file and NIS naming services use entries in ONC binding entry format to identify printing objects. The print system stores and retrieves these entries from the /etc/printers.conf file. The syntax of the ONC binding entry format is similar to that used in /etc/printcap and /etc/remote files except that the ONC binding entry format uses different key names.
ProgramNum- RPC program number of either a server or ProtoServer. A server ber program number can be one that a server creates dynamically, or it can be the special one for a spooler. ProgramVersion RPC version number of the Protoserver Authentication RPC authentication method that is used. The print system only supports sys.
pp1:paddr=hostD,105004,1,sys,pp,superv1,1,dpa pp2:paddr=hostD,105004,1,sys,pp,superv1,1,dpa This configuration file would need to be present on all hosts in a local file naming environment or used to update the NIS database in an NIS environment. Refer to Chapter 3 for information on configuring naming service. Note that, in a local file environment, the print system does not use the naming component of ONC, but the system still relies on ONC RPC.
C Printer Data Sheets This appendix contains printer data sheets for each printer that can be enabled by a print system supervisor.
Genicom LN45 PS Genicom mL450 PS HP ColorLaserJet Level2 PS HP ColorLaserJet PCL5 HP DesignJet755CM Level2 PS HP DeskJet1600CM Level2 PS HP DeskJet1600CM PCL5 HP LaserJet2100TN PS HP LaserJet2200 PS HP LaserJet4000 Level2 PS HP LaserJet4050 Level2 PS HP LaserJet4100 PS HP LaserJet4550 PS HP LaserJet4MPlus Level2 PS HP LaserJet4MPlus PCL5 HP LaserJet4Si Level2 PS HP LaserJet4Si PCL5 HP LaserJet5000 PS HP LaserJet5Si Level2 PS HP LaserJet5Si PCL5 HP LaserJet8000 PS HP LaserJet8100 PS HP LaserJet8150 PS HP Las
Lexmark OptraN PCL5 Lexmark OptraRtPlus Level2 PS Lexmark OptraRtPlus PCL5 Lexmark OptraS1250 Level2 PS Lexmark OptraS1250 PCL6 Lexmark OptraS1650 Level2 PS Lexmark OptraS1650 PCL6 Lexmark OptraS2450 Level2 PS Lexmark OptraS2450 PCL6 Lexmark OptraSC1275 Level2 PS Lexmark OptraSe3455 PS Lexmark OptraT610 PS Lexmark OptraT612 PS Lexmark OptraT614 PS Lexmark OptraT616 PS Lexmark OptraW810 PS Lexmark T620 PS Lexmark T622 PS Lexmark W820 PS Ricoh AP2100 PS SUN SPARCprinterE Level2 PS SUN SPARCprinterE PCL5 Tektr
Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox Xerox DocuPrint4090NPS DocuPrint4635NPS DocuPrint4850NPS DocuPrint4890NPS DocuPrintN17 Level2 PS DocuPrintN2025 PS DocuPrintN2125 PS DocuPrintN24 Level2 PS DocuPrintN3225 PS DocuPrintN32 Level2 PS DocuPrintN40 Level2 PS DocuTech6135 Document Centre 432ST PS Document Centre 470ST PS C–4 Printer Data Sheets
Table C–1: Printer Data Sheet: Compaq LG Line Matrix Printer (ANSI) Printer attribute file name: Compaq_LG_Series_ANSI.
Table C–2: Printer Data Sheet: Compaq Laser Printer LN16 (PS) Printer attribute file name: Compaq_LN16_PS.
Table C–3: Printer Data Sheet: Compaq Laser Printer LN32 PS Printer attribute file name: Compaq_LN32_PS.
Table C–4: Printer Data Sheet: Compaq Laser Printer LNM40 PS Printer attribute file name: Compaq_LNM40_PS.
Table C–5: Printer Data Sheet: Digital Colorwriter LSR 2000 Printer attribute file name: Digital_Colorwriter_LSR_2000_Level2PS.
Table C–6: Printer Data Sheet: DEClaser 1150 Level 1 PS Printer attribute file name: Digital_DEClaser1150_Level1PS.
Table C–7: Printer Data Sheet: DEClaser 1152 Level 2 PS Printer attribute file name: Digital_DEClaser1152_Level2PS.
Table C–8: Printer Data Sheet: DEClaser 2150 Level 1 PS Printer attribute file name: Digital_DEClaser2150_Level1PS.
Table C–9: Printer Data Sheet: DEClaser 2250 Level 1 PS Printer attribute file name: Digital_DEClaser2250_Level1PS.
Table C–10: Printer Data Sheet: DEClaser 3250 Level 1 PS Printer attribute file name: Digital_DEClaser3250_Level1PS.
Table C–11: Printer Data Sheet: DEClaser 3500 Level 2 PS Printer attribute file name: Digital_DEClaser3500_Level2PS.
Table C–12: Printer Data Sheet: DEClaser 3500 PCL5 Printer attribute file name: Digital_DEClaser3500_PCL5.
Table C–13: Printer Data Sheet: DEClaser 5100 Level 2 PS Printer attribute file name: Digital_DEClaser5100_Level2PS.
Table C–14: Printer Data Sheet: DEClaser 5100 PCL5 Printer attribute file name: Digital_DEClaser5100_PCL5.
Table C–15: Printer Data Sheet: Digital LA75 Printer attribute file name: Digital_LA75.
Table C–16: Printer Data Sheet: Digital LG04 Printer attribute file name: Digital_LG04.
Table C–17: Printer Data Sheet: Digital LG08 Printer attribute file name: Digital_LG08.
Table C–18: Printer Data Sheet: Digital LG12 Printer attribute file name: Digital_LG12.
Table C–19: Printer Data Sheet: Digital LG Line Matrix Printer (ANSI) Printer attribute file name: Digital_LG_Series_ANSI.
Table C–20: Printer Data Sheet: Digital LN03R ScriptPrinter Printer attribute file name: Digital_LN03R_Level1PS.
Table C–21: Printer Data Sheet: Digital LN17ps Level 2 PS Printer attribute file name: Digital_LN17_Level2PS.
Table C–22: Printer Data Sheet: Digital LN17 PCL5 Printer attribute file name: Digital_LN17_PCL5.
Table C–23: Printer Data Sheet: Digital Laser Printer LN20 PS Printer attribute file name: Digital_LN20_PS.
Table C–24: Printer Data Sheet: Digital Laser Printer LN40 PS Printer attribute file name: Digital_LN40_PS.
Table C–25: Printer Data Sheet: Digital PrintServer 17 Printer attribute file name: Digital_PrintServer17_Level2PS.
Table C–26: Printer Data Sheet: Digital PrintServer 20 Printer attribute file name: Digital_PrintServer20_Level2PS.
Table C–27: Printer Data Sheet: Digital PrintServer 32 Printer attribute file name: Digital_PrintServer32_Level2PS.
Table C–28: Printer Data Sheet: ANSI Compatible Printer Printer attribute file name: Generic_ANSI.
Table C–29: Printer Data Sheet: HP-GL Plotter Printer attribute file name: Generic_HPGL_Plotter.
Table C–30: Printer Data Sheet: PostScript Printer Printer attribute file name: Generic_Level1PS.
Table C–31: Printer Data Sheet: PostScript Printer Printer attribute file name: Generic_Level2PS.
Table C–32: Printer Data Sheet: PCL Printer Printer attribute file name: Generic_PCL.
Table C–33: Printer Data Sheet: Genicom LA36 Series Printer attribute file name: Genicom_LA36.
Table C–34: Printer Data Sheet: Genicom LA450 Printer attribute file name: Genicom_LA450.
Table C–35: Printer Data Sheet: GENICOM LN45 PS Printer attribute file name: Genicom_LN45_PS.
Table C–35: Printer Data Sheet: GENICOM LN45 PS (cont.
Table C–36: Printer Data Sheet: GENICOM mL450 PS Printer attribute file name: Genicom_mL450_PS.
Table C–36: Printer Data Sheet: GENICOM mL450 PS (cont.
Table C–37: Printer Data Sheet: HP Color LaserJet Level 2 PS Printer attribute file name: HP_ColorLaserJet_Level2PS.
Table C–38: Printer Data Sheet: HP Color LaserJet PCL5 Printer attribute file name: HP_ColorLaserJet_PCL5.
Table C–39: Printer Data Sheet: HP DesignJet 755CM Level 2 PS Printer attribute file name: HP_DesignJet755CM_Level2PS.
Table C–40: Printer Data Sheet: HP DeskJet 1600CM Level 2 PS Printer attribute file name: HP_DeskJet1600CM_Level2PS.
Table C–41: Printer Data Sheet: HP DeskJet 1600CM PCL5 Printer attribute file name: HP_DeskJet1600CM_PCL5.
Table C–42: Printer Data Sheet: HP LaserJet 2100TN PS Printer attribute file name: HP_LaserJet2100TN_PS.
Table C–43: Printer Data Sheet: HP LaserJet 2200 Series PS Printer attribute file name: HP_LaserJet2200_PS.
Table C–44: Printer Data Sheet: HP LaserJet 4000 Series PS Printer attribute file name: HP_LaserJet4000_Level2PS.
Table C–45: Printer Data Sheet: HP LaserJet 4050 Series PS Printer attribute file name: HP_LaserJet4050_Level2PS.
Table C–46: Printer Data Sheet: HP LaserJet 4100 Series PS Printer attribute file name: HP_LaserJet4100_PS.
Table C–47: Printer Data Sheet: HP LaserJet 4550 Series PS Printer attribute file name: HP_LaserJet4550_PS.
Table C–48: Printer Data Sheet: HP LaserJet 4M Plus Level 2 PS Printer attribute file name: HP_LaserJet4MPlus_Level2PS.
Table C–49: Printer Data Sheet: HP LaserJet 4MPlus PCL5 Printer attribute file name: HP_LaserJet4MPlus_PCL5.
Table C–50: Printer Data Sheet: HP LaserJet 4Si Level 2 PS Printer attribute file name: HP_LaserJet4Si_Level2PS.
Table C–51: Printer Data Sheet: HP LaserJet 4Si PCL5 Printer attribute file name: HP_LaserJet4Si_PCL5.
Table C–52: Printer Data Sheet: HP LaserJet 5000 Series PS Printer attribute file name: HP_LaserJet5000_PS.
Table C–53: Printer Data Sheet: HP LaserJet 5SiMX Level 2 PS Printer attribute file name: HP_LaserJet5Si_Level2PS.
Table C–54: Printer Data Sheet: HP LaserJet 5SiMX PCL5 Printer attribute file name: HP_LaserJet5Si_PCL5.
Table C–55: Printer Data Sheet: HP LaserJet 8000 Series PS Printer attribute file name: HP_LaserJet8000_PS.
Table C–55: Printer Data Sheet: HP LaserJet 8000 Series PS (cont.
Table C–56: Printer Data Sheet: HP LaserJet 8100 Series PS Printer attribute file name: HP_LaserJet8100_PS.
Table C–56: Printer Data Sheet: HP LaserJet 8100 Series PS (cont.
Table C–57: Printer Data Sheet: HP LaserJet 8150 Series PS Printer attribute file name: HP_LaserJet8150_PS.
Table C–58: Printer Data Sheet: HP LaserJet 8550 Series PS Printer attribute file name: HP_LaserJet8550_PS.
Table C–59: Printer Data Sheet: HP LaserJet 9000 Series PS Printer attribute file name: HP_LaserJet9000_PS.
Table C–59: Printer Data Sheet: HP LaserJet 9000 Series PS (cont.
Table C–60: Printer Data Sheet: HP LaserJet IIISi Level 1 PS Printer attribute file name: HP_LaserJetIIISi_Level1PS.
Table C–61: Printer Data Sheet: HP LaserJet IIISi Level 2 PS Printer attribute file name: HP_LaserJetIIISi_Level2PS.
Table C–62: Printer Data Sheet: HP LaserJet IIISiMX PCL5 Printer attribute file name: HP_LaserJetIIISi_PCL5.
Table C–63: Printer Data Sheet: Lexmark 4039 10plus Level 2 PS Printer attribute file name: Lexmark_4039plus_Level2PS.
Table C–64: Printer Data Sheet: Lexmark 4039 10plus PCL5 Printer attribute file name: Lexmark_4039plus_PCL5.
Table C–65: Printer Data Sheet: Lexmark 4079 plus Level 2 PS Printer attribute file name: Lexmark_4079plus_Level2PS.
Table C–66: Printer Data Sheet: Lexmark C720 Color PS Printer attribute file name: Lexmark_C720_PS.
Table C–67: Printer Data Sheet: Lexmark C910 PS Printer attribute file name: Lexmark_C910_PS.
Table C–68: Printer Data Sheet: Lexmark Forms Printer 2380 plus Printer attribute file name: Lexmark_Forms_2380plus.
Table C–69: Printer Data Sheet: Lexmark Forms Printer 4227 plus Printer attribute file name: Lexmark_Forms_4227plus.
Table C–70: Printer Data Sheet: Lexmark Optra C1200 Color PS Printer attribute file name: Lexmark_OptraC1200_PS.
Table C–71: Printer Data Sheet: Lexmark Optra C710 Color PS Printer attribute file name: Lexmark_OptraC710_PS.
Table C–72: Printer Data Sheet: Lexmark Optra C Level 2 PS Printer attribute file name: Lexmark_OptraC_Level2PS.
Table C–73: Printer Data Sheet: Lexmark Optra C PCL5 Printer attribute file name: Lexmark_OptraC_PCL5.
Table C–74: Printer Data Sheet: Lexmark Optra E PCL5 printer Printer attribute file name: Lexmark_OptraE_PCL5.
Table C–75: Printer Data Sheet: Lexmark Optra Lx Level 2 PS Printer attribute file name: Lexmark_OptraLx_Level2PS.
Table C–76: Printer Data Sheet: Lexmark Optra Lx PCL5 Printer attribute file name: Lexmark_OptraLx_PCL5.
Table C–77: Printer Data Sheet: Lexmark Optra Lxi+ Level 2 PS Printer attribute file name: Lexmark_OptraLxiPlus_Level2PS.
Table C–78: Printer Data Sheet: Lexmark Optra Lxi+ PCL5 Printer attribute file name: Lexmark_OptraLxiPlus_PCL5.
Table C–79: Printer Data Sheet: Lexmark Optra N Level 2 PS Printer attribute file name: Lexmark_OptraN_Level2PS.
Table C–80: Printer Data Sheet: Lexmark Optra N PCL5 Printer attribute file name: Lexmark_OptraN_PCL5.
Table C–81: Printer Data Sheet: Lexmark Optra Rt+ Level 2 PS Printer attribute file name: Lexmark_OptraRtPlus_Level2PS.
Table C–82: Printer Data Sheet: Lexmark Optra Rt+ PCL5 Printer attribute file name: Lexmark_OptraRtPlus_PCL5.
Table C–83: Printer Data Sheet: Lexmark Optra S 1250 Printer attribute file name: Lexmark_OptraS1250_Level2PS.
Table C–84: Printer Data Sheet: Lexmark Optra S 1250 Printer attribute file name: Lexmark_OptraS1250_PCL6.
Table C–85: Printer Data Sheet: Lexmark Optra S 1650 Printer attribute file name: Lexmark_OptraS1650_Level2PS.
Table C–86: Printer Data Sheet: Lexmark Optra S 1650 Printer attribute file name: Lexmark_OptraS1650_PCL6.
Table C–87: Printer Data Sheet: Lexmark Optra S 2450 Printer attribute file name: Lexmark_OptraS2450_Level2PS.
Table C–88: Printer Data Sheet: Lexmark Optra S 2450 Printer attribute file name: Lexmark_OptraS2450_PCL6.
Table C–89: Printer Data Sheet: Lexmark Optra SC 1275 Printer attribute file name: Lexmark_OptraSC1275_Level2PS.
Table C–90: Printer Data Sheet: Lexmark Optra Se 3455 PS Printer attribute file name: Lexmark_OptraSe3455_PS.
Table C–91: Printer Data Sheet: Lexmark Optra T610 PS Printer attribute file name: Lexmark_OptraT610_PS.
Table C–92: Printer Data Sheet: Lexmark Optra T612 PS Printer attribute file name: Lexmark_OptraT612_PS.
Table C–93: Printer Data Sheet: Lexmark Optra T614 PS Printer attribute file name: Lexmark_OptraT614_PS.
Table C–94: Printer Data Sheet: Lexmark Optra T616 PS Printer attribute file name: Lexmark_OptraT616_PS.
Table C–95: Printer Data Sheet: Lexmark Optra W810 PS Printer attribute file name: Lexmark_OptraW810_PS.
Table C–96: Printer Data Sheet: Lexmark T620 PS Printer attribute file name: Lexmark_T620_PS.
Table C–96: Printer Data Sheet: Lexmark T620 PS (cont.
Table C–97: Printer Data Sheet: Lexmark T622 PS Printer attribute file name: Lexmark_T622_PS.
Table C–97: Printer Data Sheet: Lexmark T622 PS (cont.
Table C–98: Printer Data Sheet: Lexmark W820 PS Printer attribute file name: Lexmark_W820_PS.
Table C–98: Printer Data Sheet: Lexmark W820 PS (cont.
Table C–99: Printer Data Sheet: Ricoh AP2100 PS Printer attribute file name: Ricoh_AP2100_PS.
Table C–100: Printer Data Sheet: Sun SPARCprinter E Level 2 PS Printer attribute file name: SUN_SPARCprinterE_Level2PS.
Table C–101: Printer Data Sheet: Sun SPARCprinter E PCL5 Printer attribute file name: SUN_SPARCprinterE_PCL5.
Table C–102: Printer Data Sheet: Tektronix Phaser 740 PS Printer attribute file name: Tektronix_Phaser740_PS.
Table C–103: Printer Data Sheet: Tektronix Phaser 750 Series PS Printer attribute file name: Tektronix_Phaser750_PS.
Table C–104: Printer Data Sheet: Tektronix Phaser 780 Series PS Printer attribute file name: Tektronix_Phaser780_PS.
Table C–105: Printer Data Sheet: Tektronix Phaser 850 Series PS Printer attribute file name: Tektronix_Phaser850_PS.
Table C–106: Printer Data Sheet: Xerox 4215 MRP Level 2 PS Printer attribute file name: Xerox_4215_Level2PS.
Table C–107: Printer Data Sheet: Xerox 4215 MRP PCL5 Printer attribute file name: Xerox_4215_PCL5.
Table C–108: Printer Data Sheet: Xerox 4219 MRP Level 2 PS Printer attribute file name: Xerox_4219_Level2PS.
Table C–109: Printer Data Sheet: Xerox 4219 MRP PCL5 Printer attribute file name: Xerox_4219_PCL5.
Table C–110: Printer Data Sheet: Xerox 4220 MRP Level 2 PS Printer attribute file name: Xerox_4220_Level2PS.
Table C–111: Printer Data Sheet: Xerox 4220 MRP PCL5 Printer attribute file name: Xerox_4220_PCL5.
Table C–112: Printer Data Sheet: Xerox 4230 MRP Level 2 PS Printer attribute file name: Xerox_4230_Level2PS.
Table C–113: Printer Data Sheet: Xerox 4230 MRP PCL5 Printer attribute file name: Xerox_4230_PCL5.
Table C–114: Printer Data Sheet: Xerox 4235 Level 1 PS Printer attribute file name: Xerox_4235_Level1PS.
Table C–115: Printer Data Sheet: Xerox 4235 MRP PCL4 Printer attribute file name: Xerox_4235_PCL4.
Table C–116: Printer Data Sheet: Xerox 4505 PCL5 Printer attribute file name: Xerox_4505_PCL5.
Table C–117: Printer Data Sheet: Xerox 4510 PCL5 Printer attribute file name: Xerox_4510_PCL5.
Table C–118: Printer Data Sheet: Xerox DocuPrint 4517 Level 2 PS Printer attribute file name: Xerox_4517_Level2PS.
Table C–119: Printer Data Sheet: Xerox DocuPrint 4517 PCL5 Printer attribute file name: Xerox_4517_PCL5.
Table C–120: Printer Data Sheet: Xerox DocuPrint 4520 Level 2 PS Printer attribute file name: Xerox_4520_Level2PS.
Table C–121: Printer Data Sheet: Xerox DocuPrint 4520 PCL5 Printer attribute file name: Xerox_4520_PCL5.
Table C–122: Printer Data Sheet: Xerox 4700 II Level 1 PS Printer attribute file name: Xerox_4700II_Level1PS.
Table C–123: Printer Data Sheet: Xerox 4700 II PCL5 Printer attribute file name: Xerox_4700II_PCL5.
Table C–124: Printer Data Sheet: Xerox DocuPrint 4050 NPS Printer attribute file name: Xerox_DocuPrint4050NPS.
Table C–125: Printer Data Sheet: Xerox DocuPrint 4090 NPS Printer attribute file name: Xerox_DocuPrint4090NPS.
Table C–126: Printer Data Sheet: Xerox DocuPrint 4635 NPS Printer attribute file name: Xerox_DocuPrint4635NPS.
Table C–127: Printer Data Sheet: Xerox DocuPrint 4850 NPS Printer attribute file name: Xerox_DocuPrint4850NPS.
Table C–128: Printer Data Sheet: Xerox DocuPrint 4890 NPS Printer attribute file name: Xerox_DocuPrint4890NPS.
Table C–129: Printer Data Sheet: Xerox DocuPrint N17 Printer attribute file name: Xerox_DocuPrintN17_Level2PS.
Table C–130: Printer Data Sheet: Xerox DocuPrint N2025 PS Printer attribute file name: Xerox_DocuPrintN2025_PS.
Table C–131: Printer Data Sheet: Xerox DocuPrint N2125 PS Printer attribute file name: Xerox_DocuPrintN2125_PS.
Table C–132: Printer Data Sheet: Xerox DocuPrint N24 Printer attribute file name: Xerox_DocuPrintN24_Level2PS.
Table C–132: Printer Data Sheet: Xerox DocuPrint N24 (cont.
Table C–133: Printer Data Sheet: Xerox DocuPrint N3225 PS Printer attribute file name: Xerox_DocuPrintN3225_PS.
Table C–134: Printer Data Sheet: Xerox DocuPrint N32 Printer attribute file name: Xerox_DocuPrintN32_Level2PS.
Table C–134: Printer Data Sheet: Xerox DocuPrint N32 (cont.
Table C–135: Printer Data Sheet: Xerox DocuPrint N40 Printer attribute file name: Xerox_DocuPrintN40_Level2PS.
Table C–135: Printer Data Sheet: Xerox DocuPrint N40 (cont.
Table C–136: Printer Data Sheet: Xerox DocuTech 6135 Printer attribute file name: Xerox_DocuTech6135.
Table C–137: Printer Data Sheet: Xerox Document Centre 432 ST PS Printer attribute file name: Xerox_Document_Centre_432ST_PS.
Table C–137: Printer Data Sheet: Xerox Document Centre 432 ST PS (cont.
Table C–138: Printer Data Sheet: Xerox Document Centre 470 ST PS Printer attribute file name: Xerox_Document_Centre_470ST_PS.
Table C–138: Printer Data Sheet: Xerox Document Centre 470 ST PS (cont.
Glossary The glossary includes definitions of terms used in the Advanced Printing Software documentation. Access Control List (ACL) A list of entities (such as users, operators, administrators, and servers) used to determine whether a certain entity has authorization to perform some operation or function. administrator A class of user that is enforced by security. An administrator sets policy and can create, modify, and delete persistent print system objects such as printers and servers.
notification Result and error reporting by a server to the client that had requested its services. Generally, the mechanisms needed to implement notification are provided by the system infrastructure. In most system environments, electronic mail can be used as a crude means for notification. object An abstraction used to represent various entities, such as printers and queues. Each print system object contains a collection of attributes. See also attributes.
server A software component that manages printing facilities on behalf of a client or clients on the same computer or over a network. For the print system, the term is generally used to refer to the print server that is either the spooler or the supervisor, but not both. Specifically, the spooler is a print server to the various API, CLI, and GUI clients that access it directly. However, the spooler is also a client of the supervisor for which the supervisor is a print server to the spooler.
Index A E access control description, 1–7 ACL creating, 4–5 description, 1–7 apx_caa_setup, 5–9 /etc/printcap, 10–1 event notification, 7–11 description, 1–7 event classes, 9–2 job events, 9–3 notification method, 9–1 notification servers, 9–1 printer events, 9–3 queue events, 9–3 server events, 9–2 C Command Line Client Programs description, 1–8 Console notification daemon description, 1–9 H Highly Available Application configuring, 5–7 resource profile, 5–7 D document description, 1–5 listing attrib
description, 1–5 discarding a job, 7–10 holding a job, 7–9 pausing, 7–8 printing, 7–2 promoting, 7–8 resuming a job, 7–9 retaining a job, 7–10 Job attributes job-discard-time, 7–10 job-hold, 7–9 job-retention-period, 7–10 LPD Outbound Gateway Supervisor description, 1–8 M messages including, 7–11 modification filters, 8–1 creating, 8–8 defining, 8–3 description, 1–10 N L LDAP configuring, 3–5 Lightweight directory access protocol, 3–5 Local File Name Service configuring, 3–1 description, 3–1 printers.
cleaning a queue, 6–2 cleaning a server, 5–18 pdconntf description, 1–9 pdcreate create logical printer, 6–14 create physical printer, 6–9 create queue, 6–1 pddelete deleting a logical printer, 6–17 deleting a server, 5–21 deleting jobs from a server, 5–18 physical printer, 6–12 pddisable disable queue, 6–2 disabling a physical printer, 6–11 disabling servers, 5–17 logical printer, 6–15 pdenable enable queue, 6–2 enabling servers, 5–16 logical printer, 6–14 physical printer, 6–10 pdls, 7–3 listing logical p
Q queue backlog events, 6–2 backlogged, 6–2 creating, 6–1 description, 1–4 disable, 6–2 enable, 6–2 listing a job, 7–4 listing queue attributes, 6–3 removing jobs, 6–2 states, 6–2 R Ready attributes description, 1–5 Resource profile, 5–7 rpc.