JPH0521248B2 - - Google Patents

Description

[Detailed Description of the Invention] [Summary] When a format definition file that is used randomly during program execution is used for multiple devices in one program, the definition file can be defined by consolidating the definition file loading area into one and managing it collectively. Measures to reduce the body loading area and the number of defined body loadings.

[Industrial application field]

The present invention relates to an improvement in a buffer management method associated with dynamic format data loading.

[Conventional technology]

A data processing device often uses a format definition when executing a program that outputs information to a printing device or the like.

This format definition body (hereinafter referred to as the definition body)
is the definition information of the screen or form format, and is usually stored in a definition file provided on a magnetic disk drive, and multiple frequently used definitions are stored in the definition program loading area (buffer) in the main memory. Use it after moving it.

Storing the desired definition program from the definition program file into a buffer and using it in this way is a measure taken to reduce the number of times data is exchanged between the magnetic disk device and the main storage device and increase processing speed. be.

FIG. 4 is a diagram illustrating a conventional format data management system.

In the figure, 1 is an application program, 2 is a processing unit of the application program 1, 3 is a data unit of the application program 1, 4 is a definition management program, 5 ₁ to 5 _o are control units, and 6 ₁ to 6 _o are each An output device, 9 a definition file device, 10 ₁ to 10 _o each a definition management unit,
11 ₁ to 11 _o are memory management tables, 12 _1
.about.12o are definition field loading areas, respectively.
The same symbols represent the same objects throughout all the figures below.

Here, the output devices 6 ₁ to 6 _o are, for example, printing devices, and according to the conventional method, the following are prepared for each output device 6 ₁ to 6 _o .

That is, the definition program loading area _12o is an area for storing definition programs for the output device _6o transferred from the definition program file device 9, and the memory management table _11o.
is a table showing the names and addresses of the definition programs stored in the definition program loading area _12o , the definition program management section _10o is the operating status of the definition program in use,
A management unit and a control unit 5 _o that indicate the addresses and addresses are programs that control the output device 6 _o .

It should be noted that the application program 1, the definition program management program 4, the control section ₅₁ to _5o , and the definition program management section ₁₀₁ to 10
_o , memory management tables 11 ₁ to 11 _o , definition program loading areas 12 ₁ to 12 _o , etc. are all set on the main storage device (not shown).

Now, the record of the data section 3 of the application program 1 is sent from the processing section 2 of the application program 1 to the output device 6 _o
On the other hand, when outputting using a certain definition program, the definition program management program 4 refers to the memory management table 11 _o for the output device 6 _o .

If there is a corresponding definition program in the memory management table _11o , it will be used to output to the output device _6o , and if there is no corresponding definition program in the memory management table _11o , it will be output from the definition program storage file 9. The relevant definition program is loaded into the definition program loading area 12 _o and entered in the memory management table 11 _o , and the information is set in the definition program management section 10 _o and output to the output device 6 _o .

As described above, conventionally, each output device 6 ₁ to 6 _o has a definition program loading area 12 ₁ to 12 _o , a memory management table 11 ₁ to 11 _o , and a definition program management section 10 ₁ to
10 _o .

[Problem that the invention seeks to solve]

As can be seen from the above explanation, in the conventional management system, a definition program loading area is provided for each of a plurality of output devices, and each of these is managed separately. The same definition body may be loaded.

Therefore, overall, there is a disadvantage that the definition program loading area is wasted and the number of times of loading from the definition program storage file to the definition program loading area increases.

[Means for solving problems]

The above problem is solved by outputting the data portion 3 of any program 1 to multiple output devices 6 ₁ to 6 _o using the format definition stored in the definition file 9 as shown in the principle diagram of FIG. In a data processing device that performs a format definition program, a definition program loading area 23 temporarily stores a format definition program commonly used for the output devices ₆₁ to _6o , and a definition program loading area 2.
A memory management table 22 is provided that indicates the addresses of format definition programs stored in the format definition program 3, and a definition program management section 21 ₁ to 21 that indicates the usage status of the format definition program currently in use is provided for each output device 6 ₁ to _6o . This problem can be solved by providing _o .

[Effect]

According to the present invention, when the definition program management program 4 outputs the data section 3 to the output devices ₆₁ to _6o using a certain format definition program, the definition program management program 4 refers to the memory management table 22. , if the corresponding format definition is not found in the memory management table 22, the definition is loaded from the definition file 9 to the definition loading area 23 and the information is sent to the definition management unit 21 for the output devices ₆₁ to _6o .
₁ to 21 _o , and if the information does not match the contents of the definition program management section 21 ₁ to 21 _o , it is set again to eliminate waste of the definition program loading area, It becomes possible to reduce the number of times of loading from the storage file.

〔Example〕

FIG. 2 is a diagram showing an embodiment of a shared format data management method according to the present invention.

In the figure, 21 ₁ to 21 _o are respectively the definition management section and 22
2 is a memory management table, 23 is a definition program loading area, 50 is a main storage device, and 51 is a main control device.

