PM04968: NEW FUNCTION FOR PREMIGRATION CHECKOUT

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • new function for premigration
    
    DB2MIGV10/K  DB2COEXIST/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 UDB for z/OS Version 8 and DB2 Version   *
    *                 9.1 for z/OS System Administrators are       *
    *                 affected by this change.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Provide a DB2 Version 10 for z/OS       *
    *                      premigration checkout job in DB2 UDB    *
    *                      for z/OS Version 8 and DB2 Version 9.1  *
    *                      for z/OS.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Beginning with DB2 V6, each release of DB2 provides a job called
    DSNTIJPM that can be run on the prior release to help identify
    conditions that can impede migration to the new release.
    
    To allow customers maximum time to prepare for migration to a
    new release, the DSNTIJPM job is shipped under a different name
    in the previous release.  For example:
    - the V8 DSNTIJPM is shipped as DSNTIJP8 in V7
    - the V9 DSNTIJPM is shipped as DSNTIJP9 in V8
    This arrangement permits customers to begin preparing for
    migration in advance of buying and SMP/E-installing the new
    version.
    
    This APAR adds the V10 DSNTIJPM job to DB2 V8 and V9 under the
    name DSNTIJPA.  DSNTIJPA generates the following reports:
     (1) Check for previous-release sample database
     (2) User-defined indexes that reside on user-managed storage
         and are defined on DB2 catalog tables that are processed
         during enabling-new-function mode
     (3) User-defined indexes that reside on DB2-managed storage
         and are defined on DB2 catalog tables that are processed
         during enabling-new-function mode
     (4) Stored procedures that use the DB2 SPAS
     (5) Plans that are autobind candidates in V10
     (6) Packages that are autobind candidates in V10
     (7) Use of external module DSNWZPR
     (8) Incomplete table definitions
     (9) Incomplete column definitions
    (10) Occurences of the DSN_PTASK_TABLE explain table with one
         or more column names that contain a hashmark character
    (11) Plans that contain DBRMs
    (12) Plans bound with ACQUIRE(ALLOCATE)
    (13) Static queries bound with query parallelism
    (14) EBDDIC explain tables
    (15) Explain tables that are not in current-release format
    (16) MQTs on the DB2 catalog that are affected by CATMAINT
    (17) MQTs on the DB2 catalog that are affected by CATENFM
    (18) Plans bound with DBPROTOCOL(PRIVATE) that can be
         converted to DRDA via REBIND PLAN
    (19) Plans bound with DBPROTOCOL(PRIVATE) that can be
         converted to DRDA via DSNTIJPD
    (20) Packages bound with DBPROTOCOL(PRIVATE) that can be
         converted to DRDA via REBIND PLAN
    (21) Packages bound with DBPROTOCOL(PRIVATE) that can be
         converted to DRDA via DSNTIJPD
    (22) Authorization IDs and roles that use EBCDIC-encoded
         routines for DBMD
    (23) Obsolete DB2-supplied objects
    (24) Packages that use UDF SYSFUN.DSN_XMLVALIDATE
    (25) Existence of inconsistent UTF-8 encoding of the
         collection IDs and the package names that were
         bound by a remote client system.
    
    Run DSNTIJPA as soon as possible on your DB2 V8 or V9 system in
    order to evaluate it for readiness for migration to DB2 Version
    10.
    
    DSNTIJPA uses DB2 REXX Language Support.  If you have not bound
    the packages and plans for DB2 REXX Language Support, use job
    DSNTIJRX to do so before running DSNTIJPA.
    
    Attention: Certain processing performed by this job requires use
    of a special package for DB2 REXX in collection id DSNREXX_500.
    Use DSNTIJPA job step DSNTIRX5 to bind this package and include
    it in the DSNREXX plan.  Before running this job step, ensure
    that you are authorized to create packages in the DSNREXX_500
    collection id and to bind the DSNREXX plan.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM04968

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-12

  • Closed date

    2010-04-22

  • Last modified date

    2011-02-19

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

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

    UK56305 UK56306

Modules/Macros

  •    DSNTIJPA DSNTINS1
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK56305

       UP10/05/07 P F005

  • R910 PSY UK56306

       UP10/05/07 P F005

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

8.0

Reference #:

PM04968

Modified date:

2011-02-19

Translate my page

Machine Translation

Content navigation