if I recall correctly @TIME returns the time that the program began running, TIME() returns the current time.

Jacques G. wrote:
Hello,

Has anyone else here observed this behavior for Universe 11.1.3 on a OS other 
than HP-UX ?

Sometimes, @TIME will report an incorrect internal time.  When I first observed 
this behavior, I changed my use of @TIME for a call to TIME().  It fixed the 
problem on one HP-UX server I was working on, but when I installed the program 
on a different HP-UX server, TIME() now sometimes reported an incorrect 
internal time.  For example, it was around 6:00 am but the time reported was 
for about 4:00 am.

I fixed the problem on that server by replacing TIME() by 
ICONVS(TIMEDATE()[1,8],"MTS")

We have a setup for temporary locks that expire after a given time these 
temporary locks were being created as already expired.  It's a problem when a 
server can't determine the correct internal time.

Thanks
Jacques G.
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


--
------------------------------------------------------------------------
Jeff Schasny - Denver, Co, USA
jschasny at gmail dot com
------------------------------------------------------------------------
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to