Migrating from IMS Index Builder Version 2.3 to Version 3.1

IMS™ Index Builder Version 3.1 can execute IMS Index Builder Version 2.3 JCL.

About this task

When migrating from IMS Index Builder Version 2.3, several actions are required to best utilize IMS Index Builder Version 3.1 functionality.

To effectively migrate from IMS Index Builder Version 2.3 to Version 3.1, complete the following steps:

Procedure

  1. Modify the IMS Index Builder JCL.
    1. Concatenate the load libraries for related products to STEPLIB.

      If applicable, concatenate IMS Tools Knowledge Base load library to STEPLIB.

    2. Remove the SORTFSZ control statements.
      Important: The function of the SORTFSZ statement has changed. In IMS Index Builder Version 3.1, SORTFSZ is used to support heavy sort loads. SORTFSZ will also trigger striped sort mode.
    3. Optional: If you want to provide the sort file size for index sorts, use the INDEX statement.
      Important: For PSINDEX, the values for sort file sizes are valid for the whole index and not for the index partition as in IMS Index Builder Version 2.3.
    4. Optional: If you want to add the sort parameters for the sort program that runs in the master address space and in the subordinate address spaces, add the SORTOPT control statement.
    5. Optional: If you want IMS Index Builder Version 3.1 to issue the DBRC NOTIFY.UIC command to turn off the IC NEEDED flag, add the VIC YES control statement.

      For more information, see VIC control statement.

    6. Remove the ALTER, EXEC, NDXIOBF, SORTE15, SORTID, SORTOUT, and SORTSTAT control statements.

      These statements are provided in the IMS Index Builder JCL Version 3.1 by default.

    7. Optional: If you want to store IMS Index Builder reports in the output repository of IMS Tools Knowledge Base, add the ITKBSRVR control statement.

      The server name can be specified in the JCL or in the runtime parameters module.

    For more information, see JCL and input control statements.

  2. Define the subordinate address space procedure.

    Include the IIUBSRT started task procedure in PROCLIB.

    Notes:
    1. Do not use the IMS Index Builder Version 2.3 started task procedures because Version 2.3 procedures do not work with IMS Index Builder Version 3.1.
    2. In IMS Index Builder Version 3.1, the started tasks are activated by internally assigned job names. The started tasks procedure name is not used.
    3. If you want to add the sort parameters for the sort program that runs in the subordinate address space, specify the DFSPARM DD statement in the IIUBSRT started task procedure or specify the SORTOPT control statement in the IMS Index Builder JCL.

    For more information, see Defining the subordinate address space procedure.

  3. Optional: Define the runtime parameters.

    By defining the runtime parameters, you can override the default procedure name and the default job names that are used when starting subordinate address spaces, and the default high-level qualifier for stripe data sets.

    For more information about runtime parameters, see Defining runtime parameters.

  4. Optional: Specify the scan methods.

    IMS Index Builder Version 3.1 has adopted a new scan technology that runs several additional scan tasks and, by default, this scan technology is used. You can specify to use the scan methods that were used in IMS Index Builder Version 2.3. For more information, see Selecting the scan method.

  5. Define RACF® authorization.
    1. Establish security authorization for subordinate address spaces.
    2. Establish proper access to stripe data sets.

    See RACF considerations for more information.

  6. Optional: Configure the IMS Tools Knowledge Base server.

    For more information, see Configuring the IMS Tools Knowledge Base server.