Long transaction processing method, device and equipment, medium and product

Abstract

The invention discloses a long transaction processing method and device, equipment, a medium and a product, and relates to the technical field of big data. The method comprises the steps that when it is detected that host operation runs to a target operation step, a communication thread is established through an REXX program and a system management tool; after the communication thread is established, searching at least one target middleware coupling system to be processed in middleware coupling systems managed by the system management tool; generating a long transaction screening rule based on the configuration data set associated with the host operation; screening out at least one target long transaction from transaction processing middleware contained in the target middleware coupling system based on a long transaction screening rule; and executing batch cleaning operation on the target long transaction. The method can automatically process long transactions in batches, improves the efficiency of releasing resources, and can achieve the purposes of reducing the pressure of the resources in time and protecting the host environment.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a long transaction processing method, device, equipment, medium and product. Background Art

[0002] When the application executes financial transactions, some transactions on the host run for a long time due to dead loops or insufficient host resources, and accumulate on the online transaction processing middleware, exceeding the gateway waiting time; even if the operation is finally completed, the gateway will return a transaction timeout or abandon the return message of these timed transactions. Therefore, these long transactions that run for a long time will cause a waste of host resources and affect host performance.

[0003] The existing method is usually that the host maintenance personnel log in to each online transaction processing middleware, check the running time of each running transaction one by one, and then force the long transactions with a long running time to end one by one. However, this method requires manual checking of the running time of each transaction one by one, and then judging and processing the transactions one by one. When there are many transactions running on the transaction processing middleware, the processing takes a lot of time and the processing efficiency is extremely low. Summary of the invention

[0004] The present application provides a long transaction processing method, device, equipment, medium and product, which can automatically process long transactions in batches, improve the efficiency of releasing resources, prevent serious failures such as memory overflow caused by exhaustion of host resources, and achieve the purpose of timely decompression of resources and protection of the host environment.

[0005] In a first aspect, the present application provides a long transaction processing method, the method comprising:

[0006] When it is detected that the host job runs to a target job step, a communication thread is established with the system management tool through a REXX program, wherein the target job step is associated with the REXX program;

[0007] After establishing the communication thread, searching for at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool;

[0008] generating a long transaction screening rule based on a configuration data set associated with the host job;

[0009] Filtering at least one target long transaction from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule;

[0010] A batch cleanup operation is performed on the target long transaction.

[0011] Furthermore, after detecting that the host job runs to the target job step, it also includes: sending the path of the configuration data set to the REXX program; reading system positioning parameters, long transaction determination time and exception transaction list from the configuration data set through the REXX program.

[0012] Furthermore, searching for at least one target middleware coupling system to be processed in the middleware coupling system managed by the system management tool includes: determining an identification code of each middleware coupling system managed by the system management tool, wherein the system management tool includes a plurality of middleware coupling systems; and comparing the system positioning parameter with the identification code of each middleware coupling system to determine at least one target middleware coupling system.

[0013] Furthermore, a long transaction screening rule is generated based on the configuration data set associated with the host job, including: analyzing the exception transaction list to obtain an identification method for the exception transaction; generating a transaction type sub-rule based on the identification method; formulating time thresholds for different transaction time periods based on the long transaction determination time; generating a transaction duration sub-rule based on the time thresholds for different transaction time periods; and splicing the transaction type sub-rule and the transaction duration sub-rule to obtain the long transaction screening rule.

[0014] Furthermore, a batch cleanup operation is performed on the target long transaction, including: determining whether there is a first long transaction in the target long transaction that meets the dead loop determination condition; if there is a first long transaction, generating a transaction disabling operation, and executing the transaction disabling operation on the first long transaction; and executing a forced termination operation on the second long transaction, the second long transaction being a long transaction in the target long transaction other than the first long transaction.

[0015] Furthermore, the method further includes: closing the communication thread between the REXX program and the system management tool.

[0016] In a second aspect, the present application provides a long transaction processing device, the device comprising:

[0017] A communication establishment module, used for establishing a communication thread with the system management tool through a REXX program when it is detected that the host job runs to a target job step, wherein the target job step is associated with the REXX program;

[0018] A positioning and searching module, used for searching at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool after establishing the communication thread;

