HP Distributed Print Service Administration Guide HP 9000 Computers Second Edition Manufacturing Part Number: B2355-90678 E0300 U.S.A.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
California. ©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985, 1986, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc. ©copyright 1990-1995 Cornell University ©copyright 1989-1991 The University of Maryland ©copyright 1988 Carnegie Mellon University Trademark Notices UNIX is a registered trademark of The Open Group.
Contents 1. Introducing HP Distributed Print Service What Are the Benefits of HPDPS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 The Minimum HPDPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .28 HPDPS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 What is an HPDPS Physical Printer? . . . . . . . . . . . . . . . . . . . . . . . . .29 What Is an HPDPS Logical Printer? . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Disk Space Required for Spooling . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Disk Space Required for Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Total Disk Space Required for an HPDPS Environment . . . . . . . . 50 Installing Individual HPDPS Components . . . . . . . . . . . . . . . . . . . . . . 51 Configuring DCE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Configuring DCE Security . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Planning User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Planning Printer Operator Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Planning System Operator Groups . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Planning Administrator Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Planning for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Handling Printer Failures . . . .
Contents Restoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Further Tuning of HPDPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 5. Creating/Configuring Supervisors and Physical Printers Creating and Configuring Supervisors . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Starting the Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Supervisors . . . . . . . . . . . . . . . . . . . . . .
Contents Configuring the Queue Backlog Attributes . . . . . . . . . . . . . . . . . . . .111 About Controlling Queue Backlog Processing . . . . . . . . . . . . . . . .113 Receiving Queue Notification Messages . . . . . . . . . . . . . . . . . . . . . . .114 Specifying Who Receives Messages From Users . . . . . . . . . . . . . . . .115 Specifying a Description for the Queue . . . . . . . . . . . . . . . . . . . . . . .116 Creating and Configuring Initial-Value-Job and Initial-Value-Document Objects . . . .
Contents Configuring Logical Printers as HPDPS Gateway Printers . . . . . . . . 150 Administering Gateway Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Other Logical Printer Configuration Tasks . . . . . . . . . . . . . . . . . . . . . Specifying a Description for the Logical Printer . . . . . . . . . . . . . . . Receiving Logical Printer Notification Messages . . . . . . . . . . . . . . . Enabling a Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Setting Two Values for Someone Other Than Yourself . . . . . . . . .203 Using Just the delivery-method Component . . . . . . . . . . . . . . . . .205 Using Just the delivery-address Component . . . . . . . . . . . . . . . . .206 Creating a Notification Profile Attributes File . . . . . . . . . . . . . . . . . . .207 Setting Notification Profile Values Using an Attributes File . . . . . .208 Resetting a Notification Profile to the Original Default Values . . . .
Contents Understanding How DCE Permissions Propagate Downward . . . . Setting the Default Permissions Granted by a Server and All Its Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Giving a Group Permission to the Security Directory IO and IC ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Group from the Security Directory IO and IC ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Querying for Enabled Logical Printers Contained in the Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 Querying for Physical Printers Registered with the Spooler . . . . . .258 Querying for Queue Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 Querying for the Status of a Queue . . . . . . . . . . . . . . . . . . . . . . . . . .259 Queue States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Receiving Messages Related to Production Jobs . . . . . . . . . . . . . . . 273 Performing Other Spooler-Related Tasks . . . . . . . . . . . . . . . . . . . . . . About Managing Queue Backlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Queue Upper Backlog Boundary . . . . . . . . . . . . . . . . . About the Queue Lower Backlog Boundary . . . . . . . . . . . . . . . . . About the Queue Backlog Update Interval . . . . . . . . . . . . . . . . . . Responding to Queue Backlog . .
Contents 10. Managing Supervisors and Physical Printers Monitoring Supervisor and Physical Printer Configurations . . . . . . .298 Setting the message Attribute for Supervisors and Supervisor Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298 Creating Archive Files for Supervisors and Supervisor Objects . . .299 Setting Policy for Job-Size Physical Printer Attributes . . . . . . . . . . . .300 Using the maximum-copies-supported Attribute . . . . . . . . . . . . . . .
Contents Disabling Job Start and End Messages . . . . . . . . . . . . . . . . . . . . . 316 Job-Related Tasks for Physical Printer Management . . . . . . . . . . . . . Determining Which Jobs Are Scheduled to a Physical Printer . . . . Cancelling Processing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pausing Processing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Pausing and Disabling Physical Printers . . . . . . . . . . . . . . .
Contents Understanding Job Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333 Understanding the user-name, job-originator, and j ob-owner Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334 Understanding the job-name Attribute . . . . . . . . . . . . . . . . . . . . . . .334 Finding Jobs Submitted by Other Users . . . . . . . . . . . . . . . . . . . . . .334 Managing Jobs in Queues and Spoolers . . . . . . . . . . . . . . . . . . . . . . . .
Contents Querying for Specific Job-Status Attributes . . . . . . . . . . . . . . . . . About Current and Previous Job States . . . . . . . . . . . . . . . . . . . . . . job-state-reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Jobs That Cannot Be Scheduled Because of Resources . . . . Querying Job Status for Large Jobs . . . . . . . . . . . . . . . . . . . . . . . . . Querying for the Number of Octets Completed for a Processing Job . . . . . . . . . . . . . . .
Contents 13. Troubleshooting Getting Full Descriptions for HPDPS Error and Notification Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376 Problems with Physical Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378 Checking the Physical Printers for a Queue . . . . . . . . . . . . . . . . . . .378 The Printer Device is Not Printing . . . . . . . . . . . . . . . . . . . . . . . . . .379 Physical Printer State is “needs-key-operator” . . . . . . . . .
Contents The Job Could Not Be Scheduled for Printing . . . . . . . . . . . . . . . The Printer Resources that the Job Requires Are Not Ready . . . Finding the Printers that Support the Job's Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the job-size-range-ready Attribute Value . . . . . . . . . Modifying the media-ready Attribute Value . . . . . . . . . . . . . . . The Printer Resources that the Job Requires Are Not Supported . . . . . . . . . . . .
Contents B. Resources Needed for Configuring a Large Number of Printers HPDPS Miminum Configuration Requirements . . . . . . . . . . . . . . . . .418 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418 Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418 Kernel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418 High Availability . . . . . . . . . . . . . . . . . .
Contents 22
Conventions Used in this Manual This manual uses the following typographic conventions: User input Text that must be entered at the command line exactly as shown, such as pdpr -x “page-count=50” File3 Computer Indicates commands or command segments, flags, attributes, files, directories, and other items whose names are predefined by the system, such as pdls and notification-delivery-method.
• Braces, { }, around values indicate required items that you must supply with the command. Here, they mean that you must enter either a LocalJobId or a GlobalJobId with the pdmod command. Braces are also used within the notification-profile attribute. • A vertical bar, |, between values indicates that you can only enter one of the values with the command. Here, it means that when you issue the pdmod command, you can specify either a LocalJobId or a GlobalJobId, but not both.
• Single quotation marks, ' ' , surround a text string that contains spaces when the text string is imbedded in a statement already enclosed in double quotation marks. An example is: -x "sides=2 job-print-after='08:00:00 03/09/95'" • Braces, {}, surround a value within the notification-profile attribute. An example is: -x "notification-profile={delivery-method=electronic-mail}" • Double ampersand, &&, means "and" within a command.
24
Introducing HP Distributed Print Service 1 Introducing HP Distributed Print Service HP Distributed Print Service (HPDPS or DPS) is a sophisticated distributed print environment that allows you to give your users access to a wide variety of printers and printing functions. It also provides you with the ability to effectively and centrally manage your entire distributed print environment.
Introducing HP Distributed Print Service What Are the Benefits of HPDPS? What Are the Benefits of HPDPS? HPDPS is a product that facilitates and simplifies printing in a network environment.
Introducing HP Distributed Print Service What Are the Benefits of HPDPS? When using DCE, HPDPS gives you the ability to configure and monitor your network printing system from any HPDPS client on your system. You can configure and monitor printers, servers, and queues. You can also configure default settings for the jobs your users submit to HPDPS-managed printers. When you use DCE, you enable expanded security as well as single-point administration of distributed features for print management.
Introducing HP Distributed Print Service The Minimum HPDPS Configuration The Minimum HPDPS Configuration You can use the minimum HPDPS configuration as a starting point for a complete, functional HPDPS print environment. The following figure shows a minimum configuration with an HPDPS client and two servers, called the spooler and the supervisor, all installed on the same processor.
Introducing HP Distributed Print Service HPDPS Architecture HPDPS Architecture Some of the components, or objects, that make up an HPDPS environment are shown in Figure 1-2, “Major HPDPS Objects,”. See “What Are Objects and Attributes?” shortly for more information on objects. Figure 1-2 Major HPDPS Objects The figure shows an HPDPS spooler server and a supervisor server. The servers contain the major objects involved with printing: jobs, documents, logical printers, physical printers, and queues.
Introducing HP Distributed Print Service HPDPS Architecture What Is an HPDPS Logical Printer? An HPDPS logical printer represents an abstract set of job and printer capabilities, such as the types of document formats supported and the types of media supported. Your users submit their jobs to logical printers, which then verify that there are physical printers capable of handling the jobs. Once verified, the logical printer sends the job to an associated queue.
Introducing HP Distributed Print Service HPDPS Architecture • Reports job status There can be several supervisors, each supporting multiple physical printers, for each spooler in your system.
Introducing HP Distributed Print Service The Two HPDPS Environments The Two HPDPS Environments HPDPS can operate within either of two environments. In the first, it optionally uses Distributed Computing Environment (DCE) services to interact with a heterogeneous mix of hardware and software products as if they were a single print environment. When HPDPS interacts with DCE, the environment is called the DCE Extended Environment. This environment requires separately purchased DCE Security software.
Introducing HP Distributed Print Service What Are Objects and Attributes? What Are Objects and Attributes? With its objected-oriented model, an HPDPS object represents a physical or logical entity in the print environment. For example, a specific printer device is represented as a physical printer object. Specific printer capabilities, on the other hand, are represented as a logical printer object.
Introducing HP Distributed Print Service How HPDPS Processes Jobs How HPDPS Processes Jobs The following information describes how the HPDPS components work together to process the jobs users submit. 1. After a user submits a job to an HPDPS logical printer, HPDPS verifies that the logical printer exists. Users either submit their jobs to a default logical printer or specify a non-default logical printer by name. 2. The next step is validation.
Introducing HP Distributed Print Service Job and Document Attributes Job and Document Attributes Two additional HPDPS objects not mentioned earlier are called initial-value-job and initial-value-document objects. Initial-value-job objects are objects that represent default attribute values for a job. Likewise, initial-value-document objects are objects that represent default attribute values for a document. You can use initial-value-job and initial-value-document objects to assign values to attributes.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users Configuring HPDPS to Meet the Needs of Your Users Deciding how many servers you need and where to locate them depends on the capacity of your system hardware, the locations of your printer devices, and the needs of your users. Once you have installed the servers in your network, they work in concert independent of their relative locations.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users Figure 1-4, “Printer Pool,”, HPDPS allows you to associate several physical printers with the same queue. Users specify the logical printer supporting the pool of printers as the destination for a job. The first physical printer that becomes available and that supports the job, accepts the next job in the queue.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users Figure 1-5 Printer Security You can also set up your logical printer so that it does not check for authorization, making the logical printer available to all users. Because users who use LP spooler print commands are not typically logged into DCE, the printers to which they send their requests must not require authorization. See Chapter 8 , “Managing DCE Security for HPDPS,” for further information.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users Figure 1-6 Authorizing Access to Printer Functions at the Logical Printer You might want to restrict users from using certain capabilities of specific physical printers. It might be the policy of your company that all jobs must be printed on two sides of the page. You can set up all your page printers so they will accept only jobs that request two-sided printing.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users Figure 1-7 Authorizing Access to Printer Functions at the Physical Printer Supporting LP Spooler Users If HPDPS is installed on a single system, LP spooler users will be able to directly access HPDPS printers without any further setup.
Introducing HP Distributed Print Service Configuring HPDPS to Meet the Needs of Your Users If an HPDPS client is installed, HPDPS translates the LP spooler commands to HPDPS commands. For detailed information, see Appendix B, "LP Spooler Commands Translated to HPDPS Commands" in the HP Distributed Print Service User's Guide. NOTE When a job is submitted through the LP spooler, the user name listed as the owner of the job will be hpdps-lp-user.
Introducing HP Distributed Print Service HPDPS System Management Interfaces HPDPS System Management Interfaces You can configure and manage your system by entering commands directly on the command line or by using the System Administration Manager (SAM). You will need an HPDPS client installed on your system to use either interface. Using the Command Line Interface The HPDPS command line interface is POSIX-compliant and provides complete configuration and monitoring capability.
Introducing HP Distributed Print Service HPDPS System Management Interfaces • SAM provides extensive, context-sensitive online help. This includes several tutorials that explain HPDPS concepts. There are several things that SAM does not currently do. They include: • SAM does not provide any support for managing initial value objects, HPDPS error logs, or notification profiles.
Introducing HP Distributed Print Service HPDPS System Management Interfaces 44 Chapter 1
Installing HP Distributed Print Service 2 Installing HP Distributed Print Service HPDPS has a modular design giving it the flexibility to accommodate a large variety of network configurations. This modularity requires you to plan how to install HPDPS on your network. You might not want to install all of the HPDPS components on all of your networked systems. This plan must take into account the configuration of your network and the printing needs of your users.
Installing HP Distributed Print Service Prerequisites for HPDPS Installation Prerequisites for HPDPS Installation A list of prerequisites follows: • HP-UX 10.20 or a subsequent release must be installed on each HP-UX system that will contain a client or server. • HPDPS uses two entries that must exist in the service name database, /etc/services.These are: pdclientd 6874/tcp pdeventd 6875/tcp If you are upgrading from a pre-10.20 system, you must manually add the above entries.
Installing HP Distributed Print Service Calculating the Memory and Disk Space Requirements Calculating the Memory and Disk Space Requirements The HPDPS client and servers require a minimum of 64MB of installed memory on the system on which they are running.
Installing HP Distributed Print Service Calculating the Memory and Disk Space Requirements Table 2-1 Disk Space Requirements for HPDPS Installation Component(s) Disk Space Required Spooler only 12MB Supervisor only 12MB The HPDPS components are installed in the /opt/pd file system. A /var/opt/pd file system is also created for spooling purposes. It also contains the printer configuration database. This database contains the current print environment print configuration.
Installing HP Distributed Print Service Calculating the Memory and Disk Space Requirements Disk Space Required for Paging If your system has more than 64MB of memory, calculate the paging space by multiplying the installed memory by two and adding 10KB per job. Table 2-2 identifies the paging space requirements based on the number of jobs being processed by either the HPDPS client or supervisor at any point in time.
Installing HP Distributed Print Service Calculating the Memory and Disk Space Requirements NOTE The paging space requirement is a system recommendation; it is not exclusive to the HPDPS application. Therefore, if your current system has 64MB of installed memory and you have already defined 180MB of paging space, you do not need to increase your paging space.
Installing HP Distributed Print Service Installing Individual HPDPS Components Installing Individual HPDPS Components You might wish to install only certain HPDPS components on a given host. For example, a host might only use the HPDPS client to access servers on other hosts, and so HPDPS servers need not be installed on that host. The components that can be individually installed are the client, the spooler, and the supervisor.
Installing HP Distributed Print Service Configuring DCE Components Configuring DCE Components If HPDPS is to be executed in the DCE Extended Environment, the DCE Security Server and DCE Cell Directory Server must be installed and a DCE cell configured. Use the DCE documentation to do the following: • Check that current state of your DCE configuration is complete. • Ensure that DCE components are running. • Configure the DCE servers for the cell. • Configure the Security Server services.
Installing HP Distributed Print Service Configuring DCE Security Configuring DCE Security When you have configured the DCE security servers and clients, you must define the DCE HPDPS-specific security identities. Security identities are created in the following hierarchy: 1. Organizations (such as your business or department) 2. Domain Groups (operators and administrators) 3. Domain Principals (the members of the two groups) 4.
Installing HP Distributed Print Service Configuring DCE Security 54 Chapter 2
Planning Your HPDPS Configuration 3 Planning Your HPDPS Configuration This section presents information that will help you to configure your HPDPS environment.
Planning Your HPDPS Configuration Planning Overview Planning Overview As you begin planning your HPDPS environment, you need to consider how to do the following, while optimizing your resources and meeting the needs of your users: • Manage your printers HPDPS gives you the ability to manage all of your printers as network resources. You can set up a configuration that gives users with common job requirements access to a particular printer or set of printers that support their jobs.
Planning Your HPDPS Configuration Planning Overview • Support users who submit jobs from an HPDPS client or who submit print requests from applications or with the LP spooler print commands such as lp and lpstat. You will want to make planning decisions for your user groups based on their printing needs as well as the availability of hardware. • Manage remote and local printer devices. The management capability provided by HPDPS allows you to centrally manage all of your printer devices.
Planning Your HPDPS Configuration Planning Your Physical Configuration Planning Your Physical Configuration Understanding how many basic HPDPS components to install is important when you are designing your HPDPS environment. If you need a minimum HPDPS configuration, you will have to install a client, a spooler, and a supervisor.
Planning Your HPDPS Configuration Planning Your Physical Configuration Determining How Many Supervisors to Install A complex print environment will typically have multiple supervisors for every spooler that is installed. Install supervisors in your network according to the following guidelines: • Install a supervisor on each host that has a direct-attached printer (such as a printer attached to a serial or parallel interface) that will be part of the HPDPS environment.
Planning Your HPDPS Configuration Planning Your Logical Configuration Planning Your Logical Configuration Once you have installed the basic HPDPS components in your network, you will want to create a logical configuration based on your printing needs. By this, we mean setting values for the different HPDPS attributes relating to the basic HPDPS components. The basic HPDPS objects that you configure are the spooler, the logical printer, the queue, the supervisor, and the physical printer.
Planning Your HPDPS Configuration Planning Your Logical Configuration jobs waiting in the queue for scheduling. You can also specify who receives notification regarding backlogged queues. Supervisor Considerations The supervisor contains physical printer objects. Most of your configuration activities will be for the physical printer objects contained in the supervisor. You will need to determine the system on which the supervisor will run and to specify a name for the supervisor.
Planning Your HPDPS Configuration Selecting Logical Configuration Models Selecting Logical Configuration Models A logical configuration model shows the relationships among logical printers, initial-value-job and initial-value-document objects, queues, and physical printers. You might want to configure all of the printers that you plan to administer with HPDPS at the same time.
Planning Your HPDPS Configuration Selecting Logical Configuration Models The advantages and disadvantages of the desktop configuration model are: Advantages: • Matches a traditional workstation printer configuration for an individual or for a small group. • Users have no uncertainty as to where their jobs will print. • Allows you to specify different defaulting for each physical printer. • Provides good security and control of printing activities. Disadvantages: • No printer workload balancing.
Planning Your HPDPS Configuration Selecting Logical Configuration Models • printers that support similar job characteristics, such as duplexed or rotated printing. Figure 3-2 Printer Pool Configuration Model The advantages and disadvantages of the printer pool configuration model are: Advantages: • Simplicity; you may have fewer HPDPS objects to create and manage as compared to the desktop model. • Allows HPDPS to balance your printer workload.
Planning Your HPDPS Configuration Selecting Logical Configuration Models • HPDPS does much of the routing of jobs to the printers. However, if your users require a specific printer device for their jobs, they must specify a physical printer with their print request. The greatest benefit of the printer pool configuration model is in balancing your printing workload. The greatest drawback is that your users do not know which of the printers in the pool will print their job.
Planning Your HPDPS Configuration Selecting Logical Configuration Models • Allows you to specify different defaulting for each logical printer. Your users can submit a variety of job types. • Allows you to control the access to both the physical printer and its features. Disadvantages: • There is no printer workload balancing. • Complexity; you must create and manage more HPDPS objects as compared to the desktop configuration model. • Limited by the capability of the physical printer.
Planning Your HPDPS Configuration Selecting Logical Configuration Models Figure 3-4 Hourglass Configuration Model The advantages and disadvantages of the hourglass configuration model are: Advantages: • Allows HPDPS to balance your printer workload. • Convenient for printer devices that are in close proximity to one another. • Convenient for printer devices with similar functions and capabilities. • Allows you to specify different defaulting for each logical printer.
Planning Your HPDPS Configuration Selecting Logical Configuration Models Once you understand the four configuration models, you can use them as building blocks to plan your logical configuration. A complex configuration is unlikely to be exactly like one of the configurations above. Rather, it will most likely combine some or all of these building blocks to meet your varied print environment needs.
Planning Your HPDPS Configuration Planning DCE Extended Environment Groups Planning DCE Extended Environment Groups The level of printing and administrative functions you can enable spans a wide range; you will want to plan to provide the appropriate functions to your users. Understanding how to group categories of users and provide appropriate printer and queue access and event notification helps simplify a complex print environment.
Planning Your HPDPS Configuration Planning DCE Extended Environment Groups correspond to the needs of each type of group as described in the following topics. See Chapter 7 , “Using Notification,” for detailed information. Planning User Groups In a DCE Extended Environment, you might group your users according to their physical locations, the type of printing they do, the hours they work, the priority level of their work, or whatever is appropriate in your environment.
Planning Your HPDPS Configuration Planning DCE Extended Environment Groups Planning System Operator Groups Another group you may want to integrate into your print environment is for people who are responsible for managing the flow of jobs through the system. As long as users are sending a balanced number and consistent types of jobs to the printers, and the printer devices are on-line and working well, the job flow requires little attention.
Planning Your HPDPS Configuration Planning for High Availability Planning for High Availability Handling Printer Failures In order to implement high availability of printers for an organization, you configure multiple physical printers on the same queue. The supervisor for different physical printers on the same queue may be one or multiple.
Getting Started with HPDPS 4 Getting Started with HPDPS This chapter discusses the following topics: • logging in as HPDPS administrator • starting HPDPS components • verifying that HPDPS processes are running • automatically starting HPDPS • setting HPDPS environment variables • backing up and restoring HPDPS directories and files Chapter 4 73
Getting Started with HPDPS Logging On as HPDPS Administrator Logging On as HPDPS Administrator As explained in Chapter 1, your HPDPS environment will be either the Basic Environment or the DCE Extended Environment. Within the Basic Environment, you simply log in as root. Within the DCE Extended Environment, you will need to do one of the following to log in to DCE: Log in as cell_admin by entering the DCE command: dce_login cell_admin The system will prompt you for your password. Or, 1.
Getting Started with HPDPS Starting HPDPS Components Starting HPDPS Components To start HPDPS within either the Basic Environment or the DCE Extended Environment, use SAM, or do the following: 1. Login as root. 2. Start the HPDPS client daemon: pdstartclient NOTE To start HPDPS spooler and supervisor components remotely, you can use SAM, but only after you have started the HPDPS client daemon after logging on to the remote system using the HP-UX rlogin command.
Getting Started with HPDPS Starting HPDPS Components Viewing Log Files Standard output and standard error of each HPDPS component started up by the system startup process are redirected to the file: /var/opt/pd/Component/startup.log where Component is the spooler or supervisor name, or pdclientd for the client daemon. These log files, in addition to /var/opt/pd/Component/error.log, can be examined for diagnostics on why a component failed to start up.
Getting Started with HPDPS Verifying That HPDPS Processes Are Running Verifying That HPDPS Processes Are Running Using SAM to Verify HPDPS Processes When you select any of the HPDPS subareas in SAM, the following occurs: • SAM determines if the HPDPS client daemon is running. If not, SAM starts it. • SAM collects information about spoolers, supervisors, logical printers, physical printers, print queues, and jobs. You can see the status (or attributes) of these objects by selecting the appropriate icon.
Getting Started with HPDPS Verifying That HPDPS Processes Are Running where SupervisorName is the name of the supervisor you want to check. In the DCE Extended Environment, this command checks the complete cell for the requested supervisor.
Getting Started with HPDPS Verifying That HPDPS Processes Are Running If you have multiple spoolers, you can verify which spoolers are running by entering the command: pdls -c server -f "server-type==spooler" \*: Chapter 4 79
Getting Started with HPDPS Automatically Starting HPDPS Automatically Starting HPDPS To automatically start HPDPS during system startup, modify the startup configuration file /etc/rc.config.d/pd. (If any HPDPS components have already been started in accordance with “Starting HPDPS Components”, first modify this file and then shut down the system; then restart as shown in “Starting HPDPS”.
Getting Started with HPDPS Automatically Starting HPDPS • Set to 1 to start the HPDPS client daemon using the default locale and the default port on this host. • Set to 0 if the HPDPS client daemon should not be started on this host. The default does not start the client daemon: PD_CLIENT=0 PD_OTHER_CLIENTS defines the list of client daemons to start on this host. This list names each client daemon by its locale and TCP/IP port number.
Getting Started with HPDPS Automatically Starting HPDPS PD_SUPERVISORS=" Super1 Super2 " The default does not start any supervisors: PD_SUPERVISORS=" " NOTE In addition to the above environment variables, the startup configuration file can also contain the following four environment variables, which can also be optionally modified: • PD_MAXTHREADS • PD_MAXRETRIES • PD_RETRY_INTERVAL • PD_MEMLIMIT For more information on these environment variables, see “Tuning Load Handling Using HPDPS Environment Variab
Getting Started with HPDPS Setting HPDPS Environment Variables Setting HPDPS Environment Variables The following information helps you to set (or verify the setting of) the HPDPS-related environment variables. Setting the PATH Environment Variable During the installation process, HPDPS updates the HP-UX PATH environment variable definition in /etc/PATH to include the directory location of the HPDPS executable files; HPDPS appends :/opt/pd/bin to the paths already specified.
Getting Started with HPDPS Setting HPDPS Environment Variables jobs without specifying a logical printer name. Defining a default logical printer also allows you to perform certain configuration tasks without specifying the logical printer name. For example, to set the default value of the PDPRINTER to LogPrt1, edit the system-wide /etc/.profile file and add the line: export PDPRINTER=LogPrt1 Users can set a different default logical printer in their individual .
Getting Started with HPDPS Setting HPDPS Environment Variables Summary of Other Environment Variables The following table summarizes other environment variables. Table 4-1 Environment Variables Variable Description PDPATH A path of directories that are searched for the file name specified in the -X AttributesFileName flag. Multiple directories are separated by a colon (:). If the PDPATH environment variable does not exist, the current working directory of the person submitting the command is used.
Getting Started with HPDPS Setting HPDPS Environment Variables Table 4-1 Environment Variables Variable Description LC_CTYPE The name of the locale for character classification. Commands: All The name of the locale containing monetary-related numeric editing information. LC_MONETARY Commands: All The name of the locale containing numeric editing, such as radix and character information. LC_NUMERIC Commands: All The name of the locale for date and time formatting information.
Getting Started with HPDPS Backing Up and Restoring HPDPS Directories and Files Backing Up and Restoring HPDPS Directories and Files This section provides some information concerning the need to back up HPDPS directories and files and how to restore the information later on. Backup Once you have HPDPS in use, your next consideration should be backing up the file systems, directories, and files. Files and directories represent a significant investment of time and effort.
Getting Started with HPDPS Further Tuning of HPDPS Further Tuning of HPDPS Every persistent object (such as a printer, spooler, or supervisor which stays in permanent storage when the process exits) requires two file descriptors. Also, each job in the spooler requires two file descriptors. The total number of open files allowed by your system is determined by the nfile kernel configuration parameter. Your HP-UX kernel may have been configured to a relatively low value.
Creating/Configuring Supervisors and Physical Printers 5 Creating/Configuring Supervisors and Physical Printers The procedures in this chapter describe how to complete initial configuration activities for HPDPS supervisors and the physical printers they control, using the command line interface. The supervisor is a server that runs under HP-UX and manages the printing process. The supervisor manages and controls physical printers, which you configure to represent your printer devices.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Supervisors Creating and Configuring Supervisors You can create and configure an HPDPS supervisor from SAM or from the command line. Using SAM, you can directly create a supervisor, or, you can create a supervisor when you add a physical printer. From the command line, you can use the pdstartsuv and pdset commands to create, start, and configure HPDPS supervisors, as shown in the sections below.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Supervisors • If the supervisor name you specify with the command does not already exist, HPDPS displays a message asking if you want to create it as a new server. Then it starts the new supervisor. • If the supervisor exists but is not currently running, HPDPS displays status information and issues a message when it has successfully started the supervisor.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Supervisors example, you might include the name of a person, a telephone number and office location: pdset -c server -x "list-of-managers='Ken Donnell, ext. 5-7007 , \ office C1-7' 'Ron Rourke, ext. 5-9007, office B1-4'" Super1 If you do not specify a value for the list-of-managers attribute, HPDPS does not provide a default.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers Creating and Configuring Physical Printers You can create and configure HPDPS physical printers from SAM or from the command line. From the command line, you create and configure a physical printer using the pdcreate command. After you create the physical printer, you can use the pdset command to further configure the physical printer.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers Table 5-1 Summary of Key Attributes According to attachment-type attachment-type values Required Attributes tcpip-bsd — printer-model — internet-address — print-queue-name lp-spool-hp, lp-spool-bsd — printer-model (optional) — internet-address — print-queue-name You use the following attributes to create a physical printer. Other attributes are defined in pd_att_phy_ptr(5).
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers • lp-spool-hp (HP-UX LP spooler) • lp-spool-bsd (non-HP-UX LP spooler) device-name This attribute is required if the value of the attachment-type attribute is serial or parallel. This single-valued attribute specifies the name of the device file name associated with the physical printer, for example, /dev/c1d14_ip. If the device file name does not include /dev, then /dev is assumed.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers printer-community-name This is an optional attribute that can be given if the value of attachment-type is tcpip. It identifies the SNMP community name which is used to obtain printer information. The default is internal. printer-model This attribute is required unless the attachment-type is either lp-spool-hp or lp-spool-bsd.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers number. Consult your Jet-Direct manual. Creating a Physical Printer To create a physical printer, use the pdcreate command, specifying the the supervisor name followed by the printer name, such as Super1:PhyPrt1. The printer name you specify can be up to 255 characters in length.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers pdcreate -c printer -x "attachment-type=lp-spool-bsd \ internet-address=15.164.144.04 print-queue-name=RemoteQueue3" \ Super1:PhyPrt1 If the same attribute is specified both on the command line (using the -x flag) and in the default attributes for the printer model, HPDPS uses the attribute value specified on the command line.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers pdcreate -c printer -x "printer-model=MyModel \ attachment-type=tcpip internet-address=11.0.23.34" \ Super1:MyPrt1 Configuring Physical Printers Use the pdset command to add or modify attributes and values after you have initially created a physical printer object. The default class for the pdset command is printer.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers to request a specific location at which their jobs will be printed. HPDPS compares the value of the job attribute printer-locations-requested to this attribute during job validation and scheduling. Determining Attributes of a Physical Printer To determine the value of attributes for a particular printer, you can use either SAM or the command line interface. Within SAM, select "View/Modify".
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers NOTE You must set the value of the physical printer associated-queue attribute as previously described in this chapter and create the queue before you can enable the physical printer. See “Creating and Configuring Queues” in Chapter 6 for instructions on creating the queue.
Creating/Configuring Supervisors and Physical Printers Creating and Configuring Physical Printers 102 Chapter 5
Configuring Spoolers, Queues, and Logical Printers 6 Configuring Spoolers, Queues, and Logical Printers The procedures in this chapter describe how to complete initial configuration activities for HPDPS spoolers, queues, and logical printers using the command line interface. To control defaulting for your HPDPS print environment, use the initial-value-job and initial-value-document objects. See “Job and Document Attributes” in Chapter 1 for more information.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring HPDPS Spoolers Creating and Configuring HPDPS Spoolers You can create and configure an HPDPS spooler using SAM or the command line interface. With SAM, you can directly create a spooler, or, you can create a spooler when you add a physical printer, logical printer, or print queue.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring HPDPS Spoolers Upon attempting to start a supervisor as shown in the example above, there are three possible results: • If the spooler name you specify with the command does not already exist, HPDPS displays a message asking if you want to create the new spooler. Then it starts the new spooler.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring HPDPS Spoolers • which HPDPS supervisor or supervisors contain the physical printers that receive jobs from the queue or queues contained in this spooler • any other information that is unique to your company or organization If you do not set a value for the descriptor attribute, HPDPS does not provide a default.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring HPDPS Spoolers The delivery-address component of this attribute defaults to the UserName@HostName of the machine where the spooler was created and the delivery-method component defaults to electronic-mail. You will want to change the value or the delivery-address component if the person who manages the spooler is someone other than the administrator who created it.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues Creating and Configuring Queues HPDPS queues receive jobs from the spooler and manage the jobs until the spooler schedules them to physical printers. You can create and start a queue from SAM or from the command line.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues physical printer PhyPrt1 can accept jobs A, B, and C, and physical printer PhyPrt2 can accept jobs X, Y, and Z. Job A was the first job received by the queue and job Z was the last. The spooler will schedule the jobs in the order shown at the bottom of the figure.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues other jobs with lower priorities that are already in the queue. The spooler places jobs of equal priority in the queue in the order in which they were submitted. Figure 6-2, “priority-fifo Queue Feeding One Physical Printer,” illustrates the priority-fifo scheduling method. The physical printer associated with the queue is capable of printing all of the jobs.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues a lesser value after they have submitted a job by using the pdmod command. You, as an administrator, can set the value of the attribute for a job to any value between 0 to 100. You can also use an initial-value-job object associated with a logical printer to set the job-priority initial-value-job attribute to any valid value. Then all jobs submitted to the logical printer will receive that priority.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues HPDPS does not calculate the value of the queue-backlog attribute and cannot notify you about backlogged queues. backlog-lower-bound This single-valued attribute specifies the amount of processing time, in hours and minutes, that will indicate a queue is not considered backlogged.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues NOTE The smaller the interval you specify, the larger the chance for detection of a backlogged queue. In general, if you specify a small value for the interval, specify a wider gap in the values for the upper and lower boundaries. Conversely, increase the interval value if you set the two boundaries fairly close together.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues Figure 6-3 Queue Backlog Upper and Lower Bounds Based on the values for 45 minutes for the upper boundary and 30 minutes for the lower boundary, the queue becomes backlogged at 10:10, is no longer backlogged at 10:30, and becomes backlogged again at 10:50. This example also illustrates the benefits of specifying different values for the upper and lower boundaries.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues • queue-backlogged The delivery-address component of this attribute defaults to the machine where the queue is created, and the delivery-method component defaults to electronic-mail. You will want to change the user identified by the delivery-address component if the operator who manages the queue is someone other than the administrator who created it.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Queues For example, to add three people to the list of people who receive messages from users for queue Queue1, enter: pdset -c queue -x "notify-operator+=message:White \ message:Jones electronic-mail:Smith@Olds" Queue1 The order in which you specify the components must be the delivery-method first, followed by the delivery-address.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Initial-Value-Job and Initial-Value-Document Objects Creating and Configuring Initial-Value-Job and Initial-Value-Document Objects You can use initial-value-job and initial-value-document objects, as defined in Chapter 1, to assign default values to job and document attributes.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Initial-Value-Job and Initial-Value-Document Objects Creating an Initial Value Object Use the following commands to create an initial value object: • To create an initial-value-document object named LP3ivd that is contained in spooler Spool1, enter: pdcreate -c initial-value-document -x "copy-count=1 \ sides=1 descriptor='IVD for LogPrt3'" Spool1:LP3ivd • To create an initial-value-job object named Smith_ivj2 that is contained in
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Initial-Value-Job and Initial-Value-Document Objects NOTE You do not have to specify a class (or use the -c flag) with the pdset command when performing configuration tasks for logical printers. printer is the default class for the pdset command. If the logical printer with which you want to associate the initial value object is enabled, you must disable it with the pddisable command to set the association.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers Creating and Configuring Logical Printers You use logical printers to set up the flow of jobs in your system. Among other things, they provide job and document defaulting and enable restricting of access to physical printers. You can create and configure logical printers using SAM or the command line interface, as described below.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers Configuring the Logical Printer Because logical printers perform so many important functions, how you configure logical printers is a large part of configuring your system.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers Figure 6-4 Job Defaulting and Validation The steps shown in the figure are: 1. Determining the job and document attribute values. 2. Validating the job against the logical printer to which the job was submitted. Values specified for logical printer attributes represent a restriction to the use of a physical printer function or some other use of a physical printer.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers If the logical printer validation or all of the physical printer validations fail, HPDPS rejects the job and the user receives an error message informing him of which job or document attributes or attribute values are not supported. The values for job and document attributes are derived from the following, in order of precedence: 1. Specific values assigned by the user with the pdpr command and the -x flag. 2.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers During logical printer validation, the spooler verifies that the job and document attribute values are supported by the logical printer. It compares the job and document attribute values to the xxx-supported attributes of the logical printer. For example, HPDPS compares the print-quality document attribute to the print-qualities-supported logical printer attribute.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers For example, if the user submits a job specifying the document attribute content-orientation=landscape, then the landscape value is compared to physical printer attribute content-orientations-supported. • Job attributes that request a particular type of printer, such as printer-models-requested.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers For complete information on document, job and printer attributes, see pd_att_document(5), pd_att_job(5), and pd_att_phy_ptr(5).
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers Table 6-1 Common Document Attributes Validated by Printer Attributes Document Attribute Name Default Printer Attribute Name Supported Values copy-counta 1 maximum-copies-sup ported 1..2147483647 plex No default plexes-supported simplex duplex sides No default sides-supported 1..
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers Physical Printer Selection Attributes There are a number of job attributes that enable users to request that their jobs should be sent to a specific physical printer or to a certain type of physical printer. These attributes are only useful for configurations with a queue that sends jobs to more than one printer. They request a particular printer or type of printer in the printer pool.
Configuring Spoolers, Queues, and Logical Printers Creating and Configuring Logical Printers NOTE Any individual value specified for this attribute can select more than one physical printer. For example, the printers could all be in the same location, such as a printer room. The values for both the job and printer attributes must match exactly, including embedded blanks, for validation to occur.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction Configuring Logical Printers for Defaulting and Restriction This section describes how to configure logical printers to provide default values for jobs and documents. It provides example logical printer configurations with initial value objects that provide the default values, and gives example commands to create the logical printers, initial-value-job, and initial-value-document objects.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction Using an Initial Value Object for Job and Document Defaulting This section describes how to create a logical printer and an initial-value-document object associated with the logical printer. The initial-value-document object provides default values for documents of jobs submitted to the logical printer. The example uses the desktop configuration model, as described in Chapter 3.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction Figure 6-5 Using Initial Value Objects for Job and Document Defaulting In this configuration, because the logical printer attributes do not have values, HPDPS only validates against the values of the physical printer attributes. The initial-value-document object IVD1 assigns default values to all jobs submitted to LogPrt1. These can be overridden by values assigned by the job submitter.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction “Planning Your HPDPS Configuration,”, by adding a logical printer or printers to the former model. It starts with the example given in “Using an Initial Value Object for Job and Document Defaulting”.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction Figure 6-6 Adding Logical Printers to a Desktop Configuration To create a logical printer associated with Queue1 with an initial-value-job object for job defaulting and an initial-value-document object for document defaulting, perform the following steps: 1.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction 3. Create the logical printer, LogPrt3: pdcreate -x "printer-initial-value-document=IVD2 \ printer-initial-value-job=IVJ1 \ associated-queue=Queue1" Spool1:LogPrt3 Jobs submitted to LogPrt3 will have some job attribute values provided by IVJ1 and will have some document attribute values provided by IVD2.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction Figure 6-7 Using Logical Printers to Restrict Printer Capabilities You use the values for the logical printer xxx-supported attributes, such as maximum-copies-supported and sides-supported, to restrict the availability of capabilities and features.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction have default values, for these attributes, you must use initial value objects to ensure the restriction. See “Using Initial Value Objects to Ensure Restriction” in the next section for details. All logical printers use the same xxx-supported attributes. However, the supported attributes for physical printers differ between printer models.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction pdcreate -x "associated-queue=Queue2 \ printer-initial-value-document=IVD3 \ sides-supported=2" Spool1:LogPrt5 • To create the initial-value-document object IVD3, enter: pdcreate -c initial-value-document \ -x "sides=2" Spool1:IVD3 • To create logical printer LogPrt6, enter: pdcreate -x "associated-queue=Queue2 \ printer-initial-value-document=IVD3 \ sides-supported=2" Spool1:LogPrt6 The initial
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Defaulting and Restriction fails. The user cannot override the initial-value-document object by attempting to request no value or the default value for the job or document attribute with a print submission. The request fails if a user enters either of the following print submissions to attempt to get around the restriction imposed by this configuration: pdpr -p LogPrt6 -x "sides= " File3.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Workload Balancing Configuring Logical Printers for Workload Balancing This section describes how to create a logical printer for a printer pool configuration of logical printers, queues, and physical printers. It presents a sample configuration which will illustrate how to: • Balance the printing workload of your system by configuring a queue to send jobs to multiple physical printers.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers for Workload Balancing The main advantage of the printer pool configuration is that it balances the workload of jobs submitted to the system. Jobs in Queue3 that can print on both physical printers will print on the printer that becomes available first.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security Configuring Logical Printers with DCE Security DCE security is available in the DCE Extended Environment only. This section describes how to use DCE security to restrict access to physical printers. Tasks covered include: • Using DCE in association with configurations with one logical printer to restrict access to physical printers.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security 1. create a DCE group for the logical printer and give the group read permission to the logical printer 2. give each person who will use the logical printer an account in the group When logged in to DCE, members of the group can submit jobs to the logical printer. See “Planning a Group for People Who Will Use Restricted Printers” in Chapter 8 for more information about using DCE with logical printers.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security The logical printer in this configuration does not impose any restrictions on the use of the physical printer. HPDPS performs job validation at the physical printer level only. Using DCE to Restrict Access with Multiple Logical Printers This section shows how to use DCE to restrict access to a physical printer that receives jobs from more than one logical printer through its associated queue.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security Figure 6-10 Using DCE to Restrict Access with Multiple Logical Printers To create the logical printers shown in Figure 6-10, “Using DCE to Restrict Access with Multiple Logical Printers,”, perform the following steps: • To create LogPrt13, enter: pdcreate -x "authorize-jobs=true associated-queue=Queue6" \ Spool1:LogPrt13 • To create LogPrt14, enter: pdcreate -x "authorize-jobs=true \ printer-initial-value-do
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security Using Logical Printers and DCE to Restrict Capabilities This section describes how to use DCE to restrict access to physical printers in combination with logical printers that restrict the use of physical printer capabilities.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security Figure 6-11 Using Logical Printers and DCE to Restrict Capabilities To create the four logical printers shown in Figure 6-11, “Using Logical Printers and DCE to Restrict Capabilities,”, do the following: • To create LogPrt15, enter: pdcreate -x "document-formats-supported=ascii pcl postscrip t \ Chapter 6 147
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security printer-initial-value-document=IVD5 \ associated-queue=Queue7 \ sides-supported=2" Spool1:LogPrt15 • To create LogPrt16, enter: pdcreate -x "authorize-jobs=true associated-queue=Queue7" \ Spool1:LogPrt16 • To create LogPrt17, enter: pdcreate -x "document-formats-supported=ascii postscript \ job-size-range-supported=0:999999 \ printer-initial-value-document=IVD5 \ associated-queue=Queue7 \ sides-supported=2" S
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers with DCE Security jobs can be directed to either of the physical printers and they can use all other capabilities of PhyPrt10 and PhyPrt11. • LogPrt17 users can only print jobs with document formats of ascii and postscript. The users are restricted to the size of jobs that they can submit. Users can only print relatively small, two-sided jobs. • LogPrt18 users can print jobs with any supported document format.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers as HPDPS Gateway Printers Configuring Logical Printers as HPDPS Gateway Printers To access a remote environment, you must create an HPDPS Gateway Printer in the local environment for a logical printer in the remote environment. You use the pdcreate command to create a logical printer in the spooler, while specifying a special set of attributes as shown here:.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers as HPDPS Gateway Printers When an HPDPS Gateway Printer target is added, deleted, or moved to a new host, every HPDPS Gateway Printer in your network that references that target must be updated accordingly. HPDPS Gateway Printers can be "chained" together; that is, an environment can define an HPDPS Gateway Printer whose target is another HPDPS Gateway Printer in the remote environment.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers as HPDPS Gateway Printers • The attributes of the spooler for a remote printer can be listed using pdls. The attributes of any initial-value-document, initial-value-job, job, log, logical printer, and queue objects contained in that spooler can also be listed. The following operations cannot be performed on the remote environment via a HPDPS Gateway Printer: • Jobs cannot be cleaned from a remote printer or server via pdclean.
Configuring Spoolers, Queues, and Logical Printers Configuring Logical Printers as HPDPS Gateway Printers the pdgwcfg(1M) utility. The administration of Gateway Printers on many hosts can be accomplished by distributing a single configuration file; see pdgwcfg.conf(4) for more information. pdgwcfg will create and enable and/or delete Gateway Printers as appropriate for a particular host. A sample of a pdgwcfg.conf entry follows. See the manpage for more detail. # /etc/pdgwcfg.
Configuring Spoolers, Queues, and Logical Printers Other Logical Printer Configuration Tasks Other Logical Printer Configuration Tasks This section describes some miscellaneous tasks you may need to perform when you create logical printers. Specifying a Description for the Logical Printer Use the descriptor attribute to specify a text string up to 4095 characters in length that describes the logical printer.
Configuring Spoolers, Queues, and Logical Printers Other Logical Printer Configuration Tasks notification-profile logical printer attribute determines which messages you receive. The default events for the logical printer notification-profile attribute are object-cleaned and object-deleted. The delivery-address component of this attribute defaults to the UserName of the administrator who created the logical printer, and the delivery-method component defaults to electronic-mail.
Configuring Spoolers, Queues, and Logical Printers Other Logical Printer Configuration Tasks After you create and enable a logical printer, you can submit a test job to it to verify that it and its associated queue and physical printer or printers are correctly configured.
Using Notification 7 Using Notification HP Distributed Print Service provides notification about events in the form of messages that you can tailor depending on the needs of users, operators, and administrators. For example, users can receive information about their own jobs, operators can receive information on HPDPS objects that may require attention, and administrators can receive HPDPS configuration information.
Using Notification What Is Notification? What Is Notification? Notification is the detection of events as they occur and the automatic generation and delivery of notification messages relating to those events. HPDPS sends notification messages related to objects to one or more users based on the notification-profile attribute of these objects. The person who manages a queue can be notified of all jobs that cannot be scheduled. Individual users can receive the same notification about their own jobs.
Using Notification Understanding the notification-profile Attribute Understanding the notification-profile Attribute You use the notification-profile attribute to configure notification profiles of specific HPDPS objects for specific HPDPS events pertaining to the object. You can create or modify a notification profile by using the pdcreate, pdmod, pdpr, or pdset commands depending on the object.
Using Notification Understanding the notification-profile Attribute • The sequence in which the components are entered is not important. event-identifiers Component This component specifies the events for which the user receives messages. This component is the only component that can have multiple values within a notification-profile attribute value. HPDPS uses default values if you do not specify values.
Using Notification Understanding the notification-profile Attribute no error is identified. HPDPS accepts this but never provides any messages for that event because the event will never occur for that type of object. delivery-method and delivery-address Components delivery-method This component specifies the method by which a person receives the event messages. Possible values are: electronic-mail, message, file, file-add-to, and none.
Using Notification Understanding the notification-profile Attribute user delivery-address value of dave@sys1.com and a delivery-method value of e-mail. If you want to retain the existing component values within the brace characters of a notification-profile, you must specify each component value. You cannot use the add (+=) operator of the pdset command to change a single component value.
Using Notification List of Notification event-identifiers List of Notification event-identifiers The following table alphabetically lists the names of individual events that you can specify as values for the event-identifiers component of the notification-profile attribute.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Message: Message from the printer backend program: Printer Printer1 has encountered a problem. document-aborted-by-printer • class-aborted • Job • class-job-attention • • class-job-default Physical Printer • Supervisor Description: The supervisor or printer aborted the document, errors were encountered during processing. Message: Document 1 (myfile.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Message: An error was detected in document 1 (myfile.txt) of job 1 (Super1:1234567890) during printing. file-transferred • class-job-status • class-report • Job Description: A file transfer was successfully completed. The file can now be modified without affecting the printed output. The document is being processed by HPDPS.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported job-cancelled-by-operator • class-aborted • Job • class-job-attention • • class-job-default Physical Printer • Queue • Spooler • Supervisor Description: The operator or administrator deleted the job. Message: Job 1 (Spool1:1234567890) was cancelled by the operator or administrator.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported job-completed • class-job-default • Job • class-job-status • • class-report Physical Printer • Queue • Spooler • Supervisor Description: The job completed processing. It might or might not have printed successfully. Check the printed output. Message: Job name /etc/motd with id 1 (Spool1:1234567890) has completed printing on PhyPrt1.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported job-promoted • class-job-status • Job • class-report • Queue • Spooler • Job Description: The job was promoted. Message: Job 1 (Spool1:1234567890) was promoted.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Description: The state of the job has changed. Job processing continues. Message: The state of job 1 (Spool1:1234567890) changed to pending.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Message: The resource Res12 needed by job 1 (Super:1234567890) was not available.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported object-deleted • class-logical-printer-con figuration • Logical Printer • • class-logical-printer-def ault Physical Printer • Queue • class-physical-printer-co nfiguration • Spooler • class-physical-printer-de fault • Supervisor • class-queue-configuration • class-queue-default • class-server-configuratio n • class-server-default • cl
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported object-paused • class-physical-printer-at tention • Job • • class-queue-attention Physical Printer • class-warning • Queue • Spooler • Supervisor Description: A printer or queue was paused and cannot process jobs. Message: Successfully paused object queue Spool1:Queue1.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Description: The object has encountered a warning condition that could not be described by any other event. This warning condition might precede an error. Check the error log for messages related to this failure. Message: Server Super1 has encountered a warning condition.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Message: Successfully enabled printer Super1:PhyPrt1. printer-function-unavailabl e • class-job-attention • • class-physical-printer-st atus Physical Printer • Supervisor • class-warning Description: The printer requires a printer function, such as duplex or offset stacking, that is not available. The function is disabled, but printing continues.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported printer-needs-operator • class-job-attention • Job • class-job-default • • class-physical-printer-at tention Physical Printer • Supervisor • class-physical-printer-de fault • class-warning Description: A physical printer needs operator attention. The printer cannot process jobs until it receives attention.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Description: The physical printer is out of paper. Message: Physical printer Super1:PhyPrt1 paper out on Spool1:Queue1.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Message: Printer Super1:PhyPrt1 was shut down after job 1 (Spool1:1234567890) started processing. printer-state-changed • class-physical-printer-st atus • class-state-changed • Physical Printer Description: The printer state changed. Processing continues. Message: The state of printer Super1:PhyPrt1 changed to paused.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported printer-unregistered • class-physical-printer-st atus • Physical Printer • class-warning • Queue • Spooler • Supervisor Description: A physical printer is no longer registered with a spooler and jobs can no longer be scheduled to print on the printer. Message: Printer Super1:PhyPrt1 is no longer registered with Spool1:Queue1.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported queue-no-longer-backlogged • class-queue-status • Jobs • class-report • Queue • Spooler Description: The queue is no longer backlogged. HPDPS calculates that the jobs currently in the queue will print within the amount of time specified for the queue-backlog-lower-bound attribute. Message: The queue Spool1:Queue1 is no longer backlogged.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Description: This server has shut down. The server is no longer available. Message: Successfully shut down supervisor Super1. server-shutdown-started • class-server-attention • Spooler • class-warning • Supervisor Description: This server has begun to shut down. Jobs are not accepted by this server. Message: The spooler Spool1 is shutting down.
Using Notification List of Notification event-identifiers Table 7-1 Description of Event Identifier Values Event Event Class Objects Supported Description: A resource required for this job is not known to the server. The job was aborted. Check the server error log for messages related to this failure. Message: Resource Res6 that is required for job 1 (Super1:1234567890) is not known to the server.
Using Notification List of Notification Event Classes List of Notification Event Classes An event class is an easy way to include multiple events in a value. Events are grouped in event classes based on the functions for which they provide notification. For example, some classes are specific to configuration tasks while other classes provide information about the status of HPDPS objects. Each event class name begins with class. An event identifier can occur in more than one class.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-aborted document-aborted-by-printer document-aborted-by-server document-cancelled-at-printer job-aborted-by-server job-cancelled-by-operator job-cancelled-by-user An aborted event occurs whenever a server aborts a job or document, or when the user or operator cancels a job.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-job-attention close-to-discard-time detailed-messages document-aborted-by-printer document-aborted-by-server document-cancelled-at-printer job-aborted-by-server job-cancelled-by-operator job-cancelled-by-user job-cannot-be-scheduled job-discarded job-paused job-timed-out past-discard-time printer-function-unavailable printer-needs-administrator printer-needs-attention printer-ne
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-job-default document-aborted-by-printer document-aborted-by-server document-cancelled-at-printer job-aborted-by-server document-cancelled-at-printer job-aborted-by-server job-cancelled-by-operator job-cannot-be-scheduled job-completed job-discarded printer-needs-attention printer-needs-operator This is the default event class for jobs.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-job-status checkpoint-taken file-transferred job-assigned-to-queue job-completed job-modified job-promoted job-requeued job-resubmitted job-resumed job-state-changed processing-started This event class includes events that give detailed status about the job. These changes in status are often routine and do not require intervention.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-logical-printer-default • object-cleaned • object-deleted This is the default event class for logical printers. class-logical-printer-status • object-cleaned • printer-enabled This event class includes events that give detailed status about the logical printer. These changes in status are often routine and do not require intervention.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-physical-printer-configura tion object-created object-deleted object-modified printer-disabled printer-enabled printer-needs-administrator printer-needs-attention printer-needs-operator printer-shutdown printer-timed-out resource-needs-attention resource-needs-operator These events have to do with the creation or deletion of a physical printer, or with modification of the attri
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-physical-printer-status object-cleaned object-resumed printer-enabled printer-function-unavailable printer-registered printer-state-changed printer-unregistered server-state-changed This event class includes events that give detailed status about the physical printer. These changes in status are often routine and do not require intervention.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-queue-default object-cleaned object-deleted queue-backlogged This is the default event class for queues. class-queue-status object-cleaned object-resumed queue-backlogged queue-no-longer-backlogged queue-state-changed This event class includes events that give detailed status about the queue. These changes in status are often routine and do not require intervention.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-report checkpoint-taken detailed-messages file-transferred job-assigned-to-queue job-completed job-discarded job-promoted job-resubmitted job-resumed object-created object-deleted object-resumed printer-enabled printer-registered processing-started queue-no-longer-backlogged server-shutdown-complete server-startup-complete A report event occurs whenever a significant point in p
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-state-changed job-state-changed printer-state-changed queue-state-changed server-state-changed A state-change event occurs whenever the state of a job, queue, printer, or server object changes.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-server-default internal-server-error object-cleaned object-deleted server-shutdown-complete This is the default event class for supervisors and spoolers. class-server-status object-cleaned server-state-changed This event class includes events that give detailed status about the supervisor or the spooler.
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-warning close-to-discard-time job-cannot-be-scheduled job-modified job-paused job-requeued job-timed-out object-cleaned object-modified object-paused other-warning printer-disabled printer-function-unavailable printer-needs-administrator printer-needs-attention printer-needs-operator printer-shutdown-job-requeued printer-timed-out printer-unregistered queue-backlogged resource-n
Using Notification List of Notification Event Classes Table 7-2 Event Classes Event Class Individual Events Description class-warning (cont.) A warning event occurs whenever a condition arises which affects processing. Generally, a warning event signals a condition that does not prevent completion of the processing, but might indicate that some action is required on the part of the operator or user.
Using Notification Understanding Default Notification Understanding Default Notification By default, the person who creates an object, such as a server, receives the notification messages for that object. The notification messages for the default events provide information on topics such as status conditions, error conditions, or configuration changes. Some of these events require intervention by the person managing the object, such as when a printer device requires attention for a paper jam.
Using Notification Understanding Default Notification Table 7-3 Default Events for Objects Object Default Events physical printer object-cleaned object-deleted printer-needs-administrator printer-needs-attention printer-needs-operator printer-paper-jam printer-paper-out printer-paper-output-problem printer-timed-out printer-toner-low queue object-cleaned object-deleted queue-backlogged spooler internal-server-error object-cleaned object-deleted server-shutdown-complete supervisor internal-server-
Using Notification Understanding Default Notification pdset -c queue -x "notification-profile= \ {delivery-address=tom@hope}" Queue1 198 Chapter 7
Using Notification Adding, Replacing, or Deleting Values from Notification Profiles Adding, Replacing, or Deleting Values from Notification Profiles This section contains the following examples: • displaying the contents of a notification profile • modifying the notification profiles for HPDPS objects and customizing the lists of events You can customize notification profiles to specify who receives notification messages for a specific object.
Using Notification Adding, Replacing, or Deleting Values from Notification Profiles want). See “delivery-method and delivery-address Components” earlier and “Sending Different People Messages for the Same Object” shortly for more information on the use of these operators. You can have many events for a given person in one notification profile value or you can have two values for the same person but with different delivery methods for the same or different events.
Using Notification Displaying the Contents of a Notification Profile Displaying the Contents of a Notification Profile Use the -c flag, -g, and -r notification-profile with the pdls command to display the values without headings for the notification profile of a specific HPDPS object. Displaying the contents of the notification profile is useful if you do not remember what the events are for a given object.
Using Notification Creating a Notification Profile Creating a Notification Profile An example of creating a notification profile with one value and every component specified for a queue is: pdset -c queue -x "notification-profile= \ {event-identifiers=job-modified queue-state-changed \ delivery-method=e-mail delivery-address=dave@cowboy \ event-comment='This is a job modification or status event' \ locale=C}" Queue1 Adding a Value to a Notification Profile An example of adding a value to the notification
Using Notification Creating a Notification Profile The event-identifier class-physical-printer-attention does not contain the event printer-shutdown and the user jjones wants to know any time that PhyPrt1 is shutdown.
Using Notification Creating a Notification Profile concerning any of the default events for queue Queue1 contained in spooler Spool1. Assumptions for this example: • You want him to receive the message whether he is logged on or off. Because of this, jjones will receive some duplicate messages when logged on, one set on the display and the other set using electronic mail. • You do not want to delete any other values you might have set or were set for you when you created this queue.
Using Notification Creating a Notification Profile Enter: pdset -c queue -x "notification-profile+= \ {event-identifier=queue-backlogged delivery-method=e-mail}" \ Queue1 You have taken advantage of the defaulting conditions of the notification profile. • One value will be added to the existing values. • The added value will have one event (queue-backlogged) and a delivery-method of electronic-mail. • The added value will have the default of your locale and your delivery-address.
Using Notification Creating a Notification Profile Using Just the delivery-address Component If you just use the component delivery-address, you can add or remove values that have a delivery-method of e-mail for a specific HPDPS object. You can also use it to replace an existing value with one that contains the default values for the components of the specified object.
Using Notification Creating a Notification Profile Attributes File Creating a Notification Profile Attributes File You can set values for a notification-profile attribute by entering attribute information on the command line. This requires an excessive amount of typing, however, and leaves room for error. You might find using an attributes file to specify events for the notification-profile attribute to be more efficient.
Using Notification Creating a Notification Profile Attributes File Queue1:notification-profile= {event-identifiers=object-deleted object-cleaned delivery-method=message delivery-address="lisah" locale=C} {event-identifiers=queue-backlogged class-queue-status close-to-discard-time delivery-method=electronic-mail delivery-address="kathyw@sys1.
Using Notification Notification Profile Examples by HPDPS Object Type Notification Profile Examples by HPDPS Object Type This section shows examples of notification profiles. In some of the examples, the events specified apply to both the main object, such as a spooler, and objects contained within the object, such as a queue. Spooler Notification Profile Examples These examples show how you can set up a notification profile for a spooler.
Using Notification Notification Profile Examples by HPDPS Object Type Example 2 The following example shows how you can set up a notification profile for a spooler and also specify events that apply to the logical printers and queues contained in the spooler. The spooler contains multiple logical printers and queues. Assumptions, Example 2: • The primary operator (adgreen) is responsible for managing the spooler. • The backup operator (fgbrown) is to be notified for the same set of events.
Using Notification Notification Profile Examples by HPDPS Object Type delivery-method=electronic-mail \ delivery-address=adgreen@poplar.xyz.com} \ event-identifiers=class-server-attention \ class-server-configuration \ object-cleaned \ object-created \ object-deleted \ object-modified \ queue-backlogged \ delivery-method=message \ delivery-address=adgreen@poplar.xyz.
Using Notification Notification Profile Examples by HPDPS Object Type Logical Printer Notification Profile Examples These examples show how you can set up notification profiles for logical printers. Example 1 In this example, an operator (fpjones) is responsible for managing any event that requires intervention of the logical printer operation. The administrator (lbjohnson) wants to know about any configuration events that occur on this logical printer.
Using Notification Notification Profile Examples by HPDPS Object Type you want, specify both the delivery-method and value and delivery-address and value. Queue Notification Profile Example Example In this example, you set up a notification profile for a queue, including assigning job-related events for the queue. An operator (jhpong) is responsible for managing a single queue (Queue2 in Spool2) and wants notification for certain events concerning the queue and jobs within the queue.
Using Notification Notification Profile Examples by HPDPS Object Type — job-cannot-be-scheduled — job-discarded Supervisor Notification Profile Example The following example shows a supervisor notification profile. This notification profile also specifies events that apply to the physical printers contained in the supervisor. Example Assumptions: • The administrator (jswhite) who created the supervisor is also responsible for managing the supervisor (Super1).
Using Notification Notification Profile Examples by HPDPS Object Type delivery-address=jswhite@poplar.xyz.com locale=C} {event-identifiers=class-server-attention printer-needs-administrator delivery-method=message delivery-address=jswhite@poplar.xyz.
Using Notification Notification Profile Examples by HPDPS Object Type NOTE The example shown here uses an attributes file to specify the new notification profile. The text of the attributes file follows the command. To modify the notification-profile attribute of the supervisor Super2 to reflect the responsibilities of administrator and operator, the administrator, lbjohnson, would enter the command: pdset -c server -X SuperAdmOper.notif Super2 where the file SuperAdmOper.
Using Notification Notification Profile Examples by HPDPS Object Type Discussion: • The printer events, contained in the class-physical-printer-configuration, specified for the operator fpjones, apply to all of the physical printers in the supervisor.
Using Notification Notification Profile Examples by HPDPS Object Type Example 1 This example shows a possible notification profile for an initial-value-job object. Assumptions: • For select jobs, you want your assistant, Todd, to receive messages that indicate problems, such as the printer needs paper and a message when a job is complete so it can be picked up. • You want to receive messages concerning all events covered by the class class-job-default by message.
Using Notification Notification Profile Examples by HPDPS Object Type This creates the initial-value-job object IVJGrp1 and associates it with logical printer LogPrt2 in spooler Spool3. The notification profile contains: notification-profile= {event-identifiers=class-job-default close-to-discard-time past-discard-time job-timed-out delivery-method=message locale=C} Note that the delivery-address component is missing.
Using Notification Notification Profile Examples by HPDPS Object Type You can submit your job and use the -X flag to bring in an attributes file that contains the notification profile you want to use.
Using Notification Getting Help for Notification Messages Getting Help for Notification Messages Use the pdmsg command and specify the message number to display help for notification messages you receive. For example, you receive notification messages similar to the following regarding the backlogged status of Queue1 contained in the spooler Spool1. To: syoussef@hope.bpc.datacom.com Subject: 5010-192 Message from HPDPS server: Spool1 [05/23/95 07:26:381] 5010-304 The queue Spool1:Queue1 is backlogged.
Using Notification Summary Tables for the notification-profile Attribute Summary Tables for the notification-profile Attribute Table 7-4 provides information on the commands used to set the components for a notification-profile attribute for the different objects as well as showing the syntax definition. Table 7-4 Notification Profile Attribute Summary Purpose: Designates which persons are to be notified of specific events relating to a given object, and how the persons are to be notified.
Using Notification Summary Tables for the notification-profile Attribute Table 7-4 Syntax: Notification Profile Attribute Summary -x "notification-profile= {event-identifiers=values delivery-address=value delivery-method=value event-comment='text' locale=value}" For example: -x "notification-profile= {event-identifiers=class-error delivery-address=mary@travel delivery-method=electronic-mail event-comment='fix problem' locale=C}" Table 7-5 presents a summary of the notification profile components.
Using Notification Summary Tables for the notification-profile Attribute Table 7-5 • Notification Profile Component Descriptions Explanation: The method by which the person is to receive the event messages. You can use this component to add, replace, or delete values in a notification profile. For more information see “delivery-method and delivery-address Components” earlier. • Value Type: Single value.
Using Notification Summary Tables for the notification-profile Attribute Table 7-5 • Notification Profile Component Descriptions Explanation: The address of the person to receive the event messages. You can use this component to add, replace, or delete values in a notification profile. For more information see “delivery-method and delivery-address Components” earlier. • Value Type: Single value.
Using Notification Summary Tables for the notification-profile Attribute Table 7-5 Notification Profile Component Descriptions event-comment This is an optional component. • Explanation: Supplies textual information that is appended to the event message. • Value Type: Single value. • Values: A text string up to 4095 characters that supplies additional information concerning the event. • Default: No value. locale The locale value is based on the LANG environment variable.
Managing DCE Security for HPDPS 8 Managing DCE Security for HPDPS Distributed Computing Environment (DCE) is an application that allows the secure use and administration of distributed applications such as HP Distributed Print Service (HPDPS). HPDPS optionally uses DCE for security services when executing in a DCE cell. HPDPS must be configured to execute in the DCE Extended Environment in order to use DCE security services. Managing DCE security is similar to managing UNIX security.
Managing DCE Security for HPDPS DCE Documentation DCE Documentation Table 8-1 lists the books available from Prentice-Hall.
Managing DCE Security for HPDPS Determining Appropriate DCE Permissions for HPDPS User Groups Determining Appropriate DCE Permissions for HPDPS User Groups This section discusses examples of four different categories of users who need different kinds of permission for HPDPS objects. In the examples, you will see how to give each category the minimum permissions necessary to do a given job.
Managing DCE Security for HPDPS Determining Appropriate DCE Permissions for HPDPS User Groups End Users NOTE This group needs to be able to print jobs, modify their own jobs, cancel their own jobs, and query HPDPS objects. If most printers will be available to all users, and if all printer functions will be available to all users, then users do not need to log in to DCE. When you do not restrict a printer, a user does not have to log in to DCE to submit, modify, query, and cancel jobs.
Managing DCE Security for HPDPS Deciding Which Groups Your Organization Needs Deciding Which Groups Your Organization Needs When you execute the pddcesetup command, the command creates two DCE groups: pd_admin and pd_operator. By default, these groups have permissions for every object in every HPDPS system you create. This includes spoolers, supervisors, queues, logical and physical printers, and other objects.
Managing DCE Security for HPDPS Creating Additional Groups Creating Additional Groups This section gives examples of different groups you can create to supplement the two default groups, pd_admin and pd_operator. This section discusses two examples: • The printer operator group • The group for users of restricted printers You also can create additional groups for system operators and administrators.
Managing DCE Security for HPDPS Creating Additional Groups printers that allow the correct permissions to your printer operator groups. 1. First, decide which supervisors will contain the physical printers representing printer devices in a particular printer room. You will probably want to create new, dedicated supervisors using the pdstartsuv command. 2.
Managing DCE Security for HPDPS Creating Additional Groups Permissions to HPDPS Objects” later for an explanation of how to do this. Planning a Group for People Who Will Use Restricted Printers This section discusses two ways you can use DCE to restrict printers.
Managing DCE Security for HPDPS Creating Additional Groups an entry from an object ACL, see “Taking Away All Permissions That any_other and unauthenticated Have to an HPDPS Object” later. 3. Create a DCE group and give the group read permission for the logical printer. 4. Give an account to each person who will use the logical printer and add them to the group. When logged in to DCE, members of the group can submit jobs to that logical printer.
Managing DCE Security for HPDPS Creating Additional Groups and add them to the group. When logged in to DCE, members of the group can submit jobs to that logical printer. 3. On the unrestricted logical printers that are available to everyone, use the pdset command to set the xxx-supported attributes, such as sides-supported and document-formats-supported, to only the values you want available to everyone.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects Giving Your DCE Groups Permissions to HPDPS Objects When you have set up groups of users according to your organizational requirements, you need to give the groups appropriate permissions to your HPDPS objects. Understanding Where HPDPS Security Information is Stored Part of DCE is a directory tree called the DCE namespace.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects directory also are created automatically for every supervisor when it is created. A printer directory (for logical printers) is created automatically for every spooler when the spooler is created. A queue directory, other directory, and log directory also are created automatically for every spooler when it is created. There is one very important difference between the way that DCE permissions and UNIX permissions work.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects PhysPrt1 cannot inherit and will not grant the new permissions. There are two ways to make PhysPrt1 grant the new permissions: 1. You can set the new permissions on the PhysPrt1 entry individually. 2. You can delete PhysPrt1, grant the new permissions to the printer directory, and then create PhysPrt1 again. Its entry in the security directory will then inherit the new permissions from the /.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects Figure 8-1 Propagation of DCE Permissions Each DCE container has an IO ACL and an IC ACL. Setting the IO ACL and the IC ACL of a container affects subsequently created entries within the container as follows: • For subsequently created child entries that are themselves containers: — The parent container IC ACL becomes both the IC ACL and the object ACL of the child container.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects Referring to Figure 8-1, “Propagation of DCE Permissions,”, the object ACL of object b is inherited from the IO ACL of Container B. For example, the object ACL for a logical or physical printer is inherited from the IO ACL of the printer directory of the server containing that printer. The permissions are propagated from the IO ACL of the /.:/pdsec directory through the supervisor and printer containers.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects default_error log object, which represents the error log for the supervisor. The Spool6 entry also is a DCE container that contains the queue container in addition to the other containers for supervisor entries (none are shown). The printer directory contains the entries for the logical printer objects contained in the spooler, and the queue directory contains the entries for the queue objects.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects NOTE The following procedure modifies the IC ACL of the /.:/pdsec directory, which propagates to the object ACL of all of the HPDPS servers. It also modifies the IO ACL of the /.:/pdsec directory, which propagates to the object ACLs of all of the HPDPS objects contained in the servers. Depending on what you want to accomplish, you can modify either one or the other, but not both.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects 2. List the ACL. For example enter: list 3. These commands return a display similar to this: # Initial SEC_ACL for objects created under: /.:/pdsec : # Default cell = /…/pda_cell.your_organization.com unauthenticated:r--t--group:subsys/dce/cds-admin:rwdtc-group:subsys/dce/cds-server:rwdtc-group:pd_admin:rwd---group:pd_operator:rw----any_other:r--t--group:Dept_6_OPs:rw----- 4.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects 1. Use the -d flag to delete the permissions the group has to the object. For example, enter: acl_edit /.:/pdsec -io -d group:Dept_6_OPs: 2. Remove the Dept_6_OPs group read and write permissions for the IC ACL of the security directory. For example, enter: acl_edit /.:/pdsec -ic -d group:Dept_6_OPs: The security directory IO and IC ACLs no longer contain entries for the Dept_6_OPs group.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects When prompted, enter the cell administrator password. 2. Use the acl_edit command to give the 203_Operators group read and write permission for the IO ACL of the /.:/pdsec/Super203/printer directory. • Use the -io flag to specify the IO ACL • Use the -m flag to modify the ACL For example, enter: acl_edit /.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects Examples of Specifying Different Kinds of Objects • To change the permissions granted by the spooler Spool1, edit the …/srvr_objs/Spool1 ACL for the object. • To change the permissions granted by the queue Queue1, contained in the spooler Spool1, edit the …/srvr_objs/Spool1/queue/Queue1 ACL for the object.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects You can use this same method to set the permissions that any HPDPS object grants. Taking Away All Permissions That a Group Has to an Individual HPDPS Object There might be times when you want to remove the permissions that a group has to an HPDPS object. For example, you might decide to remove the pd_operator group permissions from a server that you want to be supported exclusively by a different group.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects 1. If you have not already done so, log in to DCE as the cell administrator. For example, if the cell administrator DCE login is cell_admin, enter: dce_login cell_admin When prompted, enter the cell administrator password. 2. Use the acl_edit command to remove permissions for unauthenticated. • Use the -e flag because you are modifying an object ACL rather than an IO or IC ACL. • Use the pdsec soft link.
Managing DCE Security for HPDPS Giving Your DCE Groups Permissions to HPDPS Objects 250 Chapter 8
9 Managing Spoolers, Queues, and Logical Printers This chapter describes tasks for managing spoolers, queues, and logical printers. These tasks include: • Making policy decisions on how to use certain attributes for spoolers and objects contained in spoolers. • Querying for spooler, queue, and logical printer status. • Performing job-related management tasks for spoolers, queues, and logical printers. • Shutting down and deleting a spooler, and deleting queues, logical printers, and initial value objects.
Managing Spoolers, Queues, and Logical Printers Monitoring Spooler, Queue, and Logical Printer Configurations Monitoring Spooler, Queue, and Logical Printer Configurations The tasks in this section involve making decisions on how to track changes made to spooler, queue, and logical printer configurations by: • defining when and how to use the message attribute • creating archive files for spoolers, queues, logical printers, and initial value objects Setting the Message Attribute for Spoolers, Queues, and
Managing Spoolers, Queues, and Logical Printers Monitoring Spooler, Queue, and Logical Printer Configurations attribute or attributes were changed, who changed them, and when the changes were made. NOTE If you modify an object using the -m flag, then modify the object again omitting the -m flag, the message attribute will still contain the message text. This can cause users querying for the message text to receive incorrect information.
Managing Spoolers, Queues, and Logical Printers Monitoring Spooler, Queue, and Logical Printer Configurations • To create an archive file for the logical printer LogPrt1, enter the command: pdls -c printer -r archive LogPrt1 > /attr/LogPrt1.archive • To create an archive file for the initial-value-job IVJob1, enter: pdls -c initial-value-job -r archive IVJob1 > \ /attr/IVJob1.
Managing Spoolers, Queues, and Logical Printers Querying for Spooler Information Querying for Spooler Information This section describes how to query the values of attributes that reflect the state of the spooler and the associations between the spooler and other HPDPS objects. Querying for the State of a Specific Spooler Use -c server with the pdls command to query the state of a spooler. The value of the non-settable server-state spooler attribute indicates the state of the spooler.
Managing Spoolers, Queues, and Logical Printers Querying for Spooler Information State Description initializing The spooler process is initializing. ready The spooler has finished initializing and its logical printers can accept jobs if they are enabled. terminating The spooler is shutting down. The logical printers contained in the spooler will not accept new jobs, and existing jobs might or might not be scheduled.
Managing Spoolers, Queues, and Logical Printers Querying for Spooler Information Use the following commands to query job and document attributes supported by spooler Spool1: To display the job attributes supported by the spooler Spool1, enter the command: pdls -c server -r job-attributes-supported Spool1 To display the document attributes supported by the spooler Spool1, enter: pdls -c server -r document-attributes-supported Spool1 NOTE When a physical printer registers with the spooler, HPDPS updates th
Managing Spoolers, Queues, and Logical Printers Querying for Spooler Information You can request information about all objects within a server of a given class by entering the ServerName followed only by a colon (:). This lets HPDPS know that you want to obtain data about all objects within the specified class contained within that server. Thus, in the example shown above, Spool2: allows a query to find out about all printers within spooler Spool2.
Managing Spoolers, Queues, and Logical Printers Querying for Queue Information Querying for Queue Information This section describes how to query the values of attributes that reflect the state of the queue and the associations between the queue and other HPDPS objects.
Managing Spoolers, Queues, and Logical Printers Querying for Queue Information Jobs in the queue will not be scheduled to the physical printer or printers associated with the queue. paused You pause a queue with the pdpause command and change the state back to ready with the pdresume command. A queue will receive jobs from its associated logical printer or printers if it is in a ready state or it is paused. Jobs in a paused queue will not be scheduled.
Managing Spoolers, Queues, and Logical Printers Querying for Queue Information HPDPS changes the value of the backlogged attribute to false when the value of queue-backlog becomes less than the value of the queue attribute backlog-lower-bound. See “Configuring the Queue Backlog Attributes” in Chapter 6 for more information.
Managing Spoolers, Queues, and Logical Printers Querying for Queue Information backlogged queues, see “Configuring the Queue Backlog Attributes” in Chapter 6.
Managing Spoolers, Queues, and Logical Printers Querying for Logical Printer Information Querying for Logical Printer Information This section describes how to query the values of attributes that reflect the status of the logical printer and whether there are associated physical printers that are ready and enabled to receive jobs from the logical printer.
Managing Spoolers, Queues, and Logical Printers Querying for Logical Printer Information Querying for the Verbose Set of Logical Printer Attributes To query the verbose set of attributes for the logical printer LogPrt2, enter: pdls -c printer -r verbose LogPrt2 HPDPS displays information similar to the following: Printer Realization Server Locations ------- ----------- ------ --------LogPrt2 logical Spool2 B7-12/2 PRM-3 NOTE Printers Associated Enabled Queue ---------- ------- -----PhyPrt2 true Queue2 P
Managing Spoolers, Queues, and Logical Printers Querying for Logical Printer Information Printer ------LogPrt2 Realization ----------logical Enabled ------true Queue -----Queue2 Printers Associated ---------PhyPrt2 PhyPrt3 Printers Ready ------PhyPrt3 This information indicates that physical printer PhyPrt2 is not ready.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers Managing Jobs in Queues and Spoolers You might need to perform job-management tasks for the following circumstances: • One or more of the physical printers associated with the queue is unable to receive jobs from the queue. A physical printer might not currently be registered with the spooler containing the queue. • The queue is paused and unable to send jobs to a physical printer.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers • Resubmit all of the jobs to a specific logical printer. See “Resubmitting Jobs to Different Logical Printers” shortly. Querying for Jobs in the Queue Use the pdq command to query jobs in a specific queue. You can query jobs in a queue by querying any logical printer that sends jobs to that queue.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers Querying for Timed-Out and Retained Jobs in the Spooler Use the -U, -r, and -f flags with the pdls command to query timed-out or retained jobs in a specific spooler.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers printers associated with the queue, but the queue will still receive jobs from its associated logical printer or printers if they are enabled. While you seldom need to pause a queue, you might want to pause a queue to modify a job or jobs in the queue before they are scheduled to physical printers. For example, you can resubmit the job to another queue or give it a retention period.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers To resume queues Queue1 and Queue2, enter: pdresume -c queue Queue1 Queue2 The queue states change to ready. Deleting Jobs from Queues and from the Spooler You can delete any job unless its state is unknown or terminating using the procedures described below.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers NOTE If the job has a retention period, as specified by the job-retention-period job attribute, you must set the value of the attribute to zero (0) with the -r flag before you can delete the job from both the queue and the spooler. If you do not, HPDPS deletes the job from the queue but the job remains in the spooler until the retention period expires. For example, enter: pdrm -r 0 Spool3:4628700042 4.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers You must set the value of the job-retention-period job attribute to zero (0) with the -r flag in order to delete the job. Deleting Jobs with the pdclean Command You also have the option of deleting all of the jobs in a queue or all of the jobs in a spooler with the pdclean command. Use the -c flag to specify whether you are deleting jobs from the queue or from the spooler.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers against the physical printer or printers that are associated with the logical printer. If the job fails validation, the job remains in either the queue or the spooler that contained the job when you issued the pdresubmit command. You can resubmit a single job, all of the jobs in a queue regardless of the logical printer that sent the job, or all of the jobs in a queue that were sent to the queue by the same logical printer.
Managing Spoolers, Queues, and Logical Printers Managing Jobs in Queues and Spoolers HPDPS sends the message when it sends the job to the queue. The message could alert the operator to something special about the job, such as that it requires special media. See “Specifying Who Receives Messages From Users” in Chapter 6 for instructions on setting up the notify-operator queue attribute.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks Performing Other Spooler-Related Tasks This section describes the following routine tasks: • managing and responding to queue backlogs • enabling and disabling logical printers • modifying logical printer attributes • modifying the initial value object attributes • modifying the printer-register-threshold attribute About Managing Queue Backlog Queue backlog is the condition where many jobs or extremely large jobs are wa
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks their jobs, try setting the upper boundary at 20 minutes. If they are willing to wait 30 minutes, you could set the upper boundary at 45 minutes. About the Queue Lower Backlog Boundary You set the lower backlog boundary in relation to the upper boundary. The lower boundary affects the number of notification messages you receive for backlogged queues.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks then rise above it before the calculation occurs. In either case, you will not receive a notification message. • If the interval is smaller A smaller interval generally results in larger increases and decreases in the value of the queue-backlog attribute. The smaller the interval, the less likely that jobs are added to or subtracted from the queue with equal frequency.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks pdls -c queue -s column -r queue-name,queue-state,\ backlogged,queue-backlog,backlog-upper-bound,\ backlog-lower-bound,backlog-update-interval Queue3 HPDPS displays information similar to the following: Queue State Backlogged ----- ----- ---------Queue3 ready true Queue Backlog ------0:30 Backlog Upper Bound ----------0:10 Backlog Lower Bound ----------0:05 Backlog Interval -------0:05 In this example, the backlog i
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks In this example, only one job has been assigned to a physical printer. Several jobs are pending, meaning that they have not been scheduled, and several jobs are held. You will use this type of information about the jobs to determine the cause of the backlog and to perform the appropriate tasks to address the backlogged condition.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks HPDPS processes the jobs in the queue. A queue backlog is minor if the backlog value is not much greater than the upper backlog boundary. Perhaps one or two large jobs were submitted or jobs were submitted that requested printing after a certain time later in the day. After HPDPS processes these jobs, the degree of the queue backlog will decrease automatically. • Check for jobs that are held.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks job-size-range-supported logical printer attribute to control the size of jobs accepted. You could then set up a separate logical printer, queue, and physical printer configuration for large jobs. See “Using Logical Printers to Restrict the Use of Printer Capabilities” in Chapter 6.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks You receive an error message that identifies the attribute and the non-supported attribute value or values. Disabling a Logical Printer If you want to modify the values of the logical printer attributes, you will need to disable the logical printer using the pddisable command.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks pdenable -m "Logical printer LogPrt3 will now accept jobs." \ LogPrt3 To enable all logical printers associated with Queue2, enter: pdenable -c queue -m "Logical printer will now accept jobs." \ Queue2 The value of the logical printer attribute enabled changes to true and HPDPS modifies the message attribute for all of the logical printers associated with the queue.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks pdset -x "content-orientations-supported+=landscape" \ LogPrt2 • To subtract a value from a multi-valued attribute, use -x and an attribute value pair with -=.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks 1. Disable the logical printer associated with the initial-value-job. You must disable the logical printer before you can modify the attributes of any associated initial value object. To disable LogPrt6, enter: pddisable LogPrt6 2. Modify the attributes of the initial value object with the pdset command.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks notification message when a job times out if you specify the job-timed-out event in the notification profile for the spooler. NOTE Timed-out jobs require intervention from either you or the user because the spooler is not able to determine what has happened to the job. Depending on whether the job printed, either use the pdrm command to remove the job from the spooler or resubmit the job with the pdresubmit command.
Managing Spoolers, Queues, and Logical Printers Performing Other Spooler-Related Tasks • The servers become aware that they have lost communications in one of two ways: — when the supervisor does not receive a response to its periodic signaling — when the spooler does not receive a response to its requests • Shutting down a server has the following effects on communications: — When you shut down the supervisor, the supervisor notifies all spoolers containing queues that send jobs to the physical printers of
Managing Spoolers, Queues, and Logical Printers Deleting Objects Contained in Spoolers Deleting Objects Contained in Spoolers This section describes how to delete the logical printers, queues, and initial value objects contained in a spooler. Deleting a Logical Printer Disable the logical printer before you delete it. Disabling the logical printer prevents it from accepting new jobs; modifications to jobs that the logical printer has sent to the queue can still be made as necessary.
Managing Spoolers, Queues, and Logical Printers Deleting Objects Contained in Spoolers You must allow the jobs to complete processing, remove the jobs, or resubmit the jobs before you can delete the queue. See “Deleting Jobs from Queues and from the Spooler” and “Resubmitting Jobs to Different Logical Printers” earlier for the commands to use. Also see below. 2. All logical printers associated with the queue must be disabled. See below.
Managing Spoolers, Queues, and Logical Printers Deleting Objects Contained in Spoolers held because it requires resources that are not available. Or the user might have submitted the job with job-hold=true and sent a message that the job has special requirements, such as blue paper. After performing the required actions, use the pdmod command to release the hold on the job. Perform the following steps to clear jobs from the queue and then delete the queue. 1.
Managing Spoolers, Queues, and Logical Printers Deleting Objects Contained in Spoolers For example, to release the job with the global job identifier number of Spool4:4628700042, enter: pdmod -x "job-hold=false" Spool4:4628700042 c. If the reason is job-print-after-specified, use the pdmod command to specify a time earlier than the current time. For example, if the current time is 10:30 in the morning, enter: pdmod -x "job-print-after=9:00:00" Spool4:4628700042 d.
Managing Spoolers, Queues, and Logical Printers Deleting Objects Contained in Spoolers For example, to query for enabled logical printers associated with initial-value-job IVJ1 contained in spooler Spool1, enter: pdls -c initial-value-job -r logical-printers-ready \ Spool1:IVJ1 HPDPS displays information similar to the following: IVJ1: logical-printers-ready = LogPrt5 2. Disable the logical printer associated with the initial value object. To disable logical printer LogPrt5, enter: pddisable LogPrt5 3.
Managing Spoolers, Queues, and Logical Printers Shutting Down and Restarting the Spooler Shutting Down and Restarting the Spooler This section describes how to shut down the spooler. You have the following options: • shutting down the spooler immediately • shutting down the spooler after all of the jobs in the queues contained in the spooler have been scheduled and printed Shutting Down the Spooler Immediately Use the pdshutdown command to immediately shut down a spooler process.
Managing Spoolers, Queues, and Logical Printers Shutting Down and Restarting the Spooler Also, the now option for the -w flag works the same as after-current. The following command also has the same results: pdshutdown -w now Spool1 The system shutdown process will do the equivalent of a pdshutdown -w now for any HPDPS server or client daemon on the system. No special set-up or processing is necessary for HPDPS servers to shut down properly during system shutdown.
Managing Spoolers, Queues, and Logical Printers Shutting Down and Restarting the Spooler Restarting the Spooler after It Has Been Shut Down Use the pdstartspl command to restart a spooler that has been shut down. The HPDPS print database stores permanent information about the spooler and the objects it contains in files located in the directory /var/opt/pd. You can log on to the system directly or through the HP-UX rlogin command.
Managing Spoolers, Queues, and Logical Printers Deleting the Spooler Deleting the Spooler Use -c server with the pddelete command to permanently delete the spooler. The spooler and any of its queues cannot contain jobs; you must allow the jobs to print or explicitly delete jobs from the spooler and its queues using the pdrm, pddelete, or pdclean commands before you can delete the spooler.
Managing Supervisors and Physical Printers 10 Managing Supervisors and Physical Printers This chapter describes tasks for managing supervisors and physical printers.
Managing Supervisors and Physical Printers Monitoring Supervisor and Physical Printer Configurations Monitoring Supervisor and Physical Printer Configurations The tasks in this section involve tracking changes made to supervisors and physical printers by: • defining how and when to use the message attribute • creating archive files for supervisors and supervisor objects Setting the message Attribute for Supervisors and Supervisor Objects Use the -m flag with any command that modifies a supervisor or physi
Managing Supervisors and Physical Printers Monitoring Supervisor and Physical Printer Configurations NOTE If you modify an object using the -m flag, then modify the object again omitting the -m flag, the message attribute will still contain the message text. This can cause users querying for the message text to receive incorrect information.
Managing Supervisors and Physical Printers Setting Policy for Job-Size Physical Printer Attributes Setting Policy for Job-Size Physical Printer Attributes You can set a policy on how you plan to use the following physical printer attributes: • maximum-copies-supported • job-size-range-supported • job-size-range-ready You can use these attributes to control the number of copies users can request and the sizes of jobs they can submit.
Managing Supervisors and Physical Printers Setting Policy for Job-Size Physical Printer Attributes pdpr -x "copy-count=2 results-profile=:::2:" \ File1.text File2.txt the user is requesting four copies of each document in the job. If the value of the maximum-copies-supported attribute is four or greater, HPDPS accepts the job. If you decide to use the maximum-copies-supported attribute to restrict how many document copies can be requested, you can do so based on the printer device.
Managing Supervisors and Physical Printers Setting Policy for Job-Size Physical Printer Attributes To restrict the size of jobs that can be submitted to the physical printer PhyPrt2, enter: pdset -x "job-size-range-supported=0:10000 \ job-size-range-ready=0:10000" PhyPrt2 Most of the time you will set the values for the two attributes to the same value range, as in the example.
Managing Supervisors and Physical Printers Supporting Special Media Supporting Special Media You need to decide which types of media that users in your organization need and how you plan to support these needs. The values of the media-ready physical printer attribute specify which media are currently loaded in the printer device, or the types of media that are available through an input source such as a manual envelope feeder.
Managing Supervisors and Physical Printers Supporting Special Media If there is no such operator available, you need to develop procedures for your organization to support users requiring special media. For example, configure separate logical printers, queues, and physical printers for non-standard media and ensure that the associated printer devices always have the correct media loaded.
Managing Supervisors and Physical Printers Querying for Supervisor Information Querying for Supervisor Information This section describes how to query for the values of attributes that reflect the state of and information about HPDPS supervisors and the associations between the supervisor and other HPDPS objects. You can query for supervisor information in response to notification messages that indicate a problem with either the supervisor or a physical printer.
Managing Supervisors and Physical Printers Querying for Supervisor Information Supervisor States The possible states of the supervisor are: State Description initializing The supervisor process is initializing. ready The supervisor has finished initializing and its physical printers can accept jobs if they are ready. terminating The supervisor is shutting down. The physical printers contained in the supervisor do not accept new jobs, and existing jobs might or might not finish printing.
Managing Supervisors and Physical Printers Querying for Supervisor Information provides you with the name of the queue from which the physical printers receive jobs.
Managing Supervisors and Physical Printers Querying for Physical Printer Information Querying for Physical Printer Information This section describes how to query for the values of attributes that reflect the status of physical printers. Querying for the State of a Physical Printer Use the pdls command with the -c printer flag to query for the state of a specific physical printer. The results of this query also indicate whether the physical printer is enabled.
Managing Supervisors and Physical Printers Querying for Physical Printer Information needs-key-operator This state occurs when there is a serious problem with the printer device. Either the physical printer cannot connect to the printer device or there is some other problem. HPDPS automatically disables the physical printer when the physical printer enters this state. paused The physical printer has been paused with the pdpause command. printing The physical printer is processing a job.
Managing Supervisors and Physical Printers Querying for Physical Printer Information example, the supervisor and spooler have lost communications but the supervisor does not identify this condition until the next time it signals the spooler. The state of the physical printer is idle and the value of the registered-with-spooler attribute is true, indicating that it is registered.
Managing Supervisors and Physical Printers Responding to Physical Printer State Problems Responding to Physical Printer State Problems The following describes the normal sequence of printer states for an enabled and ready printer as it waits for, receives, and completes jobs: 1. The physical printer state is idle and the physical printer is ready to accept a job. 2.
Managing Supervisors and Physical Printers Responding to Physical Printer State Problems Printer needs-key-operator Problem A physical printer enters the needs-key-operator state when it locks the printer device but cannot print because it encounters an error. In this case HPDPS automatically disables the physical printer and re-queues the job to the spooler. After you fix the printer problem, you must enable the physical printer with the pdenable command.
Managing Supervisors and Physical Printers Responding to Physical Printer State Problems state changes to printing. When the job completes, the physical printer state changes to idle. HPDPS notifies you when the physical printer enters the timed-out state if the notification profile for the printer specifies you are to receive notification messages for the printer-timed-out event.
Managing Supervisors and Physical Printers Message-Related Tasks for Physical Printer Management Message-Related Tasks for Physical Printer Management This section describes physical printer tasks related to managing jobs scheduled to a physical printer for processing.
Managing Supervisors and Physical Printers Message-Related Tasks for Physical Printer Management To modify the notify-operator attribute for the physical printer PhyPrt2, enter: pdset -c printer -x "notify-operator=message:White \ electronic-mail:Jones@Chevy.xyz.com" PhyPrt2 About Controlling Job Start and End Messages How you set the start-message-supported and end-message-supported physical printer attributes determines whether users can send messages.
Managing Supervisors and Physical Printers Message-Related Tasks for Physical Printer Management sends the end message when the job finishes printing. The message can give instructions for handling the printed job. The user might specify a location to where the job should be delivered, such as a specific office or building.
Managing Supervisors and Physical Printers Job-Related Tasks for Physical Printer Management Job-Related Tasks for Physical Printer Management This section describes job-related procedures for managing physical printers. If you need to disable or pause a physical printer and the physical printer has a job or jobs scheduled to it, you have to decide what to do with the jobs. This section also contains the procedures for disabling, pausing, and and resuming physical printers.
Managing Supervisors and Physical Printers Job-Related Tasks for Physical Printer Management You can also cancel a processing job and retain it. An example of when you might want to do this is when a large job is printing on a slow printer and many smaller jobs are waiting to print. You can cancel and retain the job, then either send it to a faster printer or print it at a time when the printing workload is minimal. Use the following examples to cancel processing jobs.
Managing Supervisors and Physical Printers Job-Related Tasks for Physical Printer Management multiple jobs, additional jobs could be sent to the printer. You could also disable the printer to prevent this, but most of the time this is not necessary. • Disable the physical printer if it must be unavailable for a longer period of time. For example, if the printer device needs to be out of service for one or two hours for routine maintenance, you should disable it.
Managing Supervisors and Physical Printers Job-Related Tasks for Physical Printer Management pddisable -m "PhyPrt3 is unavailable until 15:30 because of \ required maintenance" PhyPrt3 You can now complete the tasks that required you to disable the physical printer. For example, if you are changing the type of media loaded in the printer, you can load the new media and update the physical printer attribute that reflects which media is loaded.
Managing Supervisors and Physical Printers Performing Routine Physical Printer Tasks Performing Routine Physical Printer Tasks This section describes the tasks of changing the media loaded in a printer device and performing preventive maintenance for a printer. Changing the Media in Printers In the following example, the printer device currently has yellow paper loaded and you are changing that to white paper. 1.
Managing Supervisors and Physical Printers Performing Routine Physical Printer Tasks If you are going to disable the physical printer for a long time and if jobs are in the queue, you can resubmit them to another queue. Refer to “Resubmitting Jobs to Different Logical Printers” in Chapter 9 for instructions on how to resubmit jobs. Then disable the physical printer and perform maintenance.
Managing Supervisors and Physical Printers Modifying Supervisor and Physical Printer Tuning Attributes Modifying Supervisor and Physical Printer Tuning Attributes Supervisors and physical printers have some attributes that affect performance. These attributes all have default values which ensure good performance under most circumstances.
Managing Supervisors and Physical Printers Modifying Supervisor and Physical Printer Tuning Attributes To increase the job-submission time for the supervisor Super1 to one hour, enter: pdset -c server -x "job-submission-timer=1:00" Super1 NOTE The transfer method for jobs sent to the supervisor influences your usage of the job-submission-timer attribute. The transfer-method document attribute specifies the method.
Managing Supervisors and Physical Printers Modifying Supervisor and Physical Printer Tuning Attributes HPDPS notifies you when a physical printer is no longer registered if the notification profile for either the physical printer or supervisor specifies you are to receive notification messages for the printer-unregistered event.
Managing Supervisors and Physical Printers Deleting a Physical Printer Deleting a Physical Printer If a printer is enabled, issuing the pddelete command automatically disables and deletes it. However, you may want to disable the physical printer with the pddisable command before you delete it. Disabling the physical printer prevents HPDPS from scheduling any new jobs to the physical printer.
Managing Supervisors and Physical Printers Shutting Down and Restarting the Supervisor Shutting Down and Restarting the Supervisor Under normal conditions there is no reason to shut down the supervisor. The only reasons to shut down a supervisor would be for a condition requiring re-initialization of the system on which the supervisor is installed or a condition requiring you to issue the HP-UX shutdown command.
Managing Supervisors and Physical Printers Shutting Down and Restarting the Supervisor pdshutdown -w after-all Super1 Shutting Down the Supervisor Immediately If you want to shut down the supervisor immediately, use -w now with the pdshutdown command. As a result, any currently printing jobs will be aborted. However, if possible, these jobs will be rescheduled to the any other available printer if the spooler is still active.
Managing Supervisors and Physical Printers Shutting Down and Restarting the Supervisor kill 22359 HPDPS issues a notification message when the supervisor has been successfully shut down. Restarting the Supervisor After It Has Been Shut Down Use the pdstartsuv command to restart a supervisor that has been shut down. The HPDPS print database stores permanent information about the supervisor and the objects it contains in files located in the directory /var/opt/pd.
Managing Supervisors and Physical Printers Deleting the Supervisor Deleting the Supervisor When deleting the supervisor, the physical printers contained in the supervisor cannot be processing jobs. You must allow the jobs to print or explicitly delete the jobs using the pdrm, pddelete, or pdclean commands before you can delete the supervisor. Deleting a supervisor permanently deletes all of the objects it contains, such as physical printers, from the HPDPS system.
Managing Jobs and Supporting Users 11 Managing Jobs and Supporting Users This chapter describes tasks related to managing jobs that users submit to HP Distributed Print Service.
Managing Jobs and Supporting Users Finding and Identifying Jobs Finding and Identifying Jobs A user might contact you to promote a job or to identify and fix a problem with a job.When this happens, you need to be able to determine the global job identifier for the job and locate the job. All commands that affect jobs require the job identifier. Table 11-1 lists the attributes that identify and describe a job. See the sections immediately following the table for more information.
Managing Jobs and Supporting Users Finding and Identifying Jobs Table 11-1 Job Identification Attributes Attribute Description job-owner The name of the user who is responsible for the job. This attribute defaults to the value of the user-name attribute unless the job submittor specified a different value for the job-originator attribute. HPDPS prints the value of the job-owner attribute on the start sheet for the job. The following attributes provide additional information about the job.
Managing Jobs and Supporting Users Finding and Identifying Jobs NOTE The value of the local job identifier is generated by the client program and is unique for a given UserName. If a user signs on to more than one system, the values of the job-client-id are unique for each system. In this case, it is possible for the same user name to have more than one job with the same local job identifier. However, the global job identifier for each job is unique.
Managing Jobs and Supporting Users Finding and Identifying Jobs You often already know the logical printer or printers to which the user submits jobs; if not, the user should be able to identify the logical printer to which they sent the job. You might also know the spooler that contains the logical printer. You can use the following procedures to determine the global job identifiers for jobs submitted by other users.
Managing Jobs and Supporting Users Finding and Identifying Jobs only provides information about the specified job Spool2:2934700005. • If you want to find a job or jobs sent by a user to any logical printer in a specific spooler, you can query the spooler with the pdls command.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers Managing Jobs in Queues and Spoolers This section describes how to manage jobs in the queue that are waiting to be scheduled, and how to manage jobs contained in a spooler that are either in the retained or timed-out states.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers Table 11-2 Job Control and Scheduling Attributes Attribute Description job-discard-time Specifies the calendar date and time at which the job will be discarded, whether or not it has printed. If the job is retained in the spooler using the job-retention-period attribute, the job will be discarded at the specified time even if the retention period has not expired.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers Table 11-2 Job Control and Scheduling Attributes Attribute Description printers-assigned The name of the physical printer to which the job was scheduled. This attribute has no value until HPDPS schedules and sends the job to a physical printer. Jobs in the retained and timed-out states have values for their printers-assigned attributes.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers HPDPS schedules this job ahead of other jobs in the queue that have a priority less than 75. You can also, in effect, use the job-priority attribute to promote a job to be the first job in the queue by setting the priority for the job to 100.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers Holding a Job You can hold a job to prevent it from printing for a period of time. An example might be if a job was submitted and then an error was discovered in the job. If the -l flag was used with the pdpr command when the job was submitted, you could hold the job, make the correction to the source file, and then release the job.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers After the job prints, HPDPS retains the job in the spooler for the amount of time specified. You and the user who submitted the job can make modifications to the attributes of the job while it is retained. For example, you might want to modify the results-profile attribute of the job to print copies for different people. Refer to “Setting Up the Job results-profile” shortly for an explanation of this attribute.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers Assigning a job-discard-time for a Job A user might request that you assign a discard time to a job so that, if a job has not printed by a certain time, HPDPS discards the job. For example, the job might contain confidential information that needs to be secured after printing, but the job owner is only available until 5:00 p.m. to pick up the job. Therefore, the user wants HPDPS to discard the job if it has not printed by 5:00 p.m.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers For example, to assign a job-print-after time of 12:45 p.m. on August 5th, 1997, enter: pdmod -x "job-print-after='12:45:00 \ 08/05/96'" Spool2:4857700125 If you also specify a time (and date) for the job-discard-time attribute, it should be after the time (and date) for this attribute. Otherwise, HPDPS discards the job before it prints; HPDPS does not compare these two attributes to prevent this situation.
Managing Jobs and Supporting Users Managing Jobs in Queues and Spoolers 3. HPDPS changes the value of the job-state-reasons to required-resources-not-ready Refer to “About Jobs That Cannot Be Scheduled Because of Resources” later in this chapter for more information about this job state.
Managing Jobs and Supporting Users Setting Up a Logical Printer for High-Priority Jobs Setting Up a Logical Printer for High-Priority Jobs Depending on the size of your organization and the numbers of jobs submitted, you might want to set up a logical printer specifically for high-priority jobs. You could associate this logical printer with one or more existing physical printers and restrict the use of the new logical printer to administrators or to a specific group of users.
Managing Jobs and Supporting Users Setting Up a Logical Printer for High-Priority Jobs priority is 100, HPDPS positions the job as the first job in the queue after it validates the job. This same procedure can be used to set up logical printers for jobs with other priority levels.
Managing Jobs and Supporting Users Setting Up the Job results-profile Setting Up the Job results-profile You can specify the values of the results-profile attribute when creating an initial-value-job object with the pdcreate command. You can also set the values with the pdset command. The results-profile attribute allows you to specify the following job components, referred to as a result-set: delivery-method This single-valued component specifies how the person is to receive this result-set of the job.
Managing Jobs and Supporting Users Setting Up the Job results-profile Specifying the results-profile Attribute with a Job Requesting multiple job copies with the results-profile attribute is useful for jobs consisting of multiple documents when the order in which the documents print is important.
Managing Jobs and Supporting Users Setting Up the Job results-profile The result-set order in which the job prints is: • Banner Page • First Job Copy — document1 document1 document1 document1 — document2 document2 document2 document2 — document3 document3 document3 document3 • Second Job Copy — document1 document1 document1 document1 — document2 document2 document2 document2 — document3 document3 document3 document3 Changing the Default Order of Documents To change the default order of the documents, you c
Managing Jobs and Supporting Users Setting Up the Job results-profile You enter the same command, but set the interface-program-method job attribute to lp: pdpr -x "copy-count=4 interface-program-method=lp \ results-profile=:::2" document1 document2 document3 A banner page (auxilliary start sheet) is included for each job copy. The default value for the interface-program-method is hpdps. For more information on the interface-program-method attribute, see the pd_att_job(5) manpage.
Managing Jobs and Supporting Users About Pausing and Cancelling Jobs About Pausing and Cancelling Jobs Cancelling jobs sent to a physical printer depends on the associated printer device and how much buffer memory the printer device has available. You can only pause and cancel jobs that have not been completely transferred to the printer device. You can potentially pause or cancel a job sent to a physical printer when the state of the job is processing.
Managing Jobs and Supporting Users Determining Job States and Job Status Determining Job States and Job Status This section describes the jobs states and other job attributes that reflect the status of jobs. It describes how to query jobs to determine their state and status. You can obtain job status before and while a job prints. You can obtain job status after a job finishes processing if the job is retained. Table 11-3 describes job attributes that reflect the state and status of jobs.
Managing Jobs and Supporting Users Determining Job States and Job Status Table 11-3 Job Status Attributes Attribute Description modification-time If the job has been modified, this attribute reports the time the job was modified. This attribute has no value if the job was not modified or cancelled. HPDPS might update the following attributes as it processes the job. octets-completed Reports the number of octets (bytes) in the job that have been printed.
Managing Jobs and Supporting Users Determining Job States and Job Status 5 Spool2:0900703 cmds.v1 pending 7 LogPrt3 This output reports the value of the current-job-state attribute. It also tells you how many jobs are ahead of this job in the queue, as indicated in the Intervening Jobs column. The Printer Requested column shows the logical printer to which the job was submitted. If HPDPS has scheduled the job, the Printers Assigned column identifies the physical printer processing the job.
Managing Jobs and Supporting Users Determining Job States and Job Status Querying for Specific Job-Status Attributes Sometimes the previous job state, as reported by the previous-job-state attribute, can also be helpful as shown in Table 11-4. You will notice that there are no job-state-reasons for the first two current-job-state attributes of the first job.
Managing Jobs and Supporting Users Determining Job States and Job Status pdq -U -r brief,previous-job-state,job-state-reasons -s column \ Spool3:3459400023 HPDPS displays information similar to the following: Job ID --- -----------------172 Spool3:3459400023 Previous State ------------preprocessing Name --------file1.
Managing Jobs and Supporting Users Determining Job States and Job Status processing The job has been sent to a physical printer and is being processed and printed. Depending on the printer device, this can indicate that at least one document in the job has been sent to the printer device. retained The job has been retained in the spooler after it has finished printing or after it has been cancelled. The value of the job-retention-period attribute for the job is greater than zero.
Managing Jobs and Supporting Users Determining Job States and Job Status NOTE Jobs are in the job states cancelled, preprocessing, and terminating for only a very short time. You will almost never see them as values for the current-job-state attribute. You might see them as values for the previous-job-state attribute. Refer to “About Server Communications” in Chapter 9 for a description of how the spooler and supervisor communicate.
Managing Jobs and Supporting Users Determining Job States and Job Status Table 11-5 Descriptions of job-state-reasons job-state-reasons Description required-resources-not-ready The job is in a queue but cannot be scheduled because one or more of the resources required by the job (such as media, fonts, and so on) are not ready on any of the physical printers that can accept the job.
Managing Jobs and Supporting Users Determining Job States and Job Status For more information on job scheduling refer to “Specifying the Queue Scheduling Method” in Chapter 6. The following conditions can prevent HPDPS from scheduling a validated job: • A given physical printer is no longer registered with the spooler. • The value or values for one or more physical printer attributes have been modified.
Managing Jobs and Supporting Users Determining Job States and Job Status This attribute is updated when the job is queried or after each document copy completes. job-copies-completed Reports the number of copies of the particular job that have been printed. This attribute is updated after each job copy completes. processing-time Reports the amount of time that the job has been printing on the printer. This attribute is updated when a user queries the job with the pdls command.
Managing Jobs and Supporting Users Determining Job States and Job Status Copies Completed --------1 Results Profile --------------------pickup::rob@cowboy:3: The fourth component of the results-profile attribute specifies the number of copies. In this example, HPDPS has completed one copy of the three copies requested. Querying for the Processing Time Required by a Job This can be useful if you print a large job on a regular basis, such as a monthly report.
Managing Jobs and Supporting Users Determining Job States and Job Status 364 Chapter 11
Using HPDPS Error Logs 12 Using HPDPS Error Logs This chapter contains general information on HPDPS error logs. This includes topics such as: • finding and viewing the right error log • using the messages in an error log • changing the attribute values of server error logs HPDPS creates a subdirectory in the directory /var/opt/pd for each HPDPS client and each server and places the error logs for the client and servers in that directory.
Using HPDPS Error Logs Finding and Viewing a Client Error Log Finding and Viewing a Client Error Log The error log for an HPDPS client is the file: /var/opt/pd/pdclientd/error.
Using HPDPS Error Logs Changing Server Error Log Attribute Values Changing Server Error Log Attribute Values Server error log attributes that you can modify are: log-severity The value of this attribute determines which of the server messages the server error log records. See “Available Values for the log-severity Attribute” shortly for a list of available log-severity attribute values. log-size The value of this attribute determines the maximum size to which a log can grow.
Using HPDPS Error Logs Changing Server Error Log Attribute Values NOTE While the log is disabled, it will not log any messages. 2. Change the log severity setting: pdset -c log -x "log-severity=debug" ServerName:default_error 3. Enable the log: pdenable -c log ServerName:default_error The server error log attribute log-severity now has a value of debug. Using this same process you can temporarily change the error log attribute values of other servers.
Using HPDPS Error Logs Changing Server Error Log Attribute Values • turn wrapping off so that when the log file grows to two megabytes, logging stops. • change the log severity from audit to debug. Use a text editor to edit the /var/opt/pd/spl_error.
Using HPDPS Error Logs Changing Server Error Log Attribute Values audit This is the default log severity setting. Error, warning, and audit messages are logged. The letter A precedes each audit message. debug This setting logs error, warning, audit, and debug messages. Servers generate debug messages when they begin processing each command and when they communicate with other servers. Debug messages are useful for helping to track what command a server was processing when an error occurred.
Using HPDPS Error Logs How HPDPS Backs Up Server Error Logs How HPDPS Backs Up Server Error Logs What HPDPS backs up is different for a server that is shut down than for one that is deleted. Error Log Backup After a Server is Shutdown Backups of server error logs occur as follows: 1. The first time the server is shut down and then restarted, HPDPS renames the present error log for the server from ServerName/error.log to ServerName/error.log.BAK, where ServerName is the name of the server. 2.
Using HPDPS Error Logs How HPDPS Backs Up Server Error Logs Finding and Viewing Server (Spooler and Supervisor) Error Logs Each server error log contains a record of the messages that are generated by the server and the objects it contains. If you are experiencing a problem or unexpected behavior, often the best course of action is to look in the error log of the server.
Using HPDPS Error Logs How HPDPS Backs Up Server Error Logs 5. Find the file you believe the log entry you are looking for is in. Use an editor to look at the file by entering a command similar to the following: vi error.log.BAK.19970804174858 6. Browse the file for messages of interest. If you want to find more about the message, see “Using the Messages in Error Logs” shortly. Removing Error Log Backup Files and Directories HPDPS does not delete these backups automatically.
Using HPDPS Error Logs How HPDPS Backs Up Server Error Logs E 07/31/97 10:47:33 [205fdf28 jjones−>Spool1,LogPrt3] 5010-550 Cannot print this job. No physical printers are associated wi th logical printer LogPrt3 A 07/31/97 10:47:33 [205fdf28 jjones−>Spool1,LogPrt3] 5010-528 Cannot create job 2 (Spool1:0233600000). The second message in this sample is preceded by E, for error, rather than A for audit.
Troubleshooting 13 Troubleshooting If you or a user receives an error message, try to resolve the problem by following the suggested course of action in the message help text, as explained in “Getting Full Descriptions for HPDPS Error and Notification Messages” below. The remainder of the chapter includes sections covering specific diagnostic procedures for problems with physical printers, jobs, client daemons, and servers.
Troubleshooting Getting Full Descriptions for HPDPS Error and Notification Messages Getting Full Descriptions for HPDPS Error and Notification Messages When you or a user receive an HPDPS error message or notification message, use the pdmsg command to display more information. The information about the message includes an explanation, a system action, and a response. The response suggests things you can do to correct the problem.
Troubleshooting Getting Full Descriptions for HPDPS Error and Notification Messages If there are no error or notification messages, or they do not sufficiently help you diagnose the problem, browse the topics that follow to find the topic that corresponds to the particular problem.
Troubleshooting Problems with Physical Printers Problems with Physical Printers If you or a user receive any error or notification messages, before going any further with this section, use the suggested action described in the previous section “Getting Full Descriptions for HPDPS Error and Notification Messages”. If you have done this and you need more information, or if there are no error or notification messages associated with the problem, use this section.
Troubleshooting Problems with Physical Printers 1. All of the physical printers assigned to the queue are shown to be ready. For example: Physical Printers Assigned ----------------PhysPrt1 PhysPrt2 PhysPrt3 PhysPrt4 Physical Printers Ready -------------PhysPrt1 PhysPrt2 PhysPrt3 PhysPrt4 If you see a result like this, all of your physical printers are working. 2. Not all of the assigned physical printers are shown to be ready.
Troubleshooting Problems with Physical Printers PhysPrt3: printer-state PhysPrt3: enabled PhysPrt3: message = paused = true = "Paused for maintenance.-jbird" If there is no useful information in the message value, use Table 13-2 to determine what your next action should be, based on the combination of values for printer-state and enabled.
Troubleshooting Problems with Physical Printers Table 13-1 Physical Printer Attribute Values: printer-state and enabled If printer-state is If enabled is Do this to resume and enable the printer: printing true 1. Look at the printer device fed by this physical printer to see if the device is printing. 2. If the printer device is not printing, it might be processing large or complex data. Wait to see if it successfully produces output. 3.
Troubleshooting Problems with Physical Printers Physical Printer State is “needs-key-operator” If the pdls command returns a printer state of needs-key-operator, HPDPS might not be able to communicate with the printer device. Check that the printer is configured correctly, is turned on and is connected. If the printer device is TCP/IP-attached, use your local troubleshooting procedures to see if you are having network problems.
Troubleshooting Problems with Physical Printers queue already had a job in the device when your physical printer tried to connect. This prevented your physical printer from connecting. In many cases, your physical printer will connect to the device when the other printer is done and will recover from its timed-out state. Nevertheless, it is not recommended to have an HPDPS-managed printer device fed by a second physical printer or print queue.
Troubleshooting Problems with Physical Printers This display reveals that in addition to PhysPrt1, which is the timed-out physical printer, there is a second HPDPS physical printer, PPBob, sending output to device dev1. In this case, you must make a policy decision about which physical printer to delete. Before deleting a physical printer, use the pddisable command to prevent any more jobs from being scheduled to it. Use the pddelete command to delete the physical printer.
Troubleshooting Problems with Physical Printers Cannot Print to an Enabled Physical Printer If a physical printer shows an enabled value of true, and yet you still cannot print to that physical printer, the physical printer is probably not registered with a queue. This might happen if the spooler containing the queue or the supervisor containing the physical printer was recently started or if there are DCE or network problems.
Troubleshooting Problems with Jobs Problems with Jobs If you or a user receive any error or notification messages, before going any further with this section, use the actions suggested in “Getting Full Descriptions for HPDPS Error and Notification Messages” earlier. If you have done this and you need more information, or if there are no error or notification messages associated with the problem, use this section.
Troubleshooting Problems with Jobs message from the pdpr command saying that some object necessary for printing the job, such as a file or a printer, is not found, is not available, or cannot be opened. In this case, see “HPDPS Cannot Find or Open a File or Object Your Job Needs” shortly.
Troubleshooting Problems with Jobs • HPDPS cannot find or cannot open the user's specified attributes file or document file. For example, the user specified the file File1 and received the error message: 5010-140 Cannot open file File1. In this case, have the user check the command he or she entered for the following items and then try the command again.
Troubleshooting Problems with Jobs 2. Use the pdls command to see if the supervisors containing the physical printers associated with that queue are running. For example, if supervisor Super1 contains the physical printers associated with the queue, enter: pdls -c server Super1 3. If the supervisor is not running, use the pdstartsuv command to start the supervisor. 4.
Troubleshooting Problems with Jobs Verify that the attribute the user specified is valid for jobs. Refer to the manpage pd_att_job(5) to confirm that the user is specifying a job attribute, rather than the equivalent printer attribute.
Troubleshooting Problems with Jobs section if the user submitted a job to logical printer LogPrt2 and received the following error message. pdpr: 5010-612 You must be authorized to perform this operation on object Spooler1:LogPrt2. This error message indicates that the logical printer to which the user submitted the job is restricted by DCE security. • If the user cannot, or does not, log into DCE, he or she must select a logical printer that is not restricted by DCE.
Troubleshooting Problems with Jobs 2. Use the list command. For example, enter: list This displays the permissions granted by LogPrtRestrict. For example: # SEC_ACL for /.:/pdsec/Spool1/printer/LogPrtRestrict # Default cell = /...
Troubleshooting Problems with Jobs There are three environment variables that can determine the locale, in order of precedence: LC_MESSAGES, LC_ALL, and LANG. You can specify the locale for the entire system in the file /etc/environment. A user can override this locale by specifying the LANG environment variable in the .profile file or by exporting LANG for a current session. If messages are in the wrong language, check which locale has been specified.
Troubleshooting Problems with Jobs Your next action depends on all the information you have about the job, including the results the pdls command displays. Table 13-4 tells you where in the current section to get help based on information about the job.
Troubleshooting Problems with Jobs For example, if the name of the alternative logical printer is LogPrt3 and the global job identifier is Spooler1:1000000015, enter: pdresubmit LogPrt3 Spooler1:1000000015 The Current State Is "Pending" but the Job Is Not Moving in the Queue Use this section if the job's current-job-state attribute value is pending, but the job is taking longer than you think it should to move to the head of the queue and print.
Troubleshooting Problems with Jobs instructions. If you cannot obtain any information about the physical printer, the supervisor is shut down. If this is the case, use the pdstartsuv command to start the supervisor again. The Job's Current State is Neither Pending Nor Processing In Table 13-5, find the listed combination of job attribute values that matches the pdls command results, then take the suggested action.
Troubleshooting Problems with Jobs Table 13-3 Job Attribute Values current-jobstate job-state-reasons Your next action: held required-reso urces-not-sup ported See “The Printer Resources that the Job Requires Are Not Supported” shortly. held job-print-aft er Did the user set the job-print-after attribute with the pdpr command? The job-print-after attribute could have been set in an initial value object or in an attributes file.
Troubleshooting Problems with Jobs Table 13-3 current-jobstate Job Attribute Values job-state-reasons Your next action: unknown The unknown value indicates that the spooler has lost contact with the physical printer that was printing the job. Wait a few minutes and enter the pdls command again to see if the spooler regains contact with the physical printer. If the problem is not corrected, the state will change to timed-out.
Troubleshooting Problems with Jobs Your next action depends on the combination of values the pdls command returns. Find the listed combination that matches your results. Then see the section referred to for instructions.
Troubleshooting Problems with Jobs In this example, the job size is 48 million octets, and the document in the job uses the default-medium attribute to request the medium iso-a4-transparent. Next, find all the physical printers that are associated with the queue the job is in or with the logical printer to which the job was submitted, and that support the necessary attribute values.
Troubleshooting Problems with Jobs This display shows two physical printers that support the job. The physical printer PhysPrt1 does not have the right job size range ready for the job, and the physical printer PhysPrt2 does not have the iso-a4-transparent media ready for the job.
Troubleshooting Problems with Jobs 2. Increase the supported job size range: pdset -x "job-size-range-ready=3000:48015000" PhysPrt1 The job-size-range-ready attribute of PhysPrt1 now has a value of 3000:48015000. You might also choose to specify only the upper limit. If you do so, the lower limit defaults to zero. 3. Enable the printer: pdenable PhysPrt1 The job is now able to be scheduled. Its current state changes to pending or processing.
Troubleshooting Problems with Jobs supported, submit the job again to the same logical printer using the pdresubmit command. For example, if the logical printer to which the user originally submitted the jobs is LogPrt2 and the global job identifier is Spooler1:1000000015, enter: pdresubmit LogPrt2 Spooler1:1000000015 This command results in job validation failure, and the error message that you receive tells you which attributes are not supported.
Troubleshooting Problems with Jobs The Job Printed with an Incorrect Document Format Use this section if the job printed using the wrong document format and the output contains random characters or control characters. For example, use this section if a PostScript job printed as ASCII characters. Check the following possibilities: • Did the user specify a document format with the print command? If so, have the user submit the job again.
Troubleshooting Problems with Jobs pdls -U -r brief,copy-count,job-hold Spooler1:1000000015 HPDPS displays information similar to the following: 1000000015: job-client-id = 15 1000000015: job-identifier = Spooler1:1000000015 1000000015: job-name = File1 1000000015: current-job-state = held 1000000015: intervening-jobs = 4 1000000015: printer-name-requested = LogPrt3 1000000015: printers-assigned = 1000000015: job-hold = true 1000000015.1: document-sequence-number = 1 1000000015.
Troubleshooting Problems with the HPDPS Client Daemon Problems with the HPDPS Client Daemon Use this section if you receive an error message about the HPDPS client daemon, such as: 5010-168 Cannot communicate with HPDPS daemon. Use your local problem-reporting procedure to report this message. If you or a user receive a message like this, use the pdstartclient command to start the HPDPS client again. To use this command, you must be logged in as the root user.
Troubleshooting Problems with Servers Problems with Servers If you suspect a problem with a server, even if you have not received an error message, you might want to look in the error logs for messages pertaining to your problem. This following section contains information for server problems that you might experience.
Troubleshooting Problems with Servers 1. Stop the DCE daemons. 2. Restart the DCE daemons. The pdls Command Does Not Return Status of Other Servers in the DCE Cell Suppose a DCE cell is configured and HPDPS servers are running in the DCE Extended Environment in the same cell. You request status of HPDPS servers running on other hosts in the same cell, but the pdls command does not return any information about the other servers. If you are running SAM, you may not see other servers in the DCE cell.
Troubleshooting Problems with lpstat Command Not Returning the Status of HPDPS Printers Problems with lpstat Command Not Returning the Status of HPDPS Printers HPDPS logical printers should be instantly visible with the LP interface. That is, lpstat should return the status of any HPDPS printers. So there is a problem if lpstat does not return status of HPDPS printers, but pdls does return the status of the same printers. An explanation is that HPDPS release 11.
Troubleshooting Problems with lpstat Command Not Returning the Status of HPDPS Printers 410 Chapter 13
NT Interoperability with HPDPS A NT Interoperability with HPDPS This appendix describes NT interoperability with HPDPS.
NT Interoperability with HPDPS NT to HPDPS Print Commands NT to HPDPS Print Commands The following are the two command line interfaces on an NT system to the HPDPS print environment: • lpr command. Use this command on NT to send print jobs to HPDPS.
NT Interoperability with HPDPS NT to HPDPS Print Commands • lpq command. Use this command on NT to get printer and job status. Syntax: lpq -S server-host -P printer-name [ -l ] Where: -S server-host is the name or IP address of the server host running HPDPS -P printer-name is the name of the HPDPS printer -l indicates verbose output For example, if you want to get printer and job status for an HPDPS logical printer LogPrt1 which resides on host host1.myco.com, use: lpq -S host1.myco.
NT Interoperability with HPDPS Setting Up an HPDPS Printer on an NT System Setting Up an HPDPS Printer on an NT System The following sub-sections show the requirements and procedures for setting up an HPDPS printer on an NT system. Software Requirements • Microsoft TCP/IP protocol software installed. • Microsoft TCP/IP printing software installed. Procedures 1. Make sure the lpdsvc server is running.
NT Interoperability with HPDPS Setting Up an HPDPS Printer on an NT System NOTE Be sure to remove the # character from the “printer” line (uncomment the line) in the /etc/inetd.conf file of the HPDPS server host and add the name of the NT system to the /var/adm/inetd.sec file. The entry in /etc/inetd.sec should be: printer allow # access OK for all hosts or printer allow hostname # access OK for this ‘hostname’ or leave the entry empty, which is the equivalent to printer allow. 9.
NT Interoperability with HPDPS Setting Up an HPDPS Printer on an NT System 416 Appendix A
Resources Needed for Configuring a Large Number of Printers B Resources Needed for Configuring a Large Number of Printers This appendix describes the HPDPS minimum configuration for support of up to 1500 printers.
Resources Needed for Configuring a Large Number of Printers HPDPS Miminum Configuration Requirements HPDPS Miminum Configuration Requirements To support up to 1500 printers, the HPDPS minimum configuration requirements are: Hardware ✓ K570 (2 CPU’s, 240 MHz) ✓ Physical memory = 1.50GB ✓ Swap space = 1.65GB ✓ Total memory = 3.15GB ✓ Disk space for /var/opt = 512MB NOTE The above configuration was the minimum required for a test scenario which sent 100 simultaneous print requests to a single printer.
Resources Needed for Configuring a Large Number of Printers HPDPS Miminum Configuration Requirements High Availability ✓ The host must be part of a DCE cell. ✓ The host must be part of a ServiceGuard cluster. HPDPS Configuration Test Scenario In a test scenario, 1500 printers (1500 logical printers, 1500 physical printers, and 1500 queues) were created with pdcreate in the Extended Environment. Each spooler contains 50 logical printers and 50 queues. Each supervisor contains 50 physical printers.
Resources Needed for Configuring a Large Number of Printers Paging Space Calculation Paging Space Calculation The following shows the calculation of the paging space needed. It is derived from Table 2-2 in Chapter 2. ✓ For pdclientd 512MB ✓ For 1st spooler 592MB ✓ For 1st supervisor 512MB ✓ For each additional spooler 20MB ✓ For each additional supervisor 20MB Example: Total paging space for the above configuration: 512 + 592 + 512 + (29 * 2) + (29 * 20) = 2776MB (2.8GB).
Index Symbols ">" returned after submitting job, 387 A aborted-by-system job state, 359 access providing security, 37 acl_edit command, 234, 391 adding attributes for physical printers, 99 customized printer-model attribute, 98 logical printers, 120 physical printers, 93 spoolers, 104 supervisors, 90 adding values notification profile, 202 adm_user, 74 administrator groups planning, 71 administrators DCE security, 229 any_other value, 235 removing permissions, 248 architecture of HPDPS, 29 archive file cre
Index C cancelled job state, 357 cancelled-by-operator job state, 359 cancelled-by-user job state, 359 cancelling job processing, 317 jobs, 328, 352 cell directory structure, 237 cell_admin, 74 changing attributes for physical printers, 99 scheduling method, 108 checkpoint-taken event identifier, 163 class-aborted event class, 183 class-error event class, 183 class-job-attention event class, 184 class-job-default event class, 185 class-job-problem event class, 185 class-job-status event class, 186 class-lo
Index creating archive file for spoolers and spooler objects, 253 archive file for supervisors and supervisor objects, 299 initial value objects, 131 logical printers, 120 notification profile, 202 notification profile attributes file, 207 physical printers, 93, 97 queues, 108 spoolers, 104 supervisors, 90 current-job-state attribute, 285, 341, 353, 355, 357, 395 D daemon problems, 406 verifying that it is running, 77 date format, 343 DCE acl_edit command, 234 container, 239 documentation, 228 giving group
Index /var/opt/pd/lib/model, 80 /var/opt/pd/pdclientd/error.log, 366 log, 237 printer, 237 queue, 237 disabling logical printers, 281 physical printers, 319 queues, 268 disk space requirements, 47 Distributed Computing Environment.
Index file-transferred event identifier, 165 format of document incorrect, 404 funnel configuration, 37 funnel configuration model, 65 G Gateway Printer.
Index job-cancelled-by-operator event identifier, 166 job-cancelled-by-user event identifier, 166 job-cannot-be-scheduled event identifier, 166 job-client-id attribute, 332, 333 job-comment attribute, 333 job-complete message, 403 job-completed event identifier, 167 job-copies in results-profile, 348 used with copy-count, 349 job-copies-completed attribute, 353, 361 job-discarded event identifier, 167 job-discard-time attribute, 337, 341, 343, 361 job-hold attribute, 266, 273, 337, 357, 404 job-hold-set jo
Index retention period, 272 schedules, 360 scheduling, 337 sending between Basic Environment and DCE Extended Environment, 61 specifying a results-profile, 349 states, 357 task management, 266 timed-out, 268 waiting to be scheduled, 266 jobs-copies attribute modifying, 344 job-size-range-ready setting policy, 300 job-size-range-ready attribute, 301 modifying, 401 job-size-range-supported setting policy, 300 job-size-range-supported attribute, 281, 301 jobs-priority attribute, 346 job-start-message attribut
Index M managing DCE security, 227 maximum-copies-allowed attrbute, 344 maximum-copies-supported setting policy, 300 maximum-copies-supported attribute, 127, 141, 300 media changing, 321 supporting, 303 media-ready attribute, 303 modifying, 344, 402 media-supported attribute, 124, 127, 303 memory requirements, 47 message attribute, 379 setting for spoolers and spooler objects, 252 setting for supervisors and supervisor objects, 298 message-related tasks physical printer, 314 messages disabling, 274 job sta
Index object-resumed event identifier, 172 objects, 29, 33 configuration planning, 60 default events, 196 naming convention, 90 notification profile examples, 209 octets querying for number completed, 362 octets-completed attribute, 353, 361 operators DCE security, 229 use in notification profile, 162 other-error event identifier, 172 other-warning event identifier, 172 output-bin in results-profile, 348 P pages-completed attribute, 353, 361 paging requirements for disk space, 49 paging space calculation,
Index performance tuning HPDPS, 88 permissions DCE, 237 DCE security, 229 default, 238 printer operator group, 232 propagation, 238 security directory, 243, 248 setting default, 239 personnel groups administrator groups, 71 notification considerations, 69 operator groups, 70 planning, 69 security consideration, 69 system operator groups, 71 user groups, 70 physical configuration number of clients to install, 58 number of spoolers to install, 58 number of supervisors to install, 59 planning, 58 physical pri
Index not supported, 402 printer-community-name values, 96 printer-community-name attribute values, 96 printer-disabled event identifier, 173 printer-enabled event identifier, 173 printer-function-unavailable event identifier, 174 printer-initial-value-document attribute, 35, 118, 131, 281 printer-initial-value-document atttribute, 123 printer-initial-value-job attribute, 35, 123, 281 printer-locations attribute, 99, 124, 128, 264 printer-locations-requested attribute, 100, 124, 128 printer-model attribute
Index backlog update interval, 276 lower backlog boundary, 276 queue backlog, 266, 275 determing the cause, 279 responding to, 277 queue-assigned attribute, 338 queue-backlog attribute, 111, 114, 260 queue-backlogged event identifier, 160, 178 queue-no-longer-backlogged event identifier, 179 queues backlog, 111, 266, 275 backlog processing, 113 backlogs, 279 creating, 108 default events, 197 default events for queue notification messages, 114 deleting, 288 deleting jobs, 270 disabling, 268 jobs not moving
Index between spooler and supervisor, 286 servers error log backup, 371 finding and viewing error logs for, 372 modifiable error log attributes, 367 notification profiles, 160 problems, 407 server-shutdown-complete event identifer, 92 server-shutdown-complete event identifier, 106, 179 server-shutdown-started event identifier, 180 server-startup-complete event identifier, 180 server-state attribute, 255, 293, 305 server-state-changed event identifier, 180 setting attributes for physical printers, 99 defaul
Index restarting, 329 shutting down, 327 specifying a description, 91 specifying key contacts for notification, 91 suv_error.
