JP2022156575A - Analysis program, analysis method, and information processing apparatus - Google Patents

Abstract

To facilitate recognition of operation specifications at the time of executing a program.SOLUTION: An information processing apparatus 10 stores therein a source file 1a and specification definition information defining operation specifications of a programming language used for description of an analysis object program in the source file 1a. The information processing apparatus 10 decodes operation specifications of code in each of lines described in the source file 1a on the basis of the specification definition information. Then, the information processing apparatus 10 generates specification information in which comment statements representing operation specifications of code described in each of a plurality of lines are described in association with each of the plurality of lines in the source file 1a.SELECTED DRAWING: Figure 1

Description

The present invention relates to an analysis program, an analysis method, and an information processing apparatus.

The execution environment of software such as application software (hereinafter referred to as application) may be changed due to the migration of the platform for executing the software or the change of the processing system. For example, the following platform migrations or processing system changes are possible.
・Migration from a host to a so-called open OS (Operating System) ・Migration to another OS within an open OS ・Migration from a 32-bit version to a 64-bit version in the same OS ・Version in the same OS Changes in the processing system of software created in up/high-level languages (for example, changes in the vendor that provides the compiler)
When the execution environment of software is changed, the change in behavior of the software due to the change often poses a problem. For example, in the case of a program that handles pointers to memory areas, the size of the pointers differs when moving from 32-bit to 64-bit. For this reason, when software that includes processing that uses the pointer size of 32 bits is migrated to a 64-bit version OS, the operation will continue even if there is no change in resources such as source files. Be changed. These platform migration-related specification differences are information that does not directly appear in asset documents such as the source files of the software to be migrated.

Prior confirmation of the feasibility of platform migration is carried out at the time of platform migration. For example, an assessment is performed manually to exhaustively identify incompatibilities between platforms that execute software assets.

As a technique for assisting in grasping the contents of a program, for example, a specification generation device capable of generating flexible specifications based on an input program has been proposed.

JP 2010-176553 A

Since there are parts where the operation specifications at the time of program execution do not appear in the asset statements such as the source files, it is difficult to accurately grasp the operation specifications of the program after compilation only from the source files. Therefore, for example, even if the assessment is performed when the execution environment of the software is changed, it is easy to fail to extract actions that are changed according to the change of the execution environment, resulting in a lack of accuracy. Moreover, even when the operation is changed by changing the source file of the software, it is difficult to accurately grasp the changed part of the operation.

In one aspect, the present invention aims at facilitating understanding of operation specifications during program execution.

In one proposal, an analysis program is provided that causes a computer to perform the following processes.
The computer decodes the operation specifications of the code written in the source file for each line based on the specification definition information that defines the operation specifications of the programming language used to describe the program to be analyzed in the source file. Then, the computer generates specification information in which comment statements indicating operation specifications of the code described in each of the plurality of lines are described in association with each of the plurality of lines in the source file.

According to the first aspect, it becomes easy to grasp the operation specifications during program execution.

It is a figure which shows an example of the analysis method which concerns on 1st Embodiment. It is a figure which shows an example of the whole system configuration|structure including the system before and after migration. FIG. 3 is a diagram illustrating an example of hardware of a management terminal; FIG. FIG. 4 is a block diagram showing functions of a management terminal for automatic assessment of applications; FIG. 10 is a diagram illustrating an example of an application assessment process associated with platform migration; FIG. 10 is a diagram illustrating a first generation example of specification information; FIG. 10 is a diagram illustrating a second generation example of specification information; FIG. 12 is a diagram illustrating a third generation example of specification information; FIG. 13 is a diagram showing a fourth generation example of specification information; FIG. 12 is a diagram showing a fifth generation example of specification information; It is a figure which shows an example of an assessment in the case of changing a compiler. FIG. 10 is a diagram showing an output example of specifications of a portion of a control structure; It is a figure which shows an example of the specification difference extraction of the callee of a subroutine. It is a figure which shows an example of specification difference extraction which suppressed error propagation. FIG. 10 is a diagram showing an example of specification difference extraction by referring to operating parameters; FIG. 10 is a diagram showing an example of specification difference extraction when different operation setting files exist for each system; 8 is a flowchart illustrating an example of a procedure of specification information generation processing; 9 is a flowchart showing an example of the procedure of external information analysis processing; FIG. 10 is a diagram showing an example of a system usage environment variable list table; FIG. It is a figure which shows an example of an environment variable list table. It is a figure which shows an example of a runtime option table. FIG. 11 is a diagram showing an example of an operation setting table; FIG. FIG. 10 is a diagram illustrating an example of data registration processing from an environment variable list to an environment variable list table; FIG. 10 illustrates an example of data registration processing from an operation setting file to an operation setting table; 9 is a flowchart showing an example of the procedure of source file analysis processing; It is a figure which shows an example of a variable list table. FIG. 11 is a diagram showing an output example of a difference report;

Hereinafter, this embodiment will be described with reference to the drawings. It should be noted that each embodiment can be implemented by combining a plurality of embodiments within a consistent range.
[First embodiment]
First, the first embodiment will be explained.

FIG. 1 is a diagram showing an example of an analysis method according to the first embodiment. FIG. 1 shows an information processing device 10 for realizing the analysis method. The information processing apparatus 10 can implement the analysis method according to the first embodiment by executing a predetermined analysis program, for example.

The information processing device 10 is a computer having a storage unit 11 and a processing unit 12, for example. The storage unit 11 is, for example, a memory or a storage device that the information processing device 10 has. The processing unit 12 is, for example, a processor or an arithmetic circuit included in the information processing device 10 .

The storage unit 11 stores software assets 1 , first specification definition information 2 , and second specification definition information 3 . The software asset 1 includes a software source file 1a and external information 1b indicating information to be referred to when executing the analysis target program described in the source file 1a. The first specification definition information 2 is information defining operation specifications of a programming language describing the analysis target program when the analysis target program is executed by the first system. The second specification definition information 3 is information defining operation specifications of a programming language describing the analysis target program when the analysis target program is executed by the second system. The first system and the second system are systems having different platforms such as OSs.

