- TA_IPCKEY: 32K+1 <= 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 system 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 multimachine 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. States not listed will not be returned.
|
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 < 32K
- 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 < 32K
- 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_MAXCONV: 0 <= num < 32K
- 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_MAXGTT: 0 <= num < 32K
- 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_MAXBUFSTYPE: 1 <= num < 32K
- Maximum number of buffer subtypes that can be accommodated in the Bulletin Board buffer subtype table.
- TA_MAXBUFTYPE: 1 <= num < 32K
- Maximum number of buffer types that can be accommodated in the Bulletin Board buffer type table.
- TA_MAXDRT: 0 <= num < 32K
- 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 system 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_MAXOBJECTS
- The default maximum number of active objects to be accommodated in the Active Object Map tables in the Bulletin Board.
- TA_CURINTERFACES
- The current number of interface entries used in the Bulletin Board interface tables.
- TA_HWINTERFACES
- The high water number of interface entries used in the Bulletin Board interface tables. TA_MAXNETGROUPS: 1 <= num < 8192 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_MAXINTERFACES: 0 <= num < 32,766
- Specifies the maximum number of interfaces to be accommodated in the interface table of the Bulletin Board. This value must be greater than zero and less than 32,766. If not specified, the default is 100.
Note: All instances of an interface occupy and reuse the same slot in the interface table in the Bulletin Board. For example, if server SVR1 advertises interfaces IF1 and IF2, SVR2 advertises IF2 and IF3, and SVR3 advertises IF3 and IF4, the interface count is 4 (not 6) when calculating MAXINTERFACES.
- TA_MAXMACHINES: 256 = num 8K-1
- Maximum number of machines that can be accommodated in the Bulletin Board machine table.
- Limitation: BEA Tuxedo system 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 < 8K
- 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 < 32K
- 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< 8K
- Maximum number of servers to be accommodated in the Bulletin Board server table. Allowances should be made in setting this attribute for system supplied administrative servers. Administration of each BEA Tuxedo system site adds approximately one server. Additionally, if TMSs are specified for any server groups (see T_GROUP TA_TMSNAME attribute), then they will be booted along with their server group and should be accounted for in setting TA_MAXSERVERS.
- TA_MAXSERVICES: 1 <= num < 32,766
- Maximum number of services to be accommodated in the Bulletin Board service table. Allowances should be made in setting this attribute for system supplied servers offering services for administrative purposes. Administration of each 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 < 16K
- 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(3c) 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(3c) 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(3c) 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 application. 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(3c) time should receive unsolicited messages.
- Limitations: Run-time modifications to this attribute do not affect active clients. All signaling of client processes is done by administrative system processes and not by application processes. Therefore, only clients running with the same UNIX system user identifier can be notified using the SIGNAL method.
- 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).
- Limitations: Updates to this attribute value in a running application affect only newly started clients and newly configured T_SERVER objects.
- TA_OPTIONS: {LAN|MIGRATE|ACCSTATS],*}
- 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).
- 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.
- 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 < 32K
- 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 < 32K
- 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 < 32K
- 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 < 32K
- 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 < 32K
- Current number of in use Bulletin Board routing table entries.
- TA_CURGROUPS: 0 <= num < 32K
- Current number of in use Bulletin Board server group table entries.
- TA_CURMACHINES: 0 <= num < 32K
- Current number of configured machines.
- TA_CURQUEUES: 0 <= num < 32K
- Current number of in use Bulletin Board queue table entries.
- TA_CURRFT: 0 <= num < 32K
- Current number of in use Bulletin Board routing criteria range table entries.
- TA_CURRTDATA: 0 <= num < 32K
- Current size of routing table string pool.
- TA_CURSERVERS: 0 <= num < 32K
- Current number of in use Bulletin Board server table entries.
- TA_CURSERVICES: 0 <= num < 32K
- Current number of in use Bulletin Board service table entries.
- TA_CURSTYPE: 0 <= num < 32K
- Current number of in use Bulletin Board subtype table entries.
- TA_CURTYPE: 0 <= num < 32K
- Current number of in use Bulletin Board type table entries.
- TA_HWDRT: 0 <= num < 32K
- High water number of in use Bulletin Board routing table entries.
- TA_HWGROUPS: 0 <= num < 32K
- High water number of in use Bulletin Board server group table entries.
- TA_HWMACHINES: 0 <= num < 32K
- High water number of configured machines.
- TA_HWQUEUES: 0 <= num < 32K
- High water number of in use Bulletin Board queue table entries.
- TA_HWRFT: 0 <= num < 32K
- High water number of in use Bulletin Board routing criteria range table entries.
- TA_HWRTDATA: 0 <= num < 32K
- High water size of routing table string pool.
- TA_HWSERVERS: 0 <= num < 32K
- High water number of in use Bulletin Board server table entries.
- TA_HWSERVICES: 0 <= num < 32K
- High water number of in use Bulletin Board service table entries.
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(3c) 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).
