>I already have VSM ALLOWUSERKEYCSA(NO). This health check fires anyway. > Apparently there are other ways of getting user key storage, not just >in CSA. Good of IBM to tell us all to write our own code to traverse >SMF 30. Not all of us have SAS, MICS, MXG, etc. You should have >written a sample, IBM!! > >Regards, >Tom Conley
I opened a PMR today, and learned that ALLOWUSERKEYCSA(NO) only stops one of the three User Key Common Storage uses that will cease to be available in z/OS vNext. This is all that's available today on z/OS 2.2 and z/OS 2.3. I was offered a PER SLIP that could stop the other two Common Storage uses (after OA53355) - User Key Scope=Common Data Spaces and User Key ESQA key changes, which are the other two bit flags in the SMF30_RAXFLAGS byte. I don't think a PER trap is appropriate for long term use on a production system - I just want the option to stop all of these uses of User Key storage now - before z/OS vNext. By the way, to stop the ability to create a user key CADS after OA53355, use the suggested PER SLIP and change A=TRACE to A=RECOVERY - or so I understand. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
