JPH03141427A - Preparation of information on standard record specifications - Google Patents

Abstract

PURPOSE:To reduce the working manhour by detecting the data items having the same physical relative positions, lengths or attributes in each record out of plural pieces of record defining information as the same data items and preparing the information on the standard record specifications together with other data items. CONSTITUTION:A file serving as an interface between programs and the specifi cation information on a work area record are prepared from the record defining information included in plural programs which refer to the record. In this case, the data items having the same contents of the physical relative positions or lengths in a record are correctly detected among those data items included in plural pieces of record defining information. Based on the information on these detected data items, a standard proper data name or attribute is selected for the preparation of the record specification information. Thus, the greater part of such data names and attributes that are not proper as the standards in those record defining information are not reflected on the prepared record specification information. Therefore the manhour can be reduced for a task where the prepared record specification information is manually corrected.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to improving the productivity of software, and in particular, the present invention relates to the improvement of software productivity, and in particular, to the creation of standard record specification information based on definition information of file records and work records included in existing software. The present invention relates to a standard record specification information creation method suitable for creating a standard record specification information.

[Conventional technology]

Generally, office processing software consists of a large number of programs that use files and work areas as interfaces.

In conventionally created software, the program
Generally, the record definition contents of the same file or work area serving as an interface, that is, the names, attributes, and structures of each data item making up the record of the file or work area are different. Therefore, it is difficult to understand the existing software as a whole, and in particular, to grasp all the programs that are affected by changes in the interface, making maintenance and reuse of the existing software difficult.

To solve this problem, create standard record specification information for files and work area records that serve as interfaces, and develop new programs to modify existing programs and add functions accordingly. The method is valid. Software modified in this way is
Data item names, attributes, and structures in files and work area records that serve as interfaces are unified and standardized between programs, making it easier to understand the software and change and add functions.

However, since file records and work area records that serve as interfaces generally include tens to hundreds of data items, it is not easy to manually create standard record specification information without errors.

