JPH1097413A - Software maintenance method of distributed processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software execution environment in which software modification work is efficiently carried out with it managed by holding structure management information in every device, performing generation management, also having structure management information on each processor and performing software loading with a processor mutually collated with and diagnosed. SOLUTION: When an input-output management part 5008 detects that an identifier indicating structure management information is added to data 5028 which is signaled on a common transmission medium, it delivers data to a structure management part 5014. The part 5014 collates it with the generation number and stores receiving data in a structure management file 5018 when it does not coincide with the generation number, and updates the generation of structure management information. When the device number of its own does not coincides with the one that is added to the data 5028 or when the generation number of the structure management file of its own device coincides with the one of the structure management information that is added to the receiving data, the part 5008 cancels the receiving of the data 5028.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a software configuration management, generation management, and diagnosis method in a distributed processing system.

[0002]

2. Description of the Related Art Conventionally, in a configuration management method of a distributed processing system, a master of software resources distributed to each processing device is centrally managed to manage the generation and configuration of software. Furthermore, when software of a distributed processing system is modified, a test (degradation test) is performed to measure the function degradation and performance degradation of a non-changed part when updating a specific function or data generation. The same input pattern was given to the system before and after, and the function and performance of the non-changed part were compared. In the conventional method, it was necessary to create two types of systems before and after the refurbishment and to perform the test a plurality of times, thus reducing the test efficiency.

[0003]

In the software configuration management method as described in the above-mentioned prior art, the number of processing devices to be managed and the number of configuration software become enormous, and the software loaded into each processing device becomes large. In a distributed processing system having different configurations and generations, it is difficult to centrally manage the software configurations and generations of all devices. Further, when the unit of correction at the time of software correction is diversified to the whole apparatus, function, and data unit, the unit of generation management becomes complicated, and it is difficult to perform generation management. Also,
It has been inconvenient that it is difficult to grasp and diagnose the relationship of software between multiple devices. Furthermore, since the functions and data of different generations before and after the repair could not be executed in a multiplex manner as in the above-mentioned function degeneration test, the degeneration test is performed under completely equivalent conditions in the test environment other than the input pattern. There was a problem that things could not be done.

SUMMARY OF THE INVENTION An object of the present invention is to provide a distributed processing system in which functions and data of the same name but of different generations are executed in a multiplex manner, while performing the configuration management of software modification work.
An object of the present invention is to realize a software execution environment for efficiently and without error.

[0005]

In order to achieve the above object,
In the software configuration management method according to the present invention, configuration management information is provided for each device, generation management is performed for each device, function unit, and data unit, and configuration management information for each device is held by each processing device. Perform software loading while checking and diagnosing each other. Further, when the generation of software is updated, the above-mentioned problem is solved by executing functions and data of a plurality of generations in different areas for each generation.

According to the present invention, each processing device notifies its own device number, software configuration information in its own device, and generation information added to the configuration information, and another processing device relates to its own device. Select and collect software configuration information,
After comparing, collating and diagnosing with the software configuration information managed in the own device, loading the relevant software to the corresponding processing device based on the diagnosis result, so that the software configuration management information and generation information Is performed. Furthermore, by assigning different execution areas to each generation and performing multiple functions and data groups of the different generations and related functions and data groups in the execution area of the corresponding generation, the function degradation test of the non-changed part is performed. In an equivalent execution environment.

[0007]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram showing the overall configuration of a distributed processing system to which the present invention is applied. In FIG.
Reference numerals 11, 12, 13, 14, 15, and 16 denote processing devices that store application modules for achieving predetermined processing in a memory provided therein and execute them. 20 is a common transmission medium. Each processing device 11-16 is connected to a common transmission medium 20,
Messages are mutually transmitted and received via the common transmission medium.

[0009] Addresses are given to the processing units 11-16 as identifiers that enable each to be distinguished from others.
FIG. 2 shows a format of data transmitted via the common transmission medium 20. 201 and 206 are flags indicating the beginning and end of the message, respectively. 202 is an identifier indicating configuration management information, 203 is a device number, and each processing device 11-16 connected to the common transmission medium 20 has a device number stored in its own device based on the identifier and the device number. If they are the same, data is received in the own device. Reference numeral 204 denotes generation information of the configuration management information of the entire apparatus. The generation information 204 is managed independently for each device, and the generation number is updated. When the generation number 204 of the received data is different from the generation of the configuration management information managed in the own device, each of the processing devices 11 to 16 loads the data into the own device. 205 is configuration management information. FIG. 3 shows FIG.
2 shows the contents of the configuration management information indicated by 205. 301
Are classified for each function of the software constituting the device, and the name and generation are recorded. Reference numeral 302 denotes data constituting each function, a module name, a generation, and an attribute. Reference numeral 303 stores the name of each source code, the source code constituting the module, and the generation. The configuration management information in FIG. 3 includes the device numbers 203 and 204 in FIG.
Generation information of the entire configuration management information is added and stored in each processing device.

