Figure 12-2. Life Cycle Of A Spooler Job - HP Guardian User Manual

Introduction to the Spooler
Attribute
Job Report
Name
Job
Location
Life Cycle
of a Job

Figure 12-2. Life Cycle of a Spooler Job

Create: You create a job when your application opens a collector process and writes to it; for example:
TFORM /IN filename, OUT $S.device/
Open: The application writes to the collector process, which in turn writes the data to a disk file.
Ready: The job is ready when the application closes the collector process.
Hold: You can hold a job, removing it from the device queue, only when it is in the ready or print state.
Print: The job waits in the device queue until it is ready to print. While in the print state, the job is printing
on the output device. If you place the job on hold, it immediately stops printing.
Delete: If the hold-after-printing flag is not set, the job is deleted after it finishes printing. You can also
delete a job from the spooler using a specific request. If the job is printing when you make that request,
the job immediately stops printing and is deleted.
Definition
The job report name is printed in the header message of the job, which is
described under Printer Attributes
The job location can be associated with a physical printer on the system or
with a dummy holding location. See
1. A job starts at the OPEN state while the application is writing the data to
the collector process.
2. The collector process stores the data as a job in a print queue on disk.
3. When the application is finished, the job is in the READY state.
4. The job enters the PRINT state if its spooler location is associated with a
printer.
5. The print process controls the printing of the job.
6. When printing is complete, the spooler deletes the job, unless the hold-
after-printing flag is set.
Create Open
Guardian User's Guide —425266-001
on page 12-6.
Routing Structure
Ready Print
Hold
12- 5
Spooler Jobs and Job Attributes
on page 12-8.
Delete
CDT 009 .CDD