>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?
*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