RE: Interesting question and debate on ddltables withdate fieldsthatwill not always have a value

Really? Do you happen to know which version that came with? I don't
think I've heard that mentioned on the list before today, but I'm sure I
could have missed it.

Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, October 14, 2008 5:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: Interesting question and debate on ddltables withdate
fieldsthatwill not always have a value

DeLong, Eric wrote:

No, I would want IBM to allow me to propagate the "nullness" <g> of
any given value throughout my application. If I need to pass that
field into a subprocedure, should I also need to explicitly declare an

extra parm just so I can pass it's null flag? Ideally, null should
just be an attribute of the field, and implicitly passed along with
its addressing pointer.

Is a null attribute passed in OPDESC?

Now, despite my personal bias against null fields, I must say that RPG
has gotten better at handling them. Barbara managed to introduce the
*NULLIND option on procedure parameters, which does pretty much exactly
what you need.

Joe
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.