re: [U2] [UV] TIME() truncation

2004-05-28 Thread Norman, David (SAAS)
Karl, As far as I know there isn't an OS solution - the easiest way I found was to add a $OPTIONS TIME.MILLISECOND to each program and re-compile. Another option is to use INT(TIME()) in each statement. David Norman Senior Systems Engineer SA Ambulance Service Box 3, GPO

RE: [U2] [UV] TIME() truncation

2004-05-27 Thread Stevenson, Charles
Karl, Short answer: $OPTIONS TIME.MILLISECOND affects TIME() SYSTEM(12). We are on HP UX also when upgrading from 9.6 TO 10.0.x we blindly inserted $OPTIONS TIME.MILLISECOND at top of all programs so they would function as before. Archives are at http://www.indexinfocus.com/ but I couldn't

Re: [U2] [UV] TIME() truncation

2004-05-27 Thread [EMAIL PROTECTED]
Karl, I don't believe that you can turn off the decimal portion. I'd suggest writing a subroutine with the one line field(TIME(),'.',1) and build a program to find TIME() and replace it with the subroutine call. If you go this route, I strongly suggest that you run the replacer program

Re: [U2] [UV] TIME() truncation

2004-05-27 Thread Karl L Pearson
Thanks for the responses. I tested and will use $options TIME.MILLISECONDS because of it's compile-time rather than run-time impact. But, I was interested to find that TIME() on my Linux PE 10.0.2 box returns no decimal. On my AIX 4.3.3 and UV 10.0.14 it did and using $options