System Messages: LIBTMIB Catalog 100-199


100	*ERROR: Class class* is not writable by this user**
	Description	A `SET` request for class could not be satisfied because the class contains no writable attributes for the invoking user.
	Action	In cases where the information is not intended to be writable by the invoking user, this message is informational only and there is no action to be taken. If the administrator intended the user to have write access to the indicated class, then the permissions on the class need to be relaxed by setting appropriate permissions values via the `T_CLASSATT` class or by resetting the `T_DOMAIN` `TA_MIBMASK` attribute value.
	See Also	`MIB`(5), `TM_MIB`(5)
102	ERROR: Unrecognized flags bits set on request
	Description	Flag values other than those documented in the reference pages have been specified.
	Action	Correct the request to contain only documented flag values.
	See Also	`MIB`(5), `TM_MIB`(5)
103	ERROR: Could not create child process to perform blocking admin function
	Description	The UNIX System call `fork`() failed to create a child process. The /AdminAPI uses this mechanism to implement blocking functionality such as server activation and deactivation that might otherwise impact the performance of the core application.
	Action	Check the operating system tunable parameters to make sure a sufficient number of processes may be started overall and by one user. Reconfigure the kernel if necessary.
	See Also	`fork`(2) in UNIX reference manuals, `MIB`(5), `TM_MIB`(5)
104	ERROR: Invalid or unspecified TUXCONFIG environment value
	Description	The `TUXCONFIG` environment variable is invalid or unspecified. `TUXCONFIG` must match the full path specified by the `UBBCONFIG` file.
	Action	Set the `TUXCONFIG` environment variable to the full path specified by the `UBBCONFIG` file.
	See Also	`tmunloadcf`(1)
105	ERROR: Unable to map machine identifiers in configuration file tuxconfig
	Description	The TUXCONFIG file has been corrupted or is being accessed from a machine not configured in the application.
	Action	Be sure that the file is being accessed from a machine that is configured in the application. If it is, then the file has likely become corrupted. In this case, remove the configuration file and regenerate it before continuing.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
106	ERROR: Unbooted configuration attempted on non-master site
	Description	Unbooted configuration via the `tpadmcall`(3c) interface was attempted from a site other than the configuration master machine.
	Action	Login to the master machine to do unbooted configuration or wait until the local machine is activated and access the /AdminAPI via `tpcall`(3c).
	See Also	`tpadmcall`(3c), `tpcall`(3c), `MIB`(5), `TM_MIB`(5)
107	*ERROR: Configuration file tuxconfig* is in an invalid state**
	Description	The tuxconfig file accessed by `tpadmcall`(3c) has become corrupted. The internal table representing the `RESOURCES` section of the `ubbconfig`(5) file is missing but other tables are present.
	Action	Remove the tuxconfig file and regenerate it from scratch before continuing.
	See Also	`tpadmcall`(3c), `ubbconfig`(5), `MIB`(5), `TM_MIB`(5)
108	ERROR: May not SET classes other than T_DOMAIN in an unconfigured application
	Description	A `SET` operation on a class other than `T_DOMAIN` failed because the application has not yet been configured. The only permissible `SET` operation on an unconfigured application is a `SET` of the `T_DOMAIN` class object to the `TA_STATE` `NEW`.
	Action	Configure the `T_DOMAIN` class object first and then other operations may be requested.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
109	ERROR: Failed to initialize internal MIB data structures
	Description	A call to `tpadmcall`(3c) could not be processed because the necessary internal data structures could not be initialized.
	Action	Consult the local userlog file for additional information on the failure. Messages found there will have catalog names and numbers that will indicate the cause and action for the underlying failure.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
110	*ERROR: Could not open temporary file tmpfile* for writing**
	Description	The temporary file name tmpfile could not be opened for writing while attempting to process a `tpadmcall`(3) call to `SET` a `NEW` `T_DOMAIN` class object.
	Action	Check the temporary file directory to be sure it is writable by the calling user and change the mode on the directory if necessary.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
111	ERROR: Could not write to temporary file tmpfile
	Description	The temporary file name tmpfile could not be written to while attempting to process a `tpadmcall`(3c) call to `SET` a `NEW` `T_DOMAIN` class object.
	Action	Make sure that sufficient disk space is available on the filesystem where the temporary file is being written.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
