30.01.2015 Views

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MESSAGES AND CODES<br />

MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />

<strong>FDR</strong>370 OPEN ERROR -- TAPE BYPASSED DSN=dsname<br />

Reason: A full-volume restore operation was requested from this tape. The open of the tape<br />

failed. ABR bypasses this tape unless it is the full volume (<strong>FDR</strong>) backup.<br />

Action: Check for IBM OPEN messages in the job log. <strong>Data</strong> sets that were on this incremental<br />

backup may not be restored to their latest status. Contact INNOVATION DATA<br />

PROCESSING for assistance.<br />

<strong>FDR</strong>371 FORMAT 4 DSCB NOT FOUND ON RESTORE TAPES<br />

Reason: <strong>FDR</strong> or ABR full-volume restore did not find the Format 4 DSCB (first record of the<br />

VTOC) on any of the backup tapes. The restore may not be correct. This can occur if<br />

the pointer to the VTOC in the disk volume label was invalid at the time of the dump,<br />

or if errors occurred reading the backup records containing the VTOC.<br />

Action: Contact INNOVATION DATA PROCESSING for assistance.<br />

<strong>FDR</strong>372 DISK FORMAT 4 READ ERROR<br />

Reason: An I/O error occurred reading the Format 4 DSCB (first record on the VTOC) of the<br />

output disk volume during a full-volume restore. The pointer to the next available<br />

alternate track on the volume, stored in the Format 4, if any, are lost, but the volume is<br />

probably usable. A mini-dump is printed, showing the I/O error.<br />

Action: Run a COMPAKTOR MAP to check for VTOC errors. Contact INNOVATION DATA<br />

PROCESSING for assistance.<br />

<strong>FDR</strong>373 UCB VTOC LOCATION WAS NOT UPDATED<br />

Reason: <strong>FDR</strong> failed to locate the disk label record on the backup tape (Cylinder 0 Track 0<br />

Record 3) during a full-volume restore. The volume was restored, but the system<br />

pointers to the VTOC, VTOC Index, and VVDS were not updated. The output volume<br />

may not have a volume label.<br />

Action: Use <strong>FDR</strong>DSF with “PRINT TYPE=DSF,DSN=VTOC” to print the label track and VTOC<br />

to verify that the VOL1 volume label exists on CYL 0 TRK 0; if not, contact<br />

INNOVATION DATA PROCESSING for assistance. If so, vary the volume offline and<br />

then remount it to update the system pointers.<br />

<strong>FDR</strong>374 BACKUP TAPE DID NOT CONTAIN THE ABR MODEL<br />

Reason: <strong>FDR</strong>ABR failed to locate the ABR Model DSCB in the control records at the beginning of<br />

the first incremental backup read during an ABR full-volume recovery. A normal<br />

incremental backup always contains the ABR Model DSCB, so this is not normal<br />

(perhaps the ABR Model DSCB was excluded by an EXCLUDE statement.<br />

Action: If the output volume contains an ABR Model DSCB and has the same serial as the<br />

volume being restored, the restore terminates with an U0304 ABEND. If not, the<br />

restore proceeds; this message is issued once for each incremental that does not<br />

contain the ABR Model DSCB; some data sets may not be restored correctly.<br />

<strong>FDR</strong>375 ABR MODEL OR VTOC INDEX REWRITE/RENAME/ALLOC FAILED<br />

Reason: An error occurred when <strong>FDR</strong> attempted to rewrite or allocate the ABR Model DSCB, or<br />

rename the index VTOC or ABR Model DSCB. The user may not be authorized to<br />

create, rename, or update this data set.<br />

Action: This volume may need to be re-initialized for ABR processing, or the indexed VTOC<br />

may need to be rebuilt with ICKDSF. Contact INNOVATION DATA PROCESSING for<br />

assistance.<br />

CHAPTER 100 – PAGE 100-78 –

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!