CN116467117A

CN116467117A - Host restarting flow management method, device, computer equipment and storage medium

Info

Publication number: CN116467117A
Application number: CN202310390358.9A
Authority: CN
Inventors: 吴哲琼
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-04-12
Filing date: 2023-04-12
Publication date: 2023-07-21

Abstract

The application relates to a host restarting process management method, a device, computer equipment and a storage medium, which can be used in the financial field. The method comprises the following steps: the method comprises the steps that a platform end receives a host restarting instruction, a preset restarting operation flow corresponding to a restarting task identifier is obtained according to the restarting task identifier carried in the host restarting instruction, and finally the host end is controlled to restart according to the preset restarting operation flow based on a target restarting task corresponding to the restarting task identifier, so that a restarting result of the target restarting task is generated, wherein the preset restarting operation flow comprises an operation flow before restarting, an operation flow in restarting and an operation flow after restarting. By adopting the method, the efficiency of executing the IPL flow can be improved.

Description

Host restarting flow management method, device, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for managing a host restart procedure, a computer device, and a storage medium.

Background

With the continuous development of computer technology, large-scale hosts are increasingly used in various fields. A mainframe generally refers to a large, powerful computer that can perform complex computing tasks and data processing tasks. For example, large hosts typically run a core system or core database that performs complex computing tasks and data processing tasks.

When repairing system bugs and upgrading a system of a large-scale host, the system bugs and upgrading the system are required to be realized by adopting IPL (System program Loading, initialize Program Load) operation. In the traditional method, IPL full-flow operation and subsequent system environment inspection are performed on the large-scale host computer by adopting a manual mode, so as to repair system loopholes and upgrade the system of the large-scale host computer.

However, because the flow of the IPL operation is very complex and tedious, the manual mode is adopted to execute the full-flow IPL operation on the large-scale host, and the efficiency is low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, and a storage medium for managing a host restart flow, which can improve the efficiency of IPL flow operations.

In a first aspect, the present application provides a method for managing a host restart procedure. The method comprises the following steps:

receiving a host restarting instruction;

acquiring a preset restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the preset restarting operation flow comprises an operation flow before restarting, an operation flow in restarting and an operation flow after restarting;

the control host terminal restarts based on the target restarting task according to the preset restarting operation flow, and a restarting result of the target restarting task is generated; the target restart task corresponds to the restart task identifier.

In one embodiment, if the host is in a pre-restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

acquiring a pre-restart operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction; the pre-restart operation flow includes a first initialization operation flow and a first environment detection operation flow corresponding to the restart task identifier.

In one embodiment, the method for generating a restart result of the target restart task includes:

the control host side initializes according to the first initialization operation flow corresponding to the restarting task identifier, and generates a first initialization result;

receiving the first initialization result sent by the host;

and carrying out environment detection on the host end according to the first environment detection operation flow corresponding to the restarting task identifier according to the first initialization result, and generating a first environment detection result of the host end.

In one embodiment, if the host side includes a plurality of subsystems, the generating a first environment detection result of the host side according to the first initialization result and the first environment detection operation flow corresponding to the restart task identifier, includes:

According to the first initialization result, according to the first environment detection operation flow corresponding to the restarting task identifier, an environment data acquisition instruction is sent to each subsystem of the host side; the environment data acquisition instruction is used for controlling the host side to acquire the environment data of the subsystem based on the acquisition script corresponding to the subsystem aiming at each subsystem;

receiving environment data of each subsystem sent by the host end;

and analyzing the environment data of each subsystem to generate a first environment check result of the host side.

In one embodiment, if the host is in a restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow in restarting is the operation flow adopting the loading mode of the system program.

And the control host executes the target restarting task according to the restarting operation flow and generates a task restarting result of the target restarting task.

In one embodiment, if the host is in a post-restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow after restarting comprises a second initialization operation flow and a second environment detection operation flow which correspond to the restarting task identifier.

the control host side initializes according to the second initialization operation flow corresponding to the restarting task identifier, and generates a second initialization result;

receiving a second initialization result sent by the host end;

and carrying out environment detection on the host end according to the second initialization result and the second environment detection operation flow corresponding to the restarting task identifier, and generating a second environment detection result of the host end.

In one embodiment, the method further comprises:

comparing the first environment detection result of the host end with the second environment detection result of the host end to generate a comparison result;

determining whether the environment of the host end after executing the target restarting task is abnormal or not according to the comparison result;

if the environment of the host end after executing the target restarting task is abnormal, an abnormal result is obtained from the comparison result, and the abnormal result is displayed on a display interface.

In one embodiment, the method further comprises:

generating a log file according to a restarting result of the target restarting task;

and receiving a log file sending instruction, and sending the log file to a target address according to the log file sending instruction.

In a second aspect, the present application further provides a device for managing a restart flow of a host. The device comprises:

the receiving module is used for receiving a host restarting instruction;

the acquisition module is used for acquiring a preset restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the preset restarting operation flow comprises an operation flow before restarting, an operation flow in restarting and an operation flow after restarting;

The first generation module is used for controlling the host side to restart based on a target restart task according to the preset restart operation flow and generating a restart result of the target restart task; the target restart task corresponds to the restart task identifier.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the above method when the processor executes the computer program.

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the above method.

In a fifth aspect, the present application also provides a computer program product. The computer program product comprising a computer program which, when executed by a processor, implements the steps of the above method.

According to the host restarting process management method, the device, the computer equipment and the storage medium, firstly, the platform end receives a host restarting instruction, then obtains a preset restarting operation process corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction, and finally controls the host end to restart based on a target restarting task corresponding to the restarting task identifier according to the preset restarting operation process to generate a restarting result of the target restarting task, wherein the preset restarting operation process comprises a pre-restarting operation process, a restarting operation process and a restarting operation process. In the traditional technology, the IPL full-flow operation is performed on the large-scale host computer by adopting a manual mode, so that system bug repairing and system upgrading are realized on the large-scale host computer, and the efficiency is lower because the IPL full-flow operation is performed on the large-scale host computer by adopting the manual mode because the flow of the IPL operation is very complex and tedious. In the embodiment of the application, the platform end can restart based on the target restart task according to the preset restart operation flow, so that each operation of the IPL of the large-scale host is not required to be manually executed and recorded, and the efficiency of executing the IPL flow is improved.

Drawings

FIG. 1 is an application environment diagram of a host restart flow management method in an embodiment of the present application;

FIG. 2 is a flowchart of a method for managing a host reboot process according to an embodiment of the present disclosure;

FIG. 3 is a schematic page diagram of a task management module according to an embodiment of the present application;

fig. 4 is a schematic page diagram of a process management module according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for generating a restart result according to an embodiment of the present application;

fig. 6 is a flowchart of a first environmental detection result generation method provided in an embodiment of the present application;

FIG. 7 is a second flowchart of a method for generating a restart result according to an embodiment of the present disclosure;

FIG. 8 is a second flowchart of a host reboot process management method according to the embodiment of the present application;

FIG. 9 is a third flow chart of a method for managing a host reboot flow according to the embodiment of the present application;

FIG. 10 is a schematic page diagram of a problem recording module according to an embodiment of the present disclosure;

FIG. 11 is a schematic page view of an emergency tool module according to an embodiment of the present disclosure;

FIG. 12 is a flowchart of a method for managing a host reboot process according to an embodiment of the present disclosure;

Fig. 13 is a block diagram of a host reboot process management device according to an embodiment of the present application;

fig. 14 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

The host restarting flow management method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the host end 101 communicates with the platform end 102 through a network. The data storage system may store data that needs to be processed by the platform side 102. The data storage system may be integrated on the platform end 102 or may be located on a cloud or other network server. After the platform end 102 receives the host restarting instruction, the host end 102 is controlled to restart based on the target restarting task according to the preset restarting operation flow corresponding to the restarting task identifier, and a restarting result of the target restarting task is generated. The platform 102 may be implemented as a stand-alone platform or as a cluster of multiple platform ends. The host 101 may be a large-sized host using a dedicated processor instruction set, an operating system, and application software, or may be a small-sized computer having a relatively small software or hardware system scale.

In one embodiment, fig. 2 is one of the flow diagrams of a host restart flow management method according to the embodiments of the present application, and as shown in fig. 2, a host restart flow management method is provided, and the method is applied to the platform end in fig. 1 for illustration, and includes the following steps:

s201, receiving a host restarting instruction.

The host restarting instruction is an instruction for instructing the host to restart. The host restart instruction may be: the user clicks a corresponding restarting control on the platform end system, and the platform end receives a host restarting instruction generated after the user clicks the restarting control. The host restart instruction may also be: when the system bug and the system upgrade need to be repaired in the host end, the host end sends a host restarting instruction to the platform end, so that the platform end can receive the host restarting instruction sent by the host end. Of course, the present application is not limited thereto.

In the embodiment of the application, the platform end can receive a host restarting instruction.

S202, acquiring a preset restarting operation flow corresponding to a restarting task identifier according to the restarting task identifier carried in a host restarting instruction; the preset restarting operation flow comprises a pre-restarting operation flow, a restarting operation flow and a restarting operation flow.

Here, the restart task identifier is carried in the host restart instruction. The restart task identifier may include an ID of the restart task, a name of the restart task, and the like; the restart task may be used to validate functionality to fix system vulnerabilities, system upgrades, etc., for example, the restart task may be a database patch validation task. The preset restart operation flow may include a pre-restart operation flow, a mid-restart operation flow, and a post-restart operation flow.

In this embodiment of the present application, each restart task identifier may have a corresponding preset restart operation flow, and the platform end may obtain, according to the restart task identifier carried in the host restart instruction, the preset restart operation flow corresponding to the restart task identifier.

For example, the restart task is identified as an ID of the database patch effective task, and the preset restart operation flow corresponding to the ID of the database patch effective task includes an operation flow a before restart, an operation flow a during restart, and an operation flow a after restart, and then the platform end may obtain the preset restart operation flow, an operation flow a before restart, an operation flow a during restart, and an operation flow a after restart according to the ID of the database patch effective task. For another example, the restart task is identified as an ID of the host middleware task, and the preset restart operation flow corresponding to the ID of the host middleware task includes a pre-restart operation flow a, an in-restart operation flow a and a post-restart operation flow a, so that the platform end may obtain the preset restart operation flow, the pre-restart operation flow a, the in-restart operation flow a and the post-restart operation flow a according to the ID of the host middleware task.

Fig. 3 is a schematic page diagram of a task management module according to an embodiment of the present application. Referring to fig. 3, an IPL item may identify a restart task, an ID may represent a restart task identifier, a SYSPLEX may represent a type of restart task, an IPL date may identify a time when an IPL flow is performed, a creator may identify a user who created the IPL flow, an IPL status may represent whether the IPL is completed, a presentation item may present status information of the IPL, and a detail page may enter a page of a flow management module. Meanwhile, on the task management module page, the user can delete, modify, newly establish and inquire the IPL task.

S203, the control host computer performs restarting based on the target restarting task according to a preset restarting operation flow, and a restarting result of the target restarting task is generated; the target restart task corresponds to the restart task identification.

The target restart task corresponds to a restart task identifier, for example, if the target restart task is a database patch validation task, the restart task identifier corresponding to the database patch validation task is 88. For another example, if the target restart task is pe1 shown in fig. 3, the restart task corresponding to the pe1 task is identified as 91.

In the embodiment of the application, the platform end can control the host end to restart based on the target restart task according to the preset restart operation flow, and generate the restart result of the target restart task. Assuming that the preset restart operation flow may include a pre-restart operation flow, a mid-restart operation flow, and a post-restart operation flow, when the platform end performs restart based on the target restart task, the platform end may control the host end to sequentially execute the pre-restart operation flow, the mid-restart operation flow, and the post-restart operation flow. And finally, generating a restart result of the target restart task.

For example, the target restart task is a database patch validation task, and in a pre-restart stage, the platform end can control the host end to restart based on the database patch validation task according to the pre-restart operation flow A, so as to generate a restart result of the database patch validation task in the pre-restart stage; in the restarting stage, the platform end can control the host end to restart based on the database patch effective task according to the operation flow A before restarting, and a restarting result of the database patch effective task in the restarting stage is generated; in the post-restart stage, the platform end can control the host end to restart based on the database patch validation task according to the pre-restart operation flow A, and a restart result of the database patch validation task in the post-restart stage is generated. The restart result may indicate whether the restart of the database patch validation task is successful, or may further include intermediate data obtained during the restart based on the database patch validation task, which is, of course, not limited in this application.

