Re: [U2] [U2[UV] @TIME and TIME() not reliable
The TIME() function is sensitive to local timezone settings in the OS. Is there a difference in the TZ environment variable between the two HP machines, or even for the user id running UV? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jacques G. Sent: Tuesday, 11 September 2012 2:50 AM 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 -- Message protected by DealerGuard: e-mail anti-virus, anti-spam and content filtering. http://www.pentanasolutions.com Click here to report this message as spam: https://login.mailguard.com.au/report/1FwBQGFAof/6zzhzgO3PktEIp1akWZRi4/2.953 This email and any attachments to it are confidential. You must not use, disclose or act on the email if you are not the intended recipient. Liability limited by a scheme approved under Professional Standards Legislation. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
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
Re: [U2] [U2[UV] @TIME and TIME() not reliable
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
Re: [U2] [U2[UV] @TIME and TIME() not reliable
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
