FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
MESSAGES AND CODES<br />
MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />
Action:<br />
9459 – Volsers in CPL cannot be located, or over 10 volumes passed. Contact<br />
INNOVATION DATA PROCESSING.<br />
An <strong>FDR</strong> mini-dump is printed displaying the CATALOG DEFINE parameter list and related data<br />
areas. Determine the cause and take appropriate action. For errors involving names already in<br />
the catalog, the VRECAT operand on the RESTORE statement may be used to DELETE the<br />
duplicate names from the catalog (but should be used cautiously since it may DELETE other<br />
clusters). If needed, contact INNOVATION DATA PROCESSING for assistance.<br />
When restoring a multi-volume VSAM cluster, the cluster is not usable until all pieces of the<br />
cluster have been restored from all volumes where it resided. If not all the pieces have<br />
been restored, the cluster is cataloged as non-VSAM with “####Vx” as the first volser. If<br />
possible, determine which pieces were not restored and restore them. But if you want to<br />
delete the partially restored cluster and start over, you must perform these steps:<br />
Delete the non-VSAM catalog entry with:<br />
//DELNVSM EXEC PGM=IDCAMS<br />
//SYSPRINT DD SYSOUT=*<br />
//SYSIN DD *<br />
DELETE clustername NONVSAM NOSCRATCH<br />
/*<br />
Delete each data and index component of the cluster from each disk where it was restored with:<br />
//DELVVR EXEC PGM=IDCAMS<br />
//SYSPRINT DD SYSOUT=*<br />
//DD1 DD UNIT=SYSALLDA,VOL=SER=volser,DISP=OLD<br />
//SYSIN DD *<br />
DELETE componentname VVR FILE(DD1) CAT(catalogname)<br />
/*<br />
More details on this are found in Section 80.13 “VSAM Special Considerations”.<br />
<strong>FDR</strong>158 DATA SET ENQ FAILED DSN=dsname<br />
DATA SET ENQ FAILED BUT HFS QUIESCED DSN=dsname<br />
DATA SET ENQ FAILED BUT HFS QUIESCE FILE NOT KNOWN TO SYSTEM<br />
DATA SET ENQ FAILED DSN=dsname hfserror<br />
Reason: The data set enqueue option (DSNENQ=) was in effect. This data set could not be<br />
enqueued because some other job or user currently has the data set enqueued under<br />
the SYSDSN resource.<br />
For HFS and zFS data sets, if HFS=QUIESCE or ZFS=QUIESCE was specified and the<br />
enqueue is not successful, <strong>FDR</strong> tries to do a HFS or zFS quiesce function, to prevent<br />
access to the file system in the HFS and zFS data set during the backup. If that is<br />
successful the second form of the <strong>FDR</strong>158 message is displayed and the data set is<br />
processed normally; this message does not indicate an error.<br />
If the HFS or zFS file was not known to the system where <strong>FDR</strong> was running, the third form of the<br />
<strong>FDR</strong>158 message is printed, this also does not indicate an error. However, if the HFS or zFS file<br />
was mounted on another system, it is not quiesced and the backup may be corrupted.<br />
However, HFS and zFS errors cause the fourth form of the <strong>FDR</strong>158 message to be<br />
printed with “hfserror”:<br />
AND HFS QUIESCE FAILED cccc-rrrrrrrr – The quiesce function failed with return<br />
code “cccc” and reason code “rrrrrrrr” in hex. It may be that the HFS or zFS<br />
data set was busy for more than 5 minutes. A reason code ending in 00FC<br />
indicates that the user id of the <strong>FDR</strong> job was not authorized to use UNIX<br />
System Services (USS) (does not have a UID assigned); a UID is required.<br />
AND HFS CURRENTLY QUIESCED TO ANOTHER JOB – The quiesce function<br />
failed because another job or user has already quiesced the HFS or zFS<br />
data set. Another backup of the HFS or zFS data set may be in progress.<br />
CHAPTER 100 – PAGE 100-39 –