Based on the first specification definition information 2 or the second specification definition information 3, the processing unit 12 decodes the operation specifications of the code for each line described in the source file 1a. Then, the processing unit 12 generates specification information in which comment statements indicating operation specifications of the code described in each of the plurality of lines are described in association with each of the plurality of lines in the source file 1a. For example, the processing unit 12 decodes the operation specifications of the code for each line described in the source file 1a based on the first specification definition information 2, and writes a comment statement indicating the operation specifications based on the first specification definition information 2. The first specification information 4 is generated. Based on the second specification definition information 3, the processing unit 12 decodes the operation specifications of the code for each line described in the source file 1a, and writes comment statements indicating the operation specifications based on the second specification definition information 3. second specification information 5 is generated.

Since the first specification information 4 describes the comment text indicating the operation specification based on the first specification definition information 2, referring to the first specification information 4, it is possible to understand the behavior of the program to be analyzed when it is executed by the first system. Operation specifications can be easily grasped. In addition, since the second specification information 5 contains a comment that indicates the operation specification based on the second specification definition information 3, if the second specification information 5 is referred to, the analysis target program will be executed by the second system. operation specifications can be easily grasped.

For example, when a program to be analyzed that is being executed in the first system is transferred to the second program, by comparing the first specification information 4 and the second specification information 5, it is possible to change the operation specifications accompanying the migration of the system to be executed. The point can be easily detected. In that case, the processing unit 12 may extract the difference between the first specification information 4 and the second specification information 5 and generate the specification difference information 6 indicating the extracted difference. The specification difference information 6 describes without omission the changes in the operation specification accompanying the migration of the system that executes the program to be analyzed. As a result, omission of extracting changed portions of operation specifications is suppressed.

Note that the processing unit 12 may output the difference report 7 based on the specification difference information 6 . The difference report 7 visualizes the changes in the operation specifications in an easy-to-understand manner for the user. This makes it easier for the user to grasp the changed parts of the operation specifications.

When decoding the code specifications, the processing unit 12 refers to the external information 1b describing the operation according to the external information 1b, which indicates the information to be referred to when executing the program to be analyzed. You can also decipher what happens when you run your code. In this case, the processing unit 12 inserts a comment text indicating an operation corresponding to the external information 1b based on the external information reference code into the first specification information 4 or the second specification in association with the line in which the external information reference code is described. Described in Information 5.

A comment text indicating the operation specification corresponding to the external information 1b is written in the first specification information 4 or the second specification information 5, so that the operation specification that does not appear in the text of the source file 1a is written in the first specification information 4 or the second specification information 5. It is shown in the second specification information 5 . Therefore, based on the first specification information 4 or the second specification information 5, it is possible to accurately grasp the behavior of the program to be analyzed during execution.

Further, the processing unit 12 outputs a correction proposal for migrating the analysis target program executed in the first system to the second system based on the difference between the first specification information 4 and the second specification information 5. good too. For example, the processing unit 12 holds correction proposals for eliminating the errors in association with the types of errors during operation that are found by decoding the code specifications. Then, if the second specification information 5 indicates that an operation error will occur, the processing unit 12 outputs a correction proposal for the source file 1a to prevent the error according to the type of the error. This makes it easy to modify the source file 1a in accordance with the migration of the system that executes the program to be analyzed.

Further, the processing unit 12 decodes the operation specifications of the code for each line described in the post-change source file in which the source file 1a is changed, based on the first specification definition information 2 or the second specification definition information 3. can also In this case, the processing unit 12 generates post-change specification information in which comment statements indicating operation specifications of the code described in each of the plurality of lines are described in association with each of the plurality of lines in the post-change source file. . Then, the processing unit 12 extracts the difference between the specification information and the post-change specification information. As a result, it is possible to accurately grasp the change in the operation specification during the execution of the analysis target program due to the change in the source file 1a.

[Second embodiment]
Next, a second embodiment will be described.
FIG. 2 is a diagram showing an example of an overall system configuration including systems before and after migration. In the example of FIG. 2 , a plurality of systems 200 and 300 and a management terminal 100 are connected via a network 20 . Systems 200 and 300 are computers that run applications. It is assumed that the system 200 and the system 300 are built on different platforms. For example, the system 300 operates with an OS different from that of the system 200 . The management terminal 100 is a computer used for operation management of the systems 200 and 300 .

FIG. 3 is a diagram illustrating an example of hardware of a management terminal; The management terminal 100 is entirely controlled by a processor 101 . A memory 102 and a plurality of peripheral devices are connected to the processor 101 via a bus 109 . Processor 101 may be a multiprocessor. The processor 101 is, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit), or DSP (Digital Signal Processor). At least part of the functions realized by the processor 101 executing the program may be realized by an electronic circuit such as an ASIC (Application Specific Integrated Circuit) or a PLD (Programmable Logic Device).

A memory 102 is used as a main storage device of the management terminal 100 . The memory 102 temporarily stores at least part of an OS program and application programs to be executed by the processor 101 . In addition, the memory 102 stores various data used for processing by the processor 101 . As the memory 102, for example, a volatile semiconductor memory device such as a RAM (Random Access Memory) is used.

Peripheral devices connected to the bus 109 include a storage device 103 , a GPU (Graphics Processing Unit) 104 , an input interface 105 , an optical drive device 106 , a device connection interface 107 and a network interface 108 .

The storage device 103 electrically or magnetically writes data to and reads data from a built-in recording medium. The storage device 103 is used as an auxiliary storage device for the computer. The storage device 103 stores an OS program, application programs, and various data. As the storage device 103, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive) can be used.

The GPU 104 is an arithmetic unit that performs image processing, and is also called a graphic controller. A monitor 21 is connected to the GPU 104 . The GPU 104 displays an image on the screen of the monitor 21 according to instructions from the processor 101 . Examples of the monitor 21 include a display device using an organic EL (Electro Luminescence), a liquid crystal display device, and the like.

A keyboard 22 and a mouse 23 are connected to the input interface 105 . The input interface 105 transmits signals sent from the keyboard 22 and mouse 23 to the processor 101 . Note that the mouse 23 is an example of a pointing device, and other pointing devices can also be used. Other pointing devices include touch panels, tablets, touchpads, trackballs, and the like.