FIG. 4 is a configuration diagram showing a logical configuration of each processing device. 4001 is a common transmission medium. 4002
Is a processing unit coupled to the common transmission medium. 400
Reference numeral 3 denotes an input / output management unit, and reference numeral 4007 denotes configuration management information of software registered in each device. When the input / output management unit receives the data broadcast on the common transmission medium and determines from the transmission / reception data management table 4004 that the identifier added to the data is the configuration management information, the input / output management unit receives the received data from the configuration management unit. hand over. The generation of the configuration management information collected from the common transmission medium is compared with the generation of the configuration management information in the own device.

As a result of the comparison, the first of the received configuration management information
When the second generation and the second generation of the configuration management information stored in the own device are different, the configuration management information of the first and second generations is compared and collated. Reference numeral 4005 denotes a switching object storage file. The switching object storage file stores a registration object of the software to be newly registered, a registration procedure file, and generation management information. 4
006 is a recovery object storage file. The recovery object storage file stores an old generation registration object, a registration procedure file, and generation information of software to be newly registered. Reference numeral 4007 denotes a configuration management file. The configuration management file 4007 records the names, generations, attributes, and configurations of software registered in the own device. Reference numeral 4008 denotes a program registration function. In the program registration function, the switching / restoration registration procedure file is started, and the software 4010 is registered. When the software 4010 is registered, the configuration management information of the software 4010 to be registered is registered in the configuration management file 4007. Reference numeral 4009 denotes a configuration management unit. The configuration management unit converts the generation of the configuration management information and the configuration management information stored in its own device into a data format that is broadcast to the common transmission medium, passes the data format to the input / output management unit 4003, and the input / output management unit 4003 The message is broadcast to the common transmission medium 4001. Reference numeral 4011 denotes a program management unit. The program management unit stores the switching / restoration object file, the switching procedure file, and the generation information received by the input / output management unit in the switching / restoration object storage file.

As a first embodiment, a configuration management method at the time of software switching will be described. 5001-500
6 is a processing device coupled to the common transmission medium 5029. 5
Reference numerals 007 to 5012 denote input / output management units in each processing device. 5018 to 5022 are configuration management units in each processing device. Reference numerals 5018 to 5021 denote configuration management files stored in each processing device. Reference numerals 5022 to 5025 denote operation terminals of the respective processing devices. 5030 to 5033 are switching / restoration object storage files. 5013 to 501
7 indicates data on the common transmission medium 5029. The configuration management unit 5021 in the processing device 5006
25, or when activated by an activation message notified from another processing device, the configuration management information stored in the configuration management file 5021 is passed to the input / output management unit 5012, and the target device number, After the generation number of the configuration management information is added, it is notified to the common transmission medium 5029.
It notifies above (5028). When detecting that the identifier indicating the configuration management information is added to the data 5028 broadcast on the common transmission medium, the input / output management unit 5008 in the processing device 5002 transfers the data to the configuration management unit 5014. The configuration management unit 5014 checks the generation number of the configuration management information stored in the configuration management file 5018 of the internal device 5002 with the generation number of the configuration management information added to the reception data 5028, and when the generation numbers are different, the The data is stored in the configuration management file 5018, and the generation of the configuration management information is updated. When the own device number does not match the device number added to the data 5028 on the common transmission medium,
Alternatively, when the generation number of the configuration management information stored in the configuration management file of the own device matches the generation number of the configuration management information added to the received data, as shown in the input / output management unit 5010 in the processing device 5004, The reception of the data 5028 on the common transmission medium is discarded.

The configuration management unit 5014 of the processing device 5002 that has received the configuration management information 5028 stores the first-generation configuration management information stored in its own device and the common transmission medium 50.
Second-generation configuration management information 5028 newly received from 29
After that, the change information 5026 is notified to the common transmission medium 5029. Upon receiving the change information 5026, the configuration management unit 5017 in the processing device 5006 changes the switching / restoration object storage file 5030 in the own device.
Of the load object of the software recorded in the change information 5028 is searched. If all load objects recorded in the change information 5028 exist in the switching / restoring object storage file, the change (for switching / restoring) is performed on the corresponding device 5002.
The corresponding device number is added to the object, the switching / restoration procedure file, and the generation information, and transmitted to the common transmission medium 5029 (5027).

