APAR status
Closed as fixed if next.
Error description
An attempt to use the FTP client to transfer a member of a load module data set to a server on a non-MVS system causes the client session to ABEND. MPUT * EZA1701I >>> XLMT PDS 241340 500 Unknown command, 'XLMT' CEE3204S The system detected a protection exception (System Completion Code=0C4). From entry point diroutp at compile unit offset +000006C4 at entry offset +000006C4 at address 1862AD8C. IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=4039 REASON CODE=00000000
Local fix
Use the FTP client on the non-MVS system to connect to the z/OS FTP server and perform the equivalent transfer. Other Keywords: U4039 S0C4 ABENDU4039 ABENDS00C4
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: When attempting to PUT from a load * * library to a non-MVS server, an abend * * occurs in FTP client with the message * * CEE3204S The system detected a * * protection exception (System * * Completion Code=0C4). * * From entry point diroutp at * * compile unit offset +000006C4 * * at entry offset +000006C4 at * * address 1862AD8C. * **************************************************************** * RECOMMENDATION: * **************************************************************** The root cause is that in function setupXLMT() when the reply is 500 which indicates "server does not support load module transfer", setupXLMT() should return NOTOK to indicate regular processing is to be used instead of load module processing, but actually setupXLMT() returns OK to allow load module transfer, so it leads to abend. +-------------------------------------------------------------+ + 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
Temporary fix
Comments
This APAR is being closed FIN (Fixed If Next) with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release (if any) to be available within the next 24 months. This problem will be tracked as Feature F156185 by Communications Server for z/OS Development. The solution for this APAR is included in CS for zOS Version 2 Release 1.
APAR Information
APAR number
PM79709
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-26
Closed date
2013-01-07
Last modified date
2013-09-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R1C0 PSN
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:
16 September 2013