Hi folks, Friday (6 August 1999)
Below are the original and new texts of 'hrPrinterDetectedErrorState'.
Please review them. Otherwise, so far all I've encountered to question
is that Steve Waldbusser has dumbed down Bobby Krupczak's improved
'InternationalDisplayString' from default of UTF-8 (per IETF Charset
and Languages Policy, RFC 2277) to a default of NVT-ASCII. This
datatype thus becomes *useless* for internationalized file systems
(which per X/Open UTF-FSS and recent POSIX locale standards MUST now
operate with UTF-8 filenames and pathnames by default - note that
several UNIX variants and MacOS already support UTF-8 filesystems, so
this isn't some hypothetical problem).
Read and enjoy.
Cheers,
- Ira McDonald
High North Inc
906-494-2697/2434
------------------------------------------------------------------------
[Original text from 'rfc1514.txt', September 1993]
hrPrinterDetectedErrorState OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object represents any error conditions
detected by the printer. The error conditions are
encoded as bits in an octet string, with the
following definitions:
Condition Bit # hrDeviceStatus
lowPaper 0 warning(3)
noPaper 1 down(5)
lowToner 2 warning(3)
noToner 3 down(5)
doorOpen 4 down(5)
jammed 5 down(5)
offline 6 down(5)
serviceRequested 7 warning(3)
If multiple conditions are currently detected and
the hrDeviceStatus would not otherwise be
unknown(1) or testing(4), the hrDeviceStatus shall
correspond to the worst state of those indicated,
where down(5) is worse than warning(3) which is
worse than running(2).
Bits are numbered starting with the most
significant bit of the first byte being bit 0, the
least significant bit of the first byte being bit
7, the most significant bit of the second byte
being bit 8, and so on. A one bit encodes that
the condition was detected, while a zero bit
encodes that the condition was not detected.
This object is useful for alerting an operator to
specific warning or error conditions that may
occur, especially those requiring human
intervention."
::= { hrPrinterEntry 2 }
------------------------------------------------------------------------
[New text from 'draft-ops-hostmib-00.txt', 3 August 1999]
hrPrinterDetectedErrorState OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents any error conditions detected
by the printer. The error conditions are encoded as
bits in an octet string, with the following
definitions:
Condition Bit # hrDeviceStatus
lowPaper 0 warning(3)
noPaper 1 down(5)
lowToner 2 warning(3)
noToner 3 down(5)
doorOpen 4 down(5)
jammed 5 down(5)
offline 6 down(5)
serviceRequested 7 warning(3)
inputTrayMissing 8 warning(3)
outputTrayMissing 9 warning(3)
markerSupplyMissing 10 warning(3)
outputNearFull 11 warning(3)
outputFull 12 warning(3)
inputTrayEmpty 13 warning(3)
overduePreventMaint 14 warning(3)
The hrDeviceStatus column shows the hrDeviceStatus
which is typically appropriate when such an error
condition exists. If multiple conditions are
simultaneously detected and the hrDeviceStatus would
not otherwise be unknown(1) or testing(4), the
hrDeviceStatus shall correspond to the worst state of
those indicated, where down(5) is worse than
warning(3) which is worse than running(2).
Bits are numbered starting with the most significant
bit of the first byte being bit 0, the least
significant bit of the first byte being bit 7, the
most significant bit of the second byte being bit 8,
and so on. A one bit encodes that the condition was
detected, while a zero bit encodes that the condition
was not detected.
This object is useful for alerting an operator to
specific warning or error conditions that may occur,
especially those requiring human intervention."
::= { hrPrinterEntry 2 }
------------------------------------------------------------------------