Except for the following, each attribute is either xxxRequested or xxxConsumed,
but not both.
outputBinIndex 56
outputBinIndex 56
outputBinName 56
sides 56
documentFormatIndex 56
documentFormatEnum 56
physicalDeviceIndex 57
physicalDeviceName 57
In no case is a requested value reset to 0, except for the xxxCurrentCopy
attributes.
jobCopiesRequested 57
jobCopiesCompleted 57
documentCopiesRequested 57
documentCopiesCompleted 57 [glitch in TOC doesn't show this - oops]
jobKOctetsTotal 58
jobKOctetsCompleted 59
impressionsSpooled 60
impressionsSentToDevice 60
impressionsInterpreted 60
impressionsRequested 60
impressionsCompleted 60
impressionsCompletedCurrentCopy 60
pagesRequested 60
pagesCompleted 60
pagesCompletedCurrentCopy 60
sheetsRequested 61
sheetsRequested 61
sheetsCompleted 61
sheetsCompletedCurrentCopy 61
mediumRequested 61
mediumConsumed 61
colorantRequestedIndex 61
colorantRequestedName 61
colorantConsumedIndex 62
colorantConsumedName 62
>
>Bob Pentecost
>HP
>
>
>
>----------
>From: Harry Lewis <harryl@VNET.IBM.COM>[SMTP:harryl@VNET.IBM.COM]
>Sent: Thursday, February 13, 1997 7:47 AM
>To: jmp@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.
>
>
>
>
>