Are you suggesting that 'JmTimeStampTC' be changed to units of
'TimeTicks' like 'sysUpTime' (in MIB-II)? I think the rationale
for units of seconds was to avoid the appearance of demanding
accuracy in 'TimeTicks' for processing info on print jobs,
which is unlikely to be of use to client applications anyway.
Separately, by a poor design decision, TimeTicks was made a
fundamentally different syntax (over-the-wire) in SMIv1 and
SMIv2, so that it CAN'T be stored in an 'INTEGER' type
(in the job attribute table). So if we change the units
of 'JmTimeStampTC' to hundredths of a second, we STILL
need the TC, to avoid trying to use ACTUAL 'TimeTicks'
syntax for job attributes.
Does your implementation team think we should align the
units? While an SNMP agent may know time in 'TimeTicks',
a print language interpreter may NOT have available
such accuracy (to supply the values for job attributes).
Cheers,
- Ira McDonald (outside consultant at Xerox)
-------------------------- Harry's note --------------------------
Return-Path: <jmp-owner@pwg.org>
Received: from zombi (zombi.eso.mc.xerox.com) by snorkel.eso.mc.xerox.com (4.1/XeroxClient-1.1)
id AA18594; Mon, 13 Oct 97 19:44:45 EDT
Received: from alpha.xerox.com by zombi (4.1/SMI-4.1)
id AA11908; Mon, 13 Oct 97 19:40:33 EDT
Received: from lists.underscore.com ([199.125.85.31]) by alpha.xerox.com with SMTP id <52105(5)>; Mon, 13 Oct 1997 16:40:32 PDT
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id TAA05791 for <imcdonal@eso.mc.xerox.com>; Mon, 13 Oct 1997 19:37:09 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Mon, 13 Oct 1997 19:36:13 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id TAA05674 for jmp-outgoing; Mon, 13 Oct 1997 19:35:22 -0400 (EDT)
From: Harry Lewis <harryl@us.ibm.com>
To: <jmp@pwg.org>
Subject: JMP> jmTimeStamp
Message-Id: <5030300012186609000002L092*@MHS>
Date: Mon, 13 Oct 1997 16:40:42 PDT
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: jmp-owner@pwg.org
Status: R
We've run into an observation, here, regarding the units and range of T=
imeStamp
(seconds) and the range of sysUpTime.
The jmTimeStampTC can count to appx 68 years, in seconds, while sysUp=
Time
represents time in 100ths of a second and, resets appx every 1.36 years=