On 15 Mar 2016 07:55:41 -0700, in bit.listserv.ibm-main Mike Schwab
wrote:
>On our HSM MCDS, BCDS, etc, we have 0 for the secondary extent.
>If we specified TRACK(5 1) so we get 1 track as the Control Area,
>1. How much would the Index size go up? 15X?
>2. Wouldn't CAs be reused a lot more
, March 15, 2016 9:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Freeing up space in a VSAM file
On our HSM MCDS, BCDS, etc, we have 0 for the secondary extent.
If we specified TRACK(5 1) so we get 1 track as the Control Area, 1. How
much would the Index size go up? 15X?
2. Wouldn't CAs
I have been using CA-RECLAIM since 20012 for both dfHSM and dfRMM. No problems
or worries. I highly recommend it.
As a matter of fact it is a shop-wide default here.
SET CA-RECLAIM(DATACLAS) in IGDSMS00. The default for each DATACLAS is
CA-RECLAIM(YES).
One caveat. You don’t get the benefit
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Eells
Sent: Tuesday, March 15, 2016 4:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Freeing up space in a VSAM file
Norbert Friemel wrote:
>
> CA_RECLAIM?
> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS
On our HSM MCDS, BCDS, etc, we have 0 for the secondary extent.
If we specified TRACK(5 1) so we get 1 track as the Control Area,
1. How much would the Index size go up? 15X?
2. Wouldn't CAs be reused a lot more frequently, since you only have
to get 1 track empty instead of 15?
3. Which
Norbert Friemel wrote:
CA_RECLAIM?
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d4a0/2.5.3.3
Norbert beat me to it (smile). The key to this being useful is that you
have empty CAs to reclaim. One could have a pathological application
that left one record per CA behind
On Tue, 15 Mar 2016 07:57:41 +0200, Steff Gladstone wrote:
>Greetings,
>
>We have a KSDS file that gradually fills up with records. After deleting a
>large number of records we still received nonzero response codes when
>trying to add new records indicating that there is no available space in
Steff Gladstone wrote:
>We have a KSDS file that gradually fills up with records. After deleting a
>large number of records we still received nonzero response codes when trying
>to add new records indicating that there is no available space in the file.
>We have no alternative but to disable
Greetings,
We have a KSDS file that gradually fills up with records. After deleting a
large number of records we still received nonzero response codes when
trying to add new records indicating that there is no available space in
the file. We have no alternative but to disable access to the file
