PQ11340: ABEND02A-0C USING TRACE RESOLVER IN MULTITASKING APPLICATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Multitasking socket applications that invoke Gethostbyname or
  Gethostbyaddr under multiple tasks with TRACE RESOLVER active
  may experience abend02A rc0C failures when the SYSPRINT dd
  statement is pointing to sysout.  The resolver code does not
  serialize around the trace I/O requests that are written to
  SYSPRINT.
  VERIFICATION STEPS:
  1) Trace Resolver must be coded in the TCPIP.DATA file being
     used by the application.
  2) The application must support multitasking and issue the
     Gethostbyname or Gethostbyaddr calls.
  ADDITIONAL SYMPTOMS:
  This problem has been reported when running IP-PrintWays.
  .
  KEYWORDS:
  Gethostbyname Gethostbyaddr ipprintways ip printways abend 02a
  0c
  

Local fix

• Turn Trace Resolver off in the TCPIP.DATA file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of TCP/IP for MVS using TRACE      *
  *                 RESOLVER in a multi-tasking environment.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND02A RC0C when running multitasking *
  *                      socket applications with TRACE RESOLVER *
  *                      active.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If TRACE RESOLVER is active and multitasking socket applications
  invoke resolver functions (such as Gethostbyname) simultaneously
  an ABEND02A RC0C may result when the SYSPRINT dd statement is
  pointing to SYSOUT.  The resolver code does not serialize the
  JES service requests for SYSPRINT.
  

Problem conclusion

• The TRACE RESOLVER code has been amended to serialize its JES
  service requests for I/O requests written to SYSPRINT.
  
  * Cross Reference between External and Internal Names
  

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:

  UQ18927 UQ18928 PQ17115

Modules/Macros

• EZARESMQ EZARESNM EZARESPM EZARESQU EZARESSD
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R320 PSY UQ18927

     UP98/06/24 P F806

• R340 PSY UQ18928

     UP98/06/24 P F806

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.