ECI返回碼
| code | info | desc |
|---|---|---|
| 0 | ECI_NO_ERROR | No error. |
| -1 | ECI_ERR_INVALID_DATA_LENGTH | Bad data length. This might be because the protocol used to communicate with CICS is unable to send or receive the specified COMMAREA size. |
| -2 | ECI_ERR_INVALID_EXTEND_MODE | The eci_extend_mode field is not valid. |
| -3 | ECI_ERR_NO_CICS | Communication with the target CICS server could not be established. |
| -4 | ECI_ERR_CICS_DIED | Communication with the target CICS server was interrupted during the request. |
| -5 | ECI_ERR_REQUEST_TIMEOUT | The timeout interval expired before the request was sent to CICS, or the value supplied for timeout is negative. |
| -6 | ECI_ERR_RESPONSE_TIMEOUT | The ECI call timed out while waiting for a response. |
| -7 | ECI_ERR_TRANSACTION_ABEND | The CICS transaction abended. The abend code is available in the eci_abend_code field. |
| -8 | ECI_ERR_EXEC_LUW_TOKEN | The value in eci_luw_token is incorrect. There is no active unit of work associated with the specified token. |
| -9 | ECI_ERR_SYSTEM_ERROR | An internal system error has occurred. If the problem persists, collect application and Gateway daemon trace and contact your IBM service representative. |
| -10 | ECI_ERR_NULL_WIN_HANDLE | |
| -12 | ECI_ERR_NULL_MESSAGE_ID | |
| -13 | ECI_ERR_THREAD_CREATE_ERROR | |
| -14 | ECI_ERR_INVALID_CALL_TYPE | The eci_call_type field is not valid. This can occur for the following reasons: The eci_call_type field is not set to a valid call type value. The active CICS request exit rejected the request. The request includes a channel and the destination CICS server is not a defined IPIC server. |
| -15 | ECI_ERR_ALREADY_ACTIVE | An attempt was made to continue an existing logical unit of work, but there was an outstanding asynchronous call for the same logical unit of work. |
| -16 | ECI_ERR_RESOURCE_SHORTAGE | There are insufficient resources to communicate with the target CICS server; details might be available in the CICS TG error log files. |
| -17 | ECI_ERR_NO_SESSIONS | There are insufficient communication resources to communicate with the target CICS server. |
| -18 | ECI_ERR_NULL_SEM_HANDLE | |
| -19 | ECI_ERR_INVALID_DATA_AREA | The combination of eci_commarea and eci_commarea_length values is not valid. If eci_commarea is NULL, eci_commarea_length must be zero. If eci_commarea is not NULL, eci_commarea_length must not be zero. |
| -21 | ECI_ERR_INVALID_VERSION | The eci_version field was not set to ECI_VERSION_2 or ECI_VERSION_2A. |
| -22 | ECI_ERR_UNKNOWN_SERVER | The target CICS server is unknown to the Gateway daemon. |
| -23 | ECI_ERR_CALL_FROM_CALLBACK | |
| -25 | ECI_ERR_MORE_SYSTEMS | |
| -26 | ECI_ERR_NO_SYSTEMS | |
| -27 | ECI_ERR_SECURITY_ERROR | An invalid combination of user ID and password or password phrase was specified. |
| -28 | ECI_ERR_MAX_SYSTEMS | The CICS TG has reached its limit on the maximum number of CICS servers. |
| -29 | ECI_ERR_MAX_SESSIONS | There are insufficient communication resources to complete the request. |
| -30 | ECI_ERR_ROLLEDBACK | An attempt was made to commit a logical unit of work, but the CICS server was unable to commit the changes, and backed them out instead. |
| -32 | ECI_ERR_NO_REPLY | No reply. This can occur for the following reasons: The eci_call_type field is set to ECI_GET_REPLY and there are no replies outstanding. The eci_call_type field is set to ECI_GET_SPECIFIC_REPLY and there is no reply for the specified message qualifier. |
| -33 | ECI_ERR_INVALID_MSG_QUAL | The message qualifier is not in use. |
常見錯誤及解決方式
-3 ECI_ERR_NO_CICS 連接不可用
解決方式：重啟客戶端
-4 ECI_ERR_CICS_DIED 連接中斷
解決方式：重啟客戶端
-6 ECI_ERR_RESPONSE_TIMEOUT 應答超時
解決方式：排查服務端超時原因
-7 ECI_ERR_TRANSACTION_ABEND 事務異常終止
解決方式：檢查PD是否存在库继、檢查程序(目錄)權(quán)限是己、排查后臺程序BUG