The optical drive device 106 reads data recorded on the optical disc 24 or writes data on the optical disc 24 using laser light or the like. The optical disc 24 is a portable recording medium on which data is recorded so as to be readable by light reflection. The optical disc 24 includes DVD (Digital Versatile Disc), DVD-RAM, CD-ROM (Compact Disc Read Only Memory), CD-R (Recordable)/RW (ReWritable), and the like.

The device connection interface 107 is a communication interface for connecting peripheral devices to the management terminal 100 . For example, the device connection interface 107 can be connected to the memory device 25 and the memory reader/writer 26 . The memory device 25 is a recording medium equipped with a communication function with the device connection interface 107 . The memory reader/writer 26 is a device that writes data to the memory card 27 or reads data from the memory card 27 . The memory card 27 is a card-type recording medium.

Network interface 108 is connected to network 20 . Network interface 108 transmits and receives data to and from other computers or communication devices via network 20 . The network interface 108 is a wired communication interface that is connected by a cable to a wired communication device such as a switch or router. Also, the network interface 108 may be a wireless communication interface that communicates with a wireless communication device such as a base station or an access point via radio waves.

The management terminal 100 can implement the processing functions of the second embodiment with the above hardware. Systems 200 and 300 can also be realized by hardware similar to management terminal 100 . Also, the information processing apparatus 10 shown in the first embodiment can be realized by hardware similar to that of the management terminal 100 .

The management terminal 100 implements the processing functions of the second embodiment by executing a program recorded in a computer-readable recording medium, for example. A program describing the processing content to be executed by the management terminal 100 can be recorded in various recording media. For example, a program to be executed by the management terminal 100 can be stored in the storage device 103 . The processor 101 loads at least part of the program in the storage device 103 into the memory 102 and executes the program. The program to be executed by the management terminal 100 can also be recorded in a portable recording medium such as the optical disk 24, memory device 25, memory card 27, or the like. A program stored in a portable recording medium can be executed after being installed in the storage device 103 under the control of the processor 101, for example. Alternatively, the processor 101 can read and execute the program directly from the portable recording medium.

In the system as described above, there is a case where an application running on one of the systems 200 and 300 is migrated to the other system. In this case, the system administrator uses the management terminal 100 to identify (assess) portions whose operations are changed due to the migration of the execution environment of the application. The management terminal 100 can automatically assess applications and output differences in operations according to differences in execution environments.

Here, the difficulty of assessment during platform migration of applications will be explained.
As one means of assessment, it is conceivable to use a compiler to analyze the syntax of assets to be migrated, and to extract system-based syntax errors after migration. However, since compilers are not designed to extract specification differences, there is no guarantee that all specification differences can be extracted by using a compiler to parse the assets to be migrated (problem 1).

As a case where the specification difference cannot be extracted, there is a case where an error at a certain location causes failure in judgment of subsequent code (Problem 2). For example, a data definition error will result in an error in syntax checking for the entire statement that uses that data. In that case, it may not be possible to check the specification difference of the sentence itself.

Also, if a compiler is used, only specifications that are known at the time of compilation can be checked (problem 3). For example, in a case where operation is changed by specifying parameters during operation, it is not possible to correctly determine the difference in operation before and after migration.

As another means of assessment, it is conceivable to identify in advance the specification differences between the pre-migration system and the post-migration system, and create a tool for extracting the specification differences that correspond to customer assets. In this case, differences in specifications are identified for each combination of systems before migration and systems after migration, and the number of combinations becomes enormous as the number of target systems increases (Problem 4).

Therefore, in the management terminal 100 according to the second embodiment, instead of displaying a warning for incompatible program elements like the existing check tools, for all program elements in the source file, The detailed specifications are output as comments. That is, the management terminal 100 outputs a comment text indicating that an error will occur, but does not skip subsequent processing due to error handling. The specifications output by the management terminal 100 include specifications that cannot be seen from the notation of the source file (execution platform dependent, processing system dependent, translation parameter dependent, and execution environment information dependent specifications).

In this way, the management terminal 100 does not detect "incompatibility in the specification definition in migration from platform A to platform B", but rather "operation specifications on platform A" and "platform B Operation specification on the above" is output. Operational specifications during program execution include specifications that do not appear in source files. The management terminal 100 then compares operation specifications according to different platforms. As a result, a wide variety of migration patterns for individual applications can be supported simply by implementing specification information output for each platform of the migration source and migration destination. That is, as follows, each of the above problems can be solved.

As for problem 1 (completeness of specification difference extraction), omission of specification difference detection is prevented by mechanically writing operation specifications related to source code before and after migration. As for problem 2 (prevention of error propagation), the loss of information due to error propagation can be prevented by using multiple lines for specification comments. As for problem 3 (reflection of parameters during operation), by using the operation environment setting file as an input for asset analysis, the parameters during operation can be reflected in the comparison target. As for problem 4 (prevention of increase in combination patterns), analysis patterns are reduced because the specification difference for each combination is not taken into consideration and only the system specifications are focused. In other words, when analyzing each combination of platforms, a total of _n C ₂ comparisons are required to compare n systems (n is an integer of 2 or more), but the operation of each system executing software is If it is the output of the comment text of the specification, only n ways should be considered.

FIG. 4 is a block diagram showing the functions of the management terminal for automatic assessment of applications. The management terminal 100 has a storage unit 110 , a specification information output unit 120 , a difference extraction unit 130 , a difference report output unit 140 and a correction method proposal unit 150 .

The storage unit 110 stores migration target assets 31, 32, . . . , specification definition information 41, 42, . Migration target assets 31 , 32 , . . . are software assets of applications executed by the system 200 . For example, one migration target asset 31 includes a source file 31a and external information 31b. The source file 31a is a file in which the source code of the program (analysis target program) in a high-level language is described. The external information 31b is information that is referenced when an executable file generated by compiling the source file 31a is executed.

The specification definition information 41, 42, . The specification definition information 41, 42, . . . are provided for each platform on which the compiled application is executed.

The correction rules 51, 52, .
The specification information output unit 120 generates specification information indicating detailed specifications for each line of the source code for each of the migration target assets 31, 32, . For example, the specification information output unit 120 generates specification information in which the specification of operation after compilation is written for each line in the source file.

