SCM 220.127.116.11 has problems using hsync in UDP.
It encounters a problem if the -rport switch is missing, or if the wrong port number is provided in the UDP process. It ends up in an infinite loop on client and a hsync server process needs to be killed manually.
What's happening can be seen clearly if you enter the hsync command from a command prompt window.
If the "-rport" parameter has been omitted from the command line, hsync will interactively prompt for the port number.
If you're doing this from the command line, then it's no problem because you're there in that interface to provide that information.
If you're doing this from a UDP or from a batch file, this will hang the process while it waits for input from the console that will never come.
First of all, check if the command is right:
CA SCM Admin Guide on Page 200 documents how the command should look like and how you can change this port.
With CA SCM R12.1 SP3 and with CA SCM R12.5 release this problem is fixed.
There are 2 solutions to the problem:
- Make corrections to the UDP or batch script that calls hsync to include the "-rport" parameter
- Add the "-rport=" parameter to the HClient.arg file on the machine where hsync is running.
This option is explained in the SCM 12.1 Release Notes on p. 24.