The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact email@example.com.
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
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
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:
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.