Hi Brad/Judith,

I see you tried: DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00)
DEVT(3390) VOL(Z1SW01))

Maybe the same DEFINE but with RECATALOG would work in this case.
Something like: DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00)
DEVT(3390) VOL(Z1SW01) RECATALOG)

Regards,


-------------------------------------------------------------------------------------------------------------------------------
*Lucas Rosalen*
[email protected] / [email protected]
http://br.linkedin.com/in/lrosalen


2018-07-06 1:02 GMT+02:00 Jackson, Rob <[email protected]>:

> That's because if the original attempt was tape, there's definitely no NVR.
>
> Sorry, when I mentioned IEHPROGM earlier, I was actually thinking of the
> CATLG command, as in CATLG DSNAME=dataset,VOL=3390=whocares (disk doesn't
> matter, because you just want an entry you can actually delete).  I thought
> about IEHPROGM, because it's still sort of "dumb," and just does what it's
> told, and I hoped it might just make the entry in the catalog.  If it does,
> the base already has it rolled in, and you can simply delete it with
> noscratch.  I'm not sure your IEHPROGM results so far indicate anything
> other than there is no complete catalog entry.
>
> That's a shame about rename giving you a 040842CD, which says duplicate
> catalog entry exists.  It makes me think the IEHPROGM CATLG won't work
> either, despite being old school.  It depends upon which interfaces
> IEHPROGM does not respect (but which ISPF clearly does).
>
> First Tennessee Bank
> Mainframe Technical Support
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Nelson, Judith
> Sent: Thursday, July 05, 2018 5:59 PM
> To: [email protected]
> Subject: Re: [External] Re: remove bad GDG entry from GDG base
>
> [External Email]
>
> We tried. :(
>
>
>
>    DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 FILE(VOL2) NVR
>
> IDC3014I CATALOG ERROR
>
> IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-92
>
> IDC0551I ** ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT DELETED
>
> IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
>
>
> Judith Nelson  | Senior Systems Programmer Sammons® Financial Group Member
> Companies One Sammons Plaza  | Sioux Falls, SD 57193
> Phone: (605) 373-2321
> [email protected]<mailto:[email protected]>
>
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Tom Marchant
> Sent: Thursday, July 5, 2018 10:05 AM
> To: [email protected]
> Subject: [External] Re: remove bad GDG entry from GDG base
>
>
>
> On Thu, 5 Jul 2018 09:27:07 -0500, Brad Wissink wrote:
>
>
>
> >We need to remove a GDG entry from a GDG base, but the catalog entry
>
> >doesn't exist.  What happened was that during the creation of the GDG
>
> >(PTP.DP.TRMS.ARCH999.X3.G0308V00) the user catalog filled up and could
>
> >not extend.
>
>
>
> I suspect that the NVR was created in the VVDS. I would try DELETE NVR,
> followed by DEFINE.
>
>
>
> --
>
> Tom Marchant
>
>
>
> ----------------------------------------------------------------------
>
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected]<mailto:[email protected]> with the
> message: INFO IBM-MAIN
>
>
>
> The information contained in this message is confidential, protected from
> disclosure and may be legally privileged.  If the reader of this message is
> not the intended recipient or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any disclosure, distribution, copying, or any action taken or action
> omitted in reliance on it, is strictly prohibited and may be unlawful.  If
> you have received this communication in error, please notify us immediately
> by replying to this message and destroy the material in its entirety,
> whether in electronic or hard copy format.  Thank you.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected] with the message: INFO IBM-MAIN
> FIRST TENNESSEE
>
> Confidentiality notice:
> This e-mail message, including any attachments, may contain legally
> privileged and/or confidential information. If you are not the intended
> recipient(s), or the employee or agent responsible for delivery of this
> message to the intended recipient(s), you are hereby notified that any
> dissemination, distribution, or copying of this e-mail message is strictly
> prohibited. If you have received this message in error, please immediately
> notify the sender and delete this e-mail message from your computer.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to