JPH0528020A - Retrieval system - Google Patents

Abstract

PURPOSE:To permit faster management and retrieval and to guarantee matching of data between systems at the time of retrieval, as for a retrieval system by which data is retrieved between plural systems connected by a line with CONSTITUTION:A managing origin system 1 which has a management file 12 and a reference destination system 2 are provided, and, in response to retrieval request, the reference destination system 2 retrieves a copy file 21, and when it finds desired data, it notifies a retrieval requester of it. If it is not found, the managing system 1 is requested for copy by way of a line, and the system 1 transfers data from a master file 11, besides, a data name and the reference destination system 2 of a transfer destination are stored in the management file 12, and then the reference destination system 2 stores the data which was supplied in the copy file 21, and in addition, notifies a retrieval requester, thus configured like this.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention is a retrieval system for retrieving data between a plurality of systems connected to each other, and updating / deleting data copied and managed in a reference system in a management system. The present invention relates to a search system that manages data while ensuring the consistency between the management source system and the reference destination system, when it is possible.

[0002]

2. Description of the Related Art Conventionally, data that is frequently referred to is
If you try to build a system to copy and manage the data in the reference system that references the data, if the data is updated in the management system, a file inconsistency with the data to be copied and managed in the reference system will occur. Since it occurred and the reliability of the database system was lost, the data in the management source system and the reference destination system could not be updated or deleted.

[0003]

For this reason, among the data managed by the management source system, it is not possible to transfer the data having a high frequency of reference in the reference destination system and perform copy management in the reference destination system. There has been a problem that the referent system cannot respond quickly to the referral request for frequently used data.

According to the present invention, a management file is provided in a management source system to manage a reference system and copy data, and when a data update / deletion occurs, the management file is searched and a corresponding reference system is searched. The purpose is to invalidate the copied data, to speed up the search, and to ensure the data consistency between the systems during the search.

[0005]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, a management source system 1 is a system that manages and searches data, and has a master file 11 and a management file 12.

The master file 11 is a file for managing data. The management file 12 registers and manages the data name and the reference system 2 when the data is transferred from the master file 11 and copied to the copy file 21 of the reference system 2.

The reference destination system 2 notifies data in response to a search request and has a copy file 21 for copying data that is frequently referred to.

[0008]

According to the present invention, as shown in FIG. 1, when the reference system 2 searches the copy file 21 in response to a search request and data is found, the data is found and the search request source is notified. If not, a copy request is made to the management source system 1 via the line, and the management source system 1 transfers the data from the master file 11 and stores the data name and the reference destination system 2 of the transfer destination in the management file 12 for reference. The destination system 2 stores the transferred data in the copy file 21 and notifies the search request destination.
Further, when the data in the master file 11 of the management source system 1 is updated / deleted, etc., when the data is registered in the management file 12, the reference system 2 of the transfer destination is notified of invalidation and the copy file 21 I'm trying to invalidate the data.

Therefore, a management file 12 is provided in the management source system 1 to manage the copy data of the reference destination system 2,
By retrieving the management file 12 and invalidating the copied data of the reference destination system 2 when data update / deletion occurs, it is possible to speed up the retrieval of the data and at the time of retrieval. It is possible to guarantee data consistency between systems.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

In FIG. 1, a management system 1 is, for example, a bank branch (branch A), and is a system for managing and retrieving bank account data (deposit, balance, payment, transfer, etc.). In addition, it has a master file 11 and a management file 12.

The master file 11 is a file for managing data such as bank account deposits, balances, payments and transfers. The management file 12 registers the data name and the reference system 2 when data is transferred from the master file 11 and copied to the copy file 21 of the reference system (for example, branch B) 2 and any data from the master file 11 is registered. Refers to any system 2
It is to register and manage whether or not the data has been transferred and copied.

The reference destination system 2 is, for example, a branch of a bank (branch B), and searches for data in the master file 11 of the management source system 1 via a line or manages data that is frequently referred to by the management source. The file is transferred from the master file 11 of the system 1 and copied in its own copy file 21 to notify it in response to a search request, and is taken out from this copy file 21 from the next time and notified.

The copy file 21 is a copy of the data transferred from the master file 11 of the management source system 1 and retains it. In response to a search request from the next time onward, the copy file 21 is referred to for prompt notification. It is for doing.

The operation of FIG. 1 will be described below with the management source system 1 being the branch A and the reference destination system 2 being the branch B. Causes a search request in the reference system (branch B).

[0016] searches the copy file 21 of the reference system (branch B), but cannot find the data of the corresponding account. Requests a management source system (branch A) whose reference system (branch B) has search request data for online search and data transfer.

With respect to the data for which the search request has been received at, the management source system (branch A) searches the master file 11 to find the data (data of the A account). Writes the data name (account A) searched in and the reference system (start point B) to be transferred in the management file 12 as shown in the figure, and registers it.

In, the management source system (branch A) transfers the data to the search request source via the line. Causes the reference system (branch B), which has been transferred in, to register data (account data of A) in the copy file 21. Then, the search request destination is notified of this data (data of the A account).

As described above, when the reference destination system (branch B) is not found by searching the copy file 21 in response to the search request, the online search request is sent to the management system (branch A) via the line. Then, in response to this, the management source system (branch A) registers the data name of the data (account A) retrieved from the master file 11 and the reference system (branch B) in the management file 12, and then, via the line. The information is transferred to the reference system (branch B), registered in the copy file 21, and notified to the search request destination. As a result, the copy file 2 of the referenced system (start point B) will be used from the next time onward.
1 can be searched and found, and the search request destination can be notified promptly.

