<snip> Looking to find the best process to identify and delete uncataloged data sets that are in SMS Pools. These can either be VSAM or NON VSAM data sets.
How often should this process run? How would I go about reducing or elimiating the fact data sets can be not cataloged in SMS Pools? <snip> If the pools are HSM managed, HSM issues a return code 70 (IIRC) for uncataloged datasets during backup and migration processing. Parse the HSM migration/backup logs to create a dataset list. If the quantity is small, I usually issue IDCAMS DEFINE ... RECATLOG, followed by DELETE. I have found that once a month or so is adequate to stay on top of the situation. YMMV. I do not think you can completely eliminate the possibility of having an uncataloged dataset in the SMS pool. Anyone with access to ISPF 3.4 can uncat a properly created SMS dataset and presto! A brand new instance of the problem. HTH, ---------------------------------------------------------------------- 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
