Index [student.ing-steen.se]student.ing-steen.se/unix/hp-ux/B2355-90156.pdf · 110 Index Index to a speciﬁc logical printer, 24 Q queue purpose, 36 queues, 17 list of attributes,

110 Index

Index

to a specific logical printer, 24

Qqueue

purpose, 36queues, 17

list of attributes, 63quotation marks, 25

R-r flag, 30, 44range and dimensions, 60redirecting data, 79reference file, 28requested-attributes, 61

formatting, 67syntax, 61

requested-attributes command-attribute, 45, 47, 49

requesting attribute values, 60results-profile, 58results-profile attribute, 28results-set-comment, 28

S-s flag, 44server name

when to specify, 53servers, 17

list of attributes, 63settable attributes, 54setting

logical printers, 23object-attributes, 54

sides attributespecifying, 26

single-valued attributes, 56specifiable attributes, 54spooler

purpose, 36spoolers, 17status information, 30

style command-attribute,45,49,67

style of output, 68submitting jobs, 24supervisor

purpose, 36supervisors, 17syntax

commands, 41for attribute values, 56notation, 9range of values, 60requested-attributes, 61using abbreviations, 79

T-t flag, 44terminology

basic, 17time and date, 59tray

specifying, 29

U-U flag, 44

Vvalidation

defined, 17validation of jobs, 14, 17values, 17

using abbreviations, 79

W-w flag, 46when command-attribute, 46, 49wildcards, 79

X-X flag, 46, 72-x flag, 41, 46, 72

Index

Index 109

number-up attribute, 27

Oobject, 17object classes, 36object-attributes, 41, 42

default values, 56description of, 51setting, 54

objectsnaming restrictions, 37purposes, 36

optionsspecifying for jobs, 25

orientation valuespecifying, 26

output-bin, 28

P-p flag, 44page orientation

specifying, 26page-count, 29pages

specifying number, 29paper

specifying type, 29PD_CONFIRM_DELETE

description, 76PD_MAXRETRIES

description, 77PD_MAXTHREADS

description, 77PD_MEMLIMIT

description, 77PD_RETRY_INTERVAL

description, 77PD_SOCKET

description, 77PDBASE

description, 76pdclean command

description, 39summary of, 82

pdcreate commanddescription, 39summary of, 83

pddcesetup commanddescription, 39

pddelete commanddescription, 39summary of, 84

pddisable commanddescription, 39summary of, 85

pdenable commanddescription, 39summary of, 86

pdgwcfg command, 39PDIDTABLE

description, 77pdls command, 60

authorization, 75description, 38summary of, 87

pdmod commanddescription, 38summary of, 89

pdmsg commanddescription, 38

PDPATH, 72description, 76

pdpause commanddescription, 39summary of, 90

pdpr command, 24, 28description, 38specifying attributes, 25summary of, 91

PDPRINTER, 23, 24description, 76

pdpromote commanddescription, 39summary of, 93

pdq command, 31, 60

description, 39summary of, 94

pdresubmit commanddescription, 39summary of, 95

pdresume commanddescription, 39summary of, 96

pdrm command, 34description, 39summary of, 97

pdset commanddescription, 39summary of, 98

pdshutdown commanddescription, 39summary of, 100

pdstartclient commanddescription, 40

pdstartspl commanddescription, 40

pdstartsuv commanddescription, 40

pdstopd commanddescription, 40

physical printerpurpose, 36

physical printers, 17portrait orientation

specifying, 26printer devices, 17printer-locations, 33printer-name-requested

command-attribute, 44, 49printer-name-requested object-

attribute, 52printer-register-threshold, 60printers

determining logical printernames, 24

list of attributes, 63printing

to a default logical printer, 24

108 Index

Index

global ID, 74

H-h flag, 21, 43headings command-attribute,

43, 49, 67help

for HPDPS commands, 21

Iimages

specifying number for a page,27

initial value objects (IVOs)to specify attribute values, 70

initial-value-documentdefined, 70list of attributes, 63purpose, 36

initial-value-jobdefined, 70list of attributes, 63purpose, 36

input-tray-select, 29

J-j flag, 44job

purpose, 36job identifiers, 74job-client-id

list of attributes, 63job-copies, 28job-hold object-attribute, 52job-name object-attribute, 45, 52job-print-after, 59job-retention-period object-

attribute, 45, 52jobs, 17

deleting, 34determining status, 30determining where printed, 33

list of attributes, 63printing multiple documents,

27specifying attributes, 25specifying copy count, 26specifying document format,

27specifying duplex, 26specifying orientation value,

26submitting, 24

job-size-range-ready, 58job-size-range-supported, 58

L-l flag, 44landscape orientation

specifying, 26LANG

description, 78LC_ALL

description, 78LC_CTYPE

description, 78LC_MESSAGES

description, 78LC_MONETARY

description, 78LC_NUMERIC

description, 78LC_TIME

description, 78local ID, 74log

purpose, 36logical printer

purpose, 36logical printers, 17

defining, 23determining names, 24

logslist of attributes, 63

lp commandtranslated to HPDPS

commands, 102LP spooler

commands translated toHPDPS commands, 102

specifying commands, 20lpadmin command

translated to HPDPScommands, 106

lpstat commandtranslated to HPDPS

commands, 103

M-m flag, 44man command, 21medium

specifying, 29message command-attribute,44,

49multiple copies

printing, 27multiple-valued attributes, 57

N-N flag, 44-n flag, 26, 44namespace

DCE, 54naming

objects, 37NLSPATH

description, 78non-settable attributes, 54notification

benefits, 15, 16notification profile, 57notification-delivery-method

command-attribute, 44, 49notification-profile attribute, 57notify-operator, 58

Index

Index 107

Symbols.login, 23.profile, 23

Aabbreviations

for attributes and values, 79arguments

description, 53attribute manpages, 22attribute value pair, 25, 41attributes, 17

complex, 57defaults, 56frequently used, 51multiple value, 57requesting values, 60settable, 54single value, 56specifiable, 54specifying, 25specifying for jobs, 25using abbreviations, 79values, 17

attributes command-attribute,49

attributes file, 72authorization, 75

BBasic Environment, 17

authorization, 75

C-c flag, 43cancel command

translated to HPDPScommands, 106

class command-attribute, 43, 49classes, 36command

syntax, 41command flags, 42command-attributes, 42, 48

default values, 56description of, 41

commandsdescription of arguments, 53summary of definitions and

user type, 38complex attribute, 28complex attributes, specifying,

57computer font, 9content-orientation attribute

specifying, 26copy-count

specifying attribute, 26specifying flag, 26

copy-count object-attribute, 44,52

Ddate and time, 59DCE

Extended Environment, 17Extended Environment

authorization, 75DCE Directory Service, 54default logical printer, 23default values

for command and object-attributes, 56

default-input-tray, 29default-medium, 29deleting

jobs, 34delivery-address, 28delivery-method, 28document

list of attributes, 63purpose, 36

document identifiers, 74

document-formatspecifying, 27

document-format object-attribute, 52

documentsprinting in a single job, 27

duplexspecifying, 26

Eenvironment variables

LANG, 78LC_ALL, 78LC_CTYPE, 78LC_MESSAGES, 78LC_MONETARY, 78LC_NUMERIC, 78LC_TIME, 78NLSPATH, 78PD_CONFIRM_DELETE, 76PD_MAXRETRIES, 77PD_MAXTHREADS, 77PD_MEMLIMIT, 77PD_SOCKET, 77PDBASE, 76PDIDTABLE, 77PDPATH, 76PDPRINTER, 76

F-F flag, 43-f flag, 43filter command-attribute, 49flags

examples, 47using, 42

formattingrequested-attributes, 67

G-g flag, 43global character, 79

106 Appendix B

LP Spooler Commands Translated to HPDPS CommandsLP Spooler Commands

lpstat -p PrinterName pdls -U -c printer -f" printer-name==PrinterName &&printer-realization==logical" -r printer-nameprinter-ready enabled \*:

Lists status ofPrinterName.

lpadmin -d PrinterName No equivalent HPDPS command. Sets up a logicalprinter as thedefault printer.

cancel RequestId pdrm GlobalJobID

pdrm LocalJobID

Cancels the jobspecified by theRequestId.

LPCom-mand

LP Flag HPDPS Command, Flag andValue Action

Appendix B 105


lpstat -u UserName1,UserName2, ...

pdls -U -c job -f" job-owner== UserName1 ||job-owner== UserName2 || …"-r job-client-idjob-owner job-prioritysubmission-time job-nametotal-job-octets” \*

Lists status ofprint jobs foreach UserNamein list of users.

lpstat -o PrinterName pdls -U -c job -f"printer-name-requested==PrinterName” -r" printer-name-requestedjob-client-id job-ownerjob-prioritysubmission-time job-nametotal-job-octets " \*:

Lists status ofjobs forPrinterName.

lpstat -o Request_Id pdls -r -g -c job LocalJobID Lists status ofprint job.

lpstat -o ListOfRequest-Ids,PrinterNames

pdls -r -g -c jobLocalJobID_1 … LocalJobID_npdls -r -g -c printerLogicalPrinterName_1 …LogicalPrinterName_n

Invokesmultipleinstances ofabove lpstat-o .

lpstat -s Equates to -d ,-v without anyarguments.

lpstat -t Equates to -s ,-a , -p , -owithout anyarguments.

lpstat -p pdls -U -c printer -f" printer-realization==logical " -r " printer-nameprinter-ready enabled " \*:

Lists status ofall printers.

LPCom-mand


104 Appendix B


lpstat -a pdls -U -c printer -f" printer-realization==logical " -r enabled \*:

Listsacceptancestate of allprinters.

lpstat -a PrinterName pdls -U -c printer -f" printer-realization==logical && printer-name==PrinterName" -r enabled \*:

Listsacceptancestate ofPrinterName.

lpstat -a PrinterName1,PrinterName2, ...

pdls -U -c printer -f"printer-realization==logical && printer-name==PrinterName1 || printer-name==

PrinterName2 ||...” -renabled \*:

Listsacceptancestate for eachPrinterName inlist of printers.

lpstat -d No equivalent HPDPS command. Prints thesystem defaultdestination forlp .

lpstat -u pdls -U -c job -r" job-client-id job-ownerjob-prioritysubmission-time job-nametotal-job-octets " \*:

Lists status ofprint jobs for allusers.

lpstat -u UserName pdls -U -c job -f" job-owner== UserName" -r" job-client-id job-ownerjob-prioritysubmission-time job-nametotal-job-octets " \*:

Lists status ofprint jobs forUserName.

LPCom-mand


Appendix B 103


lp -t title pdpr -x " job-name= JobName" Specifies avalue for thejob-nameattribute, whensent to anHPDPS logicalprinter.

lp -w pdpr -x" notification-profile={event-identifiers=job-completedelivery-method=email} "

Notifiesjob-originatorwhen a job hasprinted.

lp -s HPDPS default behavior for thepdpr command.

Suppressesmessages.

lp pdpr -x " job-sheets=job-set-start "

Includes abanner page.

lp -onb pdpr -x " job-sheets=none " Does notinclude abanner page.

lpstat -v pdls -U -c printer -f" printer-realization==logical " \*:

Lists devicenames of allprinters.

lpstat -v PrinterName pdls -U -c printer -f"printer-realization==logical && printer-name==PrinterName" \*:

Lists devicename forPrinterName.

lpstat -v PrinterName1,PrinterName2, ...

pdls -U -c printer -f"printer-realization==logical && printer-name==PrinterName1 ||printer-name==PrinterName2"|| \*:

Lists devicenames for eachPrinterName inlist of printers.

LPCom-mand


102 Appendix B


LP Spooler CommandsTable B-1

LPCom-mand


lp -c HPDPS default behavior for thepdpr command.

Makes a copyof the file to beprinted. Allowsthe user tochange the filebefore the jobhas printedwithoutaffecting theprinted output.

lp -d dest pdpr -p PrinterName Submits the jobto the specifiedprint queue orHPDPS logicalprinter.

lp -m pdpr -N email Delivers allmessagesregarding thejob by electronicmail.

lp -n number pdpr -x " results-profile=::: CopyCount:"

Prints thespecifiednumber of jobcopies.

