internal date doesn't change after midnight

I found an interesting problem with informix's use of the system date. I have seen the error on a customer's IBM RS6000, and have duplicated it on my SUN IPC, both machines running 4.10 4GL and 5.00 SE. Look at the following program and the results written to the error log by informix's errorlog() function, and what happens to the date used by informix in relation to the system date. -------------------------------------------------------------------- main define junk char(1) call startlog("alan.errlog") display "doing an errlog now" call errorlog("doing the first one before date change") prompt "press return after date change" for junk # change the system date manually display "doing an errlog now" call errorlog("doing the second one after date change") exit program end main ----------------------------------------------------------------------- Output in the file alan.errlog, created by the startlog() call. Date: 04/30/1993 Time: 15:48:54 doing the first one before date change { I then manually changed the system date to 05/01/93 } Date: 04/30/1993 Time: 01:00:05 doing the second one after date change It appears that the system date used by the errorlog call is not taking into account the fact that dates change at midnight, at least on the various systems I work on. 8-) This same problem occurs "naturally" on my customer's RS6000 when 4GL processes are left running overnight. Does anyone know why? Is there a workaround? Thanks -- Alan Goodman Sr.Programmer/Analyst internet: alan@dssmktg.com bangpath: uunet.uu.net!dssmktg!alan realpath: Data Systems Support 1228 Shelly Ct. Orange, CA 92668 Voice 714-771-0454 Fax 714-771-3028