RE: Time displayed in programs/DSPF's

[RPower@xxxxxxxxxx]

I'd be concerned with object locks and backups not performing properly if 
users are leaving their sessions up all the time.  Why would one want to 
do that?  Doesn't it also bring up security issues?  ie The night 
janitorial staff could possibly hop on the still running session and play 
around for a while could they not?  Perhaps I'm thinking too broadly here, 
but I firmly believe in that if you haven't used a terminal in an hour, 
then you shouldn't complain about logging back in.  I would just increase 
the inactivity level and take a firm stand on it.  But that's only my 
personal opinion.  But then again, if you have valid users on at 11:50 
thru 12:10 then you'd still need to use the Time functions over *date and 
udate.

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
Tel: 709-576-8132
Email: rpower@xxxxxxxxxx
Website: http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. - 
Sir Winston Churchill




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


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

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.




This e-mail communication and accompanying documents is intended only for the 
individual or entity to which it is addressed and may contain information that 
is confidential, privileged or exempt from disclosure under applicable law.  
Any use of this information by individuals or entities other than the intended 
recipient is strictly prohibited.  If you have received this in error, please 
notify the sender and delete all the copies (electronic or otherwise) 
immediately.