RE: Time displayed in programs/DSPF's

[rob@xxxxxxxxx]

Dan,

In a long running program do you remember to reset those fields? Otherwise 
won't they keep the same date over midnight?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Dan Bale" <dbale@xxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
09/29/2004 09:14 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Time displayed in programs/DSPF's






> wrong/inappropriate/improper use of date calls?

Eh, not necessarily, IMO.  It's just that with the normal expectations 
that
users will sign off at the end of the business day, most programmer's use
the easy reserved name UDATE, which is the job date, which does NOT change
when midnight passes.

Frankly, I'd be more concerned about users not signing off.  If your users
were previously not signing off because they knew the system would do it 
for
them, now that the system does not do this "difficult" task for them, they
need to be trained to do so.  A somewhat effective measure we have here is
that any profile that is still signed on when our operator comes in at
6:00am has their interactive job killed and their profile disabled.  When
the user calls to get their profile re-enabled, they get a tactful earful
from the operator, who has the proper sense to let the user know that they
have to remember to sign off.

Get your users to sign off, and you won't have problems with the job date.
This assumes that you don't have any legitimate night users signing on
before midnight and working past midnight.  As a rule, I never use UDATE
anymore, especially since my standard is to display a *USA date & time, 
and
this can be accomplished in RPG-IV with:

d $Date           s               d   DatFmt(*USA) Inz(*Sys)
d $Time           s               t   DatFmt(*USA) Inz(*Sys)

hth,
db

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx / Condon, Mike
> Sent: Wednesday, September 29, 2004 9:46 AM
>
> 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.