We had a user-catalog-vs-ISPF-3.4 problem that kind of surprised us. When we did a 3.4. request with a Dsname Level of SD* we would see old entries in the listing with data set names of the form SDB4.DATASET.ETC. These were old data set names that pointed to non-existent volumes. However if we issued ISPF-3.4. with a Dsname level of SDB4.* no entries would show up. (There was no ALIAS entry in the master catalog for SDB4). . We suspected that the problem was somehow related to a catalog issue so we listed all the catalog entries in all the catalogs, user and master. We found the funny entries in one of the user catalogs and did an IDCAMS delete noscratch (pointing to the problem catalog) to get rid of them. . Apparently there had been, at one time, an ALIAS entry that pointed to the user catalog, but it had been removed. Apparently by looking for SD*, ISPF cycled through the user catalog in question, but when looking for SDB4.* it quit when it determined that there was no ALIAS entry for SDB4. . Q: Is there a handy utility to check for 'orphan' catalog entries in user catalogs with no ALIAS pointer?
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