The difference extraction unit 130 extracts the difference between two pieces of specification information. For example, the difference extraction unit 130 uses the specification information of the migration target asset generated using the specification definition information 41 corresponding to the system 200 before migration and the specification definition information 42 corresponding to the system 300 after migration. Extract the difference from the specification information of the same migration target asset.

The difference report output unit 140 generates a difference report indicating the difference between the two pieces of specification information and outputs it to the file or monitor 21 .
The correction method proposing unit 150 outputs a proposal message proposing a difference correction method according to the correction rules 51, 52, .

With the functions described above, the management terminal 100 can automatically perform an assessment when migrating a platform for executing an application. Note that the function of each element shown in FIG. 4 can be realized, for example, by causing a computer to execute a program module corresponding to the element.

Note that part of the specification information output function of the specification information output unit 120 can be diverted from the function of a compiler for compiling source files. For example, the compiler performs lexical interpretation, syntactic interpretation, and semantic interpretation of the source file 31a, and generates appropriate machine language code according to these interpretation results. The specification information output unit 120 performs lexical interpretation, syntactic interpretation, and semantic interpretation of the source file 31a like a compiler. However, unlike a compiler, the specification information output unit 120 does not generate a machine language code, but generates comment statements indicating interpretation results for each line.

In the specification definition information 41, 42, . . . , specifications of lexical interpretation, syntactic interpretation, and semantic interpretation in the compiler are defined, and comment sentences are defined instead of internal codes representing interpreted contents. The specification information output unit 120 analyzes the operation specification of the source file 31a based on the specification definition information 41, 42, . do. Then, the specification information output unit 120 creates a copy of the source file 31a and adds a comment statement indicating the operation specification for each line of the program to the copy to create specification information.

A normal compiler holds specification information internally, generates code based on it, and does not disclose specification information to the outside. For the compiler, the specification information is for outputting object code, and there is no need or significance to output it itself. Also, for the same reason, we don't care about various information such as runtime environment variables that aren't finalized until runtime.

On the other hand, the specification information output unit 120 formalizes specification information and outputs it, and for this purpose, the mechanism of the compiler is partly diverted to visualize the operation specification for each statement. As a result, for example, it is possible to precisely and thoroughly investigate whether or not there is incompatibility before and after system migration. In other words, the specification information output unit 120 uses comment statements to clarify the operation during execution, which the compiler has not been aware of. Moreover, the specification information output unit 120 can also output run-time operation specifications dependent on external information such as operation setting files, which are not handled as inputs by the compiler.

Inputs for causing the management terminal 100 to automatically execute automatic assessment at the time of platform migration include, for example, a source file, execution platform type, processing system type (which vendor prepared the processing system), translation parameters, and application execution environment. Information. The output obtained as a result of executing the automatic assessment is, for example, information describing detailed specifications for each program element (each line of code) described in the source file in a predetermined format.

FIG. 5 is a diagram illustrating an example of application assessment processing associated with platform migration. For example, assume that an application corresponding to the migration target assets 31 is migrated from the system 200 to the system 300 . Specifications corresponding to the platform of system 200 are shown in specification definition information 41 . Specifications corresponding to the platform of system 300 are shown in specification definition information 42 .

The specification information output unit 120 generates the specification information 61 of the migration target asset 31 based on the source file 31 a , the external information 31 b and the specification definition information 41 of the migration target asset 31 . The specification information output unit 120 also generates the specification information 62 of the migration target asset 31 based on the source file 31 a , the external information 31 b and the specification definition information 42 of the migration target asset 31 . The specification information output unit 120 transmits the generated two pieces of specification information 61 and 62 to the difference extraction unit 130 .

The difference extraction unit 130 extracts the difference between the two pieces of specification information 61 and 62 using a diff command or the like. Difference extraction section 130 transmits specification difference information 63 indicating the extracted difference to difference report output section 140 and correction method proposal section 150 .

The difference report output unit 140 generates and outputs a difference report 64 describing the content of the difference indicated by the specification difference information 63 . Further, when there is a difference that matches any one of the correction rules 51, 52, . The correction method proposal unit 150 outputs the generated correction method instruction sheet 65 to the file or the monitor 21 .

An example of specification information output by the specification information output unit 120 will be described below with reference to FIGS. 6 to 10. FIG.
FIG. 6 is a diagram showing a first generation example of specification information. In the example of FIG. 6, the specification information is embedded in the source file in YAML notation. Note that the notation of the specification information is not limited to YAML.

For example, the specification information output unit 120 outputs specification information 61 in which a description as shown in FIG. 6 is added to the line "01 WK PIC S9(4)" (COBOL data definition) in the source file 31a. A line beginning with "*>" in the specification information 61 is a comment text indicating the specification.

For example, "type:"record"" indicates that the type of language element is record. "level: 1" indicates that the level number is "1". “name:“WK”” indicates that the name is “WK”. 'name-case-sensitivity: 'capitalize'' indicates that the name is capitalized and compared with respect to the case sensitivity of the name. The case-sensitivity specification of this name is information that depends on the processing system (type of compiler) and on the translation parameters. "usage:"display"" indicates that the usage: is "DISPLAY". The three lines of "format:", "type: "zoned-decimal"", and "sub-format: "f-tsu"" indicate that the data format is zoned decimal (F-tsusha format). there is Specifications for this format are implementation-dependent information. "width: 4" indicates that there are 4 digits. "unit-length: 1" indicates that the width of the digit is 1 byte. The width of this digit is information that depends on the processing system (type of compiler) and on the translation parameters. "signed: true" indicates that there is a sign. "child-items: null" indicates that there are no child items.

In order to accurately output execution platform dependent, processing system dependent, translation parameter dependent, and execution environment information dependent specifications, these information are also input to the specification information output unit 120 at the start of assessment processing.

The specification information output unit 120 outputs specification information for all program elements in the source file. Therefore, the difference extracting unit 130 can compare specification information for a plurality of platforms, and the correction method proposing unit 150 can present countermeasures against content differences.