lp -o option pdpr -x" printer-pass-through=-o option"

Specifiesprinter-specificoptions.

Appendix B 101

LP Spooler Commands Translated to HPDPS Commands

B LP Spooler CommandsTranslated to HPDPSCommands

100 Appendix A

Command SummaryHPDPS Commands

pdshutdown Flags:

-c server

-h

-m "MessageText"

-w {after-current | now | after-all }

-x "AttributeValuePairs"

-X AttributesFileName

Command Attributes:

attributes =AttributesFileName

class =server

message ="MessageText"

when={after-current | now | after-all }

Argument:

ServerName

Command Flags, Attributes, and Arguments

Appendix A 99


pdset (cont.) Command-Attributes:


class ={printer| job | server |queue | document |initial-value-job | initial-value-document | log }

headings = {true | false }


requested attributes ={none, brief , verbose }

style ={column | line }

Arguments:

[ServerName:]InitialValueJobName

[ServerName:]InitialValueDocumentName

ServerName:LogName

[ServerName:]PrinterName

[ServerName:]QueueName

ServerName

LocalJobID

GlobalJobID


98 Appendix A


pdset Flags:

-c {printer | job | server | queue | document |initial-value-job | initial-value-document | log }

-g

-h

-m "MessageText"

-r {none, brief ,verbose }

-s {column | line }




Appendix A 97


pdrm Flags:

-h

-m "MessageText"

-r JobRetentionPeriod



Command-Attributes:



Object-Attributes:

job-retention-period =JobRetentionPeriod

Arguments:

LocalJobID

GlobalJobID


96 Appendix A


pdresume Flags:

-c {printer | queue | job | server }

-h

-m "MessageText"



Command-Attributes:


class ={printer | queue | job | server }


Arguments:

LocalJobID

GlobalJobID



ServerName


Appendix A 95


pdresubmit Flags:

-c {job | queue | printer }

-g

-h

-r {none| brief , verbose }

-s {column | line }



Command-Attributes:


class ={job | queue | printer }

headings ={true | false }

requested-attributes ={none, brief , verbose }


Arguments:

[ServerName:]TargetPrinterName

LocalJobID

GlobalJobID




94 Appendix A


pdq Flags:

-f "FilterCriteria"

-F

-g

-h

-j

-p PrinterName

-r {brief, none , verbose , "AttributesList" | all }

-s {column | line }

-U



Command-Attributes:


filter="FilterCriteria"


printer-name-requested =PrinterName

requested-attributes ={brief, all , none , verbose ,"AttributesList"}


Arguments:

[LocalJobID[.DocNumber.]]

[GlobalJobID[.DocNumber.]]


Appendix A 93


pdpromote Flags:

-h

-m "MessageText"



Command-Attributes:



Arguments:

LocalJobID

GlobalJobID


92 Appendix A


pdpr (cont.) Command-Attributes:



notification-delivery-method ={email, message , none }

requested-attributes ={none, verbose , brief }

style ={column| line }

Object-Attributes, per document:

copy-count ={1 | CopyCount}

document-format ={ascii | pcl | PostScript | passthru }

Object-Attributes, per job:

printer-name-requested =[ServerName:]PrinterName

job-name =JobName

Arguments:

[FileName]


Appendix A 91


pdpr Flags:

-f FileName

-g

-h

-l

-n {1 | CopyCount}

-N {email | message | none}

-p PrinterName

-r {none, brief , verbose }

-s {column | line }

-t JobName




90 Appendix A


pdpause Flags:

-c {printer | queue | job |server }

-h

-j

-m "MessageText"



Command-Attributes


class ={printer | job | queue | server }


Arguments:



ServerName


Appendix A 89


pdmod Flags:

-g

-h

-m "MessageText"

-n CopyCount


-s {column | line }

-t JobName



Command-Attributes:




requested-attributes ={none, verbose , brief }


Object-Attributes:

copy-count =CopyCount

job-hold ={true | false }

job-name =JobName

Arguments:

LocalJobID

GlobalJobID


88 Appendix A


pdls (cont.) Command-Attributes:


class ={job | queue | document | initial-value-job |initial-value-document | log | printer | server }

filter ="FilterCriteria"


requested-attributes ={brief, none , verbose , archive ,"AttributesList" | all }

style ={column | line} column forrequested-attributes =brief andrequested-attributes =verbose , line forrequested-attributes =all ,requested-attributes ="AttributesList" andrequested-attributes =archive

Arguments:

LocalJobID[.DocNumber]

GlobalJobID[.DocNumber]

ServerName:InitialValueDocumentName

ServerName:InitialValueJobName

ServerName:LogName



ServerName


Appendix A 87


pdls Flags:

-c {job | queue | log | printer|initial-value-job |initial-value-document | document |server }

-f "FilterCriteria"

-F

-g

-h

-j

-r {brief, all , verbose , archive , "AttributesList" |none }

-s {column | line} column for -r brief and -rverbose , line for -r all , -r "AttributesList" and -rarchive

-U




86 Appendix A


pdenable Flags:

-c {printer | log | queue |server }

-h

-m "MessageText"



Command-Attributes:


class ={printer | log | queue |server }


Arguments:

ServerName:LogName



ServerName

pdgwcfg Flags:

-{a | -m} }

-h

-p

-v


Appendix A 85


pddisable Flags:

-c {printer |log |queue | server }

-h

-m "MessageText"



Command-Attributes:


class ={printer |log | queue | server }


Arguments:

ServerName:LogName



ServerName


84 Appendix A


pddelete Flags:

-c {printer | job |queue | initial-value-job |initial-value-document | server }

-h

-m "MessageText"

-r JobRetentionPeriod



Command-Attributes:


class ={printer |job | queue | initial-value-job |initial-value-document | server }


Object-Attributes:

job-retention-period =JobRetentionPeriod

Arguments:

LocalJobID

GlobalJobID

ServerName:PrinterName



ServerName:QueueName

ServerName


Appendix A 83


pdcreate Flags:

-c {printer | queue | initial-value-job |initial-value-document }

-g

-h

-m "MessageText"


-s column | line



Command-Attributes:


class ={printer | queue | initial-value-job |initial-value-document }

force ={true | false}

headings ={true |false }


requested-attributes ={none, brief , verbose }


Arguments:

ServerName:PrinterName

ServerName:QueueName




82 Appendix A


HPDPS CommandsTable A-1 Command Summary


pdclean Flags:

-c {printer | queue | server }

-h

-m "MessageText"



Command-Attributes:


class ={printer | queue | server }


Arguments:



ServerName

Appendix A 81

Command Summary

A Command Summary

This appendix presents HPDPS commands alphabetically and the flags,command-attributes, and arguments that each command supports.Default values are shown in bold. See Table 3-2, “HPDPS UserCommands,” and Table 3-3, “HPDPS Administrator Commands,” inChapter 3 for a description of each command.

80 Chapter 3

Command ReferenceAdditional Tips

Chapter 3 79

Command ReferenceAdditional Tips

Additional TipsThe following tips can make your use of commands easier.

Global Character (Wildcard) SupportYou can use the global asterisk character (*) to facilitate broadcastingcommands to all servers. For example, STU*: sends the command to allservers whose names begin with the letters STU.

Follow the shell-specific rules pertaining to the shell you are using. Someshells may intercept and interpret the asterisk before HPDPS has achance to operate on it. In these cases, you can surround the asterisk bycontrol characters, typically some form of quotes supported by the shell,to prevent premature interpretations.

Abbreviations for Attributes and ValuesAttributes and values can often be abbreviated by using the first letter ofeach word. Thus, the media-used attribute can be abbreviated to m-u.However, in instances where abbreviations are not unique, you will needto use more letters. For example, you cannot use j-o because of theoverlap for job-owner and job-originator . Instead, use j-ow forjob-owner or j-or for job-originator .

Redirecting DataYou can use the pdls command to create a file that contains the data youwould normally see on the display screen. You might want to do this tocreate a new attributes file or to archive the present data so you canrecover it later on. For example, to create a file SPOOL1.archive thatcontains specifiable and settable attributes and their values for serverSPOOL1, sending it to the specified directory, enter:

pdls -c server -r archive -g SPOOL1 > /attr/SPOOL1.archive

78 Chapter 3

Command ReferenceEnvironment Variables

LANG The name of the locale to use for local categories when neitherLC_ALL nor the corresponding environment variable beginningwith LC_ specifies a locale. Used to determine the language,territory, or character set of messages and other informationthat are sent to a person. Commands: All

LC_ALL The name of the locale used to override any values for localcategories specified by the setting of LANG or any environmentvariables beginning with LC_.

Commands: All

LC_CTYPE The name of the locale for character classification.

Commands: All

LC_MONETARY The name of the locale containing monetary-related numericediting information.

Commands: All

LC_NUMERIC The name of the locale containing numeric editing, such asradix and character information.

Commands: All

LC_TIME The name of the locale for date and time formattinginformation.

Commands: All

LC_MESSAGES The name of the locale for STDERR messaging.

Commands: All

NLSPATH The NLSPATH should be set to /opt/pd/lib/nls/msg/C/%Nor/opt/pd/lib/nls/msg/%L/%N:/opt/pd/lib/nls/msg/C/%N

Variable Description

Chapter 3 77


PD_MEMLIMIT Defines the maximum amount of memory (in kilobytes) the

spooler or supervisor can use on the host system.

PD_SOCKET The value for the socket number provided by your HPDPSadministrator. The socket number you specify should be for aHPDPS client and compatible with the value you specify foryour LANG environment variable.

PD_MAXRETRIES Specifies the number of times a command will retry when itcan’t reach the client daemon. (The default is 0, no retries, ifPD_MAXRETRIES is not otherwise set.) A non-default value, ifneeded, should be provided by your HPDPS administrator.PD_MAXRETRIES is read by each command invocation. Insituations involving the simultaneous arrival of concurrentprint jobs when the client daemon cannot accept new requests,setting this variable to a non-default value can prevent thecommand from quitting prematurely.

PD_MAXTHREADS Specifies the limit on simultaneous pdclientd commandthreads. (The default is 50.) This environment variable, whenset, is done so in the pdstartclient script.

PD_RETRY_INTERVAL Specifies the number of seconds to wait between commandretries. (The default is 5, if PD_RETRY_INTERVAL is nototherwise set.) The value, if needed, should be provided by yourHPDPS administrator. This is a back-off mechanism for burstrequest situations to keep the client daemon from beingoverwhelmed with simultaneous new requests when it is at itsresource limit. PD_MAXRETRIES is read by each commandinvocation.

PDIDTABLE Controls the size of the table that maps local job identifiernumbers and global job identifier numbers for jobs submittedto HPDPS clients. If you have many users who submit a smallnumber of jobs, you can improve performance by reducing thesize of the tables for each user.


76 Chapter 3


Environment VariablesTo set environment variables, edit the file that contains them. See“Defining a Default Logical Printer” in Chapter 2 for instructions onmodifying your .profile file (if you are using the POSIX or Korn shell)or your .login file (if you are using the C shell).

Table 3-8, “Environment Variables,” describes the environment variablesthat affect how HPDPS commands are processed. For more detailedinformation on those environment variables used primarily by theadministrator, see the HP Distributed Print Service AdministrationGuide.

Table 3-8 Environment Variables


PDPRINTER Used as the default logical printer by the print client when the-p PrinterName flag or the printer-name-requestedattribute is not specified.

Commands: pdpr, pdq, pdls

PDPATH A path of directories that are searched for the file namespecified in the -X AttributesFileName flag. Multipledirectories are separated by a colon (:). If the PDPATHenvironment variable does not exist, the current workingdirectory of the person submitting the command is used.Commands: All

PDBASE Specifies the root directory where the HPDPS server stores allof its working files, such as logging or tracing files. Each serverhas its own subdirectory under this directory to avoid nameconflict when multiple servers are on the same machine.Commands: pdstartspl, pdstartsuv, pdstartclientd

PD_CONFIRM_DELETE Specifies whether HPDPS issues a confirmation messagebefore deleting a printing object.

Commands: pdclean, pddelete, pdrm

Values: yes , no

Default: yes

Chapter 3 75

Command ReferenceAuthorization

