RE: Record with external defaults (DeLong, Eric)

["Steve Peel" <Steve.Peel@xxxxxxxxxx>]

Yes I agree with that.  Null field handling is, to my tastes at least,
one area where SQL is, if not simpler, at least cleared and easier to
follow than it is in native RPG, especially when you have many null
capable fields.
It can get tedious to deal with in RPG. 

Steve
------------------------------

message: 2
date: Fri, 3 Sep 2004 10:25:15 -0500
from: "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
subject: RE: Record with external defaults (DeLong, Eric)

Yes, that's correct....  At issue however was a misunderstanding of how
null
fields work in RPG.  The null indicator is just a field attribute that
tells
you (the programmer) to not use the returned data.  The contents of
the
field must still be a valid date value, even though the null flag is
set.
Other platforms handle nulllable fields differently, and this makes
OS400's
implementation of null value support a bit harder to grasp.  


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Steve Peel [mailto:Steve.Peel@xxxxxxxxxx] 
Sent: Friday, September 03, 2004 9:26 AM
To: rpg400-l@xxxxxxxxxxxx 
Subject: RE: Record with external defaults (DeLong, Eric)


If you are defing date fields in DDS use DFT('0001-01-01').  The
'default' default for any date field is the current date unless you
specify otherwise.

Steve 



****************************************

***********************************************************************

The information transmitted is confidential and is intended for the person 
or persons named above.  Any unauthorized reading, distribution, copying, 
or other use of this message or its attachments is strictly prohibited.  
If you received this message in error, contact the sender and then delete 
and destroy all copies of the material.