JP2654612B2 - Exclusive weight reduction control method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an exclusive weight reduction control method, and more particularly to an exclusive weight reduction control method for improving processing efficiency in a computer system in which simultaneous updates to shared resources occur.

[0002]

2. Description of the Related Art Conventionally, in this kind of exclusive control method of a shared resource, when a certain transaction program updates the shared resource, the shared resource is locked, and when another transaction program tries to update the same resource, another transaction program locks the shared resource. Exclusive weight for program (WAI
T), exclusive control of the shared resource is performed.

There is also a method for preventing the occurrence of an exclusive wait by locking all resources to be used prior to the start of a transaction program process (for example, see Japanese Patent Application Laid-Open No. H4-22235).

[0004]

In the above-mentioned conventional exclusive control method for shared resources, when a certain transaction program updates a shared resource, the shared resource is locked and the update processing from another transaction program is exclusively waited. As a result, since exclusive control of the shared resource is performed, there is a problem that a transaction program using the shared resource cannot be run multiple times, and it is difficult to improve processing efficiency.

Further, in a method for preventing the occurrence of an exclusive wait by locking all resources used prior to the start of transaction program processing, a plurality of transaction programs using a certain resource can be started simultaneously. However, there is a problem that it is difficult to improve the processing efficiency.

SUMMARY OF THE INVENTION In view of the foregoing, it is an object of the present invention to provide a first transaction program that updates a resource and then commits (COMMIT) or rolls back (ROLLB).
When the second transaction program updates the same resource in a state where the transaction end processing by ACK) is not performed, the second transaction program updates the resource without performing an exclusive wait, so that a plurality of transactions are performed. An object of the present invention is to provide an exclusive weight reduction control method for reducing an exclusive weight when a program updates the same resource.

[0007]

According to the exclusive weight reduction control method of the present invention, after the first transaction program has updated resources, the transaction end processing by commit or rollback has not yet been performed.
In a case where the second transaction program updates the same resource, the second transaction program updates the resource without performing an exclusive wait when updating the resource, and the second transaction program executes the first transaction. When the transaction end processing is performed prior to the program, the transaction end processing of the second transaction program is waited until the transaction end processing of the first transaction program is completed,
When the first transaction program commits, the second transaction program rolls back, and when the first transaction program rolls back, the second transaction program commits, and the first transaction program When the transaction end processing is performed prior to the second transaction program, when the first transaction program commits, the second transaction program immediately rolls back, and the first transaction program rolls back. The second transaction program continues processing when it is backed up, thereby realizing multiple runs of the transaction program for updating the same resource. And it features.

[0008]

Next, the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an operating system for implementing the exclusive weight reduction control method according to the present invention. The operating system includes a transaction dispatch unit 100, a resource update unit 200, a transaction end processing unit 30
0, a resource commit unit 400, a resource rollback unit 500, and a transaction management queue (TCQ) 6.
00 and a transaction control block (TCB) 70
0, a resource management block (RCB) 800, an update status management block (UCB) 900, and a work area 1000.

[0010] Transaction dispatching means 100
Dispatches transaction programs in the executing state, the executable state, and the waiting state.

As shown in FIG. 2, the resource updating means 200 includes a resource updating function 210 and a management information updating function 220.
To the transaction program.

The transaction end processing means 300
As shown in FIG. 2, a commit availability determination function 310 is provided to the transaction program.

As shown in FIG. 2, the resource commit unit 400 provides a transaction program with an update resource commit function 410 and a management information update function 420.

The resource rollback means 500 provides an update resource rollback function 510 and a management information update function 520 as shown in FIG.

Transaction management queue (TCQ) 6
00 is the status of the transaction program (running,
This is a queue for managing a transaction program for each (executable, waiting). As shown in FIG. 3A, the transaction management queue (TCQ) 600 includes a running TCB head address 611, a running TCB last address 612, an executable TCB head address 621, an executable TCB last address 622, and a waiting TCB. Start address 631 and TCB last address during wait 632
have.

Transaction control block (TCB)
Reference numeral 700 denotes a memory area created for each transaction program at the start of the transaction program, and is used for managing the state of the transaction program. Transaction control block (TCB) 700
Is the next TCB address 71 as shown in FIG.
1, the previous TCB address 712, the leading UCB address 72 in the transaction (hereinafter abbreviated to TX as appropriate)
1, a final UCB address in TX 722, rollback acceptability 731, rollback request presence or absence 732, rollback frequency upper limit 741, rollback frequency 742, and transaction end notification TCB address 751. When the transaction program is rolled back and rescheduled, the transaction control block (TCB) 700 before the rollback is continuously used.

A resource management block (RCB) 800 is an area in a memory created in an exclusive unit of a resource at the time of the first resource update after the start of the computer system, and is used for resource status management. Resource management block (RCB) 800
As shown in FIG. 3C, the start UCB address 811 in the resource, the last UCB address 812 in the resource,
It has a management resource length 821, a rollback count upper limit 831 and a rollback count 832.

Update state management block (UCB) 900
Is an area created for each update of the resource of the transaction program, and for managing the update status of the resource to be updated by each transaction program for each exclusive unit. The update state management block (UCB) 900 includes a TCB address 911 and an RCB address 92, as shown in FIG.
1, TX next UCB address 931, TX previous UCB address 932, resource next UCB address 941, resource previous UCB address 942, work area address 95
Have one.

As shown in FIG. 3 (e), the work area 1000 is used to store a read image / update image of a resource, and is a management resource length of a resource management block (RCB) 800 which manages a resource to be updated. An area of the size indicated by 821 is secured.

Next, the processing of the exclusive weight reduction control method of the present invention configured as described above will be described.

FIG. 4A is a schematic operation diagram for realizing the exclusive weight reduction control method according to the first embodiment of the present invention. FIG. 4B is a schematic diagram of internal processing when implementing the exclusive weight reduction control method of the first embodiment. Hereinafter, the transaction programs are referred to as TX1 and TX2.
And the resource is R1. The transaction management queue is TCQ, and the transaction control block is TCQ.
B, the resource management block is abbreviated as RCB, the update status management block is abbreviated as UCB, and TCQ, TCB, RC
The transaction programs and resources associated with B, UCB and the work area will be shown in the form of arguments in parentheses. Further, TS and TE in the transaction programs TX1 and TX2 mean a transaction start and a transaction end.

When the transaction program TX1 starts, the operating system executes TCB (TX
1) Create 700. Transaction program T
When X1 updates the resource R1, the resource updating means 200 causes the UCB (TX1-R1) 900 and the work area (TX)
1-R1) 1000 is secured and UCB (TX1-R
1) TCB (TX1) in TCB address 911 of 900
700, and RCB (R
1) 800 address, TX next UCB address 931
And NULL in the previous UCB address 932 in the TX, the next UCB address 941 in the resource, and the previous UC in the resource
NULL is set to the B address 942, the address of the work area (TX1-R1) 1000 is set to the work area address 951, and UC is set to the first UCB address 721 in the TX and the last UCB address 722 in the TX of the TCB (TX1) 700.
B (TX1-R1) 900 is set, and RC
Start UCB address 81 in the resource of B (R1) 800
1 and UCB in the last UCB address 812 in the resource
The address of (TX1-R1) 900 is set.

