Messages from FDR, DSF, and ABR (FDRnnn)

FDR000

UNABLE TO INVOKE IEBCOPY

Explanation: The FDRREORG interface for IEBCOPY PDS compression (FDRBCOPY) was not able to link to the IBM IEBCOPY program for non-compress functions.

UNABLE TO CREATE RECALL ACEE – SAF RC=n RACF RC=n

Explanation: This form of the FDR000 message indicates that auto-recall was not able to create a security ACEE for the recall process.

FDR001

NONSTANDARD RECORD ZERO -- cccchhhhrrkkllll -- function CONTINUING

Explanation: FDR detected a non-standard record zero (R0) in a track on the volume. The count field of the R0 is printed in hex. A standard IBM record zero format has an “rrkkllll” field of 00000008 -- that is, record number zero, key length zero, and data length eight. FDR does not RESTORE a track that had a non-standard record zero during the backup.

Action: Contact BMC Support for assistance.

POSSIBLE SPACE ERRORS IN VTOC -- ENTIRE PACK WILL BE DUMPED

Explanation: FDR detected an I/O error or logical error reading the VTOC. A mini-dump is printed detailing the error. FDR continues processing, dumping the entire DASD volume.

Action: Contact BMC Support for assistance.

NOT AN FDR TAPE DSN=dsn

Explanation: 1. The input for a restore (“dsn”) is not an FDR created backup.

2. The JCL specifies the wrong serial numbers, or specifies the serials in the wrong order. FDR must always read the backup from the beginning; it cannot start in the middle of a multi-volume backup. If you specified the volume serials of the backup tape in JCL, check the order of the serials.

3. The FDR backup file may have been written over.

Action: “dsn” is the tape data set name. A mini dump is printed displaying the first tape block read. An U0205 abend is issued.

TAPE BACKUP IS INCOMPATIBLE WITH RESTORE DEVICE

Explanation: An attempt was made to do a full-volume restore or copy to an unlike device type (for example: 3380 to 3390). Use FDRDSF, FDRCOPY, or FDRABR data set restore to restore to a device with different device geometry. It can also occur when attempting to do a full-volume restore to a smaller DASD of the same type (for example, 3390-3 to 3390-2).

Action: The FDR header read is printed in a mini dump. An U0104 abend follows. If necessary, contact BMC Support for assistance. If you want to force FDR to restore to a smaller DASD of the same type, specify PROT=NONE on the RESTORE or COPY statement. The FDR014 message is still printed, but the RESTORE or COPY is attempted. You get I/O errors if any tracks above the capacity of the smaller DASD must be restored. If all of the data on the larger DASD fits on the smaller DASD, use COMPAKTOR to restore and relocate the data.

FDR023

INVALID EXTENT DESCRIPTOR [REASON=reason DSN=dsn]

Explanation: FDR read a DSCB (Format 1 or 3) that contained an invalid extent description. If a mini dump is printed, the first five bytes of the DSCB printed after the registers in the mini-dump are the cylinder, head, and record number (CCHHR) of the DSCB in error. If REASON= is printed, it is one of the following:

1

ENDING CYLINDER TOO LARGE

2

STARTING TRACK TOO LARGE

3

ENDING CCHH BEFORE BEGIN

4

ENDING TRACK TOO LARGE

Action: Depending on the operation, FDR may continue the backup and dump all tracks on the volume, or may terminate with an U0110 abend.

Scratch the bad data set.

If an absolute track statement was specified (SELECT FROM/TO), the user specified a cylinder address greater than maximum cylinder number or a track number greater than the tracks per cylinder. Correct the SELECT statement.

If necessary, contact BMC Support for assistance.

UNSUPPORTED DISK DEVICE TYPE ON DDNAME=ddn

Explanation: FDR encountered a DASD device or a backup of a DASD device that is not supported. It is possible that a back level release of FDR is being used.

Action: Contact BMC Support for assistance.

text

Explanation: Messages from the FDR diagnostic mini-dump processor. BMC Support will help you interpret them.

FDR101

PROGRAM NOT APF AUTHORIZED

Explanation: Most FDR programs must be executed as an APF-authorized program in order to execute correctly. This program detected that it was not executing authorized. This most often occurs when you are testing a new version of FDR with a STEPLIB that has not been authorized.

Action: 1. Authorize the library where you executing the FDR program. You can update a library list in SYS1.PARMLIB and you may be able to input a console command that authorizes the library.

2. Move all FDR programs to an authorized library.

Contact BMC Support if you need assistance.

DATA SET NOT ON VOL=vol DSN=dsn

Explanation: 1. FDRCOPY cannot MOVE a multi-volume VSAM cluster or COPY a multi-volume VSAM cluster to the same name.

2. FDR did not find the Format 1 DSCB for data set “dsn” in the VTOC of volume “vol”, but it expected it to be there.

Action: 1. See .VSAM Special Considerations vBase for further information. FDRMOVE can MOVE a multi-volume VSAM cluster.

2. There are a variety of unusual conditions that can produce this message. Contact BMC Support for assistance.

FDR111

VOL=vol DSN=dsn reason
NUMBER OF TRACKS NECESSARY=tttttt
EXTENT CYL=ccccc TRK=tt,CYL=ccccc TRK=tt

Explanation:  This message is printed for data set restores when a preallocated output data set is too small or has other errors. It prints the first two forms of the message shown above, and then repeat the last form for all extents of the input data set (up to 128). “reason” can be:

HAS INSUFFICIENT SPACE nnnnnn TRACKS

The data set is too small to hold all of the tracks to be restored. “nnnnnn” is the size of the preallocated data set. The next FDR111 message shows the number of tracks to be restored “tttttt”. This can also occur for data sets allocated by FDR if the CYL= or TRK= operands specified a size too small for the active tracks of the data set, or when DATA=ALL is specified with the RLSE or %FREE= operands.

IS UNMOVABLE

The input data set is flagged as unmovable, which usually means that it contains location-dependent data and cannot be restored to different track addresses. The additional FDR111 messages show the extents that the data set occupied on the original volume; it must be restored to the same track addresses.

IS TOO LARGE

A VSAM index component was larger than the index on the backup. It must be the same size.

Action: The data set is not restored. Scratch the preallocated data set. In most cases, simply re-run the restore and FDR allocates the data set properly. In some cases you may need to preallocate the data set with the allocations shown (for example, FDR cannot allocate an unmovable data set with more than three extents). If you get this message for a data set allocated by FDR (not preallocated), a possible cause is that the space request was reduced by STOPX37, ACC/SRS, or other space recovery software package. The installation must code the rules for such software so that allocations requested by programs whose names start with “FDR” are not altered. If desired, contact BMC Support for assistance.

INVALID DEVICE TYPE OR VTOC TOO LARGE
INVALID DEVICE TYPE – FDR TERMINATED

Explanation: The DASD device type is not one supported by this version of FDR or for ABR the VTOC may contain too many entries for an internal table.

Action: An U0103 abend follows. Contact BMC Support for assistance.

ALTERNATE ERROR REASON=n ON TRACK CYL/HEAD=cccchhhh
ASSIGNED TO PRIME CYL/HEAD=cccchhhh PRIME R0=cccchhhh

Explanation: FDR detected an error or unusual condition with the alternate track assignments on the DASD volume being processed. The message displays the cylinder and head number of the failing alternate track in hex. “ASSIGNED TO PRIME” is printed if FDR can determine the prime track; it displays the cylinder and head of the prime track and the count field of record 0 (R0) on the prime track (the latter should point to the alternate track. This message is only produced when you are taking a backup to a sequential DASD data set (such as Archiving to DASD) or when you specify BUFNO=nn.

The reason code “n” can be:

1

I/O error occurred reading this alternate track. If the IOB in the mini-dump starts with “46008000”, the volume has no alternate tracks (this occurs with some DASD subsystems and with VM mini-volumes). As long as there are no alternate tracks assigned on the volume, this message can be ignored.

2

This alternate track is flagged as a defective alternate. FDR bypasses it. No corrective action is required.

3

The alternate track is assigned to a prime track. The alternate home address does not have the flag byte set indicating that this is an alternate track.

4

I/O error occurred reading the prime track assigned to this alternate.

5

The prime track's home address flag byte did not indicate that this is a defective track.

6

The prime track's record zero (R0) did not point back to this alternate track. (PRIME R0=) contains data read. If the PRIME R0 points to another alternate track, this track has had an alternate assigned to it multiple times.

Action: FDR continues, bypassing this alternate. If the prime data track is to be dumped, FDR may issue additional error messages. FDR121 REASON=1 can usually be ignored. Contact BMC Support for assistance.

statistics

Explanation: FDR displays status information at the successful termination of a backup or restore subtask. A second FDR122 is printed displaying the values under each header. The character “n” after the FDR122 indicates the format of the backup and is “N” (New) format or “S” (Split) format. These headers appear above the statistics values (some values are displayed only for backups, not for restores):

BYTES

Number of bytes of data dumped to tape or read from tape (for DSF, all bytes read even if not restored.)

DSK TRK

Number of DASD tracks accessed to perform this function.

T BLKS

Number of tape blocks written or read. On COPY this is an internal number of blocks passed from the dump task to the restore task.

RESTART

Internal field.

STIMERS

Internal number of STIMER commands issued.

ERRS

Using BUFNO=MAX, this is the number of tracks in error.

ACT DSK

Actual number of DASD tracks dumped or copied. For FDRCOPY, it is the number of tracks read, which is not necessarily the number of tracks written.

LOW

If not BUFNO=MAX, this is the lowest number of STIMERS issued on one cylinder. If BUFNO=MAX, this is the number of retries on tracks with data checks. Unless an FDR129 error message is displayed, the retries were successful.

HGH

If not BUFNO=MAX, this is the highest number of STIMERS issued on one cylinder. If BUFNO=MAX, this is the number of count fields encountered with a CCHH that did not match the track it resides on; this is normal on a VM mini-disk but may indicate errors on other volumes.

DEXCP

The number of DASD EXCPs issued by this subtask to dump or restore this volume. This number may be less than number of EXCPs recorded by SMF. For FDRCOPY, this is the total of EXCPs on the input DASD plus the number of tracks written to output DASD volumes; if FDRINSTANT is used to copy data sets (with FlashCopy, SnapShot, or TimeFinder), the output DASD count does not represent actual EXCPs.

NUMDS

Number of data sets processed in this backup. If an ABR incremental backup, this value includes the backup of the ABR Model DSCB.

COMP KBYTE

The number of kilobytes (kB) (1024 bytes) the data was compressed by FDR software compression (COMPRESS=). This field is not displayed if software compression was not requested (FDR cannot display the results of hardware compression, for example, IDRC)). It is displayed only for backups.

OPERATION STATISTICS FOR type VOLUME vol

Explanation: This form of the FDR122 message may appear as the header for a table of statistics about the certain FDR operations that were performed on the volume indicated; currently the previous form is used for backup, restore and print operations and this form is used for most other operations (such as SNAP). The table may include some or all of the data below. For non-backup/restore operations (such as SNAP), many of the statistics printed may be zero or very small; this is normal.

CYLINDERS ON VOLUME

Total number of data cylinders on volume being processed.

DATA SETS PROCESSED

Number of data sets selected.

BYTES READ FROM DASD

Total number of bytes actually backed up from the volume.

BYTES WRITTEN TO DASD

Total number of bytes actually restored to the volume.

BYTES ON BACKUP

Total number of bytes actually written to or read from the backup. For uncompressed backups, this is slightly higher than the DASD bytes because of control data. For compressed backups (COMPRESS= on the DUMP statement), this is the bytes after compression.

COMPRESSION SAVINGS

Percentage of the backup file size saved by FDR compression (COMPRESS= on the DUMP statement). This is calculated as the “Bytes on Backup” divided by the bytes that would have been written to the backup without compression (not displayed). This is zero unless COMPRESS=ALL was specified; compression savings from IDRC tape hardware compression is not displayed.

DASD TRACKS BACKED UP|WRITTEN

Number of data tracks read from or written to the volume.

BACKUP BLOCKS WRITTEN|READ

Number of physical blocks written to or read from the backup file.

DASD EXCPS

Number of write/read I/O requests issued to the volume.

BACKUP FILE EXCPS

Number of write/read I/O requests issued to the backup file.

CPU TIME (SECONDS)

The CPU (TCB) time required to process this volume, in seconds and thousandths of a second.

ELAPSED TIME (MINUTES)

The actual time, in minutes and tenths, required to process this volume.

BACKUP|RESTORE TIME (EXCLUDING MOUNTS)

The actual time, in minutes and tenths, required to process this volume, excluding the time spent waiting for input or output tape volumes to be mounted (at OPEN or EOV).

BACKUP COPY n ON type DSN=dsn VOL=vol

Documents the location of the backup file created. “n” is the copy number (1 or 2) and “type” is DISK or TAPE.

RESTORE FROM DSN=dsn

Documents the name of the backup file being restored.

FDR123

COUNT RECORD ERROR ON TRACK X'cccchhhh' REASON=n

Explanation: FDR detected an error on the count fields of the cylinder (cccc in hex) indicated. Reason codes 1 through 6 can only occur if BUFNO=MAX is not in effect (BUFNO=MAX is the default). The track number (hhhh in hex) printed may not be accurate. An I/O error may also occur during the actual dump of data from the track. If a cylinder has more than one count error, only one FDR123 message is issued per track. The description of DASD I/O Errors in section FDR-DSF-CPK-ABR-I-O-Error-Recovery may be helpful in understanding the error.

The reason code “n” may be:

1

The number of count fields read on this cylinder exceeded the maximum number FDR expects for this device. The remaining count fields are bypassed.

2

