RE: %addr <> *null vs %parms >= ?

Yes, you have to use the %PARMS built-in to check the parm count (always a
good programming practice, regardless).  You can't pass *NULL for the
parameter anyway.  The closest you can come is allow *OMIT to be specified
by changing your OPTIONS keyword to include *OMIT. Then you check the
address of the parm for *NULL, again, only after verifying with %PARMS that
a value was indeed passed.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Lim Hock-Chai
Sent: Thursday, August 05, 2004 3:48 PM
To: RPG programming on the AS400 / iSeries
Subject: %addr <> *null vs %parms >= ?

If the prototype for the export procedure in a service program is as below:
D $get905PgmAut   pr                       
D  userID                       10    value
D  pgmNam                       10    value
D  autToAdd                       N        
D  autToUpd                       N        
D  autToDlt                       N        
D  autToPgm                       N   OPTIONS(*NOPASS)

Should the following two if blocks get the same result?
If    %addr(autToPgm) <> *null
 ... do someting
endif
 
if    %parms >= 6
... do something
endif
 
 
I getting the Pointer not set for location referenced error when using
%addr.  However, It does not happen all the time.  Sometime it work.
Sometime it doesn't. 
 
--
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.