Tracking File in a Multi-LPAR Environment for CA Cleanup for RACF

To ensure optimal tracking file functionality in a multiple LPAR environment, consider the following recommendations based on security database sharing and Remote Sharing Facility (RRSF) enablement:
cleanup121
To ensure optimal tracking file functionality in a multiple LPAR environment, consider the following recommendations based on security database sharing and Remote Sharing Facility (RRSF) enablement:
  • Two systems share one security database and RRSF is not enabled
    We recommend using one shared tracking file.
    The use of two tracking files is supported but not common because of the additional overhead. Two tracking files may be used when IBM's Global Resource Serialization (GRS) or CA Multiple Image Manager (MIM) cannot be used to propagate enqueues. If using two tracking files, always use both as input for reports.
  • Two systems have separate security databases and RRSF is enabled
    We recommend using both tracking files.
    Report using both tracking files as input because this is one logical security system. Use the IRRDBU00 from the "master"system.
  • Two systems have separate security databases and RRSF is not enabled
    We recommend using both tracking files. The only way to track referenced or unreferenced items accurately is to have one tracking file per security database. Report separately because these are two distinct security systems.