System Messages: LIBTMIB Catalog 700-799


700	*ERROR: Cannot clear the `APPVER` option when `REQUEST_VERSION`, `VERSION_POLICY` or `VERSION_POLICY` information in RESOURCE is set.**
	Description	A set operation on `TA_OPTIONS` to disable the `APPVER` option is not allowable. The `REQUEST_VERSION`, `VERSION_RANGE` or `VERSION_POLICY` in *RESOURCE section is already configured.
	Action	Reset the `REQUEST_VERSION`, `VERSION_RANGE` or `VERSION_POLICY` to the default value by setting operation on `TA_REQUEST_VERSION`, `TA_VERSION_RANGE` or `TA_VERSION_POLCIY`.
	See Also	`MIB`(5), `TM_MIB`(5)
701	ERROR: Cannot clear the `APPVER` option when `REQUEST_VERSION`, `VERSION_POLICY` or `VERSION_POLICY` information in Group group_name is set.
	Description	A set operation on `TA_OPTIONS` to disable the `APPVER` option is not allowable. The `REQUEST_VERSION`, `VERSION_RANGE` or `VERSION_POLICY` in *GROUP section is already configured.
	Action	Reset the `REQUEST_VERSION`, `VERSION_RANGE` or `VERSION_POLICY` to default value by setting operation on `TA_REQUEST_VERSION`, `TA_VERSION_RANGE` or `TA_VERSION_POLCIY`. See Also `MIB`(5), `TM_MIB`(5)

702	*ERROR: Invalid state change specified (old* to new) because there is occurrence of the server be active**
	Description	A `SET` operation requested an invalid state change from old to new. There is occurrence of the server with status be active.
	Action	Consult the appropriate `MIB` reference page for the class in question for tables defining the valid state changes for that class and correct the request.
	See Also	`MIB`(5), `TM_MIB`(5)
706	ERROR: Cannot set TA_SCANUNIT or TA_SCANUNIT_MSEC with TA_SCANUNIT_EXT together
	Description	Can not specify `TA_SCANUNIT` or `TA_SCANUNIT_MSEC` with `TA_SCANUNIT_EXT` together for MIB `T_DOMAIN` `SET` operation
	Action	Please remove `TA_SCANUNIT` or `TA_SCANUNIT_MSEC` or `TA_SCANUNIT_EXT` from the MIB `T_DOMAIN` `SET` operation
	See Also	`MIB`(5), `TM_MIB`(5)
707	*ERROR: feature* is not supported on this platform**
	Description	The feature is only supported by some specific platforms but not by the current platform. The feature can be but not limited to XAAFFINITY,COMMONXID,NON_SINGLETON or FAN.
	Action	Disable the feature in your UBBCONFIG on the current platform.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
709	ERROR: BYPASSDOM related parameter can only be set when the RDMA option is set
	Description	Can not speficy `TA_BYPASSDOM_ID`, `TA_BYPASSDOM_SEQ_NUM` or `TA_BYPASSDOM_SHARED_DIR` for MIB `T_DOMAIN` `SET` operation, since the RDMA feature was not enabled in current UBBCONFIG.
	Action	Check your UBBCONFIG to confirm the `MODEL` is `MP` and daemon-related configurations (`RDMADAEMONIP` and `RDMADAEMONPORT`) is configured.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
712	ERROR: TA_BYPASSDOMAIN_ID, TA_BYPASSDOM_SHARED_DIR, TA_BYPASSDOM_SEQ_NUM should either all of them or none of them be specified.
	Description	`TA_BYPASSDOM_ID`, `TA_BYPASSDOM_SEQ_NUM` or `TA_BYPASSDOM_SHARED_DIR` for MIB `T_DOMAIN` `SET` operation should be all specified.
	Action	specify `TA_BYPASSDOM_ID`, `TA_BYPASSDOM_SEQ_NUM` or `TA_BYPASSDOM_SHARED_DIR` for MIB `T_DOMAIN` `SET` operation or remove all of them.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
713	ERROR: TA_MAXDOMAINS can only be configured when bypass domain feature is enabled.
	Description	`TA_MAXDOMAINS` for MIB `T_DOMAIN` `SET` operation can only be configured when bypass domain feature is enabled.
	Action	Enable bypass domain feature or remove `TA_MAXDOMAINS` for MIB `T_DOMAIN` `SET` operation.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
714	ERROR: TA_BYPASSDOM_SEQ_NUM must be less than MAXDOMAINS.
	Description	`TA_BYPASSDOM_SEQ_NUM` for MIB `T_DOMAIN` `SET` must be less than MAXDOMAINS.
	Action	Change a proper `TA_BYPASSDOM_SEQ_NUM` value for MIB `T_DOMAIN` `SET` operation or enlarge MAXDOMAINS.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
715	ERROR: TA_MAXMACHINES parameter must be less than 1023 when bypass domain feature is switch on.
	Description	`TA_MAXMACHINES` for MIB `T_DOMAIN` `SET` must be less than 1023 when bypass domain feature is switch on.
	Action	Change a proper `TA_MAXMACHINES` value for MIB `T_DOMAIN` `SET` operation.
	See Also	`EECS`, `UBBCONFIG`(5), `TM_MIB`(5)
740	ERROR: Cannot invalidate T_CACHING instance with matching configured T_SERVICE instance.
	Description	A `SET` operation on a `T_CACHING` class object to set the `TA_STATE` from `ACTIVE` to `INVALID` could not be satisfied because it be configured in `T_SERVICE` instance.
	Action	Invalidate the `T_SERVICE` that map to this `TA_CACHING_NAME` or change them to not have an associated `TA_CACHING_NAME`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
741	ERROR: Cannot set overlapping buffer types on CACHING Entry.
	Description	A `SET` operation on a `T_CACHING` class object failed because it set overlapping buffer types on CACHING Entry.
	Action	Specify a valid value for the `KEY_BUFTYPE`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
742	*ERROR: KEY parameteris invalid, the key format must be mykey_$request_mykey.*
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY` parameter.
	Action	Specify a valid value for the `KEY`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
744	ERROR: KEY_BUFTYPE parameter is invalid, there exists conflict between buffer types, they can't have same fields.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_BUFTYPE` parameter.
	Action	Specify a valid value for the `KEY_BUFTYPE`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
745	ERROR: KEY_FIELD parameter is invalid, could not start or end with '+'.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
746	ERROR: KEY_FIELD parameter is invalid, could not contain a null field.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
747	ERROR: KEY_FIELD parameter is invalid, [index1, index2] field is only for STRING,MBSTRING, X_OCTET or CARRAY.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
748	ERROR: KEY_FIELD parameter is invalid, the length of XML field must be <= 30 characters.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
749	ERROR: KEY_FIELD parameter is invalid, the maximum of of fields must be <= 8.
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)
750	*ERROR: KEY_FIELD parameter is invalid, field field_name* does not match syntax [index1,index2].**
	Description	A `SET` operation on a `T_CACHING` class object failed because the invalid `KEY_FIELD` parameter.
	Action	Specify a valid value for the `KEY_FIELD`.
	See Also	`UBBCONFIG`(5), `TM_MIB`(5)