At 11:41 05/27/97 PDT, Harry Lewis wrote:
>Tom, you requested:
>>>I've edited the list of Job Monitoring MIB objects and attributes
>>according to the San Diego meeting and subsequent e-mail.
>>>>Please review and make any comment ASAP. I'm editing these changes now.
>>Here are my comments:
>>1. What is the difference between jmJobSourcePlatformType and
> jobOriginatingHost?
jobSourcePlatformType (and corresponding JmJobSourcePlatformTypeTC) is the
type of system, and is an enum (one of the reasons that I like "Type" in the
object or attribute name) e.g. UNIX, Windows, etc.
jobOriginatingHost is the name of the host, not its type, e.g., a string
that was assigned to the host by an administrator. See IPP. This was
one of the IPP attributes that we agree to pick up into JMP at San Diego.
>2. I notice you deleted jobStateReasons1 and now treat it as a mandatory
> object in the JobTable. I don't recall this agreement.
It was not agreed to at San Diego, but the resulting e-mail discussion
seemed to indicate that a few values are mandatory, so I moved it
from the attribute table to be a real object, since it was only an integer
following our agreed principle in San Diego of moving mandatory attributes
to the jmJobTable, at least the integer ones.
If there is a problem with this, then I can move it back. But I think this
is also involved with the needsAttention state vs. deviceStopped
jmJobStateReasons1 value disucssion.
>3. Why did you remove Index from Physical device, OutputBin, colorant,
> and removed type from mediumRequested? Is this due to the fact that
> we have value as integer and octets?
Yes, as we agreed in San Diego to combine these. So I had to drop the
data type from the name. Any other suggestions for the name? Do you
find this confusing that the name doesn't indicate that there are two
possibl representations and that both can be used together?
>>Harry Lewis - IBM Printing Systems
>>