AuthorizationThe administrator configures each HPDPS host to run in one of twoenvironments: the Basic Environment or the DCE ExtendedEnvironment.

The Basic Environment is used when your host is not a member of aDistributed Computing Environment (DCE) cell. In the BasicEnvironment, only the root login may create, modify, or delete HPDPSobjects; all other logins are not authorized to perform these operations.All logins are authorized to print to each printer defined on the host, andmay use all initial-value-job and initial-value-document objects. Alllogins are also authorized to list the attributes of all objects defined onthe host with the pdls command.

The DCE Extended Environment is used when your host is a member ofa DCE cell. Your level of authorization is determined by your DCE login.In the DCE Extended Environment, there are three levels of security:

Administrator Can create, modify, and delete HPDPS objects.

Operator Can modify HPDPS objects, but not create or deletethem.

User Can perform those operations for which an HPDPSadministrator gives authorization. Normally, a user isnot given authorization to create, modify, or deleteHPDPS objects, other than his own jobs anddocuments.

If a user is not logged in to DCE, he may be able toaccess certain logical printers that have beenconfigured not to require DCE authorization. If so, hemay also access his own jobs and documents sent tothose printers. A user cannot access any logicalprinters that are configured to require DCEauthorization.

The administrator for your system will provide the proper authorizationsfor you depending on your job responsibilities. Another person cannotchange the condition of your jobs unless that person has the properauthorization to do so. See HP Distributed Print Service AdministrationGuide for information on security and how authorization is set andcontrolled.

74 Chapter 3

Command ReferenceJob and Document Identifiers

Job and Document IdentifiersMany commands accept job identifiers as input. Job identifiers(LocalJobID and GlobalJobID ) are specific arguments for somecommands. Local IDs are generated for each user, on each host, for eachjob.

A job can be referenced by either a local ID or global ID number:

• A local ID is represented as a single integer generated by the client.For example:

10

• A ServerName, a colon (:), and a number generated by the serverrepresents a global ID. For example:

server1:1019198802

• Only you (the person who submits the job) can use the local job ID.

• If you omit the server name from the command, the client assumesthat the job identifier is a local ID.

• You must be authorized to modify jobs belonging to another personand must always use the global ID to do so. See “Authorization” forfurther information.

Specific Documents within JobsA subset of the commands that accept a job-identifier parameter alsopermit you to specify a specific document number within a multiple-document job. The document number, if present, is separated by a period(.) from the job identifier. Within each multiple-document job, thedocuments are numbered starting with 1.

An example of a local ID for document number 1 is:

10.1

An example of a global ID for document number 3 is:

SPOOL1:1022565604.3

Chapter 3 73

Command ReferenceUsing an Attributes File

Both of the previous examples referenced the following sample attributesfile:

# Physical Printer Attributes File# AttrFilePP1document-formats-supported =ascii pclmaximum-copies-supported =3document-types-supported =printableprinter-memory =32

This attributes file is equivalent to the following command:

pdset -c printer -x "document-formats-supported=ascii pcl \maximum-copies-supported=3 document-types-supported=printable \printer-memory=32" PhysPrt2

• Command-attributes, and any settable or specifiable object-attributes, including the command-attribute attributes can belisted in an attributes file. Thus, an attributes file can invoke otherattributes files.

If an attributes file calls itself, an error is reported.

• You can only use a file that contains both specifiable and settableattributes with the pdcreate or pdpr commands.

If a specifiable attribute is listed in an attributes file and the file isused with the pdset or pdmod commands, the attribute is rejectedand an error message is issued.

See “Setting Object-Attributes” earlier for more information onspecifiable and settable attributes.

• Comment lines can exist in attribute files. The comment starts with a# and ends at the end of the line. This was illustrated in the abovesample attribute file.

72 Chapter 3

Command ReferenceUsing an Attributes File

Using an Attributes FileYou may want to pre-define specific attribute value pairs in permanentfiles and access them when you need those specific values within acommand.

When creating a file containing attribute and value pairings, you maywant to use space between the end of each attribute name and the equalsign so the equal signs and values are aligned. (See the sample attributefile in the section below.) This makes your files easier to read andmaintain.

If you do not specify a full path name for your attributes file, HPDPSuses the path name from the environment variable PDPATH to locate theattributes file.

If PDPATH is undefined or contains a null string, HPDPS looks in yourcurrent working directory for the attributes file. For example, if PDPATHcontained /home/smith/ , the following command would read file/home/smith/my_attributes to obtain the attributes file:

pdpr -X my_attributes File1

Reading in the Attributes FileYou can read in an attribute file in the following ways:

• Use the -x flag and specify the command-attribute attributes :

pdset -x "attributes=AttrFilePP1" PhysPrt2

• Use the -X flag to specify an attributes file name:

pdset -X AttrFilePP1 PhysPrt2

• Use both to read an attribute file into a command.

NOTE The -X and -x flags are additive so that all attributes and values areused. If the same object-attribute is specified more than once in acommand with multiple uses of the -x , -X command flags or theattributes command-attribute, or a combination of them, the valueread last takes precedence.

Chapter 3 71

Command ReferenceCommand Syntax

3. Re-enable the printer:

pdenable logptr

70 Chapter 3


Using Initial Value Objects (IVOs) to SpecifyAttribute ValuesAn initial value object (IVO) represents a collection of default valuesfor job or document attributes. There are two types of initial valueobjects:

initial-value-document Specifies values for documentattributes.

initial-value-job Specifies values for job attributes.

IVOs are contained in the spooler and can be used in two ways:

1. A logical printer can be created so it specifies a job or a document IVOor both that will provide values for all jobs submitted to that logicalprinter.

2. You can specify a job or a document IVO or both for a specific job withthe pdpr command when you submit the job.

HPDPS uses the attribute values specified in the IVOs and on thecommand line in the following order:

1. Attribute values from an IVO associated with the logical printer areused first.

2. Attribute values from an IVO specified with the pdpr commandoverride any values for the same attribute identified in the IVOassociated with the logical printer.

3. Attribute values entered on the command line or from an attributefile specified with the pdpr command override the values for anyattributes with the same name that were specified in the previoustwo conditions.

Here is an example of setting up an initial-value-job for a printer in orderto disable a banner page.

1. Create an initial-value-job for Spooler1 :

pdcreate -c initial-value-job -x “job-sheets=none” \Spooler1:no_banner_IVJ

2. Disable logical printer logptr and assign the initial-value-job to it:

a. pddisable logptr

b. pdset -c printer \-x “printer-initial-value-job=no_banner_IVJ” logptr

Chapter 3 69


This will display the requested attributes, with headings, for all of thelogical printers in the server (spooler) SPOOL2. Here "headings" meansthat each attribute name is preceded by the object name. The outputlooks like:

LogPrt1: maximum-copies-supported = 3LogPrt1: printer-name = LogPrt1LogPrt1: document-formats-supported = document-format-postscript

document-format-asciiLogPrt1: associated-server = SPOOL2LogPrt1: printer-realization = logicalLogPrt1: printers-ready = PhysPrt1LogPrt1: printer-associated-printers = PhysPrt1

PhysPrt2PhysPrt3

LogPrt1: associated-queue = loneQueueLogPrt2: maximum-copies-supported = 10LogPrt2: printer-name = LogPrt2LogPrt2: document-formats-supported = document-format-postscriptLogPrt2: associated-server = SPOOL2LogPrt2: printer-realization = logicalLogPrt2: printers-ready = PhysPrt2LogPrt2: printer-associated-printers = PhysPrt1

PhysPrt2PhysPrt3

LogPrt2: associated-queue = loneQueueLogPrt3: maximum-copies-supported =LogPrt3: printer-name = LogPrt3LogPrt3: document-formats-supported =LogPrt3: associated-server = SPOOL2LogPrt3: printer-realization = logicalLogPrt3: printers-ready = PhysPrt3LogPrt3: printer-associated-printers = PhysPrt1

PhysPrt2PhysPrt3

LogPrt3: associated-queue = loneQueue

Line Style without Headings. The following sample commanddisplays the requested printer attributes in the line style withoutheadings for SPOOL3:

pdls -c printer -x "style=line headings=false" SPOOL3:

If there is one printer, the output looks like:

printer-name = LP0printer-realization = logicalenabled = trueassociate-queue = Queue0

68 Chapter 3


Specifying headings=true or using the default, causes the followingdepending on the style selected, as described in the next section:

column The output is displayed with column headings.

line The object name precedes the attribute name.

See “Style” below for examples of displayed output with and withoutheadings.

Style . The style command-attribute or the -s flag is used to specifythe format of presentation for attribute values returned by the server.The following shows the value of style depending on the value ofrequested-attributes :

Value Default if the value of the requested attribute is…

column brief or verbose

line all , archive , or "AttributesList".

If you request groups of attributes with the -r flag (-r brief or -rverbose ), HPDPS provides the results in line style unless you alsorequest column style with -s column .

Column Style with Headings. Use the following command to displaythe requested printer attributes in the column style with headings forSPOOL1:

pdls -c printer -x "style=column headings=true \requested-attributes=printer-name printer-realization \printer-state" SPOOL1:

This will display the requested attributes for all of the logical printers inthe server (spooler) SPOOL1. The output looks like this:

Printer Realization State------- ----------- -----LogPrt1 logicalLogPrt2 logicalLogPrt3 logical

Line Style with Headings. Here is a sample command to display therequested printer attributes in the line style with headings for SPOOL2:

pdls -c printer -x "style=line headings=true" \-r maximum-copies-supported,printer-name,\document-formats-supported, associated-server,\printer-realization printers-ready,\printer-associated-printers,associated-queue SPOOL2:

Chapter 3 67


Formatting the Display of Attribute ValuesUse the headings and style command-attributes to format the displayof requested-attributes.

Headings . The headings command-attribute is used to specifywhether or not the output is to be displayed with headings. The default isto display with headings. Specifying headings=false or using the -gflag turns off headings.

Queue Brief:

associated-server

queue-name

queue-state

scheduler-ready

Verbose:

logical-printer-assigned

physical-printer-assigned

Server Brief:

server-name

server-state

server-type

Verbose:

logical-printers-supported(spooler)

physical-printers-supported

queues-supported

Object Attributes

66 Chapter 3


Log Brief:

associated-server

enabled

log-identifier

log-type

Verbose:

log-size

log-wrap

Printer Brief:

associated-queue

availability

enabled

printer-name

printer-realization

printer-state

Verbose:

associated-server

printer-associated-printers (logicalprinters)

printer-locations

scheduler-ready

Object Attributes

Chapter 3 65


Job Brief:

current-job-state

intervening-jobs (See Note 1)

job-client-id (local ID)

job-identifier (global ID)

job-name

printers-assigned (See Note 2)printer-name-requested (See Note 3)

Verbose:

job-owner

job-state-reasons

total-job-octets (See Note 4)

Notes:

1. Only returned on the pdls and pdqcommands.

2. Physical printer name to which the jobhas been assigned (if such a schedulingdecision has been made).

3. Logical printer name to which the jobwas submitted.

4. Sum of all files and copies.

Object Attributes

64 Chapter 3


Initial-Value-Job Brief:

associated-server

initial-value-job-identifierlogical-printers-ready

printer-locations-requestedprinter-models-requested

Verbose:

job-retention-period

Object Attributes

Chapter 3 63


Table 3-7 HPDPS Object-Attributes

Object Attributes

Document Brief:

document-file-name

document-format

document-sequence-number

Verbose:

copy-count

document-type

octet-count

sides

Initial-Value-Document Brief:

associated-server

copy-count

document-format

initial-value-document-identifier

logical-printers-ready

sides

Note: No Verbose attributes.

62 Chapter 3


The attribute values for requested-attributes are listed here alongwith the commands involved:

Values Available on…

all the pdls and pdq commands.

archive the pdls and pdq commands, only displaying thespecifiable and settable attributes. Refer to “SettingObject-Attributes” earlier for more information.

brief the pdcreate , pdls , pdmod, pdpr , pdq , and pdsetcommands.

"AttributesList" the pdls and pdq commands.

none the pdcreate , pdls , pdmod, pdpr , pdq , and pdsetcommands. none is the default for all the commandsexcept pdls and pdq .

