OpenTP1 Version 7 Operation
Resource managers provided outside of OpenTP1 (asynchronous RMs) can start and stop without synchronizing with OpenTP1. When you start OpenTP1 while the asynchronous RM to be accessed through the XA interface is inactive and you execute a user server that accesses the asynchronous RM, an xa_open function error occurs and the user server may terminate abnormally or shut down. Possibility of an error is especially high when this type of user server starts automatically (using the facility for starting a specified user server when OpenTP1 starts).
To prevent this situation, you should start OpenTP1 after the asynchronous RM is completely started up. This facility checks the startup of the asynchronous RM registered in OpenTP1 when OpenTP1 starts. If the applicable RM is not started, this facility suspends OpenTP1 until all the asynchronous RMs are started. By using this facility, you do not need to be aware of when to start OpenTP1 and asynchronous RMs when you start the system. This reduces the load on the system.
Whether an asynchronous RM is started is determined by whether the xa_open function provided by the asynchronous RM terminates normally. Therefore, OpenTP1 does not wait for the start of an asynchronous RM whose xa_open function terminates normally even if the RM is not started.
To use this facility, specify the trn_wait_rm_open operand in the transaction service definition. You can specify the number of retries and the interval for checking the startup of an inactive asynchronous RM.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.