I guess, obviously wrong, that RDi would be smarter than it appears to be.
There's no reason it couldn't gather the "current" date from the local
system and apply that value, but alas, it does not happen.
We have interactive jobs end in a much shorter time than that, however, RDi
runs in QUSRWRK and not QINTER, so those rules don't apply.
I hate having to close and reopen the same source member, each morning, just
for the sake of a datestamp, but that appears to be my only recourse.
Steve
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz,
Paul via WDSCI-L
Sent: Monday, April 22, 2019 14:03
To: 'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries' <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>; 'David Gibbs'
<david@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] 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
--
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding 615 miles (Yes, you read that right) in the American Diabetes
Association's Tour de Cure to raise money for diabetes research, education,
advocacy, and awareness. You can make a tax-deductible donation to my ride
by visiting
https://mideml.diabetessucks.net.
You can see where my donations come from by visiting my interactive donation
map ...
https://mideml.diabetessucks.net/map (it's a geeky thing).
I may have diabetes, but diabetes doesn't have me!
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
