 |
» |
|
|
|
This manual uses the following typographic conventions: - User input
Text that must be entered at the command line exactly as
shown, such as pdpr -x "page-count=50" File3 |
- Computer
Indicates commands or command segments, flags, attributes,
files, directories, and other items whose names are predefined by
the system, such as pdls and notification-delivery-method. Also shows text that is displayed as output on your screen
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 must replace
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 following symbols at the command line, unless specifically instructed
to do so: - Brackets
[ ] - Braces
{ } - Bar
| - Ellipsis
...
These symbols have the following meanings, as illustrated
using the following sample syntax statement: pdmod [Flags]{LocalJobId ... | GlobalJobId ...} |
Brackets, [ ], around values indicate that they are optional.
Here, they mean that you do not have to enter any of the available pdmod flags with the pdmod command. Braces, { }, around values indicate required items that you
must supply with the command. Here, they mean that you must enter either
a LocalJobId or a GlobalJobId with the pdmod command. Braces are also used within the notification-profile attribute. A vertical bar, |, between values indicates that you can only enter
one of the values with the command. Here, it means that when you
issue the pdmod command, you can specify either a LocalJobId or a GlobalJobId, but not both. An ellipsis, ..., indicates that you can
supply more than one occurrence of a particular type of value with
the command. Here, it means that you can supply more than one local
job identifier value or more than one global job identifier value
with the pdmod command.
Special Characters in Syntax Some special characters are included in commands. When colons,
dashes, the equals sign, double quotation marks, single quotation
marks, and braces are shown in command syntax notation, include
them when you issue the command. These special characters have the
following meanings: A colon, :, separates related values. For example: pdmod -x "sides=2" Spool12:1011230045 |
Spool12:1011230045 is a global job identifier on the Spool12 server. 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 value pairs,
such as: -x "sides=2 content-orientation=portrait" |
For consistency, double quotation marks also are shown around
single attribute and value pairs in all examples, although they
are not required. Double quotation marks, " ", surround text strings that contain spaces, such
as: -m "Down for maintenance" |
Single quotation marks, ' ' , surround a text string that contains spaces when
the text string is imbedded in a statement already enclosed in double
quotation marks. An example is: -x "sides=2 job-print-after='08:00:00 03/09/95'" |
Braces, {}, surround a value within the notification-profile attribute. An example is: -x "notification-profile={delivery-method=electronic-mail}" |
Double ampersand, &&, means "and" within a command. An example is: 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 Abbreviations for Attribute Names and Values In many cases, you can abbreviate attribute names and values
by using the first letter of each word in the name or value. For
example, you can use the abbreviation s-m-s for the start-message-supported attribute, t for the true value, and specify the attribute and value pair
as s-m-s=t. However, in some cases specifying only the first letter in
each word can be 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-ow and j-or. If the values are ambiguous, HPDPS rejects the
command and you receive an error message. Use abbreviated attribute
names and values as appropriate. |
Printable version
