JPH0883189A - System management device - Google Patents

Abstract

(57) [Summary] [Purpose] In a system management device used in a system that uses multiple processes, the problem that the system management device cannot be reused when reusing processes to construct a new system Resolve and improve reusability. [Configuration] Block system management processes 105, 106, 1 for managing a plurality of processes divided into blocks
07 and the overall system management process 101 that manages these block system management processes, only the software of the block system management process needs to be changed when the system is constructed by reusing the processes. Can be improved.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an entire system of a system for coordinating processing while performing inter-process communication by gathering a plurality of processes that perform a predetermined behavior according to a set of communication from the outside and an internal state. The present invention relates to a system management device that monitors the state and transitions the state of the entire system.

[0002]

2. Description of the Related Art In recent years, a system has been used in which a plurality of processes cooperate to perform processing by interprocess communication or the like. As such an example, there is a facsimile communication system. The system management device is used for managing the state of the system and for performing system state transitions such as starting and stopping.

FIG. 13 shows a schematic configuration of a conventional system management device. In FIG. 13, reference numeral 1301 is a system management process, 1302 to 1308 are processes that configure the system, 1309 is a computer that accommodates these,
An external storage device 1310 has a disk medium connected to the computer 1309.

The operation of the system management apparatus configured as described above will be described below. When the system is activated, the system management process 1301 activates the processes 1302-1308. Then, when something abnormal occurs, the disk of the external storage device 1310 is accessed each time the process is started to record the changes in the process state and the system state in order to restore the original state later.

Similarly, when the system is stopped, the system management process 1301 stops the processes 1302-1308. Then, when something abnormal occurs, the disk of the external storage device 1310 is accessed each time the process is started to record the changes in the process state and the system state in order to restore the original state later.

Here, it is assumed that a new system is constructed by reusing software of a part of processes constituting the system of FIG. When the software of the processes 1302-1308 is reused and the system is constructed with the software of the new process, it becomes as shown in FIG. In FIG. 14, reference numeral 1401 indicates a system management process, and 1402-1405 indicate processes for realizing a new system function. The system management process 1401 of this system controls the start and stop of nine processes 1302 to 1306 and 1402 to 1405, and records changes in the process state and the system state.

[0007]

However, in the above conventional configuration, when a new system is created by reusing the software of a part of the processes of the already created system, the processes such as starting and stopping of each process are not processed. You have to create a new system management process to control it. That is, in the system of FIG. 14, although the software of the processes 1302-1306 used in FIG. 13 is reused, the software of the system management process 1301 of FIG. 13 cannot be reused,
There was a problem that the software of the system management process 1401 had to be newly created.

Further, in order to create the system management process 1401, it is necessary to know all the starting and stopping methods of the processes 1302-1306 and 1402-1405. Therefore, not only the newly changed start / stop method of the processes 1402 to 1405 but also the processes 1302 to 130 that are software to be reused
It took man-hours to learn the start-stop method of 6.

Generally, it takes time for an external storage device to start after issuing a data recording or reading request,
Moreover, since the speed of data recording and reading is lower than the speed at which data can be transferred from the computer, there is a problem with I / O blocks, such as suspending data transfer to an external storage device and continuing when data transfer is possible. there were. Therefore, since 7 processes in FIG. 13 and 9 processes in FIG. 14 are started and stopped in one process, when recording a process state change and a system state change in an external storage device, There was a problem that the processing was temporarily stopped by the I / O block, the next processing could not be performed, and it took time to start and stop the system. In addition, due to this, there is a problem that the capacity of the computer is not fully utilized.

Conventionally, as a method of reusing, there has been a macro used in spreadsheet software, but this is one in which one static one is sequentially executed.
It does not work at the same time. The process according to the present invention is a process that operates independently at all times, and the idea of macro could not be directly applied.

The present invention solves the above-mentioned conventional problems and facilitates the creation of a new system in which the software of the process is reused, prevents the delay due to the I / O block of the disk, and improves the capacity of the computer. It is an object of the present invention to provide a system management device that can be fully used.

[0012]

In order to achieve the above object, a system management apparatus of the present invention includes a block system management process for managing a plurality of processes divided into blocks, and an overall system for managing the block system management process. It has a system management process.

[0013]

