RE: Object Last Used Date is reset on LPAR migration/recoveries

I did save my QAEZDISK from the day of the migration.
Not easy to incorporate both a current QAEZDISK and an older QAEZDISK.

Also saved DSPOBJD of all objects from the same date.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Friday, April 26, 2019 4:09 PM
To: Midrange Systems Technical Discussion
Subject: RE: Object Last Used Date is reset on LPAR migration/recoveries

I guess, but you'd have to do every user object on the system for it to work.

-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Friday, April 26, 2019 2:34 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Object Last Used Date is reset on LPAR migration/recoveries

If you really need to know, you can do a Create table last_used_dates as ( ... see the right IBM I Service ...
) with data
Prior to the upgrade.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Friday, April 26, 2019 3:29 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Object Last Used Date is reset on LPAR migration/recoveries

We just suffer thru it. Retaining the change/last-used would be helpful.