Rational Programming Patterns for System z

Extracting and migrating Pacbase data

You must extract and migrate the Pacbase users and development databases.

About this task

The following diagram shows the extraction and migration processes of Pacbase data.
Figure 1. Overall process
This diagram shows the extraction of the users and instances from Pacbase, the generation of the Macros and Programs and their transfer to the local workspace. It also shows the local generation and the transfer of the users and the instances (models and generated files) to the Rational Team Concert server.

Procedure

  1. Migrating the users
    1. Extract the users

      Extract and transfer all the users, from the administration database, with the MIUS, Pacbase procedure.

      This procedure extracts the identifiers, names, and email addresses of users.
      Note: This procedure is explained in the Pacbase installation guide specific to your operating system.

      Pacbase administrators are granted a JazzAdmins permission, whereas the other users are granted a JazzUsers permission.

    2. Import the users into Rational Team Concert™

      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

      where:
      • AsciiInputFile is the complete path to the file produced by the MIUS procedure. This file has an ASCII format.
      • Utf8OutputFile is the complete path to the file used as input to -createUsers, the standard command for the creation of users in Rational Team Concert: . This file has a UTF-8 format.
      Note: The AsciiToUTF8.bat file is designed to run from where it is delivered. So it is advised to keep it there. If you move it, you must modify it.
      To import the users, you must enter the standard command for creating users: -createUsers.
      Figure 2. Command lines for creating users
      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
      Note: The -createUsers command is explained in the Rational Team Concert help.

      The errors, if any, are displayed in the repotools-ccm_createUsers.log journal.

      A user already created is modified.
      Attention: The attempt to update the ADMIN user might end with a CRJAZ1350E error. So this code must not be reused.
  2. Migrating a development database
    1. Analyze a Pacbase database
      The MIAM procedure retrieves and completes some functions of the repository analysis:
      • Search for instance codes containing special characters or corresponding to a Windows® reserved word (for example: LPT1): Loading of the CS file.
      • Search for the Program instances (P) to be transformed into Macros: Loading of the PM file.
      • Search for the instances not to be retrieved (for example: Report for PDM layout): Loading of the NR file.
      • Loading of the RQ file with details of various searches (for example: list of the instances which contain a special character).
    2. Extract the data from Pacbase
      1. Extract the Pacbase models

        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.

        Note: These procedures are explained in the Pacbase installation guide specific to your operating system.
      2. Extract the Macros

        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).

        Note: This procedure is explained in the Pacbase installation guide specific to your operating system.
      3. Generate the Programs, Screens, and C/S entities

        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.

        This procedure:
        • Removes the line numbers,
        • Removes the content of columns 73 - 80,
        • Adds the level of the function or subfunction,
        • Ignores the COBOL formatting,
        • Includes the comments in the generation,
        • Takes the insertions of micropatterns into account.
        Note: This procedure is explained in the Developer's Procedures guide specific to your operating system.
      4. Generate the source control files for the Programs, Screens, and C/S entities

        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.

        Note: These procedures are explained in the Pacbase installation guide specific to your operating system.
    3. Transferring the result files
      Transfer the result files to the workstation on which the Rational® Developer for System z®, Rational Team Concert, and Rational Programming Patterns for System z clients are installed. You must transfer the files produced by the:
      • MIBA, MIBR or MIBJ procedure to a dedicated $DIRsrc directory. These files have a ta2 extension.
      • MIMA procedure to the $DIRsrc directory. These files have a cblmsp extension.
      • GPRT procedure to the $DIRsrc directory. These files have a cbl extension and are named after the external name of the generated instance.
      • MIA1, MIA2, MIA3, and MIA4 procedures to a dedicated $DIRctrl directory. These files have a .cbl extension and are named after the external name of the generated instance.
      Important: You must be careful with the code pages used upon the transfer.
      To transfer a file from a System z environment (English EBCDIC) to the workstation using FTP, you must enter the following lines in a file.scr file
      Table 1. FTP transfer commands to enter
      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  
      You can then enter the transfer command: ftp -s:file.scr.
    4. Populating the local workspace
      1. Convert the design files

        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.

      2. Dispatch the Macro source files

        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.

      3. Use the migration help function

        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.

      4. Utilities to populate the local workspace easily
        1. Run the batch process as a daemon
          Run the daemon with the rpp -–daemon command line and use thelrpp.bat script to communicate directly with the daemon.
          Note: The daemon can execute only one command at a time.
          Figure 3. Syntax of lrpp.bat
          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)
        2. Run more than one batch command in a command file

          Use the rpp.bat --commands command line to perform several batch commands listed in a command file.

          Figure 4. Syntax of rpp.bat
          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.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)