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
At 11:40 05/23/97 PDT, Harry Lewis wrote:
>Yes, I'm saying that jobStateReasons is something a DPA server might know about
>but not (practically) many printers.
>>>Your comments lead me to believe you're saying that it's too damn
>>difficult for the printer agent to say what the current "reason" is.
>>Is this true? If it is, then I think we're in real deep water here.
>>There are 4 sets of jobStateReasons... just look at the first (presumably
>most importatn?) set...
>> canceledByUser, canceledByOperator, abortedBySystem, logfilePending,
> jobRetained etc.
>>>I just went thru the V0.81 draft, but couldn't find 7.5 pages of
>>Job State Reasons in the MIB. Can you give me a better pointer?
>>(Am I looking at the proper draft?) I did find some tables on
>>various Reasons (pp. 57-58), but I guess I don't see the problem.
>>In v0.81 the PDF version (I think) see pages 49-56.
>>Harry Lewis - IBM Printing Systems
>>>>