Re: Calling similiar (overloaded) procedure that has *nopass *omit inthe parameter

ok. A big select statement is what I've being doing. Just want to make
sure that there isn't any latest greatest technique that I might have
missed. The real proc1 and proc2 actually have 16 *nopass/*omit parameters.
Is going to be ugly...

Note: Parm1 is not a concern. That is just an example.

thanks

"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote in message
news:mailman.32963.1299610616.2702.rpg400-l@xxxxxxxxxxxx...
There isn't an easy way...since RPG doesn't offer true null support...

Proc1 will be (big) select statement that determines which way to call
Proc2...

Parm1 is also going to be problamatic since it's not defined CONST or
VALUE...are you really using it for output?

Charles

On Tue, Mar 8, 2011 at 11:44 AM, hockchai Lim
<lim.hock-chai@xxxxxxxxxxxxxxx> wrote:

Assuming that proc1 is an overloaded procedure of proc2. Proc1 contains no
business logic. All it does is converting the parm1 into alpha and calls
proc2. As you can see, both parameter 2 & 3 in proc1 & proc2 are *nopass
and *omit type parameters. Can someone give me a pointer on best approach
on calling proc2 from proc1?



D proc1 pr
D parm1 10p 0
D parm2 10 options(*nopass :*omit) const
D parm3 10 options(*nopass :*omit) const

D proc2 pr
D parm1 10
D parm2 10 options(*nopass :*omit) const
D parm3 10 options(*nopass :*omit) const


--
This is the RPG programming on the IBM i / System i (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.