Conventionally, the method of supporting the creation of this standard record specification information using a computer is to select one of the multiple programs that refer to each file or work area that serves as an interface, and define the record definition in the program. Extract information and identify the names, attributes, and attributes of the data items included.
There was a method of creating standard record specification information by manually modifying parts of the structure information as necessary. For example, Kitano et al.: "Program Development in rSEA/I - Part 1: Support Functions", Information Processing Society of Japan 34th Gold Country Conference Proceedings <U>, P901-P902, (Showa 62
(March 2013).

[Problem to be solved by the invention]

The above method of extracting and modifying the record specification information of the interface file and work area using one program is suitable for cases where there is no need to manually modify the extracted record specification information, or there is only a small amount of manual modification required. is an effective method.

However, in the above-mentioned conventional technology, if many of the names and attributes of data items defined in the record definition information in the program to be extracted are not appropriate for 411$, the data items in the created record specification information There was a problem in that it required a lot of man-hours to manually correct names and attributes.

Furthermore, in office processing software, there are few programs that refer to all of the large number of data items that make up files and work area records that serve as interfaces, and each program often refers to only some data items. In this case, in a conventionally created program, each or all of the anonymous data items (named F
ILLER data item), and the name, attributes, and structure of the data item are often not defined correctly.

In this case, if the above-mentioned conventional technology is used, the number of steps required to manually add undefined data item information to the record specification information generated by one program is increased, and it is difficult to complete the standard record specification information. There was a problem that the number of man-hours increased.

An object of the present invention is to create record specification information for a file or work area record that serves as an interface between programs from record definition information within a large number of programs that refer to the record, and at this time, to create record specification information for a file or work area record that serves as an interface between programs. The purpose is to reduce the number of man-hours required to manually correct the generated record specification information by selecting appropriate names and attributes as a standard from the names and attributes of items to generate record specification information.

Another object of the present invention is to create record specification information for a file or work area record that serves as an interface between programs from a large number of in-program record definition information that references the record; (Undefined (FILLE)) Portions defined as data items can be supplemented with information such as names and attributes of data items defined in other record definition information to generate record specification information with fewer undefined portions. 4Ill by manually adding undefined data items.
The purpose of this invention is to reduce the number of man-hours required to create standard record specification information.

Another object of the present invention is to provide record definition information extracted from software products such as programs by specifying the names, attributes, etc. of each data item constituting the record in a standard manner registered in advance in data #P. The work of creating standard record specification information by manually modifying the data item names, attributes, etc. in the generated record specification information to the appropriate content by replacing the content with the standard content. The goal is to reduce man-hours.

(Means for solving the ill! problem) In order to achieve the above object, the standard record specification information creation method of the present invention is as follows:
Analyze at least one software product such as a source program or original copy text, and use record definition information of a file or work area described therein.
In a method of generating standard record specification information that defines the name, attributes, and structure of each data item that constitutes a record,
Data items with the same physical relative position and length within the record are detected as the same data item from multiple record definition information describing records with the same or the same contents in the software product, and the same data The feature is that at least one of the items is selected and combined with other data items in the plurality of record definitions to generate standard record specification information.

In addition, when detecting and selecting the same data item from the above-mentioned multiple record definition information and creating standard record specification information that includes data items other than the same data item, anonymous data item names, data items with the name FILLER, , is characterized by generating standard record specification information, excluding other general data items as long as they are in the same physical location.

Another feature is that the data items to be transferred to the standard record specification information from the same data items are automatically selected according to predetermined rules.

Another feature is that the data item to be transferred to the standard record specification information from the same data item is selected by the user.

Another feature is that already created record specification information is used as the software product to be analyzed.

In addition, the standard data item information including the standard name and attributes of the data item is stored in the data # document in advance, and the w semi-data item corresponding to the data item in the record definition information is determined by the name and attribute of the data item. The feature is that information is searched and standard record specification information is created using the searched standard data name or attribute.

The feature is that standard record specification information is created only from the portion of the record definition information obtained by analyzing the software product that includes the data item specified by the user.

In addition, the user specifies the target file, and at least one record containing the record definition information of the target file is selected from the job control parameters or command procedure using this end axis.
A feature of the present invention is that it detects one program, analyzes the program, obtains corresponding record definition information, and generates standard record specification information based on this information.

In addition, by analyzing at least one software product, standard record specification information that defines the name, attribute, and structure of each data item that constitutes a record is generated from the record definition information of the file or work area described therein. In each program that generates and uses the file/work area, the definition location and usage location of the name, attribute, and structure of the data item in the record are listed in the standard record specification information, and the name/attribute of the corresponding standard data item.・It is characterized by converting programs by replacing them with structures.

(Operation) The present invention creates record specification information of a file or work area record that serves as an interface between programs from record definition information within a plurality of programs that refer to the record, and at this time, Correctly detect data items that have the same content based on their physical relative position and length within the record, select appropriate data names and attributes as a standard based on the information of this data item, and generate record specification information. Therefore, many data names and attributes that are not appropriate as a standard in the record definition information will not be reflected in the generated record specification information, so the generated record specification information must be manually corrected to create a data name that is appropriate as a standard.・The man-hours required to create record specifications with attributes can be reduced.

In addition, in the present invention, record specification information of a file or work area record that serves as an interface between programs is created from record definition information within a plurality of programs that refer to the record, and at this time, the same data item from the plurality of record definition information is created. When detecting/selecting or creating standard record specification information that includes data items other than the same data item, a non-foam data item name (i.e., a data item with the name FILLEH) must be located in the same physical location as other general data items. Generate standard record specification information, excluding as much as possible. Accordingly, it is possible to generate record specification information with fewer undefined parts, so it is possible to reduce the number of steps required to manually add undefined data items and create standard record specification information.

Furthermore, the present invention provides record definition information extracted from a software product such as a program, and the corresponding standard data items registered in advance in a data dictionary according to the names and attributes of the data items constituting the record. information is searched and record specification information is generated using the data item names and attributes. Therefore, many of the data item names and attributes in the generated record specification information are appropriate as standard content, so these should be manually corrected to appropriate content to create standard record specification information. Work man-hours can be reduced.

〔Example〕

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a processing procedure in one embodiment of the present invention, and FIG. 2 is a diagram showing the hardware environment of this embodiment.

The standard record specification information creation method of this embodiment will be explained with reference to FIG.

First, the source program name and record name to be processed are entered manually from the input device, the corresponding program stored in the external storage device is analyzed according to the program syntax, and the corresponding record information is stored in memory ( Step 101).

Figures 3 and 4 are examples of record definitions in a source program written in the C0t30L language, and Figure 5 is an example of the storage area inclusion relationship in memory for the record definitions shown in Figures 31g and 4. As an example, in this case, Figures 3 and 4 are record definitions for the same record.

31st fi (F) rA IJ, rB IJ, fc
IJ, rD IJ.

"El" indicates the name of each item that constitutes the record, and rFILL141 (J is a symbol indicating that there is no name. The two-digit number in front of each item name in Figures 3 and 4 (
level number) indicates the inclusion relationship between each item.

For example, [01] includes the data areas of all the items indicated by the following r02J (in the example of FIG. 3, item names "B1", "C1", and "FILLER"). Similarly, "02" is the item named r03 below (in the example in Figure 3, the item name is r03).
It includes all data areas (the items indicated by lJLJ and rEIJ are included in "C1").

The character string rPICJ in Figure 3 defines the type and number of digits of the data to be subsequently placed in the data area of the item1.For example, r99J (301) of the item indicated by the item name rBIJ.
"rx" (aO2) of the item indicated by the item name "El" indicates that the data type is "numeric" and "2 digits", and the data type is "r character" and indicates "1 digit".

The inclusion relationship of the storage area of the record definition shown in Figure 3 is shown in Figure 5.
In FIG. 5, shown at 501 in the figure.

rAIJ, rBIJ, rcIJ, rl)IJ,
rEIJ.

rFi'ILLI: l (J indicates the item name shown in the example in Figure 3. 1 item name [A1] indicates 1 item name.
BIJ, rcIJ, rV ratioLl()IJ indicates that the data area occupied by the item is included; similarly, the item indicated by the item name "C1" has nine item names rDIJ, rEI
The type indicating the view of the data area of each item, which indicates that it includes the data area exclusive to the item indicated by J, is ``9''.
” and “X” for each digit.

Similarly, the inclusion relationship of storage areas in the memory of the record definition shown in FIG. 4 is shown at 502 in FIG.

FIG. 6 shows an example of an analysis result table in which the results of analyzing the record definitions shown in FIGS. 3 and 4 are stored in memory.

For example, the item (303) with item name [A1] shown in Figure 3
is parsed as 1 name rAl, position 1, length 8, type group J (601).Here, 1 position is the starting position of the storage area in memory of the record definition. '', the name indicates the starting position of the area occupied by the item, the length indicates the number of digits of the area occupied by the item, and the type name indicates the name of the specified type, and the type If the type is "9", it is written as a "number", and if the type is rXJ, it is written as an r letter. The type name "group" represents a type name given to an item that has included items.

Based on the analysis result table stored in memory, processing is performed according to the following procedure (see FIG. 1).

At the time when the analysis result table is generated, all item information in the analysis table is subject to processing. If the item to be processed is in the analysis result table (step 1)
02), First, item information with the smallest "position" is detected from the analysis result table (step 103). In the example of FIG. 6, 1 position "1" is the smallest value, and the item information corresponding to this are one name rALJ, rBIJ, rA
2J.