verbose the pdcreate , pdls , pdmod, pdpr , pdq , and pdsetcommands. verbose is the default for the pdls andpdq commands.

Multiple values can be specified in a comma-delimited list when usingthe -r flag. For example:

-r brief,document-formats-supported

Multiple values can also be specified in a string using the -x flag on thecommand line. The following example is equivalent to the previousexample:

-x "requested-attributes=brief document-formats-supported"

The result is the combination of the attribute values defined for brief ,and the document-formats-supported attribute. Whenever youcombine values with the -r flag or the requested-attributesattribute, the displayed output is shown in line format unless youspecify the column format. See “Formatting the Display of AttributeValues” shortly for formatting information.

Table 3-7, “HPDPS Object-Attributes,” lists the HPDPS objects alongwith the brief and verbose attribute values. The brief values are asubset of the verbose attribute value.

Chapter 3 61


-r Specifies the attributes for which values are to bereturned. This flag is equivalent to using thecommand-attribute requested-attributes .Refer to “Values for requested-attributes” in thenext section for a description of the use of thiscommand-attribute and flag.

-s Specifies the style or format in which the attributevalues are to be displayed. This flag is equivalent tousing the command-attribute style . Refer to“Style” later for a description of this command-attribute and flag.

• In addition to pdls and pdq , the commands you use to create objectsand to modify the values for objects can also be used to request that alimited set of attribute values be returned. The command-attributesdiscussed within this section are supported by the followingcommands:

For all objects: pdls , pdcreate , and pdset

For job and document objects: pdq , pdpr , and pdmod

Values for requested-attributesTo list the attribute values for requested-attributes , use either the-r flag, the command-attribute requested-attributes , or acombination of both. For example, using the -r flag to request allattributes for a printer LogPrt1 , enter:

pdls -c printer -r all LogPrt1

Using the command-attribute, you would enter:

pdls -c printer requested-attributes=all LogPrt1

60 Chapter 3


This format specifies hours and minutes; hours are optional. If hours areused, separate the two values with a colon, with no spaces. This exampleshows a time interval of 1 hour and 15 minutes:

pdset -c printer -x "printer-register-threshold=1:15" PhysPrt4

This can also be expressed as:

pdset -c printer -x "printer-register-threshold=75" PhysPrt4

Attribute Values for Range and DimensionsFor a range of values or dimensions, the syntax is:

AttributeName=nnn:nnn

Separate the two numeric values with a colon. For example:

pdset -c printer -x \"job-size-range-supported=0:9223372036854775800" PhysPrt3

Requesting Attribute Values from ObjectsYou can use the pdq and pdls commands to request that the systemreturn the attribute values for a specified object or objects.

• The pdq command requests the values of attributes for jobs anddocuments which are currently queued for printing. If you do notspecify a job identifier with the pdq command, the command uses thelogical printer specified in the PDPRINTER environment variable.Refer to “Job and Document Identifiers” later for more information onjob identifiers. PDPS determines the queue associated with thelogical printer and returns the values for all of the jobs in the queuethat have been submitted by you (based on your user-nameattribute, which defaults to your login).

• The pdls command requests the values of attributes for all objects,including jobs (both queued and retained).

• The following flags are used to specify the attributes for which valuesare to be returned and how the values should be presented:

-g Specifies that headings are not to be used when theattribute values are displayed. This flag isequivalent to using the command-attributeheadings=false . Refer to “Formatting the Displayof Attribute Values” later for more information.

Chapter 3 59


The rules for using a colon are as follows:

• Do not enter the component name.

• Separate the value for each component with a colon (:) and no spaces.

• Separate each attribute value with spaces.

• Enter a colon (:) even if you are not going to enter a value for a givencomponent. The default value or no value will be set for thatcomponent.

• If the last value is to be set to the default value, the colon (:) for thatcomponent is not required.

An example of setting the notify-operator attribute for a queue is:

pdset -c queue -x "notify-operator= \email:[email protected] email:[email protected]" \Queue2

An example of setting the results-profile attribute for a job are:

pdset -c job -x \"results-profile=‘pickup:Please staple:dave@cowboy:2:’" 2

See the HP Distributed Print Service Administration Guide forinformation on the results-profile attribute.

Time Attribute ValuesFor time attribute values, use the local time format as defined in theLC_TIME environment variable. The hour is based on a 24-hour clock.The following syntax and examples assume US English format for date.

AttributeName=”hh:mm:ss mm/dd/yy’’AttributeName=hh:mm:ss

Some time values include the date and some do not. If the date is notincluded, HPDPS uses the current date. Separate the values for hours,minutes, and seconds with colons, with no spaces. Separate the valuesfor month, day, and year with slashes, with no spaces. Enclose time withdate in single quotes and separate them with a space. Some examplesare:

pdpr -c job -x "job-print-after=18:30:00" BigJob

pdpr -c job -x "job-print-after=‘18:30:00 05/15/95’" BigJob

For time intervals, the syntax is:

AttributeName=[HH:]MM

58 Chapter 3


pdset -c queue \-x "notification-profile= \{event-identifiers=job-modified queue-state-changed \delivery-method=email \event-comment="This is a job modification or status event" \delivery-address=dave@cowboy locale=C}" SPOOL1:QUEUE1

If you change one component within the notification profile, the rest ofthe components will be set to their default values. For example, thefollowing command will set the delivery-address but the othercomponents will be set to their defaults:

pdset -c queue -x "notification-profile= \{delivery-address=tom@hope}" SPOOL1:QUEUE1

If you want to maintain the existing values, you must specify them. Youcannot use the add (+=) or the delete (-= ) operators of pdset or pdmodwhen changing the component values within a notification-profilevalue. However, you can add or delete a total value (a user) from thenotification-profile by using the += or -= operators and onlyspecifying the delivery-address component. For example, thefollowing command will add another user (value) to the previous one.

pdset -c queue \-x "notification-profile+={delivery-address=mary@cowboy}" \SPOOL1:QUEUE1

Now the notification-profile has two values:

notification-profile={event-identifiers=job-modified queue-state-changeddelivery-method=emailevent-comment="This is a job modification or status event"delivery-address=dave@cowboy locale=C}

{event-identifiers=object-deleted object-cleanedqueue-backloggeddelivery-method=emaildelivery-address=mary@cowboy locale=C}

However, the second one contains default values except for thedelivery-address . If you want values other than defaults, you mustspecify them.

Complex Attributes Using Colons . Complex attributes thatrequire colons between components are:

job-size-range-ready

job-size-range-supported

notify-operator

results-profile

Chapter 3 57


NOTE If you specify more than one value for a single-value attribute in onecommand using either the -x flag or an attribute file specified by the -Xflag, or a combination, only the last value specified for the attribute isassigned.

Multiple-Value AttributesFor multiple-valued attributes, the syntax is:

"AttributeName=AttributeValueX AttributeValueY AttributeValueZ"

where AttributeValueX, AttributeValueY, and AttributeValueZ eachdenote a separate value for the attribute. Enclose the attribute name andits values in quotes and separate the values with spaces. In the followingexample, two values are assigned to the content-orientations-supported attribute:

-x "content-orientations-supported=portrait landscape"

Complex AttributesComplex attributes have multiple values, but each value itself hasmultiple components. There are two types of complex attributes:

• those that require braces ({ } ) enclosing each value.

• those that use a colon (:) to separate components.

Complex Attributes Using Braces . The only complex attributethat requires braces is notification-profile .

The rules for using braces are as follows:

• Each value begins and ends with the brace characters ({ } ).

• Each value has a number of components.

• Each component has a name and associated values.

• The sequence in which the components are entered is not important.

• The component event-identifiers is the only component that canhave multiple values.

An example of creating a notification-profile with one value for aqueue is:

56 Chapter 3


There are likewise other attributes such as total-job-octets ,current-job-state , or job-copies-completed that are determinedand set by HPDPS.

Default Values for AttributesFor some attributes, the default value is "no value".

• When you create an object, HPDPS assigns a default value (or values,for some multi-value attributes) to each attribute. You can overridethese default values by specifying a different value using the -x and -X flags.

• The values can be changed back to their default values using thepdmod or pdset commands and specifying the attribute namefollowed by == without any attribute value.

For example, the following command sets the value assigned tocontent-orientations-supported for the physical printerPhysPrt3 back to its default value:

pdset -x "content-orientations-supported==" SUPER1:PhysPrt3

• Deleting all the values from a multi-valued attribute or deleting thevalue of a single-valued attribute sets the attribute value to thedefault values.

Syntax for Attribute ValuesThis section describes the syntax for some types of attributes and thevalues that can be assigned to them. Most attributes are either singlevalued (they can have only one value at a time) or multi-valued (theycan have multiple values). There are also some attributes identified ascomplex attributes.

Single-Value AttributesFor single-valued attributes, the syntax is:

AttributeName=AttributeValue

Use single quotes if the value includes spaces (such as the messagevalue for a notification profile). An example is:

-x "media-supported=iso-a4-white \message=`These attributes are for LogPrt2 ’ "

Chapter 3 55


Setting Attributes When an Object is CreatedA specifiable attribute can be set only when you create the object.Youcan specify an attribute with the pdcreate or the pdpr command.

NOTE The pdpr command creates a job object.

For example, the following command creates a logical printer calledLogPrt1 in the server (spooler) called SPOOL1, setting the logical printerattribute,printer-realization , to logical as well as assigning theattribute maximum-copies-supported the value of 4.

pdcreate -x "maximum-copies-supported=4 \printer-realization=logical" SPOOL1:LogPrt1

The attribute printer-realization and its value is a specifiableobject-attribute and cannot be changed. You should note that in thisexample, it is not necessary to set this attribute to logical since itwould have been set by default.

The attribute maximum-copies-supported is modifiable, however, asdescribed below.

Setting Attributes After an Object is CreatedYou can set or modify the value for any settable attribute using thepdmod command (for job and document objects only) or the pdsetcommand (for all objects, including jobs and documents).

For example, the following command sets (modifies) a new value for themaximum-copies-supported attribute from the previous example. Thenew value is 2.

pdset -x "maximum-copies-supported=2" LogPrt1

Attributes That Cannot be Specified or SetSome attributes are non-settable. For example, in the followingcommand, HPDPS uses the argument of the command to assign theprinter attribute printer-name the value LogPrt1 , and theassociated-server attribute the value SPOOL1.

pdcreate -x "maximum-copies-supported=4" SPOOL1:LogPrt1

Here, the user did not directly specify the printer-name norassociated-server attributes; HPDPS sets them from the printer andserver names indicated within the command.

54 Chapter 3


The server name is optional for:

• Commands using local job IDs as the argument.

• Commands using the printer name or the queue name; these namesmust be unique within the namespace. An exception to this is thepdcreate command where the server name is always required.

The server name is required for:

• Commands specifying an object class that resides in a supervisor,such as log .

• Object names within a spooler that are not unique within anamespace.

• The pdcreate command.

In the DCE Extended Environment, the DCE Directory Service providesthe means to name objects and to route commands to the correct object.DCE manages object names using a namespace within a cell. Objects inthe following object classes must have a unique name within thenamespace:

• Server (spoolers and supervisors)

• Printer (logical and physical)

• Queue

Objects from the other object classes, such as initial-value-job or log arecontained in servers. Two objects of such object classes can have thesame name if they are contained in two separate servers.

Setting Object-AttributesThere are three main types of object-attributes:

Specifiable An attribute whose value you can establish when theobject is created, but which cannot be subsequentlymodified.

Settable An attribute whose value can be set or modified afteran object is created, assuming the object is in anappropriate state to be modified.

Non-Settable An attribute whose value can only be determined byHPDPS.

Chapter 3 53


• If you specify more than one value for a single-value attribute in onecommand using either the -x flag or an attributes file specified by the-X flag, or a combination, the last value specified for the attribute isthe one assigned.

• When an object is created and its attribute values are not specifiedusing the -x flag or -X flag, some of the attribute values may be set toserver defaults. Refer to “Default Values for Attributes” shortly for adescription of default values.

• The values for job object-attributes and document object-attributescan be specified using initial-value-job objects and initial-value-document objects, respectively. See “Using Initial Value Objects(IVOs) to Specify Attribute Values” later for more information.

Using ArgumentsThe argument specified in a command is the name of the object thecommand is to act upon. Most commands must include an argument.

