System and method for processing transactions in a multisystem database environment

• US 7,406,511 B2
• Filed: 08/26/2002
• Issued: 07/29/2008
• Est. Priority Date: 08/26/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schneider, Richard, Tse, Judy Y., Yuan, Jack Chiu-Chiu, Zentner, Jerome Joseph, Bridges, Thomas Phillip, Watts, Vern Lee, Bock, Steven Michael, Hannan, Richard G., Ziebarth, Mark Neal, Kuo, Steve T.
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Baturay; Alicia
• Application Number:
  US10/228,148
• Publication Number:
  US 20040039777A1
• Time in Patent Office: 2,164 Days
• Field of Search: 707/2, 707/3, 707 8- 10, 718/105, 709/219, 709/225, 709/226
• US Class Current: 709/219
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A system for satisfying a request from a client for a send-then-commit transaction includes a front-end information management system (IMS) server. Shared message queues (SMQ) communicate with the front-end IMS server and plural back-end IMS. The front-end IMS server receives the request from the client and transmits the request to the SMQ. A back-end IMS server accesses the SMQ and generates a transaction output in response to the request. The back-end IMS server transmits the result to the front-end IMS server and the front-end IMS server interfaces with the client to communicate the response thereto. The back-end IMS server and front-end IMS server operate in separate system images, but work together in a resource recovery services (RRS) environment to commit or backout the transaction output.

Claims

1. A method for satisfying a request from a client for a send-then-commit transaction, comprising the acts of:

receiving the request at at least one front-end IMS server;

transmitting the request to at least one SMQ;

accessing the SMQ with multiple back-end IMS servers;

processing the request with at least one of the back-end IMS servers to generate a transaction output;

sending the transaction output to the front-end IMS server;

attempting to successfully interface with the client using the front-end IMS server to communicate the transaction output to the client; and

committing the transaction output if the attempting act is successful, the client deciding whether to commit to the transaction or backout from the transaction.

2. The method of claim 1, further comprising the act of:

backing out the transaction output if the attempting act is unsuccessful.

3. The method of claim 2, further comprising the act of:

transmitting the transaction output to the front-end IMS server via the SMQ.

4. The method of claim 2, further comprising the act of:

transmitting the transaction output to the front-end IMS server via an XCF.

5. The method of claim 3, wherein the transaction is conversational.

6. The method of claim 3, wherein the transaction is non-conversational and the transaction output is greater than sixty-one kilobytes (61 k).

7. The method of claim 4, wherein the transaction is non-conversational and the transaction output is less dan sixty-one kilobytes (61 k).