JP2000137620A - Method and system for changing program of transaction processing system and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a transaction multiplex information processing system capable of changing a software version in operation, and an exclusive control method. SOLUTION: Operating software and new software are simultaneously executed at the time of changing software, and a new transaction reaching an access controlling part 130 and a transaction reaching the access controlling part before the change of software are simultaneously processed respectively by the new software and the operating software. At that time, the transaction in the new software prepares exclusive information related with data to be inputted and outputted on the new software by using a mutual exclusive control part so that the transactions in the both software can operate the input and output of data without any contradiction, and the uniqueness of the data can be guaranteed by temporarily invalidating a data buffer part. When all the transactions in the operating software are ended, the operating software is stopped so that the change of the software can be operated.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a transaction multiplexing information processing system for processing a plurality of transactions in parallel, and more particularly, to an exclusive control mechanism for data input / output of transactions, such as a database management system, and the like. The present invention relates to a technique for changing software such as a transaction processing program in a transaction multiplexed information processing system having an output buffering mechanism to another software or another version during system operation.

[0002]

2. Description of the Related Art Hitherto, a change in software version such as a transaction processing program or a change in a software product in an information processing system has required a stop of the system. Therefore, in order to make software changes without forcibly stopping the transaction, the information processing system must be planned to be stopped, and transactions that are not completed by the information system suspension time and transactions that are entered during the information processing system suspension period must be entered by the user. Had to be banned or put on hold by the system. As a result, changing the software of the information processing system has been a difficult task with restrictions on the system use time for the user and restrictions on the software change time for the system administrator.

As a method of changing software during system operation, a non-stop maintenance method of a disk control device and a disk control device have been proposed in Japanese Patent Laid-Open No. 6-309117. Yes, a single volume has a plurality of clusters which are a group of disk access processing units, each of the clusters has an independent software execution area, does not require exclusive control over a plurality of different data I / Os, and The system does not have a data input / output buffer. Further, the method of software change in Japanese Patent Application Laid-Open No. 6-309117 discloses a method of temporarily disabling the acceptance of data input / output requests sequentially from a part of a cluster, and when the data input / output in the corresponding cluster is completed, the software execution area of the corresponding cluster is changed. By loading the target version software, the software of all the clusters of the disk controller can be changed without stopping completely.

[0004]

However, in a database management system, since multiplexed transaction processing units do not always have independent software execution areas, it is not possible to change software that processes some transaction processing units. Impossible. Further, since the database management system requires exclusive control over a plurality of data inputs and outputs, when a plurality of software are operated in parallel, it is necessary to share exclusive information between transaction processing units of different software. Further, since the database management system generally has a buffer for buffering data input / output for speeding up, a means for guaranteeing the uniqueness of data among a plurality of software when software is changed is required. For the above reasons, the method proposed by JP-A-6-309117 is not suitable for changing the software of the database management system.

According to the present invention, in a transaction multiplexed information processing system in which a multiplexed transaction execution unit does not have an independent software execution area, software in operation of a system can be dynamically changed from running software to new software. It is assumed that.

Further, the present invention provides a new software system that does not cause inconsistency in exclusive control even when a transaction is being processed by operating software when a software having an exclusive control mechanism for data input / output is changed during operation. To process a new transaction.

Further, according to the present invention, when software is changed during operation of a system provided with a buffer for buffering data input / output, different software guarantees data uniqueness with a data storage unit during parallel operation. Is made possible.

[0008]

The information processing system according to the present invention has an access control unit. The access control unit receives a transaction arriving at the information processing system and selectively inputs the transaction to appropriate software.

When the software of the information processing system is changed from running software to new software,
The new software loaded from the new software storage unit by the access control unit and the running software operate in parallel. When new software is loaded, the access control unit transitions from the operating software operating state to the software transition state, and inputs a newly arrived transaction to the new software. In the software transition state, the transaction is processed in parallel by the running software and the new software, and the transaction already input to the running software is not interrupted. Subsequently, when all transactions on the running software have been completed, the access control unit transitions from the software transition state to a new software operation state. As a result, the software can be changed during the operation of the system. In addition, the access control unit manages what was managed as new software as running software, and what was managed as a new software execution area is managed as running software execution area and running software execution area. The new software execution area is managed as a new software execution area, so that subsequent software changes can be performed in the same procedure.

[0010] When the information processing system for which software is to be changed requires exclusive control, the exclusive information of the running software and new software is managed in a software transition state. As a result, the transaction on the running software and the transaction on the new software can perform exclusive control without contradiction.