According to the present invention, according to the above configuration, a system block unit including a block system management process for controlling a process when reusing software of a part of processes of the system to create a new system By reusing it, the system management device can be easily created, the delay due to the disk I / O block can be prevented, and the capacity of the computer can be fully utilized.

[0014]

【Example】

(First Embodiment) A first embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of a system management device according to the first embodiment of the present invention. In FIG. 1, 101 is an overall system management process, 102 to 104 are system blocks, and 105.
Reference numerals 107 to 107 are block system management processes, 108 to 114 are processes for performing a predetermined behavior according to a set of external communication and internal state, 115 is a computer accommodating them, and 116 is a disk medium connected to the computer 115. It is an external storage device.

The operation of the system management device configured as described above will be described. When booting, the overall system management process 101 first issues a system block boot command to the block system management processes 105, 106 and 107. Then, in response to this, the block system management process 105 sequentially activates the process 108 and the process 109, and records the process state and the system state in the external storage device 116 each time the process is activated. Similarly, the block system management process 106 sequentially activates the process 110, the process 111, and the process 112 to set the process state and the system state to the external storage device 1.
Record at 16. Similarly, the block system management process 107 starts the processes 113 and 114,
The process state and system state are recorded in the external storage device 116.

In the conventional technique of FIG. 13 in which the system is constructed by using seven processes as in the case of this embodiment,
Starts one process to one system management process 13
01, the system management process 130
When 1 records changes in the process state and system state in the external storage device 1310, if the processing is temporarily interrupted by the I / O block, the next processing cannot be performed, so the overall startup time becomes long. In the embodiment, when the block system management process 105 records the change in the process state and the system state in the external storage device 116, even if the process is temporarily suspended by the I / O block, the other block system management processes 106 and 107 are Since the process is different from the block system management process 105, the process can be continued. That is, the startup time as a whole can be shortened.

Next, when the system is stopped, the entire system management process 101 issues a system block stop command to the block system management processes 105, 106 and 107 as in the case of starting. Then, in response to this, the block system management process 107 sequentially stops the processes 114 and 113, and records the process state and the system state in the external storage device 116 each time the process is stopped. Similarly, the block system management process 106 sequentially stops the process 112, the process 111, and the process 110, and sets the process state and the system state to the external storage device 1.
Record at 16. Further, similarly, the block system management process 105 stops the process 114 and the process 113, and sets the process state and the system state to the external storage device 1.
Record at 16.

In the conventional technique shown in FIG. 13, in which the system is constructed by using seven processes as in the case of the present embodiment, the seven processes are stopped by one system management process 1301. Since the system management process 1301 records changes in the process state and system state in the external storage device 1310, the I / O
If the process is temporarily interrupted by a block, the next process cannot be performed, so the overall downtime was long.
In this embodiment, when the block system management process 105 records changes in the process state and system state in the external storage device 116, even if the processing is temporarily suspended by the I / O block, another block system management process 10
Since 6 and 107 are processes different from the block system management process 105, the processing can be continued. That is, the stop time as a whole can be shortened.

Next, process 108, process 109,
The software of the process 110, the process 111, and the process 112 is reused, and instead of the processes 113 and 114, new processes 203 and 20 as shown in FIG.
Suppose you want to build a new system using 4, 205, 206. At this time, the software of the system block 102 and the system block 103 is reused. In FIG. 2, 201 is a new system block, 202 is a new block system management process, and 203 to 206 are new processes.

In the conventional technique shown in FIG. 14 in which five softwares are reused to construct a system with four new processes as in the present embodiment, software of a system management process 1401 for controlling all nine processes is newly added. In the present embodiment, the block system management process 102 and the block system management process 103 manage all control such as starting and stopping of the processes of the system blocks 103 and 104. Management process 105, 10
Since the control of starting and stopping 6 and 202 is managed by the overall system management process 101, the processes 203 to 2
It is only necessary to create software for the block system management process 202 that manages the four start / stop operations of 06.

Further, in the conventional technique of FIG. 14, in order to create the system management process 1401, not only the method of starting and stopping the newly changed processes 1402 to 1405 but also the method of starting and stopping the processes 1302 to 1306 to be reused. It took man hours to learn. However, in the present embodiment, it is not necessary to learn the method of starting and stopping the processes 108 to 112 to be reused, and it suffices to learn the interface between the overall system management process 101 and the newly created block system management system 202.
It is possible to create a new system management device without knowledge of the method of starting the entire system.

