A fix is available
APAR status
Closed as program error.
Error description
An FTP USER API call issued from an application using the FTP client API can fail with retcode x'1A (26) if the INACTTIME timer expires while the API is still established.
Local fix
code inacttime 0 in the FTP.DATA file that the client FTP API program is using verification steps: INACTTIME is set to 60 seconds Customer sets up the FTP API environment via an INIT function appl issues an OPEN to the destaination server and then transfers data and issues a CLOSE API call. The application then sleeps for 120 seconds. during this sleep the INACTTIME timer has expired. The application comes out of the sleep and issues a new OPEN request, followed by a USER command which now fails with the retcode 26. The FTP Client API trace (DEBUG ALL coded in FTP.DATA shows the following: SCMD >CLOSE >>> QUIT 221 Quit command received. Goodbye. Command(00-08-QUIT-221): SCMD <................ <-----sleep 120 seconds SCMD >OPEN xx.xx.xx.xx Command(00-08- - ): SCMD <................ SCMD >USER XXXXXXX You must first issue the 'OPEN' command Command(26-19- - ): SCMD <................ SCMD >QUIT FtpStop(00-29- - ): SCMD <................ TERM > TERM <................
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 12 and 13 * * IP: FTP * **************************************************************** * PROBLEM DESCRIPTION: The OPEN subcommand is incorrectly * * affected when the INACTTIME timer * * expires. This causes errors on * * subsequent FTP API subcommands. * **************************************************************** * RECOMMENDATION: * **************************************************************** The FTP client API processing has been amended so that the INACTTIME timer value does not affect the processing of FTP client API OPEN subcommand. +-------------------------------------------------------------+ + 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 problem has been fixed in FTP client * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM57415
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-02-03
Closed date
2012-03-04
Last modified date
2012-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK76796 UK76797
Modules/Macros
EZAFTPCU
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:
02 May 2012