Thanks John We do not have the TIMEACCURACY setting available.
We are looking at upgrading in the next few months. I can see that setting on our UV 10.3.3 box. But that does not do much for me with this current requirement. <sigh> Shelling out to unix may be do-able but seems to defeat the object of the exercise. I will have to try that and see what overhead it incurs. Cheers JR -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Hester Sent: Friday, February 12, 2010 1:07 PM To: U2 Users List Subject: Re: [U2] UV time milliseconds option You should check for the existence of the following setting in the uvconfig file: # TIMEACCURACY - This may be 0 or 1. This parameter affects the # output of the TIME() function. If set to value of 1 (default), # the TIME() function will try to report the internal time as # accurately as possible, reporting time in milliseconds or # microseconds, using decimals. If set to value of 0, the TIME() # function will report the internal time as whole seconds. # Note: since each machine reports time differently, it may not # be possible to show time in other than whole seconds. TIMEACCURACY 1 I believe this option only became available after UV 10.x, though. You may have to use EXECUTE to shell out to the HP-UX date command to capture milliseconds in UV 9.6. -John -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Rodgers Sent: Friday, February 12, 2010 7:59 AM To: u2-users@listserver.u2ug.org Subject: [U2] UV time milliseconds option We run UniVerse 9.6 on HP-UX We run PICK flavor accounts to accommodate our SB+ applications I am having trouble pinning down the cause of a performance issue so I want to record the progress of program. I need timestamps in milliseconds. I tried the $OPTIONS TIME.MILLISECOND So SYSTEM(12) should return the required value START.TIME = 38694 ;* TIME() START.SYS12 = 38694000 ;* @TIME = 38694 CPU TIME = 17280 ;* from SYSTEM(9) NAP 500 NEW TIME = 38695000 ;* SYSTEM(12) ELAPSE TIME = 1000 ;* SYSTEM(12) - START.SYS12 CPU ELAPSE = 10 That's not right. Without the nap. NEW.TIME is always = START.SYS12 ie = START.TIME : '000' I have tried variation on the theme of $OPTIONS With and without various 'FLAVOR' keywords. What am I missing? Cheers JR John Rodgers MasterPack Project Team Masonite International Tel: (813) 2612396 ext 3036 _______________________________________________ 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 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users