The two methods explained as follows are provided for registering HiRDB into the transaction manager as a resource manager.

Dynamic registration

When this method is used, the UAP is placed under the control of the transaction manager when the UAP issues the first SQL statement in a transaction. In the case of a UAP that accesses multiple resource managers including HiRDB, or in the case of a UAP that may not access HiRDB at all, dynamic registration reduces the transaction manager's transaction control overhead with respect to HiRDB.

Static registration

When this method is used, the UAP is placed under the control of the transaction manager, regardless of whether or not the UAP issues SQL statements. If the transaction manager is OpenTP1 and the connection between the UAP and HiRDB is severed (e.g., due to abnormal termination of the unit or the server process), static registration eliminates the need to restart the UAP, because an OpenTP1 facility will reconnect the UAP when a transaction is started.

For details about registering HiRDB into the transaction manager, see the HiRDB Version 8 Installation and Design Guide.