JPH063603B2 - Transaction processing data management method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION <Industrial field of application> The present invention relates to an online processing system in a financial institution, etc.
The present invention relates to a transaction processing data management method capable of efficiently managing transaction data that cannot be normally processed.

For example, in an online system in a bank, a computer installed in a center and a plurality of business stores (branches, business offices, etc.) are connected by a line. Then, transaction information input from a terminal device (a teller device, an automatic transaction device, etc.) installed in each branch is sequentially sent to the center computer.
On the basis of this transaction information, the center computer performs transaction information such as updating a customer master file (a file that stores information about the customer and the customer's account).

On the other hand, in the center, in parallel with the online transaction processing, the center side independently performs the transaction processing collectively. The collective processing at this center corresponds to, for example, automatic transfer processing such as payment of utility bills, transfer with a designated date. That is, a process of withdrawing a predetermined amount of money from the customer's account is performed every month by a predetermined date.

Thus, in the online system, online transaction processing by the center computer and batch processing (usually batch processing) are performed in parallel. At this time, in batch processing, there is a problem in handling transaction data that has been left unfinished. That is, the transaction data collectively processed as described above is a transaction process with a specified date. Therefore, it is necessary to somehow reprocess transaction data that has been unprocessed due to a system error or the like in the collective processing by the center.

As described above, there is a demand for a quick and appropriate countermeasure against transaction data that is abnormally terminated due to a system error or the like in the central processing of the center.

<Prior Art> In the above system, when transaction data of abnormal termination (unprocessed) occurs in the central processing of the center, conventionally, the center side is configured to output a list of the unprocessed transaction data. There is. The center manager then looks at this list and attempts to reprocess the unprocessed transaction data. In other words, the cause of the abnormal termination is investigated, and if there is a failure in the system (program) that performs batch processing, the failure is corrected and reprocessing of transaction data is attempted.

<Problems to be Solved by the Invention> However, the above-mentioned error coping method requires work such as debugging of the batch processing program by the center administrator. As a result, there is a problem that an enormous amount of labor and time are required for error analysis when an error occurs. Furthermore,
There is a problem that unprocessed transaction data out of the transaction data to be processed by the current day cannot be processed within the current day by batch processing.

<Means for Solving Problems> An object of the present invention is to solve the above-mentioned conventional problems. That is, for transaction data that has not been processed (cannot be processed) by the central processing of the center, it is possible for the sales office side that needs to process the transaction data to understand it.
It aims to provide a transaction processing data management method that enables a sales office to quickly deal with unprocessed data.

Therefore, in the present invention, a collection file for collecting transaction data that has been abnormally terminated in batch processing is provided, and in response to a request from a terminal device of a sales office, the collection file is referred to, It is configured so that unprocessed data related to can be returned.

<Operation> As will be described later, the transaction data to be collectively processed at the center is such that the transaction data handled by each sales office is collectively processed at the center side. Therefore, by making it possible to notify the sales office side of transaction data that has not been processed by the central processing, it becomes possible for the sales shop side to take appropriate measures for the unprocessed data.

In other words, the present invention focuses on the fact that the central batch processing and the online transaction processing exist as routes for accessing the customer master file. Then, for those that are abnormally terminated by the batch processing of the center, it is possible to re-process the online transaction input from each sales office. As a result, it becomes possible to recover transaction processing by online transaction for data that has not been processed due to a failure (program error) of the batch processing unit at the center. Hereinafter, the present invention will be described in detail with reference to examples.

<Embodiment> FIGS. 1 and 2 are diagrams showing an embodiment in which the present invention is applied to an online processing system of a bank, and FIG. 1 is a diagram showing a concrete configuration on the center side, and FIG. The figure is a block diagram showing the configuration of the entire system. In both figures, common parts are designated by the same reference numerals.

In the figure, 1 is a center computer, 3 is a sales office, 11 is a system controller (OS), 12 is a communication controller (NCP, V).
TAM), 13 is a database control unit (AIM), 14
Is a batch processing support unit, 15 is an online deposit / withdrawal processing unit (hereinafter, simply referred to as an online processing unit), 16 is a center batch processing control unit (hereinafter, simply referred to as a batch processing unit), 17
Is an abnormal termination data management unit (hereinafter referred to as an abnormality management unit), 18 is a format conversion unit, 19 is an abnormality processing unit,
Reference numeral 20 is a customer master file (hereinafter, simply referred to as a master file), 21 is a batch processing file, 22 is a management file, and 23 is an abnormal end data collection file (hereinafter, collection file).

In the figure, each part 1 that constitutes the center computer 1
Reference numerals 1 and 13 to 19 are functional portions for operating a computer, respectively, and are realized as independent program packages in this embodiment. The system control unit 11 and the database control unit 1 are base programs for constructing an online system, and are realized as basic software and packages provided by the manufacturer. It can be considered as an online processing unit 15, a batch processing unit 16, an abnormality management unit 17, and a user application program for performing banking business.

The online processing unit 15 and the batch processing unit 16 are configured to be able to independently access the master file 20 under the control of the database control unit. Of these, the online processing unit 15 receives transaction information input from a terminal device 33 such as a window device or an automatic transaction device in the sales office 3 via the communication control unit 12. The transaction information to be received includes information (account number, transaction type, amount, etc.) regarding deposit transaction, withdrawal transaction, or exchange transaction. The online processing unit 15 accesses the master file 20 according to the transaction information, determines whether or not the transaction can be performed, and if the transaction can be performed, updates the balance and the like in the corresponding account and records the transaction content. Then, the transaction approval / disapproval information, the transaction result, and the print data are returned to the terminal device 33. The terminal device 33 outputs the slip 34 on the basis of the received information, and ends one transaction for handing over to the customer.

On the other hand, the collective processing unit 16 performs the automatic transfer processing as described above. The transaction processing in the batch processing unit 16 is performed by batch processing after the bank window business is completed (for example, at night). Alternatively, it is performed by batch processing in parallel with the online transaction processing by the online processing unit 15.

As shown in FIG. 1, the transaction data (automatic transfer data) to be collectively processed at the center is the magnetic tape (MT) 24.
Stored in. For example, they are collectively stored in separate magnetic tapes 24 for each deadline of each month to be processed. That is, the data relating to the automatic transfer agreed with the customer at each business office 3 is stored collectively for each processing date. From the console (not shown), the operator (center manager, etc.)
Is issued, the batch processing described below is started.

First, the database control unit 13 reads the transaction data stored on the magnetic tape 24. Then, the format of the transaction data read by the format conversion unit conversion unit 18 is sequentially stored in the uniform batch processing file 21. This transaction data includes, for example, account number information for automatic transfer,
It includes the transfer amount, the due date, and the sales office code. The format conversion unit 18 sets a predetermined number (for example, 100 pieces of transaction data) of this transaction data as one batch processing file 21 and further attaches a record number R to each transaction data TR ₁ , TR ₂ ,. Store as.

Next, the abnormality processing unit 19 in the control unit 13 generates a management file 22 corresponding to each batch processing file 21 generated by the format conversion unit 18. Each of these files 21 and 22 may be considered as a storage area allocated to a main storage or an auxiliary storage device (not shown) of the center computer 1. It goes without saying that these files 21 and 22 are managed in a one-to-one correspondence with a series of file numbers.

Upon completion of generation of the batch processing file 21 and the management file 22, the batch processing support unit 14 of the control unit 13 is activated. The transaction data stored in the batch processing file 21 is read to the batch processing support unit 14 for each record (one transaction data), the batch processing unit 16 is activated, and the read transaction data is sent. Then, the collective processing unit 16 accesses the master file 20 according to the contents of the transaction data, and executes the designated transfer process. When the processing of the given transaction data ends normally, the batch processing unit 16 notifies the batch processing support unit 14 of the normal end. As a result, the support unit 14 reads the transaction data of the next record from the file 21 and gives it to the batch processing unit 16. In this way, the transaction data of each record of the batch processing file 21 is sequentially processed.

On the other hand, when the processing for the given transaction data ends abnormally, the collective processing unit 16 returns a message of the abnormal end to the database control unit 13. The cause of this abnormal termination includes a data exception in the program (collective processing unit 16), a database (master file) access error, and the like. The abnormal end notification from the batch processing unit 16 is accepted by the abnormal processing unit 19 of the control unit 13.

Upon receiving the notification of the abnormal end, the abnormal processing unit 19 stores the transaction data in the abnormal end in the batch processing file 21.
The record number of the file in which the transaction data is stored is recorded on the management file 22 corresponding to. If the batch processing is to be continued after this, a restart command is input from the console (not shown) by restarting. Then, the batch processing support unit 14 reads the transaction data of the next record and allows the batch processing unit 16 to continue processing the subsequent data. In this way, processing of all transaction data (100 data in the above example) in one batch processing file 21 is executed.

When the processing of the batch processing file 21 is completed, the operator operates a console (not shown) to give an instruction to collect transaction data that has ended abnormally (hereinafter, abbreviated as abnormal end data). By this collection instruction, the database control unit 1
The batch processing support unit 14 of No. 3 activates the abnormality management unit 17.

