PM25028: APPLICATION'S EZASMI ASYNC API TYPE 3 EXIT INTERMITTENTLY NOT DRIVEN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Under certain conditions an application using EZASMI ASYNC api
  type 3 calls hangs because it's exit was not driven.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 11 and 12 IP   *
  *                 EZASMI Type 3 API                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Under certain timing and heavy load     *
  *                      conditions it is possible that an       *
  *                      asynchronous EZASMI API's completion    *
  *                      would not be processed in a timely      *
  *                      manner. This could lead to an           *
  *                      application experiencing delays or even *
  *                      a hang condition waiting for            *
  *                      notification of the call's completion.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The EZASMI API routine, EZBSOH03, did not check to see if there
  were any pending signals after issuing an EZASMI resolver call.
  The resolver calls are GetHostByName, GetHostByAddr,
  GetAddrinfo, FreeAddrInfo and GetNameInfo.
  Failure to check for the pending signal would cause the
  notification of an asynchronous API completion to be delayed
  until the next EZASMI API call was issued.
  In some applications this delayed notification might lead to
  an application hang condition.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• * * * Top of File * * *
  The EZASMI API has been amended to check for pending signals
  before completing every API call. If a signal is pending the
  application will be notified of the completion of the
  asynchronous API call.
  
  ****************************************************************
  * FUNCTION AFFECTED: Communications Server TCP/IP (PM25028)    *
  *                     Resolver API processing                  *
  ****************************************************************
  * DESCRIPTION      : IPL                                       *
  ****************************************************************
  * TIMING           : Post-APPLY                                *
  ****************************************************************
  The nucleus resident module, EZBRECST, is changed by this fix.
  To pickup its fix an IPL must be done after the SMP/E APPLY of
  this PTF.
  
  
  * 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:

  UK62232 UK62233

Modules/Macros

• EZBRECST EZBSOH03
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1B0 PSY UK62232

     UP10/12/30 P F012

• R1C0 PSY UK62233

     UP10/12/30 P F012

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.