IBM Support

II05071: CACHING MASTER CATALOGS IN VLF.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • There are two types of caching available for catalog records.
    The instorage Catalog (ISC) cache is contained in the Catalog
    Address Space (CAS), and uses private storage.  The Catalog Data
    Space Cache (CDSC) uses VLF facilities.  The cache method used
    is selectable, and can be changed, stopped, or started without
    an IPL.  Catalogs can be totally removed from caching.
    Although you can use either type of catalog cache, you cannot
    use both cache types for a single catalog simultaneously.
    You must decide which cache method to use for each catalog on
    your system.  There is no restriction on which type of cache you
    may use for any catalog, including the master catalog.
    
    Instorage catalog cache uses main storage within the Catalog
    Address Space, and is the default caching method.  Catalogs that
    are not frequently updated use the ISC most effectively.  All
    catalogs (except the master) that use ISC have a limited amount
    of storage dedicated to the cache; this is not controllable by
    the user.  The main storage required to cache the master catalog
    is not limited, so the number of entries in the master catalog
    should be kept to a minimum to prevent excessive storage use.
    We recommend only data set ALIAS entries, USERCATALOG conn-
    ections, and SYS1 data sets be in the master catalog.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • This is a dummy APAR for information only.      KDL
    

APAR Information

  • APAR number

    II05071

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1991-05-09

  • Closed date

    1992-11-18

  • Last modified date

    1999-02-10

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 December 2020