RACF database verification utility program (IRRUT200)
IRRUT200 is a RACF® utility
program that you can use to identify inconsistencies in the internal
organization of each data set comprising a RACF database and to make an exact copy of a RACF data set. You can also use
it to monitor the usable space in a data set. It can perform
the following functions:
- Validate and report errors that are found in the relative byte addresses (RBAs) of each segment of all profiles.
- Validate that index entries point to the correct profile.
- Validate the data set format.
- Issue return codes to signal validation errors.
- Scan the index blocks and print information about problems with the index-block chains.
- Compare the segments of the data set that are actually in use to the segments allocated according to the BAM blocks, and print information about inconsistencies.
- Process the alias index to detect errors and display index blocks.
- Create an encoded map for each BAM block in the RACF data set, which can be used to determine the amount of space that is left in the data set and how fragmented that space is. You can use this information to decide whether the data set needs to be enlarged, or if it needs to be rebuilt to undo the fragmentation that has occurred over time.
- Create a backup copy of a RACF data set. You can use this function if the backup data set has become out of synchronization with the primary data set. With z/OS V2R5, you can use a new option PARM=RENAMEACTIVATE(dsn) to copy the primary RACF data set into the data set that was previously created. RENAMEACTIVATE renames the current data set to dsn, renames the data set to the backup RACF data set name, and activates the new backup..
- Create an enhanced, formatted index report, which displays the 255-byte profile name and profile type information.
Attention:
- If RACF is enabled for sysplex communication, whenever you need to run IRRUT200 against a data set that is active on a system that is a member of the RACF data sharing group, always run the utility from a system in the group. Failure to do so can cause the utility to build an incorrect output data set, or can cause erroneous results in the reports that are generated during the verification phase.
- The JCL must specify the real name of the data set; do not specify an alias.