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



Eric,

I try that, does NOT WORK...

Unless I hard code my program name with ExtPgm('MPGM')

D Entry PR ExtPgm('MYPGM')
D 7 Const
D Entry PI
D Customer 4 Const

I usually code like this, but RDP 8.0.3 does not work with Outline view:
Since I use V7R1M0, I no longer code the optional "PR" prototypes, because they are NOT NEEDED! <Joy Joy>

D PI
D Customer 4 Const

Program compiles and runs perfectly. Just the RDP outline view does not work...
<Big Frown>

So, back to *ENTRY, and FREE-FORMAT for the rest...

Whoops, then the new %BIF %PARMNUM no LONGER works...
<big Frown>

I can't win!!! Unless I HARD-CODE the PROGRAM name in every program...

That is STUPID and redundant!!! (To hard-code the program name in the procedure interface.) Yes, I understand it might be need if bind multiple modules together. But, we use Service Programs. <Big Smile>


-Ken Killian-

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Thursday, October 18, 2012 10:45 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] *ENTRY vs. " PI " in RDP 8.0.3 problems with OUTLINE view

Try just using "ENTRY" in the name portion... You can name the program internally however you want, and I've used this syntax before to appease the search habits of other coders.

-Eric DeLong

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Thursday, October 18, 2012 9:05 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (wdsci-l@xxxxxxxxxxxx)
Subject: [WDSCI-L] *ENTRY vs. " PI " in RDP 8.0.3 problems with OUTLINE view

Hi,

Going forward, I am using the procedure interface the "PI" for my *ENTRY parameters.

But, I hate HARD-CODING the program name in the "PI"...

So, I leave it BLANK, and it compiles fine and executes as expected! Cool!

Now to back to RDP 8.0.3, it blows up when I try to create an OUTLINE view. It just crashes and ends RDP. No message, No Error, just ENDS...
<Big Frown>

I even tried to verify first. But that fails, because it wants me to HARD-CODE the Main procedure in the "PI" statement...

I guess I should go back to FIXED Format for *ENTRY parameter list...
<Disappointment>

PS. I understand when you have multiple modules, and you need to know the main interface. But, we mostly use Service programs.

Ken Killian
Senior ILE RPG Developer/C# .Net Developer in Training.
SoftLanding/TurnOver Administrator
--
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 ...

Follow-Ups:

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.