Hadn't noticed this Doug - but I'm not surprised.

I have found that RDi doesn't seem to like the / anywhere except in position 7.


On 2014-08-18, at 12:05 PM, "Englander, Douglas" <Douglas_Englander@xxxxxxxxxxxxx> wrote:


With free format H, F, and D specs, there is also the capability to have the /COPY statement not be restricted to beginning in column 7. That works fine for a normal RPGLE type program. However, when I move a /COPY statement to begin in column 9, and my source is type SQLRPGLE, the SQL Precompiler does not always seem to recognize the /COPY statement.

I have one program with 3 /COPY statements. One is by itself in one section of my D specs, and the other two are together in a subsequent section of D specs. The two begin in column 9 and there is no problem with the SQL compiler. However, when the first one is in column 9, the SQL precompiler does not recognize it, and it looks like it treats it as a comment. When I move that one back to begin in column 7, the precompiler recognizes the /COPY.

Has anyone else experienced this or know if there a PTF for this?

Thank you,

Doug

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.