JPH0566935A - Information processing system - Google Patents

Abstract

PURPOSE:To prevent the misapplication of a patch file in an information processing system even if plural program producers or an outsider performs the control between a load module file and the patch file. CONSTITUTION:An input device 10 stores an input file consisting of a load module file name and a patch file name. A CPU 20 includes a control means 41, an input means 42, a production date acquiring means 43, two production date storage memories 44 and 45, a comparison means 46, and an output means 47. Then the means 46 compares the date and time of production of the load module file stored in the memory 44 with that of the patch file stored in the memory 45. Thus the matching property is decided between the load module file and the patch file.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing system, and more particularly to an information processing system in which a patch file storing program correction data and a program file are simultaneously stored.

[0002]

2. Description of the Related Art Conventionally, as shown in FIG. 10, an information processing system of this type has a central processing unit 20 for controlling the entire system, an external storage unit 30 for storing various information to be described later, and a central processing unit. It is composed of an input device 10 for inputting data to the device 20, a display device 11 for displaying a result of starting and ending a program, an output device 40 for outputting a processing result, and a time device 50.
Here, the central processing unit 20 stores an operating system 21 that controls all programs, and the operating system 21 stores various information in the external storage device 30.

When the external storage device 30 is a magnetic disk device, the following information is stored in the external storage device 30. (1) Volume Label 31 As shown in FIG.
The label information 31 ₁ and the file directory start position 31 ₂ are included. (2) File directory 32 As shown in FIG. 11B, the file directory 32 includes a file name 32 ₁ , a file start position 32 ₂ and a creation date and time 32 _{3 of} each data file 36 stored in the file group 33. Consists of. (3) File Group 33 As shown in FIG. 11C, the file group 33 includes a load module file 34, a patch file 35, a source file 36, a modified load module file 37, various data files 38, and the like. Here, the patch file 35 stores the program correction data, and the modified load module file 37 is the load module file 34 modified by the patch file 35.

Next, an example of the procedure from the creation of the source file 36 to the program release in this information system will be described with reference to the flowchart shown in FIG.

The program creator creates the source file 36 (step F1). An object module file is created by compiling the source file 36 (step F2), and then a load module file 34 is created by linking the object module file and the library file (step F3). The load module file 34 is evaluated (step F4), and it is determined whether it is a pass or a fail (step F5). If the determination is successful, the program is released (step F11), and the process ends. On the other hand, if the determination is unsuccessful, it is determined whether or not the source program 36 is modified (step F
6) If the source program 36 is to be modified, the process returns to the step F1 for creating the source file 36, and the procedure from the beginning is repeated. On the other hand, the source program 3
When the modification of 6 is not performed, the program creator creates the patch file 35 used to modify the load module file 34 (step F7). After that, the patch module 35 is used to modify the load module file 34 by using a patch tool to create a modified load module file 37 (step F8). The modified load module file 37 is evaluated (step F9), and it is determined whether the file has passed or failed (step F10). If the determination is successful, the program is released (step F11), and the process ends. On the other hand, if the determination is unsuccessful, the process returns to step F6 and the subsequent steps are repeated.

[0006]

However, in the above-described conventional information processing system, there is no problem if one program creator manages the load module file 34 and the patch file 35, but there is no problem. When the program creator or a third party manages this, it may cause a problem that the patch file 35 is erroneously applied. As a specific example of this problem, a case where two program creators A and B jointly create the load module file 34 will be described below.

As a result of evaluating the load module file 34 jointly created by the two program creators A and B (see step F4 in FIG. 12), the result is unsuccessful, and one program creator A creates the patch file 35 as the patch file 35. After creating the modified load module file 37 using the patch tool (see step F8 in the figure), the evaluation judgment of the modified load module file 37 is passed, and after the program is released, this program creator A loads the source program 36 and the load program. It is assumed that the module file 34 is recreated and the above-mentioned patch file 35 becomes unnecessary.
After that, a problem occurs in the modified load module file 37 released by the program, and the other program creator B
Is responsible for the correction, and when the patch file 35 is used for the correction, the other patch file 35 ₁ created by the program creator B and the patch file 35 created by the other program creator A and the patch tool 35 When the modified load module file 37 is recreated by using and, the program creator A on one side has previously created the load module file 34. Therefore, the evaluation of the modified load module file 37 in steps F9 and F10 of FIG. However, there is a problem in that wasted time is wasted in clarifying the cause.

