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


  1.  Home
  2. RPG400-L
  3. August 2004

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

If caller is not passing the optional parameter, shouldn't the optional 
parameter be *null in the called procedure?  If so, why is %addr not working?   

-----Original Message-----
From: rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx]On Behalf
Of Bob Cozzi

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.

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.