XA interface object files provided by resource managers have not been linked with a transaction service control executable-form program and a client service execution-form program that are used to install an OpenTP1 program product. When the dcsetup command is executed, the system determines the installed OpenTP1 program product and automatically links XA interface object files of a resource manager (DAM, TAM, MCF, ISAM, or MQA) provided by OpenTP1. To execute a transaction using a non-OpenTP1 resource manager under OpenTP1, execute the dcsetup command and then execute the trnlnkrm command to catalog the non-OpenTP1 resource manager before starting OpenTP1. Executing the trnlnkrm command re-creates a transaction service control executable-form program, a client service executable-form program and a standard transaction control object file. For information needed when non-Hitachi databases are used, see the manual OpenTP1 Programming Guide.

The XA interface object files provided by all resource managers and to be accessed by UAPs working under OpenTP1 must be linked with the transaction service control execution-form program and client service executable-form program. It is impossible to start any UAP that links XA interface object files for the resource manager that is not linked with the transaction service control executable-form program and client service execution-form program.

Up to 32 resource managers can be cataloged under OpenTP1.

The trnlnkrm command with the -D or -d option specified deletes a resource manager that is no longer accessed from a transaction executed under OpenTP1. Executing this command with the -D or -d option specified deletes XA interface object files for the resource manager specified from a transaction service control executable-form program and a client service executable-form program.

The trnlnkrm command can be used in offline mode only.