PM78373: DB2 DDF SQLCODE -30061 AND OR DSNL030I DRDA EXCEPTION CONDITION REASON=00D351FF FROM DSNLZRPA0001

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2TCPIP defect pm78373 dpm78373
  DB2 for z/os returns -30061 and/or a
  DSNL030I DRDA EXCEPTION CONDITION WITH
  REASON=00D351FF FROM DSNLZRPA0001 in the DB2 mstr logs due to a
  zero IP address being used to access a remote (server) system.
  One or both conditions may be present.
  The zero IP address causes a TCP/IP loopback condition to the
  same host (TCP/IP stack).
  **************************************************************
  Additional Symptoms and Keywords:
   MSGDSNL031I DSNL031I 00D351FF RC00D351FF DSNLZRPA0001
   SQLCODE30061 -30061 SQL30061N SQLN30061 DSNLZRPA
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message DSNL031I with REASON=00D351FF   *
  *                      and ERROR ID=DSNLZRPA0001, and/or       *
  *                      SQLCODE -30061, due to a zero IP        *
  *                      address being used to access a remote   *
  *                      system.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When many concurrent users are trying to access the same remote
  location, serialization issues exist during domain name
  resolution processing that allows a null IP address to be
  determined for the remote system.  The null (zero) IP address
  is interpreted by the TCP/IP stack as a "loop back" condition
  that is serviced by the same host (instead of the intended
  remote host).  If another subsystem is configured to listen on
  the same port (as the intended remote server), the connection
  request is essentially honored by the wrong partner.  The
  location name (RDBNAME) will therefore not match that of the
  intended remote system and the connection will be rejected
  (DRDA RDBNFMRM).  This results in message DSNL031I being issued
  to the console and the application will receive SQLCODE -30061.
  

Problem conclusion

• DB2 for z/OS is changed to correctly serialize domain name
  resolution processing for the benefit of users that are
  concurrently accessing the remote system.
  

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:

  UK91228 UK91229

Modules/Macros

• DSNLIDNS DSNLVCIP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK91228

     UP13/02/12 P F302

• R910 PSY UK91229

     UP13/02/12 P F302

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.