An object of the present invention is to provide an information processing system capable of preventing erroneous application of a patch file even if a plurality of program creators or third parties manage the load module file and the patch file. ..

[0009]

An information processing system according to the present invention includes a central processing unit having an operating system, an external storage device, an input device, and an output device.
The external storage device stores a source file, a load module file, a patch file, a modified load module file, and a file directory that stores creation dates and times of these files, and the central processing unit stores the source file. The load module file from the patch module, the patch file is created when the evaluation of the source file by the load module file is unsuccessful, the modified load module file is created from the patch file, and the modified load is created. In an information processing system for evaluating the source file by a module file, the input device stores an input file consisting of a load module file name and a patch file name, and the central processing unit has a control means and the input file. To Input means for reading out the load module file name and the patch file name to the control means, and reading the file directory from the external storage device for creating the load module file and the patch A creation date and time obtaining means for outputting the creation date and time of the file to the control means; a creation date and time storage memory for storing the creation date and time of the load module file and the patch file creation date inputted to the control means; Comparing the creation date and time of the load module file stored in the date and time storage memory with the creation date and time of the patch file, and comparing the result of the comparison to the control means, a message input from the control means. Output means for outputting to the output device.

[0010]

The information processing system of the present invention compares the creation date and time of the load module file stored in the creation date and time storage memory with the creation date and time of the patch file by the comparing means, thereby determining whether or not the load module file and the patch file are different. The match can be easily detected.

[0011]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a schematic configuration diagram showing an embodiment of an information processing system of the present invention.

In the information processing system of this embodiment, the input device 10 stores an input file 12 (see FIG. 8) consisting of a load module file name 12 ₁ and a patch file name 12 _2, and the central processing unit 20 Control means 41,
The input file 12 is read from the input device 10, the load module file name 12 ₁ and the patch file name 12 ₂ are output to the control means 41, and the file directory 32 is read from the external storage device 30 and the load module file is read. 34 date of creation 32 ₃ and creating a patch file 35 dates 32 ₃ control unit 4
Creation date / time acquisition means 43 for outputting to 1 and creation date / time 3 of the load module file 34 input to the control means 41
2 ₃ and two creation creation date 32 ₃ are respectively stored in the patch file 35 date and time storage memory 44, 45
When a comparison means 46 which compares the creation date and time 32 ₃ creation date 32 ₃ and patch file 35 of the load module file stored in the created date and time storage memory 44 and 45, and outputs the result of the comparison to the control means 41 10 is different from the conventional information processing system shown in FIG. 10 in that it includes an output unit 47 that outputs a message input from the control unit 41 to the output device 40.

Next, the operation of the information processing system of this embodiment will be described with reference to the flow charts shown in FIGS.

The procedure from the creation of the source file 36 to the program release in the information system of this embodiment is performed according to the flow chart shown in FIG.
The conventional information processing system shown in FIG. 12 is that the determination shown in step F20, that is, the matching determination between the patch file 35 created in step F7 and the load module file 34 created by the compiler shown in step F2 is performed. Different from the procedure in. Hereafter, step F20
The determination shown in will be described in detail.

As shown in FIG. 8, an input file 12 including a load module file name 12 ₁ and a patch file name 12 ₂ is prepared in the input device 10, and the input file 12 is displayed from the display device 11. By designating, a start instruction is given. The operating system 21 uses the input file 1 input from the input device 10.
The control means 41 is started using the name of 2 as a start parameter.

The activated control means 41 operates according to the flow charts shown in FIGS. That is,
First, after setting the input file name from the start parameters (step A1), the input file 12 is opened (step A2), and the result is judged (step A3).
If is successful, the input means 42 is called (step A4).

According to the flow chart shown in FIG. 4, the input means 42 inputs data for one record from the input device 10 (step B1) and determines whether or not the data is normally input (step B2). When it is determined that the data has been normally input, the record length is substituted for the input data length (step B3), and then the return value is "0".
Is substituted (step B4), and the process ends. on the other hand,
If it is determined in step B2 that the data has been abnormally input, an I / O error is determined (step B5), and if it is other than the I / O error, the input data length is "EOF" (End of File). ) Is substituted (step B6), "0" is substituted for the return value (step B7), and the process is terminated. On the other hand, I / O
In the case of an error, "-1" is assigned to the return value (step B8), and the process ends.

