Discussion:
remove bad GDG entry from GDG base
Add Reply
Brad Wissink
2018-07-05 14:27:15 UTC
Reply
Permalink
Raw Message
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.

GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+
IDC1566I ** PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED
IDC0014I LASTCC=4
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42

Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets

IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00
IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8
IDC0014I LASTCC=4

Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Mike Schwab
2018-07-05 14:39:56 UTC
Reply
Permalink
Raw Message
Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+
IDC1566I ** PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED
IDC0014I LASTCC=4
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00
IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8
IDC0014I LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Wissink, Brad
2018-07-05 14:50:57 UTC
Reply
Permalink
Raw Message
Trying to delete the GDG entry results in;

DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 NONVSAM NOSCRATCH PURGE

IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00
IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8
IDC0014I LASTCC=8


Trying to create the data set results in;

DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00) DEVT(3390) VOL(Z1SW01))

IDC3013I DUPLICATE DATA SET NAME+
IDC0014I LASTCC=12
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEH-8


Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511

***@sfgmembers.com | www.SammonsFinancialGroup.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Mike Schwab
Sent: Thursday, July 05, 2018 9:40 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base

Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+ IDC1566I **
PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED IDC0014I LASTCC=4 IDC3009I
** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jackson, Rob
2018-07-05 14:59:03 UTC
Reply
Permalink
Raw Message
Did you try IEHPROGM?

What happens if you create a different dataset and rename it to the messed up GDS?

First Tennessee Bank
Mainframe Technical Support

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Wissink, Brad
Sent: Thursday, July 05, 2018 10:51 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

[External Email]

Trying to delete the GDG entry results in;

DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 NONVSAM NOSCRATCH PURGE

IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I LASTCC=8


Trying to create the data set results in;

DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00) DEVT(3390) VOL(Z1SW01))

IDC3013I DUPLICATE DATA SET NAME+
IDC0014I LASTCC=12
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEH-8


Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266 Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511

***@sfgmembers.com | www.SammonsFinancialGroup.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Mike Schwab
Sent: Thursday, July 05, 2018 9:40 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base

Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+ IDC1566I **
PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED IDC0014I LASTCC=4 IDC3009I
** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Nelson, Judith
2018-07-05 21:43:28 UTC
Reply
Permalink
Raw Message
I am answering for Brad.

The entry has no disk volume associated with it, since it was created to tape. So there is no disk, no dates, no tape information, no MVS catalog connection; only an entry under the gdg base.



If you go into 3.4 and display it – you have to type the whole dataset name -, this is what I get:

Command - Enter "/" to select action Message Volume

Tracks % XT Device Dsorg Recfm Lrecl Blksz Created Referred

-------------------------------------------------------------------------------

PTP.DP.TRMS.ARCH999.X3.G0308V00



Nothing.



I tried iehprogm and got the following for an uncatlg:



UNCATLG DSNAME=PTP.DP.TRMS.ARCH999.X3.G0308V00

IEH210I YOUR REQUEST CANNOT BE SERVICED....

IT IS INVALID --OR-- IT IS NOT PROPER WITHIN YOUR PRESENT CATALOG STRUCTURE ... UNUSUAL END



And for a scratch:

SCRATCH DSNAME=PTP.DP.TRMS.ARCH999.X3.G0308V00

IEH205I INFORMATION IN CONTROL STATEMENT IS NOT SUFFICIENT

THE REQUESTED PROGRAM FUNCTION HAS NOT BEEN CALLED ... UNUSUAL END



I am sure it requires a Disk volume entry.



We tried the renaming, but get:

IEC614I RENAME FAILED - RC 008, DIAGNOSTIC INFORMATION IS (040842CD),

IKJACCNT,S10173,PTP.DP.TRMS.ARCH999.X3.H0308V00


Judith Nelson | Senior Systems Programmer
Sammons® Financial Group Member Companies
One Sammons Plaza | Sioux Falls, SD 57193
Phone: (605) 373-2321
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Jackson, Rob
Sent: Thursday, July 5, 2018 9:59 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base



Did you try IEHPROGM?



What happens if you create a different dataset and rename it to the messed up GDS?



First Tennessee Bank

Mainframe Technical Support



-----Original Message-----

From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU<mailto:IBM-***@LISTSERV.UA.EDU>> On Behalf Of Wissink, Brad

Sent: Thursday, July 05, 2018 10:51 AM

To: IBM-***@LISTSERV.UA.EDU<mailto:IBM-***@LISTSERV.UA.EDU>

Subject: Re: [External] Re: remove bad GDG entry from GDG base



