JMP Mail Archive: Re: JMP> HELD vs NEEDS-ATTENTION

Re: JMP> HELD vs NEEDS-ATTENTION

JK Martin (jkm@underscore.com)
Thu, 22 May 1997 20:54:27 -0400 (EDT)

You raise a good point, Harry. I think we really want the user
to be able to distinguish between jobs not printing due to problems
vs. administrative "hold" (no matter who put the job on hold).

One definition we'll have to nail down is NEEDS-ATTENTION. Does
that term imply device-only problems, or any kind of problem that
keeps the job from printing (other than HELD)?

Given your statements, I'd vote for having NEEDS-ATTENTION imply
_any_ kind of problem, and not just device-related problems.

Similarly, I'd suggest that HELD implies an administratively-set
condition only.

Quick comments/votes by the others? (Tick, tick, tick...)

...jay

----- Begin Included Message -----

From: Harry Lewis <harryl@us.ibm.com>
To: <jmp@pwg.org>
Subject: JMP> HELD vs NEEDS-ATTENTION
Date: Thu, 22 May 1997 19:42:38 -0400

Some of the job state reasons for HELD seem like they would fit better as
reasons for NEEDS-ATTENTION. For example:

requiredResourcesNotReady 0x20
The job is in the held state because at least one of the
resources needed by the job, such as media, fonts, resource
objects, etc., is not ready on any of the physical devices
for which the job is a candidate.

serviceOffLine 0x400000
The service/document transform is off-line and accepting no
jobs. All pending jobs are put into the held state. This
could be true if its input is impaired or broken.

These reasons seem categorically different than "Someone put this
job on Hold 'till midnight".

I guess it is fairly clear that state NeedsAttention should pertain to
actual DEVICE failures, but 0x400000, above, sounds like it could
be just that to me.

Harry Lewis - IBM Printing Systems

----- End Included Message -----