The ACF2 intercepts status changed after IPL to NO - it was YES prior to the IPL Why?

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC
• PanApt
• PanAudit

Issue/Introduction

Problem:

Before our IPL, most of the CA ACF2 intercepts said YES, but after the IPL most say NO.  Why is that?  Do we have a problem?

 

Cause:

ACF2 Intercept status only updated to YES if it has been used since IPL or start of ACF2.  This is a one time change.

 

Resolution:

show active

-- ACF2 INTERCEPTS THAT HAVE RECEIVED CONTROL --
DASD-OPEN(YES) DASD-EOV(NO) VSAM-OPEN(YES)
TAPE-OPEN(NO) TAPE-EOV(NO) CATALOG(YES)
USER CALL(YES) EXTERNAL CALL(NO) PROGRAM CALL(YES)
JOB INIT(YES) JOB/STEP TERM(YES) TSO-MVS(YES)
CAT-CVOL(NO) NONVSAM-ERASE(YES) VSAM-ERASE(YES)
VTAM-OPEN(YES)

The display only shows the intercepts that have received control since the last ipl or start of ACF2.  This does not mean that they have been disabled.  The status would change from NO to YES when the INTERCEPTS had been used since IPL or ACF2 started.  When flipped to YES, the display will show that till the next IPL or the ACF2 task is bounced.

 

Environment

Release:
Component: ACF2MS

Resolution

-