View previous topic :: View next topic
|
Author |
Message |
Theo Buckton
New User
Joined: 07 May 2010 Posts: 2 Location: Cape Town, South Africa
|
|
|
|
How does one delete a Non-VSAM data set entry in a catalog? The data does not exist on a sms-managed volume even though it appears on the Data Set List Utility screen. I tried IDCAMS delete with scratch, with nscr, purge, and even IKJEFT01. Please advise accordingly.
IDC3009I ** VSAM CATALOG RETURN CODE IS 50- REASON CODE IS IGG0CLE0-6
IDC1566I ** QNGG00.XCOMPK.NEFPOT.D2.SQ132 NOT LISTED |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
IDCAMS command
Code: |
DELETE QNGG00.XCOMPK.NEFPOT.D2.SQ132 NOSCRATCH |
should remove the catalog entry.
Posting just an error message, without giving us the IDCAMS command you executed, is not conducive to getting your problem resolved -- we need ALL the information, not just what you want to give us, in order to help you. |
|
Back to top |
|
|
Theo Buckton
New User
Joined: 07 May 2010 Posts: 2 Location: Cape Town, South Africa
|
|
|
|
Thanks for replying. My apologies for insufficient information.
I tried the following:
DELETE QNGG00.XCOMPK.NEFPOT.D2.SQ132 -
CATALOG(CATALOG.QAPLEX.APPL.GENL) FILE(DD1)
DC3014I CATALOG ERROR
DC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54
DC0551I ** ENTRY QNGG00.XCOMPK.NEFPOT.D2.SQ132 NOT DELETED
DC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
DC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8
DEL QNGG00.XCOMPK.NEFPOT.D2.SQ132 FILE(DD1) NVR
DEL QNGG00.XCOMPK.NEFPOT.D2.SQ132 FILE(DD1) VVR
All results point to a delete error in the catalog:
VSAM CATALOG RETURN CODE IS 90 |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
First, we need to find out just what you are attempting to do. Using the NVR format indicates the file is a non-VSAM file. Using the VVR format indicates the file is a VSAM file. Doing the DELETE with a CATALOG and FILE points you to a particular disk pack -- whichever disk pack DD1 points to. So you have now managed to completely confuse us about just what you are attempting to accomplish.
Is data set QNGG00.XCOMPK.NEFPOT.D2.SQ132 cataloged?
If so, which disk pack does the catalog point to?
And also, which catalog contains the data set entry -- CATALOG.QAPLEX.APPL.GENL or some other catalog?
Is it a sequential file?
Is it a VSAM file?
Does it exist on a disk pack?
If so, which disk pack is it on?
As I earlier posted, which you completely ignored, if you are attempting to remove a catalog entry where the data set does not exist on the disk pack, DELETE QNGG00.XCOMPK.NEFPOT.D2.SQ132 NOSCRATCH is the easiest way. Note there is no CATALOG nor FILE option specified on this command -- which is how I know you completely ignored my previous post. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hi Robert,
My guess is that we've joined the hunt "in the middle". . .
After some amount of flailing about, this has been posted to try to get back to "clean".
I guess that after spending time tring to fix what was broken (or at least bent), there is some reluctance to simply try the posted solution. . .
d |
|
Back to top |
|
|
Ajay Baghel
Active User
Joined: 25 Apr 2007 Posts: 206 Location: Bangalore
|
|
|
|
You can also try
DISP=(OLD,DELETE,DELETE) with IEFBR14 as well to delete the dataset. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
Message RETURN CODE IS 50- REASON CODE IS IGG0CLE0-6
indicates a missing VVDS record.
And the other message you mention IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 indicates there was an 'incomplete delete'. This can occur if a job that's deleting or renaming a file is cancelled or abends for example. The delete gets rid of the VVDS entry (VVR or NVR) first, then the DSCB and then the catalog record in that order so if it's cancelled you can get a few bits left over sometimes.
It may be an orphaned DSCB in the VTOC. which a DFDSS physical DUMP DELETE pointing to the volser its cataloged to can get rid of.
You might want to do and IDCAMS DIAGNOSE for this dataset as that will indicate more clearly what the problem is
You should probably involve your Storage Admin team in this really. |
|
Back to top |
|
|
|