This command produces a command file that can be used to run a complete migration: import, Macro dispatch, optional modification of the default generation target, 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:
|
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 |
--previousSessionFolder | Path to the COBOL files of a previous Pacbase session, if more
than one session is migrated into the same workspace. This parameter reduces the migration time because the COBOL files that are identical in both sessions (except for the Pacbase constants and the generation date) are not imported again. |
No | |
--validationFile |
Complete path of the validation.xml file, which contains the validation types. This file is automatically recognized in the preferences of the migration validation. The migration validation then automatically runs at the same time as the migration help to reduce the migration time. |
No |
If the migration results from the running of the MIBR or MIBA procedures, this file must be named MIBR.ta2.
If the migration results from the running of the MIBJ or MIBU procedures, the name of this file is not fixed but must be different from MIBR.ta2.
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.
This file must contain one
line for each mapping, according to the following format:
XX
LangageDefinition
where:
XX is
the set of the control cards (front and back) in Pacbase,
LangageDefinition is
the target language definition in Rational Team Concert™.
At the end of the log file, a counter displays the number of created or modified COBOL files.