NOTE If multiple arguments are specified in one command, they must belong tothe same object class.

When the object is a server, the argument is the name of the server. Allother objects are contained in servers. For some objects, the name of itsserver must be supplied in the form ServerName:ObjectName. For otherobjects, the server name is sometimes optional. You must look at eachcommand to determine the exact format that is allowed. The followingarguments are supported by HPDPS:

LocalJobID[.DocNumber] …

GlobalJobID[.DocNumber] …

ServerName:InitialValueJobName …

ServerName:InitialValueDocumentName …

ServerName:LogName …

[ServerName:]PrinterName …

[ServerName:]QueueName …

ServerName …

When the server name is explicitly stated in a command (regardless ofwhether it is optional or required), the command is sent to that server.

52 Chapter 3


Table 3-6 Frequently Used Object-Attributes

The following rules apply for object-attributes:

• An attribute value pair for an object-attribute, like for a command-attribute, consists of an attribute followed by a value. The attributename describes the attribute, and its value specifies a value to beassigned to the attribute. For example, the attribute used to specify abanner page in a print job is job-sheets and one of its possiblevalues is job-set-start . This attribute and its value are specifiedin a text string with a -x flag as shown here:

-x "job-sheets=job-set-start"

• Object-attributes can be either single-valued (that is, they can haveonly one value at a time) or multi-valued. Multiple values must beseparated by a space. For example:

-x "orientations-supported=portrait landscape"

Attribute Value Purpose

copy-count CopyCount An integer used to specify thenumber of copies that are to beprinted. A value of 0 is not valid.

document-format Format Specifies the format of thedocument, as for example,postscript or ascii.

job-hold true

false

Specifies whether you want to putthe job in hold state.

job-name JobName Specifies a new name for a givenjob.

job-retention-period JobRetentionPeriod Specifies the period of time youwant the job retained after beingprinted before the server deletesthe job. The format is [HH]:MM.Hours are optional.

printer-name-requested [ServerName:]

PrinterName

Queries all the jobs in the queueassociated with the specifiedlogical printer.

Chapter 3 51


Otherwise, any pre-existing values for the command-attribute are nolonger available.

• If multiple values are specified for the command attribute class andthe object class of the command argument does not agree with thelast value specified, the command is rejected.

Object-Attributes The manpages contain a list of attributes for each object. The followingmanpages are available:

pd_att(5)

pd_att_document(5)

pd_att_ivdocument(5)

pd_att_ivjob(5)

pd_att_job(5)

pd_att_log(5)

pd_att_log_ptr(5)

pd_att_phy_ptr(5)

pd_att_queue(5)

pd_att_spooler(5)

pd_att_supervisor(5)

Table 3-6 lists some frequently used object-attributes supported by someof the HPDPS commands along with the purpose of these attributes.

50 Chapter 3


The following rules apply for command-attributes:

• You access and set the command-attribute values by using the -xflag. -x takes a single text string containing one or more attribute-value pairs.

• Only the command-attributes requested-attributes and classcan have multiple values.

• The command-attribute requested-attributes is made additiveby adding a + (plus sign) before the = (equal sign). For example,

-x "requested-attributes+=printer-model"

notification-delivery-method

email

message

none

To specify the methodthat you or anotherperson is to be notified ofgiven events related tothe object.

printer-name-requested PrinterName To specify a logicalprinter as the target of aprint request.

requested-attributes all

archive

brief

none

verbose

“AttributesList"

To specify the group ofattributes that you wantdisplayed for a specifiedobject class.

style line

column

To specify the format(style) in which you wantthe requested attributesdisplayed.

when after-current

after-all

now

To specify when you wantthe server to be shutdown.


Chapter 3 49


Table 3-5 Command-Attributes


attributes AttributesFileName To read in command andobject attributes from afile. When this attributeis encountered, thedesignated attributes fileis read and the contentsare inserted at thecurrent point in thecommand.

class document

initial-value-document

initial-value-job

job

log

printer

queue

server

To define the object classthat the command is tooperate on.

filter "FilterCriteria" To specify the"FilterCriteria" you wantto use in selecting a givenitem from severalpossible items.

headings true

false

To specify whether youwant headings displayed.

message "MessageText" To specify a message thatis associated with theobject being acted on.

48 Chapter 3


The end result is that the only value returned is the value forphysical-printers-ready .

• To request all three values shown in the previous example to be usedadditively, employ the += operator within the -x attribute value pair:

pdls -c server \-r logical-printers-supported,queues-supported \-x "requested-attributes+=physical-printers-ready" \SPOOL2

Command-AttributesTable 3-5, “Command-Attributes,” shows the various command-attributes and the purpose of each.

Chapter 3 47


• The first -r flag from Table 3-4 can accept multiple values for the"AttributesList" and for another value (e.g. brief ) shown for the flag.You use a comma-delineated listing with the -r flag to achieve anadditive AttributesList, meaning all values are used.

• Using both the -r flag with multiple values and the command-attribute requested-attributes in the same command may resultin a loss of additivity. Multiple -r values are additive, but the use ofthe command-attribute replaces values specified by the -r flag unlessits value is specifically requested to be additive, as shown in the lastexample in the next section.

Examples Using Command FlagsThe following examples show a few ways to use the -r flag, the -x flag,or both in the same pdls command.

• This example shows two ways to request the names of the logicalprinters and queues supported in a spooler.

pdls -c server -x "requested-attributes= \logical-printers-supported queues-supported" \SPOOL2

pdls -c server -r logical-printers-supported,\queues-supported SPOOL2

The first example uses the command attribute requested-attributes while the second example uses the -r flag whichreplaces "-x requested-attributes= ".

• In this example, the attribute values for both logical-printers-supported and queues-supported are requested with separate -rflags. As a result, the first value is overridden by the second.

pdls -c server -r logical-printers-supported \-r queues-supported SPOOL2

The end result is that the only value returned is the value forqueues-supported .

• In this example, the attribute values for both logical-printers-supported and queues-supported are requested but areoverridden by the command-attribute requested-attributesbeing entered with the -x flag.

pdls -c server \-r logical-printers-supported,queues-supported \-x "requested-attributes=physical-printers-ready" \SPOOL2

46 Chapter 3


Rules for Command FlagsThe following rules apply for flags:

• Flags that are equivalent to specifying a corresponding command-attribute or object-attribute that can have only one value areprocessed such that only the last value specified is used. This means,if these flags occur multiple times in a command, the value specifiedfor the last occurrence of the flag is used.

• You can specify multiple instances of a flag when you use the -x , -X ,or -f FileName flags.

The following example shows how the -X flag can be entered on thecommand line so that more than one attribute file can be read withinone command. The contents of the two files are added together.

pdpr -X a.dat -X b.dat File1

However, if the two files contain the same attribute, the value of thatattribute in the file read last is used.

-w after-current

after-all

now

Specifies when you want theserver to be shut down.Equivalent to specifying thecommand-attribute when.

-x "AttributeValuePairs" Applies one or more attributesand their values on thecommand line. If there are anyspaces within the attributevalue or between the attributevalue pairs, the string must beenclosed in quotes.

-X AttributesFileName Reads in command and object-attributes from a file. Refer to“Using an Attributes File” laterfor a description of attributesfiles.

Flag Value Purpose

Chapter 3 45


-r all

archive

brief

none

verbose

“AttributesList"

Specifies the group of attributesthat you want displayed for aspecified object class.Equivalent to specifying thecommand-attributerequested-attributes . Ifyou specify more than oneattribute for the -r flag,surround the attributes withdouble quotes or use commaswith no space between them.

-r JobRetentionPeriod With pddelete or pdrm ,specifies the period of time youwant the job retained by theserver before the job is deleted.Equivalent to specifying theobject-attribute job-retention-period .

-s column

line

Specifies the format (style) inwhich you want the requestedattributes displayed. Equivalentto specifying the command-attribute style .

-t JobName Specifies a new name for a givenjob. Equivalent to specifying theobject-attribute job-name .

-U Suppresses the default user-name filter.

Flag Value Purpose

44 Chapter 3


-j With pdls , displays jobattributes. With pdpause ,pauses the currently printingjob on a specified physicalprinter.

-l Create a symbolic link from thespool area to the data filesrather than copying them.

-m "MessageText" This flag and its value (a textstring) are used to specify amessage that is associated withthe object being acted on.Enclose the message in quotes.Equivalent to specifying thecommand-attribute message .

-n CopyCount This flag and its value (aninteger) are used to specify thenumber of copies that are to beprinted. A value of 0 is not valid.Equivalent to specifying theobject-attribute copy-count .

-N email

message

none

Specifies the method by whichyou or another person are to benotified of events as the job isprocessed. Equivalent tospecifying the command-attribute notification-delivery-method .

-p PrinterName With pdpr or pdq , specifies alogical printer as the target ofthe command. Equivalent tospecifying the command-attribute printer-name-requested .

Flag Value Purpose

Chapter 3 43


Table 3-4 Command Flags

Flag Value Purpose

-c document

initial-value-document

initial-value-job

job

log

printer

queue

server

Defines the object class that thecommand is to operate on.Equivalent to specifying thecommand-attribute class .

-f “FileName” With pdpr , optionally specifiesthe name of the file you want toprint. Useful for identifying fileswhose name begins with a “- ”character.

-f "FilterCriteria" With pdpr or pdq , specifies the"FilterCriteria" you want to usein selecting a given item fromseveral possible items. Thevalue "FilterCriteria" is alwaysenclosed in quotes.

-F Turns off all filtering.

-g Turns off the display ofheadings. Equivalent to thecommand-attribute headings .

-h Displays command helpinformation. Supported by allcommands and is mutuallyexclusive (cannot be used withany other flag or attribute).

42 Chapter 3


Using Command FlagsCommand flags either substitute for command- or object-attributes ormodify the way a command is processed. For example, the -c commandflag can be used instead of the class command-attribute. Many flagshave values associated with them. See Appendix A, “CommandSummary,” or the manpages for each command to determine which flagsas well as which values are supported by that command. The table in thenext section will help you determine the purpose of each flag.

The syntax using command flags is:

[ HPDPSCommand [ -Flag Value…] [ Argument] ]

Combining Attribute Value Pairs and Command FlagsYou can combine attribute value pairs and command flags. The followingexample shows the command to submit a print job for File1 , using thecontent-orientation attribute with the value of landscape and the-n command flag to request three copies.

pdpr -x "content-orientation=landscape" -n 3 File1

Table 3-4, “Command Flags,” lists all the flags and the purpose for eachflag. If the flag uses a value, the supported values are listed.

Chapter 3 41


Command SyntaxYou can enter HPDPS commands using an attribute value pair, acommand-attribute or an object-attribute and its value, with the -x flag,other command flags, or a combination of the two. More information oneach of these options follows.

Using the -x Flag with Attribute Value PairsBoth object-attributes and command-attributes have values and can beentered using the -x flag. Command-attributes modify the action ofcommands. See Table 3-5, “Command-Attributes,” for a list of command-attributes. Object-attributes are characteristics of objects. See “Object-Attributes” for more information.

When an attribute and a value are entered, the attribute is followed bythe = sign followed by the value; no space is allowed between these threeitems unless the items are enclosed in quotes. For example,class=printer and "class = printer" are equally acceptableformats. See Table 3-5, “Command-Attributes,” and Table 3-7, “HPDPSObject-Attributes,” later for more information.

The syntax for using an attribute value pair with the -x flag is:

[ HPDPSCommand [ -x AttributeValuePair…] [ Argument…] ]

where

-x precedes the attribute and its value.

AttributeValuePair is a command-attribute or object-attribute together with its value.

Argument is the object being acted upon. See“Using Arguments” later for moreinformation.

For example, to request a listing of attributes for SPOOL1, enter:

pdls -x "class=server request-attributes=all" SPOOL1

The following command yields the same results, but is entered usingcommand flags, which are described next.

pdls -c server -r all SPOOL1

40 Chapter 3

Command ReferenceHPDPS Commands

pdstartclient Used to start the HPDPS client daemon.

pdstartspl Used to create or restart an HPDPS spooler.

pdstartsuv Used to create or restart an HPDPS supervisor.

