Executing IRRUT400

The following job control statements are necessary for executing IRRUT400:

Statement: Use
JOB: Initiates the job.
EXEC: Specifies the program name (PGM=IRRUT400) or, if the job control statements are in a procedure library, the procedure name. You can also request IRRUT400 processing options by specifying parameters in the PARM field. See Specifying parameters.
SYSPRINT DD: Defines a sequential message data set. The data set can be written to an output device, a tape volume, or a direct access volume.
INDDn DD: Defines a RACF® input database. See Specifying the input database.
OUTDDn DD: Defines a RACF output database. This statement is not required if you are executing the utility only to identify inconsistencies in a RACF database, or to unlock a database. See Specifying the output database.
Do not allocate this database in the extended addressing area of DASD volumes. To ensure that this database is not allocated in the extended addressing area, the OUTDDn DD statement must not contain the keyword parameter EATTR (unless its value is the default NO). Since EATTR=NO is the default, it is not necessary to include this on the DD statement.

If you are redistributing the profiles across more than one data set, you must also provide a range table. The range table indicates which profiles are placed in each output data set (using the TABLE keyword to make the determination). See The database range table and Selecting the output data set. If any of the input data sets are RACF-protected, you must have at least UPDATE authority for those data sets.

Restriction: If the range table is put into a STEPLIB, that STEPLIB must be APF-authorized. If it is not, the STEPLIB is not searched for the range table.