I came across a web site that is expounding the theory of the next
date bug phenomena -- 2038.

http://www.deepsky.com/~merovech/2038.html

Of course, by the year 2038 I will be too old to even care about it...

Brian.

On Mon, 7 Feb 2005 10:27:00 -0500, Brian Donaldson <[log in to unmask]>
wrote:

>The timestamps are stored in an MPEix file as "longint_types" which are
>double integers.
>
>The big problem is that these dates aren't stored as a date and time combo
>as such, but as "microseconds since January 1, 1970".
>
>In Cobol the timestamps are defined as:
>
>01 LONGINT-TYPE COMP.
>   05  FIELD-1 PIC S9(09) COMP.
>   05  FIELD-2 PIC S9(09) COMP.
>
>When you pass this field to the intrinsic "HPDATECONVERT" it will convert
>the longint-type to a real date such as 20050207 for Feb 7, 2005. Fine. I
am
>already achieving this without any problems. However, it does nothing with
>the time as far as I can tell.
>
>So, can anyone out there tell me how to convert a real date AND time
>sequence (e.g. 20050307 12:34:56) to "microseconds since January 1, 1970"
>for the impending AIF call to update the timestamps in a file?
>
>TIA,
>Brian.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *