IBM Support

PM22334: COPYING NON-VSAM DATA INTO VSAM FILE RESULTS IN UNEXPECTED DATA.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Steps to create the error:
    
    Enter FM.
    
    Edit a new, empty VSAM file.
    
    Type 'a' to copy after this point.  Then enter 'copy'
    on the command line, followed by ENTER.
    
    Type the data set name to be inserted into the current VSAM file
    and press ENTER.
    
    Scrolling to the right garbage is seen from column 127 through
    175.  There should be no information after column 126.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All File Manager users                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the COPY command from an     *
    *                      editor session, to copy records from    *
    *                      a variable length data set to a fixed   *
    *                      length data set the copied records      *
    *                      may be corrupted.                       *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    When using the COPY command to copy to a fixed length data set
    and the records being copied are of a shorter length, the length
    of the receiving data set is being used to copy the records.
    Instead the length of the copied data set should be used and the
    records padded if required.
    

Problem conclusion

  • The Copy command will copy records of a different length
    correctly truncating or padding the record depending on the
    attributes of the received data set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM22334

  • Reported component name

    FILE MANAGER ZO

  • Reported component ID

    5655V5200

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-09-13

  • Closed date

    2010-12-16

  • Last modified date

    2011-01-03

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

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

Modules/Macros

  • FMN0LVL
    

Fix information

  • Fixed component name

    FILE MANAGER ZO

  • Fixed component ID

    5655V5200

Applicable component levels

  • RA10 PSY UK63177

       UP10/12/21 P F012

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":"A10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
03 January 2011