As described above, according to this embodiment, the block system management processes 105 to 107 for managing the processes obtained by dividing the plurality of processes 108 to 114 constructing the system into blocks, and the block system management process 105. By providing the overall system management process 101 for managing the processes 107 to 107, the software of the system blocks 102 to 103 including the process and the block system management process is re-created when a new system in which the software of the process is reused is created. By using the block system management processes 105 to 107, the number of processes that need to be managed is smaller than the total number of processes constituting the system. Create the device Excellent system management device can be realized.

Further, one block system management process 105, 106 or 107 is provided by the I / O block.
Even when the processing of (1) is temporarily interrupted, the entire start / stop processing is not interrupted, and an excellent system management device capable of shortening the start / stop time can be realized.

Further, in FIG. 2, the system block 102,
The example of the system management device in the case of reusing the software of 103 to create a new system has been described.
As shown in FIG. 3, in addition to the system blocks 102 and 103, the software of the process 113 in the system block 104 is reused to create new processes 302 and 303 in place of the process 114. The same effect can be expected when creating software for a new block system management process 301 that manages 303.

Further, in FIG. 1 of the present embodiment, the block system management process 105 performs a predetermined behavior 108 according to a set of communication from the outside and an internal state,
Although I described the case of a process independent of 109,
As shown in FIG. 4, a system block 401 that performs a predetermined behavior according to a set of communication from the outside and an internal state has a function of a block system management process, and the start and stop of the processes 402 and 109, the process state and the system state. The same effect can be expected when recording, etc.

(Embodiment 2) Next, a second embodiment of the present invention will be described with reference to FIG. In FIG. 5, reference numeral 501 denotes the overall system management process, and 502 to 5
Reference numeral 04 is a system block, 505 to 507 is a block system management process, 508 to 514 are system sub blocks, 515 to 521 are sub block system management processes, 522 to 538 are processes, 539 is a computer, and 540 is an external storage having a disk medium. It is a device. The difference from the configuration of FIG. 1 is that the system block has two stages including a system sub block.

The operation of the system management process configured as described above will be described below. When booting, the overall system management process 501 first issues a system block boot command to the block system management process 505. Then, in response to this, the block system management process 505 issues a system block activation command to the sub block system management process 515. Then, in response to this, the sub-block system management process 515 activates the processes 522 and 523.
Next, the block system management process 505 issues a system block activation command to the sub block system management process 516. Then, similarly, the sub block system management process 516 activates the processes 524 to 526. Similarly, the sub block system management process 517 activates the processes 527 and 528. Further, similarly, the respective block system management processes 506 and 507 activate the process 538 from the process 529 through the sub block system management processes 518 to 521, respectively.

At this time, each time the process is activated, changes in the process state and system state are recorded in the external storage device 540. However, the I / O block temporarily suspends the processing of the sub-block system management process 515. Even
Other sub-block system management processes 516, 517
Can proceed, so the overall system boot process is not interrupted. The same effect can be expected when the other sub-block system management processes 516 to 521 temporarily suspend the processing due to the I / O block.

When stopping, the system block management device 501 first issues a system block stop command to the block system management process 505. Then, in response to this, the block system management process 505 issues a system block stop command to the sub block system management process 515. Then, in response to this, the sub-block system management process 515 notifies the process 52.
Stop 2,523. Next, the block system management process 505
A system block stop command is issued to 16. Then, similarly, the sub block system management process stops the processes 524 to 526. Similarly, the sub-block system management process 517 stops the processes 527 and 528. Further, in the same manner, the respective block system management processes 506 and 507 are respectively connected to the sub block system management processes 518 to 521.
Processes 529-538 are also stopped via.

At this time, each time the process is stopped, the changes in the process state and the system state are recorded in the external storage device 540. However, due to the I / O block, the processing of the sub-block system management process 515 is temporarily suspended. Even
Other sub-block system management processes 516, 517
Can proceed, so the overall system shutdown process is not interrupted. The same effect can be expected when the other sub-block system management processes 516 to 521 temporarily suspend the processing due to the I / O block.

