A final tidbit of followup: I discovered in testing that the time attribute
is accurate back to somewhere between June 8, 1924 and August 15, 1924.
These dates represent the birthdates of the two oldest people in our
organization, and the August 15 date works fine, while the June 8 date wraps
around and is incorrect.

Neither date is +/- 68 years from 1970, so I don't know what to conclude.
Anyway, since only one user is affected by this, we can blissfully ignore
the issue for now.

Rob.


"Father Ramon" <devforums@novell.com> wrote in message
news:VCT0g.1306$sd1.672@prv-forum2.provo.novell.com...
> eDirectory time syntax is based on ctime, a 32 bit signed number of
> seconds since January 1, 1970. As such it can only represent dates about
> +/- 68 years from that date. January 1, 1700 is well outside of that
> range so converting it results in an underflow wrap-around. For more
> information, see http://en.wikipedia.org/wiki/Ctime.
>
> There are several ways to address this problem. You have mentioned 2.
> The other obvious one is to use a different eDirectory syntax for your
> time attributes (assuming this is under your control).
>
> --
>
> Father Ramon
>
>
> Rob wrote:
> > Our HR department sets a "placeholder value" in time fields, to indicate
> > that there is no value: January 1, 1700. See the next line:
> >
> > [04/17/06 14:46:52.647]: LAWSON JDBC PT: RS field 'P01END_DATE',

length:
> > 21, value = '1700-01-01 00:00:00.0'
> >
> > My JDBC driver converts that value as follows:
> >
> > <modify-attr attr-name="phcLawP01EndDate">
> > <remove-all-values/>
> > <add-value>
> > <value type="time">-8520314400</value>
> > </add-value>
> > </modify-attr>
> >
> > And, then in Console one it appears as
> >
> > Thu Mar 16 12:56:32 CST 1972
> >
> > Worst case, if I see the value -85220314400 I can replace that with a

value
> > I like, or strip the attribute from the operation (since that value

means
> > the attribute should be blank anyway.) It would be nice if I could

actually
> > use the same value as in the HR department. Does E-Directory not handle
> > negative numbers in the time value conversions? or is there more I

don't
> > know about the mysteries of time conversion?
> >
> > Ideas?
> >
> > Thanks,
> >
> > Rob
> >
> >