DFDSS FAILED RESTORE

[esmie moo]

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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Lizette Koehler]

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-----
Behalf Of esmie moo
Sent: Thursday, September 18, 2014 8:34 AM
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
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

[esmie moo]

I picked up this problem thread 'after the fact". I understand that the dsn existed what I cannot figure out why the REPLACE didn't work. Was it because perhaps the dsn (which was on disk) resided in a different STORCLAS/STORGRP?
--------------------------------------------
On Thu, 9/18/14, Lizette Koehler <***@MINDSPRING.COM> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, September 18, 2014, 11:38 AM

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-***@LISTSERV.UA.EDU]
On

Behalf Of esmie moo
Sent: Thursday, September 18, 2014 8:34

AM

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

                       

   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
with the message: INFO IBM-MAIN

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


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

[George Rodriguez]

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*
*[phone] (office)*
*[phone] (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*

Post by esmie moo
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
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,

--
*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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

[Staller, Allan]

You can also use recatalog(*) to update the catalog with the new copy.
The replace parameter may also be needed.

<snip>

Just as a suggestion, why not use the RENAMEU(xxxxxx) parm so that the dataset will go down with a different name.​

Post by esmie moo
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
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)

</snip>

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

[esmie moo]

Thanks Alan for pointing the RECATALOG(*) option. The user didn't want to the rename because he wanted the dsn on the specific volume.
--------------------------------------------
On Thu, 9/18/14, Staller, Allan <***@KBMG.COM> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, September 18, 2014, 11:54 AM

You can also use recatalog(*) to
update the catalog with the new copy.
The replace parameter may also be needed.

<snip>

Just as a suggestion, why not use the RENAMEU(xxxxxx) parm
so that the dataset will go down with a different name.​

Post by esmie moo
Good Day Gentle Readers,
I am trying to trouble shoot the problem of a failed

DFDSS restore. 

Post by esmie moo
So far I am unable to find the reason.  The dsn

(at the time of the

Post by esmie moo
restore) was allocated on a volume but I do not know on

which volser. 

Post by esmie moo
However, the restore failed even though the REPLACE

parm was used.  I

Post by esmie moo
was told that the dsn (which is SMS managed) was NOT in

use at the time.

Post by esmie moo
I have a suspicion that the dsn resided on another

volume which was

Post by esmie moo
not in the same  STORCLAS/STORGRP which may be the

cause of the

Post by esmie moo
failure.  A colleague and I reviewed the SMS ACS

routines and all is

Post by esmie moo
in order.  The bypass of STORAGE CLASS (via jcl is

permitted and is

Post by esmie moo
valid) and it is not GUARANTEE SPACE.I would appreciate

your thoughts

Post by esmie moo
in knowing the cause of the failure.
PAGE 0001     5695-DF175 

DFSMSDSS V1R13.0 DATA SET SERVICES

Post by esmie moo
-   RESTORE INDDNAME(TAPE01)  -
         

DATASET(INCLUDE(DBU3705.SYSCICS.**))  -

Post by esmie moo
          OUTDDNAME(DASD01) -
          STORCLAS(SYSP0101) -
          REPLACE
  ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN

ASSIGNED TO COMMAND

Post by esmie moo
'RESTORE '
  ADR109I (R/I)-RI01 (01), 2014.256 09:53:27

INITIAL SCAN OF USER

Post by esmie moo
CONTROL STATEMENTS COMPLETED  ADR016I

(001)-PRIME(01), RACF LOGGING

Post by esmie moo
OPTION IN EFFECT FOR THIS TASK 0ADR006I

(001)-STEND(01), 2014.256

Post by esmie moo
09:53:27 EXECUTION BEGINS 0ADR780I (001)-TDDS (01), THE

INPUT DUMP

Post by esmie moo
DATA SET BEING PROCESSED IS IN PHYSICAL DATA SET FORMAT

AND WAS

Post by esmie moo
CREATED BY
DFSMSDSS VERSION
               

           1 RELEASE 13
MODIFICATION LEVEL 0 ON

Post by esmie moo
0ADR709E (001)-VDSS (01), AN ERROR OCCURRED IN THE

