× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have been trying to analyze the *File objects in a library to determine if I really, really need to keep them. One of the tools I'm using on the questionable ones (i.e., no one claims responsibility and I can't find anything that references them) is DSPOBJD.

The weird part (to me) is that a lot of them have a "Last Changed Date" of 26 May 2007 (a Saturday) at about 20:00. I thought that might be because of a PTF (Cume or Group) because I would have done that on a Saturday; in fact, my time log indicates that I did work that day and, other than a natural disaster, applying PTF's is about the only reason that I would have worked on a Saturday. However, I know applied a CUME and Groups to that system on 20 October 2007 (a Saturday, naturally); so that idea doesn't seem to hold water.

And most of those files exhibit a "Last Used Date" earlier (sometimes by a couple of years) than the "Last Changed Date". But, if I (or anyone) actually changed the file in any way, then the "Last Used Date" should get updated, too. Right? Well, that's what my tests (simple DFU on a file) showed, anyway. A simple query against a file affects the "Last Used" but, naturally, not the "Last Changed" date.

I have not been able to find anything in the Info Center (V5R4) or the Archives that would explain why the "Last Changed Date" would be later than the "Last Used Date." Anyone on the List know (or simply want to hazard a SWAG)?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.