This command produces a command file that can be used to run a complete migration: import, Macro dispatch and migration help. You can indicate an option for general and z/OS projects to generate the COBOL sources in different projects and separate the metadata files.
Options | Comments | Required | Default values |
---|---|---|---|
--data | Full path to the workspace (Rational® Developer for System z® option). | Yes | |
--log | Log file name The beginning of this file reminds the parameters that were entered to run the Pacbase migration procedures. |
No | trace.log |
--from | Name of the folder that contains the files required for the migration: MIA1.txt, MIA2.txt, MIA3.txt, MIA4.txt, MIBR.ta2, and MIMA.cblgen Their names cannot be changed. | Yes | |
--location | This parameter is used to replace the name of the target location for the import commands with the required value. It is also used to name the file produced by the automatic migration command: location.txt. | Yes | |
--separateCobolProject | Option available on general and z/OS projects. If this option is indicated, the COBOL sources will be generated in a separate project that is named after the project of its model instance, with a _COB suffix. |
No | |
--cobolProjectType | Type of the project that will contain the COBOL
sources:
|
No | G |
--separateMapFolder | Option to migrate Screen maps into a specific folder | No | map |
--separateMetadataFiles | Option to separate the metadata files | No | |
--pdpRootPath | Path name of the pdp metadata file | No | pdp |
--scmtoolsEntriesFile | Path and name of the script file that contains the SCM commands, to upload data to the Rational Team Concert server | No | scmtools_entries.bat in the .metadata folder of the workspace |
Other .ta2 files with other names can exist in the folder. Such is the case, for example, if you customized the migration with the MIBU procedure. All the .ta2 files are then taken into account by the automatic migration.
Other .cblgen files with other names can exist in the folder. Such is the case, for example, if you changed the source code of a Macro manually. All the .cblgen files are then taken into account by the automatic migration.