IBM Support

PH04419: MAINFRAME PDS MEMBERS DOWNLOADED AS 0 BYTE FILES INSTEAD OF FILES THAT CONTAIN THE CORRECT CONTENTS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When using AD Connect for Mainframe 5.0.5.1 and downloading
    mainframe members from a PDS, the files arrive at the AD server
    with correct file/member name but contain 0 bytes instead of
    the content that the corresponding member on z/OS contains.
    

Local fix

  • none known.
    

Problem summary

  • PDS datasets under Endevor management typically store a
    "footprint" in the user data field of each directory entry.
    The contents of this footprint could include null bytes (hex 0)
    in the field usually used by ISPF stats to record the "records
    updated" count.  The AD agent contains logic to avoid
    processing members for which this record count is zero.
    Instead, it skips the file classification, and only return a
    header with source file type UNDEFINED, which resulted in the
    AD Build client displaying UNDEFINED type members with a size
    of 0 bytes.
    

Problem conclusion

  • IBM AD code was changed to add 2 checks:
    -If the user data field in the PDS directory is not 30 bytes
    but some other length, do not perform any check on the "records
    updated" field and process the member under the assumption that
    it is required.
    -If the user data field is 30 bytes (therefore, it appears to
    contain ISPF statistics) - do some additional checks on
    individual fields to ensure they are reasonable values for ISPF
    statistics - eg. date/time fields are in proper packed format.
    If the user data does not appear to be valid ISPF statistics -
    for example - a string of hex 0 - skip the remaining check on
    "records updated" and process the member (as in the first
    check).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH04419

  • Reported component name

    AD MAINFRAME

  • Reported component ID

    5737B1610

  • Reported release

    505

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-23

  • Closed date

    2018-11-05

  • Last modified date

    2018-11-05

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

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

Modules/Macros

  • ADCFM
    

Fix information

  • Fixed component name

    AD MAINFRAME

  • Fixed component ID

    5737B1610

Applicable component levels

[{"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":"505","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"505","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
05 November 2018