A communication method and device between an open system of a commercial bank and a ZOS system

Abstract

The present invention provides a communication method and device between an open system and a ZOS system, wherein the communication method between the open system and the ZOS system comprises: receiving a task instruction sent by the open system; parsing the task instruction to generate a trigger instruction, a re-run instruction, and a query instruction; and sending the trigger instruction, the re-run instruction, and the query instruction to the DRDA service port of the ZOS system. The present invention effectively unifies the scheduling between the open system and the mainframe system, and can realize the mutual dependence between different systems of batch processing jobs without deploying multiple sets of different scheduling systems. On the other hand, it realizes the unified management of batch processing jobs, reduces the user's usage threshold, and improves the efficiency of daily management and control, as well as operation and maintenance.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a communication method and device between an open system and a ZOS system. Background Art

[0002] At present, in China, accounting transactions of large commercial banks are all run on IBM's commercial mainframes (operating system is ZOS), and data line processing is carried out on open systems (Linux, CentOS, etc.) or minicomputers (AIX, etc.) to meet the needs of different business scenarios. There is often a sequential dependency between these batch processing tasks, that is, there are certain operation sequencing requirements.

[0003] Since these operating systems are independent of each other, especially the mainframe (ZOS operating system), which is an all-in-one machine and is closed in itself, files cannot be shared with servers of open operating systems. Users cannot obtain batch tasks through the commonly used status file scanning method. If the scheduling system polls the transaction account database, it will increase the data load of the transaction account, and the data of different transaction accounts are stored in different databases, which increases the difficulty of scheduling.

[0004] For example, Control-M / Server is a professional ETL scheduling tool from BMC, which is widely used. In the banking field, it has many customers. The architecture of CTM products is as follows: Figure 1 As shown. The three-tier architecture realizes the separation of management, scheduling and job execution functions, and the modules are independent of each other. Control-M is divided into a ZOS operating system version and an open end operating system version. The two versions cannot communicate directly. If communication between the two is required, the current method is to transfer data files from the ZOS operating system to the open end through a transmission tool. The open end determines the execution status of batch tasks in the ZOS operating system by scanning data files. The interaction between the ZOS version of Control-m and the open operating system version is complex, and middleware (transmission tools) need to be introduced, which prolongs the process of batch tasks and increases the timeliness of job processing in disguise. Summary of the invention

[0005] The communication method and device between the open system and the ZOS system provided by the present invention effectively unify the scheduling between the open system and the mainframe system, and can realize the interdependence between different systems of batch processing jobs without deploying multiple sets of different scheduling systems. On the other hand, it realizes the unified management of batch processing jobs, lowers the user's usage threshold, and improves the efficiency of daily management, operation and maintenance.

[0006] In order to achieve the above object, the present invention provides a communication method between an open system on a server side and a ZOS system, comprising:

[0007] Receive task instructions sent by the open system;

[0008] Parsing the task instructions to generate trigger instructions, re-run instructions and query instructions;

[0009] Send the trigger instruction, re-run instruction and query instruction to the DRDA server of the ZOS system.

[0010] Preferably, parsing the task instruction to generate a trigger instruction, a rerun instruction and a query instruction includes:

[0011] Generate a task execution return code according to the task instruction;

[0012] Generate trigger instructions, re-run instructions and query instructions according to the task execution return code.

[0013] Preferably, the communication method between the open system and the ZOS system further includes:

[0014] Receiving the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction;

[0015] The execution result is sent to the open system.

[0016] Preferably, the DRDA server is used to verify, parse and store the trigger instructions, rerun instructions and query instructions.

[0017] The present invention also provides a communication device between an open system at a client and a ZOS system, the device comprising:

[0018] A task instruction receiving unit, used for receiving a task instruction sent by an open system;

[0019] A task instruction parsing unit, used for parsing the task instruction to generate a trigger instruction, a re-run instruction and a query instruction;

[0020] The instruction sending unit is used to send the trigger instruction, re-run instruction and query instruction to the DRDA server of the ZOS system.

[0021] Preferably, the task instruction parsing unit includes:

[0022] A return code generation module, used to generate a task execution return code according to the task instruction;

[0023] The instruction generation module is used to generate trigger instructions, re-run instructions and query instructions according to the task execution return code.