This is each item information indicated by rB21J.

Next, the names of the detected item information are all r FILLERJ
In the case of (name meaning bubble-free) (step 104), it indicates that there is no item with the name at the position of the corresponding area, so the item information with the shortest length among the detected item information is Store at least one item in the name of the detected item information in the memory (step 109)! , l (If a name other than J is found, remove the item information with the name "T°LERJ" from the detected item information. 6 Next, detect the item information with the longest length among the detected item information. In the example of FIG. 6, the item names are rAIJ, rBIJ, rA2J (step 105).

In each item information of rB21J, the order name rA1”.

Since "A2" has the maximum length of [8], the corresponding item information is detected.

Next, if the number of detected item information is one (step 106
), the item information is stored in memory as standard item information (step 108). In the example of FIG. 6, the detected item information has the name rAIJ.

Since there are two items indicated by "A2", one of the plurality of detected item information is stored in the memory as standard item information (step 107 in FIG. 1).

In the example in Figure 6, the name at the top of the analysis result table [
A1" item information is stored in the memory as standard item information.

Next, the detected item information is removed from the processing targets of the analysis result table (step 110). In the 611th example, the item information with names rAIJ and rA2J remained as the detected item information, so the analysis result table is Exclude from processing target.

While there is item information to be processed in the analysis result table,
The above-described standard item information detection and storage are repeated (step 102), and when there is no more item information to be processed, the item information stored in the memory as the standard item information is added with relationship information between items, etc. At step 111), the process is completed.

FIG. 7-a shows an example of standard item information stored in the memory, and FIG. 7-b shows an example of standard record definition information edited and output to an output device (in COBOL language format).

701 shown in FIG. 7 is the data area added in the editing output step (step 111) because the item indicated by the item name rk31J and the item indicated by the 5-item name rB21J share a data area that starts at the same position. This is an item definition that means sharing.

Since the area length shared by the data areas is two digits, which is the length of the item indicated by one name "B1", the level number indicating the same group as the name r821J is set for items up to the item indicated by one name "B22J".

The item information indicated by the name "Dl" and rD2J shown in Fig. 6 also have the same position and length, but since the type name of the item information indicated by the name "D2" is "character", they are called [group]. Taking advantage of the fact that they can be treated equally, the item definition 702 shown in Figure 7 -
For example, the type name is "Group J", and the same output is performed, and the item definition that means sharing the data area mentioned above is not output.

According to this embodiment, the item name of each record definition defined in multiple programs that use the same file or file of the same format, especially the item name of each item definition having the same position and length, can be Standard record specification information can be easily obtained because the number of non-negative item definitions (item name rFILLBIRJ) can be reduced as much as possible.

In addition, in step 107 of FIG. 1, by specifying the priority order in advance when specifying the record definition to be processed, the item name of the record definition with the highest priority among the multiple item names can be set as the standard item. It can also be a name, allowing for standardization that includes the user's intentions.

FIG. 8 is a flowchart of a standard record specification information creation method showing a second embodiment of the present invention.

The difference from the first embodiment is that a new step 1101 has been added in which the user inputs and selects from the dialog screen when there are multiple candidates for the standard data item.

The user can select a standard name from among the names of the corresponding data using the dialog screen.

FIG. 9 shows an example of an interaction screen in which candidate data items are displayed in step 1101 and the user selects them.
In Fig. 9, data “2”, that is, record “A2” data “
"E2" is selected.

The tenth is a flowchart of a standard record specification information creation method showing the third embodiment of the present invention.

The difference from the first embodiment is the program analysis step 101.
After analyzing the source program input in step 1301, the user can specify a portion of the record to be standardized through interactive processing on the interactive screen illustrated in FIG. 11. This allows a set of data items that are part of a record to be standardized.

FIG. 12 is the same as FIG. 11, and shows an example of the editing output result when the third to fifth lines of record 1 and the fourth to fifth lines of record 2 are targeted for creation of standard record specification information.

FIG. 13 is a flowchart of a standard record specification information creation method showing a fourth embodiment of the present invention.

The difference from the first embodiment is that after detecting the item with the maximum "length" in step 105, the corresponding standard data is searched from the data dictionary in step 1602, even when there is only one detected item. However, if a standard data item corresponding to the item is detected, information on the standard data item is stored.

Fig. 14 shows an example of the data dictionary of this embodiment, and it is possible to determine whether one of the items matches one of the names of "standard data name" or "variation of data name". If it exists, the "Standard Data Name" in that column is memorized in step 1605, and if it does not match, another one of the items is checked in the same way.If all the items are "Standard Data Name" If the item does not match any of the names of ``name'' and ``variation of data name,'' one of the multiple items is selected and stored in step 107, as in the first embodiment. In this case, an interactive selection method is also possible. In addition, when using a data dictionary in which "r data name variation" is not registered, as in the case of numbers 8 and 9 in Figure 14, the data item name in the existing record definition is changed to "standard data name variation" in the data dictionary. There is also a method of adopting this standard data name only if it matches the "name".

FIG. 15 is a flowchart of a standard record specification information creation method showing a fifth embodiment of the present invention.

This is step 101 of manually analyzing a source program.
Step 18 of manually analyzing the record specification information instead of
This embodiment differs from the first embodiment in that it has 01. According to this embodiment, multiple pieces of record specification information created for the same file or work area can be integrated to create standard record specification information. .

FIG. 16 shows a diagram of the processing procedure of the sixth embodiment of the present invention. In the embodiment shown in FIG. 1, the user is supposed to instruct the program to be processed, and the user You need to find a program that has record definitions for the files you want to standardize in advance.

In this embodiment, the execution order of the program and the files to be used are described in the embodiment shown in Fig. 1, and the language (job control parameters or command procedure) for automatic operation of the program is written. step (1901
) was added. The embodiment is substantially the same as the embodiment shown in FIG. 1 except for the added steps.

FIG. 17 shows an example of a job flow. In the example in Figure 17, the program names rut(iTRNIJ, rtll(i
Instructs the KEIIJ programs to be executed in sequence.

2001 is a line instructing execution of a program with the program name rut(iT)INIJ, and lines 2002 and 2003 instruct files to be used for executing the program. 2002 is the file entity name rTRANS
This shows a line instructing to use the IJ file within the program as the logical file name rTRNIJ.

In step 1901 in FIG. 16, the job flow is
The name of the program that parses and uses the file entity with the file name specified by the user.

Then, the logical file name assigned to the file within the program is detected and stored in memory.

In the example in Figure 17, for the file entity name rURIAGE I J specified by the user, lines 2003 and 200
5 instructions use the same file with the file entity name rllRiAGEI J, and the program name is rtlB.
IT) INIJ (2001) and logical file name r
URI IJ (2003), and program name URIKEilJ (2004), 41m logic 77 ILI name URIAG14J (2005)
) are stored in memory.

In step 1902 of FIG. 16, step 1 of FIG.
Instead of inputting the program name and record definition name in step 01, the corresponding program and record definition are analyzed from the program name and logical file name stored in the memory. The record definition name can be detected from the record definition name subordinate to the file definition indicated by the logical file name.

Thereafter, standard record specification information can be created using the same processing procedure as in the embodiment shown in FIG.

According to this embodiment, the program to be processed can be detected by specifying the file entity name, and the program included in the job flow to be analyzed can be detected, which has the effect of eliminating omissions.

In addition, program names that use the same file (= the file entity name is the same in the job flow description) are detected from the analyzed job flow, and the program name and logical file name are grouped together for each file entity name and stored in memory. However, by performing the same processing procedure as in the example shown in Figure 1 for each file entity name, it can be used commonly among programs included in the analyzed job flow without the user specifying the file entity name. All of the record definitions for the files that are created can be standardized.

FIG. 18 shows the processing procedure of the seventh embodiment of the present invention.The embodiment shown in FIG. be.

In this embodiment, in addition to the embodiment shown in the first part, a step is added to convert the item names in each program from which data is taken out to the item names of the standard record specifications based on the standard record specification information. Other than the added steps, this embodiment is the same as the embodiment shown in FIG.

That is, steps 2101 and 2102°2 in FIG.
103 is a step added to the embodiment shown in FIG. In step 101, the input analyzed program is sequentially processed.
As a target (step 2101), convert the item name in the program to the item name of the standard record specification (step 2102), and output the program after converting the item name to the output position M (step 2103), which are repeated (step 2101). ).

