You would need create a Windows scheduled task on the synchronization
host to restart the synchronization.bat process.

Explanation:
The synchronization.bat file needs to be run on the synchronization
host, while the process that automatically schedules a synchronization
request runs on the Jazz team server (commonly the synchronization host
is not the same machine as the Jazz team server host).

Just for interests sake, what are the drawbacks of keeping the
synchronization.bat running all the time? That's what we do for
self-hosting.

Cheers,
Geoff

gdang wrote:

RTC1.0 - ClearCase Synchronization process does not automatically kick
off synchtonization.bat. There are some drawbacks if we keep the
synchtonization.bat running all the time. Is there any way to kick
off this batch file automatically when a synchronization is scheduled
or manually started? Do we have to create a separate Windows
Schuduled Task to run synchtonization.bat periodically? Thanks.

Killing the synchronization.bat file will kill the current
synchronization, if there is one.

When a synchronization is killed in this fashion, the synchronization
stream is left locked. To unlock it, go to the ClearCase Provider
Properties page, and click the "Unlock" button (but only do this if you
are sure that the synchronization.bat process is no longer running).
Note: This info appears in the "Unlocking a synchronized stream" topic
in the dynamic help of the RTC client.

I'll ask around for the best way to get the synchronization.bat process
to run unattended (whatever technique is used to get server processes to
automatically restart when the machine is restarted should be applicable
here).

Cheers,
Geoff

gdang wrote:

Thanks, Geoff.

For our hosted server, we do not have physical access and we need to
sue Microsoft Remote Desktop Connection (RDP). One user can logon
through RDP and kick off the batch file. However when he/she logs
off, the session is closed. In addition, having a running command
window running is always a risk of being closed by other team
members.

Follow-up questions - 1) what would happen is the synchronization.bat
file is closed in the middle of synchronization? 2) I saw one
synchronization 'over due' and any further scheduled synchronization
failed due to "process in use". What could eb the cause?
Thanks.