|
I think that the earliest RPG implementation was on 360 in the 60s although I did work on an 1130 running RPG in 1977. The input device was usually a 2540 MFCM. I don't think that IBM supports a card reader any more - on any system. The earliest Rochester RPG implementation was a System/3 mod 2 or 4 or some such that bore a fairly strong resemblance to a 1620. The first machine had some little tiny memory [like 8k] and was pre-announced to support RPG. Unfortunately, the compiler writers couldn't shoehorn RPG into the tiny memory. So the littlest model never saw the light of day. Those systems used a 96-culumn square card that didn't even make a good book mark. I think that the System 38 supported a 96-column card reader but the 400 never did. [Anecdote courtesy of one of the original Rochester RPG developers as told to me in the late 1970s in at Parts Warehouse Alaska in Anchorage Alaska] Richard Jackson mailto:richardjackson@richardjackson.net www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -----Original Message----- From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On Behalf Of Gene_Gaunt/ReviewWorks@reviewworks.com Sent: Tuesday, July 11, 2000 7:02 AM To: MI400@midrange.com Subject: RE: Parm identification routine... Steve's DSPPARM program can rout out hidden exit points like the one that OPM RPG/400 calls when compiling a device type of ^^^^ (four uppercase 6's) in an F-spec columns 40-43 like the following. FINPUT IF F 80 ^^^^ IINPUT NS 01 C READ INPUT LR Do you think this code makes the compiler return fatal error QRG2013, "The Device-Type entry is not PRINTER, DISK, WORKSTN, SPECIAL, or SEQ" ? No, this code makes the compiler fail with MCH3401, "Cannot resolve to object CARDFILE. Type and Subtype X'0201' Authority X'0000' ". Okay, lets rename Steve's program into CARDFILE in our library list. Now compile the OPM RPG/400 again and the compiler fails with CPF6301, "Intermediate representation of program (IRP) contains 11 errors." My point here is entertainment (not a bug report, jeez guys) but maybe another MI400er knows the history of this fossil CARDFILE. +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +--- +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.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.