If the information processing system for which software is to be changed has a data input / output buffer with the data storage unit, the data input / output buffer of the running software and the new software is invalidated in the software transition state. By stopping the operation as described above, data input / output can be performed with the data storage unit and the uniqueness of the data guaranteed.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments of the present invention will be described below in detail by taking a version change of a transaction processing program as an example.

This embodiment will be described for the purpose of changing the current version software to the target version software in the transaction multiplexed information processing system.

FIG. 1 is a block diagram showing the configuration of a transaction multiplexed information processing system which enables a software version change during operation.

In FIG. 1, the access control unit 130 receives a transaction generated by the user application 160 and selectively inputs the transaction to the current version software 111 or the target version software 121. At this time, the access control unit 130 is held in the state storage unit 131, and determines the software version of the input destination depending on the state of the access control unit that changes in the version migration process.

The access control unit 130 loads the target version software 121, requests the data buffers 115 and 125 of the current version software 111 and the target version software 121 to be enabled and disabled, and stores the data buffer enabled state storage units 116 and 126. , Control of the mutual exclusion control flag 124 in the target version software 121, and monitoring of the end of the transaction.

The current version software execution area 110 and the target version software execution area 120 are areas on the main memory for executing the current version software 111 and the target version software 121, respectively. Further, the current version software 111 and the target version software 121 are different versions of software for performing transaction processing in the transaction multiplexed information processing system.

The data storage unit 140 stores data to be processed by the data processing system, and stores the current version software 111 and the target version software 121.
Is shared by

The target version software storage unit 150 is a part where the system administrator stores an executable program of the target version software 121 at the time of a software version change operation.

The exclusive control unit 112 in the current version software 111 and the exclusive control unit 122 in the target version software 121 transmit exclusive information on specified data in the data storage unit 140 in response to a request for a transaction to be processed on each version software. Exclusive information storage unit 113, 1
23 or deleted from the exclusive information storage units 113 and 123.

The exclusive control units 112 and 122 have exclusive information storage units 113 and 123 and mutual exclusion control flags 114 and 124, respectively. The mutual exclusion control flag 124 of the target version software 121 is turned on in the version transition state. In a state where the exclusive control flag 124 is ON, when a transaction on the target version software requests the exclusive control unit 122 to create or delete exclusive information on data in the data storage unit 140, the exclusive control unit 122 It requests the mutual exclusion unit 112 to create and delete the corresponding exclusion information. The exclusive control unit 112 processes the exclusive information creation / deletion request in the same manner as the exclusive information creation / deletion request from the transaction on the current version software 111, and creates the exclusive information in the exclusive information storage unit 113 or the exclusive information storage unit 1
Delete from 13. The exclusive control unit 122 of the target version software 121 is the exclusive control unit of the current version software 111.
Upon detecting the completion of the corresponding exclusive information creation / deletion processing by the 112, the exclusive control unit 123 creates a copy of the corresponding exclusive information or deletes a copy of the corresponding exclusive information from the exclusive control unit 123.
On the other hand, the mutual exclusion control flag 114 of the current version software 111 is not turned on during the version transition process.

The current version software 111 and the target version software 121 have data buffer units 115 and 125, respectively, and hold a partial copy of the data in the data storage unit 140 to perform a buffering operation of data input / output. The speed of data input / output with the data storage unit 140 by a transaction is increased. The data buffer unit 11
5, 125 have data buffer valid state storage units 116 and 126, respectively, for storing that the data input / output buffer operation is in the valid state, the invalid state, or the invalidating state. When the access control unit 130 requests invalidation of the data input / output buffer operation when the software version is changed, the current version software 111 and the target version software 121 are disabled.
Changed the valid state of the data buffer to invalid, and performed the operation of synchronizing the contents of the data buffer units 115 and 125 with the contents of the data storage unit, and the contents of the data buffer units 115 and 125 were synchronized with the contents of the data storage unit. The data input / output buffer operation is stopped by changing the data buffer valid state to the invalid state at the stage.

The system device 100 executes software components such as the access control unit 130, the current version software 111, and the target version software 121.

The user application 160 is a client program using the transaction multiplex information processing system as a server, and a plurality of user applications 160 can exist at the same time.

Although all software components are executed in a single system device 100 in the embodiments of the present invention, it is not necessary that all software components be executed in a single system device.

