IBM Support

PQ04788: A GET OF AN FBA FILE WITH SITE ASA SET, OE FTP SERVER IGNORES THE ASA PATH, AND PASSES PRINT CONTROL CHARS AS PLAIN TEXT DATA.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TCP/IP V3R3 OE FTP server not translating ASA correctly.
    
    OE FTP server is not translating FBA files correctly.  When
    accessing the MVS server, and the user is moving the file into
    an FBA MVS dataset, has set the SITE ASA correctly, then the
    ascii print control characters on the PC get converted to ASA
    characters correctly.
      If the user gets the MVS FBA file from the OE FTP server and
    has SITE ASA option, then the ASA characters do not get
    translated/converted and, instead, are sent to the PC as data.
      In TCPIP V3.1, this works fine.  Reviewing the FTP server
    trace and EZAFTPRR code, it is evident that the code is taking
    the "read_ascii_as_image" path and not handling the "special"
    processing for the ASA control characters.
      PUT of the same file works fine, because it is not going
    through this process.  Fails only when doing a GET.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All OE FTP 3.3 users wanting to retrieve     *
    *                 FBA (Fixed Block ASA) files to an ASCII      *
    *                 client, with ASATRANS.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: OE FTP server is not translating FBA    *
    *                      files correctly.  When accessing        *
    *                      the MVS server, and the user is moving  *
    *                      the file into an FBA MVS dataset, has   *
    *                      set the SITE ASA correctly, then the    *
    *                      ascii print control characters on the   *
    *                      PC get converted to ASA characters      *
    *                      correctly.                              *
    *                                                              *
    *                      If the user gets the MVS FBA file from  *
    *                      the OE FTP server and has SITE ASA      *
    *                      option, then the ASA characters do not  *
    *                      get translated/converted and,           *
    *                      instead, are sent to the PC as data.    *
    *                                                              *
    *                      In TCPIP V3.1, this works fine.         *
    *                      Reviewing the FTP server trace and      *
    *                      EZAFTPRR code, it is evident that the   *
    *                      code is taking the read_ascii_as_image  *
    *                      path and not handling the "special"     *
    *                      processing for the ASA control          *
    *                      characters.                             *
    *                                                              *
    *                      PUT of the same file works fine,        *
    *                      because it is not going through this    *
    *                      process.  Fails only when doing a GET.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    EZAFTPRR
    

Problem conclusion

  • Changed EZAFTPRR (retr()) to check for ASATRANS.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ04788

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    329

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / Serviceability / Xsystem

  • Submitted date

    1997-05-23

  • Closed date

    1997-06-18

  • Last modified date

    1997-07-02

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

    PQ02417

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

    UQ06432

Modules/Macros

  • EZAFTPLS EZAFTPRR
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R329 PSY UQ06432

       UP97/06/27 P F706

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

Document Information

Modified date:
02 July 1997