An input / output management unit 500 in the processing device 5002
8 receives the data 5027 on the common transmission medium,
The device number added to the data 5027 is compared with its own device number, and if it is the same as the own device number, the data 5027 is received. The received switching / restoration object file, switching / restoration procedure file, and generation information are stored in the switching / restoration object storage file 5033.

The processing device 5002 includes an operation terminal 5022,
Alternatively, a program registration function is activated by a switching / restoring instruction from another processing device, and program loading is performed.

FIG. 6 shows the processing of the input / output data management unit in each processing device. When the data is broadcast on the common transmission medium, the input / output management unit is activated to start the receiving process (6).
001). The input / output management unit receives the message on the common transmission medium (6002), and determines the type of the received message from the transmission / reception data management table (6003). If the program ID corresponding to the data identification code added to the message received from the common transmission medium is not registered in the received data management table, the received data is discarded (6004).

The program I corresponding to the data identification code
When D is registered in the reception data management table,
The received data is transferred to the corresponding program (6009).
When the received data is the configuration management data (6006), the configuration management unit is started (6007) and the received data is transferred.

FIG. 7 shows the contents of the message management table. The input / output management unit performs selective reception of data on the common transmission medium as described below using the identifier 7001 and the program IDs 7002 and 7003 indicating the contents of data recorded in the message management table.

Reference numeral 7001 denotes an identifier indicating the content of data added to the message broadcast on the common transmission medium. 7002 is a program ID for receiving each data shown in 7001. When receiving the message from the common transmission medium, the input / output management unit reads the identifier added to the received message, searches the message management table for the MID, and acquires the reception program ID. 70
03 is a program ID for transmitting each data. When the application program transmits data to the common transmission medium, the input / output management unit is activated, and adds an identifier indicating the content of the data to the transmission message.

FIG. 8 shows a process of transmitting the configuration management information.
The configuration management unit creates configuration management information from the configuration management file (8001), and adds its own device number and the generation number of the configuration management information to the configuration management information (8002). When the configuration management unit issues a data transmission command to the common transmission medium, the input / output management unit is activated and starts transmission processing (800
3). The input / output management unit sets transmission data (configuration management information) in the input / output data storage area (8004). The input / output management unit adds an identifier indicating the configuration management information recorded in the message management table to the configuration management information in the input / output data storage area (8005), and transmits the configuration management information to the common transmission medium. (8006).

FIG. 9 shows a comparison and diagnosis process of the configuration management information in the configuration management unit. When the input / output management unit receives the configuration management information from the common transmission medium, it starts the configuration management unit (9001). The type of the received configuration management information is determined (9002). If the received data is configuration management information,
The device number of the received data is compared with its own device number (9003). If the device numbers match, the generation number of the received configuration management information is compared with the generation number of the configuration management information of the configuration management information stored in the own device (900).
4). When the first generation number of the configuration management information already stored in the configuration management file in the own device is different from the second generation number of the received data, the configuration management information of two different generations is compared and compared, and the difference is determined. A collation result file is created (9005). Notification of the difference result to the common transmission medium (9
006), and ends the configuration management information comparison and diagnosis processing (9007).

FIG. 10 shows a process when the received data is determined to be the result of the difference comparison of the configuration management information in the configuration management information type determination (9002). The software name and generation of the change are read (1001). A search is made as to whether the name corresponding to the change, the software object of the generation, the switching information, and the generation information are present in the switching / restoration object storage file (1002). If the object file exists, a name corresponding to the change, an object file of the software of the generation, a switching procedure file, and generation information are created (1003).

The created object, switching procedure file, and generation information are notified to the common transmission medium (1004), and the processing is terminated (1005).

FIG. 11 shows a process of receiving the switching / restoration file. The received data is a switching / restoring file (switching / restoring object file, switching procedure file, generation information) based on the identifier added to the data notified to the common transmission medium by the input / output management unit of each processing device. Is determined, the data on the common transmission medium is received (1100).
1) Activate the program management function and transfer the received data. In the program management function, the device number added to the received file is compared with its own device number (110).
02). If the collation results match, the generation number of the switched configuration management information added to the received file is collated with the generation number of the configuration management file in the own device (11003).
If the results match, the switching / restoring object, the procedure file, and the generation information are stored in the switching / restoring object storage file (11004).

