International Business Machines Corporation

Jeffrey Douglas

Timothy W Wilson

Ian Royston Alexander Deeley

Methods, systems and computer program products for replaying arguments of an application in real-time, with re-arrangement is provided. Tags indicating an original execution environment, mapping tables corresponding to the execution environment, a plurality of callback modules, and recorded data are loaded into system memory. Execution of an application begins, and in response to intercepting a call to the execution environment, a transaction is identified. The parameters to the call are populated with data from a matching record in the recorded data, and indicating the matching record is used.

Replaying interactions with transactional and database environments with re-arrangement

Methods, systems and computer program products for bypassing execution of a module in real-time is provided. Each listed target module is located and loaded into system memory. A link is established between each target module and the stubbing framework, which begins execution of an application that includes the plurality of target modules. In response to one of the plurality of target modules being called by the application, control is passed to the stubbing framework, which includes the passing to the stubbing framework original registers from the application and a register containing an entry point of the stubbing framework. Each listed target module is bypassed. A utility module can intercept the call to the target module and provide arguments and logic to simulate the execution of the target. The results are recorded.

Bypassing execution of a module in real-time

Methods, systems and computer program products for determining a caller of a module in real-time is provided. Each listed target module is located and loaded into system memory. A link is established between each target module and the testing framework, which begins execution of an application that includes the plurality of target modules. In response to one of the plurality of target modules being called by the application, control is passed to the testing framework, which includes the passing to the testing framework original registers from the application and a register containing an entry point of the testing framework. The chain of load modules is inspected by following the linkage data provided in the registers, and the data is recorded. Control is returned from the testing framework to the target module.

Determining caller of a module in real-time

Methods, systems and computer program products for replaying arguments of a module in real-time is provided. Input includes indicator of the original execution environment, a location of load libraries having a plurality of callback modules, and a location of previously recorded data. A mapping table that corresponds to the execution environment is loaded into system memory. Batch execution of an application starts. Environmental calls to the application are intercepted. The transaction id and arguments are identified and previously recorded data that corresponds to the transaction id is loaded into system memory. The arguments to the call are populated with data from the corresponding record in the recorded data. Based on there being a corresponding callback module for the transaction, invoking the callback module and augmenting or replacing the arguments to the call with data in the callback module.

Intercepting and replaying interactions with transactional and database environments

Methods, systems and computer program products for intercepting and recording calls of a module in real-time is provided. Each listed target module is loaded into system memory. A link is established between each target module and the recording framework, which begins execution of an application that includes the plurality of target modules. In response to one of the plurality of target modules being called by the application, control is passed to the recording framework, which includes passing to the recording framework original registers from the application and a register containing an entry point of the recording framework. Recording framework records arguments passed to the target module. Tags identifying the execution environment, transaction name, transaction id, calling program name, and whether the call is for input or output are recorded. When the target module completes, control passes back to the recording framework, which records the output parameters from the target module.

Growing community of inventors

Raleigh, NC, United States of America

Jeffrey Douglas