System and method for processing transactions in a multisystem database environment

• US 7,814,176 B2
• Filed: 05/30/2008
• Issued: 10/12/2010
• 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, Zentner, Jerome Joseph, Bridges, Thomas Phillip, Watts, Vern Lee, Bock, Steven Michael, Hannan, Richard G., Ziebarth, Mark Neal, Kuo, Steve T., Tse, Judy Y., Yuan, Jack Chiu-Chiu
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Baturay; Alicia
• Application Number:
  US12/130,336
• Publication Number:
  US 20080228872A1
• Time in Patent Office: 865 Days
• Field of Search: 707/2, 707/3, 707 8- 10, 709/219, 709/225, 709/229, 718/105
• 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 system for satisfying a request from a client for a send-then-commit transaction, comprising:

a front-end information management system (IMS) server;

at least one shared message queue (SMQ); and

plural back-end IMS servers connected to the front-end IMS server via the SMQ, the front-end IMS server receiving the request from the client and transmitting the request to the SMQ, at least one back-end IMS server accessing the SMQ and generating a transaction output in response to the request, the back-end IMS server transmitting the result to the front-end IMS server, the front-end IMS server interfacing with the client to communicate the response thereto, wherein the front-end IMS server causes the transaction to commit upon successful interfacing with the client to communicate the response thereto, otherwise the front-end IMS server causing the transaction to be backed out.

2. The system of claim 1, further comprising:

a cross-system coupling facility (XCF) connected to the front-end IMS server and the back-end IMS servers.

3. The system of claim 2, wherein the transaction output is transmitted to the front-end IMS server via the XCF.

4. The system of claim 3, wherein the transaction is non-conversational and the transaction output is less than sixty-one kilobytes (61 k).

5. The system of claim 2, wherein the transaction output is transmitted to the front-end IMS server via the SMQ.

6. The system of claim 5, wherein the transaction is conversational.

7. The system of claim 5, wherein the transaction is non-conversational and the transaction output is greater than sixty-one kilobytes (61 k).

8. A computer program device, comprising:

a non-transitory computer readable storage medium executable by a digital processor for satisfying a send-then-commit transaction request between a client and a front-end IMS server, comprising;

logic for receiving the request at at least one front-end IMS servers;

logic for transmitting the request to at least one SMQ;

logic for accessing the SMQ with multiple back-end IMS servers;

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

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

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

logic for committing the transaction output if the attempting act is successful,

9. The computer program device of claim 8, further comprising:

logic for hacking out the transaction output if the attempting act is unsuccessful.

10. The computer program device of claim 9, further comprising:

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

11. The computer program device of claim 10, wherein the transaction is conversational.

12. The computer program device of claim 10, wherein the transaction is non-conversational and the transaction output is greater than sixty-one kilobytes (61 k).

13. The computer program device of claim 9, further comprising:

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

14. The computer program, device of claim 13, wherein the transaction is non-conversational and the transaction output is less than sixty-one kilobytes (61 k).