DB2 Manager User Guide 167
StorageTek Proprietary
communicated back to the calling program via generation of an SQL –652
error. The two bytes at character positions 6 and 7 in field SQLERRD in the
SQL communication area (SQLCA) at the time of the error will contain a
reason code giving additional information about the error condition.
Messages giving additional error information may also be displayed in the
system log by the DB2 Manager control region.
This section lists reason codes set by DB2 Manager in the SQLCA. Note that
reason codes in this list are displayed in hexadecimal format.
Reason code
(hex)
Explanation
01xx Storage obtain request by the DB2 Manager row edit processor failed.
‘xx’ gives the hexadecimal return code received from the STORAGE
macro request.
Action: Refer to IBM documentation on the STORAGE macro for a
description of the error. Take the appropriate corrective
action before continuing with DB2 Manager processing.
02xx An invalid row edit request code has been received from DB2. ‘xx’
gives the invalid request code.
Action: This indicates either an internal DB2 Manager error or a
possible DB2 error. Report the problem to your local DB2
Manager support representative
03xx Error received from TCBTOKEN macro request. ‘xx’ gives the
hexadecimal return code received from the macro call.
Action: Refer to IBM documentation on the TCBTOKEN macro for
a description of the error. Take the appropriate corrective
action before continuing with DB2 Manager processing.
0500 There is no free request element available for processing the request.
Action: DB2 Manager allows up to 1024 migrated row access
requests to be processed concurrently. If this limit is
exceeded, the error documented here will be received. In
this case, the request should be retried at a less busy time.
If the number of concurrent requests in the system is less
than this figure, report the problem to your local DB2
Manager support representative.
06xx Error received from ALESERV macro request. ‘xx’ gives the
hexadecimal return code received from the macro call.
Action: Refer to IBM documentation on the ALESERV macro for a
description of the error. Take the appropriate corrective
action before continuing with DB2 Manager processing.
09xx Error received from LOCASCB macro request. ‘xx’ gives the
hexadecimal return code received from the macro call.