Re: Date problems

["Dr. Syd Nicholson" <sydnic@xxxxxxxxxx>]

The 'U' date fields (eg. UDATE, UDAY, etc) use the job date. If the job
started on 26th day then UDAY will have 26 in it. If a job runs past
midnight the values in the 'U' date fields do not change even though the
system date has changed. Is it possible that your job started on 26th
August?

If you need the current date in a long running program, it is better to use
the TIME opcode, or its free format equivalent.

Syd Nicholson


----- Original Message -----
From: "Justin Houchin" <justin@RELIATEK.COM>
To: "Midrange-l" <midrange-l@midrange.com>
Sent: Wednesday, August 28, 2002 10:41 AM
Subject: Date problems


> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Hi Everyone,
>             I am making some modifications to an old program and came
> across something interesting. There is a field that gets the day of the
> month inserted into it. Here is the following code...
> 0327.00 C                   Eval      OCDAY = UDAY
>
>
> When I ran this program this morning, The OCDAY field had a 26 in it. I
> checked my system date; it says 8/28/2002. Could someone tell me why
> this date is not correct?
>
> Justin Houchin
> Programmer and Web Developer
> ReliaTek, Inc
> justin@reliatek.com
>
> --
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>