pdstopd Used to stop the HPDPS client daemon.

Command Description

Chapter 3 39


Table 3-3 HPDPS Administrator Commands

pdq Queries the status of one or more jobs in a queue.

pdresubmit Resubmits a previously submitted job (that is pending, timed-out,retained, or held) to a specified logical printer on the same ordifferent spooler.

pdrm Cancels (removes) one or more previously submitted print jobs.

Command Description

pdclean Removes all jobs from the specified server, printer, or queue.

pdcreate Creates logical printer, physical printer, queue, initial-value-job, andinitial-value-document objects.

pddcesetup Used to configure DCE information for HPDPS.

pddelete Deletes logical printer, physical printer, queue, initial-value-job,initial-value-document, server, and job objects.

pddisable Disables the specified server, printer, or queue from accepting printrequests. Logs also can be disabled.

pdenable Allows the specified server, printer, or queue to accept print requests.Logs also can be enabled.

pdgwcfg Configures HPDPS Gateway Printers in a Basic Environment.

pdpause Pauses a pending, held, or currently printing job, physical printer,server, or queue.

pdpromote Advances the specified job to the beginning of a queue. The job is thenscheduled on the next appropriate printer available.

pdresume Resumes a currently paused job, physical printer, server, or queue.

pdset Sets (or modifies) the attribute values of one or more existing objects,including jobs and documents.

pdshutdown Shuts down the specified server after all jobs have printed, after allcurrently printing jobs have printed, or immediately.

Command Description

38 Chapter 3


HPDPS CommandsThe HPDPS commands create, modify, and delete objects, and may alsoreturn status and other information about the objects. Additionally,there are commands that serve as utilities.

As a general guideline, commands can be sub-divided into thoseprimarily for users and those primarily for administrators.Administrator capability is required to run the administrator commands.Table 3-2, “HPDPS User Commands,” lists the user HPDPS commandsand Table 3-3, “HPDPS Administrator Commands,” lists theadministrator HPDPS commands. All HPDPS commands begin with pd .

You may need to be authorized to use HPDPS commands. For moreinformation on authorization, see “Authorization” in this chapter as wellas the HP Distributed Print Service Administration Guide.

NOTE For a complete description of each HPDPS command, see the appropriatemanpage. Enter:

man CommandName

The examples used in this chapter include both commands primarily forusers and those primarily for administrators. They illustrate thesyntactical features described regardless of which particular commandwas chosen for the example.

Table 3-2 HPDPS User Commands

Command Description

pdls Lists selected attribute values for objects.

pdmsg Displays the text and description of an HPDPS message.

pdmod Modifies (or sets) the attribute values of one or more previouslysubmitted jobs or documents within a job.

pdpr Creates a single print job, consisting of one or more documents, andsubmits a job to a logical printer. The printer can be specified ordefaulted.

Chapter 3 37

Command ReferenceHPDPS Object Classes vs. Objects

Naming of HPDPS ObjectsThe above system-defined object class names represent objects thatshare common features. A specific instance of one of these object classeswithin your particular printing system might be an object with a locallydefined name. For example, LogPrt1 might be the name youradministrator has given to one of your logical printers.

The following restrictions apply to the naming of HPDPS objects:

• Object names can be up to 255 characters long.

• Characters allowed in object names are uppercase A through Z,lowercase a through z, digits 0 through 9, special characters - (dash)and _ (underscore).

• Logical printer names longer than 14 characters cannot be used withLP spooler commands, such as lp and lpstat .

queue Manages a collection of jobs that are waiting to beprinted. A print queue receives jobs from one or morelogical printers and schedules and sends the jobs tophysical printers.

server (spooler) Represents the server that manages the validation,routing, notification, logging, and scheduling of jobs.The spooler applies specified defaults to print jobs,validates that jobs can be printed using the printerson the network, and schedules jobs from queues tophysical printers.

server (supervisor) Represents the server that manages and controls thephysical printers that handle the printing of jobs. Thesupervisor receives print jobs from the spooler, directsjobs to the physical printer, reports errors to thespooler and reports job status to the user.

Object Class Name Purpose

36 Chapter 3

Command ReferenceHPDPS Object Classes vs. Objects

HPDPS Object Classes vs. ObjectsObjects have associated attributes that provide information about them.Objects are grouped into classes. An object class contains objects thatshare a common definition and common properties, operations, andbehavior. The object classes printer and server are sub-divided asshown in Table 3-1; however, only the basic class can be used in acommand.

Table 3-1, “HPDPS Object Classes,” lists the object classes supported byHPDPS.

Table 3-1 HPDPS Object Classes

Object Class Name Purpose

document Represents a grouping of data within a job.

initial-value-document Represents default attribute values for a documentwithin a job.

initial-value-job Represents default attribute values for a job.

job Represents a request to print one or more documentstogether in one printing session.

log Represents a collection of messages or messagesegments added to a file for accounting or datacollection purposes. Two types of logs are used: errorand trace.

printer (logical) Represents an abstract entity that a person specifiesto indicate where a job is to be printed as well as thecharacteristics of the job. The logical printer providesrestrictions and defaulting for the jobs. It verifies thatthere are associated physical printers capable ofhandling the jobs. Once the job is verified, it is sent toan associated print queue.

printer (physical) Represents the printer device that is to be used toprint the job. It is not the actual physical printerdevice. It is a software representation of the featuresand capabilities of the actual printer hardware device.

Chapter 3 35

Command Reference

3 Command Reference

HP Distributed Print Service enables you to send a file to print on aphysical printer device. HPDPS performs the management and printingof documents by means of objects, such as a printers, jobs, or printqueues. HPDPS commands act on these objects. Both the commands andthe objects are influenced by the attributes they possess. This chapterexplains how to construct syntactically correct HPDPS commands.

34 Chapter 2

Basic Printing TasksDeleting HPDPS Print Jobs

Deleting HPDPS Print JobsUse the pdrm command to delete a job you have submitted. You identifythe job that you want to delete by its local job identifier.

To obtain your local job identifier when you submit a job, type:

pdpr -r brief FileName

To delete the job whose local job identifier is 15 , enter:

pdrm 15

NOTE If the job you want to delete is currently printing, you may not be able todelete it.

To delete a job submitted by another user, you must use its global jobidentifier; you must be authorized to do this. See “Job and DocumentIdentifiers” in Chapter 3 for more information.

Chapter 2 33

Basic Printing TasksDetermining Which Printer Device Printed the Job

Determining Which Printer DevicePrinted the JobWhen you submit a job to a logical printer, any of the logical printer'sassociated physical printers that support all of the job and documentattributes may print the job. When the printer finishes printing your job,HPDPS can send you a notification message and display the name of thephysical printer on which your job was printed.

You may be able to determine the location of that physical printer byquerying its printer-locations attribute. For example, suppose yousubmitted a job and received notification that it completed on physicalprinter PhysPrt1 . You can use the following command to attempt todisplay the location of the printer device associated with that physicalprinter:

pdls -c printer -r "printer-locations" PhysPrt1

If your administrator has kept the optional printer-locationsattribute up-to-date, the text string will accurately tell you where theprinter device is located. For example, HPDPS might display a textstring describing the location of the printer device:

PhysPrt1: printer-locations = Building 21

32 Chapter 2

Basic Printing TasksDetermining the Status of Your Job

NOTE Your administrator may have set up your system with multiple logicalprinters sending jobs to the same queue. If you have submitted jobs tomore than one of the logical printers supporting the same queue, HPDPSdisplays status information for all of your jobs in the queue (as shown inthe preceding example) regardless of which logical printer the job wassubmitted to.

Chapter 2 31


Current State Shows the status of your job. Theinformation in this example showsthat the job is pending (in the queue).

Printer Requested Shows the name of the logical printerto which the job has been submitted.

Requesting Status Information afterSubmitting the JobTo display status information about your job after you have submitted it,enter the pdq command and identify the logical printer to which yousubmitted your job. The command then displays status informationabout all the jobs (submitted by you) in the queue associated with thelogical printer to which you submitted your job. The following examplesshow how you can request status information after submitting a job.

To request status information about jobs you submitted to your defaultlogical printer, enter:

pdq

To request status information about jobs you submitted to logical printerLogPrt4 , enter:

pdq -p LogPrt4

HPDPS displays information similar to the following about all your jobsin the queue associated with the logical printer you specified.

Current Intervening Printer PrinterJob ID Name State Jobs Requested Assigned--- --------------- ---- ---------- ----------- --------- --------13 spl4:1104221000 File1 processing 0 LogPrt4 PhysPrt114 spl4:1105226030 JobA pending 1 LogPrt415 spl4:1133000058 MyJob pending 2 LogPrt2

In the first job listed, the local job identifier is 13 and the global jobidentifier is spl4:1104221000 ; the server name is spl4 . File1 is thejob name and there are no jobs ahead of it in the queue. Logical printerLogPrt4 has assigned your job to physical printer PhysPrt1 . HPDPS isprocessing the job, as indicated by Current State .

30 Chapter 2


Determining the Status of Your JobYou can request status information about your job when you submit thejob or after you submit the job.

Requesting Status Information WhenSubmitting a JobUse the optional -r flag with the pdpr command to have HPDPS displaystatus information about your job when it is accepted. This flag valuereturns a listing of key job attributes and their values. The followingexample shows how to request brief status information when you submita job.

To submit the file File1 to the default logical printer and receive briefstatus information, enter:

pdpr -r brief File1

HPDPS displays information similar to the following about your job:

Current PrinterJob ID Name State Requested--- ------------- ---- ---------- ---------8 spl5:075410002 File1 pending LogPrt1

where:

Job Is the local job identifier for your job,which you can use in HPDPScommands to refer to your job.Others, such as administrators, mustuse the global job identifier (see IDbelow) when referring to your job.

ID Is the global job identifier for yourjob. The global job identifier is thenumber by which others, such asadministrators, can refer to your job.

Name Is the name of the job. If you do notspecify the job-name attribute,HPDPS uses the name of the firstdocument file in your job as the jobname.

Chapter 2 29

Basic Printing TasksSpecifying Attributes for HPDPS Print Jobs

pdpr -x “document-type=file-reference” myref

submits the reference file, myref , and prints each document listedwithin it. Each document within myref must be on a separate line.

Specifying a Medium for a JobTo specify a particular medium to print, you can specify a value forinput-tray-select , such as top or middle . If you do not specify avalue for this document attribute, HPDPS uses the default-mediumattribute value, such as iso-a4-white or iso-a4-transparent . Ifthat is not defined, then HPDPS uses the value identified for thedefault-input-tray , such as top or middle .

Specifying the Number of PagesYou can include information about the size of a document within yourjob. This may be helpful to you or an HPDPS administrator to helpmanage job flow.

For example, if your job file File3 is about 50 pages long, you mightenter the command:

pdpr -x “page-count=50” File3

When submitting a job consisting of two files, you can specify the numberof pages for each document:

pdpr -x “page-count=40” FileA -x “page-count=70” FileB

28 Chapter 2


Using the pdpr CommandTo print multiple documents in one job, list each of the document filenames as arguments of the pdpr command. All document files in the jobmust have the same attributes or HPDPS will reject the job. Forexample, they must have the same data format such as ASCII orPostScript. Specify any document attributes, such as sides=2 ornumber-up=4 before the list of file names.

The following examples show how you can specify multiple files with asingle pdpr command.

To submit the files File1 and File2 to the default logical printer, enter:

pdpr File1 File2

To submit the documents File1 and File2 to the default logical printerand specify three copies of each document with duplexed printing, enter:

pdpr -x "copy-count=3 sides=2" File1 File2

In the above example, HPDPS prints three copies of File1 followed bythree of File2 . As an alternative, to print multiple copies of the samejob, you can use the job-copies component of the results-profilejob attribute. So, to submit a job that prints a single copy of File3 andFile4 and then prints the job again, enter:

pdpr -x "results-profile=:::2:" File3 File4

Here, results-profile is a complex attribute, that is, one that hasmultiple values. It contains the following components:

• delivery-method

• results-set-comment

• delivery-address

• job-copies

• output-bin

In the example above, the components are separated by colons. See“Complex Attributes Using Colons” in Chapter 3 for rules on colonsyntax. See HP Distributed Print Service Administration Guide or themanpage pd_att_job(5) for details on results-profile .

