I was facing the same problem a while ago, but I did it like this:
I measured the amount of time a resync usually takes and I simply perform the steps you mentioned based on the clock, not on monitoring the process itself.

I guess that if you do some smart scripting (using *nix "grep" commands) and watch the values go down to 1%, you could do it in a safe way. I must admit I never had the time to develop this script on Windows...

I need it on Windows actually

The problem with measuring time, that it's not accurate.
You need to assume that daily changes are the same.

I know and you are completely right !
We monitored the time needed to get in sync for about 2 weeks and we took the worst day and used that as a baseline. Furthermore I logged the process needed to get in sync and stopped SRDF as soon as everything was in sync.

The problem here is, as you already suggested, that as soon as I switch to SRDF A, this could take 10 or 15 minutes instead of only 1 minutes if I switch to SRDF A too fast. I´d monitor and tune the script everyday and after a month or so it was fine.... workable.

I´m sorry I can´t give you the commands as I´m no longer working at that particular DMX site and I don´t remember exactly what the syntax of the scripts were....

That's okay. I have a template for writting scripts. I just need some easy solution.
I hope EMC would make our lives easier with something like that built-in. <*cough>HINT<*cough>

I'm not sure, but I think there's a Symmetrix Procedure Generator available for customers. AFAIK it produces scripts, but I'd have to try to be sure.

In the upper left corner in Powerlink type "generator" and look for the Symmetrix Procedure Generator. I can see a couple of versions there, so be sure to pick the right one (or all of them). The most recent one is v2.01 from June 5 2009.

Message was edited by:
RRR
You can also visit Home > Support > Product and Diagnostic Tools > Symmetrix Tools > Symmetrix Procedure Generator directly.

I've downloaded the recent version.
Can't find anything useful there.
Can you post an example script?

@Echo off
SET logfile=E:\logs\srdf.log
echo %date% %time% >> %logfile%
echo. >> %logfile%
symrdf -g set mode acp_disk -noprompt
symrdf -g query >> %logfile%
echo symrdf -g resume -noprompt >> %logfile%
symrdf -g resume -noprompt
echo %date% %time% >> %logfile%
echo. >> %logfile%
echo symrdf -g set mode async -noprompt >> %logfile%
symrdf -g set mode async -noprompt
:BEGIN
symrdf -g verify -consistent
IF "%ERRORLEVEL%"=="0" GOTO SUSPEND
echo %date% %time% The symdevs are not in a consistent state yet >> %logfile%
goto BEGIN
:SUSPEND
echo %date% %time% De devices hebben nu een consistente status >> %logfile%
echo symrdf -g suspend -noprompt >> %logfile%
symrdf -g suspend -noprompt
echo %date% %time% >> %logfile%
echo. >> %logfile%
echo ------------------------- >> %logfile%
echo. >> %logfile%
SET logfile=

You need to fill in the of course and perform some testruns.
I combined 4 scripts here and each of the 4 were scheduled after one another with the first two right in the beginning and the last 2 some time later, depending on how much deltas need to be replicated.

I use SRDF/S but its ok.

But there is no wait time between the 'resume' in ACP state to the async state.

I know. I couldn't figure that out, that's what I said in my 1st post. That's why I timed how long it took for several days/weeks and scheduled the 4 scripts accordingly.