In the control means 41, the return value input from the input means 42 is "according to the flow chart shown in FIG.
It is judged whether or not it is "0" (step A5), and the return value is "
If it is 0 ", it is determined whether the input data length is" EOF "(step A6). The input data length is" EOF ".
In other cases, the load module file name 12 ₁ and the patch file name 12 ₂ stored in the input file 12 shown in FIG. 8 are set (step A).
7), the creation date / time acquisition means 43 (see FIG. 1) is called with the load module file name 12 ₁ as an argument (step A8).

The creation date / time acquisition means 43 is an external storage device 3.
If 0 (see FIG. 1) is a magnetic disk, the volume label file 31 is called from the external storage device 30 according to the flowchart shown in FIG. 5 (step C).
1). It is determined whether or not the calling of the volume label file 31 has succeeded (step C2), and if successful, the file directory 32 is read (step C3). It is determined whether or not the reading of the file directory 32 has succeeded (step C4). In the case of success, the argument is determined from the file name 32 ₁ (see FIG. 11B) stored in the file directory 32. The load module file name 12 ₁ input as is searched (step C5). As a result of the search, when the load module file name 12 ₁ is detected (step C6), the creation date and time 32 _{3 of the} load module file name 12 ₁ stored in the file directory 32 (FIG. 11B).
After reading (see step C7) (step C7), "0" is assigned to the return value (step C8), and the process ends. On the other hand, when the determinations in step C2, step C4, and step C6 are "N", "-1" is assigned to the return value (step C9), and the process ends.

The control means 41 determines whether or not the return value input from the creation date / time acquisition means 43 is "0" according to the flowchart shown in FIG. 2 (step A9), and the return value is "0". In this case, the creation date / time 32 ₃ of the load module file name 12 ₁ input from the creation date / time acquisition means 43 is stored in the one creation date / time storage memory 44 (step A10). Next, the call of the creation date and time acquisition means 43 the patch file name 12 ₂ as an argument (step A11). The creation date / time acquisition means 43 performs the same operation as when the load module file name 12 ₁ described above is used as an argument. The control unit 41 determines whether the return value input from the creation date / time acquisition unit 43 is “0” according to the flowchart shown in FIG. 3 (step A1).
6) If the return value is "0", the creation date / time acquisition means 4
Creation date and time 3 of the patch file name 12 ₂ input from 3
After storing 2 ₃ in the other creation date / time storage memory 45 (step A17), the comparison means 46 is called (step A18).

According to the flow chart shown in FIG. 6, the comparing means 46 reads out the contents of the one creation date / time storage memory 44 and substitutes it for the first date / time (step D1), and reads out the contents of the other creation date / time storage memory 45. After substituting it for the second date and time (step D2), the first date and time and the second date and time are compared (step D3). As a result of the comparison, the first
If the date and time of is earlier than the second date and time (first date and time <second date and time), "0" is substituted for the return value (step D
4), the process ends. On the other hand, if the first date and time is later than or equal to the second date and time (first date and time ≥ second date and time), "-1" is assigned to the return value (step D5), and the process ends. To do.

In the control means 41, the return value input from the comparison means 46 is "according to the flow chart shown in FIG.
If the return value is "0", it is determined that the load module file 34 was created later than the patch file 35, and the return value is "0" (step A19). Then, the procedure is returned to the calling operation of the input means 42, and the following steps are repeated, and if the input data length is "EOF" in the determination shown in step A6, a normal termination message is created (step A14). ), After the input file is closed (step A20 in FIG. 3), the output means 46 (see FIG. 1) is called (step A21), and the output means 46 follows the flow chart shown in FIG. The normal termination message input from the output device 40 (see FIG. 1)
To (step E1), and the process ends. After that, the control means 41 also ends the process (normal end).

On the other hand, in the following cases, the control means 41 ends abnormally. (1) If the result of the input file open shown in step A3 of FIG. 2 is "failure", an open error message is created (step A1).
2), the output means 46 is called (step A25 in FIG. 3). (2) If the return value when calling the input means 42 shown in step A5 of FIG. 2 is other than "0", an I / O error message is created (step A13), and the input file is closed. (Step A24 in FIG. 3), the output means 46 is called (step A25). (3) Creation date acquisition means 4 shown in step A9 of FIG.
3 If the return value at the time of calling 3 is other than "0", create a file undetected message (step A15),
After closing the input file (step A in FIG. 3)
24), the output means 46 is called (step A2).
5). (4) If the return value at the time of calling the creation date / time acquisition means 43 shown in step A16 of FIG. 3 is other than "0", a file undetected message is created (step A2).
2) After closing the input file (step A)
24), the output means 46 is called (step A2).
5). (5) If the return value at the time of calling the comparing means 46 shown in step A19 is other than "0", a file inconsistency message is created (step A23), and the input file is closed (step A24). , Output means 4
6 is called (step A25).

