BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   File Formats and Data Descriptions Reference   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


TM_MIB(5)

Name

TM_MIB—Management Information Base for core BEA Tuxedo system

Synopsis

#include <fml32.h> 
#include <tpadm.h>

Description

The BEA Tuxedo System MIB defines the set of classes through which the fundamental aspects of an application can be configured and managed. This includes management of machines, servers, networking.

TM_MIB(5) should be used in combination with the generic MIB reference page MIB(5) to format administrative requests and interpret administrative replies. Requests formatted as described in MIB(5) using classes and attributes described in this reference page may be used to request an administrative service using any one of a number of existing ATMI interfaces in an active application. Inactive applications may also be administered using the tpadmcall() function interface. For additional information pertaining to all TM_MIB(5) class definitions, see TM_MIB(5) Additional Information.

TM_MIB(5) consists of the following classes.

TM_MIB Classes

Class Name

Controls . . .

T_BRIDGE

Network connections

T_CLIENT

Clients

T_CONN

Conversations

T_DEVICE

Devices

T_DOMAIN

Global application attributes

T_FACTORY

Factories

T_GROUP

Server groups

T_IFQUEUE

Server queue interfaces

T_INTERFACE

Interfaces

T_MACHINE

Machine specific attributes

T_MSG

Message queues

T_NETGROUP

Network groups

T_NETMAP

Machines to Netgroups

T_QUEUE

Server queue

T_ROUTING

Routing criteria

T_SERVER

Servers

T_SERVERCTXT

Server context

T_SERVICE

Services

T_SVCGRP

Service group

T_TLISTEN

BEA Tuxedo system listeners

T_TLOG

Transaction log

T_TRANSACTION

Transaction

T_ULOG

User log


 

Each class description consists of four sections:

Attribute Table Format

Each class that is a part of this MIB is defined in four parts in sections that follow. One of the four parts is the attribute table. The attribute table is a reference guide to the attributes within a class and how they may used by administrators, operators, and general users to interface with an application.

There are five columns for each attribute described in an attribute table: name, type, permissions, values, and default. Each of these components is discussed in MIB(5).

TA_FLAGS Values

MIB(5) defines the generic TA_FLAGS attribute, which is a long containing both generic and component MIB specific flag values. The following are the TM_MIB(5) specific flag values supported. These flag values should be or'd with any generic MIB flags.

TMIB_ADMONLY

A flag used to indicate that only administrative processes should be activated when changing the state of a T_MACHINE object from INActive to ACTive.

TMIB_APPONLY

A flag used to indicate that only application processes should be considered when activating or deactivating a T_MACHINE object. It may also be used on T_SERVER and T_SERVERCTXT retrievals to restrict the retrieval to application servers only.

TMIB_CONFIG

A flag used to indicate that only configured groups and servers should be considered in satisfying the request.

TMIB_NOTIFY

A flag used when activating or deactivating T_MACHINE, T_GROUP, or T_SERVER objects to cause unsolicited notification messages to be sent to the originating client just prior to and just after the activation or deactivation of each server object selected.

FML32 Field Tables

The field table for the attributes described in this reference page is found in the file udataobj/tpadm relative to the root directory of the BEA Tuxedo system software installed on the system. The directory ${TUXDIR}/udataobj should be included by the application in the colon-separated list specified by the FLDTBLDIR environment variable, and the field table name tpadm should be included in the comma-separated list specified by the FIELDTBLS environment variable.

Limitations

Access to the header files and field tables for this MIB is being provided only on BEA Tuxedo release 6.1 sites and later, both native and Workstation.

Workstation access to this MIB is limited to runtime only access; the function tpadmcall(3c) is not supported on workstations.

For the purpose of preimage processing (MIB_PREIMAGE flag bit set), local attributes for classes that have global attributes are not considered. Additionally, indexed fields and the indexes that go with them are not considered, for example, T_TLOG class, TA_TLOGCOUNT, TA_TLOGINDEX, TA_GRPNO, TA_TLOGDATA attributes.

T_BRIDGE Class Definition

Overview

The T_BRIDGE class represents run-time attributes pertaining to connectivity between logical machines making up an application. These attribute values represent connection status and statistics.

Attribute Table

TM_MIB(5): T_BRIDGE Class Definition Attribute Table

Attribute1

Type

Permissions

Values

Default

TA_LMID(*)2

string

r--r--r--

"LMID1[,LMID2]"

N/A

TA_NETGROUP(k)3

string

R--R--R--

string[1. . 30]

DEFAULTNET

TA_STATE(k)

string

rwxrwxr--

GET: "{ACT | INA | SUS | PEN}"

SET: "{ACT | INA | SUS | PEN}"

N/A

N/A

TA_CURTIME

long

R--R--R--

0 <= num

N/A

TA_CONTIME

long

R-XR-XR--

0 <= num

N/A

TA_SUSPTIME

long

rwxrwxr--

0 <= num

3004

TA_RCVDBYT

long

R-XR-XR--

0 <= num

N/A

TA_SENTBYT

long

R-XR-XR--

0 <= num

N/A

TA_RCVDNUM

long

R-XR-XR--

0 <= num

N/A

TA_SENTNUM

long

R-XR-XR--

0 <= num

N/A

TA_FLOWCNT

long

R-XR-XR--

0 <= num

N/A

TA_CURENCRYPTBIT

string

R--R-----

{0 | 40 | 56 | 128}5

N/A

(k)—GET key field
(*)—GET/SET key, one or more required for SET operations


 

1All attributes in Class T_BRIDGE are local attributes.

2The TA_LMID attribute must be fully specified for SET operations, that is, LMID1,LMID2.

3SET operation may only use TA_NETGROUP DEFAULTNET in BEA Tuxedo release 6.4. GET operation may use any TA_NETGROUP defined for both LMID values.

4TA_SUSPTIME may be SET only if the TA_STATE is currently SUSPENDED or is being SET to SUSPENDED.

5The link-level encryption value of 40 bits is provided for backward compatibility.

Attribute Semantics

TA_LMID: LMID1[,LMID2]

Source logical machine identifier (LMID1) and destination logical machine identifier (LMID2) for network connection.

TA_NETGROUP: string[1 . .30]

Logical name of the network group.When both source and destination TA_LMID identifiers are in the same TA_NETGROUP, the T_BRIDGE class will present all instances of related fields per TA_NETGROUP. TA_NETGROUP may be used as a key field on GET requests. TA_NETGROUP values other than DEFAULTNET may not be used on SET operations in this BEA Tuxedo release (release 6.4).

TA_STATE:

GET: "{ACTive | INActive | SUSpended | PENding}"

A GET operation will retrieve run-time information for the selected T_BRIDGE object(s). A TA_LMID 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 will contain an expanded TA_LMID attribute value with the destination LMID filled in. The following states indicate the meaning of a TA_STATE returned in response to a GET request.

ACTive

The connection is established and active.

INActive

The connection is inactive. This state is only returned when status is requested on a particular connection, that is, both Lands specified in the TA_LMID attribute and the source logical machine is reachable.

SUSpended

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 TA_SUSPTIME attribute value. This state is ACTive equivalent for the purpose of determining permissions.

PENding

An asynchronous connection has been requested, but has not yet been completed. The final outcome of the connection request has not been determined.


 

SET: "{ACTive | INActive | SUSpended | PENding}"

A SET operation will update run-time information for the selected T_BRIDGE object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

unset

Modify an existing T_BRIDGE object. This combination is allowed only when in the ACTive or SUSpended state. Successful return leaves the object state unchanged.

ACTive

Activate the T_BRIDGE object by establishing a connection between the indicated logical machines. This operation will fail 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. While the T_BRIDGE object is establishing the asynchronous connection, the BRIDGE will do other work. Using the state change to PENding is recommended. State change allowed in the INActive and SUSpended states. For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). Successful return leaves the object in the PENding state.

INActive

Deactivate the T_BRIDGE object by closing the connection between the indicated logical machines. This operation will fail if only one logical machine is specified or if the two machines are not connected. State change allowed only when in the ACTive state. Successful return leaves the object in the INActive state.

SUSpended

Suspend the T_BRIDGE object by closing the connection between the indicated logical machines and by setting the TA_SUSPTIME parameter as indicated. State change allowed only when in the ACTive state. Successful return leaves the object in the SUSpended state. Limitation: Note that since the statistics reported are from the viewpoint of the source logical machine, resetting those statistics will cause them to be out of sync with the statistics reported by the destination logical machine for the same connection.

PENding

Activate the T_BRIDGE object by establishing an asynchronous connection between the indicated logical machines. This operation will fail if only one logical machine is specified, if either of the two machines is not active, or if the source machine is not reachable. When in the PENding 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 is outstanding. State change allowed in the INActive and SUSpended states. For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). Successful return leaves the object in the PENding state.


 

TA_CURTIME: 0 <= num

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

TA_CONTIME: 0 <= num

Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on T_BRIDGE:TA_LMID, when this connection was first established. Elapsed open time in seconds can be computed using TA_CURTIME - TA_CONTIME.

TA_SUSPTIME: 0 <= num

Time, in seconds, remaining in the suspension of this connection. After this amount of time, the connection will automatically change to a TA_STATE of INACTIVE and may be activated by normal application traffic.

TA_RCVDBYT: 0 <= num

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

TA_SENTBYT: 0 <= num

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

TA_RCVDNUM: 0 <= num

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

TA_SENTNUM: 0 <= num

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

TA_FLOWCNT: 0 <= num

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

TA_CURENCRYPTBITS: {0 | 40 | 56 | 128}

The current encryption level for this link. The level is negotiated between machines when the link is established.

Note: The link-level encryption value of 40 bits is provided for backward compatibility.

Limitations

None.

T_CLIENT Class Definition

Overview

The T_CLIENT class represents run-time attributes of active clients within an application. These attribute values identify and track the activity of clients within a running application.

Attribute Table

TM_MIB(5): T_CLIENT Class Definition Attribute Table

Attribute1

Type

Permissions

Values

Default

TA_STATE(k)

string

R-XR-XR--

GET: "{ACT | SUS | DEA}"

SET: "{ACT | SUS | DEA}"

N/A

N/A

TA_CLIENTID(*)

string

R--R--R--

string[1 . .78]

N/A

TA_CLTNAME(k)

string

R--R--R--

string[0 . .30]

N/A

TA_IDLETIME(k)

long

R--R--R--

0 <= num

N/A

TA_LMID(k)

string

R--R--R--

LMID

N/A

TA_PID(k)

long

R--R--R--

1 <= num

N/A

TA_CONTEXTID

long

R--R--R--

-2 <= num < 30,000

N/A

TA_SRVGRP(k)

string

R--R--R--

string[0 . .30]

N/A

TA_USRNAME(k)

string

R--R--R--

string[0 . .30]

N/A

TA_WSC(k)

string

R--R--R--

"{Y | N}"

N/A

TA_WSH(k)

string

R--R--R--

"{Y | N}"

N/A

TA_WSHCLIENTID(k)

string

R--R--R--

string[1 . .78]

N/A

TA_RELEASE

long

R--R--R--

0 <= num

N/A

TA_WSPROTO

long

R--R--R--

0 <= num

N/A

TA_NUMCONV

long

R-XR-XR--

0 <= num

N/A

TA_NUMDEQUEUE

long

R-XR-XR--

0 <= num

N/A

TA_NUMENQUEUE

long

R-XR-XR--

0 <= num

N/A

TA_NUMPOST

long

R-XR-XR--

0 <= num

N/A

TA_NUMREQ

long

R-XR-XR--

0 <= num

N/A

TA_NUMSUBSCRIBE

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRAN

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRANABT

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRANCMT

long

R-XR-XR--

0 <= num

N/A

TA_CMTRET

string

R--R--R--

"{COMPLETE | LOGGED}"

N/A

TA_CURCONV

long

R--R--R--

0 <= num

N/A

TA_CURENCRYPTBIT

string

R--R-----

{0 | 40 | 56 | 128}2

N/A

TA_CURREQ

long

R--R--R--

0 <= num

N/A

TA_CURTIME

long

R--R--R--

1 <= num

N/A

TA_LASTGRP

long

R--R--R--

1 <= num <30,000

N/A

TA_NADDR

string

R--R--R--

string[1 . .78]

N/A

TA_NOTIFY

string

R--R--R--

"{DIPIN | SIGNAL | THREAD | IGNORE}"

N/A

TA_NUMUNSOL

long

R--R--R--

0 <= num

N/A

TA_RPID

long

R--R--R--

1 <= num

N/A

TA_TIMELEFT

long

R--R--R--

0 <= num

N/A

TA_TIMESTART

long

R--R--R--

1 <= num

N/A

TA_TRANLEV

long

R--R--R--

0 <= num

N/A

(k)—GET key field
(*)—GET/SET key, one or more required for SET operations


 

1All attributes in Class T_CLIENT are local attributes.
2The link-level encryption value of 40 bits is provided for backward compatibility.

Attribute Semantics

TA_STATE:

GET: "{ACTive | SUSpended | DEAd}"

A GET operation will retrieve run-time information for the selected T_CLIENT object(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 TA_STATE returned in response to a GET request.

ACTive

T_CLIENT object active. This is not an indication of whether the client is idle or busy. A non 0 value retrieved for either the TA_CURCONV attribute or the TA_CURREQ attribute indicates a busy client.

SUSpended

T_CLIENT object active and suspended from making further service requests (tpcall() or tpacall()) and from initiating further conversations (tpconnect()). See SET SUSpended below for details. This state is ACTive equivalent for the purpose of determining permissions.

DEAd

T_CLIENT object 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. This state is ACTive equivalent for the purpose of determining permissions.


 

SET: "{ACTive | SUSpended | DEAd}"

A SET operation will update run-time information for the selected T_CLIENT object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

ACTive

Activate a SUSpended T_CLIENT object. State change allowed only when in the SUSpended state. Successful return leaves the object in the ACTive state.

unset

Modify an existing T_CLIENT object. This combination is allowed only when in the ACTive or SUSpended state. Successful return leaves the object state unchanged.

SUSpended

Suspend the T_CLIENT object from making service requests (tpcall() or tpacall()), initiating conversations (tpconnect()), beginning transactions (tpbegin()), and enqueuing new requests (tpenqueue()). 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 state. Successful return leaves the object in the SUSpended state.

DEAd

Abortively deactivate the T_CLIENT object. State change allowed only when in the ACTive or SUSpended state. The recommended method for deactivating clients is to first broadcast a warning message (tpbroadcast)), then to suspend them (see SET SUSpended above), and finally to abortively deactivate them by setting the state to DEAd. Successful return leaves the object in the DEAd state.

Limitation: Workstation handlers (T_CLIENT:TA_WSH == Y) may not be set to a state of DEAd.

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.


 

TA_CLIENTID: string[1..78]

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

TA_CLTNAME: string[0..30]

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

TA_IDLETIME: 0 <= num

Approximate amount of time, in seconds, since this client last interacted with the system via an ATMI call. This value is accurate to within TA_SCANUNIT (see the T_DOMAIN class) seconds. When specified as a key field, a positive value indicates that all clients with idle times of at 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.

TA_LMID: LMID

Logical machine where client is running (native clients) or where client is connected (Workstation clients).

TA_PID: 1 <= num

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.

TA_CONTEXTID: -2 <= num < 30,000

Identifier for this particular application association.

TA_SRVGRP: string[0..30]

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

TA_USRNAME: string[0..30]

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

TA_WSC: "{Y | N}"

Workstation client. If this attribute is set to "Y", then the indicated client is logged in to the application from a remote workstation.

TA_WSH: "{Y | N}"

Workstation handler. If this attribute is set to "Y", then the indicated client is a workstation handler process.

TA_WSHCLIENTID: string[1..78]

Client identifier for the associated workstation handler (WSH) if this client is a Workstation client (TA_WSH == Y); otherwise, this attribute will be returned as a 0-length string.

TA_RELEASE: 0 <= num

The BEA Tuxedo system major protocol release number for the machine where the client is running. This may be different from the TA_SWRELEASE for the same machine. Note that for Workstation clients (TA_WSC == Y), this value may be different than the major release associated with the application administered machine through which the Workstation client accesses the application.

TA_WSPROTO: 0 <= num

The BEA Tuxedo system Workstation protocol version number for a Workstation client. This value is changed with each update to the Workstation protocol. A value of 0 is returned for this attribute when associated with non-Workstation clients (TA_WSC == N).

TA_NUMCONV: 0 <= num

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

TA_NUMDEQUEUE: 0 <= num

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

TA_NUMENQUEUE: 0 <= num

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

TA_NUMPOST: 0 <= num

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

TA_NUMREQ: 0 <= num

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

TA_NUMSUBSCRIBE: 0 <= num

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

TA_NUMTRAN: 0 <= num

Number of transactions begun by this client.

TA_NUMTRANABT: 0 <= num

Number of transactions aborted by this client.

TA_NUMTRANCMT: 0 <= num

Number of transactions committed by this client.

TA_CMTRET: "{COMPLETE | LOGGED}"

Setting of the TP_COMMIT_CONTROL characteristic for this client. See the description of the BEA Tuxedo System ATMI function tpscmt() for details on this characteristic.

TA_CURCONV: 0 <= num

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

TA_CURENCRYPTBITS: {0 | 40 | 56 | 128}

The current encryption level for this client. The level is negotiated when the link is established.

Note: The link-level encryption value of 40 bits is provided for backward compatibility.

TA_CURREQ: 0 <= num

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

TA_CURTIME: 1 <= num

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

TA_LASTGRP: 1 <= num < 30,000

Server group number (T_GROUP:TA_GRPNO) of the last service request made or conversation initiated from this client.

TA_NADDR: string[1 . . 78]

For Workstation clients, this attribute indicates the network address of the client. Network addresses with unprintable characters are converted to one of the following formats:

A string in either format must contain an even number of valid hex digits. Such a string is translated internally into a character array containing the hexadecimal representations of the string specified.

For TCP/IP addresses one of the following formats is used:

Each # (pound) sign represents a decimal number in the range of 0 to 255. The value of port_number is a decimal number in the range of 0 to 65535.

Note: Some port numbers may be reserved for the underlying transport protocols (such as TCP/IP) used by your system. Check the documentation for your transport protocols to find out which numbers, if any, are reserved on your system.

Non-Workstation clients have a 0-length string associated with them for this attribute value.

Limitation: 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.

TA_NOTIFY: "{DIPIN | SIGNAL | THREAD | IGNORE}"

Setting of the notification characteristic for this client. See the T_DOMAIN class description of this attribute for more details.

TA_NUMUNSOL: 0 <= num

Number of unsolicited messages queued for this client awaiting processing.

TA_RPID: 1 <= num

UNIX system message queue identifier for the client's reply queue. Limitation: 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.

TA_TIMELEFT: 0 <= num

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

TA_TIMESTART: 1 <= num

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

TA_TRANLEV: 0 <= num

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

Limitations

None.

T_CONN Class Definition

Overview

The T_CONN class represents run-time attributes of active conversations within an application.

Attribute Table

TM_MIB(5): T_CONN Class Definition Attribute Table

Attribute1

Type

Permissions

Values

Default

TA_LMID(k)

string

R--R--R--

LMID

N/A

TA_STATE(k)

string

R--R--R--

GET: "ACT"

SET: N/A

N/A

N/A

TA_SERVICENAME

string

R--R--R--

string[1..15]

N/A

TA_CLIENTID(k)

TA_CONNOGRPNO

TA_CONNOLMID

TA_CONNOPID

TA_CONNOSNDCNT

TA_CONNOSRVID

string

long

string

long

long

long

R--R--R--

R--R--R--

R--R--R--

R--R--R--

R--R--R--

R--R--R--

string[1..78]

1 <= num < 30,001

LMID

1 <= num

0 <= num

1 <= num < 30,001

N/A

N/A

N/A

N/A

N/A

N/A

TA_CONNSGRPNO

TA_CONNSLMID

TA_CONNSPID

TA_CONNSSNDCNT

TA_CONNSSRVID

long

string

long

long

long

R--R--R--

R--R--R--

R--R--R--

R--R--R--

R--R--R--

1 <= num < 30,001

LMID

1 <= num

0 <= num

1 <= num < 30,001

N/A

N/A

N/A

N/A

N/A

(k)—GET key field


 

1All attributes in Class T_CONN are local attributes.

Attribute Semantics

TA_LMID: LMID

Retrieval machine logical machine identifier.

TA_STATE:

GET: {ACTive}

A GET operation will retrieve run-time information for the selected T_CONN object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request.

ACTive

The object returned reflects one or both sides of an active conversation within the application.


 

SET:

SET operations are not permitted on this class.

TA_SERVICENAME: string[1..15]

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

TA_CLIENTID: string[1..78]

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

TA_CONNOGRPNO: 1 <= num < 30,001

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.

TA_CONNOLMID: LMID

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

TA_CONNOPID: 1 <= num

Process identifier for the originator of the conversation.

TA_CONNOSNDCNT: 0 <= num

Number of tpsend() calls done by the originator.

TA_CONNOSRVID: 1 <= num < 30,001

Server identifier for the originator of the conversation.

TA_CONNSGRPNO: 1 <= num < 30,001

Server group number for the subordinate of the conversation.

TA_CONNSLMID: LMID

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

TA_CONNSPID: 1 <= num

Process identifier for the subordinate in the conversation.

TA_CONNSSNDCNT: 0 <= num

Number of tpsend() calls done by the subordinate.

TA_CONNSSRVID: 1 <= num < 30,001

Server identifier for the subordinate in the conversation.

Limitations

None.

T_DEVICE Class Definition

Overview

The T_DEVICE class represents configuration and run-time attributes of raw disk slices or UNIX system files being used to store BEA Tuxedo system device lists. This class allows for the creation and deletion of device list entries within a raw disk slice or UNIX system file.

Attribute Table

TM_MIB(5): T_DEVICE Class Definition Attribute Table

Attribute1

Type

Permissions

Values

Default

TA_LMID(*)

string

ru-r--r--

LMID

local_lmid

TA_CFGDEVICE(r)(*)

string

ru-r--r--

string[2..64]

N/A

TA_DEVICE(*)

string

ru-r--r--

string[2..64]

TA_CFGDEVICE

TA_DEVOFFSET(*)

long

ru-r--r--

0 <= num

0

TA_DEVSIZE(r)

long

rw-r--r--

0 <= num

10003

TA_DEVINDEX(*)2

long

r--r--r--

0 <= num

N/A


TA_STATE(k)

string

rwxr--r--

GET: "VAL"

SET: "{NEW | INV}"

N/A

N/A

(k)—GET key field
(r)—required field for object creation (SET TA_STATE NEW)
(*)—GET/SET key, one or more required for SET operations


 

1All attributes in Class T_DEVICE are local attributes.
2TA_DEVINDEX is required for SET operations to identify the particular device list entry except when setting the state to NEW for the purpose of creating a new device list entry. In the latter case, TA_DEVINDEX must not be set; a value will be assigned by the system and returned after a successful creation.
3TA_DEVSIZE may only be SET on object creation.

Attribute Semantics

TA_LMID: LMID

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 T_MACHINE entry is defined). It is required as a key field on SET operations when accessing a booted application. If specified when accessing the T_DEVICE class in an unconfigured application, this attribute is ignored.

TA_CFGDEVICE: string[2..64]

Absolute pathname of the file or device where the BEA Tuxedo filesystem is stored or is to be stored.

TA_DEVICE: string[2..64]

Absolute pathname of the device list entry.

TA_DEVOFFSET: 0 <= num

The offset, in blocks, at which space on this TA_DEVICE begins for use within the BEA Tuxedo System VTOC specified by TA_CFGDEVICE. Limitation: This attribute must be set to 0 for the first device list entry (TA_DEVICE) on the BEA Tuxedo filesystem (TA_CFGDEVICE).

TA_DEVSIZE: 0 <= num

The size in pages of the disk area to be used for the device list entry. Limitation: This attribute may be set only in conjunction with a state change to NEW.

TA_DEVINDEX: 0 <= num

Device index for TA_DEVICE within the device list addressed by TA_CFGDEVICE. This attribute value is used for identification purposes only in getting and setting attribute values relating to particular devices within a BEA Tuxedo filesystem.

TA_STATE:

GET: {VALid}

A GET operation will retrieve run-time information for the selected T_DEVICE object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request.

VALid

The BEA Tuxedo filesystem indicated by TA_CFGDEVICE exists and contains a valid device list. TA_DEVICE is a valid device within that filesystem with the device index telnet lchome3.


 

SET: {NEW | INValid}

A SET operation will update information for the selected T_DEVICE object or add the indicated object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create or reinitialize T_DEVICE object for application. State change allowed only when in the INValid or VALid state. Successful return leaves the object in the VALid state. If this state transition is invoked in the INValid state, then the object is created; otherwise, it is reinitialized. The creation of the first TA_DEVICE device list entry on the TA_CFGDEVICE BEA Tuxedo filesystem will automatically create and initialize the necessary VTOC and UDL structures on TA_CFGDEVICE. The first device list entry created for a particular TA_CFGDEVICE must have equivalent values for the TA_DEVICE attribute.

INValid

Delete T_DEVICE object for application. State change allowed only when in the VALid state. Successful return leaves the object in the INValid state. Note that TA_DEVINDEX 0 is special and must be deleted last.


 

Limitations

None.

T_DOMAIN Class Definition

Overview

The T_DOMAIN class represents global application attributes. These attribute values serve to identify, customize, size, secure, and tune a BEA Tuxedo system application. Many of the attribute values represented here serve as application defaults for other classes represented in this MIB.

There is exactly one object of the T_DOMAIN class for each application. Because of this, there are no key fields defined for this class. A GET operation on this class will always return information representing this single object. Likewise, a SET operation will update it. GETNEXT is not permitted with this class.

Attribute Table

TM_MIB(5): T_DOMAIN Class Definition Attribute Table

Attribute

Type

Permissions

Values

Default

TA_IPCKEY(r)

TA_MASTER(r)

TA_MODEL(r)

long

string

string

rw-r--r--

rwxr-xr--

rw-r--r--

32,769 <= num < 262,144

"LMID1[,LMID2]"

"{SHM | MP}"

N/A

N/A

N/A

TA_STATE

string

rwxr--r--

GET: "{ACT | INA}"

SET: "{NEW | INV | ACT | INA | FIN}"

N/A

N/A






TA_DOMAINID

string

rwxr--r--

string[0..30]

""

TA_PREFERENCES

string

rwxr--r--

string[0..1023]

""

TA_UID

long

rwyr--r--

0 <= num

(1)

TA_GID

long

rwyr--r--

0 <= num

(1 )

TA_PERM

long

rwyr--r--

0001 <= num <= 0777

0666

TA_LICEXPIRE

long

R--R--R--

string[0..78]

N/A

TA_LICMAXUSERS

long

R--R--R--

0 <= num < 32,768

N/A

TA_LICSERIAL

string

R--R--R--

string[0..78]

N/A

TA_MIBMASK

long

rwx------

0 <= num <= 0777

0000






TA_MAXACCESSERS

TA_MAXCONV

TA_MAXGTT

long

long

long

rwyr--r--

rwyr--r--

rwyr--r--

1 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

50

64

100

TA_MAXBUFSTYPE

TA_MAXBUFTYPE

TA_MAXDRT

TA_MAXGROUPS

TA_MAXNETGROUPS

TA_MAXMACHINES

TA_MAXQUEUES

TA_MAXRFT

TA_MAXRTDATA

TA_MAXSERVERS

TA_MAXSERVICES

TA_MAXACLGROUPS

long

long

long

long

long

long

long

long

long

long

long

long

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

rw-r--r--

1 <= num < 32,768

1 <= num < 32,768

0 <= num < 32,768

100 <= num < 32,766

1 <= num <= 8,192

256 <= num < 8,191

1 <= num < 8,192

0 <= num < 32,766

0 <= num < 32,761

1 <= num < 8,192

1 <= num < 32,766

1 <= num = < 16,384

32

16

0

100

8

256

50

0

0

50

100

16,384


TA_CMTRET

string

rwyr--r--

"{COMPLETE | LOGGED}"

"COMPLETE"

TA_LDBAL

string

rwyr--r--

"{Y | N}"

"Y"

TA_NOTIFY

string

rwyr--r--

"{DIPIN | SIGNAL | THREAD | IGNORE}"

