RE: QRPGSRC vs. QRPGLESRC

[rob@xxxxxxxxx]

Sometimes those PHB's drive you crazy.  I suppose some people might 
comment that at least she allows you to use RPGLE.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Malchow, Grizzly" <GMalchow@automaticproducts.com>
Sent by: midrange-l-bounces@midrange.com
01/21/2003 12:06 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        RE: QRPGSRC vs. QRPGLESRC


I brought that up to my boss and the that idea didn't fly. My boss only 
wants to do the RPG programs. 

-----Original Message-----
From: MCPARTLAND, Stan [mailto:stanley.mcpartland@bently.com] 
Sent: Tuesday, January 21, 2003 10:34 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QRPGSRC vs. QRPGLESRC


I recommend keeping all of your source (RPG, RPGLE, CL, CLLE, DDS, ...) in 
a single source file.  Current tools work much better with a single source 
file.  Source files separated by source type is a hold over from the 
System/38's programmer's menu which automatically switched source file 
depending on the source type you were processing.

Regards,
Stan

-----Original Message-----
From: Malchow, Grizzly [mailto:GMalchow@automaticproducts.com]
Sent: Tuesday, 21 January, 2003 7: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.