RE: QCLSRC, QRPGSRC, etc... best practice?

Just started following this thread.
Many of our source programs include copy source from various 3rd party products.
Every 3rd party may not follow the same source rules.
Source is stored within a library for that product.
Sometimes, an upgrade of a 3rd party product may require us to recompile to include their updated copy source.

MAILTOOL/QCOPYSRC,P.MAILTO
RXS/QRPGLECPY,RXSCB
QRPGLETPL,BCKPGM14
QSYSINC/QRPGLESRC,QUSEC
QRPGLESRC,PSDSPGM

Paul


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Monday, October 29, 2018 2:45 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: QCLSRC, QRPGSRC, etc... best practice?

I was afraid of that.

Let me repeat that back with different words.

If all my source, including CPYSRC, is in QDEV and I am promoting only
objects then I can write /COPY QDEV,CPYSRC?

If promoting the source for recompile then I must know the target file
name of the CPYSRC; and an added crucial step is mandated?

That seems awkward but workable; *FILE would be an easier default.  imho.


On 10/29/2018 1:10 PM, Buck Calabro wrote:

... mysrc custmake - Build the Customer application from source

Inside mysrc custinqr, you'd have
/copy mysrc,custcpy
...