IBM Support

PI89903: NEW DSNL076I SERVICEABILITY MESSAGE FOR SQLCODE -30025 0600 CONDITIONS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DB2DDF DB2DRDA Story 67051 S67051
    New DSNL076I serviceability message for SQLCODE -30025 0600
    conditions.
    ***************************************************************
    Additional Symptoms and Keywords:
     DSNL076I MSGDSNL076I
     SQLCODE -30025 SQLCODE30025 SQL30025N SRN30025
      REASON CODE 0600 REASONCODE0600 REASON0600 RC0600
       CLIENTAPPLCOMPAT_INCONSISTENCY
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Distributed Data Facility (DDF) users.                   *
    * DB2 12 for z/OS only.                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * New DSNL076I companion message for                           *
    * SQLCODE -30025 reason code 0600                              *
    * (CLIENTAPPLCOMPAT_INCONSISTENCY)                             *
    * conditions.                                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available.                         *
    ****************************************************************
    As a component of the DB2 12 for z/OS Continuous Delivery
    model, a -30025 SQLCODE may be returned to remote IBM Data
    Server Client/Driver environments which is associated with a
    reason code 0600 (CLIENTAPPLCOMPAT_INCONSISTENCY) condition.
    This occurs when the remote clientApplCompat configuration
    property specification is inconsistent with the APPLCOMPAT
    value bound to the DB2 package.
    A companion serviceability message is required to reflect
    this condition.
    

Problem conclusion

  • In conjunction with -30025 SQLCODE conditions that are returned
    to remote IBM Data Server Client/Driver environments, a
    DSNL076I message will now be issued to the z/OS system console
    log.  The message identifies the remote client user and its
    environment and reflects the clientApplCompat value supplied by
    the remote client in conjunction with the associated DB2
    package name and its associated APPLCOMPAT value.
    A message suppression technique is utilized to prevent
    duplicate occurrences of the condition from flooding the system
    console.
    A new DSNL076I message is introduced with the following
    description.
    ---------------------------------------------------------------
    DSNL076I csect-name DDF CONNECTION REJECTED DUE TO
             INCOMPATIBLE APPLCOMPAT VALUES.
             LUWID=luw-id
             CLIENTAPPLCOMPAT=clientapplcompat-value
             PACKAGE APPLCOMPAT=package-applcompat-value
             PACKAGE=package
             THREAD-INFO=thread-information
    
    Explanation
    
    The remote client application environment specified an
    incorrect ClientApplCompat value relative to the APPLCOMPAT
    value associated to the package being executed. This message
    is issued in conjunction with an SQLCODE -30025
    CLIENTAPPLCOMPAT_INCONSISTENCY condition that is returned to
    the remote client application. See SQLCODE -30025 for more
    information.
    
    csect-name
        The name of the control section that issued the message.
    luw-id
        The logical unit of work ID of the thread.
    clientapplcompat-value
        The client application compatibility value that is
        provided by a client application:
          o For applications that use Java drivers,
            clientapplcompat-value is the value of the
            clientApplcompat Connection or DataSource property for
            the connection to the Db2 for z/OS data server.
          o For applications that use other clients or drivers,
            such as the CLI driver, clientapplcompat-value is the
            value of the ClientApplCompat configuration keyword.
        If the application does not provide a client application
        comptibility value, this value is an asterisk (*).
    package-applcompat-value
        The APPLCOMPAT bind option value for the package that was
        used to execute the first SQL statement in the application.
    package
        The collection ID, package name, and consistency token,
        delimited by a period (.), of the associated package.
    thread-information
        Information about the thread. The information is presented
        in a colon-delimited list that contains the following
        segments:
          o The primary authorization ID that is associated with
            the thread.
          o The name of the user's workstation.
          o The ID of the user.
          o The name of the application.
          o The statement type for the previously executed
            statement: dynamic or static.
          o The statement identifier for the previously executed
            statement, if available. The statement identifier can
            be used to identify the particular SQL statement. For
            static statements, the statement identifier correlates
            to the STMT_ID column in the SYSIBM.SYSPACKSTMT table.
            For dynamic statements, the statement identifier
            correlates to the STMT_ID column in the
            DSN_STATEMENT_CACHE_TABLE table. That statement might
            not have contributed to the current failure.
          o The name of the role that is associated with the
            thread.
          o The correlation token that can be used to correlate
            work at the remote system with work performed at the
            DB2 subsystem. The correlation token, if available, is
            enclosed in '<' and '>' characters, and contains three
            components, separated by periods:
              . A 3 - 39 character IP address.
              . A 1 - 8 character port address.
              . A 12 character unique identifier
    
        An asterisk (*) in any segment indicates that the
        information is not available.
    
    System action
    
    An SQLCODE -30025 CLIENTAPPLCOMPAT_INCONSISTENCY condition is
    returned to the remote client application and the remote
    connection is terminated.
    
    Operator response
    
    Notify the system programmer for analysis.
    
    System programmer response
    
    Contact the database administrator for assistance. If you
    suspect an error in Db2, you might need to report the problem.
    For information about identifying and reporting the problem,
    see Collecting diagnostic data.
    
    Problem determination
    
    Collect the following diagnostic items:
    
        Console output from the system on which the job was run,
        and a listing of the SYSLOG data set for the period of
        time that spans the failure.
        Query result of the SYSIBM.SYSPACKAGE catalog table for
        the collection ID (COLLID) and package name (NAME) values
        specified in the message.
    
    Database administrator response
    
    You can assist the remote client application user in resolving
    their problem. Action depends on the clientapplcompat-value
    value. If clientapplcompat reflects a value of * (asterisk), a
    client application compatibility value was not set for the
    remote application, but package-applcompat-value is greater
    than V12R1M500.
    clientapplcompat-value must be set when
    package-applcompat-value is greater than V12R1M500. To fix the
    problem, first determine whether the remote client or driver is
    at a level that supports client application compatibility.
    Then, take one of the following actions:
    
      o If the remote client or driver is at a level that supports
        client application compatibility, the remote client
        application compatibility for the application should be set
        to the value of package-applcompat-value.
      o If the remote client or driver is not at a level that
        supports client application compatibility, and it is
        possible to upgrade the remote client or driver, the remote
        client or driver should be upgraded. Then the client
        application compatibility for the remote application should
        be set to package-applcompat-value or lower.
      o If the remote client or driver is not at a level that
        supports client application compatibility, and it is not
        yet possible to upgrade the remote client or driver, bind
        or rebind the driver packages with APPLCOMPAT set to
        V12R1M500 or lower.
    
    You can use the DSNTIJLC job to bind copies of the driver
    packages, or the DSNTIJLR job to rebind the driver packages,
    at the correct application compatibility level.
    
    If you bind copies of the driver packages, the remote client
    must modify its configuration keyword or bind option that
    controls the current package set so that remote applications
    will use the correct set of driver packages.
    
    If clientapplcompat reflects a value other than * (asterisk),
    the clientapplcompat-value is greater than
    package-applcompat-value. clientapplcompat-value must be less
    than or equal to package-applcompat-value. Determine whether
    the remote client application uses any capabilities for which
    the minimum function level is greater than
    package-applcompat-value. Then take one of the following
    actions:
    
      o If the remote client application does not use any
        capabilities that require a higher application
        compatibility setting, the remote client application
        compatibility setting should be set to
        package-applcompat-value.
      o If the remote client application uses capabilities that
        require clientapplcompat-value, use a version of the IBM
        data server driver or client for which the package
        application compatibility is greater than or equal to
        clientapplcompat-value.
    
    Query SYSIBM.SYSPACKAGES to find existing IBM data server
    driver or client packages at the right application
    compatibility level. If no packages exist, bind or rebind
    driver or client packages. For drivers only, you can use the
    DSNTIJLC job to bind copies of the driver packages, or the
    DSNTIJLR job to rebind the driver packages, at the correct
    application compatibility level.
    
    If you bind copies of the driver packages, the remote client
    must modify its configuration keyword or bind option that
    controls the current package set so that remote applications
    will use the correct set of driver packages.
    ---------------------------------------------------------------
    Documentation changes will be included in the Information
    Management Software for z/OS Solutions Information Center
    (http://publib.boulder.ibm.com/infocenter/imzic) at a later
    date.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89903

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-07

  • Closed date

    2017-11-30

  • Last modified date

    2018-01-03

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

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

    UI52296

Modules/Macros

  • DSNLTACC DSNLZSEA DSNLXRSS DSNFCDIR DSNLTEXC DSNLTMIN DSNFLDIR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI52296

       UP17/12/15 P F712

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

Document Information

Modified date:
03 January 2018