JPH02278423A - Data control system - Google Patents

Abstract

PURPOSE:To eliminate a useless conversion process in such an application form where no conversion of codes is desirable by preparing the defining information showing its own node system or another node system that should control data and performing the necessary code conversion process by reference to the defining information. CONSTITUTION:A data base 21 stores the data on its own node system or another node system. The defining information which is previously defined by a user is registered in a defining information memory 2b in accordance with the data stored in the base 21. Then the necessary conversion of codes is carried out by reference to the registered information when data are read, written, transferred and received. Thus the data are processed. Thus it is possible to eliminate the useless conversion processes in an application form where no conversion of codes is desirable with a host used as a data warehouse in a micromain connection system, etc.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a data management system, and in particular to a system for efficiently distributing both data storage and data processing between nodes in a micromain connection system, etc. related to data management systems.

[Conventional technology]

Conventionally, a micromain connection system has been used in which a host computer and a workstation are linked, and a plurality of computers are connected vertically and horizontally to perform distributed processing by taking advantage of the ease of use of the workstation.

On the other hand, in a network with multiple nodes, when data is transferred between nodes with different encoding systems, one or both nodes must convert the encoding system to that of the destination node. After that, it was transferred to the other party. In that case, the data used and stored in each node was managed by the code system of that node. Note that, as a document describing such a data management method, there is, for example, "Database Urayasu Search Package, DNTT Research Practical Application Report, Vol. 36, No. 11, pp. 1493.

[Problem to be solved by the invention]

By the way, in recent years, in micromain connection systems that connect computers and workstations,
There are many usage patterns in which a host computer is used as a data warehouse between workstations, and no particular business processing is performed on the host computer. In such a system.

The code conversion process that has been performed in the past becomes a completely wasteful process.

Furthermore, the code systems of the host computer and workstation, including the handling of external characters, may not correspond one-to-one. As a result, even if data is stored from the workstation to the host computer and then retrieved from the workstation again, the same characters may not be restored depending on the conversion method.

As a specific example of such a problem, we will discuss in detail the problem that occurs during data transfer between a workstation whose encoding system includes half-width and full-width characters and a host computer whose encoding system includes only full-width characters. .

FIG. 2 is an explanatory diagram of the problem to be solved by the present invention.

On the workstation II side, the half-width character FAI corresponds to the code Ir41j, but on the host computer 12 side, there is no code corresponding to the half-width character.

