Does CA Faver's GVCOPY utility copy from a Faver export that was using SAVECOMP as a parameter to export hardware compressed files? Receive S0C4 in GVFILE +7E4.

Products

• FAVER VSAM Data Protection for z/OS

Issue/Introduction

Does CA Faver's GVCOPY utility copy from a CA Faver export that was using SAVECOMP as a parameter to export hardware compressed files?

 

Environment

Faver R4.5  

Cause

If a file uses SAVECOMP on the EXPORT it also needs to use DFDSS as the data mover on the RESTORE

Resolution

Currently, if you utilize CA Faver to EXPORT a VSAM dataset that was compressed using hardware compression CA Faver will be accessing the dataset using its own EXCP data movers. If you use the SAVECOMP parameter for the EXPORT then CA Faver will call IBM's DFDSS to perform the data move and the original compressed format will be retained in the EXPORT output of CA Faver.

The GVCOPY utility will not support any of its functions on this type of EXPORT process. 

The S0C4 in GVFILE +7E4 is caused by the failure to open the EXPORT format record in the CA Faver output dataset.  

 

Additional Information

Using SAVECOMP can provide performance improvements on large compressed VSAM files.