This is an error internal to the utility. The specified message-number was not found.
System processing continues.
Record the specified message number and contact your IBM® support center.
The indicated range table entry is out of collating sequence.
Utility processing terminates.
Ensure that the range table was assembled and link-edited correctly. Correct the order of the entries which are out of sequence. For information on using a range table, see RACF System Programmer's Guide.
Verify that each entry in the range table appears with its keys in ascending order.
The load module named in the TABLE keyword could not be loaded into storage.
Utility processing terminates.
On MVS™, a STEPLIB DD statement might be missing; on VM, perhaps the member could not be loaded from the user-supplied library.
The indicated error occurred while attempting a BDAM read (READ), BDAM write (WRITE), or BSAM write (LOAD).
The ddname of the file on which the error occurred is listed, along with the RBA (relative byte address) of the byte being accessed.
Check for other errors related to the disk pack on which the database resides.
The first fullword of the range table is binary zeros, indicating no elements in the table, or the string portion of the first element is not binary zeros, as is required.
Utility processing terminates.
Ensure that the range table was assembled and link-edited correctly. For information on using a range table, see RACF System Programmer's Guide.
Space has been exhausted on the specified output RACF database.
Utility processing terminates.
Increase the size of the output database.
This message is accompanied by message number IRR65018I, which can be used to determine how much data has already been processed.
If the database is for input, the utility terminates. If the database is for output, only processing to that database is terminated.
Check for other errors related to the disk pack on which the database resides.
RACF issued a dynamic allocation request (SVC 99) for information about the ddname indicated in the message. However, the return code from dynamic allocation was unexpected.
See “Problem Determination.”
The named database has been successfully opened (BSAM open for INITIALIZATION or BDAM open for PROCESSING) with the given ddname.
Utility processing continues normally.
The utility cannot perform without at least one input RACF database.
Ensure that at least one DD statement has been allocated.
Check the JCL DD statements to verify this.
To prevent updates to the database indicated by ddname, the LOCK function is requested. If the database was not located previously, it is locked at this time.
Utility processing continues.
This message reports the results of the attempt to turn the extend bit OFF in the ICB for the listed ddname. If lock recovery is not successful, the bit will still be ON in that ICB. If lock recovery is successful, the bit has been turned OFF.
Utility processing continues.
The named profile could not be copied to an output database because it has the same name as a profile already copied from another input database. Either the profile is in a class other than DATASET or the NODUPDATASETS option is in effect.
Utility processing terminates.
Check the PARM field of the EXEC statement for this utility. For duplicate names, option DUPDATASETS must be in effect. Also, check to see what class the profile is actually in.
The index entry indicated by entry-name does not appear in the volume list of the profile for the tape volume set to which it points.
The index entry is not copied to an output database. The tape volume set is copied if no other errors exist.
See “Problem Determination.”
Ensure that the index entry and database specified by DD statement are both correct.
The range table specified with the TABLE keyword does not designate all of the members of the set to be copied to the same output database. The member names listed are not prefixed by the characters TAPEVOL-, but the prefix was used when interrogating the range table.
The tape volume set is not copied to output.
Two tape volume sets contain the same name in their volume lists. Therefore, only one of the sets can be copied to the output database.
The entire tape volume set whose members are listed is not copied to output.
The specified abnormal termination occurred during the execution of the utility.
Utility processing terminates.
See “Problem Determination.”
Use the indicated abend code and any previous messages issued by this utility, to determine the appropriate action. See your MVS system codes manual for more information about the abend indicated in the message.
Processing is terminated because adequate recovery cannot be provided.
Utility processing terminates.
Ensure that RACF and the operating system are properly installed. If they are, contact your IBM support center.
Because of an error identified by the message immediately preceding this message on the output, no further processing of the data set indicated by ddname is attempted. The data set should not be used as a RACF database.
Utility processing terminates.
Use the information given by both this and the preceding message to determine the proper corrective action.
An error occurred while performing information retrieval, opening, writing a block, or using BSAM to write empty blocks. This message follows messages IRR65003, IRR65006, and IRR65007. See the previous message description for more information.
Utility processing terminates.
Processing to the database is terminated.
The parameters specified by the user on the EXEC statement are listed.
Utility processing continues normally.
The listed text does not start with a keyword defined to the utility.
Utility processing terminates.
Check the PARM field of the EXEC statement in the JCL.
Ensure that any abbreviations for keywords contain enough significant characters to make the abbreviation uniquely identifiable to the utility.
The utility has more than one keyword with the character string indicated by keyword.
Utility processing terminates.
Ensure that abbreviations for keywords contain enough significant characters to make the abbreviation uniquely identifiable to the utility.
Either the keyword contained in the text or its opposite form was specified previously. The utility uses the first specification of the keyword.
Utility processing terminates.
Ensure that abbreviations for keywords contain enough significant characters to make the abbreviation uniquely identifiable to the utility.
For a complete description of all parameters supported by this utility, see RACF System Programmer's Guide.
The value specified is not acceptable when associated with the keyword listed.
Utility processing terminates.
See “Problem Determination.”
For a complete description of all parameters supported by this utility, see SPL: RACF.
All options, including default options, in effect for the execution of this utility are listed.
Processing continues normally.
UNLOCKINPUT is the only option specified for this execution of the utility.
The utility unlocks the input databases. The utility does not copy the databases.
More than one option was specified. UNLOCKINPUT must be the only option requested for execution.
Utility processing terminates.
Specify the UNLOCKINPUT parameter without any other option.
The database indicated by ddname was unlocked before this attempt to unlock it.
Processing continues normally.
The database indicated by ddname has been unlocked and is now ready for updates.
Processing continues normally.
The database indicated by ddname was not unlocked. Processing terminated.
If other error messages preceded this one, refer to those message explanations to determine the cause of the problem.
Without a locking parameter, the utility cannot continue processing.
Utility processing terminates after the following message.
See following message.
Without a locking parameter, the utility cannot continue processing.
Utility processing terminates.
Specify a locking parameter and invoke the utility again.
The ICB related to the RACF database indicated by the ddname in the message cannot be used by the utility. This message may also be issued when the database is empty.
Utility processing terminates.
Check that you have specified the correct ddname and that it represents the RACF database you want to use. If it is, and the RACF database was not previously formatted using this utility with the PARM=‘NEW’ specification on MVS or with the RACINITD EXEC on VM, then rerun the utility with PARM=‘NEW’.
The validity check that caused the failure can result from an invalid ICB value for the number of templates or BAMs, or an invalid RBA (relative byte address). List the contents of the data set defined by the SYSRACF DD statement to determine the cause of the problem.
The DCB for the input ddname dataset indicates a block size other than 4096. IRRUT400 will only process a data set with LRECL and BLOCKSIZE equal to 4096.
Utility processing terminates.
Ensure that the data set name specified on the ddname DD statement is a restructured RACF database. ICHUTxxx utilities should only be run against nonrestructured RACF databases. IRRUTxxx utilities should only be run against restructured RACF databases.