In the method described in the embodiment of the present invention, the access control unit 130 does not change the version. The control method of the mutual exclusion control flags 114 and 124 by the access control unit 130 and the data buffer valid state transition request method are common to different software versions. The data input / output unit and data input / output procedure with the data storage unit 140 are common to different software versions. The procedure for creating, deleting, and confirming the presence / absence of exclusive information for exclusive control units of different software versions is common to different software versions.

Prior to the description of the software version changing method of the present invention, a state in which transactions are multiplexed and processed in a transaction multiplexing information processing system will be described with reference to FIG. FIG. 2 is a conceptual diagram showing a transaction execution unit for processing a transaction multiplexed in software and a transaction processing period.

Inside the current version software 200, there are transaction processing units 210, 220 and 230 for processing transactions in a multiplex manner, and transactions 211, 212, 221 and 222 having a certain processing period in each transaction processing unit. 231 and 232 are processed. Here, the horizontal axis in FIG. 2 is time. As described above, a plurality of transactions are being executed at the same time as a certain period of time, and the transaction in the current version software is not necessarily interrupted unless the input of a new transaction is stopped. Similarly, the target version software
Inside 250, transaction processing units 260, 270, 280
In each transaction processing unit, transactions 261, 262, 271, 272, 281, and 282 are processed.

In the version transition state according to the present invention, the current version software 200 and the target version software 250 are executed in parallel, and respective transactions are processed in parallel by both versions of software.

Next, based on FIGS. 1, 8, 9 and 10,
Exclusive information structure and exclusive control processing will be described. 8 is a data storage format in the data storage unit 140, FIG. 9 is a structural diagram of exclusive information, and FIG. 10 is a table showing exclusive types of exclusive information and exclusive information creation conditions.

The data in the data storage section 140 is a data storage section 801 for storing the data itself, a data identifier storage section 802 for storing a data identifier for uniquely identifying the data in the data storage section 140, and a data storage section. 802 and 802.

The exclusive information is a data identifier storage unit 90 for storing a data identifier for identifying a data input / output unit on the data storage unit 140 for which input / output is exclusively managed.
1 and a transaction identifier storage unit 902 for specifying the transaction that created the exclusion information, and an exclusion type storage unit 903 for storing the type of exclusion control.

In this embodiment, it is assumed that there are two types of exclusive control: shared exclusive and exclusive exclusive. As shown in FIG. 10, the exclusion information whose exclusion type is shared exclusion indicates that a transaction different from the one that created the exclusion information has the exclusion type of exclusion type shared exclusion information after the data input / output unit that has the same data identifier. , The creation of exclusive information having the exclusive type of exclusive exclusion is prohibited. Also, in the exclusion information whose exclusion type is exclusive exclusion, a transaction different from the one that created the exclusion information creates exclusion information of the exclusion type shared exclusion or occupation exclusion for a data input / output unit having the same data identifier later. Prohibit that.

In the transaction multiplexing information processing system, in order for each transaction to perform a data input / output unit with the data storage unit without inconsistency, the data identifier of the data input / output unit and the transaction It is necessary to create exclusion information that has a transaction identifier of, and has an exclusion type of shared exclusion. Similarly, when outputting the data input / output unit to the data storage unit 140, it is necessary to create exclusive information having the data identifier of the data input / output unit and the transaction identifier of the transaction, and having the exclusive type of exclusive exclusion. If creation of exclusive information is prohibited by the already created exclusive information, all exclusive information that prohibits creation of exclusive information is deleted, and it is necessary to retry creating exclusive information until exclusive information is created. There is. The exclusive information can be deleted when the input / output of the data input / output unit from the data storage unit or the output to the data storage unit is completed. Also, in order to perform consistent data input / output between multiple related data input / output units, the created exclusive information may be retained until input / output of all related data input / output units is completed. It is possible.

Next, referring to FIGS. 1 and 4, the flow of processing of a transaction input to the current version software 111 in the current version operation state in which the software version is not changed will be described. FIG. 4 is a flowchart showing a processing procedure from the input of a transaction to the end.

The transaction input from the user application 160 is input to the current version software 111 via the access control unit 130 (step 40).
0). The entered transactions are decomposed into exclusive information creation requests, deletion requests, and data input / output requests for data stored in a series of data storage units, and are taken out one by one from the current version software 111 (step 4).
01).

