Migrate Objects Quickly

You can quickly specify Db2 objects and their related objects for migration
You can use the Quick Migration option to quickly specify Db2 objects and their related objects for migration. This option generates JCL that creates a Quick Migration strategy (Q-type) named QUICKM and analysis output when the JCL is submitted. You can save the generated JCL into a data set so that it can be edited and reused as a z/OS batch job. In a batch environment, you can customize the input parameters, especially the Db2 objects that are to be processed, and repeat the analysis.
2
2
Perform a Quick Migration
Use the following procedure to quickly specify Db2 objects and their related objects for migration.
  1. Complete the following steps on the RC/Migrator Main Menu:
    1. Specify the source Db2 subsystem that contains the Db2 objects to be migrated in the
      DB2 SSID
      field. Use a question mark (?) to select from a list of subsystems.
    2. Type
      4
      (Quick Migration) in the
      OPTION
      line and press Enter.
    The Quick Migration Services panel appears.
  2. Complete the following fields to specify the objects for migration:
    • For
      Object
      , specify the object type. You can specify more object types after each selection is completed.
    • For
      Name
      , specify the name of the object or specify selection criteria to select from a list of objects.
    • For
      Creator
      , specify the creator/schema name of the object or specify selection criteria to select from a list of objects.
    • (Optional) For
      Where
      , specify Y to display the Extended Query Facility (EQF), which enables specification of more SQL selection criteria.
    Press Enter to process your entries.
    The Object Selection panel appears.
  3. Type
    S
    to select the objects that you want to include in the Quick Migration strategy. Press the END key (F3) to process your selections.
    The Quick Migration Services screen reappears and displays a list of objects that is based on your selections.
  4. Enter the following commands in the
    Cmd
    column to affect the objects you have selected for migration:
    • A (All)
      Include all related objects (parents and children). The implode/explode fields for the object are set to Y.
    • D (Delete)
      Delete an object from the quick migration.
    • E or X (Explode All)
      Include all exploded objects. The explode fields for the object are set to Y.
    • I (Implode All)
      Include all imploded objects. The implode fields for the object are set to Y.
    • N (None)
      Do not include imploded or exploded objects. The implode/explode fields are set to N for this object.
    • V (Version)
      Toggle between viewing or not viewing versions of a native stored procedure or a compiled SQL scalar function.
    The selected objects are ready for migration.
  5. Repeat steps 2 through 4 to include more objects in the migration, or press the END key (F3) or type END to process your selections.
    The Quick Migration Analysis panel appears.
  6. Specify the analysis options for your quick migration and then specify the execution mode to begin the analysis in online or batch mode:
    • Online mode
      The migration commands are written to the specified data set or to an RC/Migrator managed table. Review the analysis messages when the analysis has completed.
    • Batch mode
      The Batch JCL Specification panel appears. Enter the information for the batch job. Then submit the job, save it in a data set, or preview/edit it and then submit it.
      You can edit the JCL that is saved in a data set outside of the RC/Migrator online environment. Submitting the JCL creates and analyzes a Quick Migration strategy in batch.
      For more information about editing this data set, see Quick Migration JCL Statements. For more capabilities that are available only to a z/OS Quick Migrate batch job submission, see Quick Migration Batch Only Options.
    In online and batch mode, a Quick Migration strategy that is named QUICKM and analysis output is created. The strategy appears as type Q on the RC/M Strategy Services panel (option 1 on the RC/Migrator Main Menu). The analysis output data set contains the Batch Processor commands, DDL, and DCL to perform the migration.
  7. Submit the analysis output as a batch processor script to migrate the objects. For more information, see Define and Execute Refined Batch Processor Scripts.
Quick Migration JCL Statements
The Quick Migration generates JCL statements and parameters in a data set that you can edit. After the data set has been edited, you can submit it as a normal batch job for execution to create a Quick Migration strategy with analysis output. Sample JCL follows:
//USER1B JOB (TD20-230-BAT),'name',CLASS=A, // MSGCLASS=Z /*JOBPARM ROOM 21 //* //ANALYZE EXEC PGM=PTLDRIVM,REGION=4M,PARM='[email protected]' //STEPLIB DD DISP=SHR,DSN=hlq.CDBALOAD // DD DISP=SHR,DSN=hlq.DSNEXIT // DD DISP=SHR,DSN=hlq.DSNLOAD //PTILIB DD DISP=SHR,DSN=hlq.CDBALOAD // DD DISP=SHR,DSN=hlq.DSNEXIT // DD DISP=SHR,DSN=hlq.DSNLOAD //PTIPARM DD DISP=SHR,DSN=hlq.CDBAPARM //MSGFILE DD SYSOUT=* //REPFILE DD SYSOUT=* //ABNLIGNR DD DUMMY SUPPRESS ABENDAID DUMPS [1] //DDLFILE DD DISP=SHR,DSN=USER01.KAT.TEST(DATAQ) [2] //PARMFILE DD * [3] CREATOR USER1 [4] QUICKM [5] TABLESPACE EJDB EJTS [6] IMPLODE DATABASE IMPLODE STOGROUP [7] EXPLODE TABLE EXPLODE INDEX EXPLODE VIEW EXPLODE SYNONYM DATABASE PDJISK EJDB6 IMPLODE STOGROUP EXPLODE TABLESPACE EXPLODE TABLE EXPLODE INDEX EXPLODE VIEW EXPLODE SYNONYM [8] QUICKEND [9] STRTSSID ssid [10] TOSSID ssid HEADER [11] GLBLNAME MYGCS GLBLCRTR PDJISK DBCR PDJISK DVFJSK DBNM EJDB6 EDVB6
A description of the JCL statements follows:
  • [1] DDLFILE
    Specifies the analysis output file that contains the generated DDL and possible other control statements.
  • [2] PARMFILE
    Specifies the file that provides input control parameters. Typically, this file is an in-stream file as shown in this example.
  • [3] CREATOR
    Specifies the strategy user ID of the creator.
  • [4] QUICKM
    Specifies that a Quick Migration strategy is to be created. The lines between the keywords QUICKM and QUICKEND identify the objects to be migrated. You can replace the QUICKM keyword with QUICKME (EXPLODE), QUICKMI (IMPLODE), or QUICKMIE (IMPLODE/EXPLODE) to quickly include related objects in the migration strategy. For more information, see Quick Migration Batch Only Options.
  • [5]
    object-type
    object-creator/schema/database
    object-name
    object-version
    Specifies an object to migrate.
    Specify a three-or-four-element object line for each object to be migrated. You can add, delete, and edit these lines. In the sample JCL, the first object type is TABLESPACE, the related database name is EJDB, and the object name is EJTS.
    • object-type
      The type of the object. Valid values are: STOGROUP, DATABASE, TABLESPACE, TABLE, INDEX, VIEW, ALIAS, SYNONYM, SEQUENCE, TRIGGER, FUNCTION, and PROCEDUR.
    • object-creator/schema/database
      The creator/schema/database-name of the object. For TABLESPACE, this value is the related database name. For other objects, this value is the creator or schema name.
    • object-name
      The name of the object.
    • object-version
      The version of the object. This value is only valid for the following object types: TRIGGER, FUNCTION, and PROCEDUR.
  • [6] IMPLODE (optional)
    Specifies related parent objects that you want to include in the migration. If included, you must specify a separate IMPLODE line for each type of parent object that you want to include in the migration.
    The IMPLODE lines include related objects that are higher in the Db2 object hierarchy than the preceding object specification. For example:
    TABLESPACE EJDB EJTS IMPLODE DATABASE IMPLODE STOGROUP
  • [7] EXPLODE (optional)
    Specifies related dependent objects (children) that you want to include in the migration. If included, you must specify a separate EXPLODE line for each dependent object type to be migrated.
    The EXPLODE lines include related objects that are lower in the Db2 object hierarchy than the preceding object specification. For example:
    TABLESPACE EJDB EJTS IMPLODE DATABASE IMPLODE STOGROUP EXPLODE TABLE EXPLODE INDEX
  • [8] QUICKEND
    Indicates the end of the parameters identifying the objects to be migrated.
  • [9] STRTSSID
    Specifies the source Db2 subsystem.
  • [10] TOSSID
    Specifies the target Db2 subsystem.
  • [11] GLBLNAME and GLBLCRTR
    Specifies a global change set name and creator that contains individual global change specifications.
    When quick migrate JCL is generated, the global change set is added to the parameter file. In addition, the global change set is read and its individual global change specifications are extracted and added to the generated instream input parameter file. Normally, when the JCL is submitted, the global change set itself is ignored. See Quick Migration Batch Only Options for information about using the READGCS keyword to override this behavior.
Quick Migration Batch Only Options
In a batch environment, you can customize the Quick Migration data set input parameters to specify different Db2 objects that you want to include in the migration without having to repeat the process of generating the JCL from the Quick Migration panels. You simply change the input parameters in the job and then submit the job for execution.
You can use the following keywords in batch only to simplify the inclusion of related Db2 objects and global change specifications for the migrated Db2 objects:
  • QUICKME
    (explode all),
    QUICKMI
    (implode all),
    QUICKMIE
    (implode all and explode all)
    Use QUICKME, QUICKMI, or QUICKMIE to simplify the inclusion of related Db2 objects. These keywords:
    • Make it easy for you to include parent and dependent objects in the migration without knowing what they are.
    • Eliminate the manual and error-prone process of specifying individual IMPLODE and EXPLODE statements for each object type.
    When an output QUICKME, QUICKMI, QUICKMIE analysis is re-analyzed, it behaves as if it were a QUICKM Quick Migration strategy with the appropriate IMPLODE and EXPLODE statements that are included in the generated JCL.
  • READGCS
    (use a global change set)
    Use the READGCS keyword to simplify the inclusion of global change specifications in batch mode. When included in the job, this keyword enables global changes to be read from a global change set instead of being ignored.
    Normally, the global change specifications that are contained in a global change set are expanded directly into the input parameter file stream when JCL is generated from the Quick Migration panels. You can specify the READGCS keyword to force the global change set identified by the GLBLCRTR and GLBLNAME parameters to be read from the subsystem when the job is submitted.
    When the READGCS keyword is used, any input stream global change specifications continue to be supported and take precedence over the global change specifications that are read from the global change set.