[0019] A rule generation module, configured to generate a long transaction screening rule based on a configuration data set associated with the host job;

[0020] A transaction screening module, configured to screen out at least one target long transaction from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule;

[0021] The long transaction processing module is used to perform a batch cleanup operation on the target long transaction.

[0022] In a third aspect, the present application provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the long transaction processing method described in any embodiment of the present application.

[0023] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a processor to implement the long transaction processing method described in any embodiment of the present application when executed.

[0024] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the long transaction processing method described in any embodiment of the present application.

[0025] In order to solve the defects of the prior art in the background technology, the embodiment of the present application provides a long transaction processing method, and the execution of the method can bring the following beneficial effects: the present application configures a target operation step for processing long transactions in the host operation, and associates a REXX program with the target operation step; when the host operation runs to the target operation step, first, the REXX program is executed so that the REXX program can interact with the system management tool stably, and multiple middleware coupling systems can be managed; then, based on the system positioning parameters in the configuration data set associated with the host operation, the target middleware coupling system to be processed is accurately located; then, a long transaction screening rule is generated according to the configuration data set, and since the specific parameters in the configuration data set can be flexibly set, it can adapt to different scene requirements and has good flexibility; finally, based on the long transaction screening rule, at least one target long transaction is screened out from the transaction processing middleware contained in the target middleware coupling system; and the target long transaction is batch processed. The present application can automatically process long transactions in batches, improve the efficiency of releasing resources, prevent serious failures such as memory overflow caused by exhaustion of host resources, and achieve the purpose of timely decompression of resources and protection of the host environment.

[0026] It should be noted that the above-mentioned computer instructions may be stored in whole or in part on a computer-readable storage medium, wherein the computer-readable storage medium may be packaged together with the processor of the long transaction processing device, or may be packaged separately from the processor of the long transaction processing device, and this application does not limit this.

[0027] The description of the second, third, ..., and fifth aspects in this application can refer to the detailed description of the first aspect; and the beneficial effects of the description of the second, third, ..., and fifth aspects can refer to the beneficial effect analysis of the first aspect, which will not be repeated here.

[0028] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description.

[0029] It is understandable that before using the technical solutions disclosed in the embodiments of this application, the type, scope of use, and usage scenarios of the personal information involved in this application should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0031] Figure 1 A flowchart of a long transaction processing method provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of a long transaction processing method provided in an embodiment of the present application;

[0033] Figure 3 A schematic diagram of the structure of a long transaction processing device provided in an embodiment of the present application;

[0034] Figure 4 It is a block diagram of an electronic device used to implement a long transaction processing method in an embodiment of the present application. DETAILED DESCRIPTION

[0035] 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 only 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 should fall within the scope of protection of this application.

[0036] It should be noted that the terms "first", "second", "target", and "original" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including", "having", and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0037] Figure 1 A flowchart of a long transaction processing method provided in an embodiment of the present application is provided. This embodiment can be applied to a scenario where a long transaction with a long running time is processed during an online transaction between one or more terminal devices and a server or a host system. A long transaction processing method provided in this embodiment can be executed by a long transaction processing device provided in an embodiment of the present application, which can be implemented by software and / or hardware and integrated in an electronic device that executes this method.

[0038] See also Figure 1 The method of this embodiment includes but is not limited to the following steps:

[0039] S110, when it is detected that the host job runs to the target job step, a communication thread is established with the system management tool through a Restructured Extended Executor (REXX) ​​program.

[0040] Among them, a host job refers to a job running on a host. The host can be a large host or a small or medium-sized server with a specific host operating system installed. A job can refer to a job order block (JOB) job written in the Job Control Language (JCL) language. A JOB job contains several job steps, and each job step implements one or more functions. A target job step can refer to a job step used to process long transactions. The target job step is associated with a REXX program.

[0041] REXX is a programming language mainly used on large mainframes. It should be noted that the REXX program in this application is specifically used to interact with system management tools, and the function of accessing system management tools is realized through the preset application programming interface (API) technology. The REXX program in the existing solution directly connects to the transaction processing middleware through the preset API technology. The solution of this application connects to the system management tool through the preset API technology. The advantage is that it can manage multiple middleware coupling systems and can process long transactions in batches.