FIG. 12 shows a program registration process. The program registration function is activated by the switching instruction information from the operation terminal or another device (12001). When the program registration function is activated, the switching procedure file is executed (12002). The execution path of the loading command is changed to the dummy loading command storage directory in the switching procedure file (12003). When the loading command is activated in the switching procedure file,
A dummy loading command is activated in place of the actual loading command (12004). The actual loading command is activated in the activated dummy loading command (12005). The loading result of the actual loading command is normal (no loading error)
In the case of (1), the configuration management information of the program is recorded in the configuration management file (12007), and the processing of the dummy loading command ends (12008). When the actual loading command ends abnormally, the configuration management information is not recorded.
The processing of the dummy loading command ends. When the program loading process ends in the switching procedure file, the execution log of the switching procedure file is stored in a log file (12009), and the execution of the switching procedure file ends (12010). When the execution of the switching procedure file is completed, the program management function notifies loading result information (configuration management information and loading result log) to the common transmission medium (12011), and ends the program registration function (12012).

FIG. 13 shows a processing flow of the program registration function. Reference numeral 13001 denotes a program registration processing flow in the program management function. When the program registration function is activated, the execution environment of the registration command (loading command) executed in the switching procedure file is changed (13002). The execution environment is changed by changing the execution path to the directory where the actual loading command is stored to the execution path to the directory where the pseudo loading command is stored. 13
At 003, a switching procedure file is started.

When the switching procedure file is executed, the loading command described in the switching procedure file is executed. Since the execution path of the loading command has been changed to the execution path of the pseudo loading command by the process 13002, the pseudo loading command is activated.

Reference numeral 13005 denotes a processing flow of the pseudo loading command. When the pseudo loading command is activated, the actual loading command (1
3010) is executed. At 13007, the execution result of the actual loading command is determined. If successful,
The generation information of the loaded software is recorded in the configuration management file (FIG. 14, 14009) (1300).
8). In the case of abnormal termination, recording in the configuration management file is not performed. At 13009, the software loading result is stored in the loading result information file (140 in FIG. 14).
08), the execution log (14011 in FIG. 14) of the switching procedure file is collected in 13004, and the program registration process ends.

FIG. 15 shows an outline of the degeneration test at the time of generation update. Reference numerals 15001 to 15005 denote common transmission media 1500.
A processing unit coupled to 6; The processing devices 15001 include modules M1 (15014) to Mn (1501) before repair.
5), data files F1 (15018) to F before repair
n (15019) is being executed in the execution area 15010. Reference numeral 15012 denotes an input / output management unit in the processing device 15001, which transfers input data 15007 to the data file F1 (150118),
The generation number of the processing group is added to the processing result data in (15019) to the message (204 in FIG. 2) and output to the common transmission path (15008). In the processing device 15002, the data file F1 ′ (1
5020) and a module M1 (15
016) to Mn (15017) and Fn (1502)
1) is installed and executed in the area 15011. The input / output management unit 15013 inputs the same data 15007 as the old-generation processing device before the repair, records the data in F1 ′, and adds the processing group generation number to the processing result data recorded in the data file Fn. , And outputs it to the common transmission medium (15009).

In the processing devices 15003 to 150005,
The transmission data (15008, 1
Selective reception is performed based on the generation information added to 5009). The input / output management units of the processing devices 15003 to 15005 receive the data output on the common transmission medium, and determine that the identifier added to the data is the configuration management information using the transmission / reception data management table (4004 in FIG. 4). Then, the received data is transferred to the configuration management unit. The generation of the configuration management information collected from the common transmission medium is compared with the generation of the configuration management information in the own device. As a result of the comparison, the first generation of the received configuration management information is stored in the own device. When the second generation of the configuration management information is different, the configuration management information of the first and second generations is compared and collated, and the updated function or data name and generation are displayed.

If the received data is other than the configuration management data, the data is received in a different area for each generation information added to the received data (15022, 15023).

[0032]

According to the software configuration management method of the present invention, the number of processing devices to be managed and the number of configuration software become enormous, and the distributed processing system with different software configurations and different generations loaded on each processing device. Then
It is easy to manage the software configurations and generations of all devices. Furthermore, even when the software modification unit is diversified to the entire apparatus, function, program / data unit, the configuration management of different units is facilitated by hierarchically grouping and managing the software configuration and generation. . It has configuration management information for each device, performs generation management for each device, function, and program / data, and has configuration management information for each device on both the management device and each processing device side, and checks each other. The above problem is solved by performing software maintenance while diagnosing. Furthermore, since modules are executed in different areas for each generation and a data file is created for each generation, multiplex execution of modules of different generations performed at the time of function modification can be performed without affecting other generations.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the overall configuration of a distributed processing system.

FIG. 2 shows a format of data transmitted through a common transmission medium 20.

