# Chapter 6. M3 MIB Groups

This chapter describes five MIB tables that are specific to the M3 product. To access these MIB objects, the M3 version of the Agent Connection should be running on the machine where M3 application resources are accessible. Table 6-1 lists the M3 groups. In addition to the objects in these M3 specific groups, the TUXEDO Core MIB contains the following M3 specific objects:

- `m3MaxObjects`

- `m3MaxInterfaces`

- `m3CurInterfaces`

- `m3HwInterfaces`

- `m3MachineMaxObjects`

- `m3MachineCurObjects`

- `m3MachineHwObjects`

- `m3SrvrCurObjsExt`

- `m3SrvrCurInterfaceExt`

The object `tuxTranGstate` also has M3 specific states. For more information on these objects, refer to Chapter 4, "TUXEDO Core MIB."

.

> Table 6-1 M3 Specific MIB Groups

Group Name | Description
--- | ---
`m3FactoryTable` | This table represents occurrences of factories registered with the FactoryFinder. The available factories for the M3 application are reflected in this MIB group.
`m3InterfaceTable` | This group represents the configuration and runtime attributes of CORBA interfaces at both the domain and server-group levels.
`m3LclInterfaceTable` | The instances in this table return local `m3InterfaceTable` attributes for the local host on which the Agent Connection is running.
`m3IfQueueTable` | The instances in this table represent the runtime attributes of interface as it pertains to a particular server queue (`tuxTqueue`).
`m3LclIfQueueTable` | The instances in this table represent the local attributes of `m3IfQueueTable` instances. These values are specific to the host on which the Agent Connection is running.

## m3FactoryTable

This table represents occurrences of factories registered with the FactoryFinder.

Variable Name | Object ID
--- | ---
`m3FactorySerNo` | .1.3.6.1.4.1.140.300.48.1.1
`m3FactoryId` | .1.3.6.1.4.1.140.300.48.1.2
`m3FactoryIfName` | .1.3.6.1.4.1.140.300.48.1.3
`m3FactoryState` | .1.3.6.1.4.1.140.300.48.1.4

### m3FactorySerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This object is the running number. This is used as the index to instances in this table.

### m3FactoryId

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The registered ID for the factory.

### m3FactoryIfName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The fully qualified interface name for the factory. This is the interface repository ID for the factory. The format of this name is dependent on the options specified in the IDL which generates the interface implementation. Consult the CORBA 2.1 specification, section 7.6, for details.

### m3FactoryState

> #### Syntax

> `INTEGER { active(1) }`

> #### Access

> read-only

> #### Description

> A `GET` operation retrieves runtime information for the selected `m3FactoryTable` instance or instances. The returned value is 1 (`active`) if the instance is registered with the FactoryFinder.

## m3InterfaceTable

The `m3InterfaceTable` represents configuration and runtime attributes of CORBA interfaces at both the domain and server-group levels.

There are certain semantic differences in the objects in the `m3InterfaceTable` between server-group and domain level instances.

A domain-level `m3InterfaceTable` instance is an instance that is not associated with a Server group. In this case, its `m3IfSrvGrp` attribute will have the invalid value `*`.

A server-group level instance is an instance that has an associated Server group. In this case, its `m3IfSrvGroup` attribute has a valid server group name for the domain. This server-group level representation of an interface also provides a container for managing the interface state (the `m3IfState` object) and for collecting accumulated statistics.

Every CORBA interface that is activated in a server must have a a server-group level `m3InterfaceTable` instance. The activation of interfaces in a server is controlled by the state of a `m3IfQueue` instance for the interface. Activation of an `m3IfQueue` instance causes its attributes to be initialized with values specified for the associated server-group level `m3InterfaceTable` instance. If such an instance does not already exist, then one will be dynamically created. This dynamically created server-group level `m3InterfaceTable` instance will be initialized with the attributes of the domain-level `m3InterfaceTable` instance for the interface if one exists. If an associated domain-level instance does not exist, system-specified default configuration values will be used. After they are activated, interfaces are always associated with a server-group level `m3InterfaceTable` instance.

The specification of configuration attributes for interfaces at any level is optional. Interfaces offered by a server are identified through the ICF file used for generating skeletons and advertised automatically by the system when the server is activated.

The following table lists the objects within the `m3InterfaceTable`.

