Cross-application data protection system and monitoring protection method based on z / OS system

Abstract

A z / OS-based cross-application data protection system and monitoring protection method relate to the fields of host device operation and maintenance and intelligent operation and maintenance, and can be applied to the financial field and other fields. The system comprises a client device, a front-end server, and a host server; the host server comprises a host server management and control platform, multiple logical partitions, and multiple couplers; the client device is connected to application services arranged in the multiple logical partitions through the front-end server; the host server management and control platform is respectively connected to the multiple logical partitions and the multiple couplers; the multiple logical partitions respectively independently run one or more application services, and provide received cross-application request data packets to corresponding other logical partitions through the multiple couplers; the couplers monitor the operating status of the connected logical partitions and the current coupler, generate abnormal prompt data when the operating status is abnormal, and provide the abnormal prompt data to the host server management and control platform.

Description

Technical Field

[0001] This application relates to the fields of host device operation and maintenance and intelligent operation and maintenance, and can be applied to the financial field and other fields, especially to a cross-application data protection system and monitoring protection method based on the z / OS system. Background Art

[0002] Currently, the majority of core banking operations at large state-owned banks still run on IBM mainframes (also known as mainframes). IBM mainframes utilize z / OS (z / Operating System), a mainframe operating system that provides a variety of middleware for processing online transaction data. Banks' online systems are generally built on this middleware. While many types of middleware exist on banking mainframes, CICS (Customer Information Control System) middleware is a powerful and widely used type. It offers horizontally scalable clustering capabilities, providing commercial banks with powerful data processing capabilities. However, due to the large number of customers at large banks, transaction spikes can occur during critical events or during key periods (such as Singles' Day, fund sales, and major merchant promotions). This can significantly impact mainframe services, both due to increased business volume and the increased consumption of system resources per transaction. This can lead to middleware downtime if unanticipated. To ensure the normal operation of the host, the industry often uses two methods to protect the host: one is to install a load balancing device on the general front-end server before the transaction is placed on the host server to control the number of transactions; the other is to install a monitoring device on the host to monitor the host's CPU, memory and other resource data. If it is found that the resource usage is too high, the acceptance of new transaction requests will be suspended.

[0003] However, in the actual operation and maintenance of the bank's mainframe servers, it was found that sometimes the CPU, memory and other resource usage of the mainframe servers was not high, but some online transaction data requests that needed to cross systems, applications and transactions on the mainframe were submitted to the IBM mainframe server. The server processing was congested and caused a large number of transaction failures. At this time, if the above two traditional protection methods were adopted, if the first protection solution was adopted, the general front-end server could not identify the operating status of the mainframe and did not know what abnormal conditions had occurred in the host system. It could only detect a large number of transaction failures and initiate emergency protection measures, causing other normal transactions to be rejected by the protection device, resulting in the termination of the entire mainframe system service and bringing about a larger secondary production accident. If the second protection solution is adopted, the traditional monitoring of the server's CPU, memory and other resource data cannot correctly identify the problem. However, due to the existence of the host system's Parallel Sysplex technology and LPAR (Logic Partition), when the online transaction requests involving cross-system, cross-application, and cross-transaction on the host reach a peak, the host data processing channel becomes congested. However, at this time, the utilization rate of the host's CPU, memory and other resources is often not high. Therefore, for such cross-system, cross-application, and cross-transaction online transaction data requests, the second protection solution cannot truly play an effective role in protecting and reusing them. Moreover, when such congestion problems occur, large host server administrators cannot accurately locate and discover the cause of the problem, let alone adopt effective means to solve the congestion problem.

[0004] In summary, a cross-application data monitoring and processing protection system and method based on the Z / OS mainframe is needed to ensure the security and stability of cross-system, cross-application, and cross-transaction online transaction data processing performed by IBM mainframe servers in multiple z / OS systems using Parallel Sysplex technology. When peak traffic arrives, suppression measures can be proactively adopted to protect the stable operation of the server, and problem logs can be provided to help mainframe server administrators quickly locate problems so that more mitigation measures can be taken to ensure system security. Summary of the Invention

[0005] The present application aims to provide a z / OS-based cross-application data protection system and monitoring protection method. Based on the process characteristics of transaction data processing on multiple z / OS systems using Parallel Sysplex technology on IBM mainframe servers, the system overcomes the shortcomings of existing processing models that may be overwhelmed by instantaneous high pressure during cross-system, cross-application, and cross-transaction online transaction data processing. The system ensures the security and stability of the mainframe server and provides a problem log to help mainframe server administrators quickly locate problems so that more mitigation measures can be taken to ensure system security.