If the extracted request is an exclusive information creation request, the mutual exclusion control flag 114 is checked (step 411). In the current version software operating state, the mutual exclusion control flag 114 is off and step 412 is executed. , 413 is not processed and proceeds to step 414. In step 414, the exclusion control unit 112 checks the exclusion information in the exclusion information storage unit 113. If the exclusion information creation request is not prohibited by another exclusion information, the exclusion control unit 112 creates the exclusion information in the exclusion information storage unit 113.
If the current version software detects that step 414 has failed because the corresponding exclusive information creation request is prohibited by the already created exclusive information (step 4
15) Returning to step 414, this process is repeated until all exclusive information that prohibits creation of the exclusive information is deleted. If the exclusion request creation request succeeds, the process proceeds to step 403.

If the extracted request is an exclusive information deletion request, the corresponding exclusive information in the exclusive information storage unit 113 of the current version software 111 is deleted (step 421).
Next, the mutual exclusion control flag 114 is checked (step 42).
2) In the current version software operation state, the mutual exclusion control flag 114 is off, and the process proceeds to step 403 without performing step 423.

If the retrieved request is a data input / output request, the buffer valid state storage unit 116 is checked (step 431). Therefore, data input / output with a buffer operation is performed (step 432), and the process proceeds to step 403.

In step 403, it is determined whether or not an exclusive information creation, deletion request, or data input / output request in the transaction still remains. And fetch the next exclusive information creation, deletion request, or data input / output request. If all exclusive information creation / deletion requests and data input / output requests for the transaction have been completed, the transaction is terminated (step 40).
Four).

Next, the flow of the software version change process of the transaction multiplexed information processing system will be described with reference to FIGS. FIG. 3 is a flowchart showing the entire flow of the software version change processing procedure.

The target version software storage unit 15 is provided by the administrator of the transaction multiplexing information processing system.
The execution format of the target version software 121 is stored in 0, and when an instruction to start the version change process is given to the access control unit 130, the software version change process is started (step 300).

First, the access control unit 130 loads the executable program of the target version software 121 in the target version software storage unit 150 into the target version software execution area 120 and executes it (step 30).
1).

When the target version software 121 is executed, the access control unit 130 transitions the state storage unit 131 to the version transition preliminary state, and instructs the current version software 111 to stop the input / output buffer operation with the data storage unit. It is instructed that the data buffer valid state storage unit 116 is set to the buffer invalid state. Current version software 111
Starts a data synchronization operation between the data buffer unit and the data storage unit after temporarily transitioning the data buffer valid state storage unit 116 to the buffer invalidating state. While the data buffer valid state storage unit 116 is in the buffer invalidating state, the current version software suspends the data input / output request from the transaction in the current version software and waits for the transaction. When the data in the data buffer unit and the data in the data storage unit are synchronized, the current version software 111 sets the buffer valid state storage unit 116 to an invalid state. The access control unit 130 also instructs the target version software 121 to change the data buffer valid state storage unit 126 into the buffer invalid state. Since the target version software 121 has not yet received the transaction at this point, the data in the data buffer unit 125 and the data storage unit 140 are synchronized, and the buffer valid state storage unit immediately transitions to the buffer invalid state. (Step 302).

The buffer valid state storage unit 116 of the current version software 111 and the target version software 1
When both the buffer valid state storage units 126 detect that the buffer is invalid, the access control unit 130 turns on the mutual exclusion control flag 124 of the target version software, and sets the state storage unit 131 to the version transition state. In the version transition state, a new transaction arriving at the access control unit is processed by the target version software 121 in place of the current version software 111 (step 303).

In the version transition state, the current version software 111 continues to process the transaction requested before the transition to the version transition state, and at the same time, the target version software 121 processes a newly arrived transaction. Further, the access control unit 130 monitors completion of all transactions on the current version software 111 (step 304).

When the access control unit 130 detects that all the transactions on the current version software 111 have been completed, the access control unit 130 turns off the mutual exclusion control flag 124 of the target version software 121 and stores the data buffer valid state storage unit in the target version software 121. 126 is set to the buffer valid state, and the state storage unit 131 is set to the target version software operation state (step 30).
Five). The target version software 121 resumes the data input / output buffering operation by setting the data buffer valid state storage unit 126 to the buffer valid state, and sets the mutual exclusion control flag 12.
4 is turned off, the current version software 111
Cancels exclusive control in.

