The VSAM (CICS) data source supports global transactions and can fully participate in distributed transactions when the transaction environment parameter convertAllToDistributed is set to true.
To use Oracle Connect with global transactions, you must have RRS installed and configured and have CICS TS 1.3 or above installed.
If RRS is not running, then the data source can participate in a distributed transaction as the only one-phase commit data source if the logFile parameter is set to NORRS in the transactions node of the binding properties for the relevant binding configuration on the Design Perspective's Configuration tab in Oracle Studio. The XML representation is as follows:
<transactions logFile="log,NORRS" />
where log is the high-level qualifier and name of the log file. If this parameter is not specified, then the format is the following:
<transactions logFile=",NORRS" />
That is, the comma must be specified.
To use the global transactions capability to access data on the OS/390 or z/OS machine, define every library in the ATTSRVR JCL as an APF-authorized library.
- To define a DSN as APF-authorized, in the SDSF screen enter the command:
where ac002 is the volume where you installed Oracle Connect and NAVROOT is the high-level qualifier where Oracle Connect is installed.
- If the Oracle Connect installation volume is managed by SMS, then when defining APF-authorization enter the following command in the SDSF screen:
- Make sure that the library is APF-authorized, even after an IPL (reboot) of the machine.
The VSAM file participating in the 1PC or global transaction must be defined as recoverable.
To use distributed transactions from an ODBC-based application, ensure that AUTOCOMMIT is set to 0.