The definition program management unit 21 ₁ is a definition program management unit for the output device 6 ₁ , the definition program management unit 21 _o is a definition program management unit for the output device 6 _o , and the memory management table 22 is a shared memory management table for definition program loading. The area 23 is a shared definition program loading area, both of which are located on the main storage device 50. The application program 1 is also located on the main storage device 50, and the main controller 51 loads the application program 1, the application program 1, The definition program management program 4 and the like are read and output operations are performed.

Now, the record of the data section 3 of the application program 1 is sent from the processing section 2 of the application program 1 to the output device 6 _o
When outputting using a certain definition program, the definition program management program 4 outputs the definition program in the definition program loading area 2.
Refer to the memory management table 22 of No. 3.

If the corresponding definition program is not found in the memory management table 22, the definition program is loaded from the definition program file 9 to the definition program loading area 23, the corresponding definition program is entered in the memory management table 22, and this information is sent to the definition for the output device _6o . body management section 21 _o .

If this information does not match the contents of the definition program management section _21o even if the corresponding definition program exists in the memory management table 22, the contents of the definition program management section _21o are reset.

Note that even when the corresponding definition program exists in the memory management table 22, the case where this information does not match the contents of the definition program management section _21o means that, for example, after the definition program management section _21o uses the definition program P, the definition program When the loading area 23 becomes full, the definition program P is temporarily discarded, and then when it is needed again and the definition program P is loaded from the definition program file 9 to the definition program loading area 23, the same definition is used. Even if it is a field P, its storage address does not match the previous storage address.

At this time, when the definition program management section 21 ₁ attempts to use the definition program P, the previous address is stored in the definition program management section 21 ₁ , so it may not match the new address. In such a case, the definition body management unit ₂₁₁ resets the address to a new address.

Furthermore, if the definition program loading area 23 runs out of space during loading, the LRU is used for expulsion management.

In general, the LRU (least recently used) method is often used to load modularized program information from an external storage device such as a disk device to a predetermined area of the main storage device as needed.

FIG. 3 is an explanatory diagram of the LRU method.

In the figure, A, B, C, and D are information modules, and X and Y are areas.

The LRU method is a method that manages to retrieve the latest one with the last used time.
As shown in the figure, for example, four information modules A,
The case where B, C, and D are loaded into two areas X and Y will be explained as an example.

First, when using information module A, this information module A is loaded into area X that is in an unused state.

When information module B is to be used next time, this information module B is loaded into another unused area Y.

When using information module C in a state where information modules are loaded in both areas The information module C is loaded into the area where the information module C exists, that is, the area X.

Thereafter, when loading a new information module in the same manner, the area in which the oldest used information module exists among the information modules that have already been loaded is determined as the new loading area.

〔Effect of the invention〕

As explained in detail above, according to the present invention, it is possible to reduce the number of times of loading when multiple devices share a definition program, that is, reduce the number of I/O accesses and reduce the memory area used. There is a big effect.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing the principle of the present invention. FIG. 2 is a diagram showing an embodiment of a shared format data management method according to the present invention. FIG. 3 is an explanatory diagram of the LRU method. FIG. 4 is a diagram illustrating a conventional format data management system. In the figure, 1 is an application program, 2 is a processing unit of the application program 1, 3 is a data unit of the application program 1, 4 is a definition management program, 5 ₁ to 5 _o are control units, and 6 ₁ to 6 _o are each An output device, 9 a definition file device, 10 ₁ to 10 _o each a definition management unit,
11 ₁ to 11 _o are memory management tables, 12 ₁
~12 _o are respectively definition field loading areas, 21 ₁ ~
21 _o is a definition program management unit, 22 is a memory management table, 23 is a definition program loading area, 50 is a main storage device, 51 is a main control device, A, B, C, and D are information modules, respectively, X, Y are each a domain.

Claims (1)

[Claims] 1. In a data processing device that outputs the data part 3 of an arbitrary program 1 to a plurality of output devices 6 ₁ to 6 _o using a format definition stored in a definition file 9. , a definition program loading area 23 for temporarily storing the format definition program commonly used for the plurality of output devices 61 _{to 6o} , and an address of the format definition program stored in the definition program loading area 23. A definition management unit 21 ₁ is provided for each of the output devices 6 ₁ to 6 _o to indicate the usage status of the format definition program in use.
~ _21o is provided, and when the definition program management program 4 outputs the data section 3 to the output devices ₆₁ to _6o using a certain format definition program, the definition program management program 4 manages the memory. Referring to the table 22, if the corresponding format definition is not found in the memory management table 22, the definition is loaded from the definition file 9 to the definition loading area 23 and the information is sent to the output devices ₆₁ to _6o . The information is set in the definition body management unit 21 ₁ to 21 _o of the definition body management unit 21 1 to 21 o.
₁ to 21 _o A shared format data management device characterized in that the settings are reset if they do not match the contents of o.