RE: QRPGSRC vs. QRPGLESRC

[Emilio Padilla - Sistemática Int. <EPADILLA@xxxxxxxxxxxxxxxxxx>]

Well, what I do is create 2 source file.   I name them QPEPSRC and QUEPSRC.
Both of them are created with 114 character length.  this way I keep all the
PEP sources on one of them (QPEPSRC) and the all the UEP sources on the
other one.  That way, I don't have to keep track of which module goes where.


Then, just create a BNDDIR with all the UEP modules.  [You could use an
shortcut on pdm for addbnddire, ADDBNDDIRE BNDDIR(bnddir) OBJ((&N *MODULE))]

If I have to recreate the whole application. All I do is pdm option 15 on
the UEP and PEP modules. 
Then I run a pdm option [CRTPGM PGM(&O/&N) MODULE(&N) BNDDIR(*LIBL/bnddir)
ACTGRP(*CALLER)] on the PEP modules.

This has made my compiling times a lot easier.   

PD I know there are going to be exceptions, but I do treat them one by one.
<bg> :D

Emilio

> -----Original Message-----
> From: rob@dekko.com [SMTP:rob@dekko.com]
> Sent: Tuesday, January 21, 2003 10:34 AM
> To:   Midrange Systems Technical Discussion
> Subject:      RE: QRPGSRC vs. QRPGLESRC
> 
> How does separating them help manage the source?  I think it hinders it.
> 
> 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 11:12 AM
> Please respond to Midrange Systems Technical Discussion
>  
>         To:     "Midrange Systems Technical Discussion" 
> <midrange-l@midrange.com>
>         cc: 
>         Fax to: 
>         Subject:        RE: QRPGSRC vs. QRPGLESRC
> 
> 
> Might as well include the CL source while I'm at it. It just doesn't make 
> any sense to me. I think it's poor source management. 
> 
> -----Original Message-----
> From: Tyler, Matt [mailto:mattt@wincofoods.com] 
> Sent: Tuesday, January 21, 2003 9:37 AM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: QRPGSRC vs. QRPGLESRC
> 
> 
> There is no real good reason except for many commands default to 
> QRPGLESRC. Just make a new QRPGSRC with 112 length and store both types of
> 
> RPG there. RPG III compiler will accept the longer length. 
> 
> Thank you,
> Matt Tyler
> WinCo Foods, Inc
> mattt@wincofoods.com
> 
> -----Original Message-----
> From: Malchow, Grizzly [mailto:GMalchow@automaticproducts.com]
> Sent: Tuesday, January 21, 2003 08:18
> 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.