PK62599: 04E-00D3111C DSNLIDNS:0001, AND/OR 0C4-00000011 DSNLFRCV+014E AFTER DSNLIDNS ABEND.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DDFL09 DB2TCPIP defect pk62599 dpk62599
  04E-00D3111C DSNLIDNS:0001, and/or 0C4-00000011 DSNLFRCV+014E
  after DSNLIDNS abend.
  *************************************************
  Additional symptoms and keywords:
    . ABEND04E AB04E S004E 04E 04E-00D3111C 00D3111C RC00D3111C
      DSNLIDNS DSNLIDNS:0001 0001 VRADC0001 ABNDID0001 ABID0001
    . ABEND0C4 AB0C4 S00C4 0C4 0C4-00000011 00000011 RC00000011
      DSNLFRCV DSNLFRCV+014E 014E
      FRESPREP points to corrupted PRE
    . ABEND04E AB04E S004E 04E 04E-00E50001 00E50001 RC00E50001
      DSNSDMPS
      ABEND04F AB04F S004F 04F 04F-00E50705 00E50705 RC00E50705
    . QWHD0165 IFCID165 IFCID 165 ERRNO QW0165IE invalid
    . Invalid ERRNO:
      - DSNL513I MSGDSNL513I ERRNO invalid
      - SQLCODE -904 SQLCODE904 SQL904N SQL0904N DSNLIDNS
        00D31058 RC00D31058 BPX1GAI BPX1FAI
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically those with applications that    *
  *                 remotely access remote servers via TCP/IP.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The following problems are reported:    *
  *                      1. Abend 04E-00D3111C DSNLIDNS:0001     *
  *                         or DSNLIDNS+0B04 may occur if DNS    *
  *                         is unavailable.                      *
  *                      2. Abend 0C4-00000011 DSNLFRCV+014E     *
  *                         may occur when recovering from       *
  *                         a DSNLIDNS abend, such as above.     *
  *                      3. Abend 04E-00E50001 DSNSDMPS and      *
  *                         DB2 abend 04F-00E50705 may occur     *
  *                         if an abend happens to occur while   *
  *                         DSNLIDNS holds a latch.              *
  *                      4. IFCID 165 (QWHS0165 QW0165) trace    *
  *                         record contains an invalid ERRNO     *
  *                         value in QW0165IE when a (QW0165MN)  *
  *                         BPX1GAI or BPX1FAI failure is        *
  *                         detected by DSNLIDNS.                *
  *                      5. Message DSNL513I DSNLIDNS issued     *
  *                         with incorrect ERRNO value of 0,     *
  *                         and an associated -904 00D31058      *
  *                         SQLCA is returned with incorrect     *
  *                         ERRNO value.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following problems are reported:
  1. Abend 04E-00D3111C DSNLIDNS:0001 or DSNLIDNS+0B04 may
     occur if DNS is unavailable.
     When DB2 must determine the remote location's IP address(es)
     via a domain name, DSNLIDNS makes a USS (OMVS) GetAddrInfo
     (BPX1GAI) socket call followed by a FreeAddrInfo (BPX1FAI)
     socket call. If the GetAddrInfo fails but the FreeAddrInfo
     is successful, DB2 will incorrectly abend.
     The intent of the abend is to identify logic errors in
     USS (OMVS) or TCP/IP where the GetAddrInfo call was
     successful yet no IP address was returned. In this case,
     the GetAddrInfo failed and thus no IP address was returned,
     but DB2 incorrectly believed that the GetAddrInfo was
     actually successful since the FreeAddrInfo was successful.
  2. Abend 0C4-00000011 DSNLFRCV+014E may occur when recovering
     from a DSNLIDNS abend, such as above.
     DSNLIDNS is incorrectly establishing a recovery environment
     in an FRR environment that is foriegn to DSNLIDNS. If an
     abend occurs within DSNLIDNS, or a module it calls, DSNLFRCV
     FRR processing will encounter the DSNLIDNS recovery
     environment which is no longer valid. Depending on the
     residual contents of storage related to the DSNLIDNS
     recovery environment, the abend may occur.
  3. Abend 04E-00E50001 DSNSDMPS and DB2 abend 04F-00E50705 may
     occur if an abend happens to occur while DSNLIDNS holds a
     latch.
     DSNLIDNS may execute in an environment where FRR recovery
     has not been established. If an abend occurs within
     DSNLIDNS, or in a module it calls, while DSNLIDNS holds a
     latch, there will be no recovery environment available to
     release the latch. This leads to abend 04E-00E50001 and a
     DB2 subsystem termination with reason code 00E50705.
  4. IFCID 165 (QWHS0165 QW0165) trace record contains an invalid
     ERRNO value in QW0165IE when a (QW0165MN) BPX1GAI or BPX1FAI
     failure is detected by DSNLIDNS.
     DSNLIDNS is constructing the QW0165 trace record with an
     incorrect QW0165IE value.
  5. Message DSNL513I DSNLIDNS issued with incorrect ERRNO value
     of 0, and an associated -904 00D31058 SQLCA is returned
     with an incorrect ERRNO value.
     When a GetAddrInfo socket call fails, DSNLIDNS does not set
     the ERRNO value used when generating a DSNL513I message
     or the -904 SQLCA information.
  

Problem conclusion

• The following problems are corrected:
  1. Abend 04E-00D3111C DSNLIDNS:0001 or DSNLIDNS+0B04 may
     occur if DNS is unavailable.
     DSNLIDNS has been changed to correctly remember the results
     of the GetAddrInfo socket call.
  2. Abend 0C4-00000011 DSNLFRCV+014E may occur when recovering
     from a DSNLIDNS abend, such as above.
     DSNLIDNS has been changed to establish its own recovery
     environment.
  3. Abend 04E-00E50001 DSNSDMPS and DB2 abend 04F-00E50705 may
     occur if an abend happens to occur while DSNLIDNS holds a
     latch.
     DSNLIDNS has been changed to establish its own recovery
     environment.
  4. IFCID 165 (QWHS0165 QW0165) trace record contains an invalid
     ERRNO value in QW0165IE when a (QW0165MN) BPX1GAI or BPX1FAI
     failure is detected by DSNLIDNS.
     DSNLIDNS has been changed to report the appropriate QW0165IE
     ERRNO value.
  5. Message DSNL513I DSNLIDNS issued with incorrect ERRNO value
     of 0, and an associated -904 00D31058 SQLCA is returned
     with an incorrect ERRNO value.
     DSNLIDNS has been changed to report the GetAddrInfo ERRNO
     value in the DSNL513I message and the associated -904
     SQLCA returned to the application.
  

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:

  UK34827

Modules/Macros

• DSNDLITR DSNLIDNS
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK34827

     UP08/04/07 P F804

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.