SPONSORED CONTENT
PAM, CleanUp, and Offline, share a common foundation in their use of a single started task and the same exit points within RACF. This unified approach ensures seamless data exchange and processing among the products.
However, each product has its own unique data processing requirements, reflecting their distinct functionalities. While PAM collects additional data beyond what is passed to CleanUp and Offline, all three products write to a centralized History Master File for record-keeping.
PAM allows the user to specify selection criteria to help you narrow the scope of interest to you. The user can specify such criteria as data set and general resource profiles/rules, audit attributes (such as successful read or failed updated) of those files, RACF/ACF2 IDs, as well as the use of attributes of those users (such as Special, Operations for RACF and Non-CNCL, Account, Leader for ACF2) and z/OS commands.
PAM, CleanUp, and Offline, share a common foundation in their use of a single started task and the same exit points within RACF. This unified approach ensures seamless data exchange and processing among the products.
However, each product has its own unique data processing requirements, reflecting their distinct functionalities. While PAM collects additional data beyond what is passed to CleanUp and Offline, all three products write to a centralized History Master File for record-keeping.
Vanguard Cleanup is a feature of the Vanguard Governance, Risk Management and Compliance (GRC) suite. Vanguard Cleanup generates commands to remove unused profiles, permissions, users, and groups from the RACF database using historical RACF requests. Seven batch reports are included in Vanguard Cleanup.
PAM, CleanUp, and Offline, share a common foundation in their use of a single started task and the same exit points within RACF. This unified approach ensures seamless data exchange and processing among the products.
However, each product has its own unique data processing requirements, reflecting their distinct functionalities. While PAM collects additional data beyond what is passed to CleanUp and Offline, all three products write to a centralized History Master File for record-keeping.
The use of an offline RACF database allows testing commands before actually implementing them on an active system. Thus, there is no impact of the tests on any other production application, and also no need for a dedicated LPAR just for these types of tests. Sample applications include merging RACF databases from multiple systems, and large reorganizations or cleanup of profiles.