Actually, what we so far have is Xerox MIB means to update supported
locales dynamically and a desire not to preclude doing so in real
products in the future. The presumption remains though that the
managed system would be in some 'service' mode (although the SNMP
agent was 'talking') and network jobs would NOT be floo...oops
flowing through the managed system while new locales were added
(to a hard disk, flash memory, or whatever). The managed system would be
reset (via the Printer MIB object or some other means) and do a power
cycle before the new locales would be 'available' for use.
- Ira McDonald (outside consultant at Xerox)
High North Inc
PO Box 221
Grand Marais, MI 49839
-------------------------------- Bob's note --------------------------
Received: from zombi (zombi.eso.mc.xerox.com) by snorkel.eso.mc.xerox.com (4.1/XeroxClient-1.1)
id AA06034; Thu, 26 Jun 97 18:47:30 EDT
Received: from alpha.xerox.com by zombi (4.1/SMI-4.1)
id AA03617; Thu, 26 Jun 97 18:44:41 EDT
Received: from palrel3.hp.com ([126.96.36.199]) by alpha.xerox.com with SMTP id <14675(2)>; Thu, 26 Jun 1997 15:44:21 PDT
Received: from hpbs3125.boi.hp.com (hpbs3125.boi.hp.com [188.8.131.52]) by palrel3.hp.com with SMTP (8.7.5/8.7.3) id PAA08182 for <firstname.lastname@example.org>; Thu, 26 Jun 1997 15:33:58 -0700 (PDT)
Received: from hpb15432.boi.hp.com by hpbs3125.boi.hp.com with SMTP
(184.108.40.206/15.5+IOS 3.22) id AA24254; Thu, 26 Jun 1997 16:33:53 -0600
Received: by hpb15431.boi.hp.com with Microsoft Mail
id <01BC824E.B1423F20@hpb15431.boi.hp.com>; Thu, 26 Jun 1997 16:33:35 -0600
From: Bob Pentecost <email@example.com>
To: "'Young, Lloyd PWG'" <firstname.lastname@example.org>,
"'Wellens, Chris (PWG)'" <email@example.com>,
"'Mcdonald, Ira (PWG)'" <firstname.lastname@example.org>
Cc: "'PWG-pmp'" <email@example.com>
Subject: MIB typos?
Date: Thu, 26 Jun 1997 15:33:09 PDT
Content-Type: text/plain; charset="us-ascii"
I was looking at the Printer MIB and came across what appears to be a =
cut and paste error.
SYNTAX Integer32 (1..65535)
"A unique value used by the printer to identify this
localization entry. Although these values may change due to a
major reconfiguration of the device (e.g., the addition of new
Cover sub-units to the printer), values are expected to remain
stable across successive printer power cycles."
The "e.g., " refers to " the addition of new Cover sub-units to the =
printer". I'd be quite surprised that adding covers will cause more =
localization entries! How about something along the lines of "the =
addition of new localization code to the printer."
Also, Ira mentioned today that his printers have the ability to have =
localizations added. Ira, is that done while the printer is online? HP =
printers allow localizations to be added via a ROM SIMM, so it is =
powered down for the addition. If the printer does it live, then most of =
the "DESCRIPTION" should be deleted.