Right, Scott - because CPYLIB does a bunch of CRTDUPOBJ commands, and
whatever THAT does is what you get. IIRC, that is!
On 1/28/2014 9:30 AM, Scott Mildenberger wrote:
I recently learned that CPYLIB updates the Last Used date, at least on *PGM objects and probably all, and that surprised me. That probably doesn't account for your issue as all the objects should have been touched.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Monday, January 27, 2014 4:48 PM
To: Midrange Systems Technical Discussion
Subject: when does OS/400 or IBM i reset the "last used" date of an object?
One of my customers ran into this, and I am at a loss to explain it (so far).
On their production LPAR, they ran a DSPOBJD of all objects in one production library to an *OUTFILE some time on Friday.
Now, looking at the data in that outfile today, they notice that many of those objects had the "last used" date containing blanks -- e.g. not used since it was last "reset".
Yet today, they also noticed that if they now issue DSPOBJD against any of those same objects that had a blank "last used" date, on the same production LPAR, and specify DETAIL(*FULL), they tell me they now see a "last used" date on many (but not all?) of those objects -- and the last used date shown is "20140124" (last Friday)...
What can cause this?
I know, for example, that restoring objects from a previous save, (from tape or save file), resets the "last used" date to blanks.
But, what other commands or actions will set the "last used" date?
I know that CALLing a *PGM will set its "last used" date to the current date, as will OPENing a *FILE ...
Are there any other commands that could have "touched" many objects in this one library, causing many of them to have their "last used" date set?
Thanks in advance for any ideas ...
Mark S. Waterbury
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.