Next, when the data (A account) of the master file 11 is updated or deleted in the management source system (start point A), the management file 12 is searched to find the corresponding data,
Since the A account is found here, the reference destination system (start point B) is notified of invalidation and the data (A account) of the copy file 21 of the reference destination system (start point B) is deleted. As a result, it is possible to guarantee the consistency between the data managed by the master file 11 (here, the A account) and the data of the copy file 21 of the reference system (start point B) transferred and copied. .

Next, the operation of the configuration of FIG. 1 will be concretely described according to the order shown in the flowchart of FIG. In FIG. 2, S1 requests a search. In this case, the application (or the user) of the reference destination system 2 makes a data search request.

In step S2, it is determined whether or not there is corresponding data in the copy file 21. In this case, the reference destination system 2 searches the copy file 21 in response to the search request of S1 and determines whether or not the corresponding data exists. In the case of YES, since the corresponding data exists in the copy file 21, the search request destination is notified of this in S3. On the other hand, NO
In this case, since it is determined that the corresponding data does not exist in the copy file 21, the copy request is notified to the management source system 1 via the line.

In S4, the management source system 2 searches. In response to the receipt of the copy request notification in S2, the management system 2 searches the master file 11 to find the corresponding data.

In step S5, the file is registered in the management file. This registers the data name of the data found in S4 and the reference system 2 to be transferred in the management file 12. In S6, the data is transferred to the reference destination system 2.

In step S7, the reference destination system 2 received in step S6 stores the data in the copy file 21. S8 is
Notify (display, etc.) the search data to the search request destination.

As described above, when there is a search request in the reference system 2, when there is data corresponding to the copy file 21, the search request destination is notified of this, and when there is no data, the management source The data requested to be copied by the system 1 is stored in the copy file 21 and the data is notified to the search request destination. Since the data is stored in the copy file 21 from the next time onward, it is possible to notify the retrieval request destination from which the data is extracted.

In FIG. 2, S9 is the management source system 2
Update / delete occurs. In S10, it is determined whether or not the data updated / deleted in S9 exists in the management file 12. If YES, the corresponding record in the management file 12 is deleted in S11, the corresponding branch (reference destination system) is notified of invalidation in S12, and the corresponding data in the copy file 21 is deleted in S13.

As a result, the management system 1 updates
When the deletion occurs, the management file 12 is searched, and when the corresponding data is registered, the record is deleted and the invalidation notification is notified to the reference system 2, and the corresponding data is copied from the copy file 21. delete. As a result, data consistency can be guaranteed.

FIG. 3 is a diagram illustrating a specific example of the present invention. FIG. 3A shows a case where the copy file 21 has data. This is data (A account) in the copy file 21 of the reference system (branch B) when a search request is made.
Therefore, this data is notified to the search request destination.

FIG. 3B shows the case where the copy file is invalidated. This is because there was data update and "A account A" in the master file was updated to "A account", so the management status of the management file 12 was confirmed with. Since it was registered here, refer to System (branch B)
To the invalidation notification, and then in the copy file 21 "A account"
Disable (delete). This ensures the integrity of the data "A account".

[0031]

As described above, according to the present invention,
The management file 12 is provided in the management system 1 to manage the copy data of the reference system 2, and when the data is updated or deleted, the management file 12 is searched to invalidate the copy data of the reference system 2. Since such a configuration is adopted, it is possible to speed up the data search and ensure the data consistency between the systems at the time of the search. This ensures the consistency between the data in the master file 11 and the data received from the master file 11 and stored in the copy file 21 when mutually searching data between databases of a plurality of online-connected systems. It becomes possible to do.

[Brief description of drawings]

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

FIG. 2 is a flowchart illustrating a specific example of the present invention.

FIG. 3 is a diagram illustrating a specific example of the present invention.

[Explanation of symbols]

1: Management system 11: Master file 12: Management file 2: Reference system 21: Copy file

Continued front page    (72) Inventor Takehiko Nakasone             Gunma Prefecture Maebashi City 1-chome 1-1 N 1N             F-2 building (72) Inventor Kunio Miyazaki             Gunma Prefecture Maebashi City 1-chome 1-1 N 1N             F-2 building

Claims (2)

[Claims] 1. A retrieval system for retrieving data between a plurality of systems connected by a line, wherein a master file (11) for managing data and the data managed by this master file (11) are transferred to another system. A management source system (1) having a management file (12) for registering a data name copied and a transfer destination system, and a copy file (21) for copying the data transferred from the management source system (1). A reference system (2) to have, and when the reference system (2) searches the copy file (21) in response to the search request and data is found, the search request destination is notified of this. When not found, a copy request is made to the management source system (1) via the line, and the management source system (1) transfers the data from the master file (11). The data name and the reference system (2) of the transfer destination are stored in the management file (12) while being sent, and the transferred data is transferred to the copy file (2) by the reference system (2).
A search system characterized by being stored in 1) and being notified to a search request destination. 2. A reference system of a transfer destination of the master file (11) of the management source system (1) when the data is registered in the management file (12) when the data is updated or deleted. 2. The retrieval system according to claim 1, wherein the data of the copy file (21) is invalidated by informing (2) of invalidation.