112	ERROR: Cannot set backup master on initial configuration
	Description	A `SET` operation creating a `NEW` `T_DOMAIN` class object specified a backup master logical machine identifier. This is not allowed in initial configuration since no logical machines are yet defined.
	Action	Create the configuration with only a master machine (no backup specified), then configure the machine you want to be the backup machine and then you can change the setting of `TA_MASTER` to include the newly configured machine as the backup master.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
113	ERROR: ACCSTATS may not be set in an inactive application
	Description	A `SET` operation on the `T_DOMAIN` class object attempted to set the `ACCSTATS` `TA_OPTIONS` attribute value in an inactive application.
	Action	Activate the application before attempting to set this attribute value
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
114	WARN: Partial deletion of configuration tables
	Description	A `SET` operation on the `T_DOMAIN` class changing the `TA_STATE` form INACTIVE to INVALID partially completed. Some configuration file tables could not be deleted.
	Action	Remove the binary configuration file manually.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
115	ERROR: Cannot invalidate T_ROUTING instance with matching configured T_SERVICE instance
	Description	A `SET` operation changing the `TA_STATE` of a `T_ROUTING` class object from INACTIVE to INVALID failed because the `TA_ROUTINGNAME` is referenced from a configured `T_SERVICE` or `T_SVCGRP` entry.
	Action	Invalidate the `T_SERVICE` and `T_SVCGRP` entries that map to this `TA_ROUTINGNAME` or change them to not have an associated `TA_ROUTINGNAME`.
	See Also	`MIB`(5), `TM_MIB`(5)
116	ERROR: Cannot set overlapping buffer types on identical range criteria name
	Description	A `SET` operation creating a `NEW` `T_ROUTING` class object specified a `TA_BUFTYPE` value that contains overlapping buffer types with another configured `T_ROUTING` class object.
	Action	Eliminate the overlapping buffer types from the request.
	See Also	`MIB`(5), `TM_MIB`(5)
117	ERROR: TA_CLASS/TA_OPERATION combination invalid for current system state
	Description	An /AdminAPI request passed to `tpadmcall`(3c) contained a TA_CLASS/TA_OPERATION combination that is not allowed in the current state of the application. This usually indicates the caller is not attached to the system (has called `tpinit`()) which is required to access certain classes.
	Action	Call `tpinit`(3c) before making the request.
	See Also	`tpadmcall`(3c), `tpinit`(3c), `MIB`(5), `TM_MIB`(5)
118	ERROR: TA_PASSWORD not correctly preprocessed
	Description	A `SET` operation on the `T_DOMAIN` class object failed because an update to the `TA_PASSWORD` attribute was requested but the request buffer was not preprocessed by the call using `tpcryptpw`(3c).
	Action	Call `tpcryptpw`(3c) before invoking the /AdminAPI.
	See Also	`tpcryptpw`(3c), `MIB`(5), `TM_MIB`(5)
119	ERROR: TA_PASSWORD specified without TA_SECURITY set
	Description	A `SET` operation on the `T_DOMAIN` class object contained a value for `TA_PASSWORD` without the `TA_SECURITY` attribute being set to indicate a security level for the application.
	Action	Either turn on `TA_SECURITY` for the application or remove the update to `TA_PASSWORD` from the request.
	See Also	`MIB`(5), `TM_MIB`(5)
120	ERROR: TA_SECURITY set without TA_PASSWORD
	Description	A `SET` operation for the `T_DOMAIN` class object specified a `TA_SECURITY` level but failed to include a `TA_PASSWORD` value for the secure application.
	Action	Add a `TA_PASSWORD` value to the request and preprocess the buffer using `tpcryptpw`(3c) before regenerating the request.
	See Also	`tpcryptpw`(3c), `MIB`(5), `TM_MIB`(5)
121	ERROR: Invalid system field value specified
	Description	An invalid value for a system generated field was included in the request buffer.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
122	ERROR: Could not validate security information
	Description	A `SET` operation on the `T_DOMAIN` class updating the security information failed because the system could not validate the security information passed on the master logical machine.
	Action	Consult the userlog on the master logical machine for more information on the failure and contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
