IBM Support

PI33871: NEW FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New Function
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS users migrating to DB2   *
    *                 12 for z/OS.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Toleration of fallback from DB2 12 for  *
    *                      z/OS.                                   *
    *                                                              *
    *                      In a Data Sharing environment, required *
    *                      for coexistence of DB2 12 for z/OS with *
    *                      DB2 11 for z/OS.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR must be applied to all members of a data sharing
    group and DB2 11 started on all members before one of
    the members can be started with DB2 12 to migrate the
    DB2 catalog. Non-data sharing DB2 subsystems must also run
    with this APAR before attempting to migrate to DB2 12.
    
    This APAR allows fallback to DB2 11 after a migration to DB2 12
    and also allows release coexistence in a data sharing
    environment.
    
    Refer to the DB2 12 publications for procedures
    for migration and then subsequent fallback to DB2 11.
    

Problem conclusion

Temporary fix

Comments

  • The purpose of this APAR is to allow fallback from DB2 12.
    Refer to the chapters 'Falling back' and 'Remigrating'
    in the DB2 12 Installation Guide for this procedure.
    
    ++HOLD COMMENT FOR RELEASE B10, TYPE ACT:
    After applying this PTF, you need to re-assemble and linkedit
    DSNHDECP to pick up the changes in DSNARIB. Under DB2 data
    sharing, if each member of the group has its own DSNHDECP module
    then you need to repeat the steps below for each member.
    
    These are the steps to update DSNHDECP:
       (1) Create a separate job containing only the DSNTIZP and
       DSNTIZQ steps from the job DSNTIJUZ previously edited
       by the install CLIST.
       (2) Re-assemble and linkedit the DSNHDECP load module
       by running your newly created job to produce a new
       DSNHDECP.
       (3) Stop and start your DB2.
    
    Additional Keywords:
    DB2MIGV12/K
    

APAR Information

  • APAR number

    PI33871

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-30

  • Closed date

    2016-10-14

  • Last modified date

    2016-11-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • DSNARIB  DSNGEDLC DSNRRPRC DSNTSTR2 DSNUECMI
    DSNUECM2 DSNUESCM DSNUEXDB DSNUGMAP DSNXCATL DSNXCOBC DSNXKFUN
    DSNXLDBD DSN7GCMD
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI41695

       UP16/10/20 P F610

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 May 2020