IBM's reply contained this:-
If you take a look at OA53355, you'll see the full description of the
healthcheck and how you can adjust it or reset. Here is the portion
that you'd be interested in:
Add the following new Health check:
ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM
Description:
This check determines if any usage of user key common
storage was detected on the system.
Reason for check:
Allowing programs to use user key common creates a
security risk because common storage can then be
modified by any unauthorized program. This check
provides advanced warning of this potential security
risk so the system programmer can take appropriate action.
z/OS releases the check applies to:
z/OS V2R1 and later.
Parameters accepted:
The following parameters are supported to control WTOs
produced by exception messages when a new user key common
storage usage attempt is detected:
PARM('ALL')
Exceptions should be issued if there are any user
key common storage usage attempts made on this
system since the last IPL.
==> PARM('NEW(text value)') <===
Exceptions should only be issued for user key common
storage usage attempts that are detected after this
parameter is set. The 'text value' is
free-form and is not used by health check
processing. It should contain text to help the user
uniquely identify this particular parameter set.
The following are examples of PARM specifications for
ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM:
PARM('NEW(yyyy/mm/dd hh:mm)')
PARM('ALL')
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