Here, it is assumed that a new system is constructed by reusing the software of the processes 522 to 535.
At this time, if the software of the system block 502, the system block 503, and the system sub-block 513 is reused, it becomes as shown in FIG. In FIG. 6, 601
Is a system subblock, 602 is a system subblock management process, and 603 to 606 are processes.

In the prior art, processes 522-53
5. A new system management process software must be created to control the total of 18 processes 603 to 606. Further, in the first embodiment, software of a new block system management process for controlling the six processes 534, 535, and 603 to 606 must be created, but in the present embodiment, 603 to 606. All that is required is to create a sub-block system management process 602 that controls the four processes.

Further, in the conventional technique, in order to create the system management process, the newly changed process 603 to
It takes man-hours to learn not only the start / stop method of 606 but also the start / stop method of the processes 522 to 535 to be reused. However, in this embodiment, it is not necessary to learn the method of starting and stopping the processes 522 to 535 to be reused, and it is sufficient to learn the interface between the block system management process 507 and the newly created sub block system management system 602. A new system management device can be created without knowledge of the method of starting and stopping the entire system. In addition, in the first embodiment, 5
The start / stop methods of 34 and 535 must be learned, but this is not necessary in the present embodiment.

As described above, according to the present embodiment, it is possible to easily create a new overall system management process by using a multi-stage hierarchical structure in which sub-blocks are provided in the system block. A system management process can be realized.

Further, in this embodiment, all system blocks are divided into system sub-blocks, but as shown in FIG. 7, the block system management process 702 is not divided into sub-blocks and the block system management process 702 processes 703 to 707.
Even if the system block 701 that directly manages is included, the same effect can be expected.

(Embodiment 3) Next, a third embodiment of the present invention will be described with reference to FIG. In FIG. 8, 801 is the entire system management process, 802 is an application block system management process, and 803-
Reference numeral 809 denotes a group of processes that realizes additional functions such as a bulletin board function, a post office box function, and a broadcast function by a set of communication from the outside and an internal state, 810 is a facsimile communication control block system management process, and processes 811 to 816 are communication from the outside. 817 is a FFEP (Facsi (Facsi)
mile Front End Processor) Control block system management process, 818 to 819 are processes for controlling FFEP by a combination of external communication and internal state, 820 is a device for a computer to send and receive facsimile data through a facsimile and a telephone line. FFEP, 821 is an application block, 822 is a facsimile communication control block, 823 is an FFEP control block, 824
Is a computer, and 825 is an external storage device having a disk medium.

The operation of the system block management device configured as described above will be described. First, before starting the system, the entire system management process 801 and FFE
Only P820 exists. In system activation, first, the overall system management process 801 activates the application block system management process 802, the facsimile communication control block system management process 810, and the FFEP control block system management process 817.

The FFEP control block system management process 817 initializes when started, and the process 81
8 and 819 are activated. Upon activation, the process 818 performs initialization, and sends an initialization completion notification to the FFEP control block system management process 817. The FFEP control block system management process 817 is the process 8
The fact that 18 has been activated is recorded in the external storage device 825.
When the process 819 is started, it initializes and the FFE
An initialization completion notification is sent to the P control block system management process 817. The FFEP control block system management process 817 records in the external storage device 825 that the process 819 has started. The FFEP control block system management process 817 sends an initialization completion notification to the overall system management process 801.

Similarly, when the facsimile communication control block system management process 810 is started, it initializes and starts processes 811 to 816. Upon activation, the process 811 performs initialization and sends an initialization completion notification to the facsimile communication control block system management process 810. The facsimile communication control block system management process 810 records the activation of the process 818 in the external storage device 825. Similarly, the processes 812 to 816 are also activated, and the activation is recorded in the external storage device 825.

Similarly, the application block system management process 802 has processes 803 to 809.
Is activated and the activation is recorded in the external storage device 825.

The system is started up as described above.
At this time, even if the FFEP control block system management process 817 tries to record the activation of the process 818 in the external storage device 825 and it is in an I / O block and the process is temporarily suspended, another block system management process The application block system management process 802 and the facsimile communication control block system management process 810, which are
The process is not suspended. In other words, the processing for system activation is not interrupted temporarily, so the time required for system activation is shortened.

