Method for automatically monitoring and complementing programs

Abstract

The invention discloses a method for automatically monitoring and complementing a program. The method comprises the following steps of: defining an input variable and initializing the variable; judging whether the time file of the root path exists or not, if yes, reading the file as starting time, and if not, creating a new time file, and storing the input starting time; obtaining a current operation account period, and calculating whether monitoring is executed to the end time or not according to an ascending order or a descending order; sending a program starting short message and entering batch circulation to obtain a final account period after the operation interval, monitoring and comparing each batch of final account period and ending time, and judging whether ending is needed after script batch data execution is finished; running the data development script, if the running is successful, calculating the next execution account period and inputting the next execution account period into the root path time file, so as to save the start execution account period in the batch, and when the program in the batch is accidentally terminated, reading the root path time file to obtain the breakpoint account period to continue running, so that the effect of intelligent number complement at the breakpoint is realized; if the number of continuous failures exceeds the limit, sending an alarm short message, and ending the script; and calculating actual ending time according to the ascending order or the descending order, and sending an ending short message. In the data development process, the multi-account-period data is operated in batches, and automatic complement and short message alarm reminding are supported at the breakpoint.

Description

Technical Field

[0001] The invention belongs to the technical field of data monitoring, and in particular relates to a method for automatic program monitoring and number complementation. Background Art

[0002] When running a large amount of data, and the data of different account periods are dependent on each other and cannot be run together in multiple account periods, if the program stops suddenly, you need to manually find the stop date and determine the next supplement date based on the running date sequence. This supplement method is time-consuming and labor-intensive, especially when it stops multiple times in the middle of a large number of account periods. For example, when supplementing data from January to March, the data from January 5 to 10, February 15 to 20, and March 22 to 26 all stop running unexpectedly. Then you need to manually find the stop date three times and reconfigure the running date, which can easily affect the progress of back-end development and the stability of the back-end program from the data perspective.

[0003] Existing monitoring and complement technologies mainly query results by configuring monitoring table parameters, perform quality statistics on target tasks, and generate notification and alarm information corresponding to preset monitoring tables. Alternatively, source data to be processed is obtained from multiple data sources, preprocessed, and the source data and corresponding standard tables are obtained in turn. Job cycles and scheduling parameters are configured, and multiple data models are created based on standard tables. Each data model corresponds to a job with a job type and dependency relationships.

[0004] Some studies monitor based on log files, detect whether there are new transaction records in the log files, read the SQL instructions included in each transaction record from the cache file, and synchronize the SQL instructions included in each transaction record to the target end. A small number of studies are based on incremental monitoring in the data center. Some studies focus on shell scripts, which are about the command recommendation method of shell development tools, or focus on extracting data table names, and reduce the tedious work of manually searching for each script-related data table through improved data table extraction methods. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a method for automatic program monitoring and number supplement in view of the deficiencies of the above-mentioned prior art. In the process of data development, multi-account period data are run in batches, and automatic number supplement and SMS alarm reminders are supported at breakpoints.

[0006] In order to achieve the above technical objectives, the technical solution adopted by the present invention is:

[0007] A method for automatically monitoring and complementing numbers through a program, comprising the following steps:

[0008] Define input variables and initialize the variables, the input variables include start time, end time, time file, ascending or descending order, interval time for each batch, and number of failed retries;

[0009] Determine whether the time file of the root path exists. If it exists, read the time file of the root path as the start time. If it does not exist, create a new time file and save the input start time. In the subsequent steps, the root path time file will be automatically updated to the start account period of each batch to ensure that when the program is stuck and a breakpoint occurs, the execution account period of the breakpoint is automatically saved and read, and the number is supplemented based on the breakpoint account period;

[0010] Get the current running account period through the time file, and determine whether the current execution has reached the end time according to the ascending or descending order of the running account period. If so, end the program, otherwise execute the next step to monitor the account period outside the while batch loop;

[0011] Send the program to start SMS and enter the batch cycle. Use the current running time file account period plus the interval time of each batch to get the final account period after the running interval. Compare the final account period and end time of each batch according to the ascending or descending order of the running account period, so as to monitor the account period and determine whether the script batch data needs to be ended after execution.