[0024] Preferably, the communication device between the open system and the ZOS system further includes:

[0025] An execution result receiving unit, used for receiving the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction;

[0026] The execution result sending unit is used to send the execution result to the open system.

[0027] Preferably, the DRDA server is used to verify, parse and store the trigger instructions, rerun instructions and query instructions.

[0028] In a third aspect, the present invention provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of a communication method between an open system and a ZOS system are implemented.

[0029] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a communication method between an open system and a ZOS system.

[0030] From the above description, it can be seen that the communication method and device between the open system and the ZOS system provided by the embodiment of the present invention first receives the task instruction sent by the open system; parses the task instruction to generate a trigger instruction, a re-run instruction and a query instruction; sends the trigger instruction, the re-run instruction and the query instruction to the DRDA service port of the ZOS system. The present invention can send the job scheduling instruction to the ZOS operating system on the open end operating system and drive the job running on the ZOS operating system. At the same time, it can also send the status query instruction to the ZOS operating system, query the execution status of the job in real time and send the task intervention instruction to intervene in the batch task on the ZOS operating system in real time. In summary, the present invention effectively unifies the scheduling between the open system and the mainframe system, and can realize the mutual dependence between different systems of the batch processing job without deploying multiple different scheduling systems, and realize the unified management of the batch processing job, reduce the user's usage threshold, and improve the efficiency of daily management and control, as well as operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0032] Figure 1 It is a structural schematic diagram of CTM in the prior art;

[0033] Figure 2 A first structural diagram of a communication system between an open system and a ZOS system according to an embodiment of the present application;

[0034] Figure 3 A second structural diagram of a communication system between an open system and a ZOS system according to an embodiment of the present application;

[0035] Figure 4 Schematic diagram of the communication method between the open system on the server side and the ZOS system provided in the embodiment of the present invention Figure 1 ;

[0036] Figure 5 is a flow chart of step 200 in an embodiment of the present invention;

[0037] Figure 6 Schematic diagram of the communication method between the open system on the server side and the ZOS system provided in the embodiment of the present invention Figure 2 ;

[0038] Figure 7 It is a structural diagram of the proxy task execution module in a specific application example of the present invention;

[0039] Figure 8 It is a flow chart of a communication method between an open system and a ZOS system in a specific application example of the present invention;

[0040] Fig. 9 It is a schematic diagram of the working principle of the system between the open system and the ZOS system in a specific application example of the present invention;

[0041] Fig.10 Schematic diagram of the structure of the communication device between the open system on the server side and the ZOS system in the embodiment of the present invention Figure 1 ;

[0042] Fig.11 A schematic diagram of the structure of a task instruction parsing unit in an embodiment of the present invention;

[0043] Fig.12 Schematic diagram of the structure of the communication device between the open system on the server side and the ZOS system in the embodiment of the present invention Figure 2 ;

[0044] Fig.13 FIG. 4 is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0046] This application provides a communication system between an open system and a ZOS system. Figure 2 The system may be a server A1, which may be connected to multiple task instruction receiving terminals B1 in communication, and the server A1 may be connected to multiple databases in communication, or Figure 3 As shown, these databases can also be set in the server A1. Among them, the task instruction receiving terminal B1 is used to receive the task instruction of the client. After receiving the request data, the server A1 processes the request data accordingly and sends it to the corresponding open system.

[0047] It is understandable that the client C1 may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a personal digital assistant (PDA), a vehicle-mounted device, a smart wearable device, etc. Among them, the smart wearable device may include smart glasses, a smart watch, a smart bracelet, etc.

[0048] In actual application, the part of communication between the open system and the ZOS system can be executed on the server A1 side as described above, that is, Figure 2 or Figure 3 The architecture shown in the figure can also be that all operations are completed in the client C1 device. The specific selection can be made according to the processing capability of the client device and the restrictions of the user's usage scenario. This application does not limit this. If all operations are completed in the client device, the client device can also include a processor for processing the communication results between the open system and the ZOS system.

[0049] The client C1 device mentioned above may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission with the server. The server may include a server on the communication side between the open system and the ZOS system, and other implementation scenarios may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the communication server between the open system and the ZOS system. The server may include a single computer device, or a server cluster consisting of multiple servers, or a server structure of a distributed device.

