Why is there no "ACF99900 ACF2 LOGGING - xx, yy, lid, vol, name, exit" message issued when the dataset access rule explicitly specifies READ(LOG)?

Products

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

Issue/Introduction

Question:  

Why is there no "ACF99900 ACF2 LOGGING - xx, yy, lid, vol, name, exit" message issued when the dataset access rule explicitly specifies READ(LOG)?

 

Answer: 

With the following access rule coded there is no "ACF99900 ACF2 LOGGING - xx, yy, lid, vol, name, exit" message issued when READ(LOG) access is specified in the rule entry.

 

$KEY(SYS1)
PARMLIB UID(****USER*) READ(LOG)

The READ(LOG) specification on a access rule entry does not generate a "ACF99900 ACF2 LOGGING - xx, yy, lid, vol, name, exit" message for READ access. WRITE(LOG), ALLOCATE(LOG) and EXEC(LOG) will generate the ACF99900 message. In all cases the LOG will cause an SMF entry to be written that will appear in the ACFRPTDS report as shown in the table below.

ACCESS          ACF99900 Message   SMF Record Written
-------------   ----------------   ------------------
READ(LOG)              no                 yes
EXEC(LOG)              yes                yes
WRITE(LOG)             yes                yes
ALLOCATE(LOG)          yes                yes

Additional Information:

For more details see the chapter on "Maintaining Access Rules" in the CA-ACF2 for z/OS Administrator Guide.

Environment

Release: ACF2..001AO-15-ACF2
Component:

Resolution

-