JP2817144B2 - Transaction status display management method for distributed database system - Google Patents

Description

Description: BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a transaction status display management method for a distributed database system, that is, a transaction display status management method for a plurality of nodes in a distributed database system. .

[Conventional technology]

2. Description of the Related Art Conventionally, a distributed database system is provided with a means for monitoring the system status, monitoring the system execution status for the purpose of system tune-up, finding the cause of a system failure, and recovering the system. In this case, it is particularly necessary to clearly grasp the state of the transaction that is the subject of processing. For this purpose, it generally has a function of displaying information such as a transaction identifier (a number generated inside the database system), a request node name, and an execution node name.

Regarding this, for example, reference material 44-1 “ADABAS
A distributed database function "(1984) shows a function relating to the display of a transaction state, and a function of displaying a transaction number, an origin node, and other target nodes on an operator console.

[Problems to be solved by the invention]

However, the above prior art has the following problems. That is, since the processing request is generated from a plurality of computer elements such as an application program and a TSS terminal,
Just by displaying the transaction identifier and node,
The origin in the node is unknown, and the system operator cannot specify the request source.

Further, when a distributed database management system is processed via a plurality of subsystems independent of functional units such as a DB (database) subsystem, a DC (data communication) subsystem, and the like, the conventional method requires a distributed method. A complicated operation is required to specify the source of a transaction processed by a plurality of nodes, and there is a problem that it cannot be easily specified.

The present invention has been made in view of the above circumstances, and an object of the present invention is to solve the above-described problems in the conventional technology and to provide a system for managing a transaction status display of a distributed database system that can be immediately understood by a system operator. Is to provide.

[Means for solving the problem]

An object of the present invention is to provide an online system having at least a plurality of nodes including a processor and a database and a communication network interconnecting the plurality of nodes, and a process of accessing a database of the plurality of coupled nodes. In each of the nodes, and at the end of the transaction, at the end of the transaction, synchronize the nodes to end the transaction. And a means for holding and intercommunicating the information, and a means for displaying the information, wherein at the start of the transaction, the transaction start node acquires the user information by the user information acquiring means, and Keep information and, if necessary, the mutual contact And managing the transaction execution status by displaying the information by the display means of each node when the information display request is generated at each node. This is achieved by a transaction status display management method of a distributed database system characterized by the following.

[Action]

In the transaction state display management method of the distributed database system according to the present invention, at the start of a transaction, user information is obtained by the user information obtaining means of the client node, that is, the transaction start node, and the information is held by the holding means. When the transaction is processed by another node, the other node, that is, the server node, is contacted via the mutual communication means. By displaying the information on the display unit, the system operator can manage the execution status of the transaction being processed in any node.

〔Example〕

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 2 is a configuration diagram of a distributed database system showing one embodiment of the present invention. In the figure, 2a and 2b are nodes, 3a and 3b are system administrator terminals such as operator consoles, 4a and 4b are nonvolatile memories such as magnetic disks, and 1 is a communication path connecting the nodes 2a and 2b. ing.

The nonvolatile memories 4a and 4b hold data such as a data dictionary, a database, or a processing history. Also, 5a and 5b in the nodes 2a and 2b are control functions of each functional unit (subsystem) in the node, 7a and 7b are distributed database management functions, 9a and 9b are DC management functions, and 10a and 10b are UAPs ( User program). 20a and 20b are activity management tables for control functions 5a and 5b, 30a and 30b are user information format management tables, and 50a and 50b are distributed database management functions 7a and 7b.
2 shows a transaction management table in FIG.

In the following description, each table in the nodes 2a and 2b has the same structure. An activity is a unit of resource management in a node, and a transaction is a guaranteed unit of business processing across nodes.

FIG. 3 shows the activity management table 20a (20b
Is the same). In the figure, reference numeral 21 denotes an activity identifier for distinguishing activities, reference numeral 22 denotes a processing sequence number in which a consistent number is added to each occurrence of the activity in the control functions 5a and 5b, reference numeral 23 denotes user information in the present invention, and reference numeral 24 denotes a function of an activity generation source. Function unit type representing a unit, 25 is subsystem-specific information specified in advance by control functions 5a and 5b passed from each function unit at the time of activity generation, and 25 is for managing activities in control functions 5a and 5b such as activity execution status. Indicates other information.

FIG. 4 shows the user information format management table 30a (30b
Is the same). In the figure, 31 is a table for managing a user information format table 35, 32 is a functional unit type for distinguishing a table registration source, 33 is a pointer for pointing to a corresponding user information format table, and 35 is the usage information. The above-mentioned user information format table showing the field configuration of the user information 23, 36 is the start position of the field in the user information 23, 37 is the length of the field, 38 is the internal data format of the field, and 39 is the field Shows a display data format when is output to the administrator terminal 3a or the like.

