Command Syntax

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

Using the -x Flag with Attribute Value Pairs

Both object-attributes and command-attributes have values and can be entered using the -x flag. Command-attributes modify the action of commands. 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 by the = sign followed by the value; no space is allowed between these three items unless the items are enclosed in quotes. For example, class=printer and "class = printer" are equally acceptable formats. See Table 3-5 “Command-Attributes ” and Table 3-7 “HPDPS Object-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 more information.

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 using command flags, which are described next.

pdls -c server -r all SPOOL1

Using Command Flags

Command flags either substitute for command- or object-attributes or modify the way a command is processed. For example, the -c command flag can be used instead of the class command-attribute. Many flags have values associated with them. See Appendix A “Command Summary ” or the manpages for each command to determine which flags as well as which values are supported by that command. The table in the next 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 Flags

You can combine attribute value pairs and command flags. The following example shows the command to submit a print job for File1, using the content-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 each flag. If the flag uses a value, the supported values are listed.

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 the command is to operate on. Equivalent to specifying the command-attribute `class`.
`-f`	"`FileName`"	With `pdpr`, optionally specifies the name of the file you want to print. Useful for identifying files whose name begins with a "`-`" character.
`-f`	"`FilterCriteria`"	With `pdpr` or `pdq`, specifies the "`FilterCriteria`" you want to use in selecting a given item from several possible items. The value "`FilterCriteria`" is always enclosed in quotes.
`-F`		Turns off all filtering.
`-g`		Turns off the display of headings. Equivalent to the command-attribute `headings`.
`-h`		Displays command help information. Supported by all commands and is mutually exclusive (cannot be used with any other flag or attribute).
`-j`		With `pdls`, displays job attributes. With `pdpause`, pauses the currently printing job on a specified physical printer.
`-l`		Create a symbolic link from the spool area to the data files rather than copying them.
`-m`	"`MessageText`"	This flag and its value (a text string) are used to specify a message that is associated with the object being acted on. Enclose the message in quotes. Equivalent to specifying the command-attribute `message`.
`-n`	`CopyCount`	This flag and its value (an integer) are used to specify the number of copies that are to be printed. A value of 0 is not valid. Equivalent to specifying the object-attribute `copy-count`.
`-N`	`email` `message` `none`	Specifies the method by which you or another person are to be notified of events as the job is processed. Equivalent to specifying the command-attribute `notification-delivery-method`.
`-p`	`PrinterName`	With `pdpr` or `pdq`, specifies a logical printer as the target of the command. Equivalent to specifying the command-attribute `printer-name-requested`.
`-r`	`all` `archive` `brief` `none` `verbose` `"AttributesList`"	Specifies the group of attributes that you want displayed for a specified object class. Equivalent to specifying the command-attribute `requested-attributes`. If you specify more than one attribute for the `-r` flag, surround the attributes with double quotes or use commas with no space between them.
`-r`	`JobRetentionPeriod`	With `pddelete` or `pdrm`, specifies the period of time you want the job retained by the server before the job is deleted. Equivalent to specifying the object-attribute `job-retention-period`.
`-s`	`column` `line`	Specifies the format (style) in which you want the requested attributes displayed. Equivalent to specifying the command-attribute `style`.
`-t`	`JobName`	Specifies a new name for a given job. Equivalent to specifying the object-attribute `job-name`.
`-U`		Suppresses the default user-name filter.
`-w`	`after-current` `after-all` `now`	Specifies when you want the server to be shut down. Equivalent to specifying the command-attribute `when`.
`-x`	"`AttributeValuePairs`"	Applies one or more attributes and their values on the command line. If there are any spaces within the attribute value or between the attribute value pairs, the string must be enclosed in quotes.
`-X`	`AttributesFileName`	Reads in command and object-attributes from a file. Refer to “Using an Attributes File ” later for a description of attributes files.

Rules for Command Flags

The following rules apply for flags:

