If an error message occurs at either an application server (AS) or an application requester (AR), the server message is logged on the job log to indicate the reason for the failure.
A server message exists for each SQLCODE returned from an SQL statement supported by the DB2 Universal Database™ for iSeries™ program. The message is made available in precompiler listings, on Interactive SQL, or in the job log when running in the debug mode. However, when you are working with an AS that is not an iSeries server, there might not be a specific message for every error condition in the following cases:
For example, the special register CURRENT SQLID is not supported by DB2® UDB for iSeries, so SQLCODE -411 (SQLSTATE 56040) CURRENT SQLID cannot be used in a statement that references remote objects does not exist.
DB2 UDB for iSeries will never have SQLCODE -925 (SQLSTATE 56021), SQL commit or rollback is invalid in an IMS™ or CICS® environment.
For SQLCODEs that do not have corresponding messages, a generic message is returned that identifies the unrecognized SQLCODE, SQLSTATE, and tokens, along with the relational database name of the AS which generated the message. To determine the specific condition and how to interpret the tokens, consult the product documentation corresponding to the particular release of the connected AS.
Messages in the ranges CPx3E00 through CPx3EFF and CPI9100 through CPI91FF are used for distributed relational database server messages. The following list is not inclusive, but shows more common server messages you might see in a distributed database job log on an iSeries server.
| MSG ID | Description |
|---|---|
| CPA3E01 | Attempt to delete *LOCAL RDB directory entry |
| CPC3EC5 | Some parameters for RDB directory entry ignored |
| CPD3E30 | Conflicting remote network ID specified |
| CPD3E35 | Structure of remote location name not valid for ... |
| CPD3E36 | Port identification is not valid |
| CPD3E38 | Type conflict for remote location |
| CPD3E39 | Value &3 for parameter &2 not allowed |
| CPD3E3B | Error occurred retrieving server authorization information for ... |
| CPD3ECA | RDB directory operation may not have completed |
| CPD3E01 | DBCS or MBCS CCSID not supported. |
| CPD3E03 | Local RDB name not in RDB directory |
| CPD3E05 | DDM conversation path not found |
| CPD3E31 | DDM TCP/IP server is not active |
| CPD3E32 | Error occurred ending DDM TCP/IP server |
| CPD3E33 | DDM TCP/IP server error occurred with reason code ... |
| CPD3E34 | DDM TCP/IP server communications error occurred |
| CPD3E37 | DDM TCP/IP get host by name failure |
| CPF3E30 | Errors occurred starting DDM TCP/IP server |
| CPF3E31 | Unable to start DDM TCP/IP server |
| CPF3EC6 | Change DDM TCP/IP attributes failed |
| CPF3EC9 | Scope message for interrupt RDB |
| CPF3E0A | Resource limits error |
| CPF3E0B | Query not open |
| CPF3E0C | FDOCA LID limit reached |
| CPF3E0D | Interrupt not supported |
| CPF3E01 | DDM parameter value not supported |
| CPF3E02 | AR cannot support operations |
| CPF3E04 | SBCS CCSID not supported |
| CPF3E05 | Package binding not active |
| CPF3E06 | RDB not found |
| CPF3E07 | Package binding process active |
| CPF3E08 | Open query failure |
| CPF3E09 | Begin bind error |
| CPF3E10 | AS does not support DBCS or MC |
| CPF3E12 | Commit/rollback HOLD not supported |
| CPF3E13 | Commitment control operation failed |
| CPF3E14 | End RDB request failed |
| CPF3E16 | Not authorized to RDB |
| CPF3E17 | End RDB request is in progress |
| CPF3E18 | COMMIT/ROLLBACK with SQLCA |
| CPF3E19 | Commitment control operation failed |
| CPF3E20 | DDM conversation path not found |
| CPF3E21 | RDB interrupt fails |
| CPF3E22 | Commit resulted in a rollback at the application server |
| CPF3E23 | DDM data stream violates conversation capabilities |
| CPF3E30 | Errors occurred starting DDM TCP/IP server |
| CPF3E32 | Server error occurred processing client request |
| CPF3E80 | Data stream syntax error |
| CPF3E81 | Invalid FDOCA descriptor |
| CPF3E82 | ACCRDB sent twice |
| CPF3E83 | Data mismatch error |
| CPF3E84 | DDM conversational protocol error |
| CPF3E85 | RDB not accessed |
| CPF3E86 | Unexpected condition |
| CPF3E87 | Permanent agent error |
| CPF3E88 | Query already open |
| CPF3E89 | Query not open |
| CPF3E99 | End RDB request has occurred |
| CPI9150 | DDM job started |
| CPI9152 | Target DDM job started by application requester (AR) |
| CPI9160 | DDM connection started over TCP/IP |
| CPI9161 | DDM TCP/IP connection ended |
| CPI9162 | Target job assigned to handle DDM connection started |
| CPI9190 | Authorization failure on distributed database |
| CPI3E01 | Local RDB accessed successfully |
| CPI3E02 | Local RDB disconnected successfully |
| CPI3E04 | Connection to relational database &1; ended |
| CPI3E30 | DDM TCP/IP server already active |
| CPI3E31 | DDM TCP/IP server does not support security mechanism |
| CPI3E32 | DDM server successfully started |
| CPI3E33 | DDM server successfully ended |
| CPI3E34 | DDM job xxxx servicing user yyy on mm/dd/yy at hh:mm:ss (This can be suppressed with QRWOPTIONS) |
| CPI3E35 | No DDM server prestart job entry |
| CPI3E36 | Connection to relational database xxxx ended |
| SQ30082 | A connection attempt failed with reason code... |
| SQL7992 | Connect completed over TCP/IP |
| SQL7993 | Already connected |