An OpenTP1 server UAP can report its activation to the TP1/Client application program (CUP) by using the function dc_rpc_cltsend() [CBLDCRPC ('CLTSEND')], which sends data to the CUP. This function can be used to report the activation of the server to the client simultaneously.

Data sent by the function dc_rpc_cltsend() is received with the function dc_clt_chained_accept_notification() or dc_clt_accept_notification() in the CUP. When the CUP receives data, the TP1/Client knows the server is in operation. Then, the CUP requests a service to the server.

The function dc_rpc_cltsend() can be used only when the function dc_clt_chained_accept_notification() or dc_clt_accept_notification() in the CUP on the receiving end is waiting for a notification. If the CUP is not active, the function dc_rpc_cltsend() returns with an error. The function dc_rpc_cltsend() cannot send data to any processes (processes of the server UAP) other than the functions dc_clt_chained_accept_notification() and dc_clt_accept_notification() in the CUP. For details about the functions dc_clt_chained_accept_notification() and dc_clt_accept_notification(), see the manual OpenTP1 TP1/Client User's Guide TP1/Client/W, TP1/Client/P.

The figure below shows the outline of reporting data to CUP unidirectionally.

Figure 2-9 Outline of reporting data to CUP unidirectionally