|
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Douglas Handy Sent: Thursday, August 12, 2004 11:51 AM To: Midrange Systems Technical Discussion Subject: Re: IBM overhauls iSeries for the long haul Steve, >>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. >Can I assume you never worked on the S/32 or S/34? correct. such primitive technology, who could be bothered! >The S/38 most certainly did not run OCL, nor could the >RPG III compiler on the S/38 handle all RPG II constructs >such as a KEYBORD or CRT device file. I don't remember >if it handled a CONSOLE device or not. It also didn't >support MRT style programs without modification. >Nor could it handle WSU programs, etc. I stand corrected. Most of the places I worked were mixed 36/38/400 shops. The 36 people I worked with were all a lot of fun to work with. Very respectful of their 38 mentors who always found the time to help them out. >In short, it was *not* designed to run S/32 and S/34 programs. >It was designed to have your applications rewritten in RPG III. >It was much easier to port S/3 applications to the S/38 >than S/32 or S/34 applications. which explains why rpgIII had all that useless stuff in it. SPECIAL files, matching records, ... >>The 400 was really just the s/38 in new hardware. >If you did not need the S36EE, you may have that view. >I suspect lots of folks would beg to differ. But hardly any iSeries applications run in the 36 environment anymore. So we are back to running what was and is the System/38. Other than tcp/ip, I think only journaling and a more user friendly query have been added to os400 from what cpf had to offer. -Steve
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.