APAR status
Closed as program error.
Error description
The UDPTERM records (SMF type 119 subtype 10) do not have the SMF119UD_UCRIP or SMF119UD_UCRPort values set (all 0s) in some conditions, even though packets have flowed in both directions.
Local fix
(None)
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications * * Server for z/OS Version 1 Release(s) * * 11, 12, and 13 IP: * * SMF UDPTERM * **************************************************************** * PROBLEM DESCRIPTION: UDPTERM SMF records do not contain the * * correct remote IP address and PORT for * * IPv6 sockets. * **************************************************************** * RECOMMENDATION: * **************************************************************** UDPTERM SMF records do not contain the correct remote IP address and PORT for IPv6 sockets. The SMFCONFIG TYPE119 UDPTERM profile setting creates an SMF type 119 subtype 10 record to be written when a UDP socket is closed. The SMF119UD_UCRIP field is supposed to contain the remote IP address of the last datagram received. The SMF119UD_UCRPORT field is supposed to contain the remote port of the last datagram received. These values are not being set correctly for IPv6 UDP sockets. +-------------------------------------------------------------+ + 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
EZBUDSMF has been amended to set SMF119UD_UCRIP with the remote IP address of the last datagram received on an IPv6 socket, and SMF119UD_UCRPORT with the remote port of the last datagram received. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM68039
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-03
Closed date
2012-09-17
Last modified date
2013-01-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK81861 UK81862 UK81863
Modules/Macros
EZASMF EZASMF77 EZBUDSMF
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1B0 PSY
UP
R1C0 PSY
UP
R1D0 PSY
UP
[{"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":"1C0","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":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
24 January 2013