[0006] To achieve the above-mentioned purpose, the cross-application data protection system based on the z / OS system provided in the present application specifically includes a client device, a front-end server and a host server; the host server includes a host server management and control platform, multiple logical partitions and multiple couplers; the client device is connected to the application services arranged in the multiple logical partitions through the front-end server; the host server management and control platform is respectively connected to the multiple logical partitions and the multiple couplers; the multiple logical partitions respectively run one or more application services independently, and provide the received cross-application request data packets to the corresponding other logical partitions through the multiple couplers; the coupler monitors the operating status of the connected logical partitions and the current coupler, generates abnormal prompt data when the operating status is abnormal, and provides the abnormal prompt data to the host server management and control platform.

[0007] In the above-mentioned z / OS system-based cross-application data protection system, optionally, the logical partitions in the same system complex among the multiple logical partitions are connected to the same clock server to achieve clock synchronization.

[0008] In the above-mentioned cross-application data protection system based on the z / OS system, optionally, the coupler includes a coupler status monitoring device, a coupler control device and a coupler data processing device; the coupler status monitoring device is used to monitor the current operating status of the coupler, and the cross-application request data packet data waiting to be transferred in the transaction queue of the coupler data processing device, generate monitoring data according to the operating status and the cross-application request data packet data, generate an alarm signal according to the comparison result between the monitoring data and the preset alarm threshold, and provide it to the coupler control device; the coupler control device is used to compare the monitoring data with the preset protection strategy according to the alarm signal, shut down the coupler according to the comparison result and generate abnormal prompt data; the coupler data processing device is used to connect the logical partition, convert the format of the cross-application request data packet and arrange it in the data processing queue, and forward the cross-application request data packet to the corresponding logical partition for processing according to the queue order and the first-in-first-out principle.

[0009] In the above-mentioned cross-application data protection system based on the z / OS system, optionally, the coupler also includes a coupler monitoring parameter storage device, a coupler monitoring policy adjustment device and a coupler exception reporting device; the coupler monitoring parameter storage device is used to store preset alarm thresholds and preset protection policies; the coupler monitoring policy adjustment device is used to collect historical operating data of the current coupler and the logical partition, obtain adjustment parameters through self-learning analysis based on the historical operating data, and adjust the preset alarm thresholds and preset protection policies based on the adjustment parameters; the coupler exception reporting device is used to provide the exception prompt data to the host server management and control platform.

[0010] In the above-mentioned cross-application data protection system based on the z / OS system, optionally, the coupler monitoring strategy adjustment device includes a data acquisition module, a matrix generation module, an evaluation and calculation module and an update module; the data acquisition module is used to collect the historical operation data of the current coupler and the logical partition according to a preset period, and compress the historical operation data after dividing it into time intervals to generate reference data; the matrix generation module is used to generate vector data from the reference data of the same time interval, and combine the vector data in time sequence to generate a historical performance data matrix; the evaluation and calculation module is used to calculate and obtain historical health data based on a preset health assessment model and the historical performance data matrix; and, based on the historical health data, obtain the health status of multiple time points, and obtain adjustment parameters based on the health status and the alarm thresholds of the corresponding time points; the update module is used to adjust the preset alarm threshold and the preset protection strategy based on the adjustment parameters.

[0011] The present application also provides a monitoring and protection method for the cross-application data protection system based on the z / OS system, the method comprising: a front-end server obtaining a transaction request type based on received transaction request data, obtaining corresponding logical partition information based on analysis of the transaction request type, providing the cross-application request data packet data to the corresponding logical partition for parsing and conversion processing based on the logical partition information to obtain transaction request parameters; providing the transaction request parameters to other corresponding logical partitions through a coupler for processing, generating a processing result based on the feedback result, and feeding back the processing result to the client device that initiated the transaction request data through the front-end server; and using the coupler to monitor the operating status of the connected logical partitions and the current coupler, and generating and storing abnormal prompt data when the operating status is abnormal.

[0012] In the above-mentioned monitoring and protection method, optionally, the operating status of the coupler includes the operating parameters of the processor, memory and hard disk of the coupler, and the operating status of the logical partition includes the transaction type, the operating status of the processing device on the previous logical partition, the transaction processing time of the previous logical partition processing device, and the transaction processing results.

[0013] The present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method when executing the computer program.

[0014] The present application also provides a computer-readable storage medium, which stores a computer program for executing the above method.

[0015] The present application also provides a computer program product, comprising a computer program / instruction, which implements the steps of the above method when executed by a processor.

