VSAM Reason Code IGG0CLEG-42

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

Hi

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

enrico-sorichetti · Posted: Sat Mar 07, 2009 1:51 pm

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 ??

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

It's in TSO

dick scherrer · Posted: Sat Mar 07, 2009 8:58 pm

Hello,

Is the problem file now "deleted"?

As Enrico mentoned, this should be enough to resolve the error:

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

Hi Dick
no not yet

dick scherrer · Posted: Sun Mar 08, 2009 10:15 am

Hello,

If the delete cannot find the dataset, can you see it in a tso/ispf 3.4 list of datasets?

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

Yes I can see it and the releated information but when I'm trying to listc the data set not found is appeared.

dick scherrer · Posted: Sun Mar 08, 2009 11:37 am

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?

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

No, it is not GDG base.

dick scherrer · Posted: Sun Mar 08, 2009 12:03 pm

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?

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

It is on DASD volume the above messages is appeared when I try to delete.

dick scherrer · Posted: Sun Mar 08, 2009 12:15 pm

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.

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

It's information is existing in the Volume's VTOC, but the data set is not cataloged and I can not catalog it.

dick scherrer · Posted: Sun Mar 08, 2009 1:36 pm

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.

expat · Posted: Sun Mar 08, 2009 1:49 pm

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

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

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

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

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

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

The data set is a part of multi volume data set which the main part is not available. (DSORG=PS-E)

expat · Posted: Mon Mar 09, 2009 2:42 pm

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.

Anuj Dhawan · Posted: Mon Mar 09, 2009 4:09 pm

Hi,

Please run a LISTCAT ALL on the data component and post the results.

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

I've tryed to delete by NOSCR befor this but it could not be deleted

expat · Posted: Mon Mar 09, 2009 4:55 pm

kalhor · New User Joined: 20 May 2007 Posts: 31 Location: iran

No the authority is not my problem.

expat · Posted: Mon Mar 09, 2009 8:48 pm

What have you discovered by reading the messages and codes that have been issued so far ?

Potential causes associated with this reason code:

Dataset Not Found:
This reason code might indicate that the VSAM dataset being referenced does not exist or cannot be located by the system.

File Open Error:
It could also indicate a problem during the opening of a VSAM file, such as a failure to establish or access control blocks.

Invalid Key or Index:
This reason code may be triggered if an application attempts to access or process VSAM records using an invalid key or index value.

Permissions or Access Issues:
It could point to permissions or access-related problems, where the user or program does not have the necessary privileges to perform VSAM operations.

Resource Contention:
In some cases, this reason code might indicate resource contention or conflicts, such as simultaneous access attempts by multiple processes.

VSAM Catalog Issues:
It may also be related to problems within the VSAM catalog, such as inconsistencies or corruption in catalog entries or control structures.