Next, the service activation will be described. The overall system management process 801 issues a service activation request to the application block system management process 802, the facsimile communication control block system management process 810, and the FFEP control block system management process 817. In response to this, the application block system management process 802 receives the process 803.
~ 809 issues a service activation request. In response to this, the process 803 becomes active and returns a service activation response to the application block system management process 802. The application block system management process 802 records in the external storage device 825 that the process 803 is in the operating state. Then process 80
4 is activated, and a service activation response is returned to the application block system management process 802.
Application block system management process 802
Records in the external storage device 825 that the process 804 has been activated. Similarly, processes 805-
The application block system management process 802 records in the external storage device 825 that 809 is in the operating state. The application block system management process 802 returns a service activation response to the overall system management process 801.

Similarly, the facsimile communication control block system management process 810 has processes 811-8.
With 16 as the operating state, the facsimile communication control block system management process 810 records the operating state in the external storage device 825. The facsimile communication control block system management process 810 returns a service activation response to the overall system management process 801.

Similarly, the FFEP control block system management process 817 sets the processes 818 and 819 to the operating state, and the FFEP control block system management process 817 notifies the external storage device 82 that it is in the operating state.
Record at 5. The FFEP control block system management process 817 returns a service activation response to the overall system management process 801.

The service is started as described above.
At this time, similarly to the system startup, the application block system management process 802 tries to record in the external storage device 825 that the process 803 is in the operating state, and the process is suspended in the I / O block, and the process is temporarily suspended. Is another block system management process, which is a facsimile communication control block system management process 8
Since the 10 and FFEP control block system management process 817 are separate processes, the process is not suspended. In other words, the process for starting the service is not temporarily interrupted, so that the time required for starting the service is shortened.

Next, the service stop will be described. The overall system management process 801 issues a service stop request to the application block system management process 802, the facsimile communication control block system management process 810, and the FFEP control block system management process 817. In response to this, the application block system management process 802 receives the process 803.
Issue a service stop request to ~ 809. In response to this, the process 803 enters the service stop state and returns a service stop response to the application block system management process 802. The application block system management process 802 records in the external storage device 825 that the process 803 is in the service stop state.
Next, the process 804 enters the service stop state and returns a service stop response to the application block system management process 802. The application block system management process 802 records in the external storage device 825 that the process 804 is in the service stop state. Similarly, the processes 805 to 809 are in the service stopped state, and the application block system management process 802 records the service stopped state in the external storage device 825. The application block system management process 802 returns a service stop response to the overall system management process 801.

Similarly, the facsimile communication control block system management process 810 includes the processes 811-8.
When the service is stopped at 16, the facsimile communication control block system management process 810 records that the service is stopped in the external storage device 825. Facsimile communication control block system management process 810
Returns a service stop response to the overall system management process 801.

Similarly, the FFEP control block system management process 817 sets the processes 818 and 819 in the service stop state, and the FFEP control block system management process 817 records in the external storage device 825 that the service is stopped. The FFEP control block system management process 817 returns a service stop response to the overall system management process 801.

The service is stopped as described above.
At this time, like the system startup, the application block system management process 802 tries to record in the external storage device 825 that the process 803 is in the service stopped state, and the process is temporarily suspended because it is in the I / O block. However, since the other block system management processes, that is, the facsimile communication control block system management process 810 and the FFEP control block system management process 817 are separate processes, the processing is not suspended. That is, the process for stopping the service is not interrupted temporarily, so that the time required for stopping the service is shortened.

Next, the system stop will be described. First, the overall system management process 801 includes an application block system management process 802, a facsimile communication control block system management process 810, an FF.
A system stop request is issued to the EP control block system management process 817. The FFEP control block system management process 817 issues a system stop request to the processes 818 and 819. Process 819 is FFEP
A system stop response is returned to the control block system management process 817, and the process ends. The FFEP control block system management process 817 is the process 81.
The fact that 9 is completed is recorded in the external storage device 825. The process 818 returns a system stop response to the FFEP control block system management process 817 and terminates the process. The FFEP control block system management process 817 records the completion of the process 818 in the external storage device 825. The FFEP control block system management process 817 is the entire system management process 80.
A system stop response is returned to 1 and the process ends.

Similarly, the facsimile communication control block system management process 810 has processes 811-8.
16 is stopped, and the fact that the process is completed is recorded in the external storage device 825. The facsimile communication control block system management process 810 returns a system stop response to the overall system management process 801, and ends the process.

