JPS601670B2 - Processing data transmission method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION The present invention relates to a process data transmission system between a center and multiple branches.

In a data transmission system, an intelligent terminal is placed at a branch office, sales office, etc., a distribution file is placed on the center CPU side, various data related to inventory management, etc. are written in the distribution file, and this can be discussed from the terminal at any time. If the memory area for distributed files is fixedly divided for each terminal, file management will be easy.

However, with this method, even if there is no data to be distributed to a terminal, a predetermined size of memory area must be left open in the distribution file; Since the decision must be made based on the terminal where the data is located, the distribution file must have a large capacity. Distribution data varies greatly depending on each branch, season, etc., and while there is a large amount of distribution data for one branch, there is a small amount of distribution data for other branches, and it varies depending on the day or month. I'll replace it. Therefore, the method of fixedly allocating the memory area of the distribution file to each terminal is wasteful. The present invention aims to improve this problem, and instead of allocating the memory area of the distribution file to each terminal in a fixed manner, it is allocated each time for each terminal or batch, and the allocated area is the area for the distribution file. An empty area management table is provided in the system, and when creating distribution data, selection is made from the empty areas registered in the table. Then, the address of the memory area where the distribution data is written is written in a data management table for each terminal, and when a data transmission request is received from a terminal, this management table is checked and the distribution data for that terminal is transferred from the distribution file. The data is read and sent to the corresponding terminal. In this way, the memory area for the distribution file can be effectively allocated to the terminal where the distribution data is stored, and the capacity of the file can be made as small as possible. This will be explained in detail below with reference to the drawings. A, B, C in the drawing
. . . is an intelligent terminal placed at each branch office, and is connected to the center CPUIO through a public line.

FR and PR are floppy disks and printers attached to each terminal. DF is a distribution file placed on the center side, 18 is a management unit for the file, 20 is a terminal-specific data management unit, and 22 is a free area management unit. There are various types of data written to the distribution file DF, one of which is data related to inventory. 16
indicates inventory processing, and 14 indicates its file.

Each branch sends data such as sales, inventory, requests for sending out missing items, etc. to the center, but since this data is transmitted all at once using a floppy FR, it is batch processed (12) and the received data is filtered out. If there is a problem (for example, a product code that is not supposed to exist at the branch is causing the problem, there is an excess or deficiency in inventory, etc.), the error data will also be sent to the distribution file D.
Write to F and read it from the terminal to check. The data written to the distribution file DF is by terminal,
By batch (even if the data belongs to the same terminal, the data is generated at different times, and if there is data from another terminal in between, it is treated as different data). FIG. 2 is a diagram showing the distribution file DF and tables 20 and 22 in detail. As shown in the figure, the distribution file DF is stored in its memory area 0-a. The first group data of terminal A is written to a2-a3, and the data of terminal B is written to a2-a3.
The second group data of terminal A, etc., are written in the first group data, a3-a4, and the memory areas a, a3-a4 have been written.
2. If the key is assumed to be empty, the terminal name, batch number, and address within the file are written in the terminal data management table 20 and the empty area management table 22 as shown in the figure. When a transmission request is received from the terminal side, the terminal-specific data management table 20 is first referred to, the address of the memory area on the distribution file of the distribution data for the terminal is determined, the distribution file is read out according to the address, and the read data is read out. is sent to the terminal. When distribution data is sent out, for example, when there is a transmission request from terminal B and the data in memory areas a2-a3 is sent out, the data area becomes a stop area and is deleted from the table 20 and is instead stored in the table 22. be registered. When writing distribution data to the distribution file DF, look at the area management table 22,
A free area in which the distribution data can be sufficiently written is found and the distribution data is written therein. If there is no free area in which to write the distribution data, the buffer is treated as full and writing is prohibited. In such a case, it may be possible to write by dividing the data into two empty areas, but there is a problem of where to divide the data.
In such a case, it is better to sort the free areas on the distribution file into one, and then write the data all at once. As is clear from the above explanation, according to the present invention, there is no need for the distribution file to have a space that can store the data amount on peak days for each terminal, but a space that can store the data amount on peak days for the entire system. Just let them have it.

According to this method, in applications where peak days differ for each terminal, the distribution file capacity can be reduced to 2/3 to 1/2 of that of a conventional system.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing an embodiment of the present invention, and FIG. 2 is an enlarged view of a part of FIG. 1. In the drawing, A, B, C, . . . are terminals, DF is a distribution file, 20 is a data management table for each terminal, and 22 is a free area management table. Figure 1 Figure 2

Claims (1)

[Claims] 1. It has terminal equipment installed at multiple branches and a center equipped with a processing equipment that is connected to these terminal equipment via a line and processes data for each branch. In a data transmission system in which data processing results for each branch are distributed from a center based on the data processing results, there is a file in which processing results for each branch processed by the processing device are temporarily stored in each processing unit, and a file in which each processing result in this file is stored. The center is provided with a data management unit that holds storage address information in an identifiable manner for each terminal and processing unit of each branch, and a free area management unit that holds information regarding the free space of this file. The processing results including data and error data are stored in a file for each terminal to which the processing results are to be distributed by referring to the free area management section, and the processing results corresponding to the terminal that has made the distribution request are referred to the data management section. A processing data transmission method characterized by reading data from a file and sending it to the terminal.