The method of converting the item name in the program in step 2102 is to match the name of each item in the target program of the analysis result table stored in memory with the r position J and r length J of the item in the standard record specification information. There is a method to store in memory a table that associates the names of items with "position" and "length", and convert the corresponding item to the item name in the corresponding standard record specification information, or to convert it to the item name in the standard record specification information. This is done using existing methods such as creating a correspondence between the entire record definition and the standardized record specification information based on the relative starting position and length of the area in memory occupied by each item, and converting the corresponding item name.

According to this embodiment, for at least one program that retrieves standard record specification information, the corresponding record definition is converted to a record definition having standard record specification information, and the item names used in the procedure part of the program are can also be converted into item names of standard record specification information, which has the effect of automating item name conversion that occurs when a program uses standard record specification information.

〔Effect of the invention〕

Since the present invention includes the processing procedure described above, it has the effects described below.

At least one software product such as a source program or original copy text is analyzed, and the physical relative position and length within the record are determined from multiple record definition information for files or work areas that are the same or have the same content. Detect matching data items as the same data item, select at least one of the same data items, and select each data item that makes up the record together with other data items in the multiple record definitions. name·
1 because it generates record specification information that defines attributes and structure.
It is possible to generate standard record specification information including appropriate data item names, attributes, etc., which requires less manual correction work.

