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.

CHAPTER 100 – PAGE 100-130 –<br />

MESSAGES AND CODES<br />

COMPAKTOR MESSAGES (CPKNNNXX) 100.6<br />

CPK470W reason DSN=dsname<br />

Reason: The data set “dsname” was not moved. “reason” can be:<br />

DATA SET IS ACTIVE OR UNMOVABLE – The data set is either in use by another<br />

task or is considered unmovable by COMPAKTOR (see “Unmovable<br />

<strong>Data</strong> Sets” in Section 40.4).<br />

DATA SET IS UNCHANGABLE – The extents of the data set cannot be combined<br />

(usually issued for a VSAM component whose characteristics inhibit<br />

combination).<br />

DATA SET WAS NOT MOVED – The data set was not selected for movement.<br />

This message is printed only if the PRINT=ALL operand was specified.<br />

DUPLICATE VVR EXISTS FOR – More than one VVR was detected in the VVDS<br />

for a given VSAM component.<br />

CPK501E I/O ERROR ON UNIT=uuuu,VOLSER=vvvvvv<br />

Reason: Issued when a permanent I/O error is detected on the direct-access device on unit<br />

“uuuu”, with a volume serial number of “vvvvvv”.<br />

Action: This message is always followed by a COMPAKTOR mini-dump. In this mini-dump you<br />

find the IOB, DCB, UCB, DEB, CCW CHAIN, and the last home address read.<br />

Examine the IOB sense bytes to determine the reason for the I/O error. Review<br />

<strong>FDR</strong>149 messages for information on the CCW chain in error. If you need assistance,<br />

please contact INNOVATION DATA PROCESSING.<br />

CPK502E I/O ERROR --- synadaf info<br />

Reason: While executing a COMPAKT-from-backup, a permanent I/O error was detected reading<br />

the <strong>FDR</strong> backup with BSAM. The IBM macro SYNADAF was issued to get a formatted<br />

string indicating the nature of the I/O error; that string is printed as “synadaf info”.<br />

Action: Examine the SYNADAF message to determine the cause of the error. For additional<br />

assistance, please contact INNOVATION DATA PROCESSING.<br />

CPK503E UNEXPECTED END-OF-FILE ON INPUT TAPE<br />

Reason: While executing a COMPAKT-from-backup, the physical end of the backup was found<br />

before the special <strong>FDR</strong> trailer record was read. It is possible that the <strong>FDR</strong> backup tape<br />

volumes were mounted out of order or the <strong>FDR</strong> dump did not successfully complete.<br />

Action: If message CPK321I has been printed and message CPK322I has not, the output disk<br />

volume is probably unusable. If the error can be corrected, or a good backup can be<br />

located, do an <strong>FDR</strong> restore.<br />

Contact INNOVATION DATA PROCESSING if you need assistance recovering from<br />

this error.<br />

CPK504E INPUT TAPE IS NOT AN <strong>FDR</strong> DUMP TAPE<br />

Reason: While executing a COMPAKT-from-backup, either the input tape was not created by an<br />

<strong>FDR</strong> dump, or <strong>FDR</strong> encountered errors in the VTOC when dumping (message<br />

<strong>FDR</strong>125).<br />

Action: Insure tape is an <strong>FDR</strong> volume dump tape (DSF created tapes are not accepted by<br />

COMPAKTOR). Insure that tapes were mounted in the order they were created.<br />

CPK505E TAPE BLOCKSIZE ERROR. FIRST 64 BYTES OF BLOCK READ FOLLOW.<br />

Reason: While executing a COMPAKT-from-backup, the number of bytes read from the backup<br />

for a certain block does not match the internal blocksize or the block read is invalid.<br />

This may be due to tape drive hardware errors or tape media problems and can also<br />

be caused by copying an <strong>FDR</strong> dump tape with other than the <strong>FDR</strong> Tape Copy Utility<br />

<strong>FDR</strong>TCOPY (or FATAR).<br />

Action: If possible, clean the tape and tape drive. Retry using a different tape drive or a different<br />

backup. If it still fails, contact INNOVATION DATA PROCESSING for assistance.

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

Saved successfully!

Ooh no, something went wrong!