"DIPIN"

TA_SYSTEM_ACCESS

string

rwyr--r--

"{FASTPATH | PROTECTED} [,NO_OVERRIDE]"

"FASTPATH"


TA_OPTIONS

string

rwyr--r--

"{[LAN | MIGRATE | ACCSTATS | NO_XA | NO_AA],*}"

""

TA_USIGNAL

string

rw-r--r--

"{SIGUSR1 | SIGUSR2}"

"SIGUSR2"


TA_SECURITY

string

rw-r--r--

"{NONE | APP_PW | USER_AUTH | ACL | MANDATORY_ACL}"

"NONE"

TA_PASSWORD

string

-wx------

string[0..30]

N/A

TA_AUTHSVC

string

rwxr--r--

string[0..15]

""


TA_SCANUNIT

long

rwxr-xr--

0 <= num <= 60

102

TA_BBLQUERY

long

rwxr-xr--

0 <= num <32,768

3003

TA_BLOCKTIME

long

rwxr-xr--

0 <= num < 32,768

603

TA_DBBLWAIT

long

rwxr-xr--

0 <= num < 32,768

203

TA_SANITYSCAN

long

rwxr-xr--

0 <= num < 32,768

1203


TA_CURDRT

TA_CURGROUPS

TA_CURMACHINES

TA_CURQUEUES

TA_CURRFT

TA_CURRTDATA

TA_CURSERVERS

TA_CURSERVICES

TA_CURSTYPE

TA_CURTYPE

long

long

long

long

long

long

long

long

long

long

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

TA_HWDRT

TA_HWGROUPS

TA_HWMACHINES

TA_HWQUEUES

TA_HWRFT

TA_HWRTDATA

TA_HWSERVERS

TA_HWSERVICES

long

long

long

long

long

long

long

long

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

r--r--r--

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

0 <= num < 32,768

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A


TA_SEC_PRINCIPAL_NAME

string

rwxr--r--

string[0..511]

""

TA_SEC_PRINCIPAL_LOCATION

string

rwxr--r--

string[0..511]

""

TA_SEC_PRINCIPAL_PASSVAR

string

rwxr--r--

string[0..511]

""

TA_SIGNATURE_AHEAD

long

rwxr--r--

1 <= num <= 2147483647

3600

TA_SIGNATURE_BEHIND

long

rwxr--r--

1 <= num <= 2147483647

604800

TA_SIGNATURE_REQUIRED

string

rwxr--r--

"{Y | N}"

"N"

TA_ENCRYPTION_REQUIRED

string

rwxr--r--

"{Y | N}"

"N"

(r)—required field for object creation (SET TA_STATE NEW)


 

1UID and GID as known to the UNIX system
2num must be a multiple of 5
3Specify num so that num times TA_SCANUNIT is approximately "Default"

Attribute Semantics

TA_IPCKEY: 32,769 <= num < 262,144

Numeric key for the well-known address in a BEA Tuxedo system 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.

TA_MASTER: LMID1[,LMID2]

Master (LMID1) and backup (LMID2) logical machine identifiers. The master identifier (LMID1) must correspond to the local machine for INActive applications. SHM mode applications (see TA_MODEL below) may set only the master logical machine identifier. Modifications to this attribute value in an ACTive MP application (see TA_MODEL 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 TA_MASTER attribute in a running MP 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 reestablished 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 BEA Tuxedo 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 TA_MASTER attribute must preserve this relationship.

TA_MODEL: {SHM | MP}

Configuration type. SHM specifies a single machine configuration; only one T_MACHINE object may be specified. MP specifies a multi-machine or network configuration; MP must be specified if a networked application is being defined.

TA_STATE:

GET: {ACTive | INActive}

A GET operation will retrieve configuration and run-time information for the T_DOMAIN object. The following states indicate the meaning of a TA_STATE returned in response to a GET request.

ACTive

T_DOMAIN object defined and the master machine is active.

INActive

T_DOMAIN object defined and application is inactive.


 

SET: {NEW | INValid | ACTive | INActive | FINactive}

A SET operation will update configuration and run-time information for the T_DOMAIN object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create T_DOMAIN object for application. State change allowed only when in the INValid state. Successful return leaves the object in the INActive state. Note that this state change will also create a NEW T_MACHINE object with TA_LMID inferred from TA_MASTER, TA_PMID based on the local system name, and TA_TUXCONFIG and TA_TUXDIR determined from the environment variables TUXCONFIG and TUXDIR respectively. Other configurable attributes of the T_MACHINE class may be set at this time by including values in the T_DOMAIN NEW request. If a value for TA_APPDIR is not specified, then it will default to the current directory.

unset

Modify T_DOMAIN object. Allowed only when in the ACTive or INActive state. Successful return leaves the object state unchanged.

INValid

Delete T_DOMAIN object for application. State change allowed only when in the INActive state. Successful return leaves the object in the INValid state.

ACTive

Activate administrative processes (DBBL, BBL, etc.) on the master machine. For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). State change allowed only when in the INActive state. Successful return leaves the object in the INActive state.

INActive

Deactivate administrative processes (DBBL, BBL, etc.) on the master machine. State change allowed only when in the ACTive state. Successful return leaves the object in the INActive state.

FINactive

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 allowed only when in the ACTive state. Successful return leaves the object in the INActive state.


 

TA_DOMAINID: string[0..30]

Domain identification string.

TA_PREFERENCES: string[0..1023]

Application defined field. This field is used by the BEA Tuxedo system /Admin GUI product to store and save GUI display preferences.

TA_UID: 0 <= num

Default attribute setting for newly configured objects in the T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_GID: 0 <= num

Default attribute setting for newly configured objects in the T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_PERM: 0001 <= num <= 0777

Default attribute setting for newly configured objects in the T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_LICEXPIRE: string[0..78]

Expiration date for the binary on that machine or a 0-length string if binary is not a BEA Tuxedo system master binary.

TA_LICMAXUSERS: 0 <= num < 32,768

Licensed maximum number of users on that machine or -1 if binary is not a BEA Tuxedo system master binary.

TA_LICSERIAL: string [0..78]

Serial number of license.

TA_MIBMASK: 0 <= num <= 0777

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 this reference page. For example, a setting of 0003 disallows all updates to users other than the administrator or the operator.

TA_MAXACCESSERS: 1 <= num < 32,768

Default maximum number of clients and servers that can be simultaneously connected to the bulletin board on any particular machine in this application. If not specified, the default maximum number is 50. The T_DOMAIN value for this attribute can be overridden in the T_MACHINE class on a per-machine basis.

System administration processes, such as the BBL, restartsrv, cleanupsrv, tmshutdown(), and tmadmin(), need not be accounted for in this value, but the DBBL, all bridge processes, all system-supplied and application server processes, and all potential client processes at a particular site need to be counted. (Examples of system-supplied servers are AUTHSVR, TMQUEUE, TMQFORWARD, TMUSREVT, TMSYSEVT, TMS—see T_GROUP TA_TMSNAME attribute, TMS_QM, GWTDOMAIN, and WSL.) If the application is booting workstation listeners (WSLs) at a particular site, both the WSLs and the number of potential workstation handlers (WSHs) that may be booted need to be counted.

Note that for BEA Tuxedo pre-release 7.1 (6.5 or earlier), both the TA_MAXACCESSERS and TA_MAXSERVERS attributes for an application play a part in the user license checking scheme. Specifically, a machine is not allowed to boot if the number of TA_MAXACCESSERS for that machine + the number of TA_MAXACCESSERS for the machine (or machines) already running in the application is greater than the number of TA_MAXSERVERS + user licenses for the application. Thus, the total number of TA_MAXACCESSERS for an application must be less than or equal to the number of TA_MAXSERVERS + user licenses for the application.

Note also that the user license checking scheme in BEA Tuxedo release 7.1 or later considers only the following two factors when performing its checks: the number of user licenses for an application and the number of licenses currently in use for the application. When all user licenses are in use, no new clients are allowed to join the application.

Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_MAXCONV: 0 <= num < 32,768

Maximum number of simultaneous conversations in which clients and servers on any particular machine in this application can be involved. If not specified, the default is 64 if any conversational servers are defined in the T_SERVER class, or 1 otherwise. The maximum number of simultaneous conversations per server is 64. The T_DOMAIN value for this attribute can be overridden in the T_MACHINE class on a per-machine basis.

Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_MAXGTT: 0 <= num < 32,768

Maximum number of simultaneous global transactions in which any particular machine in this application can be involved. If not specified, the default is 100. The T_DOMAIN value for this attribute can be overridden in the T_MACHINE class on a per-machine basis.

Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.

TA_MAXBUFSTYPE: 1 <= num < 32,768

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

TA_MAXBUFTYPE: 1 <= num < 32,768

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

TA_MAXDRT: 0 <= num < 32,768

Maximum number of routing table entries that can be accommodated in the bulletin board routing table. One entry per T_ROUTING class object is required. Additional entries should be allocated to allow for run-time growth.

TA_MAXGROUPS: 100 <= num < 32,766

Maximum number of server groups that can be accommodated in the bulletin board server group table. Limitation: BEA Tuxedo 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.

TA_MAXNETGROUPS: 1 <= num < 8,192

Specifies the maximum number of configured network groups to be accommodated in the NETWORK section of the TUXCONFIG file. This value must be greater than or equal to 1 and less than 8192. If not specified, the default is 8.

TA_MAXMACHINES: 256 <= num < 8,191

Maximum number of machines that can be accommodated in the bulletin board machine table. Limitation: BEA Tuxedo 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.

TA_MAXQUEUES: 1 <= num < 8,192

Maximum number of queues to be accommodated in the bulletin board queue table. Limitation: release 4.2.2 and earlier sites may join an active application only if the setting for TA_MAXQUEUES is equal to the setting for TA_MAXSERVERS.

TA_MAXRFT: 0 <= num < 32,768

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 TA_RANGES specification is required plus one additional entry per T_ROUTING class object. Additional entries should be allocated to allow for run-time growth.

TA_MAXRTDATA: 0 <= num < 32,761

Maximum string pool space to be accommodated in the bulletin board string pool table. Strings and carrays specified within TA_RANGES values are stored in the string pool. Additional space should be allocated to allow for run-time growth.

TA_MAXSERVERS: 1 <= num < 8,192

Maximum number of servers to be accommodated in the bulletin board server table for this application. If not specified, the default is 50.

All instances of system-supplied and application servers available to an application need to be accounted for in the bulletin board server table, which is a global table, meaning that the same server table resides on each machine in the application. Examples of system-supplied servers are AUTHSVR, TMQUEUE, TMQFORWARD, TMUSREVT, TMSYSEVT, TMS (see T_GROUP TA_TMSNAME attribute), TMS_QM, GWTDOMAIN, and WSL.

Administration of each BEA Tuxedo system site adds approximately one system-supplied server. Additionally, the DBBL process and all BBL, bridge, and WSH processes must be accounted for in the TA_MAXSERVERS value.

TA_MAXSERVICES: 1 <= num < 32,766

Maximum number of services to be accommodated in the bulletin board service table. If not specified, the default is 100.

Allowances should be made in setting this attribute for system-supplied servers offering services for administrative purposes. Administration of each BEA Tuxedo system site adds approximately five services. Other administrative components such as Workstation, /Q, and /DM may also add administrative services that should be accounted for.

TA_MAXACLGROUPS: 1 <= num < 16,384

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

TA_CMTRET: {COMPLETE | LOGGED}

Initial setting of the TP_COMMIT_CONTROL characteristic for all client and server processes in a BEA Tuxedo system application. LOGGED initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_LOGGED; otherwise, it is initialized to TP_CMT_COMPLETE. See the description of the BEA Tuxedo System ATMI function tpscmt() for details on the setting of this characteristic.

Limitation: Run-time modifications to this attribute do not affect active clients and servers.

TA_LDBAL: {Y | N}

Load balancing is/will be on ("Y") or off ("N").

Limitation: Run-time modifications to this attribute do not affect active clients and servers.

TA_NOTIFY: {DIPIN | SIGNAL | THREAD | IGNORE}

Default notification detection method to be used by the system for unsolicited messages sent to client processes. This default can be overridden on a per-client basis using the appropriate tpinit() 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() function.

The value DIPIN specifies that dip-in-based notification detection should be used. This means that the system will detect notification messages only 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 is the default notification detection method.

The value SIGNAL 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 THREAD specifies that THREAD notification should be used. This means that the system dedicates a separate thread for the receipt of unsolicited messages and dispatches the unsolicited message handler in that thread. Only one unsolicited message handler executes at one time per BEA Tuxedo application association. This value is allowed only on platforms that offer support for multithreading. COBOL clients cannot use THREAD notification, and will default to DIPIN if THREAD is in effect.

The value IGNORE 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() time should receive unsolicited messages.

Limitations: Run-time modifications to this attribute do not affect active clients. All signaling of native client processes is done by administrative system processes and not by application processes. Therefore, only native clients running with the same UNIX system user identifier as the application administrator can be notified using the SIGNAL method. Workstation clients may use the SIGNAL method, regardless of which user identifier they are running under.

Note: The SIGNAL notification method is not available for MS-DOS clients.

TA_SYSTEM_ACCESS: {FASTPATH | PROTECTED}[,NO_OVERRIDE]

Default mode used by BEA Tuxedo system libraries within application processes to gain access to BEA Tuxedo system's internal tables. FASTPATH specifies that BEA Tuxedo system's internal tables are accessible by BEA Tuxedo system libraries via unprotected shared memory for fast access. PROTECTED specifies that BEA Tuxedo system's internal tables are accessible by BEA Tuxedo system libraries via protected shared memory for safety against corruption by application code. NO_OVERRIDE can be specified to indicate that the mode selected cannot be overridden by an application process using flags available for use with tpinit(3c) or TPINITIALIZE(3cbl).

Limitations: (1) Updates to this attribute value in a running application affect only newly started clients and newly configured T_SERVER objects.
(2) Setting TA_SYSTEM_ACCESS to PROTECTED may not be effective for multithreaded servers because it is possible that while one thread is executing BEA Tuxedo code, which means it is attached to the bulletin board, another thread might be executing user code. The BEA Tuxedo system cannot prevent such situations.

TA_OPTIONS: {[LAN | MIGRATE | ACCSTATS | NO_XA | NO_AA],*}

Comma-separated list of application options in effect. Valid options are defined below:

LAN—networked application.

MIGRATE—allow server group migration.

ACCSTATS—exact statistics (SHM mode only).

NO_XA—do not allow XA transactions.

NO_AA—the auditing and authorization plugin functions will not be called.

Limitation: Only the ACCSTATS may be set or reset in an active application.

TA_USIGNAL: {SIGUSR1 | SIGUSR2}

Signal to be used for signal-based notification (see TA_NOTIFY above).

TA_SECURITY: {NONE | APP_PW | USER_AUTH | ACL | MANDATORY_ACL}

Type of application security. A 0-length string value or NONE for this attribute indicates that security is/will be turned off. The identifier APP_PW indicates that application password security is to be enforced (clients must provide the application password during initialization). Setting this attribute requires a non-0 length TA_PASSWORD attribute. The identifier USER_AUTH is similar to APP_PW but, in addition, indicates that per-user authentication will be done during client initialization. The identifier ACL is similar to USER_AUTH but, in addition, 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 identifier MANDATORY_ACL is similar to ACL but permission is denied if an associated ACL is not found for the name.

Note: If the NO_AA value is enabled in the TA_OPTIONS parameter, the security parameters NONE, APP_PW, and USER_AUTH will continue to work properly—except that no authorization or auditing will take place. The remaining modes of security, ACL and MANDATORY_ACL will continue to work properly—but will only use the default BEA security mechanism.

TA_PASSWORD: string[0 . . 30]

Clear text application password. This attribute is ignored if the TA_SECURITY attribute is set to nothing. The system automatically encrypts this information on behalf of the administrator.

TA_AUTHSVC: string[0..15]

Application authentication service invoked by the system for each client joining the system. This attribute is ignored if the TA_SECURITY attribute is set to nothing or to APP_PW.

TA_SCANUNIT: 0 <= num <= 60 (multiple of 5)

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 TA_BBLQUERY, TA_BLOCKTIME, TA_DBBLWAIT, and TA_SANITYSCAN attributes 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.

TA_BBLQUERY: 0 <= num < 32,768

Multiplier of the TA_SCANUNIT attribute indicating time between DBBL status checks on registered BBLs. The DBBL checks to ensure that all BBLs have reported in within the TA_BBLQUERY 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. This attribute value should be set to at least twice the value set for the TA_SANITYSCAN attribute value (see below).

TA_BLOCKTIME: 0 <= num < 32,768

Multiplier of the TA_SCANUNIT attribute 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.

TA_DBBLWAIT: 0 <= num < 32,768

Multiplier of the TA_SCANUNIT attribute 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.

TA_SANITYSCAN: 0 <= num < 32,768

Multiplier of the TA_SCANUNIT attribute 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 (MP mode only). Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default.

TA_CURDRT: 0 <= num < 32,768

Current number of in use bulletin board routing table entries.

TA_CURGROUPS: 0 <= num < 32,768

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

TA_CURMACHINES: 0 <= num < 32,768

Current number of configured machines.

TA_CURQUEUES: 0 <= num < 32,768

Current number of in use bulletin board queue table entries.

TA_CURRFT: 0 <= num < 32,768

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

TA_CURRTDATA: 0 <= num < 32,768

Current size of routing table string pool.

TA_CURSERVERS: 0 <= num < 32,768

Current number of in use bulletin board server table entries.

TA_CURSERVICES: 0 <= num < 32,768

Current number of in use bulletin board service table entries.

TA_CURSTYPE: 0 <= num < 32,768

Current number of in use bulletin board subtype table entries.

TA_CURTYPE: 0 <= num < 32,768

Current number of in use bulletin board type table entries.

TA_HWDRT: 0 <= num < 32,768

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

TA_HWGROUPS: 0 <= num < 32,768

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

TA_HWMACHINES: 0 <= num < 32,768

High water number of configured machines.

TA_HWQUEUES: 0 <= num < 32,768

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

TA_HWRFT: 0 <= num < 32,768

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

TA_HWRTDATA: 0 <= num < 32,768

High water size of routing table string pool.

TA_HWSERVERS: 0 <= num < 32,768

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

TA_HWSERVICES: 0 <= num < 32,768

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

TA_SEC_PRINCIPAL_NAME: string[0..511]

Security principal name identification string to be used for authentication purposes by an application running BEA Tuxedo 7.1 or later software. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character). The principal name specified for this attribute becomes the identity of one or more system processes running in this domain.

TA_SEC_PRINCIPAL_NAME can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. A principal name at a particular configuration level can be overridden at a lower level. If TA_SEC_PRINCIPAL_NAME is not specified at any of these levels, the principal name for the application defaults to the TA_DOMAINID string for this domain.

Note that TA_SEC_PRINCIPAL_NAME is one of a trio of attributes, the other two being TA_SEC_PRINCIPAL_LOCATION and TA_SEC_PRINCIPAL_PASSVAR. The latter two attributes pertain to opening decryption keys during application booting for the system processes running in a BEA Tuxedo 7.1 or later application. When only TA_SEC_PRINCIPAL_NAME is specified at a particular level, the system sets each of the other two attributes to a NULL (zero length) string.

TA_SEC_PRINCIPAL_LOCATION: string[0..511]

Location of the file or device where the decryption (private) key for the principal specified in TA_SEC_PRINCIPAL_NAME resides. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_LOCATION can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_PASSVAR is optional; if not specified, the system sets it to a NULL—zero length—string.)

TA_SEC_PRINCIPAL_PASSVAR: string[0..511]

Variable in which the password for the principal specified in TA_SEC_PRINCIPAL_NAME is stored. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_PASSVAR can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_LOCATION is optional; if not specified, the system sets it to a NULL—zero length—string.)

During initialization, the administrator must provide the password for each of the decryption keys configured with TA_SEC_PRINCIPAL_PASSVAR. The system automatically encrypts the password entered by the administrator and assigns each encrypted password to the associated password variable.

TA_SIGNATURE_AHEAD: 1 <= num <= 2147483647

Number of seconds into the future that a digital signature's timestamp is allowed to be, when compared to the local machine's clock. If not specified, the default is 3600 seconds (one hour). This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_SIGNATURE_BEHIND: 1 <= num <= 2147483647

Number of seconds into the past that a digital signature's timestamp is allowed to be, when compared to the local machine's clock. If not specified, the default is 604800 seconds (one week). This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_SIGNATURE_REQUIRED: {Y | N}

If set to Y, every process running in this domain requires a digital signature on its input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_SIGNATURE_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting SIGNATURE_REQUIRED to Y at a particular level means that signatures are required for all processes running at that level or below.

TA_ENCRYPTION_REQUIRED: {Y | N}

If set to Y, every process running in this domain requires an encrypted input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_ENCRYPTION_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting TA_ENCRYPTION_REQUIRED to Y at a particular level means that encryption is required for all processes running at that level or below.

Limitations

Many attributes of this class are tunable only when the application is inactive. Therefore, use of the ATMI interface routines to administer the application is not possible. The function tpadmcall() is being provided as a means of configuring or reconfiguring an unbooted application. This interface may only be used for configuration (SET operations) in an inactive application and only on the site being configured as the master site for the application. Once an initial configuration is created and activated, administration is available through the standard ATMI interfaces as described in MIB(5).

T_FACTORY MIB

Overview

The T_FACTORY MIB class represents occurrences of factories registered with the FactoryFinder. The available factories for the application are reflected in this MIB and can be shown to the administrator via the Administration Console or command-line tools. The scope is global.

Attribute Table

T_FACTORY Attributes

Attribute

Use

Type

Permissions

Values

Default

TA_STATE

k

string

R--R--R--

GET:"{ACT}"

NA

TA_FACTORYID

k

string

R--R--R--

string
[1...256]

NA

TA_INTERFACENAME

k

string

R--R--R--

string
[1...128]

NA

( k ) - GET key field

Attributes Semantics

TA_STATE

GET: {ACTive }

A GET operation will retrieve configuration and run-time information for the selected T_FACTORY objects.
The following state indicates the meaning of a TA_STATE returned in response to a GET request:

ACTive

The T_FACTORY object is registered with the FactoryFinder.


 

TA_FACTORY

The registered ID for the factory.

TA_INTERFACENAME

The fully qualified interface name for the factory. 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. See CORBA 2.1 Specification Section 7.6 for details.


 

T_GROUP Class Definition

Overview

The T_GROUP class represents application attributes pertaining to a particular server group. These attribute values represent group identification, location, and DTP information.

Attribute Table

TM_MIB(5): T_GROUP Class Definition Attribute Table

Attribute

Type

Permissions

Values

Default

TA_SRVGRP(r)(*)

TA_GRPNO(k)(r)

TA_LMID(k)(r)

string

long

string

rU-r--r--

rU-r--r--

rwyr--r--

string[1. .30]

1 <= num < 30,000

"LMID1[,LMID2]"

N/A

N/A

N/A

TA_STATE(k)

string

rwxr-xr--

GET: "{ACT | INA | MIG}"

SET: "{NEW | INV | ACT | RAC |INA | MIG}"

N/A

N/A

TA_CURLMID(k)

string

R--R--R--

LMID

N/A

TA_ENVFILE

string

rwyr--r--

string[0..78]

""

TA_OPENINFO

TA_CLOSEINFO

TA_TMSCOUNT

TA_TMSNAME(k)

string

string

long

string

rwyr--r--

rwyr--r--

rw-r--r--

rw-r--r--

string[0..256]

string[0..256]

0 or 2 <= num < 11

string[0..78]

""

""

3

""

TA_SEC_PRINCIPAL_NAME

TA_SEC_PRINCIPAL_LOCATION

TA_SEC_PRINCIPAL_PASSVAR

TA_SIGNATURE_REQUIRED

TA_ENCRYPTION_REQUIRED

string

string

string

string

string

rwxr--r--

rwxr--r--

rwxr--r--

rwxr--r--

rwxr--r--

string[0..511]

string[0..511]

string[0..511]

"{Y|N}"

"{Y|N}"

""

""

""

"N"

"N"

(k)—GET key field
(r)—required field for object creation (SET TA_STATE NEW)
(*)—GET/SET key, one or more required for SET operations


 

Attribute Semantics

TA_SRVGRP: string[1..30]

Logical name of the server group. The group name must be unique within all group names in the T_GROUP class and TA_LMID values in the T_MACHINE class. Server group names cannot contain an asterisk (*), comma, or colon.

TA_GRPNO: 1 <= num < 30,000

Group number associated with this server group.

TA_LMID: LMID1[,LMID2]

Primary machine logical machine identifier for this server group (LMID1) and optional secondary logical machine identifier (LMID2). The secondary LMID indicates the machine to which the server group can be migrated (if the MIGRATE option is specified in the T_DOMAIN:TA_OPTIONS 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 TA_CURLMID attribute. Logical machine identifiers specified with the TA_LMID attribute must be already configured. Limitation: Modifications to this attribute for an active object may only change the backup LMID designation for the group.

TA_STATE:

GET: {ACTive | INActive | MIGrating}

A GET operation will retrieve configuration and run-time information for the selected T_GROUP object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request.

ACTive

T_GROUP object defined and active (TMS and/or application servers). Server groups with non NULL strings for the TA_TMSNAME 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

T_GROUP object defined and inactive.

MIGrating

T_GROUP object defined and currently in a state of migration to the secondary logical machine. The secondary logical machine is the one listed in TA_LMID that does not match TA_CURLMID. This state is ACTive equivalent for the purpose of determining permissions.


 

SET: {NEW | INValid | ACTive | ReACtivate | INActive | MIGrating}

A SET operation will update configuration and run-time information for the selected T_GROUP object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create T_GROUP object for application. State change allowed only when in the INValid state. Successful return leaves the object in the INActive state.

unset

Modify an existing T_GROUP object. This combination is allowed only when in the ACTive or INActive state. Successful return leaves the object state unchanged.

INValid

Delete T_GROUP object for application. State change allowed only when in the INActive state. Successful return leaves the object in the INValid state.

ACTive

Activate the T_GROUP object. State change allowed only when in the INActive or MIGrating state. For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x).

If the group is currently in the INActive state, then TMS and application servers (subject to restriction by TA_FLAGS settings) 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 state, then the active secondary logical machine (identified as the alternate to TA_CURLMID in the TA_LMID list) is used to start TMS and application servers if it is active. Otherwise, the request fails. The TMIB_NOTIFY TA_FLAG value should be used when activating a server group if status on individual servers is required.

Successful return leaves the object in the ACTive state.

ReACtivate

Identical to a transition to the ACTive state except that this state change is also allowed in the ACTive state in addition to being allowed in the INActive and MIGrating states.

The TMIB_NOTIFY TA_FLAG value should be used when reactivating a server group if status on individual servers is required.

INActive

Deactivate the T_GROUP object. TMS and application servers (subject to restriction by TA_FLAGS settings) are deactivated. State change allowed only when in the ACTive or MIGrating state. Successful return leaves the object in the INActive state.

The TMIB_NOTIFY TA_FLAG value should be used when deactivating a server group if status on individual servers is required.

MIGrating

Deactivate the T_GROUP object on its active primary logical machine (TA_CURLMID) and prepare the group to be migrated to the secondary logical machine. State change allowed only when in the ACTive state. Successful return leaves the object in the MIGrating state.

UnAVailable

Suspend all application services in the group. (Note: Individual services can be suspended through the T_SVCGROUP class.) A SET operation to this state is allowed only when the group is in the ACTive state. The operation leaves the group in the ACTive state, but with all its application services in a suspended state. Limitation: Operation will fail in a mixed-release application where any pre-release 6.4 machine is active.

AVaiLable

Unsuspend all application services in the group marked as suspended. A SET operation to this state value is allowed only when the group is in the ACTive state. The operation leaves the group in the ACTive state.


 

Limitation: Operation will fail in a mixed-release application where any pre-release 6.4 machine is active.

TA_CURLMID: LMID

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

TA_ENVFILE: string[0..78]

Environment file for servers running in this group. If the value specifies an invalid filename, no values are added to the environment. the value of string is placed in the environment.

When booted, local servers inherit the environment of tmboot(1) and remote servers (not on the MASTER) inherit the environment of tlisten(1). TUXCONFIG, TUXDIR, and APPDIR are also put in the environment when a server is booted based on the information in the associated T_GROUP object.