The abnormality management unit 17 first refers to the management file 22 and reads the record number R that ended abnormally. Then, the batch processing file 21 is accessed using this record number R. As shown in FIG. 2, the abnormality management unit 17 is configured to be able to access the files 21 to 23. The abnormality management unit 17 reads the transaction data TRI that has become abnormal end data by accessing the files 21 and 22. Then, according to the sales office code included in the transaction data, the abnormal termination data is edited for each sales office 01, 02, ...
The edited result is stored in the collection file 23. By the above operation, processing of each transaction data in one batch processing file 21 and collection of transaction data abnormally ended in the batch processing are performed.

Incidentally, the list output of the abnormal end data, which is conventionally performed on the side of the center, is the list output of the record number and the input data recorded in the management file 22. In the present embodiment, transaction data that has ended abnormally is collectively written in the collection file 23 for each business store.
Further, as will be described below, the collection file 23 is provided so that it can be referred to by the database control unit 13. This enables the abnormal termination data to be returned online in response to an inquiry from each sales office.

The time zone in which the batch processing is performed by the batch processing unit 16 is predetermined by each bank system. Therefore, each sales office makes a reference (inquiry) request for abnormal end data to the center in anticipation of the end of batch processing by the center. That is, each business office 3 makes a request using its own terminal device 31. The transmission of a telegram for requesting the reference of the abnormal termination data can be easily realized by assigning the reference request instruction function to a predetermined key on the terminal device 31.

In response to the inquiry request from the terminal device 31, the database control unit 13 refers to the collection file 23. The collection file 23 is accessed through the abnormality management unit 17. Then, the abnormal termination data relating to the sales office in which the terminal device 13 that made the inquiry request is installed is read. The read abnormal termination data is returned to the terminal device 31 via the database control unit 13 and the communication control unit 12.

The terminal device 31, which has received the abnormal termination data, outputs the received data as the inquiry form 32 by its own printer or the like. By looking at this inquiry form 32,
The transaction data (transfer data in this case) that has not been processed yet at each sales office 3 can be grasped. Then, among the unprocessed data, data that needs to be processed on the same day (within the day) will be performed by the online transaction processing by the terminal device 33 described above. Alternatively, it may be processed by off-line transactions within the sales office.

As described above, in the present embodiment, the management and operation of transaction data that has not been processed (end of processing) in the center batch processing can be distributed among the sales offices. As a result, the load on the unprocessed data generated by the center administrator can be reduced.

In addition, since the unprocessed transaction data can be reprocessed (online or offline processing) at each business store, it is possible to process the unprocessed data quickly and appropriately. In particular, when processing unprocessed data by online transaction, the master file in the center is accessed by the online processing unit that operates separately from the batch processing unit. Therefore, the unprocessed data due to the failure of the batch processing unit itself can be reliably recovered.

Although the terminal device for inquiring about abnormal termination data and the terminal device for online transaction are separately provided in the above-described embodiment, this is for convenience, and both functions can be performed by one terminal device. Needless to say. Further, in the embodiment, the automatic transfer processing is taken as an example of the center batch processing, but it is needless to say that the present invention can be applied to the case where the center collectively processes transactions other than transactions handled online at a sales office.

〔The invention's effect〕

As described above, according to the present invention, when unprocessed (abnormal termination) occurs in the transaction data collectively processed in the center, the unprocessed transaction data can be notified to the sales office side.
Therefore, the processing on the transaction data can be distributed and executed in each sales office, and the transaction data that has ended abnormally can be dealt with promptly and appropriately.

[Brief description of drawings]

1 and 2 show an embodiment in which the present invention is applied to a bank online system. FIG. 1 is a diagram showing a configuration of a batch processing system in a center, and FIG. 2 is an entire system. It is a figure which shows the structure of. Reference numeral 1 is a center computer, 3 is a sales office, 15 is an online processing unit, 16 is a batch processing unit, and 17 is an abnormality management unit.

Claims (1)

[Claims] 1. An online transaction processing unit connected to a terminal device for inputting transaction information and performing a transaction process based on input information from the terminal device, and an online transaction processing unit provided separately from the online transaction processing unit. In an online processing system including a batch processing unit that collectively carries out predetermined transactions, a management file that stores information related to transaction data in which an error occurred during processing of the batch processing unit, and a management file that stores the management file A collection file that collects transaction data that has been abnormally terminated by the batch processing unit based on the information obtained, and refers to this collection file in response to a request from the terminal device and installs the terminal device. A transaction processing data management method characterized by returning abnormal termination data related to a sales office.