FIG. 3 shows the contents of configuration management information indicated by 205 in FIG. 2;

FIG. 4 is a configuration diagram showing a logical configuration of each processing device.

FIG. 5 is a diagram showing an outline of notification of configuration management information, collation, and program loading.

FIG. 6 is a diagram showing processing of an input / output data management unit in each processing device.

FIG. 7 shows the contents of a message management table.

FIG. 8 shows processing of an input / output data management unit in each processing device.

FIG. 9 is a diagram illustrating comparison and diagnosis processing of configuration management information in a configuration management unit.

FIG. 10 shows a process when the received data is determined to be the result of the difference comparison of the configuration management information.

FIG. 11 is a diagram showing a switching / recovery file receiving process.

FIG. 12 is a diagram showing a program registration process.

FIG. 13 is a view showing a pseudo command activation process of the program management unit.

FIG. 14 is a diagram showing a loading result information file.

FIG. 15 is a diagram showing an outline of a degeneration test at the time of generation update.

[Explanation of symbols]

11, 12, 13, 14, 15, 16 Processing device 20 Common transmission medium 201, 206 Flag indicating start and end of message 202 Identifier indicating configuration management information 203 Device number 204 Generation information of configuration management information of entire processing device 205 Configuration management information 301 Names of functions of software configuring the device, generation 302 Data names configuring each function, names of modules,
Generation, attribute 303 Each data, name of source code constituting module, generation 4001 Common transmission medium 4002 Processing device coupled to common transmission medium 4003 Input / output management unit 4007 Configuration management information of software registered in each device 4004 transmission / reception data management table 4005 switching object storage file 4006 recovery object storage file 4007 configuration management file 4008 program registration function 4010 software 4009 configuration management unit 4011 program management units 5001 to 5006, processing devices 5007 to 5012 Input / output management units 5018 to 5022 Configuration management units 5018 to 5021 in each processing device Configuration management files 5022 to 5025 stored in each processing device Operation terminal 503 of each processing device ～5033 switching / recovery storing objects files 5013-5017 common transmission medium 5029 Ueno data 5006 configuration management unit 5029 common transmission medium

Claims (6)

[Claims] In a distributed processing system comprising a plurality of processing units coupled to a common transmission medium and having the same name but different generations of software modules arranged in the plurality of processing units, each of which is executed in a multiplex manner, The processing device sends the message to the common transmission medium as a message obtained by adding a predetermined code to the generation information of the module group executed in the device itself and the data group processed by each module group, and performs other processing. The device has an input / output management unit that selects and collects a module group, a data group name, and generation information based on the code from the common transmission medium based on the code, and a generation managed in the own device. When a module group or data group of a different generation is received, it is arranged in a different area for each generation, and processing is performed. Theft software module execution method. 2. In a distributed processing system comprising a common transmission medium and a plurality of processing apparatuses mutually connected via the common transmission medium, each processing apparatus includes software configuration information in its own apparatus, The information is transmitted to the common transmission medium as a message in which a predetermined code is added to the generation information added to the information, and another processing device executes software related to the own device based on the code from the common transmission medium. It has an input / output management unit for selecting and collecting configuration information, and an arbitrary processing device selects, collects, and displays first generation software configuration information transmitted from each processing device, and is managed in its own device. After performing comparison, collation, and diagnosis with software configuration information of a second generation different from the first generation, registration of the corresponding software based on the diagnosis result is performed for the corresponding processing device. Software configuration management methods to. 3. The software module execution method according to claim 1, wherein when the generation update of the specific module group and the data group is performed by the software configuration management method according to claim 2, the update before the update is performed. The execution area of the first generation and the second generation after the update are divided, and the module and data group associated with each generation are divided into the execution areas of the corresponding generation and are multiplex-executed. A software module diagnosis method characterized by comparing and comparing the function and performance of the module of the non-changeable part based on the comparison and collation result of the software configuration management information. 4. A software registration method in a computer system, comprising: a registration procedure description section for describing a registration procedure for executing software registration; and a registration execution section for activating the registration procedure description section. A software registration method that, when the registration execution unit is activated, executes a pseudo registration process having the same name as the actual registration process described in the registration procedure description unit and different from the actual registration process. 5. In the software registration method according to claim 4, when the pseudo registration processing is executed, the actual registration processing is executed in the pseudo registration processing, and the end result of the actual registration processing is provided. A software registration method characterized in that the configuration management information of the software for which the registration processing has been performed is recorded only when is normal. 6. The software registration method according to claim 4, wherein when the pseudo registration processing is executed, the software is generated in an execution environment different from the real environment. Software registration method.