[External Email]



Trying to delete the GDG entry results in;



DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 NONVSAM NOSCRATCH PURGE



IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I LASTCC=8





Trying to create the data set results in;



DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00) DEVT(3390) VOL(Z1SW01))



IDC3013I DUPLICATE DATA SET NAME+

IDC0014I LASTCC=12

IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEH-8





Brad Wissink| Sr. Systems Programmer

Sammons® Financial Group Member Companies

4350 Westown Pkwy | West Des Moines | IA 50266 Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511



***@sfgmembers.com<mailto:***@sfgmembers.com> | www.SammonsFinancialGroup.com<http://www.SammonsFinancialGroup.com>





-----Original Message-----

From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Mike Schwab

Sent: Thursday, July 05, 2018 9:40 AM

To: IBM-***@LISTSERV.UA.EDU<mailto:IBM-***@LISTSERV.UA.EDU>

Subject: [External] Re: remove bad GDG entry from GDG base



Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+ IDC1566I **
PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED IDC0014I LASTCC=4 IDC3009I
** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
--

Mike A Schwab, Springfield IL USA

Where do Forest Rangers go to get away from it all?



----------------------------------------------------------------------

For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Steve Thompson
2018-07-05 15:22:25 UTC
Reply
Permalink
Raw Message
Try to create a GDS with the name of
PTP.DP.TRMS.ARCH999.X3.G0308V01 << NOTE the VERSION number

You can fill this data set with the desired contents, or you can
make it a null data set (1 track and empty).

This might get you around the problem until those entries roll
out of the GDG base.

HTHs
Steve Thompson
Post by Wissink, Brad
Trying to delete the GDG entry results in;
DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 NONVSAM NOSCRATCH PURGE
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00
IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8
IDC0014I LASTCC=8
Trying to create the data set results in;
DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00) DEVT(3390) VOL(Z1SW01))
IDC3013I DUPLICATE DATA SET NAME+
IDC0014I LASTCC=12
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEH-8
Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511
-----Original Message-----
Sent: Thursday, July 05, 2018 9:40 AM
Subject: [External] Re: remove bad GDG entry from GDG base
Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+ IDC1566I **
PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED IDC0014I LASTCC=4 IDC3009I
** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
----------------------------------------------------------------------
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,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Nelson, Judith
2018-07-05 21:50:44 UTC
Reply
Permalink
Raw Message
I created one and it allocated it and cataloged, but did not get rolled into the GDG base. Tried in batch and manually.



I also tried to run:

//STEP005 EXEC PGM=IEBGENER

//SYSUT1 DD DISP=SHR,DSN=PTP.DP.TRMS.ARCH999.X3.G0308V00

//SYSUT2 DD DSN=PTP.DP.TRMS.ARCH999.X3.G0308V01,

// DISP=(NEW,CATLG,DELETE),

// UNIT=SYSDA,SPACE=(CYL,(5,5),RLSE)

//SYSPRINT DD SYSOUT=*

//SYSIN DD DUMMY



Getting a JCL error

IEFA107I JXNIEGOV STEP005 SYSUT1 - DATA SET PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND


Judith Nelson | Senior Systems Programmer
Sammons® Financial Group Member Companies
One Sammons Plaza | Sioux Falls, SD 57193
Phone: (605) 373-2321
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Steve Thompson
Sent: Thursday, July 5, 2018 10:21 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base



Try to create a GDS with the name of

PTP.DP.TRMS.ARCH999.X3.G0308V01 << NOTE the VERSION number



You can fill this data set with the desired contents, or you can make it a null data set (1 track and empty).



This might get you around the problem until those entries roll out of the GDG base.



HTHs

Steve Thompson
Post by Wissink, Brad
Trying to delete the GDG entry results in;
DELETE PTP.DP.TRMS.ARCH999.X3.G0308V00 NONVSAM NOSCRATCH PURGE
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=8
Trying to create the data set results in;
DEFINE NONVSAM(NAME(PTP.DP.TRMS.ARCH999.X3.G0308V00) DEVT(3390)
VOL(Z1SW01))
IDC3013I DUPLICATE DATA SET NAME+
IDC0014I LASTCC=12
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS
IGG0CLEH-8
Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266 Phone 515-267-2735 |
ext. 33735 | Cell: 515-231-1511
-----Original Message-----
On Behalf Of Mike Schwab
Sent: Thursday, July 05, 2018 9:40 AM
Subject: [External] Re: remove bad GDG entry from GDG base
Create a dummy by specific number then delete?
Post by Brad Wissink
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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.
GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+ IDC1566I **
PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED IDC0014I LASTCC=4 IDC3009I
** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets
IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00 IDC3902I **
DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 IDC0014I
LASTCC=4
Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?
---------------------------------------------------------------------
- For IBM-MAIN subscribe / signoff / archive access instructions,
IBM-MAIN
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
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
----------------------------------------------------------------------

