DELETE DEVE.ZSSV.ZOD000 PURGE CLUSTER
IDC0550I ENTRY (A) DEVE.ZSSV.ZOP000 DELETED
IDC0550I ENTRY (A) DEVE.ZSSV.ZOX000 DELETED
IDC0550I ENTRY (A) DEVE.ZSSV.ZOQ000 DELETED
IDC0550I ENTRY (A) DEVE.ZSSV.ZOY000 DELETED
IDC0550I ENTRY (A) DEVE.ZSSV.ZOD000 DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
This is confusing. Your DELETE said CLUSTER but the (A) in the messages
indicates non-VSAM; I would expet that to fail. It also deleted 4
names in addition to the name you specified. those might have been
aliases of the base name but I expected aliases to show type (X).
You can't tell what volumes the dataset was deleted from. I suppose it
is possible that since you said CLUSTER but the catalog entry was
non-VSAM it deleted the catalog but not the DSCB from disk, which would
explain the following error.
IF LASTCC < 12 -
THEN ALTER DEVE.ZSSV.TMP -
NEWNAME(DEVE.ZSSV.ZOD000)
IDC3026I DUPLICATE DATA SPACE NAME ON VOLUME
IDC3009I ** VSAM CATALOG RETURN CODE IS 172 - REASON CODE IS IGG0CLEC-4
IDC0532I **ENTRY DEVE.ZSSV.TMP NOT ALTERED
If the dataset being renamed is on a different volume from the dataset
being deleted earlier, and there is an uncataloged copy of the newname
on that volume, then this could occur. Or it could be that the DSCB was
not deleted as I suggeste earlier.
I would usually try to test, but I have no time now
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