[0012] Run the data development script to determine whether the script runs successfully. If the current batch runs successfully, the next batch of start account periods will be calculated based on the ascending or descending order of the running account periods, and the next batch of start account periods will be entered into the root path time file. If a breakpoint occurs within the batch, the start account period of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint has been recorded. The program can read the root path time file and obtain the breakpoint by itself, and automatically make up the number from the breakpoint. If the run fails and the number of consecutive failures reaches the failure retry limit, an alarm SMS will be sent and the script ends.

[0013] The actual end time is calculated based on the ascending or descending order of the running account period, and an end SMS is sent.

[0014] To optimize the above technical solutions, the specific measures taken also include:

[0015] The above time file is used to store the account period to be executed, so as to facilitate reading and comparing the file time. The start account period of each batch will be automatically updated to the root path time file, so that when the program is restarted, the breakpoint account period will be automatically obtained from the time file and supplemented; when the program account period is in days, the time file stores the date. If the program account period is in months, the time file stores the month. Similarly, the content stored in the time file is not limited to days, but can also store time units such as minutes, hours, months, quarters, and years. The units of the subsequent start time and end time are also set independently according to the program time unit, not limited to the daily granularity.

[0016] The ascending or descending order is the execution order of the running account period.

[0017] The interval time of each batch is the interval number of each batch of operation account periods, which is the number of each batch of operation account periods minus 1.

[0018] The above initialization variables include initialization input variables and initialization script root path, script file name, SMS jar package location, and SMS recipient.

[0019] The above procedure determines whether the current execution has reached the end time according to the ascending or descending order of the running account period. If so, the program ends. Otherwise, the next step is executed to monitor the account period outside the while batch loop, including:

[0020] When the execution order of the running account period is in descending order, if the current running account period is less than the end time, it means that the current running account period has exceeded the end time, that is, the execution has reached the end time, and the program needs to be terminated;

[0021] When the execution order of the running account period is in ascending order, if the current running account period is greater than the end time, it means that the current running account period has exceeded the end time, that is, it is executed to the end time and the program needs to be ended.

[0022] By comparing the account period and end time of the root path time file, the execution account period can be monitored to ensure that the current execution account period will not automatically exceed the end time, and the start SMS will be sent only when the current running account period is before the end time.

[0023] The above compares the final account period and end time of each batch according to the ascending or descending order of the running account period, so as to monitor the account period and determine whether the script batch data needs to be ended after execution, including:

[0024] If the execution order of the running account period is in descending order, the program will terminate after the corresponding batch data is executed if the final account period is less than or equal to the end time.

[0025] If the execution order of the running account period is in ascending order, then the program will terminate after the corresponding batch data is executed if the final account period is greater than the end time;

[0026] By comparing the final account period and the end time of the batch, the execution account period can be monitored to ensure that the current execution account period will not automatically exceed the end time.

[0027] The above method calculates the next batch of billing periods based on the ascending or descending order of the running billing periods, and inputs the next batch of billing periods into the root path time file, including:

[0028] When the execution order of the running account period is in descending order, the final account period of each batch minus 1 is the next starting account period;

[0029] When the execution order of the running account period is in ascending order, the final account period of each batch plus 1 is the next starting account period;

[0030] Before the end of this batch, the calculated start period of the next batch is input into the root path time file. If a breakpoint occurs within the batch, the start period of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint has been recorded. The program can read the root path time file by itself to obtain the breakpoint, and automatically make up the number from the breakpoint.

[0031] The above-mentioned consecutive failure times are initially assigned a value of 0. When the program fails to execute, the consecutive failure times are increased by 1 each time it fails. If the execution is successful, the consecutive failure times are refreshed to 0 and the consecutive failure times are accumulated again.

[0032] The above calculation of the actual end time based on the ascending or descending order of the running account period includes:

[0033] When the execution order of the running account period is in descending order, the final account period of each batch minus 1 is the actual end time;

[0034] When the execution order of the running account period is in ascending order, the final account period of each batch plus 1 is the actual end time.

[0035] The present invention has the following beneficial effects:

[0036] The variable parameters configured in the present invention include not only conventional start time, end time, etc., but also parameters such as time file, ascending or descending order, and interval time of each batch, which are convenient for multiple batch operations.

