A fix is available
APAR status
Closed as program error.
Error description
A SMF119 subtype 70 record (FTP server transaction completion) shows a SMF119_TISTACK value of "INET" rather than the actual TCPIP stack name (TCPIPJOBNAME) when the FTP server is running in a single TCPIP stack environment that is not configured as CINET. The value "INET" in SMF119 records is not helpful for TCPIP stack identification reporting purposes especially when there are FTP servers running on multiple systems not configured as CINET and that have unique TCPIP stack names. A FTP server trace with options DEBUG FSC(2) and DUMP FSC will generate a "write_smf_record_119" trace record indicating the value of "INET" in the SMF119TI_STACK field at offset 16(x'10') in the TCPIP Stack Identification record at offset 28(x'1C'). Because the "INET" value is actually returned from PFS in USS for a single stack environment that is not configured as CINET, coding a TCPIP stack name in the TYPE() parameter on the FILESYSTYPE statement in the SYS1.PARMLIB member BPXPARMXX will result in x'45A' (EAFNOSUPPORT) for unsupported address family. For example, using TYPE(TCPCS) for FILESYSTYPE will result in the following error message at TCPIP stack startup: EZZ4203I Z/OS UNIX - TCP/IP CONNECTION ERROR FOR TCPCS-BPX1SOC 00000003,FFFFFFFF,0000045A,112B0000 Because PFS always return the value "INET" by design for single stack environments not configured as CINET, other methods have to be used by the FTP server to obtain the TCPIP stack name for the SMF119 subtype 70 records.
Local fix
None KEYWORDS: SMF SMF119 SMF119TI_STACK INET CINET FTP USS PFS EZAFTPRU IOCCGETSTACKS SIOCGIBMOPT SIOCGTCPPROC BPXPARMXX FILESYSTYPE EZZ4203I 45A EAFNOSUPPORT
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 10, 11, and * * 12 IP: FTP * **************************************************************** * PROBLEM DESCRIPTION: Wrong TCPIP stack name in FTP server * * SMF records in INET environment * **************************************************************** * RECOMMENDATION: * **************************************************************** In INET environment, when writing SMF type 119 records for FTP server, we always get the "INET" but not the actual stack name in the stack name field in SMF records. +-------------------------------------------------------------+ + 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 wrong TCPIP stack name in FTP server SMF records in INET environment has been corrected. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM13252
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-04-27
Closed date
2010-05-20
Last modified date
2010-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK57100 UK57101 UK57102
Modules/Macros
EZAFTPGU EZAFTPRU
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1A0 PSY UK57100
UP10/07/20 P F007
R1B0 PSY UK57101
UP10/07/20 P F007
R1C0 PSY UK57102
UP10/07/20 P F007
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:
02 August 2010