Subsequently, the access control unit 130 instructs the current version software 111 to stop, and when the current version software 111 stops, manages what was managed as the target version software 121 as the current version software 111, What was managed as the target version software execution area 120 is the current version software execution area 110, and what was managed as the current version software execution area 110 is managed as the target version software execution area 120 (step 306),
The status storage unit 131 is set to the current version operation status again to prepare for the next software version change (step 306).

According to the above processing procedure, the version of the software of the transaction multiplexing information processing system can be changed during operation.

Next, with reference to FIGS. 1, 5, 6, and 7, a description will be given of the state transition of the state storage unit 131 and the processing accompanying the state transition in the software version change of the transaction multiplexed information processing system. FIG. 5 is a state transition diagram of the access control unit regarding a software version change. FIG. 6 is a flowchart showing a processing procedure when shifting from the current version software operation state to the version migration state via the version migration preliminary state in the state transition diagram of FIG. FIG. 7 is a flowchart showing a processing procedure when a transition is made from the version transition state to the target version software operation state via the target version operation state in the state transition diagram of FIG.

When the software version change operation is not performed, the status storage unit 131 is in the current version software operation state 500, and the current version software 111 is loaded in the current version software execution area 110. In this state, the user application 160
When a transaction is submitted from, the access control unit
130 shows the transaction as current version software 1
11 and return to the current version software operation state 500. When the system administrator stores the execution format of the target version software 121 in the target version software storage unit 150 and issues an instruction to change the version to the access control unit 130, the access control unit 130 stores the state storage unit 131 in the version transition preliminary state 501. And the procedure for changing the software version is started (step 600).

In the version transition preliminary state 501, first,
The access control unit 130 loads the executable program of the target version software 121 from the target version software storage unit 150 into the target version software execution area 120 and executes the program (step 601).

The new transaction arriving in the preliminary version migration state 501 is continuously processed by the current version software 111 by the access control unit 130, and the state storage unit 131 returns to the preliminary version migration state 501 again. When the loading of the target version software 121 is completed,
The access control unit 130 instructs the current version software 111 and the target version software 121 to put the buffer valid state storage units 116 and 126 into the buffer invalid state in order to guarantee the uniqueness of the data in the data storage unit 140 (step 602). .

When the access control unit 130 detects that the buffer valid state storage unit 116 of the current version software 111 and the buffer valid state storage unit 126 of the target version software 121 enter the buffer invalid state, the target version software 121 performs mutual exclusion control. The access control unit 130 instructs to turn on the flag 124. Subsequently, the access control unit 130 changes the processing of the subsequent new arrival transaction to the target version software 121 (step 603), and the state storage unit 13
1 is set to the version transition state 502 (step 604).

In the version transition state 502, a newly arrived transaction arriving at the access control unit 130 is processed by the target version software 121, and the state storage unit 131 returns to the version transition state. A new transaction instructed to be executed by the target version software 121 is processed by the target version software 121, but at the same time, a transaction input before the transition to the version transition state 502 is continued to be processed on the current version software 111. The access control unit 130 constantly monitors transactions on the current version software 111 and the target version software 121 (step 700).

When the access control unit 130 detects the end of the last transaction of the current version software 111, the access control unit 130
21 is instructed to enable the data buffer effective state storage unit 126 to enable the buffer, and to instruct the mutual exclusion control flag 124 to be turned off, thereby setting the target version operation state 503 (step 701).

In the target version operation state 503, the data buffering operation of the data buffer unit 125 with the data storage unit 140 is resumed, and the exclusive information storage unit 113 of the current version software 111 by the target version software 121 is resumed.
Creation of exclusive information to the server and deletion of exclusive information by the exclusive information storage unit 113 are stopped. Next, the current version software 111
Is instructed to stop (step 702).

Further, the access control unit 130 manages what was managed as the target version software 121 as the current version software 111 and what is managed as the current version software execution area 110 as the target version software execution area 120. What was managed as the target version software execution area 120 is changed to the current version software execution area 11
By managing it as 0, it prepares for the next version change (step 703).

Subsequently, a transition is made to the current version software operation state 500, and a series of procedures for changing the software version is completed. (Step 704).

Here, the current version software 111 is in the preliminary version migration state 501, and the target version software 121 is in the target version software operation state 503.
Since the transaction is processed by at most a single version of software, the transaction processing flow is exactly the same as the transaction processing in the current version software operating state described above with reference to FIGS. 1 and 4. .

Next, the flow from the start of the processing by the target version software 121 of the transaction in the version transition state to the end of the transaction processing will be described with reference to FIGS.

