You must extract and migrate the Pacbase users and development databases.
Extract and transfer all the users, from the administration database, with the MIUS, Pacbase 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 which contains the extracted users to the machine which hosts the Jazz Team Server.
You must first convert the ASCII file produced by the Pacbase extraction to the UTF-8 format. To do so, run the AsciiToUTF8.bat file, 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.
Extract
the data with one of the Pacbase batch
procedures: MIBA or MIBR.
MIBA performs
an in-depth extraction of a list of instances. MIBR extracts
all the instances of the selected Library network or subnetwork in
a context (once for a given session).
You can later use
the MIBJ procedure to extract transactions from the Pacbase archived journal.
Use as input the file which contains the Programs to be transformed into Macros. This file is produced by the MIAM procedure.
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 Macros to be generated with the procedure MIMA and the user input for the procedures GPRT, MIA1, MIA2, MIA3, and MIA4.
Run the MIMA procedure to generate the Macros in a tagged COBOL format.
This procedure can also replace the unrecognized special characters in a Macro code with other characters. To do so, use the special characters file from the MIAM procedure and complete it. You must use the same special characters file as for the data extraction (MIBA, MIBR or MIBJ procedure).
Run the GPRT procedure with the C9 option to generate the COBOL sources to be used for the migration. These sources include both the code generated from the instance design and the specific code.
The user input of the procedure can be retrieved from MIBA or MIBR procedure.
Run the MIA1 (for Programs), MIA2 (for Screens), MIA3 (for TUI clients), or MIA4 procedure (for Servers) to generate the COBOL sources to be used upon the migration process. These sources contain the code generated from the instance design only.
The user input of the procedure can be retrieved from the MIBA or MIBR 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. |
get 'zFileName' c:\LocalFileName | Frame the name of the System z file with simple quotation marks (it defaults to 'tsouid'). |
quit |
Use the rpp --import command
line, or the import wizard accessed by right-clicking a location in
the Design Explorer view.
This step
initializes a local workspace with projects, structured into hierarchies.
Each project contains the entities of a Pacbase Library.
The rpp --importJournal command can be used to import updates that have been extracted from the Pacbase journal with the MIBJ procedure. This command can be executed only if you have previously made a classic import, after which is created a technical file that is required to import from the journal.
These steps create a script file for the SCM commands. The scmtools_entries.bat file is located by default in the .metadata folder of your workspace.
To validate this step, you can analyze the errors contained in the .pacmigration.log file of the .metadata folder of your workspace.
This step extracts all the sources of the Macros (macrocode.cblmsp in an XML format) from the file produced by the MIMA procedure. Then it puts this file into the same directory as the Macro model (macrocode.pacmacro).
Use the rpp --dispatchMacro command line, or the Macro dispatching wizard accessed by right-clicking a location in the Design Explorer view.
This step dispatches the Macros into the various projects of your local workspace.
Use the rpp --migrationHelp command line, or the help migration wizard accessed by right-clicking a Program, Screen or Server in the Design Explorer view.
This step recognizes the generated source files (GPRT, MIAn, ...) and populates the workspace.
When using Rational Team Concert builds, this step must be preceded by the creation of zComponent project and zFolder. In this case, you must indicate the location of the sources result of the migration help function.
Syntax: lrpp.bat [options] [subcmd] --generate - COBOL generation command. --import - Import command. --importJournal - Journal import command. --dispatchMacro - Command to dispatch Macros. --migrationHelp - Migration help command. --automaticMigration - Automatic migration command. --generateErrorMsgs - Command to generate error messages. --generateDataBlockBase - Command to generate Database Blocks. --generateCopyBook - Command to generate Copybooks. --compare - COBOL compare command. --copy - Command to copy files. --zCompCreation - Command to create z/OS components. --refresh - Commande to refresh the workspace. --commands - Command to execute a list of commands. --help - Displays this message. For more information on a specific command, type help command-name. --port - Port number (MUST be the last option). (required)
Use the rpp.bat --commands command line to perform several batch commands listed in a command file.
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.