IBM Support

II13695: DB2 V7.1 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 V8.1 AND UPGRADING R710

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ============================================================
    SECTION 1:   Toleration, Coexistance and Compatibility PTFs.
    ============================================================
                         5740XYR00 R810
    DB2 V7.1 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 V8.1
                       AND UPGRADE V710
     FOLLOWING PTFS ARE REQUIRED FOR DB2 V7.1 & V8.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 load modules are needed for processing.
    PQ48486/UQ81009(0310) Toleration of fallback from DB2 Version 8
    ......
    PQ84421/UQ85439(0403) adds a new job DSNTIJP8 to V7.
    Customers should run this job in V7 to identify
    concerns that need to be resolved before migrating to V8.
    .......
    Current DB2 V8 Unicode Services Requisites are Unicode APARs:
    OW56073 and OW56074 (z/OS 1.4 only -- fixed in 1.5 and above).
    OA03519, OA04069 and OA04043 also highly recommend for z/OS 1.4
    and 1.5 (fixed in 1.6 and above).
    OA16420 recommended on z/OS 1.7
    Abend0c4 rc38, abend0c1, abend04e rc00e80100 in DSNYECTE
    Unexpected SQLCODE +100 (SQLCODE100) running DSNTEP2 or
    COBOL program
    can occur if above maintenance is not applied.
    DSNYSIRM DSNTSTRT called CUN4LCNV routine.
    .
    OA19072 recommended on z/OS 1.7 and 1.8 for
    symptom:
    MSGDSNT552I DSNZINIT CHARACTER CONVERSION FROM CCSID  XXXX TO
    CCSID XXXX FAILED WITH ERROR CODE 24 STARTING MULTIPLE DB2
    ASIDS.
    when starting multiple DB2 members at the same time.
    .
    OA10699 (PE/Y and HIPER/Y) recommended for symptom:
    Distributed/remote applications getting intermittent ABEND0C4
    with messages MSGDSNL027I and MSGDSNL028I.
    ..........
    When executing the ++HOLD action for UQ81009, SDSNLOAD will
    need to be added to the ADSNLOAD concatination before ADSNLOAD
    in step DSNTIZQ.
    ..........
    If migrating a Data Sharing environment, UQ81009 does not need
    to be APPLY'd on all members simultaniously. However, UQ81009
    does need to be APPLY'd to all members before migrating to DB2
    V8, and before starting V8 code.
    ..........
    For migration to Version 8, job DSNTIJSG presumes you have both:
    (1) applied PQ62695/UQ72083 (adds the JDBC and ODBC metadata
        stored procedures) to DB2 V7
    (2) Created the DSNATPDB database for these stored procs in V7,
        by running either job DSNTIJMS or job DSNTIJSG (at the
        UQ72083 maintenance level or higher).
    If you haven't then you either need to do so before commencing
    migration to V8 or you need to remove all BIND PACKAGE(DSNASPCC)
    statements from your customized copy of V8 DSNTIJSG.
    *Post V8 GA customers can ignore the ++HOLD text for PTF UQ80157
    --------------------------------------------------------------
    The PTF for HIPER APAR PK04726 should be applied to V8
    before migrating to avoid truncation of view definitions
    that contain national characters in SYSVIEWS in NFM.
    If you have already migrated to V8 NFM and find you do
    have truncated view definitions in your DB2 catalog, please
    contact IBM Service to get a usermod to correct these
    view definitions.
    --------------------------------------------------------------
    Before migrating to NFM (new function mode), apply these fixes:
    PK05421/UK03239
     When in ENABLE NEW FUNCTION MODE ENFM, a REORG gets
     DSNU777I and TS will be set in COPY PENDING
    PK18164 UK11738
     Abend04E 00C90101 5005 (ERQUAL5005 VRACE5005) on SPT01
     occurs after going to DB2 V8 NFM
    HIPER PK34517/UK21071 should be applied before
    running DSNTIJNE (ENFM) to avoid corrupting the
    directory DSNDB01.SPT01.
    --------------------------------------------------------------
    The following apars report CATMAINT problems during migration
    from DB2 710 to 810:
    .
             *R710*   *R810*
    PQ86572           UQ87166 sup UQ88628
    PQ90772           UQ91069
    PQ92130  UQ93542  UQ93543
    PQ97172           UQ96520 sup UK03239
    PQ99507  UK00289  UK00290 sup UK01774 (710) UK01775 (810)
    PK01896  UK02636  UK02637
    PK02428  UK01774  UK01775
    PK04997           UK03365 *HIPER*
    PK06413  UK05958  UK05959
    PK07107           UK05955
    PK12280           UK08355
    --------------------------------------------------------------
    ------------------------------------------------------------
    -- ABEND04E at DSNXEBR :M300 when NOT using DSNTIAUL, please
       see apar PK21018
    -- ABEND04E at DSNXEBR :M300 when using DSNTIAUL, please
       read following information:
    .
    The DSNTIAUL sample unload program provided with DB2 Version
    8 uses a new-function feature called multiple row fetch
    (cursor with ROWSET) for enhanced performance.  You need to
    bind DSNTIAUL with the DBPROTOCOL(DRDA) option in order to
    retrieve data from a remote site using the multi-row fetch
    capability.  To retrieve data from a remote site when
    DSNTIAUL is bound with the DBPROTOCOL(PRIVATE) option, you
    need to switch DSNTIAUL to single-row fetch mode by
    specifying 1 for the DSNTIAUL "number of rows per fetch"
    parameter.  For example:
    DSN SYSTEM(DSN)
    RUN  PROGRAM(DSNTIAUL) PLAN(DSNTIB81) PARMS('SQL,1')
    See the discussion of DSNTIAUL in Appendix D of the DB2 V8
    Utilities Guide and Reference for more information about the
    "number of rows per fetch" parameter.
    .
    Additional search keywords: AB04E M300 OFFSETM300
    ------------------------------------------------------------
    ============================================================
    SECTION 2:   Required z/OS Unicode Services conversion
                 definitions
    ============================================================
    DB2 V8 requires Unicode System Services conversion definitions
    between CCSIDs 37, 367, 500, 1047, 1200, 1208, and the ASCII and
    EBCDIC CCSIDs used by your system.  In particular, the following
    conversion definitions are required:
           CONVERSION <your sccsid>,00367,ER;
           CONVERSION <your sccsid>,01200,ER;
           CONVERSION <your sccsid>,01208,ER;
           CONVERSION <your sccsid>,<your asccsid>,ER;
    .
           CONVERSION 00367,<your sccsid>,ER;
           CONVERSION 00367,01200,ER;
           CONVERSION 00367,01208,ER;
           CONVERSION 00367,<your asccsid>,ER;
    .
           CONVERSION 01200,<your sccsid>,ER;
           CONVERSION 01200,00367,ER;
           CONVERSION 01200,01208,ER;
           CONVERSION 01200,<your asccsid>,ER;
    .
           CONVERSION 01208,<your sccsid>,ER;
           CONVERSION 01208,00367,ER;
           CONVERSION 01208,01200,ER;
           CONVERSION 01208,<your asccsid>,ER;
    .
           CONVERSION <your asccsid>,<your sccsid>,ER;
           CONVERSION <your asccsid>,00367,ER;
           CONVERSION <your asccsid>,01200,ER;
           CONVERSION <your asccsid>,01208,ER;
    .
        If your DB2 uses mixed-byte or double-byte CCSIDs for EBCDIC
        and ASCII then these further conversion definitions are
        required:
           CONVERSION <your sccsid>,<your mccsid>,ER;
           CONVERSION <your sccsid>,<your amccsid>,ER;
           CONVERSION <your mccsid>,00367,ER;
           CONVERSION <your mccsid>,01200,ER;
    .
           CONVERSION <your mccsid>,01208,ER;
           CONVERSION <your mccsid>,<your sccsid>,ER;
           CONVERSION <your mccsid>,<your asccsid>,ER;
           CONVERSION <your mccsid>,<your amccsid>,ER;
    .
           CONVERSION <your gccsid>,00367,ER;
           CONVERSION <your gccsid>,01200,ER;
           CONVERSION <your gccsid>,01208,ER;
           CONVERSION <your gccsid>,<your agccsid>,ER;
    .
           CONVERSION <your asccsid>,<your mccsid>,ER;
           CONVERSION <your asccsid>,<your amccsid>,ER;
    .
           CONVERSION <your amccsid>,<your mccsid>,ER;
           CONVERSION <your amccsid>,00367,ER;
           CONVERSION <your amccsid>,01200,ER;
           CONVERSION <your amccsid>,01208,ER;
           CONVERSION <your amccsid>,<your asccsid>,ER;
           CONVERSION <your amccsid>,<your sccsid>,ER;
    .
           CONVERSION <your agccsid>,<your gccsid>,ER;
           CONVERSION <your agccsid>,00367,ER;
           CONVERSION <your agccsid>,01200,ER;
           CONVERSION <your agccsid>,01208,ER;
    .
           CONVERSION 00367,<your mccsid>,ER;
           CONVERSION 00367,<your gccsid>,ER;
           CONVERSION 00367,<your amccsid>,ER;
           CONVERSION 00367,<your agccsid>,ER;
    .
           CONVERSION 01200,<your mccsid>,ER;
           CONVERSION 01200,<your gccsid>,ER;
           CONVERSION 01200,<your amccsid>,ER;
           CONVERSION 01200,<your agccsid>,ER;
    .
           CONVERSION 01208,<your mccsid>,ER;
           CONVERSION 01208,<your gccsid>,ER;
           CONVERSION 01208,<your amccsid>,ER;
           CONVERSION 01208,<your agccsid>,ER;
    .
        These further conversion definitions are
        required if the DSNHDECP SCCSID is not 37:
           CONVERSION 00037,00367,ER;
           CONVERSION 00037,00500,ER;
           CONVERSION 00037,01047,ER;
           CONVERSION 00037,01200,ER;
           CONVERSION 00037,01208,ER;
           CONVERSION 00037,<your asccsid>,ER;
           CONVERSION 00367,00037,ER;
           CONVERSION 01200,00037,ER;
           CONVERSION 01208,00037,ER;
           CONVERSION <your asccsid>,00037,ER;
    .
        These further conversion definitions are
        required if the DSNHDECP SCCSID is not 500:
           CONVERSION 00500,00037,ER;
           CONVERSION 00500,00367,ER;
           CONVERSION 00500,01047,ER;
           CONVERSION 00500,01200,ER;
           CONVERSION 00500,01208,ER;
           CONVERSION 00500,<your asccsid>,ER;
           CONVERSION 00367,00500,ER;
           CONVERSION 01200,00500,ER;
           CONVERSION 01208,00500,ER;
           CONVERSION <your asccsid>,00500,ER;
    .
        These further conversion definitions are
        required if the DSNHDECP SCCSID is not 1047:
           CONVERSION 01047,00037,ER;
           CONVERSION 01047,00367,ER;
           CONVERSION 01047,00500,ER;
           CONVERSION 01047,01200,ER;
           CONVERSION 01047,01208,ER;
           CONVERSION 01047,<your asccsid>,ER;
           CONVERSION 00367,01047,ER;
           CONVERSION 01200,01047,ER;
           CONVERSION 01208,01047,ER;
           CONVERSION <your asccsid>,01047,ER;
    .
    See Info APARs II13048 and II13049 for guidance and
    assistance with setting up z/OS Unicode Services for DB2.
    -------------------------------------------
    If you are using the default codepage for Enterprise COBOL you
    need to add the 1140<->1208 conversion.
    See Chapter 4 in the Enterprise COBOL Customization Guide 3.3
    (GC27-1410-03) for information about Unicode. The best source is
    the Unicode manuals listed in that chapter.
    
    COBOL manuals can be found at:
    http://www.ibm.com/software/awdtools/cobol/zos/library/
    ...........................................................
    If customer experiences S0C1 abend after running CATMAINT;
    please have them check their AUTHORIZATION EXITS routines and
    any results from running a DSNTIJEX (optional) job.
    abend0c1 s00c1 s0c1
    ...........................................................
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • close
    

APAR Information

  • APAR number

    II13695

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-10-03

  • Closed date

    2004-09-29

  • Last modified date

    2007-02-01

  • 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

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]

Document Information

Modified date:
04 March 2021