Re: jt400 timestamp issue -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: jt400 timestamp issue
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 28 Feb 2008 10:40:46 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Mike Cunningham wrote:

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

How about making the field null capable and setting the value to null
when the employee is permanent?

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: jt400 timestamp issue , Joe Pluta

This mailing list archive is Copyright 1997-2024 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.