SQL xa_open string Configuration Options

Enterprise Server 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.

UserP={T|F}

Determines how to establish the identity of the current Enterprise Server user for each CICS transaction or batch job.

T

The identity for the connection is established via the credentials of the current Enterprise Server user for each CICS transaction or batch job. This is known as User Impersonation. To use this option, the credentials supplied in the open string must be for an account that can impersonate other users, but otherwise should have minimal database privileges and access rights. See User Impersonation for CICS and JCL for more information.

Note:

• DB2 and Oracle - When UserP=T is set for a DB2 or an Oracle XAR that uses dynamic registration, you must build the module in Enterprise Developer. When building CICS and Oracle DSNRLI applications, specify the XAID compiler directive option; however, this is not required for other DB2 or Oracle batch processing.
• One-phase commit for ODBC - UserP=T is supported only for SQL Server on Windows and Linux platforms only.
• User Impersonation is not supported for Web services.

F

The identity for the connection is established via the credentials supplied in the xa_open string and does not change. Default.

LNAME={T|F}

Determines how the XAR handles long user names during user impersonation.

T

The associated long user names of the current Enterprise Server user for each CICS transaction or batch job is used for establishing connection during user impersonation. See Long Usernames and Passwords for more information.

F

Default. The current Enterprise Server user for each CICS transaction or batch job is used for establishing connection during user impersonation.

BatchOnly={T|F}

Determines the availability of XA resources in Enterprise Server SEPs.

T

Makes the associated XAR available in Enterprise Server via JCL only for batch jobs and their corresponding SEPs only. This saves transactional workload overhead because it does not require that a connection be opened in other Enterprise Server SEPs.

F

Makes the associated XAR available in all Enterprise Server SEPs. Default.

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. Avoid setting LocalTX=T on jobs that use both VSAM and SQL.

F

The associated XAR uses XA distributed, global transactions. Default.

Note: DB2 and Oracle - When LocalTX =T is set for a DB2 or an Oracle XAR that uses dynamic registration, you must specify the XAID compiler directive option when building your CICS DSNRLI applications; however, this is not required for other DB2 or Oracle batch processing.

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)

Note: DB2 and Oracle - When ISOLEVEL is set for a DB2 or an Oracle XAR that uses dynamic registration, you must specify the XAID compiler directive option when building your CICS DSNRLI applications; however, this is not required for other DB2 or Oracle batch processing.

ESLOGGING=0001

Provides additional RM switch module diagnostics in the Enterprise Server console log, including JCL connection or database API errors.

PACKAGEPATH=schema1[+schema2+...schemaN]

DB2 only. You can use the following substitution markers to enable customization based on the current JCL or CICS user name, 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 CICS or JCL user name.

Notes:

• When used with UserP, the PACKAGEPATH value changes when the user for the connection changes.
• When PACKAGEPATH is set for a DB2 XAR that uses dynamic registration, you must build the module in Enterprise Developer. When building CICS applications, specify the XAID compiler directive option. This is not required for other batch processing.