John,
It gets worse.
For dynamically hashed files (type 30) the datetime-modified stamp gets set
even if one does no updates.  This is because UV brings the current mod &
load parameters into memory when you open the file in case it dynamically
changes.  When you close the file, those params indiscriminately get written
back to the header of DATA30, even if they have not changed.  Unix dutifully
records the data-time modified.   (Exception: if user has read-only rights,
the update to the header is not written, no harm, no foul.  Which,
incidentally, proves the update is superfluous. Seems like there might be an
enhancement request buried here.)  So you can't really trust the mod-stamp
on DATA30 to tell you when the file was really last updated.
For most files the stamp on OVER30 might be fairly accurate.  One does not
necessarily update OVER30 whenever there is a write, but for very active
files it's pretty accurate.  If OVER30 mod-stamp is 2 years old, it might
mean that the dynamic file has not been updated for 2 years.

Chuck Stevenson


On Wed, Jan 28, 2009 at 3:30 PM, John Rodgers <[email protected]>wrote:

> UniVerse 9.6.1.6 on HP/UX
>
> We are analyzing our "mature and extensive" application to find obsolete
> files.
> I was hoping to use the array loaded by STATUS() after a file OPEN to
> return
> the date/time stamps.
>
> From the manual for STATUS() after OPEN
>  ...
> Last Access date = <14> - date of last access
> Last Date Written = <16> - date of last mod
>
> It appears that opening the file immediately changes the last access
> date/time <14> and <15>.
> That seems to defeat the purpose because the answer is always today / now.
>
> Is there a way around this?
> Is there another way of getting at that info without having to parse the
> results of a unix shell command?
> One hassle with that is the external date returned which is "sometimes"
> month day & time or maybe month day & year - for older records.
>
> I can do that but it just seems simpler to stay within UniVerse to query
> UniVerse entities.
> We get spoiled by the U2 way of managing dates/times.
>
> I have searched the IBM knowledge base but got no relevant hits.
> That surprises me. I am either misunderstanding something or I am totally
> on
> the wrong path.
>
>
> Cheers
>
>
> JR
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to