why should COMET worry about 2038-01-19... that's a UNIX bug, no??

Posted by Bob A on September 28, 2010 at 13:14:27:

I have a program to test some new date formatting routines...

if I put in a date from 01/01/1970 to 01/18/2038 it works fine
if I put in a date from 01/01/1830 to 01/01/1899 it works fine

outside these dates, it brings COMET down and I get some message about unable to communicate to COSW

Note... this isn't just getting an ERRLOG.... the whole COMET crashes and I have to re-load all the COMET terminal sessions.

I remember this problem about the Y238 bug when working on some Y2K issues and one of the other contractors talked about having to come back in 2038.... just don't know why the Y238 bug pops up here...

Follow Ups:

• Re: why should COMET worry about 2038-01-19... that's a UNIX bug, no?? Barbara Brazil 15:50:40 09/28/10 (0)
• Re: why should COMET worry about 2038-01-19... that's a UNIX bug, no?? Grant Foraker 13:54:42 09/28/10 (1)
  • Re: why should COMET worry about 2038-01-19... that's a UNIX bug, no?? Bob A 05:20:20 09/29/10 (0)
• Re: why should COMET worry about 2038-01-19... that's a UNIX bug, no?? Bob A 13:26:37 09/28/10 (0)

Post a Followup

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.