|
View previous topic :: View next topic
|
| Author |
Message |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Do the datasets show up under 3.4 ?
Just wondering if in the past attempts that you restored them as either DEFERRED or ROLLED OFF
If they show up under 3.4 then delete them |
|
| Back to top |
|
 |
yuvrajdutta
New User
Joined: 13 Jul 2009
Posts: 40
Location: India
|
|
|
|
Hello Expat,
no the individual generations do not come up in 3.4
| Code: |
DSLIST - Data Sets Matching I051029.JAGA.TEST.GDGBASE* Row 1 of 1
Command ===> Scroll ===> CSR
Command - Enter "/" to select action Message Volume
-------------------------------------------------------------------------------
I051029.JAGA.TEST.GDGBASE ??????
***************************** End of Data Set list ****************************
|
Also i'll mention one more thing here w.r.t. to the SYSIN params as prescribed by Robert(excluding opt) i added a renameunc which annoyingly gives me a RC=0 but the catch here is i cannot see "DATA SET <dataset> HAS BEEN CATALOGED" which i could see when i restored a couple of dumped datasets.
| Code: |
DATA SET I051029.ARUNODAY.SORTIN HAS BEEN CATALOGED IN CATALOG CATALOG.USER.VWRK98J
|
| Code: |
DATA SET I051029.JAGA.TEST.GDGBASE.G0001V00 PREALLOCATED, ON VOLUME(S): WRK26H
DATA SET I051029.JAGA.TEST.GDGBASE.G0001V00 CONSISTS OF 00000100 TARGET TRACKS A
DATA SET I051029.JAGA.TEST.GDGBASE.G0001V00 WAS RESTORED
DATA SET I051029.JAGA.TEST.GDGBASE.G0002V00 PREALLOCATED, ON VOLUME(S): WRK86H
DATA SET I051029.JAGA.TEST.GDGBASE.G0002V00 CONSISTS OF 00000100 TARGET TRACKS A
DATA SET I051029.JAGA.TEST.GDGBASE.G0002V00 WAS RESTORED
|
Thanks.. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi,
is it possible to see the JESYSMSG output ?
Gerry |
|
| Back to top |
|
|
yuvrajdutta
New User
Joined: 13 Jul 2009
Posts: 40
Location: India
|
|
|
|
Hello Gcicchet
| Code: |
ICH70001I I051029 LAST ACCESS AT 14:46:39 ON TUESDAY, OCTOBER 6, 2009
IEF236I ALLOC. FOR ADRDSSU STEP010
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSABEND
IEF237I JES2 ALLOCATED TO SYSDUMP
IEF237I JES2 ALLOCATED TO SYSOUT
IGD103I SMS ALLOCATED TO DDNAME DD0
IEF237I JES2 ALLOCATED TO SYSIN
IEF237I 8212 ALLOCATED TO SYS00001
IEF237I 8214 ALLOCATED TO SYS00002
IEF237I 8009 ALLOCATED TO SYS00003
IEF237I 8217 ALLOCATED TO SYS00004
IEF285I SYS09279.T150353.RA000.ADRDSSU.R0152979 KEPT
IEF285I VOL SER NOS= WRK26H.
IEF285I SYS09279.T150353.RA000.ADRDSSU.R0152980 KEPT
IEF285I VOL SER NOS= WRK86H.
IEF285I SYS09279.T150354.RA000.ADRDSSU.R0152981 KEPT
IEF285I VOL SER NOS= WRK14H.
IEF285I SYS09279.T150354.RA000.ADRDSSU.R0152982 KEPT
IEF285I VOL SER NOS= WRKH6H.
IEF142I ADRDSSU STEP010 - STEP WAS EXECUTED - COND CODE 0000
IEF285I I051029.ADRDSSU.J0096565.D0000102.? SYSOUT
IEF285I I051029.ADRDSSU.J0096565.D0000103.? SYSOUT
IEF285I I051029.ADRDSSU.J0096565.D0000104.? SYSOUT
IEF285I I051029.ADRDSSU.J0096565.D0000105.? SYSOUT
IGD104I UFMS.US.SYSTST.SPCOPCDB.REPORT.DUMP RETAINED, DDNAME=DD0
IEF285I I051029.ADRDSSU.J0096565.D0000101.? SYSIN
IEF373I STEP/STEP010 /START 2009279.1503
IEF374I STEP/STEP010 /STOP 2009279.1503 CPU 0MIN 00.07SEC SRB 0MIN 00.01SEC VIRT 1956K SYS 352K EXT 892K SYS 9236K
IEF375I JOB/ADRDSSU /START 2009279.1503
IEF376I JOB/ADRDSSU /STOP 2009279.1503 CPU 0MIN 00.07SEC SRB 0MIN 00.01SEC
|
here you go.. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Mmmmmmmm, I don't know about your storage setup but seem to notice that the datasets are channeled to WRK* volumes. Only by past experience when ever I have encountered WRK* volumes they have been exclusively for && and other datasets with a lifespan of the current job.
It may be worth talking to your storage management team to see if for any strange quirk that these datasets are somehow being routed through the SCA routines and defined as temporary. |
|
| Back to top |
|
|
yuvrajdutta
New User
Joined: 13 Jul 2009
Posts: 40
Location: India
|
|
|
|
Hello Guys... phewwwww.... at last i managed to recreate the GDGs on the remote system.
i used the following inputs to the program
| Code: |
//SYSIN DD *
RESTORE -
CATALOG -
DATASET( -
INCLUDE(**) -
) -
INDDNAME(DD0) -
RENAMEUNC( -
(I051029.JAGA.TEST.GDGBASE.*, -
I051029.JAGA.TEST2.GDGBASE.*) -
) -
REPLACEUNC -
TGTGDS(ACTIVE)
/*
|
Seems like without a rename the GDG's wont get created.
Also i noticed something very peculiar.
Initially i had restored the GDG's w.r.t. the base I051029.JAGA.TEST1.GDGBASE it ran fine.
Then i deleted the base and tried to restore, it failed as the base was missing.
| Code: |
//IDCAMS01 EXEC PGM=IDCAMS,REGION=768K
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE 'I051029.JAGA.TEST1.GDGBASE'
|
But then i recreated the base again and tried to restore but nothing got restored though the RC returned was 0.
| Code: |
//DOITNOWW EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GENERATIONDATAGROUP -
(NAME(I051029.JAGA.TEST1.GDGBASE) -
NOEMPTY -
NOSCRATCH -
LIMIT(30))
/*
|
Can you'll please shed some light as to what may have happened w.r.t. the above scenario and moreover why should i always rename while restoring w.r.t. the scenario at the beginning??
Thanks a lot for your patience guys  |
|
| Back to top |
|
|
|
|
