IBM Support

PK65367: EXTENDED CORRELATION TOKEN SUPPORT (DK1082).

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • DB2DDF DDFL09 DB2SNA DB2HOP DB2DRDA
    DCR DK1082 Defect pk65379 dpk65379 111132 d111132
    Extended Correlation Token support (DK1082).
    ***********************************************
    Additional symptoms and keywords:
      DSNV448I MSGDSNV448I INDEX value duplicated if using SNA and
        hopping.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following conditions are reported:  *
    *                      . Extended Correlation information      *
    *                        received from remote clients is       *
    *                        not externalized.                     *
    *                      . Duplicate index values in Display     *
    *                        Thread Detail command report.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following conditions are reported:
    . Extended Correlation information received from remote clients
      is not externalized.
      The primary condition being reported concerns the ability
      to correlate work performed at a DB2 9 (for z/OS) server with
      work performed at remote client system.  Prior to DB2 9
      (for z/OS), the correlation of work was always accomplished
      by using the Logical Unit of Work Identifier (LUWID).
      The LUWID is basically an SNA term, however, DRDA makes
      provisions to allow the LUWID to be used between TCP/IP
      partners.  In this case, the LUWID can be effectively
      populated with the partner's IP address.
      This DRDA provision works well with IPv4 partners because
      the 32-bit (internal form - 8 hexadecimal digits) IP
      address can be made to fit very comfortably in the first
      component (8 characters) of the LUWID.  The basic message
      here is that LUWID based correlation of work could be
      utilized between TCP/IP IPv4 partners.
      DB2 9 (for z/OS) introduced support for IPv6, which extends
      an IP address to be 128-bit.  However, due to distributed
      Two Phase Commit (2PC) constraints, the LUWID could not be
      extended so the first component of the LUWID could no longer
      contain the IP address.  Some client systems require that
      the IP address be a component of their correlation design,
      and as a result, LUWID based correlation was no longer an
      option.
      Note: DB2 9 (for z/OS) client systems can still provide
        LUWID based correlation, even for TCP/IP IPv4 or IPv6
        connections, because the LUWID can still be constructed
        without an IP address.
        DB2 9 (for z/OS) typically requires a dependency to VTAM
        in which case the LUWID can still be populated with
        unique SNA Network ID and LU Name information.
        DB2 9 (for z/OS) also has the ability to be independent
        of VTAM, but in this case the LUWID can still be
        constructed with a unique name (IPNAME) provided by the
        user.
      Therefore, for the benefit of client systems that required
      IP address based correlation, the DRDA correlation token
      (CRRTKN) was enhanced to accommodate IPv6 addresses.
      This extended CRRTKN could be used for correlation purposes
      only and not for distributed 2PC purposes.  DB2 9 (for z/OS)
      does not currently externalize the extended CRRTKN value
      that may be received from remote client systems and as a
      result, SQL work performed at a DB2 9 (for z/OS) server
      system cannot potentially be correlated to the associated
      work at the remote client system, or application.  New DB2 9
      (for z/OS) function is necessary to externalize the extended
      CRRTKN received from remote clients in order to provide
      complete correlation of work between the two partners.
    . Duplicate index values in Display Thread Detail command
      report.
      When a DB2 9 (for z/OS) server system, site2, is accessed via
      SNA from another DB2 z/OS client system, site1, and
      application design causes a "hop" condition back to site1,
      the Display Thread Detail command report may contain
      DSNV448I (V448) messages with duplicated "INDEX" values.  The
      problem occurs because DB2 9 (for z/OS) Display Thread Detail
      processing is unable to distinguish the two different
      connections, inbound and outbound, with the same remote
      DB2 z/OS partner.
    

Problem conclusion

Temporary fix

Comments

  • The following changes are made:
    . Extended Correlation information received from remote clients
      is not externalized.
      New function is provided to externalize the extended CRRTKN
      information in the Display Thread command report and in
      trace records.
      - Display Thread.
        A new DSNV442I (V442) message is being introduced into
        the Display Thread Type(Active/Inactive) command reports.
        Please add the following message to the DB2 9 (for z/OS)
        Messages manual:
          DSNV442I V442-CRTKN=correlation token
          Explanation: This message appears in the output of the
          DISPLAY THREAD command. If the appropriate information
          is available, this message is issued and identifies a
          correlation token that may be used to correlate work at
          the remote system with work performed at the DB2
          subsystem. The correlation token contains three
          components, separated by a period.
          . A 3 to 39 character IP address.
          . A 1 to 8 character port address.
          . A 12 character unique identifier.
          The message number and subsystem recognition character
          are not included in the message. However, V442 is
          included in the message text to identify the message.
          System Action: Processing continues.
      - Trace records.
        The QWHC trace record correlation header (DSNDQWHC)
        will be changed to include the extended CRRTKN value.
        A new QWHCCTKN_Var character 128 variable length field
        will be added along with an associated QWHCCTKN_Off
        offset field to indicate where the variable length field
        can be found (relative to the beginning of the QWHC).
        A DSNDQWHS.QWHSSUBV value of 1 indicates that the QWHC
        has increased in size to accommodate QWHCCTKN_Off.
    . Duplicate index values in Display Thread Detail command
      report.
      DB2 9 (for z/OS) has been changed to properly distinguish
      the inbound and outbound connections from the same DB2 z/OS
      remote partner.
    

APAR Information

  • APAR number

    PK65367

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-30

  • Closed date

    2008-09-02

  • Last modified date

    2008-11-03

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

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

    UK39483

Modules/Macros

  • DSNDCCB  DSNDLACL DSNDQWHC DSNDQWUP DSNDTAB
    DSNFMDIR DSNFVDIR DSNFVDTA DSNLCLCN DSNLDTI2 DSNLEDDA DSNLEDPE
    DSNLEDTS DSNLSSST DSNLTACC DSNLTINT DSNVDRR  DSNVDT   DSNVDTA
    DSNVDTAD DSNVDTD  DSNVDTI  DSNVDTID DSNVDTM  DSNVDTMS DSNVDTP
    DSNVDTQ  DSNVDTT  DSNVDTTD DSNVMON  DSNWAACT DSNWVAPR DSNWVCOL
    DSNWVTIT DSNWVZIT DSNWVZPS DSNWVZSA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK39483

       UP08/10/03 P F810

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

Reference #: PK65367

Modified date: 03 November 2008