A fix is available
APAR status
Closed as program error.
Error description
When transferring multi-byte data, FTP uses two sets of codepages: one for the translation of the multi-byte characters, and one for the translation of the single-byte characters. However, there are some scenarios, when translating from EBCDIC to ASCII, that the EBCDIC newline (hex 15) will be stripped from the data instead of being translated using the SBCS tables.
Local fix
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: When an FTP client is using the DBCS * * transfer mode GET subcommand to * * download a data set containing EBCDIC * * New Line characters the user can not * * control NL conversion using SBDATACONN. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using DBCS transfer mode, a user is not allowed to specify a customized SBCS table using SBDATACONN. This leads to a downloaded data set's EBCDIC NL characters not being translated to what was specified in the user's SBCS tables. FTP should allow DBCS transfer mode to use an SBCS table by using SBDATACONN. +-------------------------------------------------------------+ + 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
FTP has been amended to allow DBCS transfer mode SBDATACONN to control the conversion of EBCDIC characters. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PM34827
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
2011-03-15
Closed date
2011-03-30
Last modified date
2011-05-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK66347 UK66348 UK66349 PM39242
Modules/Macros
EZAFTPNC
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R1A0 PSY UK66347
UP11/04/17 P F104
R1B0 PSY UK66348
UP11/04/17 P F104
R1C0 PSY UK66349
UP11/04/17 P F104
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:
16 May 2011