The output means 46 called upon abnormal termination described above outputs the open error message, I / O error message, file non-detection message and file inconsistency message created in accordance with the flow chart shown in FIG. Output to the device 40 (step E1).

The information processing system uses step F2 in FIG.
As a result of the determination shown in 0, when it is confirmed that the normal termination message is output from the control means 41, it is determined to be "match", and the operation after the creation of the patch file 35 shown in step F8 is performed. On the other hand, when it is confirmed that a message other than the normal termination message is output from the control means 41, it is determined to be "mismatch", and the operation after the determination of whether to correct the source program 36 shown in step F6 is performed. ..

Therefore, in the information processing system according to the present embodiment, the mismatch in the load module file 34 and the patch file 35 can be detected by the determination in step F20 of FIG. It can be prevented. As a result, the source file 36 when the judgment in step F10 in FIG.
It is possible to remarkably reduce the time required for re-creating and re-evaluating the re-created source file 36.

[0028]

Since the present invention is configured as described above, it has the following effects.

By comparing the creation date and time of the load module file stored in the creation date and time storage memory with the creation date and time of the patch file, the inconsistency between the load module file and the patch file can be easily detected. Therefore, even if a plurality of program creators or third parties manage the load module file and the patch file, it is possible to prevent erroneous application of the patch file.

[Brief description of drawings]

FIG. 1 is a schematic configuration diagram showing an embodiment of an information processing system of the present invention.

FIG. 2 is a flowchart for explaining the first half of the operation of the control means shown in FIG.

3 is a flowchart for explaining the latter half of the operation of the control means shown in FIG.

4 is a flowchart for explaining the operation of the input means shown in FIG.

5 is a flowchart for explaining the operation of the creation date / time acquisition means shown in FIG. 1. FIG.

FIG. 6 is a flowchart for explaining the operation of the comparison means shown in FIG.

FIG. 7 is a flowchart for explaining the operation of the output means shown in FIG.

8 is a diagram showing the contents of an input file stored in the input device shown in FIG.

9 is a flowchart for explaining the operation of the information processing system shown in FIG.

FIG. 10 is a schematic configuration diagram showing one conventional example of an information processing system of this type.

11 is a diagram showing the contents of various information stored in the external storage device shown in FIG. 10, (A) showing the contents of a volume label, and (B) showing the contents of a file directory. , (C) are diagrams showing the contents of a file group.

12 is a flowchart for explaining the operation of the information processing system shown in FIG.

[Explanation of symbols]

10 Input Device 11 Display Device 12 Input File 12 ¹ Load Module File Name 12 ² Patch File Name 20 Central Processing Unit 21 Operating System 30 External Storage Device 31 Volume Label 32 File Directory 32 ¹ File Name 32 ² File Start Position 32 ³ Creation Date and Time 33 file group 34 load module file 35 patch file 36 source file 37 modified load module file 38 data file 40 output device 41 control means 42 input means 43 creation date and time acquisition means 44, 45 creation date and time storage memory 46 comparison means 47 output means 50 time apparatus

Claims (1)

[Claims] 1. A central processing unit having an operating system, an external storage device, an input device, and an output device, wherein the external storage device is a source file, a load module file, a patch file, and a modified load. A module file and a file directory that stores creation dates and times of these files are stored, the central processing unit creates the load module file from the source file, and the evaluation of the source file by the load module file is not performed. In the information processing system, wherein the patch file is created when the result is acceptable, the modified load module file is created from the patch file, and the source file is evaluated by the modified load module file, wherein the input device loads Module An input file including a file name and a patch file name is stored, the central processing unit reads out the input file from the input unit, and the control unit reads out the load module file name and the patch file name. Input means for outputting the file directory from the external storage device, the creation date and time acquisition means for outputting the creation date and time of the load module file and the creation date and time of the patch file to the control means; A creation date and time storage memory that stores the input creation date and time of the load module file and the creation date and time of the patch file, the creation date and time of the load module file and the creation date and time of the patch file stored in the creation date and time storage memory And the result of the comparison The information processing system characterized in that it comprises a comparing means for outputting a control means, and output means for outputting the message input from said control means to the output device.