On 1 Dec 2010 13:36:30 -0800, in bit.listserv.ibm-main you wrote: >On Wed, 1 Dec 2010 03:33:24 -0600, Elardus Engelbrecht ><elardus.engelbre...@sita.co.za> wrote: > >>Dr. Stephen Fedtke wrote: >>>what is the best method to achieve a complete list of all currently >>cataloged data sets? really "all". actually, like using "**" in the 3.4 >data set >>criterion. >> >>Use Catalog Search Interface with Assembler or REXX. >> >>It is faster than =3.4 or IDCAMS LISTC and perhaps ISMF too. >> > > >3.4 doesn't allow * or **. > >No options with IDCAMS to list everything from all catalogs. > >The CSI is a good option, but since if you tell it to list all catalogs you >could >end up with a bunch of "dead" catalog entries. For example, a user catalog >that was previously a master from another system, or an alias for an HLQ >points to the "correct catalog" but maybe pointed to a different catalog at >one time and the entries weren't deleted or merged out. No one would >ever know about those entries to clean them up unless they looked for them. >(you can do this with CATSRCH from my web site: TSO %CATSRCH ** > > >If you did it with CSI and wrote intelligent code around it, then it would >be more accurate. For example, list the master catalog and the aliases, >then only list the HLQs in the catalogs that the aliases in the master catalog >pointed to.
If I were bothering to list all catalog entries, I would want two lists - the good entries and the bad ones. Getting rid of garbage and confusion is goodness. Clark Morris > >Mark ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