STORAGE MANAGEMENT

Post by esmie moo
SUBSYSTEM WHILE ALLOCATING DATA SET
DBU3705.SYSCICS.BTCH. SMS
               

           MESSAGES
FOLLOW.

Post by esmie moo
   IGD01010I STORCLAS SYSP0101 -

STORGRP=SYSP010

Post by esmie moo
   IGD17101I DATA SET

DBU3705.SYSCICS.BTCH

Post by esmie moo
   NOT DEFINED BECAUSE DUPLICATE NAME

EXISTS IN CATALOG

Post by esmie moo
   RETURN CODE IS 8 REASON CODE IS 38

IGG0CLEH 0ADR809I (001)-VDSS

Post by esmie moo
(01), ADDITIONAL DIAGNOSTIC DATA FOR PRECEDING
               

           SC=SYSP0101
MC=NOBACKUP DC=

Post by esmie moo
               

       
   REQPRI=0000000015TRK REQSEC=0000000000TRK

Post by esmie moo
REQVOLS=01
//STEP03   EXEC PGM=ADRDSSU,REGION=5M
//SYSPRINT DD SYSOUT=*
//DASD01   DD

DISP=SHR,UNIT=SYSDA,VOL=SER=CAP001

Post by esmie moo
//TAPE01   DD

DSN=DBU3705.SUPRA.BKUPSYTT.CAP001.,

Post by esmie moo
//            DISP=SHR
//SYSIN    DD

DISP=SHR,DSN=DBU3705.PDS.SYSIN(REST1)
</snip>

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


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

[esmie moo]

Alan,

I tried your suggestion - RECATALOG(*) - but I received the same error message.
--------------------------------------------
On Thu, 9/18/14, Staller, Allan <***@KBMG.COM> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, September 18, 2014, 11:54 AM

You can also use
recatalog(*) to update the catalog with the new copy.
The replace parameter may also be needed.

<snip>

Just as a suggestion, why not
use the RENAMEU(xxxxxx) parm so that the dataset will go
down with a different name.​

Post by esmie moo
Good Day Gentle Readers,
I am trying to trouble shoot the problem

of a failed DFDSS restore. 

Post by esmie moo
So far I

