Jacques @TIME doesn't give the current time anyway. It gives the time that whatever program or activity you're running started.
So, for example, if you do a listing LIKE: LIST VOC EVAL "@TIME" EVAL "TIME()" And sit at the "Press any Key .." point for a few seconds then continue, you'll see the difference between the two. But TIME() should go get the current time, so I don't know why it would differ from what your OS is reporting unless there is an environment issue with the time zone for your user. If you 'sh -c date' for that user, does it show the right time? Brian -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jacques G. Sent: 10 September 2012 17:50 To: U2 Users List Subject: Re: [U2] [U2[UV] @TIME and TIME() not reliable 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 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
