>Wasn't the RPG cycle developed for the S/360 before the days of S/3????

I believe you are correct, however my S/360 experience was limited to
COBOL, FORTRAN and Assembler in college.  There was no RPG in my school
(RPI), but that makes my school no different from virtually every other
school today.
>> On a System/3 Model 6, the difference in using the cycle, or not
>> was the difference in getting the program to fit into 5K or not!!!!!
>Hmmm... I remember the S/3 models as 8, 10, 12, 15, 15D.  The _super_
>15D could run TWO programs CONCURRENTLY!!!!!   WOWSIE!!!!!  :^)
>Anyway, what was the model 6?  Card only?  Were there others?

The first two models of the S/3 were models 6 and 10.  Model 6 was to be
card only (our's never had cards!) and 10 was to be disk only.  Our model 6
had an IPL run deck!, not that we had a card reader.

There was also a model 4, which was a souped up model 6 with CCP,  It
didn't sell very well.  

One day, I was having performance problems, so a substitute CE came in, and
said that I needed to have the disk heads aligned.  Within ten minutes
after he left, I had three disk failures!  Those three disks (with visible
scars) are mounted outside my computer room today.


Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406

Private mail should be sent to barsa@ibm.net
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].