You would see this on my systems also, because I use indirect catalog for SYSRES datasets, I manage multiple SYSRES's for the PLEX, one active and one for my SMPE env and one I copy maint to, be careful just relying on the vtoc list to delete any SYSx datasets one example
and check ieasym for SYSR2 symbolic - when one of my clients software was so large it spilled to a secondary SYSRES I used indirect cataloging &SYSRS2 that pointed to the secondary SYSRES SYS1.LINKLIB is on my current SYSRES my SMP and a maint volume (sysres) catalog entry is ENCRYPTIONDATA DATA SET ENCRYPTION-----(NO) VOLUMES VOLSER------------****** DEVTYPE------X'00000000' FSEQN---------- ASSOCIATIONS--------(NULL) ATTRIBUTES Carmen Vitullo ----- Original Message ----- From: "Tony Thigpen" <t...@vse2pdf.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, February 25, 2019 6:27:49 PM Subject: Identifying and eliminating uncataloged datasets I have inherited a system where nobody bothered to clean-up after themselves. If I do a DITTO VTOC of all the volumes, I can sometimes find 5 or 6 copies of the same dataset, some of which are SYSx.*. I would like to first rename all the uncataloged versions so I can eventually delete them. Does anybody know of a free tool that would help with this process? -- Tony Thigpen ---------------------------------------------------------------------- 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
