A fix is available
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. This is a fix completion for PM68039, which did not address the problem for Fast UDP sockets.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications * * Server for z/OS Version 1 Release(s) * * 12, and 13 IP: * * SMF UDPTERM * **************************************************************** * PROBLEM DESCRIPTION: UDPTERM SMF records for UDP Fast Local * * Sockets do not contain the remote IP * * address and PORT. * **************************************************************** * RECOMMENDATION: * **************************************************************** 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 for UDP Fast Local 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
Routine EZBUDLCL (UDP Fast Local Socket Routine) within macro TOUUWP has been amended to load the socket address from the source UCB into umispdsa and umispdsa6 for IPv4 and IPv6 sockets, respectively. The associated port value will also be loaded into umispdsp, and umisptype will be set accordingly. This will all be done upon return from the appropriate ?SLP_FIND_POLICY invocation. Loading these values in the data path will make them available for subsequent SMF 119 reporting by EZBUDSMF. The values will appear in the fields SMF119UD_UCRIP/SMF119UD_UCRPORT (i.e., remote IP address/port of the last datagram received on the socket). EZBUDWRT EZBUDWR1 The following parts from PM68039 have been included for maintenance purposes: EZASMF EZASMF77 EZBUDSMF * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM80172
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
2013-01-08
Closed date
2013-01-22
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91130 UK91131
Modules/Macros
EZASMF EZASMF77 EZBUDSMF EZBUDWRT EZBUDWR1 TOUUWP
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
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":"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:
04 March 2013