>RAX_SMF30_SAPFlags
This information is captured in the SMF30 records as of the APAR that
introduced this health check (OA53355), in the byte at offset 178 (x'B2')
in the Storage and Paging section of the SMF 30 record mapped by DSECT
SMF30SAP in macro IFASMFR3.
And information about that appears to be presented in the health check
message buffer which the OP did not completely include in his post. (At
least I can see that it is defined; I did not view the actual output of
the check)
It should look something like this:
Please report this problem to the system programmer. In the SMF Type 30
records,
the SMF30_UserKeyCsaUsage, SMF30_UserKeyCadsUsage and
SMF30_UserKeyChangKeyUsage flags in the Storage and Paging
section can be used in conjunction with fields in the Identification
section to identify all
job steps that use user key common storage. Change the affected software
to support having the
user key common areas of virtual storage protected in a system key, or
change the affected software to support the
storage not be common to all address spaces. Some alternatives for sharing
storage instead of having storage
common to all address spaces include the following options:
- Use a SCOPE=ALL data space to share data space storage
with select units of work in select address spaces.
- Use IARVSERV SHARE to share below the bar storage with
select address spaces.
- Use IARV64 GETSHARED to share above the bar storage with
select address spaces.
- Use z/OS UNIX shared memory to share below the bar or
above the bar storage with select address spaces.
I did notice that the message text for IGVH114E itself is not available in
the KC documentation (the check itself is). I have asked the ID folks to
remedy that situation.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
