System Messages: CMDTUX Catalog 8300-8399


8300	ERROR: Invalid password identifier format, and ${IDENTIFIER} could not be used together
	Description	***** and ${IDENTIFIER} cannot be set together for password in OPENINFO.
	Action	remove ***** or ${IDENTIFIER}.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
8323	ERROR: needs the -x option to run tmloadcf.
	Description	***** should be executed with -x option.
	Action	Add the -x option while execute the tmloadcf command.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
8324	ERROR: does not go with -x options to run tmloadcf.
	Description	***** should not be executed with -x option.
	Action	Remove the -x option while execute the tmloadcf command.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
8325	ERROR: The option is not allowed if the option ${IDENTIFIER} is not specified in RESOURCES section.*
	Description	***** should not be executed with -x option.
	Action	The ${IDENTIFIER} option should be specified when the previously mentioned option is set.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
8326	ERROR: Option needs to be set in RESOURCES section.*
	Description	Option ***** should be set in the RESOURCES section.
	Action	Add the specific option in the RESROUCES section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
8341	ERROR: EXT_AA option is not enable
	Description	The Tuxedo `OPTIONS` must be configured with `EXT_AA`.
	Action	Correct the error in `TUXCONFIG` and then reboot the Tuxedo.
	See Also	`OAUTHSVR`(5), `tmboot`(1), `tmshutdown`(1)
8342	ERROR: Authentication level must be USER_AUTH, ACL or MANDATORY_ACL.
	Description	The Tuxedo `SECURITY` must be configured with `USER_AUTH`, `ACL`, or `MANDATORY_ACL`.
	Action	Correct the error in `TUXCONFIG` and then reboot the Tuxedo.
	See Also	`OAUTHSVR`(5), `tmboot`(1), `tmshutdown`(1)
8347	ERROR: Default Tuxedo resource [%s : %s : %s] is not protected.
	Description	Default resource is not defined as protected resource in OAM. OAM always require a resource to figure out the authentication level and policies to authenticate a user. Administrator need define a default resource.
	Action	Define default protected resource in OAM.
	See Also	`OAUTHSVR`(5)
8354	ERROR: Duplicate CACHING section present.
	Description	More than one CACHING section has been specified in the configuration file.
	Action	Modify the configuration file so that only one CACHING section is specified.
	See Also	`ubbconfig`(5)
8355	ERROR: The GROUPS section must appear before the CACHING section.
	Description	The CACHING section has been defined before the GROUPS section in the configuration file.
	Action	Edit the configuration file such that the RESOURCES, MACHINES, and GROUPS sections are the first three sections in that order.
	See Also	code>ubbconfig(5)
8356	ERROR: Caching name must be <= 30 characters.
	Description	The `CACHING` identifier must be <= 30 characters.
	Action	Specify a value that is less than or equal to 30 characters.
	See Also	`ubbconfig`(5)
8357	*The KEY_FIELD parameter is invalid in CACHING entry entry_name.*
	Description	The `KEY_FIELD` list specified in an entry in the CACHING section of the UBBCONFIG file is invalid.
	Action	Specify valid `KEY_FIELD` string, and reload the configuration file.
	See Also	`ubbconfig`(5)
8358	*ERROR: CACHING entry enrty_name* specifies an illegal KEY_BUFTYPE of ALL.**
	Description	The CACHING entry flagged in the error message has a `KEY_BUFTYPE` of `ALL`. This is not allowed.
	Action	Specify a valid buffer type for the CACHING entry in error, and reload the configuration file.
	See Also	`ubbconfig`(5)
8359	*ERROR: The KEY_BUFTYPE parameter in CACHING entry entry_name* start with ','.**
	Description	The `KEY_BUFTYPE` list specified in an entry in the CACHING section of the UBBCONFIG file starts with a comma. This is not allowed.
	Action	Ensure that at least one valid buffer type is specified in the `KEY_BUFTYPE` string, and make sure that the string does not begin with a comma. When the error has been fixed, reload the configuration file.
	See Also	`ubbconfig`(5)