The transaction program TX1
Transaction TX2 asynchronously with the operation of
Is started, the operating system sets the TCB
(TX2) 700 is created. When the transaction program TX2 updates the resource R1 previously updated by the transaction program TX1, the resource updating means 200 secures the UCB (TX2-R1) 900 and the work area (TX2-R1) 1000, and the UCB (T
X2-R1) TCB at TCB address 911 of 900
(TX2) 700 address, RCB address 921 as RCB (R1) 800 address, TX next UCB address 931 and TX previous UCB address 932 as NU
LL, NULL in the next UCB address 941 in the resource,
UCB (TX1-
R1) 900, the address of the work area (TX2-R1) 1000 is set in the work area address 951, and T
First UCB address 72 in TX of CB (TX2) 700
1 and the last UCB address 722 in TX
X2-R1) 900 address is set, and RCB (R
1) U is assigned to the last UCB address 812 in the
The address of CB (TX2-R1) 900 is set, and U
The address of the UCB (TX2-R1) 900 is set to the next UCB address 941 in the resource of the CB (TX1-R1) 900.

Here, the transaction program TX
When the transaction program TX2 performs the transaction end processing before the transaction end processing of the first transaction, the transaction end processing means 300
B (TX2-R1) 900 because the previous UCB address 942 in the resource is not NULL,
Of the transaction program TX1 which is updating the first U.S.
UCB (TX1-R) pointed to by CB address 811
1) TC pointed by 900 TCB address 911
B (TX1) 700 transaction end notification TCB
The address of the TCB (TX2) 700 is set to the address 751, and the transaction end processing is interrupted.

Next, the transaction program TX1
When executing the transaction end processing by the transaction end processing means 300, the commit possibility determination function 310 determines whether or not the commit is possible. If the commit is possible, the commit function 410 of the resource commit means 400 performs the commit processing on the resource R 1. Work area (TX1-R1) 1000 by the management information update function 420
Is released, and the first U in the resources of the RCB (R1) 800
The CB address 811 is the UC to which the next UCB address 941 in the resource of the UCB (TX1-R1) 900 points.
B (TX2-R1) 900
The prior UCB address 942 in the resource of the B (TX2-R1) 900 is changed to the previous UCB address 942 in the resource of the UCB (TX1-R1) 900 (that is, NULL), the UCB (TX1-R1) 900 is released, and the TC
B (TX1) 700 transaction end notification TCB
TCB (TX2) 700 to which address 751 points
Is instructed to perform a rollback, and the transaction program TX2
Rescheduled by 0.

When the transaction program TX1 performs the transaction end processing by the transaction end processing means 300 and performs rollback, the rollback processing for the resource R1 is performed by the rollback function 510 of the resource rollback means 500, and the management information Work area (TX1-R1) 100 by update function 520
0 is released, and the head UCB address 811 in the resource of the RCB (R1) 800 becomes the UCB (TX1-R1) 900
U to which the next UCB address 941 in the resource of
Changed to the address of CB (TX2-R1) 900,
The previous UCB address 942 in the resource of the CB (TX2-R1) 900 is changed to the previous UCB address 942 in the resource of the UCB (TX1-R1) 900 (that is, NULL), and the UCB (TX1-R1) 900 is released.
Transaction end notification TC of CB (TX1) 700
TCB (TX2) 70 to which B address 751 points
0 is instructed to commit.

According to the exclusive weight reduction control method of the first embodiment, the transaction program TX1
When the transaction program TX2 updates the same resource R1 in a state where the transaction end process by commit or rollback is not performed after the update, the transaction program TX2 updates the resource R1 without performing the exclusive wait. , A transaction program TX1 for updating the same resource R1
And TX2.

By the way, in the exclusive weight reduction control method of the first embodiment, no control is performed with respect to the priority of the transaction program, and the resource is accessed first in the transaction program in which the same resource is updated.
The transaction program that has been executed is likely to be processed normally (committable), but the other transaction programs are likely to be rolled back. this
This means that a transaction can be completed in a short time.
Transaction programs with long processing times
If a resource is updated first by a program,
The waiting time at the end of the
Means not complete.

