Harry,
jmResourceType is a read-only object, so how can the job be affected?
Wouldn't the object change values only as resources are used?
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"?
Bob Pentecost
HP
----------
From: Harry Lewis <harryl at VNET.IBM.COM>[SMTP:harryl at VNET.IBM.COM]
Sent: Thursday, February 13, 1997 7:47 AM
To: jmp at pwg.org
Subject: JMP> Resource table - Missile or Camera
jmResourceTypeTC says (effectively)
"The type (and amount) of resource... required to process the job...the
amount is updated while the job processes... etc."
I was starting to wonder if we were "affecting" the job, for example,
number
of copies. But I'm sure we've been very careful to avoid "missiles". Then,
the purpose of an initial value is to establish a range for metering, like
copy 1 of 3 has been printed - right? But, if the initial value is
overwritten
per "amount is updated while the job processes...", and the MIB basically
acts as a data base to be polled, doesn't 1 of 3 fall apart, in which case
what good would the initial value be?
Sorry if I missed something here.
Harry Lewis.