[0016] The beneficial technical effects of this application are: within the context of the ParallelSysplex technology currently used by IBM mainframe servers, a coupler status monitoring device is provided on the coupler to perform transaction-level data monitoring. When an abnormality occurs, peak protection can be implemented within the host server according to the protection strategy, avoiding the disadvantage of transient high pressure in the online transaction data processing across systems, applications, and transactions on the server, thereby ensuring the security and stability of the mainframe server system. When an abnormal CF is overloaded, the CF can proactively report the type of abnormal transaction, the number of CICS across systems, and the resource status of the CF system to the host server management and control platform through the coupler abnormality reporting device. This overcomes the current defect of IBM mainframe servers that can only periodically poll each CF for data. When an abnormality occurs, the administrator can quickly locate the problem, improve problem solving efficiency, and ensure the security and stability of the mainframe server system. A monitoring policy adjustment device is provided on the CF, which uses machine learning to automatically adjust monitoring parameters, ensuring that the CF can adaptively adjust parameters based on the characteristics of transaction request data from the host and different applications, making the parameters more reasonable and avoiding operator errors. When a congestion anomaly occurs, the host server management and control platform receives the alarm information from the coupler anomaly reporting device. It can manually or automatically check the resource status of the problem target LPAR partition and the operation status of CICS, and handle the problem (for example, manually stop the abnormal job processing, automatically call the Z / OS resource balancing device to add hardware resources to the LPAR partition with insufficient resources, etc.), quickly restore the CICS transaction processing capacity of the problem LPAR partition, and set the coupler control device status to "normal". BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application, constitute a part of the present application, and do not constitute a limitation of the present application. In the drawings:

[0018] Figure 1A schematic diagram of the structure of a z / OS-based cross-application data protection system provided in one embodiment of the present application;

[0019] Figure 2 A schematic structural diagram of a coupler provided in one embodiment of the present application;

[0020] Figure 3 A schematic diagram of the structure of a coupler monitoring strategy adjustment device provided in one embodiment of the present application;

[0021] Figure 4 A schematic diagram of an adjustment process of a coupler monitoring strategy adjustment device provided in one embodiment of the present application;

[0022] Figure 5 A schematic diagram of the application process of a cross-application data protection system based on z / OS system provided in one embodiment of the present application;

[0023] Figure 6 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0024] The following will describe in detail the implementation methods of this application in conjunction with the accompanying drawings and examples, so that the application can fully understand how technical means are used to solve technical problems and achieve technical effects, and implement them accordingly. It should be noted that as long as there is no conflict, the various embodiments and the various features in each embodiment of this application can be combined with each other, and the resulting technical solutions are all within the scope of protection of this application.

[0025] Additionally, the steps shown in the flowcharts of the accompanying drawings may be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowcharts, in some cases the steps shown or described may be performed in an order different from that shown.

[0026] Please refer to Figure 1As shown, the cross-application data protection system based on the z / OS system provided by the present application specifically includes a client device 1, a front-end server 2, and a host server; the host server includes a host server management and control platform 5, multiple logical partitions 3, and multiple couplers 4; the client device 1 is connected to the application services arranged in the multiple logical partitions 3 through the front-end server 2; the host server management and control platform 5 is respectively connected to the multiple logical partitions 3 and the multiple couplers 4; the multiple logical partitions 3 each independently run one or more application services, and provide the received cross-application request data packets to the corresponding other logical partitions 3 through the multiple couplers 4; the coupler 4 monitors the operating status of the connected logical partitions 3 and the current coupler 4, and when the operating status is abnormal, generates abnormal prompt data, and provides the abnormal prompt data to the host server management and control platform 5. Among the multiple logical partitions, the logical partitions in the same system complex are connected to the same clock server to achieve clock synchronization.

[0027] Specifically, such as Figure 1 As shown, the present application divides a single z series host (e.g., z10 model) into multiple logical partitions (LPARs). OS / 390 and z / OS systems can be run independently on each LPAR. Each LPAR can be connected to a client device through a front-end server. Figure 1 As shown, a cross-application data monitoring and processing protection system based on a Z / OS host includes: a client device 1, a front-end server 2, several LPAR partitions, several couplers (CFs), and a host server management and control platform 5. The several LPAR partitions, several couplers (CFs), and the host server management and control platform are all deployed on the host server. The client device is connected to the application services deployed in the corresponding LPAR via the front-end server. The LPAR partition is linked to other LPAR partitions via the couplers (CFs). Different LPAR partitions synchronize clocks and exchange data across the system. All couplers (CFs) and LPAR partitions are connected to the host server management and control platform 5. When a coupler (CF) or LPAR partition experiences an operating peak or other anomaly, the anomaly is reported to the host server management and control platform 5 and registered in an anomaly register on the host server management and control platform 5, helping administrators quickly locate the problem.

