JPH04148233A - Storing system for specification definition information - Google Patents

Abstract

PURPOSE:To make routine for storing and reading out definition data peculiar to a system unnecessary and to reduce a system scale by storing definition information into a data base (DB) by using the routine of a data base management system (DBMS). CONSTITUTION:In the case that data processing is executed by using the definition information registered in a definition data file 104, a specification executing part 105 executes the read-out of the definition data from the definition data file 104 of a DB file as making the name of the definition a key by using the DBMS 103. The specification executing part 105 reads out real data from the real data file 106 of the DB file in conformity to this read out definition information by using the DBMS 103, and gives it working processing designated by the definition information. Thus, a read and storage part to be used exclusively for the definition data can be made unnecessary, and the reduction of a system scale can be attained.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a simple language system for processing data using an electronic computer, and in particular to a storage method of specification definition information in an office processing system using a simple language. Regarding.

[Prior Art] Generally, routine office processing in an office can be broadly classified into three tasks: issuing slips, entering data in ledgers, and issuing lists, invoices, and the like.

Such an office processing system based on the conventional technology has a C0B
The majority of systems have been developed using programming languages such as OL, but in recent years, systems using simple languages have appeared that allow even people with no programming experience to easily construct office processing systems.

When building a business processing system using a simple language,
The following feature points can be obtained.

(1) Even people with no programming experience can easily learn how to use it.

(2) There is no need to write processing methods or procedures; programs can be created simply by specifying the relationship between data and what is desired.

(3) The desired office processing system can be constructed with less than one-tenth the amount of description compared to languages such as COBOL.

(4) Simple languages are easy to use because they are based on interactive operations.

As a conventional technology related to an office processing system using such a simple language, for example, "Hitachi, Ltd. Manual Hitachi Personal Workstation 202Or Program Product 0FIS/FORM Manual J (
2020-3-019) Published in October 1988, etc. is known.

This conventional technology registers user specification definition information in a dedicated file and executes data processing based on it. This conventional technology includes a dedicated file as a definition file, and data to be processed during execution is stored in a database (DB).

FIG. 6 is a block diagram showing the configuration of a system according to the prior art as described above. In FIG. 6, 101 is a console device, 102 is a specification definition section, and 103 is a DBMS.
(database management system), 105 is a specification execution unit;
Reference numeral 108 indicates a definition data reading/storage unit, 109 a system-dedicated file, and 110 a DB file.

In the system according to the prior art shown in FIG. 6, when the user operates the console device 101 and the specification definition unit 102 defines the specification according to the operation,
The specification definition data is stored in the definition data reading storage section 108.
The data is converted into a storage format and stored in a dedicated file 109 unique to the system.

When executing this definition specification, the specification execution unit 10
5 reads definition data from the system-dedicated file 109 using the definition data reading storage unit 108, and uses the DBMS 103 to read the DB according to the specification of this definition data.
Data is extracted from the file 110, the extracted data is processed according to the definition data, and the obtained processed data is stored in the DB using the DBMS 103.
It was stored in file 110.

[Problems to be Solved by the Invention] As described above, the conventional technology retains definition information created by a user in a unique file specific to the system,
The data to be processed by executing the specifications was stored and handled in a DB file.

For this reason, the conventional technology has the problem that routines for storing and reading definition data must be created separately from the DBMS that handles the DB, leading to an increase in system scale.

Furthermore, the above-mentioned conventional technology has a problem in that it is not possible to handle definition data as flexibly as the search function of a DBMS.

It is an object of the present invention to solve the problems of the prior art, to reduce the system scale, and to flexibly handle one-specification definition data during definition operations through DBMS operations such as selection, projection, and combination. The purpose of this invention is to provide a storage method for specification definition information that makes it possible to do this.

[Means for Solving the Problem] According to the present invention, the above object is achieved by storing definition information in a DB, that is, by means of specification definition by the user;
This is achieved by comprising a means for storing definition information created by the means in a DB, and an execution means for executing data processing based on the stored specification definition information.

[Function] The present invention stores definition information in a DB using a DBMS routine.
This eliminates the need for system-specific routines for storing and reading definition data, and also makes it possible to apply the search function of the DBMS to definition data, allowing for flexible definition data. It becomes possible to handle data.

[Example 1] Hereinafter, an example of the definition execution method according to the present invention will be explained in detail with reference to the drawings.

Figure 1 is a block diagram showing the configuration of an embodiment of the present invention, Figure 2 is a diagram showing an example of a screen format called a sales slip defined by the user, and Figure 3 is a specification of the definition information shown in Figure 2. Figure 4 shows the data structure when registered in a DB file called registration table. Figure 4 shows the data structure when the definition information shown in Figure 2 is repeatedly registered in a DB file called registration table. Figure 5 shows the data structure when it is registered in a DB file called registration table. FIG. 3 is a diagram showing a data structure when the definition information shown in FIG. 2 is registered in a DB file called an item registration table. In FIG. 1, 104 is a definition data file, 106 is an actual data file, and other symbols are the same as in FIG. 6.

One embodiment of the present invention shown in FIG. 1 has the following points: Definition data and actual data can be accessed in common from the DBMS 103 and are stored in respective files 104 and 106 as B files, and a dedicated file unique to the system is stored. This differs from the prior art described with reference to FIG. 6 in that a definition data reading and storing section is not required.

In such an embodiment of the present invention, specification definition is performed using the console device 101 and the specification definition unit 102, as in the case of the prior art.

