Technical data

7.1.5 Modifying Job and Document Attributes
You can use the pdset and the pdmod commands to modify job and document
attributes.
The pdset command sets, adds, or removes values of writable attributes
of printers, queues, servers, jobs, documents, and initial-value objects.
Changes you make to the attribute values of an object are persistent; they
remain in place even after the system is restarted. The specified attribute
values will be set for every object you include as a command operand.
Some object attributes make reference to other objects in your configuration.
To set any of the following print attributes, the new value must refer to
an object that already exists:
associated-queue
printer-initial-value-job
printer-initial-value-document
Administrators can set attribute values of any object in the system. An
operator can set attributes of any job and values of the xxx-ready attributes
for physical printers. An end user can set only attribute values of owned jobs.
The pdset command has the following syntax:
pdset [-c class_name] [-g] [-m message_text] [-r requested_attributes] [-s
style_name][-xextended_attribute_string
...][-Xattribute_filename
...
]
object_instance
...
The following examples show how to use the pdset command:
• To connect physical printer ginney to queue les.
# pdset -c printer -x associated-queue=les ginney
• To add iso-a4-white media to the media-supported attribute for the
printer named samantha. The operand is assumed to be a printer name
because the default class for the pdset command is printer.
# pdset -x "media-supported+=iso-a4-white" samantha
• To release job 21, which was placed in the held state when it was
submitted for printing:
# pdset -c job -x "job-hold=no" spl:21
The pdmod command modifies job and document attributes of a job that you
have submitted for printing but that has not yet started to print. Changes
you make to the job are persistent; that is, they remain in place after the
system is restarted.
Managing Jobs and Documents 7–5