In the version transition state, a transaction requested to be processed by the user application 160 is started by the target version software 121 via the access control unit 130 (step 400). The transaction that has begun processing is decomposed into a series of exclusive information creation, deletion requests, and input and output requests for data stored in the data storage unit.
One by one is extracted from 121 (step 401).

If the extracted request is an exclusive information creation request, the mutual exclusion control flag 124 is checked (step 411). Since the mutual exclusion control flag 124 of the target version software 121 is ON in the version transition state, the exclusion control unit 122 requests the exclusion control unit 112 of the current version software 111 to create exclusion information on the corresponding data.
(Step 412). The exclusive control unit 112 reports that step 412 failed because the exclusive information that inhibits the creation of exclusive information by a transaction on the target version software exists in the exclusive information storage unit of the current version software 111.
Is detected (step 413), the process returns to step 412, and this process is repeated until other exclusive information that prohibits the creation of the exclusive information is deleted. If the exclusion request creation request succeeds, the process proceeds to step 414. In step 414, the exclusive control unit 122 attempts to create the corresponding exclusive information in the exclusive information storage unit 123.
There is no exclusive information that inhibits the creation of the corresponding exclusive information that could be created in the exclusive information storage unit 123 of the target version software 121, and the creation of the corresponding exclusive information succeeds (step 415), and the process proceeds to step 403. move on.

If the extracted request is an exclusive information deletion request, the corresponding exclusive information in the exclusive information storage unit 123 of the target version software 121 which is the own version software is deleted (step 421). Subsequently, the mutual exclusion control flag 124 is checked (step 422). In the target version software in the version transition state, the mutual exclusion control flag 124 is on, so the current version software 111
Requesting the exclusive control unit 112 to delete the corresponding exclusive information in the exclusive information storage unit 113 (step 423), and proceed to step 403.

If the fetched request is a data input / output request, the buffer valid state storage unit 126 is checked (step 431). Since it is in an invalid state, data input / output without buffer operation is performed (step 433), and the process proceeds to step 403.

In step 403, it is determined whether there remains an exclusive information creation, deletion request, or data input / output request in the transaction. If there is an exclusive information creation, deletion request, or data input / output request, the process proceeds to step 403. 401
And fetch the next exclusive information creation, deletion request, or data input / output request. If all exclusive information creation / deletion requests and data input / output requests for the transaction have been completed, the transaction is terminated (step 40).
Four).

Next, with reference to FIGS. 1 and 4, a description will be given of the flow of processing until the end of a transaction that has been input to the current version software 121 in the version transition state.

In the version transition state, a new transaction is not input to the current version software 111, so that the description of steps 400 and 401 is omitted.

If the next request extracted from the entered transaction is an exclusive information creation request, the mutual exclusion control flag 114 is checked (step 411). The mutual exclusion control flag 114 is off, and steps 412 and 413
Go to step 414 without being processed. In step 414, the exclusion control unit 112 checks the exclusion information in the exclusion information storage unit 113. If the exclusion information creation request is not prohibited by another exclusion information, the exclusion control unit 112 creates the exclusion information in the exclusion information storage unit 113. If the current version software 111 detects that step 414 has failed because the corresponding exclusive information creation request is prohibited by other exclusive information (step # 415), the process returns to step 414 and inhibits creation of the corresponding exclusive information. This operation is repeated until all exclusive information is deleted. If the exclusion request creation request succeeds, the process proceeds to step 403.

If the extracted request is an exclusive information deletion request, the corresponding exclusive information in the exclusive information storage unit 113 of the current version software 111 which is the own version software is deleted (step 421). Subsequently, the mutual exclusion control flag 114 is checked (step 422). However, even in the version transition state, the mutual exclusion control flag 114 of the current version software is off, and the process proceeds to step 403 without performing step 423.

If the extracted request is a data input / output request, the buffer valid state storage unit 116 is checked (step 431). Invalid state or buffer invalidating state. If the buffer valid state storage unit 126 is in the buffer invalidating state,
Returning to step 431, this operation is repeated until the buffer valid state storage unit 116 enters the buffer invalid state. If the buffer valid state storage unit 116 is in the buffer invalid state, data input / output without buffer operation is performed (step 433), and step 4
Go to 03.

In step 403, it is determined whether or not there remains an exclusive information creation, deletion request, or data input / output request in the transaction. If an exclusive information creation, deletion request, or data input / output request remains, the process proceeds to step 403. 401
And fetch the next exclusive information creation, deletion request, or data input / output request. If all exclusive information creation / deletion requests and data input / output requests for the transaction have been completed, the transaction is terminated (step 40).
Four).

