dpConnect to the disconnected system
Note: This is no replacement for the Official ETM Support!
I currently faced to the following unpredictable behavior of dpConnect that tries to connect to the DPE that locates in the disconnected distributed system.
If this system is disconnect the following message appears in the log when trying to make a dpConnect:
WCCOActrl (13), 2019.01.10 12:53:06.149, SYS, SEVERE, 38, Message could not be sent, DP: SYSTEM3:_2x2Redu.state.active:_online.._value, MAN: (SYS: 12 Dist -num 1 CONN: 1(R)), Could not send message DP_MSG_CONNECT #43
But when the system finally connects the CB function calls.
Note1: The amount of function calls equals to the amount of dpConnect attempts (e.g. when using loops with delays till successful dpConnect)
Note2: dpDisconnect after unsuccessful dpConnect does not help:
WCCOActrl (13), 2019.01.10 12:53:06.150, CTRL, WARNING, 71, DP does not exist, TestScript.ctl Line: 157, dpDisconnect, TRUE
viewtopic.php?f=16&t=10338&p=964777&hil ... ct#p964770
Do a dpConnect() in a loop is not necessary if the DP identification is already known.
Possibly you can do check using dpExists() before calling dpConnect() to detect if the identification is loaded for the DP you want to connect.
Senior Support Specialist