Flags that are equivalent to specifying a corresponding command-attribute or object-attribute that can have only one value are processed such that only the last value specified is used. This means, if these flags occur multiple times in a command, the value specified for 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 the command line so that more than one attribute file can be read within one 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 that attribute in the file read last is used.
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 an additive 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 result in a loss of additivity. Multiple -r values are additive, but the use of the command-attribute replaces values specified by the -r flag unless its value is specifically requested to be additive, as shown in the last example in the next section.

Examples Using Command Flags

The 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 logical printers 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 which replaces "-x requested-attributes=".
In this example, the attribute values for both logical-printers-supported and queues-supported are requested with separate -r flags. 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 for queues-supported.
In this example, the attribute values for both logical-printers-supported and queues-supported are requested but are overridden by the command-attribute requested-attributes being entered with the -x flag.
pdls -c server \ -r logical-printers-supported,queues-supported \ -x "requested-attributes=physical-printers-ready" \ SPOOL2
The end result is that the only value returned is the value for physical-printers-ready.
To request all three values shown in the previous example to be used additively, 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-Attributes

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

Table 3-5 Command-Attributes

Attribute	Value	Purpose
`attributes`	`AttributesFileName`	To read in command and object attributes from a file. When this attribute is encountered, the designated attributes file is read and the contents are inserted at the current point in the command.
`class`	`document` `initial-value-document` `initial-value-job` `job` `log` `printer` `queue` `server`	To define the object class that the command is to operate on.
`filter`	"`FilterCriteria`"	To specify the "`FilterCriteria`" you want to use in selecting a given item from several possible items.
`headings`	`true` `false`	To specify whether you want headings displayed.
`message`	"`MessageText`"	To specify a message that is associated with the object being acted on.
`notification-delivery-method`	`email` `message` `none`	To specify the method that you or another person is to be notified of given events related to the object.
`printer-name-requested`	`PrinterName`	To specify a logical printer as the target of a print request.
`requested-attributes`	`all` `archive` `brief` `none` `verbose` "`AttributesList`"	To specify the group of attributes that you want displayed for a specified object class.
`style`	`line` `column`	To specify the format (style) in which you want the requested attributes displayed.
`when`	`after-current` `after-all` `now`	To specify when you want the server to be shut down.

The following rules apply for command-attributes:

You access and set the command-attribute values by using the -x flag. -x takes a single text string containing one or more attribute-value pairs.
Only the command-attributes requested-attributes and class can have multiple values.
The command-attribute requested-attributes is made additive by adding a + (plus sign) before the = (equal sign). For example,
-x "requested-attributes+=printer-model"
Otherwise, any pre-existing values for the command-attribute are no longer available.
If multiple values are specified for the command attribute class and the object class of the command argument does not agree with the last value specified, the command is rejected.

Object-Attributes

The manpages contain a list of attributes for each object. The following manpages 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 some of the HPDPS commands along with the purpose of these attributes.

Table 3-6 Frequently Used Object-Attributes

Attribute	Value	Purpose
`copy-count`	`CopyCount`	An integer used to specify the number of copies that are to be printed. A value of 0 is not valid.
`document-format`	`Format`	Specifies the format of the document, as for example, postscript or ascii.
`job-hold`	`true` `false`	Specifies whether you want to put the job in hold state.
`job-name`	`JobName`	Specifies a new name for a given job.
`job-retention-period`	`JobRetentionPeriod`	Specifies the period of time you want the job retained after being printed before the server deletes the job. The format is [HH]:MM. Hours are optional.
`printer-name-requested`	[`ServerName`:] `PrinterName`	Queries all the jobs in the queue associated with the specified logical printer.

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 attribute name describes the attribute, and its value specifies a value to be assigned to the attribute. For example, the attribute used to specify a banner page in a print job is job-sheets and one of its possible values is job-set-start. This attribute and its value are specified in 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 have only one value at a time) or multi-valued. Multiple values must be separated by a space. For example:
-x "orientations-supported=portrait landscape"
If you specify more than one value for a single-value attribute in one command using either the -x flag or an attributes file specified by the -X flag, or a combination, the last value specified for the attribute is the one assigned.
When an object is created and its attribute values are not specified using the -x flag or -X flag, some of the attribute values may be set to server defaults. Refer to “Default Values for Attributes ” shortly for a description of default values.
The values for job object-attributes and document object-attributes can 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 Arguments

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




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

