PI41277: DATTRACE DOES NOT COLLECT OUTBOUND RECORDS FOR APPLICATIONS THAT USES ACCEPTANDRECV (BPX1ANR) WITH ATTLS ENABLED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Dattrace does not collect outbound (send/write) type records
  for applications that use acceptandrecv (BPX1ANR) with ATTLS
  enabled. The client connection is accepted and data read via
  the acceptandrecv (BPX1ANR) call, any subsequent data sent from
  the server application is not traced, but inbound data from the
  client is.
  
  IBM zOS WEBSERVERS are the most common application that use
  accpetandrecv (BPX1ANR)
  
  Additional Symptom(s)
  
  verification steps:
  With ATTLS enabled, No outbound DATTRACE records collected, but
  outbound packet trace records include data sent from
  application
  
  Search Keyword(s): No outbound Dattrace
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 1 IP: TCP/IP                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Data trace for outbound data is not traced for connections   *
  * using AT-TLS and accept_and_recv() function.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  A flag that indicates that outbound data should be traced for
  data trace was not set in the socket control block  when
  multiple connection requests were queued in the TCP backlog.
  

Problem conclusion

• EZBTCFAP will be changed to ensure that the flag used to
  indicate that data should be traced will be set for all
  connections on the TCP backlog queue.
  

Temporary fix

Comments

• ×**** PE16/08/25 FIX IN ERROR. SEE APAR PI60245  FOR DESCRIPTION
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI28842 PI44964

Modules/Macros

• EZBTCFAP
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R210 PSY UI28842

     UP15/09/11 P F509

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.