JP3615150B2 - Data processing server and method, and recording medium on which data processing program is recorded - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a data processing method for processing data, and further relates to a data processing server using such a data processing method and a recording medium on which a data processing program is recorded.
[0002]
[Prior art]
Conventionally, database systems that store various data as records and perform various operations on the records have been used.
In some cases, a plurality of users may update a certain record stored in such a database system. For example, it is a case where a first user performs a read operation, a second user performs a read operation, a first user performs an update operation, and a second user performs an update operation on a certain record. . In this case, the result of the update operation of the first user is overwritten with the result of the update operation of the second user and is lost.
[0003]
In order to prevent such multiple updating of multiple users for the same record, exclusive control such as a lock method including record lock, page lock, table lock, database lock, and the like has been performed in a conventional database system.
However, the conventional lock method requires a lot of calculation time (processing time). In addition, when a certain record is record-locked, when a predetermined condition (for example, the number of update pages exceeds a predetermined number) is satisfied, the record lock is shifted to a table lock or the like (lock escalation). In some cases, a deadlock was caused between operations. Furthermore, there are cases where another user cannot perform a read operation as well as an update operation on a record locked by an operation of a certain user.
[0004]
On the other hand, the database system as described above is used for accounting operations of companies and the like. When the database system is used for accounting operations in this way, the period from the transition from the k-th accounting period to the (k + 1) -th accounting period of a company or the like (generally, the number from the transition of the accounting period) Day to about a dozen days), input of a large number of slip data (including both slip data for the k-th fiscal period and slip data for the (k + 1) -th fiscal period), settlement processing, etc. are concentrated and smooth. In some cases, it was not possible to carry out proper accounting operations.
[0005]
For this reason, in accounting work using a conventional database system, entry of slip data within a predetermined period from the time of the transition of the accounting period is completely prohibited, and entry of slip data after the settlement of accounts for the k-th accounting period ends. Record the slip data entered within a predetermined period from the time of the transition to the accounting period, and record it in the temporary recording area after the settlement of accounts for the k-th accounting period is completed. The voucher data was transferred to the recording area for accounting work.
[0006]
[Problems to be solved by the invention]
Therefore, in view of the above points, the present invention provides a data processing server and a data processing method capable of preventing duplicate update while allowing multiple users to perform duplicate reading for the same record, and a recording medium on which a data processing program is recorded. The purpose is to provide. Another object of the present invention is to provide a data processing server and a data processing method capable of performing data input and data processing in parallel, and a recording medium recording a data processing program.
[0007]
[Means for Solving the Problems]
In order to solve the above problems, a data processing server according to a first aspect of the present invention is a server that processes data by communicating with a plurality of devices, and a recording unit that records a plurality of records; A cumulative day counting means for counting the cumulative number of days from a predetermined date to the present and outputting the value; Nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. The number output by the cumulative number of days counting means is the upper digit, the value of the number of times the system was started or rebooted on that day is the middle digit, and the number of times the number was requested to be generated on that day is the lower digit. When the data is received from any one of a plurality of devices and the number generator that generates Make a generation request A record creation means for writing a record including the received data and a number output from the number generation means to the recording means, and a request for reading the record recorded in the recording means from any one of the plurality of devices. When receiving a record reading unit that reads the requested record from the recording unit and outputs it to the device, and a record that has been edited from one of a plurality of devices, the received record Check whether the number in the record to be updated matches the number in the record to be updated and the number in the record to be updated recorded in the record means If the number matches, the number generation means Make a generation request And a record updating means for writing the record in which the number in the received record is replaced with the number output from the number generating means to the recording means.
[0008]
A data processing server according to the second aspect of the present invention is a server that processes data by communicating with a plurality of devices, and a recording unit that records a plurality of records; A cumulative day counting means for counting the cumulative number of days from a predetermined date to the present and outputting the value; Nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. The number output by the cumulative number of days counting means is the upper digit, the value of the number of times the system was started or rebooted on that day is the middle digit, and the number of times the number was requested to be generated on that day is the lower digit. Number generating means for generating and outputting the number, and when receiving data from any of the plurality of devices, the number generating means Make a generation request A record generating means for writing a record including the received data and a number output from the number generating means to the recording means, and among the records recorded in the recording means Directed by one of multiple devices For records with a number less than the number in the record containing the data Aggregate And record processing means for performing processing.
[0009]
A data processing method according to the first aspect of the present invention is a method of processing data by communicating with a plurality of devices, A step (a) of counting a cumulative number of days from a predetermined calculation date to the present and outputting the value; In the number generating means, the nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. A number in which the value output in step (a) is the upper digit, the value of the number of activations or reboots on that day is the middle digit, and the number of times the number is requested to be generated on that day is the lower digit. Step to generate ( b ), And when data is received from one of multiple devices, Make a generation request Recording a record including the received data and the number output from the number generating means on a recording medium ( c ) And a step of reading the requested record from the recording medium and outputting it to the device when receiving a request to read the record from any one of the plurality of devices ( d ) And a record whose data has been edited from one of multiple devices, the number in the received record matches the number in the record to be updated recorded on the recording medium If the number in the received record matches the number in the record to be updated recorded on the recording medium, the number generation means Make a generation request The step of writing the record in which the number in the received record is replaced with the number output from the number generation means to the recording medium ( e ).
[0010]
A data processing method according to the second aspect of the present invention is a method of processing data by communicating with a plurality of devices, A step (a) of counting a cumulative number of days from a predetermined calculation date to the present and outputting the value; In the number generating means, the nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. A number in which the value output in step (a) is the upper digit, the value of the number of activations or reboots on that day is the middle digit, and the number of times the number is requested to be generated on that day is the lower digit. Step to generate ( b ), And when data is received from one of multiple devices, Make a generation request A step of writing a record including the received data and the number output from the number generating means on the recording medium ( c ) And in the record recorded on the recording medium Directed by one of multiple devices For records with a number less than the number in the record containing the data Aggregate Step to process ( d ).
[0011]
A recording medium recording the data processing program according to the first aspect of the present invention is a recording medium that can be read by a CPU to process data by communicating with a plurality of devices. A procedure (a) of counting the cumulative number of days from a predetermined date of calculation to the present and outputting the value; In the number generating means, the nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. A number in which the value output in step (a) is the upper digit, the value of the number of activations or reboots on the day is the middle digit, and the number of times the number is requested to be generated on that day is the lower digit. Steps to generate ( b ), And when data is received from one of multiple devices, Make a generation request , A procedure for recording a record including the received data and the number output from the number generating means on a recording medium ( c ) And a procedure for reading the requested record from the recording medium and outputting it to the device when receiving a request to read the record from any one of the plurality of devices ( d ) And a record whose data has been edited from one of multiple devices, the number in the received record matches the number in the record to be updated recorded on the recording medium If the number in the received record matches the number in the record to be updated recorded on the recording medium, the number generation means Make a generation request , The procedure of writing the record in which the number in the received record is replaced with the number output from the number generating means to the recording medium ( e ) Is executed by the CPU.
[0012]
A recording medium recording a data processing program according to the second aspect of the present invention is a recording medium readable by a CPU for processing data by communicating with a plurality of devices, A procedure (a) of counting the cumulative number of days from a predetermined date of calculation to the present and outputting the value; In the number generating means, the nth Number generation Number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)) upon request. A number in which the value output in step (a) is the upper digit, the value of the number of activations or reboots on the day is the middle digit, and the number of times the number is requested to be generated on that day is the lower digit. Steps to generate ( b ), And when data is received from one of multiple devices, Make a generation request A procedure for writing a record including the received data and the number output from the number generating means to the recording medium ( c ) And in the record recorded on the recording medium Directed by one of multiple devices For records with a number less than the number in the record containing the data Aggregate Procedure for processing ( d ) Is executed by the CPU.
[0013]
According to the first aspect of the present invention, since the record is updated only when the number in the record in which the data is edited matches the number in the update target record, multiple users can be duplicated for the same record. In addition, duplicate updates can be prevented. According to the second aspect of the present invention, Directed by one of multiple devices Only for records that contain a number less than the number in the record that contains the data Aggregate Since processing is performed, data input and data processing can be performed in parallel.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. The same constituent elements are denoted by the same reference numerals, and the description thereof is omitted.
First, a data processing method according to the first embodiment of the present invention will be described. FIG. 1 is a diagram showing a system for carrying out a data processing method according to the first embodiment of the present invention.
As shown in FIG. 1, the system 1 includes client terminals 11 to 1 n and a server 21.
The client terminals 11 to 1n and the server 21 are connected to each other by a network 31 such as a LAN, a public line network, or the Internet.
The client terminals 11 to 1n are PCs or the like for the user to use the server 21.
[0015]
FIG. 2 is a diagram illustrating the server 21. As shown in FIG. 2, the server 21 includes a system date management unit 22, a system event number generation unit 23, a record creation unit 24, a record reading unit 25, a record update unit 26, and a recording medium 27. It is out.
The system date management unit 22 manages the system date of the server 21 and counts the number of days until the system date when the predetermined date of calculation is “00001” (hereinafter also referred to as “cumulative days”). Is output. For example, if January 1, 1999 is the starting date and the system date is January 1, 2001, the cumulative number of days is 731 and the system date management unit 22 outputs “00731”.
[0016]
In response to requests from the record creation unit 24 and the record update unit 26, the system event number generation unit 23 generates an SEN (system event number, hereinafter simply referred to as “number”) that is an 18-digit number. Output. Further, the system event number generation unit 23 writes the generated number in the recording medium 27 at a predetermined time.
Here, the number will be described in detail. FIG. 3 is a diagram showing a number format. As shown in FIG. 3, the number is the upper 5 digits (D ₁ D ₂ D ₃ D ₄ D ₅ ), Middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) And lower 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ).
[0017]
Top 5 digits of number (D ₁ D ₂ D ₃ D ₄ D ₅ ) Is a numerical value indicating the cumulative number of days on which this number was generated. Accordingly, the system event number generation unit 23 can generate a number from the date of calculation to the 99,999th day, that is, about 270 years after the date of calculation.
[0018]
Lower 9 digits of number (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is a number incremented for each number generation request. The lower 9 digits of the number (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) If a carry occurs, the carry is the middle 4 digits of the number (S ₁ S ₂ S ₃ S ₄ ).
[0019]
Middle 4 digits of number (S ₁ S ₂ S ₃ S ₄ ) In principle, the number of times the server 21 was rebooted within the same day (including when the server 21 was stopped due to a power failure, failure, etc., and then restarted) and the lower 9 digits of the number (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) And carry from However, as will be described later in the description of the number generation process, the middle 4 digits of the number (S ₁ S ₂ S ₃ S ₄ ) Is incremented when the server 21 is started or rebooted in a state where the system date managed by the system date management unit 22 is erroneously set to a date older than the correct date. Accordingly, the system event number generation unit 23 counts the number of times the server 21 has been rebooted within the same day, the number of times the server 21 has been started or rebooted with the system date being erroneously set to an old date, and the lower 9 digits ( C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ Numbers can be generated until the total with the carry from) is 9,999.
[0020]
The system event number generation unit 23 determines that the middle 4 digits (S) when the server 21 has not been rebooted within the same day. ₁ S ₂ S ₃ S ₄ ) And lower 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ), The number can be generated up to 9,999,999,999,999 times within the same day.
On the other hand, when the time required to generate a number was measured using a CPU and software having an operating frequency of 600 MHz, it took 0.7 seconds for 10,000 number generation processing. That is, a time of 0.00007 seconds is required for each number generation.
[0021]
Therefore, in 9,999,999,999,999 number generation processing, approximately 0.0700 million seconds (approximately 8100) obtained by multiplying 0.00007 (seconds / time) by 9,999,999,999,999 (times). Day) is required. Further, considering that various database operation processes are performed together with the generation of the number, the number has a sufficient number of digits for practical use. Further, as described above, when the server 21 is rebooted within the same day or rebooted in a state where the system date is erroneously set to an old date, the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is incremented, the number of times that a number can be generated within the same day decreases by 1,000,000,000 times. However, even if such a situation is taken into consideration, the number is considered to have a sufficient number of digits for practical use.
[0022]
The record creation unit 24 receives data from the client terminals 11 to 1n, and writes a record including the received data and number as a new record in the database in the recording medium 27.
The record reading unit 25 reads and outputs records from the database in the recording medium 27 in response to requests from the client terminals 11 to 1n.
The record update unit 26 receives records from the client terminals 11 to 1n. When the number in the received record matches the number in the record to be updated in the recording medium 27, the record update unit 26 stores the record in the recording medium 27. Update (overwrite) the update target record stored in the database.
[0023]
The recording medium 27 records a database, a number generated by the system event number generation unit 23, and the like. The recording medium 27 corresponds to a hard disk, floppy disk, MO, MT, RAM, CD-ROM, DVD-ROM, or the like.
The system date management unit 22, the system event number generation unit 23, the record creation unit 24, the record reading unit 25, and the record update unit 26 illustrated in FIG. 2 can be configured by a CPU and software (program). Each of the program, various databases, and application data files can be recorded on a recording medium such as a hard disk, floppy disk, MO, MT, RAM, CD-ROM, or DVD-ROM.
[0024]
Next, the operation of the server 21 will be described.
First, the operation of the system event number generation unit 23 will be described prior to the description of record operations by the record creation unit 24, the record reading unit 25, and the record update unit 26.
FIG. 4 is a flowchart showing an outline of the activation process operation of the system event number generation unit 23. Hereinafter, the activation processing operation of the system event number generation unit 23 will be described with reference to FIG.
[0025]
When the server 21 is activated or rebooted, the system event number generation unit 23 starts the process of FIG.
When the processing of FIG. 4 is started, the system event number generation unit 23 reads the number recorded on the recording medium 27 (step S101).
[0026]
Next, the system event number generation unit 23 receives the upper five digits (D) of the number read in step S101 (hereinafter also referred to as “final recording number”). ₁ D ₂ D ₃ D ₄ D ₅ ) Is equal to or greater than the current cumulative number of days managed by the system date management unit 22, that is, rebooted within the same day as the date when the last recorded number was recorded, or managed by the system date management unit 22. Check if the system date is incorrectly set to an old date. The system event number generation unit 23 then adds the upper five digits (D ₁ D ₂ D ₃ D ₄ D ₅ ) Is smaller than the current cumulative number of days, the process proceeds to step S103, and the upper five digits (D ₁ D ₂ D ₃ D ₄ D ₅ ) Is greater than or equal to the current cumulative number of days, the process proceeds to step S104 (step S102).
[0027]
In step S102, the upper 5 digits (D ₁ D ₂ D ₃ D ₄ D ₅ ) Is smaller than the current cumulative number of days, that is, when it is determined that the last recorded number was not rebooted within the same day as the recorded date and the system date is not set incorrectly, a system event number is generated. The unit 23 uses the upper five digits (D) of the number to be newly generated as an initial value at the time of activation (hereinafter also referred to as “activation number”). ₁ D ₂ D ₃ D ₄ D ₅ ) To the current cumulative number of days and the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Are set to “0000”, respectively (step S103).
[0028]
On the other hand, in step S102, the upper 5 digits (D ₁ D ₂ D ₃ D ₄ D ₅ ) Is greater than or equal to the current cumulative number of days, that is, if it is determined that the last recorded number was rebooted within the same day as the date of recording or that the system date was set to an older date, the system event number The generation unit 23 uses the upper 5 digits (D ₁ D ₂ D ₃ D ₄ D ₅ ) In the upper 5 digits of the last recorded number (D ₁ D ₂ D ₃ D ₄ D ₅ ) And the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is the middle 4 digits of the last recorded number (S ₁ S ₂ S ₃ S ₄ ) Are respectively set to incremented values (step S104).
[0029]
Next, the system event number generation unit 23 generates the lower 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is set to “000000000000” (step S105). Then, the system event number generation unit 23 writes the activation time number in the recording medium 27 (step S106). As described above, the system event number generation unit 23 writes the startup number into the recording medium 27, so that the startup number becomes a new final recording number. Note that the system event number generation unit 23 may record the number in an EEPROM or the like instead of the recording medium 27.
[0030]
In this way, even if the last recorded number is rebooted within the same day as the date of recording or the system date is mistakenly set to an old date, the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) In the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is set to an incremented value, it is possible to generate a startup number that is larger than the final recording number.
[0031]
Next, the operation of the system event number generation unit 22 when a number generation request is received from the record creation unit 24 or the record update unit 26 will be described. FIG. 5 is a flowchart showing an outline of the number generation processing operation of the system event number generation unit 23. Hereinafter, the number generation processing operation of the system event number generation unit 23 will be described with reference to FIG.
[0032]
Upon receiving a number generation request from the record creation unit 24 or the record update unit 26, the system event number generation unit 23 starts the process of FIG.
First, the system event number generation unit 23 is subordinate to the number generated last time (when the number generation request is received for the first time after the server 21 is started, the startup number corresponds to the number. 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is “99999999999”, that is, the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is incremented to check if a carry occurs, and the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is “99999999999”, the process proceeds to step S112; otherwise, the process proceeds to step S115 (step S111).
[0033]
In step S111, the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is "99999999999", that is, the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is incremented, the system event number generation unit 23 further determines the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is “9999”, that is, the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) If you add the carry from the middle number four digits (S ₁ S ₂ S ₃ S ₄ ) Checks whether overflow occurs. The system event number generation unit 23 then adds the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is not “9999”, the process proceeds to step S113, and the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is “9999”, the process proceeds to step S116 (step S112).
[0034]
In step S112, the middle 4 digits of the previous number (S ₁ S ₂ S ₃ S ₄ ) Is not “9999”, the system event number generation unit 23 generates the middle 4 digits (S) of the number to be newly generated (hereinafter also referred to as “new generation number”). ₁ S ₂ S ₃ S ₄ ) Is the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Increment (the lower 9 digits of the previous number (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) To the value added to the carry), and the lower 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is set to “000000000000” (step S113). Further, the system event number generation unit 23 writes the new generation number at this point in the recording medium 27 (step S114). When the system event number generation unit 23 writes the new generation number at this point in the recording medium 27, the new generation number at this point becomes the new final recording number.
[0035]
In step S111, the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is not “99999999999”, or when the process of step S114 is completed, the system event number generation unit 23 generates the lower 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is incremented, and the newly generated number is output to the record creating unit 24 or the record updating unit 26 that requested the number generation (step S115).
[0036]
On the other hand, the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is “9999”, the system event number generation unit 23 stops generating a new number and ends the process (step S116). In this case, the server 21 may display a warning text to the operator.
When the process of step S116 is executed, the system event number generation unit 23 determines that the last 9 digits (C ₁ C ₂ C ₃ C ₄ C ₅ C ₆ C ₇ C ₈ C ₉ ) Is “99999999999”, and the middle 4 digits (S ₁ S ₂ S ₃ S ₄ ) Is “9999”. However, as described above, it is considered that there are practically few number generation requests exceeding 9,999,999,999,999 times within the same day.
[0037]
As described above, the system event number generation unit 23 takes into account the reboot of the server 21 within the same day and the start-up in a state where the system date is erroneously set to an old date (including reboot). It is possible to generate a new number that always satisfies the condition that the number is larger than the number. In addition, the system event number generation unit 23 does not generate a number, but the middle four digits (S ₁ S ₂ S ₃ S ₄ ) Is incremented only when the new generation number is written to the recording medium 27, the overhead for writing the new generation number to the recording medium 27 can be reduced.
[0038]
Next, the operation of the record creation unit 24 of the server 21 will be described. FIG. 6 is a flowchart showing an outline of the record creation operation of the record creation unit 24. Hereinafter, the record creation operation of the record creation unit 24 will be described with reference to FIG.
[0039]
First, the client terminals 11 to 1n transmit data for a new record to the server 21, and the record creation unit 24 of the server 21 receives the data (step S201).
Next, the record creation unit 24 requests the system event number generation unit 23 to generate a number (step S202). Upon receiving a number generation request from the record creation unit 24, the system event number generation unit 23 generates a number and transmits it to the record creation unit 24.
When the record creation unit 24 receives the number from the system event number generation unit 23, the record creation unit 24 creates a record including the data received from the client terminals 11 to 1n and the number received from the system event number generation unit 23, Store in the database (step S204).
In this way, a record including a number can be created and stored in a database.
[0040]
Next, the operation of the record reading unit 25 of the server 21 will be described. FIG. 7 is a flowchart showing an outline of the record reading operation of the record reading unit 25. Hereinafter, the record reading operation of the record reading unit 25 will be described with reference to FIG.
[0041]
First, the client terminals 11 to 1n request the server 21 to read out a desired record, and the record reading unit 25 of the server 21 receives the record reading request (step S301).
Next, the record reading unit 25 searches and reads the records requested from the client terminals 11 to 1n from the database in the recording medium 27 (step S302).
The record reading unit 25 transmits the read record to the client terminals 11 to 1n (Step S303). The client terminals 11 to 1n can be prevented from displaying the numbers in the received records, and the user can be prevented from editing the numbers in the records.
[0042]
Next, the operation of the record update unit 26 of the server 21 will be described. FIG. 8 is a flowchart showing an outline of the record update operation of the record update unit 26. Hereinafter, the record update operation of the record update unit 26 will be described with reference to FIG.
[0043]
First, the client terminals 11 to 1n transmit the record with the edited data to the server 21, and the record update unit 26 of the server 21 receives the record with the edited data (step S401).
Next, the record update unit 26 compares the number in the record received from the client terminals 11 to 1n with the number in the update target record stored in the database in the recording medium 27. If the number in the record received from the client terminals 11 to 1n matches the number in the update target record stored in the database in the recording medium 27, the record update unit 26 proceeds to step S403. If they do not match, the process proceeds to step S406 (step S402).
[0044]
If it is determined in step S402 that the number in the record received from the client terminals 11 to 1n matches the number in the update target record stored in the database, the record update unit 26 generates a system event number generation unit. 23 is requested to generate a number (step S403). When receiving a number generation request from the record update unit 26, the system event number generation unit 23 generates a number and transmits it to the record update unit 26.
[0045]
Next, the record update unit 26 replaces the number in the record received from the client terminals 11 to 1n with the number received from the system event number generation unit 23. Then, the record update unit 26 updates the update target record in the database by storing the record in which the number is replaced at the location where the update target record of the database in the recording medium 27 is stored (step S405).
[0046]
On the other hand, if it is determined in step S402 that the number in the record received from the client terminals 11 to 1n does not match the number in the update target record stored in the database, the record update unit 26 records the recording medium. The update target record stored in the database 27 is not updated, and a warning message to that effect is transmitted to the client terminals 11 to 1n (step S406).
As described above, the record update unit 26 sets the number in the update target record only when the number in the record received from the client terminals 11 to 1n matches the number in the update target record stored in the database. It can be updated with a new generation number.
[0047]
Next, an example using the data processing method according to the present embodiment will be described. In this embodiment, the data processing method according to this embodiment is applied to employee database processing. In this embodiment, all database operations are performed on the day of calculation.
In this embodiment, a schema of an employee database that manages allowances for employees is built on the recording medium 27 of the server 21. This employee database has three columns: employee name, allowance, and number.
[0048]
First, the operations of the client terminal 11 and the server 21 when the first user creates a record in the employee database will be described with reference to the flowchart of FIG. It is assumed that the first user uses the client terminal 11.
The first user inputs data including employee names and allowances (for 4 employees) to the client terminal 11, and the client terminal 11 transmits data including employee names and allowances (for 4 employees) to the server 21. (Step S501).
[0049]
When the server 21 receives the data including the employee name and allowance (for four employees) from the client terminal 11, the server 21 generates four numbers, creates records 41 to 44 with numbers added to the respective data, and stores the employee database. (Step S601). FIG. 10A is a diagram showing the employee database 40 in which four records are stored in this way. As shown in FIG. 10A, the record 41 includes a number having a value of “000010000000000001”. This value indicates that this number is generated on the starting date, the server 21 has never been rebooted on the starting date, and this number is the first number generated on the starting date.
[0050]
Next, operations of the client terminals 12 and 13 and the server 21 when the second and third users try to update the record 41 in the employee database in duplicate will be described with reference to the flowchart of FIG. . Note that the second user uses the client terminal 12 and the third user uses the client terminal 13.
First, the second user requests to read the record 41, and the client terminal 12 transmits a request to read the record 41 to the server 21 (step S711).
[0051]
When the server 21 receives the request for reading the record 41 from the client terminal 12, the server 21 reads the record 41 from the employee database 40 and transmits it to the client terminal 12 (step S611). The client terminal 12 receives the record 41 from the server 21 and displays it.
Next, the second user edits desired data in the displayed record 41 (step S712). Here, it is assumed that the second user edits the amount of the allowance in the record 41 from 50,000 yen to 55,000 yen. FIG. 10B is a diagram showing a record 45 that is a result of editing the record 41 by the second user.
[0052]
On the other hand, at this time, the third user requests to read the record 41, and the client terminal 13 transmits a request to read the record 41 to the server 21 (step S811).
When the server 21 receives the request for reading the record 41 from the client terminal 13, the server 21 reads the record 41 from the employee database 40 and transmits it to the client terminal 13 (step S612). The client terminal 13 receives the record 41 from the server 21 and displays it.
Next, the third user edits desired data in the displayed record 41 (step S812). Here, it is assumed that the third user edits the amount of the allowance in the record 41 from 50,000 yen to 57,000 yen. FIG. 10C is a diagram showing a record 46 that is a result of editing the record 41 by the second user.
[0053]
On the other hand, the second user requests transmission of the edited record 45, and the client terminal 12 transmits the record 45 to the server 21 (step S713).
When receiving the record 45 from the client terminal 12, the server 21 confirms that the number of the record 45 matches the number of the record 41 stored in the employee database 40, and then generates a new number. In the present embodiment, the new number is “000010000000000005”. Then, the server 21 replaces the number of the record 45 with a new number, and stores the record 45 in the employee database 40 (step S613). FIG. 10D is a diagram illustrating the employee database 40 after the record 45 is stored.
[0054]
On the other hand, the third user requests transmission of the edited record 46, and the client terminal 13 transmits the record 46 to the server 21 (step S813).
When the server 21 receives the record 46 from the client terminal 13, the server 21 compares the number of the record 46 with the number of the record 45 stored in the employee database 40. However, in this embodiment, the record 45 has already been updated by the second user, and the number of the record 45 and the number of the record 46 do not match. Therefore, the server 21 does not store the record 46 in the employee database, and transmits a warning message to that effect to the client terminal 13 (step S614).
The client terminal 13 displays the warning message received from the server 21 (step S814).
[0055]
In this way, the numbers in the records received from the client terminals 12 and 13 are compared with the numbers in the records stored in the employee database 40, and the records are updated only when they match. In addition, it is possible to prevent the third user from overlapping updating.
[0056]
Next, a data processing method according to the second embodiment of the present invention will be described.
FIG. 12 is a diagram showing a system for carrying out the data processing method according to the present embodiment.
As shown in FIG. 12, the system 2 includes client terminals 11 to 1 n and a server 51.
The client terminals 11 to 1n and the server 51 are connected to each other by a network 31.
[0057]
FIG. 13 is a diagram illustrating the server 51. As shown in FIG. 13, the server 51 includes a system date managing unit 22, a system event number generating unit 23, a record creating unit 24, a record reading unit 25, a record updating unit 26, a recording medium 27, a record And a processing unit 52.
The record processing unit 52 performs predetermined processing on the records stored in the database in the recording medium 27.
[0058]
Next, the operation of the record processing unit 52 will be described. FIG. 14 is a flowchart showing an outline of the record processing operation of the record processing unit 52. Hereinafter, the record reading operation of the record processing unit 52 will be described with reference to FIG.
[0059]
First, the record processing unit 52 searches a record in the recording medium 27 for a record including predetermined data (step S901).
Next, the record processing unit 52 extracts a record including a number smaller than the number in the record searched in step S901 from the database (step S902).
Then, the record processing unit 52 performs a predetermined process on the record extracted in step S902 (step S903).
As described above, the record processing unit 52 can perform the predetermined process only on the record including the number smaller than the number in the record including the predetermined data.
[0060]
Next, an example using the data processing method according to the present embodiment will be described. In this embodiment, the data processing method according to the present embodiment is applied to settlement processing. In this embodiment, it is assumed that the calculation date is April 1, 1999 and the settlement date is March 31, 2000.
In the present embodiment, a slip database is constructed on the recording medium 27 of the server 51. This slip database has four columns of input date, date of recording, slip content, and number.
FIG. 15 is a diagram showing a slip database in the recording medium 27. In FIG. 15, eleven records 61 to 71 are stored in the slip database 60 by the record creation unit 24 or the record update unit 26.
[0061]
Next, the operation of the record processing unit 52 of the server 51 will be described with reference to the flowchart of FIG.
When the record processing unit 52 of the server 51 receives the settlement start instruction from the client terminals 11 to 1n, it starts the processing of FIG.
First, the record processing unit 52 searches the slip database for a record instructing slip closing (step S911). In the present embodiment, the record instructing slip closing is the record 70.
[0062]
Next, the record processing unit 52 extracts a record including a number smaller than the number (“003680000000000002”) of the record 70 searched in Step S901 (Step S912). In the present embodiment, records including numbers smaller than the number of the record 70 are records 61 to 69.
Next, the record processing unit 52 records among the records 61 to 69 extracted in step S902 that have a recording date before March 31, 2000 (in this embodiment, records 61 to 64, 66, and , 68) and perform settlement processing (step S913).
[0063]
As described above, by storing the record 70 instructing slip closing when the user is appropriate in the slip database, the records 61 to 64, 66, and 68 to be processed by the record processing unit 52 are specified. The record 71 stored in the slip database after the record 70 is stored can be excluded from the target of the settlement process. Therefore, input of a record including slip data (in this embodiment, record 71) is prohibited until the settlement process is completed, or the slip data is provisionally input to a temporary recording area in the recording medium 27 and the settlement process is completed. There is no need to store it again in the slip database 60.
In addition, after storing the record 70 instructing slip closing in the slip database 60, if it becomes necessary for the record 71 to be a settlement target for some reason, the record 70 is deleted and a new slip closing instruction is issued. A record may be created after the record 71.
[0064]
In each embodiment and each example described above, the number can be more reliably generated by installing a sub server in addition to the server 21 and multiplexing the servers.
[0065]
【The invention's effect】
As described above, according to the first aspect of the present invention, the record is updated only when the number in the record whose data is edited matches the number in the update target record. Duplicate updating can be prevented while enabling duplicate reading by the user. According to the second aspect of the present invention, Directed by one of multiple devices Only for records that contain a number less than the number in the record that contains the data Aggregate Since processing is performed, data input and data processing can be performed in parallel.
[Brief description of the drawings]
FIG. 1 is a diagram showing a system for carrying out a data processing method according to a first embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of the server in FIG. 1;
FIG. 3 is a diagram showing a format of a system event number.
FIG. 4 is a flowchart showing start processing of the data processing method according to the first embodiment of the present invention.
FIG. 5 is a flowchart showing system event number generation processing of the data processing method according to the first embodiment of the present invention.
FIG. 6 is a flowchart showing record creation processing of the data processing method according to the first embodiment of the present invention.
FIG. 7 is a flowchart showing record read processing of the data processing method according to the first embodiment of the present invention.
FIG. 8 is a flowchart showing record update processing of the data processing method according to the first embodiment of the present invention.
FIG. 9 is a flowchart showing a record creation process of the data processing method according to the example of the first embodiment of the present invention;
FIG. 10 is a diagram showing an employee database processed by the data processing method according to the example of the first embodiment of the present invention.
FIG. 11 is a flowchart showing record update processing of the data processing method according to the example of the first embodiment of the present invention;
FIG. 12 is a diagram showing a system for performing a data processing method according to a second embodiment of the present invention.
13 is a diagram illustrating a configuration of the server in FIG. 12. FIG.
FIG. 14 is a flowchart showing record processing of the data processing method according to the second embodiment of the present invention.
FIG. 15 is a diagram showing a slip database processed by a data processing method according to an example of the second embodiment of the present invention;
FIG. 16 is a flowchart showing a settlement process of a data processing method according to an example of the second embodiment of the present invention.
[Explanation of symbols]
1, 2 Data processing system
11 to 1n client terminal
21, 51 servers
22 System Date Management Department
23 System event number generator
24 Record creation part
25 Record reading part
26 Record update section
27 Recording media
31 network
40 employee database
41-46 records
52 Record processing section
60 slip database
61-71 records

