|
Glenn, Without any reference to any prior messages, my comment is that, "The future's so bright, together we're brilliant.". Yes, I do have a better than average view of the future of OS/400, and yes I'm 50. But I'm planning on working on this platform until I die (I had three out of 4 grandparents die over age 90 [both grandfathers worked over 90]), or until about 20 minutes after my funeral. Instructions left indicate that my eulogy should be about the work management. System Values will live longer than me! Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Glenn Ericson <Glenn-Ericson@xxxxx To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, "Midrange et> Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent by: cc: midrange-l-bounces@x Subject: Re: Planning for an iSeries future idrange.com 04/21/2003 10:54 PM Please respond to Midrange Systems Technical Discussion Are you referring to the demise announcement or the announce/availability announce . The latter was here at V4R4 time At 03:35 PM 4/21/2003 -0500, Shannon O'Donnell wrote: >The demise of the 700 series has been known for about 18 - 24 months now, >give or take a couple of months. Seems like the 700 series announcement was >made around the same time V5R1 came out. If I remember correctly, Midrange >Server (www.midrangeserver.com) wrote about this back in September or >October of 2001. Heck, I even remember hearing about this while working at >Midrange Computing magazine before it closed, so I know that it's been quite >awhile that this information has been known. > >HTH > > >Shannon O'Donnell > > >----- Original Message ----- >From: <rob@xxxxxxxxx> >To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> >Sent: Monday, April 21, 2003 2:31 PM >Subject: RE: Planning for an iSeries future > > > > Was January 24 really the first date you could plan on this? What about > > the web site which lists the life expectancy of hardware and software for > > the iSeries? When was that updated with the planned demise of the 730? > > > > I've got to give IBM a lot of credit for this site. They used to be a lot > > more closed mouth on hardware and software. > > > > All January 24 did was tout some new equipment, and packaging, that would > > (might) be cheaper and less expensive than the models they are replacing. > > You can probably count on IBM doing that on a somewhat annual basis. > > > > Rob Berendt > > -- > > "They that can give up essential liberty to obtain a little temporary > > safety deserve neither liberty nor safety." > > Benjamin Franklin > > > > > > > > > > "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx> > > Sent by: midrange-l-bounces@xxxxxxxxxxxx > > 04/21/2003 01:15 PM > > Please respond to Midrange Systems Technical Discussion > > > > To: "'Midrange Systems Technical Discussion'" > > <midrange-l@xxxxxxxxxxxx> > > cc: > > Fax to: > > Subject: RE: Planning for an iSeries future > > > > > > Ken, > > > > Your upgrade loss occurred with an announcement on January 24 of this > > year. Considering that this is a major incentive to upgrade and > > considering that many companies budget by calendar year, this is really > > short notice and you should not place too much blame on your company. > > No, you're not the only one. I'm aware of a few large companies who are > > really ripped at the short notice. > > > > Regards, > > Andy Nolen-Parkhouse > > > > > On Behalf Of Graap, Ken > > > Subject: RE: Planning for an iSeries future > > > > > > I was wondering .... As we talk about the situation with my AS/400 > > > Model > > > 730/2C6F/2068/1510... > > > > > > Is there anyone else who is in the same situation I find our company > > > in? > > > That is, being on a 730 and facing the dilemma of losing the upgrade > > > path to > > > the 8xx boxes as of October 2003? > > > > > > Or is our company the only company that has allowed this to happen? > > > > > > Did everyone else upgrade to 8xx last year? > > > > > > Kenneth > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.