|
midrange.com
But what about all of those people running V1R2 of OS/400? How many people
still haven't upgraded because they have to be able to compile down to
V1R2? I don't think I'd want to bet the future of a software company on
the marketing potential of V1R2 clients. Sooner or later V3R2 will be in
the same bandwagon as V1R2. And I wonder why people could upgrade to V3R2
and can't go past that? I am not talking the obvious - because of the
hardware. I am talking why didn't they just stay on V1R2 and what not?
Surely there must have been some cost involved upgrading from V1R2.
I've seen so many people argue that IBM is slaying themselves by not
supporting ancient versions of the OS, like V3R2. Then these people leave
the crappy employers they work for and get a newer machine, and some
education and never go back to that argument. I think this list has a
regular contributor who marketed some S/36 tools and just ranted and raved
about how IBM screwed up royally when they came out with the 400. But I
don't hear him arguing that point anymore.
Rob Berendt
==================
Remember the Cole!
Scott Klement
<klemscot@klements. To: MIDRANGE-L@midrange.com
com> cc:
Sent by: Subject: Re: FTP on V3R2
owner-midrange-l@mi
drange.com
03/19/01 02:36 AM
Please respond to
MIDRANGE-L
On Fri, 16 Mar 2001 rob@dekko.com wrote:
>
> Have fun. My 'dead horse' comment was regarding V3R2. Of which V4R5
will
> be the last release which can compile down to that level. Which will
make
> many software companies make a decision:
> 1) Abandon customers running V3R2
> 2) Keep an older machine to compile down to that level
> 3) Not upgrade.
>
>
IMHO, Option #3 is the "correct" solution. It's the only one that might
help discourage IBM from dropping support for things.
It never ceases to amaze me that IBM is still supporting the Sys/36
environment, but not supporting the entire line of CISC machines.
(Of course, now that I've got a RISC box, I'll probably stop complaining)
+---
| 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.
