Multi-session migration

To migrate several Pacbase sessions, you must use the same workspace in relation with only one Rational Team Concert™ stream. This stream is dedicated to the migration.

Before you begin

Create the migration stream in Rational Team Concert. This stream must recognize the Rational® Programming Patterns scanners. To prevent any conflict between the running of these scanners and the upload to the Rational Team Concert server, set the scanning delay to -1 for the whole migration.
  • Log in as an administrator to https://[fully-qualified hostname]:9443/ccm/admin.
  • In the Configuration entry, click Advanced properties.
  • Scroll the properties down to category Source code data collection. Scroll the category down to com.ibm.team.enterprise.internal.metadata.collection.service.MetadataCollectionLoopTaskService.
  • Change the value of Source Code Data Scanning Fixed Delay (seconds). Click the current value and overwrite it with -1.

The migration process is identical for each session. You must complete the following steps:

Procedure

  1. Extract the data with the MIBA or MIBR procedures. These procedures produce the list of the Macros to be generated with the MIMA procedure, and the input for the MIA1, MIA2, MIA3, and MIA4 procedures.
  2. Transfer the files to the workstation where the client parts of Rational Programming Patterns and of the required products are installed. You must transfer the files that are produced from the various procedures to the same directory.
    Warning: The .ta2 file that has received the journal transactions since the previous migration must not be named MIBR.ta2. For example, you can name it MIBJ.ta2 to differentiate it from the result of an initial migration.
  3. Run the automatic migration command: rpp --automaticMigration.

    Specify the --validationFile parameter in the automatic migration command to start the migration validation and the migration help at the same time. The migration help then migrates the COBOL files that have no difference after the application of the validation types and validates their migration at the same time. It produces a .log file that indicates the number of the validated COBOL files. However, before you indicate the --validationFile parameter in the automatic migration command, you are advised to verify that the validation types of the validation.xml file are adapted. Run the migration validation from the Validation Manager view on a significant subset of COBOL files. If you consider that the validation results are correct, you can then run the automatic migration with the --validationFile parameter.

  4. Run the resulting command file. This file must contain the following commands:
    • The import command of the .ta2 file that is produced by the Pacbase procedures: rpp --import.
    • The dispatch command of the Macro source code: rpp --dispatchMacro.
    • The migration help command: rpp --migrationHelp. This command is automatically run with the --validationFile parameter that is specified in the automatic migration command.
  5. Save the data in Rational Team Concert.
  6. Take a snapshot of the migration stream. In the Team artifacts view, right-click a stream and select New > Snapshot.
  7. Build the server indexes.

    In the Work Items perspective, you must select the migration stream to be scanned. In the Team Artifacts view, under your project area, select Enterprise Extensions > Source Code Data > Select Streams for Scanning.

    To build the indexes for the first time, select Update Source Code Data on the migration stream.

  8. Duplicate the migration stream. In the Team artifacts view, right-click a stream and select Duplicate.
  9. Update the server indexes.

    In the Work Items perspective, you must select the duplicated stream to be scanned. In the Team Artifacts view, under your project area, select Enterprise Extensions > Source Code Data > Select Streams for Scanning.

    To update the indexes, select Update Source Code Data on the duplicated stream.

Results

When the migration of each session is complete, copy the local workspace. This workspace can be used in a progressive migration.

From the migration of the second session onwards, the processing varies, even if the steps remain the same.

You must indicate the --previousSessionFolder parameter in the automatic migration command for each new session. 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. Moreover, the rpp --import and rpp --dispatchMacro commands recognize only the instances that have evolved.

Only the real differences are then uploaded to the Rational Team Concert server.

Important: To avoid altering the results, you must migrate the sessions one after the other without making any local modifications in Rational Programming Patterns. At the end of a multi-session migration, you can take the Pacbase modifications into account by running the MIBJ procedure.

Feedback