Good point from both you and David. It really should be a null field but the original reason I posted this was a problem where the driver was sending a null value and the java application using the driver puked on the null value. If I had it set to null that problem would still exist. I also found this since my original post
http://www-1.ibm.com/support/docview.wss?uid=nas125a815068ae8792586256aaa0054f5fb
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Clapham, Paul
Sent: Thursday, February 28, 2008 11:44 AM
To: Java Programming on and around the iSeries / AS400
Subject: RE: jt400 timestamp issue
So that's really a null in sheep's clothing. But our system is the same,
we don't have null values in user-maintainable tables. The practice
dates back to the days when you couldn't have null values, or if you did
then your RPG code couldn't work with them, and we haven't ever changed.
PC2
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: February 28, 2008 08:40
To: 'Java Programming on and around the iSeries / AS400'
Subject: RE: jt400 timestamp issue
It is a field used for when an account will expire. For fulltime
employees it is set to 12/31/9999 (highest value allowed) since fulltime
employees are hired forever or until HR says they left. Part-timers and
special accounts are set to a known exit date that is know when they are
hired so we can re-verify the account is still needed or delete it
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/java400-l.
midrange.com
