Hi Willie, I believe that Allan has hit the nail on the head for the solution, but i think you may also have to put a corresponding entry into the "dummy" bcs so that the delete nscr will match up on both sides. Just tried it on a pack on our sysprog lpar in the same situation, recreated the "lost" catalog and got an idc3012i on the delete nscr for the sys1.vvds.vxxxxx.
An inelegant solution but quick and easy would be to disnew the volume, empty it out (hsm migrate or dfdss copy etc.) then delete the vvds and define a nice new empty one, then enable the volume back to sms. Sod's law will probably have it that there's a permanently allocated dataset on the volume to put the kibosh on that idea! If you fancy being a guinea pig, theres "VVDSFIX" an unsupported IBM program you can download. You can read about and download this tool from this URL: http://www.ibm.com/support/docview.wss?uid=isg3S1000618 Was on a share presentation a few years back. Looks like it could be vaiable. Never used it, but i'm sure there are people around who have. Dave ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