[0028] Specifically, the client device 1 is a user requesting a host transaction, and may be an application system of an open platform, which submits data to the host through the front-end server 2 to request a transaction service.

[0029] The front-end server 2 connects the client device 1 and the host server and is responsible for data format conversion and communication interaction functions. Because the client device 1 is generally a development platform application, and the host server is an IBM mainframe platform using the Z / OS system, the data and communication areas are very different, requiring data conversion processing by the front-end server.

[0030] The logical partitions (LPARs) can run OS / 390 and z / OS systems. All systems within a SYSPLEX must abandon their own clocks and connect to a common clock server to synchronize the systems within the SYSPLEX. All systems are connected to multiple disk drives via ESCON Director, enabling data sharing. The LPAR partitions are allocated independent hardware resources such as CPU, memory, and disk. They receive transaction processing request data from client terminals sent by the front-end server 2 through a data receiving device, and process the sent request data by running CICS middleware on an independent CICS transaction processing device and installing independent application processing software.

[0031] The coupling facility (CF) is a device on a host server that manages shared data and communication between different partition systems. The device is equipped with memory, specific channels, and a built-in operating system. Unlike other channels, it has no input and output devices, and its operating system is also very small. The coupling device is very powerful, like a cache, with the following three main purposes: (1) shared lock information of all systems in the complex; (2) cache information of shared data (such as databases) of all systems in the complex; and (3) shared data list information of all systems in the complex. All this information in the coupling CF device resides in memory, so a coupling device usually has a large memory. As a coupling device, it can be a separate system or a logical partition LPAR. The coupler is the core channel for online transaction data transmission between LPAR partitions on a large host server across systems, applications, and transactions. When transaction peaks occur, the core channel is prone to data congestion.

[0032] The host server management and control platform is a management and operation platform for IBM mainframe servers. It can regularly check the status of each partition and each hardware and software system of the mainframe server through polling, and can also check the abnormal monitoring and early warning information actively reported by CF and other devices. Administrators can quickly locate problems and take corresponding measures by checking the early warning data information, thereby improving problem-solving efficiency and ensuring the security and stability of large mainframe server systems.

[0033] In one embodiment of the present application, the coupler includes a coupler status monitoring device, a coupler control device and a coupler data processing device; the coupler status monitoring device is used to monitor the current operating status of the coupler, and the cross-application request data packet data waiting to be circulated in the transaction queue of the coupler data processing device, generate monitoring data according to the operating status and the cross-application request data packet data, generate an alarm signal according to the comparison result of the monitoring data and the preset alarm threshold, and provide it to the coupler control device; the coupler control device is used to compare the monitoring data with the preset protection strategy according to the alarm signal, shut down the coupler according to the comparison result and generate abnormal prompt data; the coupler data processing device is used to connect the logical partition, convert the format of the cross-application request data packet and arrange it in the data processing queue, and forward the cross-application request data packet to the corresponding logical partition for processing according to the queue order and the first-in-first-out principle. Furthermore, the coupler also includes a coupler monitoring parameter storage device, a coupler monitoring strategy adjustment device and a coupler abnormality reporting device; the coupler monitoring parameter storage device is used to store preset alarm thresholds and preset protection strategies; the coupler monitoring strategy adjustment device is used to collect historical operating data of the current coupler and the logical partition, obtain adjustment parameters through self-learning analysis based on the historical operating data, and adjust the preset alarm thresholds and preset protection strategies based on the adjustment parameters; the coupler abnormality reporting device is used to provide the abnormal prompt data to the host server management and control platform.

[0034] Please refer to Figure 2 As shown, in actual work, the present application is provided with a coupler status monitoring device 40, a coupler monitoring parameter storage device 41, a coupler monitoring strategy adjustment device 42, a coupler control device 43, a coupler data processing device 44 and a coupler abnormality reporting device 45 on the CF to monitor cross-system, cross-application and cross-transaction online transaction data. When congestion occurs in the processing of such transaction data, load control and protection are immediately activated, and an early warning is issued to the host server management platform. A problem log is also provided to assist the large host server administrator to quickly locate the problem so that more mitigation measures can be taken to ensure system security. Specifically:

