|
|
The Domains MIB describes the interaction between BEA Tuxedo domains. The term access point defines an object through which you gain access to another object. Therefore, you access a remote domain through a remote domain access point, and remote domains gain access to a local domain through a local domain access point.
The Domains MIB consists of the following groups.
The tuxDmAclTable group contains objects that represent access control information for domains.
The list of remote domain access points associated with this access control list. tuxDmrAccessPointlist is a comma-separated list of remote access point names (that is, the value of the tuxDMRemoteDmAccessPoint object of a valid tuxDmRemote object). The list can contain up to 50 remote access point identifier elements. Setting the value of this object to "*" means that all the remote domains in the configuration are associated with this entry. blank string means no remote access points are associated with this entry. The default is - (equivalent of NULL string).
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmAcl instance.
GET requests:
valid(1): tuxDmAcl object is defined and inactive. This state is the only valid state for this group. ACL groups are never active.
SET requests:
The tuxDmConnectionTable group contains objects that represent the status of connections between domain access points.
The name of the local domain access point that identifies the connection between the domains.
The name of the remote domain access point that identifies the connection between the domains
The type of domain, such as tdomain.
INTEGER { active(1) | suspended(2) | initializing(3) | inactive(4) | unknown(5)}
This object denotes the current state of the tuxDmConnection instance.
GET requests:
suspended(2): The connection is awaiting retry.
initializing(3): The connection is initializing.
inactive(4): The specified domain access points are disconnected. (Returned in case of Tuxedo 7.1 and later only.)
unknown(5): The state cannot be determined.
SET requests:
active(1):Connect the specified domain access points. If the current state is suspended or inactive, SET:active places the connection into the state initializing, otherwise, there is no change.
INTEGER { enc-0-bit(1) | enc-40-bits(2) | enc-56-bits(3) | enc-128-bits(4)}
This object is available when tuxDmConDmType=tdomain.
The level of encryption in use on this connection:
enc-0-bit(1)
enc-40-bits(2), enc-56-bits(3), and enc-128-bits(4)
The tuxDmExportTable group contains objects that represent local resources that are exported to one or more remote domains through a local access point.
The local resource name for entries of resource type service (the service name), qspace (the queue space name), and qname (the queue name). For a service entry, the value of this object corresponds to the value of an active tuxTSrvGrp:tuxTsvcName object. This resource is exported to other domains with the same name or with the alias defined in the tuxDmExpDmRemoteName objects.
The local access point name. Setting this object to "*" means the resource is available at all local access points.
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmExport instance.
GET requests:
SET requests:
The name of a tuxDmAcl object to use for security on this local service. This object is not permitted if tuxDmExpDmResourceType=qname.
Specifies whether this local service is conversational or not.
INTEGER { service(1) | qspace(2) | qname(3)}
Specifies whether this entry is for a service, qspace, or qname. The default is service.
For entries of type service or qspace, this object specifies the name exported through non-topend remote access points.
Attributes available from remote access points of tuxDmExpDmResourceType=snax|ositp:
type[:subtype] -Input buffer type, optionally followed by subtype.
If this object is present, it defines the buffer type (and subtype) accepted. This object should be defined for entries of tuxDmExpDmResourceType=service when access is permitted from remote access points using ositp with the UDT application context, or when using snax. This object is not permitted if tuxDmExpDmResourceType=qspace.
Attributes available from remote access points of tuxDmExpDmResourceType=snax|ositp:
type[:subtype] -Output buffer type, optionally followed by subtype.
If this object is present, it defines the buffer type (and subtype) output by the service. This object should be defined for entries of tuxDmExpDmResourceType=service when access is permitted from remote access points using ositp with the UDT application context, or when using snax. This object is not permitted if tuxDmExpDmResourceType=qspace and qname.
The tuxDmImportTable group contains objects that represent remote resources that are imported through one or more remote domain access points and made available to the local domain through one or more local domain access points.
The remote resource name used for entries of resource type service (the service name, qspace (the queue space name), and qname (the queue name). This resource is imported from remote domains with the same name or with the alias defined in the tuxDmImpDmRemoteName or tuxDmImpDmte* objects.
Identifies the remote domain access point through which this resource should be imported. This object value is a comma-separated failover domain list; it can contain up to three remote domain access points. If this object is set to "*", the resource can be imported from all remote access points.
The name of the local domain access point through which this imported resource should be made available. If set to the null string, the resource is made available through all local domain access points.
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmImport instance.
GET requests:
SET requests:
invalid(2): The object is deleted. A state change is allowed in the active or suspended state and results in the invalid state.
When a request is received for a resource that is not already within a transaction, this object automatically starts a transaction for the resource. The default is no(2).
A boolean value (yes or no) specifies whether the service is conversational.
The dequeuing priority. Service requests with a higher priority are serviced first.
INTEGER { service(1) | qspace(2) | qname(3)}
Specifies whether this entry is for a service, qspace, or qname. The default is service.
For entries of type service or qspace, this object specifies the name imported through non-topend remote access points.
The name of a tuxDmRoutingTable object to use for routing criteria for this service or qspace.
Transaction time value (in seconds) of transactions automatically started for this service or qspace. Transactions are started automatically when a request not in transaction mode is received and the tuxDmImpDmAutoTran object is set to yes.
Limitation: Run-time updates to this object are not reflected in active requests.
Attributes available from remote access points of tuxDmRemoteDmType=snax|ositp:
type[:subtype] - Input buffer type, optionally followed by subtype. If this object is present, it defines the buffer type (and subtype) accepted. This object should be defined for entries of DMRESOURCETYPE=service when access is permitted to remote access points that use ositp with the UDT application context, or that use snax. This object is not permitted if tuxDmImpDmResourceType=qspace.
Attributes available from remote access points of tuxDmRemoteDmType=snax|ositp:
The tuxDmLocalTable group defines a local domain access point. A local domain access point is used to control access to local services exported to remote domains and to control access to remote services imported from remote domains.
This object value is an identifier unique within the scope of tuxDmLocal and tuxDmRemote entry names in the domain configuration.
The domain access point identifier. This identifier is unique across all local and remote domain access points.
The group in which the administrative servers and gateway processes of the local domain reside.
INTEGER { tdomain(1) | ositp(2) | snax(3)}
The type of domain: tdomain for a BEA Tuxedo domain, ositp for an OSI domain, and snax for an SNA domain. The presence or absence of other objects depends on the value of this object.
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmLocal instance.
GET requests:
SET requests:
DisplayString (SIZE(1..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
The name of the audit log file for this local domain.
Specifies the maximum wait time allowed for a blocking call. The value sets a multiplier of the SCANUNIT parameters specified in the tuxTdomain group. The value SCANUNIT * tuxDmLclDmBlockTime must be greater than or equal to SCANUNIT and less than 32,768 seconds. If this object is not specified, the default is set to the value of the tuxDmLclDmBlockTime object specified in the tuxTdomain object. A timeout always implies a failure of the affected request. Notice that the timeout specified for transactions in the tuxTdomain is always used when the request is issued within a transaction.
The maximum number of remote domain access points that can be involved in a single transaction.
The maximum number of simultaneous transactions allowed on this local domain access point. This number must be greater than or equal to the tuxTdomainMaxGTT object in the tuxTdomain group.
INTEGER { none(1) | app-pw(2) | dm-pw(3) | dm-user-pw(4) | te-clear(5) | te-safe(6) | te-private(7)}
The type of security enabled on this domain. This object must be set to one of the following:
none(1)
app-pw(2)
dm-pw(3)
dm-user-pw(4)
DisplayString (SIZE(1..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
The device (raw slice) or file that contains the domain TLOG for this local domain access point. The TLOG is stored as a BEA Tuxedo system VTOC table on the device. For reliability, the use of a device (raw slice) is recommended.
The domain TLOG name for this local domain access point. If more than one TLOG exists on the same device, each TLOG must have a unique name.
The size in pages of the TLOG for this local domain access point. This size is constrained by the amount of space available on the device identified in tuxDmLclTlogDev.
INTEGER { on-demand(1) | on-startup(2) | incoming-only(3)}
Attributes available when tuxDmRemoteDmType=tdomain.
Specifies the conditions under which a local domain gateway tries to establish a connection to a remote domain. Supported values are:
on-demand(1)
connect" command. The default setting for this object is on-demand. The on-demand policy provides the equivalent behavior to previous releases, in which this object was not explicitly available.
on-startup(2)
tuxDmLclMaxRetry and tuxDmLclDmRetryInterval objects.
The number of seconds between automatic attempts to establish a connection to remote domain access points. The minimum value is 0 and the maximum value is 2147483647. The default setting is 60. If tuxDmLclDmMaxRetry is set to 0, setting tuxDmLclDmRetryInterval is not allowed.
This object is valid only when the tuxDmLclDmConnectionPolicy object is set to on-startup. For other connection policies, automatic retries are disabled.
The number of times that a domain gateway tries to establish connections to remote domain access points. The minimum value is 0 and the maximum is MAXLONG. MAXLONG indicates that retry processing is repeated indefinitely, or until a connection is established. For a connection policy of on-startup, the default setting for tuxDmLclMaxRetry is MAXLONG. Setting this object to 0 turns off the auto retry mechanism. For other connection policies, auto retries are disabled.
The tuxDmLclMaxRetry object is valid only when the connection policy is on-startup.
The connection principal name identifier. This object value is the principal name used for verifying the identity of this local domain access point when establishing a connection to a remote domain access point. This object only applies to domains of type TDOMAIN that are running BEA Tuxedo 7.1 or later software.
This object can contain a maximum of 511 characters (excluding the terminating null character). If this object is not specified, the connection principal name defaults to the tuxDmLclDmAccessPointId string for this local domain access point.
For default authentication plug-ins, if a value is assigned to this object for this local domain access point, it must be the same as the value assigned to the tuxDmLclAccessPointId object for this local domain access point. If these values do not match, the local domain gateway process does not boot and the system generates the following userlog(3c) message: "ERROR: Unable to acquire credentials".
Used for grouping domains so that encoding/decoding of messages between domains can be bypassed. If no value is specified, the default is to turn encoding/decoding on. If the value set for this object is the same in both the DM_LOCAL and the DM_REMOTE section of a domain configuration file, data encoding/decoding is bypassed. The value set for this object can be any string value up to 15 characters in length. The value is used only for comparison.
This object is valid only when tuxDmRemoteDmType=tdomain.
This object is relevant only to local domain access point entries. It specifies the amount of shared memory allocated to storing binary large object log information specific to ositp.
The tuxDmOsitpTable group contains objects that define the OSI TP protocol-related configuration information for a specific local or remote domain access point.
The domain access point name for which this entry provides the protocol-specific configuration information. This object matches the domain access point name given in the tuxDmLocal or tuxDmRemote entry that defines the protocol-independent configuration of the domain access point.
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmOsitp instance.
GET requests:
SET requests:
The application process title of the domain access point in object identifier form.
The application entity qualifier of the domain access point in integer form.
This object, which specifies the network device to be used, is relevant when it defines a local domain access point and ignored for a remote domain access point.
The application context name to use with this domain access point. When you establish a dialogue to a remote domain access point, use the application context name from the remote domain access point, if it is present. If the application context name from the remote domain access point is absent, use the application context name from the local domain access point. The value xatmi selects the use of the X\Open-defined xatmi Application Service Element (ASE) and encoding. The value udt selects the use of the ISO/IEC 10026-5 User Data Transfer encoding.
This optional object defines the application process-invocation identifier to be used on this domain access point.
This optional object defines the application entity-invocation identifier to be used on this domain access point.
This object specifies the user portion of the OSI TP recovery context handle. It can be required by an OSI TP provider in order to perform recovery of distributed transactions after a communication line or system failure.
This object is relevant for defining a local domain access point and ignored for a remote domain access point.
This object specifies the number of endpoints awaiting incoming OSI TP dialogue. It is relevant for defining a local domain access point and ignored for a remote domain access point.
INTEGER { cae(1) | preliminary(2) | oltp-tm2200(3) }
This object specifies the version of the XATMI protocol used to communicate with a remote system. Valid values are: cae, preliminary, and oltp-tm2200.
This object is relevant for remote domain access points and ignored for local domain access points.
The tuxDmPasswordTable group contains objects that represent configuration information for inter-domain authentication through access points of type tdomain.
The name of the local domain access point to which the password applies.
The name of the remote domain access point to which the password applies.
The local password used to authenticate connections between the local domain access point identified by tuxDmPasswdDmlAccessPoint and the remote domain access point identified by tuxDmPasswdDmrAccessPoint.
The remote password used to authenticate connections between the local domain access point identified by tuxDmPasswdDmlAccessPoint and the remote domain access point identified by tuxDmPasswdDmrAccessPoint.
INTEGER { valid(1) | invalid(2) | recrypt(3) }
This object denotes the current state of the tuxDmPassword instance.
GET requests:
SET requests:
The tuxDmPrincipalMapTable group contains objects that represent configuration information for mapping principal names to and from external principal names across access point of type snax.
The local domain access point to which the principal mapping applies.
The remote domain access point to which the principal mapping applies.
The local principal name in the principal mapping.
The remote principal name in the principal mapping.
INTEGER { in(1) | out(2) | both(3) }
The direction to which the principal mapping applies.
in(1)
out(2)
both(3)
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmPrincipalMap instance.
GET requests:
SET requests:
The tuxDmRemoteTable group contains objects that represent remote domain access point configuration information. Local resources that can be exported through one or more local domain access points are made accessible to a remote domain through a remote domain access point. Similarly, remote resources are imported from a remote domain through a remote domain access point.
The name of this tuxDmRemote entry. This object value is an identifier unique within the scope of tuxDmLocal and tuxDmRemote entry names in the domain configuration.
The access point identifier. This identifier is unique across all local and remote domain access points.
INTEGER { tdomain(1) | ositp(2) | snax(3)}
tdomain(1)
ositp(2)
snax(3)
The presence or absence of other objects depends on the value of this object.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmRemote instance.
GET requests:
SET requests:
Attributes available when tuxDmRemoteDmType=snax. The name of the default translation tables to use when translating requests and replies that are sent through this access point.
Attributes available when tuxDmRemoteDmType=tdomain.
These objects are used for grouping domains so that encoding/decoding of messages between domains can be bypassed. If it is not specified, the default is to turn encoding/decoding on. If the value set for this object is the same in both the DM_LOCAL and the DM_REMOTE sections of a domain configuration file, data encoding/decoding is bypassed. The value set for this object can be any string value up to 15 characters in length. The object value is used only for comparison.
The tuxDmResourcesTable group contains an object that represents Domains-specific configuration information.
A user-supplied identifier for the Domains configuration.
The tuxDmRoutingTable group contains objects that represent routing criteria information for routing requests to a domain through a remote domain access point.
The name of the routing criteria table entry.
List of types and subtypes of data buffers for which this routing entry is valid.
type1[:subtype1[,subtype2...]][:type2[:subtype3[,subtype4...]]...]
A maximum of 32 type/subtype combinations is allowed. The types are restricted to the following: FML, XML, VIEW, X-C-TYPE, or X_COMMON. No subtype can be specified for FML or XML; subtypes are required for types VIEW, X_C_TYPE, and X_COMMON ("*" is not allowed).
Note that subtype names should not contain semicolon (;), colon (:), comma (,), or asterisk (*)characters. Duplicate type/subtype pairs cannot be specified for the same routing criterion name; more than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.
This object value is the routing field name. This field is assumed to be an FML buffer, XML buffer, or VIEW field name that is identified in an FML field table (using the FLDTBLDIR and FIELDTBLS environment variables), or an FML VIEW table (using the VIEWDIR and VIEWFILES environment variables), respectively. This information is used to get the associated field value for data-dependent routing to an access point of a remote domain.
For an XML buffer type, this field contains either a routing element type (or name) or a routing element object name.
The syntax of this object for an XML buffer type is as follows:
root_element[/child_element][/child_element][/...][/@object_\
name]
The element is assumed to be an XML document or datagram element type. Indexing is not supported. Therefore, the BEA Tuxedo system recognizes only the first occurrence of a given element type when it processes an XML buffer for data-dependent routing. This information is used to get the associated element content for data-dependent routing while sending a message. The content must be a string encoded in UTF-8.
The object is assumed to be an XML document or datagram object of the defined element. This information is used to get the associated object value for data-dependent routing while sending a message. The value must be a string encoded in UTF-8.
The combination of element name and object name can contain up to 30 characters.
INTEGER { char(1) | short(2) | long(3) | float(4) | double(5) | string(6)}
The type can be char, short, long, float, double, or string. Only one type is allowed. This object value is used only for routing XML buffers.
This object includes the ranges and associated server groups for the tuxDmRoutingFieldType routing field. The format of the string is a comma-separated, ordered list of range/group name pairs. A range/group pair has the following format:
where lower and upper are assigned numeric values or character strings in single quotes. lower must be less than or equal to upper. To embed a single quote in a character string value, the quote must be preceded by two backslashes (for example, `O\\'Brien'). The value MIN can be used to indicate the minimum value for the data type of the associated field on the machine. The value MAX can be used to indicate the maximum value for the data type of the associated field on the machine. Thus, "MIN-5" is all numbers less than or equal to -5, and "6-MAX" is all numbers greater than or equal to 6.
The meta-character "*" (wild-card) in the position of a range indicates any values not covered by the other ranges previously seen in the entry. Only one wild-card range is allowed per entry and it should be the last range (ranges that follow it are ignored).
The routing field can be of any data type supported in FML. A numeric routing field must have numeric range values and a string routing field must have string range values.
String range values for string, carray, and character field types must be placed inside a pair of single quotes, and cannot be preceded by a sign. The short and long integer values are a string of digits, optionally preceded by a plus or minus sign. Floating point numbers are of the form accepted by the C compiler or atof(3): an optional sign, then a string of digits (that optionally contains a decimal point), then an optional e or E followed by an optional sign or space, followed by an integer.
The raccesspoint parameter indicates the remote domain access point to which the request is routed if the field matches the range. A raccesspoint of "*" indicates that the request can go to any remote domain access point that imports the desired service.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmRouting instance.
GET requests:
SET requests:
The tuxDmrPrincipalTable group contains objects that represent password configuration information for remote principal names.
The remote domain access point to which the principal is applicable.
The remote password used for the principal name when communicating through the remote domain access point identified in tuxDmrPrincipalDmrAccessPoint.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmrPrincipal instance.
GET requests:
SET requests:
The tuxDmSnaCRMTable group defines the SNM-CRM-specific configuration information for the named local domain access point.
This object is an identifier, unique within the scope of the SNA CRM entries in the domain configuration, used to identify this SNA CRM entry.
The name of the local domain access point entry with which this SNA CRM is used.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmSnaCRM instance.
GET requests:
SET requests:
DisplayString (SIZE(1..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Specifies the network address for communication between the domain gateway of the local domain access point and the SNA CRM.
Specifies the network device to be used for communication between the domain gateway of the local domain access point and the SNA CRM.
The tuxDmSnaLinkTable group contains objects that represent snax-specific configuration information for a remote domain access point.
This object is an identifier, unique within the scope of the SNA LINK entries within the domain configuration, used to identify rows in this table.
The name of the snax stack entry to be used to reach this remote domain access point.
Identifies the remote domain access point name for which this entry provides the snax configuration data.
The local SYSID used when establishing an SNA link to the remote logical unit (LU).
The remote SYSID used when establishing an SNA link to the remote logical unit (LU).
Specifies the logical unit (LU) name associated with the remote domain access point.
The minimum number of winner sessions to the remote LU.
Specifies the name associated with the session characteristics for sessions to the remote LU.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmSnaLink instance.
GET requests:
SET requests:
INTEGER { local(1) | identify(2) | verify(3) | persistent(4) | mixidpe(5) }
Specifies the type of SNA security to be used on sessions to the remote logical unit. Valid values for this object are local, identify, verify, persistent, and mixidpe.
Specifies the type of session start-up for the destination logical unit (LU).
auto(1)
COLDSTART or WARMSTART the LU.
cold(2)
Specifies maximum number of sessions to establish with the remote LU.
The maximum SYNC LEVEL that can be support to this remote LU.
The tuxDmSnaStackTable group defines an SNA stack to be used by a specific SNA CRM.
The name of this tuxDmSnaStack entry. This object is an identifier, unique within the scope of the tuxDmSnaStackTable in the domain configuration.
Identifies the tuxDmSnaCRM table entry of the SNA CRM in which this SNA protocol stack definition is used.
Identifies the protocol stack to be used.
Specifies the LU name to be used on sessions established using this stack definition.
Specifies the TP name associated with the SNA stack. A value of "*" means accept any TP name.
Provides protocol stack specific parameters.
INTEGER { valid(1) | invalid(2)}
This object denotes the current state of the tuxDmSnaStack instance.
GET requests:
SET requests:
The tuxDmTdomainTable group defines the domain-specific configuration for a local or remote domain access point.
The local or remote domain access point name for which this entry provides the TDomain-specific configuration data.
When domain-level failover is in use, more than one tuxDmTdomainTable entry can be defined with the same tuxTDmTdomainDmAccessPoint.
Specifies the network address associated with the access point.
For a local domain access point, this object supplies the address used to listen for incoming connections.
For a remote domain access point, this object supplies the destination used when you connect to a remote domain access point.
The value of this object must be unique across all tuxDmTdomainTable objects.
INTEGER { valid(1) | invalid(2) }
This object denotes the current state of the tuxDmTdomain instance.
GET requests:
SET requests:
Specifies the network device used.
For a local domain access point, this object specifies the device used for listening.
For a remote domain access point, this object specifies the device used to connect to the remote domain access point.
This object is relevant to remote domain access points only. It specifies the threshold over which compression occurs for traffic on connections to this access point.
This object is relevant to remote domain access points only. It specifies the position of this set of addressing in the failover sequence for this remote domain access point. If no failover sequence number is supplied, the first entry for this remote domain access point is allocated the number 10 greater than the highest failover sequence number known for the remote domain access point. Thus, the first entry gets 10, the second, 20, and so on.
INTEGER { enc-0-bit(1) | enc-40-bits(2) | enc-56-bits(3) | enc-128-bits(4)}
This object is relevant to remote domain access points only. When establishing a network link to this access point, this object specifies the minimum level of encryption required.
enc-0-bit(1)
enc-40-bits(2), enc-56-bits(3), and enc-128-bits(4)
If this minimum level of encryption is not met, link establishment fails. The default value is enc-0-bit.
INTEGER { enc-0-bit(1) | enc-40-bits(2) | enc-56-bits(3) | enc-128-bits(4)}
This object is relevant to remote domain access points only. When establishing a network link to this access point, this object specifies the maximum level of encryption required.
enc-0-bit(1)
enc-40-bits(2), enc-56-bits(3), and enc-128-bits(4)
The default value is enc-128-bits.
| Note: | Modifications to this object do not affect established connections. |
The tuxDmTransactionTable group contains objects that represent information about transactions that span domains. This object can be used to find out what remote domain access points are involved in the transaction, the parent domain access point, the transaction state, and other information.
The name of the local domain access point with which the transaction is associated. This object is a required field for GET operations. For SET operations, this object must be specified.
The transaction identifier returned from tpsuspend(3c) mapped to a string representation. The data in this field should not be interpreted directly by the user, except for equality comparison. For SET operations, this object must be specified.
INTEGER { aborted(1) | abortonly(2) | active(3) | comcalled(4) | decided(5) | done(6) | habort(7) | hcommit(8) | heuristic(9) | ready(10) | unknown(11) | invalid(12) }
This object denotes the current state of the tuxDmTransaction instance.
GET requests:
abortonly(2): The transaction has been identified for rollback.
active(3): The transaction is active.
comcalled(4): The transaction has initiated the first phase of commitment.
decided(5): The transaction has initiated the second phase of commitment.
done(6): The transaction has completed the second phase of commitment.
habort(7): The transaction has been heuristically rolled back.
hcommit(8): The transaction has been heuristically committed.
heuristic(9): The transaction commitment or rollback has completed heuristically.
ready(10): The transaction has completed the first phase of a two-phase commit. All the participating groups and remote domains have completed the first phase of commitment and are ready to be committed.
unknown(11): It was not possible to determine the state of the transaction.
SET requests:
invalid(12): Forget the specified table entry. This state change is only valid in states HCOmmit and HABort.
If the transaction originated from a remote domain, this object value is the name of the remote domain access point through which the transaction originated. If the transaction originated within this domain, this value is the name of the local domain access point.
If the transaction originated from a remote domain, this object value is the external transaction identifier received from the remote domain access point through which the transaction originated. If the transaction originated within this domain, the object contains the same value as the
The number of branches to remote domain access points involved in the transaction. For a domain gateway that does not make branch information available, this value is zero.
The index of the first branch-specific object values (tuxDmTransactionDmBranchNo, tuxDmTransactionDmrAccessPoint, tuxDmTransactionDmNetTranID, and tuxDmTransactionDmBranchState) corresponding to this object.
The branch number of the participating branch (numbered from zero).
The name of the remote domain access point for this branch.
The external transaction identifier used with the remote domain access point for this branch. Some types of domain gateways do not return this information; in this scenario, this object is set to the empty string. For example, TDomains uses the local transaction identifier in tuxDmTransactionDmTpTranID for branches to remote domain access points and sets this value to the empty string.
INTEGER { aborted(1) | abortonly(2) | active(3) | comcalled(4) | decided(5) | done(6) | habort(7) | hcommit(8) | heuristic-hazard(9) | heuristic-mixed(10) | ready(11) | unknown(12) }
A GET operation retrieves run-time information for the transaction branch (when the information is available for a particular domain gateway type).
GET requests:
ABortonlY(2): The transaction branch has been identified for rollback.
ACTive(3): The transaction branch is active.
COMcalled(4): The transaction branch has initiated the first phase of commitment.
DECided(5): The transaction branch has initiated second phase of commitment.
DONe(6): The transaction branch has completed the second phase of commitment.
HABort(7): The transaction has been heuristically rolled back.
HCOmmit(8): The transaction has been heuristically committed.
Heuristic HaZard(9): Communications for the transaction branch failed and it has not been determined if rollback completed successfully.
Heuristic MIxed(10): The transaction commitment or rollback for the transaction branch has completed and the remote domain has reported that the state of some of the resources used for the commitment or rollback is not consistent with the outcome of the transaction.
REAdy 11): The transaction has completed the first phase of a two-phase commit. All the participating groups and remote domains have completed the first phase of commitment and are ready to be committed.
UNKnown(12): The state of the transaction could not be determined.
|