[0050] The server and the client device may communicate using any suitable network protocol, including network protocols that have not yet been developed on the date of filing this application. Network protocols may include, for example, TCP / IP, UDP / IP, HTTP, HTTPS, etc. Of course, network protocols may also include, for example, RPC (Remote Procedure Call Protocol) and REST (Representational State Transfer) protocols used on top of the above protocols.

[0051] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0052] The embodiment of the present invention provides a specific implementation method for a communication method between an open system on a server side and a ZOS system, see Figure 4 , the method specifically includes the following contents:

[0053] Step 100: Receive a task instruction sent by an open system.

[0054] As known from the background technology, the existing mainframe cannot receive any external instructions, including open systems, where the open systems include: Linux, CentOS and the like.

[0055] Step 200: Parse the task instruction to generate a trigger instruction, a rerun instruction and a query instruction.

[0056] Specifically, a task execution return code is generated according to the task instruction, and a trigger instruction, a rerun instruction and a query instruction are generated according to the task execution return code, wherein the query instruction can query the execution status of the job in real time.

[0057] Step 300: Send the trigger instruction, rerun instruction and query instruction to the DRDA server of the ZOS system.

[0058] The DRDA server is used to receive instruction information sent to the mainframe from the outside, and to verify, parse, and store the instruction information. DRDA clearly defines the rules for supporting distributed data access. RDBMS that complies with the DRDA standard supports complete data distribution, including multi-site updates.

[0059] From the above description, it can be seen that the communication method between the open system and the ZOS system provided by the embodiment of the present invention first receives the task instructions sent by the open system; parses the task instructions to generate trigger instructions, re-run instructions and query instructions; sends the trigger instructions, re-run instructions and query instructions to the DRDA service port of the ZOS system. The present invention can send the job scheduling instructions to the ZOS operating system on the open end operating system and drive the job running on the ZOS operating system. At the same time, it can also send status query instructions to the ZOS operating system, query the execution status of the job in real time and send task intervention instructions to intervene in the batch tasks on the ZOS operating system in real time. In summary, the present invention effectively unifies the scheduling between the open system and the mainframe system. Without deploying multiple different scheduling systems, the interdependence between different systems of batch jobs can be realized, and the unified management of batch jobs can be realized, which reduces the user's usage threshold and improves the efficiency of daily management and control, as well as operation and maintenance.

[0060] In one embodiment, see Figure 5 , step 200 further comprises:

[0061] Step 201: Generate a task execution return code according to the task instruction;

[0062] It is understandable that whether the current task is successfully executed can be determined based on the task execution return code.

[0063] Step 202: Generate a trigger instruction, a rerun instruction, and a query instruction according to the task execution return code.

[0064] Specifically, according to the number of job runs in the job flow instance information of the scheduling parameters, it is determined whether the current request is the first run or the job rerun, and the command sent to the DRDA interface is set according to different request information. Further, the current task is executed, and the task execution return code is returned according to the task execution result, and then it is determined whether the current task is successful according to the task execution return code. If the current task execution fails, a rerun instruction is generated.

[0065] In one embodiment, see Figure 6 , the communication method between the open system and the ZOS system also includes:

[0066] Step 400: receiving the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction;

[0067] Step 500: Send the execution result to the open system.

[0068] In step 400 and step 500, a status query instruction may be sent to the ZOS operating system to query the execution status of the job in real time and send a task intervention instruction to intervene in the batch processing task on the ZOS operating system in real time.

[0069] In one embodiment, the DRDA server is used to verify, parse and store the trigger instructions, rerun instructions and query instructions.

[0070] It can be understood that the DRDA server is used to receive the command information transmitted to the mainframe from the outside, and to verify, analyze and store the command information. The specific process is as follows:

[0071] 1) Structural verification: Verify whether the instruction structure is legal.

[0072] 2) Parse the following information in the instruction: job flow information, job information, requested operation, and time when the request instruction is issued.

[0073] 3) Verify the parsed result information to verify whether the instruction information is legal, whether the requested job information exists, whether the requested operation is reasonable, etc.

[0074] 4) After the verification is passed, the verification information is stored in the database, and the application on the main machine starts polling to process the job and return the information to the agent communication service module.

