rpp --automaticMigration

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.

Syntax

rpp.bat --automaticMigration [options]

Parameters

Table 1. List of the available parameters
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:
  • G for general projects
  • Z for z/OS projects
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

 
Note:
For the --from parameter, the folder must have the following structure:
  • MIBR.ta2
    Note: The Pacbase version number is included in the .ta2 file. If the version in this file is not compatible with the current version of Rational Programming Patterns, the import is not run and an error is generated. The control does not go down to the subversion level (Y09A for example).

    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.

  • MIMA.cblgen

    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.

  • MIA1.txt
  • MIA2.txt
  • MIA3.txt
  • MIA4.txt
  • COBOL_MIA1.txt for the sources that contain the complete COBOL of Programs. These sources are produced by MIA1.
  • COBOL_MIA2.txt for the sources that contain the complete COBOL of standard Screens. These sources are produced by MIA2.
  • COBOL_MIA3.txt for the sources that contain the complete COBOL of TUI clients. These sources are produced by MIA3.
  • COBOL_MIA4.txt for the sources that contain the complete COBOL of Servers. These sources are produced by MIA4.
  • CONTROL_COBOL_MIA1.txt for the sources that contain the control COBOL of Programs. These sources are produced by MIA1.
  • CONTROL_COBOL_MIA2.txt for the sources that contain the control COBOL of standard Screens. These sources are produced by MIA2.
  • CONTROL_COBOL_MIA3.txt for the sources that contain the control COBOL of TUI clients. These sources are produced by MIA3.
  • CONTROL_COBOL_MIA4.txt for the sources that contain the control COBOL of Servers. These sources are produced by MIA4.
  • inputzCompMap.txt. This optional file is not automatically generated. If you need it, you must create it manually and add it to this folder. You use it to map Pacbase sets of optional control cards with z/OS language definitions. 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™.
The automatic migration produces the following elements:
  • A COBOL_FOLDER folder and a CONTROL_COBOL_FOLDER folder. These folders both contain four directories that correspond to the four patterns (pacprogram or MIA1, pacscreen or MIA2 for example). Each of these four directories contains a subdirectory for each Library. The .cbl files are stored in the subdirectory that corresponds to the initial Library of the generated instance.
  • A location.txt command file (where location is the name of the location). You must then run the rpp.bat --commands command with this file as an option.
  • A zcompmap.txt file that maps Pacbase sets of optional control cards with z/OS language definitions. It is produced if the --cobolProjectType parameter is assigned the value Z and if the inputzCompMap.txt file exists in the folder.

At the end of the log file, a counter displays the number of created/modified COBOL files.

Example

rpp.bat --automaticMigration --data C:/usr/WKSFD2 --from C:/usr/Tests/WorkItemRTC/WI6382bis/ --location TESTON --separateCobolProject --separateMapFolder --separateMetadataFiles --previousSessionFolder C:\RppData\BES_PDDN\0010T\COBOL_FOLDER --validationFile C:\RppData\validation.xml

Feedback