In order for a UAP working 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 which is created when the dcsetup command is executed and recreated when the trnlnkrm command is executed) must be linked with that UAP.

For a UAP that accesses some of the resource managers registered in OpenTP1, a transaction control object file must be created with the trnmkobj command and linked with that UAP.

No transaction control object file needs to be linked with a UAP that does not access resource managers within a transaction. If the registered condition of resource managers has been changed with the trnlnkrm command, a transaction control object file must be linked again with a UAP with which a standard transaction control object file has been linked.

Before starting OpenTP1, the user must link to the UAP the transaction control object file created by the trnmkobj command and the XA interface object file provided by the resource manager.

A UAP to which the transaction control object file or XA interface object file has not been linked produces an error when a function provided by the resource manager is issued.