Module Error Messages
This chapter describes errors that may by generated by each module.
1. ADM Module (ADM2001 ~ )
ADM2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
ADM2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
ADM2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
ADM2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
ADM2045 TMM register error
Type |
ERROR |
Description |
Could not register the tmadmin process to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
ADM2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The tmadmin version does not match that of TMM. |
Action |
Reinstall the Tmax engine, and then recompile the configuration file and server program. |
ADM2048 Engine type mismatch (type): 'a' option must be used
Type |
ERROR |
Description |
The configuration file used for cfgadd was not generated with cfl -a. |
Action |
Generate the configuration file used for cfgadd by generating an additional configuration file with cfl -a. |
ADM3001 RACD connection error
Type |
ERROR |
Description |
An error occurred while connecting to a remote RACD. |
Action |
1) Confirm that the RACD was properly started at remote nodes. 2) Confirm that the TMAX_RAC_PORT environment variable is consistent throughout the nodes, and that it matches the RACPORT field of the DOMAIN section in the configuration file. The default value of TMAX_RAC_PORT is 3333. |
ADM3003 request to TMM error
Type |
ERROR |
Description |
Could not send a request message to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. Also verify that the MAX*** value in the DOMAIN section has been updated when performing dynamic updates using cfgadd. |
ADM3004 Time-out during admin requests.
Type |
ERROR |
Description |
A remote did not respond to a request message. |
Action |
1) Check that RACD and tmadmin are operating properly at remote nodes. 2) Check the network status. |
ADM3006 CLH is not started: clhno
Type |
ERROR |
Description |
Could not find an active CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. If the CLH process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
ADM3007 read from local RACD error
Type |
ERROR |
Description |
An error occurred while receiving data from a local RACD. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the RACD process status. |
ADM3008 write to local RACD error.
Type |
ERROR |
Description |
Could not send a message to a local RACD. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the RACD process status. |
ADM3010 register to TMM error.
Type |
FATAL |
Description |
Could not register tmadmin to the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
ADM3011 main tmadmin already started.
Type |
ERROR |
Description |
Another copy of "tmadmin -m" was already executed. |
Action |
1) Only one copy of the master tmadmin can be used at a time. If tmadmin was not yet started, this message will be displayed due to the Operating System’s socket clear delays. 2)Send a HUP signal to the TMM process. |
ADM3012 maximum admin (NUM_MAX_ADM)already started.
Type |
ERROR |
Description |
Could not start another tmadmin. |
Action |
1) There is a pre-configured limit to the number of sub-tmadmin ('tmadmin -s') sessions that can run concurrently. 2) If tmadmin has not already been started, this message may appear due to socket clear delays in the operating system. 3) Send a HUP signal to the TMM process. |
ADM3013 unregister to TMM error.
Type |
ERROR |
Description |
Could not send an unregistered message to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. 3) To unregister all tmadmin processes, send a HUP signal to the TMM process. |
ADM3014 request to remote node error: nodename
Type |
ERROR |
Description |
Could not send a request message to a remote node. |
Action |
1) Check that RACD and tmadmin are operating properly on the remote node. 2) Check the network status. |
ADM3015 remote RACD closed: nodename
Type |
ERROR |
Description |
The communication channel with a remote node was closed. |
Action |
1) Check that RACD and tmadmin are operating properly on the remote node. 2) Check the network status. |
ADM3016 request to CLH error
Type |
ERROR |
Description |
Could not send a request message to a local CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. If the CLH process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
ADM3017 ADM WaitForMultipleObjects error
Type |
ERROR |
Description |
WaitForMultipleObjects failed. |
ADM3018 socketpair error
Type |
ERROR |
Description |
Failed to create a socket pair. |
Action |
Contact the engineer. |
ADM3019 no such name is found : svr(svrname)
Type |
INFO |
Description |
The specified svr name is not found in Tmax. |
Action |
Reset the svr option using the name registered in the configuration name. |
ADM3020 svg (%s) is non-XA
Type |
INFO |
Description |
The specified svg is non-XA. |
ADM3021 resume without suspend
Type |
ERROR |
Description |
The resume operation was executed without a prior suspend. |
ADM3023 line is too long: %d
Type |
ERROR |
Description |
The string output to stdout by admin is too long. |
Action |
Contact the engineer. |
ADM4000 ADM_%s %s command(%s)
Type |
INFO |
Description |
The administrative command either succeeded or failed depending on the input. |
Action |
erify that the command syntax and input parameters are valid. |
2. BOOT Module (BOOT2001 ~ )
BOOT2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
BOOT2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
BOOT2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
BOOT2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
BOOT2045 TMM register error
Type |
ERROR |
Description |
Could not register the tmboot process to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
BOOT2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The tmboot version does not match that of TMM. |
Action |
Reinstall the Tmax engine. |
BOOT2141 License file read error: file_name
Type |
ERROR |
Description |
A license file read error occurred. |
Action |
1) Install the license file to the correct path at: (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
BOOT2142 Corrupt license file: file_name
Type |
ERROR |
Description |
A license file read error occurred. |
Action |
1) Install the license file to the correct path at: (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
BOOT2143 Licensed host not found
Type |
ERROR |
Description |
The host does not have a valid license. |
Action |
Install an updated license file. |
BOOT2144 more than licensed number of CPUs are installed.
Type |
ERROR |
Description |
The number of CPUs exceeds the licensed limit. |
Action |
Install an updated license file. |
BOOT2145 License is expired:
Type |
ERROR |
Description |
The license has expired. |
Action |
Install an updated license file. |
BOOT2146 License check error
Type |
FATAL |
Description |
The license check failed. |
Action |
Contact TmaxSoft to obtain or upgrade the license. |
BOOT2147 License start time has not yet reached :
Type |
ERROR |
Description |
The license start time has not yet been reached. |
Action |
Contact TmaxSoft to obtain or upgrade the license. |
BOOT2148 your license does not support sub_prob_name.
Type |
ERROR |
Description |
There is no valid license. |
Action |
Contact TmaxSoft to obtain or upgrade the license. |
BOOT3001 length of option arg is too long.
Type |
ERROR |
Description |
A parameter exceeded the allowed length. |
Action |
A parameter must not exceed 256 characters. |
BOOT3002 conflict flags are set.
Type |
ERROR |
Description |
An invalid option flag was specified. |
Action |
Run tmboot -h to view the correct command-line options. |
BOOT3003 unrecognized option
Type |
ERROR |
Description |
An invalid option flag was specified. |
Action |
Run tmboot -h to view the correct command-line options. |
BOOT3004 no response from svr_name while booting.
Type |
ERROR |
Description |
The specified server (svr_name) could not start successfully due to an error during the boot process. |
Action |
Resolve the error by reviewing the preceding error messages. |
BOOT3005 Tmax is already running
Type |
ERROR |
Description |
The Tmax engine was started while it was already running. |
BOOT3006 Tmax is not started
Type |
ERROR |
Description |
The application process was started while Tmax was not running. |
Action |
Start the Tmax engine. |
BOOT3007 maxsvr (max_num) over for svr (svr_name)
Type |
ERROR |
Description |
The number of running processes exceeded the value specified in the MAX field of the SERVER section. |
Action |
Increase the MAX field and restart Tmax. |
BOOT3007A maxsvr (%d) is over for svr(%s:%s): nodeno = %d, svri = %d, cur = %d, ksvr = %d
Type |
ERROR |
Description |
The number of running processes exceeded the value specified in the MAX field of the SERVER section. |
BOOT3008 server (svr_name) is not in config
Type |
ERROR |
Description |
The specified server name is not valid. |
Action |
Check that the server name is correctly registered in the configuration file. |
BOOT3008 group (svg_name) is not in config
Type |
ERROR |
Description |
The specified server group name is not valid. |
Action |
Check that the server group name is correctly registered in the configuration file. |
BOOT3010 register to TMM error
Type |
FATAL |
Description |
Could not register the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
BOOT3011 unregister to TMM error
Type |
ERROR |
Description |
Could not send the unregister request message to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. 3) To unregister all tmadmin sessions, send a HUP signal to the TMM process. |
BOOT3013 maxtms is over
Type |
ERROR |
Description |
The number of currently running TMS processes, combined with the MINTMS setting, exceeded the MAXTMS value. |
Action |
Increase the MAXTMS value in the configuration file. |
BOOT3014 maxclh is over
Type |
ERROR |
Description |
The number of currently running CLHs +1 exceeded the MAXCLH value. |
Action |
Increase the MAXCLH value in the configuration file. |
BOOT3015 cas is already running
Type |
ERROR |
Description |
CAS is already running. |
BOOT3016 BOOT cmdline error
Type |
FATAL |
Description |
Failed to write a string to start the process due to an internal error. |
Action |
Contact the engineer. |
BOOT3017 BOOT lpEnv error[%s]
Type |
FATAL |
Description |
GetEnvironmentStrings failed. |
BOOT3018 CreateProcess error[%s]
Type |
ERROR |
Description |
CreateProcess failed. |
BOOT3019 %s not answered
Type |
ERROR |
Description |
No response. |
BOOT3020 svr_name is suspended, resume(or tmdown) it first.
Type |
ERROR |
Description |
A new server was started after a previously suspended server was resumed or shut down with tmdown. |
Action |
Resume or shut down the server with tmdown before starting a new instance. |
BOOT3021 sum of MAXUSER (%d) > licensed maxuser (%d)
Type |
ERROR |
Description |
The number of users exceeded the MAXUSER value specified in the license. |
BOOT3022 option (%s) is not supported
Type |
ERROR |
Description |
The option is not supported. |
BOOT3023 Server(%s) can not start anymore. Please boot more CLH.
Type |
ERROR |
Description |
The system could no longer start the server. |
Action |
Start additional CLHs. |
BOOT3024 all servers in group (%s) reached max
Type |
ERROR |
Description |
All servers in the server group have been started, reaching the MAX setting. |
BOOT3025 tsm is already running
Type |
ERROR |
Description |
'tmboot -e tsm' is already running. |
BOOT3027 The number of ksvr is %d, but it is actually started up to max. [svri = %d, cur = %d, max = %d, ksvr = %d]
Type |
INFO |
Description |
The number of servers to run configured with the -k option (ksvr) has reached the pre-defined MAX limit. |
3. CAS Module (CAS2001 ~ )
CAS2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS2045 TMM register error
Type |
ERROR |
Description |
Could not register the CAS process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CAS2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The CAS version does not match TMM. |
Action |
Reinstall the Tmax engine. |
CAS3001 register to TMM error
Type |
FATAL |
Description |
Could not register the CAS process to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS3002 TMM closed
Type |
ERROR |
Description |
The communication channel with TMM was closed. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. 3) If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
CAS3003 CLH read error
Type |
ERROR |
Description |
Could not receive data from CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. 3) If the CLH process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
CAS3004 CLH write error
Type |
ERROR |
Description |
Could not send data to CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. 3) If the CLH process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
CAS3006 trying to write to CLH is blocked
Type |
ERROR |
Description |
Could not send data to CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. 3) If the CLH process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
CAS3007 register to CLH error
Type |
ERROR |
Description |
Could not register the CAS process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CAS3008 register to CLH error
Type |
FATAL |
Description |
Could not register the CAS process to CLH. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CAS3009 CLH connect error:
Type |
ERROR |
Description |
Could not configure the communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS3010 register to CLH (phase 1) error
Type |
ERROR |
Description |
Could not configure the communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS3011 register to CLH (phase 2) error
Type |
ERROR |
Description |
Could not configure the communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CAS3013 Invalid passwd entry found
Type |
ERROR |
Description |
The password file contains invalid data. |
Action |
1) Check the ${TMAXDIR}/config/passwd file. 2) Run the mkpw command to create a new password file. |
CAS3014 passwd file error
Type |
ERROR |
Description |
Could not find the password file, or the existing password file contains invalid data. |
Action |
1) Check the ${TMAXDIR}/config/passwd file. 2) Run the mkpw command to create a new password file. |
CAS3015 domain security check error : usr_name
Type |
WARNING |
Description |
The client attempted to access with an invalid password. |
Action |
Verify the "OWNER = usr_name" setting of the DOMAIN section in the configuration file. |
CAS3016 user authorization check failed : usr_name
Type |
WARNING |
Description |
The client attempted to access with an invalid password. |
Action |
Verify that the password file contains "usr_name:password". |
CAS3017 failed to request to TMM
Type |
ERROR |
Description |
An error occurred while sending a request message to TMM. |
Action |
Verify whether the files under the ${TMAXDIR}/path directory have been damaged, and then check the Tmax status. |
CAS3018 CLH connection closed
Type |
INFO |
Description |
The connection with CLH was closed. |
Action |
Check whether the process was terminated with tmdown or if CLH was shut down abnormally. |
CAS3019 Invalid acl entry
Type |
ERROR |
Description |
An error occurred while reading an entry in the acl file. |
Action |
Verify whether the ${TMAXDIR}/config/acl file has been damaged. |
CAS3020 acl file error
Type |
ERROR |
Description |
The acl file name is invalid. |
Action |
Verify whether the TMAXDIR setting is incorrect. |
CAS3021 user file error
Type |
ERROR |
Description |
The user file is invalid. |
Action |
Verify whether the TMAXDIR setting is incorrect. |
4. CFL Module (CFL0096 ~ )
CFL0096 shared memory : different owner user_id
Type |
ERROR |
Description |
The user ID does not match the current process user ID. This occurred while four SHM keys were already open. |
Action |
Release the already opened SHM keys or reconfigure the shared memory key values. |
CFL2141 License file read error: file_name
Type |
ERROR |
Description |
Failed to read the license validation file. |
Action |
1) Install the license file in the correct path (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
CFL2142 Corrupt license file: file_name
Type |
ERROR |
Description |
Failed to read the license validation file. |
Action |
1) Install the license file in the correct path (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
CFL2143 Licensed host not found
Type |
ERROR |
Description |
The host does not have a valid license. |
Action |
Install an updated license file. |
CFL2144 more than licensed number of CPUs are installed
Type |
ERROR |
Description |
The number of CPUs exceeds the licensed limit. |
Action |
Install an updated license file. |
CFL2145 License is expired
Type |
ERROR |
Description |
The license has expired. |
Action |
Reinstall the license file. |
CFL2148 your license does not support sub_prod_name
Type |
ERROR |
Description |
The license is not valid. |
Action |
Contact TmaxSoft to obtain or upgrade the license. |
CFL2149 more than licensed number of users/servers are configured
Type |
ERROR |
Description |
The number of users accessing the server has exceeded the limit. |
Action |
Adjust the number of users or increase the number of servers. |
CFL3001 length of option arg is too long
Type |
ERROR |
Description |
The command could not be processed because it is too long. |
Action |
Ensure that the command string does not exceed 256 characters. |
CFL3002 TMAXDIR is not set
Type |
ERROR |
Description |
The environment variable (TMAXDIR) was not configured. |
Action |
Configure the TMAXDIR variable.
|
CFL3003 parameter param is mandatory, but missed
Type |
ERROR |
Description |
The param setting does not exist in the configuration file. |
Action |
Write the relevant items in the configuration file. |
CFL3004 section sect is mandatory, but missed
Type |
ERROR |
Description |
The sect setting does not exist in the configuration file. |
Action |
Write the relevant items in the configuration file. |
CFL3005 node name node1 not found in config
Type |
ERROR |
Description |
The node name (node1) was not configured in the NODE section in the configuration file. |
Action |
Check the node name specified in the NODE section of the configuration file. |
CFL3006 no such server group is defined for COUSIN or BACKUP : svgname
Type |
ERROR |
Description |
The server group (svgname) was not configured with COUSIN or BACKUP settings in the configuration file. |
Action |
Check the group name in the SVRGROUP section of the configuration file. |
CFL3007 BACKUP of server group svg1 is in same node
Type |
ERROR |
Description |
The server group (svg1) is located on the same node as the backup server. |
Action |
Modify the configuration file to place the backup server group on a separate node from the server group. |
CFL3008 server group svg1 is defined as both COUSIN and BACKUP for svg2
Type |
ERROR |
Description |
The server group (svg1) was configured as both BACKUP and COUSIN for another server group (svg2). |
Action |
A server group cannot be defined as both BACKUP and COUSIN for another server group. Modify the configuration file accordingly. |
CFL3009 line num : cannot proceed due to previous error
Type |
ERROR |
Description |
Failed to proceed due to a previous error. |
Action |
Refer to the previous error messages. |
CFL3010 line num : parameter param duplicately defined
Type |
ERROR |
Description |
The parameter value (param) is duplicated. |
Action |
Remove the duplicate value or align it with the existing value. |
CFL3011 too many node definitions (MAX : max)
Type |
ERROR |
Description |
Too many nodes were defined in the NODE section of the configuration file. |
Action |
Ensure that the number of nodes in the NODE section does not exceed the maximum limit. |
CFL3012 line num : DOMAINNAME in NODE nodename is not defined
Type |
ERROR |
Description |
The DOMAINNAME for the node (nodename) is not defined in the NODE section of the configuration file. |
Action |
Define the DOMAINNAME for the node (nodename). |
CFL3013 line num : DOMAINNAME domname in NODE section not found
Type |
ERROR |
Description |
The domain name (DOMAINNAME) is not defined in the NODE section of the configuration file. |
Action |
Ensure that DOMAINNAME is correctly specified in the DOMAIN section of the configuration file. |
CFL3014 line num : NODENAME = node1 in SVRGROUP section not defined
Type |
ERROR |
Description |
The node name (node1) defined in the SVRGROUP section could not be found in the NODE section of the configuration file. |
Action |
Ensure that node1 is correctly specified in the NODE section of the configuration file. |
CFL3015 line num : SVGNAME = svg1 in RQ section not defined
Type |
ERROR |
Description |
The server group (svg1) specified as the SVGNAME in the RQ section of the configuration file could not be found in the SVRGROUP section. |
Action |
Ensure that svg1 is correctly specified in the SVRGROUP section of the configuration file. |
CFL3016 line num : SVG Type of server group svg1 is not RQMGR
Type |
ERROR |
Description |
The SVGTYPE of the server group (svg1) defined in the RQ section of the configuration file is not RQMGR. |
Action |
Check the SVGTYPE in the svg1 settings under the SVRGROUP section. SVGTYPE of svg1 defined in the RQ section of the configuration file must be RQMGR. |
CFL3017 line num : NODENAME = node1 in GATEWAY section not defined
Type |
ERROR |
Description |
The node1 specified as NODENAME in the GATEWAY section of the configuration file could not be found in the NODE section. |
Action |
Ensure that node1 is correctly defined in the NODE section. |
CFL3018 line num : SVGNAME = svg1 in SERVER section not defined
Type |
ERROR |
Description |
The svg1 specified as SVGNAME in the SERVER section of the configuration file could not be found in the SVRGROUP section. |
Action |
Ensure that svg1 is correctly defined in the SVRGROUP section. |
CFL3019 line num : ROUTING = rout1 in SERVICE section not defined
Type |
ERROR |
Description |
The rout1 specified as ROUTING in the SERVICE section of the configuration file could not be found in the ROUTING section. |
Action |
Ensure that rout1 is correctly defined in the ROUTING section. |
CFL3020 line num : SVRNAME = svr1 in SERVICE section not defined
Type |
ERROR |
Description |
The svr1 specified as SVRNAME in the SERVICE section of the configuration file could not be found in the SERVER section. |
Action |
Ensure that svr1 is correctly defined in the SERVER section. |
CFL3021 line num : param in DOMAIN section must be same in all domains
Type |
ERROR |
Description |
The parameter values configured in all DOMAIN sections are not identical. |
Action |
Verify the parameter values in all DOMAIN sections. In a multi-domain configuration, these values must be the same. |
CFL3022 line num : domain name dom is not unique
Type |
ERROR |
Description |
The domain name (dom) defined in the DOMAIN section is not unique. |
Action |
Verify whether dom exists elsewhere in the configuration file. |
CFL3023 line num : MAXCLH (num1) < MINCLH (num2) in section1
Type |
ERROR |
Description |
The MAXCLH value in section1 of the configuration file is smaller than MINCLH. Section1 can be either a domain or a node. |
Action |
Ensure that the MINCLH value is smaller than MAXCLH. |
CFL3024 IDLETIME must use with CLICHKINT
Type |
ERROR |
Description |
IDLETIME in the DOMAIN section of the configuration file was not used with CLICHKINT. |
Action |
Use IDLETIME and CLICHKINT together. |
CFL3025 line num : domain.OWNER must be used with SECURITY
Type |
ERROR |
Description |
OWNER in the DOMAIN section of the configuration file was not used with SECURITY. |
Action |
Use OWNER and SECURITY together. |
CFL3026 DOMAIN.OWNER = owner1 not found
Type |
ERROR |
Description |
The user name (owenr1) was not found. |
Action |
Verify whether owner1 is a user name. |
CFL3027 line num : routing name rout1 is not unique
Type |
ERROR |
Description |
The routing name (rout1) specified in the ROUTING section is not unique. |
Action |
Verify whether rout1 exists elsewhere in the configuration file. |
CFL3028 same name name1 found in section1 and section2
Type |
ERROR |
Description |
The name (name1) is duplicated in section1 and section2. |
Action |
Ensure that name1 is unique across all sections. |
CFL3029 NODE.MAXUSER (max1) > licensed maxuser (max2)
Type |
ERROR |
Description |
The MAXUSER (max1) value exceeded the maximum allowable user count (max2). |
Action |
Ensure that max1 does not exceed max2. |
CFL3030 line num : TLOGDIR cannot be same as SLOGDIR
Type |
ERROR |
Description |
The TLOGDIR setting is the same as SLOGDIR in the configuration file. |
Action |
Ensure that TLOGDIR and SLOGDIR have different paths. |
CFL3031 line num : TLOGDIR cannot be same as ULOGDIR
Type |
ERROR |
Description |
The TLOGDIR setting is the same as ULOGDIR in the configuration file. |
Action |
Ensure that TLOGDIR and ULOGDIR have different paths. |
CFL3032 line num : SLOGDIR cannot be same as ULOGDIR
Type |
ERROR |
Description |
The SLOGDIR setting is the same as ULOGDIR in the configuration file. |
Action |
Ensure that SLOGDIR and ULOGDIR have different paths. |
CFL3033 line num : node name node1 is not unique
Type |
ERROR |
Description |
The domain name (node1) specified in the NODE section is not unique. |
Action |
Verify whether node1 exists elsewhere in the configuration file. |
CFL3034 LOGOUTSVC svc1 not found in SERVICE section
Type |
ERROR |
Description |
The LOGOUTSCV svr1 setting defined in the NODE section of the configuration file could not be found in the SERVICE section. |
Action |
Ensure that svr1 is correctly defined in the SERVER section. |
CFL3035 line num : server group name svg1 is not unique. Same name found in section1
Type |
ERROR |
Description |
The server group name (svg1) on line numth of the configuration file is duplicated in section1. |
Action |
Modify the configuration file to ensure that the server group name is unique. |
CFL3036 line num : SVRGROUP.SECURITY must be used with OWNER
Type |
ERROR |
Description |
OWNER in the SVRGROUP section of the configuration file was not used with SECURITY. |
Action |
Use OWNER and SECURITY together. |
CFL3037 line num : SVRGROUP.SECURITY defined without ACL_SVG
Type |
ERROR |
Description |
The SECURITY setting in the DOMAIN section is not set to ACL_SVG, and the SECURITY item is missing in the SVRGROUP section. |
Action |
Set SECURITY to ACL_SVG in the DOMAIN section and ensure the SVRGROUP section includes the SECURITY item. |
CFL3038 line num : SVRGROUP.LOAD must be used with COUSIN
Type |
ERROR |
Description |
LOAD in the SVRGROUP section of the configuration file was not used with COUSIN. |
Action |
Use LOAD and COUSIN together. |
CFL3039 line num : SVRGROUP.OPENINFO must be used with DBNAME
Type |
ERROR |
Description |
OPENINFO in the SVRGROUP section of the configuration file was not used with DBNAME. |
Action |
Use OPENINFO and DBNAME together. |
CFL3040 line num : SVRGROUP.OPENINFO must be used with TMSNAME
Type |
ERROR |
Description |
OPENINFO in the SVRGROUP section of the configuration file was not used with TMSNAME. |
Action |
Use OPENINFO and TMSNAME together. |
CFL3041 line num : SVRGROUP.MINTMS must be used with OPENINFO
Type |
ERROR |
Description |
MINTMS in the SVRGROUP section of the configuration file was not used with OPENINFO. |
Action |
Use MINTMS and OPENINFO together. |
CFL3042 line num : SVRGROUP.MAXTMS must be used with OPENINFO
Type |
ERROR |
Description |
MAXTMS in the SVRGROUP section of the configuration file was not used with OPENINFO. |
Action |
Use MAXTMS and OPENINFO together. |
CFL3043 line num : MAXTMS (max) < MINTMAX (min)
Type |
ERROR |
Description |
The MAXTMS value configured in the SVRGROUP section is smaller than MINTMS. |
Action |
Ensure that MINTMS is smaller than MAXTMS. |
CFL3044 line num : MAX (max) < MIN (min) in SERVER section
Type |
ERROR |
Description |
The MAX value configured in the SERVER section is smaller than MIN. |
Action |
Ensure that MIN is smaller than MAX. |
CFL3045 line num : CPC cannot be defined for TMAX_STD SVR TYPE in SERVER section
Type |
ERROR |
Description |
The CPC item cannot be configured in TMAX_STD SVR TYPE. |
Action |
Remove the CPC setting. |
CFL3046 line num : SVRNAME = svr1 is not unique. Same name found in section1
Type |
ERROR |
Description |
The server name (svg1) on line numth of the configuration file is duplicated in section1. |
Action |
Modify the configuration file to ensure that the server name is unique. |
CFL3047 line num : service name = svc is not unique
Type |
ERROR |
Description |
The service name (svc) on line numth of the configuration file is duplicated. |
Action |
Modify the configuration file to ensure that the service name is unique. |
CFL3048 line num : PRESVC = presvc is not found
Type |
ERROR |
Description |
The service name (presvc) on line numth of the configuration file is not registered in the SERVICE section. |
Action |
Ensure that presvc is correctly defined in the SERVER section of the configuration file. |
CFL3049 line num : RQ name = rqsis not unique
Type |
ERROR |
Description |
The RQ name (rqs) on line numth of the configuration file is duplicated. |
Action |
Modify the configuration file to ensure that the RQ name is unique. |
CFL3050 line num : gateway name = gw is not unique
Type |
ERROR |
Description |
The gateway name (gw) on line numth of the configuration file is duplicated. |
Action |
Modify the configuration file to ensure that the gateway name is unique. |
CFL3051 line num : invalid parameter value : param. Valid range = (MIN : min, MAX : max)
Type |
ERROR |
Description |
The parameter value (param) is out of the valid range. |
Action |
Ensure that the param value falls within the valid range, between the min and max values. |
CFL3052 line num : invalid parameter value : param. Valid range = (MAX : max)
Type |
ERROR |
Description |
The parameter value (param) is out of the valid range. |
Action |
Ensure that the param value falls within the valid range and does not exceed the max value. |
CFL3053 line num : invalid parameter value : param. Valid range = (MIN = min)
Type |
ERROR |
Description |
The parameter value (param) is out of the valid range. |
Action |
Ensure that the param value falls within the valid range and is not below the min value. |
CFL3054 line num : invalid parameter value : param. Valid value = (value_list)
Type |
ERROR |
Description |
The parameter value (param) is out of the valid range. |
Action |
Change the param value to one of those listed in value_list. |
CFL3055 ROUTING is defined without COUSIN
Type |
ERROR |
Description |
The ROUTING section is defined without COUSIN setting. |
Action |
Define the COUSIN group in the SVRGROUP section. The ROUTING section should be defined between a specific server group and the COUSIN setting. For more information, refer to Tmax Administration Guide. |
CFL3056 line num : invalid RANGES value : both * and "min (max)" defined
Type |
ERROR |
Description |
The RANGES setting is incorrectly configured in the ROUTING section. |
Action |
Correctly define the minimum and maximum values in the RANGES setting. For more information, refer to Tmax Administration Guide. |
CFL3057 line num : invalid RANGES value : no * nor"min (max)"defined
Type |
ERROR |
Description |
The RANGES setting is incorrectly configured in the ROUTING section. |
Action |
Correctly define the minimum and maximum values in the RANGES setting. For more information, refer to Tmax Administration Guide. |
CFL3058 line num : invalid RANGES value : more than one "*" defined
Type |
ERROR |
Description |
The RANGES setting is incorrectly configured in the ROUTING section. |
Action |
"*" must be used only once in the RANGES setting. For more information, refer to Tmax Administration Guide. |
CFL3059 line num : RANGES value conflict : (string, int)
Type |
ERROR |
Description |
A string value conflicts with an integer value in the RANGES setting. |
Action |
Use either a string or an integer value; both cannot be used together. |
CFL3060 line num : RANGES value conflict : (mod, int)
Type |
ERROR |
Description |
A MOD value conflicts with an integer value in the RANGES setting. |
Action |
Use either a MOD value or an integer value; both cannot be used together. For more information, refer to Tmax Administration Guide. |
CFL3061 line num : RANGES value conflict : (string, mod)
Type |
ERROR |
Description |
A MOD value conflicts with a string value in the RANGES setting. |
Action |
Use either a MOD value or a string value; both cannot be used together. For more information, refer to Tmax Administration Guide. |
CFL3062 line num : invalid RANGES value : string is too long (MAX = max)
Type |
ERROR |
Description |
The string in the RANGES setting is too long. |
Action |
Ensure that the string does not exceed the maximum allowed length. |
CFL3063 line num : invalid RANGES value : string is not ended.
Type |
ERROR |
Description |
The string in the RANGES setting does not end with a double quotation mark ("). |
Action |
Ensure that the string in RANGES is enclosed in double quotation marks ("). |
CFL3064 line num : invalid RANGES value : more than one MIN (or min) defined
Type |
ERROR |
Description |
The MIN value was specified more than once in the RANGES setting. |
Action |
Ensure that the MIN value is defined only once and correctly configured. |
CFL3065 line num : invalid RANGES value : more than one MAX (or max) defined
Type |
ERROR |
Description |
The MAX value was specified more than once in the RANGES setting. |
Action |
Ensure that the MAX value is defined only once and correctly configured. |
CFL3066 line num : RANGES format error : format
Type |
ERROR |
Description |
The RANGES setting contains an incorrect format. |
Action |
For more information about the format, refer to Tmax Administration Guide. |
CFL3067 line num : RANGES error : no svrgroup name
Type |
ERROR |
Description |
The string in the RANGES setting does not end with a double quotation mark ("). |
Action |
Ensure that the string in RANGES is enclosed in double quotation marks ("). |
CFL3068 line num : RANGES error : no such server group svg defined
Type |
ERROR |
Description |
The server group (svg) defined in the RANGES setting could not be found in the configuration file. |
Action |
Ensure that the server group (svg) is specified in the SVRGROUP section of the configuration file. |
CFL3069 line num : RANGES error : bad MOD format
Type |
ERROR |
Description |
The MOD operator format used in RANGES is incorrect. |
Action |
For information about the correct MOD operator format in line numth, refer to Tmax Administration Guide. |
CFL3070 line num : RANGES error : from - to
Type |
ERROR |
Description |
The range specified in RANGES is incorrect. |
Action |
Set the range correctly |
CFL3071 line num : RANGES error : from1 - to1, from2 - to2
Type |
ERROR |
Description |
The range specified in RANGES is incorrect. |
Action |
Ensure that the condition ranges ‘from1 - to1’ and ‘from2 - to2’ do not overlap. For more information, refer to Tmax Administration Guide. |
CFL3072 line num : RANGES error : no such server group svg in COUSIN
Type |
ERROR |
Description |
The server group (svg) in the RANGES setting is not COUSIN-bound with other server groups defined in the same RANGES setting. |
Action |
For data-based load balancing, ensure that the server groups are COUSIN-bound. Verify that the COUSIN setting is correctly specified in the SVRGROUP section of the configuration file. For more information, refer to Tmax Administration Guide. |
CFL3073 line %d : RANGES buffer type error
Type |
ERROR |
Description |
The buffer type of DDR to enable the routing feature was incorrectly specified. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3082 number of listen portno (%d) is over
Type |
ERROR |
Description |
More than four ports (portno) were set in TmaxPort and CompressPort. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3084 configuration file syntax error : line(line_num) err_msg
Type |
ERROR |
Description |
A syntax error occurred at a line (line_num). |
Action |
Correct the syntax by referring to the error message. |
CFL3085 line line_num: GW(gw_name) PORTNO conflicts with TPORTNO
Type |
ERROR |
Description |
GW PORTNO conflicts with the TPORTNO used in DOMAIN or NODE. |
Action |
Change the GW PORTNO. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system and cannot be used. |
CFL3086 line line_num: GW(gw_name) PORTNO conflicts with RACPORT
Type |
ERROR |
Description |
GW PORTNO conflicts with RACPORT. |
Action |
Change the GW PORTNO or RACPORT. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system and cannot be used. |
CFL3087 line line_num: GW(gw_name) PORTNO conflicts with TPORTNOx
Type |
ERROR |
Description |
GW PORTNO conflicts with the TPORTNO used in DOMAIN or NODE. |
Action |
Change the GW PORTNO. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system and cannot be used. |
CFL3088 NODE(nodename) TPORTNOx conflicts with TPORTNOy
Type |
ERROR |
Description |
TPORTNO in DOMAIN conflicts with TPORTNO in NODE. |
Action |
Change the TPORTNO in the NODE section. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system and cannot be used. |
CFL3089 More than one DOMAIN sections are defined
Type |
ERROR |
Description |
More than one DOMAIN sections are defined |
Action |
Delete invalid DOMAIN sections. Only one DOMAIN section can be set. |
CFL3090 NODE(nodename) TPORTNOx conflicts with RACPORT
Type |
ERROR |
Description |
TPORTNO in DOMAIN or NODE conflicts with RACPORT. |
Action |
Change RACPORT or TPORTNO. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system. |
CFL3091 line line_num: GW (gw_name) PORTNO conflicts with GW (gw_name)
Type |
ERROR |
Description |
GW PORTNO conflicts with gw_name. |
Action |
Change GW PORTNO. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system. |
CFL3092 line line_num: GW (gw_name) RGWPORTNO conflicts with GW (gw_name)
Type |
ERROR |
Description |
GW RGWPORTNO conflicts with gw_name. |
Action |
Change GW RGWPORTNO. Values from TPORTNO (used in DOMAIN) up to TPORTNO + 11 are reserved by the Tmax system. |
CFL3095 more NODEs(%d) than MAXNODE(%d) are defined
Type |
ERROR |
Description |
The number of nodes specified exceeds the MAXNODE limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3096 more RQs(%d) than MAXRQ(%d) are defined
Type |
ERROR |
Description |
The number of RQs specified exceeds the MAXRQ limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3097 more GWs(%d) than MAXGW(%d) are defined.
Type |
ERROR |
Description |
The number of GWs specified exceeds the MAXGW limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3098 more SVGs(%d) than MAXTOTALSVG(%d) are defined.
Type |
ERROR |
Description |
The number of SVGs specified exceeds the MAXTOTALSVG limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3099 more SVCs(%d) than MAXSVC(%d) are defined.
Type |
ERROR |
Description |
The number of SVCs specified exceeds the MAXSVC limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3100 more ROUTs(%d) than MAXROUT(%d) are defined
Type |
ERROR |
Description |
The number of ROUTs specified exceeds the MAXROUT limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3101 more ROUT SVGs(%d) than MAXROUTSVG(%d) are defined
Type |
ERROR |
Description |
The number of ROUT SVGs specified exceeds the MAXROUTSVG limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3102 more COUSINs(%d) than MAXROUTSVG(%d) are defined
Type |
ERROR |
Description |
The number of COUSINs specified exceeds the MAXCOUSIN limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3103 more COUSIN SVGs(%d) than MAXCOUSINSVG(%d) are defined
Type |
ERROR |
Description |
The number of COUSINs specified exceeds the COUSINSVG limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3104 more BACKUPs(%d) than MAXBACUP(%d) are defined
Type |
ERROR |
Description |
The number of BACKUPs specified exceeds the MAXBACKUP limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3105 more BACKUP SVGs(%d) than MAXBACKUPSVG(%d) are defined
Type |
ERROR |
Description |
The number of BACKUP SVGs specified exceeds the MAXBACKUPSVG limit configured in the DOMAIN section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3108 MAXNODE * MAXCLH * CPC of the DOMAN section is too long (>= %d), reduce one of them.
Type |
ERROR |
Description |
The MAXNODE CPC value in the DOMAIN section must be smaller than FD_SETSIZE. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3110 more %s(%d) than %s(%d) are defined at node(%s)
Type |
ERROR |
Description |
The number of %s specified in the node exceeds the value set in %s. |
Action |
Increase the MAX value or reduce the number of %s. |
CFL3111 more %s(%d) than %s(%d) are defined
Type |
ERROR |
Description |
The number of %s specified exceeds the value set in %s. |
Action |
Increase the MAX value or reduce the number of %s. |
CFL3113 more than MAXSPR(%d) are defined at node(%s)
Type |
ERROR |
Description |
The number of server processes in use exceeds the MAXSPR limit defined in the configuration file. |
Action |
1) Adjust the MAXSPR setting in the DOMAIN or NODE section. 2) Increase the maximum user count. |
CFL3114 more than MAXCPC(%d) are defined at node(%s)
Type |
ERROR |
Description |
The number of CPCs in use exceeds the MAXCPC limit defined in the configuration file. |
Action |
Adjust the MAXCPC setting in the DOMAIN or NODE section. |
CFL3115 more than one domain (%d) defined
Type |
ERROR |
Description |
More than one domain is specified in the configuration file. |
Action |
A Tmax configuration file can contain only a single domain. Modify the configuration file accordingly. |
CFL3116 internal error: not found tip svg
Type |
FATAL |
Description |
TIP SVG was specified without the TIP server setting. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3117 line %d: SERVER(%s) is defined under RQMGR SVG(%s)
Type |
ERROR |
Description |
Non-RQ servers cannot be set in RQMGR SVG. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3118 line %d : DOMAIN CMTRET must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the CMTRET value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3119 line %d : DOMAIN BLOCKTIME must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the BLOCKTIME value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3120 line %d : DOMAIN TXTIME must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the TXTIME value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3121 line %d : DOMAIN MAXFUNC must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the MAXFUNC value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3122 line %d : DOMAIN MAXSACALL must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the MAXSACALL value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3123 line %d : DOMAIN MAXCACALL must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the MAXCACALL value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3124 line %d : DOMAIN MAXCONV_NODE must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the MAXCONV_NODE value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3125 line %d : DOMAIN MAXCONV_SERVER must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the MAXCONV_SERVER value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3126 line %d : DOMAIN CPC must be same in all domains
Type |
ERROR |
Description |
When configuring multiple domains in one configuration file, the CPC value in all domains must be the same. |
Action |
The current version does not support multiple domains in a single configuration file. |
CFL3127 no MAXUSER field found for same logical nodes, licensed number of users distributed evenly among nodes: %d users per unspecified node
Type |
INFO |
Description |
When configuring MAXUSER, the total number of available users is divided by the number of nodes, and the resulting count is applied to each node. |
CFL3128 NODE(%s): MAXSVR(%d) > MAXSPR(%d)
Type |
ERROR |
Description |
The MAXSVR value of a node must be greater than MAXSPR. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3129 NODE(%s): MAXRQSVR(%d) + MAXGWSVR(%d) > MAXSPR(%d)
Type |
ERROR |
Description |
The 'MAXRQSVR + MAXGWSVR' value of a node must be greater than MAXSPR. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3130 NODE(%s): MAXRQCPC(%d) + MAXGWCPC(%d) > MAXCPC(%d)
Type |
ERROR |
Description |
The 'MAXRQCPC + MAXGWCPC' value of a node must be greater than MAXCPC. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3131 NODE(%s): CompressPort(%d) is not define in Tmaxport
Type |
ERROR |
Description |
CompressPort must be one of TmaxPorts. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3132 NODE(%s): TMAXPORTx conflicts with CPORTNO
Type |
ERROR |
Description |
TMAXPORT conflicts with CPORTNO. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3133 NODE(%s): TMAXPORTx conflicts with EXTPORT
Type |
ERROR |
Description |
TMAXPORT conflicts with EXTPORT. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3134 NODE(%s): TMAXPORTx conflicts with EXTCLHPORTy
Type |
ERROR |
Description |
TMAXPORT conflicts with EXTCLHPORT. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3135 NODE(A) %s conflicts with NODE(B) %s
Type |
ERROR |
Description |
A setting in NODE(A) conflicts with one in NODE(B). |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3136 NODE(A) and NODE(B) have different NODETYPE
Type |
ERROR |
Description |
NODE(A) and NODE(B) have different NODETYPE values. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3137 line %d: SVR, SCHEDULE must be RR for TMAX_UCS_LOAD svrtype
Type |
ERROR |
Description |
If the svrtype is TMAX_UCS_LOAD, it must be SCHEDULE PR. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3138 line %d: SVR, cpc cannot be defined for TMAX_STD svrtype
Type |
ERROR |
Description |
If the svrtype is TMAX_STD, CPC must be 1. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3139 line %d: MIN/MAX must be 1 for SYS_SVR
Type |
ERROR |
Description |
If svrtype is SYS_SVR, the MIN/MAX value must be 1. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3140 line %d: SVR (%s) is not registered at REASVR field of NODE section
Type |
ERROR |
Description |
If svrtype is REALSVR_MT, it must be registered in REALSVR of the NODE. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3141 you don’t have enough UCS(CPC) license to support current configuration (%d < %d)
Type |
ERROR |
Description |
The UCS license level is insufficient. |
Action |
You may ignore this message since the current Tmax version does not check UCS. |
CFL3142 line %d: ENQSVC = %s is not found
Type |
ERROR |
Description |
The SVC with the name defined in ENQSVC of RQ could not be found. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3143 line %d: GW(%s) %s conflicts with %s
Type |
ERROR |
Description |
%s in GATEWAY conflicts with %s. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3144 line %d: GW(%s) %s is mandotory
Type |
ERROR |
Description |
'%s' in the GATEWAY section is a required setting. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3145 node (%s) REALSVR(%s) is not defined as REALSVR or REALSVR_MT
Type |
ERROR |
Description |
The svrtype of a server specified as REALSVR in the NODE section is not REALSVR or REALSVR_MT. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3146 REALSVR(%s) MIN(%d) must be bigger than MINCLH(%d)
Type |
ERROR |
Description |
If svrtype is REALSVR, the MIN value of the server must be greater than MINCLH in the NODE section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3147 REALSVR(%s) MAX(%d) must be smaller than MINCLH(%d) * %d
Type |
ERROR |
Description |
If svrtype is REALSVR, the MAX value of the server must be smaller than MINCLH * 16 in the NODE section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3148 REALSVR(%s) is not found in SVR table
Type |
ERROR |
Description |
A REALSVR set in the node was not found in the SERVER section of the configuration file. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3149 node (%s) MINCLH must equal MAXCLH when REALSVR defined
Type |
ERROR |
Description |
If REALSVR is set, the MINCLH and MAXCLH values must the same. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3150 line %d: REALSVR_MT (%s) cannot have a service (%s)
Type |
ERROR |
Description |
If svrtype is REALSVR_MT, no service can be registered in the server. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3151 no support dbname (%s)
Type |
ERROR |
Description |
An unsupported dbname was set. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3152 can’t get text for encryption
Type |
ERROR |
Description |
The user entered an incorrect Crypt text. |
Action |
Enter the Crypt text correctly. |
CFL3153 aflag must use with -o
Type |
FATAL |
Description |
For the cfl command, the –a and –o options must be used together. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3154 Allowed binary configuration file version is 0 or 1
Type |
ERROR |
Description |
For the cfl command, only 0 or 1 can be used for the –v option. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3155 no such name is found :
Type |
ERROR |
Description |
The specified nodename is not found in the configuration file. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3156 %s format error: %s
Type |
ERROR |
Description |
The parameter was incorrectly used. |
Action |
Refer to the relevant guide for the '%s' parameter. |
CFL3157 unknown %s parameter: kind = %d, val = %s
Type |
ERROR |
Description |
The paramter is invalid. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3158 line %d: invalid parameter value: %s
Type |
ERROR |
Description |
An invalid parameter value was set. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3159 %s file read error
Type |
ERROR |
Description |
Could not read the file. |
Action |
Refer to the message from the previous error and take the appropriate action. |
CFL3160 no svr defined for svg in rout_table: svg = %s, svr = %s, svc = %s
Type |
ERROR |
Description |
The server group (SVG) to which the service belongs is not configured for DDR. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3161 node(%s) REALSVR(%s) is not found in the same node
Type |
ERROR |
Description |
REALSVR was configured only in the NODE section and not in the SERVER section. |
Action |
Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3162 maxsvc: %d, conflict_count: %d
Type |
INFO |
Description |
Duplicate service names exist in MAXSVC. |
Action |
Each SVC name must be unique in Tmax. Change the settings in the configuration file by referring to Tmax Administration Guide. |
CFL3163 %s must be used with %s
Type |
ERROR |
Action |
%s must be used with %s. |
CFL3164 line %d: prod name is not found for server (%s)
Type |
ERROR |
Description |
No PRODNAME matches the name of a server set in a FUNCTION section. |
Action |
Check the PRODNAME in the SVG section and the SVRNAME in the FUNCTION section of the TOPEND environment configuration. |
CFL3165 prod is not available for svr (%s)
Type |
ERROR |
Description |
An invalid SVRNAME has been set for a FUNCTION. |
Action |
Check the PRODNAME setting for the SVG. |
CFL3166 too many TMSDEP entries: val > max
Type |
ERROR |
Description |
The number of TMSDEP entries exceeded the maximum allowable value. |
Action |
Set the TMSDEP entires count to be smaller than the maximum value. |
CFL3167 TMSDEP entry(tmsname) is not found
Type |
ERROR |
Description |
Could not find the entry (tmsname) set for TMSDEP. |
Action |
Check whether the TMS set for the TMSDEP exists in the same node. |
CFL3168 line num: multiple servers cannot define SYS_EVT svrtype
Type |
ERROR |
Description |
Only one event handler server (svrtype = SYS_EVT) can be configured per node. |
Action |
Verify that the event handler server is not duplicated in the SERVER section of the configuration file. |
CFL3169 line num: MIN/MAX must be 1 for SYS_EVT
Type |
ERROR |
Description |
The event handler server process (svrtype = SYS_EVT) cannot be set to a value that is greater than 1. |
Action |
Set the MIN/MAX value for the event handler server to 1 in the SERVER section of the configuration file. |
CFL3183 line num: invalid service name svc_name
Type |
ERROR |
Description |
The service name specified in the -x option of the CLOPT configuration of the SERVICE section was not found in the configuration file. |
Action |
Check that the service name specified in the -x option is correct. |
CFL3184 line num: invalid target server name svr_name
Type |
ERROR |
Description |
The server name specified in the TARGET configuration of the SERVER section was not found in the configuration file. |
Action |
Check that the server name specified in TARGET configuration is correct. |
CFL3198 line num: invalid parameter value : option. Valid range = (MIN : min_value, MAX : max_value) except (except_value)
Type |
ERROR |
Description |
The value specified for an option in the configuration file is outside the allowable range. |
Action |
Refer to the MIN, MAX, and except sections to set a valid value. |
CFL3199 line %d : MAXQCOUNT can not be 0 while ASQCOUNT is set
Type |
ERROR |
Description |
ASQCOUNT is set in the configuration file, but MAXQCOUNT is 0. |
Action |
Either remove the ASQCOUNT setting or set MAXQCOUNT to 1 or a larger value. |
CFL3200 line %d : %s cannot be less than 0 or greater than 255
Type |
ERROR |
Description |
The TSINITKILLTIMEOUT/TSDONEKILLTIMEOUT value is less than 0 or greater than 255. |
Action |
Ensure that the value is within the valid range (0–255). |
CFL3201 line %d : GW (%s) RGWPORTNO and RGWADDR conflicts with GW (%s) in other NODE (%s)
Type |
WARNING |
Description |
The RGWPORTNO/RGWADDR settings are duplicated across different gateways. |
CFL3202 LOAD mismatch: %s has LOAD=%d, but COUSIN %s has LOAD=%d
Type |
ERROR |
Description |
The LOAD settings of the server groups or gateways bound by COUSIN do not match. |
Action |
Ensure that the server groups and gateways using the COUSIN feature follow these rules:
|
CFL3203 line %d : TSKILLTIMEOUT is no longer supported, use TSINITKILLTIMEOUT/TSDONEKILLTIMEOUT
Type |
ERROR |
Description |
The TSKILLTIMEOUT setting was used, but it is no longer supported starting with version Fix5. |
Action |
Use TSINITKILLTIMEOUT/TSDONEKILLTIMEOUT instead of TSKILLTIMEOUT. |
5. CLH Module (CLH0200 ~ )
CLH0200 magic number error from client(ipaddr) : num1 num2 num3 num4
Type |
ERROR |
Description |
Due to corruption of data received from a client (the message was truncated during transmission), further processing could not be performed. The received message will be discarded, and the connection with the client will be closed. num1, num2, num3, and num4 represent the data sizes allocated by Tmax for the message type, magic number, svci, and asize fields, respectively. |
Action |
Check whether the message was successfully transmitted from the client. If not, verify the application program for possible issues such as memory corruption, invalid array access, null characters in string data, or input data exceeding the actual buffer size. |
CLH0202 corrupt msg header from client(ipaddr) : num1
Type |
ERROR |
Description |
A message received from a client was corrupted (truncated during transmission) but may be partially recovered. Only the truncated portion of the message will be discarded, and the remaining part will be processed. If an error occurs during processing, a TPEITYPE or TPEINVAL error may be returned to the client. |
Action |
Check whether the message was successfully transmitted from the client. If not, verify the application program for possible issues such as memory corruption, invalid array access, null characters in string data, or input data exceeding the actual buffer size. |
CLH0209 internal error : invalid msgtype(num1) from client(ipaddr)
Type |
ERROR |
Description |
The type field of a message received from a client was corrupted. Tmax will discard the message then wait for the next message. |
Action |
Check whether the message was successfully transmitted from the client. If not, verify the application program for possible issues such as memory corruption, invalid array access, null characters in string data, or input data exceeding the actual buffer size. |
CLH0209 internal error : disconnect client because client didn’t send tpstart msg for 60 sec.(ipaddr)
Type |
ERROR |
Description |
Clients failed to connect to Tmax because an abnormal number of client connections were established to CLH. CLH disconnects any client that does not respond to the TP START connection message within 60 seconds after the socket connection is established. |
Action |
Identify the cause of the abnormal number of client connections to CLH. |
CLH2001 service not found : ServiceName
Type |
ERROR |
Description |
Failed to find the service (ServiceName) requested by a client in the server process. The service information registered in the Tmax engine does not match the corresponding server process. |
Action |
Recompile the configuration file using cfl -i, and then run the gst command. Delete any existing objects before compiling the new file. |
CLH2002 service not found : ServiceName
Type |
FATAL |
Description |
Failed to initialize the service table because the server process could not find the corresponding service (ServiceName). |
Action |
The service information registered in the Tmax engine does not match the corresponding server process. Recompile the configuration file using cfl -i, and then run the gst command. Delete any existing objects before compiling the new file. |
CLH2004 FDL field TYPE error : Type_number
Type |
ERROR |
Description |
A transmitted message contains data using an unsupported FDL field type. |
Action |
If the error occurs on the client side, check whether the tmax.fdl file is damaged. If the error occurs on the server side, verify the FDL header file (suffix: _fdl.h) and recompile it. |
CLH2005 FDL field Type error : Type_number
Type |
ERROR |
Description |
A transmitted message contains data using an unsupported FDL field type. |
Action |
Check for any communication failures between the client and server. |
CLH2006 client timeout error
Type |
ERROR |
Description |
A response arrived within the defined timeout after executing tpcall. |
Action |
For normal processing, increase the BLOCKTIMEOUT value in the DOMAIN section of the configuration file. Otherwise, check for communication issues between the client and server. |
CLH2007 service timeout error : ServiceName
Type |
ERROR |
Description |
The service could not be completed within the specified timeout period. |
Action |
Increase the SVCTIME value for the service (ServiceName) in the configuration file. If the SVCTIME value is already sufficient, investigate potential inefficiencies in the service routine. |
CLH2009 server downed while processing client msg
Type |
ERROR |
Description |
The server was shut down while executing a request. |
Action |
Restart the server process using the tmboot -s svrname command, and investigate the server application for possible errors. |
CLH2010 CLH connection closed : fd_no
Type |
INFO |
Description |
The connection with another CLH was closed due to tmdown. |
CLH2011 TMM connection closed : fd_no
Type |
INFO |
Description |
The connection with TMM was closed due to tmdown. |
CLH2014 register to CLH error : clh_id fd_no
Type |
ERROR |
Description |
Failed to connect a CLH process due to a previous error. |
Action |
Refer to the previous error message. |
CLH2015 register to TMM error
Type |
FATAL |
Description |
Failed to register TMM due to a previous error. |
Action |
1) Check that the TMM process is operating properly by using the ps command. 2) Refer to the previous error message. |
CLH2016 register to CLL error
Type |
FATAL |
Description |
Failed to register CLL due to a previous error. |
Action |
Refer to the previous error message. |
CLH2017 DDR error : subType or field not found
Type |
FATAL |
Description |
The server was terminated due to a previous DDR error. |
Action |
Refer to the previous DDR error message. |
CLH2018 DDR bad fieldkey error : fieldkey
Type |
ERROR |
Description |
The fieldkey value for DDR was invalid. |
Action |
Check that the fieldkey value (fieldkey) defined in the ROUTING section of the configuration file is correct. |
CLH2019 DDR bad fieldkey Type error : fieldkey received_fieldkey_Type expected_fieldkey_Type
Type |
ERROR |
Description |
The fieldkey type for DDR does not match with the type defined in the configuration file. |
Action |
Check that the fieldkey type for DDR in the ROUTING section of the configuration file matches with that in the FDL definition file (extension: .f). Valid fieldkey types are: short, long, int and string. For more information, refer to Tmax Administration Guide. |
CLH2020 DDR SDL field error : field
Type |
ERROR |
Description |
The field for DDR does not exist in the related subtype of a structure-typed binary file (extension: .sdl). |
Action |
Check that the DDR field in the ROUTING section matches with that of the structure-typed definition file (extension: .s). If so, recreate a structure-typed definition binary file (SDLFILE). |
CLH2021 DDR SDL subtype error : sub Type
Type |
ERROR |
Description |
The structure type for DDR was not defined in the structure-typed binary file (extension: .sdl). |
Action |
Check that the DDR structure type of the ROUTING section matches with that of the structure-typed definition file (extension.s). If so, recreate a structure-typed definition binary file (SDLFILE). |
CLH2022 DDR error : no data received in message
Type |
ERROR |
Description |
No data was received for DDR. |
Action |
The client must send the data that was predefined in the configuration file to perform DDR. Confirm that the client received the relevant data type. |
CLH2023 DDR error : offset is not set
Type |
ERROR |
Description |
The offset value for DDR was not defined. |
Action |
The offset value is defined in the tmconfig file in the config directory. Confirm that the configuration file is compiled correctly using cfl -i. |
CLH2024 DDR error : data Type is not FIELD Type
Type |
ERROR |
Description |
The SUBTYPE of the related DDR was defined as FIELD in the ROUTING section of the configuration file, but the data received from clients did not use the field-type buffer. |
Action |
Check that the client transmission buffer is defined as field type. |
CLH2025 DDR sub Type mismatch : sub type_config sub type_received
Type |
ERROR |
Description |
The subtype name (subtype_config) defined in the SUBTYPE item of the configuration file did not match with the subtype_received of a message received from clients. |
Action |
Align the SUBTYPE in the configuration file with the subtype used by clients. If a structure-typed buffer is used, verify that the structure name in the definition file (extension: .s) matches the configuration file. If it matches, recreate the structure-typed definition binary file (SDLFILE). |
CLH2026 env file error : grammer_check_msg
Type |
ERROR |
Description |
An error occurred in an env file, which contains Tmax environment information. |
Action |
Rewrite the env file in reference to grammer_check_msg. |
CLH2030 no xa routine is setup
Type |
ERROR |
Description |
The server was terminated due to a previous DDR error related to a database. |
Action |
1) Check that the OPENINFO item and database connection information are defined properly in the SVRGROUP section of the configuration file. 2) Ensure that the database library related to a XA is linked properly. It is generally installed together with a database. You can also check this problem with the database installation team. |
CLH2031 xa_open error
Type |
ERROR |
Description |
An error occurred as a result of executing tx_open to connect to a RDBMS. |
Action |
Confirm that the OPENINFO item is described properly in the SVRGROUP section of the configuration file. In particular, confirm that the user ID and password described in OPENINFO is correct. |
CLH2032 xa_start error : xa_errno tx_errno
Type |
ERROR |
Description |
Executing xa_start for 2- phase commit caused an error. |
Action |
xa_start is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
CLH2033 xa_end error : no xa_start
Type |
WARNING |
Description |
xa_end was ignored because it was called without performing a xa_start. Transaction processing must be started by a tx_begin and terminated by a tx_commit or a tx_rollback. These functions are operated as a pair. Therefore, this error will occur if tx_commit or tx_rollback is performed without performing a tx_begin. When an error occurs a transaction will roll back. |
CLH2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2043 failed to write to TMM
Type |
FATAL |
Description |
Failed to send data to the TMM process. |
Action |
1) Use the tmadmin tool to check the connection status between CLH and TMM. 2) If an issue is found, contact the system administrator. |
CLH2043 failed to notify to TMM of CLH ready
Type |
ERROR |
Description |
Failed to send data to the TMM process. |
Action |
1) Use the tmadmin tool to check the connection status between CLH and TMM. 2) If an issue is found, contact the system administrator. |
CLH2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2045 TMM register error
Type |
ERROR |
Description |
Could not register the CLH process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CLH2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The CLH version does not match TMM. |
Action |
Reinstall the Tmax engine. |
CLH2051 maximum user connection is reached : licensed_maxuser allocated_maxuser_for_node maxuser_for_clh current_connection_count
Type |
ERROR |
Description |
The maximum number of concurrent users was exceeded. |
Action |
Increase the MAXUSER value defined in the DOMAIN section of the configuration file. When the registered maximum number of concurrent users is exceeded, a new license key must be obtained. Contact the system administrator. |
CLH2052 msg discarded due to closed client(%#x) connection : svc = svcname, msgtype = num
Type |
ERROR |
Description |
Could not send the service result because the client has been disconnected. |
Action |
Investigate the reason why the client has closed the connection without receiving the result. For example, check whether BLOCKTIME is too short or if there are delays in service processing. |
CLH2053 msg discarded due to closed server connection : svc = svcname, msgtype = num, spri = num
Type |
ERROR |
Description |
Could not send the service result to the requester server because the server has shut down or is already processing a new request. |
Action |
1) The server was shut down using tmdown -s or terminated abnormally for an unknown reason. Restart the server using tmboot -s. If the shutdown was abnormal, check the server application code. 2) This error maly also occur if tpreturn(TPFAIL) is received due to a service timeout after tpcall(), or if the tpcall() request was canceled due to expiration of blocktime, after which the server reissued tpcall and received the response to the previous request. In this case, the error can be ignored. |
CLH2054 msg is passed to the closed RealSvr connection.
Type |
ERROR |
Description |
The Tmax engine sent a message to a Real Server-type server, but the message was ignored because the connection was lost. |
Action |
The client was disconnected due to BLOCKTIME expiration or an abnormal condition. |
CLH2055 server msgs are dequeued : num
Type |
INFO |
Description |
The number (num) of messages remaining in the server process queue was deleted by tmdown when the corresponding server was terminated. |
CLH2056 tms abnormally closed : tms_name tms_no
Type |
ERROR |
Description |
The server process (tms_name) in charge of TMS was closed abnormally. |
Action |
1) Confirm that the TMS process (tms_name) was linked with the latest TMS library. 2) Ensure that the RDBMS engine is operating properly. |
CLH2057 RQS abnormally closed : rqs_name rqs_no
Type |
ERROR |
Description |
The RQ server process (rqs_name) was closed abnormally. |
Action |
This may be caused by a system issue or a human error during operation. Otherwise, contact the TmaxSoft technical support team. |
CLH2058 server abnormally closed : svr svrno running svc
Type |
ERROR |
Description |
The server process (svr) was closed abnormally while executing the service (svc). |
Action |
1) Check whether the error occurred while writing a related service routine. 2) Ensure that the related library is linked properly. |
CLH2059 remote gateway abnormally closed : rgw_ipaddr
Type |
ERROR |
Description |
A related remote gateway was closed abnormally. |
Action |
1) Check the Tmax status of the node where the related gateway was running. 2) Check for network issues across nodes. |
CLH2060 nclh abnormally closed : nodeno clhno
Type |
ERROR |
Description |
A CLH process (CLH number: clhno) in a multi-node environment (node number: nodeno) was closed abnormally. |
Action |
Refer to the error messages displayed in the console or the log file of a related node to check for the cause of the abnormal closing. For example, the error could occur if the Tmax engine of a related node was closed compulsorily using the -i option. |
CLH2061 client closed : client_index client_ipaddr
Type |
WARNING |
Description |
A related client was terminated abnormally. |
Action |
Confirm that tpend was performed before the client disconnected with Tmax. The client program must be terminated after disconnecting with the Tmax system. The error occurs when the program is closed abnormally or terminated without performing tpend due to a coding error. |
CLH2062 messages dropped while closing client : num
Type |
INFO |
Description |
Messages (num: number of messages) stored while disconnecting with a related client were deleted. |
CLH2065 server MAXQCOUNT reached : svrname
Type |
WARNING |
Description |
The number of client requests in the queue of the server process (svr) exceeded the limit. |
Action |
This is a warning message indicating that the client requests exceeded the MAXQCOUNT limit. Change the MAXQCOUNT value of the server process (svr) in the SERVER section of the configuration file. For more information, refer to Tmax Administration Guide. |
CLH2066 server processes add error : too many FD open fd
Type |
ERROR |
Description |
FD_SETSIZE exceeded the system limit. |
Action |
Refer to /usr/include/limits.h. Contact TmaxSoft. |
CLH2067 server processes add error. No available slot : fd
Type |
WARNING |
Description |
An error occurred while registering a new server process in the Tmax engine. |
Action |
Adjust the number of starting processes not to exceed the MAX value of server processes. |
CLH2068 maximum user connection is reached : licensed_maxuser allocated_maxuser_for_node maxuser_for_clh current_connection_count
Type |
ERROR |
Description |
The number of maximum users exceeded the system limit. |
Action |
Clients exceeding the maximum limit are not served. Increase the MAXUSER value in the DOMAIN section of the configuration file. If the new MAXUSER exceeds the licensed limit, contact the Tmax system administrator to obtain an updated license key. |
CLH2069 tpnotify message error : invalid node number = nodeno
Type |
ERROR |
Description |
An error occurred in a received tpnotify message. |
Action |
Check for a communication interference across nodes. |
CLH2070 tpnotify message error : invalid CLH number = clhno
Type |
ERROR |
Description |
An error occurred in a received tpnotify message. |
Action |
Check for a communication interference across nodes. |
CLH2071 tpnotify message error : invalid client number = clino
Type |
ERROR |
Description |
An error occurred in a received tpnotify message. |
Action |
Check for a communication interference across nodes. |
CLH2072 remote node is down : %s
Type |
ERROR |
Description |
A remote node (nodename) was not activated, or a request was sent to an inactive node. |
Action |
Start the related remote node by using tmboot. |
CLH2073 client add from remote node error
Type |
ERROR |
Description |
Failed to add a new client from a remote node due to a previous error. |
Action |
Refer to the previous error message. |
CLH2074 client add error : errmsg
Type |
ERROR |
Description |
Failed to add a new client from a remote node due to a previous error. |
Action |
Refer to the previous error message. |
CLH2074 failed to add client
CLH2074 failed to add client: two many FD open %d
CLH2074 failed to add client: session init fail
Type |
ERROR |
Description |
Failed to add a new client.
|
Action |
1) Increase the number of files that can be opened by the system. 2) Check the settings for encryption in Tmax Administration Guide. 3) Implement a strategy to reduce the number of simultaneous user accesses, or increase the maximum concurrent user setting. 4) This error may also occur during CLH connections across nodes. Retry the connection at intervals defined by NLIVEINQ. |
CLH2075 NW_HEADER_SIZE (size1) is different from HOST_HEADER_SIZE (size2 )
Type |
FATAL |
Description |
The size of a packet header used ins a Tmax engine is different from that of a packet header used in a network. |
Action |
Contact TmaxSoft. |
CLH2076 from the MINCLH value (val1) and system limitation, node_maxuser = max1 and clh_maxuser = max2 are assumed
Type |
INFO |
Description |
This message indicates the maximum number of concurrent users allowed to connect to a CPU-based license node. |
CLH2077 MINCLH is too small to cover maxuser : max_concurrent_users = max1, assumed_node_maxuser = max2, assumed_clh_maxuser = max3
Type |
ERROR |
Description |
The number of CLH processes is too small compared to the maximum number of concurrent users supported in a Tmax system. The maximum number of concurrent users supported in a node is max2 and each CLH can process max3. |
Action |
Increase the MINCLH value defined in the DOMAIN section in the configuration file. |
CLH2078 receiving fd from CLL error : fdno
Type |
ERROR |
Description |
An error occurred while receiving a file descriptor (fdno) from CLL. |
Action |
Check the named pipe status (Filename) of PATHDIR. If fdno is smaller than -1, refer to the system error message. |
CLH2080 client closed while trying to send data.
Type |
WARNING |
Description |
A Tmax engine sent a response for a client service request, but it was not allowed to respond due to an abnormal disconnection with a related client. The message was ignored. |
Action |
The client that requested the service closed the connection abnormally without waiting for a response. Check the client application code. Check the network status to confirm if a network failure caused the disconnection. |
CLH2081 trying to send to client is blocked : client closed and data dropped.
Type |
WARNING |
Description |
Failed to send a message to a client because a TCP/IP socket was blocked. The related connection was closed because the number of attempts to send a message exceeded a limit defined in a Tmax engine. The message was also discarded. |
Action |
This error may occur when a client connection closed abnormally. If so, refer to the error messages that were output at the time of disconnection. Otherwise, this error resulted from a network failure. Contact a system administrator to solve the problem. |
CLH2082 server process is closed before sending data. Data dropped.
Type |
ERROR |
Description |
A Tmax engine sent a message to a related server process, but it was ignored due to an abnormal disconnection with the related server process. |
Action |
The client that requested the service closed the connection abnormally without waiting for a response. Check the server application code. It may be a connection failure with the UNIX domain socket. If so, contact a system administrator to solve the problem. |
CLH2083 server process closed while trying to send data
Type |
ERROR |
Description |
While a Tmax engine was sending a message to a server process, the related server process was closed abnormally. |
Action |
The related server process was closed abnormally without waiting for a response. Check the server application code. It may be a connection failure with the UNIX domain socket. If so, contact a system administrator to solve the problem. |
CLH2084 trying to send to server is blocked : server closed and data dropped.
Type |
ERROR |
Description |
Failed to send a message to a client because a TCP/IP socket was blocked. The related connection was closed and the message was discarded because the number of attempts to send a message exceeded the limit defined inside the Tmax engine. |
Action |
Check if the server process closed abnormally. If so, refer to the error messages that were output at the time of disconnection. Otherwise, It may be a connection failure with the UNIX domain socket between a Tmax process and a server process. Contact a system administrator to solve the problem. |
CLH2085 tmax process (tproc_no) is closed before sending data. Data dropped.
Type |
ERROR |
Description |
A process connection was closed before a Tmax process ID sent a message to a Tmax process (tproc_no). The message was discarded. |
Action |
If the related process was closed, refer to the error messages output at the time of disconnection. If not, it may be a UNIX domain socket failure. Contact a system administrator to solve the problem. Tmax process ID can be checked using the st -p command. |
CLH2086 tmax process (tproc_no) is closed while processing request.
Type |
ERROR |
Description |
Connection was closed while a Tmax process ID was sending a message to a Tmax process (tproc_no). |
Action |
If the related process was closed, refer to the error messages output at the time of disconnection. If not, it may be a failure of the UNIX domain socket. Contact a system administrator to solve the problem. |
CLH2087 trying to send to tmax process is blocked : Tmax process (procname) closed and data dropped.
Type |
ERROR |
Description |
Failed to send a message to a Tmax process (procname) because a TCP/IP socket was blocked. |
Action |
Check if the Tmax process (procname) was closed abnormally. If so, refer to the error messages output at the time of disconnection. Otherwise, It may be a connection failure between the Tmax process (procname) and a UNIX domain socket. Contact a system administrator to solve the problem. |
CLH2091 node closed while trying to send data
Type |
ERROR |
Description |
Failed to send a message to a remote gateway due to a TCP/IP socket disconnection. |
Action |
The related remote node was closed abnormally or a network failure occurred. If the remote node process was closed abnormally, refer to the output error messages to solve the problem. Otherwise, check the network status. |
CLH2092 trying to send to node is blocked : node closed and data dropped
Type |
ERROR |
Description |
Failed to send a message to a node because a TCP/IP socket was blocked. The related connection was closed because the number of attempts to send a message exceeded the limit defined in a Tmax engine. The message was discarded. |
Action |
Check if the related remote node process was closed abnormally. If so, refer to the error messages output at the time of disconnection. If not, it may be a network failure. Contact a system administrator to solve the problem. |
CLH2093 server queue is purged due to CLH or SVR QTIMEOUT(clhq_timeout): SVRNAME[ServerName] CLID[client_id] REQTIME[request_time]
Type |
INFO |
Description |
The messages accumulated in a server queue were deleted because a defined CLHQTIMEOUT passed. |
Action |
If deleting of a client request queued in a related server queue becomes a problem, increase the CLHQTIMEOUT value or delete the CLHQTIMEOUT item defined in the NODE section in a configuration file. |
CLH2093 server queue is purged due to CLHQTIMEOUT or SVRQTIMEOUT:SVRNAME[%s] CLID[%x]
Type |
ERROR |
Description |
CLHQTIMEOUT or SVRQTIMEOUT specifies the maximum amount of time that messages can wait in a queue. If messages remain in a queue for too long, possibly due to problems with a host or network, CLHQTIMEOUT or SVRQTIMEOUT will determine the time it takes to remove the messages from the queue. Clients will be informed of the removal through TPEQPEUGE(27) so that they can take appropriate action. |
Action |
Ensure that the value for CLHQTIMEOUT or SVRQTIMEOUT is set to a large enough value. |
CLH2094 server queue is purged : ServerName
Type |
INFO |
Description |
Deletes all data accumulated in the queue of a related server process after receiving a command from tmadmin. The command is qp -v svrprocess_name that deleted the waiting data of a server queue in a tmadmin. |
CLH2095 client from remote node add error
Type |
ERROR |
Description |
Failed to receive a client request service from a remote node because too many clients were trying to connect from a remote server. It is not possible to connect additional clients if the number of current connected clients is equal to that of the users available in a system, which is equal to the maxfd value. The value of maxfd can be checked by ulimit -a in the console. |
Action |
Contact a system administrator to modify the maxfd value. If the value cannot be changed, increase the MINCLH/MAXCLH value in a Tmax configuration file. The 'MINCLH * system(maxfd)' value must be equal to or smaller than MAXUSER. |
CLH2096 remote node add error : nodeno = num1, clhno = num2
Type |
ERROR |
Description |
Failed to receive a client request service from a remote node. This error may occur if there are too many concurrent connected clients. |
Action |
Increase the MINCLH/MAXCLH value in the configuration file. Refer to the description for CLH2095 for more detailed information. |
CLH2097 load balancing error : node or network down
Type |
ERROR |
Description |
The load balancing function between nodes could not be performed because the nodes were terminated. |
Action |
Check for a communication interference between nodes. |
CLH2098 remote node is down : nodename
Type |
ERROR |
Description |
The functions of inter-node routing and message transferring could not be performed because nodes were terminated. |
Action |
Confirm that a node (nodename) is operating properly. |
CLH2099 dequeue error. Queue is empty. Ignored : q_kind q_id
Type |
WARNING |
Description |
Failed to read a message in a queue (q_kind) because the queue was empty. |
CLH2100 domain security check fail : username domainpwd encrypted_pwd1 encrypted_pwd2
Type |
ERROR |
Description |
Failed to get domain-leveled access authentication due to an incorrect password. username and domainpwd are the data sent via tpstart function call by a client to confirm a domain-leveled access authentication, and encrypted_pwd1 is the value encrypted by domainpwd. encrypted_pwd2 is a domain-leveled password encrypted by Tmax. Access authentication can be obtained only if encrypted_pwd1 and encrypted_pwd2 are the same. |
Action |
Contact a Tmax system administrator to check the username and domainpwd. |
CLH2101 user authentication check fail : username
Type |
ERROR |
Description |
tx_begin was not called before x_commit or tx_rollback was called. |
Action |
Set a transaction range by performing tx_begin to process a transaction. |
CLH2102 tx_commit(or tx_rollback) issued without tx_begin
Type |
ERROR |
Description |
If a rollback or commit for a transaction was not determined for about two times a transaction timeout period, it will be internally rolled back. This error occurs when there is delay in transaction processing for commits or rollbacks. |
Action |
Check the reason of the delay in transaction processing. |
CLH2103 invalid log Type : log type
Type |
WARNING |
Description |
A message requesting for an invalid log type was received from a UNIX domain socket, but the message was ignored. |
Action |
Check the status of the named pipe of PATHDIR. |
CLH2104 node name not found in config : nodename
Type |
ERROR |
Description |
Failed to find the node name (nodename) of a system in a tmconfig file. |
Action |
Confirm that nodename matches the hostname written in the NODE and SVRGROUP sections of a configuration file. The hostname of the system can be confirmed by the uname -n command. |
CLH2105 service name not found in config : svcname
Type |
ERROR |
Description |
Failed to find a service name (svcname). |
Action |
Check if the tmconfig file was damaged, and then check for the compiled configuration file. |
CLH2106 node is closed : nodeno nodename current_time
Type |
INFO |
Description |
A connection with a node (nodename) was terminated. |
CLH2107 tms for svrgroup not started. No recovery
Type |
ERROR |
Description |
A TMS process for a svrgroup was not performed. |
Action |
Confirm that the server group was defined correctly to use an xa interface in a configuration file. To use an xa interface, xa-related parameters such as DBNAME and OPENINFO must be defined.
|
CLH2108 register request from src error : msg
Type |
ERROR |
Description |
An error occurred in a register request message received by TMM. |
Action |
The msg may read as follows:
|
CLH2111 node is found dead : nodename
Type |
ERROR |
Description |
A remote node (nodename) was processed as terminated because a ping message did not receive any response from it. |
Action |
1) Check if any problem exists in the remote node (nodename) by using the network. 2) When the network is unstable or too slow, increase the NLIVEINQ value in the DOMAIN section of the configuration file. 3) The default value is 30 seconds if the NLIVEINQ value is not set. 4) For more information about the DOMAIN settings, refer to Tmax Administration Guide. |
CLH2112 no such server group id : svgno
Type |
ERROR |
Description |
Failed to find a server group number (svgno) in a shared memory space. |
Action |
Check if the $TMAXDIR/config/tmconfig file is damaged. |
CLH2125 server closed due to I/O error
Type |
ERROR |
Description |
An error occurred in a communication channel to an application server. |
Action |
1) Check if the application server is running correctly. 2) Verify if the application server was abnormally terminated due to an application fault. 3) Check if a stream pipe of $TMAXDIR/ path is damaged. |
CLH2130 env file error : errmsg
Type |
ERROR |
Description |
A syntax error occurred in a configuration file. |
Action |
Correct the syntax error in the NODE or SVRGROUP sections, or the syntax error of the configuration file read through tmaxreadenv. |
CLH2131 invalid conv cd : cd-value
Type |
ERROR |
Description |
An invalid call descriptor value (cd-value) was used in the interactive mode. |
Action |
Check that the cd value used by tpsend or a tprecv was correctly acquired by tpconnect. |
CLH2132 invalid client id : function id-value CLH2132 invalid client id : %s %x
CLH2132 invalid client id : internal %d
Type |
ERROR |
Description |
A client ID (clid) value that was used as a function parameter was invalid. This error occurs when an invalid client is terminated or an unrequested message or event is sent to a client. |
Action |
1) Check that the clid value was correctly acquired by tpgetclid. 2) Ensure that the communication channel is connected to the client. |
CLH2133 invalid message Type : module msg type
Type |
ERROR |
Description |
An invalid message was sent from a module. |
Action |
1) Check that Tmax was installed properly and if each module version matches. 2) Check the communication status across nodes. |
CLH2134 tmax process (name) is abnormally closed
Type |
ERROR |
Description |
A communication fault occurred between Tmax engines. |
Action |
1) Check if the stream pipe files in $TMAXDIR/path are damaged. 2) Refer to the log file in the system log directory. The default is $(TMAXDIR)/log/slog. |
CLH2135 read from Tmax process error
Type |
ERROR |
Description |
A communication fault occurred between Tmax engines. |
Action |
1) Check if the stream pipe files in $TMAXDIR/path are damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2136 send to Tmax process error
Type |
ERROR |
Description |
A communication fault occurred between Tmax engines. |
Action |
1) Check if the stream pipe files in $TMAXDIR/path are damaged. 2) Ensure that the Tmax engine is properly started. |
CLH2141 License file read error: file_name
Type |
ERROR |
Description |
Could not read the license file. |
Action |
1) Install the license file in the correct path: (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
CLH2143 Licensed host not found
Type |
ERROR |
Description |
The host does not have a valid license. |
Action |
Install an updated license file. |
CLH2144 more than licensed number of CPUs are installed.
Type |
ERROR |
Description |
The number of CPUs exceeds the licensed limit. |
Action |
Install an updated license file. |
CLH2145 LiIcense is expired
Type |
ERROR |
Description |
The license has expired. |
Action |
Install an updated license file. |
CLH2146 License check error
Type |
FATAL |
Description |
Failed to check the license. |
Action |
Contact TmaxSoft to obtain or update the license. |
CLH2147 Service Queue (svc_name) is purged
Type |
INFO |
Description |
The service queue was purged by tmadmin. |
CLH2148 your license does not support sub_prod_name
Type |
ERROR |
Description |
The license is invalid. |
Action |
Contact TmaxSoft to obtain or update the license. |
CLH2150 topend conv timeout: client closed
Type |
ERROR |
Description |
A timeout occurred while connecting to a server from the TOPEND conversion system. |
Action |
Ensure that the server is properly running. |
CLH2151 xid(remote_xid) transaction will be rolled back due to transaction timeout
Type |
WARNING |
Description |
The transaction is rolled back due to a timeout. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2152 xid(remote_xid) transaction will be commited internally due to transaction timeout
Type |
WARNING |
Description |
The transaction is committed due to a timeout. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2153 xid(remote_xid) transaction will be pended due to transaction timeout
Type |
WARNING |
Description |
The transaction is pending due to a timeout. The transaction will be processed again or handled through a domain transaction recovery. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2154 xid(remote_xid) transaction will be rolled back due to transaction recovery
Type |
WARNING |
Description |
The transaction is rolled back due to a transaction recovery. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2155 xid(remote_xid) transaction will be commited internally due to transaction recovery
Type |
WARNING |
Description |
The transaction is committed due to a transaction recovery. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2156 xid(remote_xid) transaction will be pended due to transaction recovery
Type |
WARNING |
Description |
The transaction is pending due to transaction timeout. The transaction will be processed again or handled through a domain transaction recovery. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2157 xid(remote_xid) transaction will be rolled back due to closed client(client_id) connection
CLH2157 xid transaction will be rolled back due to closed server(spri) connection
Type |
WARNING |
Description |
The transaction is rolled back due to a closed client or a server connection. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2158 xid(remote_xid) transaction will be commited internally due to closed client(client_id) connection
CLH2158 xid(remote_xid) transaction will be commited internally due to closed server(spri) connection
Type |
WARNING |
Description |
The transaction is committed due to a closed client or a server connection. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2159 xid(remote_xid) transaction will be pended due to closed client(client_id) connection
CLH2159 xid(remote_xid) transaction will be pended due to closed server(spri) connection
Type |
WARNING |
Description |
The transaction is pending due to a closed server or a client connection. The transaction will be processed again or handled through a domain transaction recovery. |
Action |
Check if there is a pending transaction that has the xid in a DB. If such a transaction is found, use the TMS recovery for the pending transaction, or delete the transaction from the DB through a forced rollback. |
CLH2162 [svrname:svcname] call will be failed, it causes a deadlock.
Type |
WARNING |
Description |
When a service calls another service that was included in the same server, it may be deadlocked if the status of all server processes is RUNNING. In this case, a CLH will display a WARNING message and treat it as a failure to prevent a deadlock. |
CLH3017 no such svc : svcname
Type |
WARNING |
Description |
A service name that an application server requested does not exist in a service table. |
Action |
Check if the service was actually provided. If provided, check if the server was built and started up correctly. If not provided, check the client or service that has called the service. |
CLH9990 Current Tmax configuration contains more servers for nodes than current system can support.
Type |
ERROR |
Description |
The current Tmax configuration contains more servers for nodes than the Tmax system can support. |
Action |
Decrease the maximum number of servers allowed in the Tmax system configuration file. |
CLH9990 Current Tmax configuration contains more servers for nodes than current system can support: Supported maximum user per node = %d Supported maximum user per handler = %d
Type |
INFO |
Description |
Shows the number of currently running CLHs, the number of allowable simultaneous accesses per NODE, and the maximum number of allowable accesses per CLH. |
6. CLI Module (CLI2001 ~ )
CLI2008 tpcall reply arrived after timeout. Msg discarded : msgtype seqno
Type |
WARNING |
Description |
A response to tpcall arrived after the defined timeout. The response could not be delivered to the client because processing exceeded the time limit. In this case, the response data is ignored or discarded, but the service is considered processed. For services related to transaction processing, verify the process result. |
Action |
Increase the BLOCKTIMEOUT value. |
CLI2009 server downed while processing client msg
Type |
ERROR |
Description |
The server was shut down while executing a request. |
Action |
Restart the server process using the tmboot -s svrname command, and investigate the server application for possible errors. |
CLI2032 xa_start error : xa_errno tx_errno
Type |
ERROR |
Description |
Executing xa_start for 2-phase commit caused an error. |
Action |
xa_start is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
CLI2033 xa_end error : no xa_start
Type |
WARNING |
Description |
xa_end was ignored because it was called without a preceding xa_start. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. These functions operate as a pair. This error occurs if tx_commit or tx_rollback is called without first performing tx_begin. When such an error occurs, the transaction is rolled back. |
CLI2034 xa_end error : tx_errno
Type |
ERROR |
Description |
Executing xa_end to the RDBMS for 2-phase commit caused an error. |
Action |
xa_end is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
CLI2035 xa error : tx_begin issued in this server, but no commit or rollback
Type |
WARNING |
Description |
tx_begin was called in a service routine, but the routine ended without executing tx_commit or tx_rollback. |
Action |
By default, the Tmax engine performs tx_rollback. Ensure that tx_commit or tx_rollback is called at the appropriate point before executing tpreturn(). |
CLI2036 xa_start is already done
Type |
WARNING |
Description |
xa_start was ignored because it was called multiple times. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. These functions operate as a pair, and nested transactions are not supported. Each transaction must have exactly one tx_begin and one corresponding tx_commit or tx_rollback. |
CLI2037 internal_commit_error : tx_errno
Type |
ERROR |
Description |
An error occurred during the internal execution of tx_commit. |
Action |
Verify that the RDBMS engine is operating correctly. Check tx_errno against the constants starting with TX_ in the xa.h or usrinc/tx.h files in the RDBMS directory. These constants correspond to database errors. Refer to the database error message manual for further details. |
CLI2038 xa_recover error : tx_errno
Type |
ERROR |
Description |
Executing xa_recover for a 2-phase commit caused an error. |
Action |
xa_recover is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
CLI2074 client add error : errmsg
Type |
ERROR |
Description |
An error occurred while adding a new client. |
Action |
Refer to the previous error message. |
CLI3001 sequence number error : expected_seqno received_seqno
Type |
WARNING |
Description |
A client received a message with a wrong sequential number from the Tmax engine. |
Action |
1) If the received seqno is smaller than the expected seqno, check if the previous reply message arrived after the timeout. Adjust BLOCKTIME defined in the DOMAIN section of the configuration file. 2) If the received seqno is greater than the expected seqno, check for a communication interference between the client and server. |
CLI3003 Cannot connect to main server : host_name
Type |
ERROR |
Description |
The client could not connect to the Tmax engine. |
Action |
1) Check that the TMAX_HOST_ADDR and TMAX_HOST_PORT environment variables match host_name in the configuration file. 2) Check the configuration file path used as an argument of the tmaxreadenv() function. 3) Check the network channel between the client and host_name. 4) Check that the Tmax engine was started properly for host_name. |
CLI3004 Cannot connect to backup server : host_name
Type |
ERROR |
Description |
The client could not connect to the Tmax engine. |
Action |
1) Check that the TMAX_HOST_ADDR and TMAX_HOST_PORT environment variables match host_name in the configuration file. 2) Check the TMAX_BACKUP_ADDR and TMAX_BACKUP_PORT variables. 3) Check the configuration file path used as an argument of the tmaxreadenv() function. 4) Check the network channel between the client and host_name. 5) Check that the Tmax engine was started properly for host_name. |
CLI3005 SDL file magic error
Type |
ERROR |
Description |
The magic number in the SDL binary file was invalid. |
Action |
Check that the SDLFILE environment variable points to the correct binary file generated by the sdlc command. |
CLI3006 SDL file read error
Type |
ERROR |
Description |
An error occurred while reading the SDL binary file. |
Action |
Check that the SDLFILE environment variable points to the correct binary file generated by the sdlc command. |
CLI3007 Field key table load error
Type |
ERROR |
Description |
An error occurred while reading the binary fieldkey file. (extension: .fdl or fdl_file) |
Action |
Check that the FDLFILE environment variable points to the correct binary file generated by the fdlc command. |
CLI3008 get-my_nodename error
Type |
ERROR |
Description |
Failed to call getsockname(). |
Action |
Check the system error message. |
CLI3009 Total tp_system_message length is too big
Type |
ERROR |
Description |
The tp_system_message() function contains an invalid argument. |
Action |
Check the arguments of tp_system_message(). |
CLI3010 tmax init error for server
Type |
ERROR |
Description |
Failed to initialize the client library. |
Action |
Check the previous messages. |
CLI4408 FDL magic error : magic_number
Type |
ERROR |
Description |
The magic number of the FDL binary file is invalid. |
Action |
Check whether the FDL binary file (extension: .fdl) is damaged. |
CLI4507 FDL table size is zero : fdl_file
Type |
ERROR |
Description |
An error occurred while reading the binary fieldkey file (extension: . fdl or fdl_file) because the internal table size was 0. |
Action |
Confirm that the fdl_file was created correctly and that the fieldkey definition is correct. |
CLI5001 invalid trace specification
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to Tmax Administration Guide. |
CLI5002 invalid trace specification: spec
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. The specifications contain an invalid value. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to Tmax Administration Guide. |
CLI5003 invalid trace specification, no action spec: spec
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. The action specification is missing. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to 1) Tmax Administration Guide. 2) Check if ulog(message), system(command), trace(trace-spec), and sleep(second) are properly configured in the action specification. |
CLI6022 max tcpcli(num) is over
Type |
ERROR |
Description |
The maximum number of users for the TCP client was exceeded. |
Action |
Increase the max_tcpcli value in the tcpinit function. |
7. CLL Module (CLL2001 ~ )
CLL2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLL2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLL2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLL2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
CLL2045 TMM register error
Type |
ERROR |
Description |
Could not register the CLL process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CLL2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The CLL version does not match TMM. |
Action |
Reinstall the Tmax engine. |
CLL3001 CLH is not ready
Type |
WARNING |
Description |
A new client has connected but cannot use CLH. |
Action |
A small time gap may exist between the currently running CLL and CLH. Clients that attempt to connect during this gap will be denied. Retry the client connection. |
CLL3002 TMM closed
Type |
ERROR |
Description |
The communication channel with TMM was closed. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated (killed), contact the Tmax engineer and provide the service code. |
CLL3003 CLH allocation error
Type |
ERROR |
Description |
A new client has connected but cannot use CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check that the Tmax engine is started properly. |
CLL3004 register to TMM error
Type |
FATAL |
Description |
Could not register the CLL process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
CLL3005 possible network layer malfunction, clearing.
Type |
ERROR |
Description |
The Tmax engine detected a malfunction in the network layer and is performing recovery. |
Action |
Check the network status. |
CLL3006 network recovered.
Type |
INFO |
Description |
The Tmax engine has recovered from the previous network failure. |
Action |
Check the network status. |
CLL3007 send to CLH error
Type |
ERROR |
Description |
Could not send data to the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check that the Tmax engine is started properly. |
CLL3008 remote connection rejected
Type |
WARNING |
Description |
The client access request was rejected due to the ACL settings. |
Action |
Check whether any IP addresses registered in the tmax.deny file under the ${TMAXDIR}/path directory sent connection requests. |
8. DOWN Module (DOWN2001 ~ )
DOWN2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
DOWN2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check that the Tmax engine is properly started. |
DOWN2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check that the Tmax engine is properly started. |
DOWN2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check that the Tmax engine is properly started. |
DOWN2045 TMM register error
Type |
ERROR |
Description |
Could not register the tmdown process to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
DOWN2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The tmdown version does not match TMM. |
Action |
Reinstall the Tmax engine. |
DOWN3001 length of the option is too long
Type |
ERROR |
Description |
An invalid argument was set. |
Action |
Any argument cannot exceed 256 characters. |
DOWN3004 Timeout during tmdown
Type |
ERROR |
Description |
No response was received during tmdown. |
Action |
Check the TMM process status and verify whether multiple tmdown sessions are running simultaneously. |
DOWN3005 request to TMM error
Type |
ERROR |
Description |
Could not send a tmdown request to TMM. |
Action |
Check the TMM process status and verify whether multiple tmdown sessions are running simultaneously. |
DOWN3010 register to TMM error
Type |
ERROR |
Description |
Could not register to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated (killed), contact the Tmax engineer and provide the service code. |
DOWN3011 unregister to TMM error
Type |
ERROR |
Description |
Could not send an unregister request message to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. To unregister both the tmadmin and tmdown processes, send a HUP signal to the TMM process. |
9. FDLC Module (FDLC2001 ~)
FDLC3004 input error: line_num Error_messages
Type |
ERROR |
Description |
A syntax error occurred at a line (line_num). |
Action |
Correct the syntax error. |
FDLC3005 no output generated due to previous errors
Type |
ERROR |
Description |
Could not generate the output due to previous errors. |
Action |
Correct the errors by referring to the preceding error messages. |
FDLC3006 no such field name : field_name
Type |
ERROR |
Description |
An error occurred while updating the FDL file. |
Action |
Recreate the binary FDL file by compiling the original text FDL file. |
FDLC3007 Field name already exists: field_name
Type |
ERROR |
Description |
An error occurred while updating the FDL file. |
Action |
Recreate the binary FDL file by compiling the original text FDL file. |
FDLC3008 Field key already exists: field_key
Type |
ERROR |
Description |
An error occurred while updating the FDL file. |
Action |
Recreate the binary FDL file by compiling the original text FDL file. |
FDLC3009 Field number is too big : field_key, Field number greater than 16777215 is not supported.
Type |
ERROR |
Description |
The number of field keys defined in the FDL file exceeds 16777216. |
Action |
Ensure that the number of field keys is between 0 and 16777215. |
10. RAC Module (RAC2001 ~ )
RAC3001 ADMIN is already connected
Type |
ERROR |
Description |
The user attempted to start multiple tmadmin sessions. |
Action |
1) A user can run only one tmadmin session on each node while monitoring Tmax through RACD. 2) Shut down other running tmadmin sessions that were not terminated due to previous errors. |
RAC3002 ADMIN is not started
Type |
ERROR |
Description |
Could not start the local tmadmin process. |
Action |
Ensure that the TMAXDIR environment file is correctly configured. |
RAC3003 request to tmadmin error
Type |
ERROR |
Description |
The communication channel containing the local tmadmin process was damaged. |
Action |
Check the tmadmin process status. |
RAC3004 command fail %s
Type |
ERROR |
Description |
Failed to execute a system function through a command. |
Action |
Refer to the system error message. |
11. RQS Module (RQS2001 ~ )
RQS2010 RQS connection closed : fd_no
Type |
INFO |
Description |
The connection between CLH and the UNIX domain socket was closed by tmdown. |
RQS2011 TMM connection closed : fd_no
Type |
INFO |
Description |
The connection between TMM and the UNIX domain socket was closed by tmdown. |
RQS2012 register to RQS error : index cpc_no
Type |
FATAL |
Description |
Server processes failed to connect with the Tmax engine due to previous errors. |
Action |
Refer to the preceding error messages. |
RQS2013 register to RQS error : index cpc_no
Type |
ERROR |
Description |
Server processes failed to connect with the Tmax engine due to previous errors. |
Action |
Refer to the preceding error messages. |
RQS2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
RQS2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
RQS2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
RQS2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
RQS2045 TMM register error
Type |
ERROR |
Description |
Could not register the RQS process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
RQS2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The RQS version does not match TMM. |
Action |
Reinstall the Tmax engine. |
RQS2090 trying to send to CLH is blocked
Type |
WARNING |
Description |
Could not send messages to CLH because the TCP/IP socket is blocked. |
Action |
Check whether the CLH was abnormally closed. If so, refer to the error message generated at the time of termination. Otherwise, the issue may be caused by a failed UNIX domain socket connection between the Tmax and CLH processes. Contact the system administrator to resolve the problem. |
RQS3001 register to TMM error
Type |
FATAL |
Description |
Could not register the RQS process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
RQS3002 Corrupt control data
Type |
ERROR |
Description |
Could not register the RQS process to TMM. |
Action |
Check whether the configuration file was modified after TMM started. |
RQS3003 RQ file read error
Type |
FATAL |
Description |
Could not read the RQ file. |
Action |
Check the status of RQ files defined in the FILEPATH settings of the RQ section, and verify available disk space. |
RQS3005 RQ file write error
Type |
FATAL |
Description |
Could not write to the RQ file. |
Action |
Check the status of RQ files defined in the FILEPATH settings of the RQ section, and verify available disk space. |
RQS3007 RQ buffer overflow
Type |
ERROR |
Description |
An RQ buffer overflow occurred because the RQ size exceeded the configured limit. |
Action |
Increase the QSIZE value specified in the RQ section of the configuration file. |
RQS3010 no RQ name is given: -s rqname
Type |
FATAL |
Description |
An invalid argument was detected in the RQ server command line. |
Action |
Do not start or process Tmax engine servers manually. |
RQS3012 Old RQ data file found: rqfilename
Type |
INFO |
Description |
Old RQ files were found during the WARM operation. |
Action |
The BOOT settings in the RQ section of the configuration file specifies how previous RQ files are processed.
|
RQS3013 Corrupt RQ data file: rqfilename
Type |
FATAL |
Description |
A corrupted RQ file was found during the WARM boot operation. |
Action |
Refer to the actions described in the RQS3012 message. |
RQS3014 Old RQ file Info: messages
Type |
INFO |
Description |
Old RQ files were found during the WARM operation. |
RQS3016 Invalid RQ entry
Type |
ERROR |
Description |
A corrupted RQ file was found during the WARM boot operation. |
Action |
Invalid entries exist in previous RQ files. Refer to the actions described in the RQS3012 message. |
RQS3017 RQ file overflow
Type |
FATAL |
Description |
WARM boot failed because old RQ files contained more data than allowed. |
Action |
Increase the QSIZE value in the RQ section of the configuration file. Then, remove the '.old' extension from the backup RQ files and restart the WARM boot operation. |
RQS3018 Analyzing old RQ data file: rqfilename
Type |
INFO |
Description |
Indicates the level 1 of WARM boot. |
Action |
No actions needed. Refer to the RQS3012 message. |
RQS3019 Moving old RQ data to new RQ file : rqfilename
Type |
INFO |
Description |
Indicates the level 2 of WARM boot. |
Action |
No actions needed. Refer to the RQS3012 message. |
RQS3020 Resetting RQ: rqfilename
Type |
INFO |
Description |
Indicates the startup phase of WARM boot. |
Action |
No actions needed. Refer to the RQS3012 message. |
RQS3021 RQ recovery success: rqfilename
Type |
INFO |
Description |
WARM boot completed successfully. |
Action |
No actions needed. Refer to the RQS3012 message. |
RQS3028 internal RQ QFULL (MAX : %d) occurred %d times, this log is written about every %d seconds
Type |
INFO |
Description |
This message indicates the number of TPEQFULL occurrences within the specified period of time. |
Action |
No particular actions needed. |
RQS3029 memory allocation error (size = %d) occurred %d times, this log is written about every %d seconds
Type |
INFO |
Description |
An error occurred while allocating memory up to the specified size. |
Action |
No particular actions needed. |
12. SDLC Module (SDLC2001 ~ )
SDLC3001 FDL file load error
Type |
ERROR |
Description |
Could not load the FDL file to handle the view format. |
Action |
Check the FDLFILE environment variable and create a new FDL file using the fdlc command. |
SDLC3002 type error: type_num
Type |
ERROR |
Description |
The user specified an invalid type name. |
Action |
The following SDL types are available in Tmax.
|
SDLC3010 null value too long (typeno[%d])
Type |
ERROR |
Description |
The input string for the Null field in the view file is too long. |
Action |
The Null field in the view file must be shorter than 32 characters. Reduce the length accordingly. |
SDLC3011 Improper null value(typeno[%d])
Type |
ERROR |
Description |
The Null value in the View file is invalid. |
Action |
Modify the Null value by referring to Tmax Reference Guide. |
13. SVR Module (SVR2001 ~ )
SVR2008 tpcall reply arrived after timeout. Msg discarded : msgtype seqno
Type |
WARNING |
Description |
A response to tpcall arrived after the defined timeout. |
Action |
Increase the BLOCKTIMEOUT value. The response could not be delivered to the client because processing exceeded the time limit. In this case, the response data is ignored or discarded, but the service is considered processed. For services related to transaction processing, verify the process result. |
SVR2009 server downed while processing client msg
Type |
ERROR |
Description |
The server was shut down while executing a request. |
Action |
Restart the server process using the tmboot -s svrname command, and investigate the server application for possible errors. |
SVR2010 CLH connection closed : fd_no
Type |
INFO |
Description |
CLH connection was closed by tmdown. |
SVR2011 TMM connection closed : fd_no
Type |
INFO |
Description |
TMM connection was closed by tmdown. |
SVR2012 register to SVR error : index cpc_no
Type |
FATAL |
Description |
Connections between the Tmax engines and server processes failed due to previous errors. |
Action |
Refer to the previous error messages. |
SVR2013 register to CLH error : index cpc_no
Type |
ERROR |
Description |
Connections between the Tmax engines and server processes failed due to previous errors. |
Action |
Refer to the previous error messages. |
SVR2017 DDR error : subtype or field not found
Type |
FATAL |
Description |
The server was shut down due to previous DDR errors. |
Action |
Refer to the previous DDR error messages. |
SVR2018 DDR bad fieldkey error : fieldkey
Type |
ERROR |
Description |
The field key value for DDR is invalid. |
Action |
Check if the field key value defined in the ROUTING section of the configuration file is appropriate. |
SVR2019 DDR bad fieldkey type error : fieldkey received_fieldkey_type expected_fieldkey_type
Type |
ERROR |
Description |
The field key type for DDR does not match the type specified in the configuration file. |
Action |
Ensure that the DDR field key type defined in the ROUTING section of the configuration file matches the type in the FDL file (with the '.f' extension). Valid field key types are: short, long, int, string. For more information, refer to Tmax Administration Guide. |
SVR2020 DDR SDL field error : field
Type |
ERROR |
Description |
The field for DDR does not exist in the related subtype of the structure-type binary file (extension: .sdl). |
Action |
Ensure that the DDR field defined in the ROUTING section of the configuration file matches the type in the structure-type definition file (extension: .s). If so, recreate the binary structure-type definition file (SDL file). |
SVR2021 DDR SDL subtype error : subtype
Type |
ERROR |
Description |
The structure type for DDR is not defined in the binary file (extension: .sdl). |
Action |
Ensure that the DDR structure type defined in the ROUTING section of the configuration file matches the type in the structure-type definition file (extension: .s). If so, recreate the binary structure-type definition file (SDL file). |
SVR2022 DDR error : no data received in message
Type |
ERROR |
Description |
Data for DDR is missing in the request message. |
Action |
For DDR operations, clients must send data pre-defined in the confguration file. Ensure that the client has sent the relevant data. |
SVR2023 DDR error : offset is not set
Type |
ERROR |
Description |
The offset value for DDR is not set. |
Action |
The offset value is defined in the tmconfig file under the configuration file directory. Check that the configuration file was correctly compiled using the cfl -i command. |
SVR2024 DDR error : data type is not FIELD type
Type |
ERROR |
Description |
The subtype of the related DDR was defined as FIELD in the ROUTING section of the configuration file, but the data received from the client did not use a field-type buffer. |
Action |
Ensure that the client transmission buffer is defined as a field type. |
SVR2025 DDR subtype mismatch : subtype_config subtype_received
Type |
ERROR |
Description |
The subtype name (subtype_config) defined in the SUBTYPE item of the configuration file does not match with the subtype_received of the message received from clients. |
Action |
Match the SUBTYPE in the configuration file with the subtype used by clients. If a structure-type buffer is used, confirm that the structure-type name of the structure-type definition file (extension: .s) matches with that in the configuration file. If so, recreate a structure-type definition binary file (SDLFILE). |
SVR2030 no xa routine is setup
Type |
ERROR |
Description |
Could not configure an XA-related database API routine because the TMS started by the API could not connect to the database. |
Action |
1) Check that the OPENINFO and database connection settings are correctly specified in the SVRGOUP section of the configuration file. 2) Ensure that the XA-related database library is properly linked. The library is normally installed along with the database. If no library is found, verify whether the database was installed correctly. |
SVR2031 xa_open error
Type |
ERROR |
Description |
An error occurred while executing tx_open to connect to an RDBMS. |
Action |
Check that the OPENINFO settings are correctly specified in the SVRGOUP section of the configuration file. Also, ensure that the user ID and password specified in the OPENINFO settings are correct. |
SVR2032 xa_start error : xa_errno tx_errno
Type |
ERROR |
Description |
Executing xa_start for 2- phase commit caused an error. |
Action |
xa_start is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
SVR2033 xa_end error : no xa_start
Type |
WARNING |
Description |
xa_end was ignored because it was called without a preceding xa_start. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. These functions operate as a pair. This error occurs if tx_commit or tx_rollback is called without first performing tx_begin. When such an error occurs, the transaction is rolled back. |
SVR2034 xa_end error : tx_errno
Type |
ERROR |
Description |
Executing xa_end to the RDBMS for 2-phase commit caused an error. |
Action |
xa_end is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
SVR2035 xa error : tx_begin issued in this server, but no commit or rollback
Type |
WARNING |
Description |
tx_begin was called in a service routine, but the routine ended without executing tx_commit or tx_rollback. |
Action |
By default, the Tmax engine performs tx_rollback. Ensure that tx_commit or tx_rollback is called at the appropriate point before executing tpreturn(). |
SVR2036 xa_start is already done
Type |
WARNING |
Description |
xa_start was ignored because it was called multiple times. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. These functions operate as a pair, and nested transactions are not supported. Each transaction must have exactly one tx_begin and one corresponding tx_commit or tx_rollback. |
SVR2037 internal_commit_error : tx_errno
Type |
ERROR |
Description |
An error occurred during the internal execution of tx_commit. |
Action |
Verify that the RDBMS engine is operating correctly. Check tx_errno against the constants starting with TX_ in the xa.h or usrinc/tx.h files in the RDBMS directory. These constants correspond to database errors. Refer to the database error message manual for further details. |
SVR2038 tx_open error : tx_errno xa_errno openinfo
Type |
ERROR |
Description |
An error occurred while executing tx_open to connect to an RDBMS. |
Action |
Check that the OPENINFO settings are correctly specified in the SVRGOUP section of the configuration file. Also, ensure that the user ID and password specified in the OPENINFO settings are correct. |
SVR2039 tx_close error : tx_errno xa_errno closeinfo
Type |
ERROR |
Description |
An error occurred while executing tx_close() to disconnect from an RDBMS. |
Action |
Check if the RDBMS is running correctly. For more information, refer to the database’s error message reference guide. |
SVR2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR2045 TMM register error
Type |
ERROR |
Description |
Could not register the SVR process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
SVR2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The SVR version does not match TMM. |
Action |
Reinstall the Tmax engine. |
SVR2050 service returned without tpreturn : ServiceName
Type |
WARNING |
Description |
The service routine was not terminated with tpreturn. |
Action |
Ensure that the service routine ends with tpreturn or tpforward to return the result message to the client. If not, modify the application code accordingly. |
SVR2051 svrtype mismatch : compiled type = type1, configured type = type2
Type |
ERROR |
Description |
The SVRTYPE defined in the configuration file does not match the actual type of the compiled server. |
Action |
Recompile the configuration file using cfl -i, then run the gst command. Delete any existing objects before compiling the new file. |
SVR2052 invalid cd : cd
Type |
ERROR |
Description |
An invalid call descriptor (cd) value was used in an asynchronous environment. |
Action |
Verify whether the cd value used by tpgetrply() was correctly obtained by tpacall(). |
SVR2061 client closed : clientid fd
Type |
ERROR |
Description |
The work thread of the client (clientid) was disconnected from the remote node. |
SVR2062 messages dropped while closing client : num
Type |
ERROR |
Description |
Messages (num) were deleted while disconnecting related clients. |
SVR2085 tmax process (proc) is terminated before sending data. Data dropped
Type |
ERROR |
Description |
The Tmax process (ID) was disconnected before sending a message to the Tmax process (proc). The message was dropped. |
Action |
If the related process was terminated, refer to the error message generated at the time of termination. Otherwise, the issue may have been caused by a UNIX domain socket connection failure. Contact the system administrator to resolve the issue. The Tmax process ID can be retrived using the st –p command in tmadmin. |
SVR2086 tmax process (proc) is terminated while processing request.
Type |
ERROR |
Description |
The Tmax process (ID) was disconnected before sending a message to the Tmax process (proc). The message was dropped. |
Action |
If the related process was terminated, refer to the error message generated at the time of termination. Otherwise, the issue may have been caused by a UNIX domain socket connection failure. Contact the system administrator to resolve the issue. |
SVR2090 failed to send to CLH
Type |
ERROR |
Description |
Could not send data to the CLH process. |
Action |
Check if the stream pipe in $TMAXDIR/path has been damaged. Ensure that the Tmax engine is properly running. |
SVR3001 sequence number error : expected_seqno received_seqno
Type |
WARNING |
Description |
A client received a message with a wrong sequential number from the Tmax engine. |
Action |
1) If the received seqno is smaller than the expected seqno, check if the previous reply message arrived after the timeout. Adjust BLOCKTIME defined in the DOMAIN section of the configuration file. 2) If the received seqno is greater than the expected seqno, check for a communication interference between the client and server. |
SVR3002 register to TMM error
Type |
FATAL |
Description |
Could not register the application server process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Verify whether the processes are running up to the maximum number. (Check the MAX setting in the SERVER section of the configuration file.) 3) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
SVR3003 cannot find service name (svc_name) in svc_table.
Type |
ERROR |
Description |
The application server received a request for a service that was not found in the service table. |
Action |
1) Check that the svc_name is defined in the SERVICE section of the configuration file. 2) Recompile the application after running cfl and then gst. |
SVR3004 Max file open reached.
Type |
ERROR |
Description |
Could not open the file or socket due to system restrictions. |
Action |
Use ulimit or unlimit to increase the maximum allowable number of file descriptors to open. For smaller configurations, set 1024. For larger configurations, set 4096. For more information, contact the system administrator. |
SVR3005 CLH connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR3007 Field key table loading error
Type |
ERROR |
Description |
An error occurred while reading the binary field key file (extension: .fdl or fdl_file). |
Action |
Check that the environment variable FDLFILE specifies a valid binary file compiled using the fdlc command. |
SVR3008 get-my_nodename error
Type |
ERROR |
Description |
Calling getsockname() failed. |
Action |
Check the system error message. |
SVR3009 Total tp_system_message length is too big
Type |
ERROR |
Description |
tp_system_message() contained an invalid argument. |
Action |
Check the arguments in tp_system_message(). |
SVR3010 tmax init error for server
Type |
ERROR |
Description |
Failed to initialize a client library. |
Action |
Check the preceding error messages. |
SVR3011 3011 failed to send to TMM
Type |
FATAL |
Description |
Could not send data to the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR3012 failed to read from TMM
Type |
FATAL |
Description |
An error occurred while receiving data from the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR3013 No such svc (svc_name) in shared memory.
Type |
ERROR |
Description |
The application server attempted to register a non-defined service name. |
Action |
1) Check the svc_name in the SERVICE section of the configuration file. 2) Recompile the application after running cfl and then gst. |
SVR3014 Invalid arguments in CLOPT string : clopt_string
Type |
ERROR |
Description |
The CLOPT setting contains invalid strings. |
Action |
Check the CLOPT setting in the SERVER section. User-defined arguments must be placed after the delimiter "--". |
SVR3015 CLOPT -e/-o flag processing errors.
Type |
ERROR |
Description |
Could not convert an argument with the -e or -o flag in the CLOPT setting into a valid file name. |
Action |
Check the CLOPT setting in the SERVER section. The argument following the -e or -o flag must be a valid file name. The following macros can be used when specifying arguments for the -e or -o option:
|
SVR3016 SVR (svr_name) tpsvrinit fail.
Type |
INFO |
Description |
The tpsvrinit() routine for svr_name returned a negative value. |
Action |
Check the application code that implements the tpsvrinit() function. |
SVR3017 no such svc: svc_name
Type |
ERROR |
Description |
The application server received a request for a service that was not found in the service table. |
Action |
1) Verify that svc_name is defined in the SERVICE section of the configuration file. 2) Recompile the application after running cfl and then gst. |
SVR3018 service returned without tpreturn : svc_name
Type |
ERROR |
Description |
The service (svc_name) was implemented without terminating via tpreturn(). |
Action |
Ensure that all services are properly terminated using tpreturn(). |
SVR3019 tpreturn met with outstanding reply
Type |
ERROR |
Description |
The server terminated the service before completing a request that was in progress. |
Action |
tpacall() and tpgetrply() are used as a pair. Ensure that any interactive service completes before calling tpreturn(). |
SVR3022 SVR (svr_name) is down due to tpreturn(TPEXIT).
Type |
INFO |
Description |
The server was terminated by tpreturn(TPEXIT). If RESTART=Y is set in the SERVER section of the configuration file, TMM automatically restarts the server. |
Action |
No actions needed. The server is restarted automatically by TMM. |
SVR3023 SVR (svr_name) is down due to tpreturn(TPDOWN).
Type |
INFO |
Description |
The server was terminated by tpreturn (TPDOWN). Even if RESTART=Y is set in the SERVER section of the configuration file, the server is not restarted. |
Action |
No actions needed. The server is not restarted. |
SVR3024 tpforward met with outstanding reply.
Type |
ERROR |
Description |
The server terminated the service before completing a request that was in progress. |
Action |
tpacall() and tpgetrply() are used as a pair. Ensure that any interactive service completes before calling tpreturn(). |
SVR3025 send error in tpforward.
Type |
ERROR |
Description |
Could not send a tpforward request to CLH. |
Action |
Check connection between the server and CLH. |
SVR3026 no such product name (name) defined in config.
Type |
ERROR |
Description |
The application server attempted to register a non-defined product name. |
Action |
1) Check the PRODNAME setting in the SVRGROUP section. 2) Recompile the application after running cfl and gst. |
SVR3027 Function register error.
Type |
ERROR |
Description |
The Tmax engine failed to record the function. |
Action |
1) Check the FUNC section in the configuration file. 2) Recompile the application after running cfl and gst. |
SVR3028 no such function : func_name.
Type |
ERROR |
Description |
The application server received a request for a function that was not found in the function table. |
Action |
1) Check the func_name in the FUNC section of the configuration file. 2) Recompile the application after running cfl and gst. |
SVR3029 Output area length error.
Type |
ERROR |
Description |
The client requested a service with an invalid output workspace size. |
Action |
Check the argument passed to tp_client_send(). |
SVR3031 cannot find entry (func_name) in function table.
Type |
ERROR |
Description |
The application server received a request for a function that was not found in the function table. |
Action |
1) Check the func_name in the FUNC section of the configuration file. 2) Recompile the application after running cfl and gst. |
SVR3032 service timeout error : ServiceName.
Type |
ERROR |
Description |
The service could not be completed within the specified timeout period. |
Action |
Increase the SVCTIME value for the service (ServiceName) in the configuration file. If the SVCTIME value is already sufficient, investigate potential inefficiencies in the service routine. |
SVR3032 service timeout error : ServiceName (during trace or adminapi, spr will abort)
Type |
ERROR |
Description |
A service timeout occurred while sending the trace log. As a result, the service could not be recorded in the SLOG and was abnormally terminated after logging the information to STDERR. |
Action |
Increase the SVCTIME value for the service (ServiceName) in the configuration file. |
SVR3033 service registration failure
Type |
ERROR |
Description |
An error occurred while registering a service to the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
SVR3041 fail to tpadvertise: svc(svcname) in svr(svrname:spri), mysvri(spri)
Type |
ERROR |
Description |
Failed to register the service name (svcname) with tpadvertise because it is already registered by another server process (svrname:spri). |
Action |
Ensure that the service name (svcname) is unique within the server. |
SVR3042 xid is invalid (0-0-0), svc(svcname)
Type |
ERROR |
Description |
The transaction (XID) failed because xa_start was called with an unissued identifier '0-0-0' for an unknown reason. |
Action |
For the service requester, tpcall or tpgetrply will fail with tperrno set to TPETRAN and tpurcode set to TX_ESYSTEM. |
SVR3129 svr is in abnormal state
Type |
FATAL |
Description |
In a TCS-type server, an abnormal error occurs 64 consecutive times while the server is in a pending state (not in a running state). After this error is logged, the server shuts down abnormally. If a service is successfully completed before this error occurs, the accumulated count of previous errors is reset. |
Action |
Collect the debug logs and contact the system administrator. |
SVR4408 FDL magic error : magic_number.
Type |
ERROR |
Description |
The magic number for the binary FDL file is incorrect. |
Action |
Verify whether the binary FDL file (extension : .fdl) has been damaged. |
SVR4507 FDL table size is zero : fdl_file
Type |
ERROR |
Description |
An error occurred while reading the binary field key file ( extension: .fdl or fdl_file) because the size of the internal table in the file was 0. |
Action |
Check that the fdl_file was correctly compiled and that the field key configuration file was properly written. |
SVR5001 Invalid trace specification
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to Tmax Administration Guide. |
SVR5002 Invalid trace specification : spec
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. The specifications contain an invalid value. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to Tmax Administration Guide. |
SVR5003 Invalid trace specification, no action spec : spec
Type |
ERROR |
Description |
An error occurred while configuring the Tmax Trace Specifications. The action specification is missing. |
Action |
Check if the environment variable TMAX_TRACE is correctly configured by referring to Tmax Administration Guide. Check if ulog(message), system(command), trace(trace-spec), and sleep(second) are properly configured in the action specification. |
SVR5005 read error : rconn closed
Type |
ERROR |
Description |
Failed to receive data due to a disconnection from the remote node in an RDP (Realtime Data Processor) environment. |
Action |
Check for any communication failures with the RDP client. |
SVR5006 invalid msg from fd = fd_no
Type |
ERROR |
Description |
An abnormal message was received from a channel with the fd_no value. |
Action |
Check for any communication failures with the RDP client. |
SVR5007 read error : retval size
Type |
ERROR |
Description |
Failed to receive data from the RDP server. |
Action |
1) Check if the size is available. 2) Check for any communication failures with the RDP server. 3) If retval is a negative value, refer to the system error message. |
SVR5009 invalid msg(msgtype, length) from client
Type |
ERROR |
Description |
An abnormal message was received from the RDP client. |
Action |
Check for any communication failures with the RDP client. |
SVR5010 write error: rconn(client_id) closed
Type |
ERROR |
Description |
Failed to receive data due to a disconnection from the remote node in an RDP (Realtime Data Processor) environment. |
Action |
Check for any communication failures with the RDP client. |
SVR5011 write timeout error: rconn closed
Type |
ERROR |
Description |
Failed to send a message to the RDP client due to a timeout, and the remote connection was closed. |
Action |
Check for any communication failures with the RDP client. |
SVR5012 recv_fd error : errno
Type |
ERROR |
Description |
Failed to receive FD (File Descriptor). |
Action |
Refer to the system error message. |
SVR5013 send_fd error : errno
Type |
ERROR |
Description |
Failed to send FD (File Descriptor). |
Action |
Refer to the system error message. |
SVR5100 rcah is not ready yet
Type |
WARN |
Description |
The RCA handler is not available yet. |
Action |
Wait for the RCA handler to be ready. |
SVR5101 unable to find a idle rcah
Type |
ERROR |
Description |
No available handlers. |
Action |
Control incoming requests or increase the number of RCA handlers. |
SVR5102 failed to add rcah. No available slot : fd
Type |
ERROR |
Description |
An error occurred while registering a new RCA handler. |
Action |
Check whether the number of running RCA handlers reached the maximum limit. |
SVR5103 unable to start rcah
Type |
FATAL |
Description |
Failed to start the RCA handler within the specified time limit. |
Action |
Ensure that the handler is properly running and check for any interferences in communication between the RCA listener and the RCS handler. |
SVR5104 shared memory version mismatch (version1:version2)
Type |
ERROR |
Description |
The Tmax shared memory version mismatches. |
Action |
Check the version of the Tmax server library. |
SVR5108 failed to register to rcal
Type |
FATAL |
Description |
Failed to register the RCA listener. |
Action |
Check whether the stream pipe in $RCA_DIR is damaged and confirm that the RCA listener is properly running. |
SVR6001 thread creation failure
Type |
FATAL |
Description |
An error occurred while creating a thread. |
Action |
Refer to the system error message. |
SVR6002 thread termination failure
Type |
ERROR |
Description |
Failed to terminate the work thread for the RCA handler. |
Action |
Refer to the system error message. |
SVR6003 no available worker thread
Type |
ERROR |
Description |
No work thread available for the RCA handler. |
Action |
Control incoming requests or increase the number of work threads. |
SVR6015 recursive call timeout : svc
Type |
ERROR |
Description |
A timeout occurred during a recursive tpcall for a service (svc). |
Action |
Increase the SVCTIME value for the service (ServiceName) in the configuration file. If the SVCTIME value is already sufficient, investigate potential inefficiencies in the service routine. |
SVR6020 mutex init error
Type |
ERROR |
Description |
Failed to initialize mutex for synchronizing thread processes. |
Action |
Refer to the system error message. |
SVR6021 semaphore init error
Type |
ERROR |
Description |
Failed to initialize semaphore for synchronizing processes. |
Action |
Refer to the system error message. |
SVR6100 remote gateway disconnedted, messages of tpacall with TPNOREPLY discarded
Type |
INFO |
Description |
Messages with TPNOREPLY set are removed from the queue because the remote gateway channel terminated. |
SVR6101 relay service not found
Type |
ERROR |
Description |
No relay services available to forward the response message received from the remote gateway. |
Action |
Refer to Tmax Gateway Guide (TCP/IP). |
SVR6102 remote socket closed
Type |
ERROR |
Description |
The remote gateway socket was closed. |
Action |
Check the remote gateway or the network status. |
SVR6103 remote gateway closed : ipaddr
Type |
ERROR |
Description |
The remote gateway with the IP address (ipaddr) was disconnected. |
Action |
Check the remote gateway or the network status. |
SVR6104 user routine detect a index th channel failure
Type |
ERROR |
Description |
A channel (index) failure was detected in the user-defined function chk_pong_msg(). The channel was forcibly terminated. |
Action |
Check the remote gateway or the network status. |
SVR6105 user routine error: funcname
Type |
ERROR |
Description |
An error occurred in a user-defined function (funcname). |
Action |
Review the function logic and correct any errors. |
SVR6201 gateway number is null
Type |
ERROR |
Description |
The gateway number was not specified when updating the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6202 remote server address is null
Type |
ERROR |
Description |
The address of a remote node was not specified when updating the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6203 remote portno is null
Type |
ERROR |
Description |
The port of a remote node was not specified when updating the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6204 input channel is null
Type |
ERROR |
Description |
The number of input channels was not specified when updating the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6205 output channel is null
Type |
ERROR |
Description |
The number of output channels was not specified when updating the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6206 remote connection rejected peer ip[peer IP] port[peer portno] in my port[my portno] at [service code]
Type |
ERROR |
Description |
Failed to connect to a remote node. The service code is provided for the developer to analyze the issue. |
Action |
Check the remote gateway or the network status. |
SVR6208 invalid gateway option
Type |
FATAL |
Description |
An invalid option was used when configuring CLOPT parameters for the gateway. |
Action |
Review the CLOPT parameter options configured for the TCPGW in the SERVER section of the Tmax configuration file. |
SVR6209 line num is too long : length
Type |
ERROR |
Description |
A line in the configuration file for multi-remote node connections exceeded the maximum allowed length of 255 characters. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6210 channel not found
Type |
ERROR |
Description |
Could not find the remote channel settings in the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6211 invalid channel configuration
Type |
FATAL |
Description |
An invalid setting was detected in the configuration file for multi-remote node connections. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP). |
SVR6212 remote connect error, we’ll retry to connect when request arrives
Type |
ERROR |
Description |
If a request message is received, a reconnection attempt is made immediately; otherwise, reconnection is attempted periodically. |
Action |
Check the remote gateway or the network status. |
SVR6213 remote connection fault : ipaddr
Type |
ERROR |
Description |
A failure was detected in the connection with the remote node (ipaddr). Consequently, all the associated channels were closed. |
Action |
Check the remote gateway or the network status. |
SVR6214 handler listen error
Type |
FATAL |
Description |
The listener for the TCP/IP thread gateway failed to accept connections for the handler. |
Action |
Check if the stream pipe in $TMAXDIR/path has been damaged. |
SVR6215 service is null
Type |
ERROR |
Description |
The client ID was not specified in the configuration file for the TCP/IP thread gateway. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP Thread). |
SVR6216 client not defined in configuration : ipaddr
Type |
WARN |
Description |
Could not retreive information about the client with the specified IP address (ipaddr) from the TCP/IP thread gateway configuration file. |
Action |
Review the configuration file by referring to Tmax Gateway Guide (TCP/IP Thread). |
SVR6217 unable to find a idle handler
Type |
ERROR |
Description |
No available handler for the TCP/IP thread gateway listener. |
Action |
Control incoming requests or increase the number of available handlers. |
SVR6218 failed to notify to listener : portno
Type |
ERROR |
Description |
Failed to notify the TCP/IP thread gateway listener. |
Action |
Check if the stream pipe in $TMAXDIR/path has been damaged. |
SVR6219 failed to register to listener : svri
Type |
FATAL |
Description |
Failed to register to the TCP/IP thread gateway listener. |
Action |
Check if the stream pipe in $TMAXDIR/path has been damaged. |
SVR6220 remove client : clientid fd
Type |
INFO |
Description |
The work thread of the client (clientid) is terminated by the TCP/IP thread gateway handler. |
Action |
No actions needed. |
SVR6221 failed to connect to listener
Type |
FATAL |
Description |
Failed to connect with the TCP/IP thread gateway listener. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the listener is running properly. |
SVR6222 already used client : clientid status
Type |
INFO |
Description |
The client ID is already in use. |
Action |
Check whether the client ID is duplicated in the configuration file. |
SVR6225 user routine error: undefined callback
Type |
ERROR |
Description |
No callback functions found. |
Action |
Review the application files by referring to Tmax Gateway Guide (TCP/IP). |
SVR6226 UID(%d) range is exceeded in callback
Type |
ERROR |
Description |
The uid field value in the info structure of the callback function exceeded the allowed length. |
Action |
Check the uid field in the callback function within the application. |
SVR6226A UID(%d) range is exceeded in callback, Valid range = (MAX : %d)
Type |
ERROR |
Description |
The uid field value in the info structure of the user-defined callback function registered in CUSTOM_GATEWAY exceeded the allowed length. |
Action |
Refer to the range of valid values and review the code that sets the uid field in the callback function. |
SVR6227 user routine error: returned size(%d) is larger than its orginal size(%d) in check_end_msg
Type |
ERROR |
Description |
The data returned exceeded the size of the data received from check_end_msg(). As a result, it was treated as an error. |
Action |
Review the check_end_msg() function in the application. |
SVR6228 msg discarded due to user routine error in callback channel_id : data_size
Type |
ERROR |
Description |
The message with data size (data_size) received on channel_id in the TCP/IP gateway callback function was treated as an error due to invalid data. |
Action |
1) If the callback function is check_end_msg(), the returned data is larger than the data received. Review the function for potential issues. 2) If the callback function is get_msg_info(), the value assigned to the uid field in the info structure exceeds the allowed length. Review the function for potential issues. |
14. TIP Module (TIP3001 ~ )
TIP3001 failed to register to TMM
Type |
ERROR |
Description |
Failed to register with the TMM process due to a network failure or the TMM process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3003 CLH read error
Type |
ERROR |
Description |
CLH was disconnected due to a network failure or because the CLH process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3004 CLH write error
Type |
ERROR |
Description |
CLH was disconnected due to a network failure or because the CLH process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3006 failed to write to CLH
Type |
ERROR |
Description |
Failed to send messages to the CLH process due to a network failure, or CLH being overloaded, or CLH not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3008 failed to register to CLH
Type |
ERROR |
Description |
Failed to register with the CLH process due to a network failure or because the CLH process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3010 failed to advertise to TMM
Type |
ERROR |
Description |
Failed to advertise TIPSVC to the TMM process due to a network failure or because the TMM process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
TIP3013 svc register error
Type |
ERROR |
Description |
Failed to register TIPSVC to the TMM process due to a network failure or because the TMM process is not running properly. |
Action |
1) Check the network status. 2) Review the Tmax system environment and processes. 3) Contact the Tmax system technical support team. |
15. TLM Module (TLM3001 ~ )
TLM3001 failed to register to TMM
Type |
FATAL |
Description |
Could not register the TLM process to TMM. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TLM3002 TMM closed
Type |
ERROR |
Description |
The communication channel with TMM was closed. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
TLM3003 CLH read error
Type |
ERROR |
Description |
Could not receive data from CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
TLM3004 CLH write error
Type |
ERROR |
Description |
Could not send data to CLH. Check if the stream pipe in $TMAXDIR/path has been damaged. Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
TLM3006 failed to write to CLH
Type |
ERROR |
Description |
Could not send data to CLH. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the TMM process status. If the TMM process was not intentionally terminated, contact the Tmax engineer and provide the service code. |
TLM3007 failed to register to CLH
Type |
ERROR |
Description |
Could not register the TLM process to CLH. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
TLM3008 failed to register to CLH
Type |
FATAL |
Description |
Could not register the TLM process to CLH. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
TLM3009 failed to connect to CLH
Type |
ERROR |
Description |
Could not establish a communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TLM3010 failed to register to CLH (phase 1)
Type |
ERROR |
Description |
Could not establish a communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TLM3011 failed to register to CLH (phase 2)
Type |
ERROR |
Description |
Could not establish a communication channel with the CLH process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TLM3018 CLH connection closed
Type |
ERROR |
Description |
The communication channel with CLH was lost. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Check the CLH process status. If the CLH process was not intentionally terminated, contact a Tmax engineer and provide the service code. |
TLM3103 domain(gwname) transaction pending : xid remote_xid
Type |
WARN |
Description |
The domain transaction has entered a pending state. It will be processed after the domain transaction recovery completes. |
TLM3104 domain(gwname) transaction will be recovered : COMMIT/ROLLBACK xid remote_xid svgno
Type |
WARN |
Description |
The pending domain transaction will be recovered by either committing or rolling it back. |
TLM3105 transaction pending : xid remote_xid
Type |
WARN |
Description |
The domain transaction has entered a pending state. It will be processed after the domain transaction recovery completes. |
TLM3106 transaction will be recovered : COMMIT/ROLLBACK xid remote_xid svgno
Type |
WARN |
Description |
The pending domain transaction will be recovered by either committing or rolling it back. |
TLM3107 CLH in a local node is restarted : clhno
Type |
WARN |
Description |
The CLH process on the local node has been restarted. TLM will recover transactions for CLH on the reconnected node. |
TLM3108 CLH in a remote node is restarted : nodeno clhno
Type |
WARN |
Description |
The CLH process on the remote node has been restarted. TLM will recover transactions for CLH on the reconnected node. |
16. TMD Module (TMD2001 ~ )
TMD3001 tpstart error: tperrno_string.
Type |
ERROR |
Description |
tpstart() failed. |
Action |
Fix the errors by referring to tperrno_string. |
TMD3002 file read error.
Type |
ERROR |
Description |
An error occurred while reading the input file. |
Action |
Check the input script file for errors. |
TMD3003 call type error : call_name.
Type |
ERROR |
Description |
Invalid call type. |
Action |
TMD supports the following call types:
|
TMD3004 buf type error : buf_type.
Type |
ERROR |
Description |
Invalid buffer type. |
Action |
Check the configured buffer type. The following types are supported:
|
TMD3005 sub type error : sub_type_name.
Type |
ERROR |
Description |
Invalid SUB type. |
Action |
The SUB type name must be defined in the SDLFILE. |
TMD3006 flags error : flag_name.
Type |
ERROR |
Description |
Invalid flag. |
Action |
Check the configured flag. It must be one of the following:
|
TMD3007 input data error : error_messages.
Type |
ERROR |
Description |
An error was detected in the input script. |
Action |
Correct the error by referring to the error_message. |
TMD3011 failed to read %s /* input string */
Type |
ERROR |
Description |
An invalid input value was specified in the security configuration. |
Action |
Verify and correct the input values in the security configuration. |
TMD3021 tpalloc error : /* tperrno_string */
Type |
ERROR |
Description |
tpalloc() for service call failed. |
Action |
Refer to Tmax Reference Guide. |
TMD3022 tpset_timeout error: %s /* tperrno_string */
Type |
ERROR |
Description |
tpset_timeout() for timeout setting failed. |
Action |
Refer to Tmax Reference Guide. |
TMD3030 tx_begin error: %d /* tx error */
Type |
ERROR |
Description |
tx_begin() for transaction processing failed. |
Action |
Refer to Tmax Reference Guide. |
TMD3031 tx_commit error: %d /* tx error */
Type |
ERROR |
Description |
tx_commit() for service transaction processing failed. |
Action |
Refer to Tmax Reference Guide. |
TMD3032 tx_rollback error: %d /* tx error */
Type |
ERROR |
Description |
tx_set_transaction_timeout() for transaction processing failed. |
Action |
Refer to Tmax Reference Guide. |
TMD3021 tpalloc error: tperrno_string
Type |
ERROR |
Description |
tpalloc() failed. |
Action |
Fix the errors by referring to tperrno_string. |
TMD3026 call_name error : tperrno_string.
Type |
INFO |
Description |
The service request failed. |
Action |
Fix the errors by referring to tperrno_string. |
17. GATEWAY Module (GATEWAY2001 ~ )
GATEWAY2010 TMGW connection closed : fd_no.
Type |
INFO |
Description |
The connection between CLH and the UNIX domain socket was closed by tmdown. |
GATEWAY2011 TMM connection closed : fd_no.
Type |
INFO |
Description |
The connection between TMM and the UNIX domain socket was closed by tmdown. |
GATEWAY2012 register to CLH error : index cpc_no
Type |
FATAL |
Description |
Connections between the Tmax engines and server processes failed due to previous errors. |
Action |
Refer to the previous error message. |
GATEWAY2013 register to CLH error : index cpc_no
Type |
ERROR |
Description |
Connections between the Tmax engines and server processes failed due to previous errors. |
Action |
Refer to the previous error message. |
GATEWAY2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2045 TMM register error
Type |
ERROR |
Description |
Could not register the Tmax gateway process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
GATEWAY2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The Tmax gateway version does not match TMM. |
Action |
Reinstall the Tmax engine. |
GATEWAY2059 remote gateway connected : %s:%d /* ipaddr, port */
Type |
INFO |
Description |
Successfully connected to the remote gateway. |
GATEWAY2061 remote gateway(%s) closed : %s:%d /* channel type(OUTCH:INCH), ipaddr, port */
Type |
INFO |
Description |
Successfully disconnected from the remote gateway. |
GATEWAY2062 remote gateway closed
Type |
INFO |
Description |
Disconnected from the remote gateway. The first argument, if provided, is the IP address; the second argument, if provided, is the port number. |
Action |
Check whether the remote node has been shut down. |
GATEWAY2063 messages are dropped while closing remote gateway : num
Type |
INFO |
Description |
Stored messages (num) were discarded while disconnecting from the associated remote gateway. |
GATEWAY2087 trying to send to tmax process is blocked : Tmax process (procname) closed and data dropped.
Type |
ERROR |
Description |
Sending messages to the Tmax process (procname) was blocked because the TCP/IP socket was unavailable. The connection was closed after exceeding the maximum number of send retries specified in the Tmax engine. The messages have been discarded. |
Action |
Check whether the Tmax process (procname) was shut down abnormally. If so, refer to the error messages generated at the time of disconnection. Otherwise, the issue may be due to the connection between the Tmax process (procname) and the UNIX domain socket. Contact the system administrator to resolve the problem. |
GATEWAY2087 failed to send to CLH
Type |
ERROR |
Description |
Failed to send messages to the CLH process due to a network failure, or CLH being overloaded or CLH not running properly. |
Action |
Check the network status and review the Tmax system environment and processes. If the problem persists, contact the Tmax system technical support team. |
GATEWAY2088 remote gateway is closed before sending data. Data dropped : rgw_ipaddr
Type |
ERROR |
Description |
Sending messages to the remote gateway (IP address = rgw_ipaddr) was blocked due to a disconnection between the gateway and the TCP/IP socket. The messages have been discarded. |
Action |
Check whether the corresponding gateway process was shut down abnormally or if a network error occurred. If the gateway process was shut down abnormally, refer to the corresponding error messages. Otherwise, verify the network status. |
GATEWAY2089 trying to send to remote gateway is blocked : remote gateway (rgw_ipaddr) closed and data dropped.
Type |
ERROR |
Description |
Sending messages to the Tmax process (IP address = rgw_ipaddr) was blocked because the TCP/IP socket was unavailable. The connection was closed after exceeding the maximum number of send retries specified in the Tmax engine. The messages have been discarded. |
Action |
Check whether the corresponding gateway process was shut down abnormally. If so, refer to the error messages generated at the time of disconnection. Otherwise, verify the network status. |
GATEWAY2124 reply to the closed remote gateway. Message dropped
Type |
WARNING |
Description |
The remote gateway was disconnected before sending the message. The message has been discarded. |
GATEWAY2135 read from Tmax process error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2136 send to Tmax process error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
GATEWAY2138 fail to get pending list
Type |
ERROR |
Description |
Failed to retrieve the pending list from CLH. |
Action |
Contact the Tmax system technical support team. |
GATEWAY3004 No gateway name (-s gwname) is given
Type |
FATAL |
Description |
An invalid argument was detected on the command line of the Tmax gateway server. |
Action |
Tmax engine servers must not be operated manually. |
GATEWAY3005 gateway name (-a domname) not defined
Type |
ERROR |
Description |
The -a option was not specified in the CLOPT setting for TUXGW. |
Action |
Set the -a option for the CLOPT setting with the name configured in Tuxedo. |
GATEWAY3007 register to TMM error
Type |
FATAL |
Description |
Could not register the Tmax gateway process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
GATEWAY3008 overlapped connection from remote gateway ipaddr:port
Type |
ERROR |
Description |
A duplicate connection attempt from ipaddr:port to an already connected Tuxedo gateway (TUXGW) was blocked. |
Action |
Review the configuration for any elements that can cause duplicate connection attempts. |
GATEWAY3009 overlapped connection from remote gateway (unknown host)
Type |
ERROR |
Description |
A duplicate connection attempt from an unknown address to an already connected Tuxedo gateway (TUXGW) was blocked. |
Action |
Review the configuration for any elements that can cause duplicate connection attempts. |
GATEWAY3010 connection from remote gateway error
Type |
ERROR |
Description |
An error occurred while receiving a connection request from a remote gateway. |
Action |
This error may be caused by too many connection requests from other domains. A Tmax gateway supports only one-to-one connections; multiple gateways cannot connect to a single remote gateway. Review the gateway configuration for all Tmax domains. |
GATEWAY3011 Not found such gateway name: gwname
Type |
FATAL |
Description |
The gateway name is not defined in the configuration file. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
GATEWAY3012 reply to the closed remote gateway
Type |
ERROR |
Description |
The remote gateway was disconnected before sending a message. No response message was received. |
Action |
1) Check the remote domain status. 2) Check the network connection status. |
GATEWAY3030 failed to check rgw alive: rgw closed
Type |
ERROR |
Description |
A heart beat error occurred on a remote gateway due to a network failure or because the remote gateway is not running properly. |
Action |
1) Check the network status and review the system management tool settings such as firewall. 2) Check the Tmax system configuration on the remote node. |
GATEWAY3031 Not found SVC_NAME in %s
Type |
ERROR |
Description |
The configuration file for JEUSGW is invalid. |
Action |
The requested service name is not found in the confguration file. Recreate the configuration file. |
GATEWAY3031 SVC_NAME:EJB_CLASS_NAME:EJB_METHOD_NAME is not set
Type |
ERROR |
Description |
The configuration file for JEUSGW is invalid. |
Action |
The requested service name is not found in the confguration file. Recreate the configuration file. |
GATEWAY3032 SVC_NAME:EJB_CLASS_NAME:EJB_METHOD_NAME is not set
Type |
ERROR |
Description |
The configuration file for JEUSGW is invalid. |
Action |
The requested service name is not found in the confguration file. Recreate the configuration file. |
GATEWAY3033 CLOPT -e/-o flag processing errors
Type |
ERROR |
Description |
Could not convert an argument with the -e or -o flag in the CLOPT setting into a valid file name. |
Action |
Check the CLOPT setting in the GATEWAY section. The argument following the -e or -o flag must be a valid file name. |
GATEWAY4001 %s Gateway (%d.%d.%d) Started
Type |
INFO |
Description |
The Entera gateway has been initiated in the specified version. |
GATEWAY9001 Invalid opcode or msgtype %d
Type |
ERROR |
Description |
An invalid opcode was received from Tuxedo. |
Action |
Contact the Tmax system technical support team. |
GATEWAY9002 Protocol error :
Type |
ERROR |
Description |
An invalid message was received. |
Action |
Contact the Tmax system technical support team. |
GATEWAY9003 Error reply from remote gateway :
Type |
ERROR |
Description |
An error response was received from Tuxedo in reply to the call. |
Action |
Contact the Tmax system technical support team. |
GATEWAY9004 FML16 type not supports
Type |
ERROR |
Description |
An unsupported buffer type was received from Tuxedo. |
Action |
Tmax supports only FML32 (a type of FML buffer in Tuxedo). Modify the setting in Tuxedo. |
18. TMM Module (TMM2001 ~ )
TMM2058 server abnormally closed : svr svrno svc
Type |
ERROR |
Description |
The server process (svr) was shut down abnormally while processing the service (svc). |
Action |
Check the logs for the corresponding service routine and verify that it is correctly linked to the required library. |
TMM2066 server processes add error : too many FD open fd
Type |
ERROR |
Description |
FD_SETSIZE exceeded the system limit. |
Action |
Refer to </usr/include/bits/types.h> and contact the TmaxSoft technical support team. |
TMM2067 server processes add error. No available slot : fd
Type |
WARNING |
Description |
An error occurred while registering a new server process to the Tmax engine. |
Action |
Check whether the number of running processes exceeded the maximum value of server processes specified in the configuration file. |
TMM2083 server process closed while trying to send data
Type |
ERROR |
Description |
A server process was shut down abnormally while the Tmax engine was sending a message to that process. |
Action |
The server process terminated without responding. Check the server application code. This error may also be caused by a UNIX domain socket connection failure. If so, contact the system administrator to resolve the issue. |
TMM2084 trying to write to tproc is blocked: tproc (tproc type) closed and data dropped
Type |
ERROR |
Description |
Sending messages to the client was blocked because the TCP/IP socket was unavailable. The connection was closed after exceeding the maximum number of send retries specified in the Tmax engine. The messages have been discarded. |
Action |
1) Verify whether the Tmax process (of type tproc) was shut down abnormally. If so, check the error messages generated at the time of disconnection. 2) Check whether the Tmax process (of type tproc) failed to read from the socket, and verify the current behavior of that process. |
TMM2086 tmax process(tproc_no) is closed while processing request.
Type |
ERROR |
Description |
A Tmax process (ID) was shut down while sending a message to another process (tproc_no). |
Action |
Verify whether the process was intentionally or abnormally shut down. If so, refer to the error messages generated at the time of disconnection. Otherwise, the error may have been caused by a UNIX domain socket connection failure. In that case, contact the system administrator to resolve the issue. |
TMM2091 node closed while trying to send data
Type |
ERROR |
Description |
Sending messages to a remote gateway was blocked because the TCP/IP socket for the gateway was unavailable. |
Action |
Check whether the corresponding remote node was shut down abnormally. If so, refer to the error messages generated at the time of disconnection. Otherwise, verify the network status. |
TMM2092 trying to send to node is blocked : node closed and data dropped
Type |
ERROR |
Description |
Sending messages to a remote node was blocked because the TCP/IP socket was unavailable. The connection was closed after exceeding the maximum number of send retries specified in the Tmax engine. The messages have been discarded. |
Action |
Check whether the corresponding gateway process was shut down abnormally. If so, refer to the error messages generated at the time of disconnection. Otherwise, verify the network status and contact the system administrator to resolve the issue. |
TMM2105 service name not found in config : svcname
Type |
ERROR |
Description |
The service name (svcname) was not found. |
Action |
Check whether the tmconfig file is damaged. Ensure that the configuration file is correctly compiled. |
TMM2106 node is closed : nodeno nodename current_time
Type |
INFO |
Description |
The (nodename) was disconnected. |
TMM2108 register request from src error : msg
Type |
ERROR |
Description |
An error was detected in the register request message that was accepted by TMM. |
Action |
The following messages can be displayed:
|
TMM2111 node is found dead : nodename
Type |
ERROR |
Description |
The remote node (nodename) is considered shut down because it did not respond to a ping message. |
Action |
1) Check for any network issues with the remote node (nodename). 2) If network is unstable or slow, increase the NLIVEINQ value set in the DOMAIN section of the configuration file. If the NLIVEINQ value is not explicitly set, the default value of 30 seconds applies. 3) For more information about the configuration file, refer to Tmax Administration Guide. |
TMM2111 extsvr is found dead : %d /* fd */
Type |
ERROR |
Description |
A process of type EXTSVR was disconnected. |
Action |
Check whether other EXTSVR-type processes are properly running, and verify if any system management tools, such as firewalls, may have forcibly closed external connections. |
TMM2135 read from Tmax process error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMM2136 send to Tmax process error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMM2141 License file read error: file_name
Type |
ERROR |
Description |
Could not read the license file. |
Action |
1) Install the license file in the correct path (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
TMM2142 Corrupt license file: file_name
Type |
ERROR |
Description |
Could not read the license file. |
Action |
1) Install the license file in the correct path (${TMAXDIR}/license/license.dat). 2) Check the license file version. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
TMM2143 Licensed host not found
Type |
ERROR |
Description |
The host does not have a valid license. |
Action |
Install an updated license file. |
TMM2144 more than licensed number of CPUs are installed.
Type |
ERROR |
Description |
The number of CPUs exceeds the licensed limit. |
Action |
Install an updated license file. |
TMM2145 License is expired.
Type |
ERROR |
Description |
The license has expired. |
Action |
Install an updated license file. |
TMM2146 License check error
Type |
FATAL |
Description |
Failed to check the license. |
Action |
Contact TmaxSoft to obtain or update the license. |
TMM2147 configuration loading error
Type |
FATAL |
Description |
Failed to copy the Tmax system environment file to PATHDIR. |
Action |
Check that PATHDIR is correctly specified in the Tmax system environment file and that write permissions are granted for PATHDIR. After verifying, rerun the command. |
TMM2148 your license does not support sub_prod_name
Type |
ERROR |
Description |
The license is invalid. |
Action |
Contact TmaxSoft to obtain or upgrade the license. |
TMM3001 Engine version mis-match (version1:version2)
Type |
FATAL |
Description |
The version of the Tmax engine does not match the configuration file. |
Action |
Run the cfl utility to recreate the binary configuration file. |
TMM3002 CFGADD failed: err_msg
Type |
ERROR |
Description |
Failed to update the Tmax environment using the tmadmin utility. |
Action |
Fix the error by referring to err_msg. |
TMM3003 magic error in config file
Type |
FATAL |
Description |
The binary configuration file was broken. |
Action |
Run the cfl utility to recreate the binary configuration file. |
TMM3004 svr_name is restarted the nth time (MAXRSTART = num).
Type |
INFO |
Description |
The application server (svr_name) was restarted due to a preceding error. |
Action |
Resolve the underlying issue in the application by referring to the preceding error message. |
TMM3005 no such system svc: svc_name
Type |
ERROR |
Description |
An application server attempted to register a service that is not defined in the configuration file. |
Action |
Recompile the application server by running cfl and then gst. |
TMM3006 closing logs
Type |
INFO |
Description |
TMM closed the log file due to tmdown. |
TMM3007 without node registration, cannot process message: nodeid, msgtype
Type |
ERROR |
Description |
A non-registered node sent a request message. |
Action |
All nodes in a domain must have the same Tmax version. |
TMM3008 possible network layer malfunction, clearing…
Type |
ERROR |
Description |
A network conflict occurred and Tmax is trying to recover from it. |
Action |
Check the network status. |
TMM3009 network recovered.
Type |
INFO |
Description |
Tmax has recovered from the previous network errors. |
Action |
Check the network status. |
TMM3010 SVR_NAME started for backup
Type |
INFO |
Description |
Tmax started a backup server. |
Action |
Check the primary node status. |
TMM3011 your license does not support MODULE_NAME
Type |
INFO |
Description |
Permission to use MODULE_NAME was denied. |
Action |
Upgrade the license. |
TMM3012 cannot find node name (node_name) inconfig.
Type |
FATAL |
Description |
The binary configuration file contains no information about this node (node_name). |
Action |
Check the node name in the configuration file. |
TMM3013 node(node_id) is closed while processing requests.
Type |
ERROR |
Description |
The connection with another node was closed. |
Action |
Check the communication status with the node. |
TMM3015 node add error
Type |
ERROR |
Description |
An already registered node attempted to register again. |
Action |
Check the domain configuration. In a multi-domain network, a configuration error in one domain may affect other domains. |
TMM3016 clh add error
Type |
ERROR |
Description |
More CLH processes attempted to register than the number allowed in the configuration. |
Action |
Check the configuration file and regenerate the binary configuration file. |
TMM3017 RQ name error: rq_name
Type |
ERROR |
Description |
A non-registered RQS sent a request message. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3018 RQ is already added.
Type |
ERROR |
Description |
A non-defined RQS attempted to register. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3019 GW name error: gw_name
Type |
ERROR |
Description |
A non-defined GATEWAY attempted to register. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3020 GW add error.
Type |
ERROR |
Description |
More TMS processes attempted to register than the number allowed in the configuration. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3021 TMS name error.
Type |
ERROR |
Description |
More TMS processes attempted to register than the number allowed in the configuration. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3022 TMS add error.
Type |
ERROR |
Description |
More TMS processes attempted to register than the number allowed in the configuration. |
Action |
Check whether the binary configuration file was modified after tmboot. |
TMM3023 node register (nodeid) failed
Type |
ERROR |
Description |
Failed to register with the node (nodeid). |
Action |
Check the Tmax engine status on the node and verify the network status. |
TMM3024 rout offset is different from previous one
Type |
ERROR |
Description |
Application servers provided different routing fields for DDR routing. |
Action |
Ensure that all application servers are compiled with the same FDL or SDL files. |
TMM3025 register error: type = id, errno = errno
Type |
ERROR |
Description |
An error occurred while registering with a server. |
Action |
1) The type is one of the following:
2) The error code is one of the following:
|
TMM3026 DDR offset is tried for no DDR server.
Type |
ERROR |
Description |
An application server that is not configured for DDR attempted to register DDR information. |
Action |
Check that the configuration file is consistent with the application settings. |
TMM3027 DDR offset is different from the previous one.
Type |
ERROR |
Description |
Application servers provided different routing fields for DDR routing. |
Action |
Ensure that all application servers are compiled with the same FDL or SDL files. |
TMM3030 duplicate channel found for node %d /* nodeno */
Type |
FATAL |
Description |
Failed to copy the Tmax system environment file to PATHDIR. |
Action |
Verify that PATHDIR is correctly specified in the Tmax system environment file and that write permissions are granted for PATHDIR. After verifying, rerun the command. |
TMM3034 svr_name MAXRSTART reached: svr_name
Type |
INFO |
Description |
The number of application servers restarted has reached MAXRSTART. |
Action |
Fix the error in the application by referring to the preceding error messages. |
TMM3035 %s is added to the fork list and will be processed later : %d
Type |
INFO |
Description |
If multiple application servers are started simultaneously, the system blocks them to prevent overload. The servers will be added to the fork list and started later. |
TMM3036 %s failed to add to the fork list
Type |
ERROR |
Description |
Failed to add application servers to the fork list. |
TMM3037 %s (pid = %d) failed to add to the forked list
Type |
ERROR |
Description |
Failed to add an application server (pid) to the fork list. |
TMM3038 %s (%s) is started due to ASQCOUNT, pid = %d
Type |
INFO |
Description |
A server (pid) was additionally started due to ASQCOUNT. |
TMM3041 connection request from other node was closed while tmdown
Type |
WARNING |
Description |
Connection between nodes failed because one of them was shutting down with tmdown. |
TMM3059 fail reg svc (%s, %d, %d, %d) not equal svri(%d)
Type |
ERROR |
Description |
Failed to register a service due to a mismatching svri value. |
TMM3060 (server name) is started due to POD, pid = (process id)
Type |
INFO |
Description |
A POD server process is started. |
TMM3065 reset the restarted count to zero for all servers
Type |
INFO |
Description |
The restart count for all server processes is reset. |
TMM3066 reset the restarted count to zero for SVR (%s) (MAXRSTART = %d)
Type |
INFO |
Description |
The restart count for a specific server process is reset. |
TMM3067 SIGTERM sent to disconnected CLH, pid = %d
Type |
ERROR |
Description |
TMM sent a SIGTERM to CLH to terminate the existing connection after establishing a new connection due to a previouis disconnection. |
Action |
Check that TMM and the new CLH process are running properly. |
TMM3068 TSM (tsm) is started, pid = %d
Type |
INFO |
Description |
The TMAPM setting in the SERVER section was dynamically updated, and a new TSM process was started. |
Action |
Verify that the TSM engine process is running properly. |
TMM3069 CLH (%d) registered, fd = %d, pid = %d
Type |
INFO |
Description |
TMM connected with CLH. |
TMM3070 CLL registered, fd = %d, pid = %d
Type |
INFO |
Description |
TMM connected with CLL. |
TMM3073 License will expire within a month
Type |
INFO |
Description |
The license will expire within a month. |
TMM3074 License expired
Type |
ERROR |
Description |
The license has expired. |
TMM9001 cmdline error
Type |
ERROR |
Description |
An internal process within the Tmax system failed to start. |
Action |
Review the Tmax system environment and processes. |
TMM9002 lpEnv error
Type |
ERROR |
Description |
Failed to obtain an environment variable block from the system. (Windows) |
Action |
Check the system environment. |
TMM9003 OpenProcess error: %d /* errno */
Type |
ERROR |
Description |
Failed to obtain a process handle from the system to terminate processes. (Windows) |
Action |
Rerun the command by referring to the details in the error message. |
TMM9999 error returned from CLH for SHMCHANGE_REQUEST
Type |
ERROR |
Description |
Execution of the tmadmin/cfgadd command failed due to an internal error in the Tmax system. |
Action |
Review the Tmax system environment and processes and then rerun the command. |
19. TMS Module (TMS0211 ~ )
TMS0211 General Infomation : transaction recovery will be started
Type |
INFO |
Description |
TMS will start transaction recovery. |
TMS0211 General Infomation : transaction recovery was completed
Type |
INFO |
Description |
TMS completed transaction recovery. |
TMS2010 CLH connection closed : fd_no
Type |
INFO |
Description |
CLH connection was closed by tmdown. |
TMS2011 TMM connection closed : fd_no
Type |
INFO |
Description |
TMM connection was closed by tmdown. |
TMS2012 register to TMM error : index cpc_no
Type |
FATAL |
Description |
Connections between the engines and server processes failed due to previous errors. |
Action |
Refer to the preceding error messages. |
TMS2013 register to CLH error : index cpc_no
Type |
ERROR |
Description |
Connections between the engines and server processes failed due to previous errors. |
Action |
Refer to the preceding error messages. |
TMS2020 tx_open error : tx_errno
Type |
ERROR |
Description |
An error occurred during tx_open. |
Action |
Refer to the tx_errno message. |
TMS2021 tx_open error : tx_errno
Type |
ERROR |
Description |
An error occurred during tx_open. |
Action |
Refer to the tx_errno message. |
TMS2030 no xa routine is setup
Type |
ERROR |
Description |
Could not configure an XA-related database API routine because the TMS started by the API could not connect to the database. |
Action |
1) Check that the OPENINFO and database connection settings are correctly specified in the SVRGOUP section of the configuration file. 2) Ensure that the XA-related database library is properly linked. The no library is found, verify whether the database was installed correctly. |
TMS2031 xa_open error
Type |
ERROR |
Description |
An error occurred while executing tx_open to connect to the database. |
Action |
Check that the OPENINFO settings are correctly specified in the SVRGOUP section of the configuration file. Also, ensure that the user ID and password specified in the OPENINFO settings are correct. |
TMS2032 xa_start error : xa_errno tx_errno
Type |
ERROR |
Description |
Executing xa_start for 2- phase commit caused an error. |
Action |
xa_start is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
TMS2033 xa_end error : no xa_start
Type |
WARNING |
Description |
xa_end was ignored because it was called without a preceding xa_start. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. These functions operate as a pair. This error occurs if tx_commit or tx_rollback is called without first performing tx_begin. When such an error occurs, the transaction is rolled back. |
TMS2034 xa_end error : tx_errno
Type |
ERROR |
Description |
Executing xa_end to the RDBMS for 2-phase commit caused an error. |
Action |
xa_end is a function provided by an RDBMS engine. Check that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
TMS2035 xa error : tx_begin issued in this server, but no commit or rollback
Type |
WARNING |
Description |
tx_begin was called in a service routine, but the routine ended without executing tx_commit or tx_rollback. |
Action |
By default, the Tmax engine performs tx_rollback. Ensure that tx_commit or tx_rollback is called at the appropriate point before executing tpreturn(). |
TMS2036 xa_start is already done
Type |
WARNING |
Description |
xa_start was ignored because it was called multiple times. Transaction processing must begin with tx_begin and end with either tx_commit or tx_rollback. |
Action |
These functions operate as a pair, and nested transactions are not supported. Each transaction must have exactly one tx_begin and one corresponding tx_commit or tx_rollback. |
TMS2037 internal_commit_error : tx_errno
Type |
ERROR |
Description |
An error occurred during the internal execution of tx_commit. |
Action |
Verify that the RDBMS engine is operating correctly. Check tx_errno against the constants starting with TX_ in the xa.h or usrinc/tx.h files in the RDBMS directory. These constants correspond to database errors. Refer to the database error message manual for further details. |
TMS2038 xa_recover error : tx_errno
Type |
ERROR |
Description |
Executing xa_recover for a 2-phase commit caused an error. |
Action |
xa_recover is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
TMS2041 get TMM path error
Type |
FATAL |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMS2042 TMM connect error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMS2043 write to TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMS2044 receive from TMM error
Type |
ERROR |
Description |
Could not establish a communication channel with the TMM process. |
Action |
1) Check if the stream pipe in $TMAXDIR/path has been damaged. 2) Ensure that the Tmax engine is properly started. |
TMS2045 TMM register error
Type |
ERROR |
Description |
Could not register the TMS process to TMM. |
Action |
1) Check whether the configuration file was modified after TMM started. 2) Run 'tmdown → cfl → tmboot' again to synchronize the engine environment with the binary configuration file. |
TMS2046 Engine version mismatch (version1 : version2)
Type |
FATAL |
Description |
The TMS version does not match TMM. |
Action |
Reinstall the Tmax engine. |
TMS6000 index th working thread create error : errno
Type |
ERROR |
Description |
Failed to create a work thread in the multi-threaded TMS. |
Action |
Refer to the system error message. |
TMS6003 index th working thread cancel error : errno
Type |
ERROR |
Description |
Failed to cancel a work thread in the multi-threaded TMS. |
Action |
Refer to the system error message. |
TMS6004 index th working thread join error : errno
Type |
ERROR |
Description |
Failed to join a work thread in the multi-threaded TMS. |
Action |
Refer to the system error message. |
TMS6005 invalid a working thread index : errno
Type |
ERROR |
Description |
An invalid work thread index was assigned in the multi-threaded TMS. |
Action |
Contact the Tmax system technical support team. |
TMS6006 index th working thread sigmask error : errno
Type |
ERROR |
Description |
Failed to mask a work thread signal in the multi-threaded TMS. |
Action |
Refer to the system error message. |
TMS6007 index th working thread internal error : errmsg
Type |
ERROR |
Description |
An internal work thread error occurred in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6008 index index th working thread request enqueue error : errno
Type |
ERROR |
Description |
Failed to enqueue a request for a work thread in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6009 index th working thread request dequeue error : errno
Type |
ERROR |
Description |
Failed to retrieve a work thread request from the queue in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6010 index th working thread invalid handle : errno
Type |
ERROR |
Description |
The work thread handle is corrupted in the multi-threaded TMS. |
Action |
Restart the TMS, as the kernel thread is in an abnormal state. |
TMS6011 working threads init error: errno
Type |
FATAL |
Description |
Failed to initialize a work thread in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6012 index th working thread request error: errno
Type |
FATAL |
Description |
A work thread request failed in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6013 index th working thread reply error: errno
Type |
FATAL |
Description |
Failed to respond to a work thread request in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6016 threads pool init error
Type |
FATAL |
Description |
Failed to initialize the work thread pool in the multi-threaded TMS. |
Action |
Check system resources. If the issue persists, contact the Tmax system technical support team and provide the error message. |
TMS6017 tmstype mismatch
Type |
ERROR |
Description |
The linked library does not match the type defined in the configuration file. |
Action |
Check the type specified in the configuration file and reconfigure it. |
20. UNCFL Module (UNCFL4001 ~ )
UNCFL4001 Corrupt file: %s
Type |
ERROR |
Description |
uncfl was executed on an invalid file. |
Action |
Ensure that the target file is correctly processed with cfl before uncfl. |
21. WSC Module (WSC3001 ~ )
WSC3001 TMAXDIR is not set
Type |
ERROR |
Description |
TMAXDIR is not set. |
Action |
Configure TMAXDIR as an environment variable. |
WCS3002 Contact to the Service Control Manager error
Type |
ERROR |
Description |
An error occurred while executing the OpenSCManager function. |
Action |
Refer to the system error message. |
WCS3003 CreateService error
Type |
ERROR |
Description |
An error occurred while executing the OpenSCManager CreateService function. |
Action |
Refer to the system error message. |
WCS3004 %s failed
Type |
ERROR |
Description |
An error occurred while executing the '%s' function.function |
Action |
Refer to the system error message. |
WCS3005 Failed to open the service Tmax
Type |
ERROR |
Description |
An error occurred while executing the OpenService function. |
Action |
Refer to the system error message. |
WCS3006 Couldn’t stop service Tmax
Type |
ERROR |
Description |
Could not stop the Tmax service. |
Action |
Verify whether Windows cannot control the service. |
22. WSGW Module (WSGW1001 ~ )
WSGW1001 Fail create wsdl file: Filename
Type |
ERROR |
Description |
Failed to create a WSDL file. Cannot create a file with the specified file name on the specified path. |
Action |
Check the file name and access permissions. |
WSGW1002 Fail write wsdl file: [Data]
Type |
ERROR |
Description |
Failed to save data in the WSDL file. |
Action |
Check available disk space. |
WSGW1003 Fail get service data from metadata: [ServiceName]
Type |
ERROR |
Description |
The ServiceName to be provided from a web service gateway to an external source does not exist in the binary file storing the service information. |
Action |
Confirm that the ServiceName is correct and enter the ServiceName information in the binary file (Create a file to include the service information → add the ServiceName information into the file using the tmmbfgen -I command). |
WSGW1004 Unkown buffer type: [type]
Type |
ERROR |
Description |
An error occurred while executing xwsdlgen. The buffer type specified in the configuration file is invalid; it must be one of STRING, CARRY, STRUCT, or FIELD. |
Action |
Change the buffer type to one of the supported types. |
WSGW1005 Can’t find = in restriction[RestrictionString]
Type |
ERROR |
Description |
An invalid number was specified with an equal sign (=) in the RestrictionString item. |
Action |
In the REQUEST and RESPONSE sections of a web service information file, the restriction attribute must follow the format element_name="value", element_name="value", …. Correct any incorrect usage of the equal sign (=) in the RestrictionString item. |
WSGW1006 Can’t find keyworkd[Keyword] in restriction
Type |
ERROR |
Description |
An invalid keyword was used for a restriction attribute in the web service information file. |
Action |
The value of a restriction attribute must be one of the following keywords: length, minLength, maxLength, enumeration, pattern, minExclusive, maxExclusive, minInclusive, maxInclusive, totalDigits, or fractionDigits. Verify and correct the value. |
WSGW1007 Can’t find value start position in restriction: [RestrictionString]
Type |
ERROR |
Description |
A RestrictionString in the web service information file is not in the correct format element_name="value". The value is missing an opening quotation mark ("). |
Action |
Correct the restriction attribute so that it follows the proper element_name="value" format. |
WSGW1008 Can’t find value end position in restriction: [RestrictionString]
Type |
ERROR |
Description |
A RestrictionString in the web service information file is not in the correct format element_name="value". The value is missing an ending quotation mark ("). |
Action |
Correct the restriction attribute so that it follows the proper element_name="value" format. |
WSGW1009 Couldn’t allocate memory for parser
Type |
ERROR |
Description |
An error occurred while reading a web service configuration file due to insufficient memory. |
Action |
Check system resources to ensure sufficient memory. |
WSGW1010 Fail open WebService Gateway configuration file : FileName
Type |
ERROR |
Description |
Failed to open the web service gateway configuration file (FileName). |
Action |
Check the file path FileName and access permissions. |
WSGW1011 Fail read WebService Gateway configuration file : ReturnValue
Type |
ERROR |
Description |
Failed to read the web service gateway configuration file completely. |
Action |
Check the file size. If the read operation returns a negative value, refer to the corresponding error message. |
WSGW1012 Parse error at line LineNumber:ErrorString
Type |
ERROR |
Description |
An error occurred at line (LineNumber) while reading the web service gateway configuration file. |
Action |
Check the ErrorString and correct the web service gateway configuration file accordingly. |
WSGW1013 Fail Open meta data binary file : FileName
Type |
ERROR |
Description |
Failed to open the service information binary file (FileName). |
Action |
Check the file path FileName and access permissions. |
WSGW1014 Fail Read service size of meta data binary file : ReturnValue
Type |
ERROR |
Description |
Failed to read the number of services stored from the service information binary file. |
Action |
Check the file size. If the read operation returns a negative value, refer to the corresponding error message. |
WSGW1015 Fail Read service of meta data binary file : ReturnValue
Type |
ERROR |
Description |
Failed to read the service information binary file completely. The number of services stored or the service information could not be retrieved. |
Action |
Check the file size. If the read operation returns a negative value, refer to the corresponding error message. |
WSGW1016 Fail Read parameters of meta data binary file : ReturnValue
Type |
ERROR |
Description |
Failed to read the service information binary file completely. The parameter information could not be retrieved. |
Action |
Check the file size. If the read operation returns a negative value, refer to the corresponding error message. |
WSGW1017 Fail Read meta data binary file because invalid magic
Type |
ERROR |
Description |
The version of the service information binary file is not supported by the module currently in use. |
Action |
This occurs when an older module attempts to process a newer service information binary file. Recreate the binary file using a lower version of tmmbfgen. |
WSGW1018 Fail open meta data plain text file : FileName
Type |
ERROR |
Description |
Failed to open the service information file (FileName). |
Action |
Check the file path FileName and access permissions. |
WSGW1019 Unkown type : TypeValue
Type |
ERROR |
Description |
The service information file contains an unknown TypeValue in the REQUEST or RESPONSE section. |
Action |
The value of a type attribute in the REQUEST or RESPONSE section of a service information file must be one of the following: char, short, int, float, double, string, or carray. Verify and correct the value. |
WSGW1020 Unkown type : TypeValue
Type |
ERROR |
Description |
An unknown parameter type was stored in the metadata while executing untmmbfgen. |
Action |
Verify whether the meta file created by tmmbfgen is invalid or its version is incompatible. If so, recreate the meta file. |
WSGW1021 Unkown type : TypeValue
Type |
ERROR |
Description |
The service information file contains an unknown TypeValue set for intype or outtype in the SERVICE section. |
Action |
The values of intype and outtype must be one of the following: STRING, STRUCT, FDL, CARRAY, char, short, int, float, or double. Verify and correct the value. |
WSGW1022 Fail add field because have ParameterCount para.
Type |
ERROR |
Description |
The service information file specifies char, short, int, float, or double for intype or outtype in the SERVICE section, but more than one parameter description is defined in the REQUEST or RESPONSE section. |
Action |
Identify the duplicate parameter descriptions and remove the duplicates. |
WSGW1023 can’t find struct : StructName, ServiceName
Type |
WARNING |
Description |
The struct (StructName) used by the service (ServiceName) could not be found in the service information file. |
Action |
The struct (StructName) does not exist in the SDL file specified by the SDLFILE configuration. To prevent potential issues when running the service, define this struct in the SDL file. |
WSGW1024 different field cnt of struct : StructName,ServiceName
Type |
WARNING |
Description |
The number of parameters for (StructName) used in (ServiceName) does not match the number of fields in the corresponding structure defined in the SDL file. A mismatch between the SDL file specified by SDLFILE and the service information file may cause errors. |
Action |
Ensure that the structure definition for (StructName) is consistent in both the SDL file and the service information file. |
WSGW1025 field [ParameterName] of struct [StructName] can’t match type : ServiceName
Type |
WARNING |
Description |
The field (FieldName) of (StructName) used by (ServiceName) in the service information file does not match the corresponding field name or type in the structure defined in the SDL file. A mismatch between the SDL file specified by SDLFILE and the service information file may cause errors. |
Action |
Ensure that the structure definitions, including field names and types, are identical in both the SDL file and the service information file. |
WSGW1026 can’t find field in fdl file: ParameterName,ServiceName
Type |
WARNING |
Description |
The parameter (ParameterName) used by the service (ServiceName) in the service information file is not found in the FDL file. |
Action |
To prevent potential issues when running the service, ensure that the FDL file and the service information file contain the identical data. |
WSGW1027 field [ParameterName] can’t match type of fdl file : ServiceName
Type |
WARNING |
Description |
The type of the parameter (ParameterName) used by the service (ServiceName) in the service information file is incompatible with the field ParameterName defined in the FDL file. |
Action |
To prevent potential issues when running the service, ensure that the FDL file and the service information file contain the identical data. |
WSGW1028 Fail create meta data plain text file : FileName
Type |
ERROR |
Description |
Failed to create the service information file (FileName). |
Action |
Check the file path FileName and access permissions. |
WSGW1029 Fail write data to meta data plain text file : Data
Type |
ERROR |
Description |
Failed to save the data specified in the service information file. |
Action |
Check available disk space. |
WSGW1030 Fail create meta data file : FileName
Type |
ERROR |
Description |
Failed to create the service information binary file (FileName). |
Action |
Check the file path FileName and access permissions. |
WSGW1031 Fail write meta data file : ReturnValue
Type |
ERROR |
Description |
Failed to save data in the service information binary file. |
Action |
If the save operation returns a negative value, refer to the system error message. |
WSGW1032 can’t use option 'optionA' with option 'optionB'"
Type |
ERROR |
Description |
Mutually exclusive options were specified together when running tmmbfgen. |
Action |
Review the documentation and ensure that only compatible options are used together. |
WSGW2000 General Infomation :
Type |
INFO |
Description |
Displays information required for running the web service gateway. |
WSGW2001 unsufficient size real_size max_size
Type |
ERROR |
Description |
While parsing a SOAP request, an item with a fixed size defined by Tmax exceeded its allowed size. |
Action |
Check the length of the service name or field name, and ensure that the item size does not exceed the specified max_size or real_size. |
WSGW2004 set Method fail
Type |
ERROR |
Description |
An error occurred while parsing a SOAP request. |
Action |
Check the request message. |
WSGW2006 set Body fail
Type |
ERROR |
Description |
An error occurred while parsing the body of a SOAP request. |
Action |
Check the request message. |
WSGW2009 set Envelope fail
Type |
ERROR |
Description |
An error occurred while parsing a SOAP request. |
Action |
This may be caused by an invalid attribute item or an unsupported SOAP version. Check the SOAP request message for correctness. |
WSGW2010 invalid argument : msg
Type |
ERROR |
Description |
An error occurred while the web service gateway was running. |
Action |
Refer to the message. |
WSGW2011 get metainfo fail
Type |
ERROR |
Description |
The requested service was not found in the meta data. |
Action |
Check that the service name is correct. |
WSGW2012 not support array type buffer msg
Type |
ERROR |
Description |
Failed to convert a SOAP request into a Tmax message. |
Action |
Check the SOAP message. |
WSGW2013 SOAP message create fail
Type |
ERROR |
Description |
Failed to create a response message for a SOAP request. |
Action |
Refer to the preceding error message for details. |
WSGW2014 get Attribute fail
Type |
ERROR |
Description |
Failed to create a response message for a SOAP request. |
Action |
Refer to the preceding error message for details. |
WSGW2016 get Method fail
Type |
ERROR |
Description |
Failed to create a response message for a SOAP request. |
Action |
This occurs only when the WSDL type is RPC_ENCODED. Check whether the WS was created correctly. |
WSGW2018 get Body fail
Type |
ERROR |
Description |
Failed to create a response message for a SOAP request. |
Action |
Check the service-generated response message and the preceding errors. |
WSGW2021 get Envelope fail
Type |
ERROR |
Description |
Failed to create a response message for a SOAP request. |
Action |
Refer to the preceding error message for details. |
WSGW2022 SOAP message parse fail :
Type |
ERROR |
Description |
Failed to parse a message received from a SOAP client. |
Action |
Check the XML data generated by the SOAP client and correct it accordingly. |
23. TSM Module (TSM7001 ~ )
TSM7203 svc(service_name) of svr(svr_name:spri:pid) clh(n) svctime(n) elapsed n seconds
Type |
WARN |
Description |
A service timeout occurred in the server process. Relevant information checked by TSM is displayed. |
Action |
Check the ulog to determine why the process did not terminate promptly after the timeout and take corrective action. |
TSM7204 SVR (svr_name) spri(n) is down due to TMAPM=n
Type |
INFO |
Description |
The server process was forcibly terminated by TSM through a SIGKILL. |