[0037] The present invention does not monitor based on log files, but compares the final account period and end time of each batch according to the ascending or descending order of the execution account period to achieve the purpose of monitoring data. While monitoring, if the program stops unexpectedly, the present invention can also automatically identify the stopped account period and intelligently make up the number at the breakpoint. When the program stops unexpectedly due to machine damage or network collapse, the next time the program is restarted, the running account period stored in the time file can be directly read, thereby realizing automatic making up of the account period at the last breakpoint.

[0038] The present invention can automatically set the interval time of each batch of running account periods, that is, the step size of each batch, so as to speed up the running speed. When the data to be run contains a large number of account periods, if only one account period is run in each batch, the speed of script running will be reduced. If each batch supports running multiple account periods, the efficiency of script running will be greatly improved.

[0039] The present invention can configure the ascending and descending order of the account period autonomously, thereby automatically determining the order of the next execution account period, and supports the complement of the account period in increasing or decreasing order. If the script only supports the account period in a single ascending order, when the descending order is required, an additional descending script can only be written, which increases the redundancy of the code. After supporting both the ascending and descending order of the account period, not only can the next execution account period be automatically determined, but also the account period does not need to be manually input from the outside.

[0040] The present invention compares the final account period and end time of each batch in ascending or descending order to determine whether the program needs to be terminated. Since the script is run in batches, before each batch of data starts running, it is first compared whether the final account period of each batch exceeds the end time. If it does not exceed, the batch of data is run, and if it exceeds, the operation is stopped. Since the order of the account period is not necessarily ascending or descending, the final account period and end time will be compared in ascending or descending order respectively.

[0041] The present invention sets up a separate time file, and directly stores the account period to be executed into the time file. Since scripts often involve time calculation and comparison, such as calculating the next execution account period, or comparing the final account period and end time of each batch, this method will set up a separate dedicated time file to store the account period to be run, which is convenient for program reading. When the program account period is in days, the time file stores the date. If the program account period is in months, then the time file stores the month. By analogy, the content stored in the time file is not limited to days, and time units such as minutes, hours, months, quarters, and years can also be stored. The units of the following start time and end time are also set independently according to the program time unit, and are not limited to daily granularity. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 The present invention is a flowchart of a method for automatic program monitoring and number complementation. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0044] Although the steps in the present invention are arranged with numbers, they are not used to limit the order of the steps. Unless the order of the steps is clearly stated or the execution of a certain step requires other steps as a basis, the relative order of the steps can be adjusted. It is understood that the term "and / or" used in this article involves and covers any and all possible combinations of one or more of the associated listed items.

[0045] like Figure 1 As shown, a method for automatic program monitoring and complementing of the present invention comprises the following steps:

[0046] S1. Define input variables and initialize them, including "start time", "end time", "time file", "ascending or descending", "interval between each batch", "number of failed retries", etc.

[0047] S2. Determine whether the root path time file exists. If it does, read the file as the start time. If it does not exist, create a new file and save the input start time. In the subsequent steps, the root path time file will be automatically updated to the start account period of each batch, so as to ensure that when the program is stuck and a breakpoint occurs, the execution account period of the breakpoint is automatically saved and read, and the number is supplemented based on the breakpoint account period.

[0048] S3. Obtain the current running account period through the time file, and determine whether to execute to the end time based on ascending or descending order, so as to monitor the account period outside the while batch loop.

[0049] S4. Send the program to start SMS and enter the batch cycle. Use the current running time file account period plus the interval time of each batch to get the final account period after the running interval. Compare the final account period and end time of each batch in ascending or descending order, limit the final account period range so that it does not exceed the input end time, thereby monitoring the account period and determining whether the script needs to end after the execution of the batch data is completed.

[0050] S5. Run the data development script to determine whether the script runs successfully. If it runs successfully, calculate the start period of the next batch according to ascending or descending order, and enter the start period of the next batch into the root path time file. If a breakpoint occurs within a batch, the start period of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint is recorded. The program can read the root path time file by itself to obtain the breakpoint, and automatically make up the number from the breakpoint.

[0051] When the number of consecutive failures reaches the limit, an alarm SMS is sent and the script ends.

