General Questions: Error Handling, etc.
Finally, we will go through some general questions about how FATSCOPY handles errors and sets some limits. If you’ve been through this before and know that you just want to keep the FATSCOPY default values, then click here to skip ahead.
Q: When no data sets match the selection criteria for a SELECT statements, FATSCOPY will usually issue a U0300 abend as an alert. Do you want to suppress this abend?
Yes1– Add SELTERR=NO to your COPY or SIM statement. You will still get an error message notifying you that no data sets were selected. (You might use this when you expect that certain data sets might not actually exist.)
Q: Do you want to to produce an abend dump for FATSCOPY errors which normally do not produce a dump?
Yes1 – Add DUMP=YES to your COPY or SIM statement.
Q: For many serious errors, FATSCOPY will produce a U0888 abend. Do you want FATSCOPY to terminate with a return code of 12 instead?
Yes1 – Add RETCODE to your COPY or SIM statement.
Q: Did you use SELECT ALLDSN together with CAT=ONLY?
No – click here to skip ahead.
Remember that with CAT=ONLY the output is cataloged only if the catalog entry for the input file name exactly matches the input file actually copied (volser and file sequence). If it does not match, the file is copied but the output is not cataloged. In this case FATSCOPY issues an error message and can set a return code value of 0, 4, or 8. By default FATSCOPY will set a return code of 41 when this mismatch occurs.
Q: Do you want to use a different return code when a mismatch is found?
Yes1– Add NOTCATRC=n to your COPY statement, where n is 0, 4, or 8.
You should now have a complete FATSCOPY Sim or Copy job which you can submit as a batch job.