Steven Michael Bock - Bainbridge Island WA, US Thomas Phillip Bridges - Morgan Hill CA, US Richard G. Hannan - Sun Lakes AZ, US Steve T. Kuo - San Jose CA, US Richard Schneider - San Jose CA, US Judy Y. Tse - San Jose CA, US Vern Lee Watts - Los Altos CA, US Jack Chiu-Chiu Yuan - San Jose CA, US Jerome Joseph Zentner - Zephyr Cove NV, US Mark Neal Ziebarth - Morgan Hill CA, US
Assignee:
International Business Machines Corporation - Armonk NY
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.
System And Method For Processing Transactions In A Multisystem Database Environment
Steven Michael Bock - Bainbridge Island WA, US Thomas Phillip Bridges - Morgan Hill CA, US Richard G. Hannan - Sun Lakes AZ, US Steve T. Kuo - San Jose CA, US Richard Schneider - San Jose CA, US Judy Y. Tse - San Jose CA, US Vern Lee Watts - Los Altos CA, US Jack Chiu-Chiu Yuan - San Jose CA, US Jerome Joseph Zentner - Zephyr Cove NV, US Mark Neal Ziebarth - Morgan Hill CA, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 15/16 G06F 15/173 G06F 9/46
US Classification:
709219, 709225, 709226, 718105
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.
Michael Bruce Kennedy - San Jose CA, US Robert Mark Magid - Monroe Township NJ, US Mark Neal Ziebarth - Morgan Hill CA, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 15/173
US Classification:
709241
Abstract:
A transaction message is received at a router. A determination is made whether the transaction message includes an affinity. The affinity indicates an administrator-specified preference regarding processing of the transaction message. When the transaction message includes the affinity, a server system to process the transaction message is identified based on the affinity and based on a system affinity of the server system. The system affinity specifies processing characteristics of the server system. The server system includes a set of servers. The transaction message is modified to identify the server system and routed to a message queue.
Michael Bruce Kennedy - San Jose CA, US Robert Mark Magid - Monroe Township NJ, US Mark Neal Ziebarth - Morgan Hill CA, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 15/173
US Classification:
709241
Abstract:
A router receives a transaction message. The router determines whether the transaction message may include an affinity indicating a preference regarding processing of the transaction message. The transaction message may be modified to include an identification of a server system to process the modified transaction message based on the determination of the affinity. The router may route the modified transaction message to a coupling facility. A notification message may be received from the coupling facility, where the notification message requests a server associated with or including the router to send a bid to process the modified transaction message. The router may send the bid to process the modified transaction message to the coupling facility. An authorization message, to process the modified transaction message, may be received from the coupling facility based on a timestamp of the bid.
System And Method For Generating Messages For Use In Transaction Networks
George S. Denny - San Jose CA Robert S. Lai - San Jose CA Sherry H. Li - Morgan Hill CA Joseph F. Murphy - San Jose CA Hoang M. Nguyen - San Jose CA Mark N. Ziebarth - Morgan Hill CA
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
H04L 2908 H04L 1200 G06F 1342
US Classification:
39520017
Abstract:
A communication system includes a network of transaction management systems having the same or different operating system software versions. Each transaction management system includes an associated input device for generating a transaction request or message switch. The transaction requests and message switches generated by a particular input device can be executed by the transaction management system associated with the device, and alternatively by remote transaction management systems in the network. To provide for remote execution of transaction requests and message switches, the system includes means for generating transaction request messages and message switch messages that have prefixes which can be dynamically extended as required for use by the appropriate remote transaction management system, without requiring upgrading the software of the remote system.