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.

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.

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.

Abstract: A throttling specification is received by a computer task to direct the computer task's usage of critical computer resources, such as CPU cycles. The computer task comprises units of work, and the elapsed time of each unit of work is calculated as each unit of work completes. Upon the completion of one unit of work, a suspension time is calculated based at least partially on the throttling specification and the elapsed time corresponding to the completed unit of work. Prior to initiating the next unit of work for the computer task, the computer task is suspended for the calculated suspension time. In this manner, other important computing tasks operating in the computer system have access to critical computer resources during the suspension period. Even though the computer task may be given the highest possible priority to ensure a timely and predictable completion, total monopolization of critical computer resources is avoided.

Abstract: A fuzzy data record pointer is utilized for identification of both a target file and a target data record within the target file. A target data record is accessed from a target file, selected from a set of N related files, utilizing a fuzzy data record pointer (“fuzzy”, as used herein, means that the data record pointer need not be coincident with the actual data record address). A modulus for the data record pointer divided by N is computed. This modulus is used to select the target file. A data record address is computed for the target data record utilizing the data record pointer and modulus. In this manner a fuzzy data record pointer is utilized to determine both the target file from a set of N related files and the target data record to be accessed within the target file.

Abstract: A method and apparatus for merging log data for recovering one or more database data sets to any point-in-time in a single pass of log data sets. Using disaster recovery technology, the invention may be implemented to provide a method to reduce the time that a broken database is unavailable by processing recovery input data in parallel and recovering multiple database data sets, including areas, simultaneously. The invention reduces operational complexity and resource constraints experienced by IMS customers trying to recover database data sets especially in a data sharing environment. The invention simplifies the recovery process by eliminating both the need for change accumulation and the need to run separate recovery jobs for each database data set requiring recovery, thereby reducing the impact of recovery on system resources.

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.

Abstract: A throttling specification is received by a computer task to direct the computer task's usage of critical computer resources, such as CPU cycles. The computer task comprises units of work, and the elapsed time of each unit of work is calculated as each unit of work completes. Upon the completion of one unit of work, a suspension time is calculated based at least partially on the throttling specification and the elapsed time corresponding to the completed unit of work. Prior to initiating the next unit of work for the computer task, the computer task is suspended for the calculated suspension time. In this manner, other important computing tasks operating in the computer system have access to critical computer resources during the suspension period. Even though the computer task may be given the highest possible priority to ensure a timely and predictable completion, total monopolization of critical computer resources is avoided.

Abstract: A fuzzy data record pointer is utilized for identification of both a target file and a target data record within the target file. A target data record is accessed from a target file, selected from a set of N related files, utilizing a fuzzy data record pointer (“fuzzy”, as used herein, means that the data record pointer need not be coincident with the actual data record address). A modulus for the data record pointer divided by N is computed. This modulus is used to select the target file. A data record address is computed for the target data record utilizing the data record pointer and modulus. In this manner a fuzzy data record pointer is utilized to determine both the target file from a set of N related files and the target data record to be accessed within the target file.

Abstract: The invention is an optimistic locking mechanism which allows Internet access to a database while maintaining data integrity in a stateless web environment. One embodiment of the invention incorporates a conventional IMS residing on a host computer and includes a generic transaction module which retrieves original data segments from the an IMS database in response to a search request from a web user. This embodiment of the invention further includes a server-side interface module for duplicating the original data segment into identical lines of data segments. One data segment may be updated by a web user whereas the other data segment remains constant and serves as a reference of the original state of the data segment. Both data segments are transmitted to a web user who may make changes to one data segment but not the other.

Abstract: A method and apparatus to synchronize recovery logs transmitted to a remote site for recovering related databases having different logical structuring. In one embodiment, the related databases are a hierarchial structured database such as IMS and a relational structured database such as DB2.