× 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 >= ?

Hello,

> If caller is not passing the optional parameter, shouldn't the optional
> parameter be *null in the called procedure?

No. If no parameter is passed, it can't be anything -- it's not there.

When you pass *OMIT as a value to a procedure, the system passes a null
parameter -- but it still passes something.  When you use options(*NOPASS)
and choose not to pass a parameter, there's no value to check!  Nothing
was passed.

Your question is like asking "If I don't buy anything at the store, won't
this shopping bag be empty?" You can't look in the bag to see if
it's empty or full, because you didn't go shopping, and they didn't give
you a bag.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.