Tom, I think you missed my point here,
TOM SAID
>By the way all of the attributes that you listed are the ones for
>which we don't have separate attributes (or multiple entries) for
>requested vs. consumed. In otherwords, the same entry is used for
>both (and the requested and consumed value should be the same, so it
>wasn't worth having two enums for each. See Ron Berman mail on this
>subject.
HARRY HAD SAID
>>I do not understand the need for requested values for any of the
>>following "attributes" within the context of a resource accounting
>>table such as we have defined.
>>
>>>Most attributes are either the requested value or the consumed (updated
>>>as the job progresses), but not both. The only attributes that are both
>>>requested/used are:
>>
>>>outputBinIndex*56
>>>outputBinIndex*56
>>>outputBinName*56
>>>sides*56
>>>documentFormatIndex*56
>>>documentFormatEnum*56
>>>physicalDeviceIndex*57
>>>physicalDeviceName*57
Key word in my statements is REQUESTED. I was trying to make the point,
regarding requested/consumed, that requested is unnessary for these
attributes. Can you give me an example of why they would be needed?
Harry Lewis - IBM Printing Systems