IBM Support

PM88692: Z/OS FTP CLIENT FAILS WITH EZA2825E EVEN WITH WRAPRECORD ENABLED FOR EBCDIC FILE TRANSFER FROM NON-Z/OS FTP SERVER OR FROM HFS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A FTP server (on non-z/OS platform or z/OS platform with source
    file on HFS) supports the TYPE E command for a EBCDIC file
    transfer.
    
    A z/OS FTP client has specified the following commands before
    doing a GET for a large file as a long record in stream mode
    with no newline (NL) for end-of-line record delimiters into a
    MVS data set:
    
      LOCSITE LRECL=80 BLKSIZE=xx RECFM=FM
      LOCSITE WRAP
      TYPE E
    
      where xx can be zero or non-zero for blocksize.
    
    The file transfer failed with the following error message
    issued by the z/OS FTP client because no record delimiters
    were found at all throughout the wrapped records:
    
      EZA2825E File contains records that are too long to be
               processed
    
    Depending on the LRECL and BLKSIZE values used, certain
    files (typically small ones) might work without incident.
    
    Because the z/OS FTP client has specified the DCB attributes
    for a MVS data set using a LOCSITE command for LRECL, BLKSIZE,
    and RECFM as well as a LOCSITE command for WRAPRECORD, the
    z/OS FTP client was transferring the file using the record
    wraps while checking for the record delimiters. With the
    WRAPRECORD support added to z/OS CS FTP client for EBCDIC file
    transfers, it was not necessary to terminate with an error when
    processing the last record with no record delimiter at all. If
    WRAPRECORD had not been supported for the EBCDIC file transfers,
    then the record delimiters would have been expected and the
    appropriate error message would have been issed if there were
    no record delimiters found.
    

Local fix

  • Replace the "LOCSITE WRAP" and "TYPE E" commands with
    "BIN" and "QUOTE TYPE E" commands respectively.
    
    This will tell the FTP server to translate the long record
    into EBCDIC and transfer the record as binary. The z/OS FTP
    client will receive the EBCDIC characters as binary into a
    MVS data set with the specified LRECL, BLKSIZE, and RECFM for
    the DCB attributes.
    
    KEYWORDS:
    EZA2825E EZAFTPTI RECORD DELIMITER WRAPRECORD WRAP
    LOCSITE EBCDIC BINARY BIN ASCII NEWLINE NL
    

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: Record too long error happens for       *
    *                      TYPE E transfer of a long file which    *
    *                      has no end-of-record character or       *
    *                      has a long record length from remote    *
    *                      FTP server to z/OS FTP client even      *
    *                      when WRAPRECORD is enabled.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using TYPE E transfer to get a file from the remote FTP
    server to the local z/OS FTP client, if the file is very long
    and contains no end-of-record character or the file contains
    the end-of-record character but the record is very long, even
    WRAPRECORD is enabled in the z/OS FTP client, the following
    error occured and the transfer failed:
    EZA2825E File contains records that are too long to be processed
    +-------------------------------------------------------------+
    + 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

  • The problem has been fixed in z/OS FTP client and server.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM88692

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1C0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-08

  • Closed date

    2013-06-14

  • Last modified date

    2013-08-02

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

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

    UK95109 UK95110 PM92871

Modules/Macros

  • EZAFTPTI
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1C0 PSY UK95109

       UP13/07/24 P F307

  • R1D0 PSY UK95110

       UP13/07/24 P F307

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":"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:
02 August 2013