• Subject: Re: The 1972 Y2K fix
  • From: Glenn Ericson <Glenn-Ericson@xxxxxxx>
  • Date: Sat, 04 Sep 1999 06:49:09 -0400

V3R2  is  the min  level for CISC  machines to  be Y2K  prepared.
The encapsulation process /theorymentioned is  for applicatrion code use.

At 10:41 AM 9/4/99 +1200, you wrote:
>Im running V2R3 at home on my E20 and V3R1 on my model200.So if I do a IPL
>and set the system time back to 1972 will this work?Since these are only
>home machines to learn on-its not viable to buy V3R2 under these
>circumstances.
>Dave
>
>----------
>> From: Jim Langston <jlangston@conexfreight.com>
>> To: MIDRANGE-L@midrange.com
>> Subject: Re: The 1972 Y2K fix
>> Date: Saturday, 4 September 1999 05:40
>> 
>> Actually, that is similar to the way my company is doing it, they call it
>> "encapsulation" or something like that.
>> 
>> You subtract 28 years from all the dates, because 28 years ago the
>> calendar was the same as it is today.  Then everywhere you input or
>> display a date you subtract or add 28 years to it, so the user never
>> knows.
>> 
>> Gives you 28 years to do a real conversion, anyway 8-)
>> 
>> Regards,
>> 
>> Jim Langston
>> 
>> "Arnold, Robert" wrote:
>> 
>> > I'd like to know if anyone else is planning on following my previous
>> > employer's solution to the Y2K problem?  He is planning on re-dating
>the
>> > dates in physical files to 1971 and prior.  Then setting the system
>date
>> > back to January 1, 1972.   They will modify several printed forms to
>> > indicate the new millenium.
>> >
>> > Some background information:  The company was recently re-acquired from
>a
>> > bank foreclosure.  The system is an F45 V2R3, running CA's PRMS V8.2F. 
>They
>> > have the Y2K compliant version 8.4, just no time to implement the
>solution.
>> >
>> > It's not a decision I support but, I wanted to get some other opinions
>since
>> > I have numerous friends and colleges still employed, for the time
>being.
>> > +---
>> > | This is the Midrange System Mailing List!
>> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>> > | To subscribe to this list send email to MIDRANGE-L-SUB@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
>> > +---
>> 
>> +---
>> | This is the Midrange System Mailing List!
>> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>> | To subscribe to this list send email to MIDRANGE-L-SUB@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
>> +---
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@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
>+---
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].