Classification:
Tom, a couple comments related to Output Bin and the Job MIB using draft v.81.
1. Pg. 35 jobStateAssociatedValue is INTEGER. The Associated Attribute for
state COMPLETED cannot be outputBinName, as you have specified. I had specified
outputBinIndex, not Name.
2. Pg 35. jmStateAssociatedValue is SINGULAR. You have defined attributes
outputBinIndex and outputBinName as Multi-Row. This is probably ok for the
Attribute table but, for the JobStateTable, we need a single value to represent
outputBin when the job is completed. I had specified a simple method as follows:
-1 Unknown
-2 Multi
prtOutputIndex
I believe, as I've stated many times, the jmJobStateTable is very useful for
JOB STATUS MONITORING (not job accounting). For accounting, I can (sorta) see
where you might be interested in the multi-bin facet of outputs used. But, if
you've submitted a job, I believe you want to know it's state, it's progress
and it's final destination. If you asked for collated copies, that final
destination might be (-2 Multi). I think that's enough to know, at that point.
I'd like us to go back to my proposal for outputbin on jmJobStateValue.
3. Pg. 41 You have separate attributes defined for output bin name and number.
Yet, the attribute table is structured such that an attribute type (output bin)
can have either an Integer or String representation. It is not necessary to
have two enums.
Harry Lewis - IBM Printing Systems