Why when running Endevor BSTXCOPY to copy a complete PDS library to a PDSE library the $$$SPACE member not being copied
Article ID: 30993
Updated On:
Products
Issue/Introduction
After running the Endevor Utility BSTXCOPY to copy from PDS to PDSE it was noticed that the $$$SPACE member was not copied - why?
Environment
Release: 18.0 18.1
Component: CA Endevor Software Change Manager
Resolution
$$$SPACE is a PDSMAN member, created by PDSMAN in a PDS (not PDSE) when :
- a PDS is being compressed
- there is an active $UPDATE rule with PSR=Y
The creation of and existence of $$$SPACE is required to support PDSMAN's Space Reuse feature.
If PDSMAN is active during BSTXCOPY operations, PDSMAN will prevent $$$SPACE from being copied into a PDSE or even another PDS.
The information related to a $$$SPACE member is only valid for the PDS in which it was created.
$$$SPACE should only exist in a PDSE if PDSMAN was not active when some PDS with a $$$SPACE member was copied into the PDSE.
It is okay for $$$SPACE to be in a PDSE. It will not be used.
Feedback
