IBM Support

PI40468: SOME FTP PARAMETERS PASSED FROM APPLICATION USING FTP API ARE IGNORED OR FAIL TO BE PARSED CORRECTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Some FTP command line parameters passed to FTP API are not
    working. Unexpected parsing errors or results can occur when
    a third party application (for example, SMP/E) is using the
    assembler version of FTP API to pass the parameters to z/OS
    CS FTP application program. Delimiters such as double quotes
    quotes and spaces might be ignored.
    
    Examples of FTP command line parameters that are known to fail:
    
    1) Parameters "-a TLS" or "-r TLS"
    
       Error:  Security mechanism TLS is not valid
       Result: Parameter is ignored and value from FTP.DATA is used.
    
    2) Parameter "-f ftp.data"
       Result: Does not override or merge with FTP.DATA in search
               order.
       Error:  EDC5129I NO SUCH FILE OR DIRECTORY (ERRNO=0XC90F0003)
    
    FTP.DATA search order is:
    
    1) SYSFTPD DD statement
    2) jobname.FTP.DATA,
    3) etc/ftp.data
    4) SYS1.TCPPARMS(FTPDATA)
    5) tcpip.FTP.DATA.
    
    Depending on the order of the parameters for the FTP command
    line parser, other FTP parameters might produce errors or
    unexpected results. Undesired values from the above FTP.DATA
    search order might be used instead.
    
    When the SMP/E program GIMGTPKG is used to invoke /bin/ftp
    to download package files and FTP.DATA is specified in the -f
    input parameter with double quotes surrounded for the correct
    syntax for a MVS data set, the z/OS FTP client fails with the
    following error message:
    
      Cannot open FTP.DATA specified by -f parameter
             "//'mvs_dataset_name'"
      process_ftpdata_name: fopen() errno=EDC5129I No such file or
      directory. (errno2=0x0594003D)
    
    While the input -f parameter can be in the correct syntax for
    specification of a MVS data set for FTP.DATA surrounded by
    double quotes, the double quotes and spaces were not removed
    during parameter parsing in FTP. This results in the unexpected
    EDC5129I error for FTP.DATA.
    

Local fix

  • Do not use the parameter. Use other means to specify the
    parameter in FTP.DATA according to search order. For example,
    /etc/ftp.data. See the z/OS CS IP Configuration Reference
    in topic "FTP configuration statements in FTP.DATA" for more
    information.
    
    KEYWORDS:
    FTPAPI FTP API -F -A -R TLS EZAFTPCY FTPDATA FTP.DATA
    SMP SMPE GIMGTPKG SHOPZ
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications                          *
    * Server for z/OS Version 2 Release 1:                         *
    * FTP.                                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * FTP -f option not processed correctly                        *
    * when invoked with double quotes from                         *
    * SMP/E environment.                                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF.                                                   *
    ****************************************************************
    FTP does not remove leading spaces and double quotes for
    -f and -p options.
    

Problem conclusion

  • FTP client has been updated to remove leading blanks and
    leading and trailing double quotes for -f and -p options.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI40468

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-05

  • Closed date

    2015-05-22

  • Last modified date

    2015-08-03

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

    PI38100

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

    PI41647 UI27880

Modules/Macros

  • EZAFTPCY EZAFTPDM EZAFTPEP EZAFTPRM EZAFTPRX EZAFTPSM EZAFTPSR
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R210 PSY UI27880

       UP15/08/01 P F507

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":"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:
03 August 2015