FIG. 5 is a schematic operation diagram for realizing the exclusive weight reduction control method according to the second embodiment of the present invention.
An exclusive weight reduction control method of the second embodiment, in the exclusive weight reduction control method of the first embodiment, originally short
Even if the transaction program is completed in
A long-running transaction program allows
When resources are updated in the
The following operation is different from the general operation for realizing the exclusive weight reduction control method of the first embodiment in order to solve the problem that the processing is not completed easily because the time becomes long .

When the transaction program TX2 performs the transaction end processing, the transaction end processing means 300 updates the same resource R1 first because the previous UCB address 942 in the resource of the UCB (TX2-R1) 900 is not NULL. RCB (R1) knows the existence of the transaction program TX1
TCB of the UCB (TX1-R1) 900 pointed from the head UCB address 941 in the resource 800
TCB (TX1) 700 to which address 911 points
Of the rollback request 731 of the TCB (TX2) 700 and the rollback request of the TCB (TX2) 700.

When committing in the transaction end processing of the transaction program TX2, the commit function 410 of the resource commit unit 400
Is performed on the management information update function 42
0 frees the work area (TX2-R1) 1000,
UCB (TX1-R1) 9 to which the previous UCB address 942 in the resource of UCB (TX2-R1) 900 points
00 in the next UCB address 941 in the UCB (T
X2-R1) Next UCB address 94 in resource of 900
1 (i.e., NULL) and the UCB (TX
2-R1) Next UCB address 941 in the resource of 900
Is NULL, the last UCB address 812 in the resource of the RCB (R1) 800 is changed to the UCB (TX2-
R1) is changed to the value of the previous UCB address 942 in the resource of 900, and the UCB (TX2-R1) 900 is released,
TCB (TX1) to which the TCB address 911 of the UCB (TX1-R1) 900 to which the head UCB address 811 in the resource of the RCB (R1) 800 points
A rollback is instructed to 700, and the transaction dispatcher 100 reschedules the transaction program TX1.

When the transaction program TX2 rolls back in the transaction end processing, the rollback processing for the resource R1 is performed by the rollback function 510 of the resource rollback means 500, and the work area (TX2- R1) 10
00 is released and the UCB pointed to by the previous UCB address 942 in the resource of the UCB (TX2-R1) 900
The next UCB address 941 in the resource of (TX1-R1) 900 is changed to the value of the next UCB address 941 in the resource of the UCB (TX2-R1) 900 (that is, NULL), and the next UCB address in the resource of the UCB (TX2-R1) 900 is changed. U
Since the value of CB address 941 is NULL, RCB
(R1) Last UCB address 812 in resource of 800
Is the previous UCB in the resource of UCB (TX2-R1) 900
Change to the value of address 942 and UCB (TX2-R1)
900 is released. Transaction program TX
1 continues the processing as it is.

According to the exclusive weight reduction control method of the second embodiment, in the transaction program TX1 which is likely to be rolled back because of a long processing time, it is possible to set the rollback reception availability 731 to rollback reception impossibility. If the transaction program TX1
, Even if another transaction program TX2 (short processing time) that attempts to update the same resource R1 as the updated resource R1 executes the transaction end processing in advance, the transaction program TX1 can be processed without being rolled back. There is an advantage. If it is not necessary to give priority to the own transaction program TX2 even after rolling back the other transaction program TX1, a rollback request existence 7
If no rollback request is set in 32, there is an advantage that the processing of another transaction program TX1 does not stagnate.

FIG. 6 is a schematic operation diagram for implementing the exclusive weight reduction control method according to the third embodiment of the present invention.
In the exclusive weight reduction control method of the third embodiment, the following operation is different from the schematic operation for realizing the exclusive weight reduction control method of the second embodiment.

When the TCB 700 is created, the upper limit 741 set by the user is set to the rollback frequency upper limit 741 of the TCB 700, and 0 is set to the rollback frequency 742. Further, every time the transaction program is rolled back, the number of rollbacks 742 of the TCB 700
Is counted up.