In the host restarting process management method, firstly, the platform end receives a host restarting instruction, then obtains a preset restarting operation process corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction, and finally controls the host end to restart according to the preset restarting operation process based on a target restarting task corresponding to the restarting task identifier, so as to generate a restarting result of the target restarting task, wherein the preset restarting operation process comprises an operation process before restarting, an operation process during restarting and an operation process after restarting. In the traditional technology, the IPL full-flow operation is performed on the large-scale host computer by adopting a manual mode, so that system bug repairing and system upgrading are realized on the large-scale host computer, and the efficiency is lower because the IPL full-flow operation is performed on the large-scale host computer by adopting the manual mode because the flow of the IPL operation is very complex and tedious. In the embodiment of the application, the platform end can restart based on the target restart task according to the preset restart operation flow, so that each operation of the IPL of the large-scale host is not required to be manually executed and recorded, and the efficiency of executing the IPL flow is improved.

In an embodiment, the embodiment relates to how to obtain a possible implementation manner of a preset restart operation flow corresponding to a restart task identifier according to the restart task identifier carried in a host restart instruction if the host is in a pre-restart stage, where on the basis of the embodiment, if the host is in the pre-restart stage, the step S202 includes:

acquiring an operation flow before restarting corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the pre-restart operation flow comprises a first initialization operation flow and a first environment detection operation flow, wherein the first initialization operation flow and the first environment detection operation flow correspond to the restart task identifier.

The whole restarting process of the platform end control host end can be divided into a pre-restarting stage, a restarting stage and a restarting post-stage. Then, if the host is in the pre-restart stage, the pre-restart operation flow is executed in the pre-restart stage. The pre-restart operation flow may include a first initialization operation flow and a first environment detection operation flow, which correspond to the restart task identifier. The first initialization operation may include an ACTION before IPL (system program load, initialize Program Load), down non-nanotube address space, looking up an address space not defined in SA, an environment before IPL check, confirming that a lot has completed several IPLs before work needs to be done, etc., which is of course not limited in this application. The first environment detection operational flow may be an pre-IPL environment check, the check item including an operating system portion, a database portion, and a flow automation management tool portion.

It should be noted that, the SA represents a host automation management tool, and is responsible for implementing repetitive and complex operations such as monitoring, starting/down software, hardware resources, etc. of some systems; the ACTION refers to the collective name of some columns of tasks to be completed, such as modifying parameters, starting and stopping address space and other operations; the down non-nanotube address space is an address space (which can be understood as a process on a host system) which is not stopped by a host automation management tool SA nanotube, one of the SA works is "start/down software and hardware resources", if the SA nanotube is not down by the SA tool, the down task can only be executed by writing the operation, and some address spaces in the system environment are not down by the SA nanotube for some reasons and can only be started by the operation mode.

In this embodiment of the present application, the platform end may obtain, according to a restart task identifier carried in a host restart instruction, a first initialization operation flow and a first environment detection operation flow corresponding to the restart task identifier.

For example, assuming that the restart task identifier is an ID of a database patch validation task, a first initialization operation flow corresponding to the restart task identifier is to first perform an IPL (system program loading, initialize Program Load) pre-ACTION, then go down a non-nanotube address space, and check an address space that is not defined in the SA. The first environment detection operation flow pre-IPL environment check, check item includes an operating system portion, a database portion, and a flow automation management Tool (TWS) portion. The operating system part may include ZOS version information, a system's bright label, CPU granularity checking, OMVS, etc., the database part may include checking CDDS file information, DDF, WLM, abnormal read, system table, etc., and the flow automation management tool part may include whether the address space initiated lpar is correct or not and error information in the log. Wherein CDDS represents a compression dictionary dataset of DB2 (host database), OMVS represents a component of the host system using unix environment, WLM represents a component implementing a system resource equitable allocation policy, THREAD represents a system THREAD, and ZOS represents an IBM host operating system name.

Fig. 4 is a schematic page diagram of a process management module according to an embodiment of the present application; referring to fig. 4, the interface shows four parts of pre-IPL preparation (pre-restart phase), IPL system (mid-restart phase), post-IPL operation (post-restart phase), and completion. The pre-IPL preparation comprises pre-IPL ACTION, down non-nanotube address space, address space which is not defined in SA, pre-IPL environment check and work which needs to be completed before batch completion of a plurality of IPLs is confirmed. The interface contains an entry for using the emergency kit and an entry for recording IPL problems.

In this embodiment, by acquiring the first initialization operation flow and the first environment detection operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction, the support of the operation flow before restarting can be provided for the platform end to control the host end restart by determining the first initialization operation flow and the first environment detection operation flow.

In one embodiment, fig. 5 is one of the flow diagrams of a method for generating a restart result provided in the embodiment of the present application, where the embodiment relates to a possible implementation manner of how to generate a restart result of a target restart task by controlling a host side to restart based on the target restart task according to a preset restart operation flow, and on the basis of the foregoing embodiment, the step S203 includes:

S501, the control host side initializes according to a first initialization operation flow corresponding to the restart task identifier, and generates a first initialization result.

In this embodiment of the present application, the platform side may control the host side to perform an initialization operation according to a first initialization operation flow corresponding to the restart task identifier, and generate a first initialization result corresponding to the initialization operation.

Taking the above example, the restart task identifier is the ID of the database patch validation task, and the first initialization operation flow corresponding to the restart task identifier is to first perform the previous ACTION of IPL (system program loading, initialize Program Load), then perform the next down of the non-nanotube address space, and check the address space that is not defined in SA.

Firstly, the host end performs IPL front ACTION to generate a result corresponding to the IPL front ACTION, then the host end returns the result corresponding to the IPL front ACTION to the platform end through a ZOMSF tool interface, and if no abnormal popup window exists, a user can click a 'confirm completion' control on the platform end system; then, the user can click a trigger control corresponding to the downed non-nanotube address space of the platform end system, the platform end sends an instruction of the operation of the downed non-nanotube address space to the host end through the ZOSMF tool interface, the host end performs the operation of the downed non-nanotube address space and generates an operation result, and the operation result of the downed non-nanotube address space is returned to the platform end through the ZOSMF tool interface; if the abnormal popup window does not exist, the user can click a trigger control corresponding to the address space which is not defined in the SA and is checked by the platform end system, the platform end sends an instruction for checking the address space operation which is not defined in the SA to the host end through the ZOMSF tool interface, the host end performs the operation for checking the address space which is not defined in the SA and generates an operation result, and the operation result for checking the address space which is not defined in the SA is returned to the platform end through the ZOMSF tool interface. The ZOMSF interface provides a set of application programming interfaces based on the HTTP protocol.

