IBM Support

PQ06089: FTP GET RESULTS IN '550 ALLOCATION OF <DATASET> FAILED WHILE EXECUTING RETR COMMAND' INVALIDLY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using the C FTP server ( EZAFTSRV ) performing a GET of
    a dataset that is not in use, results in:
    '550 ALLOCATION OF <dataset> FAILED WHILE EXECUTING RETR
    COMMAND' .
    To clear this up, you must recycle the FTP address space.
    To recreate the problem - you must attempt to retrieve a
    dataset that is already in use. You will get the expected
    '550 allocation failed' message, however, upon further attempts
    to retrieve this dataset, even when the dataset is no longer
    in use, you will still get the '550 allocation failed'
    message. The only way to clear this problem up is to
    recycle the FTP SERVER.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of TCP/IP Version 3 Release 2      *
    *                 for MVS: CFTP server                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: FTP GET RESULTS IN '550 ALLOCATION OF   *
    *                      <DATASET> FAILED WHILE EXECUTING RETR   *
    *                      COMMAND' INVALIDLY.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Using the C FTP server ( EZAFTSRV ) performing a GET of
    a dataset that is not in use, results in:
    '550 ALLOCATION OF <dataset> FAILED WHILE EXECUTING RETR
    COMMAND' .
    To clear this up, you must recycle the FTP address space.
    To recreate the problem - you must attempt to retrieve a
    dataset that is already in use. You will get the expected
    '550 allocation failed' message, however, upon further attempts
    to retrieve this dataset, even when the dataset is no longer
    in use, you will still get the '550 allocation failed'
    message. The only way to clear this problem up is to
    recycle the FTP SERVER.
    

Problem conclusion

  • The code erroneously checked to see if the allocation failed
    and the type of request was to store the data (put, appe).
    The code now tests just for the case where the dataset
    could not be allocated and now correctly removes the dataset
    from the CFTP DSNT.
    Additional Keywords: CFTP32 CFTP DSNT GET
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ06089

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1997-07-03

  • Closed date

    1997-07-17

  • Last modified date

    1997-08-05

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

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

    PQ06096 UQ07360

Modules/Macros

  • EZAFTSMV
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R320 PSY UQ07360

       UP97/07/29 P F707

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

Document Information

Modified date:
05 August 1997