The specification definition unit 102 classifies the definition information thus created for each DB file to be registered, and stores the registered information in the D
It is registered in the definition data file 104 as a DB file using the routine of the BMS 103.

When executing data processing using definition information registered in the definition data file 104, the specification execution unit 105:
Using the definition name as a key, the definition data can be read from the definition data file 104, which is a DB file, using the DBMS 103. Then, the specification execution unit 105
According to this read definition information, DBMS I O3
The actual data may be read from the actual data file 106, which is a DB file, using , and processed as specified by the definition information.

Hereinafter, the operation of one embodiment of the present invention will be explained in detail by giving a specific example.

A screen example of a sales slip is shown in FIG. 2, and the operation of storing definition information in the definition data file 104, which is a DB file, will be explained using this example.

It is assumed that the screen example of the sales slip shown in FIG. 2 is the format of the input image, and that the following is defined by the user's definition or as a system default.

The definition name of the illustrated screen specification is "sales slip", and information such as screen size, creation date, etc. is obtained.

In this definition, the repeat part (details part of the slip) 301 is 1
The name of the repeated part is "Details part", and the repetition information includes the number of lines to be displayed on the screen as 3 lines, the interval between detail lines as 2 lines, and the ruled line information of the "Details part". It is defined that the entire detail group is surrounded by ruled lines.

In addition, ite, XXXX302 and XXX30 are shown in Figure 2.
3 is an item for inputting and outputting data, and is a sales slip 304.
is a constant) item. .

The screen is divided into rectangles as items by the user or by the system, and each rectangle has a unique name (item name).
is attached. In addition, the attributes of each item include location,
Attributes such as data type and information on ruled lines surrounding the rectangle are defined.

That is, each item of 302, 303, and 304 in FIG. 2 is defined as follows.

The item name 302 is the customer name, starts from the 4th row, 2nd column, is 10 digits long (half-width conversion), has a character data type, is an item input by the user, and must be included in the customer name in the customer ledger table. Must be.

The item name 303 is a product code, starts from the 10th row, 3rd column, has a length of 6 digits, and has a numeric data type. The ruled line surrounds the entire item with a frame and is located within the details section. The value of this product code is input by the user and is defined as having to be less than 9000.

304 is a heading, which is named item 1 by the system, and from the 20th column of the 2nd row, the length is 8 characters, the entire item is in character type, surrounded by ruled lines, and the text ``Sales Slip'' is displayed. This is an item that outputs .

The specification definition information as described above is defined by the user,
When this specification definition is completed, this definition information is hierarchically classified and registered in a plurality of tables, and stored in the definition data file 104, which is a DB, in a relational database format.

First, one definition name of specification definition information, etc. is registered as a registration record 401 in a specification registration table as shown in FIG.

Then, in the registration table shown in FIG. 4, a record 501 containing the attribute value is registered as repetition information with the definition name "Sales slip" and as the repetition box name "Details part". Ru.

Similarly, in the item registration table shown in Figure 5, for each other item, the definition name is "sales slip", and if that item is included in the frame "details", the frame name is "details". part",
If it is not included, leave blank (or NULL) in the frame name field.
), and then a record containing the item's position, length, data type, ruled line information, and item processing is registered as the name and attributes of these items.

In this example, records 602.603.604 correspond to items 302.303.30, respectively, as illustrated by FIG.
It corresponds to 4.

As described above, an embodiment of the present invention hierarchically classifies specification definition information into information related to the entire definition, information related to repetition, and information related to each item, and creates a file as a DB file for each layer. , and store the definition information of each hierarchy as the column value of the corresponding DB file, and at that time, store the lower level information along with the key value (name) of the higher level information that contains it. There is.

In addition, when reading these, when the definition name "sales slip" is specified, it is sufficient to read the record having "sales slip" as the definition name from the specification registration table, frame registration table, and item registration table.

[Effects of the Invention] As explained above, according to the present invention, it is possible to eliminate the need for a readout storage section dedicated to definition data, thereby reducing the system scale. In addition, functions such as selection, projection, and combination provided by the DBMS can be used as they are, so definition data can be handled flexibly.

[Brief explanation of drawings]

Figure 1 is a block diagram showing the configuration of an embodiment of the present invention, Figure 2 is a diagram showing an example of a screen format called a sales slip defined by the user, and Figure 3 is a specification of the definition information shown in Figure 2. Figure 4 shows the data structure when registered in a DB file called registration table. Figure 4 shows the data structure when the definition information shown in Figure 2 is repeatedly registered in a DB file called registration table. Figure 5 shows the data structure when it is registered in a DB file called registration table. A diagram showing a data structure when the definition information shown in FIG. 2 is registered in a DB file called an item registration table, and FIG. 6 is a block diagram showing the configuration of a system according to the prior art as described above. 101...-console equipment, 102...
... Specification definition section, 103 ... DBMS (database management system), 104 ... Definition data file, 105 ... Specification execution section, 106.
. . . Actual data file, 108 . . . Definition data reading storage section, 109 Old . . . System exclusive file, 110 . . . DB file.

Claims (1)

[Scope of Claims] 1. A business processing system using an electronic computer, comprising a specification definition means by a user and a means for storing specification definition information created by the means in a database using a DBMS routine. Features: Storage method for specification definition information. 2. The specification definition information storage method according to claim 1, further comprising execution means for executing data processing based on the specification definition information. 3. The specification definition information storage method according to claim 1 or 2, wherein the database is a relational database.