Copying a data set in the RACF database

IRRUT200 serializes on the input RACF® data set and creates an exact, block-by-block copy of it. This exact copy can help performance when you are maintaining statistics on your backup data set. You can also use it to synchronize a backup data set with a primary data set.

After IRRUT200 finishes the copy, serialization is released on the input data set. If you plan to copy an in-use primary data set to its corresponding in-use backup data set (RVARY LIST output shows the in-use RACF data sets), you can specify PARM=ACTIVATE in your JCL to have IRRUT200 activate the in-use backup copy without allowing the in-use active primary RACF database to be updated between the copy and activate operations, keeping the backup and primary data sets synchronized. Data set verification does not occur during PARM=ACTIVATE processing, so it's a good idea to have a data set verification step in your procedure, before PARM=ACTIVATE. If, instead of using PARM=ACTIVATE, you choose to issue an RVARY after the copy operation to activate the backup copy, there is a window of time between the copy operation and the RVARY command when the primary data set can be updated, causing the backup data set to become out of synchronization. You should ensure that no updates occur between the conclusion of the copying and the time that RACF starts using the copy, or information could be lost.

IRRUT200 copies the RACF data set using the MVS™ utility IEBGENER. Anyone using IRRUT200 must have sufficient authorization for IRRUT200 and IEBGENER if these programs are protected by RACF. Copy performance can be improved by:

Adjusting the BUFNO option on the SYSRACF DD statement and SYSUT1 DD statement
Using DFSORT's ICEGENER (or an equivalent product) as a replacement for IEBGENER

For information on IEBGENER, see z/OS DFSMSdfp Utilities. For information on installing ICEGENER as a replacement for IEBGENER, see z/OS DFSORT Installation and Customization.

You can use IRRUT200 only if you are creating a copy of the data set that is the same size and on the same device type as the input data set. By same device type, we mean the track geometry must be the same (for example, you can copy between a 3390 Mod 2 and a 3390 Mod 3, but not between a 3390 and a 3380). To change the data set size or to copy a data set to a different device type, use IRRUT400. To copy a data set to tape, use a two-step process:

Use IRRUT200 to create a backup copy of the data set on disk.
Use another utility (for example, IEBGENER) to copy the backup copy to tape.

The target of the copy can not be an active RACF data set. If you specify an active primary or backup data set on the system on which IRRUT200 is running, the utility fails. If you need to refresh an active RACF data set, use RVARY to deactivate the data set before running IRRUT200.

To prevent copying a data set over itself, the utility fails if you specify the same data set names for SYSRACF and SYSUT1.