On 2/13/2013 11:08 AM, Mark Zelden wrote:
On Wed, 13 Feb 2013 12:07:17 -0600, Paul Gilmartin <paulgboul...@aim.com> wrote:
On Wed, 13 Feb 2013 08:40:43 -0800, Skip Robinson wrote:
3. In the case of a PDSE growing excessively large, you may want to shrink
it manually now and then.
Will MIGRATE/RECALL accomplish this for a PDSE? (I believe it will for PDS,
and for PS, but only if secondary extents are defined.)
Is there a better way?
You can just use FREE on ISPF 3.4 to release unused extents.
Partial release has never worked well for PDSE because of the way PDSE is
architected internally. Only tracks above the highest active block can be
released; there can be big "gaps" inside the PDSE of unused data; "free" blocks
were obtained using an algorithm that did not care where the blocks were located
in the data set.
Wayne Rhoten discussed at SHARE in San Francisco improvements to PDSE (V1) such
that it now prefers lower-numbered RBNs to higher-numbered RBNs when looking for
"free" blocks to store new member and directory data. This should make partial
release work much better for PDSE going forward.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
