Re: V3R2 life cycle

[DAsmussen@xxxxxxx]

Booth,

In a message dated 97-08-02 11:20:56 EDT, you write:

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

Ahhh, but the 5363 itself isn't Y2K compliant!  Even my most stodgy client
replaced their 5363 with an A/36 this year...

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

For the most part, you're right.  The problem is that most /36 applications
are NOT Y2K compliant.  The /36 is a good platform, I just don't want to work
on it anymore...

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"It's a rare person who wants to hear what he doesn't want to hear." -- Dick
Cavett
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *