PI52387: NO SYSTCPIP CTRACE SOCKAPI RECORDS ARE BEING COLLECTED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• .
  An application is using the macro extended API (EZASMI) or one
  of its derivatives (EZASOKET, CICS Sockets, IMS Sockets).  When
  the SYSTCPIP CTRACE is started specifying the SOCKAPI option,
  there are no records of that type even though other options show
  that the associated socket calls are being performed.
  
  Other symptoms:
  
    A SYSTRACE will show an S0C4 ABEND occurring in EZBSOMTU
    whenever one of these records would normally be created.  This
    ABEND is followed by RCVY with a retry (also to EZBSOMTU), and
    is not externally visible.  The TCB for the task(s) performing
    these calls will have the TCBCMP field set to 940C4000.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 2 IP:  EZASMI                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * SOCKAPI Component Trace entries are not created for EZASMI   *
  * API processing.                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  An EZASMI API program is started with the Component Trace active
  with the SOCKAPI option enabled. An invalid pointer is used by
  the EZAMSI socket trace routine preventing the SOCKAPI Component
  Trace records from being created.
  

Problem conclusion

• The EZASMI socket trace routine has been updated to use the
  correct pointer.
  

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:

  UI33611

Modules/Macros

• EZBSOMTU
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R220 PSY UI33611

     UP16/01/22 P F601

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.