| Description | A cd is an invalid descriptor. The descriptor returned when an API was used is invalid. |
| Action | Check the cd allocated through a tpcall() or re-execute a tpstart(). |
| Description | A requested service was blocked. Blocking occurs in the state that a TPNOBLOCK is set. If this error occurs when a tpgetrply or a tpgetunsol is invoked as a NonBlock Mode, socket data does not exist at the point of calling a function. In this case, a logic needs to be added that ignores the error and re-attempts the service after sleeping for a specific time limit. |
| Action | Re-request or re-attempt the service after the blocking is released. |
| Description | System resources or the resources provided by Tmax are limited. |
| Action | Allocate and use the resources provided by the operating systems in Tmax, as other resources are not sufficient. |
| Description | There is no service listed in a service table, or a Tmax engine cannot recognize a service. |
| Action | If a configuration file is modified, create a new service table with a gst and compile it together at the same time when compiling a server application program. |
| Description | An operating system error occurred. |
| Action | Check the general environment including the operating systems, whether there has been any change in the network or in the existing operating environment. |
| Description | An API was called in an inappropriate situation. |
| Action | The API call for each step was used incorrectly. Thus, first set up a buffer and then request a service, or follow the prescribed steps of sending and receiving at the time of an interactive communication. |
| Description | An error occured in a server process while a service was performed. |
| Action | Check the server processor. |
| Description | An error occurred at the application program level while a service was performed. A service routine that sends a reply to a service request had an error in an application program. |
| Action | Check the application. |
| Description | An error was detected in a Tmax system. |
| Action | Check several matters including general normal errors. Check the general environment including a network failure and server processor failure. |
| Description | A specified time is over because a blocking condition existed. Another reason may have caused this error. |
| Action | Check the reasons for the timeout at the application program level. If the timeout is normal, adjust the timeout time. It is possible to adjust the timeout time in the application program. The BLOCKTIME in the configuration file is applied as a default. |
| Description | This service does not support a transaction. |
| Action | Set a flag to a TPNOTRAN, at the time of a Tpcall. |
| Description | A signal was received in a state where a TPSIGRSTRT was not set. For a DDR using a COUSIN section, this error occurs when a CLH does not know to which node it has to request a service. |
| Description | An entered buffer type is unknown. For a DDR using a COUSIN section, this error occurs when a CLH does not know to which node it has to request a service. |
| Action | Check the data value. When a FIELD buffer is used, check whether a corresponding field key is defined and when a STRUCT buffer is used, check whether a structure is declared. |
| Description | An entered buffer type is unknown to a caller. The type and subtype of data was not matched with an entered buffer type. |
| Action | Check the data value. |
| Description | An error occurred in an interactive mode. An event is generated and data was not transferred. An event was returned to a revent value. |
| Action | Check the revent value. |
| Description | Data matching a condition to dequeue was unable to be found. |
| Action | Check that the condition is correct. |
| Description | A service is not ready, or a server processor is started up but the service was not activated. For example, a tpcall() was invoked in a state that a service is in a NRDY state. |
| Action | Check the service status with a ‘st –s’ in a ‘tmadmin’. If a NRDY is displayed, it means that a service was not started normally. Check the server processor again and re-start it. Perform a tpstart again. |
| Description | Check whether a user is allowed when a security setting is used. |
| Action | Check user privileges. |
| Description | A requested service reached a Max Queue. |
| Action | Adjust the Max Queue value in a Tmax configuration file or dynamically with the tmadmin tool. |
| Description | A manager purged a queue at his or her discretion. The manager purged a requested service that was waiting in a queue . |
| Description | Tmax is not yet started up, or it is impossible to access it. |
| Action | Check whether Tmax is successfully started up, and perform a tpstart. |
| Description | A server is down due to a service invoked through a tpcall(). |
| Action | Check whether a server processor is normally operating. It is a problem in the application program logic, so a program terminates abnormally during execution. Check the application program. |
| Description | A PRESVC error registered in a RQ section. This error is no longer used. |
| Description | When rolling-down occurs, if a tpgetrply() is invoked for the requests enqueued in an existing server queue, a TPERDOWN error is specified and the data sent through a tpacall is saved in the receiving buffer of a tpgetrply. This error occurs for a tpacall invoked after a rolling down occurs. |
| Action | Refer to the release note. |
| Description | When a tpgetrply is called in a situation where no more requests are enqueued in a server queue, this error is generated. |
| Action | Refer to the release note. |
| Description | The number of users reached a Max User count. The number of users who can access the system concurrently is limited. |
| Action | Take proper action after checking the Max User count with a ci (Client Information) in a tmadmin. |