I/O error occurred reading the count fields. The track number in the message is probably not correct. THE ENTIRE CYLINDER IS BYPASSED. The IOB in the mini-dump details the error.

3

The number of bytes on this cylinder and head exceeds the maximum set by FDR. If it does not exceed the FDR maximum buffer size FDR processes this track. 

4

The count field is out of sequence. The count field encountered has a head number lower than the previous count field. FDR processes this record as if it was the next sequential record. This track may not be correctly dumped.

5

The length of the count fields on this track developed into a negative number. FDR terminates immediately with an U0300 abend.

6

The track number on one or more count fields was higher than the maximum number of tracks per cylinder for this device (usually 15). FDR bypasses the records from the point of error to the end of the cylinder. The track number in the message has no significance.

7

The count field has an incorrect cylinder and track number using BUFNO=MAX. Since this may be a normal condition (such as on VM volumes), this reason is printed only if you specify PRINT=ALL on the DUMP statement.

8

The data read from this track appears to exceed the capacity of the track. The data read is still dumped. This track may cause an error when restored.

Action: An FDR mini-dump is printed. The unlabeled block of storage at the end of the mini-dump contains the count fields read. Each count is 8 bytes (2 words) long and consists of the CC (cylinder), HH (head), R (record), K (key length) and DD (data length). The count field causing the error is usually the first one on the third line of counts. Contact BMC Support for assistance.

FDR124

FORMAT 4 ERROR REASON= reason - id

Explanation: FDR detected a problem with the Format 4 DSCB on a volume. The Format 4 DSCB describes the VTOC itself. The VTOC may be improperly formatted. “reason” is a reason code, possibly with explanatory text; “id” is the DSCB count field. The reason code “n” may be:

1

More than one Format 4 DSCB was found, or the first DSCB in the VTOC was not a Format 4. This may be due to an IBM problem.

2

FDR found that the Format 4 contained zero free DSCBs, plus the VTOC high water mark was set to the first Format 5 DSCB. This is the condition CPK would leave the volume in if an abend or system crash occurred during the restore phase. This volume may be partially restored. This is a serious problem. The volume should be placed offline until the error is corrected. If you must dump the volume, specify PROT=NONE on the DUMP statement.

3

Label track is invalid. The label track (cylinder 0 track 0) does not contain a properly formatted volume label.

4 – VOL SIZE < DEVICE SIZE

The number of cylinders in the VTOC is less than the actual number of cylinders on the device.

6 – TOO MANY VTOC ENTRIES

ABR found too many VTOC entries on this volume and an internal table was exceeded. An U0103 abend follows. The VTOCCORE= operand may need to be specified as an override; contact BMC Support for this setting.

8

An unknown DSCB type was found.

9 – VOL SIZE 1 CYL IN VTOC

The Format 4 DSCB indicates that the volume contains only one cylinder, but the physical size of the volume is more than one cylinder.

Action: An U0602 abend is issued. List the VTOC in hex with:

//LIST EXEC PGM=IEHLIST

//SYSPRINT DD SYSOUT=*

//DISK1 DD UNIT=SYSALLDA,VOL=SER=vol,DISP=OLD

LISTVTOC VOL=3390=vol,DUMP

