Describes Micro Focus-specific xa_open string options available for defining XARs.
Visual COBOL provides xa_open string options for XARs in addition to those provided by each database vendor.
You can add these options to a resource definition by including them in the xa_open string using the format specified by the
database vendor. For example, most databases use a comma separator (,), but Oracle uses a plus sign (+) separator. See your
database documentation for more information.
- LocalTX={T|F}
- Determines how the XAR handles transactions.
- T
- The associated XAR uses local (non-distributed) transactions. This option reduces overhead, and therefore can be a good option
when using a single XAR. Be advised, however, that
LocalTX=T also handles commits and roll backs for each XAR, independent of other resources, and should be used with care.
- F
- The associated XAR uses XA distributed, global transactions. Default.
- ISOLEVEL={CR|RO|RR|SS|SZ|UR}
- Determines the isolation level of transactions for a specific XAR.
-
| Parameter
|
Description
|
| CR
|
Committed Read (default)
|
| RO
|
Read Only (Oracle only)
|
| RR
|
Repeatable Read (not supported on Oracle)
|
| SS
|
Snapshot (SQL Server only)
|
| SZ
|
Serializable
|
| UR
|
Uncommitted Read (not supported on Oracle)
|
- ESLOGGING={0001|0002}
- Provides additional RM switch module diagnostics in the
Enterprise Server console log, including
database API errors:
- 0001
- Excluding traces related to
ESXAEXTCFG.CBL for Vault access with XA.
- 0002
- Everything.
- PACKAGEPATH=schema1[+schema2+...schemaN]
- DB2 only. You can use the following substitution markers to enable customization based on the current
XA resource name,
enterprise server region name, or a combination:
- %REGION%
- The current
enterprise server region name.
- %XARN%
- The current XA resource name.
- %ESUSER%
- The current
user name.