PATH is set in the environment to:

APPDIR:TUXDIR/bin:/bin:/usr/bin:<path>

where <path> is the value of the first PATH= line in the machine environment file, if one exists (subsequent PATH= lines is ignored). This PATH is used as a search path for servers that are specified with a simple or relative pathname (that is, one that doesn't begin with slash).

LD_LIBRARY_PATH is set in the environment to:

APPDIR:TUXDIR/lib:/lib:/usr/lib:<lib>

where <lib> is the value of the first LD_LIBRARY_PATH= line appearing in the machine environment file, if one exists (subsequent LD_LIBRARY_PATH= lines are ignored).

As part of server initialization (before tpsvrinit(3c) is called), a server reads and exports variables from both the machine and server ENVFILE files. If a variable is set in both the machine and server ENVFILE, the value in the server ENVFILE will override the value in the machine ENVFILE with the exception of PATH which is appended. A client processes only the machine ENVFILE file. When the machine and server ENVFILE files are processed, lines that are not of the form <ident>= is ignored, where <ident> contains only underscore or alphanumeric characters.

If a PATH= line is encountered, PATH is set to:

APPDIR:TUXDIR/bin:/bin:/usr/bin:<path>

where <path> is the value of the first PATH= line appearing in the environment file (subsequent PATH= lines are ignored). If PATH appears in both the machine and server files, then <path> is defined as <path1>:<path2> where <path1> is from the machine ENVFILE and <path2> is from the server ENVFILE. If a LD_LIBRARY_PATH= line is encountered, LD_LIBRARY_PATH is set to:

APPDIR:TUXDIR/lib:/lib:/usr/lib:<lib>

where <lib> is the value of the first LD_LIBRARY_PATH= line appearing in the environment file (subsequent LD_LIBRARY_PATH= lines are ignored). Attempts to reset TUXDIR, APPDIR, or TUXCONFIG are ignored and a warning is displayed if the value does not match the corresponding T_GROUP attribute value. Limitation: Modifications to this attribute for an active object DO not affect running servers or clients.

TA_OPENINFO: string[0..256]

The resource manager instance-dependent information needed when opening the resource manager for this group. The value must be enclosed in double quotes and must be less than or equal to 256 characters in length.

If a non NULL string other than TMS is specified for the TA_TMSNAME attribute, the TA_OPENINFO attribute value provides the resource manager dependent information needed when initiating access to the resource manager. Otherwise, the TA_OPENINFO attribute value is ignored.

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

The format of the TA_OPENINFO string is dependent on the requirements of the vendor providing the underlying resource manager. The information required by the vendor must be prefixed with the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).

For BEA Tuxedo /Q databases, the format is:

# On UNIX #
OPENINFO = "TUXEDO/QM:qmconfig:qspace"

# On Windows #
OPENINFO = "TUXEDO/QM:qmconfig;qspace"

# In AS/400 environment #
OPENINFO = "TUXEDO/QM:qmconfig;qspace"

# In OpenVMS environment #
OPENINFO = "TUXEDO/QM,[a.b.c]qmconfig,qspace"

where TUXEDO/QM is the published name of the BEA Tuxedo /Q XA interface, qmconfig is replaced with the name of the QMCONFIG (see qmadmin(1)) on which the queue space resides, and qspace is replaced with the name of the queue space. For Windows and AS/400, the separator after qmconfig must be a semicolon (;). For OpenVMS, the separator after TUXEDO/QM and after qmconfig must be a comma (,).

For other vendors' databases, the format of the TA_OPENINFO string is specific to the particular vendor providing the underlying resource manager.

Limitation: Run-time modifications to this attribute will not affect active servers in the group.

TA_CLOSEINFO: string[0..256]

The resource manager instance-dependent information needed when closing the resource manager for this group. The value must be enclosed in double quotes and must be less than or equal to 256 characters in length. Note that a TA_CLOSEINFO string is not used for BEA Tuxedo /Q databases.

If a non NULL string other than TMS is specified for the TA_TMSNAME attribute, the TA_CLOSEINFO attribute value provides the resource manager-dependent information needed when terminating access to the resource manager. Otherwise, the TA_CLOSEINFO attribute value is ignored.

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

The format of the TA_CLOSEINFO string is dependent on the requirements of the vendor providing the underlying resource manager. The information required by the vendor must be prefixed with the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).

Limitation: Run-time modifications to this attribute will not affect active servers in the group.

TA_TMSCOUNT: 0 or 2 <= num < 11

If a non NULL string is specified for the TA_TMSNAME attribute, then this attribute value indicates the number of transaction manager servers to start for the associated group. Otherwise, this attribute value is ignored.

TA_TMSNAME: string[0..78]

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(), and ended with tpcommit()/tpabort()).

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 TLOGDEVICE 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.

TA_SEC_PRINCIPAL_NAME: string[0..511]

Security principal name identification string to be used for authentication purposes by an application running BEA Tuxedo 7.1 or later software. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character). The principal name specified for this attribute becomes the identity of one or more system processes running in this group.

TA_SEC_PRINCIPAL_NAME can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. A principal name at a particular configuration level can be overridden at a lower level. If TA_SEC_PRINCIPAL_NAME is not specified at any of these levels, the principal name for the application defaults to the TA_DOMAINID string for this domain.

Note that TA_SEC_PRINCIPAL_NAME is one of a trio of attributes, the other two being TA_SEC_PRINCIPAL_LOCATION and TA_SEC_PRINCIPAL_PASSVAR. The latter two attributes pertain to opening decryption keys during application booting for the system processes running in a BEA Tuxedo 7.1 or later application. When only TA_SEC_PRINCIPAL_NAME is specified at a particular level, the system sets each of the other two attributes to a NULL (zero length) string.

TA_SEC_PRINCIPAL_LOCATION: string[0..511]

Location of the file or device where the decryption (private) key for the principal specified in TA_SEC_PRINCIPAL_NAME resides. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_LOCATION can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_PASSVAR is optional; if not specified, the system sets it to a NULL—zero length—string.)

TA_SEC_PRINCIPAL_PASSVAR: string[0..511]

Variable in which the password for the principal specified in TA_SEC_PRINCIPAL_NAME is stored. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_PASSVAR can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_LOCATION is optional; if not specified, the system sets it to a NULL—zero length—string.)

During initialization, the administrator must provide the password for each of the decryption keys configured with TA_SEC_PRINCIPAL_PASSVAR. The system automatically encrypts the password entered by the administrator and assigns each encrypted password to the associated password variable.

TA_SIGNATURE_REQUIRED: {Y | N}

If set to Y, every process running in this group requires a digital signature on its input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_SIGNATURE_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting SIGNATURE_REQUIRED to Y at a particular level means that signatures are required for all processes running at that level or below.

TA_ENCRYPTION_REQUIRED: {Y | N}

If set to Y, every process running in this group requires an encrypted input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_ENCRYPTION_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting TA_ENCRYPTION_REQUIRED to Y at a particular level means that encryption is required for all processes running at that level or below.

Limitations

None.

T_IFQUEUE Class

Overview

The T_IFQUEUE MIB class represents run-time attributes of an interface as it pertains to a particular server queue (T_QUEUE) in a CORBA environment. This is primarily a read-only class providing access to the inherited configuration attributes of an interface as well as statistics relating to the interface on the queue. Additionally, this class gives administrators finer granularity in suspending and activating interfaces. This class provides the link between an interface name and the server processes capable of processing method invocations on the interface, that is, TA_RQADDR can be used as a key search field on the T_SERVER class.

Attribute Table

T_IFQUEUE Class Definition Attribute Table

Attribute

Usage

Type

Permissions

Values

Default

TA_INTERFACENAME

*

string

R--R--R--

string[1..128]

N/A

TA_SRVGRP

*

string

R--R--R--

string[1..30]

N/A

TA_RQADDR

*

string

R--R--R--

string[1..30]

N/A

TA_STATE

k

string

R-XR-XR--

GET: "{ACT|SUS|PAR}"
SET: "{ACT|SUS}"

N/A

TA_AUTOTRAN


string

R--R--R--

"{Y|N}"

N/A

TA_LOAD


long

R--R--R--

1 <= num < 32K

N/A

TA_PRIO


long

R--R--R--

1<= num < 101

N/A

TA_TIMEOUT


long

R--R--R--

0 <= num

N/A

TA_TRANTIME


long

R--R--R--

0 <= num

N/A

TA_FBROUTINGNAME


string

R--R--R--

string[1...15]

N/A

TA_LMID

k

string

R--R--R--

LMID

N/A

TA_NUMSERVERS


long

R--R--R--

0 <= num

N/A

TA_TPPOLICY


string

R--R--R--

"{method | transaction | process}"

N/A

TA_TXPOLICY


string

R-R-R--

"{always | never | optional | ignore}"

N/A

TA_NCOMPLETED

l

long

R-XR-XR--

0 <= num

N/A

TA_NQUEUED

l

long

R--R--R--

0 <= num

N/A

TA_CUROBJECTS

l

long

R--R--R--

0 <= num

N/A

TA_CURTRANSACTIONS

l

long

R--R--R--

0 <= num

N/A

( k ) - GET key field
( l ) - local Field
( * ) - GET/SET key, one or more required for SET operations


Attribute Semantics

TA_INTERFACENAME: string[1..128]

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 CORBA 2.1 Specification Section 7.6 for details.

TA_SRVGRP: string[0..30]

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

TA_RQADDR: string[1..30]

Symbolic address of the request queue for an active server offering this interface. See T_SERVER:TA_RQADDR for more information on this attribute.

TA_STATE:

GET: {ACTive | SUSpended | PARtitioned}

A GET operation will retrieve configuration information for the selected T_IFQUEUE objects. The following states indicate the meaning of a TA_STATE returned in response to a GET request. States not listed will not be returned.

ACTive

T_IFQUEUE object represents an available interface in the running system.

SUSpended

T_IFQUEUE object represents a currently suspended interface in the running system.

PARtitioned

T_IFQUEUE object represents a currently partitioned interface in the running system.

SET: { ACTive | SUSpended}

The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

ACTive

Activate the T_IFQUEUE object. State change only allowed when in the SUSpended state. Successful return leaves object in ACTive state.

SUSpended

Suspend the T_IFQUEUE object. State change only allowed when in the ACTive state. Successful return leaves object in SUSpended state.

Limitation: Dynamic advertisement of interfaces (i.e., state change from INActive or INValid to ACTive) is not supported, nor is unadvertisement (i.e., state change from ACTive to INActive).

TA_AUTOTRAN: { Y | N }

Signifies whether a transaction will be automatically started for invocations made outside a transaction context. See T_INTERFACE description of this attribute for discussion of limitations regarding this attribute.

TA_LOAD: 1 <= num <= 32K

This T_INTERFACE object imposes the indicated load on the system. Interface loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request.

TA_PRIO: 1 <= num <= 101

This T_INTERFACE object has the indicated dequeuing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests will be handled first.

TA_TIMEOUT: 0 <= num

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.

TA_TRANTIME: 0 <= num

Transaction timeout value in seconds for transactions automatically started for this T_INTERFACE object. Transactions are started automatically when a requests not in transaction mode is received and the T_INTERFACE:TA_AUTOTRAN attribute value for the interface is "Y".

TA_FBROUTINGNAME: string[1..15]

The factory-based routing criteria associated with this interface.

TA_LMID: LMID

Current logical machine on which the queue offering this interface is located.

TA_NUMSERVERS: 0 <= num

Number of corresponding servers offering this interface on this queue.

TA_TPPOLICY: { method | transaction | process }

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

TA_TXPOLICY: { optional | always | never | ignore }

The transaction policy for the interface. The setting in this attribute affects the effect of the TA_AUTOTRAN attribute. See TA_AUTOTRAN for further explanation. This attribute is always read-only. It is set by the developer when the server is built and registered at server startup.

TA_NCOMPLETED: 0 <= num

Number of interface method invocations completed since the interface was initially offered.

TA_NQUEUED: 0 <= num

Number of requests currently enqueued for this interface.

TA_CUROBJECTS: 0 <= num

Number of active objects for this interface for 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 that were invoked within an active transaction.

TA_CURTRANSACTIONS: 0 <= num

Number of active global transactions associated with this interface for its associated queue.

T_INTERFACE Class

Overview

The T_INTERFACE MIB class represents configuration and runtime attributes of CORBA interfaces at both the domain and server group levels.

A domain-level T_INTERFACE object is one that is not associated with a Server Group. Its TA_SRVGRP attribute contains a NULL string (string of length 0, "").

A server group level T_INTERFACE object is one that has an associated server group (i.e., its TA_SRVGRP attribute contains a valid server group name for the domain). This Server Group level representation of an interface also provides a container for managing interface state (TA_STATE) and for collecting accumulated statistics.

An associated server group level T_INTERFACE object must exist for any CORBA Interfaces that are activated in a server. The activation of interfaces in a server is controlled by the state of a T_IFQUEUE object for the interface. Activation of a T_IFQUEUE object causes its attributes to be initialized with the values specified for the associated server group level T_INTERFACE object. If such an object does not exist, then one will be dynamically created. This dynamically-created server group level T_INTERFACE object will be initialized with the attributes of the domain level T_INTERFACE object for the interface if one exists. If an associated domain level T_INTERFACE object does not exist, system specified default configuration values will be applied. Once activated, interfaces are always associated with a server group level T_INTERFACE object.

The specification of configuration attributes for interfaces at any level is completely optional, system defined defaults will be provided and run-time server group level T_INTERFACE objects will be created. Interfaces to be offered by a server are identified via the ICF file used to generate server skeletons and advertised automatically by the system at server activation time.

Attribute Table

T_INTERFACE Class Definition Attribute Table

Attribute

Usage

Type

Permissions

Values

Default

TA_INTERFACENAME

TA_SRVGRP

r*

r*

string

string

ru-r--r--

ru-r--r--

string[1..128]

string[0..30]

N/A

N/A

TA_STATE

k

string

rwxr-xr--

GET: "{ACT | INA | SUS | PAR}"

SET: "{NEW | INV | ACT | REA | SUS}"

N/A

TA_AUTOTRAN


string

rwxr-xr--

"{Y|N}"

"N"a

TA_LOAD


