WO2016183641A1 - A system, method, computer program and data signal for remotely operating and executing a program on a mainframe - Google Patents

Abstract

The present invention provides, in one embodiment, a method of delivering at least one program instruction to a mainframe system. The method comprises the steps of providing to the mainframe system a program embedded in at least one instruction as a processable job, the program including a server module arranged to operate as a virtual server. Upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system.

Description

A SYSTEM, M ETHOD, COMPUTER PROGRAM AND DATA SIGNAL FOR REMOTELY OPERATING AND EXECUTING A PROGRAM ON A MAINFRAME

FIELD OF THE INVENTION

[0001] The present invention relates to a system, method, computer program and data signal remotely operating and executing a program on a mainframe. Embodiments of the invention find particular, but not exclusive, use in the provision of an executable program within a job control language (JCL) job. In one specific embodiment, the invention relates to the provision of a virtual server within a mainframe computing system, to allow one or more programs to be executed by the mainframe within the virtual server.

BACKGROUND OF THE INVENTION

[0002] Mainframe computers, despite assertions to the contrary, are enjoying a renaissance. The term 'mainframe' originally referred to the large cabinets that held the components of first generation computing systems. As computers became smaller and began to penetrate many market sectors and organisations, the term 'mainframe' came to refer to high-end, commercial computers used by large corporate and government organisations to process very large numbers of computing tasks ('transactions').

[0003] Mainframe computers are distinguished from other computing systems by engineering that results in very high reliability (e.g. through the use of redundant systems and high quality components), extensive input-output facilities to process a very high volume of transactions, high hardware utilisation rates through software (and hardware) processes that allow for virtualisation of hardware, and strong backward compatibility between successive generations of mainframe hardware and software. In other words, mainframe computers are built for reliability and dependability in critical applications where failure (either in hardware or software) could have serious financial or real world consequences. [0004] As such, mainframe computers are the computers used by large corporate and governmental organisations to process very large volumes of data in critical applications (such as financial transactions, military exercises, etc).

[0005] Over time, with the development of personal computers, widely distributed computing networks (such as the lnternet),newer and cheaper ways of achieving redundancy (e.g. via a network of low-cost computers), more sophisticated manufacturing techniques which resulted in more reliable hardware across all sectors of the computer market, and the exponential growth in computing power coupled with the simultaneous miniaturisation of electronic circuitry, resulted in smaller computers that were reliable enough to be used for many tasks traditionally reserved for mainframe computers. In turn, mainframe computers remained very specialist and niche computers, used by only a handful of institutions for very specific applications.

[0006] Many commentators were of the opinion that mainframe computers would slowly die out, as the traditional user base of mainframe computers, such as banks, insurance companies, government departments, etc., moved to different types of computing systems for many of their ancillary (and core) computing needs.

[0007] However, with the explosion of Internet commerce and the revived need for ultra- secure and ultra-reliable computers that are optimised for transaction processing, there has been a renewed interest and uptake in mainframe computing.

[0008] It is against this background that embodiments of the invention have been developed.

SUMMARY OF THE I NVENTION

[0009] In a first aspect of the invention, there is provided a method of delivering at least one program instruction to a mainframe system, comprising the steps of providing to the mainframe system a program embedded in at least one instruction as a processable job, the program including a server module arranged to operate as a virtual server, wherein, upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system. [0010] I n one embodiment, at least one further software module arranged to operate on the virtual server is provided within the program, wherein at least one of the further instructions which operate the mainframe computing system is received from the at least one further software module.

[0011] I n one embodiment, the processable job is a Job Control Language (JCL) job.

[0012] I n one embodiment, the processable job is generated by an app software application residing on a remote computing system.

[0013] I n one embodiment, the app software application packages the processable job and the program by receiving user input and processing the user input to generate the program.

[0014] I n one embodiment, the step of processing includes the creation of a Java application including the processable job and the program.

[0015] I n one embodiment, the creation of a Java application includes the automatic generation of Java code.

[0016] I n one embodiment, the step of providing the processable job to the mainframe includes the step of transferring the processable job file using the File Transfer Protocol (FTP).

