I also want a small set of meaningful job states.
>A job can be in many, many kinds of "states", depending on the features
>(and attendant complexities) of the underlying printing system. However,
>no matter what printing system is involved, all jobs will be in exactly
>one of the three top-level "meta" states of pending, processing, done.
>Below these three states, the mgmt application in question will decide
>on the exact semantics of the job based on some *consistent* refinement
>of the top-level state. Hence, the simple two-level model I have been
>suggesting this past week or so.
> ...jay
I tend to get very confused by the 3 separate terminology's however,
those being JobState, JobSubState and JobStateReason.
I believe there are actually 7 job states that deserve to be called
STATES. We should be welcome to embellish any state with as many (or as
FEW) REASONS as seen fit. Listed in my preferred terminology along with
the current IPP/JMP name-for-a-day in parenthesis, the 7 are:
Pending
Held (Pending-Held)
Printing (Processing)
Needs_Attention (Processing-Stopped)
Completed
Canceled (Completed-Canceled)
Aborted (Completed-Aborted)
Yes, the STRAIGHT LINE PATH from submission to marks on paper is
Pending-Printing-Complete, but other significant states are Held,
Needs_Attention, Canceled and Aborted. There are all kinds of reasons
(my favorite being printer-partly-stopped). I would like to suggest, however,
that if we adopt these 7 as the "high level" states then we can eliminate the
idea of "sub-state".
Harry Lewis - IBM Printing Systems