Re: Premenos and the date data type window.

Bruce:
>
>Maybe I'm missing something, but if one does the right job now (that is,
>move to 4-digit years or their equivalent) then why would any additional
>work be needed in 2039?

If people use date formats with 4 digit years additional work will NOT be
needed in the year 2039.

>To continue using 2-digit years (and the 1940
>to 2039 window) is one way to "ease into 2000", but certainly isn't
>(to me anyway) a permanent solution; much like how I (personally) don't
>consider floating windows to be anything but a short term workaround.
>
>Why would you expect IBM to have to explain why developers took 2-digit
>approaches in the late 1990s in response to this problem?  Isn't this
>a matter of the user companies approach to the year 2000 (or at least
>how they prioritize this work against other items)?
>
There have been some sessions presented by IBM'ers at COMMON which
recommended the use of *MDY date data types.  I would suggest UNDER NO
CIRCUMSTANCES should anyone use a date format of *MDY, *DMY, *YMD, or *JUL.

Also, look at the problem with PDM.  We say the AS/400 is Y2K enabled but
PDM F17 subset will fail to function properly at some point in the future
without further modifications because it uses a 2 digit year.  It didn't
work at all without a PTF.

>Bruce Vining
>
>> >Charles L. Massoglia wrote:
>>
>> Date windows of 1940-2039, 1970-2069, or any other fixed window are us ed by
>> those who do not care if their code dies in the future.  I hope I am a live
>> in the year 2039 to see how IBM explains why we have to go through thi s Y2K
>> thing a second time in the same century.
>>
>


Charlie Massoglia, Massoglia Technical Consulting, Inc.
PO Box 1065, Okemos, MI 48854, USA
517-676-9700  Fax: 517-676-1006  EMAIL: cmassoglia@voyager.net


+---
| 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
+---