IBM Support

PI07515: SQLCODE4700 RETURNED FROM DB2 10 FOR Z/OS SERVER IN CM, CM* OR ENFM MODE to DB2 for LUW client

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as unreproducible in next release.

Error description

  • DB2DDF defect pi07515 dpi07515
    SQLCODE4700 is returned to a client that is running
    client software lower than DB2 for LUW V9.7 FP4
    connecting to a DB2 10 for z/os server that is running
    in any of the listed modes (CM8.CM9,CM8*,CM9*,ENFM).
    
    In the reported case, -4700 was returned from DSNHSM2V to a DB2
    for LUW 9.7 FP3 client that was using
    TIMESTAMP(6) in the failing sql.
    
    -4700 returned for V11 CM mode with JDBC driver at V10.5
    FP3/FP4 using getJccSpecialRegisterProperties
    
    
    Additional keywords and symptoms:
    --------------------------------
    SQLCODE4700 -4700
    DSNHSM2V
    DDFCOMPAT
    getJccSpecialRegisterProperties
    

Local fix

  • Customer needs to upgrade the client to appropriate level
    of software - DB2 for LUW V9.7 FP4 or higher
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: New DSN6FAC DDF Compatibility           *
    *                      specifications are required to help     *
    *                      users compensate for unexpected         *
    *                      behavior of remote client application   *
    *                      environments.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Users have observed unexpected behavior in remote client
    application environments where remote client environment
    related changes are necessary in order to tolerate or
    correct the situation.
    The following situations are considered:
    o Idle Thread Time-Out serviceability:
      When a DDF Idle Thread Time-Out event occurs, DB2 (DDF) will
      terminate the network connection and abort the work related
      to the idle transaction.  DB2 also returns companion
      serviceability information, in the form of a DRDA AGNPRMRM
      (AGeNt PeRManent error Reply Message) reply, to assist the
      remote client application environment in identifying the
      source, or cause, of the failed connection.
      Some remote client application environments are not prepared
      to tolerate the change in behavior that they may see as a
      result of this serviceability related reply.
      For example, remote client application environments may not
      be prepared to tolerate an ERROR CODE -1224 or SQL1224N that
      is returned instead of an ERROR CODE -4499 or SQL30081N that
      they may have been accustomed to.
    o Prior version dependency:
      Some remote client application environments may not be
      prepared to tolerate a new version of DB2, even when the
      DB2 (server) version is still operating in Conversion Mode.
      For example, this may lead to erroneous SQLCODE -4700
      conditions due to an incorrect attempt, by the remote client
      application environment, to utilize DB2 New Function that
      is not yet available.
    Remote client application environment changes are necessary
    to tolerate or correct the condition but these changes may
    take time to implement and/or deploy.  As a result, DB2 for
    z/OS changes are required to allow users to compensate for
    the condition and hence allow remote client application
    environments to continue operating until the necessary client
    environment related changes can be deployed.
    

Problem conclusion

Temporary fix

Comments

  • To help users bridge the gap until the remote client
    application environment adjustments can be made, DB2 will
    provide two new DSNZPARM DSN6FAC DDF_COMPATIBILITY keyword
    specifications:
    o Disable Idle Thread Time-Out serviceability:
      The DDF_COMPATIBILITY DISABLE_ITTO_EXCPTN specification can
      be used, perhaps in conjunction with other DDF_COMPATIBILITY
      specifications, to cause DB2 to sacrifice the Idle Thread
      Time-Out serviceability information that is normally returned
      to remote client application environments.
      This specification can be changed on-line.
      When this specification is provided, Idle Thread Time-Out
      events will cause the connection to be terminated only, and
      DB2 will not return companion serviceability information that
      identifies the source of the connection termination.
    o Prior version dependency:
      The DDF_COMPATIBILITY IDNTFY_Vnn_PRIOR_VER specification can
      be used, perhaps in conjunction with other DDF_COMPATIBILITY
      specifications, to cause DB2 to identify itself, and its DRDA
      functionality, relative to the prior version that DB2 was
      migrated from.
      This specification applies only to CM, ENFM, CM*, or ENFM*
      migration environments.  It does not apply once DB2 is
      migrated to NFM.
      This specification can be changed on-line.
      This specification allows remote client application
      environments to believe that they are still operating with
      the prior version of DB2 where the applications are known to
      behave correctly.
    Users should understand that these specifications are only
    intended to be a temporary measure until the remote client
    application environment can be modified to tolerate the
    condition.
    ž**** PE14/11/24 FIX IN ERROR. SEE APAR PI30243  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI07515

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-05

  • Closed date

    2014-08-20

  • Last modified date

    2015-06-19

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

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

    UI20718 UI20719

Modules/Macros

  • DSNDQWPZ DSNDQW02 DSNLCTRC DSNLTEXC DSNTIDXA
    DSNTIDXB DSNTINST DSNWZIFA DSNWZIFB DSN6FAC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI20718

       UP14/09/04 P F409

  • RB10 PSY UI20719

       UP14/09/04 P F409

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: 10.1

Reference #: PI07515

Modified date: 19 June 2015