When the transaction program TX2 performs the transaction end processing, the transaction end processing means 300 transmits all the UCB (TX2 TX2) created by the transaction program TX2 queued after the first UCB address 721 in the transaction of the TCB (TX2) 700. -R1) previous UC in resource of 900
UCB (TX1-R) pointed to by B address 942
1) TC to which TCB address 911 of 900 points
B (TX1) 700 is compared with rollback frequency upper limit 741 and rollback frequency 742, and rollback frequency 7
When 42 is equal to or greater than the rollback count upper limit 741, the transaction program TX2 performs rollback processing, the transaction program TX1 continues processing, and the transaction program TX2 is rescheduled by the transaction dispatching means 100.

According to the exclusive weight reduction control method of the third embodiment, when the number of rollbacks 742 of the transaction program TX1 reaches the upper limit 741 of the number of rollbacks when the transaction program TX2 commits, the transaction program TX2 is rolled. In this way, it is possible to prevent the processing of the transaction program TX1 from stagnation.

FIG. 7 is a schematic operation diagram for implementing the exclusive weight reduction control method according to the fourth embodiment of the present invention.
In the exclusive weight reduction control method of the fourth embodiment, the following operation is different from the schematic operation for realizing the exclusive weight reduction control method of the third embodiment.

When the transaction program TX2 updates the resource R1, the resource updating means 200 transmits the UC queued to the RCB (R1) 800 that manages the resource R1 to be updated after the head UCB address 811 in the resource.
The rollback count upper limit 741 of the TCB (TX1) 700 pointed to by the TCB address 911 of the B (TX1-R1) 900 is compared with the rollback count 742. If the rollback count 742 is equal to or greater than the rollback count upper limit 741, the transaction program is executed. TX2 performs rollback processing, and executes transaction program TX1.
Continues the processing, and the transaction dispatcher 100 reschedules the transaction program TX2.

According to the exclusive weight reduction control method of the fourth embodiment, in addition to the advantage of the exclusive weight reduction control method of the third embodiment, it is possible to terminate the transaction even if the transaction program TX2 continues processing. Unnecessary processing can be reduced by making a determination at the time of updating the resource R1 before performing the processing.

FIG. 8 is a schematic operation diagram for implementing an exclusive weight reduction control method according to a fifth embodiment of the present invention.
In the exclusive weight reduction control method according to the fifth embodiment, the following operation is different from the general operation for realizing the exclusive weight reduction control method according to the fourth embodiment.

When the transaction program TX2 updates the resource R1, the resource updating means 200 sets the UC queued after the first UCB address 811 in the resource of the RCB (R1) 800 managing the resource R1 to be updated.
The rollback count upper limit 741 of the TCB (TX1) 700 pointed to by the TCB address 911 of the B (TX1-R1) 900 is compared with the rollback count 742. If the rollback count 742 is equal to or larger than the rollback count upper limit 741, the UCB ( TX1-R1) TCB to transaction TCB address 751 of TCB (TX1) 700 pointed to by TCB address 911 of 900
(TX2) The address of 700 is set, the transaction program TX2 performs rollback processing, the transaction program TX1 continues processing, and the transaction program TX2 is not rescheduled at this time.

Next, the transaction program TX1
Performs transaction end processing, the transaction end processing means 300 notifies the transaction dispatch means 100 of the address of the TCB (TX2) 700 to which the transaction end notification TCB address 751 of the TCB (TX1) 700 points to the transaction program TX2. To reschedule.

According to the exclusive weight reduction control method of the fifth embodiment, unnecessary processing in which the transaction program TX2 rolls back again due to the rollback frequency upper limit 741 of the transaction program TX1 can be reduced.

FIG. 9 is a schematic operation diagram for realizing the exclusive weight reduction control method according to the sixth embodiment of the present invention.
In the exclusive weight reduction control method of the sixth embodiment, the following operation is different from the general operation for realizing the exclusive weight reduction control method of the second embodiment.

