During recall of a Dfhsm migrated dataset, the last reference date
will be updated to the date of the recall. This happens even
if the dataset is not opened, but simply recalled via
IEFBR14 for example. I would prefer that the last reference
date be updated by open/close instead of recall.
Does anyone know of a Dfhsm patch that will cause Dfhsm to
NOT update the last reference date once the recall is complete?
Now, for the "why", "do you know", "did you consider" questions
and comments.
1) I have some migrated datasets without Dfhsm backup that I
would like to recall, backup, migrate without updating the
last.ref date.
2) this will confound those who simply mass-recall their
migrated files via IEFBR14 to keep them on dasd for the next
"n" days before they get selected for migration again.
3) yes, I know this could lead to thrashing because Dfhsm might
re-migrate the files the next day and updating the last.ref date
during recall avoids that.
PS: running z/OS 1.4 with Dfsms 1.3
--
___
Play 100s of games for FREE! http://games.mail.com/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
