Lionel, Couldn't it be the case that IBM knows where the use of common storage occurred but not who the offender is?
Lou -- Artificial Intelligence is no match for Natural Stupidity - Unknown On Fri, Apr 6, 2018 at 9:31 AM, Dyck, Lionel B. (TRA) <[email protected]> wrote: > IBM provides a new Health Check - IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM > > But it is worthless (see below) - it tells me we have an issue that is > HIGH *BUT* it does not tell me who/what. If you can detect it then provide > more info otherwise it's a near useless health check - it's like going to > the Doctor who tells you that you have a problem but refuses to tell you > what your problem is but if you really want to know then go to a specialist. > > IBM - you detected the issue and you won't tell me the specifics - ARG! > > CHECK(IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM) > SYSPLEX: AUSTIN1 SYSTEM: SYP > START TIME: 04/06/2018 09:01:46.169645 > CHECK DATE: 20170807 CHECK SEVERITY: HIGH > CHECK PARM: ALL > > > * High Severity Exception * > > IGVH114E Use of user key common storage detected since > 03/04/2018 02:37:42 > > > -------------------------------------------------------------------------- > Lionel B. Dyck (Contractor) <sdg>< > Mainframe Systems Programmer - RavenTek Solution Partners > Service Operations - Infrastructure Operations > Office of Information and Technology, IT Operations and Services > Office: 512-326-6173 > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
