If you take the menu options "Source=>Convert All To Free-Form", I'm 
pretty sure the comments are converted to the **FREE** friendly version. 
Or you can select a section of code, right click and take the "Convert 
Selection To Free-Form" option to do the same.
Matt Hopkins 
Project Leader 
PDP Group, Inc. 
10909 McCormick Road 
Hunt Valley, MD 21031 
Office: 410.584.0330 
Fax: 410-584-0336 
Cell: 410.258.8845 
MWHopkins@xxxxxxxxxxxxxxx 
www.pdpgroupinc.com 
Confidentiality Notice: This email message is intended only for the 
individual or entity to which it is addressed. This email may contain 
information that is proprietary or privileged, confidential and exempt 
from disclosure under applicable law. If you are not the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you received this 
email by accident, please notify the sender immediately and destroy this 
email and all copies of it. 
From:   "Dan" <dan27649@xxxxxxxxx>
To:     "Rational Developer for IBM i / Websphere Development Studio 
Client for      System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date:   05/03/2018 12:01 PM
Subject:        Re: [WDSCI-L] Inline Syntax Checking
Sent by:        "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
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
"asterisk-asterisk-free".
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
members.
Eeek.  Maybe I'll just leave things alone for now.
Thanks Dan (and Ken)!
As an Amazon Associate we earn from qualifying purchases.