For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2018-07-05 15:04:55 UTC
Reply
Permalink
Raw Message
Post by Brad Wissink
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Nelson, Judith
2018-07-05 21:59:25 UTC
Reply
Permalink
Raw Message
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
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jackson, Rob
2018-07-05 23:02:53 UTC
Reply
Permalink
Raw Message
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 <IBM-***@LISTSERV.UA.EDU> On Behalf Of Nelson, Judith
Sent: Thursday, July 05, 2018 5:59 PM
To: IBM-***@LISTSERV.UA.EDU
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
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lucas Rosalen
2018-07-06 07:44:41 UTC
Reply
Permalink
Raw Message
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*
***@gmail.com / ***@ibm.com
http://br.linkedin.com/in/lrosalen
Post by Jackson, Rob
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-----
Sent: Thursday, July 05, 2018 5:59 PM
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
-----Original Message-----
Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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
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
FIRST TENNESSEE
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,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Burrell, Todd
2018-07-07 13:59:07 UTC
Reply
Permalink
Raw Message
Have you tried DELETE dsn NSCR or just putting a U beside the entry in an ISPF 3.4 listing?



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Nelson, Judith
Sent: Thursday, July 05, 2018 5:59 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

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
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN



This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Nelson, Judith
2018-07-10 13:18:51 UTC
Reply
Permalink
Raw Message
Hi,
We finally were able to remove the bad with the help of TREX.
We were able to list the GDG GAT entries with TREX. After sending them the listings, they created a Zap for us to delete the entry.

I executed the zap and was able to create the entry the right way, it rolled right in. :)

This was something new to me. I guess I didn't know that when creating a GDG entry that the system rolled it in first and then catalogs it. Also didn't know about GAT entries.
Every day you learn something new. :)

Thanks everybody for your input.

Judith Nelson  | Senior Systems Programmer
Sammons® Financial Group Member Companies
One Sammons Plaza  | Sioux Falls, SD 57193
Phone: (605) 373-2321
***@sfgmembers.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Burrell, Todd
Sent: Saturday, July 7, 2018 8:59 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

Have you tried DELETE dsn NSCR or just putting a U beside the entry in an ISPF 3.4 listing?



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Nelson, Judith
Sent: Thursday, July 05, 2018 5:59 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

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
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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 ***@listserv.ua.edu<mailto:***@listserv.ua.edu> 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN



This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Styles, Andy , ITS zPlatform Services
2018-07-05 15:13:46 UTC
Reply
Permalink
Raw Message
Classification: Public
Not that I've ever played with them, but there are commands / options to ROLLIN and ROLLOFF GDS members of GDGs - could they help? Looks like IEHPROGM might be able to rebuild indexes too. Chapter 29 of Using Data Sets looks like the place to go.

Never played with any of them, but worth a look!

Andy Styles
z/Series System Programmer

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Brad Wissink
Sent: 05 July 2018 15:27
To: IBM-***@LISTSERV.UA.EDU
Subject: remove bad GDG entry from GDG base

-- This email has reached the Bank via an external source --


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. We received IEC331I 020-000..... error message on this. We corrected the catalog space issue, but the PTP.DP.TRMS.ARCH999.X3 GDG base has the G0308V00 GDG associated with it, but there is no catalog entry for G0308V00. if you do a LISTCAT ALL ENTRY(PTP.DP.TRMS.ARCH999.X3) this is what you get.

GDG BASE ------ PTP.DP.TRMS.ARCH999.X3
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2017.248
RELEASE----------------2 LAST ALTER------2018.184
ATTRIBUTES
LIMIT-----------------999 SCRATCH NOEMPTY LIFO NOPURGE EXTENDED
ASSOCIATIONS
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0001V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0002V00
.......
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0307V00
NONVSAM--PTP.DP.TRMS.ARCH999.X3.G0308V00
........
NONVSAM ---- PTP.DP.TRMS.ARCH999.X3.G0307V00
IN-CAT --- TAPE.USER.CAT
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.172
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------A58863 DEVTYPE------X'78048081' FSEQN------------------1
ASSOCIATIONS
GDG------PTP.DP.TRMS.ARCH999.X3
ATTRIBUTES
IDC3012I ENTRY PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT FOUND+
IDC1566I ** PTP.DP.TRMS.ARCH999.X3.G0308V00 NOT LISTED
IDC0014I LASTCC=4
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42

