|
**SOAPBOX *ON** Hallaleua!!! (Sorry about the spelling). I too am a proponent of the RPG cycle. I still write matching record programs when the need arises. And do it all in RPG IV. Heck, the other day, I coded a program described file with a primary read and a data structure update. I feel that you use the tools that best allows you to do the job. If it is a 15 year old technique, so be it. ** SOAPBOX *OFF** ----- Original Message ----- From: R. Bruce Hoffman, Jr. <rbruceh@attglobal.net> To: <MIDRANGE-L@midrange.com> Sent: Monday, January 03, 2000 7:51 AM Subject: Re: COBOL VS RPG > More importantly, if you write reports in COBOL, you are essentially, > writing your own copy of the RPG cycle. The cycle exists because it is the > "right" way to do reports! > > Then again, most RPG programmer's today are told to NOT use the RPG cycle > and they then turn around and write their own cycle code anyway. > > Talk about a waste.... > > =========================================================== > R. Bruce Hoffman, Jr. > -- IBM Certified AS/400 Professional System Administrator > -- IBM Certified AS/400 Professional Network Administrator > > "The sum of all human knowledge is a fixed constant. > It's the population that keeps growing!" > > -----Original Message----- > From: PaulMmn <PaulMmn@ix.netcom.com> > To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> > Date: Sunday, January 02, 2000 7:12 PM > Subject: Re: COBOL VS RPG > > > >>At 06:10 PM 12/29/1999 -0600, you wrote: > > > >>Try converting the RPG cycle into COBOL. I'd rather give birth to the > >>Green Bay Packers, all at once, than attempt this. > > > >>Al > > > > > >I dunno--- many, many years ago we had 2 S/3/15/D machines. One shop was > >RPG, one was COBOL. I had occasion to write some COBOL programs from > >scratch, and I -did- code them using my own version of the RPG cycle. It > >made a -very- 'logical' program! > > > >Of course, that was back in the days when I could draw the complete RPG > >cycle from the debugging template in my sleep. (: > > > >--Paul E Musselman > >PaulMmn@Ix.netcom.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 > >+--- > > > > +--- > | 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.