Can't tell for sure whether it matches your case but I still have
a 'to do' item on my desk which seems remotely related.
I was making some tests backing up (using PGM=ADRDSSU) a number of
GDGs (all belonging to GDSes defined with limit 1) to a single
backup dataset. Not wanting to overlay the only GDG entries in
case of a restore, I tried to do the restore with RENAMEU changing
the last (GooooVoo) qualifier to hardcoded value 'RESTORE'. It
didn't work as intended but as a result I had two GDG entries in
the catalog for each GDS affected. That is, they were restored but
not renamed. I have removed these bogus entries since so I can't
check whether they were marked 'rolled off' or not.
In case someone can immediately tell me where I went wrong
parameterizing ADRDSSU for the restore here are the statements I
had used:
//STEP010 EXEC PGM=ADRDSSU,COND=(0,NE) PARM='TYPRUN=NORUN'
//BACKUP DD DSN=my.backup.dataset,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
RESTORE DATASET ( -
INCLUDE ( -
gds.dataset.name1.* -
gds.dataset.name2.* -
) -
) -
INDDNAME ( BACKUP ) -
RENAMEU ( (*,**.RESTORE) ) -
WAIT ( 15 , 60 )
Kind regards
Robert Bardos
Ansys AG, Zurich, Switzerland
>
> -----Original Message-----
> On behalf Of Mark Steely
> Sent: Thursday, January 11, 2007 2:31 PM
>
> > What does it mean when when a GDG status is ROLLED-OFF.
> <SNIP>
>
> It means that the generation data set (GDS) is no
> longer part of the
> GDG. That means that if you coded the following:
>
> //SYSUT1 DD DSN=POP.FLGD.FLD100.BYFLT,DISP=SHR
>
> you should get all the generations still in the GDG
> base, but none of
> the ones listed as "Rolled Off".
>
> Now, how is it that you have GDSes that are not in the GDG base?
>
> Steve Thompson
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