[0042] Transaction processing middleware can support online transaction services, provide online transaction processing and transaction management for applications, realize high-concurrency online transactions, and provide users with real-time transaction requests and responses, which is also commonly referred to as online. The middleware coupling system is a coupling system of a group of interconnected transaction processing middleware that handles customer workloads. It has terminals, applications, resources, etc., and meets customers' requirements for high processing capabilities and high availability. System management tools are tools for managing multiple middleware coupling systems.

[0043] Furthermore, after detecting that the host job runs to the target job step, it also includes: sending the path of the configuration data set to the REXX program so that the REXX program can know where to obtain the configuration parameters; reading the system positioning parameters, long transaction determination time and exception transaction list from the configuration data set through the REXX program.

[0044] In the embodiment of the present application, a REXX program can be designed, which uses a preset API technology to access the system management tool. The parameters used by the REXX program can be configured on the host data set, that is, the configuration data set. A host job can be designed to call up the REXX program and specify the path of the configuration data set in the external file definition. In the external file definition part of the host job, the path of the configuration data set must be clearly specified so that the REXX program can obtain the required configuration parameters when the job is running.

[0045] In addition, a timer can be added to the host to specify the job library where the host job is located, as well as the time and cycle of the job trigger operation, so that long transactions can be processed automatically. When the timer triggers the job in the host job library, the job is submitted to the job login subsystem for operation, so as to manage the job scheduling operation, input and output information, etc. in the host system. When it is detected that the host job runs to the target job step, the REXX program uses the preset API technology to access the system management tool and establish a communication thread. This communication thread is like a data transmission channel, which enables the REXX program to exchange information with the system management tool stably, such as sending requests and receiving responses.

[0046] Optionally, the configuration data set may include system positioning parameters, long transaction determination time, and exception transaction list, etc., wherein the system positioning parameters are used to clarify the name of the middleware coupling system to be accessed (such as an identification code) so as to accurately locate the target middleware coupling system; the long transaction determination time is used to determine what kind of transaction duration can be determined as a long transaction; the exception transaction list is a list of transactions that itself needs to run for a long time. Transactions in the exception transaction list are eliminated from all transactions to screen out long transactions to be processed in this embodiment.

[0047] S120 . After establishing the communication thread, searching for at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool.

[0048] Specifically, searching for at least one target middleware coupling system to be processed in the middleware coupling system managed by the system management tool includes: determining an identification code of each middleware coupling system managed by the system management tool; comparing the system positioning parameter with the identification code of each middleware coupling system to determine at least one target middleware coupling system.

[0049] The system management tool includes multiple middleware coupling systems, which cooperate and relate to each other to jointly complete related business processing. In order to accurately identify each middleware coupling system, it is necessary to set an identification code to distinguish key information of different middleware coupling systems, such as the main business functions involved in the coupling system, the specific resource range connected, and its position number in the entire system management tool management architecture.

[0050] The system location parameter includes the identification code of the middleware coupling system to be accessed. The system location parameter is compared with the identification code of each middleware coupling system one by one. If the characteristics reflected by the identification code of a middleware coupling system match the system location parameter, then this middleware coupling system will be determined as the target middleware coupling system to be processed. Finally, one or more target middleware coupling systems that meet the conditions may be found.

[0051] S130 . Generate long transaction screening rules based on the configuration data set associated with the host job.

[0052] In the job processing environment of a large mainframe, in order to accurately filter out long transactions, it is necessary to generate corresponding filtering rules based on the configuration data set associated with the mainframe job. Specifically, generating long transaction filtering rules based on the configuration data set associated with the mainframe job includes: analyzing the exception transaction list to obtain the identification method of the exception transaction; generating transaction type sub-rules based on the identification method; formulating time thresholds for different transaction periods based on the long transaction determination time; generating transaction duration sub-rules based on the time thresholds for different transaction periods; and splicing the transaction type sub-rules and transaction duration sub-rules to obtain long transaction filtering rules.