[0052] S7. Calculate the actual end time according to the ascending or descending order of the execution account period, and send an end SMS.

[0053] In the embodiment, S1 defines input variables and initializes variables, mainly including "start time", "end time", "time file", "ascending or descending order", "interval time for each batch", "number of failed retries", etc.

[0054] Define the input variables required for script running, including start time, end time, time file, ascending or descending order, interval time for each batch, number of failed retries, and end time of script running on the day.

[0055] The "time file" variable is used to store the account period to be executed, such as 20240101. This makes it easier to read and compare the start execution period of the file. The start period of each batch will be automatically updated to the root path time file, which is conducive to automatically obtaining the breakpoint period from the time file and making up the number when the program is restarted.

[0056] The variable "ascending or descending" represents the execution order of the running account period. For example, if it runs in the order of 20240101, 20240102, and 20240103, it represents ascending order. If it runs in the order of 20240131, 20240130, and 20240129, it represents descending order.

[0057] The "interval time between each batch" represents the number of intervals between each batch of running accounts, that is, the number of running accounts per batch minus 1. Assume that the data for 10 days from 20240101 to 20240110 is to be run. If each batch runs for 2 days, the first batch is from 1 to 2, and the second batch is from 3 to 4, then the "interval time between each batch" is 1. If each batch runs for 5 days, the first batch is from 1 to 5, and the second batch is from 6 to 10, then the "interval time between each batch" is 4.

[0058] If a task fails for a specified number of consecutive times, the script will stop running and send a text message notification.

[0059] In addition to the above input variables, the initialization variables also include the initialization script root path (path), script file name (file_name), SMS jar package location (send_msg_jar_path), and SMS recipient (link_man).

[0060] In the embodiment, S2 determines whether the root path time file exists. If it exists, the file is read as the start time. If it does not exist, a new file is created to save the input start time. In the subsequent steps, the root path time file is automatically updated to the start account period of each batch, so as to ensure that when the program is stuck and a breakpoint occurs, the execution account period of the breakpoint is automatically saved and read, and the number is supplemented based on the breakpoint account period.

[0061] Determine whether the time file of the root path exists. If it does, read the data from the time file of the root path as the start time. If the file does not exist in the root path, create a new file to save the input start time.

[0062] The sample code is as follows:

[0063]

[0064] In the embodiment, S3 obtains the current running account period through the time file, and determines whether to execute to the end time according to ascending or descending order, so as to monitor the account period outside the while batch loop.

[0065] Get the current running account period according to the time file in the root path. Get the execution order of the running account period according to the "ascending or descending" variable.

[0066] When the running order is descending, if the current running account period is less than the end time, it means that the current running account period has exceeded the end time and the program needs to be ended; when the running order is ascending, if the current running account period is greater than the end time, it means that the current running account period has exceeded the end time and the program also needs to be ended.

[0067] By comparing the account period and end time of the root path time file, the execution account period can be monitored to ensure that the current execution account period will not automatically exceed the end time, and the start SMS is sent only when the current running account period is before the end time.

[0068] The account period comparison in this step is a comparison outside the while batch loop. If the end time is exceeded, the start SMS for the next step will not be sent.

[0069] The sample code is as follows:

[0070]

[0071] In the embodiment, S4 sends a program start SMS and enters a batch cycle, uses the current running time file account period plus each batch interval time to obtain the final account period after the running interval, compares the final account period and end time of each batch in ascending or descending order, limits the final account period range so that it does not exceed the input end time, thereby monitoring the account period and determining whether the script needs to end after the execution of the batch of data is completed.

[0072] Since the interval time of each batch is not fixed, it is necessary to add the current running file account period to the interval time of each batch to know the last account period of the batch currently running.

[0073] If the execution order is descending, the program will terminate after the batch of data is executed if the final account period is less than or equal to the end time. If the execution order is ascending, the program will terminate after the batch of data is executed if the final account period is greater than the end time.

[0074] By comparing the final account period and the end time of the batch, the execution account period can be monitored to ensure that the current execution account period will not automatically exceed the end time.

[0075] The sample code is as follows:

[0076]