123	ERROR: Inconsistent password information passed
	Description	A `SET` operation for the `T_DOMAIN` class object setting security information provided inconsistent password information to the master site logical machine.
	Action	Make sure that the request buffer is properly preprocessed by `tpcryptpw`(3c) before the request is made.
	See Also	`tpcryptpw`(3c), `MIB`(5), `TM_MIB`(5)
124	ERROR: Could not set password information for tmloadcf
	Description	A `SET` operation creating a `NEW` `T_DOMAIN` class object could not create the necessary keys and environment variables for initializing the security information for the application.
	Action	Consult the local userlog file for more information on the failure.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
126	*WARN: MIB mapping file file* contains invalid data**
	Description	file was found in the ${TUXDIR}/addonclasses directory but did not conform to the expected format for such a file.
	Action	Contact your Oracle TUXEDO system Technical Support as to whether this file should be removed or replaced. In the meantime, the reported failure does not affect core administration of the system. It may affect administration of the related add-on product temporarily until a replacement file is available.
	See Also	`MIB`(5), `TM_MIB`(5)
127	*WARN: Could not add class class* to mapping tables, tables full**
	Description	The add-on class class could not be added because the internal class mapping tables are full.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
128	WARN: Failed to load add-on MIB mappings
	Description	One or more failures were encountered while attempting to load add-on class mappings into the internal tables.
	Action	Consult instance specific userlog messages for more details and contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
129	ERROR: Unknown class referenced
	Description	A `SET` operation on a `T_CLASSATT` class object specified an unknown `TA_CLASSNAME` attribute value.
	Action	Correct the `TA_CLASSNAME` value in the request.
	See Also	`MIB`(5), `TM_MIB`(5)
130	ERROR: Cannot set `NEW` instance for known class with known attributes
	Description	A `SET` operation creating a `NEW` `T_CLASSATT` class object a core class with an already known list of attributes. New attributes may be created only for add-on classes.
	Action	The permissions for existing attributes may be changed by removing the state change attribute from the request.
	See Also	`MIB`(5), `TM_MIB`(5)
131	WARN: MIB mapping file file contains duplicate class class
	Description	The add-on class /AdminAPI mapping file file in the `${TUXDIR}/addonclasses` directory specified a duplicate class class for which mappings and possible attribute specifications already exist.
	Action	The duplicate entry is ignored. The file should be replaced or removed as recommended by your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
132	ERROR: Memory allocation failure processing /Admin request svc
	Description	An attempt dynamically to allocate memory from the operating system using `malloc` failed while adding error information to an /AdminAPI response for the administrative service svc.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	`malloc`(3) in UNIX reference manuals, `MIB`(5), `TM_MIB`(5)
133	ERROR: Fielded buffer access error Ferror
	Description	DESCRIPTION Fielded buffer access error Ferror occurred while adding error information to an /AdminAPI reply buffer.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`Fintro`(3fml), `MIB`(5), `TM_MIB`(5)
134	ERROR: TA_OPERATION not found in FML32 typed buffer
	Description	Missing value for TA_OPERATION in /AdminAPI request buffer. This is a required input parameter on all /AdminAPI requests and must have a value of GET, `SET` or GETNEXT.
	Action	Correct the input buffer to include an appropriate value for the TA_OPERATION attribute.
	See Also	`MIB`(5), `TM_MIB`(5)
135	ERROR: TA_OPERATION specified (op) is invalid
	Description	Invalid value op for TA_OPERATION included in /AdminAPI request buffer. This is a required input parameter on all /AdminAPI requests and must have a value of GET, `SET` or GETNEXT.
	Action	Correct the input buffer to include an appropriate value for the TA_OPERATION attribute.
	See Also	`MIB`(5), `TM_MIB`(5)
136	*ERROR: Invalid state change specified (old* to new)**
	Description	A `SET` operation requested an invalid state change from old to new.
	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), `WS_MIB`(5)
137	*ERROR: Invalid field type fldtype* for field fldid in internal structures**
	Description	The internal /AdminAPI structures contain an invalid field type fldtype for the field identifier fldid.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
138	*ERROR: FML32 error (Ferror) populating /Admin service reply buffer*
	Description	An FML32 error Ferror occurred while populating the reply buffer for an /AdminAPI request.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
139	*ERROR: System error (error) processing /Admin service request*
	Description	An internal Oracle TUXEDO system/T error occurred while processing an /AdminAPI request.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
