Re: CA/Reclaim Question
Based on info from John Eells, I would say. it depends. Reading the info APAR II14640 (thanks for the reference John), I find: quote Depending on the age of VSAM data sets, you may have some data sets that are not eligible for CA RECLAIM show a value on a listcat of CA-RECLAIM(YES). Data sets created prior to the installation of the PTF for OA26256 on z/OS 1.10, or data sets created on z/OS 1.9 or earlier releases may show a value of CA-RECLAIM(YES) for ESDS, RRDS, LINEAR VRRDS data sets. Installation of the PTFs for apar OA36052 will correct the listcat output. /quote And: quote There is a tool available that will produce a one line listing of data sets that are currently eligible for CA RECLAIM. While you can run an IDCAMS LISTCAT LEVEL or LISTCAT CATALOG to get a list of data sets, either of these will also produce a large amount of output and also list data sets that are not eligible for CA RECLAIM. This tool can be downloaded from the following FTP site: ftp://public.dhe.ibm.com/servers/storage/support/software/dfsms/ It is on this site as CARECLAM.JCL.CNTL.TRSD. It will need to be downloaded in binary mode to a data set with the following DCB attributes: LRECL=1024,RECFM=FB,BLKSIZE=6144,DSORG=PS . After downloading it will need to be untersed using AMATERSE. Note that when untersing the output data set will be a PDS, so you need to supply directory blocks for the output data set when untersing. A space allocation of (TRK,(1,1,6)) should be fine. If you have questions or concerns about this tool open an ETR to component 5695DF106. /quote Of course, to be absolutely sure, you could rebuild the dataset. snip I'm not sure if I got my original question answered. We've enabled CA-Reclaim on the dataset, but I what I wanted to know does a repro back into the original dataset using the replace and reuse options, enable CA-Reclaim on all CA's, or do I need to reallocate the dataset? Mark Jacobs Staller, Allan mailto:allan.stal...@kbmg.com February 12, 2015 at 9:12 AM According to the fine manual, if CA-Reclaim is enabled globally (in IGDSMS00), you can alter the cluster to enable CA-Reclaim; From AMS Commands( Rel 2.1) SC23-6846-01: quote RECLAIMCA|NORECLAIMCA Specifies the CA reclaim attribute of a key-sequence data set (KSDS). ...remainder elided /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
Run an IDCAMS EXAMINE on the data set and see if you get message IDC01718I Found empty control areas that have not been reclaimed. HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Jacobs - Listserv Sent: Thursday, February 12, 2015 8:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CA/Reclaim Question I'm not sure if I got my original question answered. We've enabled CA-Reclaim on the dataset, but I what I wanted to know does a repro back into the original dataset using the replace and reuse options, enable CA-Reclaim on all CA's, or do I need to reallocate the dataset? Mark Jacobs -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
According to the fine manual, if CA-Reclaim is enabled globally (in IGDSMS00), you can alter the cluster to enable CA-Reclaim; From AMS Commands( Rel 2.1) SC23-6846-01: quote RECLAIMCA|NORECLAIMCA Specifies the CA reclaim attribute of a key-sequence data set (KSDS). RECLAIMCA Specifies that the DASD space for empty control areas (CAs) will be reclaimed so that it can reused for that KSDS. CA reclaim cannot reclaim space for: v Partially empty CAs v Empty CAs that already existed when CA reclaim was enabled v CAs with RBA 0 v CAs with the highest key of the KSDS v Data sets processed with GSR. NORECLAIMCA Specifies that the DASD space for empty control areas (CAs) will not be reclaimed. You can disable CA reclaim at the system level with the IGDSMSxx member of PARMLIB or with the SETSMS command. This does not change CA reclaim attributes in the catalog. For more information, see the topic about reclaiming CA space in z/OS DFSMS Using Data Sets. /quote HTH, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
I'm not sure if I got my original question answered. We've enabled CA-Reclaim on the dataset, but I what I wanted to know does a repro back into the original dataset using the replace and reuse options, enable CA-Reclaim on all CA's, or do I need to reallocate the dataset? Mark Jacobs Staller, Allan mailto:allan.stal...@kbmg.com February 12, 2015 at 9:12 AM According to the fine manual, if CA-Reclaim is enabled globally (in IGDSMS00), you can alter the cluster to enable CA-Reclaim; From AMS Commands( Rel 2.1) SC23-6846-01: quote RECLAIMCA|NORECLAIMCA Specifies the CA reclaim attribute of a key-sequence data set (KSDS). RECLAIMCA Specifies that the DASD space for empty control areas (CAs) will be reclaimed so that it can reused for that KSDS. CA reclaim cannot reclaim space for: v Partially empty CAs v Empty CAs that already existed when CA reclaim was enabled v CAs with RBA 0 v CAs with the highest key of the KSDS v Data sets processed with GSR. NORECLAIMCA Specifies that the DASD space for empty control areas (CAs) will not be reclaimed. You can disable CA reclaim at the system level with the IGDSMSxx member of PARMLIB or with the SETSMS command. This does not change CA reclaim attributes in the catalog. For more information, see the topic about reclaiming CA space in z/OS DFSMS Using Data Sets. /quote HTH, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Mark Jacobs - Listserv mailto:mark.jac...@custserv.com February 11, 2015 at 11:27 PM We have a VSAM KSDS that was allocated and populated with data prior to the CA/Reclaim function being available. This evening we had to reorg the dataset, and the REPRO back used the same physical dataset with the REPLACE and REUSE options. Does this enable CA/RECLAIM for the dataset, or do we have to allocate an entirely new KSDS? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
mark.jac...@custserv.com (Mark Jacobs - Listserv) wrote: I'm not sure if I got my original question answered. We've enabled CA-Reclaim on the dataset, but I what I wanted to know does a repro back into the original dataset using the replace and reuse options, enable CA-Reclaim on all CA's, or do I need to reallocate the dataset? snip Sorry, Mark, I missed the back into the existing data set part of your question. VSAM Development tells me you must delete and reallocate the data set to eliminate the empty CAs that existed before CA Reclaim was enabled. -- John Eells z/OS Technical Marketing IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
mark.jac...@custserv.com (Mark Jacobs - Listserv) wrote:
We have a VSAM KSDS that was allocated and populated with data prior to
the CA/Reclaim function being available. This evening we had to reorg
the dataset, and the REPRO back used the same physical dataset with the
REPLACE and REUSE options.
Does this enable CA/RECLAIM for the dataset, or do we have to allocate
an entirely new KSDS?
There are three controls for CA reclaim.
1. At the system level, in IGDSMSxx, the setting of:
[CA_RECLAIM(NONE|{DATACLAS|DATACLASS})]
2. At the DATACLAS level for new SMS-managed data sets, the setting of
CA Reclaim, which will affect what is set in the catalog when a data set
is allocated.
3. At the data set level, in IDCAMS, what you specify for
RECLAIMCA|NORECLAIMCA on an ALTER command. ALTER, of course, works for
existing data sets.
The z/OS V2.1 Init Tuning Reference says the default for (1) remains
NONE. There is also an INFO APAR about CA Reclaim enablement that I
have not read, II14640, which you might find helpful.
Also, note that CAs that are empty when the system or data set is
enabled won't be reclaimed immediately, if ever. So you might need one
last reorg. Or not, depending.
HTH,
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
ee...@us.ibm.com
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CA/Reclaim Question
On Wed, 11 Feb 2015 23:27:23 -0500, Mark Jacobs - Listserv wrote: We have a VSAM KSDS that was allocated and populated with data prior to the CA/Reclaim function being available. This evening we had to reorg the dataset, and the REPRO back used the same physical dataset with the REPLACE and REUSE options. Does this enable CA/RECLAIM for the dataset, or do we have to allocate an entirely new KSDS? -- The default for existing data sets is enabled: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d4a0/2.5.3.3.2 LISTCAT ENT(...) ALL shows SMSDATA STORAGECLASS - xx DATACLASS xx CA-RECLAIM-(YES) The reorg removed the empty CAs that already existed when CA reclaim was enabled http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d4a0/2.5.3.3.1 Norbert Friemel -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CA/Reclaim Question
We have a VSAM KSDS that was allocated and populated with data prior to the CA/Reclaim function being available. This evening we had to reorg the dataset, and the REPRO back used the same physical dataset with the REPLACE and REUSE options. Does this enable CA/RECLAIM for the dataset, or do we have to allocate an entirely new KSDS? -- Mark Jacobs Time Customer Service Technology and Product Engineering The standard you walk past is the standard you accept. Lt. Gen. David Morrison -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
