PMP Mail Archive: RE: PMP> prtAlertTime issue

PMP Mail Archive: RE: PMP> prtAlertTime issue

RE: PMP> prtAlertTime issue

Ira Mcdonald x10962 (
Fri, 6 Jun 1997 14:10:39 PDT

Hi Bob,

Yes, I agree with your wording below. This is consistent with
other practice where a 'TimeTicks' value is unknown.

I would observe that the source of 'prtAlertTime' is the
'sysUpTime' object in the (mandatory) System group in MIB-II
(RFC 1213), so of course nobody would be without an internal

- Ira McDonald (outside consultant at Xerox)
High North Inc

Return-Path: <>
Received: from by (4.1/XeroxClient-1.1)
id AA26275; Fri, 6 Jun 97 16:08:46 EDT
Received: from by (4.1/SMI-4.1)
id AA25544; Fri, 6 Jun 97 16:05:51 EDT
Received: from ([]) by with SMTP id <17935(4)>; Fri, 6 Jun 1997 13:06:04 PDT
Received: from localhost (daemon@localhost) by (8.7.5/8.7.3) with SMTP id QAA21026 for <>; Fri, 6 Jun 1997 16:02:08 -0400 (EDT)
Received: by (bulk_mailer v1.5); Fri, 6 Jun 1997 15:59:29 -0400
Received: (from daemon@localhost) by (8.7.5/8.7.3) id PAA20605 for pmp-outgoing; Fri, 6 Jun 1997 15:57:06 -0400 (EDT)
Message-Id: <>
From: Bob Pentecost <>
To: "" <>
Subject: RE: PMP> prtAlertTime issue
Date: Fri, 6 Jun 1997 12:52:25 PDT
Encoding: 39 TEXT
Status: R

When we discussed whether or not to make prtAlertTime mandatory, I was
assured by several committee members that there was a value that could be
provided if the value of sysUpTime was not available (for our printers it
is a case of sysUpTime being provided by the NIC and, as discussed for
several areas of the MIB, "the NIC doesn't know everything about the
printer and the printer doesn't know everything about the NIC").

Therefore, I request that wording be added as follows:
"A value of zero indicates the alert occurred at an unknown time."

Bob Pentecost

From: Randy Turner[]
Sent: Friday, June 06, 1997 11:18 AM
Subject: PMP> prtAlertTime issue

Lloyd referenced an earlier mail message by Bob Pentecost reflecting a
request by Bob as to
what value should be returned by a GET for prtAlertTime if the printer
didn't know the time.
Values for INTEGER types have (other) and (unknown) as possible values.
The 'TimeTicks'
object has no such equivalents. prtAlertTime is now mandatory, and is
based on sysUpTime
from MIB-II. If someone performs a GET on prtAlertTime (according the
curent definition),
then it MUST return a valid value. There are no alternative 'other' or
'unknown' scenarios
for an object like prtAlertTime, with type 'TimeTicks' that is based on
MIB-II sysUpTime.