This command imports the instances into the local workspace.
Only the import of a .ta2 file is available.
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).
Syntax
rpp.bat --import [options]
Parameters
Table 1. List of
the available parametersOptions |
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 |
--importType |
Import type |
Yes |
ta2 |
--fromFile |
Input file name |
Yes |
|
--location |
Target location |
Yes |
|
--overwrite |
Overwrite existing files |
No |
false |
--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 .metadata folder
of the workspace |
--overwriteReport |
Overwrite report file |
No |
false - default append
to the existing file |
--multisession |
Import of data from several Pacbase sessions into the
same workspace. This parameter is automatically generated if the --previousSessionFolder parameter
is indicated in the automatic migration command.
|
No |
. |
For its later use, the script file that contains
the SCM commands must be completed with the following elements:
- 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 import report file summarizes
the contents of the imported
.ta2 file. It displays
the following information:
- 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.
- The total number of instances in the .ta2 file
and the number of imported instances, after the deletion of the duplicate
instances that can be detected if you import more than one Pacbase session into the
same workspace.
Samples
rpp.bat --import --fromFile
D:/Working/Misc/PGMCUO.ta2 --location TEST01 --importType ta2 --overwrite
--log d:/utmp/trace.log --data d:/Working/JbyWks
rpp.bat --import --fromFile C:/import/IMPORT1.ta2
--location IMPORT --importType ta2 --overwrite --data C:/workspaces/batchWks
--log C:/import/out/trace.log --generatedDataFile C:/import/out/genData.xml