[0077] In the embodiment, S5 runs the data development script to determine whether the script runs successfully. If the script runs successfully, the next batch of accounts are calculated according to ascending or descending order, and the next batch of accounts are input into the root path time file. If a breakpoint occurs in a batch, the start account of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint is recorded. The program can read the root path time file by itself to obtain the breakpoint, and automatically make up the number from the breakpoint.

[0078] Enter the starting and final billing periods for the batch and run the data development script.

[0079] #Run the data development script

[0080] sh${path} / ${file_name}.sh${day_id1}${day_id2}

[0081] The time file has only one account period, which represents the account period to be executed. When the batch runs successfully, the next execution account period will be automatically calculated according to the ascending or descending order, and the next execution account period will be stored in the time file. When the execution account period is in descending order, the final account period of each batch is reduced by 1 to be the next execution account period; when the execution account period is in ascending order, the final account period of each batch is increased by 1 to be the next execution account period.

[0082] For example, if the current time file content is 20240101, the interval time of each batch is 1, and the execution account period is in ascending order, the batch runs the data of 20240101 and 20240102. When the batch runs successfully, the next execution account period is automatically calculated as 20240103, and the content of the time file is automatically updated to 20240103.

[0083] The program will transfer the start period of each batch to the root path time file. If a batch of programs is interrupted or stuck, the program ends and a breakpoint occurs. However, the root path time file has recorded the start period of the next batch before the end of the previous batch, that is, the program breakpoint. We only need to print the root path time file to know the breakpoint period of the program. The start node of the program is obtained by reading the root path time file, so when the program breaks, the program will automatically record the breakpoint period, update the root path time file, obtain the complement start time, and run again from the breakpoint.

[0084] The sample code is as follows:

[0085]

[0086] In the embodiment, when the number of consecutive failures reaches a limit, an alarm text message is sent and the program ends.

[0087] The number of consecutive failures is first assigned to 0. When the program fails to execute, the number of failures increases by 1 each time it fails. If the execution is successful, the number of failures is refreshed to 0 and the number of failures is accumulated again. If the number of failures reaches the limit threshold, an alarm SMS is sent and the program ends.

[0088] In the embodiment, S6 calculates the actual end time according to the ascending or descending order of the execution account period and sends an end SMS.

[0089] When the execution period is in descending order, the final period of each batch is reduced by 1 to obtain the actual end time; when the execution period is in ascending order, the final period of each batch is increased by 1 to obtain the actual end time. The actual end time is printed at the end.

[0090] The sample code is as follows:

[0091]

[0092] The specific embodiments are as follows:

[0093]

[0094]

[0095]

[0096]

[0097]

[0098]

[0099]

[0100]

[0101] The definitions of the terms in the above text are as follows:

[0102] Root path: usually refers to the top level or root directory of a file system, indicating the starting point of all files and directories in a computer system.

[0103] Account period: The account period in this method refers to the time account period required for the script to run, such as 20240101, 20240102.

[0104] Batch cycle: The batch cycle in this method refers to a while cycle, and the data is run in batches when the monitoring conditions are met. For those skilled in the art, it is obvious that the present invention is not limited to the details of the above exemplary embodiments, and the present invention can be implemented in other specific forms without departing from the spirit or basic characteristics of the present invention. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive. The scope of the present invention is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any figure mark in the claims should not be regarded as limiting the claims involved.

[0105] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A method for automatic program monitoring and complementing, characterized in that: The following steps are involved: Define input variables and initialize the variables, the input variables include start time, end time, time file, ascending or descending order, interval time for each batch, and number of failed retries; Determine whether the time file of the root path exists. If it exists, read the time file of the root path as the start time. If it does not exist, create a new time file and save the input start time. The subsequent root path time file is automatically updated to the start account period of each batch to ensure that when the program is stuck and a breakpoint occurs, the execution account period of the breakpoint is automatically saved and read, and the number is supplemented based on the breakpoint account period; Get the current running account period through the time file, and determine whether the current execution has reached the end time according to the ascending or descending order of the running account period. If so, end the program, otherwise execute the next step to monitor the account period outside the while batch loop; Send the program to start SMS and enter the batch cycle. Use the account period of the current running time file plus the interval time of each batch to get the final account period after the running interval. Compare the final account period and end time of each batch according to the ascending or descending order of the running account period, so as to monitor the account period and determine whether the script batch data needs to be ended after execution. Run the data development script to determine whether the script runs successfully. If the current batch runs successfully, the next batch of start account periods will be calculated based on the ascending or descending order of the running account periods, and the next batch of start account periods will be entered into the root path time file. If a breakpoint occurs within the batch, the start account period of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint has been recorded. The program can read the root path time file and obtain the breakpoint by itself, and automatically make up the number from the breakpoint. If the run fails and the number of consecutive failures reaches the failure retry limit, an alarm SMS will be sent and the script ends. The actual end time is calculated based on the ascending or descending order of the running account period, and an end SMS is sent.

