Re: Source in the IFS

I once worked on a project that had a significant amount of vendor provided source code in the IFS.

My experience was;  it was difficult to work with.

It's outside the norm of having source in PF-SRC files and traditional tools can't be used with the IFS source.
Based on my experience, I wouldn't recommend storing source in the IFS.

We use QCPYSRC files for code that is copied into multiple programs.

Another method of "copying" is to create ILE *MODULES of common routines or logic.   Then, you can include any of those modules in your program during binding (Using a *BNDDIR).
This way, you're binding together object code instead of copying source code.

Good luck,

Gavin.

On 3/29/2023 4:46 PM, Sam_L wrote:
I'm experimenting with putting source in the IFS. Would like sone input.

1) Do you miss the text on the source and the created object?

2) What's the best way to handle /COPY of utilities shared between projects.

I don't want want to hard code the /COPY file, or use an RPGINCDIR environment variable, or specify an INCDIR on the CRTxxx command.

Using path name relative to the source file directory seemed best.
For testing I created a directory structure like this:
/HOME
    MyName
        MySourcE
            Copy_Mbrs
        incText.rpgle
            Proj1
        TestInc.rpgle

TestInc looks like this:
**free
/include ../Copy_Mbrs/incText.rpgle
dsply theMsg;
*inlr = *on;
return;

incText looks like this:
**free
dcl-s theMsg char(30) inz('Hello included text');

Which compiles quite nicely. But is this the best way?

This is for my personal projects on PUB400, so no source management packages.

Any suggestions, comments, discussions welcomed.