S502, receiving a first initialization result sent by the host side.

In this embodiment of the present application, the platform side may receive a first initialization result sent by the host side.

For example, in S501, since the operation of looking up the address space not defined in the SA is the last flow of the first initialization operation flow of the restart task, the first initialization result is the result of looking up the operation of the address space not defined in the SA, the host side sends the first initialization result to the platform side, and the platform side may receive the first initialization result sent by the host side.

S503, performing environment detection on the host side according to the first initialization result and the first environment detection operation flow corresponding to the restart task identifier, and generating a first environment detection result of the host side.

In this embodiment of the present application, the platform end may perform environment detection on the host end according to the first initialization result and according to the first environment detection operation flow corresponding to the restart task identifier, so as to generate a first environment detection result of the host end.

Specifically, if the first initialization result is normal, the environment detection may be performed on the host according to the first environment detection operation flow corresponding to the restart task identifier, so as to generate a first environment detection result of the host. If the first initialization result is abnormal, the initialization check can be performed again, and then the environment detection is performed on the host side according to the new first initialization result and the first environment detection operation flow corresponding to the restart task identifier, so as to generate a first environment detection result of the host side.

For example, following the example of S502, the last flow of the first initialization operation flow of the restart task is checked for an operation of an address space not defined in the SA, the result of checking for an address space not defined in the SA is normal, and the first environment detects an environment before the operation flow IPL, and the check items include an operating system portion, a database portion, and a flow automation management Tool (TWS) portion. The environment detection may be sequentially performed on the host side according to an operating system portion, a database portion, and a flow automation management Tool (TWS) portion, to generate a first environment detection result of the host side. Specifically, the user can click on a trigger control corresponding to the pre-IPL environment inspection of the platform end system, and then the platform end sends an instruction of the pre-IPL environment inspection to the host end through the socket interface, and the host end performs corresponding operation of the pre-IPL environment inspection and generates an operation result. In addition, whether batch processing is completed can be confirmed according to corresponding operation of the environment check before IPL and generating operation results.

In the above embodiment, the platform controls the host to initialize according to the first initialization operation flow corresponding to the restart task identifier, generates the first initialization result, receives the first initialization result sent by the host, and performs environment detection on the host according to the first environment detection operation flow corresponding to the restart task identifier according to the first initialization result, so as to generate the first environment detection result of the host. The method can ensure that the IPL pre-preparation flow of the host end is executed by the host end when the host end is in the pre-restarting stage, thereby improving the execution efficiency and reducing the execution error rate.

In an embodiment, fig. 6 is a flowchart of a first environmental detection result generation method provided in the embodiment of the present application, where the embodiment of the present application relates to how to perform environmental detection on a host according to a first environmental detection operation flow corresponding to a restart task identifier according to a first initialization result if the host includes a plurality of subsystems, so as to generate a possible implementation manner of the first environmental detection result of the host, where on the basis of the embodiment, S503 includes:

s601, according to a first initialization result and a first environment detection operation flow corresponding to a restarting task identifier, sending an environment data acquisition instruction to each subsystem of a host side; the environment data acquisition instruction is used for aiming at each subsystem, and the control host side acquires the environment data of the subsystem based on the acquisition script corresponding to the subsystem.

The subsystems of the host side may include DB2 (host database), CICS (host middleware), SA (system automation management tool), TWS (flow automation management tool), MQ (message queue), and the like. The environment data acquisition instruction is used for aiming at each subsystem, and the control host side acquires the environment data of the subsystem based on the acquisition script corresponding to the subsystem.

In the embodiment of the application, the platform end sends an environment data acquisition instruction to each subsystem of the host end according to the first initialization result and according to a first environment detection operation flow corresponding to the restart task identifier. That is, the platform end can control the host end to collect the environmental data of the subsystem according to the collection script corresponding to the subsystem. For example, the script may be a REXX script, which is a programming language commonly used for script writing in host systems.

S602, receiving environment data of each subsystem sent by a host side.

In the embodiment of the application, the platform end can receive the environment data of each subsystem sent by the host end. Specifically, the host side collects environmental data according to the collection script corresponding to each subsystem, and sends the collected environmental data to the platform side, and the platform side can send the environmental data of each subsystem to the host side.

S603, analyzing the environment data of each subsystem to generate a first environment check result of the host side.

In this embodiment of the present application, the platform side may analyze the environmental data of each subsystem by using a preset program code, and generate a first environmental inspection result of the host side.

For example, the platform end may analyze the environmental data of each subsystem by using a preset program code, store the special key value of the inspection item corresponding to the subsystem and the corresponding data thereof into the database, and if the inspection result is normal, may set the inspection item state to 0 in the database, and if the inspection result is abnormal to 1. Wherein the database may be MySQL database, which is a relational database management system.

In the above embodiment, according to the first initialization result, according to the first environment detection operation flow corresponding to the restart task identifier, an environment data acquisition instruction is sent to each subsystem at the host end, the environment data of each subsystem sent by the host end is received, the environment data of each subsystem is analyzed, and a first environment inspection result at the host end is generated, so that the efficiency of the first environment inspection can be improved.

In one embodiment, the present embodiment relates to how to obtain a possible implementation manner of a preset restart operation flow corresponding to a restart task identifier according to the restart task identifier carried in a host restart instruction if the host is in a restart stage, where on the basis of the foregoing embodiment, S202 includes:

In this embodiment of the present application, if the host is in the restart stage, the platform may obtain, according to the restart task identifier carried in the host restart instruction, an operation flow of a system program loading manner corresponding to the restart task identifier. For example, assuming that the restart task is identified as the ID of the database patch validation task, the operation flow of the system program loading mode corresponding to the ID of the database patch validation task is obtained.

In the above embodiment, the platform end may obtain the operation flow of the system program loading mode corresponding to the restart task identifier according to the restart task identifier carried in the host computer restart instruction, so as to determine the restart operation corresponding to the restart task, and improve the efficiency of executing the operation flow in the restart.

