|
Bob Cozzi <BobCozzi@ibm.net> wrote >>>Actually, the example wouldn't work for another reason as well. The >>>"null flag" is associated with specific fields and is not passed when >>>passing the field as a parameter. > >That's it. I quit! > >Did you just say that the %NULLID(myDate) built-in is not allowed within an >RPG IV subprocedure? If you did, I'm gonna have to take some >Dramamine!!!!!!!!!! > >So to check for a "null" date we have to use %NULLID() but only in >main-line calcs. Okay, then I state my point again. We have NO support for >null date values in RPGIV at this point in time. %NULLID is restricted to >mainline calcs. Whoa! Hold on! I never said you can't use %NULLIND within a procedure. Just that you can't use it on a parameter passed to the procedure. You certainly can code %NULLIND(FIELD) within a procedure. (Provided, of course, that FIELD is defined as null-capable in some record.) Hans Boldt, ILE RPG Development, IBM Toronto Lab, hboldt@vnet.ibm.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.