Applies To:
  • CitectSCADA 5.xx, 6.00, 6.00 Service Pack A
Summary:
Both ClusterSetName and ClusterGetName functions always return 0 even if the server(s) do not exist.
 

Solution:
ClusterSetName() is Asynchronous. Whether the servers specified exist or not the system does not know.

How clusters work:

What it does is change the name for primary and standby for the Alarm Report Trend servers. ie [Client]Primary, [Client]Standby from the ini. It does this and closes the old connections to the original servers and attempts to reopen them but now the names have been changed to the new ones specified in the Cicode call. ClusterSetName() will only return an error if an error occurs in the name change not whether it can actually connect to those servers. It cannot tell the difference whether those servers exist or are just unavailable at that time.

The connection just go into connecting mode and continuously calls the new primary/standby servers like when you start citect as a client the servers are not running.

ClusterGetName will just return the primary or standby names set in the ini or alternatively those set by ClusterSetName. It does not check to see if that server is up or down and is not suppose to.

It is possible to use ServerInfo() instead to determine whether a valid connection is available.
 
Keywords:
 

Attachments