IBM Support

PM24975: SQLCODE -30020 EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR REASON 1254 (0200)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2DRDA defect pm24975 dpm24975
    SQLCODE = -30020, ERROR:  EXECUTION FAILED DUE TO A DISTRIBUTION
     PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION:
    REASON 1254 (0200) returned from DB2 z/os server during Client
    Optimimzation Bind processing.
    The requested command encountered an unarchitected and
    implementation
    specific condition for which there was no architected message.
    **************************************
    Additional keywords and symptoms:
     Server may issue:
      MSGDSNT501I DSNT501I RC00C90082 00C90082 TYPE00000200
       00000200 DSNEXPLN.EXPTS
      RESOURCE UNAVAILABLE EXPLAIN table
     Requester system console:
      MSGDSNL031I DSNL031I DSNLZDJN DRDA EXCEPTION
       RC00D351FF 00D351FF ERRORID=DSNLZRPA001 DSNLZRPA0001
     SQLCODE30020 SQLCODE30020N SQL30020N SRCN30020 -30020
    CMDCHKRM
    ERRORCODE=-4499, SQLSTATE=58009
    

Local fix

  • no local fix/workaround
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: During DB2 remote BIND PACKAGE          *
    *                      processing, the following occurred:     *
    *                       . At the server, message DSNT501I      *
    *                         RESOURCE UNAVAILABLE condition       *
    *                         with REASON 00C0082, TYPE 00000200,  *
    *                         NAME DSNEXPLN.EXPTS                  *
    *                       . At the requester, message DSNL031I   *
    *                         DSNLZDJN DRDA EXCEPTION condition    *
    *                         with REASON 00D351FF and ERROR ID    *
    *                         DSNLZRPA0001                         *
    *                      ------------------------------------    *
    *                      The server returnsa DRDA exception      *
    *                      to the client without returning any     *
    *                      SQL error information needed by the     *
    *                      client to diagnose the server-side      *
    *                      error                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ---------------------------------------------------------------
    The remote requester specifies that EXPLAIN tables should
    be populated on the server as part of the BIND PACKAGE
    processing(via the EXPLAIN(YES) parameter).  When one
    or more of the required EXPLAIN tables is unavailable,
    the DB2 server correctly terminates the bind process
    and returns a DRDA exception to the requester.
    However, the DB2 server returns a DRDA exception
    (CMDCHKRM) which does not include the associated
    SQL error information (such as the SQLCODE -904).
    
    Note that any scenario that causes a bind process to
    terminate (for example, SQLCODE -904, -911, -913, etc.)
    can result in the server correctly returning a required
    DRDA exception, but not returning associated SQL error
    information needed for diagnosis.
    

Problem conclusion

  • DB2 for z/OS server processing has been changed to return
    a DRDA exception (SQLERRRM) that includes the specific
    SQL error information (including SQLCODE) for terminating
    errors that occur during the remote BIND PACKAGE
    processing.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM24975

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-21

  • Closed date

    2010-12-27

  • Last modified date

    2011-02-01

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

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

    UK63529 UK63528 UK63530

Modules/Macros

  • DSNLDICT DSNLXRCS
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK63528

       UP11/01/12 P F101

  • R810 PSY UK63529

       UP11/01/12 P F101

  • R910 PSY UK63530

       UP11/01/12 P F101

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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 February 2011