The RACF folks indicate that the RACF_SENSITIVE_RESOURCES health check intends not to force the recall of migrated APF data sets. They also think that HSM does not migrate APF-authorized data sets (I'll try to confirm that).
The original appender didn't indicate the data set which was migrated. Is there any way to confirm what data set was the issue? Was it an APF-authorized dataset? If a dump of the HZSPROC address space was taken, it should be possible to determine exactly which check was running and caused the recall action. If it was the RACF_SENSITIVE_RESOURCES check, then it would sounds like their "intent" isn't being met, and that could perhaps be explored with L2. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