Variable Name | Object ID
--- | ---
`m3IfSerNo` | .1.3.6.1.4.1.140.300.53.1.1.1
`m3IfName` | .1.3.6.1.4.1.140.300.53.1.1.2
`m3IfSrvGrp` | .1.3.6.1.4.1.140.300.53.1.1.3
`m3IfState` | .1.3.6.1.4.1.140.300.53.1.1.4
`m3IfAutoTran` | .1.3.6.1.4.1.140.300.53.1.1.5
`m3IfLoad` | .1.3.6.1.4.1.140.300.53.1.1.6
`m3IfPrio` | .1.3.6.1.4.1.140.300.53.1.1.7
`m3IfTimeout` | .1.3.6.1.4.1.140.300.53.1.1.8
`m3IfTranTime` | .1.3.6.1.4.1.140.300.53.1.1.9
`m3IfFbRoutingName` | .1.3.6.1.4.1.140.300.53.1.1.10
`m3IfLmid` | .1.3.6.1.4.1.140.300.53.1.1.11
`m3IfNumServers` | .1.3.6.1.4.1.140.300.53.1.1.12
`m3IfTpPolicy` | .1.3.6.1.4.1.140.300.53.1.1.13
`m3IfTxPolicy` | .1.3.6.1.4.1.140.300.53.1.1.14

### m3IfSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This is the running number. This object is used as an index to instances in this table.

### m3IfName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The fully qualified interface name. This is the interface ID. The format of this name is one of the options specified in the IDL which generates the interface implementation. Consult the CORBA 2.1 specification, Section 7.6, for details.

### m3IfSrvGrp

> #### Syntax

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

> #### Access

> read-write

> #### Description

