II12652: DB2 V5.1 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 V7.1 AND UPGRADING R510

APAR status

• Closed as canceled.

Error description

• ============================================================
  SECTION 1:   Toleration, Coexistance and Compatibility PTFs.
  ============================================================
                       5740XYR00 R710
  
  DB2 V5.1 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 V7.1
                    AND UPGRADE R510
  
   FOLLOWING PTFS ARE REQUIRED FOR DB2 V5.1 & V7.1 BEFORE
  MIGRATION
  DB2 system administrator should take a back up from DB2
  environment (SMP/E, Active logs, BSDSs, DB2 Catalog/Directory)
  before applying maintenance.
  Remove any ZAPed (modified) DB2 module/s (lmod) by OEM from
  load libraries of a single DB2 subsystem or entire DataSharing
  group before starting DB2 with following maintenance.
  Vanilla IBM DB2 lmods are needed for processing.
  Non_DataSharing customers need to apply all PTFs in SECTION 1.
  Note: apply all the following PTFs plus their associated
        prereqs, fixing PTF (if PE'd) and superseding PTF/s.
  
  PQ34467 UQ90024 at 0011  Toleration of Fallback and coexistence
                           PTF for a DataSharing Environment.
                           PQ39555 has to be applied to all
                           members of a DataSharing group prior to
                           applying this PTF else entire group
                           needs to get upgraded and recycled.
                           Please recreate DSNHDECP after applying
                           this PTF.
  PQ43522 UQ49630 at 0101  0C7 DSNPDDSN+540 W/PQ37708 Abend0c7.
  PQ63042 UQ68817 at 0209  In a coexistence environment between a
  DB2 V5 and a DB2 V7, a CREATE VIEW statement on a V5 member will
  intermittently receive an incorrect SQLCODE -204.
  ===============================================================
  =======>      DB2 V7.1 PTFs which are necessary.       <=======
  ===============================================================
  PQ45328 UQ51254 at 0102  SQLCODE not returned for user defined
                           function.
  PQ47079 UQ53229 at 0104  To tolerate 00C900CF (ext password).
  PQ60865 UQ66468 at 0205  ABEND04E RC00E20003 IN DSNSVBK +05FC
  =============================================================
  SECTION 2: V710 DSNTIJIC (CATMAINT) issue.
  =============================================================
  1- All Views against SYSCOLDIST & SYSCOLDISTATS has to get
     Droped before CATMAINT processing if assocaited CATMAINT
     of PQ22051 did not get submitted.
     Following query helps to find out if PQ22051 CATMAINT
     was ran:
             SELECT NAME,TBNAME,LENGTH
             FROM SYSIBM.SYSCOLUMNS
             WHERE TBCREATOR = 'SYSIBM' AND
              TBNAME LIKE 'SYSCOLDIST%' AND
              NAME = 'COLVALUE';
  
    If the length returned is 254 then the catalog update for
  PQ22051 has not yet been made.
  
  2- If previous invocation of V710 CATMAINT is failed,
     DSNVVX01 & DSNVTH01 need to get Rebuilt under V510 before
     second invocation, if -DISPLAY DATABASE command shows those
     indexes are in REBUILD pending status.
  
  3- Before migrating from DB2 V5 to DB2 V7, you must ensure
  that there aren't any DB2 passwords nor any Type 1 indexes
  still remaining on the DIRECTORY.  To check for Type 1 indexes
  you can run DSN1PRNT with 'PRINT,FORMAT' parameters specified
  against the DB2 directory.  Locate PGFLAGS field from the index
  header page and if the value is '5C', then this indicates a Type
  1 index.  In this case, CATMAINT CONVERT TO TYPE 2 DIRECTORY
  must be ran (found in step 1 of DSNTIJXC job under V5 SDSNSAMP
  library).The directory will not be queried in DSNTIJPM pre-
  migration job/queries.  To determine if any DB2 passwords exist
  for the DB2 DIRECTORY, you can run DIAGNOSE DISPLAY OBD DSNDB01.
  DBD01 ALL.  From the FILE PAGESET record, begin at offset x'1A'
  and if the next 8 characters are anything other that x'00' or
  x'40', then there is a password.  It can be removed by using
  DSNJU003 utility and specifying SYSTEMDB TBLSPACE=DBD01.  The
  SYSTEMDB specification is valid for V6/V7 too, but does not
  appear to be documented in the Utility Guides for these releases
  of DB2.
  4. --  CATMAINT may fail for migration from V5 to either
  V6 or V7, with a -148 sqlcode (sqlcode148) if fieldprocs
  exist on either SYSCOLDIST or SYSCOLDISTSTATS columns, or
  if you have data capture changes (CDC) enabled for either
  or both tables.  You can run the following queries to
  determine if this is the case:
  SELECT NAME,TBNAME,FLDPROC
  FROM SYSIBM.SYSCOLUMNS
  WHERE TBCREATOR = 'SYSIBM' AND
  TBNAME LIKE 'SYSCOLDIST%' AND
  NAME = 'COLVALUE';
  to determine if fieldprocs have been defined.
  And, run the following to check for CDC:
  SELECT NAME,CREATOR,DATACAPTURE
  FROM SYSIBM.SYSTABLES
  WHERE CREATOR = 'SYSIBM' AND
  NAME LIKE 'SYSCOLDIST%';
  To turn off CDC, issue ALTER TABLE SYSIBM.SYSCOLDIST
  (SYSCOLDISTSTATS) DATACAPTURE NONE, to resolve this
  issue if 'Y' is present in DATACAPTURE column returned
  from above query.
  =============================================================
  SECTION 3: OS/390 and z/OS Unicode Conversion Services is
             required for DB2 V7 customers who use CCSIDs that
             are not already supported in SYSIBM.SYSSTRINGS
  =============================================================
  V7 PTF UQ74294 (fixes PQ56697) requires you to replace use
  of undefined (0) CCSIDs on your DB2 with defined CCSIDs.
  .
  After installing UQ74294 and specifying a defined CCSID for
  single-byte ASCII characters (ASCCSID), you may observe
  conversion errors (SQLCODE=-332) when using the SET CURRENT
  SQLID statement.  This error indicates that DB2 has no
  conversion definition to convert between your specified ASCII
  and EBCDIC CCSIDs.  The CCSIDs requiring conversion are
  identified in the DSNT408I SQL error message text, or in the
  SQLERRM field of the SQLCA.
  .
  DB2 traditionally provided its own character conversion maps
  in the SYSIBM.SYSSTRINGS table.  More recently, this capa-
  bility is provided by the OS/390 and z/OS Unicode Services
  feature.
  .
  Thus, for conversions that are not already supported in your
  SYSIBM.SYSSTRINGS table and not available in existing PTFs,
  you need to use the OS/390 and z/OS Unicode Services feature,
  and establish the required conversion definitions.  For
  guidance and further information on how to setup and use
  Unicode Services in conjunction with DB2, see info APARs
  II13048 and II13049.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Info APAR
  

APAR Information

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

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

Fix information

Applicable component levels