FDR V54L78 - Innovation Data Processing

FDR203
Reason:
Action:
MESSAGES AND CODES
CHAPTER 100 – PAGE 100-45 –
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
PREMATURE TAPE END OF FILE DSN=dsname
FDR restore detected an end-of-file on the backup data set without encountering the FDR
trailer record. The dump may not have successful. On an FDR full volume or data set
restore, FDR terminates with an U0201 ABEND; however, on a data set restore FDR stops
reading the backup when it has restored all tracks required for the data sets selected, so it
may not issue the FDR203 message or the U0201 ABEND.
The following are possible causes:
❖ The backup that created this file did not complete successfully.
❖ The backup run completed successfully, but the backup file was not correctly cataloged.
❖
The JCL for the restore specifies volume serial numbers for the backup file, but
the last volume has been omitted, or the volume serials are out of order.
In the last two cases, you can do the restore by specifying the correct volume serial
numbers on the DD statement for the backup file.
FDR204 TAPE BLOCK LENGTH CHECK--BLOCK BYPASSED
Reason: 1.FDR stores the length of each block written to the backup in the first two bytes of the block.
The length of the block read did not match the length stored in the first two bytes.
2. An error occurred during decompression of a block compressed by FDR software compression.
Action: An FDR mini-dump is printed displaying the beginning of the block. FDR continues processing,
bypassing this block. One or more tracks of data may have been lost. Message FDR366 details
the tracks lost, if any. For a data set restore, unless message FDR155 is displayed, no tracks
necessary for this restore were lost and the restore is successful.
If message FDR204 occurs many times, the cause is probably that you are restoring
from a tape that was created by using a utility program (such as IEBGENER) to copy
an FDR backup file.
Most utilities cannot copy FDR backup tapes. FDRTCOPY, FDRTSEL, or FATAR must
be used to copy FDR backup tapes. Other causes include transmission of an FDR
backup over a network, or some channel extenders used for attaching tapes.
FDR205 TAPE BLOCK CROSS-CHECK ERROR
Reason: FDR encountered an error de-blocking one of the tape blocks into track and disk block images.
A mini dump is printed displaying the beginning of the bad block. An U0204 ABEND is
issued if MAXERR= errors is exceeded.
FDR206 TAPE BLOCK COUNT ERROR
Reason: The number of blocks read from the tape did not match the block count in the tape trailer label.
Action:
An FDR mini-dump is printed displaying the DCB and registers. Register zero (0) contains the
block count from the tape trailer label that reflects the number of blocks written to the tape
volume during the backup. The fourth word of the DCB contains the count of blocks read during
the restore. FDR ignores the error and continue processing. If tracks necessary to do the
restore are lost, FDR details them in message FDR366.
FDR207 TAPE CROSS-REFERENCE TABLE IS MISSING DSN=dsname
Reason: FDR could not find the track table on the backup data set “dsname”. The backup may
have been corrupted or overwritten.
Action: The restore continues without the cross-reference check. Message FDR366 is not
issued even if data tracks were lost.
FDR210 I/O ERROR ON BACKUP DD=ddname
Reason: An I/O error occurred writing an FDR backup to the backup data set identified by
“ddname”. The message is followed by I/O diagnostic messages that identify the error.
Action: Rerun the backup, using a different output tape and/or tape drive. Ask your tape
hardware service representative to investigate the cause of the error.