IBM Support

PQ84149: WHEN AN NLST OR LS IS PERFORMED BY FTP, THE MEMBER DATA SETS OF A LISTED GDG MAY APPEAR OUT OF SEQUENCE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a Generation Data Group is listed from FTP the member
    data sets may be listed out of sequence.  This can happen when
    the maximum record length on the catalog is altered from the
    default (and recommended) value of 32400 to a smaller size.
    VERIFICATION STEPS:  list the catalog with FTP and listcat
    and compare the result.
    KEYWORDS:  GDG generation data group
               CSI Catalog Search Interface
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Communications Server for z/OS           *
    *                 Version 1 Release 5 IP: FTP                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: A client enters a mput, mget or mdelete *
    *                      for a GDG and receives a prompt for the *
    *                      base group name. When creating the list *
    *                      of potential files, FTP includes files  *
    *                      that can not be processed.              *
    *                                                              *
    *                      User enters a DIR, LIST or NLST for a   *
    *                      block of GDS names and they are         *
    *                      returned out of sequence.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The FTP client issue a mput, mget or mdelete and receives a
    prompt for each item asking if it should be transferred or
    skipped. This list may contain items such as GDG base and VSAM
    files that FTP can not transfer or delete. If the client is a
    batch job, then FTP will attempt to transfer the object as a
    file and will fail.
    
    Some GDS files may be returned out of sequence when a dir
    list or nlst is issued from FTP.
    +-------------------------------------------------------------+
    + 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 such that a mput, mget or mdelete will only
    return a list of files that FTP can transfer. This will effect
    the LS command so that LS will only display the files that can
    be processed by FTP. The DIR command will continue to work as
    normal in that, all items such as GDG's VSAM files, and ATL will
    be displayed.
    FTP has been changed to sort the GDS file names before returning
    them to the client.
    Keywords CSI, GDG, GDS, Generation Data Group
    
    The following documentation changes are required:
    
    z/OS Communications Server
    IP User's Guide and Commands
    Document Numbers: SC31-8780-03
    Chapter: LS subcommand--Obtain a list of file names
    
    Change the note by adding an additional line to read:
      --------------------------------------------------------------
    
    Note: If the local current working directory is an HFS
          directory, the results are stored in a file named
          LSOUTPUT.
          LS will only list files that FTP can process. Items such
          as GDG base, VSAM files, ATL library will not be
          displayed. See the FTP DIR command to list all types.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ84149

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    150

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2004-02-03

  • Closed date

    2004-02-10

  • Last modified date

    2004-04-03

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

    PQ77182

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

    UQ84992

Modules/Macros

  • EZAFTPMR
    

Publications Referenced
SC31878003    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R150 PSY UQ84992

       UP04/03/06 P F403

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

Document Information

Modified date:
03 April 2004