Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-23 Thread Shmuel Metz (Seymour J.)
In <4237C6039F26144AB6C2FF415A59F3B41287E0BA98@VA3DIAXVS341.RED001.local>, on 03/22/2012 at 08:34 AM, "Pesce, Andy" said: >It is still a feature. FSVO "it". >There are some small shops that do not use DFSMS. But none of them are running z/OS or OS/390. -- Shmuel (Seymour J.) Metz,

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-23 Thread Tom Marchant
On Thu, 22 Mar 2012 15:09:09 -0500, Paul Gilmartin wrote: >On Thu, 22 Mar 2012 13:27:43 -0500, Tom Marchant wrote: > >>That's not what the OP wrote. >> >The OP wrote "is in use". My mistake. Thanks for the correction. -- Tom Marchant ---

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Bonaduce, Frank
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of John Dawes Sent: Thursday, March 22, 2012 9:24 AM To: IBM-MAIN@bama.ua.edu Subject: 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 

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread retired mainframer
n List [mailto:IBM-MAIN@bama.ua.edu] On :>: Behalf Of John Dawes :>: Sent: Thursday, March 22, 2012 6:24 AM :>: To: IBM-MAIN@bama.ua.edu :>: Subject: UNABLE TO DELETE DUPLICTE DSN :>: :>: G'Day :>: :>: I am trying to delete a duplicate dsn via TSO.  Since the cataloged

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Paul Gilmartin
On Thu, 22 Mar 2012 13:27:43 -0500, Tom Marchant wrote: >On Thu, 22 Mar 2012 11:59:09 -0400, Robert A. Rosenberg wrote: > >>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 cata

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Tom Marchant
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 i

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Mike Schwab
I have had luck using TSO ISMF Dataset. Enter the DSN and volume. Enter a D on the display DSN line. It should detect if it is uncataloged or an additional volume to the cataloged dataset. It will give you a warning and reply as directed to continue. On Thu, Mar 22, 2012 at 8:24 AM, John Dawes wr

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread O'Brien, David W. (NIH/CIT) [C]
: Thursday, March 22, 2012 11:59 AM To: IBM-MAIN@bama.ua.edu Subject: Re: UNABLE TO DELETE DUPLICTE DSN 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 reside

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Robert A. Rosenberg
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. Ho

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread R.S.
W dniu 2012-03-22 15:54, Paul Gilmartin pisze: On Thu, 22 Mar 2012 10:44:16 -0400, Sevetson, Phil wrote: Rename the cataloged version to some [newname]. Catalog the uncataloged version and rename it to some [newname2]. Rename the [newname] back to the [original name]. Won't work. Why? I di

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Pesce, Andy
artin Sent: Thursday, March 22, 2012 9:51 AM To: IBM-MAIN@bama.ua.edu Subject: Re: UNABLE TO DELETE DUPLICTE DSN On Thu, 22 Mar 2012 07:42:39 -0700, Pesce, Andy wrote: >Even though it violates everything about being "Managed by SMS". >"IDCAMS Delete Noscratch" on a dataset that i

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Paul Gilmartin
On Thu, 22 Mar 2012 10:44:16 -0400, Sevetson, Phil wrote: >Rename the cataloged version to some [newname]. >Catalog the uncataloged version and rename it to some [newname2]. >Rename the [newname] back to the [original name]. > Won't work. >-Original Message- >From: IBM Mainframe Discussi

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Paul Gilmartin
On Thu, 22 Mar 2012 07:42:39 -0700, Pesce, Andy wrote: >Even though it violates everything about being "Managed by SMS". >"IDCAMS Delete Noscratch" on a dataset that is SMS controlled will indeed >leave the >dataset on the volume. > Is this a bug or a feature? Well, I suppose you need to be abl

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Sevetson, Phil
: Thursday, March 22, 2012 9:24 AM To: IBM-MAIN@bama.ua.edu Subject: 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 M

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Pesce, Andy
flist and I can give you details. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Walt Farrell Sent: Thursday, March 22, 2012 9:36 AM To: IBM-MAIN@bama.ua.edu Subject: Re: UNABLE TO DELETE DUPLICTE DSN On Thu, 22 Mar 2012 06:24:01 -0700, John

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread Walt Farrell
On Thu, 22 Mar 2012 06:24:01 -0700, John Dawes wrote: > 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 (v

Re: UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread McKown, John
ohn Dawes > Sent: Thursday, March 22, 2012 8:24 AM > To: IBM-MAIN@bama.ua.edu > Subject: 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 > thou

UNABLE TO DELETE DUPLICTE DSN

2012-03-22 Thread John Dawes
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"