Our problem is that software applications are likely to represent OFFLI=
NE,
CRITICAL ACTIVE, NON-CRITICAL ACTIVE, NORMAL, BUSY etc... as high level=
Printer
Status... as defined by the chart in the printer MIB. Unfortunately, we=
are
using the OFFLINE bit to overcome a limitation with SF which will resul=
t in a
false Status indication on the manager if the printer has a full or mis=
sing
output bin but does not actually go OFFLINE.
I submitted a proposal to add hrPrinterDetectedErrorState bits to the h=
rMIB.
Was the expectation that the top25 chart would be updated should these =
bits be
accepted? If so, I suggest the total inactivity in hrMIB is totally
unacceptable and the PWG should take matters into it's own hands by add=
ing an
object to prtGeneral which extends these bits. Then we could clean up t=
he top
25 table.
If others think it's just been too long and hard a battle to reopen at =
this
point, I'd at least like to hear from software vendors what they think =
about
indicating OFFLINE when it's really not.
Harry Lewis - IBM Printing Systems
=