[0017] I n one embodiment, the program is embedded in the processable job as a pointer to an external file.

[0018] I n one embodiment, the further instructions are provided in the REXX language.

[0019] I n a second aspect of the invention, there is provided a system for delivering at least one program instruction to a mainframe system, comprising a program embedded in at least one instruction as a processable job, the program including a server module arranged to operate as a virtual server, wherein, the program is deliverable to the mainframe in a manner such that, upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system.

[0020] In one embodiment, the system includes at least one further software module arranged to operate on the virtual server, wherein at least one of the further instructions which operate the mainframe computing system is received from the at least one further software module. [0021] In one embodiment, the processable job is a Job Control Language (JCL) job.

[0022] In one embodiment, the processable job is generated by an agent software application residing on a remote computing system.

[0023] In one embodiment, the agent software application packages the processable job and the program by receiving user input and processing the user input to generate the program.

[0024] In one embodiment, the step of processing includes the creation of a Java application including the processable job and the program.

[0025] In one embodiment, the creation of a Java application includes the automatic generation of Java code.

[0026] In one embodiment, the processable job file is transferred using the File Transfer Protocol (FTP).

[0027] In one embodiment, the program is embedded in the processable job as a pointer to an external file.

[0028] In a third aspect of the invention, there is provided a software application which includes at least one instruction, which, when executed by a computing system, carries out the method steps in accordance with the second embodiment of the invention.

[0029] In a fourth aspect of the invention, there is provided a data signal including at least one encoded instruction which, when executed by a computing system, carries out the method steps in accordance with the second embodiment of the invention.

BRIEF DESCRIPTION OF THE DRAWI NGS

[0030] The foregoing will be apparent from the following more particular description of example embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments of the present invention.

[0031] Fig. 1 illustrates an example system usable to operate an embodiment of the present invention. [0032] Fig. 2 illustrates an example embodiment of a system in accordance with the present invention.

[0033] Figs. 3 and 4 are flowcharts illustrating the steps of methods in accordance with an embodiment of the invention.

DETAILED DESCRI PTION OF EMBODIMENTS OF THE INVENTION Overview

[0034] A description of example embodiments of the invention follows. Like terms are used to denote functionally similar integers and features in the Figures.

[0035] Referring to Figure 1, there is shown an example mainframe computing system which is capable of remotely operating and executing an application in accordance with an embodiment of the present invention.

[0036] In Figure 1 there is shown a schematic diagram of a computing system, which in this embodiment is a mainframe computer 100 suitable for use with an embodiment of the present invention. The mainframe computer 100 may be used to execute applications and/or system services such as a system and method for remotely operating and executing an application in accordance with an embodiment of the present invention.

[0037] With reference to Figure 1, the mainframe computer 100 may comprise suitable components necessary to receive, store and execute appropriate computer instructions. The components may include one or more processors 102, read only memory (ROM) 104, random access memory (RAM) 106, input/output devices such as disc drives 108, direct input devices 110 (such as a 'dumb terminal') and one or more communications link(s) 114.

[0038] The mainframe computer 100 includes instructions that may be installed in ROM 104, RAM 106 or disc drives 112 and may be executed by the processor 102. There may be provided a plurality of communication links 114 which may variously connect to one or more computing devices 110 such as web servers, personal computers, laptops, wireless or handheld computing devices, or mobile communication devices such as a mobile (cell) telephone. At least one of a plurality of communications link 114 may be connected to an external computing network through a telecommunications network. [0039] The mainframe computer 100 includes a suitable operating system 118 which may also reside on a storage device or in the ROM of the server 100. The operating system is arranged to interact one or more computer programs to cause the mainframe computer to carry out the steps, functions and/or procedures in accordance with the embodiments of the invention described herein.

[0040] Broadly, the invention relates to a method of delivering at least one program instruction to a mainframe system. The method comprises the steps of providing to the mainframe system a program embedded in at least one command as a processable job, the program including a server module arranged to operate as a virtual server. Upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system.