8360	*ERROR: CACHING entry entry_name* contains an excessively long type name type_name.**
	Description	One of the buffer type names specified in the `KEY_BUFTYPE` parameter of CACHING entry of the UBBCONFIG file exceeds the maximum allowed length. The maximum allowed length of a buffer type name is 8 bytes.
	Action	Change the buffer type name so that it is no longer than 8 bytes, and reload the configuration file.
	See Also	`ubbconfig`(5)
8361	*ERROR: CACHING entry entry_name* contains a null buffer type name.**
	Description	The `KEY_BUFTYPE` parameter specified in CACHING entry contains one or more null buffer type names.
	Action	Change the `KEY_BUFTYPE` entry flagged as being in error. Make certain that the beginning of the `KEY_BUFTYPE` string specifies a valid buffer type identifier, and that the string does not start with a punctuation mark. Also, make sure that each semicolon in the `KEY_BUFTYPE` string is followed by a valid buffer type identifier. Reload the configuration file.
	See Also	`ubbconfig`(5)
8362	*ERROR: CACHING entry entry_name* contains an unexpected comma.**
	Description	The `KEY_BUFTYPE` parameter specified in CACHING section of the UBBCONFIG file contains an unexpected comma.
	Action	Change the `KEY_BUFTYPE` entry flagged as being in error. The only places where commas are allowed to occur in `KEY_BUFTYPE` entries are between entries of a list of multiple subtypes of a particular type. When the error has been fixed, the configuration file should be reloaded.
	See Also	`ubbconfig`(5)
8363	*ERROR: CACAHING entry entry_name* - only STRING, MBSTRING, CARRAY, VIEW, FML, X_OCTET, X_C_TYPE, X_COMMON,RECORD,or XML type is allowed in CACHING section.**
	Description	The `KEY_BUFTYPE` parameter specified in CACHING entry contains invalid type name.
	Action	Change the `KEY_BUFTYPE`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8364	*ERROR: CACHING entry entry_name* contains an excessively long subtype name subtype_name.**
	Description	One of the buffer type names specified in the `KEY_BUFTYPE` parameter of CACHING section entry of the UBBCONFIG file exceeds the maximum allowed length. The maximum allowed length of a buffer subtype name is 16 bytes.
	Action	Change the buffer subtype name so that it is no longer than 16 bytes, and reload the configuration file.
	See Also	`ubbconfig`(5)
8365	*ERROR: CACHING entry entry_name* contains a null buffer subtype name.**
	Description	One of the buffer subtype names specified in the `KEY_BUFTYPE` parameter of CACHING section entry of the UBBCONFIG file is null. This is not allowed.
	Action	Change the buffer subtype name, and reload the configuration file.
	See Also	`ubbconfig`(5)
8366	*ERROR: CACHING entry entry_name* specified both '' and a specific subtype name.*
	Description	A subtype list contained within the `KEY_BUFTYPE` parameter of a CACHING section entry of the UBBCONFIG file specified both the wild-card subtype "*" and a specific subtype name. This is not allowed.
	Action	If the application should accept all subtype names, specify "" without specifying any specific subtype names. If the application should accept only specific subtype names, remove "" from the list of subtype names. When the change has been made, reload the configuration file.
	See Also	`ubbconfig`(5)
8367	*ERROR: CACHING entry entry_name specifies '' where it is not allowed.*
	Description	The `KEY_BUFTYPE` parameter of a CACHING section entry of the UBBCONFIG file specified '*' as a buffer subtype. This is not allowed.
	Action	If caching in a VIEW/VIEW32, specify the specific buffer type to be routed on. If routing on an `FML/FML32` buffer, no buffer subtypes are allowed. Reload the configuration file once it has been modified.
	See Also	`ubbconfig`(5)
8368	ERROR: CACHING entry entry_name>/var>: Must have subtype for VIEW,VIEW32, X_C_TYPE, RECORD,and X_COMMON.
	Description	One of buffer type type which is VIEW, VIEW32, X_C_TYPE, RECORD,or X_COMMON within the `KEY_BUTYPE` parameter of a CACHING section entry of the UBBCONFIG file doesn't have subtype.
	Action	Specify subtype for buffer types of VIEW, VIEW32, X_C_TYPE, RECORD,and X_COMMON, and reload the configuration file.
	See Also	`ubbconfig`(5)
