JPH0213336B2 - - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Technical Field of the Invention] The present invention relates to a line number setting method in which the line number is placed outside the record in order to make it possible to use all fields within the record.

[Conventional technology and problems]

Conventionally, when editing a record, line numbers are naturally added to the record, and as a result, it is not possible to use all the fields in the record. Therefore, line numbers may not be added to allow use of all fields in a record. However, if line numbers are not added in this way, EDITOR such as the EDIT command, for example,
Line numbers cannot be specified using commands such as LIST100 and LIST1000, and such commands cannot be used, so NONUM (no number) must be specified. In this case, the relative number of the record must be located and displayed. Therefore, when editing, it is difficult to search for a desired record.

[Purpose of the invention]

The present invention solves the above-mentioned problems, and by providing the line number outside the record, it makes it possible to use all the fields in the record, making it easy and efficient to renumber all the records. The purpose is to make it easier to search for desired records.

[Structure of the invention]

In order to achieve the above object, the line number setting method of the present invention sets the initial value and increment value for each generation at the beginning of the data record when configuring a module containing multiple data records on an external storage device. The method is characterized in that line number control information is provided, and line numbers corresponding to each generation are determined for subsequent data records based on the initial value and increment value for each generation of the line number control information. It is something to do.

[Embodiments of the invention]

Hereinafter, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram showing one embodiment of the present invention;
FIG. 2 is a diagram showing an example of a data structure module according to the present invention, and FIGS. 3 to 8 are diagrams showing examples of table management information and sequence table entry states according to the present invention.

In the figure, 1 is data, 2 is line number management processing unit, 3 is processing target data set (GEM library), A is module, 4 is list output, 11
is table management information, 12 is a sequence table, and 12' is a sequence table entry.

In Figure 1, when data 1, ADD A, INIT=100, INCR=100 are input, the record length, identification flag, level, processing order, initial value, and increment value are stored in the first record storage location of module A. Line number control record 1 with
A record is written, and then a data record numbered 200 is written to the next record storage location. If there are only data 1 and 2, line number control record 2 indicating the end of the module is written in the last record storage location.

When numbering module A in Figure 1 with an initial value of 10 and an increment value of 10, numbering is completed simply by adding a line number control record at the beginning of the module, and the numbering is completed by simply adding a line number control record to the beginning of the module. There is no need to rewrite line numbers.

Figure 2 shows data 1 and 2 corrected and data 1
This shows the data structure when new data 1' is inserted between and 2. Note that when the module is first created, it is set to level 1, and when the module is subsequently corrected, it is set to level 2. The same applies below. Figure 2 shows an example of a module configuration that has a SEQ record for NUM and a SEQ record for INS (NRG).
The SEQ record for NUM corresponds to line number control record 1 in FIG. 1, and the EOM record corresponds to line number control record 2 in FIG. In Figure 2, we first set two data records with an initial value of 100 and an incremental value of 100.
I am registered with . NUM was created at that time.
This is a SEQ record for Here, 0C is X0C
In other words, the length of the record is 12 bytes, 64 is a flag indicating the line number record, indicating that it is the original line number information throughout, 1 indicates the level, and 0 indicates the processing order. 100 indicates an initial value and an increment value, respectively.
If you want to renumber to an initial value of 10 and an increment value of 10 at the next level, simply add a SEQ record for NUM to the beginning of the module to complete the renumbering. After that, if one record is to be inserted after data 1 in line number 10, a SEQ record for INS and an EOD record indicating the end of the inserted data are created and data 1' is inserted.

When outputting a list of modules as shown in Figure 2 or outputting to a display device,
How to use the information in the SEQ record will be explained with reference to FIGS. 3 to 8. When reading the module's NUM SEQ record,
FIG. 3 shows a table created by the line number processing section 2 shown in FIG. 1. The table in FIG. 3 may be considered to exist on a storage device. The first entry 12' of the sequence table 12 is
A SEQ record for NUM is created, and the second entry 12' is created by a SEQ record for NUM. When data 1 is read in this state, this record has an initial value of 10 for the first entry.
Assign. At this time, in the "Next line number" field in that entry, set the initial value (10) + increment value (10) = 20 as the line number for the next record read, and The same process is applied to the "Next line number" field, that is, 200 is set.
FIG. 4 shows the set state. Therefore, if the next module read is a data record, line number 20 will be assigned to this record. However, in the case of the example shown in FIG. 2, the next record is the INS SEQ record, so the new (3
Entry 12' (th) is created by the INS SEQ record. FIG. 5 shows the created state. According to the contents of this entry 12', line number 11 is assigned to the next read data record. At this time, the "next line number" field in the third entry is set to 12 by performing the same process as described above. FIG. 6 shows this state. When the next record is read, it is an EOD record, and this record signifies the end of the management range of the INS SEQ record with identification flag 60, so the third entry information is deleted. FIG. 7 shows this state. Therefore, the next read data
The record is assigned line number 20. At this time, the "next line number" field in the entry is subjected to the same processing as described above and is set to 30 and 300. FIG. 8 shows this state. If there is a data record called data 3 and this is to be read, line number 30 will be assigned to the data record at that time.

In Figures 3 to 8, the table management information includes the entry address for the lowest NUM, the empty entry address (address of the next entry to be used), the highest level entry address, the latest entry address, and the current (deleted) entry address. ) manages level entry addresses and insertion level entry addresses. In FIGS. 3 to 8, each management destination is indicated by an arrow.

〔Effect of the invention〕

As is clear from the above description, according to the present invention, all fields in a record can be used effectively, and when renumbering all records, only a SEQ record is created at the beginning of a module, which is efficient. And history management can be easily performed.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing one embodiment of the present invention;
FIG. 2 is a diagram showing an example of a data structure module according to the present invention, and FIGS. 3 to 8 are diagrams showing examples of table management information and sequence table entry states according to the present invention. 1...Data, 2...Line number management processing section, 3...Processing target data set (GEM library), A...Module, 4...List output, 11...Table management information, 12...Sequence table, 12'...Sequence table table entry.

Claims (1)

[Claims] 1. When configuring a module containing multiple data records on an external storage device, line number control information including an initial value and increment value for each generation is provided at the beginning of the data record, and each line number control information A line number setting method characterized in that a line number corresponding to each generation is determined for subsequent data records based on an initial value and an increment value for each generation.