/*

and contact BMC Support for assistance.

FDR125

I/O ERROR READING THE VTOC X'cccchhhh' VOL=vol TRACK WILL BE BYPASSED

Explanation: FDR detected an I/O error reading the VTOC on the cylinder and track indicated in hex. An FDR mini-dump is printed. The DSCBs stored on this track of the VTOC is not processed. This error may also be caused by an improperly formatted VTOC track. CPK cannot restore from this backup.

Action: Correct the VTOC or contact BMC Support for assistance.

FDR126

ERROR PROCESSING FORMAT 2 OR 3

Explanation: FDR attempted to read the Format 2 or 3 DSCB associated with a Format 1 DSCB. The VTOC location pointed to by the Format 1 DSCB does not contain a DSCB of the proper type. The DSCB chain for this data set may be broken.

Action: Correct or scratch this data set or list the VTOC in hex with:

//LIST EXEC PGM=IEHLIST

//SYSPRINT DD SYSOUT=*

//DISK1 DD UNIT=SYSALLDA,VOL=SER=vol,DISP=OLD

LISTVTOC VOL=3390=vol,DUMP

/*

and contact BMC Support for assistance.

DISK TRACK CROSS-CHECK ERROR CCHH=cccchhhh - DUMP CONTINUING

Explanation: FDR detected that the record length fields developed for a tape block were inconsistent with the count fields of the data dumped. The cylinder and track (in hex) of the failing track is displayed.

Action: Contact BMC Support for assistance.

INVALID RECORD ZERO ON TRACK X'cccchhhh' DATA X'cccchhhh'

Explanation: The track specified has an invalid record zero (R0). The count field of R0 should always contain the ID of the track it resides on (except for tracks with assigned alternate tracks). The cylinder and track (in hex) of the failing track is displayed, along with the count field of R0.

Action: FDR bypasses this track on the DASD and continue processing the volume. Contact BMC Support for assistance.

FDR129

I/O ERROR ON DISK PACK - LAST [HOME/SEEK] ADDRESS READ X'cccchhhh' [tct-error]

Explanation: An I/O error or logical error was detected by FDR on this volume. The cylinder and track (in hex) printed may not be accurate. An IBM IOS000I message may also have been printed on the job log.

This error can also be issued when a TCT DUMP operation is attempted with a TAPEx volume in a device that does not support TCT commands. The FDR149 messages that follow show the IOB=C6008000 and SENSE=80000000.

If tct-error is “NOT A DISK”, this indicates that the TAPEx DD statement specified for a TCT DUMP operation does not specify a DASD volume. The TAPEx DD statement for TCT DUMP operations requires a DASD device.

If tct-error is “MULTIVOL ERROR”, this indicates that the TAPEx DD statement specified for a TCT DUMP operation specifies multiple DASD volumes. The TAPEx DD statement for TCT DUMP operations can only specify a single DASD volume.

If tct-error is “TCTxxx=CONTAINER NOT FOUND”, this indicates that a TCT RESTORE operation is being performed and the CLOUD Container specified does not exist in the specified CLOUD.

Action: An FDR Mini-Dump is printed detailing the I/O error (see Mini-Dump” in Section Introduction-to-Messages). FDR attempts to continue processing from this point, bypassing the track in error. A FDR150 message may also be issued. If the error is a data check or other hardware problem, the volume must be corrected. See DASD I/O Errors in Section FDR-DSF-CPK-ABR-I-O-Error-Recovery for help in understanding the error. Contact BMC Support for assistance.

I/O ERROR DSN=*** I/O ERROR

Explanation: This is followed by FDR149 messages when DUMPing to Transparent Cloud Tiering (TCT) that can be used to diagnose the error.

Action: When DUMPing to Transparent Cloud Tiering (TCT), some possible causes are that the TAPEx DD statement does not point to a DASD device that supports TCT, or that the cloud name is not correct for this DASD control unit. This is followed by FDR149 messages that can be used to diagnose the error.

I/O ERROR DSN=*** [HTO TIME-OUT]

Explanation: A TCT operation did not complete within a reasonable amount of time.

Action: Contact the hardware vendor or BMC Support.

YOU ARE NOT LICENSED FOR FUNCTION - function

Explanation: You attempted to execute an FDR function, but that function is not included in your current FDR license. “function” indicates the failing function, such as REORG (FDRREORG), INSTANTBKP (FDRINSTANT), and others.

Action: If you believe you are licensed for this function, contact BMC Support for assistance. Check to be sure that you are executing FDR from the library containing the latest copy of FDR installed at your site. If you would like to test an unlicensed product, contact your BMC Sales Representative.

FDR138

UNABLE TO function DSN=dsn REASON=reason

Explanation: A RESTORE, COPY, or MOVE did not complete successfully. “reason” is a reason code plus explanatory text as shown below. Some of the reasons below occur only during logical restore (to an unlike device or when re-blocking) but others can occur on any data set restore.

The reason code “reason” may be:

4 - CONTAINS TRACK OVERFLOW RECORD

Data sets formatted with track overflow records (supported only on 3350 and earlier DASD) cannot be restored logically)

7 - UNSUPPORTED DSORG

These data sets are not supported for logical restore.

• BDAM ABSOLUTE
• BDAM VARIABLE or UNDEFINED
• ISAM not supported – see member ISAM in the Installation Control Library (ICL).
• CLUSTER NOT LOADED
• KEY RANGE or SPANNED
• NON-ICF VSAM
• VSAM Multi-Volume
• EXTENDED FORMAT (EF)

9 - BLOCK SIZE LARGER THAN TRKSIZE

On a logical restore, a data block larger than the output track size was found. Use BLKF= if the data set is DSORG=PS.

9 - TOTAL BLOCKS LARGER THAN TRKSIZE

On a logical restore where track image mode was forced (see message FDR139), the data from one track of the input data set does not fit on a track of the output data set. Message FDR151 is printed to identify the output track. This message may also occur if an input data set was identified as having multiple extents not in ascending order on the backup or input DASD, indicating that track image mode was attempted but failed, probably because of small blocks in the input data set (for a PDS from a 3380 being restored to a 3390, this occurs if the PDS has a directory with over 45 blocks). See “Action”.

A - CATALOG/VVDS/PAGE TO UNLIKE

Logical restore cannot restore catalogs, VVDSs, PAGE, or SWAP data sets.

A - SYS1.LOGREC OR VTOCIX TO UNLIKE

Logical restore cannot restore VTOC indexes or LOGREC data sets.

B - DATA SET IS UNMOVABLE

Logical restore cannot restore data sets flagged as unmovable.

F - SPACE IS TOO SMALL FOR DATA SET

During a logical restore, the allocated space was too small for the reformatted data. If FDR allocated the data set, this may be due to small blocks in the data set. If possible, FDR attempts to extend the data set to a secondary extent. The CYL= or TRK= operands may be used to increase the size of individual data sets.

L - I/O ERROR WRITING TO DATA SET

Another message documents the error.

Q - REBLOCK ERROR - reason

A logical restore error occurring while trying to re-block a data set (the BLKF= operand of RESTORE). “reason” briefly describes the error.

R - PDS DIRECTORY reason

A logical restore error occurred while processing the directory of a PDS (DSORG=PO). “reason” briefly describes the error.

T - TAPE BLOCK DEBLOCK ERROR

An FDR data block was improperly formatted. The backup may have been corrupted.

U - END OF FILE NOT FOUND ON INPUT

During a logical restore, an expected EOF record was not found within the dumped tracks of the data set; the data set may be usable.

V - VSAM ERROR reason

A logical restore error occurred while processing a VSAM cluster. “reason” briefly describes the error.

W - MISSING TTR

X - DATA SET WAS EXCLUDED

Y - TRACKS OUT OF ORDER FROM INPUT

On a logical restore, the tracks of the original non-VSAM data set were in multiple extents and not in ascending order on the backup or input DASD. See “Action”.

Action: Correct the error, if possible, and rerun. If this was a logical restore or copy/move to an unlike device, it may be possible to do a physical restore/copy/move to a like device (same device type). If the error was due to multiple extents not in ascending order on a non-VSAM data set (REASON=Y or REASON=9), it may be possible restore or copy/move to a like device to reallocate the data set in a single extent then copy/move it to the unlike device (or use COMPAKTOR on the input DASD to combine the extents of the data set). Read member UNLIKE in the Installation Control Library (ICL) for more details. Contact BMC Support if you need assistance.

FDR139

ERROR USING THE READ MULTIPLE CKD COMMAND (5E) - NEW PERFORMANCE OPTION TERMINATED

Explanation: FDR detected an error using the 5E (RMCKD) command. This control unit may not support the command.

Action: FDR reverts to the previous performance option. Contact BMC Support for assistance.

FDR149

FDR150

DISK TRACK X'cccchhhh' BYPASSED ERROR WHEN DUMPED

Explanation: FDR detected an I/O error or logical error when this track was dumped. Another message may have been issued detailing the error. Since the data was not properly dumped, FDR does not restore the track on the restore function.

Action: The data set associated with this track may be incomplete. On a data set restore, message FDR155 indicates the dsname. If message FDR155 does not appear, the track was not needed for this restore. If you need assistance, contact BMC Support.

FDR151

I/O ERROR DSN=dsn

I/O ERROR WRITING DISK TRACK X'cccchhhh' VOL=vol TRACK BYPASSED

Explanation: FDR detected an I/O error writing the DASD track at cylinder cccc track hhhh (both are in hex). For a data set restore only, the first FDR151 message identifies the data set that contains the track.

Action: FDR continues the restore operation. This track is bypassed. See DASD I/O Errors in Section FDR-DSF-CPK-ABR-I-O-Error-Recovery for help in understanding the error. Contact BMC Support for assistance.

FDR152

ICF VSAM ERROR REASON=n DSN=cluster/component VOL=vol

Explanation: An I/O error or logical error exists within the SYS1.VVDS data set or in the VVDS information for the cluster or component indicated on volume “vol” (this error may also occur for non-VSAM data sets on SMS-managed volumes). On a restore, FDR compares the characteristics of the cluster on the backup file with those of the cluster being restored to on DASD; if some required characteristic does not match, this message details that mismatch. The VVR/NVR from the backup and the DASD is printed for certain types of errors. The reason code “n” may be:

1

VSAM clusters exist on the volume, but FDR failed to find the SYS1.VVDS data set on the output DASD or on the backup file. The VVDS may not exist or FDR encountered an error trying to find it. The IOB details the error.¹

2

The number of extents in the SYS1.VVDS data set was zero.

3

The SYS1.VVDS contains more than 3 extents. FDR had an I/O error or logical error finding a Format 3 DSCB. The IOB details the error.¹

4

An I/O error or logical error was detected when FDR read or wrote entries within the SYS1.VVDS data set, or the VVDS contains no active records (even though there are VSAM clusters on the volume). For an I/O error, the IOB details the error.¹

5

The length of a VVR/NVR entry within the VVDS is zero or negative.¹

6

The length of all of the VVR/NVR entries within a block of the VVDS exceeded the length in use within the block.²

7

A VVDS record indicates that the length of its in-use data exceeds 4096.³

8

An error occurred when DSF attempted to find one of the associated components for this cluster. The component may be in the VVDS but not in the VTOC. The IOB details the error.

9

FDR is unable to store all of the VSAM component and cluster names in its internal table. A large number of VSAM clusters must exist on the volume. Specify the keyword ICFCORE= on the DUMP TYPE= statement or permanently increase the ICFCORE value in the FDR Global Options.

A

A cluster specifies a catalog name that was not found in the catalog entries stored in the first record of the VVDS.

B

FDR could not find the volume information/allocation cell (type 23) in the VVR record, or an individual cell had an invalid length.

C

More than one SYS1.VVDS data set found on the volume. The operating system uses the VVDS that contains the current DASD volume serial number in the name. More than one VVDS can be created if a volume with a VVDS is renamed and a VSAM cluster is allocated using the volume with the new serial number. If the VVDS with the incorrect volume serial does not have any current clusters cataloged within it, use SUPERZAP to turn off the PASSWORD indication in the DSCB and scratch the data set using IEHPROGM. A backup completes but no VSAM clusters are restored from it and non-VSAM, SMS-managed data sets may not be restorable. A restore issues an U0634 abend, so no VSAM or SMS-managed data set restores are done to this volume until the condition is corrected.

D

The volume serial in the data set name of the VVDS (SYS1.VVDS.Vvolser) does not match the volume serial of the DASD. This can occur if a volume was copied or restored to a new DASD volume serial but the VVDS was not renamed. Another possible cause is the DUMPCONDITIONING option of DFSMSdss. This is only a warning; FDR backs up the volume properly, using that VVDS. However, VSAM and SMS-managed data sets on the volume are not usable until the condition is corrected.

E

FDR did a GETMAIN for above the line storage for a VSAM table but the GETMAIN failed. Try increasing the REGION= parameter to more than 32M.³

F

FDR did not find both a VVR/NVR and a DSCB for a given data set; one was missing. Also occurs when FDR was unable to calculate the free space in a cluster.

G

The imbedded index VVR (Type Q) was not found.⁴

H

The size of an extent was not a multiple of the CA size; or the high RBA of an extent exceeded the maximum. On a logical restore, the original cluster had an imbedded index (the IMBED attribute) and the high-level index component had more than one extent.

I

The control interval size (CISIZE) on the backup cluster does not match the cluster on DASD. The displacement is x'16'.⁵

J

The number of CIs per CA on the backup cluster does not match the cluster on DASD. The displacement is x'0E'.²

K

The space allocation unit (TRACK vs CYL) on the backup cluster does not match the cluster on DASD. The displacement is x'10'.² This error is also issued following an FDR160 message; see FDR160.

L

The physical blocksize or number of blocks per track on the backup cluster does not match the cluster on DASD. The displacement is x'11' or x'15'.²

M

The number of tracks per CA on the backup cluster does not match the cluster on DASD (check the secondary allocation value specified). The displacement is x'17'.²

N

The VSAM cluster is being restored to a different type of cluster, for example, KSDS to an ESDS. Flags at two displacements are checked.²

At displacement x'03' it checks:

X’02’

Relative Record (RRDS)

X’04

Key Range

X’10’

Replication (REPLICATE)

X’20’

Imbedded Index (IMBED)

X’80’

Key Sequence (KSDS)

At displacement x'2A' it checks:

X’01’

Variable RRDS (VRRDS)

X’04’

Linear (LDS)

If none of these flags are on, the cluster is an ESDS (entry sequenced) cluster. There may be other flags on in those bytes; they do not matter. But all of the flags named above must match (on or off) between the input and output cluster.

O

The length of the VVR/NVR exceeds the length of the cells within the VVR/NVR.

P

The VVR entry found is in orphan and not related to a catalog entry.

Q

The temporary NEWNAME is not in the same catalog as the target name.

R

SMS Attributes of the backup cluster and the cluster on DASD do not match. FDR checks for Extended Format (EF) and for “over 4GB addressing”. The displacement is either x'03' or x'1D'.

S

The backup cluster contains a key range while the DASD does not or the key lengths are not the same. The displacement is x'24'.⁶

T

A VVR entry in the VVDS contains a cell type other than a 21, 23, or 60.

U

The type of VVR entry on the backup does not match the DASD (Z record being restored to Q). The user may be attempting to restore a multi-volume component to the wrong sequence component.

V

The total length of a VVR/NVR record does not match the sum of the lengths of the cells within it, on the output DASD.

W

The total length of a VVR/NVR record does not match the sum of the lengths of the cells within it, on the backup file.

X

The number of extents specified in the VVR record does not match the DSCB entry in the VTOC for a component.

Y

A base cluster is being restored to an alternate index or vice versa.

Z

Internal error. The length of the FDR backup file control block for VSAM was less than the sum of the lengths of the VVRs/NVRs within it.

Action:

• During a dump, the cluster or component indicated (or all clusters if SYS1.VVDS.Vvolser is the name printed) may not be restorable. An FDR mini-dump may be printed to help diagnose the error.
• During a restore, the cluster or component indicated is not restored (it is possible for one component to be restored without error while another fails, but the cluster is not usable). For many reason codes, an FDR mini-dump is printed displaying the VVR from the backup and the VVR from the DASD.³
• For I/O errors, an FDR mini-dump is printed showing the I/O results.
• Errors resulting from a comparison of the characteristics of the cluster being restored compared to cluster on DASD are actually not detected until the restore is complete; the data tracks have been restored but the cluster is probably not usable.³
• If restoring to a preallocated cluster, it was not defined with the characteristics that FDR requires to restore; in most cases, simply delete the cluster and let FDR define it properly. Some errors can occur even if FDR allocates the cluster. Contact BMC Support for assistance if the error cannot be corrected. See VSAM-Special-Considerations.

VSAM SCRATCH ERROR COMP=comp CODE=code CLUSTER=cluster

VSAM SCRATCH/UPDATE ERROR COMP=comp CODE=code CLUSTER=cluster

Explanation: FDR attempted to scratch a VSAM cluster but the CATALOG DELETE SVC failed. “comp” and “code” match the return code and reason code documented for IBM message IDC3009I except that “comp” values over 9000 are internal FDR errors.

Some commonly occurring IBM codes are:

comp values over 9000 are from FDR:

Action: Check the error code and correct if necessary. An FDR mini-dump is printed displaying the CATALOG DELETE parameter list and the catalog name. If needed, contact BMC Support for assistance.

FDR154

FDR155

nnnnn TRACKS MISSING ON function OF DSN=dsn

Explanation: Data set RESTORE, COPY, or MOVE detected that a number of expected tracks were not found during the restore of the data set “dsn”. “nnnnn” is the number of tracks that were not found. The remainder of the data set was restored, but it may be unusable. The cause may be:

• The restore specified DATA=ALL, but the backup used DATA=USED.
• The restore used DATA=ALL or DATA=USED but the backup was created with DATA=NONE.
• The restore used LBPZERO=INVALID, but the backup used LBPZERO=VALID.
• Backup file errors (message FDR200) were reported during the backup or restore.
• A DASD error occurred during the backup that required tracks or cylinders to not be recorded on the backup file (for example, message FDR123 or FDR129). Message FDR150 is also printed for such tracks during the restore.
• Blocks were lost from the backup file due to unreported tape drive errors.
• The restore subtask abended before completing the restore (message FDR997 is also issued).

Action: If the cause cannot be determined, contact BMC Support for assistance.

ALLOCATE FAILED FOR nnnnn quan COMP=X'comp-code' VOL=vol DSN=dsn

ALLOCATE FAILED TO CATALOG COMP=comp CODE=code VOL=vol DSN=dsn

Explanation: FDR attempted to allocate a non-VSAM data set “dsn” on volume “vol” and the attempt failed (if “FAILED TO CATALOG” is displayed, the allocation was successful, but a later attempt to catalog the data set failed; this can also occur for VSAM). “nnnnn” is the size of the data set that failed allocation in tracks or cylinders, “quan” is TRK or CYL. If the allocation was attempted on multiple volumes (because of the NVOL= operand or the ABR RESTORE ALLOCATION LIST), it failed on all of them, but “vol” is the first volume where it was tried, and “comp” is the error code from that volume. If the data set is SMS-managed, “vol” is the volume that FDR selected for the data set and may not be the same as the volume where SMS tried to allocate it.

“comp” may be return codes from the IBM ALLOCATE SVC (SVC 32), from the IBM CATALOG SVC (SVC 26), from the IBM SMS interface, or internal diagnostic codes from FDR itself.

If “FAILED TO CATALOG” is displayed, “comp” is the return code and “code” is the reason code from the CATALOG SVC, in decimal, as documented for the IBM message IDC3009I. Some of the common catalog codes shown under message FDR157 also apply to FDR156.

Common ALLOCATE codes include:

“comp” values greater than 1000 are from FDR, in hex, as follows:

Action: Determine the cause and take appropriate action. It may be possible to circumvent the problem by preallocating the output data set. If needed, contact BMC Support for assistance.

FDR157

VSAM ALLOCATION ERROR COMP=comp CODE=code VOL=vol CLUSTER=cluster

Explanation: FDR attempted to allocate a VSAM cluster, using the IBM CATALOG SVC, but the attempt failed. “comp” is the return code and “code” is the reason code from CATALOG, in decimal, or is a value generated by FDR itself. If the allocation was attempted on multiple volumes (because of the NVOL= operand or the ABR RESTORE ALLOCATION LIST), it failed on all of them, but “vol” is the first volume where it was tried, and the codes are from that volume. If the cluster is SMS-managed, “vol” is the volume that FDR selected for the cluster and may not be the same as the volume where SMS tried to allocate it.

Codes from the IBM CATALOG SVC can be found documented under IBM message IDC3009I. Common codes include:

If “comp” is a value above 9000, the error is generated by FDR itself (COMP values from 9052 through 9080 may occur if the cluster being restored had an imbedded index, and at the time of the backup the high-level index component was in multiple extents):

Action: An FDR mini-dump is printed displaying the CATALOG DEFINE parameter list and related data areas. Determine the cause and take appropriate action. For errors involving names already in the catalog, the VRECAT operand on the RESTORE statement may be used to DELETE the duplicate names from the catalog (but should be used cautiously since it may DELETE other clusters). If needed, contact BMC Support for assistance.

When restoring a multi-volume VSAM cluster, the cluster is not usable until all pieces of the cluster have been restored from all volumes where it resided. If not all the pieces have been restored, the cluster is cataloged as non-VSAM with “####Vx” as the first volume serial number. If possible, determine which pieces were not restored and restore them. But if you want to delete the partially restored cluster and start over, you must perform these steps:

1.Delete the non-VSAM catalog entry with:

//DELNVSM EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE clustername NONVSAM NOSCRATCH /*

2.Delete each data and index component of the cluster from each DASD where it was restored with:

//DELVVR EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //DD1 DD UNIT=SYSALLDA,VOL=SER=vol,DISP=OLD //SYSIN DD * DELETE componentname VVR FILE(DD1) CAT(catn) /*

More details on this are found in VSAM-Special-Considerations.

FDR158

FDR159

FDR160

XMS ERROR REASON=x

Explanation: FDR was unable to find module IGG0CLX0 in the Catalog Address Space (CAS) using Cross Memory Services (XMS). The reason codes document various internal errors.

Action: Contact BMC Support for assistance.

AIX RESTORE DEFERRED BASE CLUSTER NOT YET RESTORED AIX=name

Explanation: During a restore or copy of a multi-volume VSAM cluster with an alternate index (AIX), FDR detected that the AIX was on the current backup or input volume but the base cluster has not yet been restored, probably because it is on a different backup or DASD volume that has not yet been processed. The AIX cannot be defined until the base cluster has been completely restored.

Action: An ABR restore bypasses the AIX but remembers that it did so. After all other backups requested in this ABR restore have been processed, ABR reprocesses the backups containing the bypassed AIXs and attempt to restore them again (this may require remounting backup tapes). If the base cluster of the bypassed AIX was successfully restored from the other backups, the restore of the AIX is usually successful. If the message appears a second time for the same AIX on the same backup, or the AIX restore fails for another reason, contact BMC Support for assistance.

A DSF restore or FDRCOPY copy bypasses the AIX and does not attempt to reprocess it; you can re-execute the restore/copy with the PRESTAGE operand.

SMS NVR RECORD ERROR REASON=1, DSN=dsn

Explanation: On an SMS-managed volume, the non-VSAM Record (NVR) in the VVDS had a length exceeding 256 bytes.

Action: Contact BMC Support for assistance.

ENCRYPT/DECRYPT ERROR REASON=reason

Explanation: A DUMP, RESTORE, or BACKUP copy with encryption (FDRCRYPT) got an error. “reason” is a reason code plus explanatory text as shown below. Although the explanations refer to backup and restore, similar messages are generated by FDRTCOPY and FDRTSEL when copying or creating encrypted backups. The reason code “reason” may be:

0 - FDRCRYPT NOT FOUND

Encryption was requested on a backup, or an encrypted tape was being restored, but the FDRCRYPT module was not found. You may not be licensed for FDRCRYPT or you may be executing from the wrong FDR library.

1 - DECRYPT KEY NOT SPECIFIED

An encrypted backup was encountered during a restore, but the decryption key was not found in the Encryption Keyfile or on a DECRYPT statement.

3 - UNSUPPORTED ENCRYPTTYPE

Internal error. Contact BMC Support for assistance.

4 - MASTERKEY IS INVALID

A master key was specified for a restore, but the master key did not pass validation; it is not the master key that was used during encryption of the backup or no master key was used during the backup.

5 - DECRYPT KEY IS INVALID

A decryption key was specified for a restore (or was obtained from the Encryption Keyfile), but the key did not pass validation; it is not the encryption key that was used to encrypt the backup.

6 - DUPLICATE BYTE GENERATED

Internal error. Contact BMC Support for assistance.

7 - KEYFILE OPEN ERROR

An OPEN error occurred opening the FDRCRYPT Encryption Keyfile.

8 - KEYFILE NOT FORMATTED BLKSIZ=0

The FDRCRYPT Encryption Keyfile has not been preformatted. Use the FDRCRYFM utility to format the Encryption Keyfile.

9 - KEYFILE IS FULL

The FDRCRYPT Encryption Keyfile has no free space to record the key of the current backup. Use the FDRCRYFM utility to re-organize the Encryption Keyfile or copy it to a larger Encryption Keyfile.

A - KEYFILE INTERNAL ID INVALID

The FDRCRYPT Encryption Keyfile is not valid. Either it has been overlaid or improperly formatted.

B - KEYFILE READ/WRITE I/O ERROR

An I/O error occurred on the FDRCRYPT Encryption Keyfile.

C - FDRCRYPT PROGRAM HAS EXPIRED

The version of FDRCRYPT has reached its expiration date. Contact BMC Support to purchase the product.

D - KEYFILE NOT DEFINED

No Encryption Keyfile name was provided. The name could be on a KEYFILE statement in the FDRCRYPT DD statement input, or a default Encryption Keyfile could be specified in the FDR Global Options.

E - BACKUP NOT RECORDED IN KEYFILE

An encrypted backup was encountered during a restore, but no record of the backup was found in the FDRCRYPT Encryption Keyfile and no decryption key or master key was provided.

F - KEYFILE DYNALLOC ERROR

An error occurred dynamically allocating the Encryption Keyfile specified on a KEYFILE statement or in the FDR Global Options. Message FDR336 was also issued with the dynamic allocation error codes.

G - MASTERKEYID NOT FOUND

When creating an encrypted backup, MASTERKEYID=profile was specified (or a default MASTERKEYID was specified in the FDR Global Options), but FDRCRYPT did not find profile FACILITY/FDRCRYPT.profile in your security system. Either the profile is not defined, or (under CA ACF2 or CA TOP SECRET) the user ID under which the job is running is not authorized to access the profile, or the security system is not active.

H - MASTERKEYID INVALID

When creating an encrypted backup, MASTERKEYID=profile was specified (or a default MASTERKEYID was specified in the FDR Global Options), but the profile FACILITY/FDRCRYPT.profile in your security system did not specify a valid MASTERKEY= value in the APPLDATA field of the profile (for example, MASTERKEY= not specified or the value is not 32 hex digits).

I - SPECIFIED DDNAME/DSNAME NOT ENCRYPTED/DECRYPTED

In FDRCAMS, one or more ENCRYPT or DECRYPT statements were not processed because no matching IDCAMS REPRO statement was executed.

J - INVALID EOD RECORD

When decrypting, FDRCAMS encountered an invalid encryption EOD record.

K - PREMATURE END OF FILE

When decrypting, FDRCAMS encountered the end of the input file without reading an encryption EOD record.

L - SYNAD ERROR

An I/O error occurred on the encrypted file.

M - MUST BE DECRYPTED WITH FDRCAMS

The user attempted to use the no-charge program FDRDECRY to decrypt an encrypted file created by FDRDECRY; this is not permitted. FDRDECRY can only be used to decrypt files created by FDRCAMS, and encrypted files created by FDRDECRY can only be decrypted by FDRCAMS.

P - PUBLIC KEY ERROR – ERROR CODE=rrrrccccssss

PUBLICKEY or PRIVATEKEY was specified in an FDRCAMS step, but ICSF returned an error with the indicated codes. For common codes, additional explanatory text is printed.

Z - UNKNOWN REASON CODE

Internal error. Contact BMC Support for assistance.

Action: Correct the error, if possible, and rerun. Contact BMC Support if you need assistance.

FDR200

BLOCK DROPPED--synadaf--datablock

Explanation: A permanent BSAM read or write I/O error has occurred on a backup data set. “synadaf” is descriptive error text provided by the IBM SYNADAF macro. “datablock” is the first 20 bytes of backup data block read or written, in hex, if available. An IBM IOS000I I/O error message may also appear in the job's job log. Tape I/O Errors in Section FDR-DSF-CPK-ABR-I-O-Error-Recovery gives more details.

DUMP

If on reel-to-reel tape (3420-type tapes), FDR issues an EOV to force a new output volume to be mounted. The blocks that were being written to the tape having the error is rewritten as the first blocks on the new reel. If this tape switch occurs more than 19 times, FDR terminates with an U0200 abend.

On cartridges drives, because of the control unit buffer, FDR issues the U0200 abend immediately after the first unrecoverable tape error. FDR terminates immediately if the error occurs during the write of the control records at the beginning of the backup.

RESTORE

Any block in error is bypassed. If the error is due to I/O errors during the dump to a reel-to-reel tape, the block in error was rewritten on the next tape volume; if it is read successfully the data is properly restored (logical data set restore may fail on this condition). FDR drops up to 19 blocks before terminating with an U0200 abend. If any track images were never successfully read from any tape volume, message FDR366 (and possibly message FDR155) are issued to document this; if neither is issued then the restore was successful despite the I/O errors.

The block number in “synadaf” indicates the number of the tape block dropped. MAXERR= can increase or decrease the number of errors FDR bypasses. The keyword TAPERRCD=NO suppresses the condition code or abend that normally occurs at the end of the dump or restore.

FDR203

FDR204

FDR211

FDR ERROR ON DD=ddn REASON=reason

Explanation: FDRINSTANT discovered an error when attempting to initialize “ddn”. The “reason” can be:

8 - FDR.USE.UNIT NOT FOUND

The DASD device specified by DSN=FDR.USE.UNITuuuu on the DISKx DD statement was not found in your I/O configuration.

9 - FDR.USE.UNIT IS ONLINE

The DASD device specified by DSN=FDR.USE.UNITuuuu on the DISKx DD statement is online. It must be offline to z/OS.

A - FDRINSTANT VOLSER MISMATCH

The volume serial of the offline DASD device being dumped does not match the volume serial of the online primary volume.

C - FDRINSTANT UNIT NOT FOUND

The DASD device containing the FDRINSTANT volume image was not found in your I/O configuration. For PGM=FDR or FDRDSF, if you specify BCV=, PPRC=, FCOPY=, or SNAP=, this can also occur if you are trying to do Instant backups and non-Instant backups in the same step.

D - FDR INSTANT PATH GROUP ERR

FDR called the IBM module IECDVPTH to establish path groups for the offline DASD, but the return code was non-zero. The backup is completed but there may be some performance degradation.

E - INSTANT BKUP NOT CATALOGED

The latest backup generation and cycle as recorded in the ABR Model DSCB is not cataloged.

F - INSTANT BKUP ALREADY DONE

The latest backup generation and cycle as recorded in the ABR Model DSCB is currently cataloged to a tape or a DASD other than the source DASD itself, so the backup has already been moved. This message is normal if you restart the ABR backup step after some backups have been successfully moved to tape; it does not set any error codes and processing on the volume is bypassed.

G - INSTANT BKUP UNIT MISSING

A SNAP, SPLIT, PSPLIT, or FCOPY was previously done, but FDR cannot locate the UCB for the device that was the target of the operation (that contains the volume image).

H - INSTANT BKUP GEN/CYC ERROR

The generation/cycle of the backup on the offline volume is not the same as current generation/cycle as recorded in the ABR Model DSCB. This can also occur if an offline volume is released in a prior unsuccessful run with FCOPY=(USE,REL) and the DUMP job is being rerun.

I - LOAD FAILURE FOR MODULE EMCSAI/EMCQCAPI

FDR was unable to load an EMC API module. The EMC libraries must be in the system link list (LNKLST) or a STEPLIB in the FDR step.

J - INSTANTBKUP TYPE= MISMATCH

The TYPE= parameter used on the SNAP, SPLIT, PSPLIT, or FCOPY operation was different from that specified on the subsequent DUMP statement.

K - FDRINSTANT LABEL I/O ERROR

An I/O error occurred reading the volume label from the offline volume.

M - INSTANTUNIT=uuuu NOT READY

The offline DASD copy of the online DASD is not ready. If you have the DSN=FDR.USE.UNITuuuu in the FDR DISKx DD statement, this may mean that you have provided the wrong offline device address, or it may mean that the offline copy has not been properly split from its online source. If this is a BCV in an EMC subsystem or a ShadowImage copy in a Hitachi Vantara subsystem, this may mean that the SPLIT or PSPLIT function has not been executed or has not completed.

N - FDRINSTANT I/O ERROR

An I/O error occurred while performing the FDRINSTANT backup.

P - FDRINSTANT LABEL NOT FDR1

FDRINSTANT changes the VOL1 label on the output volume to FDR1 when you do a SNAP, SPLIT, PSPLIT, or FCOPY so it cannot be brought online by accident. But during the backup phase of FDRINSTANT, the volume label was not FDR1 as expected.

Y - UNABLE TO SPLIT – SPLIT RETRY COUNT EXCEEDED

Because of conditions within the Symmetrix, FDR was forced to re-establish and re-split the BCV a number of times, but the retry limit for this re-establish/re-split was reached before a valid split BCV was created.

Action: The backup is terminated (except for reason “D”). Many of these errors indicate that the FDRINSTANT jobs have not been run in the correct order or with the correct parameters. Correct the error, if possible, and rerun. Otherwise, contact BMC Support.

If you attempted to do a SNAP, SPLIT, PSPLIT, or FCOPY, but it failed for some reason, then the DUMP step gets this message with reason “E” or “F”. Check the output of the SNAP, SPLIT, PSPLIT, or FCOPY step to determine the cause of the error. However, reason F is normal if the DUMP step fails after processing some volumes, and you resubmit it; ABR gets reason “F” for the SNAP, SPLIT, PSPLIT, or FCOPY volumes it has already processed and automatically bypasses them.

FDR218

FDR219

FDR224

FDR VOL=vol IS BEING DUMPED FROM ONLINE UNIT BECAUSE SNAP/SPLIT/PSPLIT/FCOPY NEVER DONE

Explanation: A FDRABR DUMP is being executed with SNAP=USE, PPRC=USE, FCOPY=USE, and/or BCV=USE but the identified volume is not eligible for FDRINSTANT processing. It is issued for every volume in the backup step that has not had a SNAP, SPLIT, PSPLIT, or FCOPY executed against it successfully.

This message is issued for all normal volumes (volumes that you want regular backups, not FDRINSTANT) that are processed in the same step with FDRINSTANT volumes, unless you have erroneously attempted to do a SNAP, SPLIT, PSPLIT, or FCOPY of those ineligible volumes.

The message is also issued for all eligible volumes for which SNAP, SPLIT, PSPLIT, or FCOPY has never been done, indicating that you want to backup those volumes normally.

Action: The volume is backed up by normal ABR backup processing, but it is not a point-in-time backup.

If the message identifies a volume that you did not intend to backup with FDRINSTANT, it can be ignored.

If you did intend to use FDRINSTANT on this volume, check your SNAP, SPLIT, PSPLIT, or FCOPY step to be sure that it was included.

FDR230

pgm type UNIT=uuuu REASON=reason

Explanation: FDRINSTANT had an error attempting to use special hardware facilities to get a point-in-time image of a volume for FDRINSTANT use. “type” is “WARNING” or “ERROR”. “uuuu” is the device address of the target DASD and “reason” indicates the cause. Note that some reason codes have several versions depending on the hardware facility that failed. Reason codes include:

FCOPY ERROR - SRC/TGT NOT IN SAME SUBSYSTEM

The source and target are not in the same subsystem. DEVSERV QDASD can identify the subsystem serial number. 

1 - MOUNT STATEMENT NOT SPECIFIED

There were no MOUNT statements following a SNAP, SPLIT, PSPLIT, or FCOPY statement. MOUNT statements are used to define the source volume and target device for the FDRINSTANT copy.

2 - MOUNT STATEMENT NOT FOUND

Some control statements were provided after the SNAP, SPLIT, PSPLIT, or FCOPY statement, but none of them were MOUNT statements. Only MOUNT statements can follow that statement.

3 - xxxxUNIT= NOT SPECIFIED IN MOUNT STATEMENT

A MOUNT statement does not contain the operand SNAPUNIT=, PPRCUNIT=, FLASHUNIT=, or BCVUNIT=. It is required.

4 - SOURCE AND type UNIT ADDRESS ARE EQUAL

The unit on which the volume specified by VOL= is mounted is the same as the unit specified by xxxxUNIT=. A volume cannot be copied to itself.

5 - INCOMPATIBLE SOURCE AND type UNIT DEVICE TYPES

The device type of the unit on which the volume specified by VOL= and the unit specified by xxxxUNIT= are not the same. You cannot snap from a 3380 to a 3390 or vice versa.

5 - CONSISTENCY GROUP DETECTED - CTG=SI

This indicates that you are attempting to perform a PSPLIT on a Relationship that is part of a "CONSISTENCY GROUP". Units in a Consistency Group must be processed by using CONPSPLIT in a separate step or job. When any unit in a Consistency Group relationship is split/suspended, it causes all units in that Consistency Group to also be split/suspend.

6 - type UNIT NOT FOUND

The device address specified by xxxxUNIT= was not found in the current I/O configuration. Be sure you specified a 4-digit hex address; add a leading zero if required.

7 - type UNIT NOT DASD

The device address specified by xxxxUNIT= was defined as a type other than DASD in the current I/O configuration.

8 - type UNIT IS NOT OFFLINE

The DASD address specified by xxxxUNIT= was not varied offline to z/OS. If you are sure that you want to use this device as an FDRINSTANT target, vary it offline.

9 - UNKNOWN DEVICE OR DEVICE NOT type CAPABLE

Either the source volume specified by VOL= or the target volume specified by xxxxUNIT= is capable of the special hardware feature requested (e.g, “ECAM” is the special command set used to perform SnapShot).

9 - UNABLE TO OBTAIN SYMMETRIX DEVICE NUMBER

FDR was unable to determine the z/OS device address of the BCV assigned to the online volume being dumped. Possibly it is not in the I/O configuration or is in a different Symmetrix. Try specifying BCVUNIT= on the MOUNT statement.

9 - UNABLE TO OBTAIN PPRC DUPLEX NUMBER

FDR was unable to determine the z/OS device address of the ShadowImage volume assigned to the online volume being dumped. Possibly it is not in the I/O configuration or is in a different DASD subsystem.

9 - UNKOWN DEVICE OR DEVICE NOT FLASHCOPY CAPABLE

Device is not capable of FlashCopy or FlashCopy cannot be used between the source and target devices specified.

A - UNEQUAL SOURCE/TARGET CONTROLLER FRAME SERIAL NO.

The source volume specified by VOL= and the target volume specified by xxxxUNIT= are not both in the same DASD subsystem (for FlashCopy V1, they must be in the same logical subsystem (LSS)).

A - SYMMETRIX QUERY FAILED

A query to the EMC Symmetrix to get BCV information failed.

A - DEVICE IS NOT IN DUPLEX STATE

No PPRC session exists for the primary device.

B - SNAP STATUS INDICATES FAILURE

Contact BMC Support for assistance.

B - UNKNOWN DEVICE STATE FLAG=xx

Contact BMC Support for assistance.

C - SNAP STATUS INDICATES TIME OUT

An internal time-out occurred in the hardware. If it is repeatable, contact BMC Support for assistance.

D - SNAP STATUS INDICATES INVALID EXECUTE ATTEMPTED

Contact BMC Support for assistance.

E - SNAP STATUS INDICATES COUNT FIELD INCOMPATIBILITY

Contact BMC Support for assistance.

F - I/O ERROR DURING PROCESSING

An unexpected I/O error occurred while processing the special hardware request. The error is documented by another message. This can occur at DRP during a RESTORE procedure when the catalog being used has the backup entry pointing to the instant offline volume instead of the backup tape. This can occur when the ABR catalog being used was captured before the FDRABR DUMP process but after the SNAP, SPLIT, PSPLIT, or FCOPY process. Contact BMC Support for assistance.

G - MESSAGE ID=mmmm STATUS CODE=ssss

ECAM message number “mmmm” was issued to the SnapShot device. The message was accepted but it returned status code “ssss”. Contact BMC Support for assistance.

H - MESSAGE ID=mmmm COMPLETION CODE=cccc REASON=rrrr

ECAM message number “mmmm” was issued to the SnapShot device. The message was rejected with completion code “cccc” and reason code “rrrr”. Contact BMC Support for assistance.

I - MESSAGE ID=mmmm PARMID=pppp COMP CODE=cccc REASON=rrrr

ECAM message number “mmmm” was issued to the SnapShot device. The message was rejected because of a problem with message parameter “pppp” with completion code “cccc” and reason code “rrrr”. Contact BMC Support for assistance.

J - TARGET UNIT HAS LESS CYLINDERS THAN SOURCE DEVICE

The source volume specified by VOL= has more cylinders than the target volume specified by SNAPUNIT=. The target volume must be equal to or larger than the source volume in size.

K - UNDEFINED SNAPSHOT STATUS

Unexpected response from the SnapShot device.

L - UNDEFINED SNAPSHOT MESSAGE COUNT

Unexpected response from the SnapShot device.

M - EXPECTED MSGID=nnnn. RECEIVED MSGID=nnnn

Unexpected response from the SnapShot device; the wrong ECAM message was received.

N - INVALID FDRINSTANT VOL1 LABEL OR GEN/CYCLE MISMATCH

FDR changed the ID of the volume label of the target DASD to FDR1 so that it cannot be accidentally brought online. When the point-in-time image was dumped, the label was no longer FDR1, or the ABR generation and cycle created during the SNAP, SPLIT, PSPLIT, or FCOPY was not the same as that currently recorded on the target. Contact BMC Support if you do not want FDRINSTANT to modify the volume label.

O - PRIOR FDRABR INSTANT BACKUP PENDING DSN=dsn

A DUMP or SNAP, SPLIT, PSPLIT, or FCOPY was not done because a previous SNAP, SPLIT, PSPLIT, or FCOPY had been done, but you have not yet executed the DUMP to move the point-in-time backup to tape. If you want to do a DUMP (non-FDRINSTANT) and discard the point-in-time backup, specify the operand INSTANTLOSS=YES on the DUMP statement.

P - PRIOR FDRABR INSTANT BACKUP IS LOST DSN=dsn

A DUMP or SNAP, SPLIT, PSPLIT, FCOPY detected that a previous SNAP, SPLIT, PSPLIT, FCOPY had been done, but you have not yet executed the DUMP to move the point-in-time backup to tape. Since you replied “YES” to the FDRW02 message or specified CONFMESS=NO or INSTANTLOSS=YES, the uncompleted backup is discarded and is no longer usable.

Q - TOO MANY WRITES PENDING

While FDRCOPY was attempting to use the EMCCOPY internal copy function on an EMC Symmetrix, the Symmetrix reported that an internal limit of pending writes (from cache to DASD) was exceeded. The copy continues using normal read/write I/O.

Q - CONTROLLER DOES NOT SUPPORT LRE/WFT

Contact BMC Support for assistance.

R - TARGET VOLSER DOES NOT MATCH SOURCE

The operand VERIFYVOLSER=YES was specified, but the current volume serial number of the offline target does not match the volume serial number of the online source volume.

R - DEVN/UNIT LOCATION ROUTINE ERROR FUNC=function

Contact BMC Support for assistance.

S - PPRCUNIT IS NOT PAIRED WITH PRIMARY

The device specified by PPRCUNIT= is not currently in a PPRC session with the primary volume. You did not issue a previous (C)ESTPAIR command to establish the session.

S - ANTRQST IS NOT INSTALLED AT LEVEL 4

You do not have the proper level of the IBM ANTRQST API to support FlashCopy installed. Contact BMC Support for assistance.

S - ANTRQST REQUEST BUFFER EXHAUSTED

An error occurred while invoking the IBM FlashCopy API. Contact BMC Support for assistance.

S - SOURCE VOLUME NOT IN FLASHCOPY STATUS

An error occurred while invoking the IBM FlashCopy API. Contact BMC Support for assistance.

S - SRC/TGT VOLUMES NOT PAIRED OR IN SIMPLEX STATE

The FlashCopy source and target volumes are each already paired with a different volume OR they are not both in Simplex state. FlashCopy cannot be used on this pair until those FlashCopy sessions are terminated.

S - FLASHCOPY – ANTRQST FUNCTION FAILURE

An unknown error occurred while attempting to issue the ANTRQST function. Check FDR149 message for requested function, return and reason codes.

S - FLASHCOPY UNEXPECTED QUERY DATA RETURNED

An error occurred while invoking the IBM FlashCopy API. Contact IBM to be sure you have the latest maintenance for FlashCopy and contact BMC Support for assistance.

S - FLASHCOPY WITHDRAW FUNCTION FAIL CODE=nnnnn-nnnnn RELEASE BYPASSED

FCOPY=(USE,REL) was specified but the FlashCopy withdraw (FCWITHDR) failed with the indicated return codes.

S - FUNCTION FCESTABX FAILED - RTNCD=000F RSNCD=00

FCESTABX command to establish a FlashCopy relationship between the user-specified source and target device has failed. Review FDR149 for information on current device status, return codes, reason codes, and your control cards. The target volume may already be in a FlashCopy relationship as a target unit for another source volume.

T - FLASHCOPY VOLS ARE IN ACTIVE RELATIONSHIPS

Either the FlashCopy source or target volume is already paired with a different volume. FlashCopy cannot be used on this pair until that FlashCopy session is terminated.

T - FLASHCOPY ESTABLISH FAILED FOR SOURCE

An attempt to establish the relationship has failed. Perform FCQUERY on source and target volumes to determine cause of failure. Review FDR149 for information on current device status, return and reason codes. Check source and target compatibility and capacity.

T - FLASHCOPY RELEASE FAILURE

An attempt to release the relationship due to the use of FCOPY=(USE,REL) has failed. Review FDR149 for information on current device status, return and reason codes. Possibly due to the use of FCOPY=COPY or an external FCWITHDR being performed.

T - ANTRQST - PPRC REQUEST FAILURE

An error occurred while invoking the IBM PPRC API. Contact BMC Support for assistance.

U - SECURITY ACCESS DENIED TO DSN=FDR.USE.UNITxxxx

FDRINSTANT security checking was enabled, and the user id under which the FDRINSTANT request was run does not have UPDATE authority to the data set FDR.USE.UNITxxxx where “xxxx” is the device address of the offline target volume specified by the xxxxUNIT= operand.

V - BCVUNIT= IS NOT SPLIT FROM SOURCE DEVICE – WILL SEARCH UCBS

The device specified by BCVUNIT= was not a BCV split from the online volume specified by VOL=. FDR searches all offline UCBs for the proper BCV; if found, the operation continues; if not found, another message is issued and the operation fails.

W - VOL1 RESERVED FIELDS NOT BLANK

FDRINSTANT stores information in reserved fields in the volume label of the offline volume. This is a warning that those fields were not blanks, as expected, but ABR overlaid them anyway. Member FDRVOL2 in the Installation Control Library (ICL) can be used to set the reserved fields in the volume label to blanks.

X - EMCQCAPI ERROR RC=rrrrrrrr ACTION=aa IORC=iiii

An error occurred invoking the EMC SNAP API. Error codes are displayed. If the API returned a text explanation of the error, a second line with MSG= is displayed. One common cause is that the EMCSCF address space is not active.

Z - EMC DEVICE EMCFLASH=NO AND FCOPY=FRR IS INVALID

The FCOPY=FRR operand is invalid when EMCFLASH is disabled (EMCFLASH=NO). Enable EMCFLASH in order to use FCOPY=FRR.

Action: In most cases, the volume is bypassed. In the case of FDRCOPY, it may use standard read/write I/O if an instant replication facility cannot be used. If additional MOUNT statements were specified, additional volumes are processed.

FDR232

FDR258

FDR274

FDR276

FDR277

NOT CONVERTED REASON=reason FUNCTION=fn, RETURN CODE=rc, REASON=rsn

Explanation: The data set or cluster named in the preceding FDR276 message could not be converted by FDRCONVT for “reason”. For errors in system calls (such as CATALOG), the second line of the message displays the function code “fn”, the return code “rc” and/or the reason code “rsn”.

There are many possible “reason” values. Some common ones include:

DATA SET STORCLAS IS NULL

The Automatic Class Selection (ACS) routines returned a null storage class for this data set, so it cannot be SMS-managed. You can specify the storage class via a SELECT with STORCLAS= but the Automatic Class Selection (ACS) routines may still override it to null.

VVDS MANAGER ERROR

Return/reason codes of 24 and 6 indicate that the VVR/NVR for the data set was not found in the VVDS.

ACS ROUTINE FAILURE

the reason code “rsn” probably corresponds to an IBM message IGDnnnnn; look it up in the IBM messages space.

LOCATE FAILED FOR DATA SET

A catalog operation failed. The return and reason codes are documented under IBM message IDC3009I in the IBM messages space.

DATA SET NOT CATALOGED

The data set to be converted was not cataloged and CATLG=YES was not specified.

Other reason values are possible.

Action: Processing continues with the next data set. Determine from the reason printed why the data set was not eligible. If necessary, contact BMC Support for assistance.

VOLUME vol INELIGIBLE FOR CONVERSION: REASON=reason
VTOC SMS FLAG=f1 VTOCIX SMS FLAG=f2

Explanation: The volume specified could not be converted to the desired status because it was not eligible.

Action: Determine from the reason printed why the volume was not eligible. If necessary, contact BMC Support for assistance. Processing terminates with an FDR274 message.

VOLUME vol PROCESSING WARNING ** REASON=VTOC/VTOCIX MISMATCH
VTOC SMS FLAG=40 VTOCIX SMS FLAG=00

Explanation: The volume’s VTOC indicates SMS, but the VTOCIX is not SMS.

Action: Volume will be considered marked as INITIAL and processing will be allowed to continue with the warning message for informational purposes.

MASTER CATALOG NAME NOT FOUND

Explanation: The name of the master catalog could not be determined. FDRCONVT must determine the master catalog name in order to run.

Action: Correct any problems with the master catalog and rerun the job. If the problem cannot be determined, contact BMC Support for assistance.

ATTACH ERROR, RC=comp

Explanation: FDRCONVT could not successfully attach a required subtask. “comp” is the return code, in hex, from ATTACH.

Action: If the problem cannot be determined from the dump, contact BMC Support for assistance.

reason catn

Explanation: FDRCONVT encountered an error while trying to find a catalog specified in the INCAT parameter for the “reason” indicated. If the reason is LOCATE ERROR, the return code and reason code from CATALOG are displayed; these are documented under IBM message IDC3009I in the IBM messages spaces.

Action: Correct the error. Specify the correct catalog if necessary. Contact BMC Support for assistance if required.

ERROR OBTAINING type DEFINITIONS R15=nnnnnnnn, SFN=fn, RETN=rrrrrrrr, RSN=ssssssss

Explanation: FDRCONVT was unable to obtain the definitions for SMS classes; type is STORCLAS, MGMTCLAS, or DATACLAS. R15 contains the return code from the SMS subsystem call. “fn” is the SMS function code. “rrrrrrrr” and “ssssssss” are the SMS return code and reason codes. The codes can be found in the IBM space DFSMSdfp Diagnosis Reference.

Action: Correct the error. Contact BMC Support for assistance if necessary.

FDRKWDPR INTERNAL ERROR

Explanation: An internal error was encountered while processing control statements.

Action: Contact BMC Support for assistance.

FDR302

CONTROL STATEMENT ERROR NEAR REL LOCATION nn -- REASON x -- JOB TERMINATED

Explanation: An error was encountered during the processing of a user-supplied control statement. If “NEAR REL LOCATION nn” appears, the keyword or operand causing the error is at or near column “nn” on the input statement.

The error is defined by the reason code within the message. The failing statement is displayed immediately above.

The reason “x” can be:

1

A SELECT statement did not specify any operands. Control statement was blank after the command name.

2

Command name on the first control statement was incorrectly specified. For example, FDRDSF must start with a DUMP, RESTORE, or PRINT statement. See the section in this space for the program you are executing for details.

3

Operand on the first control statement was incorrectly specified. (Valid operands include TYPE=DSF and RESERVE).

4

Operand did not end with a blank or comma.

5

SYSIN data set was empty.

6

Expected continuation statement was not found. The previous statement ended with a comma and a blank.

7

One of the following:

• The TYPE= operand was omitted on a command that requires it (such as PRINT or COPY).
• A control statement after the first was not a SELECT statement. A SELECT statement contained an invalid keyword. (Valid keywords include DSN= and VOL=.)
• On the first control statement, invalid or incompatible operands were specified. (Examples: RESERVE was specified but TYPE= was omitted, or FROM/TO was specified and TYPE= followed it.)

8

An operand on a SELECT statement specified a blank or comma after the equal sign.

9

On the control statement printed above, one of the options exceeded its maximum length or was shorter than its minimum length. A data set name exceeded 44 characters. A volume serial number exceeded 6 characters. The TAPEDD= operand exceeded one (1) character. The NOTIFY operand exceeded seven (7) characters. The DD= or NEWDD= operand exceeded eight (8) characters. A CLOUD Container name exceeded 128 characters.

B

The DD= or NEWDD= operand specified a ddname that did not appear in the JCL.

C

Maximum number of SELECT statements was exceeded. The number of SELECT statements plus the number of commands in the PROTECT and/or ALLOCATE list was greater than the value specified in the MAXCARDS operand (default of 100 for ABR or 250 for FDRDSF).

D

ADATE= operand did not specify numeric data.

E

ADATE= operand is neither five digits (yyddd) nor seven digits (yyyyddd).

F

An operand that requires numeric data (for example, MAXCARDS=) specified non-numeric characters, or an operand that requires hexadecimal data (for example, SNAPUNIT=) specified non-hex characters.

G

An operand did not end with a blank or comma or exceeded 15 digits (for example, MAXCARDS=).

H

ADAYS= operand resulted in a negative year.

I

Keyword is invalid under the operation indicated (for example, GEN= was specified on a DUMP operation, CATDSN= was specified on an EXCLUDE statement, or COMPRESS= was specified with CLOUD=). Check space for allowable keywords under this operation. Also, if the operation invokes encryption, ensure that RTC=YES is not specified since encryption performs its own compression.

J

Control statement was completely blank. You can enter comment lines by placing an * (asterisk) in column 1.

K

A required operand was not specified on the preceding SELECT statement. On RESTORE TYPE=FDR, VOL= was not specified. On all other operations DSN, DSG, DD, ALLDSN, or FROM/TO was not specified.

L

NEWG= began with a period.

M

COPY operand specified other than “1” or “2” on the SELECT command, DSORG specified an invalid value, a date was improperly specified, the data set specified by CATDSN= is cataloged on more than 255 volumes, a TAPEVOLGn= operand was invalid, or a container name did not start with FDR. .

O

An operand was specified on a system that does not support it. For example, SMSMANAGE=YES cannot be specified on a system where SMS is not active.

P

ALLDSN was specified without ADATE on RESTORE TYPE=ARC. NEWN/G/I was specified with NEWNAME disabled. VOLG was specified on a RESTORE TYPE=ABR or TYPE=FDR.

Q

Keyword exceeded maximum value or was negative (for example, GEN=10000 or CYCLE=64).

R

TYPE=xxx was specified multiple times.

S

An operand on the SELECT statement was specified multiple times or was mutually exclusive with another operand. (for example, DSN and DSG were both specified). DSN or DSG was specified on a MOUNT command.

T

The operand BACKUP appeared on a SELECT statement read during a RESTORE TYPE=ARC operation or the operand ARCHIVE appeared on a SELECT statement read during a RESTORE TYPE=ABR operation. The operands BACKUP and ARCHIVE should only appear on restore requests written to the remote queue restore data sets (ABRREST and ABRARCH), respectively. Perhaps these two data sets were reversed.

U

The TYPE=xxx operand was missing or invalid on the first statement. This operand is required for FDR, DSF, FDRCOPY, or ABR.

V

An absolute track keyword was specified to FDRDSF (FROM/TO). The FROM/TO specification was in error. CYL and TRK did not specify numeric values or FROM value was higher than TO value, or absolute track operations have been disabled (NOABSTRK), or FROM/TO was specified on an EXCLUDE statement (DUMP only).

Action: Correct error and resubmit job. If you do not understand the error after reviewing the relevant sections of this space, contact BMC Support for assistance.

FDR303

FDR304

FDR305

CATALOG FAILURE FOR BACKUP COMP CODE=X’ffff00001111’

Explanation: A catalog request for an ABR backup data set has failed. “ffff” is the catalog return code containing R15, “0000” is the catalog return code containing R0, and “1111” is the catalog return code containing R1. Common R15 values are:

0008

ABR backup data set is already cataloged. Since the name of this backup duplicates a previous backup, this backup may not be usable. Some possible causes are:

• The FDRABRM REMODEL command (FDRABRM-REMODEL-Statement) has been used incorrectly.
• A full volume RESTORE or COPY under FDR or FDRABR has been done with VOLRESET=NO.
• A Stand Alone Restore (SAR) has been done.

These operations can back-level the generation and cycle number. The REMODEL command of program FDRABRM or the ABR ISPF dialogs can be used to update the model DSCB on the volume to the proper generation and cycle.

For an application backup (FDRAPPL), if the backup of the control file is a GDG, return code 8 can also occur if the GDG base has not been defined.

0020

The ABR catalog is full. Once you have expanded or reorganized the catalog you can spacely catalog the backup using the information in the FDR305 message.

CATALOG FAILURE FOR BACKUP - MAXIMUM VOLSERS EXCEEDED

If the text “MAXIMUM VOLSERS EXCEEDED” appears, a single ABR backup file has exceeded 20 tape volumes and cannot be cataloged. You may be able to reduce the number of volumes required by using higher-capacity tapes or using tape hardware compression (for example, IDRC) or ABR software compression (COMPRESS=).

Action: If you cannot correct the error, contact BMC Support for assistance.

FDR310

FDR311

FDR314

FDR316

function status REQUESTED DSN/DSG=dsn VOL=vol

Explanation: A SELECT or EXCLUDE statement was input to an FDR program, but none of the data sets processed by that program matched the data set name, dsname mask, or data set group name “dsn” on that statement. This is probably an error, since there must have been a reason for providing the statement. “vol” is the volume serial number if specified by VOL= on the SELECT or if selected from the catalog by CATDSN=.

If “status” is DID NOT FIND:

• For backups, no data set on the input DASD matched the name specification.
• For DSF restores, it means that no such data set was found on the input backup files.
• For ABR restores, it means that Volume Backup information or Archive Backup information could not be located.

This can also be caused by an EXCLUDE preceding the SELECT for the same data sets. Another error (such as message FDR325) may also cause the data sets not to be selected.

If “status” is EXCLUDED, the message simply documents that the named data sets were excluded.

If “dsn” is MOUNT, then an ABR MOUNT statement did not select any volumes for ABR processing.

If an ABR full-volume dump was forced (see message FDR310), then SELECT statements were not processed, and message FDR316 appears for every SELECT. However, all data sets on the volumes were dumped.

Action: If this is an error, correct and resubmit job. If you did not expect to get this message, there is probably some error in your SELECT statements; check them. One common error: if you have more than one SELECT statement, and an earlier one selects all the data set that would be selected by a later one, the later one gets the FDR316. For example,

SELECT DSN=A.B.**
SELECT DSN=A.B.C

In general, put the SELECT statements with the most restrictive selection first.

This message usually causes the FDR step to end with an abend or non-zero return code. If you expect to get this error (perhaps because some data sets may not always exist) and want to ignore it, specify SELTERR=NO on the DUMP statement.

I/O ERROR ON DISK TRACK X'cccchhhh' I/O ERROR ON DISK - DDNAME ddn - SEEK ADDRESS cccchhhh

Explanation: ABR encountered an I/O error while reading or writing the VTOC. The FDR mini-dump is printed.

Action: ABR continues processing the VTOC bypassing this track. Contact BMC Support for assistance.

FDR319

FDR OPERATION ABNORMALLY TERMINATED VOL=vol COMP CODE=Ssss Uuuuu

Explanation: An internal FDR subtask failed on volume “vol”.

If “sss” is non-zero (in hex), the task failed with a System Ssss abend. Consult IBM documentation for the meaning of the abend. Sx13 and Sx14 abends are OPEN and CLOSE errors and are accompanied an explanatory message in the job log of the FDR job.

If “uuuu” is non-zero (in decimal), the task failed with an Uuuuu abend. The abend is probably generated by FDR; See ABEND-Codes. Most FDR User abends are preceded by an FDR message.

Action: If the problem cannot be determined from the abend code, contact BMC Support for assistance. If the abend produced a storage dump, have it available.

Only this volume is affected, FDR continues to process other volumes. However, the step ends with an abend or non-zero return code to call attention to the error.

If this is an ABR backup to tape, and there are more DASD volumes to be processed, ABR calls for a fresh scratch tape on the output drive for the TAPEx and TAPExx DD statements in use by the dump subtask that abended.

If this is an FDRCOPY of a data set using NEWI= (or NEWNAME=) that directs the data set to the master catalog and the job receives a S0C6 abend with the PSW=x0000243, this indicates FDRCOPY failed in an attempt to locate the volume serial of the new catalog. The locate is being done because the RACF indicator is on in the source cluster’s F1DSCB. In order to restore this data set, specify a NEWI= (or NEWNAME=) that directs the data set to a user catalog instead of the master catalog.

UNABLE TO function REASON=x--DSNAME=dsn

Explanation: FDR was unable to RESTORE, COPY, or MOVE the data set specified in the message. The reason code “x” may be:

The FD restore subtask restoring this data set from a backup failed; see message FDR319, other FDR messages may also appear.

3

I/O error reading a Format 2 or Format 3 DSCB from the output DASD.

6

Data set enqueue failed for this data set. DSNENQ=NONE overrides this check.

6

Data set enqueue failed for this data set. DSNENQ=NONE overrides this check.

B

Data set is unmovable.

C

Data set not found on the backup file. The user may have misidentified the backup (the backup does not contain the data set), or it may be due to:

• The same DSNAME was specified on more than one control statement or the DSNAME is a component of previously requested VSAM cluster.
• For VSAM clusters, can occur if there was more than one VVR for a component of the cluster in the VVDS of the original DASD when dumped (this is an error).

D

Data set has an F3 DSCB, but it could not be found on the backup.

E

Data set was being restored to a new name and the FDR security checking option (ALLCALL) is enabled, or an FDR.NOALLCALL security profile is defined and the user does not have Read authority to it, but:

• The user does not have READ authority to the original data set
• The original data set is not protected by your security system (this is considered an error since the data set may have been backed up on another system where it was protected).

G

Unable to locate data set's F3 DSCB on target volume or F2 DSCB found for a non-ISAM data set.

J

Data set was RACF or password protected when it was backed up, but user has preallocated it without protection, or vice versa.

K

Data set has not reached its expiration date, and the operator replied “NO” to the FDRW03 message.

O

PRESTAGE was specified. Data set restore bypassed since data set was found.

P

Characteristics of the input data set and the preallocated output data set do not match; or it is not possible to create the output data set on the requested volume. Examples of this:

• VSAM to non-VSAM
• PDSE to non-PDSE
• HFS to non-HFS
• Extended Format SMS to non-EF
• And vice-versa in each case. Other combinations also cause errors.

S

A data set that must be SMS-managed (such as Extended Format (EF)) is being restored to a non SMS-managed volume.

T

FDRCOPY COPY/MOVE detected a copy/move of a data set on top of itself (same volume serial number, same data set name).

U

Error updating ISAM Format 2 DSCB, or VSAM component in the VTOC but not in the VVDS.

V

VSAM cluster is being restored to a VSAM cluster that has different options or characteristics. Message FDR152 or FDR159 details the error.

W

Catalog inaccessible. Possible causes are:

• When restoring a catalog, the JCL contained a STEPCAT or JOBCAT DD statement. This is not supported.
• When restoring a catalog, the catalog being restored was defined in the master catalog, but it was not usable (probably did not actually exist on DASD). You must remove the entry for the old catalog, probably by IDCAMS EXPORT DISCONNECT.

X

Data set security exit rejected this data set

Y

NEWINDEX= failure or duplicate data set name generated. It may be that the new data set name does not meet IBM standards, or that the resulting name is greater than 44 characters.

Z

One or more data sets failed to restore using ALLDSN or DSN=mask. Check the subtask listing for errors.

Action: Take appropriate action and/or contact BMC Support for assistance.

UNABLE TO RESTORE REASON=x--DSNAME=dsn

Explanation: The data set specified in the message could not be restored. The reason code “x” may be:

2

The ABR JCL does not include any DISKxxxx DD statement pointing to a DASD volume of the same type (for example, 3390) as the original volume of the data set.

3

The OPERATOR operand was specified, but the operator replied “NO” or “BYPASS” to the request for the backup tapes needed to restore the data set.

5

The DASD volume that FDR was attempting to restore the data set could not be opened, or could not be dynamically allocated.

6

Internal Error. Contact BMC Support.

7

For an ABR restore, the backup data set was not found.

A

For an ABR restore from volume backups, the data set was found on DASD and ABR is trying to get backup information from its DSCB but no current backup information was recorded. Either the data set has never been backed up by ABR or it has been deleted and reallocated since its last backup. This can also occur if some other software has corrupted the ABR backup information in the DSCB. If you can identify an ABR backup that contains the data set, you can specify GEN=, CYCLE=, and VOL= to restore it.

B

For an ABR restore from volume backups:

• The data set is not cataloged and VOL= was not specified.
• The data set is not on the volume identified by the system catalog (or by the VOL= operand).
• It was also not found in the ABR record of scratched and renamed data sets (the ABR SCRATCH catalog). The most likely causes are:
• The DSN= or VOL= operand is incorrect.
• The data set was archived.
• ABR is not recording scratched and renamed data sets (ABR DADSM exit not installed).

If you can identify an ABR backup that contains the data set, you can specify GEN=, CYCLE=, and VOL= to restore it.

D

For an ABR restore from volume backups, ABR identified a specific backup containing the requested data set, but that backup was not cataloged in the ABR catalog. The backup may have expired or was part of an older generation that ABR has uncataloged. If COPY=n was specified, it may be that the specified copy was not created. If the backup file still exists but has been uncataloged, TAPEDD= can be used to restore the data set.

E

For an ABR restore from archive backups, the backup file containing the data set has reached its expiration date (as recorded in the Archive Control File). If the backup file still exists, you can restore the data set by specifying TAPE=EXP on the RESTORE control statement.

F

For an ABR restore from volume backups, the volume from which the data set was backed up, as specified by the VOL= operand or the catalog, is not currently initialized for ABR processing; or an I/O error occurred when reading the ABR Model DSCB controlling the DASD volume. If you can identify an ABR backup that contains the data set, you can specify GEN=, CYCLE=, and VOL= to restore it.

G

SELECT statement for a data set restore did not specify VOL=. This data set was not found in the system catalog, or in ABR's record of scratched data sets. See reason “B” for suggestions.

H

The volume from which the data set was backed up, as specified by the VOL= operand or the system catalog, was not mounted so ABR could not locate the backup of the data set. If possible, mount the volume. If you can identify an ABR backup that contains the data set, you can specify GEN=, CYCLE=, and VOL= to restore it.

J

GEN= was specified without CYCLE=.

K

TAPEDD=x was specified but no TAPEx DD statement was found, or TAPEDD= was specified with TYPE=ARC.

L

The most likely causes are:

• The data set was not found on the volume specified by the VOL= operand (if coded) or by the catalog or it was found but had no current ABR backup recorded in its DSCB.
• The data set was found in the ABR SCRATCH catalog, but with a different volume serial. This probably occurred because the data set was scratched and reallocated on a different volume.
• The data set was found in the ABR SCRATCH catalog but the generation number was invalid.

You can restore the data set by specifying VOL= the volume in the ABR SCRATCH catalog, or by specifying VOL= and CYCLE= (and possibly GEN=) for any volume and cycle on which the data set was backed up, or by specifying TAPEDD=.

M

COPY=2 was requested for this data set, but the ARCHIVE control data set indicates that a second copy was not created during archival.

N

The backup file containing this data set failed to OPEN, or dynamic allocation error. Check the job log and SYSPRINT for IBM or FDR error messages. The backup data set may have been written over.

Q

RACF authorization error.

R

The backup file containing this data set was not an FDR-formatted backup; or an I/O error occurred reading the FDR Header Record.

T

A TYPE=ABR restore had a SELECT statement that specified DSG= or ALLDSN without either TAPEDD= or VOL=, GEN=, and CYCLE=.

U

DYNTAPE was specified but one or more TAPEx DD statements were also provided. DYNTAPE attempted to allocate a tape volume already allocated by one of the TAPEx DD statements. Remove the TAPEx DD statements and let DYNTAPE allocate all tapes.

V

For a restore from Archive Backup or Application Backup, the backup file exceeded 5 tape volumes, but ABR was not able to find an entry for it in the catalog. The catalog contains the complete volume list, while the Control File only records the first 5.

X

A DSF absolute track restore was requested (SELECT FROM/TO) and cylinder or track numbers were specified that are invalid for the type of DASD that was backed up.

Y

For an ABR restore from volume backups:

• OLDBACKUP= was specified. The data set does not contain as many levels of OLDBACKUP= information as requested by the OLDB=nn operand or the specified backup is no longer in the ABR catalog.
• The ABR backup information in the DSCB for the data set is invalid.

Z

An ABR data set restore was requested and a TAPEx DD statement was provided, but the backup containing this data set occupies more than 5 tape volumes. To restore this data set, remove the TAPEx DD statement and specify the DYNTAPE operand. This code also occurs if you use the TAPED=x operand on an archive restore (TYPE=ARC) or application restore (TYPE=APPL).

Action: Take appropriate action for the problem described by the message.

FDR324

DDNAME=ddn IS MISSING OR IN ERROR REASON=x

Explanation: A failure has occurred for ddname specified in the message. In the reason text below, “Control File” refers to the Archive Control File for Archive Backups, and to the Application Control File for Application Backups. The reason code “x” may be:

1

SYSIN DD statement missing.

2

I/O error on SYSIN data set or remote queue data set.

3

ARCHIVE DD statement missing and DYNARC was not specified.

4

Control File block size is zero. The file may have been allocated but never initialized. If so, use FDRARCH to initialize it.

5

I/O error on Control File.

6

The date of the last Archive or Application backup, as recorded in the Control File, is higher than the current system date; this might occur if you did backups while you had the system date set ahead for YEAR2000 testing. To override the ABR date check, specify PROT=NONE on the DUMP statement of next Archive or Application job using that Control File only. The Control File will be out of date sequence.

7

A block of the Control File did not contain ABR identifiers. The Control File may have been overwritten by another program. You may be able to restore a backup of the most recent Control File. Please contact BMC Support for assistance.

8

The Control File is full. You can reorganize or expand it with FDRARCH. If you are using the option of Application Backup to create the Control File, increase the space allocated.

9

The number of TAPEx DD statements exceeded 9.

A

No TAPEx DD statements were specifying tape or DASD backup were found. ABR ignores DD DUMMY statements

B

The number of DISKxxxx DD statements plus any volumes selected by ONLINE, ONLVOL, and MOUNT was greater than the value specified in the MAXDD= operand (default of 256).

D

A SYSPRINx DD statement was missing. ABR requires a SYSPRINx DD statement for each TAPEx DD statement.

E

A DISKx ddname was used more than once in the JCL for this step.

F

A FDR or FDRDSF backup specified DISP=MOD on the TAPEx DD statement. Also occurs if the TAPEx DD statement refers to a subsystem data set via the SUBSYS= JCL parameter, and the RTC=YES operand was also specified on the DUMP statement; these are not compatible. The DASD volume associated with this tape is not processed.

H

A TAPExx was specified in a Transparent Cloud Tiering (TCT) DUMP. TAPExx is not supported when DUMPING to the TCT.

I

OPEN failed for the backup file. Check the job log for IBM error messages.

K

LASTAPE was specified but the TAPEx DD specified more than one tape volume serial.

L

Most likely causes are:

• DYNTAPE was specified to dynamically allocate the backup medium but a TAPE# DD statement is in the JCL. Remove it; it is required for DYNTAPE dynamic allocation.
• A TAPEx DD statement was present on a TYPE=DRP restore. This is not permitted.

M

COPY or MOVE was specified. The TAPEx DD statement for the target volume was not a DASD or specified DD DUMMY.

N

The TAPEx DD statement specified the same volume serial as the DISKx DD statement.

O

Internal error detected by module FDRDSKTP. Contact BMC Support for assistance.

Q

An ABR dump specified DISK as the backup medium (TAPEx). ABR found that the volume to be dumped (DISKx) was the same as the backup medium (TAPEx). You cannot backup a volume to itself; it is bypassed.

R

ABR space allocation was not successful for a backup data set on any of the DASD volumes specified by the TAPEx DD statement. Possible reasons are:

• The output DASD volumes may be full or have insufficient space for this backup.
• The backup data set name being allocated already exists on the output volume (possibly due to an aborted ABR run). Scratch the duplicate backup data set and run the backup again.

S

SUBSYS= is not supported on TAPE DD statements with DUMP TYPE=ARC unless SCRATCH=NO is also specified (making it an application backup).

T

User specified multiple TAPEx DD statements using the same last character (x). The first one specified DUMMY.

U

Dynamic allocation or OPEN of the backup data set on a DASD volume failed. Check the job log for IBM error messages or the SYSPRINx printouts for FDR error messages.

Action: Take appropriate action for the problem described by the message.

FDR325

FDR328

LAST TAPE OR POOL OPTION FAILED ON TAPE DD=ddn REASON=reason DIAGNOSTIC DATA: R15=ffffffff R0=00000000 R1=11111111

Explanation: ABR JCL options were used to request for the LASTAPE, POOLTAPE, or POOLDISK features of ABR, but the request failed. “reason” can be:

1 LASTAPE FILE FAILED TO OPEN

The LASTAPE file identified in the JCL was cataloged as having been created in a previous ABR run, but the attempt to OPEN it failed. It may have been overwritten. Check for IBM OPEN error messages in the job log. ABR uncataloged the LASTAPE file so if you resubmit the job, ABR asks for a scratch tape.

6 POOLDISK DOES NOT SPECIFY DISK

Must point to DASD volumes.

9 LASTAPE/POOLTAPE NOT A TAPE

Must point to a tape device.

A LASTAPE UNCAT FAILED COMP=nnnn

The request to uncatalog the LASTAPE data set failed with catalog return code “nnnn”.

C POOLDISK SORTING ERROR SWAREQ

While sorting the POOLDISK volumes by space available, an error occurred during an SWAREQ macro to access the volume list.

D POOLDISK SORTING ERROR DEVTYPE

While sorting the POOLDISK volumes by space available, an error occurred doing a DEVTYPE macro on one of the volumes.

E POOLDISK SORTING ERROR UCB

While sorting the POOLDISK volumes by space available, an error occurred accessing a UCB.

F POOLDISK SORTING ERROR LSPACE

While sorting the POOLDISK volumes by space available, an error occurred doing an LSPACE macro to get the free space on the volume.

G POOLDISK DOES NOT SUPPORT SMS

POOLDISK volumes must be non-SMS volumes.

Action: You may be able to avoid reasons “C” through “F” by specifying POOLSORT=NO on the ABR DUMP statement. If the cause cannot be determined, contact BMC Support for assistance.

function SCRATCH status ON DSN=dsn

Explanation: An attempt to delete a non-VSAM data set FAILED or was BYPASSED. FDR deletes data sets during an FDRCOPY MOVE, an Archive Backup (DUMP TYPE=ARC), or ABR Superscratch (DUMP TYPE=SCR).

“status” of FAILED indicates that a SCRATCH SVC (for non SMS-managed data sets) or DELETE NVR or NONVSAM (for SMS-managed data sets) failed to scratch this data set. An FDR mini-dump is printed showing the registers and SCRATCH or DELETE parameter list.

For a non SMS-managed data set, the SCRATCH status code appears in the mini-dump, in the first line of the storage display after the registers, in the second byte of the last word (right most word).

• Code 1 indicates that the data set was not found in the VTOC.
• Code 7 indicates that SCRATCH failed because the data set was in use; this can be avoided by using the DSNENQ= operand.
• Code 2 or 8 indicates a security violation.

For an SMS-managed data set, register 15 (R15) contains the DELETE return code, and the reason code is in the last 2 bytes of the 6th word of the first line of the storage dump after the registers, in hex. These codes can be found under message IDC3009I in the IBM messages space after converting the codes to decimal.

• For Archive Backup, ABR has backed up the data set and recorded it in the Archive Control File. This data set may have been uncataloged or recataloged for recall as indicated by message FDR314.
• For Superscratch, this data set may have been uncataloged as indicated by message FDR314.
• For FDRCOPY MOVE, if the data set was cataloged, it has been successfully recataloged and/or uncataloged.

A “status” of BYPASSED indicates that the scratch was not attempted for this data set, because of an earlier error, such as a catalog error that is described by another message.

Action: If appropriate, scratch the data set spacely. If desired, contact BMC Support for assistance.

FDR334

FDR FAILED TO CATALOG comp DSN=dsn status

Explanation: FDR allocated and restored the non-VSAM data set “dsn”, but could not catalog it.

If “comp” is printed, it is COMP=X'ffff00001111' that contains the catalog return codes from registers R15 (ffff), R0 (0000), and R1 (1111). If the register 15 value is x'FF14', then the code was generated by FDR, and indicates either that the data set was currently cataloged on zero volumes or more than 255 volumes, or that the volume sequence number of the current piece of the data set was higher than 255; the R0 value is the number of volumes currently in the catalog entry (in hex). FDR supports cataloging of multi-volume data sets up to a maximum of 255 volumes.

If “status” is ALREADY CATALOG VOL=vol then RECAT was not specified, and the output data set was already cataloged to a volume “vol” other than the output volume (or the input volume for a MOVE). For a multi-volume data set, “vol” is the volume in the catalog entry that corresponds to the volume sequence number of the portion of the data set that has just been processed.

If “status” is NAME IS AN ALIAS then the data set name being cataloged was an alias of another data set in the catalog so FDR did not update it.

Action: Determine the cause and take appropriate action. If desired, contact BMC Support for assistance.

FDR336

DYNAMIC ALLOCATION ERROR COMP=cc, CODE=nnnn, INFO=iiii, DDNAME=ddn bypass

Explanation: FDR attempted to dynamically allocate (DYNALLOC) a DASD volume or a data set (such as a DASD or tape backup data set, the Archive Control File, or the FDRCRYPT Encryption Keyfile), but the allocation failed. “cc” is the return code in R15, “nnnn” is the dynamic allocation reason code, and “iiii” is the dynamic allocation information code. For z/OS, these codes are documented in the IBM space Authorized Assembler Services Guide. They can also be found in Appendix A of the ISPF online HELP. Frequently encountered “nnnn” values include:

0210

Requested data set not available (for example, another job had the Archive Control File with DISP=OLD).

0218

TSO user did not have MOUNT privileges to mount an ABR tape.

021C

Invalid unit name used. ABR uses generic unit names, such as 3480, 3490, 3590-1, 3390, and the rest. One common cause of this is an attempt to allocate a 3480 cartridge on a system that no longer has 3480s in the configuration; contact BMC Support for a circumvention.

0220

Requested volume not available (for example, another job is using a tape volume required by ABR).

0484

The operator replied “NO” to message IEF235D.

1708

Data set not found in the catalog (for example, the name in the ABR option table for the Archive Control File does not exist in the catalog).

“bypass” may be VOL=vol BYPASSED indicating that ABR bypassed processing the volume because of the error or DSN=dsn BYPASSED if a data set was bypassed.

Action: This volume or data set operation is bypassed. In some cases, the error can be avoided by setting the dynamic allocation flags in the FDR Global Options (see ALLOCATEFLAG in Section ABR-Options). If necessary, contact BMC Support for assistance.

FDR338

FDR341

FDR FAILED TO FIND THE ABR HIGH LEVEL INDEX

Explanation: FDRABR issued a LOCATE (SVC 26) for the ABR high-level index (by default, FDRABR), however, the alias could not be found.

Action: Use IDCAMS LISTCAT to list the master catalog and determine if an alias entry exists for the ABR index. Check the ABR high-level index name specified in the FDR Global Options and determine if the name matches the one in the master catalog. If cause cannot be determined, contact BMC Support for assistance.

FILTER ERROR REASON=reason -- ENTRY=entry

Explanation: “SELECT CATDSN=filter” was used to select entries from the system catalogs, and an error occurred. “entry” indicates the catalog name or the catalog entry on which the error occurred. “reason” indicates the error:

1 - NO CATALOGED ENTRIES FOUND

The filter did not select any entries from the catalogs. See Generic-Data-Set-Name-Selection for filter rules. For VSAM clusters, the filter is only compared to the base cluster name. Component names, PATH names and AIX (alternate index) cluster and component names are not tested.

2 - CATLG ERROR COMP=cccc CODE=reason

The IBM catalog SVC returned return code “xxxx” with reason code “reason”. These codes can be found under message IDC3009I in IBM message spaces.

3 - CATLG NAME FPL ADDR MISSING

Internal error.

4 - CATLG VOLSER FPL ADDR MISSING

Internal error.

5 - CATLG VOLSER 0 OR MORE THAN 20

A catalog entry was selected that had either 0 volume serial numbers or more than 20 volume serial numbers in a CVOL (SYSCTLG) catalog.

6 - MAXCARDS MUST BE INCREASED

Since a SELECT statement is simulated for every data set selected from the catalog, the value of MAXCARDS= must be large enough to accommodate all selected data sets.

7 - CATLG ENTYPE FPL ADDR MISSING

Internal error.

A - NAME LAST CHARACTER HIGH VALUES

Internal error.

B - VSAM COMPONENTS NOT FOUND

A VSAM cluster was selected from the catalog but catalog entries for its components were not found.

C - VOL= CANNOT BE SPECIFIED

The VOL= operand cannot be specified on a SELECT CATDSN= statement in a RESTORE operation.

D - CANNOT END IN A PERIOD

The filter cannot end in a period. See Generic-Data-Set-Name-Selection for filter rules.

E - INVALID GENERATION NUMBER

The filter ends in an invalid GDG relative generation number.

F - SEQUENCE ERROR IN CATALOG

A VSAM sequence error was encountered reading a catalog, indicating a structural error in the catalog.

G - ALL ENTRIES EXCLUDED OR DUPS

All catalog entries matching this filter were discarded because:

• They were excluded by a preceding EXCLUDE statement.
• They were selected by a preceding SELECT statement.
• They specified a volume serial that did not match the VOL= operand on this SELECT statement.
• They were migrated by DFSMShsm (vol=MIGRAT).
• They were archived by ABR and recataloged for Auto-recall.

J - INSUFFICENT STORAGE

The REGION size was not large enough. Increase the REGION (use REGION=0M if you can) and resubmit.

K - ABR BACKUP NOT FOUND VOL=vol

The ABR backup file for a cloned data set was not found in the ABR catalog. The current backup of a selected data set is no longer recorded.

S - SYMBOLIC CATALOG NAME ERROR - ENTRY=catalog.name

Either the supplied symbolic catalog name could not be resolved or the resolved catalog name could not be found.

Correct the catalog name and rerun the job.

Action: Serious errors cause an U0502 abend. Others (such as reason “1”) are simply treated as if a SELECT statement did not select any data sets, unless SELTERR=NO was specified.

SMS MGMTCLAS ERROR VOL=vol REASON=reason DSN=dsn

Explanation: SMSMANAGE=YES was specified, but an error occurred trying to use SMS management classes for ABR processing. “vol” identifies the volume being processed (if known) and “dsn” identifies the data set being processed for errors related to a particular data set. “reason” describes the error:

GETMAIN FAILURE -- MGMTCLAS DISABLED

Indicates that the GETMAIN for storage above the 16M line to hold the definitions of all active management classes failed. Management class processing is disabled.

NVR/VVR TYPE UNKNOWN

A VVDS record was not type N, Z, or Q. The VVDS may be damaged.

TYPE 21 NOT FOUND

The type 21 cell was not found in a VSAM VVR. The VVDS may be damaged.

TYPE 22 NOT FOUND

The type 22 sub-cell was not found in a non-VSAM NVR. The VVDS may be damaged.

TYPE 23 NOT FOUND

The type 23 cell was not found in a VSAM VVR. The VVDS may be damaged.

TYPE 24 NOT FOUND

The type 24 cell was not found in a non-VSAM NVR. The VVDS may be damaged.

MGMTCLAS INVALID

The management class name in the NVR/VVR of an SMS-managed data set (or the default management class name) is not currently defined to SMS.

NO MGMTCLAS TABLE

Internal error.

NO VVDS ENTRY

No NVR/VVR was found in the VVDS for an SMS-managed data set. The VVDS or the VTOC may be damaged, or creation of an SMS-managed data set was interrupted.

MULTI-VOL ERROR

For a multi-volume data set, a LOCATE is done on other than the first volume to get the management class, and it failed.

Action: If DSN= is displayed, that data set is not selected by ABR in this run. If possible, correct the error and rerun. If necessary, contact BMC Support for assistance.

FDR365

TAPE WAS NOT FOUND DSN=dsn

Explanation: ABR attempted to locate this backup file in the ABR catalog. The catalog search failed. This entry may have been uncataloged.

Action: ABR bypasses this file. Use the TAPEDD= operand on the SELECT statement if the data set name, volume serials and file number are known. Contact BMC Support for assistance.

FDR366

CYL TRKS-0....5....ABCDEF0....5....ABCDEF -- TRACKS NOT FOUND ON TAPE

Explanation: The indicated tracks were expected to be on the backup tape, but they were not found. One detail line is printed for each cylinder for which tracks were not found. The cylinder number is printed in decimal. The tracks that were not found are each indicated by an “X”. The position of the “X” indicates the number of the track: the first position after the hyphen in the heading line represents track 0, the next position is track 1, and so on.

Action: Review the listing from the backup run that created the tape. A possible reason for getting message FDR366 on a restore is that message FDR123 with REASON=2 appeared on the backup run, indicating that the entire cylinder was not dumped. On a data set restore, if message FDR155 does not appear, then the tracks not found were not needed, and the requested data sets have been correctly restored. On a full-volume restore, message FDR366 always indicates that not all of the tracks have been restored. If appropriate, contact BMC Support for assistance.

ABR TERMINATED RESTORE FOR NOT FINDING FDR TAPE

Explanation: On a full-volume restore, ABR could not locate the full-volume restore tape (cycle 00) in the ABR catalog. Message FDR365 identifies the backup data set

Action: This volume restore is terminated. Contact BMC Support for assistance.

FDR368

OPEN ERROR -- TAPE BYPASSED DSN=dsn

Explanation: A full-volume restore operation was requested from this tape. The open of the tape failed. ABR bypasses this tape unless it is the full volume (FDR) backup.

Action: Check for IBM OPEN messages in the job log. Data sets that were on this incremental backup may not be restored to their latest status. Contact BMC Support for assistance.

FORMAT 4 DSCB NOT FOUND ON RESTORE TAPES

Explanation: FDR or ABR full-volume restore did not find the Format 4 DSCB (first record of the VTOC) on any of the backup tapes. The restore may not be correct. This can occur if the pointer to the VTOC in the DASD volume label was invalid at the time of the dump, or if errors occurred reading the backup records containing the VTOC.

Action: Contact BMC Support for assistance.

DISK FORMAT 4 READ ERROR

Explanation: An I/O error occurred reading the Format 4 DSCB (first record on the VTOC) of the output DASD volume during a full-volume restore. The pointer to the next available alternate track on the volume, stored in the Format 4, if any, are lost, but the volume is probably usable. A mini-dump is printed, showing the I/O error.

Action: Run a COMPAKTOR MAP to check for VTOC errors. Contact BMC Support for assistance.

UCB VTOC LOCATION WAS NOT UPDATED

Explanation: FDR failed to locate the DASD label record on the backup tape (Cylinder 0 Track 0 Record 3) during a full-volume restore. The volume was restored, but the system pointers to the VTOC, VTOC Index, and VVDS were not updated. The output volume may not have a volume label.

Action: Use FDRDSF with “PRINT TYPE=DSF,DSN=VTOC” to print the label track and VTOC to verify that the VOL1 volume label exists on CYL 0 TRK 0; if not, contact BMC Support for assistance. If so, vary the volume offline and then remount it to update the system pointers.

FDR374

ABR MODEL OR VTOC INDEX REWRITE/RENAME/ALLOC FAILED

Explanation: An error occurred when FDR attempted to rewrite or allocate the ABR Model DSCB, or rename the index VTOC or ABR Model DSCB. The user may not be authorized to create, rename, or update this data set.

Action: This volume may need to be re-initialized for ABR processing, or the indexed VTOC may need to be rebuilt with ICKDSF. Contact BMC Support for assistance.

MULTIPLE ABR MODELS FOUND ON BACKUP DSN=dsn

Explanation: FDR found more than one ABR Model DSCB on the backup tape during a full-volume restore. The first one encountered is the one used. The DASD volume serial number or the ABR Model DSCB name may have been changed prior to the dump without using the ABR maintenance programs.

Action: SCRATCH the incorrect model using IEHPROGM specifying PURGE on the SCRATCH command. Use program FDRABRM with a REMODEL command (see FDRABRM-REMODEL-Statement) or the ABR ISPF dialogs (see ABR-Options) to reset the remaining ABR Model DSCB to the correct Generation and Cycle number. Contact BMC Support for assistance.

RENAME FAILED COMP=cccc CODE=code FROMDSN=tempname NEWDSN=permname CLUSTER=clusname

Explanation: On an FDRCOPY MOVE or RESTORE of a VSAM cluster to the same name, the output cluster and its components were initially created with temporary names (an index level starting with “T” is inserted). After the input data set was deleted, FDRCOPY attempted to ALTER the temporary names back to the original cluster and component names but an error occurred. “cccc” is the return code and “code” is the reason code from ALTER; look up these codes under IBM message IDC3009I in the IBM message spaces.

If “cccc” is 04nn, then “nn” is the return code from a RENAME SVC; if it is 05nn, then it is a return code from the SMS RENAME service.

“tempname” is the temporary cluster or component name that FDRCOPY was trying to rename back to “permname”. “clusname” is the original name of the cluster if the rename failed on a component.

Action: If an FDR378 is not issued for the cluster itself, it was renamed successfully and the cluster can be used under its original name.

If an FDR378 was issued for the cluster, the cluster was not renamed. It can be used under its temporary name “tempname”, but you probably want to check the error codes and ALTER the cluster to its original name if possible.

If FDR378 messages were issued for one or more components, those components were not renamed. The cluster is usable, but you may want to check the error codes and ALTER the component to its original name if possible.

If needed, contact BMC Support for assistance.

FDR392

function SELECTED DSN=dsn [(clustername)]

Explanation: Message showing the data sets that were selected for backup. For VSAM clusters, “dsn” is the component name and “clustername” is the cluster name.

FDR CLOUD ID=nnnnnnnn OBJ=backup.object

Explanation: Message showing the data set name of the backup.object that was specified on the TAPEn DD statement for the DUMP using Transparent Cloud Tiering (TCT).

FDR407