On Thu, 22 Mar 2012 11:59:09 -0400, Robert A. Rosenberg wrote: >At 06:24 -0700 on 03/22/2012, John Dawes wrote about UNABLE TO DELETE >DUPLICTE DSN: > >>G'Day I am trying to delete a duplicate dsn via TSO. Since the >>cataloged version which resides on volume MPR003 is in use, I >>thought that I could rename the duplicate dsn which resides on >>MPR027. However when I try to rename the dsn (via TSO) it gave me >>the message "Duplicate data set name" followed by "Data set is >>cataloged on a volume other than MPR027". Both volumes are managed >>by SMS. Is there some other tactic I could employ? Thanks. > >Since the problem is that the DSN Name is enqueued upon (which is
That's not what the OP wrote. The problem is that the data set is on an SMS-managed volume and the catalog says that the data set is on a different volume. >you need to rename >the dataset you want to delete (so it is not a duplicate of a dataset >with a current ENQ). One way to do this is to use SUPERZAP to edit >the VTOC entry to alter the dataset name. Not a great idea, IMO. >Once this is done you can >then do the delete. This may leave a orphan record in the VTOCIX Also in the VVDS. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