[0075] The communication method between the open system and the ZOS system provided in the embodiment of the present application combines the precise positioning information of the high-precision positioning device with the authentication information of the client device to accurately display the surrounding trusted devices in real time, and financial transactions can be realized by simply sliding the screen on the smart phone. This overcomes the shortcomings of the prior art that the transfer-type financial transactions have a complicated process, require manual account selection, and require manual input for accounts that have not been traded, and cannot break through the shortcomings of acquaintance transactions, and lead to inconvenience in the use of financial transactions, making it difficult to solve the problem efficiently.

[0076] To further illustrate the present solution, the present application provides a specific application example of a communication method between an open system and a ZOS system, and the specific application example specifically includes the following contents.

[0077] The mainstream scheduling products on the market currently have the following problems with cross-platform scheduling:

[0078] 1) CTM's scheduling products are divided into two versions: supporting the ZOS operating system and the open operating system, and the two versions cannot communicate directly with each other, which brings inconvenience to unified scheduling management at the enterprise level.

[0079] 2) With the development of banking business, the timeliness requirements for batch processing tasks are getting higher and higher. During the operation of batch processing tasks, it is necessary to be able to directly trigger the operation of subsequent jobs to reduce the intermediate links and improve the timeliness of the business.

[0080] Based on the above problems, the present application also provides a communication system between an open system and a ZOS system, see Figure 7 The system includes: a scheduling server, an execution agent component and a ZOS operating system, wherein the execution agent component is composed of an agent task execution module, an agent communication service module and a DRDA server. The functions of the agent task execution module are as follows: receiving ZOS batch tasks; generating ZOS scheduling instructions; determining the results of ZOS instruction execution. The agent communication service module is mainly composed of a scheduling instruction sending interface DRDAClient, and its main functions are as follows: responsible for sending scheduling instructions to the DRDA server on the ZOS operating system; receiving the result information returned by the DRDA server. The main functions of the DRDA server are as follows: responsible for receiving scheduling instructions sent by the agent communication service module; checking, storing and specifying the scheduling of ZOS batch jobs for scheduling instructions; returning the results of scheduling instruction execution.

[0081] Based on the communication system between the open system and the ZOS system, the communication method between the open system and the ZOS system provided in this specific application example includes the following steps, see Figure 8 as well as Fig. 9 :

[0082] S10: The ZOS batch task command execution receiver is responsible for receiving and parsing the commands of the mainframe processing tasks issued by the scheduling and dispatching component.

[0083] S20: The ZOS scheduling instruction generator generates a trigger instruction, a rerun instruction, and a query instruction respectively according to the parsing status of the command execution receiver and the scheduling instruction execution return code information parsed by the ZOS scheduling instruction execution status parser.

[0084] S30: The ZOS scheduling instruction execution state analyzer sends the instruction generated by the instruction generator to the agent communication service module, and captures the abnormal information that may be generated in the agent communication service module, and feeds it back to the instruction generator.

[0085] It should be noted that the agent communication service module is responsible for sending the ZOS scheduling instructions to the DRDA interface on the mainframe, performing preliminary analysis based on the return information of the DRDA interface, and then returning it to the agent task execution module for processing.

[0086] The specific application example of the present invention realizes the loose coupling between the open system and the ZOS operating system through the DRDA interface, and the batch processing commands to be executed on the mainframe operating system are parsed, verified, and registered in the distributed database system through the proxy task execution service on the scheduling platform, and then the mainframe operating system performs batch processing scheduling. Specifically:

[0087] 1. The agent task execution module communicates with the ZOS service module in a restful manner and handles exceptions based on the different return code information returned by the DRDA interface. The handling methods are as follows:

[0088] According to the job scheduling situation, it is determined whether the job is running for the first time or in a failed rerun state on ZOS, and then different request instructions are sent according to different states, such as sending job query, first run, failed rerun, etc. After each request instruction is sent, the execution status of the request instruction itself will be determined first, that is, the instruction itself is sent to the server and the information on whether it is successfully executed on the server. Only after confirming that the request is sent and executed successfully, the job status contained in the instruction is determined, and the job query instruction is sent at regular intervals to determine the current latest status of the job in DRDA until the success or failure information of the job is obtained.

[0089] 2. The agent task execution module supports high availability.

