FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
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 />
– Application Control File (for restore from Application Backup)<br />
<strong>FDR</strong> bypasses the restore of the data set. These data sets are read and updated by <strong>FDR</strong><br />
during a restore, so it is almost always a mistake to try to restore them as data sets.<br />
SELECT ALLDSN may cause <strong>FDR</strong>159 REASON=3 for the VVDS even though it was not<br />
backed up; it can be ignored. This message is only a warning message; it does not cause<br />
an ABEND or non-zero condition code to be issued. If the VTOC index is damaged, the<br />
best way to recover is usually to rebuild it by using the BUILDIX command of program<br />
ICKDSF. To rebuild the ABR Model DSCB use the REMODEL command of program<br />
<strong>FDR</strong>ABRM (Section 50.40 “VTOC Maintenance Utility (<strong>FDR</strong>ABRM)”).<br />
Correct if this is an error. The message can be ignored if you did not intend to restore<br />
these data sets, but if the message is annoying, add an EXCLUDE DSN=dsname<br />
statement before the SELECT to suppress it.<br />
<strong>FDR</strong>160<br />
Reason:<br />
Action:<br />
UNABLE TO RESTORE -- INDEX HAS INCORRECT EXTENT SIZES -- CLUSTER=clustername<br />
SCRATCH THE CLUSTER AND TRY THE RESTORE AGAIN LETTING <strong>FDR</strong><br />
ALLOCATE IT FOR YOU. MESSAGE <strong>FDR</strong>152 REASON=K FOLLOWS.<br />
The VSAM cluster that was backed up, or the input VSAM cluster for the copy or move,<br />
had an imbedded index (the IMBED option), and had an index component that was in<br />
multiple extents. In order to do the restore or copy or move, the output cluster must<br />
have the same arrangement of extents as the original cluster. However, the output<br />
cluster was found to exist on disk before the restore or copy or move, with a different<br />
arrangement of extents. There is no practical way for the user to DEFINE the output<br />
cluster with the correct arrangement of extents.<br />
Delete the cluster that you pre-defined, and let <strong>FDR</strong> do the allocation. <strong>FDR</strong><br />
automatically rebuilds the cluster with the original arrangement of extents.<br />
<strong>FDR</strong>161 XMS ERROR REASON=x<br />
Reason: <strong>FDR</strong> was unable to find module IGG0CLX0 in the Catalog Address Space (CAS) using<br />
Cross Memory Services (XMS). The reason codes document various internal errors.<br />
Action: Contact INNOVATION DATA PROCESSING for assistance.<br />
<strong>FDR</strong>162 SMS ERROR MESSAGE FOR DSN=dsname message text<br />
Reason: The allocation of an SMS-Managed data set failed. The diagnostic and informational<br />
messages generated by SMS during this allocation are printed.<br />
Action: Examine the messages to determine the cause of the allocation failure.<br />
<strong>FDR</strong>164<br />
Reason:<br />
Action:<br />
CANDIDATE-SPACE ALLOCATION BYPASSED DSN=dsname<br />
The current backup or input disk contains an extent of a multi-volume VSAM cluster that was<br />
flagged as a “candidate space”. A candidate space is created when a multi-volume SMS<br />
cluster is allocated with a storage class with the “guaranteed space” attribute and real<br />
volume serials are specified. SMS pre-allocates extents on the volume, but they are not<br />
part of the active extents of the cluster until it expands and uses them.<br />
The candidate space is bypassed and is not allocated. <strong>FDR</strong> does not restore VSAM<br />
candidate volumes, either regular or candidate-space.<br />
CHAPTER 100 – PAGE 100-41 –
Change language