IBM Mainframe Forum

Hi Robert,

Thanks. I'm still unable to restore the AIX1, 2, 3, I got the error messaqge below.

SDSF OUTPUT DISPLAY GDUBAGAR JOB28690 DSID 103 LINE 9 COLUMNS 01- 80
COMMAND INPUT ===> SCROLL ===> CSR
0ADR006I (001)-STEND(01), 2010.029 11:49:07 EXECUTION BEGINS
0ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN LOGICAL
1 RELEASE 9 MODIFICATION LEVEL 0
0ADR380E (001)-FDSRL(04), DATA SET PADTPR.KSCI1DU.PF00610 NOT PROCESSED, 08
0ADR711I (001)-NEWDS(01), DATA SET PADTPR.KSCI1DU.PF00610.AIX1 HAS BEEN ALLOCAT
STORCLAS SCTEST, NO DATACLAS, AND NO MGMTCLAS.
0ADR788I (001)-TDUNL(01), PROCESSING COMPLETED FOR CLUSTER PADTPR.KSCI1DU.PF006
0ADR489I (001)-TDLOG(02), CLUSTER GDUBAGA.PADTPR.KSCI1DU.PF0061Y WAS RESTORED
CATALOG UCAT.TSOZ.ICFCAT
COMPONENT GDUBAGA.PADTPR.KSCI1DU.PF0061Y.DATA
COMPONENT GDUBAGA.PADTPR.KSCI1DU.PF0061Y.INDEX
0ADR761W (001)-TDLOG(01), CLUSTER GDUBAGA.PADTPR.KSCI1DU.PF0061Y IN CATALOG UCA
0ADR380E (001)-FRLBO(01), DATA SET PADTPR.KSCI1DU.PF00610.AIX2 NOT PROCESSED, 3
0ADR380E (001)-FRLBO(01), DATA SET PADTPR.KSCI1DU.PF00610.AIX3 NOT PROCESSED, 3
0ADR480W (001)-TDLOG(01), THE FOLLOWING DATA SETS WERE NOT PROCESSED FROM THE L
0 PADTPR.KSCI1DU.PF00610.AIX2
0 PADTPR.KSCI1DU.PF00610.AIX3
0ADR454I (001)-TDLOG(01), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
0 PADTPR.KSCI1DU.PF00610.AIX1

Below is my JCl

//* VOL=SER=(HTSTZB)
//TAPEIN DD DISP=SHR,DSN=GDUBAGA.PADTPR.KSCI1DU.PF00610.TAPX
//SYSIN DD *
RESTORE INDDNAME(TAPEIN) -
DATASET(INCLUDE(PADTPR.KSCI1DU.PF00610.**)) -
RENUNC(PADTPR.KSCI1DU.PF00610.** -
GDUBAGA.PADTPR.KSCI1DU.PF0061Y.**)

Btw PADTPR.KSCI1DU.PF00610 is currently existing. Will it be ok to have it in include statement?

thanks

I think at this point you need to contact your site support group for assistance, particularly since the partial messages you posted specifically indicate that the AIX1 file was successfully restored. There were problems with AIX2 and AIX3 but AIX1 is supposed to be out there.

thanks Robert,
the alternate indexes are not there

GDUBAGA.PADTPR.KSCI1DU.PF0061Y *VSAM*
GDUBAGA.PADTPR.KSCI1DU.PF0061Y.DATA TSTU0D
GDUBAGA.PADTPR.KSCI1DU.PF0061Y.INDEX TSTU0D

but the filename i was using are already existing in out mainframe

PADTPR.KSCI1DU.PF00610 *VSAM*
PADTPR.KSCI1DU.PF00610.AIX1 *AIX *
PADTPR.KSCI1DU.PF00610.AIX1.DATA TSTU25
PADTPR.KSCI1DU.PF00610.AIX1.INDEX TSTU25
PADTPR.KSCI1DU.PF00610.AIX2 *AIX *
PADTPR.KSCI1DU.PF00610.AIX2.DATA TSTU24
PADTPR.KSCI1DU.PF00610.AIX2.INDEX TSTU24
PADTPR.KSCI1DU.PF00610.AIX3 *AIX *
PADTPR.KSCI1DU.PF00610.AIX3.DATA TSTU05
PADTPR.KSCI1DU.PF00610.AIX3.INDEX TSTU05
PADTPR.KSCI1DU.PF00610.DATA TSTU0A
PADTPR.KSCI1DU.PF00610.INDEX TSTU0A

could this be the cause?

Yeah, you need to include the REPLACE option on the RESTORE command.

Robert Sample wrote:Yeah, you need to include the REPLACE option on the RESTORE command.

thanks Robert , really really appreciate the help

Glad to hear I'm helping!

This problem has been resolved just wanted to thank you again for the help =D