You can extract and migrate the Pacbase users and development databases. Jazz™ can be interconnected with an LDAP or a security system such as RACF®. In this case, there is no migration of Pacbase users.
Extract and transfer all the users from the administration database with the MIUS procedure.
Pacbase administrators are granted a JazzAdmins permission, whereas the other users are granted a JazzUsers permission.
Import the extracted users into Rational Team Concert. The Jazz Team Server must be running.
Transfer the file that contains the extracted users to the machine that hosts the Jazz Team Server.
You must first convert the ASCII file that is produced by the Pacbase extraction to the UTF-8 format. To do so, run the AsciiToUTF8.bat file that is located under the rpp directory of the Software Delivery Platform. Enter the following command line:
AsciiToUTF8 AsciiInputFile Utf8OutputFile
C:\...\IBM\JazzTeamServer\server\repotools-ccm -createUsers
fromFile=C:\...\MIUSFILE (after its conversion to the UTF-8 format)
repositoryURL=https://…:9443/ccm
adminUserId=xxxx
adminPassword=xxxx
The errors, if any, are displayed in the repotools-ccm_createUsers.log journal.
You must analyze the results of this procedure and complete all the actions that are indicated in the Pacbase installation guide before you extract the data. For example, you must manage the special characters and the instances that have the same external name. If the database contains Database Blocks with a DB type, you must run the TRDQ procedure to transform their type into Q2 before the migration.
These procedures can also replace the unrecognized special characters in an instance code with other characters. To do so, use the special characters file from the MIAM procedure and complete it.
These procedures provide the list of the Macros to be generated with the MIMA procedure and the input for the MIA1, MIA2, MIA3, and MIA4 procedures. Remember to indicate the codes of the optional control cards to insert separators in the MIAn procedures.
Command lines to enter | Explanations |
---|---|
open hostname | Replace hostname with the source host address. |
tsouid | Replace tsouid with the TSO user. |
tsopwd | Replace tsopwd with the TSO password. |
quote site sbdataconn=(IBM-1047,ISO8859-1) | Parameters for transferring the English EBCDIC to ASCII. |
quote site notrailingblanks | Parameter for removing blank characters at the end of the records |
get 'zFileName' c:\LocalFileName | Frame the name of the System z file with simple quotation marks (it defaults to 'tsouid'). |
quit |
Run the rpp --automaticMigration command. This command creates the command file that is used to run the import, dispatch the Macros, modify the generation target (if it is requested), and run the migration help. It creates the directories of the migrated sources by splitting the various programs. You must conform to the structure of the directory that contains the transferred files. See section Transfer the files.
Be sure to correctly use the parameters to create the projects that contain the COBOL sources. These projects can be zComponent projects or standard projects.
Information is available on the Progressive migration and the Multi-session migration.
The automatic migration produces a location.txt file (where location is the name of the location).
Example of an automatic migration command that creates a zComponent project and separates the COBOL source files from the Rational Programming Patterns metadata files. The metadata files will be stored in the design directory:
rpp.bat --automaticMigration --data "C:\Migration\Workspace" --log "C:\Migration\automatic.log" --from "C:\Migration\Input" --location XXXX --separateCobolProject --cobolProjectType Z --separateMetadataFiles --pdpRootPath design
The workspace that is created by the automatic migration can be used as is for a lookup only. To complete some updates or an impact analysis, for example, you must index it. To do so, right-click the Design Explorer view. Select Rebuild local workspace and Rebuild mappings between designs and generated files.
After running the automatic migration, you must start Rational Programming Patterns in graphic mode (Start > All programs > IBM Software Delivery Platform > IBM Rational Programming Patterns by default). Enter the name of the workspace that is to be used upon the migration.
Syntax: rpp.bat --commands [options]
--data - workspace. (required)
--log - Log file name. (trace.log by default)
--file - File containing the list of batch commands. (required)
--exitOnError - Exit in case of error on a command.
This step initializes a local workspace that contains a hierarchy of projects. Each project contains the instances that belong to a Pacbase Library.
This step recognizes the file that is produced by the MIMA procedure. It assigns the Macro sources to the corresponding Macros of the projects in your workspace.
If errors occurred during the dispatch, you can consult the .pacdispatchmacro.log error file in the .metadata folder of your workspace.
This optional step modifies the default generation target of the instance before its migration.
This step recognizes the source files that are generated by MIAn and migrates the COBOL files of Programs, Screens, and Servers into the workspace.