In order for a UAP running under OpenTP1 to access a resource manager within a transaction, a transaction control object file must be linked with that UAP.

For a UAP that accesses all resource managers registered in OpenTP1, the standard transaction control object file named dc_trn_allrm.o (a file under $DCDIR/spool/trnrmcmd/userobj that is created when the dcsetup command is executed, and re-created when the trnlnkrm command is executed) must be linked with that UAP.

For a UAP that does not access all of the source managers registered in OpenTP1, a transaction control object file must be created by executing the trnmkobj command and linked with that UAP.

For a UAP that does not access a resource manager within a transaction, no transaction control object file needs to be linked with that UAP. However, if the trnlnkrm command is executed to change the resource manager registration status, the UAP with which a standard transaction control object file has been linked must be linked again.

Note that linking the same resource manager with all UAPs that make up a global transaction optimizes the commit process (by suppressing process-to-process communication) to enhance transaction performance.

Before starting OpenTP1, the transaction control object file created by the trnmkobj command and the XA interface object file provided by a resource manager must be linked with the UAP.