[0090] 3. The status consistency between the scheduling service and the batch jobs on the ZOS system can be automatically repaired. When the proxy execution service module is interrupted due to network or server failure, the latest status of the batch jobs on the ZOS system can be automatically obtained and returned to the scheduling service when the service is restored next time to ensure the consistency between the two.

[0091] Based on the same inventive concept, the embodiments of the present application also provide a communication device between an open system and a ZOS system, which can be used to implement the methods described in the above embodiments, such as the following embodiments. Since the principle of solving the problem by the communication device between an open system and a ZOS system is similar to the communication method between an open system and a ZOS system, the implementation of the communication device between an open system and a ZOS system can refer to the implementation of the communication method between an open system and a ZOS system, and the repeated parts will not be repeated. As used below, the terms "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0092] The embodiment of the present invention provides a specific implementation of a communication device between an open system and a ZOS system that can implement a communication method between an open system and a ZOS system, see Fig.10 The communication device between the open system and the ZOS system specifically includes the following contents:

[0093] The task instruction receiving unit 10 is used to receive the task instruction sent by the open system;

[0094] The task instruction parsing unit 20 is used to parse the task instruction to generate a trigger instruction, a re-run instruction and a query instruction;

[0095] The instruction sending unit 30 is used to send the trigger instruction, re-run instruction and query instruction to the DRDA server of the ZOS system.

[0096] Preferably, see Fig.11 , the task instruction parsing unit 20 comprises:

[0097] A return code generating module 201 is used to generate a task execution return code according to the task instruction;

[0098] The instruction generation module 202 is used to generate a trigger instruction, a re-run instruction and a query instruction according to the task execution return code.

[0099] Preferably, see Fig.12 , the communication device between the open system and the ZOS system also includes:

[0100] An execution result receiving unit 40, configured to receive the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction;

[0101] The execution result sending unit 50 is used to send the execution result to the open system.

[0102] Preferably, the DRDA server is used to verify, parse and store the trigger instructions, rerun instructions and query instructions.

[0103] From the above description, it can be known that the communication device between the open system and the ZOS system provided by the embodiment of the present invention first receives the task instruction sent by the open system; parses the task instruction to generate a trigger instruction, a re-run instruction and a query instruction; sends the trigger instruction, the re-run instruction and the query instruction to the DRDA service port of the ZOS system. The present invention can send the job scheduling instruction to the ZOS operating system on the open end operating system and drive the job running on the ZOS operating system. At the same time, it can also send the status query instruction to the ZOS operating system, query the execution status of the job in real time and send the task intervention instruction to intervene in the batch task on the ZOS operating system in real time. In summary, the present invention effectively unifies the scheduling between the open system and the mainframe system. Without deploying multiple different scheduling systems, the interdependence between different systems of the batch processing job can be realized, and the unified management of the batch processing job can be realized, which reduces the user's usage threshold and improves the efficiency of daily management and control, as well as operation and maintenance.

[0104] The embodiment of the present application also provides a specific implementation of an electronic device capable of implementing all steps in the communication method between the open system and the ZOS system in the above embodiment, see Fig.13 , electronic equipment specifically includes the following:

[0105] Processor (processor) 1201, memory (memory) 1202, communication interface (CommunicationsInterface) 1203 and bus 1204;

[0106] The processor 1201 , the memory 1202 , and the communication interface 1203 communicate with each other via the bus 1204 ; the communication interface 1203 is used to implement information transmission between server-side devices, user-side devices, and other related devices.

[0107] The processor 1201 is used to call the computer program in the memory 1202. When the processor executes the computer program, all steps in the communication method between the open system and the ZOS system in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0108] Step 100: receiving a task instruction sent by an open system;

[0109] Step 200: parsing the task instruction to generate a trigger instruction, a rerun instruction and a query instruction;

[0110] Step 300: Send the trigger instruction, rerun instruction and query instruction to the DRDA service port of the ZOS system.

[0111] The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps of the communication method between the open system and the ZOS system in the above embodiments. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps of the communication method between the open system and the ZOS system in the above embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0112] Step 100: receiving a task instruction sent by an open system;

[0113] Step 200: parsing the task instruction to generate a trigger instruction, a rerun instruction and a query instruction;

