Open and Close Strings

Most XA-compliant transaction processing monitors provide a way to pass startup information (referred to as the open string) to the database resource manager when opening it. Similarly, most TP monitors provide a way to pass shutdown information (referred to as the close string) to the database resource manager when closing it. SQL Server expects to receive both an open and a close string from the TP monitor. SQL Server’s open and close strings are identical. The open and close strings take the form:

Tm=TPMonitorName, RmRecoveryGuid=RecoveryGUID

where

TPMonitorName

Is the name of the transaction processing monitor. The name can be up to 40 characters in length. Typical values for TPMonitorName are:

TUXEDO

TOPEND

ENCINA

RecoveryGUID

Is a global unique identifier in registry format but without braces. To obtain a RecoveryGUID, run the guidgen utility program. A unique RecoveryGUID must be specified for each XA program on a system. If you run multiple instances of a program on a system, each instance of the program must have a unique RecoveryGUID.

Example

Here is a sample open or close string:

Tm=ENCINA, RmRecoveryGuid=AC0BE353-3046-11CF-B48D-00AA00A2FA25
  

Each XA-compliant transaction processing monitor has its own mechanism for specifying the open and close strings. For Tuxedo, the open and close strings are specified in the “GROUPS Section” of the UBBCONFIG file. For TOP END, the open and close strings are specified in the RMSWITCH.C file, which is used to produce the RMSWITCH.DLL file. For Encina, the open and close strings are specified by the system administrator through the Encina Enconsole facility.