rpp --importJournal
This command imports updates into Rational Programming Patterns. These updates are extracted from the Pacbase journal or from the file that is produced by the MIBU customized migration procedure. The file to be imported must have a .ta2 extension but its name must not be MIBR. This command is automatically run by the rpp --automaticMigration command for a progressive migration. However, you can also run it independently.
Syntax
rpp.bat --importJournal [options]Parameters
Options | Comments | Required | Default values |
---|---|---|---|
--data | Full path to the workspace | 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 |
--fromFile | Name of the input .ta2 file. This file must not be named MIBR.ta2. | Yes | |
--fromDataFile | Path and name of the .xml technical file to take into account for the import | Yes | |
--location | Target location | Yes | |
--generatedDataFile | Path and name of the .xml technical file that is generated after the import | No | imported_data_refer.xml in the .metadata folder, where refer corresponds to the target location |
--report | Import report file | No | .pacmigration.log in the .metadata folder of the workspace |
--overwriteReport | Overwriting of the report file | No | false - default append to the existing file |
--librariesFilterFile | Filtering of the extraction results to import the data from some
Libraries only. These Libraries must be listed in the librariesFilter.txt file, which must be present in the import directory. This file must contain one Library per line. |
No | |
--noMigratedFile | Full path to the file that contains the list of Programs,
Screens, or Servers whose COBOL files must not be migrated upon a multi-session migration
(MIBR procedure) or progressive migration (MIBJ procedure).
Each time one of the procedures is run, the updated list is reexported. You can take it into account
each time a session or the journal is imported by specifying the --noMigratedFile option. The COBOL files of the new instances that are integrated in the updated list are
then automatically removed from the workspace if they had been previously imported. The file that contains the instances list must have been previously copied into the migration directory, possibly renamed (userNMig for example), and assigned a .txt extension. You can specify the --noMigratedFile option in the automatic migration command. If you do not use this command, you can specify the option in the import command or journal import command. |
No |
- User code in Rational Team Concert
- Name of the stream where the projects are uploaded to
- Address of the Rational Team Concert server
- Path of the folder that contains the lscm command
The .xml technical file that is created at the end of the import is required for a subsequent import. This file contains information that is not included in the Rational Programming Patterns metamodel, and the list of the instances that were previously imported.
- The context of the import such as the database, user, session, Library, and date.
- The replaced special characters.
- The statistics of the instances that are present in the .ta2 file. These figures include the instances that were duplicated by the migration procedures.
- The errors that were detected upon the import.
- The Data Structures and Dialogs that were duplicated by the import. A Data Structure is duplicated if some of its Segments exist in a lower Library in Pacbase; the Data Structure is then duplicated in the corresponding Rational Programming Patterns subproject. A Dialog is duplicated if the type of some of its components (Screens, Servers, or Folders for example) is not compatible with its own type. For example, in Pacbase, a Server Dialog gathers Servers and Client Screens. In this case, a Client Dialog is created by the import in Rational Programming Patterns to gather these Client Screens.
- The number of imported instances and the number of the instances in the .ta2 file. The number of imported instances can be lower than the number of the instances in the .ta2 file if you import a new Pacbase session into the same workspace. In this case, the instances that were not modified are not counted among the imported instances.
- The number of modified/created/deleted design entities.