JP2666703B2 - Data unit configuration record matching method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for matching data of records composed of data units, which are logical information units, and more particularly, to a method in which a data unit ID for identifying a data unit and a matching key value are the same. And a data unit configuration record matching method for matching data units in data unit units.

[0002]

2. Description of the Related Art Conventionally, a method of matching records composed of data units, which are logical information units, is performed by matching data units of the same data unit ID in a corresponding record in the physical arrangement order in the record. Was.

[0003] As shown in FIG. 2, a record is generally composed of a fixed length part and a plurality of data units.

Conventionally, each data unit is composed of only a data unit length area, a data unit ID area for identifying the data unit, and user data. Therefore, when records are matched, they have the same data unit ID. The correspondence between data units is not clear,
Data units having the same data unit ID can be matched only in the physical arrangement order in the record.

[0005]

As described above, in the conventional reconciliation method, reconciliation can be performed only for each data unit ID in the physical arrangement order within a record, and thus data such as deletion, insertion, and modification of data units can be used. If a match is made after the update process, data units that are not originally supported will be matched, and the intended result may not be obtained. For this reason, there is a problem that the verification work after updating the data is difficult, and it takes a lot of man-hours.

[0006]

For a record composed of a plurality of data units, which are logical information units registered by a user, a data unit length area, a data unit ID area for identifying a data unit, and Refer to the data unit configuration information file storing the position, length, and attribute of the data unit configuration information in the data unit, such as the matching key area having a unique value for each data unit ID, and the data unit configuration information file And a collision control information acquisition unit for acquiring a position, a length, and an attribute of the data unit configuration information in the data unit of the data unit to be collated, and a data unit configuration acquired by the collision control information acquisition unit. A data unit configuration information storage area for storing information; The same data unit ID recognizing means for searching for data units in two matching target records by referring to the configuration information of the data units stored in the area and recognizing a data unit having the same data unit ID; Corresponding data for recognizing a data unit having the same matching key value by searching for the data unit recognized by the same data unit ID recognizing means with reference to the information on the configuration of the data unit stored in the configuration information storage area Unit recognizing means, data unit recognizing means for reconciling data of the data units recognized by the corresponding data unit recognizing means with reference to the two reconciliation target records, and obtaining reconciliation result information; Recognition means, the corresponding data unit recognition means, and Serial and a butting result information storage area for storing obtained butting result information by the data unit butting means.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described with reference to the drawings.

FIG. 2 shows a general record conceptual diagram 20 composed of a fixed length part and a plurality of data units, and also shows the difference between the configuration of each data unit in the conventional and the present invention. That is, the conventional data unit 2
1 is composed of a data unit length area, a data unit ID area for identifying the data unit, and user data. The data unit 22 of the present invention is a data unit ID area for identifying the data unit length area and the data unit.
It consists of a matching key area having a unique value for each area and data unit ID, and user data. Here, the data unit length area, the data unit ID area, and the matching key area are arbitrary areas in the data unit.

FIG. 1 is a block diagram of an embodiment of the present invention. The data unit length area of a data unit, a data unit ID area for identifying a data unit, and a unique data unit ID for each data unit in a record to be matched. The data unit configuration information file 11 storing the position, length, and attribute of the data unit configuration information in the data unit, such as the reconciliation key area having a value, and the data unit configuration information file 11 Control information acquisition means 12 for acquiring the position, length, and attribute of the data unit configuration information of the data units 31 and 32 in the data unit, and the data unit configuration information acquired by the collision control information acquisition means 12 are stored. The data unit configuration information storage area 13 and the data unit configuration storage area 13 The same data unit ID recognizing means 14 which searches for data units in the two matching target records 31 and 32 with reference to the configuration information of the data unit thus obtained and recognizes a data unit having the same data unit ID, The corresponding data unit recognizing means 15 for retrieving the data unit recognized by the unit ID recognizing means 14 and recognizing the data unit having the same matching key value, and the data of the data unit recognized by the corresponding data unit recognizing means 15 And a data unit matching means 16 for obtaining matching result information, and a matching result information storage area 17 for storing matching result information.

The overall operation flow will be described with reference to FIG.

When the record data is compared, first, the position and length in the data unit of the data unit configuration information such as the data unit length area, the data unit ID area, and the comparison key area stored in the data unit configuration information file 11 are described. And the attribute of the matching control information acquiring means 1
2 and the data unit configuration information storage area 13
To be stored.

This data unit configuration information storage area 13
, The same data unit ID recognizing means 14 searches data units in the matching target records 31 and 32 and recognizes a data unit having the same data unit ID.

If a data unit having the same data unit ID cannot be recognized from both records 31 and 32, the same data unit ID recognizing means 14 stores the information in the matching result information storage area 17. Store.

When a data unit having the same data unit ID is recognized from both the records 31 and 32 to be matched, the corresponding data unit recognizing means 15
Retrieves the data unit based on the information stored in the data unit configuration information storage area 13 and recognizes a data unit having the same matching key value.

