Re: DDL - Handling Nulls

[Doug Palme <DPalme@xxxxxxxxxxx>]

   I think I was vague in my question :) What I was trying to determine or
   get some assistance on was not what a NULL is, but how to test for it with
   an RPG IV program....not embedded  or free format.

   From:     vhamberg@xxxxxxxxxxx                                             
   To:       Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>  
   Date:     08/01/2008 10:51 AM                                              
   Subject:  Re: DDL - Handling Nulls                                         

     ----------------------------------------------------------------------

   NULL-capable fields have a NULL-indicator you can test - in embedded you
   also can define a separate indicator variable - details are in the SQL
   programming manuals for RPGLE.

   Now things are getting better all the time - find the manual that matches
   your OS level.

   Strictly speaking, NULL is neither a value or a data type - it indicates
   that the value of this column of this type is not known, or has no value.
   However, many do loosely speak of a NULL value.

   Best I can say is RTFM - it's all in there.

   HTH
   Vern

   -------------- Original message --------------
   From: Doug Palme <DPalme@xxxxxxxxxxx>

   > We have been expirementing with DLL files lately and have run into an
   > issue regarding NULL values. Now, I know that SQL tables allow NULL as a
   > value for a field and it is considered a data type that can be used; and
   > that is different than a blank.
   >
   > I also know that I can code the DDL up front to not allow nulls and
   > provide a default value, but is there a way to handle nulls in an RPG IV
   > program without having to recompile the DDL?
   >
   > Just looking for as many options here as possible, knowing that the best
   > one is to code it right up front....
   > This transmission may contain information that is privileged,
   confidential
   > and/or exempt from disclosure under applicable law. If you are not the
   > intended recipient, you are hereby notified that any disclosure,
   copying,
   > distribution, or use of the information contained herein (including any
   > reliance thereon) is STRICTLY PROHIBITED. If you received this
   > transmission in error, please immediately contact the sender and destroy
   > the material in its entirety, whether in electronic or hard copy format.
   > Thank you.
   > --
   > 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.
   >
   --
   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.

   This transmission may contain information that is privileged, confidential
   and/or exempt from disclosure under applicable law. If you are not the
   intended recipient, you are hereby notified that any disclosure, copying,
   distribution, or use of the information contained herein (including any
   reliance thereon) is STRICTLY PROHIBITED. If you received this
   transmission in error, please immediately contact the sender and destroy
   the material in its entirety, whether in electronic or hard copy format.
   Thank you.