Nope, that is not the original problem. What happened was that when I was working through a list of datasets that have not been used for over a year, I found out that some of those files were not catalogued. As those are (were) SMS managed datasets, this should not happen. The user catalogs are alright or we would be having a lot of problems. But , for some reason, some files were uncatalogued but not scratched from the VTOC. I suppose that can happen to some GDG entries when the base definition is "NOSCRATCH". But most of the files that I have found so far are not GDG entries. So, I need a process to find uncatalogued datasets that will not take ages to run, that will not be way too much CPU heavy, and that does not rely on vendor software other than the IBM software that we already have. And ideally I would not want to use REXX programming or if I have to use it, that it will be very simple, easy to understand and to maintain if such a need would arise. Regards Jack
On Tue, 26 Jul 2022 at 10:11, Colin Paice <[email protected]> wrote: > Do you need to worry about data sets cataloged in a user catalog, but the > user catalog is not connected to the master catalog - or is this part of > your original problem? > Colin > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