In one embodiment, the present embodiment relates to a possible implementation manner of how to generate a restart result of a target restart task by controlling a host to restart based on the target restart task according to a preset restart operation flow, where on the basis of the foregoing embodiment, S203 includes:

And the control host executes the target restarting task according to the restarting operation flow, and generates a task restarting result of the target restarting task.

In the embodiment of the application, the platform end can control the host end to execute the target restarting task according to the restarting operation flow, and a task restarting result of the target restarting task is generated. For example, if the target restart task is a database patch validation task, the control host executes the restart task of the database patch validation task according to the operation flow in the restart process, and generates a task restart result of the target restart task.

In the above embodiment, by controlling the host side to execute the target restart task according to the operation flow in restart, the task restart result of the target restart task is generated, so that the efficiency of executing the operation flow in restart can be improved.

In one embodiment, the present embodiment relates to how to obtain a possible implementation manner of a preset restart operation flow corresponding to a restart task identifier according to the restart task identifier carried in a host restart instruction if the host is in a post-restart stage, where on the basis of the foregoing embodiment, S202 includes:

The operation flow after restarting comprises a second initialization operation flow and a second environment detection operation flow which correspond to the restarting task identifier. The second initialization operational procedure may include at least one of post IPL ACTION, restarting a set of TWS address spaces, post IPL environment checking. The second environment detection operational flow may include an IPL post-environment check; the check items include an operating system portion, a database portion, a host middleware (CICS), a Message Queue (MQ) address space launch state check, and a flow automation management Tool (TWS) portion. The operating system portion may include ZOS version information, a system light label, CPU granularity checking, OMVS, an IPLINFO query result, RES volume, APF, LINKLST, HEALTCHK, OMVSMF; the DB2 part can comprise checking CDDS file information, DDF, WLM, abnormal THREAD, system table; the CICS part can comprise MAS number, WORKLOAD number, TARGET number, ROUTING number, DB2 connection number, MRO connection number and LU6.2 connection number, wherein a default value can be set to check whether the ACTIVE number is consistent with the default value; the TWS portion may include whether the address space enabled lpar is correct and error information in the log.

In this embodiment of the present application, if the host is in the post-restart stage, according to the restart task identifier carried in the host restart instruction, the second initialization operation flow and the second environment detection operation flow corresponding to the restart task identifier are obtained. For example, the restart task is identified as an ID of the database patch validation task, and the operation flow after restarting corresponding to the ID of the database patch validation task is obtained according to the ID of the database patch validation task: and firstly performing IPL and then performing ACTION, restarting a set of TWS address space, and finally performing environment inspection after IPL.

In the above embodiment, the platform end may obtain the second initialization operation flow and the second environment detection operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction, so that the support of the operation flow after restarting can be provided for the platform end to control the host end by determining the second initialization operation flow and the second environment detection operation flow.

In an embodiment, fig. 7 is a second flowchart of a method for generating a restart result provided in the embodiment of the present application, where the embodiment relates to a possible implementation manner of how a control host performs restart based on a target restart task according to a preset restart operation flow, and how the control host performs restart based on the target restart task according to the preset restart operation flow, so as to generate a restart result of the target restart task, where on the basis of the foregoing embodiment, S203 includes:

S701, the control host side initializes according to a second initialization operation flow corresponding to the restart task identifier, and generates a second initialization result.

In this embodiment of the present application, the platform side may control the host side to perform an initialization operation according to a second initialization operation flow corresponding to the restart task identifier, and generate a second initialization result corresponding to the initialization operation.

Taking the above example, the restart task identifier is the ID of the database patch validation task, and the second initialization operation flow corresponding to the restart task identifier is to perform IPL and then ACTION first, and then restart a set of TWS address space. Firstly, the host end performs IPL post-ACTION to generate a result corresponding to the IPL post-ACTION, then the host end returns the result corresponding to the IPL post-ACTION to the platform end through a ZOMSF tool interface, and if no abnormal popup window exists, a user can click a 'confirm completion' control on the platform end system; then, the user can click a trigger control corresponding to restarting a set of TWS address space of the platform end system, the platform end sends an instruction for restarting the set of TWS address space operation to the host end through the ZOSMF tool interface, the host end performs the operation of restarting the set of TWS address space and generates an operation result, and the operation result of restarting the set of TWS address space is returned to the platform end through the ZOSMF tool interface. And generating a second initialization result to restart the set of TWS address space because the second initialization operation flow corresponding to the restart task identifier is ended when restarting the set of TWS address space.

S702, receiving a second initialization result sent by the host side.

In this embodiment of the present application, the platform side may receive the second initialization result sent by the host side.

For example, in S701, since restarting the operation of the set of TWS address space is the last flow of the second initialization operation flow of the restart task, the second initialization result is the result of restarting the operation of the set of TWS address space, the host side sends the second initialization result to the platform side, and the platform side may receive the second initialization result sent by the host side.

S703, performing environment detection on the host end according to a second environment detection operation flow corresponding to the restart task identifier according to the second initialization result, and generating a second environment detection result of the host end.

In this embodiment of the present application, the platform end may perform environment detection on the host end according to the second initialization result and according to the second environment detection operation flow corresponding to the restart task identifier, so as to generate a second environment detection result of the host end.

Specifically, if the second initialization result is normal, the environment detection may be performed on the host according to a second environment detection operation flow corresponding to the restart task identifier, so as to generate a second environment detection result of the host. If the second initialization result is abnormal, the initialization check can be performed again, and then the environment detection is performed on the host end according to a second environment detection operation flow corresponding to the restart task identifier according to the new second initialization result, so as to generate a second environment detection result of the host end.

Before the environment detection, the connectivity between the host end and the platform end needs to be checked, and the identity information of the user needs to be checked.

In the above embodiment, the host side is controlled to perform initialization according to the second initialization operation flow corresponding to the restart task identifier, a second initialization result is generated, the second initialization result sent by the host side is received, and finally, according to the second initialization result, the environment detection is performed on the host side according to the second environment detection operation flow corresponding to the restart task identifier, so as to generate a second environment detection result of the host side. The method can ensure that the IPL post-preparation flow of the host end is executed by the host end when the host end is in the post-restarting stage, reduce the execution error rate and improve the efficiency after the IPL is executed.

In an embodiment, fig. 8 is a second flowchart of a method for managing a host reboot process according to the embodiment of the present application, where the method further includes:

