Error Codes and Actions
2 : TPEBADDESC
Description |
The cd is an invalid descriptor. The descriptor returned by the function is invalid. |
Action |
Check the cd allocated by tpcall() or execute tpstart() again. |
3 : TPEBLOCK
Description |
The requested service is blocked. A blocking condition occurred while TPNOBLOCK was set. If this error occurs when invoking tpgetrply or tpgetunsol in non-block mode, the socket contained no data at the time of the call. In this case, the application should add logic to wait (sleep) for a certain amount of time and retry, ignoring the error. |
Action |
Resend the service request, or retry after the blocking condition has been resolved. |
5 : TPELIMIT
Description |
System resources or the resources provided by Tmax are insufficient. |
Action |
Allocate and use the resources provided by the operating systems. |
6 : TPENOENT
Description |
No services exist in the service table, or the Tmax engine cannot recognize services. |
Action |
If the configuration file has been modified, create a new service table by executing gst, and compile the file together with the server application. |
7 : TPEOS
Description |
An operating system error occurred. |
Action |
Check the operating system, network, and related system environments for any recent changes or issues. |
9 : TPEPROTO
Description |
The function was called in an invalid state. |
Action |
The API calls were used in the wrong order. Ensure a buffer is set up before requesting a service, and follow the prescribed send/receive sequence during interactive communication. |
10 : TPESVCERR
Description |
A server process error occurred during service execution. |
Action |
Check the server process. |
11 : TPESVCFAIL
Description |
An application error occurred during service execution. This happens while the service routine sending the response to the request is running. |
Action |
Check the application. |
12 : TPESYSTEM
Description |
An anomaly is detected in the Tmax system. |
Action |
Perform a system-wide check, including the network, server processes, and other system environments, as this error covers all types of system anomalies. |
13 : TPETIME
Description |
A blocking condition occurred, or a time limit expired. |
Action |
Identify the cause of the timeout in the application level. If no issue is found, adjust the timeout period at the application level. By default, the BLOCKTIME value in the configuration file is used. |
14 : TPETRAN
Description |
The requested service does not support transactions. |
Action |
Set the flag to TPNOTRAN when invoking tpcall. |
15 : TPGOTSIG
Description |
A signal was received while TPSIGRSTRT was not set. For a DDR configured with the COUSIN setting, this may also occur if the CLH cannot determine which node should handle the service request. |
17 : TPEITYPE
Description |
The type of the input buffer is unknown. For a DDR configured with the COUSIN setting, this may also occur if the CLH cannot determine which node should handle the service request. |
Action |
Check the data value. If a field-key buffer was used, verify that the field key is defined. If a structure buffer was used, ensure the structure has been declared. |
18 : TPEOTYPE
Description |
The type of the input buffer is unknown to the caller. This happens when the type and subtype of data do not match those of the buffer. |
Action |
Check the data value. |
22 : TPEEVENT
Description |
An error occurred in an interactive communication. An event was generated without data. The event is returned in the revent value. |
Action |
Check the event (revent) value. |
23 : TPEMATCH
Description |
The data matching the specified conditions could not be found. |
Action |
Ensure that the conditions are specified correctly. |
24 : TPENOREADY
Description |
The service is not ready or has not been activated after being started. For example, the service may be in the NRDY state when tpcall() is executed. |
Action |
Check the service status using the 'st –s' option in tmadmin. If the service is displayed as NRDY, it was not started properly. Check the server process, restart it if necessary, and reissue tpstart(). |
25 : TPESECURITY
Description |
A non-permitted user attempted to access the system while security configuration is enabled. |
Action |
Verify the user’s permissions. |
26 : TPEQFULL
Description |
The service requests have reached the maximum queue limit. |
Action |
Adjust the maximum queue value in the Tmax configuration file or dynamically using the tmadmin tool. |
27 : TPEQPURGE
Description |
The queue was forcibly purged by the administrator. This occurs when a service request is removed from the queue while waiting to be processed. |
28 : TPECLOSE
Description |
Tmax was not started or inaccessible. |
Action |
Ensure that Tmax is properly started and reissue tpstart(). |
29 : TPESVRDOWN
Description |
The server was shut down while executing a service via tpcall(). |
Action |
Ensure the server process is running properly. Also, check the application logic, as errors in the program can cause an abnormal shutdown. |
30 : TPEPRESVC
Description |
An error occurred related to the PRESVC registered in the RQ section. This error does not occur under current conditions, as PRESVC is not currently applied. |
31 : TPERDOWN
Description |
A roll-down condition occurred while tpgetrply was executed for requests queued on the server. Data sent during tpacall is reloaded into the tpgetrply reception buffer. This error also applies to any tpacall function called after a roll-down occurs. |
Action |
Refer to the release notes for details. |
32 : TPERDCLOSE
Description |
The tpgetrply function was called when no requests remained in the server queue. |
Action |
Refer to the release notes for details. |
33 : TPEMAXNO
Description |
The number of concurrent users has reached the maximum limit. |
Action |
Check the client Information (ci) using tmadmin. |