Filter
Top Products
98 DB2 Manager User Guide
StorageTek Proprietary
Print reports
The row restore utility will write a number of print reports to the SYSPRINT
dataset during execution. These consist of:
• Parameter specification and validation report. This will contain a list
of SYSIN parameters specified (or defaulted) for execution of the utility,
and a validation error report if errors are detected in parameter
specification. It will also specify the SQL row restore selection statement
coded in the SQLIN file.
• Execution report. Any errors or warning conditions encountered during
execution of the utility will be identified in this report.
• Summary processing report. At end of processing, the utility will write
the summary processing report which will identify the total number of
table rows processed, and the total number restored, up to the last
successful commit point (for runs which do not terminate successfully) or
up to end of processing (for successful runs).
Condition codes
The row restore utility will set a condition code on completion. This code may
take the following values:
0 - the utility has been executed successfully.
4 - a warning condition has been encountered during processing
of the utility. A warning message will have been written to the
SYSPRINT dataset. The utility has been executed
successfully.
8 - an error condition has been encountered during processing of
the utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has continued.
12 - a serious error has been encountered during processing of the
utility. An error message will have been written to the
SYSPRINT dataset. Execution of the utility has been
terminated.
Utility failure and restart considerations
If the row restore utility fails to complete successfully (return code greater
than 8), consult the error report in the SYSPRINT dataset to identify the
cause of the problem. Refer to chapter 7 for a description of the message(s)
appearing in the error report. All rows successfully processed prior to the
last successful commit point before failure will have been successfully
restored from Archive Manager to DB2, and any access requests for those
objects will be satisfied via DB2 only.
After correcting the error, the utility may be rerun normally. The utility will
automatically restart processing from the last successful commit point during