8369	ERROR: CACHING entry entry_name>/var> contains an unexpected colon or comma.
	Description	The `KEY_BUFTYPE` parameter specified in an entry in the CACHING section of the UBBCONFIG file contains an unexpected colon or comma.
	Action	Examine the `BUFTYPE` entry flagged as being in error to determine the exact problem. A colon may occur only between a name of a type and the name of the first acceptable subtype. A comma may occur only between names of subtypes. When the error has been corrected, reload the configuration file.
	See Also	`ubbconfig`(5)
8370	*ERROR: CACHING entry entry_name* contains a duplicate type(type_name)/subtype(subtype_name) pair.**
	Description	The `KEY_BUFTYPE` parameter of a CACHING section entry in the UBBCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the `KEY_BUFTYPE` parameter specified duplicate type pairs.)
	Action	Modify the `KEY_BUFTYPE` parameter so that the same type/subtype pair is not specified more than once. Reload the configuration file.
	See Also	`ubbconfig`(5)
8371	*ERROR: CACHING entry entry_name* too many buffer type/subtypes specified.**
	Description	The maximum number of type/subtype combinations that a service can accept was exceeded.
	Action	This is a fixed limit that requires a recompiled Oracle TUXEDO system version to increase. Contact your Oracle TUXEDO system Technical Support. Other options are: Reduce the number of type/subtype combinations by using "*" for a subtype wildcard. Have the server process call `tptypes()` on its input buffer, and enforce its own rules concerning allowed buffer type/subtype combinations.
	See Also	`ubbconfig`(5)
8372	*ERROR: CACHING entry entry_name* contains a duplicate type(type_name)/subtype(subtype_name) pair.**
	Description	The `KEY_BUFTYPE` parameter of a CACHING section entry in the UBBCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the `KEY_BUFTYPE` parameter specified duplicate type pairs.)
	Action	Modify the `KEY_BUFTYPE` parameter so that the same type/subtype pair is not specified more than once. Reload the configuration file.
	See Also	`ubbconfig`(5)
8373	ERROR: CACHENAME parameter in CACHING entry must be <= 78 characters.
	Description	The `CACHENAME` parameter in CACHING entry must be <= 78 characters.
	Action	Specify a value that is less than or equal to 78 characters.
	See Also	`ubbconfig`(5)
8374	ERROR: KEY_BUFTYPE parameter in CACHING entry must be <= 255 characters.
	Description	The `KEY_BUFTYPE` parameter must be <= 255 characters.
	Action	Specify a value that is less than or equal to 255 characters.
	See Also	`ubbconfig`(5)
8375	ERROR: KEY_FIELD parameter in CACHING entry must be <= 255 characters.
	Description	The `KEY_FIELD` parameter must be <= 255 characters.
	Action	Specify a value that is less than or equal to 255 characters.
	See Also	`ubbconfig`(5)
8376	ERROR: KEY parameter in CACHING entry must be <= 127 characters.
	Description	The `KEY` parameter must be <= 127 characters.
	Action	Specify a value that is less than or equal to 255 characters.
	See Also	`ubbconfig`(5)
8377	*WARN: CACHING entry entry_name* (for SERVICE service_name) is not defined in the CACHING section.**
	Description	The `CACHINGENTRY` parameter in one `SERVICE` entry is not defined in the `CACHING` section.
	Action	Specify a valid `CACHINGENTRY`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8379	*ERROR: The subtype in KEY_BUFTYPE of CACHING entry entry_name* should not contain semicolon, colon, comma, or asterisk characters.**
	Description	The `KEY_BUFTYPE` parameter of a CACHING entry of the UBBCONFIG file specified a subtype which contain semicolon, colon, comma, or asterisk characters. This is not allowed.
	Action	Specify a valid value as the subtype, and reload the configuration file.
	See Also	`ubbconfig`(5)