long

rwxr-xr--

1 <= num < 32K

501

TA_PRIO


long

rwxr-xr--

1<= num < 101

50a

TA_TIMEOUT


long

rwxr-xr--

0 <= num

0a

TA_TRANTIME


long

rwxr-xr--

0 <= num

30a

TA_FBROUTINGNAME


string

rwyr-yr--

string[1...15]

2

TA_LMID

k

string

R--R--R--

LMID

N/A

TA_NUMSERVERS


long

R--R--R--

0 <= num

N/A

TA_TPPOLICY


string

R--R--R--

"{method | transaction | process}"

N/A

TA_TXPOLICY


string

R-R-R--

"{always | never | optional | ignore}"

N/A

TA_NCOMPLETED

l

long

R-XR-XR--

0 <= num

N/A3

TA_NQUEUED

l

long

R--R--R--

0 <= num

N/A

( k ) - GET key field
( l ) - local Field
( r ) - required field for object creation (SET TA_STATE NEW)
( * ) - GET/SET key, one or more required for SET operations

1

Group level T_INTERFACE objects (TA_SRVGRP != "") determine their defaults from the domain level T_INTERFACE object with a matching TA_INTERFACENAME setting if one exists. The listed defaults apply if no domain level object exists or if a domain level object is being created.

2

All T_INTERFACE objects with the same TA_INTERFACENAME must have matching TA_FBROUTINGNAME values. Therefore, the default for a newly configured object is the 0 length string ("") if there are currently no matching objects with the same TA_INTERFACENAME. Otherwise, the default (and in fact only legal value) is the currently configured TA_FBROUTINGNAME value for the existing matched objects.

3

TA_NCOMPLETED and TA_IMPLID (locals) require TA_LDBAL="Y" in the T_DOMAIN MIB class.

Attribute Semantics

TA_INTERFACENAME: string[1..128]

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 CORBA 2.1 Specification Section 7.6 for details.

TA_SRVGRP: string[0..30]

Server group name. Server group names cannot contain an asterisk, comma or colon. An explicitly specified 0 length string for this attribute is used to specify and query domain level configuration and run-time information for an interface. There are certain limitations and semantic differences noted in other attributes with respect to domain and group level objects in this class.

TA_STATE:

Following are the semantics for GET and SET TA_STATE values on the T_INTERFACE class. Where semantics differ between group and domain level objects, those differences are noted.

GET: {ACTive | INActive | SUSpended | PARtitioned}

A GET operation will retrieve configuration information for the selected T_INTERFACE objects. The following states indicate the meaning of a TA_STATE returned in response to a GET request. States not listed will not be returned.

ACTive

T_INTERFACE object is defined and at least one corresponding T_IFQUEUE entry is in the ACTive state.

Note: For a group level T_INTERFACE object, corresponding T_IFQUEUE entries are those with matching TA_INTERFACENAME and TA_SRVGRP attributes. For a domain level T_INTERFACE object, corresponding T_IFQUEUE entries are those with matching TA_INTERFACENAME attributes regardless of their TA_SRVGRP value.

INActive

T_INTERFACE object is defined and there are no corresponding T_IFQUEUE entries in any ACTive equivalent state.

SUSpended

T_INTERFACE object is defined and amongst all corresponding T_IFQUEUE entries there are none in the ACTive state and at least one in the SUSpended state. This state is ACTive equivalent for the purpose of determining permissions.

PARtitioned

T_INTERFACE object is defined and amongst all corresponding T_IFQUEUE entries there are:

  1. None in the ACTive state

  2. None in the SUSpended state and

  3. At least one in the PARtitioned state. This state is ACTive equivalent for the purpose of determining permissions.

SET: {NEW | INValid | ACTive | REActivate | SUSpended}

A SET operation will update configuration and run-time information for the selected T_INTERFACE object. Note that modifications may affect more than one server group when making domain level changes and run-time modifications may affect more than one server if multiple servers are currently offering an interface. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create T_INTERFACE object for application. State change only allowed when in the INValid state. Successful return leaves object in INActive state. Creation of a domain level T_INTERFACE object will affect existing group level objects with the same TA_INTERFACENAME value by resetting all TA_FBROUTINGNAME values if a new value is explicitly specified. All other configuration attribute settings will not affect existing group level T_INTERFACE objects.

INValid

Delete T_INTERFACE object for application. State change only allowed when in the INActive state. Successful return leaves object in INValid state.

ACTive

Activate the T_INTERFACE object. Setting this state on the domain level object has the effect of activating all corresponding T_IFQUEUE entries that are currently SUSpended throughout the domain. Setting this state on the group level object will affect only servers within the group offering the interface. State change only allowed when in the SUSpended state. Successful return leaves object in ACTive state.

REActivate

Reactivate the T_INTERFACE object. Setting this state on the domain level object has the effect of activating all corresponding T_IFQUEUE entries that are currently SUSpended throughout the domain. Setting this state on the group level object will affect only servers within the group offering the interface. State change only allowed when in the ACTive or SUSpended states. Successful return leaves object in ACTive state. This state permits global activation of T_IFQUEUE entries suspended at the group level without having to individually activate each group level T_INTERFACE object.

SUSpended

Suspend the T_INTERFACE object. Setting this state on the domain level object has the effect of suspending all corresponding T_IFQUEUE entries that are currently ACTive throughout the domain. Setting this state on the group level object will affect only servers within the group offering the interface. State change only allowed when in the ACTive state. Successful return leaves object in SUSpended state.

Limitation: Dynamic advertisement of interfaces (i.e., state change from INActive or INValid to ACTive) is not supported, nor is unadvertisement (i.e., state change from ACTive to INActive).

TA_AUTOTRAN: { Y | N }

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

Limitations: Run-time updates to this attribute are not reflected in active equivalent T_INTERFACE objects and TA_TXPOLICY may override the value specified for this attribute in the UBBCONFIG file. If TA_TXPOLICY is:

always

A value of N will have no effect at run time. Behavior will be as though the setting was Y.

never

A value of Y will have no effect at run time. The interface will never be involved in a transaction.

ignore

A value of Y will have no effect at run time. The interface will never be involved in a transaction.

TA_LOAD: 1 <= num <= 32K

This T_INTERFACE object imposes the indicated load on the system. Interface loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request.

Limitation: Run-time updates to this attribute for domain level objects will not affect corresponding group level objects for the same interface.

TA_PRIO: 1 <= num <= 101

This T_INTERFACE object has the indicated dequeuing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests will be handled first.

Limitation: Run-time updates to this attribute for domain level objects will not affect corresponding group level objects for the same interface.

TA_TIMEOUT: 0 <= num

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.

Limitation: Run-time updates to this attribute for domain level objects will not affect corresponding group level objects for the same interface.

TA_TRANTIME: 0 <= num

Transaction timeout value in seconds for transactions automatically started for this T_INTERFACE object. Transactions are started automatically when a requests not in transaction mode is received and the T_INTERFACE: TA_AUTOTRAN attribute value for the interface is "Y".

Limitation: Run-time updates to this attribute for domain level objects will not affect corresponding group level objects for the same interface.

Note: Updating this value at runtime for domain level objects should cause a warning, since the only use would be to set the default for a subsequent boot of the application.

TA_FBROUTINGNAME: string[1..15]

The factory-based routing criteria associated with this interface. The name FBROUTINGNAME is used to allow for the future possibility of other routing criteria for message-based routing. This will be less confusing than trying to overload ROUTINGNAME.

Limitation: This attribute may be set only for a domain level T_INTERFACE object, i.e., TA_SRVGRP is "".

TA_LMID: LMID

Current logical machine with which the active equivalent group level T_INTERFACE object is associated. This attribute is blank, i.e., "" for domain level objects unless a local query is performed, i.e., TA_FLAGS has the MIB_LOCAL bit set. In the local case, multiple domain level objects will be returned for the same interface, one per machine, with the local values retrieved from each machine represented in the separate objects.

TA_NUMSERVERS: 0 <= num

Number of corresponding servers offering this interface.

TA_TPPOLICY: { method | transaction | process }

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

TA_TXPOLICY: { optional | always | never | ignore }

The transaction policy for the interface. The setting in this attribute affects the effect of the TA_AUTOTRAN attribute. See TA_AUTOTRAN for further explanation. This attribute is always read-only. It is set by the developer when the server is built and registered at server startup.

TA_NCOMPLETED: 0 <= num

Number of interface method invocations completed with respect to the corresponding T_IFQUEUE objects since they were initially offered. Local queries (TA_FLAGS MIB_LOCAL bit set) on domain level objects will return one object per machine with the statistics for the indicated interface on that machine.

TA_NQUEUED: 0 <= num

Number of requests currently enqueued for this interface. Local queries (TA_FLAGS MIB_LOCAL bit set) on domain level objects will return one object per machine with the statistics for the indicated interface on that machine.

Implementation Hint

The T_INTERFACE MIB is a mapping from an interface to a BEA Tuxedo service. The MIB server can implement some of the get/set operations for an interface by calling the existing logic for the associated T_SERVICE object.

T_MACHINE Class Definition

Overview

The T_MACHINE class represents application attributes pertaining to a particular machine. These attribute values represent machine characteristics, per-machine sizing, statistics, customization options, and UNIX system filenames.

Attribute Table

TM_MIB(5): T_MACHINE Class Definition Attribute Table

Attribute

Type

Permissions

Values

Default

TA_LMID(r)(*)1

string

rU-r--r--

string[1..30]

N/A

TA_PMID(r)(*)1

string

rU-r--r--

string[1..30]

N/A

TA_TUXCONFIG(r)

string

rw-r--r--

string[2..64]

N/A

TA_TUXDIR(r)

string

rw-r--r--

string[2..78]

N/A

TA_APPDIR(r)

string

rw-r--r--

string[2..8]

N/A

TA_STATE(k)

string

rwyr-yr--

GET: "{ACT | INA | PAR}"

SET: "{NEW | INV | ACT | RAC | INA | FIN | CLE}"

N/A

N/A

TA_UID

long

rw-r--r--

0 <= num

(2)

TA_GID

long

rw-r--r--

0 <= num

(2)

TA_ENVFILE

string

rwyr--r--

string[0..78]

""

TA_PERM

long

rwyr--r--

0001 <= num <= 0777

(2)

TA_ULOGPFX

string

rwyr--r--

string[0..78]

(3)

TA_TYPE

string

rw-r--r--

string[0..15]

""

TA_MAXACCESSERS

long

rw-r--r--

1 <= num < 32,768

(2)

TA_MAXCONV

long

rw-r--r--

0 <= num < 32,768

(2)

TA_MAXGTT

long

rw-r--r--

0 <= num < 32,768

(2)

TA_MAXWSCLIENTS

long

rw-r--r--

0 <= num < 32,768

0

TA_MAXACLCACHE

long

rw-r--r--

10 <= num <= 32,000

100

TA_TLOGDEVICE

string

rw-r--r--

string[0..64]

""

TA_TLOGNAME

string

rw-r--r--

string[0..30]

TLOG

TA_TLOGSIZE

long

rw-r--r--

1 <= num < 2,049

100

TA_BRIDGE

string

rw-r--r--

string[0..78]

N/A

TA_NADDR

string

rw-r--r--

string[0..78]

N/A

TA_NLSADDR

string

rw-r--r--

string[0..78]

N/A

TA_FADDR

string

rw-r--r--

string[0..78]

""

TA_FRANGE

long

rw-r--r--

1 <= num <= 65,535

1

TA_CMPLIMIT

string

rwyr-yr--

"remote[,local]"

MAXLONG,MAXLONG

TA_TMNETLOAD

long

rwyr-yr--

0 <= num < 32,768

0

TA_SPINCOUNT

long

rwyr-yr--

0 <= num

0

TA_ROLE

string

r--r--r--

"{MASTER | BACKUP | OTHER}"

N/A

TA_MINOR

long

R--R--R--

1 <= num

N/A

TA_RELEASE

long

R--R--R--

1 <= num

N/A

TA_MINENCRYPTBITS

string

rwxrwx---

{0 | 40 | 56 | 128}4

0

TA_MAXENCRYPTBITS

string

rwxrwx---

{0 | 40 | 56 | 128}4

128

TA_MAXPENDINGBYTES

long

rw-r--r--

100000 <= num <= MAXLONG

2147483647

TA_SICACHEENTRIESMAX

string

rw-r--r--

"0"-"32767"

"500"

TA_SEC_PRINCIPAL_NAME

TA_SEC_PRINCIPAL_LOCATION

TA_SEC_PRINCIPAL_PASSVAR

TA_SIGNATURE_REQUIRED

TA_ENCRYPTION_REQUIRED

string

string

string

string

string

rwxr--r--

rwxr--r--

rwxr--r--

rwxr--r--

rwxr--r--

string[0..511]

string[0..511]

string[0..511]

"{Y|N}"

"{Y|N}"

""

""

""

"N"

"N"

T_MACHINE Class: LOCAL Attributes

TA_CURACCESSERS

long

R--R--R--

0 <= num < 32,768

N/A

TA_CURCLIENTS

long

R--R--R--

0 <= num < 32,768

N/A

TA_CURCONV

long

R--R--R--

0 <= num < 32,768

N/A

TA_CURGTT

long

R--R--R--

0 <= num < 32,768

N/A

TA_CURRLOAD

long

R--R--R--

0 <= num

N/A

TA_CURWSCLIENTS

long

R--R--R--

0 <= num < 32,768

N/A

TA_HWACCESSERS

long

R--R--R--

0 <= num < 32,768

N/A

TA_HWCLIENTS

long

R--R--R--

0 <= num < 32,768

N/A

TA_HWCONV

long

R--R--R--

0 <= num < 32,768

N/A

TA_HWGTT

long

R--R--R--

0 <= num < 32,768

N/A

TA_HWWSCLIENTS

long

R--R--R--

0 <= num < 32,768

N/A

TA_NUMCONV

long

R-XR-XR--

0 <= num

N/A

TA_NUMDEQUEUE

long

R-XR-XR--

0 <= num

N/A

TA_NUMENQUEUE

long

R-XR-XR--

0 <= num

N/A

TA_NUMPOST

long

R-XR-XR--

0 <= num

N/A

TA_NUMREQ

long

R-XR-XR--

0 <= num

N/A

