HP NonStop G-Series - Manual (Page 87)

Synchronization Over TCP/IP
HP AutoSYNC User’s Guide—522580-015
7-5
Synchronization over TCP/IP
In this case, the source ASYSYNCP does not directly start the destination
synchronization process ASYSYNC. Instead, ASYSYNCP connects to the monitor
process on the destination system using a user-configured port. The destination
monitor is the LISTNER. The monitor then starts an ASYSYNCP process.
The destination ASYSYNCP must perform a log down from the access ID of the
remote AutoSYNC authorizer, to the access ID of the user that requests the
synchronization. Due to the requirement to perform a log down on the destination
system, both the source and destination synchronization processes are ASYSYNCP
objects.
The destination ASYSYNCP receives a LISTNER startup message containing the port
and IP address of the source ASYSYNCP process.
The destination ASYSYNCP accepts a connection from source ASYSYNCP and
receives messages over the socket.
Both source and destination ASYSYNCP send and receive messages through the
same TCP socket. They can be receiving and sending concurrently but only one
operation of each type is active.
When synchronizing over an Expand link, the destination ASYSYNC opens the logfile
SLggguuu through Expand and writes records directly to the log. However when
synchronizing over TCPIP, the source ASYSYNCP sets up and accepts a connection
from the destination ASYSYNCP over a special logging socket. Any message received
over that socket is written to the log file by the source ASYSYNCP.
The remaining steps in synchronization processing follow the same protocol whether
the synchronization is over TCP/IP or over Expand.
Note. Specifying a destination node name as back slash asterisk (\*) is not supported for
synchronization over TCP/IP. The destination node name must be a valid EXPAND node
name.