IRR401I

Explanation
An abend or an I/O error occurred during RACF® processing, or the restart
key was pressed. relative-byte-address
The RBA (relative byte address) where the I/O error occurred.
request-name
The type of request the RACF manager
was processing when the error occurred.
class-name
For resources other than DASD data sets, the class name of the
resource. The 8-character class name and a hyphen precede the entry
name zzz in the RACF database
index. For example, the index name of TAPEVOL -T12345 is used to locate
profile T12345 in class TAPEVOL.
dsname and nnn
If more than one RACF database
exists, dsname and nnn indicate
the database and sequence number affected.

System action
The indicated request to the RACF manager failed. RACF stops processing the request. An automatic
RVARY might occur when there is an active backup and the device is
varied offline or boxed.

Operator response
Save the exact text of this message and of
any following RACF messages
(particularly IRR413I), and report them to the systems programmer
or the RACF security administrator,
or both.

Programmer response
If message IRR402I, IRR403I, or IRR404I
does not follow this message at the security console, the error occurring
in the RACF database might
not represent a permanent error. Attempt to reenter the RACF request (either the RACF command or the utility program), or cause
the RACF SVC to be invoked
again (such as reentering the LOGON command, rerunning the job, or
trying dynamic allocation again).
If message IRR402I, IRR403I,
or IRR404I does follow this message, then a permanent error might
exist in the RACF database.
Perform the action as specified by the problem determination section
for that message.
If an I/O error is occurring frequently on
the RACF database, an alternate
device can be considered for the next IPL.
If multiple extents
were created for a new RACF database,
this message is issued when the new database is used. Delete the database
and rerun the IRRMIN00 utility to recreate it. Specify CONTIG and
do not specify secondary space on the SPACE parameter in the JCL.

Problem determination
If an abend occurred, do the following
tasks: Get the abend code from this message. If the abend is 000, see
other messages issued for this problem (such as ICH409I) for the abend
code.
Look for a description of the abend code in the following places: RACF abend codes
../com.ibm.zos.v2r1.ieah700/iea3h700.htm. 
If
you cannot find the abend code described in any of the above, see z/OS Security Server RACF Diagnosis Guide for
information about diagnosing documentation errors and reporting documentation
errors to IBM®.
 Diagnostic data is provided
in the LOGREC data.

If an I/O error occurred, determine whether the device
or volume is malfunctioning. For a permanent I/O error, see the LOGREC
data for diagnostic information. Also, see the topic on failure during I/O operations on the RACF database in z/OS Security Server RACF System Programmer's Guide. 
If
message IRR402I, IRR403I, or IRR404I follows this message, see “Problem
Determination” for that message.

Routing code
9 and 11
The complete text of this message
is sent only to the security console. Only IRR401I abend-code ABEND
DURING RACF PROCESSING is sent to the programmer.

Descriptor code
6 for x3E and x22 abends and 1 for all other
abends.