Similarly, the application block system management process 802 processes the processes 803 to 809.
External storage device 82
Record at 5. The application block system management process 802 returns a system stop response to the overall system management process 801, and ends the process.

The system is stopped as described above.
At this time, similar to the system startup, even if the application block system management process 802 tries to record the termination of the process 803 in the external storage device 825 and the process is suspended in the I / O block and the process is temporarily interrupted, Facsimile communication control block system management process 810 and FFEP control block system management process 817 which are block system management processes of
Is a separate process, processing is not suspended. In other words, the processing for stopping the system is not interrupted temporarily, so that the time required for stopping the system is shortened.

Here, the software of the processes 811 to 819 is reused to construct a new application block as shown in FIG. In FIG. 9, 901
Is a new application block, 902 is a new application block system management process, 903
˜909 are processes for realizing new additional functions.

If such a system is reconstructed by the conventional technique, processes 811 to 816, 818, and 819 are obtained.
And software of a new system management process for controlling the start and stop of the entire 15 processes 903 to 909 had to be created, but in this embodiment, a block for controlling the seven processes 903 to 909 is provided. All that is required is to create the software for the system management process 902.

Further, according to the conventional technique, in order to create the system management process, the newly changed process 903-
It takes man-hours to learn not only the method of starting and stopping 909 but also the method of starting and stopping the processes 811 to 816, 818, and 819 to be reused. However, in this embodiment, the processes 811 to 816, 818, 81 to be reused are reused.
It is not necessary to learn the startup / shutdown method of 9 and it is sufficient to learn only the interface between the whole system management process 801 and the newly created block system management system 902. A system management device can be created.

As described above, according to this embodiment, the block system management process 8 for managing a process in which a plurality of processes constructing the system are divided into blocks.
21-823 and the block system management process 821
~ Overall system management process 80 for managing 823
By providing No. 1, when a system that reuses the process software is newly created, the system block software including the process and the block system management process is reused to start and stop all processes. It is not necessary to create the software for the management process, and only the software for the block system management process of the newly used process may be created.

That is, in the case of reusing a part of the software of the existing facsimile communication system to create a new facsimile communication system, the block system management for activating and stopping the processes in the block whose number is smaller than the number of processes of the entire system Since only the process software needs to be created, it is possible to realize an excellent system management device that can easily create a new facsimile communication system.

Further, although FIG. 9 shows the embodiment in which all the processes of the application block are replaced, when adding the process to the application block, it is sufficient to recreate the software of the application block system management process. The same effect can be expected. The same effect can be expected when deleting a process.

Further, in FIG. 8 of this embodiment, the application block system management process 802 uses the bulletin board function, the post office box function, the combination of the communication from the outside and the internal state.
Process group 803 to realize additional functions such as broadcast function
I described the case of a process independent of 809,
As shown in FIG. 10, an application block 1 that performs a predetermined behavior according to a set of communication from the outside and an internal state.
001 has the function of an application block system management process, and the process group 803-80
The same effect can be expected when starting and stopping 8, 1002, recording the process state or the system state, and the like.

Similarly, as shown in FIG. 11, the facsimile communication control block 1101 which performs a predetermined behavior according to the set of the communication from the outside and the internal state also has the function of the facsimile communication block system management process. The same effect can be expected when starting and stopping the groups 812 to 816 and 1101 and recording the process state and the system state.

Further, similarly, as shown in FIG. 12, the FFEP control block 1201 which performs a predetermined behavior according to the set of the communication from the outside and the internal state has the function of the FFEP control block system management process, and the process group 819. The same effect can be expected when starting and stopping 1201 to 1201 and recording the process state and the system state.

[0063]

As described above, the present invention provides a block system management process for managing a process in which a plurality of processes constructing a system are divided into blocks, and an overall system management process for managing the block system management process. By creating a new system that reuses the process software, it is easy to create a new overall system management process by reusing the system block software including the process and block system management process. And prevent delays due to disk I / O blocks,
It is possible to realize an excellent system management device that can fully utilize the capacity of a computer.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of a system management device according to a first embodiment of the present invention.

FIG. 2 is a block diagram showing a schematic configuration for explaining a new system construction in the first embodiment.

FIG. 3 is a block diagram showing a schematic configuration for explaining a new system construction in the first embodiment.

FIG. 4 is a block diagram showing a schematic configuration of another system management apparatus according to the first embodiment of the present invention.

