HP Integrity NonStop J-Series - Manual (Page 93)

Synchronization Over TCP/IP
HP AutoSYNC User’s Guide—522580-017
7-5
Connection Setup over TCP/IP
to the source and destination file sets. If the destination is on a remote system, the
destination file set must include the Expand node name of the remote system.
Connection Setup over TCP/IP
As in synchronizations over an Expand link, the source ASYSYNCP receives its file
sets from the monitor or Autosync CI. However, if the file set specifies a TCP/IP
address, ASYSYNCP follows a different protocol to set up the communication with the
destination synchronization process.
Connection Setup
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
destination 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.
Note on ASYSYNCP Execute Access
The destination sync process ASYSYNCP must perform some SQL operations to
provide recovery for the synchronization of SQL tables. On the first SQL operation, the
SQL Executor accesses the SQL object in the ASYSYNCP object file. The SQL
Executor uses "EXECUTE security" to access this SQL data.
As mentioned above, the ASYSYNCP on the destination runs under the access ID of
the Syncuser that requests the synchronization. If the owner of ASYSYNCP is
SUPER.SUPER and ASYSYNCP execute access is set to "U", only SUPER.SUPER
can access the SQL object in ASYSYNCP. A synchronization under any other
ADD SYNCF[ILESET[ src-fileset TO \systname.dest-fileset,
HOST { name | IP address } [, sync-options];