JP2004334325A - File conversion system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for efficiently transferring a system. <P>SOLUTION: A conversion processing part 30 converts information included in a transfer target file stored in a transfer target file storage part 11 according to a prescribed rule. A conversion file including the information converted by the conversion processing part 30 and information showing that the conversion processing part 30 cannot execute the conversion is stored in a conversion file storage part 13. The conversion file can be edited by use of an editor. The conversion file is edited by the editor to become a transfer completion file, and is stored in a transfer completion file storage part 14. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technique for converting a file, and more particularly, to a technique for converting a source code of a computer program and migrating a system.
[0002]
[Prior art]
2. Description of the Related Art There is known a system in which a program running on a transfer source computer is converted so that the program can be executed on a transfer destination computer, and the program is transferred (for example, Patent Document 1).
[0003]
[Patent Document 1]
Japanese Patent Application Laid-Open No. 8-147156
[Problems to be solved by the invention]
The greater the scale of the system to be migrated, the greater the merit of automatically converting programs and data using the migration system and migrating. However, as the scale increases, there will be various variations in programs and the like. Therefore, constructing a migration system for automatically performing batch conversion of all programs and the like requires an enormous number of man-hours, and in many cases, the efficiency of the entire migration is degraded.
[0005]
Also, a test for confirming normal operation after converting a program or the like is indispensable. In particular, a combination test performed by combining a plurality of programs (modules) is important.
[0006]
Therefore, an object of the present invention is to provide a technique for efficiently migrating a system.
[0007]
[Means for Solving the Problems]
A file conversion system according to one embodiment of the present invention includes a first storage unit that stores a conversion target file, a conversion unit that converts information included in the conversion target file according to a predetermined rule, and the conversion unit. Second storage means for storing a conversion file including information converted by the conversion means and information indicating that conversion was not possible by the conversion means, an editor for editing the conversion file, And third storage means for storing the edited file.
[0008]
In a preferred embodiment, the conversion target file may be a source code file of a computer program operating on the first system or a file described in JCL (Job Control Language). At this time, the conversion means can perform conversion for shifting from the first system to the second system.
[0009]
In a preferred embodiment, for a plurality of file groups constituted by a plurality of the edited files, fourth storage means for storing identification information of a plurality of edited files belonging to each file group; Fifth storage means for storing the identification information of the person in charge in association with it, means for confirming that the edited file exists in the third storage means, and all of the edited files belonging to one file group exist. Notification means for notifying the person in charge associated with the one file group when the above is performed.
[0010]
In a preferred embodiment, the file group may be a group for performing an operation check test.
[0011]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an overall configuration of a migration system 1 according to the present embodiment. The present system 1 performs file conversion necessary for performing system migration. The following description converts software resources for a system that operates on a large computer, called a mainframe, to operate on a small computer such as a workstation (hereinafter, WS) or personal computer (hereinafter, PC). This is done by taking as an example the case where migration is performed.
[0012]
The migration system 1 is configured by, for example, a general-purpose computer system, and individual components or functions in the system 1 described below are realized, for example, by executing a computer program.
[0013]
The system 1 includes a transfer target file storage unit 11, a conversion log storage unit 12, a conversion file storage unit 13, a transfer completion file storage unit 14, a transfer target file registration unit 21, an editor 22, a status management unit 23 and a conversion processing unit 30.
[0014]
The transfer target file storage unit 11 stores files to be transferred. In the present embodiment, the migration target files are a source code file described in COBOL (Common Business Oriented Language) operating on the mainframe, a file described in JCL (Job Control Language), and a registered original document.
[0015]
The transfer target file registration unit 21 registers the transfer target file in the transfer target file storage unit 11. The input for file registration may be performed by an operator using an input device (not shown), for example.
[0016]
The conversion processing unit 30 acquires the files stored in the transfer target file storage unit 11 and performs a predetermined conversion for each file. For example, the conversion processing unit 30 converts information such as a source code, a script, and a registered original indicating a record format included in the migration target file according to a predetermined rule. In the present embodiment, the conversion processing unit 30 converts the COBOL and JCL for the mainframe into the COBOL and JCL for WS or PC, respectively. Further, the conversion processing unit 30 converts the registered original text for the mainframe into the registered original text for the WS or the PC. A conversion file is generated based on the converted information, and stored in the conversion file storage unit 13. The conversion file may include a message such as an error code indicating that the conversion processing unit 30 could not perform conversion, in addition to the converted source code, the JCL, and the registered original text. The detailed configuration and operation of the conversion processing unit 30 will be described later.
[0017]
The conversion log storage unit 12 stores a log when the conversion processing unit 30 performs the conversion process.
[0018]
In the conversion processing performed by the conversion processing unit 30, the conversion may fail or may not be performed, and it may not be possible to transfer all the program files or the like in a complete form. Therefore, in the present system, the operator can use the editor 22 to correct the conversion file. For example, the operator can use the input / output device (not shown) and the editor 22 to refer to information in each file stored in the conversion file storage unit 13, check the conversion state, and edit.
[0019]
The file that has been checked and corrected by the operator is stored in the transfer completion file storage unit 14 as a transfer completion file. As for the program file or the JCL file, a file that has completed the unit test for checking the operation in file units may be stored as a migration completion file. The unit test may be an operator who has edited with an editor, or may be a unit tester different from the operator.
[0020]
The status management unit 23 monitors the file conversion status. For example, the status management unit 23 refers to the migration completion file storage unit 14 and checks the existence of the migration completion file. The status management unit 23 may store a file group for performing a combination test for checking operation by combining a plurality of files.
[0021]
The file group can be managed by, for example, a combination test table 50 as shown in FIG. In the combination test table 50, a file group name 51, a file name 52, and a test staff 53 are associated with each other. In the file name 52, a plurality of migration completed file names required for performing the combination test are stored.
The test staff 53 stores information for identifying the test staff. For example, here, the e-mail address of each person in charge is stored.
[0022]
The status management unit 23 refers to the test technician 53 and notifies each technician of the completion of all the migration completion files registered in the file name 52. As a result, it is understood that each tester is in a state where he can perform the test he or she is responsible for.
[0023]
Next, details of the conversion processing performed by the conversion processing unit 30 will be described with reference to FIG.
[0024]
First, the transfer target file storage unit 11 can store a transfer target source code file 111, a transfer target registration original text 112, and a transfer target JCL file 113. The transfer target source code file 111, the transfer target registered original document 112, and the transfer target JCL file 113 can each be singly or plurally stored.
[0025]
Similarly, the conversion file storage unit 13 can store a conversion source code file 131, a conversion registration original document 132, and a conversion JCL file 133. The conversion source code file 131, the conversion registration original document 132, and the conversion JCL file 133 can each store one or more.
[0026]
The conversion processing unit 30 further includes a source conversion unit 31, a registered original text conversion unit 32, a conversion target extraction unit 33, a JCL conversion unit 34, a data length table 35, an error code table 36, and an intermediate file storage. A part 37.
[0027]
The source conversion unit 31 acquires the migration target source code file 111, and converts the source code included in the file according to a predetermined rule. If the source conversion unit 31 cannot convert the source code, an error message is stored in the conversion log storage unit 12. The normally converted source code is stored in the conversion file storage unit 13 as a conversion source code file 131. The source code cannot be converted, for example, in the case of a function not supported by WS or PC COBOL, such as a tape output process.
[0028]
The registered original text conversion unit 32 acquires the transfer target registered original text 112 and converts it according to a predetermined rule. The registered original text conversion unit 32 acquires the data length for each item of the registered original text, and registers the data length in the data length table 35. The converted original text 132 is stored in the converted file storage unit 13.
[0029]
Conversion of the JCL file is performed in two steps. That is, the conversion target extraction unit 33 acquires the migration target JCL file 113, extracts a conversion target portion (operand) from the JCL included in the file, and generates an intermediate file. The generated intermediate file is temporarily stored in the intermediate file storage unit 37.
[0030]
The JCL converter 34 acquires the intermediate file and converts the JCL according to a predetermined rule. For example, the JCL conversion unit 34 acquires the data item name and the data length from the data length table 35 and embeds them in the JCL. Here, the JCL conversion unit 34 does not perform the JCL conversion for, for example, those for which automatic conversion such as utility and parameter setting is difficult, and those for which there is no corresponding function in WS or PC COBOL. Therefore, when the JCL conversion unit 34 does not perform the JCL conversion, it is processed as an error. That is, the JCL conversion unit 34 refers to the error code table 36 and acquires an error code corresponding to the type of the error.
Then, the JCL conversion unit 34 generates a conversion JCL file including the normally converted JCL, and embedding an error code and information indicating the content of the error at a location where an error has occurred, and stores the converted JCL file in the conversion file storage unit 13. Store.
[0031]
As a result, the converted JCL file 133 includes an error code as information indicating that the JCL has been normally converted and information indicating that the JCL has not been converted. Therefore, if the operator opens this file with the editor 22, the location where the error occurred and the content thereof can be immediately known without referring to the log, and correction can be made on the spot. Also, in the conversion of the source code, information on the error may be included in the converted source code 131.
[0032]
Next, the overall processing procedure performed by the migration system 1 having the above-described configuration will be described with reference to the flowchart in FIG.
[0033]
First, a file to be migrated is stored in the file to be migrated storage unit 11 (S11). The conversion processing unit 30 acquires each transfer target file from the transfer target file storage unit 11 and performs each conversion process as described above (S12). Then, the conversion processing unit 30 stores the conversion file including the converted information in the conversion file storage unit 13. Since there is a portion in the conversion file that needs to be corrected, the conversion file is supplied to the editor 22, and the operator or the like makes a manual correction using the editor (S13). The corrected file is stored in the migration completed file storage unit 14 as a migration completed file. Then, finally, the tester performs each combination test using the migration completion file (S15). When the connection test is completed, the transfer by the present system 1 is completed.
[0034]
In addition, the system 1 notifies each person in charge that the files necessary for the combination test have been prepared in order to perform the combination test in step S15. The procedure for performing this notification will be described with reference to the flowchart in FIG.
[0035]
The status management unit 23 confirms the existence of each file by referring to the migration completion file storage unit 14. Then, it is determined whether or not there is a group having all the files among the system groups registered in the integration test table 50 (S21). If there is a system group in which the files are available, the person in charge of the group is notified that the files are available, for example, by e-mail (S22). These steps are repeated until all files to be migrated are collected and a notification is sent to the person in charge for all file groups (S23).
[0036]
The embodiments of the present invention described above are exemplifications for describing the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating an entire configuration of a migration system 1 according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating an example of a combined file table.
FIG. 3 is a configuration diagram for describing in detail a process performed by a conversion processing unit 30;
FIG. 4 is a flowchart showing an overall processing procedure of the migration system 1;
FIG. 5 is a flowchart illustrating a processing procedure for notifying a binding tester;
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Migration system, 11 ... Migration target file storage part, 12 ... Conversion log storage part, 13 ... Conversion file storage part, 14 ... Migration completion file storage part, 21 ... Migration target file registration part, 22 ... Editor, 23 ... Status Management unit, 30... Conversion processing unit.

