× 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.



Kurt,

I'm not saying it isn't valid syntax...

But it doesn't make sense for the RDi outline parser to treat it as literal
without actually having the quotes there.

That's what was weird. The fields/record name being pulled in was from
KORITDOR_2 even though I didn't have the quotes.

Charles


On Tue, Mar 4, 2014 at 4:29 PM, Anderson, Kurt <KAnderson@xxxxxxxxxxxx>wrote:

Your ExtDesc is valid syntax. But since you didn't make it a literal, the
compiler thinks it's a variable. So when you tried to compile, it couldn't
find the variable it was referring to. Though maybe you already realize
that.

It would make sense for the verifier to pick up the error. Another
common compile-time error missed by the verifier is having the wrong
program name on the PI for the program. (If my program name is ProgramB
and I copied my source from ProgramA and did not change the PI to ProgramB,
the verifier won't pick up the error, but a compile will.)


Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Charles Wilt
Sent: Tuesday, March 04, 2014 3:04 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] RDi 9.0.0.1 parser not handling extdesc keyword
correctly.

Had a file defined as so:
FKORITDOR UF A E K DISK extdesc(KORITDOR_2)
F extfile(*EXTDESC)
F rename(KORITDOR_2:KORITDO1)

RDi was perfectly happy with it. Live and static parser both showed the
file and fields properly in the outline.

However, my CRTBNDRPG failed with an error
RNF2572 - The parameter for the EXTDESC keyword is not valid

You have to quote the file name since it's a literal in this case...

FKORITDOR UF A E K DISK extdesc('KORITDOR_2')
F extfile(*EXTDESC)
F rename(KORITDOR_2:KORITDO1)

Any of the IBM's on this list want to confirm that this is not a known
issue and I should open an APAR?

Thanks!
Charles
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.