IBM Support

PQ97801: FTP REPLY CODE '451 TRANSFER ABORTED: FILE ERROR' DURING LARGE FILE TRANSFER WHEN USING FILETYPE=JES AND ASCII MODE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A FTP client may get a FTP reply '451 transfer aborted: file
    error' on a large file transfer when using filetype=JES and
    ASCI mode.  The FTP client has PUT a JCL on the FTP server for
    JCL to be executed on JES.  The FTP client is waiting for JES
    to generate the output and does a GET to retrieve the output.
    However, it has been found that JES may not be responding fast
    enough and ocassionally zero data will be seen even when the
    data is not EOF.  This zero data can contribute to setting an
    error and nothing happens until the real EOF is being seen.
    At that point, because of the error that happened some time ago,
    the rc_read is set and causes the unexpected 451 transfer
    aborted error.  A FTP server trace will show something like:
    ----------------------------------------------------------------
    ftp> quote site file=jes
    200 SITE command was accepted
    ftp> get ldwview3 ldwviewo(replace
    200 Port request OK.
    125-Submitting job ldwview3 FIXrecfm 80
    125 When JOB00423 is done, will retrieve its output
    <...>
    seq_read_file: no data, not eof, and no error
    MR5705 progressReport: entered
    MF1193 seq_read_file: entered
    MF1208 seq_read_file: calling fread() for up to 92160 bytes
    MF1216 seq_read_file: 0 bytes from fread()
    MF1232 seq_read_file: eof reached
    TO4114 read_stream: 0 bytes read into buffer size 92160
    <..no "250 Transfer completed successfully" message>
    SR2821 reply: entered
    reply: --> 451 Transfer aborted: file error.
    ----------------------------------------------------------------
    

Local fix

  • If possible, use EBCDIC data transfer type and BLOCK data
    transfer mode.
    KEYWORDS: EZAFTPTO EZAFTPSR EZAFTPMF JES RC_READ 451 TRANSFER
    ABORTED FILE ERROR
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS                            *
    *                 Version 1 Release 4, 5 & 6 IP: FTP           *
    ****************************************************************
    * PROBLEM DESCRIPTION: FTP REPLY CODE '451 TRANSFER ABORTED:   *
    *                      FILE ERROR' DURING LARGE FILE TRANSFER  *
    *                      WHEN USING FILETYPE=JES                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A FTP client may get a FTP reply '451 transfer aborted: file
    error' on a large file transfer when using filetype=JES.
    The FTP client submits a job to JES and is retrieving the
    sysout. FTP requests the sysout one record at a time. If Jes
    can not respond, we set an error code and retry. If the
    retry is successful, the error code is not reset. When the
    file is complete (eof is received) we exit the loop with the
    erroneous error code. This causes the 451 error reply and
    the received data set is deleted.
    +-------------------------------------------------------------+
    + 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 changed to correctly set the return code
    from the get of a Jes sysout file.
    
    * Cross Reference between External and Internal Names
    PREFTPCX (EZAFTPCX)  PREFTPLS (EZAFTPLS)
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ97801

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    140

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2004-11-30

  • Closed date

    2004-12-16

  • Last modified date

    2005-02-01

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

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

    UQ96190 UQ96191 UQ96192

Modules/Macros

  • EZAFTPCX EZAFTPLS EZAFTPTO
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R140 PSY UQ96190

       UP05/02/01 P F501

  • R150 PSY UQ96191

       UP05/02/01 P F501

  • R160 PSY UQ96192

       UP05/02/01 P F501

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

Document Information

Modified date:
01 February 2005