× 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 support@midrange.com.

Agree. I spent an hour making this function to consume a rest API fit and be somewhat readable in seu to go into turnover. It went from readable to looking like a code generator did it. 
On Wednesday, March 29, 2023, 10:22:44 PM CDT, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:

Source in the IFS is definitely the way to go in the long run.

There are a small handful of tools that still don't support IFS -- but
it's not hard to work around the problem (just a simple utility that
copies source to a temporary member during compile.)

For /copy books, I recommend having a place that's designated as the
location for any needed copybooks.  On the Unix system I work on, they
use /usr/include for copybooks included with the system, and
/usr/local/include for copybooks that are specific to your
installation.   If you use those locations (or designate your own) for
your copybooks, it's just one location to be sure you include.

Use relative paths for testing in development/test/qa environments (with
a copy of the copybook)

Then use the RPGINCDIR system wide to set up folders like /usr/include
and /usr/local/include and use paths relative to those for anything
available system-wide (i.e. things that aren't currently "checked out"
by the developer for making changes, etc.)

On 3/29/2023 3: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:

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

incText looks like this:
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

Any suggestions, comments, discussions welcomed.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.