Job control statements

The following job control statements are necessary for using IRRUT200:

Statement

Use

JOB

Initiates the job.

EXEC

Specifies the program name (PGM=IRRUT200) or, if the job control statements reside in a procedure library, the procedure name.

You can specify PARM=ACTIVATE on the EXEC statement. Specifying this parameter indicates the following:

The input data set pointed to by SYSRACF is an active primary RACF® data set on the system on which the utility is running.
The output data set pointed to by SYSUT1 is the corresponding inactive backup RACF data set on the system on which the utility is running.
The output data set should be activated after the copy completes. No activation password is required to activate the data set.

If the output data set is not the inactive backup data set, both the copy and the activation fail.

The ACTIVATE parameter can ensure that no updates are made to the input data set between the time that it is copied and the time that the copy is activated. However, it can only ensure a synchronized copy if the system on which the utility is running is in RACF sysplex communications mode, or the RACF data set is not shared with another system. If other systems share the backup data set and are not in sysplex communications mode, IRRUT200 can only activate the data set on the system on which the utility is running. To activate the backup data set on the sharing systems, you must issue an RVARY ACTIVE.

The intent of the ACTIVATE parameter is to create a synchronized copy of an active RACF data set, not perform diagnosis. Therefore, the control statements specified in SYSIN are ignored when the ACTIVATE parameter is specified. If you need to verify the RACF data set, do that before you make a copy of it.

If RACF is enabled for sysplex communication in a sysplex with multiple members, to run IRRUT200 specifying PARM=ACTIVATE from one of the members, at least one of the following must be true:

The RACF sysplex communication group (IRRXCF00) is in data sharing mode.
SYSZRACF RESERVEs are being converted to ENQs.

SYSRACF DD

Defines a RACF data set on a direct access device. IRRUT200 requires this data set unless the work data set already contains a copy of the RACF data set. Specify the real name of the data set; do not specify an alias.

SYSUT1 DD

Defines a work data set on a direct access device. IRRUT200 requires this data set unless a RACF data set is used throughout processing. If you specify both SYSRACF and SYSUT1, SYSUT1 cannot point to an active RACF data set on this system. If you specify the same data set that you specify for SYSRACF, IRRUT200 fails.

Do not allocate this data set in the extended addressing area of DASD volumes. To ensure that this data set is not allocated in the extended addressing area, the SYSUT1 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.

Note:

Do not specify the RLSE subparameter with the SPACE subparameter on this statement. The RLSE subparameter causes an abend because IRRUT200 uses IEBGENER to copy the RACF data set.
When PARM=ACTIVATE is specified with SYSUT1, the dataset must be catalogued prior to running this jobstep. The dataset may be created and cataloged in an IEFBR14 jobstep prior to this jobstep.

SYSIN DD

Defines the control data set. The control data set is normally found in the input stream; however, it can be a member of a procedure library or a sequential data set existing elsewhere.

SYSIN is ignored when PARM=ACTIVATE is specified on the EXEC statement.

SYSUT2 DD

Defines a sequential message data set.

SYSPRINT DD

Defines a sequential data set for printed output. The data set can be written to an output device, a tape volume, or a direct access device.

If you specify PARM=ACTIVATE on the EXEC statement, SYSPRINT is not used, and you do not need to specify it.

Guideline: Do not run IRRUT200 under TSO, because doing so can increase the time that the RACF data set is RESERVEd. However, if you do run IRRUT200 under TSO, you can allocate both the SYSIN and SYSUT2 data sets to the terminal. Although you can allocate SYSPRINT to the terminal, you should allocate it to SYSOUT, because IRRUT200 might produce a large volume of output.