Hi Peter
When you enter SYS1.RACF.** on the selection screen from AM.1, you select all profiles that MATCH that pattern, i.e., you could see SYS1.RACF.PRIM* and SYS1.RACF.BACKUP profiles listed. If you only want the single generic profile, you could add quotes around the pattern, like 'SYS1.RACF.**'
The Simulated field selections use the RACF database to explain why an access event occurred. As you know, ACCESS records show the INTENT, ALLOWED ACCESS, RESOURCE NAME and PROFILE, but not the permit (or privilege) that was used. To help you understand which permit, or UACC for that matter, the current RACF database (the one selected from SE.1) is used to figure out why access was (or could have been) granted. If no permit can explain the access, no GLOBAL profile present and INTENT <= UACC, then SIM_VIA would implicate UACC as the reason for successful access.
If your intent is to remove access via UACC, you would add PERMITs in your database, run AM.1 with your updated database, spot remaining SIM_VIA=UACC cases, add more permits (or connect remaining users to appropriate groups), and try again.
If you wanted to explain why a user has inappropriate access (to your RACF database), look at the SIM_VIA reason, using the current RACF database, or a backup at the time of the successful access event. Look at all the possible SIM_VIA values in the help panel (or pdf documentation).
------------------------------
Rob van Hoboken
------------------------------
Original Message:
Sent: Mon November 07, 2022 02:58 PM
From: Peter Ten Eyck
Subject: z/Secure and "simulated fields selection"
Trying to make sure I understand z/Secure and "simulated fields selection".
I am using access monitor records (monthly rollup) from the AM.1 screen to check activity on class DATASET profile SYS1.RACF.**, selecting "simulated fields selection" and then selecting "UACC".
Does this run all the access monitor records found within the monthly rollup for that resource and check them against the current RACF DB and report if UACC would be used to grant access? Inferring, if no RACF DB changes have been made, then UACC was not used at the time of the access recoreds were created.
The documentation makes it sound like that is the case.
------------------------------
Peter Ten Eyck
------------------------------