Oops, you are quite right, I didn't mention the file type but I was referring to static hashed files (Types 2 to 18).
For example, the VOC in my test account is a type 3 file and only COUNT changes the timestamp, unless of course I write something to the file. LIST, SORT, SSELECT, HASH.TEST all have no effect on the timestamp. Cheers, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hona, David S Sent: Tuesday, 17 February 2004 9:30 AM To: 'U2 Users Discussion List' Subject: RE: COUNT modifying unix timestamp You don't mention the file type, but I am assuming it is a dynamic file. If it is, this is "normal". I recall the first release of reliable dynamic files had the feature of disallowing access to users without 'read and write' permission...which wasn't actually documented anywhere...ouch! I think you will find 'LIST' and other 'read-only' commands has the same effect. Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Eves, David Sent: Tuesday, February 17, 2004 9:40 AM To: U2 Users Discussion List Subject: COUNT modifying unix timestamp We have a client running UV 10.0.16 on HPUX 11i who has noted that a Universe COUNT will modify the unix timestamp of a file. Has this always been the case? Why does a supposedly read-only operation like COUNT modify the timestamp but others such as LIST, SORT, etc. don't? Cheers, David Eves -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users