|
View previous topic :: View next topic
|
| Author |
Message |
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 :
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 |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
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 |
|
|
kalhor
New User
Joined: 20 May 2007
Posts: 31
Location: iran
|
|
|
|
| It's in TSO |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
kalhor
New User
Joined: 20 May 2007
Posts: 31
Location: iran
|
|
|
|
Hi Dick
no not yet |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If the delete cannot find the dataset, can you see it in a tso/ispf 3.4 list of datasets? |
|
| Back to top |
|
|
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. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
kalhor
New User
Joined: 20 May 2007
Posts: 31
Location: iran
|
|
|
|
| No, it is not GDG base. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
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. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
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. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
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 |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
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 |
|
|
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 :
| 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 |
|
|
kalhor
New User
Joined: 20 May 2007
Posts: 31
Location: iran
|
|
|
|
| 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 |
|
|
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 |
|
| Back to top |
|
|
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) |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
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 |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
Please run a LISTCAT ALL on the data component and post the results. |
|
| Back to top |
|
|
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 |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| kalhor wrote: |
| I've tryed to delete by NOSCR befor this but it could not be deleted |
Then you are probably not authorised to use the NOSCR parameter, hence my previous suggestion to talk to storage management / sysprogs who should be authorised to use this parameter. This was made quite clear in my previous post.
Anuj - pay attention  I believe that the OP has said that LISTCAT did not work in a previous post. He has also said that this is part of a multi vol dataset where the "main part" (which I would guess being volser 1) is unavailable. |
|
| Back to top |
|
|
kalhor
New User
Joined: 20 May 2007
Posts: 31
Location: iran
|
|
|
|
| No the authority is not my problem. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| What have you discovered by reading the messages and codes that have been issued so far ? |
|
| Back to top |
|
|
|
|
