II07501: HINTS & TIPS FOR A SMOOTH DB2 VERSION 3 MIGRATION INCLUDING EXCERPTS FROM OCT. 1993 DB2 TECH. CONFERENCE & OTHER HINTS/TIPS

APAR status

• Closed as canceled.

Error description

• 1. Migration Planning
  A. Preventive Service Planning (PSP) Bucket Upgrade DB2310
       contains:
      * Program Directory Changes
      * Documentation Changes
      * General Hints
      * Hiper Maintenance
      * Cross Product Dependencies
     B. DB2 Program Directory
       * Minimum System Requirements
       * Distribution Tape Information
     C. End Support Date for V2.2 is September 30, 1993
  
  2. If a DB2 V2.2 to V2.3 Migration is Necessary refer to
     II05712 listing common install/migration problems especially
     A. Catmaint - migration job DSNTIJTC
     B. Fallback Procedure after Catmaint failure
  
  3. If Fallback from V3.1 to V2.3 is Necessary verify:
     A. UN90088 is the Small Programming Enhancement (SPE) needed
        to fall back to V2.3
     B. UN90088 includes the fix for PN16741/UN19000 on PUT 9204.
        *  UN19000 resolves the problem where START_RBA was
           incorrectly set as END_RBA for full image copies taken
           with SHRLEVEL change.
        *  Verify by entering: SELECT * FROM SYSIBM.SYSCOPY WHERE
           SHRLEVEL='C';
     C. Application programs may experience ABEND806 after
        fallback.  DSNTIA1 is now dynamically loaded by DSNTIAR.
        * Relink applications with V2.3 DSNLOAD
        * Include a Version 3 DSNTIA1 in STEPLIB
  
  4. ERLY Code Requirements
     A. Apply UN35452 to V2.3 to execute DB2 Version 3 with V2.3
        ERLY code
     B.  UN35452 has no effect on DB2 V2.3
     C.  All ERLY code maintenance requires an IPL to have it
         take effect.  Cannot STEPLIB to DSNLINK, LLA REFRESH,
         or STOP/START LLA to pick up ERLY code maintenance.
  
  5. DSNTINST 'Text not Found" message indicates the IBM target
     libraries SDSNCLST or SDSNSAMP have been modified.  These
     libraries are created when DB2 is installed.  The intention
     is that these libraries will only be modified by IBM.  The
     libraries should NOT be manually edited.
     A.  DSNTINST uses TSO/E edit subcommands FIND and CHANGE to
         customize JCL and CLISTs using parameters the customer
         supplied on the install panels.
     B.  The customized jobs are stored in prefix.NEW.SDSNSAMP.
     C. Search strings may not be found if SDSNSAMP is edited,
        causing the 'text not found' message.
     D. There are two methods to locate the cause of the 'text
        not found' message.
        * Execute DSNTINST with CONTROL(LIST) option.  Keep track
          of the member names as they are edited.  The member
          preceeding the 'text not found' message is the problem.
          Restore the member by copying it from the SDSNMACS
          library to the target library (SDSNCLST or SDSNSAMP).
        * As each member is edited, DSNT489I will be displayed
          with the member name.  Find the last DSNT489I message
          and refresh that member from ADSNMACS.
  
  6. Migration Steps
     A. Steps 10 (DSNTIJUZ), 12 (DSNTIJIN) and 13 (DSNTIJID) may
        be executed beforehand if no BSDS updates are necessary.
  
  7. Potential DSN1COPY error
     A. ABEND04E RC00C200C1 may result after copying a tablespace
        or index from one DB2 subsystems to another.
     B. Each page contains a log RBA in bytes 1-6 which must be
        consistent with the BSDS.
     C. Avoid this error by specifying PARM='RESET' when copying
        tablespaces or indexes.
  
  8. Access Method Services Failures
     A. For RC00D70025 errors, find the message pair
        DSNP009I/DSNP010I.  Inbetween these messages find IGD
        (SMS), IDC (AMS), or IEC (Data Management) error messages
        indicating the root cause.
     B. Error messages can be found in the DB2MSTR started task
        log.
  
  9. Potential problem with lock held flag settings
     A. ABEND04E RC00C90101 in DSNIMSAR vrace5003 during an SQL
        delete or update statement.  Need to apply APAR PN49506/
        PTF UN54705.
     B. Recovery and reorg of tablespace did not help to bypass
        the problem.
     C. Applying PTF UN52509 did not help either.
  
  10.  Distributed INSERT/UPDATE/DELETE  using two phase commit
  (IMS CICS): SYNCLVL=SYNCPT must be added to the APPL
  See DB2 Admin. Guide Vol. I SC26-4888-00 page 1-17 and 3-11
  
  Potential symptoms: SQLCODE = -919 SQLCODE = -817
  Additional search arguments: SQLCODE919 SQLCODE817 DRDA DB2DDF
  
  11. DB2 Version 3 DSNTIJIC image copy job was altered to make
      two job steps.  SYSUTILX must be in it's own job step to
      avoid locking contention.  Because of this additional job
      step the referback for volume will cause an A13-18 ABEND
      if your image copy spans mutiple tapes.  This is a MVS JCL
      allocation restriction.  If this occurs, users must alter
      DSNTIJIC to handle multiple tapes.  If your image copies
      fit on one tape, DSNTIJIC runs fine without changes.
  ================================================================
   Dallas System Center Flashes:
  DSSC FLASH 4005
  DB2 V3 - APP. DEV., INSTALLATION, AND MIGRATION CONSIDERATIONS
  .
  DSSC FLASH 2146
  DB2 V2R3 CCSID 037 VS DEFAULT OF 500: HAVE YOU COMPROMISED
  DATA INTEGRITY?
  .
  DSSC FLASH 3080
  I/O SCHEDULING ENHANCEMENT FOR DB2
  .
  DSSC FLASH 3101
  QMF 3.1.1 RESTRICTION ON EXPLOITING I/O PARALLELISM IN DB2 V3
  
  DSSC FLASH 3102
  DB2 VERSION 3 - MIGRATION CONSIDERATIONS FOR DSNTIAR
  ================================================================
  DSNTIAR now calls a new routine of DSNTIA1 starting in DB2 3.1.
  If you had used the DFSESL DD statement for SDSNLOAD as
  referred to on 2-289 in the Admin Guide, you need to define
  the load library (SDSNLOAD) in STEPLIB (JOBLIB etc.) as well
  or else DSNTIA1 will not be found. If DSNTIA1 can not be
  found you will receive msgCSV003i DSNTIA1 not found.
  ================================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSED FOR RETENTION
  DB2INFO
  

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