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

Re: Passing a Null Date to a Procedure

That seems it should not be possible - the point of prototypes is to tell what data type is being passed. I'd say add a test for being NULL, then pass an additional parameter that indicates this, perhaps a simple indicator. Or may operational descriptors can handle it directly - have not used them yet, no need up to now. Or on the first suggestion, use a CONST and have a logical expression over IS NULL and pass that indicator.

HTH
Vern

Doug Palme wrote:
Is there any way to define a date value in a procedure interface as being null capable?
I have checked the reference manual and so far have come up empty handed on this.

We have a file that allows for null capable dates and I have to pass this value to a procedure for some processing, but it does not like the usage of the %NULLIND parm.

*RNF0342 20 3 The parameter for %NULLIND is not valid; %NULLIND is ignored

*RNF0342 20 259 008812 Parameter WENDDATE for %NULLIND is not null capable
%NULLIND is ignored.
Suggestions?

Douglas





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.