RE: Time displayed in programs/DSPF's

Mike,

I'm afraid it is working as designed.  The Job date is set when a job is
first started and is never changed.

The RPG special fields UDATE and *DATE access the job date.  From the RPG
reference, (TIME opcode)
"Note: The special fields UDATE and *DATE contain the job date. These values
are
not updated when midnight is passed, or when the job date is changed
during the running of the program."

You need to have your RPG programs use the TIME opcode or the %DATE bif to
access the system time.

Note that that may cause problems if the programs are designed specifically
to use the job date so that they can be run for past or future dates.
Perhaps for testing or what not.

Charles


> -----Original Message-----
> From: Condon, Mike [mailto:M1C@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, September 29, 2004 9:46 AM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: Time displayed in programs/DSPF's
> Importance: High
> 
> 
> To quiet down one complaint, another has surfaced.
> I changed QINACTITV to *NONE, since users were grumbling 
> about interactive
> sessions getting closed. It was also causing some confusion 
> as to whether
> Applications issues were tanking interactive sessions or not. 
> Now we're having a problem with the RPG app's retaining the 
> prior day's date
> if the session is open past midnight into the next day. Is 
> this a result of
> the wrong/inappropriate/improper use of date calls within the 
> RPG app's? I'm
> not primarily an RPG programmer, mostly system admin, but I 
> can make the
> necessary changes once I have some more facts.
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>