am unable to find the reason.  The dsn (at the time of the

Post by esmie moo
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

Post by esmie moo
was told that the dsn (which

is SMS managed) was NOT in use at the time.

Post by esmie moo
I have a suspicion that the dsn resided on

another volume which was

Post by esmie moo
not in the

same  STORCLAS/STORGRP which may be the cause of the

Post by esmie moo
failure.  A colleague and I reviewed the

SMS ACS routines and all is

Post by esmie moo
in

order.  The bypass of STORAGE CLASS (via jcl is permitted
and is

Post by esmie moo
valid) and it is not GUARANTEE

SPACE.I would appreciate your thoughts
in knowing the cause of the failure.

Post by esmie moo
PAGE 0001     5695-DF175 

DFSMSDSS V1R13.0 DATA SET SERVICES
-   RESTORE INDDNAME(TAPE01)  -

Post by esmie moo
         

DATASET(INCLUDE(DBU3705.SYSCICS.**))  -

Post by esmie moo
          OUTDDNAME(DASD01) -
          STORCLAS(SYSP0101) -
          REPLACE
  ADR101I (R/I)-RI01 (01), TASKID 001 HAS

BEEN ASSIGNED TO COMMAND

Post by esmie moo
'RESTORE

'

Post by esmie moo
  ADR109I (R/I)-RI01 (01),

2014.256 09:53:27 INITIAL SCAN OF USER
CONTROL STATEMENTS COMPLETED  ADR016I (001)-PRIME(01), RACF
LOGGING

Post by esmie moo
OPTION IN EFFECT FOR THIS TASK

0ADR006I (001)-STEND(01), 2014.256
09:53:27 EXECUTION BEGINS 0ADR780I (001)-TDDS (01), THE
INPUT DUMP

Post by esmie moo
DATA SET BEING PROCESSED IS

IN PHYSICAL DATA SET FORMAT AND WAS
CREATED BY
DFSMSDSS VERSION

Post by esmie moo
               

           1 RELEASE 13 MODIFICATION LEVEL 0
ON

Post by esmie moo
0ADR709E (001)-VDSS (01), AN ERROR

OCCURRED IN THE STORAGE MANAGEMENT
SUBSYSTEM WHILE ALLOCATING DATA SET

Post by esmie moo
DBU3705.SYSCICS.BTCH. SMS
                       

   MESSAGES FOLLOW.

Post by esmie moo
   IGD01010I STORCLAS SYSP0101 -

STORGRP=SYSP010

Post by esmie moo
   IGD17101I

DATA SET DBU3705.SYSCICS.BTCH

Post by esmie moo
   NOT DEFINED BECAUSE DUPLICATE

NAME EXISTS IN CATALOG

Post by esmie moo
   RETURN CODE IS 8 REASON CODE

IS 38 IGG0CLEH 0ADR809I (001)-VDSS

Post by esmie moo
                       

   SC=SYSP0101 MC=NOBACKUP DC=

Post by esmie moo
                       

   REQPRI=0000000015TRK REQSEC=0000000000TRK

Post by esmie moo
REQVOLS=01

//STEP03   EXEC PGM=ADRDSSU,REGION=5M

Post by esmie moo
//SYSPRINT DD SYSOUT=*
//DASD01   DD

DISP=SHR,UNIT=SYSDA,VOL=SER=CAP001
//TAPE01   DD
DSN=DBU3705.SUPRA.BKUPSYTT.CAP001.,
//            DISP=SHR

Post by esmie moo
//SYSIN 

  DD DISP=SHR,DSN=DBU3705.PDS.SYSIN(REST1)
</snip>

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


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

[Lizette Koehler]

Did you enter the name you are trying to restore in 3.4?

What were the results?

Do you see an entry?

Does the entry, if there, have SPACE?

Lizette

-----Original Message-----
Behalf Of esmie moo
Sent: Thursday, September 18, 2014 10:41 AM
Subject: Re: DFDSS FAILED RESTORE
Alan,
I tried your suggestion - RECATALOG(*) - but I received the same error message.
--------------------------------------------
Subject: Re: DFDSS FAILED RESTORE
Received: Thursday, September 18, 2014, 11:54 AM
You can also use
recatalog(*) to update the catalog with the new copy.
The replace parameter may also be needed.
<snip>
Just as a suggestion, why not
use the RENAMEU(xxxxxx) parm so that the dataset will go down with a different
name.​

Post by esmie moo
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

Post by esmie moo
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.

Post by esmie moo
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.

Post by esmie moo
PAGE 0001 5695-DF175

DFSMSDSS V1R13.0 DATA SET SERVICES
- RESTORE INDDNAME(TAPE01) -
DATASET(INCLUDE(DBU3705.SYSCICS.**)) -

Post by esmie moo
OUTDDNAME(DASD01) - > STORCLAS(SYSP0101) -
REPLACE > ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN

ASSIGNED TO COMMAND > 'RESTORE '

Post by esmie moo
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

Post by esmie moo
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.

Post by esmie moo
IGD01010I STORCLAS SYSP0101 -

STORGRP=SYSP010

Post by esmie moo
IGD17101I

DATA SET DBU3705.SYSCICS.BTCH

Post by esmie moo
NOT DEFINED BECAUSE DUPLICATE

NAME EXISTS IN CATALOG

Post by esmie moo
RETURN CODE IS 8 REASON CODE

IS 38 IGG0CLEH 0ADR809I (001)-VDSS
SC=SYSP0101 MC=NOBACKUP DC=
REQPRI=0000000015TRK REQSEC=0000000000TRK > REQVOLS=01 >
//STEP03 EXEC PGM=ADRDSSU,REGION=5M

Post by esmie moo
//SYSPRINT DD SYSOUT=*
//DASD01 DD

DISP=SHR,UNIT=SYSDA,VOL=SER=CAP001
//TAPE01 DD
DSN=DBU3705.SUPRA.BKUPSYTT.CAP001.,
// DISP=SHR

Post by esmie moo
//SYSIN

DD DISP=SHR,DSN=DBU3705.PDS.SYSIN(REST1)
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to

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

[Thomas Conley]

Post by esmie moo
Alan,
I tried your suggestion - RECATALOG(*) - but I received the same error message.
--------------------------------------------

Try REPUNC.

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

[retired mainframer]

If REPLACE is specified, CATALOG and RECATALOG are both ignored.

-----Original Message-----
Behalf Of esmie moo
Sent: Thursday, September 18, 2014 10:41 AM
Subject: Re: DFDSS FAILED RESTORE
Alan,
I tried your suggestion - RECATALOG(*) - but I received the same error message.

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

[retired mainframer]

According to the manual, if REPLACE is specified for an SMS managed dataset,
the existing copy is located via the catalog. So the OUTDDNAME operand
should be ignored. The manual also specifies that if the dataset is found,
the SMS attributes are unchanged. So the STORCLAS operand should be
ignored. Does the dataset (not just the catalog entry) really exist? Is it
SMS managed? Is it catalogued? Is the dataset actually on the volume the
catalog indicates?

-----Original Message-----
Behalf Of esmie moo
Sent: Thursday, September 18, 2014 8:34 AM
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

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

[esmie moo]

The dataset exists physically on the volume. I was able to access it via 3.4

I think I hit on something. I did a phyiscal backup and a logical backup of the dsn. The restore of the dsn using the logical backup worked. The dsn was replaced successfully. I tried another test with the logical backup. I specified another volser (other than where the source dsn resides) and the restore worked, the dsn was replaced.

However I found a problem with the restore from the physical dsn backup. When I specified a volser other than that of the source dsn, the restore failed with the same error messages. However, when I specified the source volume volser the dsn was replaced. I think that DFDSS restore using a physical dsn backup will only be replaced if the dsn is being restored to the original source volume. If the dsn is not existing the restore would work if the dsn is restored to another volume other than the source volume.

Please correct me if I am wrong.

--------------------------------------------
On Thu, 9/18/14, retired mainframer <retired-***@Q.COM> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, September 18, 2014, 1:58 PM

According to the manual,
if REPLACE is specified for an SMS managed dataset,
the existing copy is located via the catalog. 
So the OUTDDNAME operand
should be
ignored.  The manual also specifies that if the dataset is
found,
the SMS attributes are unchanged. 
So the STORCLAS operand should be
ignored. 
Does the dataset (not just the catalog entry) really
exist?  Is it
SMS managed?  Is it
catalogued?  Is the dataset actually on the volume the
catalog indicates? 
-----Original Message-----

From: IBM

Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU]
On

