IBM Mainframe Forum

I have tried everything I can to delete this dataset like DELETE VVR and things....The dataset does not show on volume now....but shows only in 3.4 ...But ACSVS.ETFR.V122.CSI does not show up in 3.4 but ACS%S.ETFR.V122.CSI.DATA shows up

DEFINE CLUSTER -
(NAME(ACSVS.ETFR.V122.CSI) -
RECATALOG VOLUMES(PP0005))-
DATA (NAME(ACSVS.ETFR.V122.CSI.DATA) VOLUMES(PP0005)) -
INDEX (NAME(ACSVS.ETFR.V122.CSI.INDEX) VOLUMES(PP0005))
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 86 - REASON CODE IS IGG0CLEY-6
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12

Sounds like you've got an orphan. This is what happens when someone deletes a VSAM dataset incorrectly, and the catalog entries don't get removed correctly as a result. So:

1) Identify the correct catalog with the entry, using the IDCAMS LISTCAT utility.
2) Delete with the following IDCAMS statement, using the correct catalog:
DELETE ACSVS.ETFR.V122.CSI.DATA CATALOG(CATALOG.DS.NAME)

This example assumes the VTOC entry does not exist, so make sure. The easiest way to check is to do a 3.4 on the volume. If it shows up there, your dataset isn't deleted.

It is not clear from what you have posted what the problem is. If the DATA component exists without a catalog entry, you need to use IDCAMS command where DD is a DD name pointing to the volume serial. You can do the same with the INDEX component if it exists without a catalog entry. If the catalog entry exists without the data sets being on the volume serial, you'll need to delete the catalog entry (see NOSCRATCH in the IDCAMS manual DELETE command).

Yes the dataset was their wothout a volume

My colleague did DEl NOSCR with the catalog and it worked....

Thanks

Robert Sample wrote:It is not clear from what you have posted what the problem is. If the DATA component exists without a catalog entry, you need to use IDCAMS command

Select all

DELETE ACSVS.ETFR.V122.CSI.DATA NVR FILE(DD)

where DD is a DD name pointing to the volume serial. You can do the same with the INDEX component if it exists without a catalog entry. If the catalog entry exists without the data sets being on the volume serial, you'll need to delete the catalog entry (see NOSCRATCH in the IDCAMS manual DELETE command).

Just when I needed something like this, you come along!

Any hints as how I would find all datasets on every volume that only exist as a VTOC entry?

Glad to hear the time was right!

We usually run across uncataloged datasets by accident. The DCOLLECT D type record has a bit flag in information byte #2 (offset 70) at the third bit in (..1. ....) iwhich ndicates whether or not the data set is cataloged in an ICF catalog.

Robert Sample wrote:Glad to hear the time was right!

We usually run across uncataloged datasets by accident. The DCOLLECT D type record has a bit flag in information byte #2 (offset 70) at the third bit in (..1. ....) iwhich ndicates whether or not the data set is cataloged in an ICF catalog.

I have slightly elevated RACF privileges on a z/OS system, and occasionally come across them. The method of getting rid of VTOC remnants of VSAM files works like a charm, but I've also got datasets in the VTOC that are resistant to the method - I get a message that the delete is successful, but when I go back to the volume in ISPF option 3.4, the data set is still there.

Any clues?

I suppose that the final method would be to ZAP the VTOC. A long long time since I've done that.

Think that the program name may have changed since the dark ages when I last run one, but maybe a google on AMASPZAP might help you out here for deleting the FORMAT1 DSCB entry.