Mainframe performance testing method and device

Abstract

The embodiment of the present application provides a mainframe performance testing method and device, which can be used in the field of big data technology. The method includes: directly connecting the pressure initiation tool outside the target mainframe to the target mainframe to initiate a performance test for the target mainframe; automatically generating a corresponding target transaction message according to the target transaction type corresponding to the performance test request for the target mainframe currently received, the transaction data and transaction script corresponding to the preset target transaction type; sending the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data. The present application can effectively improve the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, thereby effectively realizing high-concurrency performance testing of bank transaction systems using mainframes.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, in particular to the field of big data technology, and specifically to a mainframe performance testing method and device. Background Art

[0002] Mainframes have unparalleled advantages over other types of servers in terms of availability, scalability, security, partitioning, and load capacity. Mainframes have superb capabilities in handling complex multi-tasks, and their downtime is much lower than other types of servers. Mainframes have strong I / O capabilities and are good at accessing very large databases. They adopt dynamic partition management and flexibly allocate system resources according to the size of different application loads. The design strategy of preventing intrusion from the bottom layer improves the security of mainframes. The above features are extremely important for applications in industries such as finance, telecommunications, transportation, energy, and government that have extremely demanding requirements for system processing capabilities and security and stability.

[0003] However, the mainframe is not just a hardware concept, it is an organic whole of hardware and proprietary software, an inseparable closed system. The mainframe also uses special software tailored for it. This closed system brings high reliability and security to the mainframe system, but also makes it difficult for general computer practitioners to enter this field. Testing the performance of the mainframe is an extremely cumbersome process.

[0004] At present, the testing of mainframes is mainly carried out by deploying non-mainframe applications of the same amount as production, and manually simulating actual business behaviors to conduct testing. Through external applications, transactions are finally transmitted to the business processing logic of the mainframe. In the actual testing process, due to the existing mainframe performance testing methods requiring many supporting external applications, cumbersome environment construction, long training time for testers, and inability to complete performance testing with high concurrent loads, the existing performance testing methods for mainframes have problems such as low efficiency, high labor costs, and poor test reliability. Summary of the invention

[0005] In response to the problems in the prior art, the present application provides a mainframe performance testing method and device, which can effectively improve the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, thereby effectively realizing high-concurrency performance testing of bank transaction systems using mainframes.

[0006] In order to solve the above technical problems, this application provides the following technical solutions:

[0007] In a first aspect, the present application provides a mainframe performance testing method, comprising:

[0008] directly connecting a stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test on the target mainframe;

[0009] Automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request for the target mainframe currently received, the preset transaction data and transaction script corresponding to the target transaction type;

[0010] The target transaction message is sent to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0011] Furthermore, before directly connecting the stress initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, the method further includes:

[0012] Obtain preset transaction message description files and transaction log files;

[0013] Obtaining a corresponding target format from the transaction message description file, and reading an uploaded value from the transaction log file;

[0014] Generate a corresponding transaction script file based on the target format of the uploaded value;

[0015] Based on the preset performance test requirement data, extracting test data from the database corresponding to the target mainframe;

[0016] A test data file for performing a performance test on the target mainframe is generated according to the transaction script file and the test data.

[0017] Further, the step of directly connecting the stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test on the target mainframe includes:

[0018] receiving interactive commands from a stress initiation tool external to the target mainframe;

[0019] Determine the type of the corresponding pressure initiating tool based on the content in the interactive command;

[0020] A corresponding control command is generated according to the type of the pressure initiation tool and a preset mapping rule, so as to directly connect the pressure initiation tool with the target mainframe based on the control command.

[0021] Furthermore, the automatically generating a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset transaction data and transaction script corresponding to the target transaction type, includes:

[0022] receiving a performance test request for the target mainframe including a target transaction type;

[0023] Obtaining a corresponding target transaction type from the performance test request;

[0024] Read the transaction script file to obtain a transaction script corresponding to the target transaction type;

[0025] and, reading the test data file to obtain transaction data corresponding to the target transaction type;

[0026] A corresponding target transaction message is generated according to the transaction script and the transaction data.

[0027] Further, the sending of the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data includes:

[0028] Sending the target transaction message to the target mainframe, and enabling the target mainframe to perform a performance test corresponding to the target transaction message based on a preset stress testing tool and generate corresponding test result data;

[0029] Receive test result data of a target transaction type corresponding to the target mainframe.

[0030] Furthermore, it also includes:

[0031] When or after obtaining the test result data corresponding to each target transaction type corresponding to the current transaction test, performing data parsing on the test result data corresponding to each target transaction type based on the transaction message description file to obtain transaction parsing data corresponding to each target transaction type;

[0032] Generate a performance test report corresponding to the target mainframe according to the transaction analysis data corresponding to each of the target transaction types;

[0033] Output the performance test report.

[0034] Furthermore, it also includes:

[0035] Acquire corresponding performance test track data according to the performance test report;

[0036] The performance test track data and the preset asset management indicators are sent to the corresponding client device based on a preset interface, so that the user can determine whether to perform corresponding asset information operations based on the performance test track data and the preset asset management indicators read from the client device.

[0037] In a second aspect, the present application provides a mainframe performance testing device, comprising:

[0038] A tool connection module, used for directly connecting a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test for the target mainframe;

[0039] A message generation module, used for automatically generating a corresponding target transaction message according to a target transaction type corresponding to a performance test request currently received for the target mainframe, and preset transaction data and transaction script corresponding to the target transaction type;

[0040] The performance testing module is used to send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0041] In a third aspect, the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the mainframe performance testing method is implemented when the processor executes the program.

[0042] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the mainframe performance testing method when executed by a processor.

[0043] It can be seen from the above technical scheme that the present application provides a mainframe performance testing method and device, the method comprising: directly connecting a stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test for the target mainframe; automatically generating a corresponding target transaction message according to a target transaction type corresponding to a performance test request currently received for the target mainframe, and transaction data and transaction script corresponding to the preset target transaction type; sending the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data. By directly connecting a stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test for the target mainframe, it is possible to call a core transaction processing module to complete the initiation of a mainframe transaction, thereby eliminating the need to build an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and effectively reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can be quickly expanded horizontally. It can support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system; it can automatically generate the corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset transaction data and transaction script corresponding to the target transaction type, and send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message. It can compile performance test data using the existing data in the mainframe database, greatly improve the test credibility, greatly reduce the learning cost and operation cost of testers, and thus effectively improve the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, and can effectively reduce the manpower, time, hardware installation and maintenance costs used for testing, etc., and thus can effectively realize high-concurrency performance testing of bank transaction systems using mainframes, and improve the user experience of testers and other operation and maintenance personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application 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 application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] Figure 1 It is a schematic diagram of the relationship between the mainframe performance testing device in the embodiment of the present application and the target mainframe, database and client device respectively.

[0046] Figure 2 This is a first flow chart of the mainframe performance testing method in the embodiment of the present application.

[0047] Figure 3 It is a second flow chart of the mainframe performance testing method in the embodiment of the present application.

[0048] Figure 4 It is a third flow chart of the mainframe performance testing method in the embodiment of the present application.

[0049] Figure 5 This is a fourth flow chart of the mainframe performance testing method in the embodiment of the present application.

[0050] Figure 6 This is the fifth flow chart of the mainframe performance testing method in the embodiment of the present application.

[0051] Figure 7 This is the sixth flow chart of the mainframe performance testing method in the embodiment of the present application.

[0052] Figure 8 This is the seventh flow chart of the mainframe performance testing method in the embodiment of the present application.

[0053] Fig. 9 It is a structural diagram of a mainframe performance testing device in an embodiment of the present application.

[0054] Fig.10 It is a structural diagram of a mainframe performance test system provided in the application example of this application.

[0055] Fig.11 It is a schematic diagram of the structure of an electronic device in an embodiment of the present application.

[0056] Fig.12 It is a schematic diagram of an example processing flow of a mainframe transaction core processing module 2 provided in the application example of the present application.

[0057] Fig.13 It is a schematic diagram of an example processing flow of the transaction process control module 3 provided in the application example of this application. DETAILED DESCRIPTION

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

[0059] It should be noted that the mainframe performance testing method and device disclosed in the present application can be used in the field of big data technology, and can also be used in any field other than the field of big data technology. The application field of the mainframe performance testing method and device disclosed in the present application is not limited.

[0060] The existing performance testing methods for mainframes have the following problems:

[0061] 1. There are many supporting external applications, and the environment construction is cumbersome. Although mainframes have incomparable advantages in terms of reliability and performance, due to their high prices, they mainly carry the company's core systems, and supporting systems are still deployed on open platform systems. In order to test the core system of the mainframe, a complete supporting development platform environment must be built, which involves the installation and maintenance of a large number of servers, and the hardware cost and maintenance cost are very high.

[0062] 2. The training time for testers is long and the human resource cost is high. Since the core system runs on the mainframe, which is a complete black box for ordinary testers, testers cannot effectively match external operations with the business logic of the core system on the mainframe, and the learning cost is very high. At the same time, due to the complexity of the system, testers cannot cover everything, so a large number of testers are needed to complete the testing work of different parts respectively, which has huge human and time costs.

[0063] 3. Manual testing methods cannot complete performance testing of high-concurrency loads. Under the existing testing system, mainframe testing is mainly done manually, but the use scenarios of mainframes usually require supporting high-concurrency loads. Manual testing methods are obviously impossible to complete high-concurrency performance testing, and new testing methods need to be studied to complete high-concurrency testing.

[0064] Based on this, the existing mainframe performance testing methods require many supporting external applications, cumbersome environment construction, long training time for testers, and inability to complete high concurrent load performance testing. The existing performance testing methods for mainframes have problems such as low efficiency, high labor costs and poor test reliability. The embodiment of the present application provides a mainframe performance testing method, which directly connects the pressure initiation tool outside the target mainframe to the target mainframe to initiate a performance test for the target mainframe, and can call the core transaction processing module to complete the initiation of mainframe transactions, eliminating the need to build an external supporting application environment, and can effectively avoid the installation and maintenance of a large number of servers, and can effectively reduce hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can quickly expand horizontally, which can support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problem of environment construction under the existing testing system. The problems of cumbersome and numerous supporting systems are solved; by automatically generating the corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset transaction data and transaction script corresponding to the target transaction type, and sending the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message, the performance test data can be compiled using the existing data in the mainframe database, the test credibility is improved to a greater extent, and the learning cost and operation cost of the testers are greatly reduced, thereby effectively improving the reliability and convenience of the mainframe performance test process, and effectively improving the efficiency, automation and intelligence of the mainframe performance test process, and effectively reducing the manpower, time, hardware installation and maintenance costs used for testing, etc., thereby effectively realizing high-concurrency performance testing of bank transaction systems using mainframes, and improving the user experience of testers and other operation and maintenance personnel.

[0065] In one or more embodiments of the present application, a mainframe or mainframe uses a dedicated processor instruction set, operating system, and application software, and refers to a series of IBM computers starting with System / 360, or compatible systems manufactured by other manufacturers (such as Amdahl, Hitachi Data Systems (HDS)). A mainframe uses a dedicated instruction system and operating system, and a supercomputer uses a general-purpose processor and a UNIX or UNIX-like operating system (such as Linux). Mainframes are good at non-numerical computing (data processing); mainframes are mainly used in commercial fields, such as banking and telecommunications. Mainframes use a large number of redundancy technologies to ensure their security and stability, so there are usually two sets of internal structures.

[0066] Based on the above content, the present application also provides a mainframe performance testing device for implementing the mainframe performance testing method provided in one or more embodiments of the present application. The mainframe performance testing device can be a server. Figure 1 The mainframe performance testing device can communicate and connect with the target mainframe to be performance tested, the database corresponding to the target mainframe, and the client devices held by each user by itself or through a third-party server, wherein the mainframe performance testing device can receive the interactive command of the stress initiation tool and the performance test request for the target mainframe sent by the client device, and directly connect the stress initiation tool outside the target mainframe with the target mainframe according to the interactive command of the stress initiation tool to initiate a performance test for the target mainframe; according to the target transaction type corresponding to the performance test request for the target mainframe currently received, the preset transaction data and transaction script corresponding to the target transaction type, automatically generate the corresponding target transaction message, send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates the corresponding test result data, and the mainframe performance testing device can also send the test result data to the user's client device, etc.

[0067] In another practical application scenario, the part of the mainframe performance test performed by the aforementioned mainframe performance test device can be executed in the server as described above, or all operations can be completed in the user terminal device. The specific selection can be made based on the processing capacity of the user terminal device and the limitations of the user's usage scenario. This application does not limit this. If all operations are completed in the user terminal device, the user terminal device can also include a processor for specific processing of the mainframe performance test.

[0068] It is understandable that the mobile terminal may include any mobile device capable of loading applications, such as a smart phone, a tablet electronic device, a network set-top box, a portable 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, smart watches, smart bracelets, etc.

[0069] The above-mentioned mobile terminal 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 task scheduling center side, 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 task scheduling center server. The server may include a single computer device, or a server cluster consisting of multiple servers, or a server structure of a distributed device.

[0070] The server and the mobile terminal may communicate with each other using any suitable network protocol, including network protocols that have not yet been developed on the date of filing this application. The network protocols may include, for example, TCP / IP, UDP / IP, HTTP, HTTPS, etc. Of course, the 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.

[0071] The details are described in detail through the following embodiments and application examples.

[0072] In order to solve the problems that the existing mainframe performance testing methods require many supporting external applications, cumbersome environment construction, long training time for testers, and inability to complete high concurrent load performance testing, the existing performance testing methods for mainframes have low efficiency, high labor costs, and poor test reliability. This application provides an embodiment of a mainframe performance testing method, see Figure 2 The mainframe performance testing method executed by the mainframe performance testing device specifically includes the following contents:

[0073] Step 100: directly connect a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test on the target mainframe.

[0074] In step 100, a preset interface for mainframe performance testing may be encapsulated to facilitate calling through a common stress initiation tool.

[0075] Step 200: automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, and the preset transaction data and transaction script corresponding to the target transaction type.

[0076] In step 200, a transaction message description file and a transaction log file may be prepared in advance; a transaction script file may be generated based on the transaction message description file and the transaction log file, and test data may be extracted from a mainframe database according to test requirements to organize and generate a test data file. Then, transaction data corresponding to the target transaction type may be obtained from the transaction script file, and a transaction script corresponding to the target transaction type may be obtained from the test data file.

[0077] Step 300: Send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0078] In step 300, the sequence of the preceding and following items and the loop logic of the control transaction can also be obtained by reading the preceding and following item control files corresponding to the current control file according to the pre-defined preceding and following item control file logic, thereby ensuring the correct execution of the current target transaction test.

[0079] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application can realize the initiation of mainframe transactions by calling the core transaction processing module, by directly connecting the stress initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, eliminating the need to build an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and effectively reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can be rapidly expanded horizontally to support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system; by The transaction data and transaction script corresponding to the target transaction type automatically generate the corresponding target transaction message, and the target transaction message is sent to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message. The performance test data can be compiled using the existing data in the mainframe database, thereby improving the credibility of the test to a greater extent, greatly reducing the learning cost and operation cost of the tester, and thus effectively improving the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, and can effectively reduce the manpower, time, hardware installation and maintenance costs used for testing, etc., and thus can effectively realize high-concurrency performance testing of bank transaction systems using mainframes, and improve the user experience of testers and other operation and maintenance personnel.

[0080] In order to compile performance test data using the existing data in the mainframe database and improve the test credibility to a greater extent, an embodiment of the mainframe performance test method provided in this application is provided. Figure 3 The mainframe performance testing method further specifically includes the following contents before step 100:

[0081] Step 010: Obtain the preset transaction message description file and transaction log file.

[0082] Step 020: Obtain the corresponding target format from the transaction message description file, and read the uploaded value from the transaction log file.

[0083] Step 030: Generate a corresponding transaction script file according to the target format based on the uploaded value.

[0084] Step 040: Based on the preset performance test requirement data, extract test data from the database corresponding to the target mainframe.

[0085] Step 050: Generate a test data file for performance testing of the target mainframe based on the transaction script file and the test data.

[0086] Specifically, according to the established message interaction logic, read the transaction message description file, and parse the specific file content into memory, mainly including message structure, message field, field type, field length and number of cycles. Obtain the transaction log file from the external access channel, read the transaction log file, and parse the sent values ​​of the message fields in the log according to the message description file. According to the sent values ​​parsed from the transaction log, generate the final transaction script file for use by this system in accordance with the format specified in the message description file. Connect to the mainframe database BD2 through jcc. According to the data conditions to be extracted, connect to the database through the mainframe database connection module, extract the data that meets the conditions, and generate the data file required for the test according to the parameter information in the generated transaction script file.

[0087] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application generates a transaction script file in a specific format based on the transaction message description file and the transaction log file, connects to the mainframe database, extracts data and completes the organization, and can use the existing data in the mainframe database to compile performance test data, thereby improving the credibility of the test to a greater extent, greatly reducing the learning cost and operating cost of the testers, and further improving the reliability and convenience of the mainframe performance testing process, and further improving the efficiency, automation and intelligence of the mainframe performance testing process.

[0088] In order to effectively avoid the installation and maintenance of a large number of servers and to further reduce hardware costs and maintenance costs, an embodiment of the mainframe performance testing method provided in this application is described in detail. Figure 4 , step 100 of the mainframe performance testing method specifically includes the following contents:

[0089] Step 110: Receive an interactive command from a pressure initiation tool outside the target mainframe.

[0090] Step 120: Determine the type of the corresponding pressure initiating tool based on the content in the interactive command.

[0091] Step 130: Generate a corresponding control command according to the type of the pressure initiation tool and a preset mapping rule, so as to directly connect the pressure initiation tool with the target mainframe based on the control command.

[0092] Specifically, it receives the interaction command of the external pressure initiating tool, determines the type of the external pressure initiating tool, generates the control command of the mainframe performance testing system according to the corresponding mapping rule, and controls the mainframe performance testing system to complete the corresponding instruction operation according to the control command.

[0093] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application generates a corresponding control command according to the type of the stress initiation tool and the preset mapping rules, so as to directly connect the stress initiation tool with the target mainframe based on the control command, thereby realizing the initiation of mainframe transactions by calling the core transaction processing module, eliminating the need to set up an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and further reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools and quickly expand horizontally, and can support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system.

[0094] In order to further utilize the existing data in the mainframe database to compile performance test data, an embodiment of the mainframe performance test method provided in this application is provided. Figure 5 Step 200 of the mainframe performance testing method specifically includes the following contents:

[0095] Step 210: Receive a performance test request for the target mainframe including a target transaction type.

[0096] Step 220: Obtain the corresponding target transaction type from the performance test request.

[0097] Step 230: Read the transaction script file to obtain a transaction script corresponding to the target transaction type.

[0098] Step 240: Read the test data file to obtain transaction data corresponding to the target transaction type.

[0099] Step 250: Generate a corresponding target transaction message according to the transaction script and the transaction data.

[0100] Specifically, it is possible to first establish a connection with the mainframe based on the TCP / IP protocol, maintain a smooth connection with the mainframe through the detection and keep-alive mechanisms, sub-packetize the incoming data and send it to the mainframe, sort and reorganize the received data packets, and complete the connection closing operation with the mainframe after receiving the disconnection request; and according to the communication specifications with the mainframe, the incoming data can be converted and encrypted according to the data structure and different types, and finally generate a data packet that can be sent to the mainframe; and then according to the self-explanatory script file writing logic, read the corresponding transaction script from the script folder, and parse it into the program memory, so as to facilitate the subsequent assembly with the test data. And according to the self-explanatory data file organization logic, read the transaction data used by the corresponding transaction from the data folder, and assemble it with the loaded script to obtain a complete transaction message.

[0101] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application reads the transaction script file to obtain the transaction script corresponding to the target transaction type; reads the test data file to obtain the transaction data corresponding to the target transaction type, and can further utilize the existing data in the mainframe database to compile performance test data, thereby greatly improving the credibility of the test and greatly reducing the learning cost and operation cost of the tester.

[0102] In order to further improve the reliability of mainframe performance testing, an embodiment of the mainframe performance testing method provided in this application is shown in FIG. Figure 6 Step 300 of the mainframe performance testing method specifically includes the following contents:

[0103] Step 310: Send the target transaction message to the target mainframe, and based on a preset stress testing tool, enable the target mainframe to execute a performance test corresponding to the target transaction message and generate corresponding test result data.

[0104] Step 320: Receive test result data of the target transaction type corresponding to the target mainframe.

[0105] Specifically, it can be sent to the mainframe through the mainframe transaction core processing module, and then according to the communication specifications with the mainframe, the received data can be decrypted and format converted accordingly according to the data structure and different types, and finally a plaintext data packet that can be used by the open platform program is generated. According to the self-explanatory logic of the previous and next item control file, the previous and next item control files are read to control the order of the previous and next items and the loop logic of the transaction, thereby ensuring the correct progress of the subsequent transaction.

[0106] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application can further improve the reliability of the mainframe performance testing by enabling the target mainframe to execute the performance test corresponding to the target transaction message and generate corresponding test result data based on a preset stress testing tool, and further improve the efficiency, automation and intelligence of the mainframe performance testing process.

[0107] In order to improve the efficiency and automation of the output of the mainframe performance test results, an embodiment of the mainframe performance test method provided in this application is shown in FIG. Figure 7 The mainframe performance testing method further specifically includes the following contents after step 300:

[0108] Step 410: When or after obtaining the test result data corresponding to each target transaction type corresponding to the current transaction test, perform data analysis on the test result data corresponding to each target transaction type based on the transaction message description file to obtain transaction analysis data corresponding to each target transaction type.

[0109] Step 420: Generate a performance test report corresponding to the target mainframe according to the transaction analysis data corresponding to each of the target transaction types.

[0110] Step 430: Output the performance test report.

[0111] Specifically, the unpacked transaction return information can be parsed according to the message description file, and the parsed content can be saved to the database, mainly including whether the transaction is correct, the reason for the error, the time consumed for transaction processing, etc. A test report can be generated based on the parsed transaction return information.

[0112] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application can provide an analysis report with reference value by performing data analysis on the test result data corresponding to each target transaction type based on the transaction message description file to obtain the transaction analysis data corresponding to each target transaction type respectively. It can effectively improve the efficiency and automation of the output of the mainframe performance test results, so that the operation and maintenance personnel can obtain the corresponding mainframe performance test results in a timely manner.

[0113] In order to perform trace-oriented test asset management, an embodiment of the mainframe performance testing method provided in this application is shown in FIG. Figure 8 , the mainframe performance testing method further specifically includes the following contents after step 430:

[0114] Step 510: Obtain corresponding performance test trace data according to the performance test report.

[0115] Step 520: Send the performance test trace data and preset asset management indicators to the corresponding client device based on the preset interface, so that the user can determine whether to perform corresponding asset information operations based on the performance test trace data and preset asset management indicators read from the client device.

[0116] Specifically, asset information can be maintained. After completing the test steps from step 100 to step 400, specific test track data is formed. Performance test data can be managed according to the transaction link. According to different performance test data tracks combined with different indicators, effective management of related assets such as mainframe hardware and software can be performed. Including script files, data files, test results and test reports, etc., for easy search and use. Specifically, a page for the front desk to interact with the user is provided to facilitate the user to enter, query and use asset information, manage test assets, and provide an interface for the user interaction module to call.

[0117] From the above description, it can be seen that the mainframe performance testing method provided in the embodiment of the present application can perform trajectory-oriented test asset management by sending the performance test trajectory data and preset asset management indicators to the corresponding client device based on a preset interface, and effectively maintain asset information, including script files, data files, test results, test reports, etc., which is easy to search and use, and can further improve the user experience of operation and maintenance personnel.

[0118] From the software level, in order to solve the problems of low efficiency, high labor cost and poor test reliability in the existing performance testing methods for mainframes, such as the large number of supporting external applications, cumbersome environment construction, long training time for testers and inability to complete performance testing with high concurrent loads, the present application provides an embodiment of a mainframe performance testing device for executing all or part of the contents of the mainframe performance testing method, see Fig. 9 The mainframe performance testing device specifically includes the following contents:

[0119] The tool connection module 10 is used to directly connect a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test for the target mainframe.

[0120] The message generation module 20 is used to automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset transaction data and transaction script corresponding to the target transaction type.

[0121] The performance testing module 30 is used to send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0122] The embodiment of the mainframe performance testing device provided in the present application can be specifically used to execute the processing flow of the embodiment of the mainframe performance testing method in the above embodiment. Its functions will not be repeated here, and reference can be made to the detailed description of the above method embodiment.

[0123] From the above description, it can be seen that the mainframe performance testing device provided in the embodiment of the present application can directly connect the pressure initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, so as to realize the initiation of the mainframe transaction by calling the core transaction processing module, thereby eliminating the need to build an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and effectively reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can be rapidly expanded horizontally to support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system; by corresponding to the target transaction type and preset The transaction data and transaction script corresponding to the target transaction type automatically generate the corresponding target transaction message, and the target transaction message is sent to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message. The performance test data can be compiled using the existing data in the mainframe database, thereby improving the credibility of the test to a greater extent, greatly reducing the learning cost and operation cost of the tester, and thus effectively improving the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, and can effectively reduce the manpower, time, hardware installation and maintenance costs used for testing, etc., and thus can effectively realize high-concurrency performance testing of bank transaction systems using mainframes, and improve the user experience of testers and other operation and maintenance personnel.

[0124] To further illustrate this solution, this application example designs and completes a set of mainframe performance testing methods and systems for mainframes in response to the performance testing requirements of mainframes with high concurrency requirements. It involves the field of performance testing and implements high-concurrency performance testing of bank transaction systems using mainframes. By using a general stress initiation tool, the core transaction processing module is called to complete the initiation of mainframe transactions. At the same time, a complete set of performance test script generation tools is provided, and performance test data can be compiled using existing data in the mainframe database to further improve the credibility of the test. In addition, the test results are automatically analyzed, and an analysis report with reference value is provided. Track-oriented test asset management is performed on the script data and test results that have been tested.

[0125] The performance testing method and system for mainframes proposed in the application example of this application effectively solve the problems of complicated environment construction and numerous supporting systems under the existing testing system. The mainframe is directly connected to the performance testing stress tool, eliminating the work of setting up an external supporting application environment. At the same time, it provides concise test script writing rules and an automated script and data generation system, which greatly reduces the learning and operating costs of testers. In addition, the application example of this application can be initiated through common general performance testing tools, and can be quickly expanded horizontally, which can support performance testing scenarios of hundreds of thousands of TPS.

[0126] This application example is designed and completed for the performance testing needs of mainframes with high concurrency requirements. A set of mainframe performance testing methods and systems for mainframes have been designed and completed, which realizes high-concurrency performance testing of bank transaction systems using mainframes. By using a general stress initiation tool, the core transaction processing module is called to complete the initiation of mainframe transactions. At the same time, a complete set of performance test script generation tools is provided, and performance test data can be compiled using existing data in the mainframe database to greatly improve the credibility of the test. In addition, the test results are automatically analyzed, and an analysis report with reference value is provided. Track-oriented test asset management is performed for the script data and test results that have been tested.

[0127] See also Fig.10 The mainframe performance testing system mainly includes six parts, namely: stress tool interaction module 1, mainframe transaction core processing module 2, transaction process control module 3, script generation and data organization module 4, result analysis and processing module 5 and asset management module 6.

[0128] Among them, the pressure tool interaction module 1 is responsible for encapsulating the interface of this system to facilitate calling through common pressure initiation tools; the mainframe transaction core processing module 2 is responsible for handling communication and interaction with the mainframe and completing the core logical processing; the transaction process control module 3 is responsible for controlling the transaction process and ensuring the correct completion of the transaction processing process; the script generation and data organization module 4 is responsible for generating a transaction script file in a specific format based on the message description file and the transaction log file, and connecting to the mainframe database to extract data and complete the organization; the result analysis processing module 5 is responsible for processing transaction return information and generating a test report based on the test results; the asset management module 6 is responsible for maintaining asset information, including script files, data files, test results and test reports, etc., for easy search and use.

[0129] The functions of each module of the mainframe performance testing system are described in detail as follows:

[0130] (1) Pressure tool interaction module 1

[0131] The stress tool interaction module 1 is responsible for encapsulating the interface of the mainframe performance test system to facilitate calling through common stress initiation tools. The stress tool interaction module 1 includes three units: an interaction input unit 11, a logic mapping unit 12 and a control output unit 13.

[0132] 1) The interactive input unit 11 receives the interactive command from the external pressure initiating tool and submits the interactive command to the logic mapping unit 12 .

[0133] 2) Logical mapping unit 12: determines the type of the external pressure initiating tool according to the received interactive command, generates a control command of the mainframe performance test system according to the corresponding mapping rule, and submits the control command to the control output unit 13.

[0134] 3) Control output unit 13: Controls the mainframe performance test system to complete corresponding instruction operations according to the received control commands.

[0135] (2) Mainframe transaction core processing module 2

[0136] The mainframe transaction core processing module 2 is responsible for processing the communication interaction with the mainframe and completing the core logic processing. The mainframe transaction core processing module 2 mainly includes the following three units: a bottom communication unit 21, a communication area packaging unit 22 and a communication area unpacking unit 23.

[0137] The example processing flow of the mainframe transaction core processing module 2 is shown in Fig.12 ,include:

[0138] Initiate an 1100 transaction (for example), set the transaction name to 1100 and leave the transaction parameters empty; call TransDispatch to initiate a transaction; pass in the teller information and create a task; read the script, if it fails, exit with an error; if successful, determine whether it is an 1100 transaction, if so, set the transaction parameters: teller password; if not, pass the Task value and Tcb value; Tcb.run(); initialize CAU and initialize the task; create and initialize the gateway and transaction; start the gateway; split the command; execute the command; end the task; whether it is an 1100 transaction, obtain information: host date; the transaction process ends.

[0139] 1) Bottom-layer communication unit 21: Establishes a connection with the mainframe based on the TCP / IP protocol, maintains the connection with the mainframe through the detection and keep-alive mechanisms, divides the incoming data into packets and sends them to the mainframe, sorts and reorganizes the received data packets, and completes the connection closing operation with the mainframe after receiving the disconnection request.

[0140] 2) Communication area packet unit 22: According to the communication specification with the mainframe, the incoming data is converted and encrypted according to the data structure and different types, and finally a data packet that can be sent to the mainframe is generated.

[0141] 3) Communication area unpacking unit 23: According to the communication specification with the mainframe, the received data is decrypted and formatted accordingly according to the data structure and different types, and finally a plaintext data packet is generated that can be used by the open platform program.

[0142] (3) Transaction process control module 3

[0143] The transaction process control module 3 is responsible for controlling the transaction process and ensuring the correct completion of the transaction processing process. It mainly includes the following three units: a script reading and parsing unit 31, a data reading and assembling unit 32, and a transaction pre- and post-item control unit 33.

[0144] Among them, the example processing flow of the transaction process control module 3 is shown in Fig.13 , including: opening Jmeter; static class: loading vuser_info information into thread-safe queue; obtaining default parameters: thread number, data folder path; obtaining thread number, obtaining data folder path, obtaining vuser_info data based on thread number; initializing teller information: constructing userfile and datafile file pointers; initiating 1100 transaction, if the transaction status is failed, exit with an error, if the transaction status is successful, obtain teller information according to the return packet: host date, large transaction sequence number; initiating transaction, if not continuing, initiating 1101 transaction, the process ends and resources are recycled.

[0145] 1) Script reading and parsing unit 31: formulates self-explanatory script file writing logic, reads the corresponding transaction script from the script folder, and parses it into the program memory to facilitate subsequent assembly with test data.

[0146] 2) Data reading and assembling unit 32: formulates self-explanatory data file organization logic, reads the transaction data used by the corresponding transaction from the data folder, and assembles it with the loaded script to obtain a complete transaction message, which is sent to the mainframe through the mainframe transaction core processing module 2.

[0147] 3) Transaction pre- and post-item control unit 33: formulates self-explanatory pre- and post-item control file logic, controls the pre- and post-item sequence and loop logic of the transaction by reading the pre- and post-item control file, and ensures the correct execution of post-item transactions.

[0148] (4) Script generation and data organization module 4

[0149] The script generation and data organization module 4 is responsible for generating a transaction script file in a specific format according to the transaction message description file and the transaction log file, and connecting to the mainframe database to extract data and complete the organization. The script generation and data organization module 4 mainly includes the following five units: a message description file reading and parsing unit 41, a transaction log reading and parsing unit 42, a script file generation unit 43, a mainframe database connection unit 44, and a data extraction and organization unit 45.

[0150] 1) Transaction message description file reading and parsing unit 41: reads the transaction message description file according to the established message interaction logic, and parses the specific file content into the memory, mainly including the message structure, message field, field type, field length and number of loops.

[0151] 2) Transaction log reading and parsing unit 42: obtains the transaction log file from the external access channel, reads the transaction log file, and parses the sent values ​​of the message fields in the log according to the message description file.

[0152] 3) Script file generation unit 43: generates a transaction script file for final use by the system according to the uploaded values ​​parsed from the transaction log and in accordance with the format specified in the message description file.

[0153] 4) Mainframe database connection unit 44: connects to the mainframe database BD2 via jcc.

[0154] 5) Data extraction and organization unit 45: According to the data conditions to be extracted, the mainframe database connection module is used to connect to the database, extract the data that meets the conditions, and generate the data file required for the test according to the parameter information in the generated transaction script file.

[0155] (5) Result analysis and processing module 5

[0156] The result analysis and processing module 5 is responsible for processing the transaction return information and generating a test report according to the test results. The result analysis and processing module 5 mainly includes the following two units: a transaction return information processing unit 51 and a test report generating unit 52.

[0157] 1) Transaction return information processing unit 51: parses the unpacked transaction return information according to the message description file, and saves the parsed content to the database, mainly including whether the transaction is correct, the reason for the error, the time consumed for transaction processing, etc.

[0158] 2) Test report generating unit 52: generates a test report according to the parsed transaction return information.

[0159] (6) Asset Management Module 6

[0160] The asset management module 6 is responsible for maintaining asset information. After completing the test steps, specific test track data is formed. According to the transaction link, performance test data can be managed. According to different performance test data tracks combined with different indicators, relevant assets such as mainframe hardware and software can be effectively managed. Including script files, data files, test results and test reports, etc., for easy search and use. The asset management module 6 mainly includes the following two units: user interaction unit 61 and storage management unit 62.

[0161] 1) User interaction unit 61: provides a page for the front desk to interact with the user, so that the user can enter, query and use asset information.

[0162] 2) Storage management unit 62: manages test assets and provides an interface for the user interaction module to call.

[0163] Based on the above content, the overall process of the mainframe performance testing method implemented by the mainframe performance testing system is as follows:

[0164] Step 71: Prepare transaction message description files and transaction log files.

[0165] Step 72: Generate a transaction script file based on the transaction message description file and the transaction log file, and extract test data from the mainframe database according to test requirements to organize and generate data files.

[0166] Among them, steps 71 and 72 are implemented by the script generation and data organization module 4 in the aforementioned mainframe performance testing system.

[0167] Step 73: Use external tools to call up the mainframe online transaction that needs to be performance tested.

[0168] Wherein, step 73 is implemented by the stress tool interaction module 1 in the aforementioned mainframe performance test system.

[0169] Step 74: Receive external request and submit it to transaction process control module 3 after conversion.

