HP-UX Reference (11i v1 00/12) - 1 User Commands N-Z (vol 2)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1/neqn.1
________________________________________________________________
___ ___
p
pdls(1) pdls(1)
(TO BE OBSOLETED)
NAME
pdls - lists selected attribute values
SYNOPSIS
pdls [-c ObjectClass][-f "FilterCriteria" ][-F][-g][-j][-r "RequestedAttributes" ]
[-s StyleName][-U][-x "AttributeValuePairs" ][-X AttributesFileName]
[ServerName... |
ServerName:InitialValueDocumentName... |
ServerName:InitialValueJobName... |
ServerName:LogName... |
[ServerName:]PrinterName... |
[ServerName:]QueueName... |
LocalJobId[.DocNumber]... |
GlobalJobId[.DocNumber]...]
pdls -h
DESCRIPTION
You enter the pdls command to request that selected attribute values be displayed for one or more print
jobs or other HPDPS objects.
• By default, a filter is created when listing jobs which only allows you to see your jobs. The jobs have a
predefined value for the filter that is equal to the job attribute user-name
; this value is your login
identity when you submit a job.
• You add to this filter to further restrict the jobs for which information is to be returned.
• You must suppress the default filter by using the
-U option or turn off all filtering with the
-F option
to see more than your own jobs.
• If you only specify the ServerName as the command argument, the attribute values for all objects
belonging to the object class you specify are displayed.
• You can list the attribute values for specific jobs by using the local ID or the global ID. You must have
submitted the job to use the local ID.
Note: There is a situation when you must use the global ID. If the client daemon responsible for mapping
local ID to global ID is not available, HPDPS may not be able to tie the local ID to the global ID. If this
situation exists, you must use the global ID, the name of the server (spooler), or an argument specification
using global characters.
There is a possible situation that can occur if your administrator has set the PDIDTABLE environment
variable to a low value, for example 10. You submit a series of jobs during a short time span such that the
number of jobs you have in process is larger than the value set, say 14. You will have two jobs with the
local IDs of 1, 2, 3, and 4. However, HPDPS no longer associates the first four jobs with a local ID because
those local IDs have been given to the 11th, 12th, 13th, and 14th jobs. Therefore, you must use the global
ID to take action for any of the first four jobs.
Options
pdls recognizes the following options:
-c ObjectClass
Specifies the object class of the object whose attributes you want listed. ObjectClass can be one of:
job (default)
document
initial-value-document
initial-value-job
log
printer
queue
server
This option is equivalent to the command-attribute class.
-f "FilterCriteria
"
Specifies the filter criteria you want to use in selecting from the candidate objects. Among the candi-
date objects, only those matching the filter expression are returned. See the command-attribute
Section 1−−682 − 1 − HP-UX Release 11i: December 2000
___
___