# Chapter 4. TUXEDO Core MIB

The TUXEDO system Core MIB defines the set of groups through which the fundamental aspects of an application may be configured and managed. This includes management of machines, servers, networking, and load balancing.

The TUXEDO Core MIB defines the basic objects that form a TUXEDO application. The Core MIB is the main information repository to control the operation and configuration of the application. When an application is active, the Core MIB contains groups related to the runtime activity of your application. You can use this information to monitor the behavior of your application. The Core MIB consists of the following groups.

Group Name | Description
--- | ---
`tuxTBridgeTbl` | Network connection
`tuxTclientTbl` | Client
`tuxTconnTable` | Conversation
`tuxTdeviceTbl` | Device
`tuxTwhichCfgDev` | Control MIB for `tuxTdeviceTbl`
`tuxTdomain` | Domain information
`tuxTgroupTable` | Server group
`tuxTmachineTable` | Machine configuration attributes
`tuxTmachineActive` | Runtime machine characteristics
`tuxTmsgTable` | Message queue
`tuxTqueueTable` | Server queue
`tuxTroutingTable` | Routing criteria
`tuxTsrvrTbl` | Server configuration attributes
`tuxTsrvrTblExt` | Server runtime characteristics
`tuxTsvcTbl` | Service
`tuxTsvcGrp` | Service-group configuration attributes
`tuxTlistenTbl` | /T listeners
`tuxTranTbl` | Transaction
`tuxTulogTable` | Userlog
`tuxTulogCtrl` | Control filter MIB for `tuxTulogTable`
`tuxTnetMapTbl` | Maps logical machine IDs to network groups
`tuxTnetGrpTbl` | Application attributes of network groups

## tuxTBridgeTbl

This group represents runtime attributes pertaining to connectivity between logical machines making up an application. These attribute values represent connection status and statistics. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine. The index into the table consists of `tuxTBridgeLmid` and `tuxTBridgeNetworkGrpNo`. In TUXEDO 6.4, `SET` requests are allowed only for the `DEFAULTNET` network group, so all SET requests should use `0` for `tuxTBridgeNetworkGrpNo` in the SNMP index.

Variable Name | Object ID
--- | ---
`tuxTBridgeLmid` | .1.3.6.1.4.1.140.300.16.1.1.1
`tuxTBridgeState` | .1.3.6.1.4.1.140.300.16.1.1.2
`tuxTBridgeCurTime` | .1.3.6.1.4.1.140.300.16.1.1.3
`tuxTBridgeConTime` | .1.3.6.1.4.1.140.300.16.1.1.4
`tuxTBridgeSuspTime` | .1.3.6.1.4.1.140.300.16.1.1.5
`tuxTBridgeRcvdByte` | .1.3.6.1.4.1.140.300.16.1.1.6
`tuxTBridgeSentByte` | .1.3.6.1.4.1.140.300.16.1.1.7
`tuxTBridgeRcvdNum` | .1.3.6.1.4.1.140.300.16.1.1.8
`tuxTBridgeSentNum` | .1.3.6.1.4.1.140.300.16.1.1.9
`tuxTBridgeFlowCnt` | .1.3.6.1.4.1.140.300.16.1.1.10
`tuxTBridgeCurEncryptBits` | .1.3.6.1.4.1.140.300.16.1.1.11
`tuxTBridgeNetworkGrpNo` | .1.3.6.1.4.1.140.300.16.1.1.12
`tuxTBridgeNetworkGrpName` | .1.3.6.1.4.1.140.300.16.1.1.13

### tuxTBridgeLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..61`))

> #### Access

> read-only

> #### Description

> `DisplayString` is of the format: `LMID1``[,``LMID2``]`

> `LMID1`
>   Is the logical machine identifier for network connection and is in the range from one to sixty-one characters.

> `LMID2`
>   Is the destination logical machine identifier for network connection and is in the range from one to sixty-one characters.

### tuxTBridgeState

> #### Syntax

> `INTEGER {active(1), inactive(2), suspended(3), pending(4)}`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET:{active(1)|inactive(2)|suspended(3)|pending(4)}`
>   A `GET` operation retrieves runtime information for the selected `tuxTBridgeTbl` instance(s). A `tuxTBridgeLmid` attribute value with only one logical machine identifier matches all active connections from `LMID1` to other machines in the application. In this case, each retrieved record contains an expanded `tuxTBridgeLmid` attribute value with the destination LMID filled in. The following states indicate the meaning of a `tuxTBridgeState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   The connection is established and active.

> `inactive(2)`
>   The connection is inactive. This state is only returned when status is requested on a particular connection, that is, both LMIDs are specified in the `tuxTBridgeLmid` attribute and the source logical machine is reachable.

> `suspended(3)`
>   An established connection was terminated due to an error condition, and reconnection has been suspended for at least the amount of time indicated in the `tuxTBridgeSuspTime` attribute value.

> `pending(4)`
>   An asynchronous connection has been requested but has not yet completed. The final outcome of the connection request has not been determined. This state is only supported on TUXEDO 6.4 or later.

> `SET: {active(1)|inactive(2)|suspended(3)|pending(4)}`
>   A `SET` operation updates runtime information for the selected `tuxTBridgeTbl` object. The following states indicate the meaning of a `tuxTBridgeState` set in a `SET` request. States not listed cannot be set.

> `active(1)`
>   TUXEDO 6.3 and earlier: Activate the `tuxTBridgeTbl` object by establishing a connection between the indicated logical machines. This operation fails if only one logical machine is specified, if either of the two machines is not active, or if the source logical machine is not reachable. State change allowed in the `inactive(2)` and `suspended(3)` states. Successful return leaves the object in the `active(1)` state. TUXEDO 6.4 and later: Activate the `tuxTBridgeTbl` instance by establishing an asynchronous connection between the indicated logical machines. This operation fails if only one machine is specified, if either of the machines is not active, or if the source machine is not reachable. When in the `pending(4)` state, the success or failure of the connection has not yet been determined. The BRIDGE may continue to process other events and data while the connection is outstanding. This state change is allowed in the `inactive(2)` and `suspended(3)` states. Successful return leaves the instance in the `active(1)` or `pending(4)` state.

> `inactive(2)`
>   Deactivate the `tuxTBridgeTbl` object by closing the connection between the indicated logical machines. This operation fails if only one logical machine is specified or if the two machines are not connected. State change allowed only when in the `active(1)` state. Successful return leaves the object in the `inactive(2)` state.

> `suspended(3)`
>   Suspend the `tuxTBridgeTbl` object by closing the connection between the indicated logical machines and by setting the `tuxTBridgeSuspTime` parameter as indicated. State change allowed only when in the `active(1)` state. Successful return leaves the object in the `suspended(3)` state.

> Note: Since the statistics reported are from the source logical machine, resetting those statistics causes them to be out of sync with the statistics reported by the destination logical machine for the same connection.

> `pending(4)`
>   Activate the `tuxTBridgeTbl` instance by establishing an asynchronous connection between the indicated logical machines. This operation fails if only one logical machine is specified, if either of the two machines is inactive, or if the source logical machine is not reachable. When in the `pending(4)` state, the success or failure of the connection request has not yet been determined. However, the BRIDGE may continue to process other events and data while the connection request is outstanding. State change allowed in `inactive(2)` and `suspended(3)` states. Successful return leaves the instance in the `pending(4)` state. This state is supported only on 6.4 and later versions of TUXEDO systems.

### tuxTBridgeCurTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on `tuxTBridgeLmid`. This attribute can be used to compute elapsed time from the following attribute values.

### tuxTBridgeConTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time, in seconds, that this connection has been active.

### tuxTBridgeSuspTime

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Time, in seconds, remaining in the suspension of this connection. After this amount of time, the connection automatically changes to a `tuxTBridgeState` of `inactive(2)` and may be activated by normal application traffic.

### tuxTBridgeRcvdByte

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of bytes sent from the destination logical machine to the source logical machine.

### tuxTBridgeSentByte

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of bytes sent from the source logical machine to the destination logical machine.

### tuxTBridgeRcvdNum

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of messages sent from the destination logical machine to the source logical machine.

### tuxTBridgeSentNum

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of messages sent from the source logical machine to the destination logical machine.

### tuxTBridgeFlowCnt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of times flow control has been encountered over this connection.

### tuxTBridgeCurEncryptBits

> #### Syntax

> `Integer {none(1), 40-bit(2), 128-bit(3), not-available(4)}`

> #### Access

> read-only

> #### Description

> The current level of encryption for this link. This is negotiated between the machines when the link is established. The number specifies the encryption key length (in bits). This object is only supported on TUXEDO 6.4 and later.

### tuxTBridgeNetworkGrpNo

> #### Syntax

> `Integer`

> #### Access

> read-only

> #### Description

> Logical network group number. When both the source and destination `tuxTBridgeLmid` machine identifiers are in the same network group, `tuxTBridgeTbl` will present all instances of related fields per network group. This object is supported only on TUXEDO 6.4 and later.

### tuxTBridgeNetworkGrpName

> #### Syntax

> DisplayString

> #### Access

> read-only

> #### Description

> Logical network group name. This object is only supported on TUXEDO 6.4 or later.

## tuxTclientTbl

This group represents runtime attributes of active clients within an application. These attribute values identify and track the activity of clients within a running application. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine.

Variable Name | Object ID
--- | ---
`tuxTclientState` | .1.3.6.1.4.1.140.300.17.1.1.1
`tuxTclientBirthTime` | .1.3.6.1.4.1.140.300.17.1.1.2
`tuxTclientMachineId` | .1.3.6.1.4.1.140.300.17.1.1.3
`tuxTclientReg` | .1.3.6.1.4.1.140.300.17.1.1.4
`tuxTclientClntName` | .1.3.6.1.4.1.140.300.17.1.1.5
`tuxTclientIdleTime` | .1.3.6.1.4.1.140.300.17.1.1.6
`tuxTclientPid` | .1.3.6.1.4.1.140.300.17.1.1.7
`tuxTclientSrvGrp` | .1.3.6.1.4.1.140.300.17.1.1.8
`tuxTclientUsrName` | .1.3.6.1.4.1.140.300.17.1.1.9
`tuxTclientWsc` | .1.3.6.1.4.1.140.300.17.1.1.10
`tuxTclientWsh` | .1.3.6.1.4.1.140.300.17.1.1.11
`tuxTclientWshClientId` | .1.3.6.1.4.1.140.300.17.1.1.12
`tuxTclientRelease` | .1.3.6.1.4.1.140.300.17.1.1.13
`tuxTclientWsProto` | .1.3.6.1.4.1.140.300.17.1.1.14
`tuxTclientNumConv` | .1.3.6.1.4.1.140.300.17.1.1.15
`tuxTclientNumDeque` | .1.3.6.1.4.1.140.300.17.1.1.16
`tuxTclientNumEnque` | .1.3.6.1.4.1.140.300.17.1.1.17
`tuxTclientNumPost` | .1.3.6.1.4.1.140.300.17.1.1.18
`tuxTclientNumReq` | .1.3.6.1.4.1.140.300.17.1.1.19
`tuxTclientNumSubscribe` | .1.3.6.1.4.1.140.300.17.1.1.20
`tuxTclientNumTran` | .1.3.6.1.4.1.140.300.17.1.1.21
`tuxTclientNumTranAbt` | .1.3.6.1.4.1.140.300.17.1.1.22
`tuxTclientNumTranCmt` | .1.3.6.1.4.1.140.300.17.1.1.23
`tuxTclientCmtRet` | .1.3.6.1.4.1.140.300.17.1.1.24
`tuxTclientCurConv` | .1.3.6.1.4.1.140.300.17.1.1.26
`tuxTclientCurReq` | .1.3.6.1.4.1.140.300.17.1.1.27
`tuxTclientCurTime` | .1.3.6.1.4.1.140.300.17.1.1.28
`tuxTclientLastGrp` | .1.3.6.1.4.1.140.300.17.1.1.29
`tuxTclientNaddr` | .1.3.6.1.4.1.140.300.17.1.1.30
`tuxTclientNotify` | .1.3.6.1.4.1.140.300.17.1.1.31
`tuxTclientNumUnSol` | .1.3.6.1.4.1.140.300.17.1.1.32
`tuxTclientRpid` | .1.3.6.1.4.1.140.300.17.1.1.33
`tuxTclientTimeLeft` | .1.3.6.1.4.1.140.300.17.1.1.34
`tuxTclientTimeStart` | .1.3.6.1.4.1.140.300.17.1.1.36
`tuxTclientTranLev` | .1.3.6.1.4.1.140.300.17.1.1.37
`tuxTclientId` | .1.3.6.1.4.1.140.300.17.1.1.38

### tuxTclientState

> #### Syntax

> `INTEGER { active(1), suspended(2), dead(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|suspended(2)|dead(3)}`
>   A `GET` operation will retrieve runtime information for the selected `tuxTclientTbl` instance(s). Note that client information is kept in local bulletin board tables only. Therefore, for maximum performance, inquiries on client status should be restricted using key fields as much as possible. The following states indicate the meaning of a `tuxTclientState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTclientTbl` instance active. This is not an indication of whether the client is idle or busy. A non-0 value retrieved for either the `tuxTclientCurConv` attribute or the `tuxTclientCurReq` attribute indicates a busy client.

> `suspended(2)`
>   `tuxTclientTbl` instance active and suspended from making further service requests (`tpcall`(3) or `tpacall`(3)) and from initiating further conversations (`tpconnect`(3)). See `SET` suspended(2) below for details.

> `dead(3)`
>   `tuxTclientTbl` instance identified as active in the bulletin board but currently not running due to an abnormal death. This state will exist only until the BBL local to the client notices the death and takes action to clean up the client's bulletin board resources.

