IBM Support

PM96072: WHEN ATTEMPTING TO DELETE A VSAM FILE WITH AIX, NOT ALL FILE PARTS ARE DELETED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When attempting to delete VSAM files with alternate indices,
    client receives the following msgs:
    
      DELETE (vsam.dataset.name) PURGE SCRATCH FILE (volume)
    
      IDC0550I ENTRY (G) vsam.dataset.name.AIX   DELETED
      IDC2895I ALL REQUIRED VOLUMES NOT INCLUDED IN DD STATEMENT
               SPECIFIED IN FILE PARAMETER
      IDC3014I CATALOG ERROR
      IDC3009I ** VSAM CATALOG RETURN CODE IS 76 - REASON CODE IS
                  IGG0CLFM-8
      IDC0551I ** ENTRY vsam.dataset.name NOT DELETED
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All File Manager users.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When deleting a VSAM data set using     *
    *                      the Catalog Services utility, the AIX   *
    *                      data set will not be deleted if it is   *
    *                      on a different pack.                    *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    The IDCAMS DELETE statement generated includes the FILE
    parameter which points to a DDname for only the VSAM data set
    volumes and not the volumes for any associated data sets.
    

Problem conclusion

  • File Manager has been modified to not include the FILE parameter
    in the generated IDCAMS DELETE statement.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM96072

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-08-29

  • Closed date

    2013-12-05

  • Last modified date

    2014-01-02

  • 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 Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC10 PSY UI13230

       UP13/12/07 P F312

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

Document Information

Modified date:
02 January 2014