yes, I mean 'copystgpool=[yadda]'.
well, I experienced this myself within a PMR.
the problem is the "data movement".
it's not the same, and therefore the pool is removed from the list of copypools.
sadly have no more detailed information on this, maybe ask IBM...
I'm using nonblocked pools myself as a Content Manager target.
Regards, Alex
Von: "Allen S. Rout" <asr < at > UFL.EDU>
An: ADSM-L < at > VM.MARIST.EDU
Datum: 04.01.2012 20:45
Betreff: Re: [ADSM-L] Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?
Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>
On 01/04/2012 09:17 AM, Alexander Heindl wrote:
use a nonblocked pool
(you cannot change this setting - you'll need to move all data)
consider some disadvantages of nonblocked data, e.g. no autocopy with
"blocked" pools...
Could you hit that with a little more detail? When you say 'autocopy',
I think 'copystgpool=[yadda]'. But nonblock is specifically allowed for
copystgpool sources. I don't use copystgpool, but it's of interest
nonetheless.
- Allen S. Rout
