RE: QRPGSRC vs. QRPGLESRC

  There is no good reason why you should do this. (imho) As a matter of
fact, I'd recommend that you put ALL your source in one source file.
Especially if you have good naming standards for your source.  For instance,
if you have a program named PGM025R,  The CL that runs it is named PGM025J,
the command to start it is PGM025C, It has a display file named PGM025S and
print files named PGM025P1 and PGM025P2.  
  If you have all these members in one source file, (I name mine QSRC, makes
things simple) then when you're working on the program, and making changes
to the display file and the print files, you don't have to move from source
file to source file just to do what needs to be done.  Also, everything
associated with that program, is right there, in alphabetical order.
  It's just one of those things that makes life easier.

Duane

> -----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.