Resolving fragmentation exceptions for PHIDAM primary indexes

Resolve the fragmentation exceptions that you received for your PHIDAM primary index.

Before you begin

Ensure that you have completed the analysis steps for PHIDAM primary index exceptions and that you have identified the possible causes of the exceptions. If you have not yet analyzed the fragmentation exceptions, see Analyzing fragmentation exceptions for HIDAM and PHIDAM databases.

Procedure

The only fragmentation exception for PHIDAM primary indexes is the EXCESSIVE_INDEX_CI_OR_CA_SPLITS exception.

If you observe no performance degradation in IMS applications that use the PHIDAM partition, you can ignore this exception.

If you observe performance degradation, you can resolve this exception by removing the CI splits and CA splits by re-creating the VSAM KSDS. However, performance degradation can be caused by the PHIDAM partition rather than the primary index. Therefore, consider analyzing the fragmentation and optimization exceptions for the PHIDAM partition. If you reorganize the PHIDAM partition, CI splits and CA splits in the primary index are also resolved.