> And the state is even required by an ACCOUNTING application,
> so the jmJobStateValue is replicated in the Attribute Table as
> jobState(3) attribute, so that an accounting application can skip over
> jobs that are not yet completed.
Whoa, here. Replication of MIB values is an explicit non-goal of
traditional MIB design, right? At least this is what Steve Waldbusser
has repeatedly stated (and for good reason).
If you're replicating values to somehow make it easier for a mgmt app,
then I'd suggest the MIB is too complicated.
...jay