|
They were in use at remote offices. I had offices that only had 2 - 3 employees. they ran there own warehouses. The systems were originally used with a lease line and connected to our main system. They were upgraded when we purchased our model 200 at V3R2 and they had distributed license? I think that was the term. they both have network cards and are in place out our main office just as a storage for the remote offices data. ----- Original Message ----- From: <rob@dekko.com> To: <MIDRANGE-L@midrange.com> Sent: Tuesday, March 20, 2001 12:20 PM Subject: Re: FTP on V3R2 > > And what was the business case for upgrading the operating system on those? > > Rob Berendt > > ================== > Remember the Cole! > > > > "Scott Swaim" > <sswaim@qualitycorp To: <MIDRANGE-L@midrange.com> > s.com> cc: > Sent by: Subject: Re: FTP on V3R2 > owner-midrange-l@mi > drange.com > > > 03/20/01 11:50 AM > Please respond to > MIDRANGE-L > > > > > > > I currently still have a B-10 and a B-20 up and running. Both are at V3R2 > > > ----- Original Message ----- > From: "Scott Klement" <klemscot@klements.com> > To: <MIDRANGE-L@midrange.com> > Sent: Tuesday, March 20, 2001 10:22 AM > Subject: Re: FTP on V3R2 > > > > > > I wasn't aware that the B10 couldn't run V3. We had a B35 running V3 at > > one point, so I assumed that all the B-series would upgrade to V3. > > If they truly left B10 users high and dry, then YES I think IBM was > > foolish in that decision. > > > > My original point, however, was that if you don't like IBM's decision to > > do something like this, the correct response is "I won't upgrade". In > > other words, if you're not pleased with one of IBM's decisions, you > > shouldn't encourage that decision by giving IBM money. > > > > Naturally to people like you who don't mind these decisions, you should > > continue to buy the upgrades. > > > > > > On Tue, 20 Mar 2001 rob@dekko.com wrote: > > > > > > And what is the highest release you would run on a B10? I once argued > > > against upgrading one special purpose 400 (E04) from V2R3 to V3 because > of > > > the huge disk eating size of the database cross reference files which > first > > > came out in V3. QADBIFLD on 1 of our 400's is 1.8gb. So take this > highest > > > version you would put on a B10, and if it is less than V3R2, then in > your > > > opinion did IBM shoot themselves in the foot long ago by dropping a > whole > > > class of machines which were serving their purpose? And yes a B10 is a > > > fair comparison to some of the larger CISC machines. Just compare the > > > performance of the latest RISC machines against these same CISC > machines. > > > > > > Rob Berendt > > > > > > ================== > > > Remember the Cole! > > > > > > > > > What bothers me is not the dropping of support for old releases, but > > > rather the dropping of support for CISC machines that are still working > > > just fine and serving their purpose. > > > > > > I think its unfortunate that V3R2 is the most recent release for CISC > > > machines -- but since it is, it should not be dropped. > > > > > > And thats the difference between dropping support for V1R2 and V3R2. > > > When you drop V3R2 you drop an entire hardware platform. > > > > > > > > > > +--- > > | 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 +---
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.