Upgrade Guide - Prolifics

Transaction ManagerTransaction ManagerFor information on API changes (functions, properties, commands, slice events), referto page 1-28, “Transaction Manager API Changes.”Transaction Manager Common ModelThe previous set of database-specific transaction models delivered with Panther havebeen replaced with smaller, more manageable models. In addition to thedatabase-specific model, each engine also accesses a common transaction model,containing the functionality common to all of the database engines. The source codefor the new database-specific transaction models is provided and can be modified tomake global changes in transaction manager functionality. The common model shouldnot be modified; however, the source code is available for reference.Having a database-specific model expands the event processing in the transactionmanager. As in previous versions, the transaction manager first checks to see if anevent function has been specified for the event. If so, it is processed; otherwise, thetransaction manager proceeds to the database-specific transaction model. Ifdatabase-specific processing for the event is required, it must be contained in thismodel. Otherwise, the transaction manager proceeds to the common transaction modeland performs the processing defined there.To call the common model in addition to an event function and the database-specificmodel, have the event processing in the event function and the database-specific modelreturn TM_PROCEED, which passes the processing to the next level. The common modelis always called for TM_START and TM_FINISH events.The common model provides plausible processing for every event known to thetransaction manager. This includes default behavior for the database transactionevents. While a majority of the database-specific transaction models set the mode toinitial after a database transaction is committed, the common model does not, leavingthis for the database-specific transaction models.1-44 Upgrading to Panther from JAM 7