PM82054: MSGDSNL030I MAY CONTAIN AN INVALID LUWID VALUE. THE TRANSLATED IP ADDRESS AND PORT DO NOT RESOLVE TO THE ADJACENT CONNECTION.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2DRDA DB2TCPIP defect pm82054 dpm82054
  MSGDSNL030I was issued from DSNLTSEC for an invalid password
  connection error. The LUWID displayed with the message did not
  properly resolve to the gateway address used for the connection.
  The LUWID should translate to the hex value for the IP address
  and port of the adjacent connection. This problem is only seen
  if the connection to DB2/z is made thorugh a gateway.
  DSNL030I
  *************************************************************
  Additional Symptoms and Keywords:
   MSGDSNL030I DSNL030I DSNLTSEC LUWID IP address.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: DSNL030I message from CSECT DSNLTSEC    *
  *                      may not properly identify origin of     *
  *                      the failed request.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an error is detected by DB2 CSECT DSNLTSEC, such as an
  authentication error, a DSNL030I message is issued to reflect
  the condition. The LUWID value is intended to refer to the
  adjacent remote system network address related to the failure
  however the LUWID value may actually refer to a network
  address that is not related to the failure. This can impede
  the user's ability to determine the origin of the failure and
  to correct the condition.
  The LUWID value may reflect an unrelated network address when
  the adjacent remote system operates in a gateway environment
  that services work from end users at different network
  addresses.
  When a user is successfully authenticated, at which point the
  end user's LUWID may be known, the LUWID value will now reflect
  the actual end user LUWID and hence its network address. If the
  gateway environment then assigns the connection (to DB2) to a
  different end user that encounters an error, such as a failed
  authentication, the DSNL030I message LUWID value will refer to
  the prior user and hence be misleading.
  

Problem conclusion

• When the remote system operates in a gateway environment, the
  network address of the actual end user causing the failure
  cannot yet be known because CSECT DSNLTSEC is involved at the
  very early stages of the access to DB2. It would however
  benefit users to always be aware of network address of the
  remote (gateway) system that's directly adjacent to DB2.
  However, with respect to IPv6 considerations, the LUWID value
  cannot fully reflect an IPv6 address of the adjacent partner.
  As a result, the IP address of the adjacent partner will now
  be reflected in the "correlation token" component of the
  DSNLTSEC DSNL030I message THREAD-INFO information.
  Note: The LUWID value may still refer to a prior user and
    its address that may be unrelated to the failure.
  

Temporary fix

Comments

APAR Information

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

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

  UK94312

Modules/Macros

• DSNLTSEC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK94312

     UP13/05/31 P F305

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.