In addition, when detecting and selecting the same data item from the above-mentioned multiple record definition information and creating standard record specification information that includes data items other than the same data item, anonymous data item information Item - is excluded as long as other general data items are in the same physical location, and standard record specification information is generated, reducing the amount of work required to add undefined data item information by one manual operation. , can generate standard record specification information.

In addition, since the selection of data items to be transferred to the standard record specification information from the same data items mentioned above is automatically performed according to established rules, the amount of manual correction work can be reduced and appropriate data can be used as a standard. Standard record specification information including item names, attributes, etc. can be generated.

In addition, since the selection of the data items to be transferred to the standard record specification information from the same data items mentioned above is done by the user's specification, the amount of manual correction work can be reduced.
Standard record specification information including appropriate data item names, attributes, etc. can be generated as a standard.

In addition, by using already created record specification information as the software product to be analyzed above, the standard record specification that includes data item names, attributes, etc. that are appropriate as a standard can reduce the amount of manual correction work. Information can be generated.

In addition, standard data item information including the standard name and attributes of the data item is stored in a data dictionary in advance, and for each data item in the record definition axis, the corresponding standard data item information is stored according to the name and attribute of the data item. By searching for and creating standard record specification information using the searched standard data names or attributes, it is possible to reduce the amount of manual correction work and include data item names, attributes, etc. that are appropriate as a standard. Standard record specification information can be generated.

