OS Y2K Compiant

Neil,

Just in case the second reference to 'V3R1' below was intended to be
'Y2K', then let me assure you that V3R1 is NOT Y2K compliant (ready)
even with PTFs.  IBM does provide enablement PTFs to V3R1 so that
developers can start using attributes such as the QCENTURY system value,
the 4-digit year support of the Convert Date API, job attribute CYMDDATE,
etc. without having to upgrade to V3R2 in order to GET STARTED.  But
OS/400 INTERNALLY is not using unambiguous dates throughout.  That's
what V3R2 brings into the picture -- OS/400 internal compliance with
Year 2000.  Users will want to be on V3R2 (IMPI) or V3R7, V4R1,... (RISC)
come 1999/2000.

Bruce Vining

> ...
>V3R1 is supposedly V3R1 compliant with all the required PTF's but I
>would not trust that - go to V3R2.
> ...
>
>... Neil Palmer
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---