Re: Change Datestamps

Some of our applications have a similar issue depending on what code/process was used to obtain the date.
If the job runs past midnight, some dates could be incorrect.
We force end any interactive job after 12 hours.

This does two things.
1) End interactive sessions for users not signing off.
2) Ensures when users sign in, they have today's date.

Paul

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of David Gibbs via WDSCI-L
Sent: Monday, April 22, 2019 2:26 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Cc: David Gibbs
Subject: Re: [WDSCI-L] Change Datestamps

On Mon, Apr 22, 2019 at 1:18 PM Steve M via WDSCI-L
<wdsci-l@xxxxxxxxxxxxxxxxxx> wrote:

Being a full-time remote employee I leave my RDi session running for days on
end (well, until the VPN drops me and makes me re-attach). I started my
latest session last evening, on Sunday 4/21.

Today, I was editing one of the source members I had open, did a recompile
of the object, then checked the compilation to make sure my change was
included. The source line in the compile showed 4/21 - uh, no, today is
Monday 4/22. I thought that strange, so I did a "show data area" and sure
enough, the changed lines all read 4/21. I checked my PC date and it does
properly read 4/22.

I'm guessing that the host server that RDi is connecting to is using
the JOB date (which, IIRC, does not change) as apposed to the system
date.

It's akin to using UDATE vs. TIME.

davod