Claims (6)

First storage means for storing a file to be converted;
Conversion means for converting information contained in the conversion target file according to a predetermined rule,
Second storage means for storing a conversion file including information converted by the conversion means and information indicating that conversion was not possible by the conversion means;
An editor for editing the conversion file;
A third storage unit for storing the edited file edited by the editor. The conversion target file is a source code file of a computer program operating in the first system or a file described in JCL (Job Control Language).
2. The file conversion system according to claim 1, wherein the conversion unit performs conversion for shifting from the first system to the second system. Fourth storage means for storing identification information of a plurality of edited files belonging to each file group for a plurality of file groups constituted by a plurality of the edited files;
Fifth storage means for storing the file group identification information and the person in charge identification information in association with each other;
Means for confirming that the edited file exists in the third storage means;
2. The file conversion system according to claim 1, further comprising: notifying means for notifying, when all the edited files belonging to one file group are present, a person associated with the one file group to that effect. . 4. The file conversion system according to claim 3, wherein the file group is a group for performing an operation check test. The method performed by the file conversion system,
Obtaining a conversion target file from the first storage means;
Converting the information included in the conversion target file according to a predetermined rule,
Storing in a second storage means a conversion file including information converted by the conversion and information indicating that conversion was not possible by the conversion;
Obtaining the conversion file from the second storage means and supplying the converted file to an editor;
Storing the edited file edited by the editor in a third storage unit. When executed on a computer,
Obtaining a conversion target file from the first storage means;
Converting the information included in the conversion target file according to a predetermined rule,
Storing in a second storage means a conversion file including information converted by the conversion and information indicating that conversion was not possible by the conversion;
Obtaining the conversion file from the second storage means and supplying the converted file to an editor;
Storing the edited file edited by the editor in a third storage means.

Images