So the error
  NOT DEFINED BECAUSE DUPLICATE NAME EXISTS IN CATALOG
States there is another dsn in the catalog. 

Did you go to 3.4 and see if there is a cataloged version?  Did you see one
and then use PF 11 to see if there was space or if it was just a catalog
entry?

What is it you are trying to do?  Can you restore with RENUNC instead and
see if that works?

Use ISMF Option 1 (Dataset) and do a generic search for catalog and
uncataloged datasets.

You JESMSGS should tell you where the dataset was going to.

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of esmie moo
> Sent: Thursday, September 18, 2014 8:34 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: DFDSS FAILED RESTORE
> 
> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to