FIG. 5 shows the transaction management table 50a described above.
(Same for 50b). In the figure, 51 is a transaction identifier for distinguishing a transaction,
Reference numeral 52 denotes a transaction state indicating the execution state of the transaction, 53 denotes an activity identifier corresponding to the transaction, and 54 denotes other information for managing the transaction.

FIG. 6 shows a user information communication format 60 between nodes.
In the figure, reference numeral 61 denotes user information indicating a transaction origin, a UAP name, a JOB name executing the UAP, or
Contains the user ID that identifies the user logged on from the TSS terminal. Reference numeral 62 denotes subsystem information indicating information on the DC management function, including a subsystem identifier for distinguishing the subsystem and a subsystem processing serial number. 63 is client information indicating the request source of the distributed database management function,
The transaction identifier includes the name of the client node, that is, the name of the transaction start node.

FIGS. 7 (a) and 7 (b) show a transaction status information display format for the administrator terminal. In both figures, reference numeral 80 denotes a transaction status information display format at the client node, and reference numeral 90 denotes a transaction status information display format at the server node, that is, the partner node of the transaction.

The outline of the operation of the present embodiment configured as described above is as follows.

The distributed database management functions 7a and 7b and the DC management functions 9a and 9b shown in FIG.
By making a connection request to 5b, it becomes executable. At the same time, a request for registration of each user information format table 35 is made to the control functions 5a and 5b. The control functions 5a and 5b receive the user information format table 35, and
Is set to the function unit type and the pointer of the connection request source, and the preparation is completed.

After being in the executable state, the DC management function 9a activates the UAP 10a at the request of the user, adds the activity generation request and the subsystem information in the DC management function 9a,
Contact control function 5a. The control function 5a generates an activity based on the request, and registers the activity information and the subsystem information in the activity management table 20a for each processing request source.

Thereafter, when a database processing request occurs from the UAP 10a, the request is communicated to the distributed database management function 7a via the DC management function 9a and the control function 5a.

The following operation will be described based on the flowchart shown in FIG. FIG. 1A is a flowchart illustrating the operation of the transaction state information management processing of the client node in the present embodiment, and FIG. 1B is a flowchart illustrating the operation of the server node node in the state information management processing.

The distributed database management function 7a sends the request to the UAP1
If it is the first processing request from 0a, the first processing request after the end of the previous transaction, or a direct transaction start request (step 11), a new transaction is generated and the transaction management table 50 is created.
Register transaction management information in a (Step 1
2). Further, it requests the control function 5a for activity information corresponding to the processing request (step 13), and registers the information in the transaction management table 50a (step 14).

If the transaction has already started in step 11, the previous transaction assigned to the UAP 10a is taken over from the transaction management table 50a (steps 15, 16). Thereafter, it is determined whether the request can be processed by the node or should be processed by another node (step 17).

If it is to be processed by another node, it requests the control function 5 for the activity information and subsystem information of the transaction (step 18), and assembles the user information contact data 60 based on these (step 19), and communicates. The request is sent to the server node 2b via the line 1.

The distributed database management system 7b of the node 2b that has received the processing request searches the transaction management table 50b to determine whether the processing request is the first request (Step 41). If it is the first request, a transaction start process is performed in the node 2b, and the transaction information is registered in the transaction management table 50b (step 42). At the same time, an activity start declaration and a registration request for the user information are made to the control function 5 (steps 43 and 44). The registration information in this case is
These are the user information 61, subsystem information 62, and client information 63 shown in FIG.

If a transaction has already been started in the third node 2b, that is, if a transaction identifier with the same name exists in the transaction management table 50b, the previous transaction state is taken over (steps 45 and 46). Thereafter, the result of the database processing of the request is transferred to the client node 2a via the communication line 1 (steps 47 and 48). The distributed database management function 7a of the client node 2a passes the processing result to the UAP 10a via a path reverse to that at the time of the request.
In the case of a transaction end, a transaction end process is performed via a similar route.

When a processing request is issued from the UAP 10b of the node 2b, the transaction processing is executed in the reverse mode, that is, the node 2b is a client node and the node 2a is a required server node.

Next, FIG. 1 (c) shows an operation when a display request of a client transaction is issued from the administrator terminal 3a to the distributed database management function 7a during execution of the above-mentioned system.
It will be described based on.

