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 />

Action:<br />

S –<br />

T –<br />

U –<br />

V –<br />

W –<br />

X –<br />

Y –<br />

Z –<br />

– PDSE to non-PDSE<br />

– HFS to non-HFS<br />

– Extended Format SMS to non-EF<br />

– And vice-versa in each case. Other combinations also cause errors.<br />

A data set that must be SMS-Managed (such as Extended Format (EF)) is<br />

being restored to a non-SMS volume.<br />

<strong>FDR</strong>COPY COPY/MOVE detected a copy/move of a data set on top of itself<br />

(same volser, same data set name).<br />

Error updating ISAM Format 2 DSCB, or VSAM component in the VTOC but<br />

not in the VVDS.<br />

VSAM cluster is being restored to a VSAM cluster that has different options<br />

or characteristics. Message <strong>FDR</strong>152 or <strong>FDR</strong>159 details the error.<br />

Catalog inaccessible. Possible causes are:<br />

– When restoring a catalog, the JCL contained a STEPCAT or<br />

JOBCAT DD statement. This is not supported.<br />

– When restoring a catalog, the catalog being restored was defined<br />

in the master catalog, but it was not usable (probably did not<br />

actually exist on disk). You must remove the entry for the old<br />

catalog, probably by IDCAMS EXPORT DISCONNECT.<br />

<strong>Data</strong> set security exit rejected this data set<br />

NEWINDEX= failure or duplicate data set name generated. It may be that<br />

the new data set name does not meet IBM standards, or that the resulting<br />

name is greater than 44 characters.<br />

One or more data sets failed to restore using ALLDSN or DSN=mask.<br />

Check the subtask listing for errors.<br />

Take appropriate action and/or contact INNOVATION DATA PROCESSING for assistance.<br />

<strong>FDR</strong>321 UNABLE TO RESTORE REASON=x--DSNAME=dsname<br />

Reason: The data set specified in the message could not be restored. The reason code “x” may be:<br />

2 – The ABR JCL does not include any DISKxxxx DD statement pointing to a disk<br />

volume of the same type (e.g., 3390) as the original volume of the data set.<br />

3 – The OPERATOR operand was specified, but the operator replied “NO” or<br />

“BYPASS” to the request for the backup tapes needed to restore the data set.<br />

5 – The disk volume that <strong>FDR</strong> was attempting to restore the data set could not<br />

be opened, or could not be dynamically allocated.<br />

A – For an ABR restore from volume backups, the data set was found on disk and<br />

ABR is trying to get backup information from its DSCB, but no current backup<br />

information was recorded. Either the data set has never been backed up by<br />

ABR or it has been deleted and reallocated since its last backup. This can also<br />

occur if some other software has corrupted ABR's backup information in the<br />

DSCB. If you can identify an ABR backup that contains the data set, you can<br />

specify GEN=, CYCLE=, and VOL= to restore it.<br />

B – For an ABR restore from volume backups:<br />

– The data set is not cataloged and VOL= was not specified.<br />

– The data set is not on the volume identified by the system catalog<br />

(or by the VOL= operand).<br />

– It was also not found in ABR's record of scratched and renamed data<br />

sets (the ABR SCRATCH catalog). The most likely causes are:<br />

– The DSN= or VOL= operand is incorrect.<br />

– The data set was archived.<br />

– ABR is not recording scratched and renamed data sets (ABR<br />

DADSM exit not installed).<br />

If you can identify an ABR backup that contains the data set, you can<br />

specify GEN=, CYCLE=, and VOL= to restore it.<br />

CHAPTER 100 – PAGE 100-65 –

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

Saved successfully!

Ooh no, something went wrong!