When the object is a server, the argument is the name of the server. All other objects are contained in servers. For some objects, the name of its server must be supplied in the form ServerName:ObjectName. For other objects, the server name is sometimes optional. You must look at each command to determine the exact format that is allowed. The following arguments 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 of whether it is optional or required), the command is sent to that server.

The server name is optional for:

Commands using local job IDs as the argument.
Commands using the printer name or the queue name; these names must be unique within the namespace. An exception to this is the pdcreate 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 a namespace.
The pdcreate command.

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

Server (spoolers and supervisors)
Printer (logical and physical)
Queue

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

Setting Object-Attributes

There are three main types of object-attributes:

Specifiable: An attribute whose value you can establish when the object is created, but which cannot be subsequently modified.
Settable: An attribute whose value can be set or modified after an object is created, assuming the object is in an appropriate state to be modified.
Non-Settable: An attribute whose value can only be determined by HPDPS.

Setting Attributes When an Object is Created

A specifiable attribute can be set only when you create the object.You can 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 called LogPrt1 in the server (spooler) called SPOOL1, setting the logical printer attribute,printer-realization, to logical as well as assigning the attribute 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 specifiable object-attribute and cannot be changed. You should note that in this example, it is not necessary to set this attribute to logical since it would have been set by default.

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

Setting Attributes After an Object is Created

You can set or modify the value for any settable attribute using the pdmod command (for job and document objects only) or the pdset command (for all objects, including jobs and documents).

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

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

Attributes That Cannot be Specified or Set

Some attributes are non-settable. For example, in the following command, HPDPS uses the argument of the command to assign the printer attribute printer-name the value LogPrt1, and the associated-server attribute the value SPOOL1.

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

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

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

Default Values for Attributes

For 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 override these default values by specifying a different value using the -x and -X flags.
The values can be changed back to their default values using the pdmod or pdset commands and specifying the attribute name followed by == without any attribute value.
For example, the following command sets the value assigned to content-orientations-supported for the physical printer PhysPrt3 back to its default value:
pdset -x "content-orientations-supported==" SUPER1:PhysPrt3
Deleting all the values from a multi-valued attribute or deleting the value of a single-valued attribute sets the attribute value to the default values.

Syntax for Attribute Values

This section describes the syntax for some types of attributes and the values that can be assigned to them. Most attributes are either single valued (they can have only one value at a time) or multi-valued (they can have multiple values). There are also some attributes identified as complex attributes.

Single-Value Attributes

For single-valued attributes, the syntax is:

AttributeName=AttributeValue

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

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




	NOTE: If you specify more than one value for a single-value attribute in one command using either the `-x` flag or an attribute file specified by the `-X` flag, or a combination, only the last value specified for the attribute is assigned.

Multiple-Value Attributes

For multiple-valued attributes, the syntax is:

"AttributeName=AttributeValueX AttributeValueY AttributeValueZ"

where AttributeValueX, AttributeValueY, and AttributeValueZ each denote a separate value for the attribute. Enclose the attribute name and its values in quotes and separate the values with spaces. In the following example, two values are assigned to the content-orientations-supported attribute:

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

Complex Attributes