TA_NUMSUBSCRIBE

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRAN

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRANABT

long

R-XR-XR--

0 <= num

N/A

TA_NUMTRANCMT

long

R-XR-XR--

0 <= num

N/A

TA_PAGESIZE

long

R--R--R--

1 <= num

N/A

TA_SWRELEASE

string

R--R--R--

string[0..78]

N/A

TA_HWACLCACHE

long

R--R--R--

0 <= num

N/A

TA_ACLCACHEHITS

long

R--R--R--

0 <= num

N/A

TA_ACLCACHEACCESS

long

R--R--R--

0 <= num

N/A

TA_ACLFAIL

long

R--R--R--

0 <= num

N/A

TA_WKCOMPLETED

long

R--R--R--

0 <= num

N/A

TA_WKINITIATED

long

R--R--R--

0 <= num

N/A

(k)—GET key field
(r)—required field for object creation (SET TA_STATE NEW)
(*)—GET/SET key, one or more required for SET operations


 

1TA_LMID and TA_PMID must each be unique within this class. Only one of these fields is required as a key field for a SET operation. If both are specified, then they must match the same object.
2Default is same as value set for this attribute in Class T_DOMAIN.
3Default is TA_APPDIR for this machine followed by /ULOG.
4The link-level encryption value of 40 bits is provided for backward compatibility.

Attribute Semantics

TA_LMID: string[1..30]

Logical machine identifier. This identifier is used within the rest of the TM_MIB definition as the sole means of mapping application resources to T_MACHINE objects.

TA_PMID: string[1..30]

Physical machine identifier. This identifier should match the UNIX system nodename as returned by the "uname -n" command when run on the identified system.

TA_TUXCONFIG: string[2..64]

Absolute pathname of the file or device where the binary BEA Tuxedo system configuration file is found on this machine. The administrator need only maintain one such file, namely the one identified by the TA_TUXCONFIG attribute value on the master machine. The information contained in this file is automatically propagated to all other T_MACHINE objects as they are activated. See TA_ENVFILE in this class for a discussion of how this attribute value is used in the environment.

TA_TUXDIR: string[2..78]

Absolute pathname of the directory where the BEA Tuxedo system software is found on this machine. See TA_ENVFILE in this class for a discussion of how this attribute value is used in the environment.

TA_APPDIR: string[2..78]

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 TA_ENVFILE in this class for a discussion of how this attribute value is used in the environment.

TA_STATE:

GET: "{ACTive | INActive | PARtitioned}"

A GET operation will retrieve configuration and run-time information for the selected T_MACHINE object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request.

ACTive

T_MACHINE object defined and active (administrative servers, that is, DBBL, BBL, and BRIDGE).

INActive

T_MACHINE object defined and inactive.

PARtitioned

T_MACHINE object defined, listed in accessible bulletin boards as active, but currently unreachable. This state is ACTive equivalent for the purpose of determining permissions.


 

SET: "{NEW | INValid | ACTive | ReACtivate | INActive | ForceINactive | CLEaning}"

A SET operation will update configuration and run-time information for the selected T_MACHINE object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create T_MACHINE object for application. State change allowed only when in the INValid state. Successful return leaves the object in the INActive state.

unset

Modify an existing T_MACHINE object. This combination is allowed only when in the ACTive or INActive state. Successful return leaves the object state unchanged.

INValid

Delete T_MACHINE object for application. State change allowed only when in the INActive state. Successful return leaves the object in the INValid state.

ACTive

Activate the T_MACHINE object. 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 (subject to restriction by TA_FLAGS settings). For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). State change allowed only when in the INActive state. Successful return leaves the object in the ACTive state.

The TMIB_NOTIFY TA_FLAG value should be used when activating a machine if status on individual servers is required.

ReACtivate

Activate the T_MACHINE object. 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 (subject to restriction by TA_FLAGS settings). For the purpose of determining permissions for this state transition, the active object permissions are considered (that is, --x--x--x). State change allowed only when in either the ACTive or INActive state. Successful return leaves the object in the ACTive state.

The TMIB_NOTIFY TA_FLAG value should be used when reactivating a machine if status on individual servers is required.

INActive

Deactivate the T_MACHINE object. Necessary administrative servers such as the BBL and BRIDGE are stopped on the indicated site as well as application servers running on that site (subject to restriction by TA_FLAGS settings). State change allowed only when in the ACTive state and when no other application resources are active on the indicated machine. Successful return leaves the object in the INActive state.

The TMIB_NOTIFY TA_FLAG value should be used when deactivating a machine if status on individual servers is required.

ForceINactive

Deactivate the T_MACHINE object without regard to attached clients. Necessary administrative servers such as the BBL and BRIDGE are stopped on the indicated site as well as application servers running on that site (subject to restriction by TA_FLAGS settings). State change allowed only when in the ACTive state. Successful return leaves the object in the INActive state.

The TMIB_NOTIFY TA_FLAG value should be used when deactivating a machine if status on individual servers is required.

CLEaning

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 state and the T_MACHINE object is in either the ACTive or PARtitioned state. Successful return for a non-partitioned machine leaves the state unchanged. Successful return for a partitioned machine leaves the object in the INActive state.


 

Limitation: State change to ForceINactive or INActive allowed only for non-master machines. The master site administrative processes are deactivated via the T_DOMAIN class.

TA_UID: 0 <= num

UNIX system user identifier for the BEA Tuxedo system 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.

Limitation: 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.

TA_GID: 0 <= num

UNIX system group identifier for the BEA Tuxedo system 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.

Limitation: 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.

TA_ENVFILE: string[0..78]

Environment file for clients and servers running on this machine. If the value specifies an invalid filename, no values are added to the environment. the value of string is placed into the environment.

When booting servers, local servers inherit the environment of tmboot(1) and remote servers (not on the MASTER) inherit the environment of tlisten(1). TUXCONFIG, TUXDIR, and APPDIR are also put into the environment when a server is booted based on the information in the associated T_MACHINE object. PATH will be set in the environment to:

APPDIR:TUXDIR/bin:/bin:/usr/bin:<path>

where <path> is the value of the first PATH= line appearing in the machine environment file, if one exists (subsequent PATH= lines will be ignored). This PATH will be used as a search path for servers that are specified with a simple or relative pathname (that is, that doesn't begin with slash). LD_LIBRARY_PATH will be set in the environment to:

APPDIR:TUXDIR/lib:/lib:/usr/lib:<lib>

where <lib> is the value of the first LD_LIBRARY_PATH= line appearing in the machine environment file, if one exists (subsequent LD_LIBRARY_PATH= lines will be ignored).

As part of server initialization (before tpsvrinit() is called), a server will read and export variables from both the machine and server ENVFILE files. If a variable is set in both the machine and server ENVFILE, the value in the server ENVFILE will override the value in the machine ENVFILE with the exception of PATH which is appended. A client will process only the machine ENVFILE file. When the machine and server ENVFILE files are processed, lines that are not of the form <ident>= will be ignored, where <ident> begins with an underscore or alphabetic character, and contains only underscore or alphanumeric characters. If a PATH= line is encountered, PATH will be set to:

APPDIR:TUXDIR/bin:/bin:/usr/bin:<path>

where <path> is the value of the first PATH= line appearing in the environment file (subsequent PATH= lines are ignored). If PATH appears in both the machine and server files, then <path> is <path1>:<path2> where <path1> is from the machine ENVFILE and <path2> is from the server ENVFILE. If a LD_LIBRARY_PATH= line is encountered, LD_LIBRARY_PATH will be set to:

APPDIR:TUXDIR/lib:/lib:/usr/lib:<lib>

where <lib> is the value of the first LD_LIBRARY_PATH= line appearing in the environment file (subsequent LD_LIBRARY_PATH= lines are ignored). Attempts to reset TUXDIR, APPDIR, or TUXCONFIG will be ignored and a warning will be printed if the value does not match the corresponding T_MACHINE attribute value. Limitation: Modifications to this attribute for an active object will not affect running servers or clients.

TA_PERM: 0001 <= num <= 0777

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

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

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.

TA_ULOGPFX: string[0..78]

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

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

TA_TYPE: string[0..15]

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 TA_TYPE attributes should be set when the application spans a heterogeneous network of machines or when compilers generate dissimilar structure representations. The default for this attribute, a 0-length string, matches any other machine with a 0-length string as its TA_TYPE attribute value.

TA_MAXACCESSERS: 1 <= num < 32,768

Maximum number of clients and servers that can be simultaneously connected to the bulletin board on this machine. If not specified, the default is the TA_MAXACCESSERS value specified in the T_DOMAIN class.

System administration processes, such as the BBL, restartsrv, cleanupsrv, tmshutdown(), and tmadmin(), need not be accounted for in this value, but the DBBL, all bridge processes, all system-supplied and application server processes, and all potential client processes at this site need to be counted. (Examples of system-supplied servers are AUTHSVR, TMQUEUE, TMQFORWARD, TMUSREVT, TMSYSEVT, TMS—see T_GROUP TA_TMSNAME attribute, TMS_QM, GWTDOMAIN, and WSL.) If the application is booting workstation listeners (WSLs) on this site, both the WSLs and the number of potential workstation handlers (WSHs) that may be booted need to be counted.

Note that for BEA Tuxedo pre-release 7.1 (6.5 or earlier), both the TA_MAXACCESSERS and TA_MAXSERVERS (see T_DOMAIN TA_MAXSERVERS) attributes for an application play a part in the user license checking scheme. Specifically, a machine is not allowed to boot if the number of TA_MAXACCESSERS for that machine + the number of TA_MAXACCESSERS for the machine (or machines) already running in the application is greater than the number of TA_MAXSERVERS + user licenses for the application. Thus, the total number of TA_MAXACCESSERS for an application must be less than or equal to the number of TA_MAXSERVERS + user licenses for the application.

Note also that the user license checking scheme in BEA Tuxedo release 7.1 or later considers only the following two factors when performing its checks: the number of user licenses for an application and the number of licenses currently in use for the application. When all user licenses are in use, no new clients are allowed to join the application.

TA_MAXCONV: 0 <= num < 32,768

Maximum number of simultaneous conversations in which clients and servers on this machine can be involved. If not specified, the default is the TA_MAXCONV value specified in the T_DOMAIN class. The maximum number of simultaneous conversations per server is 64.

TA_MAXGTT: 0 <= num < 32,768

Maximum number of simultaneous global transactions in which this machine can be involved. If not specified, the default is the value specified in the T_DOMAIN class.

TA_MAXWSCLIENTS: 0 <= num < 32,768

Number of accesser entries on this machine to be reserved for Workstation clients (as opposed to native clients). If TA_MAXWSCLIENTS is not specified, the default is 0.

The number specified here takes a portion of the total accesser slots specified with TA_MAXACCESSERS, meaning that the accesser slots reserved for TA_MAXWSCLIENTS are unavailable for use by other clients and servers on this machine. It is an error to set this number greater than TA_MAXACCESSERS.

The TA_MAXWSCLIENTS attribute is only used when the BEA Tuxedo system Workstation feature is used. The appropriate setting of this attribute helps to conserve interprocess communication (IPC) resources since Workstation client access to the system is multiplexed through a BEA Tuxedo system-supplied surrogate, the workstation handler (WSH).

TA_MAXACLCACHE: 10 <= num <= 32,000

Number of entries in the cache used for ACL entries when TA_SECURITY is set to ACL or MANDATORY_ACL. The appropriate setting of this parameter helps to conserve on shared memory resources and yet reduce the number of disk access to do ACL checking.

TA_TLOGDEVICE: string[0..64]

The device (raw slice) or UNIX system file containing the BEA Tuxedo filesystem that holds the DTP transaction log for this machine. The DTP transaction log is stored as a BEA Tuxedo system VTOC table on the device. This device or file may be the same as that specified for the TA_TUXCONFIG attribute for this machine.

TA_TLOGNAME: string[0..30]

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

TA_TLOGSIZE: 1 <= num < 2,049

The numeric size, in pages, of the DTP transaction log for this machine. The TA_TLOGSIZE attribute value is subject to limits based on available space in the BEA Tuxedo filesystem identified by the TA_TLOGDEVICE attribute.

TA_BRIDGE: string[0..78]

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 BEA Tuxedo system binary. This attribute is not needed for sockets-based BEA Tuxedo system binaries.

TA_NADDR: string[0..78]

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 T_DOMAIN:TA_OPTIONS attribute value.

If string has the form "0xhex-digits" or "\\xhex-digits", it must contain an even number of valid hex digits. These forms are translated internally into a character array containing the hexadecimal representations of the string specified. For TCP/IP addresses either the

"//hostname:port"

or

"//#.#.#.#:port"

format is used.

TA_NLSADDR: string[0..78]

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 TA_NADDR attribute above.

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 T_DOMAIN:TA_OPTIONS attribute value.

TA_FADDR: string[0..78]

Specifies the complete network address to to which local processes such as tmboot, BRIDGE, BSBRIDGE and tmloadcf can bind before making an outbound connection. This address must be a TCP/IP address. This attribute, along with the TA_FRANGE attribute, determines the range of TCP/IP ports to which a process will attempt to bind before making an outbound connection. If this parameter is set to the NULL or empty string, then the operating system randomly chooses a local port with which to bind.

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

For TCP/IP addresses, one of the following formats is used:

TA_FRANGE: 1<= num <= 65,535

Specifies the range of TCP/IP ports to which local processes will attempt to bind before making an outbound connection. The TA_FADDR attribute specifies the base address of the range.

TA_CMPLIMIT: "remote[,local]"

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.

Limitation: This attribute value is not part of the T_MACHINE object for active sites running BEA Tuxedo system release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.

TA_TMNETLOAD: 0 <= num < 32,768

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

Limitation: This attribute value is not part of the T_MACHINE object for active sites running BEA Tuxedo release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.

TA_SPINCOUNT: 0 <= num

Spincount used on this machine for pre-ticket user level semaphore access. Defaults are built into the BEA Tuxedo system binaries on each machine. These defaults may be overridden at run time 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. There is also a TMSPINCOUNT environment variable, which the system uses if the value is not set here or in the UBBCONFIG file.

Limitation: This attribute value is not part of the T_MACHINE object for active sites running BEA Tuxedo release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.

TA_ROLE: "{MASTER | BACKUP | OTHER}"

The role of this machine in the application. "MASTER" indicates that this machine is the master machine, "BACKUP" indicates that it is the backup master machine, and "OTHER" indicates that the machine is neither the master nor backup master machine.

TA_MINOR: 1 <= num

The BEA Tuxedo system minor protocol release number for this machine.

TA_RELEASE: 1 <= num

The BEA Tuxedo system major protocol release number for this machine. This may be different from the TA_SWRELEASE for the same machine.

TA_MINENCRYPTBITS: {0 | 40 | 56 | 128}

Specifies the minimum level of encryption required when establishing a network link to this machine. 0 means no encryption, while 40, 56, and 128 specify the encryption key length (in bits). If this minimum level of encryption cannot be met, link establishment will fail. The default is 0.

Note: The link-level encryption value of 40 bits is provided for backward compatibility.

Limitation: Modifications to this attribute will not effect established network links.

TA_MAXENCRYPTBITS: {0 | 40 | 56 | 128}

Specifies the maximum level of encryption that can be negotiated when establishing a network link. 0 means no encryption, while 40, 56, and 128 specify the encryption length (in bits). The default is 128.

Note: The link-level encryption value of 40 bits is provided for backward compatibility.

Limitation: Modifications to this attribute will not effect established network links.

TA_MAXPENDINGBYTES: 100000 <= num <= MAXLONG

Specifies a limit for the amount of space that can be allocated for messages waiting to be transmitted by the BRIDGE process.

TA_SICACHEENTRIESMAX: "0"-"32767"

The number of service and interface cache entries kept on this machine. If not specified, the value will be set to "500". A value of "0" implies that service caching is not used on this machine.

TA_SEC_PRINCIPAL_NAME: string[0..511]

Security principal name identification string to be used for authentication purposes by an application running BEA Tuxedo 7.1 or later software. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character). The principal name specified for this attribute becomes the identity of one or more system processes running on this machine.

