IBM Support

PI37869: ABEND04E RC00E70005 DSNXIDDL.DSNXIDMN:P010 FROM DSNTIJEN AT STEP ENFM0001 AFTER REPORT39 ROWS ARE CLEANED UP AND SYSLINKS EXISTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • V10 DSNTIJPM report39 returned rows. Per report39 instruction,
    customer asked the lab to send jcl to clean up.  After customer
    ran the clean-up jcl, DSNTIJEN abends at ENFM001 step with
    ABEND04E RC00E70005 at DSNXIDDL.DSNXIDMN:P010 due to SYSIBM.
    SYSLINKS table still exists in customer's system even though
    customer is at V10 C9(conversion mode). SYSIBM.SYSLINKS table
    is supposed to have been dropped in V8; somehow this did not
    happen and caused the abend.
    keywords: DB2MIGV10/K DB2MIGV11/K
    

Local fix

  • When DSNTIJPM report39 returns rows, customer can run
    query SELECT * FROM SYSIBM.SYSTABLES WHERE CREATOR='SYSIBM' AND
    NAME='SYSLINKS' to verify if SYSIBM.SYSLINKS table exists.
    If it does, then no action is required because DSNTIJEN can
    handle this case.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users who are migrating to DB2 10        *
    *                 for z/OS or DB2 11 for z/OS.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect output from the following:    *
    *                      1. DSNTIJPB report27.                   *
    *                      2. DSNTIJPM report39 (DB2 Version 10    *
    *                         for z/OS) and report27 (DB2 Version  *
    *                         11 for z/OS).                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In DSNTIJPB and DSNTIJPM, there are queries on the
    SYSIBM.SYSRELS catalog table to identify orphan rows.
    These jobs incorrectly identify rows.
    

Problem conclusion

  • The SYSIBM.SYSRELS queries in DSNTIJPB and DSNTIJPM has been
    updated to correct the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37869

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-26

  • Closed date

    2015-07-30

  • Last modified date

    2016-01-04

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

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

    UI33438 UI33439

Modules/Macros

  • DSNTIJPB DSNTIJPM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI33438

       UP15/12/16 P F512

  • RB10 PSY UI33439

       UP15/12/16 P F512

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 January 2016