You might want to check the EXPIREBV command for NONSMSVERSIONS

Start with the EXPIREBV DISPLAY NONSMSVERSIONS(uncatalogeddata(10))
ods(yourtsoid.aaaa) to determine if the desired records are being
targeted. Then proceed with the EXPIREBV EXECUTE
NONSMSVERSIONS(uncatalogeddata(10))

The above should target BCDS records which are no longer cataloged and
are more than 10 days old.

-----Original Message-----
From: Bob Henry [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 18, 2006 10:57 AM
To: [email protected]
Subject: Problems with HSM & GDGs

I have a non-SMS HSM environment with several GDGs defined. New
generations are produced daily and they are backed up by autobackup each
day. They are defined with 5 generations and SCRATCH. When they roll
off, the GDG is scratched and it appears the HSM version record (C) is
removed but the backup record (B) still refers to the deleted C record.
When I run an AUDIT DSCTL(BACKUP), I receive an ERR 39 for the backup
record. I'm not running PATCH .MCVT.+53 BITS(11......) because it
appears to deal with migrated, rolled-off GDGs. Would it do the same
thing for backed up GDGs?  

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

Reply via email to