[0170] Wherein, step 74 is implemented by the mainframe transaction core processing module 2 in the aforementioned mainframe performance testing system.

[0171] Step 75: Apply the preset performance testing tool (such as Jmeter, etc.), read the transaction script and data file, assemble the message, and send it to the mainframe for processing through the core processing module.

[0172] Wherein, step 75 is implemented by the transaction process control module 3 in the aforementioned mainframe performance testing system.

[0173] Step 76: parse and process the information returned by the mainframe transaction core processing module.

[0174] Wherein, step 76 is implemented by the mainframe transaction core processing module 2 in the aforementioned mainframe performance testing system.

[0175] Step 77: If there is loop control, jump to step 75.

[0176] Step 78: If there is previous and next item control, jump to step 75.

[0177] Step 79: After completing all transaction contents, generate a test report and collect and manage the assets involved in the test process.

[0178] Among them, step 79 is implemented by the result analysis and processing module 5 and the large asset management module 6 in the aforementioned mainframe performance test system.

[0179] Aiming at the performance testing needs of mainframes with high concurrency requirements, the application example of this application has designed and completed a mainframe performance testing method and system for mainframes, realizing high-concurrency performance testing of bank transaction systems using mainframes. By using a general stress initiation tool, the core transaction processing module is called to complete the initiation of mainframe transactions. At the same time, a complete set of performance test script generation tools is provided, and performance test data can be compiled using existing data in the mainframe database to greatly improve the credibility of the test. In addition, the test results are automatically analyzed, and an analysis report with reference value is provided. Track-oriented test asset management is performed for the script data and test results that have been tested. The application example of this application can achieve the following effects:

[0180] 1. The application example of this application provides an effective performance testing method and system for mainframes in view of the current situation that online transaction testing of mainframes is difficult.

[0181] 2. It makes up for the shortcomings of existing mainframe performance testing methods and greatly shortens the testing cycle. At the same time, it reduces the testing difficulty and equipment and personnel expenses of mainframe performance testing, and fills the gap in existing testing technology that cannot complete extremely high concurrency testing.

[0182] Using performance testing methods and systems for mainframes to quickly complete various mainframe performance testing requirements is of great significance for improving subsequent test quality and ensuring test progress.

[0183] From the hardware level, in order to solve the problems that the existing mainframe performance testing method requires many supporting external applications, cumbersome environment construction, long training time for testers, and inability to complete high concurrent load performance testing, the existing performance testing method for mainframes has low efficiency, high labor costs, and poor test reliability. The present application provides an embodiment of an electronic device for implementing all or part of the content of the mainframe performance testing method, and the electronic device specifically includes the following content:

[0184] Fig.11 FIG. 9 is a schematic block diagram of the system structure of the electronic device 9600 according to an embodiment of the present application. Fig.11 As shown, the electronic device 9600 may include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. It is worth noting that Fig.11 is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0185] In one embodiment, the mainframe performance test function may be integrated into the central processing unit. The central processing unit may be configured to perform the following control:

[0186] Step 100: directly connect a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test on the target mainframe.

[0187] Step 200: automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, and the preset transaction data and transaction script corresponding to the target transaction type.

[0188] Step 300: Send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0189] From the above description, it can be seen that the electronic device provided in the embodiment of the present application can directly connect the pressure initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, so as to realize the initiation of the mainframe transaction by calling the core transaction processing module, thereby eliminating the need to build an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and effectively reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can be rapidly expanded horizontally, and can support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system; by according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset The transaction data and transaction scripts corresponding to the target transaction type automatically generate the corresponding target transaction message, and the target transaction message is sent to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message. The performance test data can be compiled using the existing data in the mainframe database, thereby improving the credibility of the test to a greater extent, greatly reducing the learning cost and operating cost of the testers, and thus effectively improving the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, and can effectively reduce the manpower, time, hardware installation and maintenance costs used for testing, etc., and thus can effectively realize high-concurrency performance testing of bank transaction systems using mainframes, and improve the user experience of testers and other operation and maintenance personnel.

[0190] In another embodiment, the mainframe performance testing device may be configured separately from the central processing unit 9100. For example, the mainframe performance testing device may be configured as a chip connected to the central processing unit 9100, and the mainframe performance testing function may be implemented through the control of the central processing unit.

[0191] like Fig.11 As shown, the electronic device 9600 may also include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is worth noting that the electronic device 9600 does not necessarily have to include Fig.11 In addition, the electronic device 9600 may also include Fig.11 For components not shown, reference may be made to the prior art.

[0192] like Fig.11 As shown, the central processing unit 9100 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor device and / or logic device. The central processing unit 9100 receives input and controls the operation of various components of the electronic device 9600.

[0193] The memory 9140 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices. The above-mentioned information related to the failure may be stored, and a program for executing the relevant information may also be stored. The CPU 9100 may execute the program stored in the memory 9140 to implement information storage or processing, etc.

[0194] The input unit 9120 provides input to the central processing unit 9100. The input unit 9120 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used to display display objects such as images and texts. The display may be, for example, an LCD display, but is not limited thereto.

[0195] The memory 9140 may be a solid-state memory, such as a read-only memory (ROM), a random access memory (RAM), a SIM card, etc. It may also be a memory that saves information even when the power is off, can be selectively erased, and is provided with more data, examples of which are sometimes referred to as EPROMs, etc. The memory 9140 may also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application / function storage unit 9142, which is used to store application programs and function programs or processes for executing the operation of the electronic device 9600 through the central processor 9100.

