RE: IBM overhauls iSeries for the long haul

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

The S/38 could run RPGII programs.  I am not sure about the s/38 running
ocl, but the system was designed to run s/32 and s/34 applications.  It is
just that the s/38 was so much more expensive than the s/34 that it made no
sense to migrate a s/34 application to the s/38.    The 400 was really just
the s/38 in new hardware.

-Steve

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pat Barber
Sent: Thursday, August 12, 2004 10:06 AM
To: Midrange Systems Technical Discussion
Subject: Re: IBM overhauls iSeries for the long haul


More than you can imagine. Since there was far more S/36
installed than S/38(50 to 1, maybe much higher), you gotta
imagine many of those folks never bothered to convert to
"native".

I have several customers who never bothered and never asked
to be converted once they saw that the 400 could handle
their software "as is".

  Many have converted over the years, but some still run a few
applications just as they were on the S/36. The S/36 customers
are the reason the 400 exists today in my opinion.

I don't believe "anybody" including IBM, has any idea how
much S/36 code still runs. Remember the S/36 was wildly
popular in other countries other than the USA.

Of course IBM also didn't think many people were using
OV/400.

Shields, Ken wrote:


That's another reason why IBM, rushed to put the Sys/36 out in the market.
The S/36 was so popular, that even to-day, on the current release of OS400,
the Sys 36 Environment is still supported.

I'm very curious to know just how many companies are still using the
S36 Environment.


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