I used to do things like that. Then I decided that it wasn't worth the bother. I guess as I get older, I am not as concerned about keeping things "shiny like new".
On Thu, Jul 18, 2013 at 8:27 AM, Staller, Allan <[email protected]>wrote: > The cheapest solution is to define the "required" ucat. Issue a delete > command for that ucat against the VVDS, and then delete the recently > defined ucat. > A PITA granted, but it workds. > > HTH, > > <snip> > I don't think that IBM has a facility to clean up these types of records > in a VVDS. Dino Software's T-Rex does. > > > First of all, thanks for the interest. > > Snippet: > > IDC11367I THE FOLLOWING VVDS REFERENCED CATALOGS WERE NOT ENCOUNTERED: > > CATALOG.MVSICF1.VMVSE18 > ....snippage > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