s801, comparing a first environment detection result of the host side with a second environment detection result of the host side to generate a comparison result.

The first environment detection result may include an environment detection result obtained by a first environment detection operation flow in the operation flow before restarting. The second environmental result may include an environmental detection result obtained by a second environmental detection operation flow in the operation flow after the restart. The comparison result may include information such as the first environment detection result being the same as the second environment detection result, the first environment detection result being different from the second environment detection result, and the like.

In this embodiment of the present application, the platform side may compare the received second environmental detection result of the host side with the first environmental detection result of the host side stored in the previous database, to generate a comparison result.

It should be noted that, in the second environment inspection operation flow, there is an inspection item in the first environment inspection operation flow, and parameters for comparing the first environment inspection result at the host end with the second environment inspection result at the host end may include: the RES volume is each lpar vs. IPL front, LOAD parameters, APF, etc. IPLINFO parameters. The RES volume is a storage volume for storing product medium files of the operating system and the subsystems; the lpar represents a logical partition, and a plurality of independent systems are created by dividing the CPU, the memory and other resources of a single system so as to finish the effective utilization of the system resources; APF is an authorized component for users, programs and the like in the system; IPLINFO represents a parameter file that queries the system for boot information, boot time, and boot usage.

S802, determining whether the environment of the host end after executing the target restarting task is abnormal or not according to the comparison result.

In the embodiment of the application, the platform end can determine whether the environment of the host end after executing the target restart task is abnormal according to the comparison result. Specifically, if the comparison result is that the first environment detection result is different from the second environment detection result, it can be determined that the environment of the host end after the target restart task is executed is abnormal; if the comparison result is that the first environment detection result is the same as the second environment detection result, it can be determined that the environment of the host end after the target restart task is executed is not abnormal.

S803, if the environment of the host end after the target restarting task is executed is abnormal, an abnormal result is obtained from the comparison result, and the abnormal result is displayed on the display interface.

The abnormal result may include a state of each inspection item in the environment detection flow of the operation flow after restarting, and the like.

In the embodiment of the application, if the environment of the host end after the target restart task is executed is abnormal, the platform end may obtain an abnormal result from the comparison result and display the abnormal result on the display interface. If the abnormality occurs, a red highlighting prompt for the abnormal examination item in the page is displayed, and if the abnormality does not occur, a green highlighting prompt for the abnormal examination item in the page is displayed. For example, the display interface may be a grafana presentation page, which may present abnormal results and normal results, and may also present information such as IPL completion time, IPL details, and the like. grafana is an open source data visualization tool that can be used to custom display charts for data display.

In the above embodiment, the comparison result is generated by comparing the first environmental detection result of the host end with the second environmental detection result of the host end, and then, according to the comparison result, it is determined whether the environment of the host end after executing the target restart task is abnormal, and finally, if the environment of the host end after executing the target restart task is abnormal, the abnormal result is obtained from the comparison result, and the abnormal result is displayed on the display interface. Whether the environment state of the IPL at the host end is normal or not can be checked, and the efficiency of finding problems is improved, so that the IPL operation efficiency can be improved.

In an embodiment, fig. 9 is a third flowchart of a method for managing a host restart procedure according to the embodiment of the present application, where the method further includes:

and S901, generating a log file according to a restarting result of the target restarting task.

Wherein the log file may be presented in the form of a presentation. The contents of the log file record may include: time of the current IPL flow, matters of the IPL flow, environment inspection and display after the IPL, problems recorded in the IPL process and the like.

In the embodiment of the application, the user can click a completion control in the flow management module in the system of the platform end and the like, so that the platform end can generate the log file according to the restarting result of the target restarting task.

S902, receiving a log file sending instruction, and sending the log file to a target address according to the log file sending instruction.

In the embodiment of the application, the user can click on a control such as sending the log file, and the platform end can receive the log file sending instruction and send the log file to the target address according to the log file sending instruction. The log file may be sent to a target mailbox of the target user in the form of a mail. The target user may be an operation and maintenance person.

In the embodiment, the log file is generated according to the restart result of the target restart task, the log file sending instruction is received, and the log file is sent to the target address according to the log file sending instruction, so that the restart result of the target restart task can be received by a worker working remotely, and convenience is provided for the worker needing to check the restart result.

In one embodiment, fig. 10 is a schematic page diagram of a problem recording module according to an embodiment of the present application. The problem recording module can be arranged on a system of the platform end, the user can click on a related control of the problem recording module to open a page of the problem recording module, the user can click on a control corresponding to the newly-built problem on the page, a problem recording can be newly built to record the problem or the question existing in the IPL flow, the user can click on the corresponding control to store the recorded problem in the database, and the system of the platform end can conveniently check the recorded problem later.

In one embodiment, fig. 11 is a schematic page view of an emergency tool module according to an embodiment of the present application. The opening control corresponding to the emergency tool module can be clicked on the system page of the platform end, so that a user can simply operate the host end on the platform end under the condition that identity verification is not performed, such as inquiring the address space state, sending a command, going down the address space, starting the address control and the like. The emergency tool module calls a ZOMSF tool interface of the host end to transmit instructions and return results.

In an exemplary embodiment, fig. 12 is a fourth flow chart of a host restart flow management method according to the embodiment of the present application, and referring to the host restart flow management method provided in fig. 12, the method includes:

s1201, receiving a host restarting instruction.

S1202, if the host end is in a pre-restart stage, acquiring a pre-restart operation flow corresponding to a restart task identifier according to the restart task identifier carried in a host restart instruction; the pre-restart operation flow comprises a first initialization operation flow and a first environment detection operation flow, wherein the first initialization operation flow and the first environment detection operation flow correspond to the restart task identifier.

S1203, the control host performs initialization according to the first initialization operation flow corresponding to the restart task identifier, and generates a first initialization result.

S1204, receiving a first initialization result sent by the host side.

S1205, if the host end comprises a plurality of subsystems, sending an environment data acquisition instruction to each subsystem of the host end according to a first environment detection operation flow corresponding to the restart task identifier according to a first initialization result; the environment data acquisition instruction is used for aiming at each subsystem, and the control host side acquires the environment data of the subsystem based on the acquisition script corresponding to the subsystem.

S1206, receiving the environment data of each subsystem sent by the host.

S1207, analyzing the environment data of each subsystem to generate a first environment check result of the host side.

