Mainframe data stream proxy and method for caching communication between emulators and mainframes

• US 8,428,931 B2
• Filed: 01/27/2010
• Issued: 04/23/2013
• Est. Priority Date: 01/13/2010
• Status: Active Grant

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: Yaffe, Lior
• Primary Examiner(s): PATEL, SHAMBHAVI K
• Application Number:
  US12/656,369
• Publication Number:
  US 20110172986A1
• Time in Patent Office: 1,182 Days
• Field of Search: 703/17, 703/20, 703/21, 703/23, 703/26
• US Class Current: 703/26
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131

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).

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.

2. The system of claim 1, wherein the runtime application server is further configured to determine whether the cache already comprises the at least one mainframe action corresponding to the at least one received emulator action based on an identifier of a screen, at least one AID key, a focus location and/or data of at least one field extracted from the at least one received emulator action, wherein the at least one emulator action corresponds to a screen currently displayed by the at least one emulator.

3. The system of claim 1, wherein the application server is further configured to send the at least one received emulator action to the at least one mainframe, to receive the corresponding mainframe action from the at least one mainframe, and to store the at least one corresponding mainframe action in the cache.

4. The system of claim 1, wherein the runtime application server is further configured to optimize the synchronization path by removing at least one emulator action from the synchronization path that does not modify data and/or application state on the at least one mainframe.

5. The system of claim 1, wherein the runtime application server is further configured to optimize the synchronization path by replacing a sub-path of the synchronization path with another sub-path based on at least one predefined rule.

6. The system of claim 1, wherein the MDSP is located on a computer distinct from the at least one emulator and/or the at least one mainframe.

7. The system of claim 1, wherein the runtime application server is further configured to determine whether a received mainframe action should be stored in the cache based on an identification of the structure of a screen comprised in the received mainframe action.

16. The system of claim 1, wherein the synchronization path includes a log of emulator actions and corresponding mainframe actions received by the MDSP over time.

17. The system of claim 1, wherein each said emulator action represents an action to be performed on a mainframe screen currently displayed by a requesting emulator.

18. The system of claim 17, wherein each said mainframe action represents a new screen to be displayed on the requesting emulator.

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.

9. The method of claim 8, further comprising determining whether the cache already comprises the at least one mainframe action corresponding to the at least one received emulator action based on an identifier of a screen, at least one AID key, a focus location and/or data of at least one field extracted from the at least one received emulator action, wherein the at least one emulator action corresponds to a screen currently displayed by the at least one emulator.

10. The method of claim 8, further comprising sending the at least one received emulator action from the MDSP to the at least one mainframe, receiving the corresponding mainframe action from the at least one mainframe at the MDSP and storing the at least one corresponding mainframe action in the cache.

11. A non-transitory computer readable storage medium storing a computer program comprising instructions that, when executed, implement the method of claim 8.

12. The method of claim 8, further comprising optimizing the synchronization path by removing at least one emulator action from the synchronization path that does not modify data and/or application state on the at least one mainframe.

13. The method of claim 8, further comprising optimizing the synchronization path by replacing a sub-path of the synchronization path with another sub-path based on at least one predefined rule.

14. The method of claim 8, wherein the MDSP is located on a computer distinct from the at least one emulator and/or the at least one mainframe.

15. The method of claim 8, further comprising determining whether a received mainframe action should be stored in the cache based on an identification of the structure of a screen comprised in the received mainframe action.