Although the example of FIG. 6 shows the specification for one line in the source file 31a, the specification information output unit 120 similarly outputs the specification description for all lines in the source file 31a. As a result, specifications are written without omission for all codes in the source file 31a.

It should be noted that when the source file 31a is corrected, the content of the correction is also reflected in the output specification information.
FIG. 7 is a diagram showing a second generation example of specification information. FIG. 7 shows an example of specifications when the line "01 WK PIC S9(4)" in the source file 31a is changed to "01 WK PIC 9(8)". In this case, "width: 4" is changed to "width: 8" in the specification information 61a for the changed source file 31c. Also, in the specification information 61a for the changed source file 31c, "signed: true" is changed to "signed: false". Thus, if the code in the source file 31a is rewritten, the operation specifications indicated in the specification information also change. Note that the specification information 61a is an example of post-change specification information shown in the first embodiment.

Also, even if the source file 31a is the same, different specification information is generated when different translation options are applied.
FIG. 8 is a diagram showing a third generation example of specification information. FIG. 8 shows an example of the specification of the line "01 WK PIC S9(4)" in the source file 31a when "NOALPHAL" is not specified and when "NOALPHAL" is specified as a translation option. . The specification of "NOALPHAL" indicates that alphabetic characters in the source file 31a are not capitalized.

The specification information 61 when "NOALPHAL" is not specified indicates a comment text "name-case-sensitivity:"capitalize"". On the other hand, when "NOALPHAL" is specified, the corresponding comment text of the specification information 61b is "name-case-sensitivity:"sensitive".

In this way, even if the code in the source file 31a is the same, the difference in the specified translation option is expressed in the comment text as the difference in operation specification in the specification information 61 and 61b.
Even if the source file 31a is the same, different specification information is generated when the specification definition information corresponding to each different compiler is applied.

FIG. 9 is a diagram showing a fourth generation example of specification information. FIG. 9 shows an example of the specification of "01 WK PIC S9(4)" in the source file 31a generated by applying specification definition information corresponding to different compilers. For example, the specification information 61 is generated by applying specification definition information corresponding to a compiler manufactured by Ftsu. The specification information 62 is generated by applying the specification definition information corresponding to the M company's compiler.

In the specification information 61 when the specification definition information corresponding to the F-Tsu compiler is applied, the comment text "sub-format:"f-tsu"" is shown. On the other hand, the corresponding comment text in the specification information 62 when the specification definition information corresponding to the M company's compiler is applied is "sub-format:"m-focus"".

Even if the source file 31a is the same, different specification information is generated when different execution environment settings are applied. Execution environment settings are included in the external information 31b.
FIG. 10 is a diagram showing a fifth generation example of specification information. FIG. 10 shows specifications of the line "DISPLAY “TEXT" UPON SYSERR." An example is shown.

In the specification information 61 when there is no additional setting of the execution environment, 'type: 'stdio'' and 'kind: 'stderr'' are described under 'target-device:'. On the other hand, in the specification information 61c when the execution environment setting 31d for changing the message output destination is specified, the message output destination indicated in the execution environment setting 31d is described under "target-device:". In the example of FIG. 10, in the execution environment setting 31d, the message output destination is "type:"file"" and "path:"c:\punch. txt"".

The execution environment setting does not appear in the source file 31a, but is information that is applied when the application is executed. The runtime specification of the message output destination differs between the specification information 61 when there is no additional setting of the runtime environment and the specification information 61c when the runtime environment setting 31d is specified. That is, by generating the specification information 61c when the execution environment setting 31d is specified, the specification of the application assuming the execution environment can be recognized.

As described above, by generating the specification information according to the platform on which the application is executed, the assessment at the time of platform migration becomes easy. For example, when an asset to be migrated that was compiled and executed with a compiler provided by one vendor is compiled and executed with a compiler provided by another vendor, the difference in behavior before and after migration can be easily compared.

FIG. 11 is a diagram showing an example of assessment when changing the compiler. Assume that the pre-migration system 200 is executing an application in which a compiler provided by M company is used to compile the source file 31a. Assume that the post-migration system 300 is scheduled to execute an application obtained by compiling the source file 31a using a compiler provided by F-Tsu Corporation. In this case, the specification information 61d is generated by applying the specification definition information corresponding to the compiler of M company to the source file 31a. For the source file 31a, the specification information 62a is generated by applying the specification definition information corresponding to the F-Tsu compiler. The example of FIG. 11 shows the difference between the specification information 61d and 62a regarding the specification for "MOVE WK-X TO WK-N." in the source file 31a.

Company M's compiler allows direct transfer from an alphanumeric item to a NATIONAL item (a national language string type item). Therefore, in the specification information 61d, the content of the transcription process is described as the specification of "MOVE WK-X TO WK-N."

On the other hand, Ftsu's compiler does not allow a direct transfer from an alphanumeric item to a NATIONAL item. Therefore, the specification information 62a describes that a translation error occurs as the specification of "MOVE WK-X TO WK-N."

Differences between the specification information 61d and the specification information 62a are extracted by the difference extraction unit 130. FIG. For example, a correction rule is prepared in advance for the case where the description of the transcription processing contents of the specification information 61d regarding the platform of the migration source becomes a translation error of "error-id: 'JMN3023I-S'" in the specification information 62a regarding the platform of the migration destination. can be kept. For the correction rule, for example, a solution "Proposal 1. Rewrite the transcription source to FUNCTION NATIONAL (WK-X)" is set. Based on the specification difference information 63 generated by the difference extracting unit 130 and the correction rule, the correction method proposing unit 150 makes a correction including a proposal message "Proposal 1. Rewrite the transcription source to FUNCTION NATIONAL (WK-X)." Generate method instructions 65 . In this way, the correction contents to be implemented at the time of platform migration are automatically generated.

The program written in the source file 31a includes a control structure such as an IF statement. The specification information output unit 120 also analyzes the specification of the control structure in the source file 31a line by line, and writes the specification in the specification information 61 as a comment.

FIG. 12 is a diagram showing an output example of the specification of the part of the control structure. As shown in FIG. 12, even if there is a conditional branch such as an IF statement, the specifications for all branch destinations are analyzed line by line, and the specification description is output to the specification information 61 . The meanings of the main items shown in FIG. 12 are as follows. "type" indicates the type of sentence/clause. "spec" indicates the classification of specifications. "condition" indicates details. "operands" indicate elements of an expression. "name" indicates a name. "class" indicates a data type. "width" indicates the data length. "format" indicates the data format. "value" indicates the value of data. "target" indicates the target of the operation.