As described with reference to FIG. 3, the information processing system is in the version transition state when the target version software 121 processes the first transaction. In the version transition state, all exclusive information created in the exclusive information storage unit 123 of the target version software 121 is also created in the exclusive information storage unit 113 of the current version software 111, and the current version software 1
The exclusive control unit 112 manages the information together with the exclusive information created only in the 11 exclusive information storage units 113. Further, in the version transition state in which the current version software 111 and the target version software 121 are executed simultaneously, the buffering operation of the data input / output to / from the data storage unit 140 by the data buffer units 115 and 125 is in an invalid state or in an invalid state. In this state, data input / output to / from the data storage unit 140 is awaited, so that data input / output to / from the data storage unit 140 by each version of software does not impair the uniqueness of data.

As described above, exclusive control regarding data input / output in the data storage unit is required, and the version of the software of the transaction multiplexed information processing system having the data input / output buffer mechanism can be changed during operation.

As a second embodiment, as another method for performing exclusive management without inconsistency between the current version software and the target version software, a method using a shared memory for the exclusive information storage unit can be considered.

FIG. 11 is a block diagram showing the configuration of a transaction multiplexed information processing system that enables a software version change using a shared memory in an operating exclusive information storage unit.

FIG. 11 shows that the exclusive information storage units 113 and 123 in FIG.
1 is arranged on the shared memory 1170 as 1190 and shared by the exclusive control units 1112 and 1122 of the current version software 1111 and the target version software 1121.
The other parts have the same configuration except that there are no mutual exclusion control flags 114 and 124 and that the shared memory reference update exclusive management unit 1180 exists on the shared memory. The shared memory is a storage space that can be commonly referred to by the exclusive control unit 1112 of the current version software 1111 and the exclusive control unit 1122 of the target version software 1121.

The exclusive control unit 1112 in the current version software 1111 and the exclusive control unit 1122 in the target version software 1121 store exclusive information on specified data in the data storage unit 1140 in response to a request for a transaction to be processed on each version software. Exclusive information storage 1190
Created or deleted from the exclusive information storage unit 1190.

Further, on the shared memory 1170, there is a shared memory reference update exclusive management unit 1180. The shared memory reference update exclusion management unit 1180 provides a new exclusion to the exclusion information creation unit 1190 while one of the exclusion control units 1113 and 1123 refers to the exclusion information in the exclusion information storage unit 1190 and updates it. Exclusive information for not updating information, exclusive reference management unit for reference update
By turning on the off state of 1180, the right to refer to and update the shared memory can be obtained. Exclusive control unit is 1112, 11
One of the 22 refers to the reference update exclusion manager 1180, and then confirms that the switch is off.
It is assumed that the hardware as the operation board of the information processing system guarantees that the other exclusive control unit does not refer to the reference update exclusive management unit 1180 during a series of operations until turning on.

In this embodiment, the access control unit changes to the version transition state, and at the same time, the access control unit changes the input destination of the new transaction to the target version software, so that the target version software can immediately accept a new transaction. Becomes
Further, since transactions are processed in parallel in the current version software and the target version software, the transactions already input to the current version software are not interrupted. Further, since the access control unit automatically stops the current version software when all the transactions on the current version software are completed, the user does not need to be conscious of stopping the current version software.

In the version transition state, the target version software creates exclusive information that can be referenced by the exclusive control unit of the current version software and then creates exclusive information that can be referenced by its own exclusive control unit. Transactions on the version software and transactions on the target version software can perform exclusive control without contradiction.
Therefore, even in an information processing system that requires exclusive control over data input / output, a new transaction can be executed with the target version software without waiting for the end of the transaction on the current version software and without aborting the transaction on the current version software. You can change the software version while accepting it at any time.

When all transactions on the current version software have been completed, the access control unit transitions to the target version software operation state, and at this point, mutual exclusion control on the current version software by the transactions in the target version software is stopped. Therefore, the overhead due to the mutual exclusion control between the current version software and the target version software can be limited to the version transition state.

In the version transition state, the data buffer is disabled, and the data input / output buffering operation by the data buffer unit is stopped, so that the current version software and the target version software operate in parallel, and each transaction is processed in parallel. This also enables data input / output that guarantees data uniqueness with the data storage unit. Since the data input / output buffering operation by the data buffer unit is not stopped except at the time of version change, high-speed data input / output with the data storage unit is possible.

