JPH04107751A - Method for shifting file environment from low-order system - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed Description of the Invention] [Summary] Regarding a file environment migration method when migrating an RDB file from a lower system to a higher system, the purpose of the present invention is to easily migrate the file environment from a lower system to a higher system. Transfer resources from the lower system to the higher system, enter a command, search for a file definition in the library of the higher system, expand the information of the searched file definition to the information table area of the higher system, and then write the file definition. Search for a physical file in the library of the upper system based on the physical file name in the body information, expand the searched file information to the information table area, set the information table information in the parameter of the conversion command, and use the control language The control language program is output as a program, and by translating and executing the control language program, a file environment for the host system is created.

[Industrial application field] This invention is -7: (RDB from i system to upper system
Concerning how to migrate the file environment when migrating files.

In data processing of a computer system, there are cases where it is desired to migrate the file environment (including physical files such as databases) used in a lower system to an upper system. However, even if you try to move the files from the lower system to the higher system and make it work on the higher system, it will not work properly on the higher system. This is because the search tools used to search for files are different, and the way they are controlled, how they search, and how they hold information are also different.

[Prior Art] FIG. 4 is an explanatory diagram of a conventional file environment migration method. 10 is a lower system, and 20 is an upper system. The figure shows the migration of the file environment from the lower system 10 to the higher system 20.

The lower system 10 includes a physical file 1 and a file definition body 2. Here, the physical file is a type of database, for example, an address and a name.

This is a file consisting of data such as telephone numbers. On the other hand, a logical file is a file that stores search conditions when searching for other addresses, telephone numbers, etc. using name data as a key, for example.

These physical files and logical files are collectively called an RDB file. The file definition body 2 is a unit containing information that associates physical files and logical files.

When transferring an RDB file from the lower system 10, first, the resources of the lower system 10 are transferred to the upper system 20, and sorting is performed. After that, we performed the following tasks.

(1) Apply the file definition structure imported with the contents of file definition structure 2 in the lower system 10 in mind to the file definition structure conversion tool 11, execute the file definition conversion command, and convert the file definition structure into the format of the upper system. (■ in the figure).

(2) Next, after checking the output result of the file definition conversion tool 11, create a file definition for the upper system using the file definition creation tool 12 (■ in the figure)
.

(3) Next, be aware of the format of the RDB file in the lower system 10, and if it is physical file 1, set the parameters of the physical file creation command and execute it to create physical file 14 (■ in the diagram) . If it is a logical file, set the parameters of the logical file creation command and execute it to create logical file 15 (■ in the diagram)
.

(4) When the physical file 14 is created by the process of (■) above, the data imported from the lower system 10 is stored in the physical file 14 (■ in the figure).

If there are multiple resources, perform (1) to (4) for each resource.
perform the work. In this way, an RDB file environment that is exactly the same environment as the lower system 10 is created. 13 is a created file definition for the upper system, 14 is a physical file, and ]5 is a logical file.

[Problems to be Solved by the Invention] Such a series of operations is performed manually by an operator. In other words, in the past, the operator had to check the file definition without looking at the screen, and then make changes to match the host system 20. Therefore, the conventional method has the following problems.

■Since it is done manually, there are many steps and it is easy to make mistakes.

■Work is troublesome because the operator must always be aware of the contents of the file definition and file.

■The more resources to be migrated, the more man-hours are required.

The present invention has been made in view of these problems, and an object of the present invention is to provide a method for migrating a file environment from a lower system to an upper system, which allows the file environment to be easily migrated from a lower system to a higher system. It is said that

[Means for Solving the Problems] FIG. 1 is a flowchart showing the principle of the method of the present invention. In the present invention, in step 1), resources from a lower system are transferred to an upper system, in step 2), a command is input, a file definition is searched in the library of the upper system, and the information of the searched file definition is transferred to the upper system. Step 3) Search for a physical file in the library of the upper system from the physical file name in the file definition information, and expand the searched file information to the information table area.Step 4) Set the information in the information table as a parameter of the conversion command and output it as a control language program (Step 5), and create a file environment for the upper system by translating and executing the control language program (Step 6).
It is characterized by the fact that

[Function] One command is input, and when that command is received, the migration work from the lower system to the higher system is processed within the command. As a result, the operator only needs to input one command, and the file environment can be easily migrated from the lower system to the higher system. Further, according to the present invention, since a control language program output method is adopted, it is possible to flexibly respond to changes in internal use.

