When I run a Verify, it reports an error on the PI not having a name. But when I compile it works. I've opened a PMR for this.
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 Anderson, Kurt
Sent: Tuesday, March 04, 2014 5:20 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.0.0.1 parser not handling extdesc keyword correctly.
Well what do you know, it worked. I guess it's one of those things I thought you had to do.
Thanks for the response. I like this very much.
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 Ken Killian
Sent: Tuesday, March 04, 2014 4:55 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.0.0.1 parser not handling extdesc keyword correctly.
I do NOT like Hard-Coding the program name...
I do a PI, Procedure-Interface like this:
// ===============================
// *Entry Parameters
// ===============================
Dcl-pi *N;
OrdNbr Zoned(7);
END-PI;
I didn't hard code for the Old Fixed format *ENTRY, so I do NOT do it for the new Free Format either...
If you prefer the Fixed format, you can do it like this:
// ===============================
// *Entry Parameters
// ===============================
d pi
d OrdNbr 7s 0
Why Hard-Code the Entry Parameters. Unless you are binding multiple modules together? Normally, I use Service program for commonly used sub-procedures...
For internal Sub-procedure, the Prototypes are now Optional, so I remove them! Of course they are needed for External program calls...
-Ken Killian-
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
Sent: Tuesday, March 04, 2014 4:29 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.0.0.1 parser not handling extdesc keyword correctly.
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.
--
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.
midrange.com