[0053] In an embodiment of the present application, during the transaction processing, there are some special circumstances that cause transactions that cannot be measured according to the conventional long transaction judgment criteria. These transactions are listed as exception transactions and are aggregated to form an exception transaction list. For example, some transactions involving complex business logic, specific customer groups, or transactions arising from special external cooperative relationships, although the transaction duration may be long, belong to the normal business scope and are not the long transactions that this embodiment focuses on. By analyzing the exception transaction list, it is possible to summarize the identification method for distinguishing exception transactions from ordinary transactions. For example, these exception transactions are identified by the type code of the transaction, the level of the customer initiating the transaction, the source channel of the transaction, etc. According to the determined identification method of the exception transaction, a specific rule for screening the transaction type is constructed.

[0054] During business peaks, the judgment time for long transactions may be appropriately relaxed because the system load is high and the transaction processing speed may naturally slow down. During business troughs, the judgment criteria may be stricter. Considering the dynamic adjustment of time, based on the long transaction judgment time, the corresponding time thresholds are determined for different trading periods (such as peak period, trough period, normal period, etc.). According to the time thresholds of different trading periods, corresponding rules are constructed to filter transactions whose transaction duration meets the long transaction standards. The transaction type sub-rule and the transaction duration sub-rule are combined to form a complete rule for filtering long transactions. Optionally, a structured query language (SQL) statement can be used to express the rule.

[0055] S140. Filter out at least one target long transaction from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule.

[0056] Among them, a middleware coupling system includes multiple transaction processing middleware.

[0057] In an embodiment of the present application, the running time of all transactions in each transaction processing middleware in the target middleware coupling system can be obtained first, and then the target long transactions that meet the conditions can be screened out according to the long transaction screening rules.

[0058] Further, it is determined whether the number of target long transactions is greater than 0. If it is greater than 0, step S150 is executed; otherwise, step S110 is executed to enter the next processing cycle.

[0059] S150. Perform a batch cleanup operation on the target long transaction.

[0060] Specifically, the batch cleaning operation is performed on the target long transaction, including: determining whether there is a first long transaction that meets the infinite loop judgment condition in the target long transaction; if there is a first long transaction, a transaction disabling job is generated, and the transaction disabling job is performed on the first long transaction through a job execution command to prevent the transaction of the infinite loop from being triggered again, thereby preventing the serious fault of memory overflow caused by exhaustion of host resources. The second long transaction is forced to end the operation through a job execution command, and the operation of the long transaction is forced to end in batches, and the second long transaction is a long transaction in the target long transaction except the first long transaction.

[0061] Optionally, after executing the transaction prohibition operation on the first long transaction, an infinite loop transaction alarm and a transaction prohibition notification need to be generated. After executing the forced termination operation on the second long transaction, a long transaction alarm and a processing result notification need to be generated.

[0062] Furthermore, the long transaction processing method of the present application also includes: closing the communication thread between the REXX program and the system management tool, and entering the next processing cycle.

[0063] The technical solution provided in this embodiment is as follows: when it is detected that the host job runs to the target job step, a communication thread is established with the system management tool through the REXX program; after the communication thread is established, at least one target middleware coupling system to be processed is searched in the middleware coupling system managed by the system management tool; a long transaction screening rule is generated based on the configuration data set associated with the host job; at least one target long transaction is screened out from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule; and a batch cleanup operation is performed on the target long transactions. The present application configures a target job step for processing long transactions in the host job, and associates a REXX program with the target job step; when the host job runs to the target job step, first, the REXX program is executed so that the REXX program can interact with the system management tool stably, and multiple middleware coupling systems can be managed; then, based on the system positioning parameters in the configuration data set associated with the host job, the target middleware coupling system to be processed is accurately located; then, a long transaction screening rule is generated according to the configuration data set. Since the specific parameters in the configuration data set can be flexibly set, it can adapt to different scene requirements and has good flexibility; finally, based on the long transaction screening rule, at least one target long transaction is screened out from the transaction processing middleware contained in the target middleware coupling system; and the target long transactions are batch processed. The present application can automatically process long transactions in batches, improve the efficiency of releasing resources, prevent serious failures such as memory overflow caused by exhaustion of host resources, and achieve the purpose of timely decompression of resources and protection of the host environment.