FIG. 5 is a block diagram showing a schematic configuration of a system management device according to a second embodiment of the present invention.

FIG. 6 is a block diagram showing a schematic configuration for explaining a new system construction in the second embodiment.

FIG. 7 is a block diagram showing a schematic configuration of another system management device according to the second embodiment of the present invention.

FIG. 8 is a block diagram showing a schematic configuration of a system management device according to a third embodiment of the present invention.

FIG. 9 is a block diagram showing a schematic configuration for explaining a new system construction in a third embodiment.

FIG. 10 is a block diagram showing a schematic configuration of another system management device according to the third embodiment of the present invention.

FIG. 11 is a block diagram showing a schematic configuration of another system management device according to the third embodiment of the present invention.

FIG. 12 is a block diagram showing a schematic configuration of another system management apparatus according to the third embodiment of the present invention.

FIG. 13 is a block diagram showing a schematic configuration of a conventional system management device.

FIG. 14 is a block diagram showing a schematic configuration for explaining a conventional new system construction.

[Explanation of symbols]

101 Overall System Management Process 102-104 System Block 105-107 Block System Management Process 108-114 Process 115 Computer 116 External Storage Device 201 System Block 202 Block System Management Process 203-206 Process 301 Block System Management Process 302-303 Process 401 Block Process having system management process functions 501 Overall system management process 502 to 504 System block 505 to 507 Block system management process 508 to 514 System sub block 515 to 521 Sub block System management process 522 to 538 process 539 Computer 540 External storage Equipment 601 System sub-block 602 Sub-block system pipe Physical process 603 to 606 process 701 System block 702 Block system management process 703 to 707 process 801 Overall system management process 802 Application block system management process 803 to 809 Process group 810 Facsimile communication control block system management process 811 to 816 Process group 817 FFEP control Block system management process 818 to 819 process group 820 FFEP 821 application block 822 facsimile communication control block 823 FFEP control block 824 computer 825 external storage device 901 application block 902 application block system management process 903 to 909 process group 1001 application block system Application block 1101 having a function of a management process Facsimile communication block Facsimile communication control block having a function of a system management process 1201 FFEP control block FFEP control block having a function of a system management process 1301 Application block system management process 1302 ~ 1308 Process 1309 Computer 1310 External Storage Device 1401 System Management Process 1402-1405 Process

Claims (7)

[Claims] 1. A system-wide state monitor and a system-wide system in which a plurality of processes, each of which performs a predetermined behavior according to a set of communication from the outside and an internal state, are gathered to perform a process cooperatively while performing inter-process communication. In a system management device that performs state transition of the system, the system is divided into several blocks according to functions, and a block system management process that manages processes in each block, and an overall system management process that manages the block system management process are provided. System management equipment. 2. The system management device according to claim 1, wherein the block system management process manages a sub-block system management process that manages a process divided into sub-blocks. 3. The system according to claim 1, wherein the block system management process is not an independent process, and one of a plurality of processes which the block system management process starts and stops has a function of the block system management process. Management device. 4. A computer, F, which is a device for transmitting and receiving facsimile data through a facsimile and a telephone line.
FFE and FFE by the combination of external communication and internal state
A process group that controls P, a process group that controls the communication order of facsimile communication by a set of external communication and internal state, and a bulletin board function, a post office box function, and a broadcast by a set of external communication and internal state. A FFEP control block system management process that is used in a facsimile communication system having a process group that realizes an additional function such as a function, and that monitors the process state of the process group that controls the FFEP and performs state transitions such as starting and stopping; Facsimile communication block system management process that monitors the process status of the process group that controls facsimile communication and performs state transitions such as start and stop, and process transitions such as process state monitoring and start and stop of process groups that implement additional functions Application block system management process When the FFEP control block administration process, facsimile communication block system management device that includes a system-wide management process for performing start and stop of the administration process and application block administration process. 5. The FFEP control block system management process has a function which is performed by one of the processes forming a process group for controlling the FFEP.
The system management device described in. 6. The system management apparatus according to claim 4, wherein one of the processes forming a process group for controlling facsimile communication performs the function of the facsimile communication block system management process. 7. The system management apparatus according to claim 4, wherein one of the processes forming a process group that realizes an additional function performs the function of the application block system management process.