Enter Input Parameter one at a time for 'IRRUT400' or Enter END to use default values nolockinput Enter Next Parameter for 'IRRUT400' or Enter END to specify end of input or Enter QUIT to terminate. end Processing begins All output will be placed in the 'UT400 OUTPUT' file on the 'A' disk. Program 'IRRUT400' is being executed - Please wait - Processing completes Return code from 'IRRUT400' = 0 

The primary RACF database is copied to the RACFVM F200 disk. You can now perform other operations on this copy, such as reporting or making further backups by using DDR or other facilities. 

## Using the RACUT200 and RACUT400 tools 

The RACUT200 and RACUT400 execs that start the RACF utilities are sensitive to the types of disks that are used. It also makes assumptions about the type of device to expect based on the device addresses used. 

In this example, when we attached the F200 minidisk by using F200 as the virtual device address, the device address was rejected by the utility as invalid. Only the common device addresses that are used for RACF database minidisks (200, 300, and 400) are accepted by the tools. 

When we attempted to perform the copy that is shown in Example 4-47 on page 103 by using the full-pack minidisk that is attached at 200 and the F200 minidisk that is attached at 300, the utility failed with a message saying the output data set is invalid. It seems that safety checks exist that are built in to the utilities. 

If you use the 200 and 300 devices, the utilities seem to treat them as through they should be the pair of RACF primary and backup disks, and check the data set names to be as expected. In our case, the real 200 disk and the F200 disk have the data set name RACF.DATASET , and this issue caused the utility to fail. Attaching the F200 minidisk at 400 instead worked well because the utility makes no assumptions about the name of the data set that should appear at device 400. 

## 4.3.8 RACF recovery options 

If a system availability issue occurs, it might be necessary to recover RACF data from a backup. Circumstances also might exist that prevent the RACFVM server from starting. 

This section introduces some basic methods to use to perform recovery of RACF. 

