When redistributing or copying a RACF® database, you must code an OUTDDn statement for every output data set that the utility will create. The ddnames of the statements defining the output data sets have a relationship to the range table. If a range table is provided, IRRUT400 uses the greatest data set number in the table as an upper boundary for processing. If no range table is provided, the upper boundary is 1. IRRUT400 does not process any output data set identified by a ddname with a number greater than the upper boundary. You can specify as many as 255 output data sets on statements named OUTDD1 through OUTDD255.

Output data sets can be new or old direct-access data sets. RACF uses only the first extent. Therefore, do not create any data sets with a secondary space allocation. The output data set cannot be the same as any data set that is pointed to by an INDD statement.

IRRUT400 fails if an output data set is an active primary or backup data set on the system on which the utility is running, or if you attempt to copy a data set into itself by pointing to the same data set with INDD and OUTDD.

If you are executing IRRUT400 only to identify inconsistencies in the RACF databases, do not code an OUTDDn statement. See Processing of conflicts and inconsistencies for a description of inconsistencies found in the databases.

If you are running IRRUT400 to unlock a database, you do not need an OUTDDn statement. See Specifying parameters for information on the UNLOCKINPUT keyword.