1 - 3 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W
restart
Click on the red underlined text to get to the source
... Job object's Cancel-Job operation. An end-user can also hold,
release, and restart their print jobs using the Job object's OPTIONAL
Hold-Job, Release-Job, and Restart-Job operations, if implemented.
...
... release, and restart their print jobs using the Job object's OPTIONAL
Hold-Job, Release-Job, and Restart-Job operations, if implemented.
A privileged operator or administrator ...
... A privileged operator or administrator of a Printer object can
cancel, hold, release, and restart any user's job using the REQUIRED
Cancel-Job and the OPTIONAL Hold-Job, Release-Job, and Restart-Job
...
... cancel, hold, release, and restart any user's job using the REQUIRED
Cancel-Job and the OPTIONAL Hold-Job, Release-Job, and Restart-Job
operations. In additional privileged operator or administrator of a
...
... Hold-Job (section 3.3.5)
Release-Job (section 3.3.6)
Restart-Job (section 3.3.7)
The Send-Document and Send-URI ...
... present, from the job object that had been supplied in the create or
most recent Hold-Job or Restart-Job operation and removes its effect
on the job. The IPP ...
... Restart-Job Operation ...
...
This OPTIONAL operation allows a client to restart a job that is
retained in the queue after processing has completed (see section
...
... The job is moved to the 'pending' or 'pending-held' job state and
restarts at the beginning on the same IPP Printer object with the
same attribute values. If any of the documents in the job were
...
... URI), the Printer MUST re-
fetch the data, since the semantics of Restart-Job are to repeat all
Job processing. The Job Description attributes that accumulate job
progress, such as "job-impressions-completed", "job-media-sheets-
...
... progress, such as "job-impressions-completed", "job-media-sheets-
completed", and "job-k-octets-processed", MUST be reset to 0 so that
they give an accurate record of the job from its restart point. The
job object MUST continue to use the same "job-uri" and "job-id"
attribute values.
...
... 4.3.7.2.
Note: In order to prevent a user from inadvertently restarting a job
in the middle, the Restart-Job request is rejected when the job is in
...
... Note: In order to prevent a user from inadvertently restarting a job
in the middle, the Restart-Job request is rejected when the job is in
the 'processing' or 'processing-stopped' states. If in the future an
operation is needed to hold or restart ...
... Restart-Job request is rejected when the job is in
the 'processing' or 'processing-stopped' states. If in the future an
operation is needed to hold or restart jobs while in these states, it
will be added as an additional operation, rather than overloading the
Restart ...
... restart jobs while in these states, it
will be added as an additional operation, rather than overloading the
Restart-Job operation, so that it is clear that the user intended
that the current job not be completed.
...
... Restart-Job Request ...
... IPP object
MUST support this Operation attribute in a Restart-Job request,
if it supports the "job-hold-until" Job Template attribute in
create ...
... IPP
object NEED NOT support the "job-hold-until" Operation
attribute in a Restart-Job request.
If supplied and supported as specified in the Printer's "job-
...
... according to section 3.1.7, returns the 'successful-ok-
ignored-or-substituted-attributes' status code, and restarts
the job, i.e., ignores the "job-hold-until" attribute.
...
... removes the "job-
hold-until" attribute, if present, from the job. If there are
no other reasons to hold the job, the Restart-Job operation
makes the job a candidate for processing immediately (see
...
... Restart-Job Response ...
... also explains the 'job-restartable' value of the "job-state-reasons"
Job Description attribute for use with the Restart-Job operation.
Job Not Completed: When a job is in the 'pending', 'pending-held',
...
... called Job Retention. While in the Job Retention phase, the job's
document data is retained and a client may restart the job using the
Restart-Job operation. If the IPP ...
... client may restart the job using the
Restart-Job operation. If the IPP object supports the Restart-Job
...
... Restart-Job operation. If the IPP object supports the Restart-Job
operation, then it SHOULD indicate that the job is restartable by
adding the 'job-restartable' value to the job's "job-state ...
... implementation detects errors.
'job-restartable' - This job is retained (see section 4.3.7.2) and
is currently able to be restarted using the Restart-Job
operation (see section 3.3.7). If 'job-restartable' is a value
of the job's 'job-state ...
... state-reasons' attribute, then the IPP object
MUST accept a Restart-Job operation for that job. This value
SHOULD be supported if the Restart-Job operation is supported.
...
... MUST accept a Restart-Job operation for that job. This value
SHOULD be supported if the Restart-Job operation is supported.
'queued-in-device': The job has been forwarded to a device or
print system that is unable to send back status. The Printer
...
... first began processing after the create operation or the most recent
Restart-Job operation. The out-of-band 'no-value' value is returned
if the job has not yet been in the 'processing' state ...
... 0x000C Hold-Job
0x000D Release-Job
0x000E Restart-Job
0x000F reserved for a future operation
0x0010 Pause-Printer
...
... 1. Know how long it has been down, and resume at some value
greater than 'n', or
2. Restart from 1.
In other words, if the device or devices that the Printer object is
...
... continue counting this value or MAY reset this value to 1 depending
on implementation. However, if the Printer object software ceases
running, and restarts without knowing the last value for "printer-
up-time", the implementation MUST reset this value to 1. If this
value is reset and the Printer has persistent jobs, the Printer MUST
...
... Hold-Job (section 3.3.5) OPTIONAL
Release-Job (section 3.3.6) OPTIONAL
Restart-Job (section 3.3.7) OPTIONAL
Conforming IPP ...
... a job with no documents.
26. Sections 3.3.5, 3.3.6, and 3.3.7 - added the OPTIONAL Hold-
Job, Release-Job, and Restart-Job operations. Clarified the
Restart-Job operation so that the Printer MUST re-fetch any
...
... Job, Release-Job, and Restart-Job operations. Clarified the
Restart-Job operation so that the Printer MUST re-fetch any
documents passed by-reference (Print-URI or Send-URI ...
... "job-hold-until" attribute for use with the create operations
and Hold-Job and Restart-Job operations.
36. Section 4.2.6 - added more enum values to the "finishings" Job
Template attribute.
...
... first time processing since the create operation or the
Restart-Job operation.
49. Section 4.3.14.2 and 4.3.14.3 - clarified that the out-of-band
...
... 9. Section 4.3.7.2 - indicated that the 'job-restartable' job
state reason SHOULD be supported if the Restart-Job operation
is supported.
10. Section 4.3.8 - changed "job-state ...
... detects warnings. The 'job-completed-with-errors' SHOULD be
supported if the implementation detects errors. The 'job-
restartable' SHOULD be supported if the Restart-Job operation
is supported.
12. Section 4.3.10 - allowed a Printer to localize the "job-
...