Therefore, when transferring data to the host computer 12, half-width characters [i'AJl is the code ff of the full-width character "A"]
2341J]. Therefore, when the half-width character [rAj code [i'41J] is transferred to the host computer, the code! i'2341j. When this data is retrieved from the workstation 11 again, the code corresponding to the full-width character "Aj" on the workstation 11 is converted to the code [i'8260j, and is not converted to the original code "41", that is, the half-width character 1i'Aj. .

The purpose of the present invention is to solve such conventional problems, and to eliminate wasteful conversion processing and prevent inconsistencies due to code conversion in usage forms where it is better not to perform code conversion, such as in micromain connection systems. An object of the present invention is to provide a data transfer management system that can transfer data with the same functions as conventional ones.

[Means to solve the problem]

In order to achieve the above object, the data management system of the present invention includes a database and a means for accessing the database, executes read/write processing to the database, and communicates with a plurality of nodes having different code systems. The data management system in each node that performs data transfer accepts definition information from the user as to whether each data to be stored in the database should be stored in the code system of the own node or in the code system of another node. , a means for registering the definition information corresponding to the name of data stored in the database, and a means for determining and analyzing the contents of the registration means, and executing each of reading, writing, and transferring data to the database. At times, an analysis judgment means instructs a required code conversion, a code conversion means performs code conversion according to the instruction from the analysis judgment means, and data is exchanged with another node according to the instruction from the analysis judgment means. It is characterized in that it has a transfer means for executing.

[For production]

In the present invention, definition information indicating whether management should be performed in the local node system or other node system is created according to a user's definition set in advance, and necessary code is created by referring to this definition information. By performing the conversion process, the definition information is referred to when reading and writing data transfer, that is, when transferring and storing data.

A predetermined code conversion process is executed based on the definition information.

As a result, data can be transferred and stored according to user-defined storage modes.

In addition, when a data usage request is issued by an application program, the data is returned without going through conversion if the data specifies the own node system, or through data conversion if the data specifies another node system. do. This allows the data user to perform data inquiry operations regardless of the cord diameter of the stored data.

〔Example〕

EMBODIMENT OF THE INVENTION Below, one embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is an overall configuration diagram of a data management system in each node showing an embodiment of the present invention.

In FIG. 1, a database 21 stores data on other node systems or the own node system.

The data access unit 22 in the system 10 is the analysis determination unit 2
The database 21 has a function of storing and searching data in the database 21 according to instructions from the database 21. Further, the definition registration unit 2a defines, according to a user's specification, whether data is stored in the code system of the own node or another node, and registers it in the definition information memory 2b. The definition information memory 2b stores information defined by the definition registration section 2a, and its contents are referred to by the analysis and determination section 24. The analysis/determination unit 24 also determines the contents of the definition information 2b, analyzes and determines whether the data should be stored in another node system or the own node system, and instructs necessary data conversion.

Further, the code conversion unit 23 performs code conversion of data to other node systems and decoding conversion to the own node system according to instructions from the analysis determination unit 24. Further, the transfer unit 25 sends and receives data to and from other nodes according to instructions from the analysis and determination unit 24. Further, an application program (hereinafter abbreviated as AP) 26 stores in advance a user's application program. The user data area 27 is the AP2
This is a memory area in which data is exchanged between the analysis determination unit 6 and the analysis determination unit 24. Further, the data buffer 28 is a memory area for exchanging data between the analysis determination section 24 and the data access section 22. Further, the transfer buffer 29 is a memory area for exchanging data between the analysis and determination section 24 and the transfer section 25.

The data management system 10 having such a configuration is provided in all nodes, and manages data between the nodes.

FIG. 3 is a storage format diagram of the definition information memory in FIG. 1.

The name section 31 in FIG. 3 is an area for storing the name of the invention. Further, the ID section 32 is an identification flag indicating whether the data is stored in the own node body diameter or in the other node system. In Figure 3, one name data is the own node system.

Sales data is stored in the other node system, inventory data is stored in the own node body diameter, and order data is stored in the own node system.

FIG. 4 is a flowchart of the definition information registration process by the fixed escape registration section in FIG.

In the flowcharts from FIG. 4 onward, O indicates processing, ◯ indicates condition determination, and ◇ indicates the start and end of processing.

First, when the user specifies the storage code system of the corresponding data by defining the data, the definition registration section 2a
reads this (step 41), and registers the data name in the name section 31 of the definition information 2b (step 42).

Next, determine the code system to be stored (step 43
), if the user's specification is storage in the own node system, I
A flag 'self' indicating the own node system is set in the D section 32 (step 44). Furthermore, when this designation is for the other node system, a flag 'other' indicating this is set (skip 45).

5 to 10 are diagrams showing the flow of data reading, writing, and transfer processing centered on the analysis/judgment section 24 in FIG. 1.

FIG. 5 is a flowchart showing the flow of data reading processing.

When the AP 26 issues a data read request, control is transferred to the data access unit 22, and the corresponding data is read from the database 21 into the data buffer 28 (step 51). Next, with reference to the ID section 32 of the definition information memory 2b, it is determined whether the node ID is the own node system or another node system (step 52). Here, when the node ID is in another node system, the code converter 2
3 and executes code conversion (step 5
3). Next, the data buffer 28 is stored in the user data area 27.
Step 54) to transfer data from the AP 26
Return it to.

FIG. 6 is a flowchart 1 to 1 showing the flow of data writing processing.

When the AP 26 sets write data in the user data area 27 and issues a data write request (step 6
1) The analysis/determination unit 24 refers to the ID section 32 of the definition information 2b and determines whether to write the data in the own node system or in the other node system (step 6).
2). At this time, when it becomes clear that writing will be done using another node system.

Control is transferred to the code conversion unit 23 to execute code conversion processing (step 63). Next, data is transferred to the data buffer 28 (step 64), control is transferred to the data access unit 22, data is written to the database 21 (step 65), and control is returned to the AP 26.

FIGS. 7 and 8 are flowcharts showing the flow when data is transferred from a certain node (sending side) to another node (receiving side).

FIG. 7 shows the processing flow of the sending node. When the AP 26 sets the transfer data in the user data area 27 and issues a transfer command (step 71), the analysis determination unit 24 transfers the data in the user data area 27 to the transfer buffer 2.
9 (step 72), control is transferred to the transfer unit 25, and the transfer unit 25 transfers the data to the destination node (step 73). Then, after waiting for a transfer completion notification from the receiving side, control is returned to the AP 26.

FIG. 8 shows the processing flow of the receiving node. When data transfer is received from another node, the analysis/judgment unit 24 of the receiving node transfers control to the transfer unit 25 and receives the data into the transfer buffer 29 (step 81). Next, by referring to the definition information memory 2b (step 82), if the data is found to be in the own node system, control is transferred to the code converter 23, which converts the code into the own node system code. (Step 83), transfer buffer 29
data is written to the data buffer 28 (step 8
4). Then, control is transferred to the data access unit 22,
Write the data to the database 21 (step 8
5) Notify the sender of the completion of the transfer.

FIGS. 9 and 10 are diagrams showing the flow of processing for transferring data read from the database of another node (sending side) in response to a data transfer request from a certain node (receiving side).

FIG. 9 shows the processing flow of the receiving node that requested data. When the AP 26 issues a data transfer command from another node, the analysis/judgment unit 24 sends a data transfer request to the corresponding node (step 91).

As a result, when data is transferred from another node, control is transferred to the transfer unit 25, and the data sent from the other node is set in the transfer buffer 29 (step 92).

Next, after transferring the contents of the transfer buffer 29 to the user data area 27 (step 93), control is returned to the AP 26.

FIG. 10 shows the flow of processing on the sending side that receives a data transfer request. When the analysis/judgment unit 24 receives a data transfer request from another node, it transfers control to the data access unit 22 and reads the corresponding data from the database 21 into the data buffer 28 (step 101). Next, the analysis/judgment unit 24 refers to the definition information memory 2b (step 102), and if the data is in the own node system, the control is transferred to the code conversion unit 23, where the code conversion is executed and the data is transferred. Convert to the code of the previous node system (
Step 103). Next, the data in the data buffer 28 is moved to the transfer buffer 29 (step 104). Then, control is transferred to the transfer unit 25, and the data is sent from the transfer unit 25 to the node that requested the transfer (step 105).

In this way, in this embodiment, definition information defined by the user is registered in advance in correspondence with data stored in the database, and during read, write, transfer processing, and transfer reception processing, , the data is processed after performing the necessary code conversion by referring to the registration information, so the user does not have to be aware of the code system of the stored data, and automatically changes the system code of the node to be used. You can then use the data.

〔Effect of the invention〕

As explained above, according to the present invention, in a usage mode in which a host is used as a data warehouse in a micromain connection system, etc., and code conversion is not performed, wasteful conversion processing can be eliminated, and inconsistencies in code conversion can be avoided. This has the advantage of being able to prevent data transfer between the host computer and the workstation, and to realize the same data transfer function as in the past.

[Brief explanation of drawings]

Figure 1 is an overall configuration diagram of a data management system showing one embodiment of the present invention, Figure 2 is a diagram showing the problem to be solved by the present invention, and Figure 3 is the storage format of the definition information memory in Figure 1. Figure 4 is a flowchart of the definition information registration process in Figure 1, Figure 5 is a flowchart of the data read process in Figure 1, Figure 6 is a flowchart of the data write process in Figure 1, and Figure 7 is a flowchart of the data write process in Figure 1. is a processing flowchart of a node that transfers data to another node, FIG. 8 is a processing flowchart of a node to which data has been transferred from another node, and FIG. 9 is a processing flowchart of a node that requests transfer to another node. FIG. 10 is a processing flowchart of a node that has received a transfer request from another node. 1o: Data management system, 2a: Definition registration unit. 2b: definition information memory, 21: database, 22: data access section, 23: code conversion section, 24: analysis judgment section, 25: transfer section, 26: application program (AP), 27: user data area, 28: data Buffer, 29: Transfer buffer, 31: Name section, 32: ID section (identification flag section). Figure Figure 11 Workstation 12 Host computer Half-width person ``41'' Full-width Ar2341J Figure Figure ◇ Figure ◇ Figure ◇ Figure Figure ◇ Figure Atta beggar on Tahesu 2 (Step 85) figure

Claims (1)

[Claims] (1) A data management system in each node that includes a database and means for accessing the database, executes read/write processing for the database, and transfers data between multiple nodes with different code systems. For each data to be stored in the database, it accepts definition information from the user as to whether it should be stored in the code system of its own node or in the code system of another node, and the definition information is used to define the data stored in the database. means for registering in correspondence with the name, and analysis/judgment means for determining and analyzing the contents of the registration means and instructing necessary code conversion when reading, writing, and transferring data to the database. and a code converting means for converting a code according to an instruction from the analysis and determination means, and a transfer means for exchanging data with another node according to an instruction from the analysis and determination means. data management system.