When the RCB 800 is created, an upper limit specified by the user is set in the rollback frequency upper limit 831 of the RCB800, 0 is set in the rollback frequency 832, and when the transaction program TX1 is rolled back. The number of rollbacks 832 of the RCB 800 that manages the resource R1 that is the cause of the rollback is counted up, and the operating system prepares a timer task that is activated every unit time. The rollback count 832 is cleared to zero.

When the transaction program TX2 updates the resource R1, the resource updating means 200
The upper limit 831 of the number of rollbacks of the B (R1) 800 is compared with the number 832 of the number of rollbacks, and
UCB when 2 is equal to or greater than the upper limit of rollback times 831
Without creating (TX2-R1) 900, RCB (R1) 8
00 TCB address 9 of UCB (TX1-R1) 900 to which the head UCB address 811 in the resource 9 points
The transaction end notification TCB address 751 of the TCB (TX1) 700 to which
2) After setting the address of 700, the transaction dispatcher 100 causes the transaction program TX2 to wait exclusively.

The transaction program TX1 is transmitted by the transaction end processing means 300 to TCB (T
X1) Notifying the transaction dispatching means 100 of the address of the TCB (TX2) 700 to which the transaction end notification TCB address 751 of the transaction 700 points, releases the exclusive wait of the transaction program TX2 and restarts the processing.

According to the exclusive weight reduction control method of the sixth embodiment, the number of rollbacks 832 per unit time is 8
When the number has reached 1, the transaction program TX2 for updating the resource R1 is exclusively weighted later, so that the stagnation of the processing of the transaction program TX1 can be prevented.

[0050]

As described above, the present invention is applicable to the case where the second transaction program updates the same resource while the first transaction program has not executed the transaction end processing after updating the resource. Since the second transaction program updates the resource without performing the exclusive wait, the exclusive wait when a plurality of transaction programs update to the same resource can be reduced, and the processing efficiency of the transaction program is improved. There is an effect that can be made.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an operating system for realizing an exclusive weight reduction control method according to the present invention.

FIG. 2 is a configuration diagram of an implementation unit of an exclusive weight reduction control method of the present invention.

FIG. 3 is a diagram showing a configuration of management information used in an exclusive weight reduction control method of the present invention, wherein (a) is a transaction management queue, (b) is a transaction control block, (c) is a resource management block, d) shows the contents of the update state management block, respectively.

FIG. 4A is a schematic operation diagram when the exclusive weight reduction control method according to the first embodiment is realized, and FIG. 4B is a schematic internal process when the exclusive weight reduction control method according to the first embodiment is realized. FIG.

FIG. 5 is a schematic operation diagram when implementing an exclusive weight reduction control method according to a second embodiment of the present invention.

FIG. 6 is a schematic operation diagram when implementing an exclusive weight reduction control method according to a third embodiment of the present invention.

FIG. 7 is a schematic operation diagram when implementing an exclusive weight reduction control method according to a fourth embodiment of the present invention.

FIG. 8 is a schematic operation diagram when implementing an exclusive weight reduction control method according to a fifth embodiment of the present invention.

