PK11129: NEW FUNCTION

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• New function
  
  DB2MIGV9/K  DB2COEXIST/K
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 V8 users migrating to V9.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Toleration of fallback from DB2         *
  *                      Version 9 (R910).                       *
  *                                                              *
  *                      In a Data Sharing environment,          *
  *                      required for coexistence of             *
  *                      V8R1 and V9R1.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR must be applied on DB2 V8R1 and DB2 V8R1 must be
  stopped and restarted prior to starting migration to DB2 V9R1.
  
  This APAR must be applied to allow fallback to DB2 Version 8
  Release 1 of DB2 (8.1) after a migration to DB2 Version 9.
  Refer to the DB2 Version 9 publications for procedures
  for migration and then subsequent fallback to DB2 Version 8.
  
  This APAR must be applied to all members of a Data Sharing
  group and DB2 V8R1 started on all members before one of the
  members can be started with DB2 Version 9 to migrate the DB2
  catalog. Non-data sharing DB2 subsystems must also run with
  this fallback SPE before attempting to migrate to DB2
  Version 9.
  

Problem conclusion

Temporary fix

Comments

• The purpose of this APAR is to allow fallback from Version 9.
  Refer to the chapter 'Falling back and Remigration' in the DB2
  Version 9 Installation Guide for this procedure. This APAR
  prereqs all of the fallback APARs.
  
  ++HOLD COMMENT FOR RELEASE 810, 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 V8.
  
  See INFO APAR II14224 for more information.
  ž**** PE07/02/09 FIX IN ERROR. SEE APAR PK33664  FOR DESCRIPTION
  ž**** PE07/03/27 FIX IN ERROR. SEE APAR PK39850  FOR DESCRIPTION
  ž**** PE07/02/13 FIX IN ERROR. SEE APAR PK38799  FOR DESCRIPTION
  ž**** PE07/06/27 FIX IN ERROR. SEE APAR PK44884  FOR DESCRIPTION
  ž**** PE09/03/20 FIX IN ERROR. SEE APAR PK74494  FOR DESCRIPTION
  

APAR Information

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

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

  UK90008

Modules/Macros

• DSNACA70 DSNARA70 DSNARIB  DSNDMRIC DSNDRIB
  DSNECP12 DSNGEDLC DSNHDECP DSNRRPRC DSNRRSBS DSNTSTR2 DSNUECM2
  DSNUXOBD DSNXCATL DSNXLDBD DSNXLVCM DSNXSDBI DSNX9RIB
  

Fix information

• Fixed component name

  5740 IBM DATABA

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK90008

     UP06/10/17 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.