ACF99913 violation is seen. Documentation is needed to find a resolution and provide the needed ACF2 rules.
Component: ACF2MS
The CA-ACF2 reports, decompile of rules and a list of the logonid provide a useful basis in debugging CA-ACF2 violations.
The following documentation is an important tool in debugging both dataset ACF99913 and resource ACF04056 violations.
1) The ACFRPTDS report for dataset violations and the ACFRPTRV report for resource violations.
Sample report JCL:
//REPORT EXEC PGM=ACFRPTDS
//SYSPRINT DD SYSOUT=*
//* The following DDs should point to current SMF
//RECMAN1 DD DISP=SHR,DSN=SYS1.MAN1
/RECMAN2 DD DISP=SHR,DSN=SYS1.MAN2
//RECMAN3 DD DISP=SHR,DSN=SYS1.MAN3
//SYSIN DD *
TITLE(ACFRPTDS)
ALL
/*
//REPORT EXEC PGM=ACFRPTRV
//SYSPRINT DD SYSOUT=*
//* The following DDs should point to current SMF
//RECMAN1 DD DISP=SHR,DSN=SYS1.MAN1
//RECMAN2 DD DISP=SHR,DSN=SYS1.MAN2
//RECMAN3 DD DISP=SHR,DSN=SYS1.MAN3
//SYSIN DD *
TITLE(ACFRPTRV)
ALL
/*
2) A DECOMPILE of the rules involved in the validations including any NEXTKEY rules that may be involved. This would include the rules that are expected to be used as well as the rule identified in the ACFRPTRV report "LOOKUP KEY" and the ACFRPTDS report "RKEY".
3) A LIST of the logonid that the violation is occurring - from a TSO ACF command.
Note: This documentation is the typical documentation that is needed for most violation problem related to rules. Depending on the specific situation and violation, additional documentation may be needed.