[0041] Other aspects of the broad inventive concept relate to a corresponding method and data signal.

No-Install Technology - packaging and deploying applications to a mainframe

[0042] Referring now to Figure 2, there is shown a schematic diagram of a system 200 which includes a Mainspace™ Java Application 202 (i.e. app software application) which operates on a personal computer 204. The personal computer 204 is in communication (e.g. via a network or via a direct cable connection, not shown) to a mainframe computing system 206, the system 200 being a system in accordance with an embodiment of the present invention.

[0043] In the ensuing description, reference may be made to the 'Mainspace' trade mark, a trade mark of Mainframe Cloud Pty Ltd, an Australian limited company. The 'Mainspace' trade mark is used in the ensuing description to refer to one specific commercial embodiment of the invention and no 'gloss' should be taken from the use of the trade mark or the specific reference to features of the commercial embodiment to limit the broader invention defined and described herein. The commercial embodiment is described solely to assist the reader in better understanding one embodiment of the invention, and the description of the commercial embodiment should be taken at all times as being illustrative rather than restrictive.

[0044] Returning to Figure 2, the Mainspace Java App 202 includes appropriate code to operate a Graphical User Interface (GUI) 208, and certain aspects of the mainframe program logic 210. The Mainspace Java App 202, once deployed, interfaces with the mainframe computing system 206 to launch and operate a Mainspace Agent program 212, as shown in Figure 2. The process by which the Mainspace Java App and Mainspace Agent operate are described in more detail below.

[0045] It will be understood that the Mainspace Java App is the subject of the present application, and the Mainspace Agent is the subject of a co-pending application.

[0046] In the context of the embodiment described herein, the Mainspace Agent is the vehicle by which the mainframe program is deployed on the mainframe (i.e. the program the user wishes to deploy and execute on the mainframe computing system).

[0047] In the embodiment described, the mainframe program is written in the

