RE: creating a new procedure that callanexistingprocedurewithoneadditional parm

*OMIT forces a *NULL pointer to be passed.

That still counts as a param being passed.

So given

  MyProc(*omit:*omit:*omit)


 %parms would return 3.



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 Paul Morgan
> Sent: Wednesday, July 27, 2005 10:47 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: creating a new procedure that
> callanexistingprocedurewithoneadditional parm
> 
> 
> Barbara,
> 
> Would a %Parms check work with *OMIT?  You could use *OMIT on 
> a variable in
> the middle of the parameter list.  Does *OMIT force a null 
> pointer for that
> parameter?
> 
> 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
> 
> Barbara wrote
> 
> > You first have to check %parms to see how many parameters 
> were passed,
> > and then once you know a parameter was passed, you can check for the
> > address being null.
> 
> 
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (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.
> 
>