JMP Mail Archive: Re: JMP> Should jobStateReasons1 be mandatory?

Re: JMP> Should jobStateReasons1 be mandatory?

Harry Lewis (harryl@us.ibm.com)
Wed, 28 May 1997 19:54:09 -0400

I'll repeat ... I don't see how we can make a particular state mandatory
but for the sake of discussion... how can we possibly label "jobPrinting"
as Optional but jobCompletedWithWarnings and jobCompletedWithErrors
Mandatory? I can guarantee it will be easier for some printer job agents
to be aware that the job is Printing then to know whether or not warnings
or errors were encountered on the way to the stacker!

> JMP jobStateReasons1 values
> other
> unknown
>Man jobIncoming
>OPT jobOutgoing
> jobHeld
> jobHoldSpecified, jobHeld
> jobHoldUntilSpecified, jobHeld
> jobHoldUntilResourcesAreReady,jobHeld
> jobProcessAfterSpecified, jobHeld
>OPT deviceStoppedPartly
>MAN deviceStopped
>OPT jobPrinting
> jobCanceledByUser
> jobCanceledByOperator
>OPT logfilePending
>OPT logfileTransferring
>MAN jobCompletedSuccessfully
>MAN jobCompletedWithWarnings
>MAN jobCompletedWithErrors
> jobPaused
> jobInterrupted
> jobRetained

Harry Lewis - IBM Printing Systems

---------------------- Forwarded by Harry Lewis/Boulder/IBM on 05/28/97 05:35 PM
---------------------------

jmp-owner@pwg.org
05/28/97 10:31 AM
Please respond to jmp-owner@pwg.org @ internet

To: Harry Lewis/Boulder/IBM@IBMUS
cc: jmp@pwg.org @ internet
Subject: Re: JMP> Should jobStateReasons1 be mandatory?

At 17:16 05/27/97 PDT, Harry Lewis wrote:
>So, let me understand...
>
>>Harry,
>
>>It was on this mail and Jay's that I concluded we had JMP agreement on
>>making jobStateReasons1 attribute mandatory and I made the second
>>step of moving it to the jmJobTable, as we agreed for all mandatory
>>attributes in San Diego. Making it mandatory also agrees with IPP.
>
>>Tom
>
>You are proposing that jmJobTable contain a mandatory OID for
>jobStateReasons1. But, if, of the 20 reasons specified, a printer
>can only "detect" the 4 that I have marked with (*), below, that's acceptable,
>right?

Almost. Even though the jmJobStateReason1 object is mandatory because
its in a Mandatory group, we get to decide on a enum by enum basis
which ones are mandatory (agent shall implement whether printer has or not)
which are conditionally mandatory (agent shall implement, but only if the
printer has that behavior)
and which ones are optional (agent doesn't have to imlement, even if the
printer has that behavior)

Most of the reasons are conditionally mandatory. The mandatory ones
are indicate below with "Man":

>
>*other
>*unknown
>*no reason (all zeros)
> documentsNeeded
> jobHoldSet
> jobProcessAfterSpecified
> requiredResourceNotReady
>*successfulCompletion
> completedWithWarnings
> completedWithErrors
> canceledByUser
> canceledByOperator
> abortedBySystem
> logfilePending
> logfileTransferring
> jobPreProcessing
> jobPaused
> jobInterrupted
> jobRetained
> jobHoldUntil
>
>
>Harry Lewis - IBM Printing Systems
>
>