PI37892: DB2 DDF SQLCODE30061 WHEN SYSIBM.LOCATIONS HAS DBALIAS AND SYSIBM.IPNAMES IPADDR POINTS TO MULTIPLE IPADDRESSES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2TCPIP DB2DRDA defect pi37892 dpi37892
  DB2 DDF connection may receive -30061 when the DB2 z/os (CDB)
  communications database table contains a row in SYSIBM.LOCATIONS
  with a DBALIAS value specified and the SYSIBM.IPNAMES IPADDR row
  specifies a value thats associated with two or more IP
  addresses.
  
  In an DB2 z with Iseries environment using encryption this may
  result in a sqlcode805 (-805) due to the DRDA SECCHK
  not containing the correct RDBNAME to allow Iseries server to
  map the user to the proper database.
  
  **************************************************************
  Additional Symptoms and Keywords:
   SQLCODE -30061 SQLCODE30061 SQL30061N
   DSNL031I MSGDSNL031I 00D351FF RC00D351FF DSNLZRPA0001
   SQLCODE -805 SQLCODE805 SQLCODE00805 SQL805N SQL00805N
  

Local fix

• Local workaround/fix: A stop and start of DDF will reset the
  DBALIAS value to allow successful connection.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: SQLCODE -30061 may be detected when     *
  *                      accessing a remote server via TCP/IP    *
  *                      if a SYSIBM.LOCATIONS DBALIAS value is  *
  *                      specified and SYSIBM.IPNAMES IPADDR     *
  *                      refers to a domain name that resolves   *
  *                      to multiple IP addresses.               *
  *                      Users may also observe message DSNL031I *
  *                      indicating REASON=00D351FF and          *
  *                      ERROR ID=DSNLZRPA0001.                  *
  *                      Unpredictable symptoms may also be      *
  *                      observed, including SQLCODE -805, when  *
  *                      accessing a remote DB2 for i server     *
  *                      when two (or more) DB2 for i servers    *
  *                      exist at the same IP addresses.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The user has applications that refer to a remote server
  database by the value reflected in the SYSIBM.LOCATIONS
  LOCATION column.  The actual name of the remote server database
  is different so the user also provides an associated DBALIAS
  value that identifies its actual name.
  If the SYSIBM.IPNAMES IPADDR column refers to a domain name
  that resolves to two or more IP addresses, the DBALIAS value
  may (essentially) be incorrectly ignored if a communication
  error occurs when attempting to access the remote server.  If
  the DBALIAS value is incorrectly ignored, the LOCATION column
  value will be (incorrectly) used as the server's name.
  The incorrect server name (DRDA RDBNAM) will typically not
  match the actual name of the server and this results in an
  unexpected SQLCODE -30061 condition.
  Users may also observe a DSNL031I message indicating
  REASON=00D351FF and ERROR ID=DSNLZRPA0001.
  However, if the server environment is i/Series related, the
  i/Series environment may route the request to the (incorrect)
  named server database.  In this case, the connection may be
  honored by the server (a -30061 condition is not detected) but
  results are unpredictable because the connection was actually
  routed to an unexpected DB2 for i server.  One known symptom is
  SQLCODE -805 (since packages were not bound at that server).
  

Problem conclusion

• When the domain name resolves to additional IP addresses that
  can be utilized, DB2 has been changed to associate the DBALIAS
  value to these additional IP addresses.
  

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:

  UI26682 UI26683

Modules/Macros

• DSNLVCIP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI26682

     UP15/04/25 P F504

• RB10 PSY UI26683

     UP15/04/25 P F504

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.