When a display request of a client transaction is made from the administrator terminal 3a to the distributed database management function 7a,
The distributed database management function 7a searches the transaction management table 50a (step 101), and based on the activity identifier 53 corresponding to the transaction identifier 51,
The detailed information of the activity is requested to the control function 5a (step 103). The control function 5a searches the activity management table 20a (step 106), and passes detailed information of the activity, subsystem specific information 25, and user information 23 (see FIG. 3) to the distributed database management function 7a (step 106). 108).

The distributed database management function 7a assembles the passed activity information, subsystem specific information 25, user information 23, and transaction information (step 104), and stores the transaction state display information 80 (see FIG. 7) in the client node as an administrator. Output to the terminal 3a (step 105).

In addition, the distributed database management function 7b
If a display request for a server transaction is made, the distributed database management function 7b searches the transaction management table 50b and, based on the activity identifier 53 corresponding to the transaction identifier 51, the control function 5b Request more information. The control function 5b searches the activity management table 20a and passes detailed information of the activity, subsystem-specific information, and user information 23. The distributed database management function 7b assembles the passed activity information, subsystem-specific information, user information, and transaction information, and outputs transaction status display information 90 in the server node to the administrator terminal 3b.

When a failure occurs in the distributed database management function 7a, an activity status display request is made to the control function 5a. Hereinafter, this will be described with reference to FIG.

The control function 5a searches the activity management table 20a (step 106), assembles the activity detail information and the user information (step 108), and displays them on the administrator terminal 3a. At this time, for the user information, the user information management table 30a is searched based on the function unit type 24 of the activity management table 20a, and a user information format table 35 corresponding to the function unit is obtained. Edit the user information 23 according to the format (step 110),
It is displayed on the administrator terminal 3a (step 111).

Further, when a failure occurs in the distributed database management function 7b, the user information format table 35 corresponding to the function unit is obtained by the same operation as above, and the user information 23 is edited according to the format and managed. Is displayed on the user terminal 3b.

Unlike the above embodiment, a system in which the user information format management table is registered in advance on a disk or the like, a system in which the user information format is specified in advance by the system, and conversely, subsystem specific information is included as user information. Method, method of including user information in transaction identifier, or
It is also possible to change the method of registering user information for each processing request.

〔The invention's effect〕

As described above, according to the present invention, at the start of a transaction, user information is acquired by the user information acquiring means of the client node, the information is retained by the retaining means, and, if necessary, via the mutual communication means. Contacting the server node, and when a display request of the information is generated in each node, the information is displayed by the display means of each node, so that the system operator can immediately understand the information. This has a remarkable effect that the transaction state display management method of the distributed database system can be realized.

[Brief description of the drawings]

FIG. 1 is a flowchart showing the operation of one embodiment of the present invention, FIG. 2 is a block diagram of the distributed database system of the embodiment, FIG. 3 is a diagram showing a format of an activity management table, and FIG. FIG. 5 is a diagram showing a format of a transaction management table, FIG. 6 is a diagram showing a user information communication format, and FIG. 7 is a diagram showing a transaction status information display format. 2a, 2b: node, 3a, 3b: system administrator terminal, 4a, 4b: nonvolatile memory, 5a, 5b: control function, 7a, 7b: distributed database management function, 9a, 9b: DC management function, 10a, 10b : UAP, 20a, 20b:
Activity management table, 30a, 30b: user information format management table, 50a, 50b: transaction management table.

Claims (3)

(57) [Claims] 1. An online system having at least a plurality of nodes each having a processor and a database and a communication network interconnecting the plurality of nodes, wherein a process of accessing a database of the plurality of coupled nodes is performed. A distributed database system configured to process at each node and to end the transaction by synchronizing between the nodes at the end of the transaction; Means for holding and interconnecting the information, and means for displaying the information, wherein at the start of the transaction, the transaction start node acquires the user information by the user information obtaining means, and the information is stored by the holding means. And, if necessary, through the interconnecting means The other nodes, and when a display request for the information is generated at each node, the information is displayed by the display means of each node, thereby managing the execution status of the transaction. A transaction status display management method for a distributed database system. 2. When a program or a system constituting each of the nodes is composed of a plurality of independent function units or subsystems, the user information is exchanged between the respective function units or subsystems. 2. The transaction status display management method for a distributed database system according to claim 1, wherein the transaction status is managed. 3. The system according to claim 1, wherein a configuration format of said user information is communicated between said functional units or subsystems, and said information is displayed in accordance with said format when a display request for said information is made. Item 3. A transaction status display management method for a distributed database system according to Item 2.