SLIP A=RECOVERY will stop the ability, but it will do it by causing a 06F abend in VSM or RSM while their FRRs are still in place, so their recovery will run, and will likely take an SDUMP of the 06F abend.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 04/05/2018 03:48:35 PM: > 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
