Just as a suggestion, why not use the RENAMEU(xxxxxx) parm so that the dataset will go down with a different name.
*George Rodriguez* *Specialist II - IT Solutions* *IT Enterprise Applications* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-251* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Eight Consecutive Years* On Thu, Sep 18, 2014 at 11:34 AM, esmie moo <esmie_...@yahoo.ca> wrote: > Good Day Gentle Readers, > I am trying to trouble shoot the problem of a failed DFDSS restore. So > far I am unable to find the reason. The dsn (at the time of the restore) > was allocated on a volume but I do not know on which volser. However, the > restore failed even though the REPLACE parm was used. I was told that the > dsn (which is SMS managed) was NOT in use at the time. > I have a suspicion that the dsn resided on another volume which was not in > the same STORCLAS/STORGRP which may be the cause of the failure. A > colleague and I reviewed the SMS ACS routines and all is in order. The > bypass of STORAGE CLASS (via jcl is permitted and is valid) and it is not > GUARANTEE SPACE.I would appreciate your thoughts in knowing the cause of > the failure. > > PAGE 0001 5695-DF175 DFSMSDSS V1R13.0 DATA SET SERVICES > - RESTORE INDDNAME(TAPE01) - > DATASET(INCLUDE(DBU3705.SYSCICS.**)) - > OUTDDNAME(DASD01) - > STORCLAS(SYSP0101) - > REPLACE > ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE > ' > ADR109I (R/I)-RI01 (01), 2014.256 09:53:27 INITIAL SCAN OF USER CONTROL > STATEMENTS COMPLETED > ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK > 0ADR006I (001)-STEND(01), 2014.256 09:53:27 EXECUTION BEGINS > 0ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN > PHYSICAL DATA SET FORMAT AND WAS CREATED BY > > DFSMSDSS VERSION > 1 RELEASE 13 MODIFICATION LEVEL 0 ON > 0ADR709E (001)-VDSS (01), AN ERROR OCCURRED IN THE STORAGE MANAGEMENT > SUBSYSTEM WHILE ALLOCATING DATA SET > > DBU3705.SYSCICS.BTCH. SMS > MESSAGES FOLLOW. > IGD01010I STORCLAS SYSP0101 - STORGRP=SYSP010 > IGD17101I DATA SET DBU3705.SYSCICS.BTCH > NOT DEFINED BECAUSE DUPLICATE NAME EXISTS IN CATALOG > RETURN CODE IS 8 REASON CODE IS 38 IGG0CLEH > 0ADR809I (001)-VDSS (01), ADDITIONAL DIAGNOSTIC DATA FOR PRECEDING MESSAGE: > SC=SYSP0101 MC=NOBACKUP DC= > REQPRI=0000000015TRK REQSEC=0000000000TRK > REQVOLS=01 > //STEP03 EXEC PGM=ADRDSSU,REGION=5M > //SYSPRINT DD SYSOUT=* > //DASD01 DD DISP=SHR,UNIT=SYSDA,VOL=SER=CAP001 > //TAPE01 DD DSN=DBU3705.SUPRA.BKUPSYTT.CAP001., > // DISP=SHR > //SYSIN DD DISP=SHR,DSN=DBU3705.PDS.SYSIN(REST1) > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- *Disclaimer: *Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
