The specification of the PDXAMODE operand affects the scope of the LOCK TABLE UNTIL DISCONNECT specification, as explained as follows:

(a) PDXAMODE=0

1. Resource Manager opened by means of AP coding
   The LOCK TABLE UNTIL DISCONNECT specification remains in effect until the Resource Manager is closed.
   
2. Resource Manager opened separately for each transaction
   The LOCK TABLE UNTIL DISCONNECT specification remains in effect throughout the global transaction.
   

(b) PDXAMODE=1

1. Resource Manager opened by means of AP coding
   
   • Transaction is not moved
     The LOCK TABLE UNTIL DISCONNECT specification remains in effect until the Resource Manager is closed.
     
   • Transaction is moved
     The LOCK TABLE UNTIL DISCONNECT specification remains in effect throughout the global transaction.
     
2. Resource Manager opened separately for each transaction
   The LOCK TABLE UNTIL DISCONNECT specification remains in effect throughout the global transaction.
   

Table 3-7 shows the scope of the LOCK TABLE UNTIL DISCONNECT specification when OpenTP1 is used.

Table 3-7 Scope of the LOCK TABLE UNTIL DISCONNECT specification when OpenTP1 is used

PDXAMODE specification	OpenTP1 specification				Scope of LOCK TABLE UNTIL DISCONNECT
0	trn_rm_open_close_scope=process				Effective until Resource Manager is closed.
	trn_rm_open_close_scope=transaction				Effective within a global transaction.
1	trn_rm_open_close_scope=process	-d option specified in trnstring operand			Effective until the Resource Manager is closed.
		-d option not specified in trnstring operand	A single AP comprises a global transaction in the OpenTP1 system.
			Multiple APs comprise a global transaction in the OpenTP1 system.	A single AP links to the HiRDB XA library.
				Multiple APs link to the HiRDB XA library.	Effective within the global transaction.
	trn_rm_open_close_scope=transaction

Note

The -d option can be specified when the TP1/Server Base version is 03-03 or later and the HiRDB version is for UNIX systems.