[Embodiments] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 2 is a diagram showing the operation of the present invention. The explanation will be given below along with the drawings.

(1) Enter the command (■ in the diagram). At this time, the operator (user) is asked to specify the file descriptor name as a parameter when inputting a command.

Here, the file definition name may be a single file definition name or a generic name of file definition names.

(When you enter the 2 command, this command searches for the file definition name in the library 30 of the upper system based on the file definition name (■ in the figure). For example, there are definition entities A to M. Search for the definition entity name that corresponds to the command from among these definition entities. In this case, if the specified file definition entity name is a single name, the specified file definition entity is When a generic name is specified, all file definition bodies in the library 30 are processed.

(3) Once the file definition is retrieved, the following information is collected from the file definition and expanded into the information table area 40 (■ in the figure). The information collected is as follows.

■File definition type For physical files For logical files ■Record length ■Blocking factor ■Physical file name (4) When the information described above is expanded to the information table area 40, from the physical file name to the library 3
The physical file 22 within 0 is searched (■ in the figure). The figure shows a case where six files, physical file 1 to physical file 6, exist.

(5) When a physical file is found, the following information is collected from the file label 22a of the physical file and expanded to 40 in the table area (■ in the figure).

■Number of logical records in the data area ■Blocking factor ■Record length (6) Expand various information from the information table area 40 and find the values to be set in the parameters of each command (■ in the diagram)
.

(7) Once you have determined the value to be set, set the parameters for each command based on that value (7 in the figure).

(8) Output the command string formed by setting the parameters of each command as a control language blockrum (■ in the figure). A control language blockrum 50 is created by repeating such a sequence.

In addition, in the case of specifying a generic name, steps (2) to (7) are repeated and output as one control language blockrum.

As described above, according to the present invention, since the sequence from (1) to (8) is processed within the command, the operator only needs to input one command.

In addition, since a control language program output method is adopted, it is possible to respond flexibly when changing the contents.

FIG. 3 is a diagram showing the overall operation of the present invention.

Components that are the same as those in FIGS. 2 and 4 are designated by the same reference numerals.

(1) First, save the RDB1y environment in the lower system 1() to a medium.

(2) Next, the RDB file environment of the lower system 1C is imported into the library in the higher system 30. Let 31 be the imported resources imported into the host system 30 in this way.

(3) Sort resources.

(4) After sorting the resources, execute this command. The detailed procedure for executing the command is as explained in detail using FIG. 2. At this time, the operator specifies the file descriptor name as a parameter when inputting the command, or if a single name is specified, the specified file descriptor is searched, or if a generic name is specified, all file definitions in the library 30 are searched. Process the body sequentially.

(5) As a result of executing this command, the environment setting control language program 32 is created.

(6) This environment setting control language program 32 is translated, and an environment setting object program 33 is created.
By executing this environment setting object program 33, the RDB file environment 34 for the upper system is created.
Or constructed. This RDB file environment 34 for the upper system is the same environment as the F-rank system 10.

[Effects of the Invention] As described above in detail, according to the present invention, one command is input, and when that command is received, the migration work from the lower system to the higher system is processed within the command. This allows the operator to input just one command, making it easy to migrate the file environment from the lower system to the higher system. Further, according to the present invention, since a control language program output method is adopted, it is possible to flexibly respond to changes in internal use.

[Brief explanation of the drawing]

Figure 1 is a flow chart showing the principle of the method of the present invention. Figure 2 is a diagram showing the operation of the present invention. Figure 3 is a diagram showing the overall operation of the present invention. Figure 4 is a diagram showing the conventional file environment migration method. It is an explanatory diagram. In FIG. 2, 2] is a file definition body, 22 is a physical file, 22a is a file label, 30 is a library of the upper system, 40 is an information table area, and 50 is a control language program.

Claims (1)

[Claims] Transfer resources from the lower system to the higher system (step 1), input a command (step 2), search for a file definition in the library of the higher system, and retrieve the searched file definition. Expand the information to the information table area of the upper system (Step 3) Search for a physical file in the library of the upper system from the physical file name in the information of the file definition, and expand the searched file information to the information table area. (Step 4), set the information in the information table to the parameters of the conversion command, output it as a control language program (Step 5), and create a file environment for the upper system by translating and executing the control language program. (Step 6)
A method for migrating a file environment from a lower system, characterized by the following.