Doing a LISTCAT All ENTRY(PTP.DP.TRMS.ARCH999.X3.G0308V00) gets

IDC3901I ERROR QUALIFYING PTP.DP.TRMS.ARCH999.X3.G0308V00
IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8
IDC0014I LASTCC=4

Is there anyway to delete the unwanted GDG entry from the GDG base without have to delete and rebuild the GDG base?



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN


Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225 4555.

Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 2065. Telephone 0207626 1500.

Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone: 03457 801 801.

Lloyds Bank Corporate Markets plc. Registered office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 10399850.

Lloyds Bank plc, Bank of Scotland plc and Lloyds Bank Corporate Markets plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.

Halifax is a division of Bank of Scotland plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it (including any attachments) immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Telephone calls may be monitored or recorded.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2018-07-06 13:33:46 UTC
Reply
Permalink
Raw Message
Tried that too.
You might be down to DEL GDG RECOVERY followed by DEF GDG.

I have never done that, so I can't vouch for how it works, so if I were
you, I would create a GDG with several GDSes and experiment with that.

If that works the way we would hope, you may feel comfortable with
doing it on your problem GDG.
--
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Wissink, Brad
2018-07-06 13:42:14 UTC
Reply
Permalink
Raw Message
That is what we are going to do and have already began testing the process out. I would like to thank everyone for the help.

Brad Wissink| Sr. Systems Programmer
Sammons® Financial Group Member Companies
4350 Westown Pkwy | West Des Moines | IA 50266
Phone 515-267-2735 | ext. 33735 | Cell: 515-231-1511

***@sfgmembers.com | www.SammonsFinancialGroup.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Friday, July 06, 2018 8:34 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base
Tried that too.
You might be down to DEL GDG RECOVERY followed by DEF GDG.

I have never done that, so I can't vouch for how it works, so if I were you, I would create a GDG with several GDSes and experiment with that.

If that works the way we would hope, you may feel comfortable with doing it on your problem GDG.

--
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Marchant
2018-07-06 14:09:10 UTC
Reply
Permalink
Raw Message
Post by Wissink, Brad
That is what we are going to do and have already began testing the process out. I would like to thank everyone for the help.
Please let us know what you do how it goes.
--
Tom Marchant

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jim Beck
2018-07-06 14:28:09 UTC
Reply
Permalink
Raw Message
How about trying DEFINE NVSAM(NAME(.....) DEVT(....) VOL(......) RECATALOG ? I saw a post where a define nvsam failed with already cataloged. I have seen RECATALOG sometimes clean things up, but don't remember using it on a GDG.

Jim

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Nelson, Judith
2018-07-06 14:36:02 UTC
Reply
Permalink
Raw Message
We tried, - it errors on duplicate data set name.

Judith Nelson  | Senior Systems Programmer
Sammons® Financial Group Member Companies
One Sammons Plaza  | Sioux Falls, SD 57193
Phone: (605) 373-2321
***@sfgmembers.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Jim Beck
Sent: Friday, July 6, 2018 9:28 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

How about trying DEFINE NVSAM(NAME(.....) DEVT(....) VOL(......) RECATALOG ? I saw a post where a define nvsam failed with already cataloged. I have seen RECATALOG sometimes clean things up, but don't remember using it on a GDG.

Jim

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jesse 1 Robinson
2018-07-07 14:57:03 UTC
Reply
Permalink
Raw Message
Unless IBM can give you better advice in an SR, I would suggest abandoning this catalog altogether by doing a REPRO MERGECAT into a new one. This command allows filtering such that you can repro everything up to the problem entry, then repro everything after that. You might have to DEF NVSAM the squirrelly GDG entries, but that shouldn't be a burdensome task.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
***@sce.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Burrell, Todd
Sent: Saturday, July 07, 2018 6:59 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: (External):Re: [External] Re: remove bad GDG entry from GDG base

Have you tried DELETE dsn NSCR or just putting a U beside the entry in an ISPF 3.4 listing?



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Nelson, Judith
Sent: Thursday, July 05, 2018 5:59 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: [External] Re: remove bad GDG entry from GDG base

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
***@sfgmembers.com<mailto:***@sfgmembers.com>



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Tom Marchant
Sent: Thursday, July 5, 2018 10:05 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [External] Re: remove bad GDG entry from GDG base
Post by Brad Wissink
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Loading...