A fix is available
APAR status
Closed as program error.
Error description
With short lived connections, SMF119 termination records may show timestamps that suggest a connection ended at a time earlier than it began. This is because the SMF119AP_TTESTCK field has not been updated to account for leap year.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 10 and 11 * * IP: TCP SMF records * **************************************************************** * PROBLEM DESCRIPTION: The SMF119AP_TTSSTCK time field of the * * SMF record type 119 subtype 2 can * * appear to be after the * * SMF119AP_TTESTCK when the system Leap * * Second Offset (LSO) is non zero. * **************************************************************** * RECOMMENDATION: * **************************************************************** The SMF record was built using the STCK clock time from the system hardware timer, but was not converted to UTC time by applying the Leap Second Offset (LSO) value. When non zero then start time can appear to have occurred after the end time. The end time had been converted to UTC time. +-------------------------------------------------------------+ + 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
The SMF record formatting routine has been amended to set the UTC time in both the start and stop fields of the SMF record. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM05716
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1A0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-01-21
Closed date
2010-02-15
Last modified date
2010-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK54388 UK54389
Modules/Macros
EZBTCUTL
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":"1A0","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":"1A0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 April 2010