[0064] like Figure 2 FIG. 1 is a schematic diagram of a long transaction processing method provided in an embodiment of the present application. Figure 2 In the figure, reference numeral 101 is a timer, reference numeral 102 is a host job library, reference numeral 103 is a job login subsystem, reference numeral 104 is a REXX program, reference numeral 105 is a configuration data set, reference numeral 106 is a system management tool, reference numerals 107 and 108 are middleware coupling systems (i.e., the middleware coupling system in the figure), and reference numerals 201, 202, 301 and 302 are transaction processing middleware (i.e., the transaction processing middleware in the figure).

[0065] Figure 2The diagram shows that the system management tool 106 manages two middleware coupling systems, namely, the middleware coupling system 107 and the middleware coupling system 108. The middleware coupling system 107 couples two transaction processing middlewares, namely, the transaction processing middleware 201 and the transaction processing middleware 202. Two online transaction APP1 and APP2 are running on the transaction processing middleware 201, and two online transaction APP3 and APP4 are running on the transaction processing middleware 202. The middleware coupling system 108 couples two transaction processing middlewares, namely, the transaction processing middleware 301 and the transaction processing middleware 302. Two online transaction APP5 and APP6 are running on the transaction processing middleware 301, and two online transaction APP7 and APP8 are running on the transaction processing middleware 302.

[0066] First, the timer 101 triggers the job in the host job library 102, and the job is submitted to the job login subsystem 103 and starts running. The job contains information such as the path and name of the REXX program 104 and the configuration data set 105.

[0067] Then, when the job runs to the job step where the REXX program 104 is located, the path of the configuration data set 105 specified by the external file is passed to the REXX program 104, and the REXX program 104 associates the external file with the internal file to obtain the parameters in the configuration data set 105.

[0068] Afterwards, the REXX program 104 uses the preset API technology to access the system management tool, establishes a communication thread, and then locates the corresponding target middleware coupling system through the system positioning parameters (such as CONTEXT and SCOPE, etc.) in the configuration data set 105, that is, Figure 2 The middleware coupling system 107 or the middleware coupling system 108 in the embodiment.

[0069] Finally, according to the parameters such as the exception transaction list and the long transaction determination time in the configuration data set 105, the long transaction screening rules are spliced ​​to screen out the target long transactions that meet the conditions from the target middleware coupling system. For example, if the long transaction selection condition configured in the configuration data set 105 is that the running time exceeds 1 second, then the transactions APP2 and APP3 in the figure are long transactions; if the dead loop transaction feature is that the running time exceeds 600 seconds, then the transaction APP7 in the figure is a dead loop transaction.

[0070] Figure 3 A schematic diagram of the structure of a long transaction processing device provided in an embodiment of the present application, such as Figure 3 As shown, the device 300 may include:

[0071] A communication establishment module 310, for establishing a communication thread with the system management tool through a REXX program when it is detected that the host job runs to a target job step, wherein the target job step is associated with the REXX program;

[0072] A positioning and searching module 320 is used to search for at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool after establishing the communication thread;

[0073] A rule generation module 330, for generating a long transaction screening rule based on the configuration data set associated with the host job;

[0074] A transaction screening module 340, configured to screen out target long transactions from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule;

[0075] The long transaction processing module 350 is used to perform a batch cleanup operation on the target long transaction.

[0076] Furthermore, the long transaction processing device may further include: a parameter acquisition module;

[0077] The parameter acquisition module is used to send the path of the configuration data set to the REXX program after detecting that the host job runs to the target job step; and read the system positioning parameters, long transaction determination time and exception transaction list from the configuration data set through the REXX program.

[0078] Furthermore, the above-mentioned positioning and searching module 320 can be specifically used to: determine the identification code of each middleware coupling system managed by the system management tool, wherein the system management tool includes a plurality of middleware coupling systems; compare the system positioning parameters with the identification code of each middleware coupling system to determine at least one target middleware coupling system.

[0079] Furthermore, the above-mentioned rule generation module 330 can be specifically used to: analyze the exception transaction list to obtain the identification method of the exception transaction; generate a transaction type sub-rule based on the identification method; formulate time thresholds for different transaction time periods based on the long transaction determination time; generate a transaction duration sub-rule based on the time thresholds for different transaction time periods; and splice the transaction type sub-rule and the transaction duration sub-rule to obtain the long transaction screening rule.

