Migrating from DB2 V11 to DB2 V12 FL 100

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.




    What steps need to be taken for customers need to migrate from DB2 v11 to DB2 v12 FL 100?  The DB2 Customization Guide appears to show the steps for migrating to DB2 v12 FL 500.  What if a customer has to go to FL 100 first?


    Customers should refer to the BMC Products and Solutions for DB2 Customization Guide, Appendix A Migrating to a different version of DB2 on the BMC documentation website (docs.bmc.com). Please note that in the manual these tasks appear as necessary for FL500, but if you migrate to FL100 first and keep your DB2 Subsystem running at FL100 for some time, you need to run these Binds at FL100.

    1.- For the Administrative products that use static binds, when you migrate DB2 to V12 FL100, after you migrate DB2 Catalog, you need to run the binds from <hlq>.UBMCCNTL members

      • ACTssidP
      • DAAssidP or PS1ssidP
      • AEXssidP (Execution)
      • ACMssidP
      • ACSssidP
      • AEXssidP
    • DASD MANAGER     
      • ASUssidP
      • ACSssidP
      • ATSssidP
      • AEXssidP

    2.- Access the BMC Documentation website (docs.bmc.com) and Perform the tasks that are documented in the BMC Products and Solutions for DB2 Customization, Appendix A Migrating to a different version of DB2, under topic Completing the migration to a new version of DB2. For your convenience, below I copy an excerpt of this manual (in italics).

    Perform the following procedure to verify the values for the DB2EXIT and DB2LOAD libraries.

    1 Verify the values for the libraries in the product options file (POF).
        a Edit the POF in your HLQ.UBMCCNTL data set. The name of the file is specified in the POFDS
           keyword in the installation options module for your product.
        b Ensure that the values for the DB2EXIT and DB2LOAD keywords are correct for the version of DB2
           to which you have migrated.

    2 If you modified the values in the POF in step 1, refresh the POF. When you refresh the POF, users
       receive the updated values.
         a Edit the initial POF outside of the product.
         b Change the value of the POFDATE keyword to the current date.
        c Append the refresh attribute ,(R) to the values that you want to update.
        d Save the POF.
        e (for runtime data sets) Copy the POF from HLQ.UBMCCNTL to HLQ.BMCCNTL.

    3 Verify the values for the libraries in the control table.
        a Edit the control table in the HLQ.CONTAB data set.
        b Ensure that the location and name of the DB2EXIT and DB2LOAD libraries are
           correct for the version of DB2 to which you have migrated. For example:
          *LIB  SSID Data Set Name
           EXIT DB11 'SYS3.DB11.DSNEXIT'           *
           LOAD DB11 'SYS2.DB2V11M.DSNLOAD'        *

    3.- For the Utility products that use dynamic binds, you can re-run the IVP installation job $770IVP and that will bind the dynamic packages, or you can wait until the product is used at which time an auto rebind is performed.

    4.- Finally, going from FL100 to FL500 does not necessarily require binds unless you are using AEXFLVL REXX to change the APPLCOMPAT for CATALOG MANAGER and CHANGE MANAGER to run at the higher Function Level. Also implementing any SPE that takes advantage of a particular Function Level will have HOLD DATA instructing you to bind.

    The AEXFLVL REXX program can be found on member HLQ.BMCCNTL(AEXFLVL) and the JCL includes the directions to run it.


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles