RE: creating a new procedure that callanexistingprocedurewithoneadditional parm

I think it depends on what happens to be in memory at a particular location.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Lim Hock-Chai
> Sent: Tuesday, July 26, 2005 3:39 PM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: creating a new procedure that
> callanexistingprocedurewithoneadditional parm
> 
> 
> Sometime it work.  Depending on you luck.  May be Barbara can 
> explain more.
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Morgan
> Sent: Tuesday, July 26, 2005 2:21 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: creating a new procedure that call
> anexistingprocedurewithoneadditional parm
> 
> 
> Lim,
> 
> I wasn't sure either but it worked for me in a small test 
> program I mocked
> up to check.
> 
> Paul
> 
> -- 
> Paul Morgan
> Senior Programmer Analyst - Retail
> J. Jill Group
> 100 Birch Pond Drive, PO Box 2009
> Tilton, NH 03276-2009
> Phone: (603) 266-2117
> Fax:   (603) 266-2333
> 
> Lim wrote
> 
> > I don't think that is a true statement.
> >
> > If a parm is not passed, the *omit field may or may not be 
> null.  Never
> understand why IBM design it that way.
> 
>