Since we started using it, we've had issues with our SRDF process.
There are
always several dozen volumes in HELD status when SRDF comes along to
replicate
to our DR site. It turns out SNAP copies of datasets require a manual
RELEASE
command be issued for each of the target volumes. A SNAP copy of an
entire volume
automatically releases the target volume once the SNAP completes. I
don't know
why there is a difference, but there is.
Has anyone else used this feature ??? Do you experience the same
issues ???
Have you come up with a way around it ???
I didn't realize it affected SRDF, but the same issue affects BCV
(SPLIT, RE-ESTABLISH, etc.). After a SNAP operation from an online disk
with a BCV, you can't SPLIT or RE-RESTABLISH with issuing the RELEASE.
We had to build this into FDRINSTANT.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
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
