There is information in OA53355 about using SLIP to find the problems nondisruptively. For example,
SLIP SET,IF,A=TRACE,ID=UCSA,NUCEP=(IGVVSMG2,0,1),END Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY IBM Mainframe Discussion List <[email protected]> wrote on 04/05/2018 12:09:49 PM: > I've been asked off-list to elaborate on my post. Truth is I have > nothing else to contribute. Health check > ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM is installed by the APAR but not > activated. Odd if you ask me. So I activated it just on our sandbox > sysplex. *Immediately* got this: > > * High Severity Exception * > > IGVH114E Use of user key common storage detected since > 03/09/2018 16:08:05 > > Explanation: User key common storage usage attempts were made on this > system. Usage attempts can be obtaining user key CSA/ECSA storage, > creating user key SCOPE=COMMON data spaces or changing the key of > SQA/ESQA storage to a user key using CHANGKEY. Allowing programs to > use user key common creates a security risk because common storage > can then be modified by any unauthorized program. > > System Action: The system continues processing. > > Operator Response: Please report this problem to the system > programmer. > > OK, System Programmer response: no idea what the problem is. We have > run in this sysplex for many years with > > VSM ALLOWUSERKEYCSA(YES) /* AFOP abends B78-5C in z/OS 1.9 */ > > We moved from AFOP to System Automation many years ago, so that's > not the culprit. The health check comes with lots of advice on how > to find the offender, but at this moment, we have no idea who that > is. As I posted, lots of work in the offing. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
