You don't have to worry about /copy members; the compiler handles that
automatically. For any comments with * in column 7, just add // somewhere
before it.

Also, in addition to **free, there is **end-free, which does what you think
it does. I believe this is undocumented and not supported, but I've used
it so that I could have output specs for a report in a program I created.
IBM uses it for embedded SQL code that it converts to fixed column RPG. I
suppose that, if **end-free went away, I'd have to put the O specs in a
/copy member.

- Dan

On Thu, May 3, 2018 at 10:58 AM, Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

OK now I see! :)

I stopped using the "slash-free" a long time ago. Somewhere I missed

I'm on v7r3 - just upgraded a few weeks ago. Have the latest TR.
Added **free as the first statement in one of my source members, but now
it doesn't like my comments where I used single asterisk in column 7. I
would have to change the comments in my source members and all the /copy

Eeek. Maybe I'll just leave things alone for now.

Thanks Dan (and Ken)!

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-2022 by 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.