[0084]

According to the present invention, the burden on the system administrator in changing the software of the transaction processing system can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of an embodiment.

FIG. 2 is a conceptual diagram illustrating an existing period of a transaction according to the embodiment.

FIG. 3 is a flowchart illustrating a processing procedure of a software version change.

FIG. 4 is a flowchart illustrating a processing procedure of a transaction in the transaction multiplexed information processing system.

FIG. 5 is a state transition diagram illustrating a state of an access control unit.

FIG. 6 is a flowchart illustrating a processing flow of an access control unit when transitioning to a version transition state.

FIG. 7 is a flowchart illustrating a process flow of an access control unit when transitioning to a current version software operation state.

FIG. 8 is a structural diagram illustrating a data format in a data storage unit.

FIG. 9 is a structural diagram of exclusive information stored in an exclusive information storage unit.

FIG. 10 is a table showing types of exclusive information and exclusive information creation conditions for each type.

FIG. 11 is a block diagram illustrating a configuration of a second example.

[Explanation of symbols]

100: System unit, 110: Current version software execution area, 120: Target version software execution area, 111: Current version software, 121: Target version software, 112, 122: Exclusive control unit, 113, 123: Exclusive information storage unit, 114, 124: Mutual exclusion Control flags, 115, 125: Data buffer section, 116, 126: Buffer valid state storage section, 130: Access control section, 140: Data storage section, 150: Target version software storage section, 160: User application, 200: Current version software, 250 ... Target version software, 210,220,230,260,270,280… logical transaction processing unit, 211,212,221,222,231,232,261,262,271,272,281,282…
Existence period of each transaction, 1100: system unit, 1110: current version software execution area, 1120: target version software execution area, 1111: current version software, 1121: target version software, 1112, 1122: exclusive control unit, 1113, 1123 ... Data buffer unit, 1114, 1124: Buffer effective state storage unit, 1130: Access control unit, 1140: Data storage unit, 1150: Target version software storage unit, 1160: User application, 1170: Shared memory, 1180: Shared memory Exclusive exclusion management unit for update, 1190 ... Exclusive information storage unit.

Claims (9)

[Claims] 1. A transaction processing system for processing a plurality of transactions in parallel, wherein the first program and the second program are executed when a first program used in the system is changed to a second program. A transaction processing system comprising: an execution area for executing the transaction processing system; and an access control unit for selecting whether the transaction received by the transaction processing system is processed by the first program or the second program of the system. . 2. The transaction processing system according to claim 1, wherein a data storage unit storing data used by said first program and said second program is temporarily stored when said data in said data storage unit is used. And a data buffer unit for storing the data, and an identifier indicating whether data in the data buffer unit is valid when the first program is changed to the second program. system. 3. The transaction processing system according to claim 1, wherein a data storage unit storing data used by the first program and the second program, and exclusive control for exclusively controlling access to the data storage unit. A transaction processing system comprising a unit. 4. A program change method for a transaction processing system for processing a plurality of transactions in parallel, wherein the first program and the second program are changed when a first program used in the system is changed to a second program. In the execution area, and the access control unit selects whether the transaction received by the transaction processing system is processed by the first program or the second program of the system. How to change the program of the transaction processing system. 5. The method according to claim 4, wherein when the first program and the second program use data in a data storage unit, the data in the data storage unit is temporarily stored. A program changing method for a transaction processing system, comprising referring to an identifier indicating whether data in a data buffer unit to be stored is valid, and processing the transaction using data in a data storage unit if the data is not valid. 6. The program change method for a transaction processing system according to claim 4, wherein when the first program and the second program use data in a data storage unit, the program using the data is an exclusive control unit. Requesting a lock on the data storage unit, the exclusive control unit locking the data storage unit, and permitting the program to access the data storage unit. . 7. A program change method for a transaction processing system for processing a plurality of transactions in parallel, wherein the second program is activated while the first program is operating, and is received before the second program is activated. Transactions are processed by the first program, transactions accepted after starting the second program are processed by the second program, and the first program stops when there are no more transactions to be processed by the first program A method for changing a program of a transaction processing system, comprising: 8. A computer-readable storage medium storing a program for implementing the program change method of the transaction processing system according to claim 4. 9. A computer-readable storage medium storing a program for implementing the program change method of the transaction processing system according to claim 7.