Complex attributes have multiple values, but each value itself has multiple 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 attribute that 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 can have multiple values.

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

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 of the components will be set to their default values. For example, the following command will set the delivery-address but the other components 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. You cannot use the add (+=) or the delete (-=) operators of pdset or pdmod when changing the component values within a notification-profile value. However, you can add or delete a total value (a user) from the notification-profile by using the += or -= operators and only specifying the delivery-address component. For example, the following 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-changed
delivery-method=email
event-comment="This is a job modification or status event"
delivery-address=dave@cowboy locale=C}
 
{event-identifiers=object-deleted object-cleaned
queue-backlogged
delivery-method=email
delivery-address=mary@cowboy locale=C}

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

Complex Attributes Using Colons

Complex attributes that require colons between components are:

job-size-range-ready
job-size-range-supported
notify-operator
results-profile

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 given component. The default value or no value will be set for that component.
If the last value is to be set to the default value, the colon (:) for that component is not required.

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

pdset -c queue -x "notify-operator= \
email:White@Caddy.xyz.com email:Jones@Chevy.xyz.com" \
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 for information on the results-profile attribute.

Time Attribute Values

For time attribute values, use the local time format as defined in the LC_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 not included, HPDPS uses the current date. Separate the values for hours, minutes, and seconds with colons, with no spaces. Separate the values for month, day, and year with slashes, with no spaces. Enclose time with date in single quotes and separate them with a space. Some examples are:

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

This format specifies hours and minutes; hours are optional. If hours are used, separate the two values with a colon, with no spaces. This example shows 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 Dimensions

For 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 Objects

You can use the pdq and pdls commands to request that the system return the attribute values for a specified object or objects.

The pdq command requests the values of attributes for jobs and documents which are currently queued for printing. If you do not specify a job identifier with the pdq command, the command uses the logical printer specified in the PDPRINTER environment variable. Refer to “Job and Document Identifiers ” later for more information on job identifiers. PDPS determines the queue associated with the logical printer and returns the values for all of the jobs in the queue that have been submitted by you (based on your user-name attribute, 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 values are to be returned and how the values should be presented:
-g
Specifies that headings are not to be used when the attribute values are displayed. This flag is equivalent to using the command-attribute headings=false. Refer to “Formatting the Display of Attribute Values” later for more information.
-r
Specifies the attributes for which values are to be returned. This flag is equivalent to using the command-attribute requested-attributes. Refer to “Values for requested-attributes ” in the next section for a description of the use of this command-attribute and flag.
-s
Specifies the style or format in which the attribute values are to be displayed. This flag is equivalent to using 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 objects and to modify the values for objects can also be used to request that a limited set of attribute values be returned. The command-attributes discussed within this section are supported by the following commands:
- For all objects: pdls, pdcreate, and pdset
- For job and document objects: pdq, pdpr, and pdmod

Values for requested-attributes

To list the attribute values for requested-attributes, use either the -r flag, the command-attribute requested-attributes, or a combination of both. For example, using the -r flag to request all attributes 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

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

Values                    Available on...

all: the pdls and pdq commands.
archive: the pdls and pdq commands, only displaying the specifiable and settable attributes. Refer to “Setting Object-Attributes ” earlier for more information.
brief: the pdcreate, pdls, pdmod, pdpr, pdq, and pdset commands.
"AttributesList": the pdls and pdq commands.
none: the pdcreate, pdls, pdmod, pdpr, pdq, and pdset commands. none is the default for all the commands except pdls and pdq.
verbose: the pdcreate, pdls, pdmod, pdpr, pdq, and pdset commands. verbose is the default for the pdls and pdq commands.

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

-r brief,document-formats-supported

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

-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 you combine values with the -r flag or the requested-attributes attribute, the displayed output is shown in line format unless you specify the column format. See “Formatting the Display of Attribute Values” shortly for formatting information.

Table 3-7 “HPDPS Object-Attributes ” lists the HPDPS objects along with the brief and verbose attribute values. The brief values are a subset of the verbose attribute value.

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.
Initial-Value-Job	`Brief:` `associated-server` `initial-value-job-identifier` `logical-printers-ready` `printer-locations-requested` `printer-models-requested` `Verbose:` `job-retention-period`
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: Only returned on the `pdls` and `pdq` commands. Physical printer name to which the job has been assigned (if such a scheduling decision has been made). Logical printer name to which the job was submitted. Sum of all files and copies.
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` (logical printers) `printer-locations` `scheduler-ready`
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`

Formatting the Display of Attribute Values

Use the headings and style command-attributes to format the display of requested-attributes.

Headings

The headings command-attribute is used to specify whether or not the output is to be displayed with headings. The default is to display with headings. Specifying headings=false or using the -g flag turns off headings.

Specifying headings=true or using the default, causes the following depending 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 without headings.

Style

The style command-attribute or the -s flag is used to specify the format of presentation for attribute values returned by the server. The following shows the value of style depending on the value of requested-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 -r verbose), HPDPS provides the results in line style unless you also request column style with -s column.