Claims (16)

A server that processes data by communicating with multiple devices,
Recording means for recording a plurality of records;
A cumulative day counting means for counting the cumulative number of days from a predetermined date to the present and outputting the value;
In response to the nth number generation request, the number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)), and the cumulative number of days is counted. Number generating means for generating a number having a value output by the means as an upper digit, a value of the number of times of activation or rebooting on that day as a middle digit, and a value of the number of times requested to be generated on that day as a lower digit ; ,
When data is received from any one of the plurality of devices, a number generation request is made to the number generation means, and the record including the received data and the number output from the number generation means is recorded in the recording means Record creation means to write to,
Record reading means for reading the requested record from the recording means and outputting it to the apparatus when receiving a request to read the record recorded in the recording means from any one of the plurality of devices When,
When a record whose data has been edited is received from any one of the plurality of devices, the number in the received record matches the number in the record to be updated recorded in the recording means. If the number in the received record matches the number in the record to be updated recorded in the recording means, a number generation request is made to the number generating means, and the received record A record updating means for writing a record in which the number in the record is replaced with the number output from the number generating means to the recording means;
A data processing server comprising: A server that processes data by communicating with multiple devices,
Recording means for recording a plurality of records;
A cumulative day counting means for counting the cumulative number of days from a predetermined date to the present and outputting the value;
In response to the nth number generation request, the number x (n) satisfying x (i) <x (n) (i = 1,..., (N−1)), and the cumulative number of days is counted. A number that generates and outputs a number in which the value output by the means is the upper digit, the value of the number of times it is started or rebooted on the day is the middle digit, and the number of times the number is requested to be generated on that day is the lower digit Generating means;
When data is received from any one of the plurality of devices, a number generation request is made to the number generation means, and the record including the received data and the number output from the number generation means is recorded in the recording means Record creation means to write to,
Record processing means for performing aggregation processing on records having a number smaller than the number in the record including data designated by any one of the plurality of devices among the records recorded in the recording means When,
A data processing server comprising: Record reading means for reading the requested record from the recording means and outputting it to the apparatus when receiving a request to read the record recorded in the recording means from any one of the plurality of devices When,
When a record whose data has been edited is received from any one of the plurality of devices, the number in the received record matches the number in the record to be updated recorded in the recording means. If the number in the received record matches the number in the record to be updated recorded in the recording means, a number generation request is made to the number generating means, and the received record A record updating means for writing a record in which the number in the record is replaced with the number output from the number generating means to the recording means;
The data processing server according to claim 2, further comprising: The record recorded by the recording means is a record relating to a slip , and the record processing means includes data designated by any one of the plurality of devices among the records recorded in the recording means. 4. The data processing server according to claim 2 , wherein the record processing is performed by counting records having numbers smaller than the numbers in the records . Further comprising number recording means for recording the number generated by the number generating means at a predetermined time,
When the number generating means is activated or rebooted, it compares the upper digit value of the number recorded in the number recording means with the value of the cumulative number of days output from the cumulative number of days counting means. If the value of the upper digit of the recorded number is equal to or greater than the value of the cumulative number of days output by the cumulative number of days counting means, the upper digit of the number recorded in the number recording means is the upper digit, and the number recording A number obtained by incrementing the middle digit of the number recorded in the means is set as the middle digit, and a number is generated with the value of the number of times the number generation is requested from that day of the day, and the number is recorded in the number recording means. If the value of the upper digit of the number is smaller than the value of the cumulative number of days output by the cumulative number of days counting unit, the value output by the cumulative number of days counting unit Claim the upper digit, and the value of the number of times that has been started or rebooted on that day and middle digit, and generating a number of values of the number of the day that time is requested number generated from the lower digit 1 The data processing server of any one of -4 . 6. The data processing server according to claim 5 , wherein said number recording means records a number when there is a change in a middle digit of the number generated by said number generating means. The number generating means, when the carry from the lower digit of the number is generated, any one data processing server according to claim 1, wherein adding the carry to the middle digit number. A method of processing data by communicating with a plurality of devices,
A step (a) of counting a cumulative number of days from a predetermined calculation date to the present and outputting the value;
In number generating means, in response to the n-th number generation request, a x (i) <x (n ) (i = 1, ···, (n-1)) Number satisfy x (n) The value output in step (a) is the upper digit, the value of the number of times of activation or rebooting on the day is the middle digit, and the number of the number of times requested to be generated on that day is generated as the lower digit. Step ( b );
When data is received from any one of the plurality of devices, a number generation request is made to the number generation unit, and a record including the received data and the number output from the number generation unit is recorded on the recording medium. Recording step ( c );
When receiving a request to read a record from either of the devices of the plurality of devices, the step (d) to output the requested record to the device is read from the recording medium,
When a record whose data has been edited is received from any one of the plurality of devices, the number in the received record matches the number in the record to be updated recorded on the recording medium. If the number in the received record matches the number in the record to be updated recorded on the recording medium, a number generation request is made to the number generation means, and the received record A step ( e ) of writing a record in which the number in the list is replaced with the number output from the number generating means to the recording medium;
A data processing method comprising: A method of processing data by communicating with a plurality of devices,
A step (a) of counting a cumulative number of days from a predetermined calculation date to the present and outputting the value;
In number generating means, in response to the n-th number generation request, a x (i) <x (n ) (i = 1, ···, (n-1)) Number satisfy x (n) a value step (a) is output as the upper digit, the number of the value of the number of times that has been started or rebooted on that day and middle digit, the value of the number of times required to numbers generated its day low order Generating step ( b );
When data is received from any one of the plurality of devices, a number generation request is made to the number generation unit, and a record including the received data and the number output from the number generation unit is recorded on the recording medium. Writing step ( c );
A step of performing a tabulation process on a record having a number smaller than a number in a record including data instructed by any one of the plurality of devices recorded in the recording medium ( d) )When,
A data processing method comprising: A step of reading the requested record from the recording medium and outputting it to the apparatus when receiving a request to read the record recorded on the recording medium from any one of the plurality of apparatuses ( e) )When,
When a record whose data has been edited is received from any one of the plurality of devices, the number in the received record matches the number in the record to be updated recorded on the recording medium. If the number in the received record matches the number in the record to be updated recorded on the recording medium, a number generation request is made to the number generation means, and the received record Writing a record in which the number in the list is replaced with the number output from the number generating means to the recording medium ( f ),
The data processing method according to claim 9 , further comprising: The record recorded on the recording medium is a record relating to a slip , and the step ( d ) includes data designated by any one of the plurality of devices among the records recorded on the recording means. The data processing method according to claim 9 or 10 , characterized in that a record having a number smaller than a number in a record to be included is totaled and a settlement process is performed. A step (g) of recording the number generated in step ( b ) at a predetermined time;
When step ( b ) is started or rebooted, the upper digit value of the number recorded in step (g) is compared with the cumulative number of days output in step ( a ), and recorded in step (g). If the upper digit value of the number is greater than or equal to the cumulative number of days output in step ( a ), the upper digit of the number recorded in step (g) is taken as the upper digit and recorded in step (g). The number obtained by incrementing the middle digit of the number is used as the middle digit, and a number is generated with the value of the number of times the number is requested to be generated from that day of the day as the lower digit, and the number recorded in step (g) If the value of the upper digit is smaller than the value of the cumulative number of days which is output in step (a), the output value in step (a) and higher digits , Claim 8, characterized in that it comprises the step of generating a number of the day the value of count that was started or rebooted and middle digits, the value of the number of times that has been requested number generated from that time of the day and low-order digit The data processing method of any one of -11 . Step (g) The data processing server according to claim 12, wherein the comprising the step of recording the number when there is a change in the middle digit number generated by the step (b). The data according to any one of claims 8 to 13 , wherein step ( b ) includes a step of adding a carry to a middle digit of a number when a carry occurs from a lower digit of the number. Processing server. A CPU-readable recording medium for processing data by communicating with a plurality of devices,
A procedure (a) of counting the cumulative number of days from a predetermined date of calculation to the present and outputting the value;
In number generating means, in response to the n-th number generation request, a x (i) <x (n ) (i = 1, ···, (n-1)) Number satisfy x (n) , the value Step (a) is output as the upper digit, and the value of the number of times that has been started or rebooted on that day and middle digit, generating a number of values of the number of times required to number generator that day and lower digit Step ( b )
When data is received from any one of the plurality of devices, a number generation request is made to the number generation unit, and a record including the received data and the number output from the number generation unit is recorded on the recording medium. Recording procedure ( c );
When receiving a request to read a record from any one of the plurality of devices, a procedure of reading the requested record from the recording medium and outputting it to the device ( d );
When a record whose data has been edited is received from any one of the plurality of devices, the number in the received record matches the number in the record to be updated recorded on the recording medium. If the number in the received record matches the number in the record to be updated recorded on the recording medium, a number generation request is made to the number generation means, and the received record A procedure ( e ) for writing a record in which a number in the record is replaced with a number output from the number generating means to the recording medium;
A recording medium on which a program for causing the CPU to execute is recorded. A CPU-readable recording medium for processing data by communicating with a plurality of devices,
A procedure (a) of counting the cumulative number of days from a predetermined date of calculation to the present and outputting the value;
In number generating means, in response to the n-th number generation request, a x (i) <x (n ) (i = 1, ···, (n-1)) Number satisfy x (n) The number output by the procedure (a) is the upper digit, the number of times of activation or rebooting on the day is the middle digit, and the number of times the number is requested to be generated that day is the lower digit. Step ( b )
When data is received from any one of the plurality of devices, a number generation request is made to the number generation unit, and a record including the received data and the number output from the number generation unit is recorded on the recording medium. Writing procedure ( c );
A procedure of performing a tabulation process on a record having a number smaller than the number in a record including data instructed by any one of the plurality of devices recorded in the recording medium ( d )When,
A recording medium on which a program for causing the CPU to execute is recorded.

Images