Re: Duplicate Dataset
Posted: Wed Feb 22, 2012 6:55 pm
Its a user dataset and is available in only SMS managed volumes.
Mainframe Technical Support Forums
http://www.ibmmainframeforum.com/
https://www.ibmmainframeforum.com/system-programming/topic7218-10.html
STEP0 OUTFILE2 - ALLOCATION FAILED DUE TO DATA FACILITY SYSTEM
IGD17001I DUPLICATE DATA SET NAME ON VOLUME TST002
FOR DATA SET RCIP00S.JDH.DUMP.PROD
IGD17001I DUPLICATE DATA SET NAME ON VOLUME TST003
FOR DATA SET RCIP00S.JDH.DUMP.PROD
IGD17001I DUPLICATE DATA SET NAME ON VOLUME TST001
FOR DATA SET RCIP00S.JDH.DUMP.PROD
“If the system cannot find volume information for the data set on the DD statement, in the catalog, or passed with the data set from a previous step, the system assumes that the data set is being created in this job step.â€
expat wrote:Which volume does the catalog point to, if anywhere for this dataset.
Have you done a 3.4 on each of the volumes listed in the error messages to see if the dataset does indeed exist on those volumes.
NicC wrote:What is your JCL for the delete step?
NicC wrote:Whoops!
What I do see is that in the delete youa re using UNIT=DISK and in your create step you are using UNIT=SYSDA. These may, or may not, point to the same set of dasd.
Oh, and try using SPACE=(TRK,0) in your delete step. You are deleting a file therefore you do not need any space allocated. Won't affect your problem but it is just neater.
expat wrote:I suggest that you use IDCAMS for deleting datasets, far more reliable than IEFBR14 if your site still uses esoteric DASD pooling, as pointed out by Nic, the unit does differ between the delete and create steps.
Also, you will need to use IDCAMS again to delete the NVR from each of the volumes on which the rogue dataset resides. If the volumes are non SMS managed, then perhaps IEHPROGM may be required.