Column Style with Headings

Use the following command to display the requested printer attributes in the column style with headings for SPOOL1:

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 in the server (spooler) SPOOL1. The output looks like this:

Printer  Realization   State
-------  -----------   -----
LogPrt1  logical
LogPrt2  logical
LogPrt3  logical

Line Style with Headings

Here is a sample command to display the requested 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:

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

LogPrt1: maximum-copies-supported    = 3
LogPrt1: printer-name                = LogPrt1
LogPrt1: document-formats-supported  = document-format-postscript
                                       document-format-ascii
LogPrt1: associated-server           = SPOOL2
LogPrt1: printer-realization         = logical
LogPrt1: printers-ready              = PhysPrt1
LogPrt1: printer-associated-printers = PhysPrt1
                                       PhysPrt2
                                       PhysPrt3
LogPrt1: associated-queue            = loneQueue
LogPrt2: maximum-copies-supported    = 10
LogPrt2: printer-name                = LogPrt2
LogPrt2: document-formats-supported  = document-format-postscript
LogPrt2: associated-server           = SPOOL2
LogPrt2: printer-realization         = logical
LogPrt2: printers-ready              = PhysPrt2
LogPrt2: printer-associated-printers = PhysPrt1
                                       PhysPrt2
                                       PhysPrt3
LogPrt2: associated-queue            = loneQueue
LogPrt3: maximum-copies-supported    =
LogPrt3: printer-name                = LogPrt3
LogPrt3: document-formats-supported  =
LogPrt3: associated-server           = SPOOL2
LogPrt3: printer-realization         = logical
LogPrt3: printers-ready              = PhysPrt3
LogPrt3: printer-associated-printers = PhysPrt1
                                       PhysPrt2
                                       PhysPrt3
LogPrt3: associated-queue           		 	= loneQueue

Line Style without Headings

The following sample command displays the requested printer attributes in the line style without headings for SPOOL3:

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

If there is one printer, the output looks like:

printer-name         = LP0
printer-realization  = logical
enabled              = true
associate-queue      = Queue0

Using Initial Value Objects (IVOs) to Specify Attribute Values

An initial value object (IVO) represents a collection of default values for job or document attributes. There are two types of initial value objects:

initial-value-document: Specifies values for document attributes.
initial-value-job: Specifies values for job attributes.

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

A logical printer can be created so it specifies a job or a document IVO or both that will provide values for all jobs submitted to that logical printer.
You can specify a job or a document IVO or both for a specific job with the pdpr command when you submit the job.

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

Attribute values from an IVO associated with the logical printer are used first.
Attribute values from an IVO specified with the pdpr command override any values for the same attribute identified in the IVO associated with the logical printer.
Attribute values entered on the command line or from an attribute file specified with the pdpr command override the values for any attributes with the same name that were specified in the previous two conditions.

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

Create an initial-value-job for Spooler1:

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

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

pddisable logptr

pdset -c printer \
-x "printer-initial-value-job=no_banner_IVJ" logptr

Re-enable the printer:
pdenable logptr