> The server group name. Server group names cannot contain an asterisk, comma, or colon. If an asterisk (`*)` is specified as a value for this object, this specifies a domain level instance.

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

### m3IfState

> #### Syntax

> `INTEGER { active(1), inactive(2), suspended(3), partitioned(4), invalid(5), reactivate(6) }`

> #### Access

> read-write

> #### Description

> The semantics for `GET` and `SET` requests differ between server-group and domain level instances as noted in the following list.

> `GET:{active(1)|inactive(2)|suspended(3)|partitioned(4)}`
>   A `GET` request will retrieve configuration information for the selected `m3InterfaceTable` instance or instances. The only states that may be returned are: `active`, `inactive`, `suspended`, `partitioned`.

> `active(1)`
>   The `m3InterfaceTable` instance is defined and at least one corresponding `m3IfQueueTable` instance is in the active state. For a server-group level `m3InterfaceTable` instance, corresponding `m3IfQueueTable` instances are those with matching `m3IfName` and `m3IfSrvGrp` objects. For a domain-level `m3InterfaceTable` instance, corresponding `m3IfQueueTable` instances are those with matching `m3IfName` value regardless of their `m3IfSrvGrp` value.

> `inactive(2)`
>   The `m3InterfaceTable` instance is defined and there are no corresponding `m3IfQueueTable` instances in any active state.

> `suspended(3)`
>   The `m3InterfaceTable` instance is defined and amongst all corresponding `m3IfQueueTable` instances there are none in the active state and at least one in the suspended state.

> `partitioned(4)`
>   The `m3InterfaceTable` instance is defined and amongst all the corresponding `m3IfQueueTable` instances, there are none in the active state, none in the suspended state, and at least one in the partitioned state.

> `SET: {invalid(5)|active(1)|inactive(2)|reactivate(6)|suspended(3)}`
>   A `SET` request updates runtime and configuration information for the selected `m3InterfaceTable` instance. Modifications may affect more than one server group when making domain-level changes and runtime modifications may affect more than one server if multiple servers are currently offering an interface. Only the following values may be used in a `SET` request: `invalid`, `active`, `reactivate`, or `suspended`.

> `invalid(5)`
>   Delete the `m3InterfaceTable` instance for the application. This state change is allowed only when the instance is in the inactive state.

> `active(1)`
>   Activate the `m3InterfaceTable` instance for the application. Setting this state on a domain level instance has the effect of activating all corresponding `m3IfQueueTable` instances that are currently suspended throughout the domain. Setting this state on a server-group level instance affects only servers within the group offering the interface. This state change is allowed only when the instance is in the suspended state. A successful return leaves the object in the `active(1)` state.

> `reactivate(6)`
>   Reactivates the `m3InterfaceTable` instance. Setting this state on a domain level instance has the effect of activating all corresponding `m3IfQueueTable` instances that are currently suspended throughout the domain. Setting this state on a server-group level instance affects only servers within the group offering the interface. This state change is allowed only when the instance is in the `active(1)` or `suspended(3)` states. Successful return leaves the instance in the `active(1)` state. Setting this state permits global activation of `m3IfQueueTable` instances suspended at the server-group level without having to individually activate each server-group level `m3InterfaceTable` instance.

> `suspended(3)`
>   Suspend the `m3InterfaceTable` instance. Setting this state on the domain-level object has the effect of suspending all corresponding `m3IfQueueTable` instances that are currently active throughout the domain. Setting this state on a server-group level instance affects only servers within the group offering the interface. This state change is permitted only when in the `active(1)` state. Successful return leaves the object in the `suspended(3)` state.

> Note: Dynamic advertisement of interfaces (that is, state change from `inactive(2)` or `invalid(5)` to `active(1)`) is not supported, nor is removal of advertisement (that is, state change from `active(1)` to `inactive(2)`).

### m3IfAutoTran

> #### Syntax

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

> #### Access

> read-write

> #### Description

> Signifies whether a transaction will be automatically started for invocations made outside of a transaction context.

> This object has the following limitations:

> - Runtime updates to this attribute are not reflected in active equivalent `m3InterfaceTable` instances.

> - The `m3IfTxPolicy` object may override the value specified for this attribute in the `ubbconfig` file. If `m3IfTxPolicy` is `always(1)`, an `m3IfAutoTran` value of `no(2)` will have no effect at runtime. Behavior will be as though the setting were `yes(1)`. If `m3IfTxPolicy` is `never(2)`, an `m3IfAutoTran` value of `yes(1)` will have no effect. The interface will never be involved in a transaction. If `m3IfTxPolicy` is `ignore(4)`, an `m3IfAutoTran` value of `yes(1)` will have no effect. The interface will never be involved in a transaction.

### m3IfLoad

> #### Syntax

> `INTEGER``(1..32767)`

> #### Access

> read-write

> #### Description

> This object imposes the indicated load on the system. Inferface loads are used for load-balancing. That is, queues with higher enqueued workloads will be less likely to be chosen for a new request.

> Note: Runtime updates to this attribute for domain level instances will not affect corresponding server-group level instances for the same interface.

### m3IfPrio

> #### Syntax

> `INTEGER` `(1..100)`

> #### Access

> read-write

> #### Description

> Dequeueing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests are handled first.

> Note: Runtime updates to this attribute for domain-level instances will not affect corresponding server-group level instances for the same interface.

### m3IfTimeout

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> The time limit (in seconds) for processing individual method invocations for this interface. Servers processing method invocations for this interface will be terminated abortively if they exceed the specified time limit in processing the request. A value of 0 for this attribute indicates that the server should not be terminated abortively.

> Note: Runtime updates to this attribute for domain-level instances will not affect corresponding server-group level instances for the same interface.

### m3IfTranTime

> #### Syntax

> `INTEGER`

> #### Access

> read-write

> #### Description

> Transaction timeout value in seconds for transactions automatically started for this `m3InterfaceTable` instance. Transactions are started automatically when a request not in transaction mode is received and the `m3IfAutoTran` object value for the interface is `yes(1)`.

> Note: Runtime updates to this attribute for domain-level instances will not affect corresponding server-group level instances for the same interface.

### m3IfFbRoutingName

> #### Syntax

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

> #### Access

> read-write

> #### Description

> The factory-based routing criteria associated with this interface.

> Note: This attribute may be set only for a domain-level `m3InterfaceTable` instance, that is, only if `m3IfSrvGrp` is `*`.

### m3IfLmid

> #### Syntax

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

> #### Access

> read-only

> #### Description

> Current logical machine with which the active equivalent server-group level `m3InterfaceTable` instance is associated. This attribute is `NULL` for domain-level instances.

### m3IfNumServers

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of corresponding servers offering this interface.

### m3IfTpPolicy

> #### Syntax

> `INTEGER { method(1), transaction(2), process(3) }`

> #### Access

> read-only

> #### Description

> The TP framework deactivation policy. This reflects the policy registered with the framework at server startup. The first server to register with the interface sets the value in `m3InterfaceTable`. This cannot be changed.

### m3IfTxPolicy

> #### Syntax

> `INTEGER { always(1), never(2), optional(3), ignore(4) }`

> #### Access

> read-only

> #### Description

> The transaction policy for the interface. The setting in this attribute affects the `m3IfAutoTran` object. This policy is set by the application developer and is registered when the server starts.

## m3LclInterfaceTable

The table returns values for the local host on which the Agent Connection is running. The following table lists the columnar objects that comprise each row (instance) in the table.

Variable Name | Object ID
--- | ---
`m3LclIfSerNo` | .1.3.6.1.4.1.140.300.53.2.1.1
`m3LclIfName` | .1.3.6.1.4.1.140.300.53.2.1.2
`m3LclSrvGrp` | .1.3.6.1.4.1.140.300.53.2.1.3
`m3LclIfNcompleted` | .1.3.6.1.4.1.140.300.53.2.1.4
`m3LclIfNqueued` | .1.3.6.1.4.1.140.300.53.2.1.5

### m3LclIfSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> This is the running number. This is used as an index into the table.

### m3LclIfName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The fully qualified interface name. The interface repository ID for the interface. The format of this name is dependent on the options specified in the IDL which generates the interface implementation. See the CORBA 2.1 Specification Section 7.6 [CORBA] for details.

### m3LclIfSrvGrp

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The server group name. Server group names cannot contain an asterisk, comma, or colon. A value of `*` for this object indicates a domain-level interface.

### m3LclIfNcompleted

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of method invocations completed for the corresponding `m3IfQueueTable` instances since they were initially offered. The values returned are for the indicated interface on the local host where the Agent Connection is running.

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

### m3LclIfNqueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of requests currently enqueued for this interface. The values returned are for the indicated interface on the local host where the Agent Connection is running.

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

## m3IfQueueTable

This table represents the runtime attributes of an interface for a particular server queue. This group provides access to the inherited configuration attributes of an interface as well as statistics relating to the interface on the queue. This class gives administrators finer granularity in suspending and activating interfaces. This group provides the link between the interface name and the server processes capable of processing method invocations on the interface. For example, `m3IfQRqAddr` can be used to identify the corresponding server in the `tuxTsrvrTbl` and `tuxTsrvrTblExt` groups.

Variable Name | Object ID
--- | ---
`m3IfQueueSerNo` | .1.3.6.1.4.1.140.300.53.3.1.1
`m3IfQueueName` | .1.3.6.1.4.1.140.300.53.3.1.2
`m3IfQueueSrvGrp` | .1.3.6.1.4.1.140.300.53.3.1.3
`m3IfQueueRqAddr` | .1.3.6.1.4.1.140.300.53.3.1.4
`m3IfQueueState` | .1.3.6.1.4.1.140.300.53.3.1.5
`m3IfQueueAutoTran` | .1.3.6.1.4.1.140.300.53.3.1.6
`m3IfQueueLoad` | .1.3.6.1.4.1.140.300.53.3.1.7
`m3IfQueuePrio` | .1.3.6.1.4.1.140.300.53.3.1.8
`m3IfQueueTimeout` | .1.3.6.1.4.1.140.300.53.3.1.9
`m3IfQueueTranTime` | .1.3.6.1.4.1.140.300.53.3.1.10
`m3IfQueueFbRoutingName` | .1.3.6.1.4.1.140.300.53.3.1.11
`m3IfQueueLmid` | .1.3.6.1.4.1.140.300.53.3.1.12
`m3IfQueueNumServers` | .1.3.6.1.4.1.140.300.53.3.1.13
`m3IfQueueTpPolicy` | .1.3.6.1.4.1.140.300.53.3.1.14
`m3IfQueueTxPolicy` | .1.3.6.1.4.1.140.300.53.3.1.15

### m3IfQueueSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The running number used as an index into this table.

### m3IfQueueName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The fully qualified interface name. The interface repository ID for the interface. The format of this name is dependent on the options specified in the IDL which generates the interface implementation. See the CORBA 2.1 specification Section 7.6 for details.

### m3IfQueueSrvGrp

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The server group name. Server group names cannot contain an asterisk, comma, or colon.

### m3IfQueueRqAddr

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The symbolic address of the request queue for an active server offering this interface. See `tuxTsrvrRqAddr` for more information about this attribute.

### m3IfQueueState

> #### Syntax

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

> #### Access

> read-write

> #### Description

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

> `GET:{active(1)|suspended(2)|partitioned(3)}`
>   A `GET` request will retrieve configuration information for the selected `m3IfQueueTable` instances. The meaning of the possible return values are as follows:

> `active(1)`
>   Represents an available interface in the running system.

> `suspended(2)`
>   Represents a currently suspended interface in the running system.

> `partitioned(3)`
>   Represents a currently partitioned interface in the running system.

> `SET:{active(1)|suspended(2)}`
>   The values for `SET` are:``

> `active(1)`
>   Activates the `m3IfQueueTable` instance. This state change is allowed only when in the `suspended(2)` state. A successful return leaves instances in the `active(1)` state.

> `suspended(2)`
>   Suspends the `m3IfQueueTable` instance. This state change is allowed only when in the `active(1)` state. A successful return leaves the object in the `suspended(2)` state.

> Note: Dynamic advertisement of interfaces (i.e., a state change from inactive or invalid to active) is not supported, nor is unadvertisement (i.e., a state change from active to inactive).

### m3IfQueueAutoTran

> #### Syntax

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

> #### Access

> read-only

> #### Description

> Signifies whether a transaction will be automatically started for invocations made outside a transaction context.

> This object has the following limitations:

> - Runtime updates to this attribute are not reflected in active equivalent `m3InterfaceTable` instances.

> - The `m3IfTxPolicy` object may override the value specified for this attribute in the `ubbconfig` file. If `m3IfTxPolicy` is `always(1)`, an `m3IfQueueAutoTran` value of `no(2)` will have no effect at runtime. Behavior will be as though the setting were `yes(1)`. If `m3IfTxPolicy` is `never(2)`, an `m3IfQueueAutoTran` value of `yes(1)` will have no effect. The interface will never be involved in a transaction. If `m3IfTxPolicy` is `ignore(4)`, an `m3IfQueueAutoTran` value of `yes(1)` will have no effect. The interface will never be involved in a transaction.

### m3IfQueueLoad

> #### Syntax

> `INTEGER` `(1..32767)`

> #### Access

> read-only

> #### Description

> Load imposed on the system by this instance. Interface loads are used for load-balancing. Queues with higher enqueued workloads are less likely to be chosen for a new request.

### m3IfQueuePrio

> #### Syntax

> `INTEGER``(1..101)`

> #### Access

> read-only

> #### Description

> Dequeueing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests will be handled first.

### m3IfQueueTimeout

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The time limit (in seconds) for processing individual method invocations for this interface. Servers processing method invocations for this interface will be abortively terminated if they exceed the specified time limit in processing the request. A value of 0 for this attribute indicates that the server should not be abortively terminated.

### m3IfQueueTranTime

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

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

### m3IfQueueFbRoutingName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The factory-based routing criterion associated with this interface.

### m3IfQueueLmid

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The current logical machine on which this queue is offering this interface.

### m3IfQueueNumServers

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of corresponding servers offering this interface on this queue.

### m3IfQueueTpPolicy

> #### Syntax

> `INTEGER { method(1), transaction(2), process(3) }`

> #### Access

> read-only

> #### Description

> The TP framework deactivation policy. This reflects the policy registered with the framework at the server startup. The first server to register the interface sets the value. This value cannot be changed.

## m3LclIfQueueTable

This table represents the local attributes of the `m3IfQueueTable`. These values are specific to the host on which the Agent Connection is running.

.

Variable Name | Object ID
--- | ---
`m3LclIfQueueSerNo` | .1.3.6.1.4.1.140.300.53.4.1.1
`m3LclIfQueueName` | .1.3.6.1.4.1.140.300.53.4.1.2
`m3LclIfQueueSrvGrp` | .1.3.6.1.4.1.140.300.53.4.1.3
`m3LclIfQueueRqAddr` | .1.3.6.1.4.1.140.300.53.4.1.4
`m3LclIfQueueNcompleted` | .1.3.6.1.4.1.140.300.53.4.1.5
`m3LclIfQueueNqueued` | .1.3.6.1.4.1.140.300.53.4.1.6
`m3LclIfQueueCurObjs` | .1.3.6.1.4.1.140.300.53.4.1.7
`m3LclIfQueueCurTrans` | .1.3.6.1.4.1.140.300.53.4.1.8

### m3LclIfQueueSerNo

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The running number used as an index into this table.

### m3LclIfQueueName

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The fully qualified interface name. The interface repository ID for this interface. The format of this name is dependent on the options specified in the IDL that generates the interface implementation. See the CORBA 2.1 specification Section 7.6 for details.

### m3LclIfQueueSrvGrp

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The server group name. Server group names cannot contain an asterisk, comma, or colon.

### m3LclIfQueueRqAddr

> #### Syntax

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

> #### Access

> read-only

> #### Description

> The symbolic address of the request queue for an active server offering this interface. See `tuxTsrvrRqAddr` for more information about this attribute.

### m3LclIfQueueNcompleted

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of interface method invocations completed since the interface was initially offered.

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

### m3LclIfQueueNqueued

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of requests currently enqueued for this interface.

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

### m3LclIfQueueCurObjs

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of active objects for this interface for the associated queue. This number represents the number of entries in the active object table for this queue on the associated machine. This includes objects that are not in memory but were invoked within an active transaction.

### m3LclIfQueueCurTrans

> #### Syntax

> `INTEGER`

> #### Access

> read-only

> #### Description

> The number of active global transactions associated with this interface for its associated queue.