Using
Abbreviations
for
A
ttribute
Names
and
V
alues
pdresume
Spool4:4628700042
Note:
Dep ending
on
the
requiremen
ts
of
the
job,
a
job
y
ou
resume
could
go
in
to
a
held
state.
Y
ou
can
c
hec
k
the
state
of
resumed
jobs
to
see
if
they
are
in
a
pending
or
processing
state,
and
not
in
a
held
state.
F
or
held
jobs:
a.
Determine
the
reasons
that
jobs
are
held
b
y
querying
one
of
the
logical
prin
ters
that
sends
jobs
to
the
queue.
F
or
example,
to
determine
the
reasons
for
all
held
jobs
in
Queue4
con
tained
in
sp o oler
Spool4 ,
en
ter:
pdq
-U
-f
job-state=held
-r
job-state-reasons
-p
LogPrt4
b.
If
the
reason
is
job-hold-set ,
query
for
the
v
alue
of
the
job-message-
to-operator
attribute
for
the
job
to
determine
if
the
user
has
sp ecial
requiremen
ts
for
the
job.
After
resp onding
to
the
message,
or
if
there
is
no
message,
use
the
pdmod
command
to
release
the
job
hold.
T
o
release
the
job
with
the
global
job
iden
tier
n
um
b er
of
Spool4:4628700042
,
en
ter:
pdmod
-x
"job-hold=false"
Spool4:4628700042
c.
If
the
reason
is
job-print-after-specified ,
use
the
pdmod
command
to
sp ecify
a
time
earlier
than
the
curren
t
time.
F
or
example,
if
the
curren
t
time
is
10:30
in
the
morning,
en
ter:
pdmod
-x
"job-print-after=9:00:00"
Spool4:4628700042
d.
If
the
reason
is
required-resources-not-ready
or
required-
resources-not-supported ,
a
c
hange
to
or
a
problem
with
the
ph
ysical
prin
ter
or
prin
ters
that
could
prin
t
the
job
when
it
w
as
rst
submitted
has
o ccurred.
There
is
no
longer
a
ph
ysical
prin
ter
that
supp orts
all
of
the
attributes
of
the
job.
The
most
likely
cause
of
this
problem
is
that
the
ph
ysical
prin
ter
is
no
longer
ready
.
See
\Querying
for
the
State
of
a
Ph
ysical
Printer"
in
Chapter
10.
e.
Delete
the
queue:
pddelete
-c
queue
Queue4
9-38
Managing
the
Spooler,
Logical
Printers,
and
Queues