[0035] The coupler status monitoring device 40 is responsible for monitoring the coupler operating system status, including the CPU, MEM, and I / O of the coupler operating system. It also monitors cross-application request packet data waiting to be transferred in the transaction queue of the coupler data processing device 44 within the channel. This data includes data such as the transaction type number, the CICS operating status of the previous LPAR partition, the waiting time for the previous LPAR partition's CICS to process the transaction request and return the result, and whether the transaction was successful. If an abnormality occurs, such as exceeding the alarm threshold stored in the coupler monitoring parameter storage device, an alarm signal is immediately sent to the coupler control device 43. The CICS operating status includes the number of transactions processed per second and the operating status of various CICS service domains, including AP (Application), PG (Program Manager), SM (Storage Manager), DS (Dispatcher), DD (Direct Manager), US (User), KE (Kernel), XM (Transaction Manager), LD (Loader), XS (Security Manager), and ME (Message).

[0036] The coupler monitoring parameter storage device 41 is responsible for storing the coupler operation, monitoring and other parameter settings, and is responsible for storing the mainframe coupler operation monitoring and protection strategy.

[0037] The coupler monitoring policy adjustment device 42 is responsible for collecting historical data on the actual operation of the host server coupler system and the actual CICS operation on each LPAR partition. It regularly performs dynamic calculations and self-learning analysis based on the actual historical data of the server's actual operation to adjust parameter thresholds, and adjusts the parameters and protection policies stored in the coupler monitoring parameter storage device 41 based on the calculated thresholds. In actual applications, over time, the operating status of the coupler on the host server and the user activity, transaction frequency, and transaction type of the business system hosted by the middleware CICS on each LPAR partition exhibit certain cyclical patterns. These factors directly affect the number of CICS transactions processed by the application server, the CPU utilization of the coupler, the success rate of CICS data processing on the previous LPAR partition, the waiting time and TPS for the feedback result of the CICS processing transaction request on the previous LPAR partition, etc. Dynamic calculations and self-learning analysis based on the actual historical data of the server's actual operation adjust parameter thresholds and update protection policies, effectively avoiding the problem of traditional manually fixed protection policies and parameters that cannot effectively ensure the operation security of the host. In addition, the coupler monitoring policy adjustment device 42 also adjusts monitoring parameters based on the operating status of the coupler and monitoring data. Figure 4, I will not go into details here.

[0038] The coupler control device 43 monitors the data information according to the coupler status monitoring device 40, compares the parameters and protection strategy on the coupler monitoring parameter storage device 41, and if a peak abnormality occurs, starts the protection processing action, sets the coupler control device status to "abnormal", closes the CF data channel, and returns the closing reason and processing failure result to the client device 1 in the original path, starts the coupler abnormality reporting device 45 to feed back the abnormality reason and protection operation result to the host server management control platform 5, and registers the abnormal transaction processing register.

[0039] The coupler data processing device 44 is the daily data channel function of the mainframe coupler. It mainly converts the format of the data request of the previous initiating LPAR partition and arranges it in the data processing queue. It then forwards the data request packet to the CICS in the next LPAR partition for processing according to the queue order and the first-in-first-out principle.

[0040] The coupler abnormality reporting device 45 is responsible for feeding back the abnormality cause and protection operation result to the host server management control platform 5 and registering the abnormal transaction processing register.

[0041] Please refer to Figure 3 As shown, in one embodiment of the present application, the coupler monitoring strategy adjustment device includes a data acquisition module 31, a matrix generation module 32, an evaluation and calculation module 33 and an update module 34; the data acquisition module 31 is used to collect the historical operation data of the current coupler and the logical partition according to a preset period, and compress the historical operation data after dividing it into time intervals to generate reference data; the matrix generation module 32 is used to generate vector data from the reference data of the same time interval, and combine the vector data in time sequence to generate a historical performance data matrix; the evaluation and calculation module 33 is used to calculate and obtain historical health data based on a preset health assessment model and the historical performance data matrix; and, based on the historical health data, obtain the health status of multiple time points, and obtain adjustment parameters based on the health status and the alarm thresholds of the corresponding time points; the update module 34 is used to adjust the preset alarm threshold and the preset protection strategy according to the adjustment parameters.

[0042] For details, please refer to Figure 4 As shown, the complete process of the above-mentioned coupler monitoring strategy adjustment device self-learning and data analysis, and regular adjustment of the parameters on the coupler monitoring parameter storage device can be referred to the following steps:

[0043] Step S401: The coupler monitoring strategy adjustment device 41 regularly collects historical performance data such as the CPU utilization of the coupler in the previous monitoring cycle, the success rate of CICS data processing on the previous LPAR partition, the waiting time for the CICS to process the transaction request feedback result on the previous LPAR partition, and TPS from the coupler system, and divides each historical performance data into Groups, where T is the coupler system performance monitoring period. Then, each group of data is compressed as follows:

