Maybe you can go at it from the test side via DDM. Something like this..
o DSPOBJD of files in target library.
o Read temp file for PFs.
o Create/change DDM file pointing at remote system's PF counterpart.
o CPYF from DDM file to our target file.
o Get next PF.
This way you don't interrupt production at all.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Saturday, March 03, 2012 8:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Save While Active
Thanks, Rob. That would be the easiest way to go (HA replication to DR
and then update test from the DR box). The problem is that DR box is offsite and we don't want to use that pipe to update the local testing partition. I'm trying to figure out how to keep the traffic from updating the test partition local. It looks like *SYSDFN will be our best bet.
When we were using savact on production I wanted the *lib because of the
possibilities you pointed out below. Management deemed this unacceptable
because you still have to kick the users out until the sync point is
achieved. Just letting you know that in case you decide to try *lib,
which, based on your test requirements, and your understanding of the
ramifications, I don't think you need.
Now we use Mimix and back up off of the dr machine.