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>629 DSN=dsname SCRATCH FAILED volser CODE=nnnn<br />

Reason: <strong>FDR</strong>TSEL received a non-zero return code for the request to scratch a disk Archive<br />

Backup. This message is accompanied by an <strong>FDR</strong>516 message containing the error<br />

return codes, and by another <strong>FDR</strong>629 message containing the scratch return code for<br />

each of the volumes where the archive backup resides.<br />

Action: See message <strong>FDR</strong>516.<br />

<strong>FDR</strong>630<br />

Reason:<br />

Action:<br />

INSUFFICIENT STORAGE service description -- AMOUNT REQUIRED nnnnnnnn BYTES<br />

INSUFFICIENT STORAGE TO READ ENTIRE VVDS -- VOL=volser -- AMOUNT<br />

REQUIRED nnnn PAGES<br />

INSUFFICIENT STORAGE TO READ ENTIRE VVDS -- VOL=volser -- AMOUNT<br />

REQUIRED nnnnnnnn nnnnnnnn SEGMENTS<br />

The executing program requires additional storage to perform the service described but<br />

is unable to get enough storage.<br />

Increase the region size (REGION=) and resubmit the job. If the program is <strong>FDR</strong>EPORT<br />

and message <strong>FDR</strong>631 follows, <strong>FDR</strong>EPORT runs successfully.<br />

<strong>FDR</strong>631 VTOC WILL BE READ ONE (1) TRACK AT A TIME<br />

Reason: Because of insufficient storage, <strong>FDR</strong>EPORT was unable to read the entire VTOC into<br />

storage, so it is read one track at a time.<br />

Action: <strong>FDR</strong>EPORT should complete successfully, but the elapsed time is increased. Increase<br />

the region size for future use.<br />

<strong>FDR</strong>632 SYS1.VVDS.Vvolser IN ERROR -- CONTAINS EXTENT COUNT OF ZERO<br />

SYS1.VVDS.Vvolser REQUIRED -- NAME NOT FOUND IN VTOC<br />

Reason: <strong>FDR</strong>EPORT was trying to read the VVDS since the volume contains VSAM clusters or<br />

SMS-Managed data sets, but it failed for the reason indicated.<br />

Action: Message <strong>FDR</strong>618 follows.<br />

<strong>FDR</strong>633 SYS1.VVDS.Vvolser IN ERROR -- FORMAT 3 DSCB NOT FOUND IN VTOC<br />

Reason: <strong>FDR</strong>EPORT was trying to read the VVDS since the volume contains VSAM clusters or<br />

SMS-Managed data sets, but it failed for the reason indicated.<br />

Action: Message <strong>FDR</strong>618 follows.<br />

<strong>FDR</strong>634 SYS1.VVDS.Vvolser IN ERROR -- I/O ERROR READING VVDS<br />

Reason: <strong>FDR</strong>EPORT was trying to read the VVDS since the volume contains VSAM clusters or<br />

SMS-Managed data sets, but it failed for the reason indicated.<br />

Action: Message <strong>FDR</strong>618 follows.<br />

<strong>FDR</strong>635 TRKCALC FAILED -- R15=xxxxxxxx -- VOL=vvvvvv -- DSN=dsname<br />

SYS1.VVDS.Vvolser IN ERROR -- TRKCALC FAILED -- R15=xxxxxxxx<br />

Reason: The TRKCALC SVC was issued for the data set name listed to determine the number of<br />

records that fit on a track of the device. The SVC failed with a non-zero return code in<br />

register 15.<br />

Action: The following fields are set to zero (0) as a result of the failing TRKCALC:<br />

%CAPUSED, BLKSTRK, BYTESFRE, BYTESUSE, and CAPBYTES.<br />

Call INNOVATION DATA PROCESSING for support.<br />

CHAPTER 100 – PAGE 100-107 –

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

Saved successfully!

Ooh no, something went wrong!