S1208, if the host end is in a restarting stage, acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow in restarting is the operation flow adopting a loading mode of the system program.

S1209, the control host executes the target restarting task according to the restarting operation flow, and generates a task restarting result of the target restarting task.

S1210, if the host end is in the post-restart stage, acquiring a post-restart operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction; the operation flow after restarting comprises a second initialization operation flow and a second environment detection operation flow which correspond to the restarting task identifier.

S1211, the control host side initializes according to the second initialization operation flow corresponding to the restart task identifier, and generates a second initialization result.

S1212, receiving a second initialization result sent by the host.

S1213, performing environment detection on the host side according to the second initialization result and the second environment detection operation flow corresponding to the restart task identifier, and generating a second environment detection result of the host side.

S1214, comparing the first environment detection result of the host end with the second environment detection result of the host end to generate a comparison result.

S1215, determining whether the environment of the host end after the target restarting task is executed is abnormal according to the comparison result.

S1216, if the environment of the host end after the target restarting task is executed is abnormal, obtaining an abnormal result from the comparison result, and displaying the abnormal result on a display interface.

In the above embodiment, the platform end receives the host restart instruction, if the host end is in the stage before restarting, according to the restart task identifier carried in the host restart instruction, the operation flow before restarting corresponding to the restart task identifier is obtained, the host end is controlled to initialize according to the first initialization operation flow corresponding to the restart task identifier, a first initialization result is generated, and the first initialization result sent by the host end is received; if the host end comprises a plurality of subsystems, according to a first initialization result and a first environment detection operation flow corresponding to the restarting task identifier, sending an environment data acquisition instruction to each subsystem of the host end; the environment data acquisition instruction is used for acquiring the environment data of the subsystems based on the acquisition scripts corresponding to the subsystems by the control host side aiming at the subsystems, then receiving the environment data of the subsystems sent by the host side, analyzing the environment data of the subsystems and generating a first environment inspection result of the host side. And if the host end is in the restarting stage, acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction, controlling the host end to execute the target restarting task according to the restarting operation flow, and generating a task restarting result of the target restarting task. If the host end is in a post-restart stage, acquiring a post-restart operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction, controlling the host end to initialize according to the second initialization operation flow corresponding to the restart task identifier, generating a second initialization result, receiving the second initialization result sent by the host end, performing environment detection on the host end according to the second environment detection operation flow corresponding to the restart task identifier according to the second initialization result, generating a second environment detection result of the host end, comparing the first environment detection result of the host end with the second environment detection result of the host end, generating a comparison result, determining whether the environment of the host end after executing the target restart task is abnormal according to the comparison result, if the environment of the host end after executing the target restart task is abnormal, acquiring the abnormal result from the comparison result, and displaying the abnormal result on a display interface. In the traditional technology, the IPL full-flow operation is performed on the large-scale host computer by adopting a manual mode, so that system bug repairing and system upgrading are realized on the large-scale host computer, and the efficiency is lower because the IPL full-flow operation is performed on the large-scale host computer by adopting the manual mode because the flow of the IPL operation is very complex and tedious. In the embodiment of the application, the platform end can restart based on the target restart task according to the preset restart operation flow, so that each operation of the IPL of the large-scale host is not required to be manually executed and recorded, and the efficiency of executing the IPL flow is improved.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a host restarting flow management device for implementing the host restarting flow management method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of one or more host restart flow management devices provided below may refer to the limitation of the host restart flow management method described above, and will not be repeated here.

In one embodiment, fig. 13 is a block diagram of a configuration of a host restart flow management device according to an embodiment of the present application, and as shown in fig. 13, a host restart flow management device 1300 is provided, including: a receiving module 1301, an acquiring module 1302, and a first generating module 1303, wherein:

a receiving module 1301, configured to receive a host restart instruction.

An obtaining module 1302, configured to obtain a preset restart operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction; the preset restarting operation flow comprises a pre-restarting operation flow, a restarting operation flow and a restarting operation flow.

The first generating module 1303 is configured to control the host to restart based on the target restart task according to a preset restart operation flow, and generate a restart result of the target restart task; the target restart task corresponds to the restart task identification.

In one embodiment, if the host is in the pre-restart stage, the obtaining module 1302 includes:

the first acquisition sub-module is used for acquiring an operation flow before restarting corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the pre-restart operation flow comprises a first initialization operation flow and a first environment detection operation flow, wherein the first initialization operation flow and the first environment detection operation flow correspond to the restart task identifier.

In one embodiment, the first generating module 1303 includes:

the first control sub-module is used for controlling the host side to initialize according to a first initialization operation flow corresponding to the restart task identifier, and generating a first initialization result.

The first receiving sub-module is used for receiving a first initialization result sent by the host side.

The first generation sub-module is used for carrying out environment detection on the host end according to a first initialization result and a first environment detection operation flow corresponding to the restarting task identifier, and generating a first environment detection result of the host end.

In one embodiment, if the host includes a plurality of subsystems, the first generating sub-module includes:

the first sending unit is used for sending an environment data acquisition instruction to each subsystem of the host side according to a first environment detection operation flow corresponding to the restart task identifier according to a first initialization result; the environment data acquisition instruction is used for aiming at each subsystem, and the control host side acquires the environment data of the subsystem based on the acquisition script corresponding to the subsystem.

The first receiving unit is used for receiving the environment data of each subsystem sent by the host side.

The first generating unit is used for analyzing the environment data of each subsystem and generating a first environment check result of the host side.

In one embodiment, the host side is in a restart phase, and the acquiring module 1302 includes:

the second obtaining submodule is used for obtaining the restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow in restarting is the operation flow adopting the loading mode of the system program.

In one embodiment, the first generating module 1303 includes:

the second control subunit is used for controlling the host side to execute the target restarting task according to the restarting operation flow and generating a task restarting result of the target restarting task.

In one embodiment, if the host is in the post-restart stage, the obtaining module 1302 includes:

the third obtaining submodule is used for obtaining a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow after restarting comprises a second initialization operation flow and a second environment detection operation flow which correspond to the restarting task identifier.

In one embodiment, the first generating module 1303 includes:

the second control sub-module is used for controlling the host end to initialize according to a second initialization operation flow corresponding to the restarting task identifier and generating a second initialization result;

The second receiving sub-module is used for receiving a second initialization result sent by the host end;

