Browse Prior Art Database

Transaction Retry With Trace

IP.com Disclosure Number: IPCOM000039652D
Original Publication Date: 1987-Jul-01
Included in the Prior Art Database: 2005-Feb-01
Document File: 2 page(s) / 56K

Publishing Venue

IBM

Related People

Moore, LD: AUTHOR [+2]

Abstract

This invention relates to an adaptive method for retrying a transaction in a transaction-oriented system. In this method, all changes to the system are written to a log in support of recovery in the event of interruption. Each transaction utilizes BEGIN, COMMIT, and ROLLBACK primitives so as to bound the transaction. REDOs ensure transaction return to the most recent COMMIT point, while UNDOs ensure return to the transaction BEGIN point. Referring now to the figure, there is shown the control flow for the transaction retry, reference being made to such publicly described system as the IBM Information Management System (IMS) with trace and fast path options therein.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 2

Transaction Retry With Trace

This invention relates to an adaptive method for retrying a transaction in a transaction-oriented system. In this method, all changes to the system are written to a log in support of recovery in the event of interruption. Each transaction utilizes BEGIN, COMMIT, and ROLLBACK primitives so as to bound the transaction. REDOs ensure transaction return to the most recent COMMIT point, while UNDOs ensure return to the transaction BEGIN point. Referring now to the figure, there is shown the control flow for the transaction retry, reference being made to such publicly described system as the IBM Information Management System (IMS) with trace and fast path options therein. The method steps include (a) upon interruption of a predetermined type, such as a software failure, UNDOing and retrying the transaction while concurrently recording an execution trace thereof (steps 1-7); and (b) in the event of subsequent interruption (step 8), substituting another execution path for the one being presently executed as a function of indicia embedded in the recorded trace (steps 9-12).

1

Page 2 of 2

2

[This page contains 3 pictures or other non-text objects]