[0196] The memory 9140 may also include a data storage unit 9143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 9144 of the memory 9140 may include various drivers for communication functions of the electronic device and / or for executing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0197] The communication module 9110 is a transmitter / receiver 9110 that sends and receives signals via an antenna 9111. The communication module (transmitter / receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as the case of a conventional mobile communication terminal.

[0198] Based on different communication technologies, multiple communication modules 9110 may be provided in the same electronic device, such as a cellular network module, a Bluetooth module and / or a wireless LAN module, etc. The communication module (transmitter / receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide an audio output via the speaker 9131 and receive an audio input from the microphone 9132, thereby realizing a common telecommunication function. The audio processor 9130 may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor 9130 is also coupled to the central processor 9100, so that recording can be performed on the local machine through the microphone 9132, and the sound stored on the local machine can be played through the speaker 9131.

[0199] The embodiment of the present application also provides a computer-readable storage medium capable of implementing all the steps in the mainframe performance testing method in the above embodiment. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps in the mainframe performance testing method in the above embodiment are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0200] Step 100: directly connect a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test on the target mainframe.

[0201] Step 200: automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, and the preset transaction data and transaction script corresponding to the target transaction type.

[0202] Step 300: Send the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data.

[0203] From the above description, it can be seen that the computer-readable storage medium provided in the embodiment of the present application can realize the initiation of mainframe transactions by calling the core transaction processing module, by directly connecting the stress initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, eliminating the need to build an external supporting application environment, effectively avoiding the installation and maintenance of a large number of servers, and effectively reducing hardware costs and maintenance costs. It can be initiated through common general performance testing tools, and can be rapidly expanded horizontally to support performance testing scenarios of hundreds of thousands of TPS; it can effectively solve the problems of cumbersome environment construction and numerous supporting systems under the existing testing system; by The transaction data and transaction script corresponding to the target transaction type automatically generate the corresponding target transaction message, and the target transaction message is sent to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message. The performance test data can be compiled using the existing data in the mainframe database, thereby improving the credibility of the test to a greater extent, greatly reducing the learning cost and operation cost of the tester, and thus effectively improving the reliability and convenience of the mainframe performance testing process, and can effectively improve the efficiency, automation and intelligence of the mainframe performance testing process, and can effectively reduce the manpower, time, hardware installation and maintenance costs used for testing, etc., and thus can effectively realize high-concurrency performance testing of bank transaction systems using mainframes, and improve the user experience of testers and other operation and maintenance personnel.

[0204] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0205] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (apparatus), 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 generate 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 1A device that provides the functions specified in a block or multiple blocks.

[0206] 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.

[0207] 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 A step that specifies a function in one or more boxes.

[0208] 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 mainframe performance testing method, characterized in that: include: directly connecting a stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test on the target mainframe; Automatically generate a corresponding target transaction message according to the target transaction type corresponding to the performance test request for the target mainframe currently received, the preset transaction data and transaction script corresponding to the target transaction type; Sending the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data; Before directly connecting the stress initiation tool outside the target mainframe to the target mainframe to initiate the performance test for the target mainframe, the method further includes: Obtain preset transaction message description files and transaction log files; Obtaining a corresponding target format from the transaction message description file, and reading an uploaded value from the transaction log file; Generate a corresponding transaction script file based on the target format of the uploaded value; Based on the preset performance test requirement data, extracting test data from the database corresponding to the target mainframe; A test data file for performing a performance test on the target mainframe is generated according to the transaction script file and the test data.

2. The mainframe performance testing method according to claim 1, characterized in that: The step of directly connecting a stress initiation tool outside the target mainframe to the target mainframe to initiate a performance test on the target mainframe includes: receiving interactive commands from a stress initiation tool external to the target mainframe; Determine the type of the corresponding pressure initiating tool based on the content in the interactive command; A corresponding control command is generated according to the type of the pressure initiation tool and a preset mapping rule, so as to directly connect the pressure initiation tool with the target mainframe based on the control command.

3. The mainframe performance testing method according to claim 1, characterized in that: The automatically generating a corresponding target transaction message according to the target transaction type corresponding to the performance test request currently received for the target mainframe, the preset transaction data and transaction script corresponding to the target transaction type, comprises: receiving a performance test request for the target mainframe including a target transaction type; Obtaining a corresponding target transaction type from the performance test request; Read the transaction script file to obtain a transaction script corresponding to the target transaction type; and, reading the test data file to obtain transaction data corresponding to the target transaction type; A corresponding target transaction message is generated according to the transaction script and the transaction data.

4. The mainframe performance testing method according to claim 1, characterized in that: The sending of the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data includes: Sending the target transaction message to the target mainframe, and enabling the target mainframe to perform a performance test corresponding to the target transaction message based on a preset stress testing tool and generate corresponding test result data; Receive test result data of a target transaction type corresponding to the target mainframe.

5. The mainframe performance testing method according to claim 1, characterized in that: Also includes: When or after obtaining the test result data corresponding to each target transaction type corresponding to the current transaction test, performing data parsing on the test result data corresponding to each target transaction type based on the transaction message description file to obtain transaction parsing data corresponding to each target transaction type; Generate a performance test report corresponding to the target mainframe according to the transaction analysis data corresponding to each of the target transaction types; Output the performance test report.

6. The mainframe performance testing method according to claim 5, characterized in that: Also includes: Acquire corresponding performance test track data according to the performance test report; The performance test track data and the preset asset management indicators are sent to the corresponding client device based on a preset interface, so that the user can determine whether to perform corresponding asset information operations based on the performance test track data and the preset asset management indicators read from the client device.

7. A mainframe performance testing device, characterized in that: include: A tool connection module, used for directly connecting a stress initiation tool outside a target mainframe to the target mainframe to initiate a performance test for the target mainframe; A message generation module, used for automatically generating a corresponding target transaction message according to a target transaction type corresponding to a performance test request currently received for the target mainframe, and preset transaction data and transaction script corresponding to the target transaction type; A performance testing module, used for sending the target transaction message to the target mainframe so that the target mainframe executes the performance test corresponding to the target transaction message and generates corresponding test result data; The mainframe performance testing device is also used for: Obtain preset transaction message description files and transaction log files; Obtaining a corresponding target format from the transaction message description file, and reading an uploaded value from the transaction log file; Generate a corresponding transaction script file based on the target format of the uploaded value; Based on the preset performance test requirement data, extracting test data from the database corresponding to the target mainframe; A test data file for performing a performance test on the target mainframe is generated according to the transaction script file and the test data.

8. 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 computer program, the mainframe performance testing method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the mainframe performance testing method described in any one of claims 1 to 6 is implemented.

Images