[0114] Step 300: Send the trigger instruction, rerun instruction and query instruction to the DRDA service port of the ZOS system.

[0115] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0116] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0117] Although the present application provides method operation steps such as embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel (for example, in a parallel processor or multi-threaded processing environment).

[0118] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0119] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0120] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0121] The present invention uses specific embodiments to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A communication method between an open system of a commercial bank and a ZOS system, characterized in that: include: Receive task instructions sent by the open system; Parsing the task instructions to generate trigger instructions, re-run instructions and query instructions; Send the trigger command, re-run command and query command to the DRDA server of the ZOS system; the DRDA server is used to receive command information transmitted to the ZOS system from the outside, and verify, parse and store the command information; DRDA clearly stipulates the rules for supporting distributed data access; RDBMS that complies with the DRDA standard supports complete data distribution, including multi-site updates; The step of parsing the task instruction to generate a trigger instruction, a rerun instruction and a query instruction includes: Generate a task execution return code according to the task instruction; Generate trigger instructions, re-run instructions and query instructions according to the task execution return code, specifically: according to the number of job runs of the job flow instance information of the scheduling parameter, determine whether the current request is the first run or the job re-run, and set the command sent to the DRDA interface according to different request information; further, execute the current task, and return the task execution return code according to the task execution result, and then determine whether the current task is successful according to the task execution return code; if the current task execution fails, generate a re-run instruction; The DRDA server is used to verify, parse and store the trigger instruction, re-run instruction and query instruction. The specific process is as follows: 1) Structural verification: verify whether the instruction structure is legal; 2) parse the following information in the instruction: job flow information, job information, requested operation, and time when the request instruction was issued; 3) Verify the parsed result information to verify whether the instruction information is legal, whether the requested job information exists, and whether the requested operation is reasonable; 4) After the verification is passed, the verification information is stored in the database, and the application on the ZOS system starts polling to process the job and return the information to the agent communication service module.

2. The communication method between an open system and a ZOS system according to claim 1, characterized in that: Also includes: Receiving the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction; The execution result is sent to the open system.

3. A communication device between an open system and a ZOS system, characterized in that: include: A task instruction receiving unit, used for receiving a task instruction sent by an open system; A task instruction parsing unit, used for parsing the task instruction to generate a trigger instruction, a re-run instruction and a query instruction; The instruction sending unit is used to send the trigger instruction, re-run instruction and query instruction to the DRDA server of the ZOS system; the DRDA server is used to receive instruction information transmitted to the ZOS system from the outside, and to verify, parse and store the instruction information; the rules clearly defined by DRDA support distributed data access; the RDBMS that complies with the DRDA standard supports complete data distribution, including multi-site updates; The task instruction parsing unit comprises: A return code generation module, used to generate a task execution return code according to the task instruction; An instruction generation module, used to generate a trigger instruction, a re-run instruction and a query instruction according to the task execution return code; The instruction generation module is specifically used to determine whether the current request is the first run or the job rerun according to the number of job runs of the job flow instance information of the scheduling parameter, and to set the command sent to the DRDA interface according to different request information; further, execute the current task, and return the task execution return code according to the task execution result, and then determine whether the current task is successful according to the task execution return code; if the current task execution fails, a rerun instruction is generated; The DRDA server is used to verify, parse and store the trigger instruction, re-run instruction and query instruction. The specific process is as follows: 1) Structural verification: verify whether the instruction structure is legal; 2) parse the following information in the instruction: job flow information, job information, requested operation, and time when the request instruction was issued; 3) Verify the parsed result information to verify whether the instruction information is legal, whether the requested job information exists, and whether the requested operation is reasonable; 4) After the verification is passed, the verification information is stored in the database, and the application on the ZOS system starts polling to process the job and return the information to the agent communication service module.

4. The communication device between the open system and the ZOS system according to claim 3, characterized in that: Also includes: An execution result receiving unit, used for receiving the execution result of the ZOS system in response to the trigger instruction, the re-run instruction and the query instruction; The execution result sending unit is used to send the execution result to the open system.

5. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the communication method between the open system and the ZOS system according to any one of claims 1 to 2 are implemented.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the communication method between the open system and the ZOS system as claimed in any one of claims 1 to 2 are implemented.

Images