and
OTD130xx – pre-fetch utility messages
Messages from the DB2 Manager
OTD13000 Batch Pre-fetch Utility ended with completion code xx
Explanation: The DB2 Manager
completion code. This can 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.
Action: None. This is an informational message.
OTD13001 OPEN failed for xxxxxxxx dataset
Explanation: An attempt to open a
Action: Consult other available system messages for further information on the cause of the open failure. Take the appropriate corrective action and
OTD13002 The operand for keyword xxxxxxxx in exec parameters is too long
Explanation: The operand specified for the SYSIN parameter keyword ‘xxxxxxxx’ identified in the message is longer than the maximum value permitted. The character string ‘xxxxxxxx’ can take one of the following values: INDEXONLY, DB2SSID, PLAN, BATCH, PRINT. Execution of the utility will terminate with condition code 12.
Action: Refer to page 102 for a description of SYSIN parameter formats for the row restore utility. Correct the parameter error and
DB2 Manager User Guide | 129 |
StorageTek Proprietary |
|