140	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc` failed while processing an /AdminAPI request.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	`malloc`(3) in UNIX reference manuals, `MIB`(5), `TM_MIB`(5)
141	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc` failed while processing an /AdminAPI request.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	`malloc`(3) in UNIX reference manuals, `MIB`(5), `TM_MIB`(5)
142	*ERROR: Error accessing table* table of TUXCONFIG file**
	Description	An error occurred accessing the table table in the binary configuration file while processing an /AdminAPI request.
	Action	Contact your Oracle TUXEDO system Technical Support
	See Also	`MIB`(5), `TM_MIB`(5)
143	*ERROR: Error expanding table* table of TUXCONFIG file**
	Description	An error occurred while attempting to expand the table table in the binary configuration file as part of processing an /AdminAPI request.
	Action	If the configuration file is stored in a UNIX System file, then clean up the UNIX System filesystem to create additional space for the file to grow. If the configuration file is stored on a raw device, then additional extents may need to be added to allow for table expansion.
	See Also	Administering the Oracle TUXEDO System, `MIB`(5), `TM_MIB`(5)
144	*ERROR: Fielded buffer access error (Ferror) processing /Admin request*
	Description	An operation and/or value change that is not yet supported has been requested via the /AdminAPI.
	Action	Modify the request to use only supported features.
	See Also	`MIB`(5), `TM_MIB`(5)
145	ERROR: Unsupported operation/value specified
	Description	An operation and/or value change that is not yet supported has been requested via the /AdminAPI.
	Action	Modify the request to use only supported features.
	See Also	`MIB`(5), `TM_MIB`(5)
146	ERROR: Preimage failure for SET operation
	Description	A `SET` operation failed because the preimage specified with the request did not match the current image of the class object. Preimage processing is discussed in detail in `MIB`(5).
	Action	Modify the specified preimage to match the current class object or turn off preimage processing.
	See Also	`MIB`(5), `TM_MIB`(5)
147	ERROR: Permissions violation on SET request
	Description	A permissions violation has occurred while attempting to process an /AdminAPI `SET` request on the indicated class object. The attribute `TA_BADFLD` is set on the reply to indicate the field that is in violation of permissions.
	Action	The administrator can tune permissions for any attribute user combination to the maximum supported by the system. However, write access is not supported on all attributes in all class object states. Therefore, the update may need to be delayed until the class object is in a different state.

148	ERROR: Invalid attribute value on SET request
	Description	The value specified on a `SET` request for the attribute indicated by the `TA_BADFLD` attribute in the reply buffer is invalid. Valid values for writable attributes are specified on the `MIB` reference page for the appropriate class.
	Action	Correct the attribute value in question to a valid value.
	See Also	`MIB`(5), `TM_MIB`(5)
149	ERROR: TA_STATE specified on a SET with other changing attributes
	Description	A `SET` request included both an update to the `TA_STATE` attribute and an update to other attributes in the class as well. The /AdminAPI allows for only one of these actions in any one `SET` request.
	Action	Split the request into one that changes the non-state attributes and one that changes the state.
	See Also	`MIB`(5), `TM_MIB`(5)
150	ERROR: Key fields specified do not match any class instance
	Description	The key fields specified on a non state change `SET` request do not uniquely identify exactly one existing class object.
	Action	Check that the key fields specified are correct. Sometimes transient objects (those that automatically disappear when they deactivate) such as `T_CLIENT` objects can cause this symptom.
	See Also	`MIB`(5), `TM_MIB`(5)
151	WARN: Extra field present on /Admin SET request ignored, class/fldname
	Description	A `SET` operation on a class object contained an extraneous attribute fldname for update. The value for fldname is ignored.
	Action	Informational message only, no action required.
	See Also	`MIB`(5), `TM_MIB`(5)
152	ERROR: Required field not present on SET request
	Description	A `SET` operation creating a `NEW` class object failed to include a value for a required attribute. The missing required field identifier is returned as the value of the `TA_BADFLD` field in the reply buffer.
	Action	Supply a value for the missing required field before regenerating the request.
	See Also	`MIB`(5), `TM_MIB`(5)
