On 10/18/2011 11:41 AM, Mike B wrote:
Hi,
We wish to clean up unwanted abars tape datasets using expirebv and
retainversions(n)
Listing a test abars group, we know that the oldest version of an agg-
group had two datasets and two volsers involved. Running EXPIREBV
ABARSVERSIONS AGNAME(ABENDAID) RETAINVERSIONS(0021) DISPLAY showed
that it woud UNcatalog the two datasets.
I then ran the expirebv with execute, and this morning after rmm
housekeeping the two volsers show in RMM as SCRATCH, but when I go
into the RMM panels, it shows the 2 datasets are still on the volsers.
1) Must I run the expirebv a second time before these 2 uncataloged
datasets go away? (I've seen references in google for running
expirebv a 2nd time...1st just marks it uncataloged...2nd run whacks
em)
Mike,
This is not a problem, RMM is WAD. After a volume is scratched, RMM
retains the dataset name. When the scratch volume is mounted, RMM
checks the dataset name against the tape label. If the datasets don't
match, then RMM disallows the mount, since the tape was created outside
RMM control. This is a fail-safe to ensure that anyone creating a tape
while RMM is RESET or bypassing RMM with EXPDT=98000 does not have their
data destroyed.
Regards,
Tom Conley
----------------------------------------------------------------------
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