[0044]

[0045] Wherein, n represents the number of historical performance data contained in the group, v'j represents the value of the j-th performance data, i is a natural number greater than or equal to 0 and less than N, and vi represents the value obtained after compressing the i-th group of data.

[0046] Step S402: compress the historical performance data obtained at the same time point into a vector [t i ,c i ,m i ,d i ,tps i ], where t i represents the i-th time point, t i ,c i ,m i ,d i ,tps i The vectors are respectively the CPU utilization of the coupler at the i-th time point after compression, the success rate of CICS data processing on the previous LPAR partition, the waiting time for the CICS to process the transaction request feedback result on the previous LPAR partition, and the TPS. These vectors are then organized into a historical performance data matrix according to time series, as follows:

[0047]

[0048] Step S403: The coupler monitoring strategy adjustment device also uses the coupler health assessment model to calculate its historical health and obtain the latest health monitoring alarm threshold:

[0049] h i =w1*c i +w2*m i +w3*d i +w4*tps i ;

[0050] Among them, w1, w2, w3 and w4 represent the CPU utilization, the CICS data processing success rate on the previous LPAR partition, the waiting time used by the CICS on the previous LPAR partition to process the transaction request feedback result, and the TPS weight respectively.

[0051] Step S404: The coupler monitoring strategy adjustment device obtains the alarm threshold value at a specific predicted time point according to the above steps, and determines the average alarm threshold value according to the following formula to improve the accuracy and rationality of the alarm threshold value:

[0052] Z n′+1 is the alarm threshold at the n′+1th prediction time point, that is, the alarm threshold corresponding to the n′+1th predicted health level, k is the alarm threshold parameter, which is a constant less than 1; h j is the historical actual health at the jth prediction time point, and m is the preset number of means. For example, assuming m = 8, n′ = 8, h1 = 23, h2 = 25, h3 = 26, h4 = 24, h5 = 25, h6 = 23, h7 = 26, h8 = 25, and k = 0.6, then

[0053] Step S405: As time goes by, h j The coupler monitoring strategy adjustment device continuously adjusts and updates the alarm threshold value on the coupler monitoring parameter storage device.

[0054] The present application also provides a monitoring and protection method for the z / OS-based cross-application data protection system, the method comprising: a front-end server obtaining a transaction request type based on received transaction request data, analyzing the transaction request type to obtain corresponding logical partition information, providing the cross-application request data packet data to the corresponding logical partition for parsing and conversion based on the logical partition information to obtain transaction request parameters; providing the transaction request parameters to the corresponding other logical partitions via a coupler for processing, generating a processing result based on the feedback result, and feeding the processing result back to the client device that initiated the transaction request data via the front-end server; and using the coupler to monitor the operating status of the connected logical partitions and the current coupler, and generating and storing abnormal prompt data when the operating status is abnormal. The operating status of the coupler includes the operating parameters of the processor, memory, and hard disk of the coupler, and the operating status of the logical partition includes the transaction type, the operating status of the processing device on the previous logical partition, the transaction processing time of the processing device on the previous logical partition, and the transaction processing result.

[0055] For details, please refer to Figure 1 and Figure 5As shown, in actual work, the application process of the monitoring and protection method provided by this application in the cross-application data protection system based on the z / OS system can be executed as follows:

[0056] Step S501: the client device 1 initiates a transaction data request, where the request data includes requested transaction type data.

[0057] Step S502: the front-end server 2 converts the transaction data request data initiated by the client device 1 into a data format, determines the corresponding application system according to the requested transaction type, and sends the transaction request data to the corresponding LPAR (A) partition responsible for the transaction processing.

[0058] Step S503: The data receiving device within LPAR(A) receives the transaction request data, parses and converts the data, and then transfers it to the CICS transaction processing device for processing. Based on the transaction type, the CICS transaction processing device identifies the transaction as a cross-system, cross-application transaction request. After preliminary registration and processing, it issues a cross-application data processing request to Coupler A. The request data includes, but is not limited to, the target LPAR partition number, the target application name, the transaction type, and other transaction elements.

[0059] Step S504: The coupler data processing device determines whether the coupler control device is in normal state, and then proceeds to step S405; otherwise, proceeds to step S406.

[0060] Step S505: If normal, the coupler data processing device forwards the data request packet according to the target LPAR partition number in the request data. After the CICS on the target LPAR partition completes processing and returns the processed data, the processing result is returned to the client device 1 along the original path, and the transaction processing ends.