153	ERROR: VTOC error accessing device
	Description	An error occurred while accessing the VTOC (Volume Table Of Contents) on the Oracle TUXEDO system device device.
	Action	device has been corrupted and needs to be destroyed and reinitialized before continuing. The device can be destroyed using `SET` requests on the `T_DEVICE` class to set the device state to INVALID. If this fails to clear the device, then manual interaction may be required. Consult your operating specific manuals for methods of clearing data in a device file.
	See Also	`MIB`(5), `TM_MIB`(5)
154	WARN: Timeout period expired on /Admin blocking request
	Description	A blocking /AdminAPI request timed out before the operation could be completed. The status of the operation is uncertain.
	Action	Increase the time out interval (`TA_MIBTIMEOUT`) before generating the request. A subsequent query on the object being updated may be used to determine the final result of the timed out operation.
	See Also	`MIB`(5), `TM_MIB`(5)
155	ERROR: Unbooted configuration update attempted in active application
	Description	A `SET` operation was attempted using `tpadmcall`(3c) from an unattached client (has not executed `tpinit`(3c)) in an active application.
	Action	Either defer the update until the application is inactive or attach to the application using `tpinit`(3c) before requesting the update using `tpcall`(3c).
	See Also	`tpadmcall`(3c), `tpcall`(3c), `tpinit`(3c), `MIB`(5), `TM_MIB`(5)
156	ERROR: Could not create temporary file name
	Description	A temporary file name could not be generated for /AdminAPI processing.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`tmpnam`(3) in UNIX reference manual, `MIB`(5), `TM_MIB`(5)
157	ERROR: Cannot activate class instance in an inactive application
	Description	A `SET` operation requesting a `TA_STATE` change to the `ACTIVE` state for a `T_GROUP`, `T_MACHINE`, `T_SERVER` or `T_SVCGRP` class object was requested via `tpadmcall`(3c) in an inactive application.
	Action	Defer activation of these class objects until the application is activated and the invoking administrative process has joined the application using `tpinit`(3c). At that point these class objects may be activated using `tpcall`(3c).
	See Also	`tpadmcall`(3c), `tpcall`(3c), `tpinit`(3c), `MIB`(5), `TM_MIB`(5)
158	*ERROR: TMIB service not available on site lmid* for global SET operation**
	Description	A `SET` operation could not be satisfied because global update of all bulletin boards is required and the required /AdminAPI service is not available for logical machine lmid.
	Action	Oracle TUXEDO system sites running releases prior to 5.0 do not have the /AdminAPI service and the requested global update cannot be done while those systems are active within the application. Otherwise, the indicated machines userlog file should be examined for possible causes of the missing service. The indicated machine can be deactivated and reactivated in an attempt to make the required service available.
	See Also	`MIB`(5), `TM_MIB`(5)
159	ERROR: Cannot set multiple type/subtype combinations in T_ROUTING class for an active application
	Description	A `SET` operation creating a `NEW` `T_ROUTING` class object in an active application specified multiple type/subtype combinations as part of the value for the `TA_BUFTYPES` attribute.
	Action	Split the request into one request per buffer type/subtype combination or defer the update until the application is completely deactivated.
	See Also	`MIB`(5), `TM_MIB`(5)
160	ERROR: MIB_SELF not allowed for non-client/server process
	Description	The `TA_FLAGS` value `MIB_SELF` was set on a call to `tpadmcall`(3c) from an unattached process.
	Action	Remove the setting of the `MIB_SELF` flag value or defer the request until the process is attached as a client or server.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
161	ERROR: Could not read RESOURCES section in configuration file tuxconfig
	Description	The `RESOURCES` section of the binary configuration file tuxconfig could not be read.
	Action	Remove and regenerate the binary configuration file before continuing.
	See Also	`MIB`(5), `TM_MIB`(5)
162	ERROR: Unable to map machine identifiers in configuration file tuxconfig
	Description	The TUXCONFIG file has been corrupted or is being accessed from a machine not configured in the application.
	Action	Be sure that the file is being accessed from a machine that is configured in the application. If it is, then the file has likely become corrupted. In this case, remove the configuration file and regenerate it before continuing.
	See Also	`tpadmcall`(3c), `MIB`(5), `TM_MIB`(5)
