Re: V3R2 life cycle(s)?

[Mark Bauman <mlbauman@xxxxxxxxxxxx>]

Glenn, 

Excerpts from mail: 31-Jul-97 Re: V3R2 life cycle(s)? Glenn
Ericson@att.net (2392*) 

> OK that is  -3- different  answers. 

> IBM are you listening  - What is the correct  reply here? 

I work for IBM however, I am not going to stand up and say which is the
correct reply - because there is not a general correct reply for every
situation.  I stated in a previous note on this subject, that all new
development is centered on RISC based machines.  Personally, I would try
to go with the latest and greatest.    However, each situation is
different and must be studied with all of the factors involved.  Hank
Heath states some of those factors very well in his note as follows:  

Excerpts from mail: 31-Jul-97 Re: V3R2 life cycle HankHeath@aol.com (2569) 

> One of the major implementation roadblocks in getting a world wide 
> organization on the bleeding edge is just coordinating the whole damned 
> thing. For instance, there is a major piece of software that they purchased 
> and modified a number of years ago. It is not certified for RISC, yet. Until 
> they get that taken care of, they can't just roll out an upgrade and pray for 
> the best. 

> Another issue is momentum. After going to the well a number of times for 
> upgrades within the CISC architecture, it is a difficult sell to go back, and 
> ask for another deep drink. 

> Then there is the competitive pricing within IBM that offers some real 
> advantages to staying on CISC.  

There are other factors too which have been stated by other participants
on this list.  All I can say is apply each of the factors to your
particular situation and then make a decision.  

Mark L. Bauman 
AS/400 Communications Development     


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