Hi Emlyn,
Thank you for your suggestion, I have opened a story on the PDSMAN backlog
to discuss.
One idea, one we have had Endevor clients use, is to use a FastCopy step
(with an EMPTYO command) or the PDSM10 utility (with PARM=EMPTYO) in
processors to reset PDSE libraries after the content is copied. Is this
something that may help?
Regards.
--
*Ray Frazier*
Broadcom Inc.
Mainframe Software Engineer
Office: 1.631-533-8956
Mobile: 1.740-250-1512
Email:
Ramah.Frazier@broadcom.com--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
Original Message:
Sent: 8/30/2024 10:42:00 AM
From: Emlyn Williams
Subject: Enhance XCOMPRESS to compress PDSe
We use XCOMPRESS/VOLCOMPRESS to compress PDS and sequential datasets on our volumes.
However there is no utility to compress PDSe datasets.
While PDSe does reuse space when you add new members, we can't release space without copying the dataset. With Endevor we regularly find that PDSe datasets are filled up then emptied as projects are moved through the lifecycle resulting in a lot of wasted DASD.