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
On 07/05/2018 10:50 AM, Wissink, Brad wrote:
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
[email protected] | www.SammonsFinancialGroup.com
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Mike Schwab
Sent: Thursday, July 05, 2018 9:40 AM
To: [email protected]
Subject: [External] Re: remove bad GDG entry from GDG base
Create a dummy by specific number then delete?
On Thu, Jul 5, 2018 at 9:27 AM Brad Wissink <[email protected]> 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. 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 [email protected] with the message: INFO 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 email to
[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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