FIG. 9 is a schematic operation diagram when implementing an exclusive weight reduction control method according to a sixth embodiment of the present invention.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 transaction dispatch means 200 resource update means 210 resource update function 220 management information update function 300 transaction end processing means 310 commit possibility determination function 400 resource commit means 410 commit function 420 management information update function 500 resource rollback means 510 rollback function 520 management Information update function 600 Transaction management queue (TCQ) 611 TCB start address during execution 612 TCB end address during execution 621 Executable TCB start address 622 Executable TCB end address 631 TCB start address during wait 632 TCB last address during wait 700 Transaction control block (TCB) 711 Next TCB address 712 Previous TCB address 721 First UCB address in TX 722 The last UCB address in TX 731 Rollback acceptability 732 Rollback request availability 741 Rollback count upper limit 742 Rollback count 751 Transaction end notification TCB address 800 Resource management block (RCB) 811 First UCB address in resource 812 Last UCB in resource Address 821 Management resource length 831 Rollback count upper limit 832 Rollback count 900 Update state management block (UCB) 911 TCB address 921 RCB address 931 TX next UCB address 932 TX previous UCB address 941 Resource next UCB address 942 Resource previous UCB address 951 Work area address 1000 Work area

 ──────────────────────────────────────────────────続 き Continuation of the front page (56) References Bill Claybrook, Fuji Software, “OLTP Online Transaction Processing System” (Heisei 6), Fuji Software, P. 113-136. JEFFREY D. ULLL, Translated by Toshiyasu Kunii and Nobuo Ohbo, "Principles of Database Systems," (Showa 60), The Computer Association of Japan, 486 −492. Sadayuki Hikita, “Introduction to Distributed Database System”, (Hei 1), Ohmsha, P.K. 113-114.

Claims (6)

(57) [Claims] 1. After the first transaction program updates resources, in a state where transaction end processing by commit or rollback has not yet been performed,
In a case where the second transaction program updates the same resource, the second transaction program updates the resource without performing an exclusive wait when the resource is updated, and the second transaction program updates the first transaction. When the transaction end processing is performed prior to the program, the transaction end processing of the second transaction program is waited for until the transaction end processing of the first transaction program is completed. When you commit the second
When the first transaction program rolls back and the first transaction program rolls back, the second transaction program commits, and the first transaction program performs a transaction end process prior to the second transaction program. In the case of execution, when the first transaction program commits, the second transaction program immediately rolls back, and when the first transaction program rolls back, the second transaction program continues processing. The exclusive weight reduction control method is characterized by realizing multiple runs of a transaction program that updates the same resource by performing the same. 2. In a case where the second transaction program performs a transaction end process prior to the first transaction program,
The user defines whether rollback can be accepted and whether or not there is a rollback request for each transaction program, so that the second transaction program with a rollback request can execute the rollback transaction with the first transaction program. Perform the transaction end processing without waiting until
When the second transaction program commits, the first transaction program immediately rolls back, and when the second transaction program rolls back, the first transaction program continues processing. 2. The exclusive weight reduction control method according to claim 1, wherein multiple running of a transaction program to be updated is realized. 3. The user defines an upper limit of the number of rollbacks for each transaction program when the first transaction program rolls back by committing the second transaction program, and activates the first transaction program. The number of rollbacks is counted later, and when the number of rollbacks of the first transaction program reaches an upper limit defined for each transaction program when the second transaction program commits, the second transaction program 3. The exclusive weight reduction control method according to claim 2, wherein the first transaction program is rolled back to prevent stagnation of the processing of the first transaction program. 4. When the number of rollbacks of the first transaction program reaches an upper limit prescribed for each transaction program when the second transaction program updates the resource, the second transaction is executed. In addition to preventing the stagnation of the processing of the first transaction program by rolling back the program, the rollback is performed even if the second transaction program continues processing. 4. The exclusive weight reduction control method according to claim 3, wherein unnecessary processing is reduced by making a determination when updating resources. 5. The rescheduling of the second transaction program, which has been rolled back because the number of rollbacks of the first transaction program has reached the upper limit, is not performed immediately after the rollback. By suspending the rescheduling of the second transaction program until the end processing is performed, there is no need for the second transaction program to roll back again due to the upper limit of the number of rollbacks of the first transaction program. The exclusive weight reduction control method according to claim 3 or 4, wherein a complicated process is reduced. 6. The user defines an upper limit of the number of rollbacks per unit time, counts the number of rollbacks caused by simultaneous update of the resource per unit time for each exclusive unit, 2. The method according to claim 1, wherein when the number of rollbacks per unit time has reached an upper limit, the second transaction program for updating resources is weighted exclusively to prevent stagnation of processing of the first transaction program. Or the exclusive weight reduction control method described in 2.