163	*ERROR: Configuration file tuxconfig* is in an invalid state**
	Description	The tuxconfig file accessed by `tpadmcall`(3c) has become corrupted. The internal table representing the RESOURCES section of the `ubbconfig`(5) file is missing but other tables are present.
	Action	Remove the tuxconfig file and regenerate it from scratch before continuing.
	See Also	`tpadmcall`(3c), `ubbconfig`(5), `MIB`(5), `TM_MIB`(5)
164	ERROR: May not decrease TA_MAX with active servers above new maximum
	Description	A `SET` operation on a `T_SERVER` class object request a decrease in the setting for the `TA_MAX` attribute with active servers beyond the new setting.
	Action	Deactivate the associated servers above the new setting for `TA_MAX` before attempting to change the value.
	See Also	`MIB`(5), `TM_MIB`(5)
166	ERROR: Cannot change workstation handler state to `DEAD`
	Description	A `SET` operation on a `T_CLIENT` class object representing a workstation handler (`WSH`) changing the `TA_STATE` to `DEAD` failed. Workstation handlers may only be set to a `TA_STATE` of `DEAD` through their `T_WSH` class object.
	Action	Use the `T_WSH` class to set the state for the workstation handler.
	See Also	`MIB`(5), `TM_MIB`(5), `WS_MIB`(5)
167	*ERROR: TA_MINHANDLERS(min) must be less than or equal to TA_MAXHANDLERS(max)*
	Description	A `SET` operation on a `T_WSL` class object set the value for the minimum number of workstation handlers (min) greater than the value for the maximum number of handlers (max).
	Action	Correct the request to specify a minimum value less than or equal to the maximum value.
	See Also	`MIB`(5), `TM_MIB`(5), `WS_MIB`(5)
168	ERROR: Failed to advertise dynamic /Admin service, no service name
	Description	The dynamic /AdminAPI service could not be advertised because the internal routines did not supply a service name to be associated with the function.
	Action	Contact your Oracle TUXEDO system Technical Support.
	See Also	`MIB`(5), `TM_MIB`(5)
169	ERROR: TA_MINHANDLERS may not be increased for an active T_WSL object with a TA_MAXHANDLERS value of 0
	Description	A `SET` operation on an active `T_WSL` class object attempted to increase the value for `TA_MINHANDLERS` with a configured value for `TA_MAXHANDLERS` of 0.
	Action	Deactivate the `T_WSL` class object before attempting to increase the `TA_MINHANDLERS` value.
	See Also	`MIB`(5), `TM_MIB`(5)
170	*ERROR: /Admin service svc* on machine lmid unavailable**
	Description	The /AdminAPI service svc is not available on logical machine lmid to satisfy the request.
	Action	This error usually indicates that information specific to a particular site is referenced but the site is not currently active. In this case, the request should be redirected to an active site or deferred until the site in question is active.
	See Also	`MIB`(5), `TM_MIB`(5)
171	*ERROR: /Admin service svc* unavailable**
	Description	The /AdminAPI service svc is not available to satisfy the current request.
	Action	Oracle TUXEDO system sites running releases prior to 5.0 do not have the /AdminAPI service and the requested service cannot be done while those systems are active within the application. Pre-5.0 machines can be deactivated so that the request can be completed.
	See Also	`MIB`(5), `TM_MIB`(5)
172	INFO: Abortively terminating WSH process pid
	Description	An /AdminAPI request to change the state of a `WSH` to `DEAD` has caused the system to terminate the process pid with the `SIGKILL` signal.
	Action	Informational message only, no action required.
	See Also	`MIB`(5), `TM_MIB`(5)
173	ERROR: TA_GRPNO may not be changed because of active servers in group
	Description	A `SET` operation on a `T_GROUP` class object attempted to change the `TA_GRPNO` value while some server(s) in the server group were active.
	Action	Deactivate the remaining servers in the server group before attempting the modification.
	See Also	`MIB`(5), `TM_MIB`(5)
175	WARN: Server RESTART set to Y and MAXGEN set < 2
	Description	A `SET` operation on a `T_SERVER` class object set the `RESTART` option but the `TA_MAXGEN` value was set to a value less than 2 so that the server will never be restarted.
	Action	No action is required. Normally, the `TA_MAXGEN` value should be set higher so that the server will restart.
	See Also	`MIB`(5), `TM_MIB`(5)