In the example shown in FIG. 12, the source file 31a includes a subroutine call instruction "CALL "CBLABN" USING ABN-CODE". In programs that call such subroutines, the subroutine to be called may be created by the user or may be provided by the product. For customer assets that use subroutines that were provided in products on the pre-migration platform, users may create such subroutines on the post-migration platform.

In such a case, even if the compiler is used to parse the client assets, the compiler only determines that "this subroutine is defined by the user" and cannot detect the existence of incompatible parts. In addition, the method of identifying differences in specifications between the pre-migration system and the post-migration system in advance involves comparing the subroutine support status before and after the migration, making it difficult to manage combinations as the number of system combinations increases.

On the other hand, the specification information output unit 120 adds all specifications that can be grasped by syntactic analysis for each line as comment sentences. This makes it possible to extract differences in the specifications of subroutine call destinations.

FIG. 13 is a diagram showing an example of extraction of specification differences between subroutine call destinations. Note that FIG. 13 shows only the line of interest among the comment texts added by the specification information output unit 120, and omits other comment texts.

The comment described as "kind: 'service-routine'" in the specification information 61 according to the platform before migration is changed to "kind: 'user-routine'" in the specification information 62 according to the platform after migration. description has changed. By extracting the difference between the specification information 61 and the specification information 62, it becomes possible to extract the specification difference of the call destination of the subroutine.

Further, when the specifications are extracted line by line based on the specification definition information, the specification information output unit 120 continues extracting the specifications for the subsequent lines even if there is an error in the compilation. do. As a result, it is possible to prevent an operation change portion from being omitted from being extracted due to error propagation.

FIG. 14 is a diagram illustrating an example of specification difference extraction in which error propagation is suppressed. In the example of FIG. 14, the CALL statement in the source file 31a contains an undefined constant. When parsed by the compiler, evaluation of the entire CALL statement may be interrupted by an undefined constant. On the other hand, the specification information output unit 120 does not stop extraction of subsequent specifications even if there is an undefined constant. Therefore, even if an undefined constant is included in the CALL statement, the specification information 61 and 62 correctly represents the specification difference between the subroutine call destinations. The specification information 61 and 62 also include a comment indicating an undefined constant.

Further, since the specification information output unit 120 generates specification information by referring to the external information 31b, it is possible to extract specification differences that are not known at the time of compiling but are found at the time of operation. For example, the specification information output unit 120 refers to the operation setting file included in the external information 31b and correctly extracts the specification difference when the operation changes according to the parameter settings during operation.

FIG. 15 is a diagram illustrating an example of specification difference extraction by referring to operating parameters. In the example of FIG. 15, the line "DISPLAY "TEXT" UPON SYSPUNCH" is included in the source file 31a. "DISPLAY SYSPUNCH" is an instruction to output characters to the standard output (stdout) in the initial setting.

It is assumed that in the migration source system, the external information 31b includes an operation setting file 31e of Company A's specifications. The operation setting file 31e includes information "CBL_SYSPUNCH=stderr" specifying an output destination as a specific specification of A company. In this case, the specification information 61e corresponding to the source system includes a comment indicating that the output destination is "stderr".

On the other hand, in the migration destination system, the output destination is not specified by the operation setting file. In this case, the specification information 62 corresponding to the migration destination system includes a comment text indicating that the output destination is the default "stdout".

In this manner, the specification information output unit 120 can reflect the setting of the external information in the output result of the specification, and can output the specification comment incorporating the unique system specification. This makes it possible to detect specification differences that cannot be detected by the compiler.

Different information is set in the external information for each company that operates the system. When comparing system specifications before and after migration, all combinations of systems that can be migrated must be compared, resulting in a huge amount of processing. On the other hand, by focusing on the software to be migrated and referring to the external information applied to the software to generate usage information, the amount of processing can be reduced.

FIG. 16 is a diagram showing an example of specification difference extraction when different operation setting files exist for each system. For example, it is assumed that there is an operation setting file 31e for A company's system and an operation setting file 31f for B company's system. Assume that an application based on the source file 31a is transferred from the system of Company A and the system of Company B to a system that does not use an operation setting file. In this case, specification information 61e to which the operation setting file 31e is applied, specification information 61f to which the operation setting file 31f is applied, and specification information 62 to which the initial setting values are applied are generated.

At the time of system migration of an application based on the source file 31a, it is possible to extract a difference simply by comparing the comment texts of the specification information 61e and 61f before migration and the specification information 62 after migration. If you try to create a tool for identifying differences in specifications between the pre-migration system and the post-migration system in advance, you will have to create a total of _n C ₂ tools for n systems. On the other hand, if specification information for each system is to be created for the source file 31a, only n pieces of specification information need to be created.

Next, the specification information generation processing at the time of platform migration of the application will be described in detail.
FIG. 17 is a flowchart illustrating an example of the procedure of specification information generation processing. The processing shown in FIG. 17 will be described below along with the step numbers.

[Step S101] The specification information output unit 120 acquires a list of migration target assets. For example, the specification information output unit 120 receives an input from the user of a list of assets to be migrated indicating software assets to be migrated to the destination system among the software assets installed in the migration source system.

[Step S102] The specification information output unit 120 acquires operating system information indicating an operating system. For example, the specification information output unit 120 receives, from the user, a set of identification information of the pre-migration system and identification information of the post-migration system as operating system information.

[Step S103] The specification information output unit 120 reads from the storage unit 110 the specification definition corresponding to the system indicated in the operating system information.
[Step S104] The specification information output unit 120 loops the processing of step S105 until the processing of step S105 is completed for all the external information assets included in the migration target assets shown in the acquired migration target asset list.

[Step S105] The specification information output unit 120 analyzes the external information. The details of this process will be described later (see FIG. 18).
[Step S106] When the process of step S105 is completed for all external information assets, the specification information output unit 120 advances the process to step S107.

