JMP Mail Archive: Re: JMP> Output Bin Attribute

Re: JMP> Output Bin Attribute

Tom Hastings (hastings@cp10.es.xerox.com)
Mon, 17 Mar 1997 18:19:07 PST

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Ron Bergman: "JMP> First Comment Set on version 0.7 MIB"
Previous message: Tom Hastings: "Re: JMP> Job States and State Reasons"
Maybe in reply to: Harry Lewis: "JMP> Output Bin Attribute"
Next in thread: Harry Lewis: "Re: JMP> Output Bin Attribute"

So that the Job Monitoring MIB can be used with a server that hasn't
implemented the Printer MIB.

We could add a second enum that has a value that is the output bin
index for those implementations that have a Printer MIB, should we?

(I think its better to add a second enum, instead of saying that this
outputBin enum could have either a text value or an integer (index)
value or both, correct?)

Tom

At 16:28 03/17/97 PST, Harry wrote:
>Classification:
>Prologue:
>Epilogue: Harry Lewis - IBM Printing Systems
>
>Why is outputBin (the jmAttributeTC) defined as TEXT rather than an index into
>the associated Printer MIB (like jobSourceChannelIndex)?
>
>Harry Lewis - IBM Printing Systems
>
>

Next message: Ron Bergman: "JMP> First Comment Set on version 0.7 MIB"
Previous message: Tom Hastings: "Re: JMP> Job States and State Reasons"
Maybe in reply to: Harry Lewis: "JMP> Output Bin Attribute"
Next in thread: Harry Lewis: "Re: JMP> Output Bin Attribute"