Hi Scott,
that must be a glitch that these error messages are not documented in zSecure release 3.1.0. But, I can tell you that these are documented as follows in release 3.2.0:
CKR3380
Missing ICSF key label for dsn on <volume> [(volume_x)], system [version]
Explanation:
An inconsistency is detected between a VTOC and VVDS data. That is, a VTOC states that a dsn on volume is encrypted but no encryption information was collected from the VVDS on that
volume. In case of a multi-volume data set, the volume_x denotes a volume for subsequent parts of that multi-volume data set.
User response:
Perform the IDCAMS DIAGNOSE function on the VVDS to check VTOC/VVDS consistency.
Severity 04
CKR3382
Conflicting encryption keys for dsname on system [version]
Explanation:
Multiple records that refer the same dsname and have different encryption keys are found in the HSM migration control data set.
The program takes the first record into account.
User response:
Contact your system programmers and storage administrators to perform the DFSMS(hsm) diagnosis. Also see the IBM Support Community for possible maintenance associated with this message.
If you cannot find applicable maintenance, follow the procedures described in Contacting IBM Support to report the problem.
Severity 04
Jeroen Tiggelman asked me to post the following on his behalf:
Hi Scott,
When we issue PTFs for APARs we do not always update the Messages Guide.
APAR OA67497 introduced these messages in zSecure 3.1.
They are documented in the PTF cover letter:
VIEW TDSHR1.ZSECURE.HCKR310.UJ96802 Columns 00001 00072
Command ===> ________________________________________________ Scroll ===> CSR
000054 PLEASE NOTE the following documentation changes for manual IBM
000055 Security zSecure Messages Guide
000056 -
000057 Chapter 7. CKR messages, section "CKR messages from 3300 to 3399"
000058
000059 The following message is defined:
000060
000061 CKR3380 Missing ICSF key label for <dsn> on <volume>
etc.
Regards,
Jeroen