StorageTek 312564001 User Manual
DB2 Manager User Guide
87
StorageTek
Proprietary
Condition codes
The table migration utility will set a condition code on completion. This code
may take the following values:
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.
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.
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. 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 table migration 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
migrated from DB2 to Archive Manager, and any access requests for those
objects will be satisfied by DB2 Manager from the appropriate Archive
Manager database.
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
migrated from DB2 to Archive Manager, and any access requests for those
objects will be satisfied by DB2 Manager from the appropriate Archive
Manager database.
After correcting the error, the utility may be rerun with an execution parameter
of “RESTART=YES” specified. The utility will automatically restart
processing from the last successful commit point during the failed execution.
No other special actions need to be taken prior to re-starting the failed table
migration job.
of “RESTART=YES” specified. The utility will automatically restart
processing from the last successful commit point during the failed execution.
No other special actions need to be taken prior to re-starting the failed table
migration job.
Operator commands
Execution of the utility may be terminated at any point by entering the
following command through the system console:
following command through the system console:
(STO)P jobname
where ‘jobname’ is the name of the job used to execute the object
management procedure.
management procedure.
The utility will acknowledge receipt of this command via message OTD10023,
and perform normal termination processing. All database updates performed
by the utility prior to termination will be committed, and the utility will
terminate with a condition code of 4.
and perform normal termination processing. All database updates performed
by the utility prior to termination will be committed, and the utility will
terminate with a condition code of 4.