IBM Support

PM91717: FTP LOGIC INCONSISTENCY FOR MBCS CONVERSION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • FTP client's PUT logic in determining if MBCS conversion will be
    done or not needs to be corrected to match with the FTP server's
    RETRIEVE logic.
    

Local fix

  • Use FTP server's code to do MBCS conversion.  That is, set up an
    FTP server on the system where the file to be read resides.
    Then do a GET on that file from a client system.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * for z/OS Version 1 Release(s) 12, 13 and Version             *
    * 2 Release(s) 1                                               *
    * IP: FTP                                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the PUT subcommand is run for TAPE data set and MBCS    *
    * encoding is used,                                            *
    * the transferred data set is incorrect. The MBCS encoding can *
    * not be translated                                            *
    * correctly.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * See local fix                                                *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

  • The solution for this APAR is included in CS for zOS Version 2
    Release 2.
    

APAR Information

  • APAR number

    PM91717

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-24

  • Closed date

    2013-07-18

  • Last modified date

    2015-09-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • EZAFTPCP
    

Fix information

Applicable component levels

  • R210 PSY

       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":"210","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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 September 2015