Mainframe data stream proxy and method for caching communication between emulators and mainframes
First Claim
Patent Images
1. A computer system, comprising;
- at least one emulator;
at least one mainframe; and
a mainframe data stream proxy (MDSP) for caching communication of the at least one emulator directed to the at least one mainframe, wherein the MDSP comprises;
a runtime application server configured to receive at least one emulator action from the at least one emulator and to send at least one corresponding mainframe action to the at least one emulator;
wherein the runtime application server is further configured to retrieve the at least one corresponding mainframe action to be sent to the at least one emulator from a cache of the MDSP;
wherein the application server is further configured to store the at least one received emulator action in a synchronization path of the MDSP,wherein the application server is further configured to send the at least one emulator action stored in the synchronization path to the at least one mainframe to support synchronization of the at least one mainframe with the at least one emulator, andwherein the application server is further configured to send emulator actions stored in the synchronization path to the at least one mainframe until the at least one mainframe is put into a state expected by the at least one emulator.
1 Assignment
0 Petitions
Accused Products
Abstract
The present invention concerns a mainframe data stream proxy (MDSP) (1) for caching communication of at least one emulator (2) directed to at least one mainframe (3), wherein the MDSP (1) comprises:
- a. a runtime application server (10), adapted for receiving (101, 201) at least one emulator action from the at least one emulator (2) and for sending (105, 209) at least one corresponding mainframe action to the at least one emulator (2);
- b. wherein the runtime application server (10) is further adapted for retrieving (102, 103) the at least one corresponding mainframe action to be sent to the at least one emulator (2) from a cache (20) of the MDSP (1).
-
Citations
18 Claims
-
1. A computer system, comprising;
-
at least one emulator; at least one mainframe; and a mainframe data stream proxy (MDSP) for caching communication of the at least one emulator directed to the at least one mainframe, wherein the MDSP comprises; a runtime application server configured to receive at least one emulator action from the at least one emulator and to send at least one corresponding mainframe action to the at least one emulator; wherein the runtime application server is further configured to retrieve the at least one corresponding mainframe action to be sent to the at least one emulator from a cache of the MDSP; wherein the application server is further configured to store the at least one received emulator action in a synchronization path of the MDSP, wherein the application server is further configured to send the at least one emulator action stored in the synchronization path to the at least one mainframe to support synchronization of the at least one mainframe with the at least one emulator, and wherein the application server is further configured to send emulator actions stored in the synchronization path to the at least one mainframe until the at least one mainframe is put into a state expected by the at least one emulator. - View Dependent Claims (2, 3, 4, 5, 6, 7, 16, 17, 18)
-
-
8. A method for caching communication of at least one emulator directed to at least one mainframe, the method comprising:
-
receiving at least one emulator action from the at least one emulator at a mainframe data stream proxy (MDSP) and sending at least one corresponding mainframe action from the MDSP to the at least one emulator; retrieving the at least one corresponding mainframe action to be sent to the at least one emulator from a cache of the MDSP; storing the at least one received emulator action in a synchronization path of the MDSP; sending the at least one emulator action stored in the synchronization path to the at least one mainframe to support synchronization of the at least one mainframe with the at least one emulator; and sequentially sending emulator actions stored in the synchronization path to the at least one mainframe until the at least one mainframe is put into a state expected by the at least one emulator. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15)
-
Specification