> Use ISMF or something like that to search for all your 'other' dataset on all > of your catalogs. Just to make sure there is not another [unwanted] duplicate > on another volser. Just review your Linklist and APF that they are referring > to the correct dataset and/or volser where applicable. I have spent an inordinate amount of time already wading through the contents of the ADCD supplied disks. I have already cleaned up quite a few obsolete (empty) catalog entries. I am currently attempting to copy the SMP/E environment that comes with the ADCD setup so that I can install maintenance without risking an IPL and/or a non-IPLable system (can you say linklib goes into extents while running apply?). I have deleted about a thousand obsolete DDDEFs that were carried over from who knows when, using an official 1.13 program directory. While copying target libraries to a mod9 (and cleaning up the placement of them) I found out that quite a few of these target libraries are much much bigger than they should be (as in 4000 tracks instead of 300). This indicates to me that they were carried over from the last millenium and never cleaned up. Which is actually funny, since the ADCD systems come packaged for mod3 sized volumes, and DASD space is at a premium for those mod3!
> >On the other hand, this catalog (USERCAT.Z113.PRODS) contains a lot of the > >same data sets as the master catalog. > Wasn't that user cat not an old master catalog? I have no clue. It comes with the ADCD setup. A few products come with their own HLQ (not SYS1), but nobody bothered to define an alias for those HLQs. There were also some empty aliases without any data sets behind them. My guess is that what I am seeing is a badly executed cloning job for this delivered system. This is kinda confirmed by the jcl that was apparently used to install - it uses fairly different volsers that are not available to this system. What I find much worse is that the USS file systems are called HFS and ZFS and they have no alias entry anywhere. Hence they're catalogued in master cat. And some of them are called ZFS as their HLQ, but they are actually HFSs. I don't think I have any chance to define an alias when there are already data sets with that HLQ in the master cat. And given that this is my favourite USS, I cannot even rename them, define the alias and copy them back (when they're VSAM, they need to be physically copied, rename won't work). > If you have say, XYZ.* on mastercatalog and also on usercatalog, then if you > don't have an alias, you would see the entries on mastercatalog. But if you > create an alias, you should see the entries on the usercatalog. But in your > case, you're referring to SYS1.* entries, so you're probably sitting with > duplicate entries. Yes, that explains the first data set I found while copying DLIBs. That one existed in the usercat and on the distribution volume with a SYS1 HLQ, which *should* have been catalogued in the master cat, not a user cat. The second DLIB data set doesn't have an alias entry in the master cat, so it couldn't be found using standard search order. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