[Step S107] The specification information output unit 120 loops the process of step S108 until the process of step S108 is completed for all the source files included in the migration target assets shown in the acquired migration target asset list.

[Step S108] The specification information output unit 120 performs source file analysis processing. The details of this process will be described later (see FIG. 25).
[Step S109] The specification information output unit 120 ends the specification information generation process when the process of step S108 is completed for all source files.

FIG. 18 is a flowchart showing an example of the procedure of external information analysis processing. The processing shown in FIG. 18 will be described below along with the step numbers.
[Step S121] The specification information output unit 120 analyzes the type of external information. If the external information is the environment variable list, specification information output unit 120 advances the process to step S122. If the external information is a runtime option file, specification information output unit 120 advances the process to step S126. Further, if the external information is an operation setting file, specification information output unit 120 advances the process to step S129.

[Step S122] The specification information output unit 120 loops the processing of steps S123 to S124 until the processing of steps S123 to S124 is completed for all variable definitions shown in the environment variable list.

[Step S123] The specification information output unit 120 checks whether or not there is a variable name of a variable definition included in the environment variable list in the system usage environment variable list table indicated in the specification definition information for each system. The system usage environment variable list table is a list of variables provided by the system that executes the application.

FIG. 19 is a diagram showing an example of a system usage environment variable list table. In the system use environment variable list table 71, for example, the variable name of the system use environment variable is set in association with the item name "Key" indicating the system use environment variable.

Hereinafter, the explanation will be returned to FIG. 18 .
[Step S124] The specification information output unit 120 stores a record corresponding to the variable name of each variable included in the environment variable list in the environment variable list table. The environment variable list table contains the result of investigation as to whether or not the variable is included in the system use environment variable list table.

FIG. 20 is a diagram showing an example of an environment variable list table. The environment variable list table 72 has columns of "Key", "Value", and "System Flag". A variable name is set in the “Key” column. The value of the variable is set in the "Value" column. A system flag indicating whether or not the variable is included in the system use environment variable list table is set in the "system flag" column. For example, if the variable is included in the system use environment variable list table, the system flag is set to "1", and if the variable is not included in the system use environment variable list table, the system flag is set to "0".

Hereinafter, the explanation will be returned to FIG. 18 .
[Step S125] The specification information output unit 120 ends the external information analysis process when the process for all variable definitions is completed.

[Step S126] The specification information output unit 120 loops the processing of step S127 until the processing of step S127 is completed for all runtime options indicated in the runtime option file.

[Step S127] The specification information output unit 120 stores data corresponding to the runtime option in the runtime option table.
FIG. 21 is a diagram showing an example of the runtime option table. The runtime option table 73 has columns of "Key" and "Value". In the "Key" column, variable names of execution environment variables used as runtime options are set. In the "Value" column, identification information (file location, file name, etc.) of the file in which the execution environment variable is set is set.

Hereinafter, the explanation will be returned to FIG. 18 .
[Step S128] The specification information output unit 120 terminates the external information analysis processing when the processing for all runtime options is completed.

[Step S129] The specification information output unit 120 loops the processing of step S130 until the processing of step S130 is completed for all the operation settings indicated in the operation setting file.

[Step S130] The specification information output unit 120 stores data in the operation setting table for each function.
FIG. 22 is a diagram showing an example of an operation setting table. The operation setting table 74 has columns of "Key" and "Value". The name of the function is set in the "Key" column. A value specifying a function is set in the "Value" column.

Hereinafter, the explanation will be returned to FIG. 18 .
[Step S131] The specification information output unit 120 ends the external information analysis process when the process for all operation settings is completed.

External information is analyzed in this manner. The external information analysis process is performed not only for the external information arbitrarily set by the user, but also for system-specific external information.
FIG. 23 is a diagram showing an example of data registration processing from the environment variable list to the environment variable list table. The specification information output unit 120 reads the runtime environment variables from the execution environment variable definition file 81 that defines the execution environment variables in addition to the system environment variables and user environment variables. The execution environment variable definition file 81 contains a list of environment variables. Environment variables are defined in the environment variable list in the form of "key=value". The specification information output unit 120 adds to the environment variable list table 72 a record corresponding to each environment variable definition expression in the execution environment variable definition file 81 . The specification information output unit 120 sets the value of the left side of the definitional expression of the environment variable in the "Key" column of the added record. Further, the specification information output unit 120 sets the value of the right side of the definitional expression of the environment variable in the "Value" column of the added record. Since the environment variables defined in the execution environment variable definition file 81 are not system use environment variables, "0" is set in the system flag column of the corresponding record.

FIG. 24 is a diagram showing an example of data registration processing from the operation setting file to the operation setting table. In addition to specifying the operation of the entire migration target asset using environment variables, external information that sets the operation of a specific function may be used. In that case, for example, the operation setting file 82 is used as the external information.

The operation setting file 82 shown in FIG. 24 is a file for setting screen display operations in the function of creating a GUI (Graphical User Interface) screen. In the operation setting file 82, screen display operation settings are defined in the form of "key value". A character string beginning with "*" is a comment text. The operation settings shown in the operation setting file 82 define the title of the GUI window, the name of the font to be used, the size of the font to be used, the display position of the GUI window, and the like.

The specification information output unit 120 adds records corresponding to each operation setting in the operation setting file 82 to the operation setting table 74 . The specification information output unit 120 sets the value on the left side of the operation setting in the "Key" column of the added record. Further, the specification information output unit 120 sets the value on the right side of the operation setting in the "Value" column of the added record.

By analyzing the external information, referring to the environment variable list table 72, the runtime option table 73, and the operation setting table 74, the source file is analyzed to extract operation specifications according to the application execution status. be able to.

Next, the source file analysis processing will be explained in detail.
FIG. 25 is a flowchart illustrating an example of the procedure of source file analysis processing. The processing shown in FIG. 25 will be described below along with the step numbers.

[Step S141] The specification information output unit 120 outputs the external information used in the subsequent analysis as a comment text to the specification information.
[Step S142] The specification information output unit 120 loops the processing of steps S143 to S151 until the processing of steps S143 to S151 is completed for all lines and tokens in the source file.