In addition, by creating standard record specification information only from the portion of the record definition information obtained by analyzing software products that includes data items specified by the user, the standard It is possible to generate standard record specification information including appropriate data item names, attributes, etc.

In addition, the user specifies the target file, and this information allows the user to specify at least one file containing the record definition report of the target file from the job control parameters or command procedure.
By detecting one program, analyzing that program to obtain the corresponding record definition information, and generating standard record specification information based on this, the amount of manual correction work from multiple record definition information can be reduced. , standard record specification information including appropriate data item names, attributes, etc. can be generated.

In addition, by analyzing at least one software product, standard record specification information that defines the name, attribute, and structure of each data item that constitutes a record is generated from the record definition information of the file or work area described therein. The corresponding standard data item name and usage location of the name, attribute, and structure of the data order in the record in each ProGuerra 11 that generates and uses the file/work area are specified in the standard record specification information. By converting the program by replacing it with attributes and structures, it is possible to efficiently standardize and unify data items in already developed software.

As described above, the present invention streamlines the creation of standard record specification information and the standardization and unification of data items in already developed software using it, which in turn leads to the maintenance and reuse of already developed software. This has excellent effects such as making work more efficient.

[Brief explanation of the drawing]

FIG. 1 is a processing procedure diagram in an embodiment of the present invention, FIG. 2 is a diagram showing a hardware environment in which the present invention is implemented, and FIG.
4 and 4 are exemplary diagrams of record definitions in the source program to be processed, FIG. Example diagram of record definition analysis result table, No. 7
The figure shows an example of the standard data item information in the memory and the generated standard record specification information, Figure 8 is a processing procedure diagram in the embodiment of the cylinder 2 of the present invention, and Figure 9 shows the selection of standard data items in this embodiment. 10 is a processing procedure diagram in the third embodiment of the present invention. FIG. 11 is an example of a dialog screen for specifying the standardization target range of this embodiment. An illustrative diagram of the standard record specification information generated in the example, FIG. 13 is a processing procedure diagram in the fourth embodiment of the present invention, and FIG. 14 is a diagram showing a data dictionary used in this embodiment,
FIG. 15 is a processing procedure diagram in the fifth embodiment of the present invention,
FIG. 16 is a processing procedure diagram of the sixth embodiment of the present invention, and FIG.
The figure shows a description example of a job flow used in this embodiment, and FIG. 18 is a diagram showing a processing procedure in a seventh embodiment of the present invention. 101...Program input analysis step, 102...
・Target item presence/absence determination step, 103...Position minimum item detection step, 104...All applicable items 1'ILLf:
R determination step, 105...Maximum length item detection step, 106...Number of items 1 determination step, 107...
Item selection storage step, 108... Item storage step, 109... Length minimum do ratio L14) 1 item storage step, 110... Detected item target exclusion step, 111
...Memory item editing output step, 301...Numeric data type, 302...Character data type, 303...Data item, 501-502...Memory step inclusion relationship, 60
1...Analysis data item information, 701...Data area shared data item, 702...Group type data item, 11
01...Standard data item selection specification step, 1102
...Specified item storage step, 1301...Target data item specification step, 1602...Data dictionary input step, 1603...Standard data matching determination step,
1605...Applicable standard data storage step, 1801
... Record specification information input analysis step, 1901.
. . . Job flow human power analysis step, 1902 . . . Program input analysis step, 2001 . . . Program execution specification line. 2002-2003...Use file specification line, 200
4...Program execution specification line, 2005-2007.
. . . Use file specification line, 2101 . . . Target program existence determination step, 2102 . . . Item name conversion step in the program, 2103 . . . Target program output step. /1... Figure 4 Figure 5 Figure 2 Figure 3 Figure 9 Figure 12 Figure 14