TA_SEC_PRINCIPAL_NAME can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. A principal name at a particular configuration level can be overridden at a lower level. If TA_SEC_PRINCIPAL_NAME is not specified at any of these levels, the principal name for the application defaults to the TA_DOMAINID string for this domain.

Note that TA_SEC_PRINCIPAL_NAME is one of a trio of attributes, the other two being TA_SEC_PRINCIPAL_LOCATION and TA_SEC_PRINCIPAL_PASSVAR. The latter two attributes pertain to opening decryption keys during application booting for the system processes running in a BEA Tuxedo 7.1 or later application. When only TA_SEC_PRINCIPAL_NAME is specified at a particular level, the system sets each of the other two attributes to a NULL (zero length) string.

TA_SEC_PRINCIPAL_LOCATION: string[0..511]

Location of the file or device where the decryption (private) key for the principal specified in TA_SEC_PRINCIPAL_NAME resides. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_LOCATION can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_PASSVAR is optional; if not specified, the system sets it to a NULL—zero length—string.)

TA_SEC_PRINCIPAL_PASSVAR: string[0..511]

Variable in which the password for the principal specified in TA_SEC_PRINCIPAL_NAME is stored. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).

TA_SEC_PRINCIPAL_PASSVAR can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVER class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_LOCATION is optional; if not specified, the system sets it to a NULL—zero length—string.)

During initialization, the administrator must provide the password for each of the decryption keys configured with TA_SEC_PRINCIPAL_PASSVAR. The system automatically encrypts the password entered by the administrator and assigns each encrypted password to the associated password variable.

TA_SIGNATURE_REQUIRED: {Y | N}

If set to Y, every process running on this machine requires a digital signature on its input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_SIGNATURE_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting SIGNATURE_REQUIRED to Y at a particular level means that signatures are required for all processes running at that level or below.

TA_ENCRYPTION_REQUIRED: {Y | N}

If set to Y, every process running on this machine requires an encrypted input message buffer. If not specified, the default is N. This attribute only applies to applications running BEA Tuxedo 7.1 or later software.

TA_ENCRYPTION_REQUIRED can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN class, T_MACHINE class, T_GROUP class, and T_SERVICE class. Setting TA_ENCRYPTION_REQUIRED to Y at a particular level means that encryption is required for all processes running at that level or below.

TA_CURACCESSERS: 0 <= num < 32,768

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

TA_CURCLIENTS: 0 <= num < 32,768

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

TA_CURCONV: 0 <= num < 32,768

Number of active conversations with participants on this machine.

TA_CURGTT: 0 <= num < 32,768

Number of in use transaction table entries on this machine.

TA_CURRLOAD: 0 <= num

Current service load enqueued on this machine. Limitation: If the T_DOMAIN:TA_LDBAL attribute is "N" or the T_DOMAIN:TA_MODEL attribute is "MP", then an FML32 NULL value is returned (0).

TA_CURWSCLIENTS: 0 <= num < 32,768

Number of Workstation clients currently logged in to this machine.

TA_HWACCESSERS: 0 <= num < 32,768

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

TA_HWCLIENTS: 0 <= num < 32,768

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

TA_HWCONV: 0 <= num < 32,768

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

TA_HWGTT: 0 <= num < 32,768

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

TA_HWWSCLIENTS: 0 <= num < 32,768

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

TA_NUMCONV: 0 <= num

Number of tpconnect() operations performed from this machine.

TA_NUMDEQUEUE: 0 <= num

Number of tpdequeue() operations performed from this machine.

TA_NUMENQUEUE: 0 <= num

Number of tpenqueue() operations performed from this machine.

TA_NUMPOST: 0 <= num

Number of tppost() operations performed from this machine.

TA_NUMREQ: 0 <= num

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

TA_NUMSUBSCRIBE: 0 <= num

Number of tpsubscribe() operations performed from this machine.

TA_NUMTRAN: 0 <= num

Number of transactions initiated (tpbegin()) from this machine.

TA_NUMTRANABT: 0 <= num

Number of transactions aborted (tpabort()) from this machine.

TA_NUMTRANCMT: 0 <= num

Number of transactions committed (tpcommit()) from this machine.

TA_PAGESIZE: 1 <= num

Disk pagesize used on this machine.

TA_SWRELEASE: string[0..78]

Software release for binary on that machine or a 0-length string if binary is not a BEA Tuxedo system master binary.

TA_HWACLCACHE: 0 <= num

High water number of entries used in the ACL cache.

TA_ACLCACHEHITS: 0 <= num

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

TA_ACLCACHEACCESS: 0 <= num

Number of accesses to the ACL cache.

TA_ACLFAIL: 0 <= num

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

TA_WKCOMPLETED: 0 <= num

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.

TA_WKINITIATED: 0 <= num

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.

Limitations

SHM mode (see T_DOMAIN:TA_MODEL) applications can have only one T_MACHINE object. MP mode (see T_DOMAIN:TA_MODEL) applications with the LAN option set (see T_DOMAIN:TA_OPTIONS) may have up to the maximum number of configurable T_MACHINE objects as defined by the T_DOMAIN:TA_MAXMACHINES attribute. Many attributes of this class are tunable only when the application is inactive on the site. Since the master machine at least must be active in a minimumly active application, the use of the ATMI interface routines to administer the application is not possible with respect to the master machine object. The function tpadmcall() is being provided as a means configuring an unbooted application and may be used to set these attributes for the master machine.

T_MSG Class Definition

Overview

The T_MSG class represents run-time attributes of the BEA Tuxedo system managed UNIX system message queues.

Attribute Table

TM_MIB(5): T_MSG Class Definition Attribute Table

Attribute1

Type

Permissions

Values

Default

TA_LMID(k)

string

R--R--R--

LMID

N/A

TA_MSGID(k)

long

R--R--R--

1 <= num

N/A

TA_STATE(k)

string

R--R--R--

GET: "ACT"

SET: N/A

N/A

N/A

TA_CURTIME

long

R--R--R--

1 <= num

N/A

TA_MSG_CBYTES

long

R--R--R--

1 <= num

N/A

TA_MSG_CTIME

long

R--R--R--

1 <= num

N/A

TA_MSG_LRPID

long

R--R--R--

1 <= num

N/A

TA_MSG_LSPID

long

R--R--R--

1 <= num

N/A

TA_MSG_QBYTES

long

R--R--R--

1 <= num

N/A

TA_MSG_QNUM

long

R--R--R--

1 <= num

N/A

TA_MSG_RTIME

long

R--R--R--

1 <= num

N/A

TA_MSG_STIME

long

R--R--R--

1 <= num

N/A

(k)—GET key field


 

1All attributes in Class T_MSG are local attributes.

Attribute Semantics

TA_LMID: LMID

Logical machine identifier.

TA_MSGID: 1 <= num

UNIX system message queue identifier. Limitation: 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.

TA_STATE:

GET—>ACTive

A GET operation will retrieve run-time information for the selected T_MSG object(s). The following state indicates the meaning of a TA_STATE returned in response to a GET request.

ACTive

T_MSG object active. This corresponds exactly to the related T_MACHINE object being active.


 

SET:

SET operations are not permitted on this class.

TA_CURTIME: 1 <= num

Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on T_MSG:TA_LMID. This attribute can be used to compute elapsed time from the T_MSG:TA_?TIME attribute values.

TA_MSG_CBYTES: 1 <= num

Current number of bytes on the queue.

TA_MSG_CTIME: 1 <= num

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

TA_MSG_LRPID: 1 <= num

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

TA_MSG_LSPID: 1 <= num

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

TA_MSG_QBYTES: 1 <= num

Maximum number of bytes allowed on the queue.

TA_MSG_QNUM: 1 <= num

Number of messages currently on the queue.

TA_MSG_RTIME: 1 <= num

Time since the last read from the queue.

TA_MSG_STIME: 1 <= num

Time since the last write to the queue.

Limitations

This class is UNIX system-specific and may not be supported in non-UNIX implementations of BEA Tuxedo system.

T_NETGROUP Class Definition

Overview

The T_NETGROUP class represents application attributes of network groups. Network groups are groups of LMIDs which can communicate over the TA_NADDR network addresses defined in the T_NETMAP class.

Attribute Table

TM_MIB(5): T_NETGROUP Class Definition Attribute Table

Attribute

Type

Permissions

Values

Default

TA_NETGROUP(r)(*)

string

rU-------

string[1..30]

DEFAULTNET

TA_NETGRPNO(r)(*)

long

rU-------

1 <= num < 8192

N/A

TA_STATE(k)

string

rw-r--r--

GET: "VAL"

SET: "{NEW | INV}"

N/A

N/A

TA_NETPRIO(*)

long

rwyrw----

1 <= num < 8,192

100

(k)—GET key field
(r)—required field for object creation (SET TA_STATE NEW)
(*)—GET/SET key, one or more required for SET operations


 

Attribute Semantics

TA_NETGROUP: string[1..30]

Logical name of the network group. A group name is a string of printable characters and cannot contain a point sign, comma, colon, or newline.

TA_NETGRPNO: 1 <= num <= 8192

Group identifier associated with network group.

TA_STATE:

GET: {VALid}

A GET operation will retrieve configuration information for the selected T_NETGROUP object(s). The following states indicate the meaning of a TA_STATE returned in response to a GET request.

VALid

T_NETGROUP object is defined and inactive. Note that this is the only valid state for this class. NETGROUPs are never ACTive.


 

SET: {NEW | INValid}

a SET operation will update configuration information for the selected T_NETGROUP object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.

NEW

Create T_NETGROUP object for application. State change allowed only when in the INValid state. Successful return leaves the object in the VALid state.

unset

Modify an existing T_NETGROUP object. Only allowed in the VALid state. Successful return leaves the object state unchanged.

INValid

Delete T_NETGROUP object from application. State change allowed only when in the VALid state and only if there are no objects in the T_NETMAP class which have this network group object as a key. Successful return leaves the object in the INValid state.


 

TA_NETPRIO: 1 <= num < 8,192

The priority band for this network group. All network groups of equivalent band priority will be used in parallel. If all network circuits of a certain priority are torn down by the administrator or by network conditions, the next lower priority circuit is used. Retries of the higher priority are attempted.

Note: In BEA Tuxedo release 6.4, parallel data circuits are prioritized by network group number (NETGRPNO) within priority group number. In future releases, a different algorithm may be used to prioritize parallel data circuits.

Limitations

None.

T_NETMAP Class Definition

Overview

The T_NETMAP class associates TA_LMIDs from the T_MACHINE class in the TM_MIB to a TA_NETGROUP object from the T_NETGROUP class. In other words, this class contains assignments of logical machines to network groups. A TA_LMID may be included in many TA_NETGROUP groups. When one LMID connects to another LMID, the BRIDGE process determines the subset of network groups to which the two LMIDs belong. When the pair of LMIDs are in several common groups, they are sorted in descending TA_NETPRIO order (TA_NETGRPNO is the secondary sort key). The Network groups with the same TA_NETPRIO will flow network data in parallel. Should a networking error prevent data from flowing through all the highest priority group(s), only then the next lower priority network group(s) are used for network traffic (failover). All network groups with a higher priority than the ones flowing data are retried periodically. Once a network connection is established with a higher TA_NETPRIO value, no further data is scheduled for the lower priority one. Once the lower priority connection is drained, it is disconnected in an orderly fashion (failback).

Attribute Table

TM_MIB(5): T_NETMAP Class Definition Attribute Table

Attribute

Type

Permissions

Values

Default

TA_NETGROUP(r)(*)

string

ru-------

string[1 . .30]

N/A

TA_LMID(r)(*)

string

ru-------

string[1 . .30]

N/A

TA_STATE

string

RW-------

GET: "VAL"

SET: "{NEW | INV}"

N/A

N/A

TA_NADDR

string

rw-r--r--

string[1 . .78]

""

TA_FADDR

string

rw-r--r--

string[0..78]

""

TA_FRANGE

long

rw-r--r--

1 <= num <= 65,535

1

TA_MINENCRYPTBITS

string

rwxrwx---

{0 | 40 | 56 | 128}1

0

TA_MAXENCRYPTBITS

string

rwxrwx---

{0 | 40 | 56 | 128}1

128

(r)—required field for object creation (SET TA_STATE NEW)
(*)—GET/SET key, one or more required for SET operations


 

1 The link-level encryption value of 40 bits is provided for backward compatibility.

Attribute Semantics

TA_NETGROUP: string