Behalf Of esmie moo
Sent: Thursday, September 18, 2014 8:34

AM

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

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


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

[Elardus Engelbrecht]

Post by esmie moo
The dataset exists physically on the volume.

Is that dataset only on ONE volser?

If not, logical backup and restore should work, but physical not always.

AFAIK, logical backup/restore just don't care about volsers depending on how you setup your jobs in the first place.

Groete / Greetings
Elardus Engelbrecht

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

[willie bunter]

Yes, the dsn exists only on one volume.
--------------------------------------------
On Fri, 9/19/14, Elardus Engelbrecht <***@SITA.CO.ZA> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Friday, September 19, 2014, 9:11 AM

The dataset exists physically on the volume. 

Is that dataset only on ONE volser?

If not, logical backup and restore should work, but physical
not always.

AFAIK, logical backup/restore just don't care about volsers
depending on how you setup your jobs in the first place.

Groete / Greetings
Elardus Engelbrecht

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

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

[esmie moo]

Thanks Willie. Yes the dsn is not multi-file.
--------------------------------------------
On Fri, 9/19/14, Elardus Engelbrecht <***@SITA.CO.ZA> wrote:

Subject: Re: DFDSS FAILED RESTORE
To: IBM-***@LISTSERV.UA.EDU
Received: Friday, September 19, 2014, 9:11 AM

The dataset exists physically on the volume. 

Is that dataset only on ONE volser?

If not, logical backup and restore should work, but physical
not always.

AFAIK, logical backup/restore just don't care about volsers
depending on how you setup your jobs in the first place.

Groete / Greetings
Elardus Engelbrecht

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

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