× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Ray,
I'm with you. I've been programming in RPG 4 for a little over 4 years and if 
it were up to me, I'd convert ever piece of RPG 3 code we have to RPG 4. Then I 
wouldn't mind sticking it into once source file.
Griz

-----Original Message-----
From: Shahan, Ray [mailto:rshahan@SchoolSpecialty.com] 
Sent: Tuesday, January 21, 2003 9:53 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QRPGSRC vs. QRPGLESRC


Because RPG 4 is very much different than RPG 3 (or RPG400 if you prefer), and 
for that reason alone, it should have it's own file ( as does COBOL). It's the 
reason the standard exists.

Of course, this answer is coming from a newbie...  :-)



Ray Shahan

"Life is what happens while you're busy making other plans", John Lennon 

> -----Original Message-----
> From: Malchow, Grizzly [SMTP:GMalchow@automaticproducts.com]
> Sent: Tuesday, January 21, 2003 9:18 AM
> To:   midrange-l@midrange.com
> Subject:      QRPGSRC vs. QRPGLESRC
> 
> I'm supposed to create a source file named QRPGSRC that will be hold 
> all of source files, both RPG and RPGILE. I've always kept the 2 
> source members in seperate source files. I.E. QRPGSRC and QRPGLESRC. I 
> know QRPGLESRC has a longer record length. I'm supposed to create a 
> QRPGSRC with a record lenght of 112. Everywhere I've been before has 
> always kept the sources seperate. I don't think it's necesarily a good 
> idea. I need a good reason to explain why we should not do this, other 
> than industry standards, the differences in the code etc. 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To 
post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or 
change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.