A fix is available
APAR status
Closed as program error.
Error description
DATTRACE is not capturing data for ATTLS connection. CTRACECLEARTEXT set to ON. As DatTrace is currently coded, the data trace settings is checked when the connection starts. A bit gets turned on in the SCB, ScbDataTrc. This bit indicates if this socket should record data trace records. Once the bit is set, it is never reset and the code has no awareness of if a new Data Trace command is entered.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of the IBM Communications Server for z/OS Version * * 2 Release 1 IP * * Data Trace * **************************************************************** * PROBLEM DESCRIPTION: * * Data trace is not capturing data for an AT-TLS connection, * * * * even though CTRACECLEARTEXT is set to ON. * **************************************************************** * RECOMMENDATION: * * Apply the PTF. * **************************************************************** The current design of data trace is to check during bind(), open(), or accept() processing to see if a socket matches the current data trace filters. If the socket matches, flag bit ScbDataTrc is set for the socket and, from then on, data trace records are created for activity on the socket. Once the flag is set it is never reset, even if a subsequent VARY TCPIP,,DATTRACE command removes the filter that matched the socket. And the socket is never checked again to determine if a subsequent V TCPIP,,DATTRACE command filter now matches the socket.
Problem conclusion
The data trace support has been changed to increment an internal counter each time a VARY TCPIP,,DATTRACE command is processed. A similar internal counter will be maintained for each socket. During socket function call processing, if the counter in the socket indicates that a new data trace command has been processed since the last activity on the socket, we will check the socket against the current data trace filters to see if it matches a filter. If it matches, we will begin creating trace records for the socket activity. If it doesn't match, we will ensure that we don't create any more trace records for the socket activity.
Temporary fix
Comments
APAR Information
APAR number
PI15257
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-04
Closed date
2014-05-01
Last modified date
2014-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI17592
Modules/Macros
EZBPFTRC EZBPFRDX EZBPFWRX EZBPFSET EZBPFANR EZBPFFSR EZBPFRDW EZBPFSRF EZBPFSRM EZB2SCB EZBPFRWV EZBPFFSF EZA2TSDX EZBPFFSM EZBPFSDR EZBPFCLO
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R210 PSY UI17592
UP14/06/12 P F406
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 July 2014