Using a Reference FileYou can use a reference file that contains a list of the documents youwant to print with the pdpr command. For example,

Chapter 2 27


you do not specify the content-orientation attribute, HPDPS printsyour job in portrait orientation. To submit the file File1 to the defaultlogical printer and specify landscape orientation, enter:

pdpr -x "content-orientation=landscape" File1

Specifying the Document Format for a JobUse -x document-format= Format with the pdpr command to specifythe document format of your job. HPDPS accepts jobs in differentdocument formats such as PostScript, PCL, and ASCII. If you do notspecify the document format of the job when you submit the printrequest, HPDPS automatically tries to determine the format and processthe request accordingly. This saves you time when entering printcommands from the command line. It is also an advantage if you are notsure of the data format of the job. There can be times when you need toexplicitly tell HPDPS the document format of your job. If HPDPS cannotdetermine the document format, it treats the file as ASCII data and theprinted results may not be acceptable. In such cases, you should specifythe document format.

For example, to submit file PSFile2 to the default logical printer andspecify the document format PostScript, enter:

pdpr -x "document-format=ps" PSFile2

Specifying Number of Images on a PageUse -x number-up= NumberOfImages to specify the number of imageson a page. The value for NumberOfImages can be 1, 2, 3, or 4.

For example, to print File1 with an image displaying on each half of apage for a total of two images per page, enter:

pdpr -x "number-up=2" File1

Printing Multiple Documents in a Single JobTo print jobs that contain more than one document, you can eitherspecify the name of each document with the pdpr command, or, you cancreate a reference file that lists each document.

26 Chapter 2


Some attributes have additional flags that can be used to substitute forthe attribute name. For example, to print three copies of File1 you canalso use -n CopyCount flag and its value:

pdpr -n 3 File1

Refer to Chapter 3, “Command Reference” for a complete description ofall flags and more information on attribute value pairs.

NOTE The default attribute values described in the following tasks are thevalues provided with HPDPS. Be aware that these defaults may havebeen modified by your print administrator for your distributed printenvironment.

Specifying the Number of CopiesUse -n CopyCount or -x copy-count= CopyCount with the pdprcommand to specify the number of document copies in a job that youwant to print. If you do not specify a copy count for your job, HPDPSprints the default number of copies. For examples, see the previoussection.

Specifying Two-Sided Print JobsUse -x sides=2 with the pdpr command to specify two-sided(duplexed) printing for your job. Duplexed jobs print on both sides of thepaper such that the top of each side is at the same edge of the paper. Ifyou do not specify the sides attribute, HPDPS applies the default valuefor this attribute.

To submit file File1 to the default logical printer and specify duplexedprinting, enter:

pdpr -x "sides=2" File1

Specifying the Page OrientationUse -x content-orientation= OrientationValue with the pdprcommand to specify the page orientation for your job. The two mostcommon page orientations are portrait and landscape. Portraitorientation has the short edges of the printed page as the top and bottomwith the long edges as the sides. Landscape orientation rotates the page90 degrees so that the long edges of the page are at the top and bottom. If

Chapter 2 25


Specifying Attributes for HPDPS PrintJobsQuite often, the characteristics, or attributes, of print jobs differ from jobto job. You may have a particularly large job that requires printing ontwo sides. You may have other jobs that require rotation of the printingorientation or multiple copies. You may also have jobs that require acombination of these things. You can specify attributes for your jobs anddocuments by specifying an attribute and a value, referred to as anattribute value pair. For a complete list of attributes, see themanpages for attributes that belong to each HPDPS object. See “GettingHelp for HPDPS Commands” earlier for a list of these manpages orenter:

man pd_att

Examples of some of these attributes are:

• copy-count (number of document copies)

• sides (double or single-sided copies)

• content-orientation (landscape or portrait layout)

• document-format (type of format)

• number-up (number of images on a page)

• results-profile (includes number of copies of a job)

• input-tray-select (specifying which printer tray to use)

To enter an attribute value pair, you use the -x attribute flag. Forexample, to print three copies of File1 , enter:

pdpr -x "copy-count=3" File1

If you want to specify several attributes and their values, the followingexample illustrates how:

pdpr -x "copy-count=3 sides=2" File1

The above command specifies three copies with two-sided printing.

NOTE For consistency in examples, double quotation marks are shown around asingle attribute and value pair, even though they are required only formultiple attribute and value pairs.

24 Chapter 2

Basic Printing TasksSubmitting Jobs to an HPDPS Printer

Submitting Jobs to an HPDPS PrinterWhen you or your print administrator have configured one or moreHPDPS logical printers, you can submit jobs to them:

• Using “drag and drop” printing from CDE or HP VUE

• By entering commands at the command line, such as pdpr

• From an application

Printing to a Default Logical PrinterTo submit a job, you can use the pdpr command. If a default logicalprinter has been set in your PDPRINTER environment variable and youwant to use it, enter the pdpr command without specifying a logicalprinter.

For example, to submit the file File1 to your default logical printer,enter:

pdpr File1

Printing to a Specific Logical PrinterTo send a job to a specific logical printer use -p PrinterName with thepdpr command. Requesting a specific logical printer can be useful if yourdistributed print environment has many available logical printers or hasdefined logical printers based on the types of print jobs that the logicalprinters accept. Examples of logical printers defined by types of jobscould include those that only accept large jobs, those that are specificallyfor PostScript jobs, or those that only support single-sided jobs. Tosubmit the file, File1, to the logical printer LogPrt2 , enter:

pdpr -p LogPrt2 File1

Contact your administrator for the names of the logical printers specificto your installation, or use the pdls command to list the names of yourconfigured logical printers.

If you submit a job to a logical printer that has no associated physicalprinters capable of handling your job, HPDPS rejects the job and youreceive an error message.

Chapter 2 23

Basic Printing TasksDefining a Default Logical Printer

Defining a Default Logical PrinterEvery job in HPDPS is submitted to a logical printer. If you submit all ormost of your jobs to the same logical printer, defining a default logicalprinter allows you to issue HPDPS printing commands without overtlyspecifying the logical printer.

You specify the default logical printer using the environment variablePDPRINTER in your .profile or .login file. (This is equivalent tospecifying LPDEST when you use the LP spooler.) Use the followingprocedure to set or change your default logical printer:

1. If you use the POSIX or Korn shell, insert or modify the following linein your .profile file in your home directory:

export PDPRINTER= PrinterName

or, if you use the C shell, insert or modify the following line in your.login file in your home directory:

setenv PDPRINTER PrinterName

where PrinterName is the name of the logical printer you want to setas your default.

2. Save the change in plain text format and exit from the editor.

3. To make the change to the .profile file take effect, enter:

. .profile

or, to make the change to the .login file take effect, enter:

source .login

4. To verify the setting, enter:

echo $PDPRINTER

The logical printer name you entered is displayed.

Any print jobs you submit without specifying a logical printer will goto this logical printer. You can submit jobs to the default logicalprinter or request that a specific logical printer handle your job, asdescribed next.

22 Chapter 2

Basic Printing TasksGetting Help for HPDPS Commands

The following HPDPS attribute manpages are available. These list validattributes for a given object:

pd_att(5) pd_att_document(5)

pd_att_ivdocument(5) pd_att_ivjob(5)

pd_att_job(5) pd_att_log(5)

pd_att_log_ptr(5) pd_att_phy_ptr(5)

pd_att_queue(5) pd_att_spooler(5)

pd_att_supervisor(5)

Chapter 2 21

Basic Printing TasksGetting Help for HPDPS Commands

Getting Help for HPDPS CommandsFor quick help about an HPDPS command and its flags, enter acommand followed by the -h flag. For example, for information on thepdpr command used to print jobs, enter:

pdpr -h

You can also use the HP-UX man command to display help informationabout HPDPS commands. For example:

man pdpr

The manpages contain examples of all the HPDPS commands. Thefollowing HPDPS command and their manpages are available:

pdclean(1) pdcreate(1)

pddcesetup(1M) pddelete(1)

pddisable(1) pdenable(1)

pdls(1) pdmod(1)

pdmsg(1) pdpause(1)

pdpr(1) pdpromote(1)

pdq(1) pdresubmit(1)

pdresume(1) pdrm(1)

pdset(1)(1) pdshutdown(1)

pdstartclient(1M) pdstartspl(1M)

pdstartsuv(1M) pdstopd(1M)

pdgwcfg(1M)

20 Chapter 2

Basic Printing TasksUsing LP Spooler Commands

Using LP Spooler CommandsWith HPDPS, you can continue to submit your usual HP-UX LinePrinter Spooler (LP spooler) commands. HPDPS translates thesecommands as needed and provides, as closely as possible, the samefunctionality. However, there are small differences between the waysthat LP spooler-managed printers and HPDPS-managed printers handlesome commands. You may also see differences in the informationreturned from a query command. For more detailed information, seeAppendix B, “LP Spooler Commands Translated to HPDPS Commands”.

All printers configured with HPDPS on a local system are visibleimmediately to the LP spooler without any additional configuration.Remotely located HPDPS printers will also be visible to the LP spooler ifrunning in the DCE Extended Environment.

Chapter 2 19

Basic Printing Tasks

2 Basic Printing Tasks

This chapter contains information to help you do the following tasks:

• use LP spooler commands

• get help for HPDPS commands

• set up a default logical printer

• submit a print job

• specify attributes for HPDPS jobs

• determine the status of your job

• determine which printer device printed a job

• delete print jobs

For complete information about all the HPDPS commands and theirattributes, refer to Chapter 3, “Command Reference”.

18 Chapter 1

What Is HP Distributed Print Service?HPDPS Terminology

Chapter 1 17

What Is HP Distributed Print Service?HPDPS Terminology

HPDPS TerminologyAll jobs are printed on hardware called printers or printer devices.Within your printing system, there are likely to be many printer deviceswith each device having its own capabilities. For example, some printerdevices can print on both sides of the page, some can print PostScriptdocuments, and so on. HPDPS internally represents each printer deviceand its capabilities as a physical printer. Each physical printer withinan HPDPS environment has an associated print queue and logicalprinter, defined below.

When you submit a job for printing, you submit it to a logical printer.HPDPS uses a logical printer to check (validate) the printerrequirements of a job and determine if there is a physical printer capableof handling the job requirements before the job is accepted. WhenHPDPS accepts the job, the logical printer provides some default valuesfor the job and places the job in a print queue where the job waits untilan appropriate physical printer is available to print the job.

HPDPS manages and prints jobs by using objects such as printers, jobs,and queues. Each HPDPS object has attributes and associated attributevalues. For example, the attributes of a job define the printerrequirements of the job, and the attributes of a physical printer definethe capabilities of the printer device it represents. Using particularattribute values, HPDPS can determine which printer device is capableof printing the job.

The logical printers, queues and physical printers to which you haveaccess are all managed by a server. The HPDPS environment has twotypes of servers: the spooler and the supervisor. The HPDPS spooler isthe server that manages the logical printers. The HPDPS supervisor isthe server that controls the physical printers that print the job.

Each HPDPS command described in this book acts on one or more ofHPDPS objects. These commands enable you to submit, modify andremove jobs. They also enable you to query the status and attributes ofyour jobs and all the other objects in your HPDPS environment.

If HPDPS uses Distributed Computing Environment (DCE) services, theenvironment is called a DCE Extended Environment; if DCE servicesare not used, then HPDPS operates in a Basic Environment. This hasimplications for how your print system is set up. See the HP DistributedPrint Service Administration Guide for more information.

16 Chapter 1

What Is HP Distributed Print Service?What Functionality Does HPDPS Provide?

What Functionality Does HPDPSProvide?You can query a job’s status and receive messages telling you how yourjob is progressing.

HPDPS will validate your job, ensuring that there are printers capable ofprinting it.

When you submit a job, you can indicate specific characteristics orattributes for your job and the documents in your job. If you need to alterthese attributes, you can modify the job at any time until the job beginsprinting. For example, suppose you submit a job and then realize youneed multiple copies or two-sided output. As long as the job is stillwaiting to print, you can modify the request.

If the printers become too busy or inoperable, you can move your job toanother printer without reconstructing the job.

