Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Goto page 1, 2  Next
 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sat Mar 07, 2009 1:45 pm    Post subject: VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Reply with quote

Hi
I've faced a problem while I'm taying to delete a QSAM
following messages is appeared :

IDC3012I ENTRY BUAEDP7.TSBRHM.D2008143.T205715 NOT FOUND+
IDC0551I ** ENTRY BUAEDP7.TSBRHM.D2008143.T205715 NOT DELETED
IDC0014I LASTCC=8
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10202
Location: italy

PostPosted: Sat Mar 07, 2009 1:51 pm    Post subject: Reply to: VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG
Reply with quote

and ...

where is the problem?? what does the messages manual tell ??

but even without looking at the manual
the first message in the sequence is clear, isn' t it ??
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sat Mar 07, 2009 2:20 pm    Post subject:
Reply with quote

It's in TSO
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sat Mar 07, 2009 8:58 pm    Post subject:
Reply with quote

Hello,

Is the problem file now "deleted"?

As Enrico mentoned, this should be enough to resolve the error:
Quote:
BUAEDP7.TSBRHM.D2008143.T205715 NOT FOUND
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 9:46 am    Post subject:
Reply with quote

Hi Dick
no not yet
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Mar 08, 2009 10:15 am    Post subject:
Reply with quote

Hello,

If the delete cannot find the dataset, can you see it in a tso/ispf 3.4 list of datasets?
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 11:23 am    Post subject:
Reply with quote

Yes I can see it and the releated information but when I'm trying to listc the data set not found is appeared.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Mar 08, 2009 11:37 am    Post subject:
Reply with quote

Hello,

Is this by chance a gdg base?

If so, it cannot be deleted the same way a file is deleted. Is there anything other than the base defined?
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 11:54 am    Post subject:
Reply with quote

No, it is not GDG base.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Mar 08, 2009 12:03 pm    Post subject:
Reply with quote

Hmmm. . .

What volser does 3.4 show for the file? It is not a tape file?

What happens if you try to delete this file from 3.4?
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 12:07 pm    Post subject:
Reply with quote

It is on DASD volume the above messages is appeared when I try to delete.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Mar 08, 2009 12:15 pm    Post subject:
Reply with quote

Hello,

Look in the vtoc where the dataset is cataloged. It is possible that there is a catalog entry, but no entry in the vtoc.

If this is the case, you would uncatalog the file rather than delete it.

If this is the case, it would be advisable to determine how the file was deleted and the catalog entry left behind.
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 1:00 pm    Post subject:
Reply with quote

It's information is existing in the Volume's VTOC, but the data set is not cataloged and I can not catalog it.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Sun Mar 08, 2009 1:36 pm    Post subject:
Reply with quote

Then you need to delete it by naming the volser in the delete.

When the volser is not mentioned, the catalog is searched and this causes the "not found". As i mentioned earlier, it sounds like the catalog and the vtoc have somehow gotten out of sync.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Sun Mar 08, 2009 1:49 pm    Post subject:
Reply with quote

Clarification required here .................

You say that the dataset is visible under 3.4, yet later state that the dataset is uncataloged. So, are you using 3.4 with a volume specified.

If it is uncataloged, have you tried DELETE NVR
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 4:06 pm    Post subject:
Reply with quote

By naming the volume in the volser it can not be deleted and the following message in the job is appeared :

Code:
IEF344I DELETE DELETE DEL - ALLOCATION FAILED DUE TO DATA FACILITY SYSTEM ERROR
IGD301I DATA SET ALLOCATION REQUEST FAILED -                                   
DATA SET BUAEDP7.TSCUSM.D2008143.T205715                                       
IS NOT ELIGIBLE FOR ALLOCATION ON SMS-MANAGED VOLUME SMTG18                   

the related job is

Code:
000001 //DELETE   JOB CLASS=A                                                 
000002 //DELETE EXEC PGM=IEFBR14                                             
000003 //DEL   DD DSN=BUAEDP7.TSCUSM.D2008143.T205715,                       
000004 //         DISP=(MOD,DELETE),SPACE=(TRK,1),VOL=SER=SMTG18


Edited: Please use BBcode when You post some code/error, that's rather readable, Thanks... Anuj
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 4:19 pm    Post subject:
Reply with quote

expat wrote:
Clarification required here .................

You say that the dataset is visible under 3.4, yet later state that the dataset is uncataloged. So, are you using 3.4 with a volume specified.

If it is uncataloged, have you tried DELETE NVR


Hi Expat
It is visible in P.3.4 with out volume specification.
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Sun Mar 08, 2009 6:15 pm    Post subject:
Reply with quote

following messages appeared by using NVR to delete :

IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE4-88
IDC0551I ** ENTRY BUAEDP7.TSCUSM.D2008143.T205715 NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
Back to top
View user's profile Send private message
kalhor

New User


Joined: 20 May 2007
Posts: 31
Location: iran

PostPosted: Mon Mar 09, 2009 1:30 pm    Post subject:
Reply with quote

The data set is a part of multi volume data set which the main part is not available. (DSORG=PS-E)
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Mar 09, 2009 2:42 pm    Post subject:
Reply with quote

Maybe (If you are authorised) you can DELETE NOSCR and then use AMASPZAP to delete the VTOC entry.

You may need to contact your storage admin people to do this for you, or even your systems programmers.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Goto page 1, 2  Next
Page 1 of 2

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts PL/I code tuning/Performance improvement Virendra Shambharkar PL/I & Assembler 4 Mon Dec 05, 2016 11:57 am
No new posts What is the code in CLIST to enable t... jackzhang75 CLIST & REXX 1 Fri Dec 02, 2016 3:02 am
No new posts IDEAL - Code Retrieval yugendran CA Products 0 Fri Nov 25, 2016 3:27 pm
No new posts DFHWS2LS return value divated CICS 4 Mon Nov 07, 2016 5:44 pm
No new posts BWO option in VSAM blayek CICS 3 Sat Nov 05, 2016 10:47 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us