JMP Mail Archive: Re: JMP> JobStateValue

Re: JMP> JobStateValue

Tom Hastings (hastings@cp10.es.xerox.com)
Thu, 8 May 1997 17:19:15 PDT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Harry Lewis: "JMP> Persistence and Table management"
Previous message: JK Martin: "Re: JMP> JobStateValue"
Maybe in reply to: Harry Lewis: "JMP> JobStateValue"
Next in thread: JK Martin: "Re: JMP> JobStateValue"

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
>
>

Next message: Harry Lewis: "JMP> Persistence and Table management"
Previous message: JK Martin: "Re: JMP> JobStateValue"
Maybe in reply to: Harry Lewis: "JMP> JobStateValue"
Next in thread: JK Martin: "Re: JMP> JobStateValue"