You can select which job-related messages you want to receive. Forexample, if your printer is located within your work area, you may notwant messages related to problems with the printer but you may want toknow if your job is cancelled by the administrator before it gets to theprinter. If you are sending a high-priority job to a printer that is notlocated near you, you may want to get detailed information about anysignificant happenings related to the job. In addition, you can route somejob messages to other interested users.

Chapter 1 15

What Is HP Distributed Print Service?What Are the Advantages of Using HPDPS?

You Receive Notification of Job Progress orProblemsAfter your job is accepted by HPDPS, it waits in a queue until a physicalprinter becomes available to print the job. While the job is waiting in thequeue and then while it is printing, you can receive messages thatindicate its progress or any problems that occur. For example, you can benotified when the job finishes printing.

You Can Receive Improved AdministrativeSupportHPDPS provides tools for managing printers and jobs that improve theability of your administrator to meet your printing needs. Theadministrator can configure the distributed print environment and setup job defaults according to your needs while also meeting the needs ofother groups of users. Problems in the print system are reported to theappropriate personnel immediately so that an administrator cananticipate or respond to a problem, often before you are even aware of it.If your job gets delayed because of a large demand for a printer, youradministrator can re-route or promote your job so that it will print morequickly.

14 Chapter 1

What Is HP Distributed Print Service?What Are the Advantages of Using HPDPS?

What Are the Advantages of UsingHPDPS?

You Will Not Have to Start from Scratch toLearn How to Print JobsYou may not even be aware that you are using HPDPS-managedprinters. To send jobs to HPDPS printers, you can use the samecommands, applications, and “drag and drop” actions that you are usingtoday. All you do is just specify a printer configured as an HPDPS printeras the destination for your job.

You Can Access Many Kinds of PrintersYou may currently be using desktop PostScript printers,network-attached printers, and host-attached production printers toprint from your applications. You may be using different print commandsor menus to access each of these printers and may get involved in somecomplicated setup procedures to gain access to the printers you need.With HPDPS, you can access the printers in your network withouthaving to know where the printers are located, which data formats theyaccept, or to which print servers the printers are attached.

Your Print Jobs Are ValidatedSubmitting your job to an HPDPS-managed “logical” printer gives youmore power and flexibility than sending your job to a specific hardwaredevice. When you submit a job to a logical printer, HPDPS validates thejob before accepting it to ensure that a physical printer will be able toprint the job correctly. (More on the distinction between a logical printerand a physical printer shortly.) You don't need to be an expert on dataformats or printer capabilities; HPDPS directs your job to a printercapable of successfully completing your job, if one exists, or rejects yourjob, if one doesn't exist. You do not have to wait until your job is printed,possibly incorrectly, to find out whether the printer can accept aparticular data format or if it can print double-sided jobs (duplex).

Chapter 1 13

What Is HP Distributed Print Service?

1 What Is HP Distributed PrintService?

HP Distributed Print Service (HPDPS or DPS) is a product thatfacilitates and simplifies printing in a network environment. It allowsyou to use systems, printers, and applications from a variety of vendorsand gives your print administrator the tools to serve your needseffectively.

12

11

• Double quotation marks, " " , surround text strings that containspaces, such as:

-m "Down for maintenance"

• Single quotation marks, ' ' , surround a text string that containsspaces when the text string is imbedded in a statement alreadyenclosed 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-profileattribute. An example is:

-x "notification-profile={delivery-method=electronic-mail}"

• Double ampersand, &&, means "and" within a command. An exampleis:

pdls -U -f "user-name=*fljones && \printer-name-requested==LogPrt1" Spool1:

• Double vertical bar, || , means "or" within a command. An example is:

pdls -U -r brief,job-state-reasons -s column \-f "current-job-state==retained \

|| current-job-state==timed-out" \Spool2:

• Asterisks and equal signs are used to match strings. For example:

"job owner=*Jones" initial string match

"job-owner*=*one" any substring match

"job-owner*=nes" final string match

Using Abbreviationsfor Attribute Namesand Values

In many cases, you can abbreviate attribute names and values by usingthe first letter of each word in the name or value. For example, you canuse the abbreviation s-m-s for the start-message-supportedattribute, t for the true value, and specify the attribute and value pairas s-m-s=t .

However, in some cases specifying only the first letter in each word canbe ambiguous, as for the attributes job-owner and job-originator .In these cases, specify enough of the name so that is unique, as in j-owand j-or . If the values are ambiguous, HPDPS rejects the command andyou receive an error message. Use abbreviated attribute names andvalues as appropriate.

10

• Brackets, [ ] , around values indicate that they are optional. Here,they mean that you do not have to enter any of the available pdmodflags with the pdmod command.

• Braces, { } , around values indicate required items that you mustsupply with the command. Here, they mean that you must entereither 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 oneof the values with the command. Here, it means that when you issuethe pdmod command, you can specify either a LocalJobId or aGlobalJobId, but not both.

• An ellipsis, …, indicates that you can supply more than oneoccurrence of a particular type of value with the command. Here, itmeans that you can supply more than one local job identifier value ormore than one global job identifier value with the pdmod command.

Special Characters inSyntax

Some special characters are included in commands. When colons, dashes,the equals sign, double quotation marks, single quotation marks, andbraces are shown in command syntax notation, include them when youissue the command. These special characters have the followingmeanings:

• A colon, : , separates related values. For example:

pdmod -x "sides=2" Spool12:1011230045

Spool12:1011230045 is a global job identifier on the Spool12server.

• A dash, - , always precedes a flag. For example, -x .

• The equals sign, =, separates attribute and value pairs. For example:

pdmod -x "sides=2" Spool12:1011230045

means that 2 is the value assigned to the sides attribute.

• Double quotation marks, " " , surround multiple attribute and valuepairs, such as:

-x "sides=2 content-orientation=portrait"

For consistency, double quotation marks also are shown around singleattribute and value pairs in all examples, although they are notrequired.

9

Conventions Used in this ManualThis manual uses the following typographic conventions:

User input Text that must be entered at the command line exactlyas shown, such as

pdpr -x “page-count=50” File3

Computer Indicates commands or command segments, flags,attributes, files, directories, and other items whosenames are predefined by the system, such as pdls andnotification-delivery-method .

Also shows text that is displayed as output on yourscreen or is included within a particular file, such as

# This is a line in my attributes file

Italics Indicates a parameter or argument that you mustreplace with the actual value, such as ServerName.

Also indicates a manpage reference.

Bold Indicates words defined for the first time.

Also indicates a default value for a flag.

Syntax Notation Command syntax notation uses symbols to indicate specific conditions.When issuing an HPDPS command, do not actually enter the followingsymbols at the command line, unless specifically instructed to do so:

Brackets [ ]

Braces { }

Bar |

Ellipsis …

These symbols have the following meanings, as illustrated using thefollowing sample syntax statement:

pdmod [ Flags]{ LocalJobId … | GlobalJobId …}

8

Contents

Contents

7

Time Attribute Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Attribute Values for Range and Dimensions . . . . . . . . . . . . . . . . . . .60

Requesting Attribute Values from Objects . . . . . . . . . . . . . . . . . . . . . .60Values for requested-attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Formatting the Display of Attribute Values . . . . . . . . . . . . . . . . . . .67

Headings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Using Initial Value Objects (IVOs) to Specify Attribute Values . . . . .70

Using an Attributes File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Reading in the Attributes File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Job and Document Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Specific Documents within Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Additional Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Global Character (Wildcard) Support . . . . . . . . . . . . . . . . . . . . . . . . . .79Abbreviations for Attributes and Values. . . . . . . . . . . . . . . . . . . . . . . .79Redirecting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

A. Command Summary

HPDPS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

B. LP Spooler Commands Translated to HPDPS Commands

LP Spooler Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

6

Contents

Determining the Status of Your Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Requesting Status Information When Submitting a Job . . . . . . . . . . 30Requesting Status Information after Submitting the Job . . . . . . . . . 31

Determining Which Printer Device Printed the Job . . . . . . . . . . . . . . . 33

Deleting HPDPS Print Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3. Command Reference

HPDPS Object Classes vs. Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Naming of HPDPS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

HPDPS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Using the -x Flag with Attribute Value Pairs . . . . . . . . . . . . . . . . . . . 41Using Command Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Combining Attribute Value Pairs and Command Flags . . . . . . . . . 42Rules for Command Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Examples Using Command Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Command-Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Object-Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Using Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Setting Object-Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Setting Attributes When an Object is Created . . . . . . . . . . . . . . . . 55Setting Attributes After an Object is Created . . . . . . . . . . . . . . . . . 55Attributes That Cannot be Specified or Set . . . . . . . . . . . . . . . . . . . 55

Default Values for Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Syntax for Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Single-Value Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Multiple-Value Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Complex Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Complex Attributes Using Braces . . . . . . . . . . . . . . . . . . . . . . . . . 57Complex Attributes Using Colons . . . . . . . . . . . . . . . . . . . . . . . . . 58

Contents

5

1. What Is HP Distributed Print Service?

What Are the Advantages of Using HPDPS?. . . . . . . . . . . . . . . . . . . . . .14You Will Not Have to Start from Scratch to Learn How to Print Jobs .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14You Can Access Many Kinds of Printers . . . . . . . . . . . . . . . . . . . . . . . .14Your Print Jobs Are Validated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14You Receive Notification of Job Progress or Problems . . . . . . . . . . . . .15You Can Receive Improved Administrative Support . . . . . . . . . . . . . .15

What Functionality Does HPDPS Provide? . . . . . . . . . . . . . . . . . . . . . . .16

HPDPS Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

2. Basic Printing Tasks

Using LP Spooler Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Getting Help for HPDPS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Defining a Default Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Submitting Jobs to an HPDPS Printer. . . . . . . . . . . . . . . . . . . . . . . . . . .24Printing to a Default Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . .24Printing to a Specific Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . .24

Specifying Attributes for HPDPS Print Jobs . . . . . . . . . . . . . . . . . . . . . .25Specifying the Number of Copies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Specifying Two-Sided Print Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Specifying the Page Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Specifying the Document Format for a Job. . . . . . . . . . . . . . . . . . . . . .27Specifying Number of Images on a Page . . . . . . . . . . . . . . . . . . . . . . . .27Printing Multiple Documents in a Single Job. . . . . . . . . . . . . . . . . . . .27

Using the pdpr Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Using a Reference File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Specifying a Medium for a Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Specifying the Number of Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

4

3

This software is based in part on the Fourth Berkeley SoftwareDistribution under license from the Regents of the University ofCalifornia.

©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 OpenGroup.

X Window System is a trademark of the Massachusetts Institute ofTechnology.

MS-DOS and Microsoft are U.S. registered trademarks of MicrosoftCorporation.

OSF/Motif is a trademark of the Open Software Foundation, Inc. in theU.S. and other countries.

2

Legal NoticesThe information in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to thismanual, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose. Hewlett-Packardshall not be held liable for errors contained herein or direct, indirect,special, incidental or consequential damages in connection with thefurnishing, performance, or use of this material.

Warranty. A copy of the specific warranty terms applicable to yourHewlett-Packard product and replacement parts can be obtained fromyour local Sales and Service Office.

Restricted Rights Legend. Use, duplication or disclosure by the U.S.Government is subject to restrictions as set forth in subparagraph (c) (1)(ii) of the Rights in Technical Data and Computer Software clause atDFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and(c) (2) of the Commercial Computer Software Restricted Rights clause atFAR 52.227-19 for other agencies.

HEWLETT-PACKARD COMPANY3000 Hanover StreetPalo Alto, California 94304U.S.A.

Use of this manual and flexible disk(s) or tape cartridge(s) supplied forthis pack is restricted to this product only. Additional copies of theprograms may be made for security and back-up purposes only. Resale ofthe programs in their present form or with alterations, is expresslyprohibited.

Copyright Notices. ©copyright 1983-97 Hewlett-Packard Company, allrights reserved.

Reproduction, adaptation, or translation of this document without priorwritten permission is prohibited, except as allowed under the copyrightlaws.

©copyright 1979, 1980, 1983, 1985-93 Regents of the University ofCalifornia

HP Distributed Print ServiceUser’s Guide

HP 9000 Computers

B2355-90156

E1097

Printed in: U.S.A.

© Copyright 1997, Hewlett-Packard Company.