JPS6224332A - Initial diagnosis control system - Google Patents

Abstract

PURPOSE:To execute the minimum necessary precaring and to eliminate the delay of rise of a subsystem by executing the precaring of the subsystem in response to execution of the precaring of a host system. CONSTITUTION:When a host system decides that the precaring must be executed, '1' set to an execution flag 1 for execution of the precaring. While '0' is set to the flag 1 when the host system decides that no execution of the precaring is needed. While a subsystem receives a loading request from the host system together with the information on a control block including '1' or '0' of the flag 1 and extracts the flag 1 out of the control block. An initial diagnosis discriminating part 2 decides whether the precaring should be executed or not for the extracted flag 1. Then the precaring of the subsystem is carried out when the flag 1 is equal to '1' for example.

Description

[Detailed Description of the Invention] [Summary] In an initial diagnosis control method that controls initial diagnosis of a subsystem connected to a host system, an execution flag indicating whether the host system has performed an initial diagnosis and a notification of the execution flag are provided. an initial diagnosis determination unit that determines whether or not to perform initial diagnosis based on is loaded, and when the initial diagnosis determination unit determines that an initial diagnosis should be performed based on the execution flag included in the loaded control block, the initial diagnosis of the subsystem is executed.

[Conventional technology]

Conventionally, pre-care (initial diagnosis) of subsystems connected to a host system has been carried out, that is, checking by software whether or not the hardware is operating normally.

This initial diagnosis is automatically executed when the subsystem is downloaded from the host system as indicated by the dotted line in FIG. The configuration shown in FIG. 2 will be explained below.

In the figure, ■ indicates the state for determining whether or not it is necessary to execute pre-care of the host system; if YES, 9
Execute @ in the diagram. If No, execute O in Figure 1.

In the figure, @ indicates a state in which pre-care is executed.

This means activating an initial diagnostic program to diagnose whether the hardware of the host system is operating normally.

In the figure, @ indicates a state in which firmware is loaded into the host system.

In the figure, [phase] indicates a state in which the subsystem is downloaded. As a result, the [phase] in the diagram of the subsystem is executed. And the host system is the software's IP
Execute L (initial loading).

■ in the figure indicates a state in which the subsystem executes pre-care. This pre-care is always executed, and as in the case of the host system shown in ■ in the figure, it may be executed once a day, for example, as needed. Not controlled to run.

In the figure, [phase] indicates a state in which firmware is loaded.Next, software IPL is executed.

[Problem that the invention seeks to solve]

Conventionally, as shown in FIG. 2, a subsystem connected to a host system always executes pre-care when downloading from the host system, resulting in a delay in startup of the subsystem.

[Means for solving problems]

In order to solve the above-mentioned problem, the present invention prevents delays in the start-up of the subsystem by adopting a configuration in which pre-care of the subsystem is executed in response to the execution of pre-care in the host system.

FIG. 0 is a diagram illustrating means for solving problems using the configuration diagram of an embodiment of the present invention shown in FIG. 1.

1 represents an execution flag, and 2 represents an initial diagnosis determination unit.

In FIG. 1, the execution flag 1 in FIG. 9 stores the result of determining whether or not the host system needs to execute pre-care (■, ■ in the figure).

The initial diagnosis determining unit 2 in the figure determines whether the subsystem should perform pre-care.

Based on this determination result, pre-care of the subsystem is executed (e in the figure).

[Effect]

According to the present invention, in FIG. 1, when the host system determines that it is necessary to execute pre-care at ■ in the figure, the execution flag is set to "l" at ■ in the figure, and pre-care is executed at ■ in the figure. are doing. and.

■ If it is determined that there is no need to perform pre-care,
The execution flag is set to "0".

On the other hand, the subsystem receives notification from the host system of a control block containing an execution flag of 1'' or ``0'' together with a loading request as indicated by ■ in the figure.

Execution flags are extracted from this control block.

This extracted execution flag is indicated by ■ in Figure 2, which indicates the initial diagnosis Mll.
i112 kayo 1') - C7"
Pre-care of the subsystem is executed at [stock] in the figure.

〔Example〕

The configuration and operation of the present invention will be explained in detail using the configuration diagram of one embodiment of the present invention shown in FIG.

In Figure 1, ■ in Figure 9 determines whether the host system needs to execute pre-care.
This indicates that the host system - tactically - stores a time clock and is controlled to perform maintenance, for example, once a day. For this reason.

After performing precare once a day, do not perform precare repeatedly even if the power of the host system is turned off or reset.

Then, in the case of YES, the process (■) in Figure 5 is executed. In the case of NO, perform ■ in Figure 1.

In the figure, "1" is set in the execution flag to indicate that pre-care needs to be executed.

In the figure, "0" is set to the execution flag to indicate that there is no need to execute pre-care.

■ in the figure indicates a state in which pre-care is executed.

As mentioned above, this means diagnosing whether or not the hardware of the host system is operating normally using software.

■ in the figure indicates a state in which firmware is loaded.

In the figure, ■ indicates a state in which the host system issues a loading request, for example, an interrupt request, to the subsystem, and also issues a request to load a control block containing an execution flag.

The host system then performs software loading.

On the other hand, the subsystem performs the following processing.

In the figure, ■ indicates a state in which it is determined whether or not a loading request has been issued from the host system. This means determining whether a loading request, for example an interrupt request (REQ), has been issued.

In the figure, ■ indicates a state in which the subsystem loads a control block from the host system.

In the figure, ■ indicates a state in which it is determined whether the content of the execution flag instructing to execute pre-care is "1" or not.
If YES, pre-care is executed in [phase] in Figure 1.

As a result, pre-care of the subsystem is executed in a so-called synchronized manner with the host system. Therefore, even if the subsystem does not have a 1-time clock, it can be controlled to perform pre-care only once a day, if necessary. If NO, no pre-care is performed. The subsystems then sequentially perform firmware and software loading.

〔Effect of the invention〕

As explained above, according to the present invention, an execution flag is provided to identify whether or not the host system needs to execute pre-care, and the subsystem performs pre-care of the subsystem based on the notification of this execution flag. Since the pre-care is controlled to be executed by determining whether or not it is, the minimum necessary pre-care can be executed and the subsystem can be started up quickly without sacrificing performance.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of one embodiment of the present invention, and FIG. 2 is a block diagram of a conventional initial diagnosis control system. In the figure, 1 represents an execution flag, and 2 represents an initial diagnosis determination section. Patent Applicant Usatsuk Electronic Industry Co., Ltd. Representative Patent Attorney Hiroshi Mori 1) (and 2 other people) Figure 2

Claims (1)

[Claims] In an initial diagnosis control method for controlling initial diagnosis of a subsystem connected to a host system, an execution flag (1) indicating whether or not the host system has performed an initial diagnosis; and an execution flag (1) included in a control block. an initial diagnosis determination unit (2) that determines whether or not to perform an initial diagnosis of the subsystem based on the execution flag that is displayed; In response to this, the subsystem loads a control block, and when the initial diagnosis determination unit (2) determines that the execution flag contained in the loaded control block should be used for initial diagnosis, the initial diagnosis of the subsystem is An initial diagnosis control method characterized by controlling execution of initial loading after execution of diagnosis.