[0061] Step S506: The coupler data processing device rejects the transaction request and returns a transaction failure and error code to the client device 1. The coupler exception reporting device 45 reports the cause of the exception and the result of the protection operation to the host server management and control platform 5 and enters the abnormal transaction processing register. The transaction processing ends.

[0062] The beneficial technical effects of this application are: within the context of the ParallelSysplex technology currently used by IBM mainframe servers, a coupler status monitoring device is provided on the coupler to perform transaction-level data monitoring. When an abnormality occurs, peak protection can be implemented within the host server according to the protection strategy, avoiding the disadvantage of transient high pressure in the online transaction data processing across systems, applications, and transactions on the server, thereby ensuring the security and stability of the mainframe server system. When an abnormal CF is overloaded, the CF can proactively report the type of abnormal transaction, the number of CICS across systems, and the resource status of the CF system to the host server management and control platform through the coupler abnormality reporting device. This overcomes the current defect of IBM mainframe servers that can only periodically poll each CF for data. When an abnormality occurs, the administrator can quickly locate the problem, improve problem solving efficiency, and ensure the security and stability of the mainframe server system. A monitoring policy adjustment device is provided on the CF, which uses machine learning to automatically adjust monitoring parameters, ensuring that the CF can adaptively adjust parameters based on the characteristics of transaction request data from the host and different applications, making the parameters more reasonable and avoiding operator errors. When a congestion anomaly occurs, the host server management and control platform receives the alarm information from the coupler anomaly reporting device. It can manually or automatically check the resource status of the problem target LPAR partition and the operation status of CICS, and handle the problem (for example, manually stop the abnormal job processing, automatically call the Z / OS resource balancing device to add hardware resources to the LPAR partition with insufficient resources, etc.), quickly restore the CICS transaction processing capacity of the problem LPAR partition, and set the coupler control device status to "normal".

[0063] The present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method when executing the computer program.

[0064] The present application also provides a computer-readable storage medium, which stores a computer program for executing the above method.

[0065] The present application also provides a computer program product, comprising a computer program / instruction, which implements the steps of the above method when executed by a processor.

[0066] like Figure 6 As shown, the electronic device 600 may further include: a communication module 110, an input unit 120, an audio processing unit 130, a display 160, and a power supply 170. It is worth noting that the electronic device 600 does not necessarily have to include Figure 6 In addition, the electronic device 600 may also include all components shown in Figure 6 For components not shown, reference may be made to the prior art.

[0067] like Figure 6 As shown, the central processing unit 100 is sometimes also referred to as a controller or an operation control unit, and may include a microprocessor or other processor device and / or logic device. The central processing unit 100 receives inputs and controls the operations of various components of the electronic device 600 .

[0068] Memory 140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information and may also store programs that execute the relevant information. The CPU 100 may execute the programs stored in memory 140 to implement information storage or processing.

[0069] The input unit 120 provides input to the CPU 100. The input unit 120 may be, for example, a keypad or touch input device. The power supply 170 is used to provide power to the electronic device 600. The display 160 is used to display objects such as images and text. The display may be, for example, an LCD display, but is not limited thereto.

[0070] The memory 140 may be a solid-state memory, such as a read-only memory (ROM), a random access memory (RAM), or a SIM card. Alternatively, it may be a memory that retains information even when power is off, can be selectively erased, and is provided with more data. Examples of such memory are sometimes referred to as EPROMs. The memory 140 may also be some other type of device. The memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application / function storage unit 142 for storing application programs and function programs or processes for executing the operations of the electronic device 600 via the central processing unit 100.

[0071] The memory 140 may also include a data storage unit (data 143) for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit (driver 144) of the memory 140 may include various driver programs 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.).

[0072] The communication module 110 is a transmitter / receiver 110 that transmits and receives signals via an antenna 111. The communication module (transmitter / receiver) 110 is coupled to the central processor 100 to provide input signals and receive output signals, which may be the same as in a conventional mobile communication terminal.

