Register the names of various resource managers which are not provided by the OpenTP1. Use either methods to register them in OpenTP1:

• Use the dcsetup command to set up the OpenTP1, then execute the trnlnkrm command.
• Create an extended RM registration definition.

Once you create an extended RM registration definition, you need not execute the trnlnkrm command after setting up the OpenTP1 with the dcsetup command. For details on how to use the trnlnkrm command, see the manual OpenTP1 Operation. For details on how to specify extended RM registration definitions, see the manual OpenTP1 System Definition.

To create executable files for a UAP, you must link the object files used for transaction control with the DBMS libraries and object modules.

Use the trnmkobj command to make object files used for transaction control. For details on the trnmkobj command, see the manual OpenTP1 Operation.

To use DBMSs, you must use trnstring in the transaction service definition and, if necessary, use trnrmid in the user service definition or user service default definition. Specified contents include the items for DBMSs. For details on such items, see the appropriate manuals for the database you use.

For details on definitions using trnstring and trnrmid, see the manual OpenTP1 System Definition.

When a non-OpenTP1 resource manager is used, you must define the set format in the transaction service definition and extend the size of the thread stack area.

For details on the set format definition, see the manual OpenTP1 System Definition.

Some DBMS may require special environment variables for use with OpenTP1 UAPs. If they are necessary, you must use putenv in the transaction service definition, user service definition, or user service default definition.

For details on definitions using putenv, see the manual OpenTP1 System Definition.