[Step S143] The specification information output unit 120 analyzes the type of line or token to be processed. Specification information output unit 120 advances the process to step S144 if the line or token is a variable definition. If the line or token is a processing instruction, specification information output unit 120 advances the process to step S147. Furthermore, specification information output unit 120 advances the process to step S149 if the line or token is an instruction argument.

[Step S144] The specification information output unit 120 refers to the result of the external information analysis, and analyzes the variable definition information based on the variable definition information corresponding to the migration source or migration destination system.
[Step S145] The specification information output unit 120 stores the analysis result in the variable list table.

FIG. 26 is a diagram showing an example of a variable list table. The variable list table 75 has columns of "Name", "Class", "width", and "format". A variable name is set in the “Name” column. The “Class” column contains variable types (character string type: string, numerical value type: numeric, etc.). The data length of the variable is set in the "width" column. A data format (Japanese: Jpn, packed decimal: packed-decimal, etc.) is set in the “format” column.

Hereinafter, the explanation will be returned to FIG.
[Step S146] The specification information output unit 120 outputs the variable specification as a comment text to the specification information. Thereafter, specification information output unit 120 advances the process to step S152.

[Step S147] The specification information output unit 120 refers to the result of the external information analysis, and analyzes the instruction type based on the variable definition information corresponding to the migration source or migration destination system.
[Step S148] The specification information output unit 120 outputs the instruction specification for each instruction type and for each system as a comment to the specification information. Thereafter, specification information output unit 120 advances the process to step S152.

[Step S149] The specification information output unit 120 refers to the result of the external information analysis, and analyzes the argument type based on the variable definition information corresponding to the migration source or migration destination system.
[Step S150] The specification information output unit 120 refers to the variable list table 75 and acquires argument information.

[Step S151] The specification information output unit 120 outputs the argument specification as a comment text to the specification information.
[Step S152] When the processing of steps S143 to S151 is completed for all lines and tokens, the specification information output unit 120 ends the source file analysis processing.

The specification information output unit 120 generates specification information before migration and after migration. The difference in specification is clarified by comparing the specification information by the difference extraction unit 130 . The specification difference is output as a difference report in a format that is easy for the user to understand, for example, by the difference report output unit 140 .

FIG. 27 is a diagram illustrating an output example of a difference report. A difference report 64 is generated based on the specification difference information 63 obtained by extracting the difference between the specification information 61 and 62 before and after migration generated based on the source file 31a. The difference report 64 includes information on the pre-migration system and the post-migration system (type of OS, type of processing system, etc.). In addition, the difference report 64 describes the line number of the line in which the operation has a difference, the indication number, the content of the indication, etc., in association with the asset name of the migration target asset. The indication number is a number indicating the type of difference that has occurred.

The difference report output unit 140 displays the difference report 64 on the monitor 21, for example. As a result, the user can accurately grasp the change in operation that occurs when the platform on which the asset to be migrated is executed is migrated.

[Other embodiments]
In the second embodiment, an example of migrating software assets written in COBOL is used. It can be similarly applied to migration of software assets.

Although the embodiment has been exemplified above, the configuration of each part shown in the embodiment can be replaced with another one having the same function. Also, any other components or steps may be added. Furthermore, any two or more configurations (features) of the above-described embodiments may be combined.

1 Software Asset 1a Source File 1b External Information 2 First Specification Definition Information 3 Second Specification Definition Information 4 First Specification Information 5 Second Specification Information 6 Specification Difference Information 7 Difference Report 10 Information Processing Device 11 Storage Unit 12 Processing Unit

Claims (7)

to the computer,
deciphering the operation specifications of the code for each line described in the source file based on the specification definition information defining the operation specifications of the programming language used to describe the analysis target program in the source file;
generating specification information in which a comment statement indicating operation specifications of the code described in each of the plurality of lines is associated with each of the plurality of lines in the source file;
An analysis program that causes processing to be performed. In decoding the code specification, based on the external information indicating the information to be referred to when executing the analysis target program, the operation when the external information reference code describing the operation according to the external information is executed. decipher,
In the generation of the specification information, a comment text indicating an operation corresponding to the external information based on the external information reference code is described in the specification information in association with the line in which the external information reference code is described.
The analysis program according to claim 1. to the computer, further comprising:
Based on the specification definition information, decipher the operation specifications of the code for each line described in the post-change source file after the change is made to the source file;
generating post-change specification information in which a comment statement indicating operation specifications of the code written in each of the plurality of lines is associated with each of the plurality of lines in the post-change source file;
extracting a difference between the specification information and the post-change specification information;
3. The analysis program according to claim 1, which causes a process to be executed. Decoding the specification of the code is described in the source file based on the first specification definition information defining the operation specification of the programming language in which the program to be analyzed is described when the program to be analyzed is executed on the first system. based on the second specification definition information defining the operation specifications of the programming language in which the analysis target program is described when the analysis target program is executed on the second system; to decipher the operation specifications of the code for each line described in the source file,
In the generation of the specification information, a comment statement indicating the operation specification based on the first specification definition information of the code written in each of the plurality of lines is described in association with each of the plurality of lines in the source file. The first specification information is generated, and a comment statement is associated with each of the plurality of lines in the source file and indicates the operation specification of the code written in each of the plurality of lines based on the second specification definition information. generating the described second specification information;
extracting a difference between the first specification information and the second specification information;
The analysis program according to claim 1 or 2. to the computer, further comprising:
Based on the difference between the first specification information and the second specification information, outputting a correction proposal for migrating the analysis target program executed in the first system to the second system;
5. The analysis program according to claim 4, causing the processing to be executed. the computer
deciphering the operation specifications of the code for each line described in the source file based on the specification definition information defining the operation specifications of the programming language used to describe the analysis target program in the source file;
generating specification information in which a comment statement indicating operation specifications of the code described in each of the plurality of lines is associated with each of the plurality of lines in the source file;
The parsing method that causes the processing to take place. a storage unit that stores a source file and specification definition information that defines an operation specification of a programming language used to describe a program to be analyzed in the source file;
deciphering the operation specifications of the code for each line described in the source file based on the specification definition information; a processing unit that generates specification information in which comment statements indicating operation specifications of are described;
Information processing device having

Images