ABEND Codes
Any of the programs and utilities in the FDR family may abend (abnormally end) with any of the following user abend codes. In many cases, a diagnostic message is printed before the abend, so look up any error messages that were printed first. If no message was printed that relates to this abend, then read the explanation below. Contact BMC Support if you need assistance understanding or resolving the error.
Number | Description |
|---|---|
U0100 | OPEN ERROR TRYING TO OPEN A DASD OR TAPE DCB Explanation: Usually proceeded by an FDR324 message. Check the job log for IBM messages that may indicate the reason for the error. |
U0101 | MAXIMUM I/O ERRORS EXCEEDED ON A DIRECT-ACCESS DEVICE Explanation: More DASD I/O errors than are allowed by the MAXERR= operand occurred. If you want to complete the operation in spite of the errors, specify a larger MAXERR= value. However, many data sets may be invalid. |
U0102 | ALTERNATE TRACKS INVALIDLY ASSIGNED Explanation: Alternate tracks are not assigned according to IBM specifications. Can only occur during a dump without BUFNO=MAX. |
U0103 | DISK DEVICE TYPE NOT SUPPORTED OR VTOC TOO BIG Explanation: The type of DASD being backed up or restored is not among those supported by FDR, or for ABR, an internal table was exceeded because the VTOC is too large. |
U0104 | FULL-VOLUME RESTORE TO UNLIKE DISK DEVICE NOT SUPPORTED Explanation: Use FDRDSF, FDRCOPY, or FDRABR data set restore to restore to an unlike device. |
U0110 | INVALID EXTENT DESCRIPTOR IN DSCB OR VVDS Explanation: The descriptor for an extent of a data set in the DSCB or in the VVDS was invalid because it pointed to tracks outside the limits of the volume. |
U0200 | I/O ERROR ON BACKUP DATA SET Explanation: A permanent I/O has occurred on the backup tape or DASD data set. The backup is not usable. This can also occur if a RDJFCB, DEVTYPE, or OPEN fails. |
U0201 | PREMATURE END-OF-FILE ON INPUT Explanation: The end of the backup file was encountered without finding the special FDR trailer record. |
U0202 | INVALID BLOCK READ Explanation: An invalidly formatted block was read from a backup. |
U0204 | INVALID BLOCK READ Explanation: An invalidly formatted block was read from a backup. |
U0205 | NOT AN FDR BACKUP Explanation: A restore process detected that the backup was not created by FDR. |
U0207 | MAXIMUM TAPE BLOCK LENGTH CHECKS EXCEEDED Explanation: See message FDR204. |
U0210 | INTERNAL ERROR IN FDR SOFTWARE COMPRESSION Explanation: |
U0300 | MAXIMUM FOR COUNT FIELD ERRORS ON DIRECT-ACCESS DEVICE EXCEEDED Explanation: More FDR123 messages than are allowed by the MAXERR= operand occurred. If you want to complete the operation in spite of the errors, specify a larger MAXERR= value. However, many data sets may be invalid. |
U0301 | MAXIMUM FOR INVALID RECORD ZEROES ON A DIRECT-ACCESS DEVICE EXCEEDED |
U0302 | INTERNAL END-OF-EXTENT ERROR Explanation: The IGG019YZ module did not have the FDR identifier or was copied from a previous version of FDR or ABR. The most likely cause is that although you have installed a new version of FDR or ABR correctly in a link list (LNKLST) library, there is an older version of IGG019YZ in LPALIB or in a library earlier in the link list (LNKLST) concatenation. You must SCRATCH the older version. |
U0303 | ABR FULL-VOLUME RESTORE CANCELLED, NO VTOC ON THE BACKUP Explanation: Message FDR368 was issued. |
U0304 | INTERNAL ERROR ON FULL VOLUME ABR RESTORE ON MODEL DSCB Explanation: Message FDR374 was issued. |
U0305 | INVALID ABR RESTORE ALLOCATION LIST Explanation: The ABR Restore Allocation List (FDRALLOC) or one of the ABR Protect Lists (FDRPROTA, FDRPROTD, FDRPROTR, or FDRPROTS) have been corrupted. The first 8 bytes of these modules must be the name of the module. |
U0401 | SYSIN DD STATEMENT ERROR Explanation: A SYSIN DD statement is missing or incorrectly specified or an I/O error occurred on the SYSIN data set. |
U0402 | SYSPRINT/SYSPRINx/ABRMAP/SYSMAP DD STATEMENT ERROR Explanation: One of the above DD statements is missing or incorrectly coded or I/O error occurred processing the data set. There must always be a SYSPRINT DD statement, and there must be a SYSPRINx DD statement for each backup TAPEx DD statement when using ATTACH or ABR. |
U0405 | INVALID PARM FIELD SPECIFIED FOR FDR Explanation: This abend indicates that the FDRECALL program did not receive a valid PARM. This usually occurs when the SYNRECAL PROC is modified and the “PARM='&PTR” operand is omitted from the SYNRECAL PROC. |
U0409 | IN FDRTSEL, THE NUMBER OF BACKUP FILES SELECTED HAS CAUSED AN INTERNAL TABLE TO BE EXCEEDED. Explanation: You can reduce the number of backup files selected, or you can increase the table size by specifying TBSIZE=n on the CATLG statement, where “n” is the number of megabytes (2 to 6) to be obtained for the table (default is 2MB). |
U0502 | ONE OR MORE CONTROL STATEMENTS ARE IN ERROR Explanation: One or more of the control statements specified are not recognized by the program being executed. |
U0503 | GENERAL CATALOG OPERATION HAS FAILED |
U0504 | INTERNAL SORT OPERATIONS HAS FAILED Explanation: Message FDR485 was issued. There probably is sort related messages that describe why the sort operation has failed. |
U0600 | REQUIRED DD STATEMENT IS MISSING OR IN ERROR Explanation: A message is always printed with the ddname and reason. |
U0601 | INTERNAL ERROR READING A VTOC Explanation: An FDR mini-dump is printed. |
U0602 | |
U0603 | ERROR ON ABR FULL VOLUME RESTORE Explanation: Message FDR328 was issued. |
U0604 | TAPE VOLUME COUNT ERROR Explanation: More than 20 tape volumes were used for the backup file of one DASD volume (for backup or archive), or POOLDISK wrapped around the pool and wrote over the beginning of the data set. |
U0605 | VTOC ERROR REWRITING THE ABR MODEL DSCB |
U0608 | FDRABR TAPE CATALOG ERROR Explanation: The DASD volume currently being dumped has been restored or modified by a program other than ABR (that is: an old release of FDR or SAR). An attempt to correct the condition and resynchronize the DASD volume and the catalog failed. |
U0609 | DYNAMIC ALLOCATION ERROR Explanation: Message FDR336 shows the specific cause. |
U0610 | INTERNAL WAIT ERROR Explanation: This code can result from exceeding the maximum of nine unique units on TAPEx DD statements when running FDR or FDRDSF in ATTACH mode or FDRABR. |
U0611 | DISK DEVICE TYPE NOT SUPPORTED |
U0612 | EXIT ERROR Explanation: A parameter passed back by a user-written security exit was invalid. |
U0613 | ERROR DETERMINING THE DEVICE TYPE Explanation: FDR issued a DEVTYPE SVC for a device and it failed. |
U0615 | LAST TAPE OPTION ERROR Explanation: ABR detected an abend condition trying to read the validation file for the LAST TAPE option. The IBM abend is printed on the job log. Resubmit the job and ABR will ask for a scratch tape. |
U0616 | VTOC ERROR Explanation: The number of DSCBs per track in the VTOC on a DASD volume exceeded the maximum expected. |
U0619 | ARCHIVE DSCB ERROR Explanation: ABR attempted to ARCHIVE a data set that had invalid or overlapping extents. |
U0620 | INTERNAL ERROR ON THE REMOTE QUEUE DATA SETS |
U0621 | DIRECT ACCESS DEVICE TYPE NOT FOUND IN AN INTERNAL TABLE |
U0623 | ARCHIVE DSCB ERROR Explanation: ABR attempted to ARCHIVE a data set that had an invalid Format 2 or Format 3 DSCB pointer. |
U0624 | INTERNAL DSCB ERROR ON FORMAT 2 OR 3 |
U0625 | TAPE OR DISK DD STATEMENT ERROR Explanation: An ABR TAPEx or DISKxxxx does not point to a supported device type. |
U0626 | |
U0628 | MAXIMUM BACKUP FILES EXCEEDED Explanation: See message FDR338. |
U0629 | INTERNAL LOGIC ERROR Explanation: If program FDRABR is in control, the RESTORE/REORG number in the Archive Control File (ACF) has changed during the ABR jobstep. |
U0632 | INTERNAL COMPAKTOR UNMOVABLE TABLE IS FULL Explanation: The table built by FDR when running under COMPAKTOR for unmovable data sets is full. The backup is terminated, and COMPAKTion is not attempted. The DASD volume is not disturbed in any way. You can increase the size of the table (default: 8000) by specifying CPKUCORE=nnnnn on the DUMP TYPE=FDR statement. However, a large number of unmovable data sets impacts COMPAKTOR's ability to COMPAKT the volume, so the COMPAKTion may not be worth continuing. |
U0633 | INTERNAL LOGIC ERROR IN BUFNO=MAX |
U0634 | MORE THAN ONE VVDS IN THE VTOC Explanation: Message FDR152 with REASON=C was issued. |
U0650 | DISKxxxx DD STATEMENT OPEN FAILED |
U0654 | VTOC READ ERROR Explanation: See message FDR486. |
U0655 | VTOC REWRITE ERROR |
U0658 | MIXED PROGRAM LEVELS Explanation: See message FDR496. |
U0659 | INTERNAL LOGIC ERROR Explanation: Should not occur. Program did not expect this condition. Action: Contact BMC Support for assistance. |
U0701 | ERROR IN COMPAKTOR REBUILD OF INDEXED VTOC OR UPDATE OF VVDS |
U0777 | INTERNAL PROGRAM ERROR, ENVIRONMENT ERROR OR USER ERROR Explanation: Some possible causes are:
Action: Contact BMC Support for assistance. |
U0801 | RESTORE CANCELLED BY OPERATOR OR SECURITY FAILURE Explanation: This abend can also be issued for other errors as described by messages in the listing. For an ABR SNAP or SPLIT with DSNENQ=, a data set was found to be in use by another task (message FDR158) so the SNAP or SPLIT is canceled. Specify ENQERR=NO on the SNAP or SPLIT statement if you want to create the point-in-time backup anyway. |
U0802 | INVALID COMPLETION CODE FROM AN USER EXIT Explanation: A parameter passed back by an user security exit was invalid. |
U0803 | ERROR IN FDRCRYPT (ENCRYPTION OR DECRYPTION) Explanation: A non-recoverable error occurred in FDRCRYPT; see other messages for details. |
U0804 | ERROR IN DE-COMPRESSION Explanation: A non-recoverable error, probably due to bad data, occurred while decompressing a compressed FDR data block. This can occur if a backup encrypted with FDRCRYPT is restored using a library that does not have FDRCRYPT. |
U0805 | FDRINSTANT PROCESS TERMINATED ABNORMALLY Explanation: The FDRINSTANT process detected an abnormal situation and cannot continue. The FDRINSTANT process terminated itself. Preceding FDR nnn messages describe the reason for this abnormal termination. |
U0887 | MESSAGE FDR321 REASON=E OR M WAS ISSUED Explanation: An abend was forced by the DEBUG option. |
U0888 | A NON-TERMINATING ERROR OCCURRED Explanation: One or more FDR, DSF, FDRCOPY, ABR, or COMPAKTOR operations abnormally terminated or ended with diagnostic messages, but the errors were not severe enough to prematurely terminate the entire step. This abend is issued to call attention to the errors. Examine the printout for the error messages causing this abend. If a subtask abnormally terminated, the real abend code is printed in the storage dump and in the FDR319 message. FDR, DSF, FDRCOPY, and COMPAKTOR issue this abend by default when non-terminating errors occur, but the abend can be changed to a return code by updating the FDR Global Options. ABR issues a return code of 12 in this case, by default, but it can be changed in the option table to issue the U0888 abend instead. |
U0991 | LEVEL MISMATCH OR INTERNAL LOGIC ERROR Explanation: Some possible causes are:
Action: Corresponding actions are:
Also, FDRPAS, FDRMOVE, and FDRERASE should always be run with a STEPLIB or JOBLIB, never from LINKLIST. If you desire further assistance after checking the above points, contact BMC Support. |
U0996 | DIAGNOSTIC ABEND Explanation: This is an intentional ABEND activated by a debugging feature (ABENDM=). |
U0997 | INTERNAL DEBUGGING ABEND Explanation: Contact BMC Support if this abend occurs unexpectedly. |
U0999 | RELOAD FAILURE IN FDRREORG |
U1000 | ERROR OPENING XMI FILE FOR OUTPUT |
U1010 | ERROR OPENING XMI FILE FOR INPUT |
U1020 | ERROR OPENING REXX FILE FOR INPUT |
U1030 | ERROR OPENING REXX FILE FOR OUTPUT |
U1040 | RJFCB ERROR FOR REXX FILE |
U1050 | ERROR FREEING WORK FILES |
U1060 | ERROR IN BUILDING COMMAND WITH PDS NAME |
U1070 | ERROR IN EXECUTING ISPSTART COMMAND |
U1080 | ERROR IN MODIFING REXX COMMAND (PDS) |
U1085 | ERROR IN MODIFING REXX COMMAND (PDS) |
U1090 | ERROR IN MODIFING REXX COMMAND (PASSWORD) |
U1095 | ERROR IN MODIFING REXX COMMAND (PASSWORD) |
U1100 | INPUT OPEN FAILED |
U1110 | MODULE ID CHECK FAILED LOOKING FOR CUSTOMER NUMBER |
U1120 | ERROR WITH LOGIC FLOW |
U1130 | ERROR ALLOCATING TERSE INPUT FILE |
U1135 | ERROR ALLOCATING TERSE OUTPUT FILE |
U1136 | ERROR ALLOCATING TERSE SYSOUT FILE |
U1137 | ERROR EXECUTING UNTERSE LOOK AT DATA SET (USERID.IDPRECUP.RPT) |
U1140 | ERROR ALLOCATING COMMAND FILE |
U1150 | ERROR EXECUTING COMMAND LOOK AT DATA SET (USERID.IDPREC.MDUMP) Explanation: Look at data set userid.IDPREC.MDUMP for more information. |
U1160 | ERROR CONSTRUCTING EXECUTE COMMAND |
U1170 | ERROR IN MODIFING REXX COMMAND (PASSWORD) |
U1180 | DDNAME NOT FOUND FOR SHIPPDS |
U1190 | RJFCB ERROR FOR SHIPPDS FILE |
U1200 | ERROR FREE OF SHIP PDS FILE |
U1210 | IDPROUT_ NOT ALLOCATED |
U1220 | ERROR ALTLIB ACTIVATE |
U1225 | ERROR ALTLIB RESET |