Claims (1)

[Claims] 1. Analyzing at least one software product,
In a standard record specification information creation method that generates standard record specification information that defines the name, attribute, and structure of each data item constituting a record from record definition information of a file or work area described therein, the software From multiple record definition information describing records with the same or the same content within a product, identify data items that have the same physical relative position within the record, or in addition to this, length, or attributes that match. Detected as a data item, at least one from the same data item
A method for creating standard record specification information, characterized in that one is selected and combined with other data items in the plurality of record definitions to generate standard record specification information. 2. When detecting and selecting the same data item from the above multiple record definition information or creating standard record specification information that includes data items other than the same data item, anonymous data items - that is, data items with the name FILLER - are , generating standard record specification information while excluding other general data items as long as they are in the same physical location.
Standard record specification information creation method described. 3. Standard record specification information creation according to claims 1 and 2, characterized in that the selection of data items to be transferred to the standard record specification information from the same data items is automatically performed according to predetermined rules. Method. 4. The method for creating standard record specification information according to claims 1 and 2, characterized in that the data item to be transferred to the standard record specification information from the same data item is selected by a user's designation. 5. Claims 1 and 2, characterized in that the software product to be analyzed for the station is already created record specification information.
Standard record specification information creation method described in 3 and 4. 6. Analyzing at least one software product,
A standard record specification information creation method that generates standard record specification information that defines the name, attribute, and structure of each data item constituting a record from record definition information of a file or work area described therein, and claims. 1
In the standard record specification information creation method described in , 2, 3, 4, and 5, standard data item information including standard names and attributes of data items is stored in a data dictionary in advance, and for data items in the record definition information, A standard record specification information creation method characterized by searching for corresponding standard data item information based on the name or attribute of the data item, and creating standard record specification information using the searched standard data name or attribute. . 7. Analyzing at least one software product,
A standard record specification information creation method that generates standard record specification information that defines the name, attribute, and structure of each data item constituting a record from record definition information of a file or work area described therein, and claims. 1
In the standard record specification information creation method described in , 2, 3, 4, 5, and 6, standard record specification information is created from only the part of the record definition information obtained by analyzing the software product that includes the data item specified by the user. A standard record specification information creation method characterized by creating record specification information. 8. Analyzing at least one software product,
A standard record specification information creation method that generates standard record specification information that defines the name, attribute, and structure of each data item constituting a record from record definition information of a file or work area described therein, and claims. 1
In the standard record specification information creation methods described in , 2, 3, 4, 5, 6, and 7, the user specifies the target file and uses this information to create the record definition information of the target file from the job control parameter or command procedure. 1. A method for creating standard record specification information, comprising: detecting at least one program that includes the program, analyzing the program to obtain corresponding record definition information, and creating standard record specification information based on the obtained record definition information. 9. Analyzing at least one software product,
A standard record specification information creation method that generates standard record specification information that defines the name, attribute, and structure of each data item constituting a record from record definition information of a file or work area described therein, and claims. 1
, create standard record specification information using the standard record specification information creation method described in 2, 3, 4, 5, 6, 7, and 8;
In each program that uses the file/work area, define and use the name, attribute, and structure of the data item in the record to the name, attribute, and structure of the corresponding standard data item described in the standard record specification information. A program conversion method characterized by replacement.