>jmResourceType is a read-only object, so how can the job be affected?
Thanks for pointing that out.
>This brings up another question. ................... ce,
>......... 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"?
You've done a better job at stating my observation. My recommendation
is to separate values which are passed in from values that will vary
during the job.
Harry Lewis