Regular File Maintenance Can Improve Unload Utility Performance.

book

Article ID: 53219

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

When running the C1BM5000 utility to UNLOAD (Full or INCRemental) an environment, one can experience performance issues, with long elapsed times, when the inventory files are not properly tuned.

Why the performance of your daily or weekly Unload jobs start to degrade?

Environment

Release: ENDAE.00200-18.0-Endevor-Software Change Manager
Component:

Resolution

When the performance of your daily or weekly Unload jobs start to degrade, the first thing you should check is the state of the inventory files defined to the environment causing the bottleneck.

  1. Perform an IDCAMS LISTCAT against the Endevor VSAM files (MCF, PACKAGE, ELMCATL, EINDEX?):

    Verify low Extents, CI/CA Splits, etc.
     
  2. Perform a BC1PNLIB INQUIRE (with Option Analyze) against any ELIB base and delta files.

    Check the number of library extends and number of directory overflows (which should be 0).
     
  3. View statistics of any PDS or PDS/e Base and Delta libraries.

    Check number of physical extents. Ideally there is only one. A weekly compress of any PDS is highly recommended. For PDS/e libraries, refer to IBM's PDS/e documentation.

Additional Information

See also:

Tips and Techniques for Managing Endevor Elibs.
IBM Topic "What is a PDSEs?"