> `SET: {active(1)|suspended(2)|dead(3)}`
>   A `SET` operation will update runtime information for the selected `tuxTclientTbl` object. The following states indicate the meaning of a `tuxTclientState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate a `suspended(2)` `tuxTclientTbl` instance. State change allowed only when in the suspended(2) state. Successful return leaves the object in the `active(1)` state.

> `suspended(2)`
>   Suspend the `tuxTclientTbl` instance from making service requests (`tpcall`(3) or `tpacall`(3)), initiating conversations (`tpconnect`(3)), beginning transactions (`tpbegin`(3)), and enqueuing new requests (`tpenqueue`(3)). Clients within a transaction will be permitted to make these calls until they abort or commit the current transaction, at which time they will become suspended. Invocations of these routines will result in a TPESYSTEM error return and a system log message being generated indicating the situation. State change allowed only when in the `active(1)` state. Successful return leaves the object in the suspended(2) state.

> `dead(3)`
>   Abortively deactivate the `tuxTclientTbl` instance. State change allowed only when in the `active(1)` or suspended(2) state. The recommended method for deactivating clients is to first suspend them, and then to abortively deactivate them by setting the state to dead(3). Successful return leaves the object in the dead(3) state

> Note: Workstation handlers (`tuxTclientWsh == yes(1)`) may not be set to a state of dead(3). The system may not be able to kill the client due to platform or signaling restrictions. In this case, a native client will be abortively terminated at its next access to ATMI, and a workstation client's connection to a WSH will be preemptively torn down.

### tuxTclientBirthTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.

### tuxTclientMachineId

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.

### tuxTclientReg

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.

### tuxTclientClntName

> #### Syntax

> `DisplayString` (`SIZE`(`0..30`))

> #### Access

> read-only

> #### Description

> Client name associated with client at `tpinit`(3) time via the cltname element of the TPINIT structure.

### tuxTclientIdleTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Approximate amount of time, in seconds, since this client last interacted with the system via an ATMI call. This value is accurate to within `tuxTdomainScanUnit` (see the `tuxTdomain` group) seconds. When specified as a key field, a positive value indicates that all clients with idle times of least the indicated value match, a negative value indicates that all clients with no more than the indicated value match, and a 0 value matches all clients.

### tuxTclientPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier of client. Note that for workstation clients, this identifier indicates the workstation handler through which the workstation client is connected. A negative number may be specified on a `GET` operation for the purpose of retrieving client information for the calling process. If the calling process is not a client, then an error will be returned.

### tuxTclientSrvGrp

> #### Syntax

> `DisplayString` (`SIZE`(`0..30`))

> #### Access

> read-only

> #### Description

> Server group with which the client is associated. This information is set via the grpname element of the TPINIT structure at `tpinit`(3) time.

### tuxTclientUsrName

> #### Syntax

> `DisplayString` (`SIZE`(`0..30`))

> #### Access

> read-only

> #### Description

> User name associated with client at `tpinit`(3) time via the usrname element of the TPINIT structure.

### tuxTclientWsc

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-only

> #### Description

> If this attribute is set to `yes(1)`, then the indicated client is logged in to the application from a remote workstation.

### tuxTclientWsh

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-only

> #### Description

> Workstation handler. If this attribute is set to `yes(1)`, then the indicated client is a workstation handler process.

### tuxTclientWshClientId

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> Client identifier for the associated workstation handler (WSH) if this client is a workstation client (`tuxTclientWsc == yes(1)`); otherwise, this attribute will be returned as a 0-length string.

### tuxTclientRelease

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The TUXEDO System/T major protocol release number for the machine where the client is running. This may be different from the `tuxTmachineSWrelease` for the same machine. Note that for /WS clients (`tuxTclientWsc == yes(1)`), this value may be different than the major release associated with the application administered machine through which the /WS client accesses the application.

### tuxTclientWsProto

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The TUXEDO System/T /WS protocol version number for a workstation client. This value is changed with each update to the /WS protocol. A value of 0 is returned for this attribute when associated with non-/WS clients (`tuxTclientWsc == no(2)`).

### tuxTclientNumConv

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of conversations initiated by this client via `tpconnect`(3).

### tuxTclientNumDeque

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of dequeue operations initiated by this client via `tpdequeue`(3).

### tuxTclientNumEnque

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of enqueue operations initiated by this client via `tpenqueue`(3).

### tuxTclientNumPost

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of postings initiated by this client via `tppost`(3).

### tuxTclientNumReq

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of requests made by this client via `tpcall`(3) or `tpacall`(3).

### tuxTclientNumSubscribe

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of subscriptions made by this client via `tpsubscribe`(3).

### tuxTclientNumTran

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions begun by this client.

### tuxTclientNumTranAbt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions aborted by this client.

### tuxTclientNumTranCmt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions committed by this client.

### tuxTclientCmtRet

> #### Syntax

> `INTEGER { complete(1), logged(2) }`

> #### Access

> read-only

> #### Description

> Setting of the TP_COMMIT_CONTROL characteristic for this client. See the description of the System/T ATMI function `tpscmt`(3) for details on this characteristic.

### tuxTclientCurConv

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of conversations initiated by this client via `tpconnect`(3) that are still active.

### tuxTclientCurReq

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of requests initiated by this client via `tpcall`(3) or `tpacall`(3) that are still active.

### tuxTclientCurTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on the local host. This attribute can be used to compute elapsed time from the `tuxTclientTimeStart` attribute value.

### tuxTclientLastGrp

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Server group number of the last service request made or conversation initiated from this client.

### tuxTclientNaddr

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> For workstation clients, this attribute indicates the network address of the client. Network addresses with unprintable characters will be converted to the "0x..." network address format as described in the `tuxTmachineNaddr` attribute. Non-workstation clients will have a 0-length string associated with them for this attribute value.

> Note: The ability of the system to provide this information is determined by the transport provider in use. In some cases, workstation clients may not have addresses associated with them if the provider does not make this information available.

### tuxTclientNotify

> #### Syntax

> `INTEGER { dipin(1), signal(2), ignore(3) }`

> #### Access

> read-only

> #### Description

> Setting of the notification characteristic for this client. See the `tuxTdomain` group description of this attribute for more details.

### tuxTclientNumUnSol

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of unsolicited messages queued for this client awaiting processing.

### tuxTclientRpid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system message queue identifier for the client's reply queue.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTclientTimeLeft

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time left, in seconds, for this client to receive the reply for which it is currently waiting before it will timeout. This timeout may be a transactional timeout or a blocking timeout.

### tuxTclientTimeStart

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on local host, since the client joined the application.

### tuxTclientTranLev

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current transaction level for this client. 0 indicates that the client is not currently involved in a transaction.

### tuxTclientId

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> Client Identifier.

## tuxTconnTable

This represents runtime attributes of active conversations within an application. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine. All objects in this MIB group are local attributes i.e., values for these objects correspond to the local host only, where the TUXEDO agent is running. So the user needs to run an instance of the TUXEDO agent on every node for which these values are of interest. The index into this table is `tuxTconnSerNo`.

Variable Name | Object ID
--- | ---
`tuxTconnSerNo` | .1.3.6.1.4.1.140.300.18.1.1.1
`tuxTconnState` | .1.3.6.1.4.1.140.300.18.1.1.2
`tuxTconnSvcName` | .1.3.6.1.4.1.140.300.18.1.1.3
`tuxTconnClientId` | .1.3.6.1.4.1.140.300.18.1.1.4
`tuxTconnOgrpNo` | .1.3.6.1.4.1.140.300.18.1.1.5
`tuxTconnOlmid` | .1.3.6.1.4.1.140.300.18.1.1.6
`tuxTconnOpid` | .1.3.6.1.4.1.140.300.18.1.1.7
`tuxTconnOsndcnt` | .1.3.6.1.4.1.140.300.18.1.1.8
`tuxTconnOsrvId` | .1.3.6.1.4.1.140.300.18.1.1.9
`tuxTconnSgrpNo` | .1.3.6.1.4.1.140.300.18.1.1.10
`tuxTconnSlmid` | .1.3.6.1.4.1.140.300.18.1.1.11
`tuxTconnSpid` | .1.3.6.1.4.1.140.300.18.1.1.12
`tuxTconnSsndcnt` | .1.3.6.1.4.1.140.300.18.1.1.13
`tuxTconnSsrvId` | .1.3.6.1.4.1.140.300.18.1.1.14

### tuxTconnSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> A running number as an index for `tuxTconnTable`.

### tuxTconnState

> #### Syntax

> `INTEGER { active(1) }`

> #### Access

> read-only

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)`
>   A `GET` operation will retrieve runtime information for the selected `tuxTconnTable` instance(s). The following state indicates the meaning of a `tuxTconnState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   The object returned reflects one or both sides of an active conversation within the application.

> `SET`:
>   `SET` operations are not permitted on this class.

### tuxTconnSvcName

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-only

> #### Description

> Service name of the conversational service invoked by the originator and processed by the subordinate.

### tuxTconnClientId

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.

### tuxTconnOgrpNo

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Server group number for the originator of the conversation. If the originator is a client, then 30,000 is returned as the value for this attribute.

### tuxTconnOlmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine identifier indicating where the originator is running or is accessing the application (in the case of /WS clients).

### tuxTconnOpid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier for the originator of the conversation.

### tuxTconnOsndcnt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of `tpsend`(3) calls done by the originator.

### tuxTconnOsrvId

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Server identifier for the originator of the conversation.

### tuxTconnSgrpNo

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Server group number for the subordinate of the conversation. If the originator is a client, then 30,000 is returned as the value for this attribute.

### tuxTconnSlmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine identifier indicating where the subordinate is running or is accessing the application (in the case of /WS clients).

### tuxTconnSpid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier for the subordinate in the conversation.

### tuxTconnSsndcnt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of `tpsend`(3) calls done by the subordinate.

### tuxTconnSsrvId

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Server identifier for the subordinate in the conversation.

## tuxTdeviceTbl

This represents configuration and runtime attributes of raw disk slices or UNIX system files being used to store TUXEDO System/T device lists. This class allows for the creation and deletion of device list entries within a raw disk slice or UNIX system file. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine. To create a new row in this table, the user needs to send a SET request, with at least a value for `tuxTdevSize`. The index into this table is `tuxTdevCfgDev` and `tuxTdevIndex`.

Variable Name | Object ID
--- | ---
`tuxTdevLmid` | .1.3.6.1.4.1.140.300.19.1.1.1
`tuxTdevCfgDev` | .1.3.6.1.4.1.140.300.19.1.1.2
`tuxTdeviceName` | .1.3.6.1.4.1.140.300.19.1.1.3
`tuxTdevOffset` | .1.3.6.1.4.1.140.300.19.1.1.4
`tuxTdevSize` | .1.3.6.1.4.1.140.300.19.1.1.5
`tuxTdevIndex` | .1.3.6.1.4.1.140.300.19.1.1.6
`tuxTdevState` | .1.3.6.1.4.1.140.300.19.1.1.7

### tuxTdevLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Logical machine identifier where the device is located. Note that this attribute may be used as a key field in both unbooted and booted applications as long as they are already configured (that is, at least one `tuxTmachineTable` instance exists). It is required as a key field on `SET` operations when accessing a booted application. If specified when accessing the `tuxTdeviceTbl` table in an unconfigured application, this attribute is ignored.

> Note: This object can be set only during row creation.

### tuxTdevCfgDev

> #### Syntax

> `DisplayString` (`SIZE`(`2..64`))

> #### Access

> read-write

> #### Description

> Absolute pathname of the file or device where the TUXEDO System/T filesystem is stored or is to be stored.

> Note: This object can be set only during row creation.

### tuxTdeviceName

> #### Syntax

> `DisplayString` (`SIZE`(`2..64`))

> #### Access

> read-write

> #### Description

> Absolute pathname of the device list entry.

> Note: This object can be set only during row creation.

### tuxTdevOffset

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> The offset, in blocks, at which space on this `tuxTdevice` begins for use within the TUXEDO System/T VTOC specified by `tuxTdevCfgDev`.

> Note: This object can be set only during row creation.

### tuxTdevSize

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> The size in pages of the disk area to be used for the device list entry.

> Note: This attribute may be set only in conjunction with row creation.

> Note: This object can be set only during row creation.

### tuxTdevIndex

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Device index for `tuxTdevice` within the device list addressed by `tuxTdevCfgDev`. This attribute value is used for identification purposes only in getting and setting attribute values relating to particular devices within a TUXEDO System/T filesystem.

### tuxTdevState

> #### Syntax

> `INTEGER { valid(1), invalid(2), re-init(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {valid(1)}`
>   A `GET` operation will retrieve runtime information for the selected `tuxTdeviceTbl` instance(s). The following state indicates the meaning of a `tuxTdevState` returned in response to a `GET` request. States not listed will not be returned.

> `valid(1)`
>   The TUXEDO System/T filesystem indicated by `tuxTdevCfgDev` exists and contains a valid device list. `tuxTdevice` is a valid device within that filesystem with the device index `tuxTdevIndex`.

> `SET: {invalid(2)|re-init(3)}`
>   A `SET` operation will update information for the selected `tuxTdeviceTbl` instance or add the indicated object. The following states indicate the meaning of a `tuxTdevState` set in a `SET` request. States not listed may not be set.

> `invalid(2)`
>   Delete `tuxTdeviceTbl` instance for application. State change allowed only when in the valid(1) state. Successful return leaves the object in the invalid(2) state. Note that `tuxTdevIndex 0` is special and must be deleted last.

> `re-init(3)`
>   To re-initialize a valid device.

## tuxTwhichCfgDev

The value of this object determines the device for which `tuxTdeviceTbl` returns configuration and runtime information.

Variable Name | Object ID
--- | ---
`tuxTwhichCfgDev` | .1.3.6.1.4.1.140.300.19.2

### tuxTwhichCfgDev

> #### Syntax

> `DisplayString` (`SIZE`(`2..64`))

> #### Access

> read-write

> #### Description

> The value of this object determines the device for which `tuxTdeviceTbl` returns configuration and runtime information.

> The default value of this object is the TUXCONFIG file for the current domain.

## tuxTdomain

The following objects of `tuxTdomain` represent global application attributes for the domain to which the TUXEDO SNMP agent is currently connected. These object values serve to identify, customize, size, secure, and tune a TUXEDO System/T application. Many of the object values represented here serve as application defaults for other groups represented in this MIB.

There is exactly one instance of the `tuxTdomain` group for each application.

Variable Name | Object ID
--- | ---
`tuxTdomainKey` | .1.3.6.1.4.1.140.300.3.1
`tuxTdomainMaster` | .1.3.6.1.4.1.140.300.3.2
`tuxTdomainModel` | .1.3.6.1.4.1.140.300.3.3
`tuxTdomainState` | .1.3.6.1.4.1.140.300.3.4
`tuxTdomainID` | .1.3.6.1.4.1.140.300.3.5
`tuxTdomainUID` | .1.3.6.1.4.1.140.300.3.7
`tuxTdomainGID` | .1.3.6.1.4.1.140.300.3.8
`tuxTdomainPerm` | .1.3.6.1.4.1.140.300.3.9
`tuxTdomainMask` | .1.3.6.1.4.1.140.300.3.10
`tuxTdomainMaxAccessers` | .1.3.6.1.4.1.140.300.3.11
`tuxTdomainMaxConv` | .1.3.6.1.4.1.140.300.3.12
`tuxTdomainMaxGTT` | .1.3.6.1.4.1.140.300.3.13
`tuxTdomainMaxBufsType` | .1.3.6.1.4.1.140.300.3.14
`tuxTdomainMaxBufType` | .1.3.6.1.4.1.140.300.3.15
`tuxTdomainMaxDRT` | .1.3.6.1.4.1.140.300.3.16
`tuxTdomainMaxGroups` | .1.3.6.1.4.1.140.300.3.17
`tuxTdomainMaxMachines` | .1.3.6.1.4.1.140.300.3.18
`tuxTdomainMaxQueues` | .1.3.6.1.4.1.140.300.3.19
`tuxTdomainMaxRFT` | .1.3.6.1.4.1.140.300.3.20
`tuxTdomainMaxRTData` | .1.3.6.1.4.1.140.300.3.21
`tuxTdomainMaxServers` | .1.3.6.1.4.1.140.300.3.22
`tuxTdomainMaxServices` | .1.3.6.1.4.1.140.300.3.23
`tuxTdomainMaxACLgroups` | .1.3.6.1.4.1.140.300.3.24
`tuxTdomainCMTRET` | .1.3.6.1.4.1.140.300.3.25
`tuxTdomainLoadBalance` | .1.3.6.1.4.1.140.300.3.26
`tuxTdomainNotify` | .1.3.6.1.4.1.140.300.3.27
`tuxTdomainSystemAccess` | .1.3.6.1.4.1.140.300.3.28
`tuxTdomainOptions` | .1.3.6.1.4.1.140.300.3.29
`tuxTdomainSignal` | .1.3.6.1.4.1.140.300.3.30
`tuxTdomainSecurity` | .1.3.6.1.4.1.140.300.3.31
`tuxTdomainAuthsvc` | .1.3.6.1.4.1.140.300.3.33
`tuxTdomainScanUnit` | .1.3.6.1.4.1.140.300.3.34
`tuxTdomainBBLQuery` | .1.3.6.1.4.1.140.300.3.35
`tuxTdomainBlockTime` | .1.3.6.1.4.1.140.300.3.36
`tuxTdomainDBBLWait` | .1.3.6.1.4.1.140.300.3.37
`tuxTdomainSanityScan` | .1.3.6.1.4.1.140.300.3.38
`tuxTdomainCurDRT` | .1.3.6.1.4.1.140.300.3.39
`tuxTdomainCurGroups` | .1.3.6.1.4.1.140.300.3.40
`tuxTdomainCurMachines` | .1.3.6.1.4.1.140.300.3.41
`tuxTdomainCurQueues` | .1.3.6.1.4.1.140.300.3.42
`tuxTdomainCurRFT` | .1.3.6.1.4.1.140.300.3.43
`tuxTdomainCurRTdata` | .1.3.6.1.4.1.140.300.3.44
`tuxTdomainCurServers` | .1.3.6.1.4.1.140.300.3.45
`tuxTdomainCurServices` | .1.3.6.1.4.1.140.300.3.46
`tuxTdomainCursType` | .1.3.6.1.4.1.140.300.3.47
`tuxTdomainCurType` | .1.3.6.1.4.1.140.300.3.48
`tuxTdomainHwDRT` | .1.3.6.1.4.1.140.300.3.49
`tuxTdomainHwGroups` | .1.3.6.1.4.1.140.300.3.50
`tuxTdomainHwMachines` | .1.3.6.1.4.1.140.300.3.51
`tuxTdomainHwQueues` | .1.3.6.1.4.1.140.300.3.52
`tuxTdomainHwRFT` | .1.3.6.1.4.1.140.300.3.53
`tuxTdomainHwRTdata` | .1.3.6.1.4.1.140.300.3.54
`tuxTdomainHwServers` | .1.3.6.1.4.1.140.300.3.55
`tuxTdomainHwServices` | .1.3.6.1.4.1.140.300.3.56
`tuxTdomainMaxNetGroups` | .1.3.6.1.4.1.140.300.3.58
`m3MaxObjects` | .1.3.6.1.4.1.140.300.3.63
`m3MaxInterfaces` | .1.3.6.1.4.1.140.300.3.68
`m3CurInterfaces` | .1.3.6.1.4.1.140.300.3.73
`m3HwInterfaces` | .1.3.6.1.4.1.140.300.3.78

### tuxTdomainKey

> #### Syntax

> `INTEGER (32769..262143)`

> #### Access

> read-write

> #### Description

> Numeric key for the well-known address in a TUXEDO System/T bulletin board. In a single processor environment, this key "names" the bulletin board. In a multiple processor or LAN environment, this key names the message queue of the DBBL. In addition, this key is used as a basis for deriving the names of resources other than the well-known address, such as the names for bulletin boards throughout the application.

### tuxTdomainMaster

> #### Syntax

> `DisplayString` (`SIZE` (`1..30`))

> #### Access

> read-write

> #### Description

> `DisplayString` is in format: `LMID1``[,``LMID2``]`

> `LMID1`
>   Is the master logical machine identifier and is in the range from one to thirty characters.

> `LMID2`
>   Is the backup logical machine identifier and is in the range from one to thirty characters.

> The master identifier (`LMID1`) must correspond to the local machine for inactive applications. single-machine(1) mode applications (see `tuxTdomainModel` below) may set only the master logical machine identifier. Modifications to this attribute value in an active multi-machine(2) application (see `tuxTdomainModel` below) have the following semantics.

> Assuming current active master LMID A, current backup master LMID B, and secondary LMIDs C, D, ...., the following scenarios define the semantics of permitted changes to the `tuxTdomainMaster` attribute in a running `multi-machine(2)` mode application.

> A,B -> B,A - Master migration from A to B. A,B -> A,C - Change backup master LMID designation to C.

> Note that master migration may be either orderly or partitioned. Orderly migration takes place when the master machine is active and reachable. Otherwise, partitioned migration takes place. All newly established or re-established network connections will verify that the two sites connecting share a common view of where the master machine is. Otherwise, the connection will be refused and an appropriate log message generated.

> The master and backup machines in an active application must always have a TUXEDO System/T release number greater than or equal to all other machines active in the application. The master and backup machines must be of the same release. Modifications to the `tuxTdomainMaster` attribute must preserve this relationship.

### tuxTdomainModel

> #### Syntax

> `INTEGER { single-machine(1), multi-machine(2) }`

> #### Access

> read-write

> #### Description

> Configuration type. single-machine(1) specifies a single machine configuration; only one `tuxTmachineTable` object may be specified. multi-machine(2) specifies a multi-machine or network configuration; it must be specified if a networked application is being defined.

### tuxTdomainState

> #### Syntax

> `INTEGER { active(1), inactive(2), forcible-inactive(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|inactive(2)}`
>   A `GET` operation will retrieve configuration and runtime information for the `tuxTdomain` group. The following states indicate the meaning of a `tuxTdomainState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTdomain` group defined and the master machine is active.

> `inactive(2)`
>   `tuxTdomain` group defined and application is inactive.

> `SET: active(1)|inactive(2)|forcible-inactive(3)`
>   A `SET` operation will update configuration and run-time information for the `tuxTdomain` group. The following states indicate the meaning of a `tuxTdomainState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate administrative processes (DBBL, BBL, etc.) on the master machine. A state change is allowed only when in the `inactive(2)` state. Successful return leaves the object in the `active(1)` state.

> `inactive(2)`
>   Deactivate administrative processes (DBBL, BBL, etc.) on the master machine. A state change is allowed only when in the `active(1)` state. Successful return leaves the object in the `inactive(2)` state. To do a complete shutdown of the application, you must first make all groups inactive. (See `tuxTgroupState`.) This state transition fails if any application servers or clients are still attached to the domain. To ignore any running clients or application servers, set to `forcible-inactive(3)` as explained below.

> `forcible-inactive(3)`
>   Forcibly deactivate administrative processes (DBBL, BBL, etc.) on the master machine. Attached clients will be ignored for the purpose of determining if shutdown should be allowed. State change is allowed only when in the `active(1)` state. Successful return leaves the object in the `inactive(2)` state. You will need to restart any clients before they can be used to process services after this state transition.

### tuxTdomainID

> #### Syntax

> `DisplayString` (`SIZE` (`0..30`))

> #### Access

> read-write

> #### Description

> Domain identification string.

### tuxTdomainUID

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainGID

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainPerm

> #### Syntax

> `DisplayString` (`SIZE`(`1..9`))

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainMask

> #### Syntax

> `DisplayString` (`SIZE`(`1..9`))

> #### Access

> read-write

> #### Description

> Attribute access mask. User type/access mode combinations specified by this attribute value will no longer be allowed for all class/attribute combinations defined in `TM_MIB`(5). For example, a setting of 0003 disallows all updates to users other than the administrator or the operator. The value of this object should be provided as an octal number - 0 through 0777.

### tuxTdomainMaxAccessers

> #### Syntax

> `INTEGER (1..32767)`

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainMaxConv

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainMaxGTT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Default attribute setting for newly configured objects in the `tuxTmachineTable` group.

> Note: Changes to this attribute do not affect active or already configured `tuxTmachineTable` instances.

### tuxTdomainMaxBufsType

> #### Syntax

> `INTEGER (1..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of buffer subtypes that can be accommodated in the bulletin board buffer subtype table.

### tuxTdomainMaxBufType

> #### Syntax

> `INTEGER (1..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of buffer types that can be accommodated in the bulletin board buffer type table.

### tuxTdomainMaxDRT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of routing table entries that can be accommodated in the bulletin board routing table. One entry per `tuxTroutingTable` group object is required. Additional entries should be allocated to allow for runtime growth.

### tuxTdomainMaxGroups

> #### Syntax

> `INTEGER (100..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of server groups that can be accommodated in the bulletin board server group table.

> Note: TUXEDO System/T Release 4.2.2 and earlier sites have a fixed setting of 100 for this attribute. Interoperability with these sites requires that no more than 100 server group entries be in use at any time. Release 4.2.2 and earlier sites will not be allowed to join an application that has more than 100 defined server groups. Additionally, applications already including Release 4.2.2 or earlier sites will not be allowed to add server groups beyond 100.

### tuxTdomainMaxMachines

> #### Syntax

> `INTEGER (256..8190)`

> #### Access

> read-write

> #### Description

> Maximum number of machines that can be accommodated in the bulletin board machine table.

> Note: TUXEDO System/T Release 4.2.2 has a fixed setting of 256 for this attribute. Releases prior to Release 4.2.2 have a fixed setting of 50 for this attribute. Interoperability with Release 4.2.2 and earlier sites requires that no more than the lowest fixed setting number of machine table entries be in use at any time. Release 4.2.2 sites will not be allowed to join an application that has more than 256 defined machines. Pre-Release 4.2.2 sites will not be allowed to join an application that has more than 50 defined machines. Additionally, applications already including active Release 4.2.2 or earlier sites will not be allowed to add machines beyond the lowest applicable limit.

### tuxTdomainMaxQueues

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> Maximum number of queues to be accommodated in the bulletin board queue table.

> Note: Release 4.2.2 and earlier sites may join an active application only if the setting for `tuxTdomainMaxQueues` is equal to the setting for `tuxTdomainMaxServers`.

### tuxTdomainMaxRFT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of routing criteria range table entries to be accommodated in the bulletin board range criteria table. One entry per individual range within a `tuxTroutingRanges` specification is required plus one additional entry per `tuxTroutingTable` class object. Additional entries should be allocated to allow for runtime growth.

### tuxTdomainMaxRTData

> #### Syntax

> `INTEGER (0..32760)`

> #### Access

> read-write

> #### Description

> Maximum string pool space to be accommodated in the bulletin board string pool table. Strings and carrays specified within `tuxTroutingRanges` values are stored in the string pool. Additional space should be allocated to allow for runtime growth.

### tuxTdomainMaxServers

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> Maximum number of servers to be accommodated in the bulletin board server table. Allowances should be made in setting this attribute for system supplied administrative servers. Administration of each System/T site adds approximately one server. Additionally, if TMSs are specified for any server groups (see `tuxTgroupTMSname`), then they will be booted along with their server group and should be accounted for in setting `tuxTdomainMaxServers`.

### tuxTdomainMaxServices

> #### Syntax

> `INTEGER (1..32767)`

> #### Access

> read-write

> #### Description

> Maximum number of services to be accommodated in the bulletin board service table. Allowances should be made in setting this attribute for system supplied servers offering services for administrative purposes. Administration of each System/T site adds approximately five services. Other administrative components such as /WS, /Q, and /DM may also add administrative services that should be accounted for.

### tuxTdomainMaxACLgroups

> #### Syntax

> `INTEGER (1..16384)`

> #### Access

> read-write

> #### Description

> Maximum number of group identifiers that can be used for ACL permissions checking. The maximum group identifier that can be defined is `tuxTdomainMaxACLgroups - 1`.

### tuxTdomainCMTRET

> #### Syntax

> `INTEGER { complete(1), logged(2) }`

> #### Access

> read-write

> #### Description

> Initial setting of the TP_COMMIT_CONTROL characteristic for all client and server processes in a System/T application. `logged(2)` initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_LOGGED; otherwise, it is initialized to TP_CMT_COMPLETE. See the description of the System/T ATMI function `tpscmt`(3) for details on the setting of this characteristic.

> Note: Runtime modifications to this attribute do not affect active clients and servers.

### tuxTdomainLoadBalance

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Load balancing is/will be on `yes(1)` or off `no(2)`.

> Note: Runtime modifications to this attribute do not affect active clients and servers.

### tuxTdomainNotify

> #### Syntax

> `INTEGER { dipin(1), signal(2), ignore(3) }`

> #### Access

> read-write

> #### Description

> Default notification detection method to be used by the system for unsolicited messages sent to client processes. This default value can be overridden on a per-client basis using the appropriate `tpinit`(3) flag value. Note that once unsolicited messages are detected, they are made available to the application through the application defined unsolicited message handling routine identified via the `tpsetunsol`(3) function.

> The value `dipin(1)` specifies that dip-in-based notification detection should be used. This means that the system will only detect notification messages on behalf of a client process while within ATMI calls. The point of detection within any particular ATMI call is not defined by the system, and dip-in detection will not interrupt blocking system calls. `dipin(1)` is the default notification detection method.

> The value `signal(2)` specifies that signal-based notification detection should be used. This means that the system sends a signal to the target client process after the notification message has been made available. The system installs a signal catching routine on behalf of clients selecting this method of notification.

> The value `ignore(3)` specifies that by default, notification messages are to be ignored by application clients. This would be appropriate in applications where only clients that request notification at `tpinit`(3) time should receive unsolicited messages.

> Note: Runtime modifications to this attribute do not affect active clients. All signaling of client processes is done by administrative system processes and not by application processes. Therefore, only clients running with the same UNIX system user identifier can be notified using the `signal(2)` method.

### tuxTdomainSystemAccess

> #### Syntax

> `INTEGER { fastpath(1), protected(2), fastpath-no-override(3), protected-no-override(4) }`

> #### Access

> read-write

> #### Description

> Default mode used by System/T libraries within application processes to gain access to System/T's internal tables. `fastpath(1)` specifies that System/T's internal tables are accessible by System/T libraries via unprotected shared memory for fast access. `protected(2)` specifies that System/T's internal tables are accessible by System/T libraries via protected shared memory for safety against corruption by application code. `fastpath-no-override(3)` or `protected-no-override(4)` can be specified to indicate that the mode selected cannot be overridden by an application process using flags available for use with `tpinit`(3).

> Note: Updates to this attribute value in a running application affect only newly started clients and newly configured `tuxTsrvrTbl` objects.

### tuxTdomainOptions

> #### Syntax

> `INTEGER { lan(1), migrate(2), accstats(3), lan-migrate(4), lan-accstats(5), migrate-accstats(6), lan-migrate-accstats(7), none(8) }`

> #### Access

> read-write

> #### Description

> Comma separated list of application options in effect. Valid options are defined as follows:

> `lan(1)`
>   Networked application.

> `migrate(2)`
>   Allow server group migration.

> `accstats(3)`
>   Exact statistics (`single-machine(1)` mode only).

> Note: Only the accstats(3) may be set or reset in an active application.

### tuxTdomainSignal

> #### Syntax

> `INTEGER { sigusr1(1), sigusr2(2) }`

> #### Access

> read-write

> #### Description

> Signal to be used for signal-based notification (see `tuxTdomainNotify` above).

### tuxTdomainSecurity

> #### Syntax

> `INTEGER DisplayString`

> #### Access

> read-write

> #### Description

> Type of application security. The format is:

> >     security_mode[/app_password]

> where `security_mode` can have the following values:

> >     NONE
> >     APP_PW
> >     USER_AUTH
> >     ACL
> >     MANDATORY_ACL

> `app_password` is needed whenever `security_mode` is being set to anything but `NONE`. To change the value of `app_password`, `SET` this object to:

> `current_security_mode``/``new_password`

> On a `GET` operation, this object only returns the security mode; the password is not returned.

> A string value `NONE` for this attribute indicates that security is (or will be) turned off. The value `APP_PW/``app_password` indicates that application password security is to be enforced. Clients must provide the application password during initialization. The value `USER_AUTH` is similar to `APP_PW`, but indicates also that per-user authentication is done during client initialization. The value `ACL` is similar to `USER_AUTH`, but also indicates that access control checks will be done on service names, queue names, and event names. If an associated ACL is not found for a name, it is assumed that permission is granted. The value `MANDATORY_ACL` is similar to `ACL`, but permission is denied if an associated ACL is not found for the name.

### tuxTdomainAuthsvc

> #### Syntax

> `DisplayString` (`SIZE` (`1..15`))

> #### Access

> read-write

> #### Description

> Application authentication service invoked by the system for each client joining the system. This attribute is ignored if the `tuxTdomainSecurity` attribute is set to `NONE` or to APP-PW.

### tuxTdomainScanUnit

> #### Syntax

> `INTEGER (0..60)`

> #### Access

> read-write

> #### Description

> Interval of time (in seconds) between periodic scans by the system. Periodic scans are used to detect old transactions and timed-out blocking calls within service requests. The `tuxTdomainBBLQuery`, `tuxTdomainBlockTime`, `tuxTdomainDBBLWait`, and `tuxTdomainSanityScan` objects are multipliers of this value. Passing a value of 0 for this attribute on a `SET` operation will cause the attribute to be reset to its default value.

### tuxTdomainBBLQuery

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Multiplier of the `tuxTdomainScanUnit` object indicating time between DBBL status checks on registered BBLs. The DBBL checks to ensure that all BBLs have reported in within the `tuxTdomainBBLQuery` cycle. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned. Passing a value of 0 for this attribute on a `SET` operation will cause the attribute to be reset to its default value. This attribute value should be set to at least twice the value set for `tuxTdomainSanityScan`.

### tuxTdomainBlockTime

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Multiplier of the `tuxTdomainScanUnit` object indicating the minimum amount of time a blocking ATMI call will block before timing out. Passing a value of 0 for this attribute on a `SET` operation will cause the attribute to be reset to its default value.

### tuxTdomainDBBLWait

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Multiplier of the `tuxTdomainScanUnit` object indicating maximum amount of time a DBBL should wait for replies from its BBLs before timing out. Passing a value of 0 for this attribute on a `SET` operation will cause the attribute to be reset to its default value.

### tuxTdomainSanityScan

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-write

> #### Description

> Multiplier of the `tuxTdomainScanUnit` object indicating time between basic sanity checks of the system. Sanity checking includes client/server viability checks done by each BBL for clients/servers running on the local machine as well as BBL status check-ins (`multi-machine(2)` mode only). Passing a value of 0 for this attribute on a `SET` operation will cause the attribute to be reset to its default value.

### tuxTdomainCurDRT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board routing table entries.

### tuxTdomainCurGroups

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board server group table entries.

### tuxTdomainCurMachines

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of configured machines.

### tuxTdomainCurQueues

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board queue table entries.

### tuxTdomainCurRFT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board routing criteria range table entries.

### tuxTdomainCurRTdata

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current size of routing table string pool.

### tuxTdomainCurServers

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board server table entries.

### tuxTdomainCurServices

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board service table entries.

### tuxTdomainCursType

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board subtype table entries.

### tuxTdomainCurType

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Current number of in use bulletin board type table entries.

### tuxTdomainHwDRT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board routing table entries.

### tuxTdomainHwGroups

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board server group table entries.

### tuxTdomainHwMachines

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of configured machines.

### tuxTdomainHwQueues

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board queue table entries.

### tuxTdomainHwRFT

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board routing criteria range table entries.

### tuxTdomainHwRTdata

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water size of routing table string pool.

### tuxTdomainHwServers

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board server table entries.

### tuxTdomainHwServices

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> High water number of in use bulletin board service table entries.

### tuxTdomainMaxNetGroups

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> The maximum number of groups that can be configured. This object is only supported on TUXEDO 6.4 or later.

### m3MaxObjects

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> The default maximum number of active objects to be accommodated in the Active Object Map tables in the M3 bulletin board.

> Note: This object is supported for M3 applications only.

### m3MaxInterfaces

> #### Syntax

> `INTEGER (1..32765)`

> #### Access

> read-write

> #### Description

> Specifies the maximum number of interfaces to be accommodated in the interface table of the bulletin board. If not specified, the default is 100.

> All instances of an interface occupy and re-use the same slot in the interface table in the bulletin board. For example, if server SVR1 advertises interfaces IF1 and IF2, SVR2 advertises IF2 and IF3, and SVR3 advertises IF3 and IF4, the interface count is 4, not 6, when calculating `m3MaxInterfaces`.

> Note: This object is supported for M3 applications only.

### m3CurInterfaces

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The current number of interface entries used in the bulletin board interface tables.

> Note: This object is supported for M3 applications only.

### m3HwInterfaces

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The high water mark for the number of interface entries used in the bulletin board interface tables.

> Note: This object is supported for M3 applications only.

## tuxTgroupTable

The `tuxTgroupTable` group represents application attributes pertaining to a particular server group. These attribute values represent group identification, location, and DTP information. The index for this table is `tuxTgroupNo`. To create a new row, it is necessary to issue a SET request for a non-existing instance that at least specifies values for `tuxTgroupName` and `tuxTgroupLMID`.

Variable Name | Object ID
--- | ---
`tuxTgroupName` | .1.3.6.1.4.1.140.300.4.1.1.1
`tuxTgroupNo` | .1.3.6.1.4.1.140.300.4.1.1.2
`tuxTgroupLMID` | .1.3.6.1.4.1.140.300.4.1.1.3
`tuxTgroupState` | .1.3.6.1.4.1.140.300.4.1.1.4
`tuxTgroupCurLMID` | .1.3.6.1.4.1.140.300.4.1.1.5
`tuxTgroupCloseInfo` | .1.3.6.1.4.1.140.300.4.1.1.6
`tuxTgroupOpenInfo` | .1.3.6.1.4.1.140.300.4.1.1.7
`tuxTgroupTMScount` | .1.3.6.1.4.1.140.300.4.1.1.8
`tuxTgroupTMSname` | .1.3.6.1.4.1.140.300.4.1.1.9

### tuxTgroupName

> #### Syntax

> `DisplayString` (`SIZE` (`1..30`))

> #### Access

> read-write

> #### Description

> Logical name of the server group. The group name must be unique within all group names in the `tuxTgroupTable` class and `tuxTgroupLMID` values in the `tuxTmachineTable` class. Server group names cannot contain an asterisk (*), comma, or colon.

> Note: This object can be set only during row creation.

### tuxTgroupNo

> #### Syntax

> `INTEGER (1..29999)`

> #### Access

> read-write

> #### Description

> Group number associated with this server group.

> Note: This object can be set only during row creation.

### tuxTgroupLMID

> #### Syntax

> `DisplayString` (`SIZE` (`1..61`))

> #### Access

> read-write

> #### Description

> `DisplayString` is in the format: `LMID1``[,``LMID2``]`

> `LMID1`
>   Is the primary machine logical machine identifier for this server group and is in the range from one to sixty-one characters.

> `LMID2`
>   Is the optional secondary logical machine identifier and is in the range from one to sixty-one characters.

> The secondary LMID indicates the machine to which the server group can be migrated (if the MIGRATE option is specified in the `tuxTdomainOptions` attribute). A single LMID specified on a `GET` operation will match either the primary or secondary LMID. Note that the location of an active group is available in the `tuxTgroupCurLMID` object. Logical machine identifiers specified with the `tuxTgroupLMID` object must be already configured.

> Note: Modifications to this attribute for an active object may only change the backup LMID designation for the group.

### tuxTgroupState

> #### Syntax

> >     INTEGER { active(1), inactive(2), migrating(3), invalid(4),
> >     re-active(5), suspend-services(6), resume-services(7)}

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|inactive(2)|migrating(3)}`
>   A `GET` operation will retrieve configuration and runtime information for the selected `tuxTgroupTable` object(s). The following states indicate the meaning of a `tuxTgroupState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTgroupTable` object defined and active (TMS and/or application servers). Server groups with non-0 length values for the `tuxTgroupTMSname` attribute are considered active if the TMSs associated with the group are active. Otherwise, a group is considered active if any server in the group is active.

> `inactive(2)`
>   `tuxTgroupTable` object defined and inactive.

> `migrating(3)`
>   `tuxTgroupTable` object defined and currently in a state of migration to the secondary logical machine. The secondary logical machine is the one listed in `tuxTgroupLMID` that does not match `tuxTgroupCurLMID`.

> `SET: {active(1)|inactive(2)|migrating(3)|invalid(4)|re-active(5) |suspend-services(6)|resume-services(7)}`
>   A `SET` operation will update configuration and run-time information for the selected `tuxTgroupTable` object. The following states indicate the meaning of a `tuxTgroupState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate the `tuxTgroupTable` object. State change allowed only when in the inactive(2) or migrating(3) state. If the group is currently in the `inactive(2)` state, then TMS and application servers are started on the primary logical machine if the primary logical machine is active; otherwise, the TMS and application servers are started on the secondary logical machine if it is active. If neither machine is active, then the request fails. If the group is currently in the migrating(3) state, then the active secondary logical machine (identified as the alternate to `tuxTgroupCurLMID` in the `tuxTgroupLMID` list) is used to start TMS and application servers if it is active. Otherwise, the request fails. Successful return leaves the object in the active(1) state.

> `inactive(2)`
>   Deactivate the `tuxTgroupTable` instance. TMS and application servers are deactivated. State change allowed only when in the active(1) or `migrating(3)` state. Successful return leaves the object in the `inactive(2)` state.

> `migrating(3)`
>   Deactivate the `tuxTgroupTable` object on its active primary logical machine (`tuxTgroupCurLMID`) and prepare the group to be migrated to the secondary logical machine. State change allowed only when in the active(1) state. Successful return leaves the object in the migrating(3) state.

> `invalid(4)`
>   Delete `tuxTgroupTable` object for application. State change allowed only when in the inactive(2) state. Successful return leaves the object in the invalid(4) state.

> `re-active(5)`
>   Identical to a transition to the active(1) state except that this state change is also allowed in the active(1) state in addition to being allowed in the `inactive(2)` and migrating(3) states.

> `suspend-services(6)`
>   Suspend the application services in the group. A `SET` operation to this state is allowed only when the group is in the `active(1)` state. The operation leaves the group in `active(1)` state but with all its application services in a suspended state. This state is only available in TUXEDO 6.4 and later.

> `resume-services(7)`
>   Unsuspend and resume all application services in the group that are marked suspended. This operation is allowed only when the group is in the `active(1)` state. The operation leaves the group in the `active(1)` state. Note that his operation fails in an application environment that includes any machine where TUXEDO 6.3 or earlier applications are active.

### tuxTgroupCurLMID

> #### Syntax

> >     DisplayString (SIZE (1..30))

> #### Access

> read-only

> #### Description

> Current logical machine on which the server group is running. This attribute will not be returned for server groups that are not active.

### tuxTgroupCloseInfo

> #### Syntax

> >     DisplayString (SIZE (0..256))

> #### Access

> read-write

> #### Description

> If a non-0 length value other than `TMS` is specified for the `tuxTgroupTMSname` object, then this object value indicates the resource manager dependent information needed when terminating access to the resource manager. Otherwise, this attribute value is ignored.

> The format for this object value is dependent on the requirements of the vendor providing the underlying resource manager. The information required by the vendor must be prefixed with `rm_name:`, which is the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).

> A 0-length string value for this attribute means that the resource manager for this group (if specified) does not require any application specific information to close access to the resource.

> Note: Runtime modifications to this attribute will not affect active servers in the group.

### tuxTgroupOpenInfo

> #### Syntax

> >     DisplayString (SIZE (0..256))

> #### Access

> read-write

> #### Description

> If a non-0 length value other than `TMS` is specified for the `tuxTgroupTMSname` object, then this object value indicates the resource manager dependent information needed when initiating access to the resource manager. Otherwise, this object value is ignored.

> The format for this object value is dependent on the requirements of the vendor providing the underlying resource manager. The information required by the vendor must be prefixed with `rm_name:`, which is the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).

> A 0-length string value for this attribute means that the resource manager for this group (if specified) does not require any application specific information to open access to the resource.

> Note: Runtime modifications to this attribute will not affect active servers in the group.

### tuxTgroupTMScount

> #### Syntax

> >     INTEGER (0..11)

> #### Access

> read-write

> #### Description

> If a non-0 length value is specified for the `tuxTgroupTMSname` object, then this object value indicates the number of transaction manager servers to start for the associated group. Otherwise, this object value is ignored.

### tuxTgroupTMSname

> #### Syntax

> >     DisplayString (SIZE (0..78))

> #### Access

> read-write

> #### Description

> Transaction manager server `a.out` associated with this group. This parameter must be specified for any group entry whose servers will participate in distributed transactions (transactions across multiple resource managers and possibly machines that are started with `tpbegin`(3) and ended with `tpcommit`(3)/`tpabort`(3)).

> The value `TMS` is reserved to indicate use of the null XA interface. If a non-empty value other than `TMS` is specified, then a `tuxTmachineTlogDevice` must be specified for the machine(s) associated with the primary and secondary logical machines for this object

> A unique server identifier is selected automatically for each TM server, and the servers will be restartable an unlimited number of times.

## tuxTmachineTable

The `tuxTmachineTable` group represents application attributes pertaining to a particular machine. These attribute values represent machine characteristics, per-machine sizing, statistics, customization options, and UNIX system filenames. This group is available for configured-inactive as well as configured-active machines in the application. The index into this table is `tuxTmachinePmid`. To create a new row, a SET request should be issued for a non-existing row that specifies at least the values for `tuxTmachineLmid`, `tuxTmachineTuxDir`, `tuxTmachineTuxConfig`, and `tuxTmachineAppDir`. For a multi-machine TUXEDO application, `tuxTmachineNaddr`, `tuxTmachineNlsAddr`, and `tuxTmachineBridge` must also be specified.

Variable Name | Object ID
--- | ---
`tuxTmachinePmid` | .1.3.6.1.4.1.140.300.5.1.1.1
`tuxTmachineLmid` | .1.3.6.1.4.1.140.300.5.1.1.2
`tuxTmachineTuxConfig` | .1.3.6.1.4.1.140.300.5.1.1.3
`tuxTmachineTuxDir` | .1.3.6.1.4.1.140.300.5.1.1.4
`tuxTmachineAppDir` | .1.3.6.1.4.1.140.300.5.1.1.5
`tuxTmachineState` | .1.3.6.1.4.1.140.300.5.1.1.6
`tuxTmachineUid` | .1.3.6.1.4.1.140.300.5.1.1.7
`tuxTmachineGid` | .1.3.6.1.4.1.140.300.5.1.1.8
`tuxTmachineEnvFile` | .1.3.6.1.4.1.140.300.5.1.1.9
`tuxTmachinePerm` | .1.3.6.1.4.1.140.300.5.1.1.10
`tuxTmachineUlogPfx` | .1.3.6.1.4.1.140.300.5.1.1.11
`tuxTmachineType` | .1.3.6.1.4.1.140.300.5.1.1.12
`tuxTmachineMaxAccessers` | .1.3.6.1.4.1.140.300.5.1.1.13
`tuxTmachineMaxConv` | .1.3.6.1.4.1.140.300.5.1.1.14
`tuxTmachineMaxGtt` | .1.3.6.1.4.1.140.300.5.1.1.15
`tuxTmachineMaxWsClients` | .1.3.6.1.4.1.140.300.5.1.1.16
`tuxTmachineMaxAclCache` | .1.3.6.1.4.1.140.300.5.1.1.17
`tuxTmachineTlogDevice` | .1.3.6.1.4.1.140.300.5.1.1.18
`tuxTmachineTlogName` | .1.3.6.1.4.1.140.300.5.1.1.19
`tuxTmachineTlogSize` | .1.3.6.1.4.1.140.300.5.1.1.20
`tuxTmachineBridge` | .1.3.6.1.4.1.140.300.5.1.1.21
`tuxTmachineNaddr` | .1.3.6.1.4.1.140.300.5.1.1.22
`tuxTmachineNlsaddr` | .1.3.6.1.4.1.140.300.5.1.1.23
`tuxTmachineCmpLimit` | .1.3.6.1.4.1.140.300.5.1.1.24
`tuxTmachineTmNetLoad` | .1.3.6.1.4.1.140.300.5.1.1.25
`tuxTmachineSpinCount` | .1.3.6.1.4.1.140.300.5.1.1.26
`tuxTmachineRole` | .1.3.6.1.4.1.140.300.5.1.1.27
`tuxTmachineMinor` | .1.3.6.1.4.1.140.300.5.1.1.28
`tuxTmachineRelease` | .1.3.6.1.4.1.140.300.5.1.1.29
`tuxTmachineMaxPendingBytes` | .1.3.6.1.4.1.140.300.5.1.1.30
m3MaxMachineObjects | .1.3.6.1.4.1.140.300.5.1.1.35

### tuxTmachinePmid

> #### Syntax

> >     DisplayString (SIZE (1..30))

> #### Access

> read-write

> #### Description

> Physical machine identifier. This identifier should match the UNIX system nodename as returned by the `uname -n` command when run on the identified system. For a Windows NT system, this identifier should match the computer name and the name configured with the name server.

> Note: This object can be set only during row creation.

### tuxTmachineLmid

> #### Syntax

> >     DisplayString (SIZE (1..30))

> #### Access

> read-write

> #### Description

> Logical machine identifier.

> Note: This object can be set only during row creation.

### tuxTmachineTuxConfig

> #### Syntax

> >     DisplayString (SIZE (2..78))

> #### Access

> read-write

> #### Description

> Absolute pathname of the file or device where the binary TUXEDO System/T configuration file is found on this machine. The administrator need only maintain one such file, namely the one identified by the `tuxTmachineTuxConfig` attribute value on the master machine. The information contained in this file is automatically propagated to all other `tuxTmachineTable` objects as they are activated. See `tuxTmachineEnvFile` for a discussion of how this attribute value is used in the environment.

### tuxTmachineTuxDir

> #### Syntax

> >     DisplayString (SIZE (2..78))

> #### Access

> read-write

> #### Description

> Absolute pathname of the directory where the TUXEDO System/T software is found on this machine. See `tuxTmachineEnvFile` below for a discussion of how this attribute value is used in the environment.

### tuxTmachineAppDir

> #### Syntax

> >     DisplayString (SIZE (2..78))

> #### Access

> read-write

> #### Description

> Colon separated list of application directory absolute pathnames. The first directory serves as the current directory for all application and administrative servers booted on this machine. All directories in the list are searched when starting application servers. See `tuxTmachineEnvFile` for a discussion of how this attribute value is used in the environment.

### tuxTmachineState

> #### Syntax

> >     INTEGER { active(1), inactive(2), partitioned(3), invalid(4),
> >     re-activate(5), cleaning(7) }

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|inactive(2)|partitioned(3)}`
>   A `GET` operation will retrieve configuration and runtime information for the selected `tuxTmachineTable` instance(s). The following states indicate the meaning of a `tuxTmachineState` returned in response to a `GET` request. States not listed will not be returned

> `active(1)`
>   `tuxTmachineTable` instance defined and active (administrative servers, that is, DBBL, BBL, and BRIDGE).

> `inactive(2)`
>   `tuxTmachineTable` instance defined and inactive.

> `partitioned(3)`
>   `tuxTmachineTable` instance defined, listed in accessible bulletin boards as active, but currently unreachable.

> `SET: {active(1)|inactive(2)|invalid(4)|re-activate(5)|cleaning(7)}`
>   A `SET` operation will update configuration and run-time information for the selected `tuxTmachineTable` instance. The following states indicate the meaning of a `tuxTmachineState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate the `tuxTmachineTable` instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site as well as application servers configured to run on that site. State change allowed only when in the inactive(2) state. Successful return leaves the object in the active(1) state.

> `inactive(2)`
>   Deactivate the `tuxTmachineTable` instance. Necessary administrative servers such as the BBL and BRIDGE are stopped on the indicated site as well as application servers running on that site. State change allowed only when in the active(1) state and when no other application resources are active on the indicated machine. Successful return leaves the object in the inactive(2) state.

> `invalid(4)`
>   Delete `tuxTmachineTable` instance for application. State change allowed only when in the inactive(2) state. Successful return leaves the object in the `invalid(4)` state.

> `re-activate(5)`
>   Activate the `tuxTmachineTable` instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site. State change allowed only when in either the active(1) or inactive(2) state. Successful return leaves the object in the active(1) state.

> `cleaning(7)`
>   Initiate cleanup/scanning activities on and relating to the indicated machine. If there are dead clients or servers on the machine, they will be detected at this time. If the machine has been partitioned from the application master site, then global bulletin board entries for that machine will be removed. This combination is allowed when the application is in the active(1) state and the `tuxTmachineTable` instance is in either the active(1) or partitioned(3) state. Successful return for a non-partitioned machine leaves the state unchanged. Successful return for a partitioned machine leaves the object in the inactive(2) state.

> Note: State change to inactive(2) allowed only for non-master machines. The master site administrative processes are deactivated via the `tuxTdomain` class.

### tuxTmachineUid

> #### Syntax

> >     INTEGER

> #### Access

> read-write

> #### Description

> UNIX system user identifier for the TUXEDO System/T application administrator on this machine. Administrative commands such as `tmboot`(1), `tmshutdown`(1), and `tmadmin`(1) must run as the indicated user on this machine. Application and administrative servers on this machine will be started as this user.

> Note: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTmachineGid

> #### Syntax

> >     INTEGER

> #### Access

> read-write

> #### Description

> UNIX system group identifier for the TUXEDO System/T application administrator on this machine. Administrative commands such as `tmboot`(1), `tmshutdown`(1), and `tmadmin`(1) must run as part of the indicated group on this machine. Application and administrative servers on this machine will be started as part of this group.

> Note: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTmachineEnvFile

> #### Syntax

> >     DisplayString (SIZE (2..78))

> #### Access

> read-write

> #### Description

> Environment file for clients and servers running on this machine.

### tuxTmachinePerm

> #### Syntax

> >     DisplayString (SIZE(1..9))

> #### Access

> read-write

> #### Description

> UNIX system permissions associated with the shared memory bulletin board created on this machine. Default UNIX system permissions for system and application message queues.

> Note: Modifications to this attribute for an active object will not affect running servers or clients.

> Note: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTmachineUlogPfx

> #### Syntax

> >     DisplayString (SIZE (0..78))

> #### Access

> read-write

> #### Description

> Absolute pathname prefix of the path for the `userlog`(3) file on this machine. The `userlog`(3) file name is formed by appending the string .`mmddyy` to the `tuxTmachineUlogPfx` attribute value .`mmddyy` represents the month, day, and year that the messages were generated. All application and system `userlog`(3) messages generated by clients and servers running on this machine are directed to this file.

> Note: Modifications to this attribute for an active object will not affect running servers or clients.

### tuxTmachineType

> #### Syntax

> >     DisplayString (SIZE (1..15))

> #### Access

> read-write

> #### Description

> Machine type. Used to group machines into classes of like data representations. Data encoding is not performed when communicating between machines of identical types. This attribute can be given any string value; values are used only for comparison. Distinct `tuxTmachineType` attributes should be set when the application spans a heterogeneous network of machines or when compilers generate dissimilar structure representations. The default value for this attribute, a 0-length string, matches any other machine with a 0-length string as its `tuxTmachineType` attribute value.

### tuxTmachineMaxAccessers

> #### Syntax

> >     INTEGER (1..32767)

> #### Access

> read-write

> #### Description

> Maximum number of clients and servers that can have access to the bulletin board on this machine at one time. System administration processes such as the BBL and tmadmin need not be accounted for in this figure, but all application servers and clients and TMS servers should be counted. If the application is booting workstation listeners on this site, then both the listeners and the potential number of workstation handlers that may be booted should be counted.

### tuxTmachineMaxConv

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-write

> #### Description

> Maximum number of simultaneous conversations in which clients and servers on this machine can be involved.

### tuxTmachineMaxGtt

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-write

> #### Description

> Maximum number of simultaneous global transactions in which this machine can be involved.

### tuxTmachineMaxWsClients

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-write

> #### Description

> Number of entries for accessers on this machine to be reserved for workstation clients. The number specified here takes a portion of the total slots for accessers specified with the `tuxTmachineMaxAccessers` attribute. The appropriate setting of this parameter helps to conserve IPC resources since workstation client access to the system is multiplexed through a System/T supplied surrogate, the workstation handler. It is an error to set this number greater than `tuxTmachineMaxAccessers`.

### tuxTmachineMaxAclCache

> #### Syntax

> >     INTEGER (10..32000)

> #### Access

> read-write

> #### Description

> Number of entries in the cache used for ACL entries when `tuxTdomainSecurity` is set to `acl(4)` or `mandatory-acl(5)`. The appropriate setting of this parameter helps to conserve shared memory resources and yet reduce the number of disk access to do ACL checking.

### tuxTmachineTlogDevice

> #### Syntax

> >     DisplayString (SIZE (0..64))

> #### Access

> read-write

> #### Description

> The device (raw slice) or UNIX system file containing the TUXEDO System/T filesystem that holds the DTP transaction log for this machine. The DTP transaction log is stored as a TUXEDO System/T VTOC table on the device. This device or file may be the same as that specified for the `tuxTmachineTuxConfig` attribute for this machine.

### tuxTmachineTlogName

> #### Syntax

> >     DisplayString (SIZE (0..30))

> #### Access

> read-write

> #### Description

> The name of the DTP transaction log for this machine. If more than one DTP transaction log exists on the same `tuxTmachineTlogDevice`, they must have unique names. `tuxTmachineTlogName` must be different from the name of any other table on the `tuxTmachineTlogDevice` where the DTP transaction log table is created.

### tuxTmachineTlogSize

> #### Syntax

> >     INTEGER (1..2048)

> #### Access

> read-write

> #### Description

> The numeric size, in pages, of the DTP transaction log for this machine. The `tuxTmachineTlogSize` attribute value is subject to limits based on available space in the TUXEDO System/T filesystem identified by the `tuxTmachineTlogDevice` attribute.

### tuxTmachineBridge

> #### Syntax

> >     DisplayString (SIZE (0..78))

> #### Access

> read-write

> #### Description

> Device name to be used by the BRIDGE process placed on this logical machine to access the network. This is a required value for participation in a networked application via a TLI-based TUXEDO System/T binary. This attribute is not needed for sockets-based TUXEDO System/T binaries.

### tuxTmachineNaddr

> #### Syntax

> >     DisplayString (SIZE (0..78))

> #### Access

> read-write

> #### Description

> Specifies the complete network address to be used by the BRIDGE process placed on the logical machine as its listening address. The listening address for a BRIDGE is the means by which it is contacted by other BRIDGE processes participating in the application. This attribute must be set if the logical machine is to participate in a networked application, that is, if the LAN option is set in the `tuxTdomainOptions` attribute value.

> If string has the form `0xhex-digits` or `\\xhex-digits`, it must contain an even number of valid hexadecimal digits. These forms are translated internally into a character array containing the hexadecimal representations of the string specified.

### tuxTmachineNlsaddr

> #### Syntax

> >     DisplayString (SIZE (0..78))

> #### Access

> read-write

> #### Description

> Network address used by the `tlisten`(1) process servicing the network on the node identified by this logical machine. This network address is of the same format as that specified for the `tuxTmachineNaddr` attribute.

> This attribute must be set if the logical machine is to participate in a networked application, that is, if the LAN option is set in the `tuxTdomainOptions` attribute value.

### tuxTmachineCmpLimit

> #### Syntax

> >     DisplayString

> #### Access

> read-write

> #### Description

> Threshold message size at which compression will occur for remote traffic and optionally local traffic. Remote and local may be either non-negative numeric values or the string `MAXLONG`, which is dynamically translated to the maximum long setting for the machine. Setting only the remote value will default local to `MAXLONG`.

> Note: This attribute value is not part of the `tuxTmachineTable` object for active sites running TUXEDO System/T Release 4.2.2 or earlier. However, site release identification is not determined until runtime, so this attribute may be set and accessed for any inactive object. When a TUXEDO System/T Release 4.2.2 or earlier site is activated, the configured value is not used.

### tuxTmachineTmNetLoad

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-write

> #### Description

> Service load added to any remote service evaluated during load balancing on this machine.

> Note: This attribute value is not part of the `tuxTmachineTable` object for active sites running TUXEDO System/T Release 4.2.2 or earlier. However, site release identification is not determined until runtime, so this attribute may be set and accessed for any inactive object. When a TUXEDO System/T Release 4.2.2 or earlier site is activated, the configured value is not used.

### tuxTmachineSpinCount

> #### Syntax

> >     INTEGER

> #### Access

> read-write

> #### Description

> Spincount used on this machine for pre-ticket user level semaphore access. Default values are built into the TUXEDO System/T binaries on each machine. These defaults may be overridden at runtime for tuning purposes using this attribute. The spincount may be reset to the default built-in value for the site by resetting this attribute value to 0.

> Note: This attribute value is not part of the `tuxTmachineTable` object for active sites running TUXEDO System/T Release 4.2.2 or earlier. However, site release identification is not determined until runtime, so this attribute may be set and accessed for any inactive object. When a TUXEDO System/T Release 4.2.2 or earlier site is activated, the configured value is not used.

### tuxTmachineRole

> #### Syntax

> >     INTEGER { master(1), backup(2), other(3) }

> #### Access

> read-only

> #### Description

> The role of this machine in the application. `master(1)` indicates that this machine is the master machine, `backup(2)` indicates that it is the backup master machine, and `other(3)` indicates that the machine is neither the master nor backup master machine.

### tuxTmachineMinor

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> The TUXEDO System/T minor protocol release number for this machine.

### tuxTmachineRelease

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> The TUXEDO System/T major protocol release number for this machine. This may be different from the `tuxTmachineSWrelease` for the same machine.

### tuxTmachineMaxPendingBytes

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Specifies a limit for the amount of space that can be allocated for messages waiting to be transmitted by the BRIDGE process. The minimum value for this is 100000. This object is supported on TUXEDO 6.4 and later only.

### m3MachineMaxObjects

> #### Syntax

> INTEGER

> #### Access

> read-write

> #### Description

> The maximum number of objects to be accommodated in the Active Object Map tables in the bulletin board.

> Note: This object is supported for M3 applications only.

## tuxTmachineActive

This group represents run-time statistics on the local machine if it is active (i.e., some component of the application is active on the machine). Objects in this group are only accessible through a TUXEDO SNMP agent installed on the local machine.

Variable Name | Object ID
--- | ---
`tuxTmachineCurAccessers` | .1.3.6.1.4.1.140.300.5.2.1
`tuxTmachineCurClients` | .1.3.6.1.4.1.140.300.5.2.2
`tuxTmachineCurConv` | .1.3.6.1.4.1.140.300.5.2.3
`tuxTmachineCurGTT` | .1.3.6.1.4.1.140.300.5.2.4
`tuxTmachineCurLoad` | .1.3.6.1.4.1.140.300.5.2.5
`tuxTmachineCurWsClients` | .1.3.6.1.4.1.140.300.5.2.6
`tuxTmachineHwAccessers` | .1.3.6.1.4.1.140.300.5.2.7
`tuxTmachineHwClients` | .1.3.6.1.4.1.140.300.5.2.8
`tuxTmachineHwConv` | .1.3.6.1.4.1.140.300.5.2.9
`tuxTmachineHwGTT` | .1.3.6.1.4.1.140.300.5.2.10
`tuxTmachineHwWsClients` | .1.3.6.1.4.1.140.300.5.2.11
`tuxTmachineNumConv` | .1.3.6.1.4.1.140.300.5.2.12
`tuxTmachineNumDequeue` | .1.3.6.1.4.1.140.300.5.2.13
`tuxTmachineNumEnqueue` | .1.3.6.1.4.1.140.300.5.2.14
`tuxTmachineNumPost` | .1.3.6.1.4.1.140.300.5.2.15
`tuxTmachineNumReq` | .1.3.6.1.4.1.140.300.5.2.16
`tuxTmachineNumSubscribe` | .1.3.6.1.4.1.140.300.5.2.17
`tuxTmachineNumTran` | .1.3.6.1.4.1.140.300.5.2.18
`tuxTmachineNumTranAbt` | .1.3.6.1.4.1.140.300.5.2.19
`tuxTmachineNumTranCmt` | .1.3.6.1.4.1.140.300.5.2.20
`tuxTmachineLicExpires` | .1.3.6.1.4.1.140.300.5.2.21
`tuxTmachineLicMaxUsers` | .1.3.6.1.4.1.140.300.5.2.22
`tuxTmachineLicSerial` | .1.3.6.1.4.1.140.300.5.2.23
`tuxTmachinePageSize` | .1.3.6.1.4.1.140.300.5.2.24
`tuxTmachineSWrelease` | .1.3.6.1.4.1.140.300.5.2.25
`tuxTmachineHwAclCache` | .1.3.6.1.4.1.140.300.5.2.26
`tuxTmachineAclCacheHits` | .1.3.6.1.4.1.140.300.5.2.27
`tuxTmachineAclCacheAccess` | .1.3.6.1.4.1.140.300.5.2.28
`tuxTmachineAclFail` | .1.3.6.1.4.1.140.300.5.2.29
`tuxTmachineWkCompleted` | .1.3.6.1.4.1.140.300.5.2.30
`tuxTmachineWkInitiated` | .1.3.6.1.4.1.140.300.5.2.31
m3MachineCurObjects | .1.3.6.1.4.1.140.300.5.2.36
m3MachineHwObjects | .1.3.6.1.4.1.140.300.5.2.41

### tuxTmachineCurAccessers

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Number of clients and servers currently accessing the application either directly on this machine or through a workstation handler on this machine.

### tuxTmachineCurClients

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Number of clients, both native and workstation, currently logged in to this machine.

### tuxTmachineCurConv

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Number of active conversations with participants on this machine.

### tuxTmachineCurGTT

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Number of in use transaction table entries on this machine.

### tuxTmachineCurLoad

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Current service load enqueued on this machine.

> Note: If the `tuxTdomainLoadBalance` attribute is `no(2)` or the `tuxTdomainModel` attribute is `multi-machine(2)`, then an FML32 NULL value is returned (0).

### tuxTmachineCurWsClients

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Number of workstation clients currently logged in to this machine.

### tuxTmachineHwAccessers

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> High water number of clients and servers accessing the application either directly on this machine or through a workstation handler on this machine.

### tuxTmachineHwClients

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> High water number of clients, both native and workstation, logged in to this machine.

### tuxTmachineHwConv

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> High water number of active conversations with participants on this machine.

### tuxTmachineHwGTT

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> High water number of in use transaction table entries on this machine.

### tuxTmachineHwWsClients

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> High water number of workstation clients currently logged in to this machine.

### tuxTmachineNumConv

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tpconnect`(3) operations performed from this machine.

### tuxTmachineNumDequeue

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tpdequeue`(3) operations performed from this machine.

### tuxTmachineNumEnqueue

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tpenqueue`(3) operations performed from this machine.

### tuxTmachineNumPost

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tppost`(3) operations performed from this machine.

### tuxTmachineNumReq

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tpacall`(3) or `tpcall`(3) operations performed from this machine.

### tuxTmachineNumSubscribe

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of `tpsubscribe`(3) operations performed from this machine.

### tuxTmachineNumTran

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of transactions initiated (`tpbegin`(3)) from this machine.

### tuxTmachineNumTranAbt

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of transactions aborted (`tpabort`(3)) from this machine.

### tuxTmachineNumTranCmt

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of transactions committed (`tpcommit`(3)) from this machine.

### tuxTmachineLicExpires

> #### Syntax

> >     DisplayString (SIZE(0..78))

> #### Access

> read-only

> #### Description

> Expiration date for the binary on that machine or a 0-length string if binary is not a TUXEDO System/T master binary.

### tuxTmachineLicMaxUsers

> #### Syntax

> >     INTEGER (0..32767)

> #### Access

> read-only

> #### Description

> Licensed maximum number of users on that machine or -1 if binary is not a TUXEDO System/T master binary.

### tuxTmachineLicSerial

> #### Syntax

> >     DisplayString (SIZE(0..78))

> #### Access

> read-only

> #### Description

> Serial number for binary on that machine or a 0-length string if binary is not a TUXEDO System/T master binary.

### tuxTmachinePageSize

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Disk pagesize used on this machine.

### tuxTmachineSWrelease

> #### Syntax

> >     DisplayString (SIZE(0..78))

> #### Access

> read-only

> #### Description

> Software release for binary on that machine or a 0-length string if binary is not a TUXEDO System/T master binary.

### tuxTmachineHwAclCache

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> High water number of entries used in the ACL cache.

### tuxTmachineAclCacheHits

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of accesses to the ACL cache that resulted in a "hit" (that is, the entry was already in the cache).

### tuxTmachineAclCacheAccess

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of accesses to the ACL cache.

### tuxTmachineAclFail

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Number of accesses to the ACL cache that resulted in a access control violation.

### tuxTmachineWkCompleted

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Total service load dequeued and processed successfully by servers running on this machine. Note that for long running applications this attribute may wraparound, that is, exceed the maximum value for a long, and start back at 0 again.

### tuxTmachineWkInitiated

> #### Syntax

> >     INTEGER

> #### Access

> read-only

> #### Description

> Total service load enqueued by clients/servers running on this machine. Note that for long running applications this attribute may wraparound, that is, exceed the maximum value for a long, and start back at 0 again.

### m3MachineCurObjects

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of entries in use in the bulletin board object table for this machine.

> Note: This object is supported for M3 applications only.

### m3MachineHwObjects

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The high water mark of entries used in the bulletin board object table for this machine.

> Note: This object is supported for M3 applications only.

## tuxTmsgTable

The `tuxTmsgTable` class represents runtime attributes of the TUXEDO System/T managed UNIX system message queues. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine. `tuxTmsgId` is the index into this table.

Variable Name | Object ID
--- | ---
`tuxTmsgId` | .1.3.6.1.4.1.140.300.6.1.1.1
`tuxTmsgState` | .1.3.6.1.4.1.140.300.6.1.1.2
`tuxTmsgCurTime` | .1.3.6.1.4.1.140.300.6.1.1.3
`tuxTmsgCbytes` | .1.3.6.1.4.1.140.300.6.1.1.4
`tuxTmsgCtime` | .1.3.6.1.4.1.140.300.6.1.1.5
`tuxTmsgLrPid` | .1.3.6.1.4.1.140.300.6.1.1.6
`tuxTmsgLsPid` | .1.3.6.1.4.1.140.300.6.1.1.7
`tuxTmsgQbytes` | .1.3.6.1.4.1.140.300.6.1.1.8
`tuxTmsgQnum` | .1.3.6.1.4.1.140.300.6.1.1.9
`tuxTmsgRtime` | .1.3.6.1.4.1.140.300.6.1.1.10
`tuxTmsgStime` | .1.3.6.1.4.1.140.300.6.1.1.11

### tuxTmsgId

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system message queue identifier.

> Note: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTmsgState

> #### Syntax

> `INTEGER { active(1) }`

> #### Access

> read-only

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)`
>   A `GET` operation will retrieve runtime information for the selected `tuxTmsgTable` object(s). The following state indicates the meaning of a `tuxTmsgState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTmsgTable` object active. This corresponds exactly to the related `tuxTmachineTable` object being active.

> `SET:`
>   `SET` operations are not permitted on this class.

### tuxTmsgCurTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on the local host.

### tuxTmsgCbytes

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current number of bytes on the queue.

### tuxTmsgCtime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time of the last `msgctl`(2) operation that changed a member of the `msqid_ds` structure associated with the queue.

### tuxTmsgLrPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier of the last process that read from the queue.

### tuxTmsgLsPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier of the last process that wrote to the queue.

### tuxTmsgQbytes

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Maximum number of bytes allowed on the queue.

### tuxTmsgQnum

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of messages currently on the queue.

### tuxTmsgRtime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time since the last read from the queue.

### tuxTmsgStime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time since the last write to the queue.

## tuxTqueueTable

The `tuxTqueueTable` group represents runtime attributes of queues in an application. These attribute values identify and characterize allocated TUXEDO System/T request queues associated with servers in a running application. They also track statistics related to application workloads associated with each queue object. The index into this table is `tuxTqueueRqAddr`. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine

Variable Name | Object ID
--- | ---
`tuxTqueueRqAddr` | .1.3.6.1.4.1.140.300.7.1.1.1
`tuxTqueueState` | .1.3.6.1.4.1.140.300.7.1.1.2
`tuxTqueueRqId` | .1.3.6.1.4.1.140.300.7.1.1.3
`tuxTqueueSrvrCnt` | .1.3.6.1.4.1.140.300.7.1.1.4
`tuxTqueueTotNqueued` | .1.3.6.1.4.1.140.300.7.1.1.5
`tuxTqueueTotWkQueued` | .1.3.6.1.4.1.140.300.7.1.1.6
`tuxTqueueSource` | .1.3.6.1.4.1.140.300.7.1.1.7
`tuxTqueueNqueued` | .1.3.6.1.4.1.140.300.7.1.1.8
`tuxTqueueWkQueued` | .1.3.6.1.4.1.140.300.7.1.1.9

### tuxTqueueRqAddr

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Symbolic address of the request queue. Servers with the same `tuxTsrvrRqAddr` attribute value are grouped into a Multiple Server Single Queue (MSSQ) set. Attribute values returned with a `tuxTqueueTable` object apply to all active servers associated with this symbolic queue address.

### tuxTqueueState

> #### Syntax

> `INTEGER { active(1), migrating(2), suspended(3), partitioned(4) }`

> #### Access

> read-only

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|migrating(2)|suspended(3)|partitioned(4)}`
>   A `GET` operation will retrieve runtime information for the selected `tuxTqueueTable` instance(s). The `tuxTqueueTable` group does not address configuration information directly. Configuration related attributes discussed here must be set as part of the related `tuxTsrvrTbl` instances. The following states indicate the meaning of a `tuxTqueueState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   At least one server associated with this `tuxTqueueTable` instance is active(1).

> `migrating(2)`
>   The server(s) associated with this `tuxTqueueTable` instance is currently in the migrating(2) state. See the `tuxTsrvrTbl` group for more details on this state.

> `suspended(3)`
>   The server(s) associated with this `tuxTqueueTable` instance is currently in the suspended(3) state. See the `tuxTsrvrTbl` group for more details on this state.

> `partitioned(4)`
>   The server(s) associated with this `tuxTqueueTable` instance is currently in the partitioned(4) state. See the `tuxTsrvrTbl` group for more details on this state.

> `SET:`
>   A `SET` operation will update runtime information for the selected `tuxTqueueTable` object. State changes are not allowed when updating `tuxTqueueTable` object information. Modification of an existing `tuxTqueueTable` object is allowed only when the object is in the active(1) state.

### tuxTqueueRqId

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system message queue identifier.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTqueueSrvrCnt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of active servers associated with this queue.

### tuxTqueueTotNqueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The sum of the queue lengths of this queue while it has been active. This sum includes requests enqueued to and processed by servers that are no longer active on the queue. Each time a new request is assigned to the queue, the sum is incremented by the length of the queue immediately before the new request is enqueued.

> Note: If the `tuxTdomainLoadBalance` attribute is `no(2)` or the `tuxTdomainModel` attribute is `multi-machine(2)`, then `tuxTqueueTotNqueued` is not returned. In the same configuration, updates to this attribute are ignored. Consequently, when this attribute is returned `tuxTqueueSource` has the same value as the local host.

### tuxTqueueTotWkQueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The sum of the workloads enqueued to this queue while it has been active. This sum includes requests enqueued to and processed by servers that are no longer active on the queue. Each time a new request is assigned to the queue, the sum is incremented by the workload on the queue immediately before the new request is enqueued.

> Note: If the `tuxTdomainLoadBalance` attribute is `no(2)` or the `tuxTdomainModel` attribute is `multi-machine(2)`, then `tuxTqueueTotWkQueued` is not returned. In the same configuration, updates to this attribute are ignored. Consequently, when this attribute is returned `tuxTqueueSource` has the same value as the local host.

### tuxTqueueSource

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine from which local attribute values are retrieved.

### tuxTqueueNqueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of requests currently enqueued to this queue from the `tuxTqueueSource` logical machine. This value is incremented at enqueue time and decremented when the server dequeues the request.

> Note: If the `tuxTdomainLoadBalance` attribute is `no(2)` or the `tuxTdomainModel` attribute is `multi-machine(2)`, then `tuxTqueueNqueued` is not returned. Consequently, when this attribute is returned `tuxTqueueSource` has the same value as the local host.

### tuxTqueueWkQueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Workload currently enqueued to this queue from the `tuxTqueueSource` logical machine. If the `tuxTdomainModel` attribute is set to `single-machine(1)` and the `tuxTdomainLoadBalance` attribute is set to `yes(1)`, then this attribute reflects the application-wide workload enqueued to this queue. However, if `tuxTdomainModel` is set to `multi-machine(2)` and `tuxTdomainLoadBalance` is set to `yes(1)`, this attribute reflects the workload enqueued to this queue from the `tuxTqueueSource` logical machine during a recent timespan. This attribute is used for load balancing purposes. So as to not discriminate against newly started servers, this attribute value is zeroed out on each machine periodically by the BBL.

## tuxTroutingTable

The `tuxTroutingTable` group represents configuration objects of routing specifications for an application. These object values identify and characterize application data dependent routing criteria with respect to field names, buffer types, and routing definitions. This table also represents configuration objects for Factory-based routing for M3 applications. `m3RoutingFieldType` is valid only for factory-based routing. `tuxTroutingBufType` is valid only for service-based routing.

The index into this table consists of the following attributes: `tuxTroutingName`, `beaRoutingType`, and `tuxInternalIdx`.

`m3RoutingFieldType` is valid only for factory-based routing. This is supported only for M3 applications.

`tuxTroutingBufType` is valid only for service-based routing (either TUXEDO or M3 applications).

When specifying the index in SET requests, `tuxInternalIdx` is used as an index.

For factory-based routing, `tuxInternalIdx` must always have a value of `-`.

For service-based routing, `tuxInternalIdx` should equal the first 30 characters in `tuxTroutingBufType`.

To create a new row in the table, it is necessary to issue a SET request for a non-existing row specifying the values of all objects applicable to the `beaRoutingType`.

Variable Name | Object ID
--- | ---
`tuxTroutingName` | .1.3.6.1.4.1.140.300.8.1.1.1
`tuxTroutingBufType` | .1.3.6.1.4.1.140.300.8.1.1.2
`tuxTroutingField` | .1.3.6.1.4.1.140.300.8.1.1.3
`tuxTroutingRanges` | .1.3.6.1.4.1.140.300.8.1.1.4
`tuxTroutingState` | .1.3.6.1.4.1.140.300.8.1.1.5
`beaRoutingType` | .1.3.6.1.4.1.140.300.8.1.1.6
`m3RoutingFieldType` | .1.3.6.1.4.1.140.300.8.1.1.7
`tuxInternalIdx` | .1.3.6.1.4.1.140.300.8.1.1.8

### tuxTroutingName

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-write

> #### Description

> Routing criterion name.

> Note: This object can be set only during row creation.

### tuxTroutingBufType

> #### Syntax

> `DisplayString` (`SIZE`(`1..256`))

> #### Access

> read-write

> #### Description

> List of types and subtypes of data buffers for which this routing entry is valid. A maximum of 32 type/subtype combinations are allowed. The types are restricted to be one of FML, VIEW, X_C_TYPE, or X_COMMON. No subtype can be specified for type FML, and subtypes are required for types VIEW, X_C_TYPE, and X_COMMON (`*` is not allowed). Note that subtype names should not contain semicolon, colon, comma, or asterisk characters. Duplicate type/subtype pairs cannot be specified for the same routing criterion name. More than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.

> Note: This object is applicable only for service-based routing.

> Note: This object can be set only during row creation.

### tuxTroutingField

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Routing field name.

> For Service-based Routing: This field is assumed to be an FML buffer or view field name that is identified in an FML field table (using the FLDTBLDIR and FIELDTBLS environment) or an FML view table (using the VIEWDIR and VIEWFILES environment), respectively. This information is used to get the associated field value for data dependent routing during the sending of a message.

> For Factory-based Routing: This is assumed to be a field that is specified in an NVList parameter to:

> `PortableServer::POA::create_reference_with_criteria`

> for an interface that has this factory routing criteria associated with it. See the M3 documentation for more details.

### tuxTroutingRanges

> #### Syntax

> `DisplayString` (`SIZE`(`1..2048`))

> #### Access

> read-write

> #### Description

> The ranges and associated server groups for a routing criterion are as follows:

> >     criterion: range: group
> >     range: value | lower - upper | *
> >     lower: value
> >     upper: value
> >     value: MIN | MAX | numeric | string
> >     group: string | *
> >     numeric: [+ | -]digits[.digits][e | E[ | + | - ] digit
> >     digit: 0-9
> >     digits: digit[digit]

> `\` can be used to escape the single-quote character in strings.

> `lower` must be less than `upper`. A group specified as a string must specify a valid `tuxTgroupName`.

> Note: Attribute values greater than 256 bytes in length will disable interoperability with TUXEDO System/T Release 4.2.2 and earlier.

### tuxTroutingState

> #### Syntax

> `INTEGER { valid(1), unknown(2), invalid(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: valid(1)`
>   A `GET` operation will retrieve configuration information for the selected `tuxTroutingTable` instance(s). The following state indicates the meaning of a `tuxTroutingState` returned in response to a `GET` request. States not listed will not be returned.

> `valid(1)`
>   `tuxTroutingTable` instance is defined. Note that this is the only valid state for this class. Routing criteria are never active; rather, they are associated through the configuration with service names and are acted upon at runtime to provide data dependent routing.

> `SET: invalid(3)`
>   A `SET` operation will update configuration information for the selected `tuxTroutingTable` instance. The following state indicates the meaning of a `tuxTroutingState` set in a `SET` request. States not listed may not be set.

> `invalid(3)`
>   Delete `tuxTroutingTable` instance for application. State change allowed only when in the valid(1) state. Successful return leaves the object in the invalid(2) state.

### beaRoutingType

> #### Syntax

> `INTEGER { service(1), factory(2) }`

> #### Access

> read-write

> #### Description

> `factory(2)` specifies that the routing criterion applies to factory-based routing for a CORBA interface. `service(1)` specifies that routing criteria apply to data-dependent routing for a BEA TUXEDO service.

> Note: The routing type affects the validity and possible values for other attributes defined for this table.

> Note: This object can be set during row creation only.

### m3RoutingFieldType

> #### Syntax

> `INTEGER { short(1), long(2), float(3), double(4), char(5), string(6) }`

> #### Access

> read-write

> #### Description

> This object specifies the type of `tuxTroutingField` on which this routing criterion is defined. This is valid only for factory-based routing.

> Note: This object is supported only for M3.

> Note: This object can be set only during row creation.

### tuxInternalIdx

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> This object is used as an index of this table instead of `tuxTroutingBufType` (for service-based routing) or `tuxTroutingField` (for factory-based routing) to reduce the size of the index. Its value, for service based routing (`beaRoutingType` = `service(1`)) is equal to the first 30 characters in `tuxTroutingBufType`.

> In case of entries for factory-based routing (`beaRoutingType` =`factory(2)`), its value is always `tuxTroutingField`.

> Note: This object can be set only during row creation.

## tuxTsrvrTbl

This group represents configuration and runtime attributes of servers within an application. These attribute values identify and characterize configured servers as well as provide runtime tracking of statistics and resources associated with each server object. The index into this table is provided by the attributes `tuxTsrvrGrpNo` and `tuxTsrvrId`. To create a new row in the table, it is necessary to issue a SET request specifying the values of at least `tuxTsrvrGrp` and `tuxTsrvrName`.

Variable Name | Object ID
--- | ---
`tuxTsrvrGrp` | .1.3.6.1.4.1.140.300.20.1.1.1
`tuxTsrvrId` | .1.3.6.1.4.1.140.300.20.1.1.2
`tuxTsrvrName` | .1.3.6.1.4.1.140.300.20.1.1.3
`tuxTsrvrGrpNo` | .1.3.6.1.4.1.140.300.20.1.1.4
`tuxTsrvrState` | .1.3.6.1.4.1.140.300.20.1.1.5
`tuxTsrvrBaseSrvId` | .1.3.6.1.4.1.140.300.20.1.1.6
`tuxTsrvrClOpt` | .1.3.6.1.4.1.140.300.20.1.1.7
`tuxTsrvrEnvFile` | .1.3.6.1.4.1.140.300.20.1.1.8
`tuxTsrvrGrace` | .1.3.6.1.4.1.140.300.20.1.1.9
`tuxTsrvrMaxgen` | .1.3.6.1.4.1.140.300.20.1.1.10
`tuxTsrvrMax` | .1.3.6.1.4.1.140.300.20.1.1.11
`tuxTsrvrMin` | .1.3.6.1.4.1.140.300.20.1.1.12
`tuxTsrvrRcmd` | .1.3.6.1.4.1.140.300.20.1.1.13
`tuxTsrvrRestart` | .1.3.6.1.4.1.140.300.20.1.1.14
`tuxTsrvrSequence` | .1.3.6.1.4.1.140.300.20.1.1.15
`tuxTsrvrSystemAccess` | .1.3.6.1.4.1.140.300.20.1.1.16
`tuxTsrvrConv` | .1.3.6.1.4.1.140.300.20.1.1.17
`tuxTsrvrReplyQ` | .1.3.6.1.4.1.140.300.20.1.1.18
`tuxTsrvrRpPerm` | .1.3.6.1.4.1.140.300.20.1.1.19
`tuxTsrvrRqAddr` | .1.3.6.1.4.1.140.300.20.1.1.20
`tuxTsrvrRqPerm` | .1.3.6.1.4.1.140.300.20.1.1.21
`tuxTsrvrGeneration` | .1.3.6.1.4.1.140.300.20.1.1.22
`tuxTsrvrPid` | .1.3.6.1.4.1.140.300.20.1.1.23
`tuxTsrvrRpid` | .1.3.6.1.4.1.140.300.20.1.1.24
`tuxTsrvrRqId` | .1.3.6.1.4.1.140.300.20.1.1.25
`tuxTsrvrTimeRestart` | .1.3.6.1.4.1.140.300.20.1.1.26
`tuxTsrvrTimeStart` | .1.3.6.1.4.1.140.300.20.1.1.27

### tuxTsrvrGrp

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Logical name of the server group. Server group names cannot contain an asterisk (*), comma, or colon.

> Note: This object can be set only during row creation.

### tuxTsrvrId

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-write

> #### Description

> Unique (within the server group) server identification number.

> Note: This object can be set only during row creation.

### tuxTsrvrName

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-write

> #### Description

> Name of the server executable file. The server identified by `tuxTsrvrName` will run on the machine(s) identified by the `tuxTgroupLMID` object for this server's server group. If a relative pathname is given, then the search for the executable file is done first in `tuxTmachineAppDir`, then in `tuxTmachineTuxDir/bin,` then in `/bin` and `/usr/bin`, and then in `<path>`, where `<path>` is the value of the first `PATH=` line appearing in the machine environment file, if one exists. Note that the attribute value returned for an active server will always be a full pathname.

### tuxTsrvrGrpNo

> #### Syntax

> `INTEGER (1..30000)`

> #### Access

> read-only

> #### Description

> Group number associated with this server's group.

### tuxTsrvrState

> #### Syntax

> >     INTEGER { active(1), inactive(2), migrating(3), cleaning(4),
> >     restarting(5), suspended(6), partitioned(7), dead(8), invalid(10) }

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)|inactive(2)|migrating(3)|cleaning(4)|restarting(5)|
> suspended(6)|partitioned(7)|dead(8)`
>   A `GET` operation will retrieve configuration and runtime information for the selected `tuxTsrvrTbl` instance(s). The following states indicate the meaning of a `tuxTsrvrState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTsrvrTbl` instance defined and active. This is not an indication of whether the server is idle or busy. An active server with a non-0 length `tuxTsrvrCurService` attribute should be interpreted as a busy server, that is, one that is processing a service request.

> `inactive(2)`
>   `tuxTsrvrTbl` instance defined and inactive.

> `migrating(3)`
>   `tuxTsrvrTbl` instance defined and currently in a state of migration to the server group's secondary logical machine. The secondary logical machine is the one listed in `tuxTgroupLMID` attribute that does not match the `tuxTgroupCurLMID` object.

> `cleaning(4)`
>   `tuxTsrvrTbl` instance defined and currently being cleaned up after by the system due to an abnormal death. Note that restartable servers may enter this state if they exceed `tuxTsrvrMaxgen` starts/restarts within their `tuxTsrvrGrace` period.

> `restarting(5)`
>   `tuxTsrvrTbl` instance defined and currently being restarted by the system due to an abnormal death.

> `suspended(6)`
>   `tuxTsrvrTbl` instance defined and currently suspended pending shutdown.

> `partitioned(7)`
>   `tuxTsrvrTbl` instance defined and active; however, the machine where the server is running is currently partitioned from the `tuxTdomainMaster` site.

> `dead(8)`
>   `tuxTsrvrTbl` instance defined, identified as active in the bulletin board, but currently not running due to an abnormal death. This state will exist only until the BBL local to the server notices the death and takes action (`restarting(5)|cleaning(4)`).

> `SET: {active(1)|inactive(2)|dead(8)|invalid(10)}`
>   A `SET` operation will update configuration and run-time information for the selected `tuxTsrvrTbl` instance. The following states indicate the meaning of a `tuxTsrvrState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate the `tuxTsrvrTbl` instance. State change allowed only when in the `inactive(2)` state. (Servers in the `migrating(3)` state must be restarted by setting the `tuxTgroupState` to `active(1)`.) Successful return leaves the object in the `active(1)` state.

> `inactive(2)`
>   Deactivate the `tuxTsrvrTbl` instance. State change allowed only when in the `active(1)` state. Successful return leaves the object in the `inactive(2)` state.

> `dead(8)`
>   Deactivate the `tuxTsrvrTbl` instance by sending the server a SIGTERM signal followed by a SIGKILL signal if the server is still running after 20 seconds. Note that by default, a SIGTERM signal will cause the server to initiate orderly shutdown and the server will become inactive even if it is restartable. If a server is processing a long running service or has chosen to disable the SIGTERM signal, then SIGKILL may be used and will be treated by the system as an abnormal termination. State change allowed only when in the `active(1)` or `suspended(6)` state. Successful return leaves the object in the `inactive(2)`, `cleaning(4)`, or `restarting(5)` state.

> `invalid(10)`
>   Delete `tuxTsrvrTbl` instance for application. State change allowed only when in the `inactive(2)` state. Successful return leaves the object in the `invalid(10)` state.

### tuxTsrvrBaseSrvId

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Base server identifier. For servers with a `tuxTsrvrMax` attribute value of 1, this attribute will always be the same as `tuxTsrvrId`. However, for servers with a `tuxTsrvrMax` value of greater than 1, this attribute indicates the base server identifier for the set of servers configured identically.

### tuxTsrvrClOpt

> #### Syntax

> `DisplayString` (`SIZE`(`0..256`))

> #### Access

> read-write

> #### Description

> Command line options to be passed to server when it is activated. See the `servopts`(5) manual page for details.

> Note: Runtime modifications to this attribute will not affect a running server.

### tuxTsrvrEnvFile

> #### Syntax

> `DisplayString` (`SIZE`(`0..78`))

> #### Access

> read-write

> #### Description

> Server specific environment file. See `tuxTmachineEnvFile` for a complete discussion of how this file is used to modify the environment.

> Note: Runtime modifications to this attribute will not affect a running server.

### tuxTsrvrGrace

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> The period of time, in seconds, over which the `tuxTsrvrMaxgen` limit applies. This attribute is meaningful only for restartable servers, that is, if the `tuxTsrvrRestart` attribute is set to `yes(1)`. When a restarting server would exceed the `tuxTsrvrMaxgen` limit but the `tuxTsrvrGrace` period has expired, the system resets the current generation (`tuxTsrvrGeneration`) to 1 and resets the initial boot time (`tuxTsrvrTimeStart`) to the current time. A value of 0 for this attribute indicates that a server should always be restarted.

> Note that servers sharing a request queue (that is, equal values for `tuxTsrvrRqAddr`) should have equal values for this attribute. If they do not, then the first server activated will establish the runtime value associated with all servers on the queue.

> Note: Runtime modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

### tuxTsrvrMaxgen

> #### Syntax

> `INTEGER (0..256)`

> #### Access

> read-write

> #### Description

> Number of generations allowed for a restartable server (`tuxTsrvrRestart == yes(1)`) over the specified grace period (`tuxTsrvrGrace`). The initial activation of the server counts as one generation and each restart also counts as one. Processing after the maximum generations is exceeded is discussed above with respect to `tuxTsrvrGrace`.

> Note that servers sharing a request queue (that is, equal values for `tuxTsrvrRqAddr`) should have equal values for this attribute. If they do not, then the first server activated will establish the runtime value associated with all servers on the queue.

> Note: Runtime modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

### tuxTsrvrMax

> #### Syntax

> `INTEGER (1..1001)`

> #### Access

> read-write

> #### Description

> Maximum number of occurrences of the server to be booted. Initially, `tmboot`(1) boots `tuxTsrvrMin` objects of the server, and additional objects may be started individually (by starting a particular server id) or through automatic spawning (conversational servers only). Runtime modifications to this attribute will affect all running servers in the set of identically configured servers (see `tuxTsrvrBaseSrvId` above) as well as the configuration definition of the server.

### tuxTsrvrMin

> #### Syntax

> `INTEGER (1..1001)`

> #### Access

> read-write

> #### Description

> Minimum number of occurrences of the server to be booted by `tmboot`(1). If a `tuxTsrvrRqAddr` is specified and `tuxTsrvrMin` is greater than 1, then the servers will form an MSSQ set. The server identifiers for the servers will be `tuxTsrvrId` up to `tuxTsrvrId + tuxTsrvrMax - 1`. All occurrences of the server will have the same sequence number, as well as any other server parameters.

> Note: Runtime modifications to this attribute will not affect a running server.

### tuxTsrvrRcmd

> #### Syntax

> `DisplayString` (`SIZE`(`0..78`))

> #### Access

> read-write

> #### Description

> Application specified command to be executed in parallel with the system restart of an application server. This command must be an executable file.

> Note that servers sharing a request queue (that is, equal values for `tuxTsrvrRqAddr`) should have equal values for this attribute. If they do not, then the first server activated will establish the runtime value associated with all servers on the queue.

> Note: Runtime modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

### tuxTsrvrRestart

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Restartable `yes(1)` or non-restartable `no(2)` server. If server migration is specified for this server group (`tuxTdomainOptions = migrate(2)` and `tuxTgroupLMID` with alternate site), then this attribute must be set to `yes(1)`.

> Note that servers sharing a request queue (that is, equal values for `tuxTsrvrRqAddr`) should have equal values for this attribute. If they do not, then the first server activated will establish the runtime value associated with all servers on the queue.

> Note: Runtime modifications to this attribute will affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this attribute.

### tuxTsrvrSequence

> #### Syntax

> `INTEGER (1..10000)`

> #### Access

> read-write

> #### Description

> Specifies when this server should be booted (`tmboot`(1)) or shutdown (`tmshutdown`(1)) relative to other servers. If two servers are given the same sequence number, it is possible for `tmboot`(1) to boot them in parallel and for `tmshutdown`(1) to shut them down in parallel. `tuxTsrvrTbl` instances added without a `tuxTsrvrSequence` attribute specified or with an invalid value will have one generated for them that is 10,000 or more and is higher than any other automatically selected default value. Servers are booted by `tmboot`(1) in increasing order of sequence number and shutdown by `tmshutdown`(1) in decreasing order. Runtime modifications to this attribute affect only `tmboot`(1) and `tmshutdown`(1) and will affect the order in which running servers may be shutdown by a subsequent invocation of `tmshutdown`(1).

### tuxTsrvrSystemAccess

> #### Syntax

> `INTEGER { fastpath(1), protected(2) }`

> #### Access

> read-write

> #### Description

> Mode used by System/T libraries within this server process to gain access to System/T's internal tables. See `tuxTdomainSystemAccess` for a complete discussion of this attribute.

> Note: Runtime modifications to this attribute will not affect a running server.

### tuxTsrvrConv

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Conversational server `yes(1)` or request/response server `no(2)`.

### tuxTsrvrReplyQ

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Allocate a separate reply queue for the server (`tuxTsrvrReplyQ == yes(1)`). MSSQ servers that expect to receive replies should set this attribute to `yes(1)`.

### tuxTsrvrRpPerm

> #### Syntax

> `DisplayString` (`SIZE(4)`)

> #### Access

> read-write

> #### Description

> UNIX system permissions for the server's reply queue. If a separate reply queue is not allocated (`tuxTsrvrReplyQ == no(2)`), then this attribute is ignored. This is a string representation of octal numbers starting with a leading 0 0001 through 0777.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrRqAddr

> #### Syntax

> `DisplayString` (`SIZE`(`0..30`))

> #### Access

> read-write

> #### Description

> Symbolic address of the request queue for the server. Specifying the same `tuxTsrvrRqAddr` attribute value for more than one server is the way multiple server, single queue (MSSQ) sets are defined. Servers with the same `tuxTsrvrRqAddr` attribute value must be in the same server group.

### tuxTsrvrRqPerm

> #### Syntax

> `DisplayString` `(SIZE(4))`

> #### Access

> read-write

> #### Description

> UNIX system permissions for the server's request queue. This is a string representation of octal numbers starting with a leading 0 0001 through 0777.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrGeneration

> #### Syntax

> `INTEGER (1..32768)`

> #### Access

> read-only

> #### Description

> Generation of the server. When a server is initially booted via `tmboot`(1) or activated through the SNMP agent, its generation is set to 1. Each time the server dies abnormally and is restarted, its generation is incremented. Note that when `tuxTsrvrMaxgen` is exceeded and `tuxTsrvrGrace` has expired, the server will be restarted with the generation reset to 1.

### tuxTsrvrPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system process identifier for the server. Note that this may not be a unique attribute since servers may be located on different machines allowing for duplication of process identifiers.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrRpid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system message queue identifier for the server's reply queue. If a separate reply queue is not allocated (`tuxTsrvrReplyQ == no(2)`), then this attribute value will be the same as `tuxTsrvrRqId`.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrRqId

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system message queue identifier for the server's request queue. If a separate reply queue is not allocated (`tuxTsrvrReplyQ == no(2)`), then this attribute value will be the same as `tuxTsrvrRpid`.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrTimeRestart

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on local host, when the server was last started or restarted.

### tuxTsrvrTimeStart

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the `time`(2) system call on local host, when the server was first started. Restarts of the server do not reset this value; however, if `tuxTsrvrMaxgen` is exceeded and `tuxTsrvrGrace` is expired, this attribute will be reset to the time of the restart.

## tuxTsrvrTblExt

An extension of the `tuxTsrvrTbl`. Objects in this table are only accessible through a TUXEDO SNMP agent installed on the local machine

Variable Name | Object ID
--- | ---
`tuxTsrvrIdExt` | .1.3.6.1.4.1.140.300.20.2.1.1
`tuxTsrvrGrpNoExt` | .1.3.6.1.4.1.140.300.20.2.1.2
`tuxTsrvrNumConv` | .1.3.6.1.4.1.140.300.20.2.1.3
`tuxTsrvrNumDeque` | .1.3.6.1.4.1.140.300.20.2.1.4
`tuxTsrvrNumEnque` | .1.3.6.1.4.1.140.300.20.2.1.5
`tuxTsrvrNumPost` | .1.3.6.1.4.1.140.300.20.2.1.6
`tuxTsrvrNumReq` | .1.3.6.1.4.1.140.300.20.2.1.7
`tuxTsrvrNumSubscribe` | .1.3.6.1.4.1.140.300.20.2.1.8
`tuxTsrvrNumTran` | .1.3.6.1.4.1.140.300.20.2.1.9
`tuxTsrvrTranAbt` | .1.3.6.1.4.1.140.300.20.2.1.10
`tuxTsrvrTranCmt` | .1.3.6.1.4.1.140.300.20.2.1.11
`tuxTsrvrTotReqC` | .1.3.6.1.4.1.140.300.20.2.1.12
`tuxTsrvrTotWorkL` | .1.3.6.1.4.1.140.300.20.2.1.13
`tuxTsrvrCltLmid` | .1.3.6.1.4.1.140.300.20.2.1.14
`tuxTsrvrCltPid` | .1.3.6.1.4.1.140.300.20.2.1.15
`tuxTsrvrCltReply` | .1.3.6.1.4.1.140.300.20.2.1.16
`tuxTsrvrCmtRet` | .1.3.6.1.4.1.140.300.20.2.1.17
`tuxTsrvrCurConv` | .1.3.6.1.4.1.140.300.20.2.1.18
`tuxTsrvrCurReq` | .1.3.6.1.4.1.140.300.20.2.1.19
`tuxTsrvrCurService` | .1.3.6.1.4.1.140.300.20.2.1.20
`tuxTsrvrCurTime` | .1.3.6.1.4.1.140.300.20.2.1.21
`tuxTsrvrLastGrp` | .1.3.6.1.4.1.140.300.20.2.1.22
`tuxTsrvrSvcTimeOut` | .1.3.6.1.4.1.140.300.20.2.1.23
`tuxTsrvrTimeLeft` | .1.3.6.1.4.1.140.300.20.2.1.24
`tuxTsrvrTranLev` | .1.3.6.1.4.1.140.300.20.2.1.25
`tuxTsrvrStateExt` | .1.3.6.1.4.1.140.300.20.2.1.26
`tuxTsrvrGrpExt` | .1.3.6.1.4.1.140.300.20.2.1.27
`m3SrvrCurObjsExt` | .1.3.6.1.4.1.140.300.20.2.1.32
`m3SrvrCurInterfaceExt` | .1.3.6.1.4.1.140.300.20.2.1.37

### tuxTsrvrIdExt

> #### Syntax

> `INTEGER (1..30001)`

> #### Access

> read-only

> #### Description

> Unique (within the server group) server identification number.

### tuxTsrvrGrpNoExt

> #### Syntax

> `INTEGER (1..30000)`

> #### Access

> read-only

> #### Description

> Group number associated with this server's group.

### tuxTsrvrNumConv

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of conversations initiated by this server via `tpconnect`(3).

### tuxTsrvrNumDeque

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of dequeue operations initiated by this server via `tpdequeue`(3).

### tuxTsrvrNumEnque

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of enqueue operations initiated by this server via `tpenqueue`(3).

### tuxTsrvrNumPost

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of postings initiated by this server via `tppost`(3).

### tuxTsrvrNumReq

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of requests made by this server via `tpcall`(3) or `tpacall`(3).

### tuxTsrvrNumSubscribe

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of subscriptions made by this server via `tpsubscribe`(3).

### tuxTsrvrNumTran

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions begun by this server since its last (re)start.

### tuxTsrvrTranAbt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions aborted by this server since its last (re)start.

### tuxTsrvrTranCmt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of transactions committed by this server since its last (re)start.

### tuxTsrvrTotReqC

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Total number of requests completed by this server. For conversational servers (`tuxTsrvrConv == yes(1)`), this attribute value indicates the number of completed incoming conversations. This is a runtime attribute that is kept across server restart but is lost at server shutdown.

### tuxTsrvrTotWorkL

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Total workload completed by this server. For conversational servers (`tuxTsrvrConv == yes(1)`), this attribute value indicates the workload of completed incoming conversations. This is a runtime attribute that is kept across server restart but is lost at server shutdown.

### tuxTsrvrCltLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine for the initiating client or server. The initiating client or server is the process that made the service request that the server is currently working on.

### tuxTsrvrCltPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> UNIX system process identifier for the initiating client or server.

> Note: This is a UNIX system specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.

### tuxTsrvrCltReply

> #### Syntax

> `INTEGER { yes(1), no(2), null(3) }`

> #### Access

> read-only

> #### Description

> The initiating client or server is expecting a reply `yes(1)` or is not expecting a reply `no(2)`.

### tuxTsrvrCmtRet

> #### Syntax

> `INTEGER { complete(1), logged(2) }`

> #### Access

> read-only

> #### Description

> Setting of the TP_COMMIT_CONTROL characteristic for this server. See the description of the System/T ATMI function `tpscmt`(3) for details on this characteristic.

### tuxTsrvrCurConv

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of conversations initiated by this server via `tpconnect`(3) that are still active.

### tuxTsrvrCurReq

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of requests initiated by this server via `tpcall`(3) or `tpacall`(3) that are still active.

### tuxTsrvrCurService

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-only

> #### Description

> Service name that the server is currently working on, if any.

### tuxTsrvrCurTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as on the local host. This attribute can be used to compute elapsed time from the `tuxTsrvrTimeStart` and `tuxTsrvrTimeRestart` object values.

### tuxTsrvrLastGrp

> #### Syntax

> `INTEGER (1..30000)`

> #### Access

> read-only

> #### Description

> Server group number (`tuxTgroupNo`) of the last service request made or conversation initiated from this server outward.

### tuxTsrvrSvcTimeOut

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time left, in seconds, for this server to process the current service request, if any. A value of 0 for an active service indicates that no timeout processing is being done. See `tuxTsvcTimeOut` for more information.

### tuxTsrvrTimeLeft

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time left, in seconds, for this server to receive the reply for which it is currently waiting before it will timeout. This timeout may be a transactional timeout or a blocking timeout.

### tuxTsrvrTranLev

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Current transaction level for this server. 0 indicates that the server is not currently involved in a transaction.

### tuxTsrvrStateExt

> #### Syntax

> `INTEGER { active(1), inactive(2), migrating(3), cleaning(4), restarting(5), suspended(6), partitioned(7), dead(8) }`

> #### Access

> read-only

> #### Description

> Refer to description of `tuxTsrvrState` for details.

### tuxTsrvrGrpExt

> #### Syntax

> `DisplayString`

> #### Access

> read-only

> #### Description

> Name of group to which this server belongs. This object is included for readability purposes only.

### m3SrvrCurObjsExt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of entries in use in the bulletin board object table for this server.

### m3SrvrCurInterfaceExt

> #### Syntax

> `DisplayString (SIZE(1..128))`

> #### Access

> read-only

> #### Description

> The interface name of the interface currently active in this server.

## tuxTsvcTbl

This represents configuration attributes of services within an application. These attribute values identify and characterize configured services. A `tuxTsvcTbl` object provides activation time configuration attributes for services not specifically configured as part of the `tuxTsvcGrp` group. The index into this table is `tuxTsvcName`. Objects in this group are only accessible through a TUXEDO SNMP agent installed on the local machine. To create a new row in the table, it is necessary to issue a SET request for a non-existing row in the table.

Variable Name | Object ID
--- | ---
`tuxTsvcName` | .1.3.6.1.4.1.140.300.10.1.1.1
`tuxTsvcType` | .1.3.6.1.4.1.140.300.10.1.1.2
`tuxTsvcState` | .1.3.6.1.4.1.140.300.10.1.1.3
`tuxTsvcAutoTran` | .1.3.6.1.4.1.140.300.10.1.1.4
`tuxTsvcLoad` | .1.3.6.1.4.1.140.300.10.1.1.5
`tuxTsvcPrio` | .1.3.6.1.4.1.140.300.10.1.1.6
`tuxTsvcTimeOut` | .1.3.6.1.4.1.140.300.10.1.1.7
`tuxTsvcTranTime` | .1.3.6.1.4.1.140.300.10.1.1.8
`tuxTsvcBufType` | .1.3.6.1.4.1.140.300.10.1.1.9
`tuxTsvcRoutingName` | .1.3.6.1.4.1.140.300.10.1.1.10

### tuxTsvcName

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-write

> #### Description

> Service name.

> Note: This object can be set only during row creation.

### tuxTsvcType

> #### Syntax

> `INTEGER { app(1), callable(2), system(3), unknown(4) }`

> #### Access

> read-only

> #### Description

> Type of service. app(1) indicates an application defined service name. callable(2) indicates a system provided callable service. system(3) indicates a system provided and system callable service. system(3) services are not available to application clients and servers for direct access.

### tuxTsvcState

> #### Syntax

> `INTEGER { active(1), inactive(2), invalid(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|inactive(2)}`
>   A `GET` operation will retrieve configuration information for the selected `tuxTsvcTbl` instance(s). The following states indicate the meaning of a `tuxTsvcState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTsvcTbl` instance is defined and at least one `tuxTsvcGrp` object with a matching `tuxTsvcName` value is active.

> `inactive(2)`
>   `tuxTsvcTbl` instance is defined and no `tuxTsvcGrp` object with a matching `tuxTsvcName` value is active.

> `SET: invalid(3)`
>   A `SET` operation will update configuration information for the selected `tuxTsvcTbl` instance. The following states indicate the meaning of a `tuxTsvcState` set in a `SET` request. States not listed may not be set.

> `invalid(3)`
>   Delete `tuxTsvcTbl` instance for application. State change allowed only when in the `inactive(2)` state. Successful return leaves the object in the `invalid(3)` state.

### tuxTsvcAutoTran

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Automatically begin a transaction (`yes(1)`) when a service request message is received for this service if the request is not already in transaction mode.

> Note: Runtime updates to this attribute are not reflected in active `tuxTsvcGrp` objects.

### tuxTsvcLoad

> #### Syntax

> `INTEGER (1..32768)`

> #### Access

> read-write

> #### Description

> This `tuxTsvcTbl` object imposes the indicated load on the system. Service loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request. Service loads have meaning only if the `tuxTdomainLoadBalance` is set to `yes(1)`.

> Note: Runtime updates to this attribute are not reflected in active `tuxTsvcGrp` objects.

### tuxTsvcPrio

> #### Syntax

> `INTEGER (1..100)`

> #### Access

> read-write

> #### Description

> This `tuxTsvcTbl` object has the indicated dequeuing priority. If multiple service requests are waiting on a queue for servicing, the higher priority requests will be serviced first.

> Note: Runtime updates to this attribute are not reflected in active `tuxTsvcGrp` objects.

### tuxTsvcTimeOut

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Time limit (in seconds) for processing requests for this service name. Servers processing service requests for this service will be abortively terminated (`kill -9`) if they exceed the specified time limit in processing the request. A value of 0 for this attribute indicates that the service should not be abortively terminated.

> Note: Runtime updates to this attribute are not reflected in active `tuxTsvcGrp` objects.

> Note: This attribute value is not enforced on TUXEDO System/T Release 4.2.2 sites or earlier.

### tuxTsvcTranTime

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Transaction timeout value in seconds for transactions automatically started for this `tuxTsvcTbl` object. Transactions are started automatically when a request not in transaction mode is received and the `tuxTsvcAutoTran` attribute value for the service is `yes(1)`.

> Note: Runtime updates to this attribute are not reflected in active `tuxTsvcGrp` objects.

### tuxTsvcBufType

> #### Syntax

> `DisplayString` (`SIZE`(`1..256`))

> #### Access

> read-write

> #### Description

> `type1[:subtype1[,subtype2 . . . ]][;type2[:subtype3[,. . . ]]] . . .`

> List of types and subtypes of data buffers accepted by this service. A maximum of 32 type/subtype combinations are allowed. Types of data buffers provided with TUXEDO System/T are FML (for FML buffers), VIEW, X_C_TYPE, or X_COMMON (for FMLviews), STRING (for NULL terminated character arrays), and CARRAY or X_OCTET (for a character array that is neither encoded nor decoded during transmission). Of these types, only VIEW, X_C_TYPE, and X_COMMON have subtypes. A VIEW subtype gives the name of the particular VIEW expected by the service. Application types and subtypes can also be added (see `tuxtypes`(5)). For a buffer type that has subtypes, "*" can be specified for the subtype to indicate that the service accepts all subtypes for the associated buffer type.

> A single service can only interpret a fixed number of buffer types, namely those found in its buffer type switch (see `tuxtypes`(5)). If the `tuxTsvcBufType` value is set to ALL, that service will accept all buffer types found in its buffer type switch.

> A type name can be 8 characters or less in length and a subtype name can be 16 characters or less in length. Note that type and subtype names should not contain semicolon, colon, comma, or asterisk characters.

> Note: This attribute value represents the buffer types that must be supported by each and every instance of an application service with this service name. Since this attribute value is processed at service activation time, updates to this attribute are allowed only when there are no active `tuxTsvcGrp` objects with matching service names.

### tuxTsvcRoutingName

> #### Syntax

> `DisplayString` (`SIZE`(`0..15`))

> #### Access

> read-write

> #### Description

> This `tuxTsvcTbl` object has the indicated routing criteria name. Active updates to this attribute will be reflected in all associated `tuxTsvcGrp` objects.

## tuxTsvcGrp

The `tuxTsvcGrp` group represents configuration and runtime attributes of services/groups within an application. These attribute values identify and characterize configured services/groups as well as provide runtime tracking of statistics and resources associated with each object.

Both `tuxTsvcTbl` and `tuxTsvcGrp` define activation time attribute settings for service names within the application. When a new service is activated (advertised), either due to initial activation of a server or due to a call to `tpadvertise`(3), the following hierarchy exists for determining the attribute values to be used at service startup time.

1. If a matching configured `tuxTsvcGrp` entry exists (matching service name and server group), then the attributes defined in that object are used to initially configure the advertised service.

2. Otherwise, if a matching configured `tuxTsvcTbl` entry exists (matching service name), then the attributes defined in that object are used to initially configure the advertised service.

3. Otherwise, if any configured `tuxTsvcGrp` entries are found with matching service name value, then the first one found is used to initially configure the advertised service.

4. If none of the preceding cases is used, then the system defaults for service attributes are used to initially configure the advertised service.

Objects in this group are only accessible through a TUXEDO SNMP agent installed on the local machine.

To create a new row in the table, it is necessary to issue a `SET` request that specifies at least `tuxTsvcGrpName`. The combination of values specified for `tuxTsvcGrpName` and `tuxTsvcGrpSvcName` in the `SET` request should not correspond to an existing row. If the value of `tuxTsvcSrvrId` is zero in the `SET` request, the service entry is configured but not activated (advertised). If `tuxTsvcSrvrId` is not set to zero, the service is activated using the value of `tuxTsvcSrvrId` to identify the server instance.

Variable Name | Object ID
--- | ---
`tuxTsvcGrpSvcName` | .1.3.6.1.4.1.140.300.10.2.1.1
`tuxTsvcGrpName` | .1.3.6.1.4.1.140.300.10.2.1.2
`tuxTsvcGrpNo` | .1.3.6.1.4.1.140.300.10.2.1.3
`tuxTsvcGrpState` | .1.3.6.1.4.1.140.300.10.2.1.4
`tuxTsvcGrpAutoTran` | .1.3.6.1.4.1.140.300.10.2.1.5
`tuxTsvcGrpLoad` | .1.3.6.1.4.1.140.300.10.2.1.6
`tuxTsvcGrpPrio` | .1.3.6.1.4.1.140.300.10.2.1.7
`tuxTsvcGrpSvcTimeOut` | .1.3.6.1.4.1.140.300.10.2.1.8
`tuxTsvcGrpTranTime` | .1.3.6.1.4.1.140.300.10.2.1.9
`tuxTsvcSrvrLmid` | .1.3.6.1.4.1.140.300.10.2.1.10
`tuxTsvcSrvrRqAddr` | .1.3.6.1.4.1.140.300.10.2.1.11
`tuxTsvcSrvrId` | .1.3.6.1.4.1.140.300.10.2.1.12
`tuxTsvcrName` | .1.3.6.1.4.1.140.300.10.2.1.13
`tuxTsvcSrvrNcompleted` | .1.3.6.1.4.1.140.300.10.2.1.14
`tuxTsvcSrvrNqueued` | .1.3.6.1.4.1.140.300.10.2.1.15

### tuxTsvcGrpSvcName

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-only

> #### Description

> Service name.

### tuxTsvcGrpName

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Server group name. Server group names cannot contain an asterisk.

### tuxTsvcGrpNo

> #### Syntax

> `INTEGER (1..29999)`

> #### Access

> read-write

> #### Description

> Server group number.

### tuxTsvcGrpState

> #### Syntax

> `INTEGER { active(1), inactive(2), invalid(3) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)|inactive(2)`
>   A `GET` operation will retrieve configuration information for the selected `tuxTsvcGrpState` instance(s). The following states indicate the meaning of a `tuxTsvcGrpState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   At least one instance is active, suspended, or partitioned.

> `inactive(2)`
>   `tuxTsvcGrp` instance defined and inactive.

> `SET: invalid(3)`
>   It removes the corresponding `tuxTsvcGrp` instance. When a `tuxTsvcGrp` instance is deleted it will also remove the associated `tuxTsvcSrvr` instances which correspond to server instances which are a part of this group advertising this service. This transition is permissible only in `inactive(2)` state.

### tuxTsvcGrpAutoTran

> #### Syntax

> `INTEGER { yes(1), no(2) }`

> #### Access

> read-write

> #### Description

> Automatically begin a transaction (`yes(1)`) when a service request message is received for this service if the request is not already in transaction mode.

### tuxTsvcGrpLoad

> #### Syntax

> `INTEGER (1..32767)`

> #### Access

> read-write

> #### Description

> This `tuxTsvcGrp` instance imposes the indicated load on the system. Service loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request.

### tuxTsvcGrpPrio

> #### Syntax

> `INTEGER (1..100)`

> #### Access

> read-write

> #### Description

> This `tuxTsvcGrp` object has the indicated dequeuing priority. If multiple service requests are waiting on a queue for servicing, the higher priority requests will be serviced first.

### tuxTsvcGrpSvcTimeOut

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Time limit (in seconds) for processing requests for this service name. Servers processing service requests for this service will be abortively terminated (`kill -9`) if they exceed the specified time limit in processing the request. A value of 0 for this attribute indicates that the service should not be abortively terminated.

### tuxTsvcGrpTranTime

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Transaction timeout value in seconds for transactions automatically started for this `tuxTsvcGrp` instance. Transactions are started automatically when a request not in transaction mode is received and the `tuxTsvcGrpAutoTran` attribute value for the service is `yes(1)`.

### tuxTsvcSrvrLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Current logical machine on which an active server offering this service is running.

### tuxTsvcSrvrRqAddr

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Symbolic address of the request queue for an active server offering this service. See `tuxTsrvrRqAddr` for more information on this attribute.

### tuxTsvcSrvrId

> #### Syntax

> `INTEGER (1..30000)`

> #### Access

> read-write

> #### Description

> Server ID of which the service is a part of. The user can also set the value of this object to activate (advertise) one or more `tuxTsvcGrp` instances. The value provided to set this object is used to activate another instance of `tuxTsvcGrp`.

### tuxTsvcrName

> #### Syntax

> `DisplayString` (`SIZE`(`1..15`))

> #### Access

> read-write

> #### Description

> Function name within the associated server assigned to process requests for this service. When this object is specified, the `tuxTsvcGrp` instance is activated (advertised). The user needs to specify the server ID of the corresponding server instance (`tuxTsvcSrvrId`) in the SNMP index. This object can be updated only during row creation.

### tuxTsvcSrvrNcompleted

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of service requests completed with respect to the retrieved active or suspended instance since it was activated (advertised).

> Note: This attribute is returned only when `tuxTdomainLoadBalance` is equal to `yes(1)`.

### tuxTsvcSrvrNqueued

> #### Syntax

> `INTEGER (0..32767)`

> #### Access

> read-only

> #### Description

> Number of requests currently enqueued to this service. This attribute is incremented at enqueue time and decremented when the server dequeues the request.

> Note: This attribute is returned only when the `tuxTdomainModel` is set to `single-machine(1)` and the `tuxTdomainLoadBalance` attribute is set to `yes(1)`.

## tuxTlistenTbl

This group represents runtime attributes of /T listener processes for a distributed application.

Variable Name | Object ID
--- | ---
`tuxTlistenLmid` | .1.3.6.1.4.1.140.300.21.1.1.1
`tuxTlistenState` | .1.3.6.1.4.1.140.300.21.1.1.2

### tuxTlistenLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine identifier.

### tuxTlistenState

> #### Syntax

> `INTEGER { inactive(2), active(1) }`

> #### Access

> read-only

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: {active(1)|inactive(2)}`
>   A `GET` operation will retrieve runtime information for the selected `tuxTlistenTbl` instance(s). The following states indicate the meaning of a `tuxTlistenState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   `tuxTlistenTbl` instance active.

> `inactive(2)`
>   `tuxTlistenTbl` instance not active.

## tuxTranTbl

This table represents runtime attributes of active transactions within the application. The following objects comprise the index for rows in this table: `tuxTranIndx1`, `tuxTranIndx2`, `tuxTranIndx3`, `tuxTranIndx4`, `tuxTranIndx5`. Objects in this table are accessible only through a TUXEDO SNMP agent running on the local machine.

Variable Name | Object ID
--- | ---
`tuxTranCoordLmid` | .1.3.6.1.4.1.140.300.23.1.1.1
`tuxTpTranId` | .1.3.6.1.4.1.140.300.23.1.1.2
`tuxTranXid` | .1.3.6.1.4.1.140.300.23.1.1.3
`tuxTranIndx1` | .1.3.6.1.4.1.140.300.23.1.1.4
`tuxTranIndx2` | .1.3.6.1.4.1.140.300.23.1.1.5
`tuxTranIndx3` | .1.3.6.1.4.1.140.300.23.1.1.6
`tuxTranIndx4` | .1.3.6.1.4.1.140.300.23.1.1.7
`tuxTranIndx5` | .1.3.6.1.4.1.140.300.23.1.1.8
`tuxTranState` | .1.3.6.1.4.1.140.300.23.1.1.9
`tuxTranTimeOut` | .1.3.6.1.4.1.140.300.23.1.1.10
`tuxTranGrpCnt` | .1.3.6.1.4.1.140.300.23.1.1.11
`tuxTranGrpIndex` | .1.3.6.1.4.1.140.300.23.1.1.12
`tuxTranGrpNo` | .1.3.6.1.4.1.140.300.23.1.1.13
`tuxTranGstate` | .1.3.6.1.4.1.140.300.23.1.1.14

### tuxTranCoordLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Logical machine identifier of the server group responsible for coordinating the transaction.

### tuxTpTranId

> #### Syntax

> `DisplayString` (`SIZE`(`2..78`))

> #### Access

> read-only

> #### Description

> Transaction identifier as returned from `tpsuspend`(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

### tuxTranXid

> #### Syntax

> `DisplayString` (`SIZE`(`2..78`))

> #### Access

> read-only

> #### Description

> Transaction identifier as returned from `tx_info`(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.

### tuxTranIndx1

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This number is purely for unique indexing of this table.

### tuxTranIndx2

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This number is purely for unique indexing of this table.

### tuxTranIndx3

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This number is purely for unique indexing of this table.

### tuxTranIndx4

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This number is purely for unique indexing of this table.

### tuxTranIndx5

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This number is purely for unique indexing of this table.

### tuxTranState

> #### Syntax

> `INTEGER { active(1), abort-only(2), aborted(3), com-called(4), ready(5), decided(6), suspended(7) }`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)|abort-only(2)|aborted(3)|com-called(4)|ready(5)|
> decided(6)|suspended(7)`
>   A`GET` operation will retrieve runtime information for the selected `tuxTranTbl` instance(s). The following states indicate the meaning of a `tuxTranState` object. States not listed will not be returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) may indicate differing states. In general, the state indicated on the coordinator's site (`tuxTranCoordLmid`) indicates the true state of the transaction. The exception is when a noncoordinator site notices a condition that transitions the transaction state to `abort-only(2)`. This transition will eventually be propagated to the coordinator site and result in the rollback of the transaction, but this change may not be immediately reflected on the coordinator site.

> `active(1)`
>   The transaction is active.

> `abort-only(2)`
>   The transaction has been identified for rollback on the retrieval site.

> `aborted(3)`
>   The transaction has been identified for rollback and rollback has been initiated on the retrieval site.

> `com-called(4)`
>   The initiator of the transaction has called `tpcommit`(3) and the first phase of two-phase commit has begun on the retrieval site.

> `ready(5)`
>   All of the participating groups on the retrieval site have successfully completed the first phase of two-phase commit and are ready to be committed.

> `decided(6)`
>   The second phase of the two-phase commit has begun on the retrieval site.

> `suspended(7)`
>   The initiator of the transaction has suspended processing on the transaction. Note that this state will be returned from the initiator's site only.

> `SET: aborted(3)`
>   A `SET` operation will update runtime information for the selected `tuxTranTbl` instance. The following state indicates the meaning of a `tuxTranState` set in a `SET` request. States not listed may not be set.

> `aborted(3)`
>   Abort the `tuxTranTbl` instance for the application. State change allowed only when in the `active(1)`, `abort-only(2)`, or `com-called(4)` states. May not be accompanied by a change to `tuxTranGstate`. Successful return leaves the object in the `aborted(3)` state.

### tuxTranTimeOut

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time left, in seconds, before the transaction will timeout on the retrieval site. Note that this attribute value is returned only when the transaction state is `active(1)`.

### tuxTranGrpCnt

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Number of groups identified as participants in the transaction by the information returned from the retrieval site.

### tuxTranGrpIndex

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Index of the first group specific attribute values (`tuxTranGrpNo` and `tuxTranGstate`) corresponding to this object.

### tuxTranGrpNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Group number of the participating group.

### tuxTranGstate

> #### Syntax

> `INTEGER { active(1), aborted(2), rd-only(3), ready(4), hcommit(5), habort(6), done(7), pre-prepare(8), post-abort(9), post-commit(10), unknown(11) )`

> #### Access

> read-write

> #### Description

> The values for `GET` and `SET` operations are as follows:

> `GET: active(1)|aborted(2)|rd-only(3)|ready(4)|hcommit(5)|habort(6)
> |done(7)`
>   A `GET` operation will retrieve runtime information for the selected `tuxTranTbl` instance(s) pertaining to the indicated group. The following states indicate the meaning of a `tuxTranGstate` returned in response to a `GET` request. States not listed will not be returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) may indicate differing states for individual groups. In general, the state indicated on the group's site indicates the true state of the group's participation in the transaction. The exception is when the coordinator site determines that the transaction should abort and sets each participant group state to `aborted(2)`. This transition will be propagated to the group's site and result in the rollback of the group's work in the transaction but may not be reflected immediately

> `active(1)`
>   The transaction is active in the indicated group.

> `aborted(2)`
>   The transaction has been identified for rollback and rollback has been initiated for the indicated group.

> `rd-only(3)`
>   The group has successfully completed the first phase of two-phase commit and has performed only read operations on the resource manager, thus making it unnecessary to perform the second phase of commit for this group.

> `ready(4)`
>   The group has successfully completed the first phase of two-phase commit and is ready to be committed.

> `hcommit(5)`
>   The group has been heuristically committed. This may or may not agree with the final resolution of the transaction.

> `habort(6)`
>   The group has been heuristically rolled back. This may or may not agree with the final resolution of the transaction.

> `done(7)`
>   This group has completed the second phase of the two-phase commit.

> `pre-prepare(8)`
>   Indicates that the transaction group contains M3 servers that have called `xa_end` (TMSUSPEND) during the course of transactional work and that commit processing is beginning. This state will exist until either (1) All servers that called `xa_end` (TMSUSPEND) have caused a call to `xa_end` (TMSUCCESS), at which point the group state will be become ready, or (2) One of the target servers does a rollback of the transaction at which point the group state will become either `post-abort(9)` or `aborted(2)`.

> Note: This state is supported for M3 applications only.

> `post-abort(9)`
>   Indicates that an M3 server called `xa_end` (TPFAIL) and that the TMS has not yet called `xa_rollback()`. In this case, other M3 servers that called `xa_end` (TMSUSPEND) are being notified by the TMS in order to clean up their associated CORBA objects.
>   Note: This state is supported for M3 applications only.

> `post-commit(10)`
>   This state is not implemented yet.

> Note: This state is supported for M3 applications only.

> `SET: hcommit(5)|habort(6)`
>   A `SET` operation will update runtime information for the first group in the originating request within the selected `tuxTranTbl` instance. The following states indicate the meaning of a `tuxTranGstate` set in a `SET` request. States not listed may not be set. State transitions are allowed only when performed within the object representing the group's site.

> `hcommit(5)`
>   Heuristically commit the group's work as part of the indicated transaction. State change allowed only when `tuxTranGstate` is ready, `tuxTranState` is ready, and the indicated group is not on the coordinator's site. Successful return leaves the object in the `hcommit(5)` state.

> `habort(6)`
>   Heuristically rollback the group's work as part of the indicated transaction. State change allowed only when `tuxTranGstate` is `active(1)` or `ready(4)`, `tuxTranState` is `ready(4)`, and the indicated group is not on the coordinator's site. Successful return leaves the object in the `habort(6)` state.

## tuxTulogTable

The `tuxTulogTable` group represents runtime attributes of userlog files within an application. The index into this table is `tuxTulogSerNo`. The values returned for objects in this table are controlled by the MIB control group `tuxTulogCtrl`.

Variable Name | Object ID
--- | ---
`tuxTulogSerNo` | .1.3.6.1.4.1.140.300.9.1.1.1
`tuxTulogLmid` | .1.3.6.1.4.1.140.300.9.1.1.2
`tuxTulogPmid` | .1.3.6.1.4.1.140.300.9.1.1.3
`tuxTulogMmDdYy` | .1.3.6.1.4.1.140.300.9.1.1.4
`tuxTulogTime` | .1.3.6.1.4.1.140.300.9.1.1.5
`tuxTulogLine` | .1.3.6.1.4.1.140.300.9.1.1.6
`tuxTulogMsg` | .1.3.6.1.4.1.140.300.9.1.1.7
`tuxTulogTpTranId` | .1.3.6.1.4.1.140.300.9.1.1.8
`tuxTulogXid` | .1.3.6.1.4.1.140.300.9.1.1.9
`tuxTulogPid` | .1.3.6.1.4.1.140.300.9.1.1.10
`tuxTulogSeverity` | .1.3.6.1.4.1.140.300.9.1.1.11
`tuxTulogCat` | .1.3.6.1.4.1.140.300.9.1.1.12
`tuxTulogMsgNum` | .1.3.6.1.4.1.140.300.9.1.1.13
`tuxTulogProcName` | .1.3.6.1.4.1.140.300.9.1.1.14

### tuxTulogSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> A running serial number for the rows in `tuxTulogTable`.

### tuxTulogLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Retrieval machine logical machine identifier.

### tuxTulogPmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Physical machine identifier.

### tuxTulogMmDdYy

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Month, day, and year of the log file.

### tuxTulogTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Time at which the message was generated.

### tuxTulogLine

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Line number of the message in the log file.

### tuxTulogMsg

> #### Syntax

> `DisplayString` (`SIZE`(`1..256`))

> #### Access

> read-only

> #### Description

> The entire text of the userlog message as it appears in the userlog file.

### tuxTulogTpTranId

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> Transaction identifier as returned from `tpsuspend`(3). The data in this field should not be interpreted directly by the user except for equality comparison. Messages not associated with transactions will retrieve a 0-length string as the value for this attribute.

### tuxTulogXid

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-only

> #### Description

> Transaction identifier as returned from `tx_info`(3). The data in this field should not be interpreted directly by the user except for equality comparison. Messages not associated with transactions will retrieve a 0-length string as the value for this attribute.

### tuxTulogPid

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Process identifier of the client or server that generated the userlog message.

### tuxTulogSeverity

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Severity of message, if any.

### tuxTulogCat

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Catalog name from which the message was derived, if any.

### tuxTulogMsgNum

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> Catalog message number, if the message was derived from a catalog.

### tuxTulogProcName

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-only

> #### Description

> Process name of the client or server that generated the userlog message.

## tuxTulogCtrl

The values of objects in this group control the ulog messages returned by the `tuxTulogTable`.

Variable Name | Object ID
--- | ---
`tuxTulogLmidCtrl` | .1.3.6.1.4.1.140.300.9.2.1
`tuxTulogPmidCtrl` | .1.3.6.1.4.1.140.300.9.2.2
`tuxTulogMmddyyCtrl` | .1.3.6.1.4.1.140.300.9.2.3
`tuxTulogTimeCtrl` | .1.3.6.1.4.1.140.300.9.2.4
`tuxTulogEndTimeCtrl` | .1.3.6.1.4.1.140.300.9.2.5
`tuxTulogLineCtrl` | .1.3.6.1.4.1.140.300.9.2.6
`tuxTulogMsgCtrl` | .1.3.6.1.4.1.140.300.9.2.7
`tuxTulogTptranIdCtrl` | .1.3.6.1.4.1.140.300.9.2.8
`tuxTulogXidCtrl` | .1.3.6.1.4.1.140.300.9.2.9
`tuxTulogPidCtrl` | .1.3.6.1.4.1.140.300.9.2.10
`tuxTulogSeverityCtrl` | .1.3.6.1.4.1.140.300.9.2.11
`tuxTulogCatCtrl` | .1.3.6.1.4.1.140.300.9.2.12
`tuxTulogMsgNumCtrl` | .1.3.6.1.4.1.140.300.9.2.13
`tuxTulogProcNameCtrl` | .1.3.6.1.4.1.140.300.9.2.14

### tuxTulogLmidCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Logical machine ID to qualify machine from where the userlog file is read for `tuxTulogTable`. By default, the ULOG files from the local host are returned, per the ULOGPFX. To revert to the default setting, set this object to `null`.

### tuxTulogPmidCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Physical machine name to qualify the source machine for userlog messages to be listed in `tuxTulogTable`. By default, messages from all hosts within ULOG files qualified by `tuxTulogLmidCtrl` are returned. To revert to the default setting, set this object to `null`.

### tuxTulogMmddyyCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Date value to qualify userlog messages to be listed in `tuxTulogTable`. Default value is current date. To reset the value of the qualifier to its default, set this object to `0`.

### tuxTulogTimeCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Starting time for the time range for which the userlog messages are to be listed in `tuxTulogTable`. This number is calculated as under - "hrs*10000 + mins*100 + secs". The default value is `0`.

### tuxTulogEndTimeCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Ending time for the time range for which the userlog messages are to be listed in `tuxTulogTable`. This number is calculated as under - "hrs*10000 + mins*100 + secs". By default, the maximum value is considered. To revert to the default setting, set this object to `0`.

### tuxTulogLineCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Beginning line number from which the userlog messages are to be listed in `tuxTulogTable`. By default, all messages are returned. To revert to the default setting, set this object to `0`.

### tuxTulogMsgCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Regular expression to qualify userlog messages to be listed in `tuxTulogTable` on the basis of the message body. By default, all messages are listed. To revert to the default setting, set this object to `null`.

### tuxTulogTptranIdCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..78`))

> #### Access

> read-write

> #### Description

> Value of `tuxTpTranId` to qualify messages to be displayed in the in `tuxTulogTable`. By default, all messages are returned. To revert to the default setting, set it to `null`.

### tuxTulogXidCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Value of `tuxTranXid` to qualify messages to be displayed in the in `tuxTulogTable`. By default, all messages are returned. To revert to the default setting, set it to `null`.

### tuxTulogPidCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Value of process Id of the source to qualify messages to be displayed in the `tuxTulogTable`. By default, messages with any pid are listed. To revert to the default setting, set this object to `0`.

### tuxTulogSeverityCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Regular expression to qualify userlog messages to be listed in `tuxTulogTable` on the basis of message severity, if any. By default, messages with any severity are listed. To revert to the default setting, set this object to `null`.

### tuxTulogCatCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Regular expression to qualify userlog messages to be listed in `tuxTulogTable` on the basis of the catalog name, if any. By default, messages from all catalogs are listed. To revert to the default setting, set this object to `null`.

### tuxTulogMsgNumCtrl

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Message number in catalog to qualify userlog messages to be listed in `tuxTulogTable`. By default, all message numbers are returned. To revert to the default setting, set this object to `0`.

### tuxTulogProcNameCtrl

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Regular expression to qualify userlog messages to be listed in `tuxTulogTable` on the basis of the process name that generated the message, if known. By default, all messages are returned. To revert to the default setting, set this object to `null`.

## tuxTnetGrpTbl

This table represents application attributes of network groups. Network groups are groups of logical machine IDs that can communicate over the network address defined in the `tuxTnetMapNaddr` object in the `tuxTnetMapTbl` table entry. For row creation, a `SET` request with `tuxTnetGrpName`, `tuxTnetGrpNo` and `tuxTnetGrpPrio` is required. `tuxTnetGrpNo` provides the index into this table.

Note: This table is supported only on TUXEDO 6.4 or later.

Variable Name | Object ID
--- | ---
`tuxTnetGrpName` | .1.3.6.1.4.1.140.300.28.1.1
`tuxTnetGrpNo` | .1.3.6.1.4.1.140.300.28.1.2
`tuxTnetGrpState` | .1.3.6.1.4.1.140.300.28.1.3
`tuxTnetGrpPrio` | .1.3.6.1.4.1.140.300.28.1.4

### tuxTnetGrpName

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Logical name of the network group. A group name is a string of printable characters and cannot contain a pound sign (#), comma (,), colon (:), or newline character. This object can be updated only during row creation.

### tuxTnetGrpNo

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> Group identifier of the network group. This object can be updated only during row creation.

### tuxTnetGrpState

> #### Syntax

> `INTEGER { valid(1), invalid(2) }`

> #### Access

> read-write

> #### Description

> A `GET` request retrieves configuration information for the selected `tuxTnetGrpTbl` instance (or instances). The following states indicate the meaning of the value that is returned:

> `GET: valid(1)`
>   The instance is defined. This is the only valid state for this object.

> `SET: invalid(2)`
>   Delete the selected `tuxTnetGrpTbl` instance from the application.

> States not listed are not returned.

### tuxTnetGrpPrio

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> The priority band for this network group. All network groups that have an equivalent band priority are used in parallel.

## tuxTnetMapTbl

The instances in the `tuxTnetMapTbl` associate `tuxTmachineLmid`s to an instance in the `tuxTnetGrpTbl`. The rows in this table identify which logical machines belong to which network groups. For row creation, a `SET` request with at least `tuxTnetMapNaddr` is needed. The index into this table is provided by `tuxTnetMapGrpNo` and `tuxTnetMapLmid`.

Note: This table is supported only on TUXEDO 6.4 or later.

Variable Name | Object ID
--- | ---
`tuxTnetMapGrpName` | .1.3.6.1.4.1.140.300.33.1.1
`tuxTnetMapGrpNo` | .1.3.6.1.4.1.140.300.33.1.2
`tuxTnetMapLmid` | .1.3.6.1.4.1.140.300.33.1.3
`tuxTnetMapState` | .1.3.6.1.4.1.140.300.33.1.4
`tuxTnetMapNaddr` | .1.3.6.1.4.1.140.300.33.1.5
`tuxTnetMapMinEncryptBit` | .1.3.6.1.4.1.140.300.33.1.6
`tuxTnetMapMaxEncryptBit` | .1.3.6.1.4.1.140.300.33.1.7

### tuxTnetMapGrpName

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> The logical name of the network group. A group name is a string of printable characters and cannot contain a pound sign (#), comma (,), colon (:), or a newline character.

### tuxTnetMapGrpNo

> #### Syntax

> `INTEGER (1..8191)`

> #### Access

> read-write

> #### Description

> Identifier for this logical network group. This object can be updated only during row creation.

### tuxTnetMapLmid

> #### Syntax

> `DisplayString` (`SIZE`(`1..30`))

> #### Access

> read-write

> #### Description

> Logical machine name for this network mapping. This object can be updated only during row creation.

### tuxTnetMapState

> #### Syntax

> `Integer { valid(1), invalid(2) }`

> #### Access

> read-write

> #### Description

> A `GET` request retrieves configuration information for the selected `tuxTnetMapTbl` instance (or instances). The following states indicate the meaning of the value of `tuxTnetMapState` that is returned:

> `GET: valid(1)`
>   The instance is defined. This is the only valid state for this object.

> `SET: invalid(2)`
>   Delete the selected `tuxTnetMapTbl` instance from the application. If any network links were active as a result of the mapping, they will be disconnected. This disconnection may cause a state change in `tuxTBridgeTbl` instances associated with the network links.

> States not listed are not returned.

### tuxTnetMapNaddr

> #### Syntax

> `DisplayString (``SIZE``(1..78))`

> #### Access

> read-write

> #### Description

> Specifies the complete network address to be used by the BRIDGE process placed on the logical machine as its listening address. The listening address for a BRIDGE is the means by which it is contacted by other BRIDGE processes participating in a networked application, that is, if the value of `tuxTdomainOptions` is `lan(1)`. If the string is of the form `0x` `hex-digits` or`\\x` `hex-digits`, it must contain an even number of valid hexadecimal digits. These forms are translated internally into a character array containing the hexadecimal representation of the string specified. For TCP/IP addresses, either the `//``hostname``:``port` or`#.#.#.#:``port` format is used.

### tuxTnetMapMinEncryptBit

> #### Syntax

> `INTEGER { none(1), 40-bit(2), 128-bit(3), unknown(4) }`

> #### Access

> read-write

> #### Description

> Specifies the required level of encryption when establishing a network link to this machine. `none(1)` means no encryption while `40-bit(2)` and `128-bit(3)` specify the encryption key length (in bits). If this minimum level of encryption cannot be met, the attempt to establish the link fails. The default value is `none(1)`. Modifications to this object do not affect network links that have already been established.

### tuxTnetMapMaxEncryptBit

> #### Syntax

> `Integer {none(1), 40-bit(2), 128-bit(3), unknown(4) }`

> #### Access

> read-write

> #### Description

> Encryption can be negotiated up to the specified level when establishing a network link. `none(1)` means no encryption while `40-bit(2)` and `128-bit(3)` specify the encryption key length (in bits). The default value is `128-bit(3)`. Modifications to this object will not affect network links that are already established.

## beaEventFilters

You can use the TUXEDO event filters to define a subset of TUXEDO event notifications to be generated for each TUXEDO or M3 domain being monitored. The columnar objects in the `beaEvtFilterTable` correspond to fields in TMEVENT_FILTER entries in the BEA Manager configuration file (`beamgr.conf`). Refer to the "Configuration Files" chapter in the Agent Integrator Reference Manual.

Variable Name | Object ID
--- | ---
`beaEvtFilterTblStatus` | .1.3.6.1.4.1.140.300.14.1
`beaEvtFilterTable` | .1.3.6.1.4.1.140.300.14.2

### beaEvtFilterTblStatus

> #### Syntax

> `INTEGER { sync(1), dirty(2) }`

> #### Access

> read-write

> #### Description

> When the agent starts, this value is always `sync(1)`. If any change is done to `beaEvtFilterTable` through `SET` requests, the value of this object becomes `dirty(2)` and the changes made to `beaEvtFilterTable` do not take effect. The changes made to the `beaEvtFilterTable` take effect only when you set the value of this object to `sync(1)`. When you set the value to `sync(1)`, all changes since the last synchronization are applied to the event-processing module.

### beaEvtFilterTable

This MIB group represents all the event filters defined for the Agent Connection. These are used to determine the collection of events to be forwarded as SNMP trap notifications.

Note: Changes to this table are applied only once `beaEvtFilterStatus` is set to `sync(1)`.

Variable Name | Object ID
--- | ---
`beaEvtFilterId` | .1.3.6.1.4.1.140.300.14.1.1.1
`beaEvtAgentName` | .1.3.6.1.4.1.140.300.14.1.1.2
`beaEvtExpr` | .1.3.6.1.4.1.140.300.14.1.1.3
`beaEvtFilter` | .1.3.6.1.4.1.140.300.14.1.1.4
`beaEvtFilterState` | .1.3.6.1.4.1.140.300.14.1.1.5

### beaEvtFilterId

> #### Syntax

> `DisplayString (``SIZE``(1..16))`

> #### Access

> read-write

> #### Description

> A unique identifier for the event filter within the filter table.

> Note: This object can be `SET` only during row creation.

### beaEvtAgentName

> #### Syntax

> `DisplayString (``SIZE``(1..32) )`

> #### Access

> read-only

> #### Description

> This logical agent name of the agent supporting this filter. This object is provided only for user convenience since the MIB only returns the event filters for the agent that was queried.

### beaEvtExpr

> #### Syntax

> `DisplayString (``SIZE``(1..255) )`

> #### Access

> read-write

> #### Description

> An event name expression. Consult the BEA TUXEDO Reference Manual entry for `recomp`(3) for the format of this expression. For a TUXEDO system event to be forwarded as an SNMP trap, its name should match this expression. Consult the BEA TUXEDO Reference Manual for a list of TUXEDO event names. The default for this object is all system events.

> #### Examples

> >     \.Sys.*

> matches all system events. (This is the default.)

> >     \.SysServer.*

> matches all system events related to servers.

> A value of `NONE` blocks all events from being forwarded by the selected agent and overrides any other filter table entries for the same logical agent name.

### beaEvtFilter

> #### Syntax

> >     DisplayString (SIZE (1..255) )

> #### Access

> read-write

> #### Description

> An event filter expression. Each TUXEDO event is accompanied with an FML buffer containing pertinent information about the event. The buffer's contents are evaluated with respect to this filter, if it is present. The filter must evaluate to TRUE or the event is not forwarded.

> The Agent Connection uses this attribute as an argument to `tpsubscribe()`. Please refer to the BEA TUXEDO Reference Manual for further information.

> #### Example

> `TA_EVENT_SEVERITY=='ERROR' || TA_EVENT_SEVERITY=='WARN'`

> This filter selects events with a severity of either ERROR or WARNING.

### beaEvtFilterState

> #### Syntax

> `INTEGER { active(1), inactive(2), invalid(3) }`

> #### Access

> read-write

> #### Description

> This object denotes the current state of the event filter instance.

> `GET {active(1)|inactive(2)}`
>   A `GET` operation will retrieve configuration and runtime information for the selected `beaEvtFilterTbl` instance(s). The following states indicate the meaning of a `beaEvtFilterState` returned in response to a `GET` request. States not listed will not be returned.

> `active(1)`
>   This filter is being used.

> `inactive(2)`
>   This filter is not being used.

> `SET {active(1)|inactive(2)|invalid(3)}`
>   A `SET` operation will update configuration and run-time information for the selected `beaEvtFilterTbl` instance. The following states indicate the meaning of a `beaEvtFilterState` set in a `SET` request. States not listed may not be set.

> `active(1)`
>   Activate the event filter. This can be done only when the filter is in the inactive(2) state.

> `inactive(2)`
>   Inactivate the event filter. This can be done only when the filter is in the active(1) state.

> `invalid(3)`
>   Inactivate (if active) and remove this event filter.