Will the new IBM Function - Reclaiming CA Space for a KSDS file cause CA Endevor Software Change Manager's KSDS files to have a problem?

book

Article ID: 49796

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA PanAudit Plus CA Easytrieve Report Generator CA PAN/SQL 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) CA 2E

Issue/Introduction

Description:

What is the effect on the Endevor VSAM files; would there be a benefit/harm to setting the value to YES?

Solution:

Z/OS 1.12 introduced a new VSAM function CA Reclaim. CA Reclaim provides for improved DASD space usage, but it requires additional I/O to keep track of the reclaimed CAs so that they can be reused. The cost of this I/O may not be justified if there are none or very few CA splits to reuse empty CAs. Endevor Software Change Manager has large KSDS VSAM files. The default for Z/OS for all VSAM files is set to CA Reclaim=YES. What is the effect on the Endevor VSAM files; would there be a benefit/harm to setting the value to YES?

CA Reclaim will not break CA Endevor Software Change Manager and will likely somewhat negatively affect performance.

Environment

Release:
Component: C21E