I’m not a STORAGE guy. It means that I can look at stuff created by someone else. We seem to make odd use of DATACLAS here, but LISTCAT on the RMM data base shows that it's eligible. I also looked a troublesome user catalog; it's eligible as well.
Meanwhile I turned on CA reclaim in the sandbox environment just make sure we don't experience problems. Wait and see. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Greg Shirey Sent: Friday, October 07, 2016 2:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: VSAM CA reclaim for RMM Skip, The IGDSMSxx setting is either NONE or DATACLAS. So, it's not quite global - the VSAM file must be assigned a DATACLAS at creation which has CA RECLAIM set to Y. We modified all our Data Classes sometime in mid-2012, so our SMS-managed VSAM files have been reclaiming CA's for years. I spent a lot of time trying to determine a method of proving any benefit or detriment but never could. Sorry to be late joining the thread, been out for a few days... Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: Jesse 1 Robinson [mailto:jesse1.robin...@sce.com] Sent: Thursday, September 29, 2016 4:03 PM Subject: Re: VSAM CA reclaim for RMM Correcting ALTER syntax. -----Original Message----- From: Jesse 1 Robinson Sent: Thursday, September 29, 2016 1:59 PM To: 'IBM Mainframe Discussion List' <IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: VSAM CA reclaim for RMM Thanks. Spent some time this morning wading through the doc. Here's a thumbnail version of my understanding. -- CA reclaim must be 'turned on' at the system level in PARMLIB IGDSMSxx. Default value is 'off'. -- It can also be turned on or off for a system with a SETSMS command. -- Once turned on globally, CA reclaim will be in effect for (more or less) every VSAM cluster unless a cluster is specifically turned off. That is, the default at the cluster level is on. My RMM control data set is 'on' as shown by LISTCAT. -- You can turn a cluster off or back on with a simple ALTER command--which BTW I cannot find documented anywhere except in KC discussions of CA reclaim. For example, I cannot find any reference to reclaim in TSO HELP for ALTER. -- The IDCAMS command is "ALTER entry-name RECLAIMCA/NORECLAIMCA". That command is accepted now when I enter it even though we do not have reclaim turned on globally. So if you turned reclaim on for 'some user catalogs' and for SMS control data sets, did you take any action to turn it off for everything else in the house? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com > When CA reclaim was first presented at a closed SHARE session on a Sunday > morning, there was great interest in the room but also some skepticism. What > is the current consensus on CA reclaim? How extensively is it implemented > these days? Recommendations? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
