Re: V3R2 life cycle

Even more sad is one of my clients that is "upgrading" to a Sys/36 model
5363 this fall.  His ultimate plan is to do it all on PCs.  That plan has
been shaping up now since he got his first PS/2 6 years ago.  So far the
migration is progressing smoothly.  He's already replaced "DisplayWrite"
with PC word processing. <vbg> 

On a side note: I've looked over his code and frankly, outside of a few
minor sorts, his Y2K problem has never existed.  Then again, we didn't
write any non-compliant code after 1985 anyway.

My point is, I guess, that even the old Sys/36 performs better in a group
setting then any PC network out there even now, in 1997.

on 07/31/97  at 10:57 PM, DAsmussen@aol.com said:


Like I've said before, do YOU want to wait as long

(almost 10 years) as the S/36 people did for new support from IBM just

because you know you're right?  The sad thing is that 36'ers can get Y2K

compliant hardware and OS, but that doesn't fix their applications, does

it?


JMHO,

-- 
-----------------------------------------------------------
boothm@earth.goddard.edu
-----------------------------------------------------------

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *