IBM Support

PI35030: DSNX881I OCCURS REPEATEDLY WITH MISSING INFORMATION

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2IDAA defect pi35030 dpi35030
    dsnx881i repeatedly issued with missing information
    **************************************************************
    Additional Symptoms and Keywords:
     IDAA  IDAAV2R1/K IDAAV3R1/K IDAAV4R1/K
     DSNX881I MSGDSNX881I LOOP LP
    
     This APAR fix also happens to include a solution for a
     situation that is not related to IDAA.
     A remote, site1, client environment involves a DB2 Connect
     gateway that services some old clients that do not support
     DRDA Unicode traffic and some newer clients that do.
     A newer site1 client application accesses the DB2 z/OS
     server, site2, via the DB2 Connect Gateway. The application
     executes SQL that refers to yet another remote (hop)
     location, site3. Unicode traffic is correctly negotiated
     between site2/3 because the remote site1 client environment
     also supports Unicode traffic. The remote site1 application
     commits and so the site1/2 connection is therefore pooled by
     the client gateway environment.
     An older site1 client application accesses the DB2 z/OS
     server, site2, via the DB2 Connect Gateway. The existing
     site1/2 connection is reused by the gateway to service the
     client application but this site1/2 connection is
     renegotiated for DRDA EBCDIC traffic only. The application
     executes SQL that refers to the same remote (hop) location,
     site3. Because EBCDIC traffic is negotiated between site1/2,
     EBCDIC traffic is also negotiated on the site2/3 connection
     but the residual contents of a flag (DDAN_UNICODEMGR) is not
     reset and this incorrectly causes a Unicode DRDA ACCRDB
     RDBNAM value to be provided to site3. The site3 server
     detects the inconsistency and returns a DRDA VALNSPRM.
      Note: If the site3 server is also DB2 for z/OS, a DSNL032I
       message may be issued at site3:
       DSNL032I MSGDSNL032I REASON 00D35000 RC00D35000 ERROR ID
        DSNLZSEA0091 DSNLZSEA 0091
     As a result of receiving an unexpected VALNSPRM from site3,
     DB2 for z/OS site2 may issue the following message.
      DSNL031I MSGDSNL031I REASON 00D351FF RC00D351FF ERROR ID
       DSNLZRPA0001 DSNLZRPA 0001
     This will be followed by one of the following symptoms at
     site2:
     o ABEND04E AB04E S004E 04E
        04E-00D3440B 00D3440B RC00D3440B
         DSNLXRCN DSNLXRCN:0007 0007 ABNDID0007 VRADC0007
       If a site2 stored procedure caused the site3 access.
     o SQLCODE -30073 SQLCODE30073 SQL30073N
        DSNLTAC1 00D300F6 RC00D300F6 00001006
       is generated and returned to the site1 client application.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 and 11 for z/OS users who use     *
    *                 IBM DB2 Analytics Accelerator.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unpredictable symptoms including loop   *
    *                      of DSNX881I messages.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an accelerator major version is downgraded, DB2 does not
    reset internal indicators reflecting the version support.  As
    a result, DB2 may send a monitor related request that is no
    longer supported by the (down level) accelerator version.  This
    subsequently causes DB2 to use an invalid address representing
    the monitor reply.  The incorrect reply reference may lead to
    unpredictable results including repeated (loop) occurrences of
    an empty DSNX881I message.
    

Problem conclusion

  • DB2 has been changed to reset Accelerator connection indicators
    after each new connection in order to make sure DB2 does not
    send an incorrect monitor request to an accelerator that may no
    longer support the request.  DB2 will also validate that a
    monitor reply is successfully returned.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI35030

  • 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-02-13

  • Closed date

    2015-04-14

  • Last modified date

    2015-10-12

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

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

    UI26749 UI26750

Modules/Macros

  •    DSNLZREX DSNX8API DSNX8EKG
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI26749

       UP15/06/05 P F506

  • RB10 PSY UI26750

       UP15/06/05 P F506

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.



Document information

More support for: DB2 for z/OS

Software version: A10

Reference #: PI35030

Modified date: 12 October 2015


Translate this page: