IBM Support

OA45407: DIAGNOSE OF A CATALOG GETS REASON: 2 - CELL TYPE NOT RECOGNIZED FOR A GDS IN AN EXTENSION RECORD WITH MULTIPLE ALIASES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • NOTE: this is a reversal of FIN apar OA44551 to be fixed in
    current releases
    
    
    An IDCAMS DIAGNOSE for a BCS gets IDC21364I with
    REASON: 2 - CELL TYPE NOT RECOGNIZED
    for large GDG's with extension records. This kind of corruption
    can happen for generations which have multiple aliases and
    reside in a GDG extension record (type J).
    
    In the specific case the error happens when a second alias is
    defined to a generation and which requires the generation to be
    moved from the GDG base to an extension record. The alias is
    added to the association cell for the GDS, but the length of
    that cell as well as the number of associations is not changed
    to reflect the new alias.
    
    The invalid cell length causes wrong positioning within the
    catalog entry and makes all cells beyond the association cell
    inaccessible.
    
    Addtional symptom:
    IDC21364I ERROR DETECTED BY DIAGNOSE:
    REASON: 28 - GAT CELL ENTRY NOT FOUND
    
    CATKEYS:  CAT2014 CATGDG CATBCS IDCDIAG
    

Local fix

  • Avoid defining multiple aliases to GDSs for larger GDGs (GDGs
    with high limits, GDSs with many candidate volumes, etc).  Once
    the error is encountered, the VVDSfix tool will be needed to
    remove the extension records.  Note VVDSFIX delbcsr may need
    to be issued multiple times.  VVDSfix is supplied by defect
    support.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of HDZ1C10 and above.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: DEFINE ALIAS over a Generation data set *
    *                      can cause catalog structural problems   *
    *                      in certain cases.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DEFINE ALIAS over a Generation data set can lead to issues
    with IDCAMS DIAGNOSE due to catalog structural problems.
    

Problem conclusion

  • Code has been added to make sure the DEFINE ALIAS over a
    Generation data set does not cause any structural problems in
    the catalog.
    
    KEYWORDS:
    FINREVERSAL OF APAR OA44551
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA45407

  • Reported component name

    ICF CATALOG & I

  • Reported component ID

    5695DF105

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-11

  • Closed date

    2014-07-16

  • Last modified date

    2014-09-02

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

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

    UA74210 UA74211 UA74212

Modules/Macros

  • IGG0CLEF
    

Fix information

  • Fixed component name

    ICF CATALOG & I

  • Fixed component ID

    5695DF105

Applicable component levels

  • RC10 PSY UA74210

       UP14/08/18 P F408

  • RD10 PSY UA74211

       UP14/08/18 P F408

  • R210 PSY UA74212

       UP14/08/18 P F408

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":""}}]

Document Information

Modified date:
02 September 2014