[0073] Based on different communication technologies, multiple communication modules 110 may be provided in the same electronic device, such as a cellular network module, a Bluetooth module, and / or a wireless local area network module. The communication module (transmitter / receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132, thereby implementing common telecommunication functions. The audio processor 130 may include any suitable buffer, decoder, amplifier, etc. Furthermore, the audio processor 130 is also coupled to the central processing unit 100, enabling local recording via the microphone 132 and playback of stored audio via the speaker 131.

[0074] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

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

[0076] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work 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 The function specified in one or more boxes.

[0077] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device 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.

[0078] The specific embodiments described above further illustrate the purpose, technical solutions and beneficial effects of the present application. It should be understood that the above description is only a specific embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A cross-application data protection system based on z / OS system, characterized in that: The system includes a client device, a front-end server and a host server; The host server includes a host server management and control platform, a plurality of logical partitions and a plurality of couplers; The client device is connected to the application services arranged in the plurality of logical partitions through the front-end server; The host server management and control platform is respectively connected to a plurality of logical partitions and a plurality of couplers; The plurality of logical partitions independently run one or more application services, and provide received cross-application request data packets to corresponding other logical partitions through the plurality of couplers; The coupler monitors the operating status of the connected logical partition and the current coupler, generates abnormal prompt data when the operating status is abnormal, and provides the abnormal prompt data to the host server management and control platform.

2. The z / OS-based cross-application data protection system according to claim 1, characterized in that: The logical partitions in the same system complex among the plurality of logical partitions are connected to the same clock server to achieve clock synchronization.

3. The z / OS-based cross-application data protection system according to claim 1, characterized in that: The coupler comprises a coupler status monitoring device, a coupler control device and a coupler data processing device; The coupler state monitoring device is used to monitor the current operating state of the coupler and the cross-application request data packet data waiting to be transferred in the transaction queue of the coupler data processing device, generate monitoring data based on the operating state and the cross-application request data packet data, and generate an alarm signal based on a comparison result between the monitoring data and a preset alarm threshold and provide the alarm signal to the coupler control device; The coupler control device is used to compare the monitoring data with the preset protection strategy according to the alarm signal, shut down the coupler according to the comparison result and generate abnormal prompt data; The coupler data processing device is used to connect the logical partitions, convert the format of the cross-application request data packets and arrange them in the data processing queue, and forward the cross-application request data packets to the corresponding logical partitions for processing according to the queue order and the first-in-first-out principle.

4. The z / OS-based cross-application data protection system according to claim 3, characterized in that: The coupler further comprises a coupler monitoring parameter storage device, a coupler monitoring strategy adjustment device and a coupler abnormality reporting device; The coupler monitoring parameter storage device is used to store preset alarm thresholds and preset protection strategies; The coupler monitoring strategy adjustment device is used to collect historical operating data of the current coupler and the logical partition, obtain adjustment parameters through self-learning analysis based on the historical operating data, and adjust the preset alarm threshold and the preset protection strategy according to the adjustment parameters; The coupler abnormality reporting device is used to provide the abnormal prompt data to the host server management and control platform.

5. The z / OS-based cross-application data protection system according to claim 4, characterized in that: The coupler monitoring strategy adjustment device comprises a data acquisition module, a matrix generation module, an evaluation calculation module and an update module; The data acquisition module is used to collect historical operation data of the current coupler and the logical partition according to a preset period, and compress the historical operation data after dividing it into time intervals to generate reference data; The matrix generation module is used to generate vector data from reference data of the same time interval, and to combine the vector data in time sequence to generate a historical performance data matrix; The evaluation calculation module is used to calculate and obtain historical health data based on a preset health evaluation model and the historical performance data matrix; and to obtain health conditions at multiple time points based on the historical health data, and to obtain adjustment parameters based on the health conditions and the alarm thresholds at the corresponding time points; The updating module is used to adjust the preset alarm threshold and the preset protection strategy according to the adjustment parameter.

6. A monitoring and protection method for a z / OS-based cross-application data protection system according to any one of claims 1 to 5, characterized in that: The method comprises: The front-end server obtains a transaction request type based on the received transaction request data, obtains corresponding logical partition information based on the transaction request type, and provides the cross-application request data packet data to the corresponding logical partition for parsing and conversion processing based on the logical partition information to obtain transaction request parameters; Providing the transaction request parameters to the corresponding other logical partitions through the coupler for processing, generating a processing result based on the feedback result, and feeding the processing result back to the client device that initiated the transaction request data through the front-end server; Furthermore, the coupler is used to monitor the operation status of the connected logical partition and the current coupler, and when the operation status is abnormal, abnormal prompt data is generated and stored.

7. The monitoring and protection method according to claim 6, characterized in that: The operating status of the coupler includes the operating parameters of the coupler's processor, memory and hard disk, and the operating status of the logical partition includes the transaction type, the operating status of the processing device on the previous logical partition, the transaction processing time of the previous logical partition processing device, and the transaction processing result.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 6 to 7 is implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program for causing a computer to execute the method according to claim 6 or 7.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to claim 6 or 7 are implemented.

Images