What ever tool you use to find all the Datasets you are looking for, be aware that there is a field called LADAT - Last Access Date for GDG's. This can reveal datasets that are older than 1 year. There can be 1000's of these. Reasons are Jobs become obsolete or are Replaced, so all their GDG's remain. Secondly, tape datasets could have been changed to disk with no update to the NOSCRATCH Setting or a GDG could have been mistakenly set to NOSCRATCH during initial setup. Finding and deleting these can free lots of disk.
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jack Zukt Sent: Saturday, July 23, 2022 5:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finding uncatalogued datasets Thank you all for your input. Regarding the last comments, my problem is that I have found multiple "SMS" uncatalogued datasets. A few are rolled out GDG versions, but most are not. And yes, the environment in a parallel sysplex with two master catalogs, but those files are all (were) in user catalogs visible on all lpars with shared alias. I am excluding from this search the master catalogue aliases, such as SYS1. Prior to looking for help I was considering a rexx using the catalog search interface to validate the files, but I would prefer a more standard approach if I could find one. Regards Jack On Sat, Jul 23, 2022, 01:00 Lennie Dymoke-Bradshaw < 0000032fff1be9b4-dmarc-requ...@listserv.ua.edu> wrote: > Be careful to pay attention to your configuration. If you are running > a sysplex with multiple Master Catalogs then you will likely find data > sets which are catalogued on the other system from the one where you are > running. > > Lennie Dymoke-Bradshaw > https://rsclweb.com > ‘Dance like no one is watching. Encrypt like everyone is.’ > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Gibney, Dave > Sent: 23 July 2022 00:24 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Finding uncatalogued datasets > > SMS shouldn't have uncataloged datasets. In reality, there are ways... > All of which should be considered an error. > > Of course, in my opinion. Most, if not all, uncataloged datasets are > likely in error. And the reason(s) for looking for them is to correct > these errors. > > So, I wouldn't exclude my SMS volumes from such a search. > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Mike Schwab > > Sent: Friday, July 22, 2022 4:08 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Finding uncatalogued datasets > > > > > > > > SMS storage groups can't have uncataloged data sets, so you can > > eliminate those volumes. > > > > On Fri, Jul 22, 2022 at 9:01 AM Jack Zukt <jzuk...@gmail.com> wrote: > > > > > > Hi all, > > > As a byproduct of what I am working now, I have found out a few > > > uncatalogued datasets. Now I would like to find out all the > > > uncatalogued datasets that are forgotten on the hundred of volumes > that are out there. > > > Using ADRDDSU and (CATLG EQ NO) is not an option as it would need a > DD > > > for each VOLSER. I could write a rexx that would read the DCOLLECT > > > VOLUMES(*) NODATAINFO and generate a JOB for each VOLSER or group > > of > > > VOLSERs but I really would like to use a more standard approach. I > > > seem to remember, from another age, that FDRABR could do it. > > > However > Dr. > > Google has > > > not been able to find me anything to that effect using only IBM tools. > > > Do you have any ideas how to go about this? > > > Your help will be, as always, greatly appreciated. > > > Regards, > > > Jack > > > > > > ------------------------------------------------------------------ > > > -- > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO > > > IBM-MAIN > > > > > > > > -- > > Mike A Schwab, Springfield IL USA > > Where do Forest Rangers go to get away from it all? > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
