A fix is available
APAR status
Closed as program error.
Error description
VSAM or VVDS Inconsistencies report does not contain relevant messages when a select on SENSTYPE is used. A select with SENSITIVITY does cause the inconsistencies to be reported correctly with SENSDSN reporting. The processing triggered for SENSITIVITY and SENSTYPE should be the same, but is not.
Local fix
Use a select with SENSITIVITY instead of SENSTYPE.
Problem summary
**************************************************************** * USERS AFFECTED: Users of zSecure Audit exploiting the * * "Sensitive data sets" report (newlist type * * SENSDSN). * **************************************************************** * PROBLEM DESCRIPTION: zSecure Audit does not issue messages * * that indicate VSAM or VVDS * * Inconsistencies (MSGCKR0072, MSGCKR0286 * * and MSGCKR0293 for example) when record * * selection criteria based on the * * SENSTYPE field (contrary to the record * * selection based on the SENSITIVITY * * field which is an alias for SENSTYPE). * * The report processing triggered by * * SENSITIVITY and SENSTYPE fields is also * * different. * **************************************************************** * RECOMMENDATION: Apply the PTF provided. * **************************************************************** When selection criteria for "Sensitive data sets" reports is based on the SENSTYPE field, zSecure Audit does not issue messages that indicate VSAM or VVDS Inconsistencies (MSGCKR0286 which begins with the text "No VTOC and no VVDS entry for cluster component ...", MSGCKR0293 which begins with the text "Volume not mounted on any system ..." and MSGCKR0072 which begins with the text "Catalog not found on any volume ..."). The report processing triggered by SENSITIVITY and SENSTYPE fields is also different while it should be the same as the SENSTYPE field is an alias for the SENSITIVITY field.
Problem conclusion
zSecure Audit has been modified so that record selection based on the SENITIVITY and SENSTYPE fields results in identical program behavior while "Sensitive data sets" reports are being processed.
Temporary fix
Comments
APAR Information
APAR number
OA61989
Reported component name
ZSEC BASE,ADMIN
Reported component ID
5655T0100
Reported release
240
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-08-25
Closed date
2021-08-27
Last modified date
2021-09-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UJ06401
Modules/Macros
CKRINMO GKRINMO
Fix information
Fixed component name
ZSEC BASE,ADMIN
Fixed component ID
5655T0100
Applicable component levels
R240 PSY UJ06401
UP21/08/31 P F108
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPQTM","label":"IBM Security zSecure Admin"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"240"}]
Document Information
Modified date:
02 September 2021