Subject: | |
From: | |
Reply To: | |
Date: | Mon, 4 Jan 1999 14:33:13 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Recently in response to another post on 3000-L I said:
> ...... I just went and looked at the structure of the
> DICT/3000 database (it is standard TurboIMAGE), and sure
> enough: DATE-CREATE and DATE-CHANGE are pervasive
> in almost all the datasets in the DICT database; they are both
> YYMMDD X6....
HP responded to my above on [log in to unmask] Since users
of the RAPID products are not the only ones who use DICT/3000,
FYI for any who care; and because at least one third-part vendor
has apparently been saying that DICT/3000 is not Y2K compliant;
I forward HP's response to this list. Kelly Sznaider said:
> Dictionary/3000 was modified to handle year 2000. The dates are in
> the form of YYMMDD. No changes will be made to include the century.
> These dates are basically for auditing purposes. Each transaction is
> date stamped and displayed with the appropriate command. No "real"
> processing happens with the date fields in Dictionary or the
> Dictionary utilities. All these programs have been tested according
> to HP's Y2K compliance.
>
> Dictionary is Y2K compliant as of version A.03.01. You can get this
> version via MPE/iX 5.5 PowerPatch 6 or MPE/iX 6.0 or call the response
> center for patch DICKXD5.
>
> Regards,
> Kelly Sznaider
> Hewlett-Packard
Since no operations are performed on DATE-CREATE and
DATE-CHANGE, the above sounds reasonable to me....
Ken Sletten
|
|
|