and the second generating sub-module is used for carrying out environment detection on the host end according to a second initialization result and a second environment detection operation flow corresponding to the restarting task identifier, and generating a second environment detection result of the host end.

In one embodiment, the host restart flow management apparatus 1300 further includes:

the second generating module is used for comparing the first environment detection result of the host end with the second environment detection result of the host end to generate a comparison result.

And the determining module is used for determining whether the environment of the host end after the target restarting task is executed is abnormal or not according to the comparison result.

And the display module is used for acquiring an abnormal result from the comparison result and displaying the abnormal result on the display interface if the environment of the host end after the target restarting task is executed is abnormal.

and the third generation module is used for generating a log file according to the restarting result of the target restarting task.

The receiving module is used for receiving the log file sending instruction and sending the log file to the target address according to the log file sending instruction.

The above-mentioned modules in the host restart flow management device may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 14. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a host restart flow management method.

It will be appreciated by those skilled in the art that the structure shown in fig. 14 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the computer device to which the present application applies, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:

receiving a host restarting instruction;

the control host terminal restarts based on the target restarting task according to a preset restarting operation flow, and a restarting result of the target restarting task is generated; the target restart task corresponds to the restart task identification. In one embodiment, the processor when executing the computer program further performs the steps of:

In one embodiment, the processor when executing the computer program further performs the steps of:

the control host side performs initialization according to a first initialization operation flow corresponding to the restarting task identifier, and generates a first initialization result;

receiving a first initialization result sent by a host terminal;

and carrying out environment detection on the host end according to the first initialization result and the first environment detection operation flow corresponding to the restarting task identifier, and generating a first environment detection result of the host end.

according to a first initialization result and a first environment detection operation flow corresponding to the restarting task identifier, sending an environment data acquisition instruction to each subsystem of the host end; the environment data acquisition instruction is used for aiming at each subsystem, and the control host side acquires the environment data of the subsystem based on the acquisition script corresponding to the subsystem;

Receiving environment data of each subsystem sent by a host end;

In one embodiment, the processor when executing the computer program further performs the steps of: acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow after restarting comprises a second initialization operation flow and a second environment detection operation flow which correspond to the restarting task identifier.

The control host end initializes according to a second initialization operation flow corresponding to the restarting task identifier, and generates a second initialization result;

receiving a second initialization result sent by a host terminal;

and performing environment detection on the host end according to a second environment detection operation flow corresponding to the restarting task identifier according to a second initialization result, and generating a second environment detection result of the host end.

if the environment of the host end after the target restarting task is executed is abnormal, an abnormal result is obtained from the comparison result, and the abnormal result is displayed on a display interface.

and receiving a log file sending instruction, and sending the log file to the target address according to the log file sending instruction.

In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:

receiving a host restarting instruction;

the control host terminal restarts based on the target restarting task according to a preset restarting operation flow, and a restarting result of the target restarting task is generated; the target restart task corresponds to the restart task identification.

In one embodiment, the computer program when executed by the processor further performs the steps of:

Receiving a first initialization result sent by a host terminal;

receiving environment data of each subsystem sent by a host end;

receiving a second initialization result sent by a host terminal;

In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:

receiving a host restarting instruction;

receiving a first initialization result sent by a host terminal;

Receiving environment data of each subsystem sent by a host end;

receiving a second initialization result sent by a host terminal;

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples represent only a few embodiments of the present application, which are described in more detail and are not thereby to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A host restart flow management method, the method comprising:

receiving a host restarting instruction;

The control host terminal restarts based on the target restart task according to the preset restart operation flow, and a restart result of the target restart task is generated; and the target restarting task corresponds to the restarting task identifier.

2. The method of claim 1, wherein if the host is in a pre-restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

acquiring a pre-restart operation flow corresponding to the restart task identifier according to the restart task identifier carried in the host restart instruction; the pre-restart operation flow comprises a first initialization operation flow and a first environment detection operation flow which correspond to the restart task identifier.

3. The method of claim 2, wherein the controlling the host performs restarting based on a target restart task according to the preset restart operation flow, and generating a restart result of the target restart task includes:

the control host side performs initialization according to the first initialization operation flow corresponding to the restarting task identifier, and generates a first initialization result;

Receiving the first initialization result sent by the host side;

4. The method of claim 3, wherein if the host side includes a plurality of subsystems, the performing environment detection on the host side according to the first initialization result and the first environment detection operation flow corresponding to the restart task identifier, to generate a first environment detection result of the host side includes:

according to the first initialization result, according to the first environment detection operation flow corresponding to the restarting task identifier, an environment data acquisition instruction is sent to each subsystem of the host side; the environment data acquisition instruction is used for controlling the host side to acquire environment data of the subsystems based on acquisition scripts corresponding to the subsystems for each subsystem;

receiving environment data of each subsystem sent by the host side;

5. The method according to any one of claims 1-4, wherein, if the host is in a restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

acquiring a restarting operation flow corresponding to the restarting task identifier according to the restarting task identifier carried in the host restarting instruction; the operation flow in restarting is the operation flow adopting a loading mode of the system program.

6. The method of claim 5, wherein the controlling the host performs restarting based on a target restart task according to the preset restart operation flow, and generating a restart result of the target restart task includes:

7. The method according to claim 3 or 4, wherein if the host is in a post-restart stage, the obtaining, according to a restart task identifier carried in the host restart instruction, a preset restart operation flow corresponding to the restart task identifier includes:

8. The method of claim 7, wherein the controlling the host performs restarting based on a target restart task according to the preset restart operation flow, and generating a restart result of the target restart task includes:

the control host side performs initialization according to the second initialization operation flow corresponding to the restarting task identifier, and generates a second initialization result;

receiving a second initialization result sent by the host side;

9. The method of claim 8, wherein the method further comprises:

if the environment of the host end after executing the target restarting task is abnormal, acquiring an abnormal result from the comparison result, and displaying the abnormal result on a display interface.

10. The method according to claim 1, wherein the method further comprises:

generating a log file according to the restarting result of the target restarting task;

11. A host restart flow management apparatus, the apparatus comprising:

the receiving module is used for receiving a host restarting instruction;

the first generation module is used for controlling the host side to restart based on a target restart task according to the preset restart operation flow and generating a restart result of the target restart task; and the target restarting task corresponds to the restarting task identifier.

12. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 10 when the computer program is executed.

13. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 10.

14. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 10.