Table of Contents
This chapter describes error messages that may occur in each module.
| Type | FATAL |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a tmadmin process to Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | A tmadmin version did not match with a Tm version. |
| Action | Re-install the Tmax engine, and then re-compile the configuration file and server program. |
| Type | ERROR |
| Description | A configuration file used for a cfgadd was not generated with cfl -a. |
| Action | Generate the configuration file used for cfgadd by generating an additional configuration file with cfl -a. |
| Type | ERROR |
| Description | An error occurred while connecting to a remote RACD. |
| Action | Confirm that the RACD was properly booted at remote nodes. 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. |
| Type | ERROR |
| Description | Could not send a request message to a Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. |
| Type | ERROR |
| Description | A remote did not respond to a request message. |
| Action | Check that RACD and tmadmin are operating properly at remote nodes. Check the network status. |
| Type | ERROR |
| Description | Could not find an active CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. Check the CLH process status. If the CLH process was not terminated intentionally, contact a Tmax engineer with the service code. |
| Type | ERROR |
| Description | An error occurred while receiving data from a local RACD. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. Check the RACD process status. |
| Type | ERROR |
| Description | Could not send a message to a local RACD. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. Check the RACD process status. |
| Type | FATAL |
| Description | Could not register a tmadmin to a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. If the Tm process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Another copy of "tmadmin -m" was already started. |
| Action | Only one copy of the master tmadmin can be used at a time. If a tmadmin was not yet started, this message will be displayed due to the Operating System’s socket clear delays. A HUP signal will be sent to the Tm process. |
| Type | ERROR |
| Description | Could not start another tmadmin. |
| Action | There is a pre-configured limit to the number of sub-tmadmin ("tmadmin -s") that can be started at a single time. If no tmadmin has been started, this message will be displayed due to the Operating System’s socket clear delays. A HUP signal will be sent to the Tm process. |
| Type | ERROR |
| Description | Could not send an unregistered message to a Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. To unregister all tmadmin processes, send a HUP signal to the Tm process. |
| Type | ERROR |
| Description | Could not send a request message to a remote node. |
| Action | Check that RACD and tmadmin are operating properly at the remote node. Check the network status. |
| Type | ERROR |
| Description | A communication channel with a remote node closed. |
| Action | Check that RACD and tmadmin are operating properly at the remote node. Check the network status. |
| Type | ERROR |
| Description | Could not send a request message to a local CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the CLH process status. If the CLH process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | WaitForMultipleObjects has failed. |
| Type | ERROR |
| Description | Failed to create a socket pair. |
| Action | Contact the TmaxSoft technical support team. |
| Type | INFO |
| Description | A svr name was not found in Tmax. |
| Action | Specify the svr option again with the name registered in a configuration file. |
| Type | INFO |
| Description | A svg is non-XA. |
| Type | ERROR |
| Description | The resume function was executed without first executing the suspend function. |
| Type | ERROR |
| Description | The length of a character to be displayed with a stdout was too long. |
| Action | Contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a TMBOOT process to a Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | A tmboot version does not match with a Tm version. |
| Action | Re-install the Tmax engine. |
| 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. |
| 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. |
| Type | ERROR |
| Description | A host does not have a valid license. |
| Action | Contact the TmaxSoft technical support team to acquire a new license. |
| Type | ERROR |
| Description | A machine has more CPUs than a license allowed. |
| Action | Install a new license file that supports the amount of CPUs. |
| Type | ERROR |
| Description | A license has expired. |
| Action | Contact the TmaxSoft technical support team to acquire a new license. |
| Type | FATAL |
| Description | A license check failed. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. |
| Type | ERROR |
| Description | A license is invalid. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. |
| Type | ERROR |
| Description | Option arguments are too long. |
| Action | Option arguments must not be longer than 256 characters. |
| Type | ERROR |
| Description | Invalid option flags. |
| Action | Refer to the command line help (tmboot -h) for correct arguments. |
| Type | ERROR |
| Description | Invalid option flags. |
| Action | Refer to the command line help (tmboot -h) for correct arguments. |
| Type | ERROR |
| Description | A svr_name could not boot successfully due to a boot time error. |
| Action | Correct errors referencing previous errors. |
| Type | ERROR |
| Description | Tried to boot a Tmax engine while Tmax was already running. |
| Type | ERROR |
| Description | Tried to boot application processes when Tmax was not running. |
| Action | Boot the Tmax engine first. |
| Type | ERROR |
| Description | Tried to run more processes than specified in the MAX field of the SERVER section in a configuration file. |
| Action | Adjust the MAX field value and reboot Tmax. |
| Type | ERROR |
| Description | The number of processes to be executed is greater than the maximum allowable number of processes specified in the MAX field of the SERVER section in a configuration file. |
| Type | ERROR |
| Description | An invalid server name was used. |
| Action | Check a configuration file for valid server names. |
| Type | ERROR |
| Description | An invalid server group name was used. |
| Action | Check the configuration file for valid server group names. |
| Type | FATAL |
| Description | Could not register to a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. If the Tm process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send unregistered messages to a Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. To unregister all tmadmin processes, send a HUP signal to the Tm process. |
| Type | ERROR |
| Description | The number of currently booted TMS processes + MINTMS is greater than a MAXTMS value in a configuration file. |
| Action | Increase the MAXTMS value in the configuration file. |
| Type | ERROR |
| Description | The number of currently booted CLHs +1 is greater than a MAXCLH value in a configuration file. |
| Action | Increase the MAXCLH value in the configuration file. |
| Type | ERROR |
| Description | A CAS has been already booted. |
| Type | FATAL |
| Description | Failed to create a character string to boot a process due to an internal error. |
| Action | Contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Failed to call GetEnvironmentStrings. |
| Type | ERROR |
| Description | Failed to call CreateProcess. |
| Type | ERROR |
| Description | There was no response from the Tmax server. |
| Type | ERROR |
| Description | A new server was booted after resuming a suspended server, or after using a tmdown. |
| Action | Boot the server after resuming or after using tmdown. |
| Type | ERROR |
| Description | A MAXUSER count has exceeded the maximum number of allowed users specified in a license. |
| Type | ERROR |
| Description | This option is not supported. |
| Type | ERROR |
| Description | A system can not start a server any more. |
| Action | Start additional CLHs. |
| Type | ERROR |
| Description | The number of servers in a group has reached a set limit. |
| Type | FATAL |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a CAS process to a Tm. |
| Action | Confirm that a configuration file was not changed after a Tm boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | A CAS version did not match with a Tm. |
| Action | Re-install the Tmax engine. |
| Type | FATAL |
| Description | Could not register a CAS process to a Tm. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A communication channel with a Tm closed. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the Tm process status. If the Tm process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not receive data from a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the CLH process status. If the CLH process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send data to a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the CLH process status. If the CLH process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send data to a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the CLH process status. If the CLH process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not register a CAS process to a CLH. |
| Action | Make sure that the configuration file has not changed after a Tm boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | Could not register a CAS process to a CLH. |
| Action | Confirm that the configuration file has not changed after a Tm boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | Could not establish a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A password file contains invalid data. |
| Action | Check the password file $(TMAXDIR)/config/passwd. Make a new password file using the mkpw command. |
| Type | ERROR |
| Description | A password file contains invalid data. |
| Action | Check the password file in $(TMAXDIR)/config/passwd. Make a new password file using mkpw. |
| Type | WARNING |
| Description | A client connected with an invalid password. |
| Action | Check the configuration file for "OWNER = usr_name" in the DOMAIN section. |
| Type | WARNING |
| Description | A client connected with an invalid password. |
| Action | Confirm that a password file contains a usr_name:password pair. |
| Type | ERROR |
| Description | An error occurred while sending a request message to a Tm. |
| Action | Check that the files in the $TMAXDIR/path directory were not damaged. |
| Type | INFO |
| Description | A connection to a CLH was disconnected. |
| Action | Check whether tmdown was executed or if CLH was abnormally terminated. |
| Type | ERROR |
| Description | An error occurred while reading an entry in an acl file. |
| Action | Check whether the $TMAXDIR/config/acl file was damaged. |
| Type | ERROR |
| Description | An invalid acl file name was used. |
| Action | Check whether the TMXDIR config is valid. |
| Type | ERROR |
| Description | An invalid user file name was used. |
| Action | Check whether the TMAXDIR config is valid. |
| Type | ERROR |
| Description | A user ID did not match a current process user ID. This was caused by 4 SHM KEYs being opened concurrently. |
| Action | Release the opened shm keys, or reconfigure the key value of shared memory. |
| Type | ERROR |
| Description | A license file read error occurred. |
| Action | 1) Install a license file to 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. |
| Type | ERROR |
| Description | A license file read error occurred. |
| Action | 1) Install a license file to 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. |
| Type | ERROR |
| Description | A host does not have a valid license. |
| Action | Re-install the license file. |
| Type | ERROR |
| Description | There are more CPUs than licensed. |
| Action | Re-install the license file. |
| Type | ERROR |
| Description | A license has expired. |
| Action | Re-install the license file. |
| Type | ERROR |
| Description | A license is invalid. |
| Action | Contact the TmaxSoft technical support team to acquire a new license. |
| Type | ERROR |
| Description | Too many users and server processes were used. |
| Action | Adjust the number of users and server processes. |
| Type | ERROR |
| Description | A command could not be executed because an argument was too long. |
| Action | The string length of an argument must be within 256 characters. |
| Type | ERROR |
| Description | A configuration variable (TMAXDIR) was not set. |
| Action | Set the configuration variable (TMAXDIR). - For ksh: export TMAXDIR = dirname - For csh: setenv TMAXDIR = dirname |
| Type | ERROR |
| Description | A param item does not exist in a configuration file. |
| Action | Input the related item in the configuration file. |
| Type | ERROR |
| Description | A sect item does not exist in a configuration file. |
| Action | Input the related item in the configuration file. |
| Type | ERROR |
| Description | A node name (node1) was not defined in the NODE section of a configuration file. |
| Action | Check the node name in the NODE section of the configuration file. |
| Type | ERROR |
| Description | A server group name (svgname) was not defined as the value of a COUSIN or BACKUP item in a configuration file. |
| Action | Check the server group name in the SVRGROUP section of the configuration file. |
| Type | ERROR |
| Description | A server group (svg1) and its BACKUP were located in the same node. |
| Action | The BACKUP server group must be defined as the server group of another node. Rewrite the configuration file. |
| Type | ERROR |
| Description | A server group (svg1) was configured as BACKUP and COUSIN for another server group (svg2). |
| Action | A server group cannot be defined as both BACKUP and COUSIN for another server group. Rewrite the configuration file. |
| Type | ERROR |
| Description | Failed to proceed due to a previous error. |
| Action | Refer to the previous error message. |
| Type | ERROR |
| Description | The parameter value (param) was duplicated. |
| Action | Delete the duplicated part in the configuration file. |
| Type | ERROR |
| Description | Too many nodes were defined in the NODE section of a configuration file. |
| Action | The number of nodes defined in the NODE section must not exceed a max value. |
| Type | ERROR |
| Description | The DOMAINNAME item of a node (nodename) was not defined in the NODE section of a configuration file. |
| Action | Define the DOMAINNAME item of the node (nodename). |
| Type | ERROR |
| Description | A DOMAINNAME was not defined in the NODE section of a configuration file. |
| Action | Confirm that the DOMAINNAME in the DOMAIN section of the configuration is correct. |
| Type | ERROR |
| Description | The definition for a node name defined as NODENAME = node1 in the SVRGROUP section of a configuration file could not be found in the NODE section. |
| Action | Confirm that node1 is defined in the NODE section of the configuration file. |
| Type | ERROR |
| Description | A server group (svg1) that was specified as the SVGNAME of the RQ section of a configuration file was not defined in the SVRGROUP section. |
| Action | Confirm that svg1 is defined in the SVRGROUP section of the configuration file. |
| Type | ERROR |
| Description | The SVGTYPE of a server group (svg1) that was defined in the RQ section of a configuration file was not RQMGR. |
| Action | Check SVGTYPE in the definition of svg1 in the SVRGROUP section. The SVGTYPE of svg1 defined in the RQ section of the configuration file must be must be RQMGR. |
| Type | ERROR |
| Description | Node1 specified as a NODENAME in the GATEWAY section of a configuration file was not defined in the NODE section. |
| Action | Confirm that node1 is defined in the NODE section of the configuration file. |
| Type | ERROR |
| Description | svg1 specified as a SVGNAME in the SERVER section of a configuration file was not defined in the SVRGROUP section. |
| Action | Confirm that svg1 is defined in the SVRGROUP section of the configuration file. |
| Type | ERROR |
| Description | rout1 specified as a ROUTING item in the SERVICE section of a configuration file was not defined in the ROUTING section. |
| Action | Confirm that rout1 is defined in the ROUTING section. |
| Type | ERROR |
| Description | svr1 specified as SVRNAME in the SERVICE section of a configuration file was not defined in the SERVER section. |
| Action | Confirm that svr1 is defined in the SERVER section. |
| Type | ERROR |
| Description | The all param values defined in the DOMAIN sections in a configuration file were not equal. |
| Action | Check the param values in the DOMAIN sections and make them equal. In a multi-domain environment, a param must be equal in all DOMAIN sections. |
| Type | ERROR |
| Description | A domain name (dom) defined in the DOMAIN section of a configuration file was not unique. |
| Action | Confirm that the dom does not exist in other parts of the configuration file. |
| Type | ERROR |
| Description | A MAXCLH defined in section1 of a configuration file is smaller than MINCLH. |
| Action | Change values to satisfy the condition that the value of MINCLH must be less than that of MAXCLH. section1 should be a DOMAIN or a NODE. |
| Type | ERROR |
| Description | An IDLETIME in the DOMAIN section of a configuration file was not used with CLICHKINT. |
| Action | Use IDLETIME and CLICHKINT together. |
| Type | ERROR |
| Description | A OWNER in the DOMAIN section of a configuration file was not used with SECURITY. |
| Action | Use OWNER and SECURITY together. |
| Type | ERROR |
| Description | A user name (owenr1) was not found. |
| Action | Confirm that owner1 is an available user name. |
| Type | ERROR |
| Description | A routing name (rout1) defined in the ROUTING section of a configuration file is not unique. |
| Action | Confirm that rout1 does not exist in other parts of the configuration file. |
| Type | ERROR |
| Description | A same name (name1) was used in both section1 and section2. |
| Action | Change the configuration file for name1 so that it is not duplicated. |
| Type | ERROR |
| Description | A MAXUSER value (max1) exceeds the permitted value of max2. |
| Action | Set the allowed maximum user number value so that max1 cannot exceed max2. |
| Type | ERROR |
| Description | A TLOGDIR defined in a configuration file is the same as SLOGDIR. |
| Action | Set TLOGDIR and SLOGDIR so that they are not the same. They must have different paths. |
| Type | ERROR |
| Description | A TLOGDIR defined in a configuration file is the same as ULOGDIR. |
| Action | Set TLOGDIR and ULOGDIR so that they are not the same. They must have different paths. |
| Type | ERROR |
| Description | A SLOGDIR defined in a configuration file is the same as ULOGDIR. |
| Action | Set SLOGDIR and ULOGDIR so that they are not the same. They must have different paths. |
| Type | ERROR |
| Description | A domain name (node1) defined in the NODE section of a configuration file is not unique. |
| Action | Confirm that node1 does not exist in other parts of the configuration file. |
| Type | ERROR |
| Description | A LOGOUTSCV svr1 defined in the NODE section of a configuration file was not found in the SERVICE section. |
| Action | Confirm that svr1 is defined in the SERVER section. |
| Type | ERROR |
| Description | A server group name (svg1) defined in the numth line in a configuration file was duplicated in section1. |
| Action | Change the configuration file in order to prevent duplication. A server group name must be unique in the configuration file. |
| Type | ERROR |
| Description | An OWNER item in the SVRGROUP section of a configuration file was not used with a SECURITY item. |
| Action | Use OWNER and SECURITY together. |
| Type | ERROR |
| Description | A SECURITY item in the DOMAIN section was not defined as ACL_SVG. |
| Action | Set the SECURITY item in the DOMAIN section to ACL_SVG to define the SECURITY item in the SVRGROUP section. |
| Type | ERROR |
| Description | A LOAD item in the SVRGROUP section of a configuration file was not used with a COUSIN. |
| Action | Use LOAD and COUSIN together. |
| Type | ERROR |
| Description | An OPENINFO in the SVRGROUP section of a configuration file was not used with a DBNAME. |
| Action | Use OPENINFO and DBNAME together. |
| Type | ERROR |
| Description | An OPENINFO in the SVRGROUP section of a configuration file was not used with a TMSNAME. |
| Action | Use OPENINFO and TMSNAME together. |
| Type | ERROR |
| Description | A MINTMS in the SVRGROUP section of a configuration file was not used with an OPENINFO. |
| Action | Use MINTMS and OPENINFO together. |
| Type | ERROR |
| Description | A MAXTMS in the SVRGROUP section of a configuration file was not used with an OPENINFO. |
| Action | Use MAXTMS and OPENINFO together. |
| Type | ERROR |
| Description | A MAXTMS defined in a SVRGROUP section was smaller than a MINTMS. |
| Action | Change the values so that MINTMS is less than MAXTMS. |
| Type | ERROR |
| Description | A MAX defined in a SERVER section is smaller than a MIN. |
| Action | Change the values so that MIN is less than MAX. |
| Type | ERROR |
| Description | A CPC item could not be defined in a TMAX_STD SVRTYPE server. |
| Action | Remove the CPC item. |
| Type | ERROR |
| Description | A server name (svg1) defined in the numth line of a configuration file was duplicated in section1. |
| Action | Change the configuration file in order to prevent duplication. The server name must be unique in the configuration file. |
| Type | ERROR |
| Description | A service name (svc) defined in the numth line of a configuration file was duplicated. |
| Action | Change the configuration file in order to prevent duplication. The service name must be unique in the configuration file. |
| Type | ERROR |
| Description | A service name (presvc) defined in the numth line of a configuration file was not registered in the SERVICE section. |
| Action | Confirm that presvc is defined correctly in the SERVER section of the configuration file. |
| Type | ERROR |
| Description | A RQ name (rqs) defined in the numth line of a configuration file was duplicated. |
| Action | Change the configuration file in order to prevent duplication. The RQ name must be unique in the configuration file. |
| Type | ERROR |
| Description | A gateway name (gw) defined in the numth line of a configuration file was duplicated. |
| Action | Change the configuration file in order to prevent duplication. The gateway name must be unique in the configuration file. |
| Type | ERROR |
| Description | A parameter value (param) is out of a valid range. |
| Action | Change the param value to be within a valid range. The valid range of param is more than min and less than max. |
| Type | ERROR |
| Description | A parameter value (param) is out of a valid range. |
| Action | Change the param value to be within a valid range. The valid range of param is less than max. |
| Type | ERROR |
| Description | A parameter value (param) is out of a valid range. |
| Action | Change the param value to be within a valid range. The valid range of param is more than min. |
| Type | ERROR |
| Description | A parameter value (param) is out of a valid range. |
| Action | Change the param value to one of the parameters listed in value_list. |
| Type | ERROR |
| Description | A ROUTING section was defined without defining a COUSIN item. |
| Action | Define the COUSIN group in the SVRGROUP section. The ROUTING section is defined between a specific server group and its COUSIN. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A RANGES item in a ROUTING section was defined incorrectly. |
| Action | Redefine the min and max values of RANGES. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A RANGES item in a ROUTING section was defined incorrectly. |
| Action | Redefine the RANGES value, or set the min and max values in RANGES. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A RANGES item in a ROUTING section was defined incorrectly. |
| Action | "*" can only be used once in the RANGES parameter of a configuration file. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A string value and an integer value conflicted in a RANGES. |
| Action | Choose either a of string or an of integer. Avoid using an integer and string together. |
| Type | ERROR |
| Description | A MOD value and an integer value conflicted in a RANGES. |
| Action | Choose either a of MOD or an of integer. Avoid using an integer and a MOD together. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A MOD value and a string value conflicted in a RANGES. |
| Action | Choose either a of MOD or an of integer. Avoid using an integer and a MOD together. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A string defined in a RANGES is too long. |
| Action | Reduce the length of the string so that it does not exceed the max value. |
| Type | ERROR |
| Description | A string defined in a RANGES did not end with " ". |
| Action | When a string is defined, it must be enclosed by " ". |
| Type | ERROR |
| Description | A MIN was defined more than once in a RANGES item. |
| Action | Only use MIN once. |
| Type | ERROR |
| Description | A MAX was defined more than once in a RANGES item. |
| Action | Only use MAX once. |
| Type | ERROR |
| Description | The format used for a RANGES item was invalid. |
| Action | For more information about the format, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A string defined in a RANGES did not end with " ". |
| Action | When a string is defined, it must be enclosed by " ". |
| Type | ERROR |
| Description | A server group (svg) specified in a RANGES was not defined in a configuration file. |
| Action | Check the server group (svg) defined in the SVRGROUP section. |
| Type | ERROR |
| Description | A MOD operator format defined in a RANGES is incorrect. |
| Action | Correct the MOD operator format in the numth line by referring to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A configured RANGES parameter is incorrect. |
| Action | Set RANGES correctly. |
| Type | ERROR |
| Description | A configured RANGES parameter is incorrect. |
| Action | Change the range to satisfy the following condition: ranges ‘from1 - to1’ and ‘from2 - to2’ must not overlap each other. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | A server group (svg) defined in a RANGES does not have a COUSIN relation with other server groups defined in the same RANGES item. |
| Action | For load balancing based on data, the defined server groups must be in a COUSIN relation with each other. Make sure that the COUSIN item is defined correctly in reference to the SVRGROUP section of the configuration file. For more information, refer to "Tmax Administrator's Guide". |
| Type | ERROR |
| Description | The buffer type of DDR to enable the routing function was incorrectly specified. |
| Action | Redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of ports specified in a TmaxPort and a CompressPort exceeds 4. |
| Action | Correct the configuration by referring to the manual. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A syntax error occurred at a line (line_num). |
| Action | Correct the syntax by referring to the error message. |
| Type | ERROR |
| Description | A GW PORTNO conflicts with a TPORTNO used in a DOMAIN or NODE. |
| Action | Change the GW PORTNO. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A GW PORTNO conflicts with A RACPORT. |
| Action | Change the GW PORTNO or RACPORT. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A GW PORTNO conflicts with a TPORTNO used in a DOMAIN or NODE. |
| Action | Change the GW PORTNO. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A TPORTNO used in a DOMAIN conflicts with a TPORTNO used in a NODE. |
| Action | Change the TPORTNO used in the NODE, The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A DOMAIN section was used incorrectly. |
| Action | Remove the invalid DOMAIN section. Only one DOMAIN section can be used. |
| Type | ERROR |
| Description | A TPORTNO used in a DOMAIN or NODE conflicts with a RACPORT. |
| Action | Change the RACPORT or TPORTNO. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A GW PORTNO conflicts with a gw_name. |
| Action | Change the GW PORTNO. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | A GW RGWPORTNO conflicts with a gw_name. |
| Action | Change the GW RGWPORTNO. The values from TPORTNO (used in DOMAIN) to TPORTNO + 11 are used by the Tmax system, so it cannot be one of those values. |
| Type | ERROR |
| Description | The number of defined nodes is larger than a MAXNODE value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined RQs is larger than a MAXRQ value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined GWs is larger than a MAXGW value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined SVGs is larger than a MAXTOTALSVG value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined SVGs is larger than a MAXSVC value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined ROUTs is larger than a MAXROUT value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined ROUT SVGs is larger than a MAXROUTSVG value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined COUSINs is larger than the MAXCOUSIN value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined COUSINs is larger than the COUSINSVG value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined BACKUPs is larger than the MAXBACKUP value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of defined BACKUP SVGs is larger than the MAXBACKUPSVG value in a DOMAIN section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A MAXNODE CPC in a DOMAIN section must be smaller than FD_SETSIZE. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The number of %s specified in a node is larger than the value set in %s. |
| Action | Increase the MAX value or decrease the number of %s. |
| Type | ERROR |
| Description | The number of %s is larger than the value set in %s. |
| Action | Increase the MAX value or decrease the number of %s. |
| Type | ERROR |
| Description | The number of running server processes is larger than the MAXSPR defined in a configuration file. |
| Action | Set MAXSPR in the DOMAIN or NODE sections properly or increase the number of maximum users. |
| Type | ERROR |
| Description | The number of CPCs has exceeded the MAXCPC value defined in a configuration file. |
| Action | Redefine the MAXCPC value set in the DOMAIN or NODE sections to be larger than the CPC value. |
| Type | ERROR |
| Description | Two or more DOMAINs are specified. |
| Action | Redefine the configuration. Only one DOMAIN is allowed in a Tmax configuration. |
| Type | FATAL |
| Description | A TIP SVG has been configured, but not a TIP server. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A server that was not a RQ server was set in a RQMGR SVG. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the CMTRET value set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the BLOCKTIME value set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the TXTIME values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multi domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the MAXFUNC values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the MAXSACALL values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the MAXCACALL values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the MAXCONV_NODE values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the MAXCONV_SERVER values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | ERROR |
| Description | To configure multiple domains in one configuration, the CPC values set in the domains must be the same. |
| Action | In Tmax 5.0 and newer, multiple domains cannot be set in one configuration. |
| Type | INFO |
| Description | If a MAXUSER is set, the number of available users will be distributed evenly among nodes. |
| Type | ERROR |
| Description | A MAXSVR value in a node is smaller than a MAXSPR value. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A MAXRQSVR value + a MAXGWSVR value in a node must be larger than a MAXSPR value. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A MAXRQCPC value + a MAXGWCPC value in a node must be larger than a MAXCPC value. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A CompressPort must be a TmaxPort. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A TMAXPORT conflicts with a CPORTNO. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A TMAXPORT conflicts with a EXTPORT. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A TMAXPORT conflicts with an EXTCLHPORT. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A NODE(A) conflicts with a NODE(B). |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A NODE(A) and a NODE(B) have different NODETYPEs. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A schedule item must be set to PR for a Tmax_UCS_LOAD svrtype. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A server that has a TMAX_STD svrtype must have one CPC. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The MIN/MAX value for a server with a SYS_SVR svrtype must be 1. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A REALSVR_MT svrtype server must have been registered in the REALSVR field of the NODE section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A UCS license is invalid, however, UCS is not checked for this version of the application. |
| Action | Ignore this message. |
| Type | ERROR |
| Description | The specified name of a SVC was not found in the ENQSVC of a RQ. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A %s in a GATEWAY section conflicts with %s. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A %s in a GATEWAY section of a configuration file must be specified. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A REALSVR svrtype server in a NODE section was not defined as REALSVR or REALSVR_MT. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The MIN value of a REALSVR svrtype server must be larger than the MINCLH value of a NODE section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The MAX value of a REALSVR svrtype server must be smaller than the MINCLH * 16 of a NODE section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A REALSVR set in a node was not found in a SERVER section of a configuration file. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | When a REALSVR is defined, a MINCLH must be equal to a MAXCLH. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A service was registered for a REALSVR_MT svrtype server. |
| Action | A service cannot be registered for a REALSVR_MT svrtype server. Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The dbname is not supported. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | Invalid encryption text was entered. |
| Action | Enter the encryption text correctly. |
| Type | FATAL |
| Description | When executing CFL, the -a and –o options must be used together. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | Only 0 or 1 is allowed for a –v option to execute CFL. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A nodename is not set in a configuration. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | An invalid parameter format was specified in a configuration file. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on the %s parameter. |
| Type | ERROR |
| Description | An invalid parameter was specified in a configuration file. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | An invalid parameter value was specified in a configuration file. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | Failed to read a file. |
| Action | Deal with the error message you got before this error. |
| Type | ERROR |
| Description | No DDR is set for a SVG that a service belongs to. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | A REALSVR configured in a NODE section was not found in a SERVER section. |
| Action | Check the manual to redefine the configuration. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | INFO |
| Description | Duplicate service names exist in a MAXSVC. |
| Action | Edit the MAXSVC so that each SVC has a unique name. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Action | %s must be used with %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 SERVERNAME in the FUNCTION section of the TOPEND environment configuration. |
| Type | ERROR |
| Description | An invalid SVRNAME has been set for a FUNCTION. |
| Action | Check the PRODNAME setting for a SVG. |
| Type | ERROR |
| Description | The number of TMSDEP entries has exceeded a maximum allowable value. |
| Action | Set the TMSDEP entry value to be smaller than the maximum value. |
| Type | ERROR |
| Description | Could not find an entry (tmsname) set for a TMSDEP. |
| Action | Check whether the TMS set for the TMSDEP exists in the same node. |
| Type | ERROR |
| Description | Two or more event handler servers in a configuration file (svrtype is SYS_EVT) could not be specified for a node. |
| Action | Check whether there is duplicate event handler server setting in the SERVER section of the configuration file. |
| Type | ERROR |
| Description | Two or more processes could not be specified for an event handler server (svrtype is SYS_EVT). |
| Action | Specify MIN/MAX values for the event handler server in the SERVER section to 1. |
| 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. |
| 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. |
| Type | ERROR |
| Description | Due to corruption of data received from a client (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. |
| Action | Check whether a message has been successfully transmitted from the client. If not, check whether there are any errors in the application program such as a memory attack, invalid arrays, nulls in string data, or whether input data is larger than the actual buffer size. |
| Type | ERROR |
| Description | A message received from a client is corrupted (message was truncated during transmission) but can possibly be recovered. Only the truncated part then process the message will be discarded. When an error occurs during processing, a TPEITYPE or TPEINVAL error may be returned to the client. |
| Action | Check whether the message has been successfully transmitted from the client. If not, check whether there are any errors in the application program such as a memory attack, invalid arrays, nulls in string data, or whether the input data is larger than the actual buffer size. |
| 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 has been successfully transmitted from the client. If not, check whether there are any errors in the application program such as a memory attack, invalid arrays, nulls in string data, or whether the input data is larger than the actual buffer size. |
| Type | ERROR |
| Description | Clients failed to connect to Tmax because unlimited number of clients are abnormally connected to CLH. CLH disconnects the client which does not reply TP START connection message within 60 seconds after a socket connection to the client is made. |
| Action | Identify the reason for unlimited connections to the CLH. |
| Type | ERROR |
| Description | Failed to find a service (ServiceName) requested by a client in the server process. |
| Action | Execute the gst command after recompiling the configuration file by using cfl -i. Existing objects must be deleted in order to compile a new file. |
| Type | FATAL |
| Description | Failed to initialize a service table because a server process could not find a related service (ServiceName). |
| Action | Execute the gst command after recompiling the configuration file by using cfl -i. Existing objects must be deleted in order to compile a new file. |
| Type | ERROR |
| Description | Data exists that uses an unsupported FDL field type in a transferred message. |
| Action | If the error occurs with a client, check if tmax. fdl is damaged. If the error occurs with a server, check the FDL header file (suffix: _fdl.h) to compile it. |
| Type | ERROR |
| Description | Data exists that uses an unsupported FDL field type in a transferred message. |
| Action | Check for a communication interference between a client and a server. |
| Type | ERROR |
| Description | A response arrived within a defined timeout after executing a tpcall. |
| Action | In case of a normal process, increase the BLOCKTIMEOUT value defined in the DOMAIN section of a configuration file. Otherwise, check for a communication interference between a client and a server. |
| Type | ERROR |
| Description | A service was not processed within a defined timeout. |
| Action | Increase the SVCTIME value of the service (ServiceName) in a configuration file. If the SVCTIME value is correct, check for inefficient components in a service routine. |
| Type | ERROR |
| Description | A server terminated while processing a request. In this situation the server process is generally terminated by server process errors or other external causes. |
| Action | Restart the server process by using the tmboot -s svrname command. And identify the server process program error. |
| Type | INFO |
| Description | The connection with another CLH was closed due to a tmdown. |
| Type | INFO |
| Description | The connection with a Tm was closed due to a tmdown. |
| Type | ERROR |
| Description | Failed to connect a CLH process due to a previous error. |
| Action | Refer to the previous error message. |
| Type | FATAL |
| Description | Failed to register a Tm due to a previous error. |
| Action | Check that the Tm process is operating properly by using the ps command. Refer to the previous error message. |
| Type | FATAL |
| Description | Failed to register a cl due to a previous error. |
| Action | Refer to the previous error message. |
| Type | FATAL |
| Description | A server was terminated due to a previous DDR error. |
| Action | Refer to the previous DDR error message. |
| Type | ERROR |
| Description | The fieldkey value for a DDR was invalid. |
| Action | Check that the fieldkey value (fieldkey) defined in the ROUTING section of a configuration file is correct. |
| Type | ERROR |
| Description | The fieldkey type for DDR does not match with the type defined in a 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. Refer to the "Tmax Administrator's Guide" for more information on environment configuration. |
| Type | ERROR |
| Description | The field for DDR does not exist in a 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). |
| 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). |
| Type | ERROR |
| Description | No data was received for a DDR. |
| Action | A client must send the data that was predefined in a configuration file to perform DDR. Confirm that a client received a relevant data type. |
| 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. |
| Type | ERROR |
| Description | The SUBTYPE of a related DDR was defined as a FIELD in the ROUTING section of a configuration file, but the data received from clients did not use a field-type buffer. |
| Action | Check that the client transmission buffer is defined as a field type. |
| Type | ERROR |
| Description | The subtype name (subtype_config) defined in the SUBTYPE item of a configuration file did not match with the subtype_received of a message received from clients. |
| Action | Base the SUBTYPE of the configuration file with the subtype used by clients. If a structure-typed buffer is used, confirm that the structure-typed name of the structure-typed definition file (extension: .s) matches with that of the configuration file. If so, recreate a structure-typed definition binary file (SDLFILE). |
| 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. |
| Type | ERROR |
| Description | A server was terminated due to a previous DDR error related to a database. |
| Action | First, confirm that the OPENINFO item and database connection information are defined properly in the SVRGROUP section of a configuration file. Next, check 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. |
| 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 a configuration file. In particular, confirm that the user ID and password described in OPENINFO is correct. |
| Type | ERROR |
| Description | Executing xa_start for 2- phase commit created an error. |
| Action | xa_start is a function provided by an RDBMS engine. Confirm that the RDBMS engine was started. For more information, refer to the error reference guide of the database. |
| 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. |
| Type | FATAL |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | Failed to send data to a Tm process. |
| Action | Use the tmadmin tool to check the connection status between a CLH and Tm. If there's a connection problem, contact the system administrator. |
| Type | ERROR |
| Description | Failed to send data to a Tm process. |
| Action | Use the tmadmin tool to check the connection status between a CLH and Tm. If there's a connection problem, contact the system administrator. |
| Type | ERROR |
| Description | Could not establish a communication channel with a Tm process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a CLH process to a Tm. |
| Action | Confirm that a configuration file was not changed after the Tm boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | A CLH version does not match with a Tm. |
| Action | Re-install the Tmax engine. |
| Type | ERROR |
| Description | A maximum allowed number of concurrent users was exceeded. |
| Action | Increase the MAXUSER value defined in the DOMAIN section of the configuration file. When exceeds the registered maximum number of user connections, a new license key must be obtained. Contact the system administrator. |
| Type | ERROR |
| Description | Could not send a service process result due to a disconnection from a client. |
| Action | Find the reason why the client has closed the connection without processing a result. For example, check whether BLOCKTIME is too short or if there are delays in service processing. |
| Type | WARNING |
| Description | A Tmax engine sent a message to a server process, but it was ignored due to a disconnection. |
| Action | The related server was terminated by using tmdown -s or abnormally terminated due to a fault. Reboot the related server by using tmboot -s. If the server is closed abnormally, check the server application codes. |
| Type | WARNING |
| Description | A Tmax engine sent a message to a server process, but it was ignored due to a disconnection. |
| Action | The related client was been disconnected by a BLOCKTIME timeout or an abnormal condition. |
| Type | INFO |
| Description | The number of messages (num) remaining in a server process queue was deleted by tmdown when a related server was terminated. |
| Type | ERROR |
| Description | A server process (tms_name) in charge of a TMS was closed abnormally. |
| Action | Confirm that the TMS process (tms_name) was linked with the latest TMS library. Confirm that the RDBMS engine is operating properly. |
| Type | ERROR |
| Description | A RQ server process (rqs_name) was closed abnormally. A system problem or an operation error occurred. |
| Action | This may be caused by a system error or faulty system operation. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | A server process (svr) was closed abnormally. |
| Action | Confirm that the error occurred when writing a related service routine. Confirm that the related library is linked properly. |
| Type | ERROR |
| Description | A related remote gateway was closed abnormally. |
| Action | Check the Tmax status of the node where the related gateway was operated. Check for network problems between nodes. |
| 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. |
| 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. |
| Type | INFO |
| Description | Messages (num) stored while disconnecting with a related client were deleted. |
| Type | WARNING |
| Description | The number of client requests in the queue of a server process (svr) exceeded a set limit. |
| Action | Change the MAXQCOUNT value of the server process (svr) in the SERVER section of a configuration file. |
| Type | ERROR |
| Description | A FD_SETSIZE exceeded a limit supported by a system. |
| Action | Refer to /usr/include/bits/types.h. Contact the TmaxSoft technical support team. |
| Type | WARNING |
| Description | An error occurred while registering a new server process in a Tmax engine. |
| Action | Adjust the number of starting processes not to exceed the MAX value of server processes. |
| Type | ERROR |
| Description | The number of maximum users exceeded a limit supported by a system. The Tmax service was not provided to a client that passed the maximum concurrent user limit. |
| Action | Increase the MAXUSER value defined in the DOMAIN section in a configuration file. To exceed a limit, contact the TmaxSoft technical support team to acquire a new license. |
| Type | ERROR |
| Description | An error occurred in a received tpnotify message. |
| Action | Check for a communication interference between nodes. |
| Type | ERROR |
| Description | An error occurred in a received tpnotify message. |
| Action | Check for a communication interference between nodes. |
| Type | ERROR |
| Description | An error occurred in a received tpnotify message. |
| Action | Check for a communication interference between nodes. |
| 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. |
| 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. |
| Type | ERROR |
| Description | Failed to add a new client due to a previous error. |
| Action | Refer to the previous error message. |
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 client due to the following reasons: - too many FD open: The limit on the number of open files has been exceeded. - session init fail: Initialization of encryption for a session failed. |
| Action | 1) Increase the number of files that can be opened in the system. 2) Refer to the "Tmax Administrator's Guide" to check the system configuration for encryption. 3) Decrease the number of simultaneous users or increase the limit for simultaneous accesses. 4) This error can occur when a connection is made between CLHs of nodes. Attempt to reconnect every interval period specified in a NLIVEINQ. |
| 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 the TmaxSoft technical support team. |
| Type | INFO |
| Description | Displays the maximum number of concurrent users that are allowed to connect to a CPU-based license node. |
| 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 a configuration file. |
| Type | ERROR |
| Description | An error occurred while receiving a file descriptor (fdno) from a cl. |
| Action | Check the named pipe status (Filename) of PATHDIR. If fdno is smaller than -1, refer to the system error message. |
| 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. |
| 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 could be caused 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 | Check whether the value for CLHQTIMEOUT or SVRQTIMEOUT has been set to a large enough value. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| Type | WARNING |
| Description | Failed to read a message in a queue (q_kind) because the queue was empty. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| Type | INFO |
| Description | A connection with a node (nodename) was terminated. |
| 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.
|
| Type | ERROR |
| Description | An error occurred in a register request message received by a Tm. |
| Action | The msg may be as follows: - MAX_CLH_REACHED: No more CLH processes can be created because the number of current CLH processes reaches the MAXCLH value defined in a configuration file. Increase the MAXCLH value if more CLH processes are needed. - MAX_TMS_REACHED: No more TMS processes can be created because the number of current TMS processes reaches the MAXTMS value defined in a configuration file. Increase the MAXTMS value if more TMS processes are needed. - MAX_SPR_REACHED: No more server processes can be created because the number of current server processes reaches the MAX value defined in a configuration file. Increase the MAX value if more server processes are needed. - SVR_NOT_IN_CONFIG: A requested server name could not be found in a configuration file. - ADM_MAIN_STARTED: No more than one tmadmin can be created for a main mode. - MAX_ADM_REACHED: The number of the tmadmin processes of a main or sub mode exceeds a limit. - ALREADY_TMM_REGISTERED: No more tmboot or tmdown processes can be created because they are already executed. |
| Type | ERROR |
| Description | A remote node (nodename) was processed as terminated because a ping message did not receive any response from it. |
| Action | Check if any problem exists in the remote node (nodename) by using the network. When the network is unstable or too slow, increase the NLIVEINQ value in the DOMAIN section of the configuration file. The default value is 30 seconds if the NLIVEINQ value is not set. Refer to the "Tmax Administrator's Guide" for more information on DOMAIN settings. |
| 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. |
| Type | ERROR |
| Description | An error occurred in a communication channel to an application server. |
| Action | Check if the application server is operating correctly or if it was abnormally terminated due to an application fault. Check if a stream pipe of $TMAXDIR/ path is damaged. |
| 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. |
| Type | ERROR |
| Description | An invalid call descriptor value (cd-value) was used in the interactive mode. |
| Action | Check that the cd value used by tpsendor a tprecv was correctly acquired by tpconnect. |
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 | Check that the clid value was correctly acquired by tpgetclid and that the communication channel is connected to the client. |
| Type | ERROR |
| Description | An invalid message was sent from a module. |
| Action | Check that Tmax was installed properly and if each module version matches. Check the communication status between nodes. |
| Type | ERROR |
| Description | A communication fault occurred between Tmax Engines. |
| Action | Check if the stream pipe files in $TMAXDIR/path are damaged. Refer to the log file in the system log directory. The default value is $(TMAXDIR)/log/slog. |
| Type | ERROR |
| Description | A communication fault occurred between Tmax engines. |
| Action | 1) Check that the stream pipe of $TMAXDIR/path is not damaged. 2) Make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A communication fault occurred between Tmax engines. |
| Action | 1) Check that the stream pipe of $TMAXDIR/path was not damaged. 2) Make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A license file read error occurred. |
| Action | 1) Install a license file to 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 or later. |
| Type | ERROR |
| Description | A host does not have a valid license. |
| Action | Install a new valid license file. Contact the TmaxSoft technical support team to acquire a new license. |
| Type | ERROR |
| Description | There are more CPUs than licensed. |
| Action | Install a new valid license file. |
| Type | ERROR |
| Description | A license is expired. |
| Action | Install a new valid license. |
| Type | FATAL |
| Description | A license check failed. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. |
| Type | INFO |
| Description | A service queue was cleared due to a request from a tmadmin. |
| Type | ERROR |
| Description | A license is invalid. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. |
| Type | ERROR |
| Description | A timeout occurred when trying to connect to server in a TOPEND migration system. |
| Action | Check whether the server is normally operating. |
| Type | WARNING |
| Description | A transaction will be rolled back due to a transaction 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. |
| Type | WARNING |
| Description | A transaction will be committed due to a transaction 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. |
| Type | WARNING |
| Description | A transaction will become pending due to a 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. |
| Type | WARNING |
| Description | A transaction will be 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. |
| Type | WARNING |
| Description | A transaction will be 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. |
| Type | WARNING |
| Description | A transaction will become 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 transaction will be rolled back due to closed server(spri) connection
| Type | WARNING |
| Description | A transaction will be 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 committed internally due to closed server(spri) connection
| Type | WARNING |
| Description | A transaction was 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 server(spri) connection
| Type | WARNING |
| Description | A transaction will become 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. |
| 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. |
| 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. |
| Type | ERROR |
| Description | A current Tmax configuration contains more servers for nodes than a Tmax system can support. |
| Action | Decrease the maximum number of servers allowed in the Tmax system configuration file. |
| 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. |
| Type | WARNING |
| Description | A response to a tpcall arrived after a defined timeout. The response could not be sent to a client because the processing time exceeded a limit. In this situation, response data is ignored or deleted, but the service is regarded as processed. Therefore, if a service is related to transaction processing, the process result should be checked. |
| Action | Increase the BLOCKTIMEOUT value. |
| Type | ERROR |
| Description | A server was terminated while processing a request. The server process was terminated by server process errors or other external causes. This generally occurs due to server process program errors. |
| Action | Restart the server process by using the tmboot -s svrname command. |
| Type | ERROR |
| Description | Executing xa_start for a 2-phase commit created an error. |
| Action | xa_start is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
| Type | WARNING |
| Description | xa_end was ignored because it was called without first performing xa_start. Transaction processing must be started by tx_begin and terminated by tx_commit or tx_rollback. These functions are operated as a pair. Therefore, this error will occur if tx_commit or tx_rollback is performed without first performing tx_begin. In this case, a transaction will be rolled back. |
| Type | ERROR |
| Description | Executing xa_end for a 2-phase commit created an error. |
| Action | xa_end is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
| Type | WARNING |
| Description | tx_begin was called in a service routine, but the service routine was terminated without calling tx_commit or tx_rollback. |
| Action | A Tmax engine performs tx_rollback by default. Execute tx_commit or tx_rollback in an intended location before executing tpreturn(). |
| Type | WARNING |
| Description | xa_start was ignored because it is called duplicately. Transaction processing must be started by tx_begin and terminated by tx_commit or tx_rollback. These functions are operated as a pair and nested transactions are not supported. A transaction must be processed by one tx_begin and one tx_commit or tx_rollback. |
| Type | ERROR |
| Description | Internally executing tx_commit created an error. |
| Action | Confirm that a RDBMS engine is operating properly. Refer to the constant value started with TX_ in the xa.h or usrinc/tx.h files of the RDBMS directory in order to check a tx_errno. This constant value should match with the database error. Refer to the error message manual of the database for more information. |
| 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. |
| Type | ERROR |
| Description | Failed to add a new client. |
| Action | Refer to previous error messages. |
| Type | WARNING |
| Description | A client received a message with a wrong sequential number from a Tmax engine. |
| Action | 1) If a received seqno is smaller than an expected seqno, check if a previous reply message arrived after a timeout. Adjust BLOCKTIME defined in the DOMAIN section in a configuration file. 2) If a received seqno is greater than an expected seqno, check for a communication interference between a client and a server. |
| Type | ERROR |
| Description | A client could not connect to a Tmax engine. |
| Action | 1) Check that the TMAX_HOST_ADDR and TMAX_HOST_PORT environment variables match host_name of a configuration file. 2) Check the configuration file path used as an argument of the tmaxreadenv() function. 3) Check the network channel between a client and host_name. 4) Check that the Tmax engine was booted properly for host_name. |
| Type | ERROR |
| Description | A client could not connect to a Tmax engine. |
| Action | 1) Check that the TMAX_HOST_ADDR and TMAX_HOST_PORT environment variables match host_name of a configuration file. 2) Check TMAX_BACKUP_ADDR and TMAX_BACKUP_PORT. 3) Check the configuration file path used as an argument of the tmaxreadenv() function. 4) Check the network channel between a client and host_name. 5) Check that the Tmax engine was booted properly for host_name. |
| Type | ERROR |
| Description | A magic number in an SDL binary file was incorrect. |
| Action | Check that the SDLFILE environment variable points to a correct binary file generated by the sdlc command. |
| Type | ERROR |
| Description | An error occurred while reading an SDL binary file. |
| Action | Check that the SDLFILE environment variable points to a correct binary file generated by the sdlc command. |
| Type | ERROR |
| Description | An error occurred while reading a binary fieldkey file. (extension: .fdl or fdl_file) |
| Action | Check that the FDLFILE environment variable points to a correct binary file generated by the fdlc command. |
| Type | ERROR |
| Description | A getsockname() call failed. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | tp_system_message() has an invalid argument. |
| Action | Check arguments of tp_system_message(). |
| Type | ERROR |
| Description | A client library initialization failed. |
| Action | Refer to previous error messages. |
| Type | ERROR |
| Description | A magic number in a FDL binary file was incorrect. |
| Action | Confirm that the FDL binary file (extension: .fdl) was not damaged. |
| Type | ERROR |
| Description | An error occurred while reading a binary fieldkey file (extension: . fdl or fdl_file) because an internal table size was 0. |
| Action | Confirm that the fdl_file was created correctly and that the fieldkey definition is correct. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification was specified in a configuration file. |
| Action | Check if TMAX_TRACE was correctly configured. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification was specified in a configuration file. The spec has an invalid value. |
| Action | Check if TMAX_TRACE was correctly configured. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification was specified in a configuration file. The Action Spec has not been specified. |
| Action | Check if TMAX_TRACE was correctly configured. Check if the ulog(message), system(command), trace(trace-spec), and sleep(second) parameters in a Action Specification were correctly configured. |
| Type | ERROR |
| Description | The number of TCP clients exceeds the maximum allowable number of users. |
| Action | Increase the max_tcpcli value in the tcpinit function. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a CLL process to a TMM. |
| Action | Make sure that the configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | A CLL version does not match with a TMM. |
| Action | Re-install the Tmax engine. |
| Type | WARNING |
| Description | A new client connected, but no CLH was available. |
| Action | There is a slight time gap between CLL and CLH booting. Clients connected during this time will be rejected. Retry client connections. |
| Type | ERROR |
| Description | A communication channel with a TMM was closed. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. Check the TMM process status. |
| Type | ERROR |
| Description | A new client connected to a Tmax server, but no CLH was available. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | Could not register a CLL process to a TMM. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | A Tmax engine found that a network layer malfunctioned and its recovery was performed. |
| Action | Check the network status. |
| Type | INFO |
| Description | A Tmax engine was recovered from previous network failures. |
| Action | Check the network status to prevent future errors. |
| Type | ERROR |
| Description | Could not send data to a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a tmdown process to a TMM. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | A tmdown version does not match with a TMM. |
| Action | Re-install the Tmax engine. |
| Type | ERROR |
| Description | An invalid argument was specified. |
| Action | The length of any argument must not exceed 256 characters. |
| Type | ERROR |
| Description | No response while terminating processes. |
| Action | Check the TMM process status. Make sure that no more than one tmdown process is active at a time. |
| Type | ERROR |
| Description | Could not send a terminate process request to a TMM process. |
| Action | Check the TMM process status. Make sure that no more than one tmdown process is active at a time. |
| Type | ERROR |
| Description | Could not write data to a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the TMM process status. If the TMM process was not terminated intentionally, contact the TmaxSoft technical support team after checking a service code. |
| Type | ERROR |
| Description | Could not send an unregister message to a TMM. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the TMM process status. To unregister all of the tmadmin and tmdown processes, send a HUP signal to the TMM process. |
| Type | ERROR |
| Description | A syntax error at line_num. |
| Action | Correct the syntax errors of an input file. |
| Type | ERROR |
| Description | No output was generated due to previous errors. |
| Action | Fix previous errors by referring to previous error messages. |
| Type | ERROR |
| Description | An error occurred while updating a FDL file. |
| Action | Regenerate a binary FDL file from the text FDL file. |
| Type | ERROR |
| Description | An error occurred while updating a FDL file. |
| Action | Regenerate a binary FDL file from the text FDL file. |
| Type | ERROR |
| Description | An error occurred while updating a FDL file. |
| Action | Regenerate a binary FDL file from the text FDL file. |
| Type | ERROR |
| Description | A field key number defined in a FDL file is greater than or equal to 16777216. |
| Action | A field key number must be greater than 0 and less than 16777216. |
| Type | ERROR |
| Description | An error occurred when trying to boot multiple tmadmins. |
| Action | 1) A user can run only one tmadmin at each node while monitoring Tmax using a RACD. 2) There is a tmadmin process running which was not terminated due to previous errors. Terminate tmadmin processes manually. |
| Type | ERROR |
| Description | Could not invoke a local tmadmin process. |
| Action | Make sure that the TMAXDIR environment is properly set. |
| Type | ERROR |
| Description | A communication channel with a local tmadmin process was broken. |
| Action | Check the tmadmin process state. |
| Type | ERROR |
| Description | Failed to execute a system function with a command. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | INFO |
| Description | The connection between a CLH and a UNIX domain socket was closed due to tmdown. |
| Type | INFO |
| Description | The connection between a TMM and a UNIX domain socket was closed due to tmdown. |
| Type | FATAL |
| Description | Failed to connect a server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | ERROR |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a RQS process to a TMM. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | A RQS version does not match with a TMM. |
| Action | Re-install the Tmax engine. |
| Type | WARNING |
| Description | Failed to send a message to a CLH because a TCP/IP socket was blocked. |
| Action | Check if the CLH was closed abnormally. If so, refer to the error messages that were output at the time of disconnection. If not, the problem may be a connection failure with a UNIX domain socket between a Tmax process and the CLH process. Contact a system administrator for further assistance. |
| Type | FATAL |
| Description | Could not register a RQS process to a TMM. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | Could not register a RQS process to a TMM. |
| Action | Confirm that a configuration file was not changed after a TMM boot. |
| Type | FATAL |
| Description | Could not read a RQ file. |
| Action | Check the status of the RQ files located in the FILEPATH field of the RQ section. |
| Type | FATAL |
| Description | Could not write a RQ file. |
| Action | Check the status of the RQ files located in the FILEPATH field of the RQ section and in free disk space. |
| Type | ERROR |
| Description | An overflow occurred because a RQ data file exceeded a defined size. |
| Action | Increase the QSIZE item value defined in the RQ section in a configuration file. |
| Type | FATAL |
| Description | Invalid arguments were found in a RQ server command line. |
| Action | Tmax engine servers must not be executed manually. |
| Type | INFO |
| Description | Previous RQ files were found during a WARM boot. |
| Action | The BOOT field of the RQ section in a configuration file determines the handling method of previous RQ files. - Cold boot (BOOT = COLD): Removes previous RQ files, and starts with empty RQ data files. - Warm boot (BOOT = WARM): Revives data from previous RQ files. During a WARM boot, previous RQ files are backed up with an ".old" extension. If a WARM boot fails, contact a Tmax engineer with backup RQ files. |
| Type | FATAL |
| Description | A RQ file error occurred during a WARM boot. |
| Action | Refer to the action of the RQS3012 message. |
| Type | INFO |
| Description | Previous RQ files were found during a WARM boot. |
| Type | ERROR |
| Description | RQ file errors occurred during a WARM boot. |
| Action | The BOOT field of the RQ section in a configuration file determines the handling method of previous RQ files. - Cold boot (BOOT = COLD): Removes previous RQ files, and starts with empty RQ data files. - Warm boot (BOOT = WARM): Revives data from previous RQ files. During a WARM boot, previous RQ files are backed up with an ".old" extension. If a WARM boot fails, contact a Tmax engineer with backup RQ files. |
| Type | FATAL |
| Description | A WARM boot failed because previous RQ files contained more data than a current file could handle. |
| Action | Increase the QSIZE value defined in the RQ section in a configuration file. Rename the backup RQ file without an ".old" extension, and retry the WARM boot. |
| Type | INFO |
| Description | WARM boot phase 1. |
| Action | None. Refer to the action section of the RQS3012 message. |
| Type | INFO |
| Description | WARM boot phase 2. |
| Action | None. Refer to the action section of the RQS3012 message. |
| Type | INFO |
| Description | WARM boot phase. |
| Action | None. Refer to the action section of the RQS3012 message. |
| Type | INFO |
| Description | A WARM boot was successfully finished. |
| Action | None. Refer to the action section of the RQS3012 message. |
| Type | ERROR |
| Description | Could not load a FDLFILE for a view type process. |
| Action | Check the FDLFILE environment variable. Generate the file with the fdlc command. |
| Type | ERROR |
| Description | An invalid type name. |
| Action | Supported types for a Tmax SDL are as follows: - SDL_CHAR: 1 - SDL_SHORT: 2 - SDL_INT: 3 - SDL_LONG: 4 - SDL_FLOAT: 5 - SDL_DOUBLE: 6 - SDL_STRING: 7 - SDL_CARRAY: 8 - SDL_STRUCT: 9 - SDL_TYPEDEF: 10 |
| Type | ERROR |
| Description | A string entered in a null field when creating a View file was too long. |
| Action | The null field length in the view file must be smaller than 32. Check the value and decrease the length. |
| Type | ERROR |
| Description | A NULL value in a view file was not an allowable value. |
| Action | Change the NULL value to an allowable value. |
| Type | WARNING |
| Description | A response to a tpcall arrived after a defined timeout. The result could not be sent to a client because the processing time exceeded a set limit. In this situation, result data will be ignored and deleted, but a service will be processed. Therefore, if a service is not related to a transaction process, check process results. |
| Action | Increase the BLOCKTIMEOUT value. |
| Type | ERROR |
| Description | A server terminated while processing a request. The server process was terminated by server process errors or other external causes. This error generally occurs due to server process program errors. |
| Action | Look for the program errors then restart the server process by using the tmboot -s svrname command. |
| Type | INFO |
| Description | A connection with a CLH was closed due to tmdown. |
| Type | INFO |
| Description | A connection with a TMM was closed due to tmdown. |
| Type | FATAL |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | ERROR |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | FATAL |
| Description | A server was terminated due to a previous DDR error. |
| Action | Refer to previous DDR error messages. |
| Type | ERROR |
| Description | A fieldkey value for a DDR was invalid. |
| Action | Confirm that the fieldkey value defined in the ROUTING section in a configuration file is correct. |
| Type | ERROR |
| Description | The fieldkey type of a DDR does not match with the type defined in a configuration file. |
| Action | Confirm that the fieldkey type for DDR in the ROUTING section in the configuration file matches with the FDL definition file (extension: .f). Valid fieldkey types are: short, long, int and string. |
| Type | ERROR |
| Description | The field for a DDR does not exist in the related subtype of a structure-type binary file (extension: .sdl). |
| Action | Confirm that the DDR field of the ROUTING section matches with the structure-type definition file (extension: .s). If so, recreate a structure-type definition binary file (SDLFILE). |
| Type | ERROR |
| Description | The structure type for a DDR was not defined in a structure-type binary file (extension: .sdl). |
| Action | Confirm that the DDR structure type of the ROUTING section matches with the structure-typed definition file (extension: .s). If so, recreate a structure-type definition binary file (SDLFILE). |
| Type | ERROR |
| Description | Data for a DDR does not exist in a request message. |
| Action | A client must send the data that was predefined in a configuration file to perform a DDR. Check if a client sends a relevant data. |
| Type | ERROR |
| Description | An offset value for a DDR was not defined. |
| Action | An offset value is defined in the tmconfig file in a config directory. Check that the configuration file was compiled correctly (cfl -i). |
| Type | ERROR |
| Description | A SUBTYPE of a related DDR was defined as a FIELD in the ROUTING section of a configuration file, but the data received from clients did not use a field-type buffer. |
| Action | Check if the client transmission buffer is defined as a field type. |
| Type | ERROR |
| Description | A subtype name (subtype_config) defined in the SUBTYPE item of a configuration file does not match with the subtype_received of a message received from clients. |
| Action | Match the SUBTYPE of 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). |
| Type | ERROR |
| Description | A XA-related DB API routine could not be set. This is because TMS that was started by the API could not be connected to a database. |
| Action | 1) Check if the OPENINFO item and the database connection information are defined properly in the SVRGROUP section in a configuration file. 2) Check if the database library related to XA is linked properly. The library is generally installed together with a database. |
| Type | ERROR |
| Description | Executing tx_open to connect to a RDMBS caused an error. |
| Action | Check if the OPENINFO items are described properly in the SVRGROUP section in a configuration file. In particular, check that the user ID and password described in a OPENINFO are correct. |
| Type | ERROR |
| Description | Executing xa_start for a 2-phase commit caused an error. |
| Action | xa_start is a function provided by a RDBMS engine. Check that the RDBMS engine was started. |
| Type | WARNING |
| Description | xa_end was ignored because it was called without performing xa_start. Transaction processing must be started by tx_begin and terminated by tx_commit or tx_rollback. These functions are operated as a pair. Therefore, this error will occur if tx_commit or tx_rollback is performed without first performing tx_begin. In this case, a transaction will be rolled back. |
| Type | ERROR |
| Description | Executing xa_start for a 2-phase commit caused an error. |
| Action | xa_end is a function provided by a RDBMS engine. Check that the RDBMS engine was started. |
| Type | WARNING |
| Description | tx_begin was called in a service routine, but the service routine was terminated without calling tx_commit() or tx_rollback(). |
| Action | A Tmax engine performs tx_rollback by default. Execute tx_commit or tx_rollback in an intended location before executing tpreturn(). |
| Type | WARNING |
| Description | xa_start was duplicately called and ignored. Transaction processing must be started by tx_begin and terminated by tx_commit or tx_rollback. These functions are operated as a pair, and nested transactions are not supported. A transaction must be processed by using tx_begin then tx_commit or tx_rollback. |
| Type | ERROR |
| Description | Internally executing tx_commit created an error. |
| Action | Check that a RDBMS engine is operating properly and refer to the constant value stated by a TX_ in the xa.h or usrinc/tx.h files of the RDBMS directory in order to check txerrno. This constant value should match with the database error. |
| Type | ERROR |
| Description | An error occurred when executing tx_open to connect to a RDBMS. |
| Action | Check whether OPENINFO items are correctly set in the SVRGROUP section of a configuration file. Confirm that the user ID and password described in OPENINFO are correct. |
| Type | ERROR |
| Description | An error occurred when executing tx_close to disconnect from a RDBMS. |
| Action | Check if the RDBMS is running normally. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a SVR process to a TMM. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | A SVR version does not match with a TMM. |
| Action | Re-install the Tmax engine. |
| Type | WARNING |
| Description | A service routine was not terminated by tpreturn. A Tmax server process program must be terminated by functions such as tpreturn or tpforward, and resulting messages should be returned to clients. This error occurs generally if a program is terminated without performing functions such as exit or tpreturn. |
| Action | Check if tpreturn or tpforward was used to terminate the service routine then modify the server application codes. |
| Type | ERROR |
| Description | A SVRTYPE set in a configuration file does not match the SVRTYPE of a complied server. |
| Action | Recompile the configuration file using cfl– i and execute a get command. Make sure that an existing object is deleted to compile a new file. |
| Type | ERROR |
| Description | An invalid call descriptor value (cd-value) was used in an asynchronous environment. |
| Action | Check whether the cd value used by tpgetrply() was retrieved through tpacall(). |
| Type | ERROR |
| Description | The working thread of a clientid was disconnected from a remote node. |
| Type | ERROR |
| Description | A saved message (num) was deleted while closing a connection from a client. |
| Type | ERROR |
| Description | A Tmax process (proc) was disconnected while a Tmax process ID was sending data to the Tmax process (proc) and the data was discarded. |
| Action | If the Tmax process (proc) was terminated, refer to the message displayed when the connection was closed. Otherwise, this error happened because a UNIX domain socket connection failed. Contact the system administrator to solve this problem. Tmax process ID's can be checked with the st –p command with tmadmin. |
| Type | ERROR |
| Description | A Tmax process (proc) was disconnected while receiving data from a Tmax process ID. |
| Action | If a Tmax process (proc) was terminated, refer to the message displayed when the connection was closed. Otherwise, this error happened because a UNIX domain socket connection failed. Contact a system administrator to solve this problem. |
| Type | ERROR |
| Description | Failed to send data to a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | WARNING |
| Description | A client received a message with a wrong sequential number from a Tmax engine. |
| Action | 1) received seqno < expected seqno: A previous reply message arrived after a timeout. Adjust the BLOCKTIME defined in the DOMAIN section in a configuration file. 2) received seqno > expected seqno: Check for a communication interference between a client and server. |
| Type | FATAL |
| Description | Could not register an application server process to a TMM. |
| Action | 1) Make sure that a configuration file is not changed after a TMM boot. 2) Check that no more than the maximum (MAX field of the SERVER section in a configuration file) number of processes has been booted. 3) Make the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | An application server received a request for a service that is not in its service table. |
| Action | 1) Check the SERVICE section in a configuration file for the svc_name. 2) Recompile the application after running cfl and gst. |
| Type | ERROR |
| Description | Could not open a file or a socket due to a system limitation. |
| Action | Raise the maximum number of open file descriptors using the ulimit or unlimit command. Recommended values are 1024 for small configurations and 4096 for large configurations. Contact a system administrator for further support. |
| Type | ERROR |
| Description | Could not establish a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | An error occurred when reading a binary fieldkey file (extension: .fdl or fdl_file). |
| Action | Check that the FLDLFILE environment variable points to a correct binary file generated by the fdlc command. |
| Type | ERROR |
| Description | Failed to call getsockname(). |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Invalid arguments exist in tp_system_message(). |
| Action | Check the arguments of tp_system_message(). |
| Type | ERROR |
| Description | Failed to initialize a client library. |
| Action | Refer to the previous error messages. |
| Type | FATAL |
| Description | Could not send data to a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | FATAL |
| Description | An error occurred when receiving data from a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | An application server tried to register an unset service name. |
| Action | 1) Check the SERVICE section of a configuration file for svc_name. 2) Recompile an application after running cfl and gst. |
| Type | ERROR |
| Description | A CLOPT field contains invalid strings. |
| Action | Check the CLOPT field in the SERVER section in a configuration file. User defined arguments must be located after a "--" separator. |
| Type | ERROR |
| Description | Could not convert the -e or -o argument flags of a CLOPT field to valid file names. |
| Action | Check the CLOPT field in the SERVER section in a configuration file. Arguments next to the -e or -o flags must be valid file names. The macros that can be used as arguments to the –e and -o options are as follows: $(SVR): server name $(SVRI): server index $(SPRI): unique process index $(SPRMIN): MIN field of a server section $(SPRMAX): MAX field of a server section $(SPRN): server process sequential number (0 ~ $(SPRMAX)) $(DATE): server start date in the MMDDYYYY format $(TIME): server start time in the HHMMSS format $(PID): server process id |
| Type | INFO |
| Description | The tpsvrinit() routine of svr_name returned a negative value. |
| Action | Check the application code of the tpsvrinit() function. |
| Type | ERROR |
| Description | An application server received a request for a service that was not in its service table. |
| Action | 1) Check the SERVICE section in a configuration file for svc_name. 2) Recompile an application after running cfl and gst. |
| Type | ERROR |
| Description | A user coded service (svc_name) does not end with a tpreturn() function. |
| Action | All services must be ended with tpreturn(). |
| Type | ERROR |
| Description | A user ended a service without first terminating server initiated requests. |
| Action | tpacall() must be paired with tpgetrply(). Conversational services must be terminated before running tpreturn(). |
| Type | INFO |
| Description | A user terminated a server with tpreturn (TPEXIT). If "RESTART=Y" existed in the SERVER section of a configuration file, a server will be restarted by a TMM. |
| Action | None. The server will be restarted by the TMM. |
| Type | INFO |
| Description | A user terminated a server with tpreturn (TPDOWN). Even if "RESTART=Y" existed in the SERVER section of a configuration file, a server will not be restarted. |
| Action | None. The server will not be restarted. |
| Type | ERROR |
| Description | A user ended a service without first terminating server initiated requests. |
| Action | tpacall() must be paired with tpgetrply(). Conversational services must be terminated before running a tpreturn(). |
| Type | ERROR |
| Description | Could not send a tpforward request to a CLH. |
| Action | Check the connection between a server and a CLH. |
| Type | ERROR |
| Description | An application server tried to register an unset product name. |
| Action | 1) Check the PRODNAME field of the SVRGROUP section in a configuration file. 2) Recompile the application after running cfl and gst. |
| Type | ERROR |
| Description | Failed to register a function to a Tmax engine. |
| Action | 1) Check the FUNC section in a configuration file. 2) Recompile the application after running cfl and gst. |
| Type | ERROR |
| Description | An application server received a request for a function that was not in its function table. |
| Action | 1) Check the FUNC section in a configuration file for the func_name. 2) Recompile the application after running cfl and gst. |
| Type | ERROR |
| Description | A client requested a service and an invalid output workspace size was detected. |
| Action | Check the arguments for tp_client_send(). |
| Type | ERROR |
| Description | An application server received a request for a function that did not exist in a function table. |
| Action | 1) Check the FUNC section in a configuration file for func_name. 2) Recompile the application after running cfl and gst. |
| Type | ERROR |
| Description | A service was not processed within a defined timeout. |
| Action | Increase the SVCTIME value of the service (ServiceName) in a configuration file. If the SVCTIME value was correct, check for inefficient components in a service routine. |
| Type | ERROR |
| Description | A service timeout occurred while sending a trace log. A program will terminate abnormally after sending a log to a stderr. |
| Action | Increase the SVCTIME value specified for a ServiceName in a configuration file. |
| Type | ERROR |
| Description | An error occurred while registering a service to a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Failed to register a service name as a tpadvertise. The service name was already registered by another process named 'svrname:spri'. |
| Action | Confirm that the service name is unique within a single server. |
| Type | ERROR |
| Description | A transaction, '0-0-0', has an invalid XID and failed to perform xa_start. |
| Action | The return value of a tpcall or tpgetrply indicates a failure. tperno and tpurcode are set to TPETRAN and TX_ESYSTEM. |
| Type | ERROR |
| Description | An incorrect magic number was found in a FDL binary file. |
| Action | Check if the FDL binary file (extension: .fdl) was damaged. |
| Type | ERROR |
| Description | An error occurred while reading a binary fieldkey file (extension: .fdl or fdl_file) because an internal table size was 0. |
| Action | Check if fdl_file was created correctly and a fieldkey definition file was written correctly. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification. |
| Action | Check if the environment variable TMAX_TRACE was set properly. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification. The trace specified for a command was not a valid value. |
| Action | Check if the environment variable TMAX_TRACE was set properly. |
| Type | ERROR |
| Description | An invalid Tmax Trace Specification. No action specification was configured. |
| Action | Check if the environment variable TMAX_TRACE was set properly. Also check that the ulog(message), system (command), trace(trace-spec), and sleep(second) variables were set correctly. |
| Type | ERROR |
| Description | Failed to receive data in a Realtime Data Processor (RDP) due to a disconnection from a remote client. |
| Action | Check to see if there was a communication failure with a RDP client. |
| Type | ERROR |
| Description | An invalid message was received from a channel with a fd_no value. |
| Action | Check to see if there was a communication failure with a Realtime Data Processor (RDP) client. |
| Type | ERROR |
| Description | Failed to receive data from a Realtime Data Processor (RDP) server. |
| Action | 1) Check if a retval size is available. 2) Check to see if there was a communication failure with the RDP server. 3) If retval is a negative value, refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An invalid message was received from a Realtime Data Processor (RDP) client. |
| Action | Check to see if there was a communication failure with a RDP client. |
| Type | ERROR |
| Description | Failed to receive data in a Realtime Data Processor (RDP) due to a disconnection from a remote client. |
| Action | Check to see if there is communication failure with RDP client. |
| Type | ERROR |
| Description | Failed to send data to a Realtime Data Processor (RDP) client due to a timeout. The connection to a remote client was closed. |
| Action | Check to see if there was a communication failure with a RDP client. |
| Type | ERROR |
| Description | Failed to receive a file descriptor (FD). |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Failed to send a file descriptor (FD). |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | WARN |
| Description | A RCA handler was not available. |
| Action | Wait until the RCA handler is ready. |
| Type | ERROR |
| Description | Failed to find an available handler. |
| Action | Control the number of requests or increase the number of RCA handlers. |
| Type | ERROR |
| Description | An error occurred while registering a new RCA handler. |
| Action | The number of running RCA handlers exceeded the maximum allowable number of RCA handlers. |
| Type | FATAL |
| Description | Failed to start a RCA handler within a limited time. |
| Action | Check if the RCA handler is running correctly. Also check to see if there is a communication failure between a RCA listener and a RCS handler. |
| Type | ERROR |
| Description | Detected Tmax shared memory versions did not match. |
| Action | Check the Tmax version of a server library. |
| Type | FATAL |
| Description | Failed to register a RCA listener. |
| Action | Check that the stream pipe of $RCA_DIR was not damaged and the RCA listener was started. |
| Type | FATAL |
| Description | An error occurred while creating a thread. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Failed to close a working thread of a RCA handler. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Failed to find an available working thread in a RCA handler. |
| Action | Control the number of requests or increase the number of working threads. |
| Type | ERROR |
| Description | A timeout occurred while sending a local recursive-tpcall to a svc service. |
| Action | Increase the SVCTIME of the service (ServiceName) in a configuration file. If the SVCTIME is proper, check if there are any inefficient components of the service routine. |
| Type | ERROR |
| Description | Failed to initialize a mutex for a thread/process synchronization. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Failed to initialize a semaphore for a process synchronization. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | INFO |
| Description | Messages tagged with a TPNOREPLAY were deleted from a queue due to a disconnection from a remote gateway. |
| Type | ERROR |
| Description | Could not find a service to send a reply message from a remote gateway. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP) ". |
| Type | ERROR |
| Description | A socket to a remote gateway socket was closed. |
| Action | Check the remote gateway and network status. |
| Type | ERROR |
| Description | A connection with a gateway that had an ipaddr address was lost. |
| Action | Check the remote gateway and network status. |
| Type | ERROR |
| Description | A channel (index) failure was detected in a user function (chk_pong_msg()). The channel will forcibly close. |
| Action | Check the remote gateway and network status. |
| Type | ERROR |
| Description | An error occurred in a user function, funcname. |
| Action | Check the logic and error of the user function. |
| Type | ERROR |
| Description | Gateway numbers necessary to make connections with a number of remote nodes were missing in a configuration file. |
| Action | Check the configuration file by referring to the "Tmax Gateway Guide (TCP/IP)". |
| Type | ERROR |
| Description | Addresses of the remote nodes necessary to make connections with a number of remote nodes were missing in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | Remote port numbers necessary to make connections with a number of remote nodes were missing in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | The number of input channels necessary to make connections with a number of remote nodes was missing in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | The number of output channels necessary to make connections with a number of remote nodes was missing in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | Failed to connect to a remote node. |
| Action | Check the remote gateway and network connection status. |
| Type | FATAL |
| Description | An invalid option was used to configure a CLOPT gateway parameter. |
| Action | Check the options of the CLOPT parameter in the TCPGW sub-section of the server section in a Tmax configuration file. |
| Type | ERROR |
| Description | The length of a one line set in a configuration file exceeded a maximum allowable length (255 characters). |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | A remote channel setting was missing in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | FATAL |
| Description | An invalid channel setting was found in a configuration file. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | Failed to connect to a remote node. A reconnection will be attempted periodically, as well as when a new request arrives. |
| Action | Check the remote gateway and network connection status. |
| Type | ERROR |
| Description | Since an error occurred in a connection to a remote node (ipaddr), all relevant channels are terminated. |
| Action | Check the remote gateway and network connection status. |
| Type | FATAL |
| Description | A TCP/IP thread gateway listener failed to listen to a handler. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. |
| Type | ERROR |
| Description | The clientid item was missing in a configuration file of a TCP/IP thread gateway. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | WARN |
| Description | Failed to retrieve client information for an IP (ipaddr) from the configuration file of a TCP/IP thread gateway. |
| Action | Refer to: "Tmax Gateway Guide (TCP/IP)" and check the configuration file. |
| Type | ERROR |
| Description | Could not find an available handler in a TCP/IP thread gateway listener. |
| Action | Control the number of requests or increase the number of available handlers. |
| Type | ERROR |
| Description | Failed to send a notification to a TCP/IP thread gateway listener. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. |
| Type | FATAL |
| Description | Failed to register a TCP/IP thread gateway listener. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged. |
| Type | INFO |
| Description | A TCP/IP thread gateway handler closed a working thread for a clientid. |
| Action | None. |
| Type | FATAL |
| Description | Failed to connect to a listener of a TCP/IP thread gateway. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and that the listener started. |
| Type | INFO |
| Description | A clientid is already in use. |
| Action | Check if the clientid was duplicated in a configuration file. |
| Type | ERROR |
| Description | Failed to register a TMM process due to a network failure or an abnormal TMM operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not receive data from a CLH due to a network failure or an abnormal CLH operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send data to a CLH due to a network failure or an abnormal CLH operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Failed to send a message to a CLH process due to a network failure or due to an excessive overloading or abnormal operation of the CLH process. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Failed to register a message to a CLH process due to a network failure or an abnormal CLH operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Failed to advertise a TIPSVC to a TMM process due to a network failure or an abnormal TMM operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Failed to register a TIPSVC to a TMM process due to a network failure or an abnormal TMM operation. |
| Action | Check the network status and the Tmax system environment along with its processes. Contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Could not register a TLM process to a TMM. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A connection to a TMM was closed. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the status of the TMM process. If the TMM process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not receive data from a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the status of the TMM process. If the TMM process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send data to a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the status of the TMM process. If the TMM process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send data to a CLH. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and check the status of the TMM process. If the TMM process was not terminated intentionally, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Failed to register a TLM process to a CLH. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Keep the engine configuration consistent with a binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | Failed to register a TLM process to a CLH. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Keep the engine configuration consistent with a binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | Failed to configure a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Failed to configure a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Failed to configure a communication channel with a CLH process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A connection to a CLH was closed. |
| Action | 1) Check that the stream pipe of $TMAXDIR/path was not damaged. 2) Check the status of the CLH process. If the process was not intentionally terminated, contact the TmaxSoft technical support team. |
| Type | WARN |
| Description | The status of a domain transaction was changed to pending. It will be processed again through a transaction recovery. |
| Type | ERROR |
| Description | Failed to execute tpstart(). |
| Action | Fix the errors by referring to the tperrno_string. |
| Type | ERROR |
| Description | An error occurred while reading an input file. |
| Action | Check the input script file. |
| Type | ERROR |
| Description | A call type was invalid. |
| Action | TMD supports the following call types: - tpcall() - tpacall() - tpgetrply() |
| Type | ERROR |
| Description | A buffer type was invalid. |
| Action | The following buffer types are supported: - STRUCT - FIELD - CARRAY - STRING |
| Type | ERROR |
| Description | A sub type was invalid. |
| Action | A sub-type name must be a valid name specified in a SDLFILE. |
| Type | ERROR |
| Description | A flag was invalid. |
| Action | The following flags are supported: - TPNOBLOCK - TPNOREPLY - TPNOTRAN - TPNOTIME - TPNOGETANY - TPGETANY - TPNOCHANGE - TPBLOCK - TPSENDONLY - TPRECVONLY |
| Type | ERROR |
| Description | An error occurred in an input script. |
| Action | Fix input script errors by referring to the error_messages. |
| Type | ERROR |
| Description | A security input value was invalid. |
| Action | Check the input value for the security configuration. |
| Type | ERROR |
| Description | Failed to execute tpalloc() for a service call. |
| Action | Refer to the "Tmax Reference Guide". |
| Type | ERROR |
| Description | Failed to execute tpset_timeout() for a timeout configuration. |
| Action | Refer to the "Tmax Reference Guide". |
| Type | ERROR |
| Description | Failed to execute tx_begin() for transaction processing. |
| Action | Refer to the "Tmax Reference Guide". |
| Type | ERROR |
| Description | Failed to execute tx_commit() for service transaction processing. |
| Action | Refer to the "Tmax Reference Guide". |
| Type | ERROR |
| Description | Failed to execute tx_set_transaction_timeout() for transaction processing. |
| Action | Refer to the "Tmax Reference Guide". |
| Type | ERROR |
| Description | Failed to execute tpalloc(). |
| Action | Fix the errors by referring to the tperrno_string. |
| Type | INFO |
| Description | Failed to request a service. |
| Action | Fix the errors by referring to the tperrno_string. |
| Type | INFO |
| Description | The connection between a CLH and a UNIX domain socket was closed by tmdown. |
| Type | INFO |
| Description | The connection between a TMM and a UNIX domain socket was closed by tmdown. |
| Type | FATAL |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to previous error messages. |
| Type | ERROR |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to previous error messages. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a Tmax Gateway process to a TMM process. |
| Action | Confirm that a configuration file was not changed after the TMM booted. Keep the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | FATAL |
| Description | The version of a Tmax Gateway does not match with a TMM process. |
| Action | Re-install the Tmax engine. |
| Type | ERROR |
| Description | A remote gateway was closed abnormally. |
| Action | Check the Tmax status of the node where the related gateway was operating. Check for network problem between nodes. |
| Type | INFO |
| Description | A Tmax server successfully connected to a remote gateway. |
| Type | INFO |
| Description | A connection to a remote gateway was closed through a normal process. |
| Type | INFO |
| Description | A connection to a remote gateway was closed. |
| Action | Confirm that a remote node was not terminated. |
| Type | INFO |
| Description | The messages (num) stored while disconnecting from a remote gateway were deleted. |
| Type | ERROR |
| Description | Failed to send a message to a Tmax process (procname) because a TCP/IP socket was blocked. The related connection was closed because the number of retrials to send a message exceeded the limit defined inside the Tmax engine. The message was discarded. |
| Action | Check if the Tmax process (procname) was closed abnormally. If so, refer to the error messages output at the disconnection time. Otherwise, It may be a connection failure between the Tmax process (procname) and the NIX domain socket. Contact a system administrator to solve it. |
| Type | ERROR |
| Description | Failed to send a message to a CLH process. This error may occur due to a network failure or an overload on a CLH. |
| Action | Check the network status, Tmax system environment, and Tmax system processes. If the error cannot be resolved, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not send a message to a remote gateway (IP Address = rgw_ipaddr) due to a disconnection between a related gateway and a TCP/IP socket. The message was discarded. |
| Action | A related remote gateway process was closed abnormally or a network failure occurred. If the remote gateway process was closed abnormally, refer to the error messages that were output to solve the problem. Otherwise, check the network status. |
| Type | ERROR |
| Description | Could not send a message to a remote gateway (IP Address = rgw_ipaddr) because a TCP/IP socket was blocked. The related connection was closed because the number of attempts to re-send a message exceeded the limit defined inside the Tmax engine. The message was discarded. |
| Action | Check if the related remote gateway process was closed abnormally. If so, refer to the error message that was output at the time of disconnection. If the related remote gateway process was not closed abnormally, the issue may be caused by a network failure. |
| Type | WARNING |
| Description | A remote gateway connection was closed before sending a message. The message was ignored. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Failed to retrieve a pending list from a CLH process. |
| Action | Contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Invalid arguments found in Tmax gateway server command lines. |
| Action | Tmax engine servers must not be executed manually. |
| Type | ERROR |
| Description | The -a option was not specified in the CLOPT of a TUXGW. |
| Action | Specify an -a option for the name set in a tuxedo in the CLOPT. |
| Type | FATAL |
| Description | Could not register a Tmax Gateway process to a TMM process. |
| Action | Check that the configuration file was not changed after the TMM booted. Keep the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | A connection request from a remote gateway caused an error. |
| Action | Too many connection requests from other domains resulted in this error type. Connections between Tmax Gateways must be one-to-one. Several gateways cannot connect to a remote gateway. Check the gateway configurations of Tmax domains. |
| Type | FATAL |
| Description | Failed to find a gateway name in a configuration file. |
| Action | Check that the configuration file was not changed after a TMM booted. Keep the engine configuration consistent with the binary configuration file by running the "tmdown → cfl → tmboot" process again. |
| Type | ERROR |
| Description | A connection from a remote gateway closed before sending a message. A reply message will not be created. |
| Action | Check the status of the remote domain and the network connections. |
| Type | ERROR |
| Description | A heart beat check error occurred in a remote gateway. This might have occurred due to a network failure or an abnormal operation of a remote gateway. |
| Action | Check the network status and configuration environments of system management tools such as firewalls. The Tmax system in remote nodes must be checked as well. |
| Type | ERROR |
| Description | Incorrect configuration file for JEUSGW. |
| Action | Since the requested service name does not exist in the configuration file, recreate the configuration file. |
| Type | ERROR |
| Description | Incorrect configuration file for JEUSGW. |
| Action | Since the requested service name does not exist in the configuration file, recreate the configuration file. |
| Type | ERROR |
| Description | Incorrect configuration file for JEUSGW. |
| Action | Since the requested service name does not exist in the configuration file, recreate the configuration file. |
| Type | ERROR |
| Description | Could not convert a factor set in a -e or -o flag in a CLOPT to a valid file name. |
| Action | Check the CLOPT field in a GATEWAY section. The factor specified in a -e or -o flag must be a valid date value. |
| Type | INFO |
| Description | Entera gateway has started with this version. |
| Type | ERROR |
| Description | An incorrect opcode has been sent from a Tuxedo. |
| Action | Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | An invalid message was received. |
| Action | Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | An error reply has been sent from a Tuxedo. |
| Action | Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | An unsupported buffer type has been sent from a Tuxedo. |
| Action | Tmax supports only a FML32 of a Tuxedo FML buffer. Correct the Tuxedo configuration. |
| Type | ERROR |
| Description | A server process (svr) was closed abnormally while operating a service (svc). |
| Action | Check a service routine related to the error. Confirm that a related library is linked properly. |
| Type | ERROR |
| Description | FD_SETSIZE exceeded a limit supported by a system. |
| Action | Refer to </usr/include/bits/types.h>. Contact the TmaxSoft technical support team. |
| Type | WARNING |
| Description | An error occurred while registering a new server process in a Tmax engine. This error may occur when the number of starting processes exceeds the MAX value of the related server processes. |
| Action | Terminate existing server processes before registering new processes. |
| Type | ERROR |
| Description | While a Tmax engine was sending a message to a server process, a related server process was closed abnormally without waiting for a response. |
| Action | Check the server application code. It may be caused by a connection failure with a UNIX domain socket. If so, contact a system administrator. |
| Type | ERROR |
| Description | Could not to send a message to a client because a TCP/IP socket was blocked. A related connection was closed and the message was discarded because the number of attempts to re-send a message exceeded the limit defined inside a Tmax engine. |
| Action | Check if the server process was closed abnormally. If so, refer to the error messages that were output at the time of disconnection. Otherwise, the problem could be caused by a connection failure with a UNIX domain socket between a Tmax process and a server process. Contact a system administrator. |
| Type | ERROR |
| Description | A related process was closed while a Tmax process ID was sending a message to a Tmax process (tproc_no). |
| Action | Refer to the error messages output at the disconnection time. |
| Type | ERROR |
| Description | Could not send a message to a remote gateway due to a disconnection between a related gateway and a TCP/IP socket. A related remote node was closed abnormally or a network failure occurred. |
| Action | If the remote node process was closed abnormally, refer to the error messages that were output to solve the problem. Otherwise, check the network status. |
| Type | ERROR |
| Description | Could not send a message to a remote node because a TCP/IP socket was blocked. A related connection was closed because the number of attempts to re-send a message exceeded the limit defined inside a Tmax engine. The message was discarded. |
| Action | Check if a related remote node process was closed abnormally. If so, refer to the error messages that were output at the time of disconnection. If not, the cause of the problem may be a network failure. Contact a system administrator to solve it. |
| Type | ERROR |
| Description | Failed to find the svcname service in the tmconfig file. |
| Action | Check if the tmconfig file was not damaged. Confirm that the configuration file is compiled successfully. |
| Type | INFO |
| Description | A connection with a node (nodename) was terminated. |
| Type | ERROR |
| Description | An error occurred in a register request message received by a TMM process. |
| Action | A error type will be displayed. The types will be one of the following: - MAX_CLH_REACHED: Cannot create any more CLH processes because the number of current CLH processes reaches the MAXCLH value defined in the configuration file. Increase the MAXCLH value if more CLH processes are needed. - MAX_TMS_REACHED: Cannot create any more TMS processes because the number of current TMS processes reaches the MAXTMS value defined in the configuration file. Increase the MAXTMS value if more TMS processes are needed. - MAX_SPR_REACHED: Cannot create any more server processes because the number of current server processes reaches the maximum value defined in the configuration file. Increase the maximum value if more server processes are needed. - SVR_NOT_IN_CONFIG: Cannot find a requested server name in the configuration file. - ADM_MAIN_STARTED: Cannot create more than one tmadmin for the main mode. - MAX_ADM_REACHED: The number of the tmadmin processes of the main and sub modes exceeds the limit. - ALREADY_TMM_REGISTERED: Cannot create any more tmboot or tmdown processes because one of them has already been executed. |
| Type | ERROR |
| Description | A remote node (nodename) was processed as terminated because a ping message did not receive any response from it. |
| Action | Check if any problem exists in the remote node (nodename) network. If a remote node network is unstable or too slow, it is recommended to increase the NLIVEINQ value in the DOMAIN section of the configuration file. The default value is 30 seconds if the NLIVEINQ value is not set. Refer to the "Tmax Administrator's Guide" for more information on the configuration file settings. |
| Type | ERROR |
| Description | A connection to an EXTSVR type process was closed. |
| Action | Confirm that the EXTSVR type process operates correctly and that there are no system management device such as firewalls that are forcibly closing external connections. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | A license file read error occurred. |
| Action | 1) Install a license file to the correct path ($(TMAXDIR)/license/license.dat). 2) Check the version of a license file. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
| Type | ERROR |
| Description | A license file read error occurred. |
| Action | 1) Install a license file to the correct path ($(TMAXDIR)/license/license.dat). 2) Check the version of a license file. License files for Tmax engines prior to Tmax 3.5 are not compatible with Tmax 3.5. |
| Type | ERROR |
| Description | This host does not have valid license. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | ERROR |
| Description | This machine has more CPUs than licensed. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | ERROR |
| Description | A license has expired. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | FATAL |
| Description | A license check failed. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | FATAL |
| Description | Failed to copy a Tmax configuration file into PATHDIR. |
| Action | Confirm that PATHDIR is correctly specified in a Tmax configuration file and check if users have write permissions for the PATHDIR. |
| Type | ERROR |
| Description | An invalid license was detected. |
| Action | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | FATAL |
| Description | The versions of Tmax and a configuration file were not matched. |
| Action | Re-generate a binary configuration file using the cfl utility. |
| Type | ERROR |
| Description | A Tmax configuration change using the tmadmin utility failed. |
| Action | Refer to the err_msg, and remove the causes of the error. |
| Type | FATAL |
| Description | A binary configuration file was broken. |
| Action | Re-produce the binary configuration file using the cfl utility. |
| Type | INFO |
| Description | An application server svr_name was restarted due to previous errors. |
| Action | Refer to the previous error messages, and fix errors in the application program. |
| Type | ERROR |
| Description | An application server tried to register services that did not exist in a configuration file. |
| Action | Recompile application servers after running cfl and gst. |
| Type | INFO |
| Description | A TMM closed log files due to tmdown. |
| Type | ERROR |
| Description | An unregistered node sent a request message. |
| Action | All nodes of a domain must have the same Tmax version. |
| Type | ERROR |
| Description | A network crash occurred, and Tmax is trying to recover from the errors. |
| Action | Check the network status. |
| Type | INFO |
| Description | Tmax recovered from previous network errors. |
| Action | Check the network status for errors to prevent further Tmax errors. |
| Type | INFO |
| Description | Tmax started backup servers. |
| Action | Check the status of the primary node. |
| Type | INFO |
| Description | Not licensed to use MODULE_NAME. |
| TMM3011 | Contact the TmaxSoft technical support team to acquire a new license or upgrade a license. Then install a new license file. |
| Type | FATAL |
| Description | A binary configuration file had no information about a node (node_name). |
| Action | Check the node names in a configuration file. |
| Type | ERROR |
| Description | A connection with another node was closed. |
| Action | Check the communication status with the node. |
| Type | ERROR |
| Description | A registered node tried to register again. |
| Action | Check the domain configuration. When there are multiple domains in a network, a configuration error in a domain can affect other domains. |
| Type | ERROR |
| Description | More CLHs tried to register than were configured to be allowed. |
| Action | Check a configuration file, and then regenerate a binary configuration file. |
| Type | ERROR |
| Description | An error occurred while registering an unconfigured RQS. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | An error occurred while registering an unconfigured RQS. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | An error occurred while registering an unconfigured TMGW. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | More TMGWs tried to register than were configured to be allowed. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | More TMSs tried to register than were configured to be allowed. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | More TMSs tried to register than were configured to be allowed. |
| Action | Confirm that a binary configuration file was not modified after a tmboot. |
| Type | ERROR |
| Description | Registration to a node (nodeid) failed. |
| Action | Check the Tmax engine status of the node and the network status. |
| Type | ERROR |
| Description | Application servers provided different routing fields for a DDR route. |
| Action | Application servers must be compiled with the same FDL or SDL files. |
| Type | ERROR |
| Description | An error occurred while registering a server. |
| Action | 1) The type must be one of the following: - CLL: 1 - CLH: 2 - CAS: 3 - SVR: 4 - TMS: 5 - ADM: 7 - BOOT: 8 - DOWN: 9 - GATEWAY/TCPGW: 17 2) The error number is one of the following: - 102: registration request from an invalid server. - 122, 123, 124, 125: maximum number of servers already registered. - 131: only one instance of that server type can be registered. - 132: a server that is not in the configuration tried to register. - 141: only one master tmadmin can be started at the same time. |
| Type | ERROR |
| Description | An application server which was not configured to use DDR tried to register DDR information. |
| Action | Check the consistency between a configuration file and applications. |
| Type | ERROR |
| Description | Application servers provided different routing fields for a DDR route. |
| Action | Application servers must be compiled with the same FDL or SDL files. |
| Type | FATAL |
| Description | Failed to copy a Tmax configuration file into a PATHDIR. |
| Action | Confirm that PATHDIR is correctly specified in a configuration file and check whether users are allowed to write to the PATHDIR. Run the command again. |
| Type | INFO |
| Description | As many application servers have been restarted as MAXRSTART. |
| Action | Fix application errors by referring to the previous error messages. |
| Type | INFO |
| Description | Simultaneous starting of multiple processes of an application server caused a system overload. To prevent this, the processes should be added to a fork list and started later. |
| Type | ERROR |
| Description | Failed to add an application server to a fork list. |
| Type | ERROR |
| Description | Failed to add an application server (of a pid) to a fork list. |
| Type | INFO |
| Description | The server (of a pid) was started due to ASQCOUNT. |
| Type | WARNING |
| Description | Failed to connect to a node because it was performing a tmdown. |
| Type | ERROR |
| Description | Failed to register a service due to an invalid svri value. |
| Type | ERROR |
| Description | Failed to start a Tmax system internal process. |
| Action | Check the Tmax system environment and processes. |
| Type | ERROR |
| Description | Failed to acquire an environment variable block from a system (Windows). |
| Action | Check the system environment. |
| Type | ERROR |
| Description | Could not retrieve process handles used to terminate processes (Windows). |
| Action | Refer to the displayed error message then try the command again. |
| Type | ERROR |
| Description | Failed to execute a tmadmin/cfgadd command. |
| Action | Recheck the Tmax system environment and processes then run the command again. |
| Type | INFO |
| Description | A transaction recovery started in a TMS process. |
| Type | INFO |
| Description | A transaction recovery completed in a TMS process. |
| Type | INFO |
| Description | A connection with a CLH was closed due to a tmdown process. |
| Type | INFO |
| Description | A connection with a TMM was closed due to a tmdown process. |
| Type | FATAL |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | ERROR |
| Description | Failed to connect server processes with a Tmax engine due to a previous error. |
| Action | Refer to the previous error message. |
| Type | ERROR |
| Description | An error occurred while executing tx_open. |
| Action | Refer to the tx_errno error message. |
| Type | ERROR |
| Description | An error occurred while executing tx_open. |
| Action | Refer to the tx_errno error message. |
| Type | ERROR |
| Description | An error occurred while executing tx_open. |
| Action | Refer to the tx_errno error message. |
| Type | ERROR |
| Description | A XA-related DB API routine could not be set because a starting TMS could not be connected to a database. |
| Action | 1) Check that the OPENINFO item and database connection information are defined properly in the SVRGROUP section of a configuration file. 2) Check that the database library related to XA is linked properly. It is generally installed together with a database. If not, contact a database installation team. |
| Type | ERROR |
| Description | Executing tx_open caused an error. |
| Action | Check that the OPENINFO items are described properly in the SVRGROUP section of a configuration file. In particular, check that the user ID and password described in OPENINFO is correct. |
| Type | ERROR |
| Description | Executing xa_start for 2-phase commit caused an error. |
| Action | xa_start is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
| Type | WARNING |
| Description | xa_end was ignored because it was called without first performing xa_start.Transaction processing must be started by using tx_begin and terminated by using tx_commit or tx_rollback. These functions are operated as a pair. Therefore, this error occurs if tx_commit or tx_rollback are executed without performing tx_begin. In this case, a transaction will be rolled back. |
| Type | ERROR |
| Description | Executing xa_end for 2-phase commit caused an error. |
| Action | xa_end is a function provided by a RDBMS engine. Confirm that the RDBMS engine was started. |
| Type | WARNING |
| Description | A tx_begin() function was called in a service routine, but the service routine was terminated without calling tx_commit() or tx_rollback(). |
| Action | tx_rollback() is performed as a default in a Tmax engine, so perform the tx_commit() or tx_rollback() function in an intended location before performing tpreturn(). |
| Type | WARNING |
| Description | A xa_start() function was duplicately called and ignored. Transaction processing must be started by using tx_begin() and terminated by using tx_commit() or tx_rollback(). |
| Action | A transaction must be started by using tx_begin() and then finished by using tx_commit() or tx_rollback(). |
| Type | ERROR |
| Description | An error occurred while tx_commit() was executed. |
| Action | Check that the RDBMS engine is operating properly. Refer to the constant value started with TX_ in the xa.h or usrinc/tx.h files of the RDBMS directory in order to check txerrno. Refer to the error message manual of the database for more information. |
| 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. |
| Type | FATAL |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not establish a communication channel with a TMM process. |
| Action | Check that the stream pipe of $TMAXDIR/path was not damaged and make sure that the Tmax engine was properly booted. |
| Type | ERROR |
| Description | Could not register a TMS process to a TMM process. |
| Action | Confirm that a configuration file was not changed after a TMM boot. Make the engine configuration consistent with the binary configuration file by running the "tmdown →cfl → tmboot" process again. |
| Type | FATAL |
| Description | A TMS version does not match with a TMM process. |
| Action | Re-install the Tmax engine. |
| Type | ERROR |
| Description | Could not create a working thread for a Multithread TMS process. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Could not cancel a working thread from a Multithread TMS process. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Could not join a working thread to any other thread in a Multithread TMS process. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An invalid working thread index was found in a Multithread TMS process. |
| Action | Contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not mask a signal of a thread in a Multithread TMS process. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An internal error occurred from a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not put requests into a queue for a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | Could not get requests from a queue for a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | An error occurred in a working thread handle in a Multithread TMS due to an abnormal status of a kernel thread. |
| Action | Restart the TMS. |
| Type | FATAL |
| Description | Could not initialize a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Could not request for a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Could not reply to a working thread in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | FATAL |
| Description | Could not initialize a working thread pool in a Multithread TMS process. |
| Action | Check system resources. If the issue cannot be resolved, contact the TmaxSoft technical support team. |
| Type | ERROR |
| Description | A linked library does not match the type specified in a configuration file. |
| Action | Check the type specified in the configuration file. If it does not match, then change the type. |
| Type | ERROR |
| Description | uncfl was executed for a wrong file. |
| Action | Check whether uncfl was executed for a file for which cfl had been executed successfully. |
| Type | ERROR |
| Description | A TMAXDIR is not set. |
| Action | Set TMAXDIR as an environment variable. |
| Type | ERROR |
| Description | An error occurred while executing an OpenSCManager function. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while executing an OpenSCManager CreateService function. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while executing a %s function. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while executing an OpenService function. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Could not stop a Tmax service. |
| Action | Confirm that windows can control services normally. |
| Type | ERROR |
| Description | Failed to create a WSDL file. Could not create a Filename in a specified path. |
| Action | Check the file name and access authority. |
| Type | ERROR |
| Description | Failed to save data in a WSDL file. |
| Action | Check available disk space. |
| Type | ERROR |
| Description | A ServiceName to be provided from a web service gateway to an external source does not exist in binary file storing service information. |
| Action | Confirm that the ServiceName is correct and enter the ServiceName information in the binary file (Create a file to include service information → add the ServiceName information into the file with tmmbfgen -I command). |
| Type | ERROR |
| Description | An error occurred while executing xwsdlgen. The buffer type set in a configuration file was unknown (not STRING, CARRY, STRUCT, and FIELD). |
| Action | Change the unknown buffer type. |
| Type | ERROR |
| Description | A number entered with an equal sign (=) in a RestrictionString item was incorrect. |
| Action | The restriction attribute of the REQUEST and RESPONSE sections in a web service information file must be in the form of element_name="value", element_name="value",... Modify incorrect parts of an equal sign (=) in the RestrictionString item. |
| Type | ERROR |
| Description | A keyword item of restriction attributes in a web service information file was invalid. |
| Action | A valid keyword for the value of a restriction attribute is: length, minLength, maxLength, enumeration, pattern, minExclusive, maxExclusive, minInclusive, maxInclusive, totalDigit, and fractionDigits. Check and change the value. |
| Type | ERROR |
| Description | A RestrictionString of restriction attributes in a web service information file was not in the format of element_name="value". The "value" did not have an opening quotation mark ("). |
| Action | Change the restriction attribute to be a valid format. |
| Type | ERROR |
| Description | A RestrictionString of restriction attributes in a web service information file was not in the format of element_name="value". The "value" did not have an ending quotation mark ("). |
| Action | Change the restriction attribute to be a valid format. |
| Type | ERROR |
| Description | An error occurred while reading a web service configuration file due to insufficient memory. |
| Action | Set system resources to make sure that sufficient resources are available. |
| Type | ERROR |
| Description | Failed to open a web service gateway configuration file. |
| Action | Check the access authority to FileName. |
| Type | ERROR |
| Description | Could not read a web service gateway configuration file in a correct size. |
| Action | Check the file size, or check the system error message in case ReturnValue is a negative value. |
| Type | ERROR |
| Description | An error occurred in a LineNumber while reading a web service gateway configuration file. |
| Action | Check ErrorString and change the web service gateway configuration file. |
| Type | ERROR |
| Description | Failed to open a service information binary file. |
| Action | Check the access authority to FileName. |
| Type | ERROR |
| Description | Failed to read the number of services stored in a service information binary file. |
| Action | Check the file size, or check the system error message in case ReturnValue is a negative value. |
| Type | ERROR |
| Description | Could not read a service information binary file in a correct size. Failed to read the number of the stored services or service information. |
| Action | Check the file size, or check the system error message in case ReturnValue is a negative value. |
| Type | ERROR |
| Description | Could not read a service information binary file in a correct size. Failed to read parameter information. |
| Action | Check the file size, or check the system error message in case ReturnValue is a negative value. |
| Type | ERROR |
| Description | A current version of a service information binary file could not be processed in a current module. This error can occur when the service information binary file created in a new version of a module is used in a previous version. |
| Action | Create a lower version of the service information binary file using the tmmbfgen command. |
| Type | ERROR |
| Description | Failed to open a service information file. |
| Action | Check the access authority to FileName. |
| Type | ERROR |
| Description | An invalid TypeValue was included in the REQUEST or RESPONSE section of a service information file. |
| Action | Valid values for a type attribute in the REQUEST or RESPONSE sections of a service information file are: char, short, int, float, double, string, or carray. Set TypeValue to one of these values. |
| Type | ERROR |
| Description | An unknown parameter type was stored in meta data when executing the untmmbfgen command. This error may occur due to an incorrect meta data file created with tmmbfgen or due to a different version. |
| Action | Recreate a meta data file. |
| Type | ERROR |
| Description | An unknown TypeValue was included in the intype or outtype attributes of the SERVICE section in a service information file. |
| Action | Valid values for intype and outtype are: STRING, STRUCT, FDL, CARRAY, char, short, int, float, and double. Set TypeValue to one of these values. |
| Type | ERROR |
| Description | When the intype or outype attributes in the SERVICE section of a service information file contains a char, short, int, float, or double value and one or more parameters are defined in REQUEST, REQUEST, or RESPONSE section, then an error occurs. |
| Action | Correct the section to have only one parameter. |
| Type | WARNING |
| Description | Could not find StructName used in ServiceName in a service information file. An error will occur when an sdl file is not specified in SDLFILE that contains a StructName. |
| Action | A StructName must be defined in an SDL file. |
| Type | WARNING |
| Description | The number of parameters defining a StructName used in a ServiceName in a service information file did not match the number of fields in the structure referenced by an sdl file. An error will occur when StructName in an sdl file specified in SDLFILE is not the same as a structure specified in a service information file. |
| Action | Correct the structure information to be the same in both the SDL file and service information file. |
| Type | WARNING |
| Description | FieldName of a StructName used by ServiceName in a service information file was not compatible with a fieldname and type of a structure referenced to by an sdl file. An error will occur when the StructName in an sdl file specified in SDLFILE is not the same as a structure specified in a service information file. |
| Action | Correct the structure information to be the same in both in the SDL file and service information file. |
| Type | WARNING |
| Description | ParameterName used by ServiceName in a service information file does not exist in a fdl file. |
| Action | Correct the parameter information to be the same in both in the SDL file and service information file. |
| Type | WARNING |
| Description | The type of ParameterName used by ServiceName in a service information file was not compatible with the type of ParameterName defined in a fdl file. |
| Action | Correct the parameter information to be the same in both in the FDL file and service information file. |
| Type | ERROR |
| Description | Failed to create a service information file. |
| Action | Check the path, name, and access authority to FileName. |
| Type | ERROR |
| Description | Failed to store data specified in a service information file. |
| Action | Check for available disk space. |
| Type | ERROR |
| Description | Failed to create a service information binary file. |
| Action | Check the path, name, and access authority to FileName. |
| Type | ERROR |
| Description | Failed to store meta data in the service information binary file. |
| Action | If ReturnValue is a negative value, check the system error message. |
| Type | ERROR |
| Description | An error occurred because an invalid option was used when executing tmmbfgen. |
| Action | Check the manual then use a desired option. |
| Type | INFO |
| Description | Displays information required to execute a webservice gateway. |
| Type | ERROR |
| Description | An error occurred when receiving a SOAP request containing an item larger than a fixed size specified in a Tmax configuration file. |
| Action | Check the length of the service or field name, and then limit the size of the item within the bounds of max_size or real_size. |
| Type | ERROR |
| Description | An error occurred while interpreting a SOAP request. |
| Action | Refer to the request message. |
| Type | ERROR |
| Description | An error occurred while interpreting the body of a SOAP request. |
| Action | Refer to the request message. |
| Type | ERROR |
| Description | An error occurred while interpreting a SOAP request. This error occurs when interpreting an attribute or if a SOAP version is incorrect. |
| Action | Refer to the SOAP request message. |
| Type | ERROR |
| Description | An error occurred during a webservice gateway operation. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | Could not find requested service in meta data. |
| Action | Confirm that the service name is correct. |
| Type | ERROR |
| Description | Failed to convert a SOAP request to a Tmax message. |
| Action | Refer to the SOAP message. |
| Type | ERROR |
| Description | Failed to create a SOAP response message. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while creating a response message to a SOAP request. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while creating a response message to a SOAP request. |
| Action | This error occurs only when a wsdl type is set to RPC_ENCODED, so confirm that ws is correctly created. |
| Type | ERROR |
| Description | Failed to create a response message to a SOAP request. |
| Action | Refer to the response message and associated system error message. |
| Type | ERROR |
| Description | Failed to create a SOAP response message. |
| Action | Refer to the system error message displayed at the time of the error. |
| Type | ERROR |
| Description | An error occurred while interpreting a message received from a SOAP client. |
| Action | Check the xml of the data created in the SOAP client, and then correct it. |