If the data unit ID recognized by the same data unit ID recognition means 14 cannot recognize a data unit having the same matching key value from the same data unit, the corresponding data unit recognition means 15
Stores the information in the matching result information storage area 17.

When the corresponding data unit recognizing means 15 recognizes a data unit having the same matching key value,
The data unit matching means 16 matches the corresponding data units and stores the result in the matching result information storage area 17.

Next, the contents of a specific data unit will be exemplified with reference to FIGS. 3, 4 and 5, so that the data records are compared by the conventional data unit configuration record matching method and the present invention. The difference in the result of the comparison with the case of performing based on the method is shown.

It is assumed that the specific contents of each data unit of the two matching records 31 and 32 are as shown in FIG.

Now, consider a case in which the matching target records 31 and 32 are matched after the matching target record 31 is updated like the matching target record 32 for the data unit having the data unit ID of “A”.

The contents of the update are as follows.

(1) The data unit A having the matching key “a” and the user data “1” is deleted.

(2) The user data of the data unit A having the match key "b" and the user data "2" is changed to "9".

(3) Insert a data unit A whose matching key is "d" and whose user data is "4".

In the conventional method, the data units to be matched are matched only in the physical arrangement order of the data units having the same data unit ID, and the matching result is as shown in FIG.

As can be seen from FIG. 4, in this case, the data unit having the data unit ID of "A" is determined that all the results are inconsistent. I can't tell if it was done.

According to the method of the present invention, since the data unit to be matched is recognized by both the data unit ID and the matching key, a matching result as shown in FIG. 5 is obtained, and the originally corresponding data unit can be matched. Becomes

Further, as is apparent from FIG. 5, it is possible to clarify the difference between operations performed on the data unit such as deletion, insertion, change processing, and no update processing.

[0028]

As described above, according to the present invention, when matching record data composed of data units as logical information units, a data unit ID for identifying a data unit and a data unit ID for each data unit ID are used. Recognizing the matching key with a unique value and matching in data unit units, it is possible to match the corresponding data unit without depending on the physical position of the data unit in the record, consisting of data units It is possible to perform a match making use of the characteristics of the record.

Further, since the specific contents of the updating process can be known, there is an effect that the verification work after updating the data can be facilitated and the efficiency can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram of an embodiment of the present invention.

FIG. 2 is a conceptual diagram of a record and a conceptual diagram of a data unit according to the related art and the present invention.

FIG. 3 is a specific example of a matching target record for explaining the embodiment.

FIG. 4 shows a result of a collision when a collision is made by a conventional technique.

FIG. 5 shows a result of a match when a match is made with the technique of the present invention.

[Explanation of symbols]

 11 Data Unit Configuration Information File 12 Matching Control Information Acquisition Means 13 Data Unit Configuration Information Storage Area 14 Same Data Unit ID Recognition Means 15 Corresponding Data Unit Recognition Means 16 Data Unit Collation Means 17 Matching Result Information Storage Area 20 Record Conceptual Diagram 21 Conventional Schematic diagram of data unit 22 Schematic diagram of data unit of the present invention 31, 32 Matching target record

Claims (2)

(57) [Claims] In a record matching method for mutually matching record data stored in a data file, a record composed of a plurality of data units, which are logical information units registered by a user, is provided. By storing the position, length, and attributes of the data unit configuration information in the data unit, such as the data unit length area, the data unit ID area for identifying the data unit, and the matching key area having a unique value for each data unit ID Data unit configuration information file, and by referring to the data unit configuration information file, the reconciliation control information acquisition for acquiring the position, length, and attribute in the data unit of the data unit configuration information of the data unit to be reconciled Means, and a data unit obtained by the matching control information obtaining means. A data unit configuration information storage area for storing formation information, retrieves the data units in abutting target record configuration information with reference to the two data units stored in the data unit configuration storage area, the same data unit ID
Data unit I that recognizes a data unit with
D recognizing means, and referring to information on the configuration of the data unit stored in the data unit configuration information storage area, searching for the data unit recognized by the same data unit ID recognizing means, and finding the same matching key value. A corresponding data unit recognizing means for recognizing a data unit possessed; and a data unit reconciling means for reconciling data of the data units recognized by the corresponding data unit recognizing means with reference to the two records to be reconciled and obtaining reconciliation result information. Means, and a matching result information storage area for storing matching result information acquired by the same data unit ID recognizing means, the corresponding data unit recognizing means, and the data unit matching means. Record matching method. 2. In a record matching method in which record data stored in a data file are compared with each other, a plurality of data units which are logical information units registered by a user are used as record data to be matched. The data unit further comprises a data unit length area, a data unit ID area for identifying the data unit, and a matching key area having a unique value for each data unit ID. Data unit configuration record matching method described in 3.