At 16:29 05/08/97 PDT, JK Martin wrote:
>Tom,
>>> 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.
I agree completely that the same information should not have two ways to
be accessed. That is why I have been suggesting getting rid of
the Job State table altogether.
>> ...jay
>>