Restoring empty VSAM data sets

Learn about the workaround of restoring empty VSAM data sets.

Symptom	Problem determination
When you try to restore an empty VSAM data set that contains a lot of unused but occupied space, or has a smaller size and was heavily used, the restoration fails with the Broken pipe error message.	When ZD&T calls DFDSS to dump the data set, the dumped image contains a lot of unused space, while the DFDSS restoring does not use the space. So the restoration thread completes, while the transfer thread is still trying to send data to the restoration thread. You can follow the steps to solve the issue: For an empty VSAM data set that contains a lot of unused but occupied space, redefine the VSAM file size to a smaller value. For an empty VSAM data set that has a smaller size and was heavily used, redefine the VSAM file size to the exact value. Re-extract the VSAM file by creating a new component version. Create a new image version to contain the new component version. Update the provision with the new image version.

Symptom

Problem determination

When you try to restore an empty VSAM data set that contains a lot of unused but occupied space, or has a smaller size and was heavily used, the restoration fails with the Broken pipe error message.

When ZD&T calls DFDSS to dump the data set, the dumped image contains a lot of unused space, while the DFDSS restoring does not use the space. So the restoration thread completes, while the transfer thread is still trying to send data to the restoration thread. You can follow the steps to solve the issue:

For an empty VSAM data set that contains a lot of unused but occupied space, redefine the VSAM file size to a smaller value. For an empty VSAM data set that has a smaller size and was heavily used, redefine the VSAM file size to the exact value.
Re-extract the VSAM file by creating a new component version.
Create a new image version to contain the new component version.
Update the provision with the new image version.