At 14:14 02/13/97 PST, Lloyd Young wrote:
>Bob Pentecost wrote
>>This brings up another question. jmResourceType says "The type of resource,
>>e.g., medium, ink, staples, processing-time, color-impressions, etc.
>>required to process the job before the job start processing. This value is
>>updated while the job processes to indicate the amount of the resource that
>>is being used while the job is processing. After the job completes
>>processing, this value indicates the total usage of this resource made by
>>the job." If a job hasn't started processing, a resource will indicate how
>>many will be produced. Then, when the job starts processing, the value will
>>go to zero and count up to three. Is the management application expected to
>>query jmJobState to know how to interpret the value? If so, should we
>>define which states cause the value of a resource to change from "required"
>>to "used"?
>>I do not think it is likely that any system will ever fill in the values for a
>particular resource that are required to process the job before the job starts
>processing. It would make this whole thing simpler if we changed the first
>sentence and said "The type of resource, e.g. medium, ink, staples,
>processing-time,
>color-impressions, etc. that are consumed while processing the job. This value
>is
>updated while the job processes ....... ". With this wording change, the
>resources
>now are stricly what is consumed in processing the job.
I agree. Here is what I've clarified the beginning of the jmAttributeGroup
in the Internet Draft 00:
The jmAttributeGroup consists attributes of the job and document(s).
Attribute may represent information about the job and document(s), such as
file-names, document-names, submission-time, completion-time, size.
Attributes may also represent requested and/or consumed resources for each
job. Instead of allocating distinct objects for each attribute, each
attribute item is represented as a separate row in the jmAttributeTable.
Each column in the row describes the attribute, such as its type represented
as an enum, and the value represented as (1) an integer or (2) an octet
string (character coded text and binary octet strings, such as DateAndTime)
or (3) both.
Ok?
>>Lloyd Young
>Lexmark
>>