[0080] Furthermore, the above-mentioned long transaction processing module 350 can be specifically used to: determine whether there is a first long transaction that meets the dead loop judgment condition in the target long transaction; if there is a first long transaction, generate a transaction disabling operation, and execute the transaction disabling operation on the first long transaction; execute a forced termination operation on the second long transaction, and the second long transaction is a long transaction in the target long transaction except the first long transaction.

[0081] Furthermore, the above-mentioned long transaction processing device may further include: a communication closing module;

[0082] The communication closing module is used to close the communication thread between the REXX program and the system management tool.

[0083] The long transaction processing device provided in this embodiment can be applied to the long transaction processing method provided in any of the above embodiments, and has corresponding functions and beneficial effects.

[0084] Figure 4 It is a block diagram of an electronic device for implementing a long transaction processing method of an embodiment of the present application. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0085] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0086] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0087] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a long transaction processing method.

[0088] In some embodiments, the long transaction processing method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the long transaction processing method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the long transaction processing method in any other appropriate manner (e.g., by means of firmware).

[0089] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0090] Computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0091] In the context of the present application, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0092] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0093] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server) or a computing system that includes middleware components (e.g., an application server) or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein) or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0094] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0095] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. For example, those skilled in the art can use the various forms of processes shown above to reorder, add, or delete steps; the steps recorded in the present application can be performed in parallel, sequentially, or in different orders, as long as the desired results of the technical solution of the present application can be achieved, and this document does not limit them here.

[0096] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A long transaction processing method, characterized in that: The method comprises: When it is detected that the host job runs to a target job step, a communication thread is established with the system management tool by reconstructing the extended executor REXX program, wherein the target job step is associated with the REXX program; After establishing the communication thread, searching for at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool; generating a long transaction screening rule based on a configuration data set associated with the host job; Filtering at least one target long transaction from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule; A batch cleanup operation is performed on the target long transaction.

2. The long transaction processing method according to claim 1, characterized in that: After detecting that the host job runs to the target job step, it also includes: sending the path of the configuration data set to the REXX program; The system positioning parameters, long transaction determination time and exception transaction list are read from the configuration data set by the REXX program.

3. The long transaction processing method according to claim 2, characterized in that: Searching for at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool includes: determining an identification code of each middleware coupling system managed by the system management tool, the system management tool including a plurality of middleware coupling systems; The system positioning parameter is compared with the identification code of each middleware coupling system to determine at least one target middleware coupling system.

4. The long transaction processing method according to claim 2, characterized in that: Generating a long transaction screening rule based on the configuration data set associated with the host job, including: Analyze the exception transaction list to obtain identification methods of the exception transactions; Generate a transaction type sub-rule based on the identification method; Formulate time thresholds for different trading sessions based on the long transaction determination time; Generate transaction duration sub-rules based on the time thresholds of the different transaction periods; The transaction type sub-rule and the transaction duration sub-rule are concatenated to obtain the long transaction screening rule.

5. The long transaction processing method according to claim 1, characterized in that: Performing a batch cleanup operation on the target long transaction, including: Determine whether there is a first long transaction that meets the infinite loop determination condition in the target long transaction; If the first long transaction exists, a transaction disabling operation is generated, and the transaction disabling operation is executed on the first long transaction; A forced termination operation is performed on a second long transaction, where the second long transaction is a long transaction in the target long transaction except the first long transaction.

6. The long transaction processing method according to claim 1, characterized in that: The method further comprises: The communication thread between the REXX program and the system management tool is closed.

7. A long transaction processing device, characterized in that: The device comprises: A communication establishment module, used for establishing a communication thread with the system management tool through a REXX program when it is detected that the host job runs to a target job step, wherein the target job step is associated with the REXX program; A positioning and searching module, used for searching at least one target middleware coupling system to be processed in the middleware coupling systems managed by the system management tool after establishing the communication thread; A rule generation module, configured to generate a long transaction screening rule based on a configuration data set associated with the host job; A transaction screening module, configured to screen out at least one target long transaction from the transaction processing middleware included in the target middleware coupling system based on the long transaction screening rule; The long transaction processing module is used to perform a batch cleanup operation on the target long transaction.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores a computer program executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the long transaction processing method described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the long transaction processing method according to any one of claims 1 to 6 when executed.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the long transaction processing method according to any one of claims 1 to 6.

Images