MFE TF Clone/Snap: VVDS Extent Count Is Incorrect When Using Parameter CONSOLIDATE_VOLUME

Summary: Snapping a multi-volume striped dataset, using the "CONSOLIDATE" parameter the extent count stored in the target VVDS is incorrect.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The target of a snapped dataset is not usable by FDR.

 

An FDRABR restore of a VSAM file that was backup up using snap failed. No error messages are issued, FDRABR recatalogs the non-VSAM catalog entry for the cluster indicating that not all the expected pieces of a multi-volume KSDS cluster were found.

 

The following are the snap dataset statements that are generated.

SNAP DATASET  (SOURCE(AAAA.BBBBP.CCCCC)  -                    
 TARGET(XXXX.ZZZZ.**) DATACLAS(DATACLS1) -                         
 EXTENT_ALLOCATION(YES,CONSOLIDATE_ALL) RECALCULATE_FREESPACE(YES) -  
 DATAMOVER(ADRDSSU) REPLACE(Y) FORCE(N) HCPYMODE(SHR))                

 

Cause

The code was incorrectly calculating the extent count and updating the VTOC with incorrect information when a CONSOLIDATE was performed.

 

Resolution

Workaround:

  • Remove the "CONSOLIDATE" Parameter from the SNAP control statements.

 

Permanent Fix:

  • For Mainframe Enablers 8.3, PTF SN83129 has been developed to correct the issue. It is available to download from Dell Online Support.
  • For Mainframe Enablers 8.4, PTF SN84029 has been developed to correct the issue. It is available to download from Dell Online Support.
  • For Mainframe Enablers 8.5, PTF SN85010 has been developed to correct the issue. It is available to download from Dell Online Support.

 

Affected Products

Mainframe Enablers
Article Properties
Article Number: 000182098
Article Type: Solution
Last Modified: 01 Oct 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.