Filter
Top Products
DB2 Manager User Guide 121
StorageTek Proprietary
Explanation: The column name identified in the message has been specified as a
key field in the SQLIN file, but the column does not exist in the DB2
table. Execution of the utility is terminated with condition code 12.
Action: Check that the names of the columns which uniquely index each row
in the table have been specified correctly in the SQLIN file, and re-
submit the job.
OTD10010 SQL Error during execution of xxxxxxxx command SQLCODE = xxxx
Explanation: An error has been received executing the SQL command identified in
the message. Processing of the utility is terminated with a condition
code 12. All DB2 and Archive Manager updates performed by the
utility will be rolled-back to the last commit point. The following SQL
commands may appear in this message: DESCRIBE, PREPARE,
DECLARE, SET, EXECUTE, OPEN, FETCH, CLOSE, COMMIT. The
message will be followed by a line containing parameters from the
appropriate SQL error message.
Action: Refer to the DB2 Messages and Codes manual for a description of
the SQL error code displayed in the message. Take the appropriate
corrective action and re-submit the job, with SYSIN parameter
“RESTART=YES” specified.
OTD10011 Return code X'xx’ retrieving Name/Token pair
Explanation: An error has occurred retrieving an OS/390 name/token pair. ‘xx’
gives the hexadecimal reason code received from the retrieve
request. Execution of the utility is terminated with condition code 12.
Action: Refer to IBM documentation on the IEANTRT callable service for a
description of the error code. Take the appropriate corrective action
and re-submit the job. If no obvious cause for the error can be
identified, contact your local STK support representative.
OTD10012 Error locating ODCT
Explanation: The utility has been unable to locate the DB2 Manager control region
communications table (ODCT) in ECSA storage. Execution of the
utility is terminated with condition code 12.
Action: To resolve this error, terminate and re-start the DB2 Manager control
region, then re-submit the job. If the error persists, contact your local
STK support representative.