2. A method for automatic program monitoring and complementing according to claim 1, characterized in that: The time file is used to store the bill period to be executed, so as to facilitate reading and comparing the time of the file. The starting bill period of each batch is automatically updated to the root path time file, so that when the program is restarted, the breakpoint bill period is automatically obtained from the time file and the number is supplemented; the time file is stored according to the time granularity of the program bill period, and the time granularity includes time units such as minute level, hour level, day level, month level, quarter level, year level, etc.; The ascending or descending order is the execution order of the running account period. The interval time of each batch is the interval number of each batch of operation account periods, which is the number of each batch of operation account periods minus 1.

3. A method for automatic program monitoring and complementation according to claim 1, characterized in that: The initialization variables include initialization input variables and initialization script root path, script file name, SMS jar package location, and SMS recipient.

4. A method for automatic program monitoring and complementation according to claim 1, characterized in that: According to the ascending or descending order of the running account period, it is determined whether the current execution has reached the end time. If so, the program ends, otherwise the next step is executed to monitor the account period outside the while batch loop, including: When the execution order of the running account period is in descending order, if the current running account period is less than the end time, it means that the current running account period has exceeded the end time, that is, the execution has reached the end time, and the program needs to be terminated; When the execution order of the running account period is in ascending order, if the current running account period is greater than the end time, it means that the current running account period has exceeded the end time, that is, the execution has reached the end time, and the program needs to be terminated; By comparing the account period and end time of the root path time file, the execution account period can be monitored to ensure that the current execution account period will not exceed the end time automatically, and the start SMS will be sent only when the current running account period is before the end time.

5. A method for automatic program monitoring and complementation according to claim 1, characterized in that: The final account period and end time of each batch are compared according to the ascending or descending order of the running account period, so as to monitor the account period and determine whether the script batch data needs to be ended after execution, including: If the execution order of the running account period is descending, the program will terminate after the corresponding batch data is executed if the final account period is less than or equal to the end time. If the execution order of the running account period is in ascending order, then the program will terminate after the corresponding batch data is executed if the final account period is greater than the end time; By comparing the final account period and the end time of the batch, the execution account period can be monitored to ensure that the current execution account period will not automatically exceed the end time.

6. A method for automatic program monitoring and complementing according to claim 1, characterized in that: The calculation of the next batch of start execution account period according to the ascending or descending order of the running account period, and inputting the next batch of start execution account period into the root path time file, includes: When the execution order of the running account period is in descending order, the final account period of each batch minus 1 is the next starting account period; When the execution order of the running account period is in ascending order, the final account period of each batch plus 1 is the next starting account period; Before the end of this batch, the calculated start period of the next batch is input into the root path time file. If a breakpoint occurs within the batch, the start period of the batch has been updated to the root path time file before the end of the previous batch, and the breakpoint has been recorded. The program can read the root path time file by itself to obtain the breakpoint, and automatically make up the number from the breakpoint.

7. A method for automatic program monitoring and complementation according to claim 1, characterized in that: The number of consecutive failures is initially assigned a value of 0. When the program fails to execute, the number of consecutive failures increases by 1 each time it fails. If the execution is successful, the number of consecutive failures is refreshed to 0 and the number of consecutive failures is accumulated again.

8. A method for automatic program monitoring and complementing according to claim 1, characterized in that: The actual end time is calculated based on the ascending or descending order of the running account period, including: When the execution order of the running account period is in descending order, the final account period of each batch minus 1 is the actual end time; When the execution order of the running account period is in ascending order, the final account period of each batch plus 1 is the actual end time.

Images