Tom, in v1, there were inconsistent implementations when using strings as an
index. In some cases, the octet string would be preceded by it's length
e.g. get-request jmJobIndex.5.h.a.r.r.y
In other cases, the length of the octet string would be IMPLIED by
the length of the OID, so the 'length' indication wasn't included.
get-request jmJobIndex.h.a.r.r.y
I think v2 tried to address this inconsistency by Adding 'IMPLIED'
to the declaration which clearly indicates the 'length' should be omitted.
jmJobIDEntry OBJECT-TYPE
...
INDEX { IMPLIED jmJobSubmissionIDIndex }
...
I would like to request that you change the definition of jmJobIDEntry as such.
Harry Lewis - IBM Printing Systems