On Aug 18, 2022, at 7:53 AM, Peter Relson 
<[email protected]<mailto:[email protected]>> wrote:

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.


Looking through the logs, at a later point in the IPL after DFRMM had started, 
we found this:


22219 03:28:41.47 STC46322 00000090 *IEF233D M 1302,VP0597,,HZSPROC,HZSSTEP, 986
22219 03:28:57.04 STC46322 00000090 *15 IEF455D MOUNT VP0597 ON 120B FOR 
HZSPROC HZSSTEP OR REPLY 'NO'
22219 03:28:57.17          00000281  IEE400I THESE MESSAGES CANCELLED - 15.
22219 03:28:57.30 STC46322 00000090  FDR314   FDR UNCATALOGED  
DSN=$VTC.VTC280.LIBRARY
22219 03:28:57.30 STC46322 00000090  FDR311   FDR RESTORED 
DSN=$VTC.VTC280.LIBRARY
22219 03:28:57.30 STC46322 00000090  FDR311                ON VOLSER=WBPM07  
UNIT=3390-54 (WBPM08) STORCLAS=U
22219 03:28:57.30 STC46322 00000090  EDGI100I SUBSYSTEM UXTB NOT DEFINED OR NO 
TABLE LOADED
22219 03:28:57.34 STC46322 00000281  IEF234E K 120B,VP0597,PVT,HZSPROC,HZSSTEP 
- RACK=VP0597
22219 03:28:57.36 STC46322 00000090  HZS0001I CHECK(IBMCSV,CSV_LNKLST_SPACE): 
071
22219 03:28:57.55 STC46322 00000090  HZS0001I CHECK(IBMCSV,CSV_APF_EXISTS): 072


$VTC.VTC280.LIBRARY is both in the APF list and SMS-managed. Apparently FDRABR 
does migrate APF libraries. I’m going to make sure that all our APF libraries 
have a non-migrate management class.

Thanks for the help.


--
Curtis Pew
ITS Campus Solutions
[email protected]<mailto:[email protected]>




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to