8380	ERROR: RM_ERR_THRESHOLD parameter must be >= 0 and <=1000
	Description	RM_ERR_THRESHOLD specifies the times of XAERR_RMFAIL and XAERR_RMERR returned by xa_start()/xa_open(). If RM_ERR_THRESHOLD is set to non-zero value, Server Reconnect to RM feature is enabled. The Range is [0,1000].
	Action	Specify a valid value, and reload the configuration file.
	See Also	`ubbconfig`(5)
8381	ERROR: RM_ERR_INTERVAL parameter must be >= 1 and <= 32767
	Description	RM_ERR_INTERVAL specifies the interval time for tuxedo server to try to connect the RM. If server reconnect to RM feature is enabled, the default value of RM_ERR_INTERVAL is 30s. the Range is [1,32767]
	Action	Specify a valid value, and reload the configuration file.
	See Also	`ubbconfig`(5)
8382	WARN: Feature RM reconnect to Server is not enabled.
	Description	Feature RM reconnect to Server is not enabled, because RM_ERR_THRESHOLD is set as 0
	Action	To enable Feature RM reconnect to Server, RM_ERR_THRESHOLD should be > 0 and <=1000.
	See Also	`ubbconfig`(5)
8383	ERROR: The length of an XML field in KEY_FIELD parameter of a CACHING entry must be <= 30 characters.
	Description	The XML field in `KEY_FIELD` parameter of a CACHING entry must be <= 30 characters.
	Action	Specify a valid value as the XML field, and reload the configuration file.
	See Also	`ubbconfig`(5)
8384	*ERROR:The field number in KEY_FIELD parameter of a CACHING entry entry_name* must be <= 8.**
	Description	The field number in `KEY_FIELD` parameter of a CACHING entry entry_name must be <= 8.
	Action	Specify a valid value as the `KEY_FIELD`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8385	*ERROR: The KEY_FIELD fields_name* for buffer types STRING, CARRAY, MBSTRING or X_OCTET must match the syntax[index1, index2].**
	Description	The field in `KEY_FIELD` parameter for buffer types STRING, CARRAY, MBSTRING or X_OCTET must match the syntax[index1, index2]. index1, index2 start from 1.
	Action	Specify a valid value as the `KEY_FIELD`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8386	*ERROR: The CACHING entry entry_name* specifies an invalid KEY_BUFTYPE parameter.**
	Description	There exists conflict between buffer types in `KEY_BUFTYPE` parameter of a CACHING entry, they can't have same fields.
	Action	Specify a valid value as the `KEY_BUFTYPE`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8387	*ERROR: The CACHING entry entry_name* specifies an invalid KEY_BUFTYPE parameter.**
	Description	A CACHING entry should not set subtype for CARRAY, X_OCTET, STRING, MBSTRING,FML, FML32 and XML.
	Action	Specify a valid value as the `KEY_BUFTYPE`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8388	*ERROR:The CACHING entry entry_name* specifies an invalid KEY_FIELD parameter.**
	Description	The `KEY_FIELD` in CACHING entry could not start or end with '+' character.
	Action	Specify a valid value as the `KEY_FIELD`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8389	*ERROR:The CACHING entry entry_name* specifies an invalid KEY_FIELD parameter.**
	Description	The `KEY_FIELD` in CACHING entry, could not contain a null field.
	Action	Specify a valid value as the `KEY_FIELD`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8390	*ERROR:The CACHING entry entry_name* specifies an invalid KEY parameter.**
	Description	The format for `KEY` in CACHING entry, must be [mykey1][_$request_][mykey2], and the separator is '_' character.
	Action	Specify a valid value as the `KEY`, and reload the configuration file.
	See Also	`ubbconfig`(5)
8391	*ERROR:The CACHING entry entry_name* specifies an invalid KEY_FIELD parameter.**
	Description	The `KEY_FIELD`parameter is invalid in a CACHING entry. The syntax [index1, index2] field is only for STRING, MBSTRING,CARRAY or X_OCTET.
	Action	Specify a valid value as the `KEY_FIELD`, and reload the configuration file.
	See Also	`ubbconfig`(5)