Gee, I think just the opposite. Each job submission protocol has the
recipient server or printer return an identifier to the submitter.
So we need to know the *name* of the fundamental attribute in each
job submission protocol that maps to the jmJobIndex object.
So it is vital that we understand which attribute (that is returned
by the recipient) maps to the jmJobIndex.
By the way, we have the serious issue of what happens for a job submission
protocol in which the job identifier generated by the server or printer
is 0 (say for the first job after the system is booted). SNMP won't allow
us to have a 0 value as an index. SO we need to know how many job
submission protocols return 0 for a valid job identifier. If there are some,
we need to figure out what to do. See the issues list. Map 0 to the highest
index?
Tom
At 08:21 03/04/97 PST, you wrote:
>The first object in the Template provided by Tom Hastings is jmJobIndex.
>>Since this object is defined and used by the device that is providing
>the MIB it must always be present. IMHO, this object most likely will
>not map into an existing parameter defined by the Job Submission
>Protocol. I would recommend that this object be ignored by all who
>are completing this template.
>>-----------------------------------------------------------------------
> Ron Bergman
> Dataproducts Corp
>rbergma at dpc.com> (805)578-4421
>>>>