REstructured extended eXecutor (REXX) language, which is an interpreted programming language written developed by IBM, a US corporation (see http://www.ibm.com/rexx/). The program is stored in a conventional personal computer file file in the REXX format. For the purpose of the ensuing description, reference will be made to a single Mainspace agent (i.e. the mainframe program). However, it will be understood that the user may have multiple mainframe programs.

[0048] Moreover, it will be understood that the embodiment described herein refers to the REXX programming language. However, in other embodiments, other types of programming languages and/or "code" may be passed via the Mainspace Agent.

[0049] More specifically, in another embodiment, the Mainspace Agent may be programmed in any suitable language and may take the form of executable code.

[0050] The Mainspace Agent is run on the mainframe via a Job Control language (JCL) job, which is a scripting language used on IBM mainframes (see, for example,

htl:p:// .red books.ibm.com/red books/pdfs/s^247436.pdf for an introduction to JCL).

[0051] That is, the Mainspace Agent, which is programmed in REXX, is 'packaged' into a JCL job. The JCL job is then submitted to the mainframe over the network (usually by using the File Transfer Protocol (FTP) and once submitted, the JCL job runs the Mainspace Agent REXX program on the mainframe within a virtual server which is opened up by the Mainspace agent program within the mainframe computer.

[0052] The JCL source used to carry out this process is also coded and stored in a conventional personal computer file in a conventional JCL format.

Packaging

[0053] Referring to Figure 3, the process of packaging will now be described in more detail with reference to flow chart 300. When packaging the Mainspace Java application a custom built batch process is utilised.

[0054] The batch process comprises the following steps. Firstly, at step 302 the REXX source is extracted. As described previously, in some instances the source may not be REXX code, but may be another code, or alternatively, may be executable code which is constructed in a manner that allows the executable code to be packaged into a JCL format, but being included in a specific section of the JCL format.

[0055] Secondly, at step 304 a Java class source file ("ZZAGENTREXX.java" Java program) is created within the Mainspace Java application project (to replace the existing file of the same name).

[0056] Thirdly, at step 306, Java source code is constructed (i.e. the code is generated automatically by the batch process) to assign the content of the REXX source to a Java object variable. Fourthly, at step 308, the Mainspace Java application is compiled, resulting in the Mainspace mainframe code residing within the Mainspace Java application as a Java object.

[0057] The same steps are taken for the JCL source (creates Java source file

ZZAGENTJCL.java). The "mainframe entity java objects" generated in this way are then ready to be used to launch the application on the mainframe, as described below.

Launch Time [0058] To launch a program on the mainframe, a user executes the Mainspace PC Java application, to have access to one or more Mainspace Agents.

[0059] The user may then, at their discretion, execute a "Start Mainspace Agent" action, which results in the process described generally at Figure 4 with reference to flow chart 400.

[0060] Firstly, at step 402, the JCL object described above is dynamically inserted with required user profile data (setup information preferences previously defined by the user via a setup dialog), programmatic information required to allow multiple Mainspace Agent submissions on the same mainframe and network information to allow the Mainspace Agent to communicate with the Mainspace Java application that submitted it.

[0061] Secondly, at step 404, the JCL object is inserted with the Mainspace Agent REXX program.

[0062] Thirdly, at step 406, the JCL is submitted to run on the mainframe from the Mainspace Java PC application using the technique described below.

Execution of Application

[0063] Firstly, at step 408, the JCL job is transferred to the mainframe. When transferring a file to the mainframe using FTP, the FTP SITE COMMAND "FI LETYPE=JES" can be used to flag with the mainframe that the uploaded file is to be executed as a JCL job. In this way the user submits a JCL job to run on the mainframe, remotely from their PC, without saving any files on the mainframe.

[0064] In the embodiment described herein, the Mainspace PC Java application includes an FTP Client program, which is used to seamlessly FTP transfer the Mainspace Agent JCL to the mainframe to start the Mainspace Agent. In other words, the user is not explicitly aware that FTP is used to transfer the file. Rather, the process occurs in the background without the user's explicit knowledge.

[0065] The standard practice for running programs from a JCL job is to code the JCL to point to an external file which contains the program to run.

[0066] It is also possible to run a program from JCL by embedding the whole program physically inside the JCL file (instream to JCL), instead of pointing to an external file. With the "mainframe entity java objects" design (building the JCL and embedded REXX dynamically within our Java application before launching to mainframe), and the FTP/JCL feature, this instream approach provides the ability to run a mainframe software solution on the mainframe without installing any software on the mainframe.

[0067] Referring now generally to Figures 5 to 13, there are shown various screenshots of an embodiment of the invention. The screenshots shown generally at Figures 5 to 13 are to an web-based "application" arranged to operate on a personal computer, but it will be understood that the broader inventive concept contemplates any type of application, such as a an applet, an app operating on a portable tablet or mobile (cell) telephone device, or any other type of computing system that may potentially interface with a mainframe computing system.

[0068] Referring to Figure 5, there is shown a login screen 500 presented to a user including a login button 502. Once the user clicks the login button, the user is taken to the screen shown in either Figure 6 or Figure 7.

[0069] If the user has not yet registered an account with the provider of the embodiment of the invention, they are taken to a "register" screen at Figure 6 and are required to enter identifying information at text boxes 602. Alternatively, if the user has registered an account, they are taken to a login page at Figure 7 and can login using their email and password at text boxes 702.

[0070] Once the user is logged in, the user is taken to screen 800 at Figure 8 and can click the "launch" button 802 to launch the application.

[0071] The user may then log into the mainframe by using the logins shown at either Figures 9 or 10 (input boxes 900 and 1000 respectively). This takes the user to an FTP box which allows the user to then submit a batch job (input boxes 902 and 1002 respectively).

[0072] The user is now logged in and can utilise the screens generally shown at Figures 11 to 15. At Figure 11, the user utilises screen 1100 to navigate the explore product, where the user can start the agent (as described earlier in the specification).

[0073] At Figure 12, at screen 1200, the user can perform various actions on existing files and new files, including editing, importing, saving, deleting and renaming files.

[0074] At Figure 13, at screen 1300, the user can open numerous files in multiple windows, to allow the user to operate across multiple files simultaneously. [0075] At Figure 14, at screen 1400, the user can switch to the command mode, which allows the user to review certain aspects of the mainframe, such as active users, status of jobs, input queue, and various other statistical and informational parameters.

[0076] At Figure 15, at screen 1500, the user can create new complex, multi-step commands for the mainframe to execute and can do so using a series of predetermined simple commands.

Advantages

[0077] In order to better understand the advantages that arise from embodiments of the invention, it is instructive to briefly describe prior art mainframe systems and the market forces that control software and hardware development in the mainframe computing system market. It will be understood that any reference to a prior art system is provided herein solely for the purpose of better contextualising embodiments of the present invention, and no 'gloss' should be taken from the description of a prior art system to limit the scope or nature of any feature of the embodiments, the embodiments as a whole, or the broader inventive concept described herein.

[0078] Mainframe computers, due to their high security, high reliability and ability to run critical applications in a dependable manner, are generally very constrained in the software applications that are installed and run, and moreover, any addition of software applications and/or upgrades to software applications are generally preceded by a long period of testing, before an application is installed on a 'live' mainframe. The rigorous testing and long installation process associated with mainframe software applications results in high costs and long lead times to deploy new applications or upgrade existing applications.

[0079] Moreover, the high cost and long lead times for development of new applications has meant that the market for mainframe software applications is, by nature, very small and specialised. The very high cost of mainframes, the relatively small user base, and the need to ensure extremely high reliability in the deployment and execution of mainframe software applications has meant that there is a high cost associated with application development, coupled with a low demand in the marketplace. These market forces, coupled with a very conservative user base of potential clients, have meant that there is little innovation in the field of mainframe software development ecosystem. However, from the existing user base, there is a strong need or desire for new and innovative products in the mainframe software development ecosystem, notwithstanding the overriding issues of reliability, security and long development and testing times.

[0080] Embodiments of the present invention ameliorate the need to rigorously test and install new mainframe software applications, as the 'no-install' technology which allows an application to be executed on a mainframe computing system without needing to install and test the application beforehand.

[0081] The 'no-install' technology provides a number of advantages. Firstly, by removing the need to install an application on a mainframe, appreciable time is saved installing and testing the application prior to deployment.

[0082] Moreover, a user of the mainframe is no longer limited to executing only the applications which are installed on the mainframe. The user can, in practice, run any mainframe application they have access to, whether it is installed on the mainframe or whether it is located on their personal computer or terminal, or on another accessible computing system (such as a remote server).

[0083] Importantly, the user keeps complete control over the application, as the application is run within a virtual server that is deployed by the receipt of the JCL job by the Mainspace agent, and concurrently, the mainframe computing system is not exposed to potential issues from untested applications, as the 'no-install' technology does not require any files to be installed on the mainframe.

[0084] The system, method, computer program and data signal in accordance with the embodiment described herein finds use in any situation where it is desirable to execute an application on a mainframe without wishing to expend time and resources testing the application for suitability. The no-install technology interfaces with the broader Mainspace virtual platform solution which are described and defined in other co-pending patent applications filed by Mainframe Cloud Pty Ltd. Together, the no-install technology and the other Mainframe Cloud Pty Ltd solutions address the need in the mainframe market to provide greater and lower cost access to mainframe computing solutions. Variations and Modifications

[0085] It will be understood that the embodiments and broader invention described herein refer to a mainframe software application, namely a software application arranged to operate on a mainframe computing system. However, the embodiments and broader invention may also find use in analogous situations, such as the operation of software on a server, a distributed computing network, a so-called 'supercomputer', or any other use analogous to the use of a mainframe for transactional or calculation computational purposes.

[0086] Moreover, it will be understood that aspects or features of the described and defined invention and embodiments thereof may be implemented in hardware (for example, as firmware, as opposed to software which is arranged to interface with hardware via an operating system) may provide particular advantages, such as the ability to better secure communication channels and/or the ability to perform transactions more quickly (which may be important in a busy environment). Such variations are encompassed by the broader inventive concept described herein.

[0087] Although not required, the embodiments described with reference to the figures can be implemented via an application programming interface (API), an application development kit (ADK) or as a series of libraries, for use by a developer, for the creation of software applications which are to be used on any one or more mainframe computing platforms or analogous devices, such as a server structure, including a 'data farm' or within a bespoke transaction processing system.

[0088] Generally, as program modules include routines, programs, objects, components and data files that perform or assist in the performance of particular functions, it will be understood that the functionality of the software applications described and defined herein may be distributed across a number of routines, programs, objects or components to achieve the same functionality as the embodiments and the broader invention claimed herein. Such variations and modifications are within the purview of those skilled in the art.

[0089] It will also be appreciated that the methods and systems of the present invention and/or embodiments are implemented by mainframe computing systems or partly implemented by mainframe computing systems then any appropriate mainframe computing system architecture may be utilised.

[0090] Where the terms "computer", "computing system" and "computing device" are used in the specification, these terms are intended to cover any appropriate arrangement of computer hardware for implementing the inventive concept and/or embodiments defined and described herein.

Claims

1. A method of delivering at least one program instruction to a mainframe system, comprising the steps of providing to the mainframe system a program embedded in at least one instruction as a processable job, the program including a server module arranged to operate as a virtual server, wherein, upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system.

2. The method in accordance with claim 1, wherein at least one further software module arranged to operate on the virtual server is provided within the program, wherein at least one of the further instructions which operate the mainframe computing system is received from the at least one further software module.

3. The method in accordance with claim 1 or 2, wherein the processable job is a Job Control Language (JCL) job.

4. The method in accordance with claim 1, 2 or 3, wherein the processable job is

generated by an agent software application residing on a remote computing system.

5. The method in accordance with claim 3, wherein the agent software application

packages the processable job and the program by receiving user input and processing the user input to generate the program.

6. The method in accordance with claim 4, wherein the step of processing includes the creation of a Java application including the processable job and the program.

7. The method in accordance with claim 5, wherein the creation of a Java application includes the automatic generation of Java code.

8. The method in accordance with any one of the preceding claims, wherein the step of providing the processable job to the mainframe includes the step of transferring the processable job file using the File Transfer Protocol (FTP).

9. The method in accordance with any one of the preceding claims, wherein the program is embedded in the processable job as a pointer to an external file.

10. The method in accordance with any one of the preceding claims, wherein the further instructions are provided in the REXX language.

11. A system for delivering at least one program instruction to a mainframe system, comprising a program embedded in at least one instruction as a processable job, the program including a server module arranged to operate as a virtual server, wherein, the program is deliverable to the mainframe in a manner such that, upon the processable job being executed on the mainframe, the virtual server is started and is capable of receiving further instructions to operate the mainframe computing system.

12. The system in accordance with claim 11, including at least one further software

module arranged to operate on the virtual server, wherein at least one of the further instructions which operate the mainframe computing system is received from the at least one further software module.

13. The system in accordance with claim 11 or 12, wherein the processable job is a Job Control Language (JCL) job.

14. The system in accordance with claim 11, 12 or 13, wherein the processable job is generated by an agent software application residing on a remote computing system.

15. The system in accordance with claim 14, wherein the agent software application packages the processable job and the program by receiving user input and processing the user input to generate the program.

16. The system in accordance with claim 15, wherein the step of processing includes the creation of a Java application including the processable job and the program.

17. The system in accordance with claim 16, wherein the creation of a Java application includes the automatic generation of Java code.

18. The system in accordance with any one of claims 11 to 17, wherein the step of providing the processable job to the mainframe includes the step of transferring the processable job file using the File Transfer Protocol (FTP).

19. The system in accordance with any one of claims 11 to 18, wherein the program is embedded in the processable job as a pointer to an external file.

20. The system in accordance with any one of claims 11 to 19, wherein the further

instructions are provided in the REXX language.

21. A software application which includes at least one instruction, which, when executed by a computing system, carries out the method steps in accordance with any one of claims 1 to 10.

22. A data signal including at least one encoded instruction which, when executed by a computing system, carries out the method steps in accordance with any one of claims 1 to 10.