If you are not using or trying to implement Kerberos in the CICS regions then what you are seeing is the failed R_kerbinfo service requests due to an incomplete implementation of Kerberos support in CICS. IBM started setting up CICS for Kerberos in CICS TS 2.2, but at that release only completed the initialization component and not the authorization component. So, the failure to find a Kerberos profile record was ignored by CICS. The failures have continued through a number of subsequent releases.
If you are not using Kerberos in CICS and you are not seeing any errors in CICS related to Kerberos you should ignore any failed R_kerbinfo requests that are appearing in the ACFRPTOM report. You can add the EXCLUDE(R_kerbinfo) parm in the ACFRPTOM report. Note that the service specified in the EXCLUDE is case sensitive and if the case is not correct message 'CAS2522E INVALID OPERAND VALUE FOR KEYWORD EXCLUDE' will be issued.
Sample ACFRPTOM JCL:
//REPORT EXEC PGM=ACFRPTOM
//SYSPRINT DD SYSOUT=*
//RECMAN1 DD DISP=SHR,DSN=SYS1.MAN1
//RECMAN2 DD DISP=SHR,DSN=SYS1.MAN2
//RECMAN3 DD DISP=SHR,DSN=SYS1.MAN3
//SYSIN DD *