ACF99910 ACF2, VIOLATION EXCESSION, CANCELLED . OMVS Address Space cancellled. What caused violation
Article ID: 189024
ACF2ACF2 - DB2 OptionACF2 for zVMACF2 - z/OSACF2 - MISCLDAP SERVER FOR Z/OSPAM CLIENT FOR LINUX ON MAINFRAMEWEB ADMINISTRATOR FOR TOP SECRET
ACF99910 ACF2, VIOLATION EXCESSION, CANCELLED IEF196I ACF99910 ACF2, VIOLATION EXCESSION, CANCELLED IEA989I SLIP TRAP ID=X222 MATCHED. JOBNAME=OMVS , ASID=0010. *BPXI019E OMVS DETECTED A SEVERE INTERNAL ERROR THAT WILL REQUIRE A RE-IPL TO CORRECT
NOMAXVIO was added to OMVS logonid and it did not get cancelled again.
Problem - what caused the violations in the omvs addrspace?
Release : 16.0
Component : CA ACF2 for z/OS
The violations were caused by a mount request that was trying to mount a file system that OMVS did not have access to. IBM provided details on how to find who is issuing a mount request. The mount request is occurring almost at the same time every day. IBM noted that there is probably a DCOLLECT Batch job running at that time. ( DFSMS IDCAMS DCOLLECT) When DCOLLECT sees an HFS it tries to Automatically mount and then unmount it afterwards trying to get Space usage.
When DCOLLECT gathers information about an HFS, an implicit mount is issued to gather the statistics and then, the filesystem gets unmounted.
Having a dump with the OMVS ctrace running would show who requested the mount that is performed by the OMVS address space. then take a console dump after the dataset violation occured. Note: SYSOMVS CTRACE wraps around in a few minutes on an active system. follow these instructions to get the trace of OMVS activity.
i) turn on the SYSOMVS CTRACE
Turn on the OMVS ctrace: TRACE CT,64M,COMP=SYSOMVS reply: R XX,OPTIONS=(FILE),END
ii) wait for the dataset violation
iii) take a console dump DUMP COMM=(DUMP OF OMVS) R nn,JOBNAME=(OMVS),DSPNAME=('OMVS'.B*,'OMVS'.S*),CONT R rn,SDATA=(CSA,LPA,TRT,RGN,SUM,SQA,ALLNUC,PSA,XESDATA,COUPLE), CONT