Question:
I am seeing message ACF75052 ACCESS RULE stored by xxxxxxxx where the logonid is incorrect and appears to be random logonids not related to the rule. What is causing this?
Answer:
The problem usually appears after performing F ACF2,REFRESH(ALL).
ETF/A dynamically implants its intercepts at ACF2 exit points. The REFRESH(ALL)
will include the refresh of the EXITS record which suddenly removes the ETF/A
intercepts, which then causes the problem with the incorrect logonid identified
in the ACF75052 message.
A stop and restart of ETF/A resolves the problem.
Note that there should be ETF/A documentation that identifies this and they
recommend stopping ETF/A before issuing F ACF2,REFRESH(EXITS) or
F ACF2,REFRESH(ALL) and then restart ETF/A after the refresh is complete.
Additional Information:
For more details regarding the above ETF/A information please contact ETF/A vendor EKC.