Message Reference

APPC

Below is a list of CPI-C function return codes which the user may encounter most frequently. It is NOT a complete list of return codes. The number in parentheses indicates the defined number corresponding to the return code.

• CM_ALLOCATE_FAILURE_NO_RETRY (1): Allocation failed because of a non-temporary condition. For example, the session cannot be activated due to a system definition error or session-activation protocol error. This return code is also returned when the session is deactivated because of a session protocol error before the conversation can be allocated.
• CM_ALLOCATE_FAILURE_RETRY (2): Allocation failed because of a temporary condition. For example, the session cannot be activated due to a temporary lack of resources at the local system or remote system.
• CM_CONVERSATION_TYPE_MISMATCH (3): Allocation failed because the remote program does not support the conversation type in the allocation request. This is likely a problem with the TP at the server. Ensure that the TP at the server is configured to support a conversation type of basic.
• CM_TPN_NOT_RECOGNIZED (9): This error occurs when the allocate request is sent to the remote system. It indicates that the remote system does not recognize the transaction program name specified in the request. If you are not using global directory services, ensure that the TP name specified in the CPI-C Side Information profile at the client, matches the TP name specified at the server. If you are using global directory services, request your database administrator's help to ensure that the TP name specified in the global directory entry matches the TP name specified at the server.
• CM_TP_NOT_AVAILABLE_NO_RETRY (10): This error occurs when the allocate request is sent to the remote system. It indicates that the remote LU recognizes the TP name sent, but cannot start the program. Also check that the userid specified in the TPN profile at the server is valid.
• CM_TP_NOT_AVAILABLE_RETRY (11): This error occurs when the allocate request is sent to the remote system. It indicates that the remote LU recognizes the TP name sent, but for some reason which may be temporary, it cannot start the program. Ensure that the database manager and APPC protocol support at the server have been started successfully.
• CM_DEALLOCATED_ABEND (17): This error occurs when the remote program deallocates the conversation. This can occur if the remote program has abnormally terminated, or has encountered a fatal error condition. If you are trying to connect to DB2 for AIX, check that the database manager and APPC protocol support at the server have been started successfully. For an AIX server, this error could also be caused by one of the following:
  • The database agent at the server was forced off by the system administrator.
  • A database agent could not be started at the server because the maxagents database manager configuration parameter has been exceeded. Check the First Failure Service Log (DB2DIAG.LOG) at the server to see if an error message has been logged.
  • The database agent at the server was terminated due to an abnormal termination of a key database manager process.
• CM_PRODUCT_SPECIFIC_ERROR (20): A product-specific error has been detected, and a description of the error has been stored in the product's system error log. Check that the local APPC subsystem has been started successfully. For Communication Server for AIX, to get more information about a product-specific error, it is necessary to check the value of the global variable errno. See the section below for more information on possible errnos that can be returned. Communication Server for OS/2 records errors in the OS/2 system error log.
• CM_RESOURCE_FAILURE_NO_RETRY (26): This error occurs when the conversation terminates prematurely (on either the remote or local end) from an error related to resources (such as sessions or links). For an OS/2 server, this error could also be caused by one of the following:
  • The database agent at the server was forced off by the system administrator.
  • A database agent could not be started at the server because the maxagents database manager configuration parameter has been exceeded. Check the First Failure Service Log (DB2DIAG.LOG) at the server to see if an error message has been logged.
  • The database agent at the server was terminated due to an abnormal termination of a key database manager process.
• CM_RESOURCE_FAILURE_RETRY (27): This error occurs when the conversation terminates prematurely (on either the remote or local end) for about the same reason as the NO_RETRY condition described above. The only difference is that the error may not be permanent.

For the most part, CPI Communications return codes are enough to deduce the cause of the error. But when CM_PRODUCT_SPECIFIC_ERROR is returned, additional information is provided.

For Communication Server for AIX, the errno provides additional information. Below is a list of some of the more common errnos. It is NOT a complete list. Errnos numbered 101 and higher can be found in the file /usr/include/luxsna.h, which contains the Communication Server for AIX specific errnos. Most of these errnos are translated to CPI-C return codes. Lower-numbered errnos are related to AIX problems and can be found in the file /usr/include/sys/errno.h. The errno number itself is in parentheses.

• EBADF (9): This is a "bad file descriptor" error. If this error occurs when trying to connect to the database, it usually means that the SNA subsystem at the server has not been started, or that there is some problem with the SNA configuration profiles. Check that the SNA subsystem at the server has been started. Check that the link station to the server node can be activated.
• EACCESS (13): This is a "permission denied" error. If this error occurs when trying to connect to the database, it usually means that there is some problem with the SNA configuration profiles.

On HP-UX, for SNAPlus2, please refer to the /usr/include/sys/errno.h file for a description of the error.

For OS/2, when CPI Communications returns CM_PRODUCT_SPECIFIC_ERROR, an entry is created in the error log. Information in the error log entry identifies CPIC as the originator. If Communications Server/2 (CS/2) is installed, CS/2 records the error in the OS/2 system error log. Refer to the problem determination guide for the specific product, for a complete description of the error, and the recommended action to take.

For more information on CPI Communications errors, refer to Systems Application Architecture Common Programming Interface Communications Reference.