AutoSYNC Software User's Guide (Update 19)

Synchronization Over TCP/IP
HP AutoSYNC User’s Guide—522580-020
7-6
Logging
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
Syncuser fails with a SQL error -8025 (The SQL region was not SQL compiled),
because the SQL Executor cannot access the SQL object in ASYSYNCP.
Consequently, ASYSYNCP EXECUTE security must be set to "N" if any non
SUPER.SUPER Syncusers are configured to perform synchronizations.
Logging
When synchronizing over an Expand link, the destination ASYSYNC opens the log file
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, either assigned from a
pool of unused sockets or configured explicitly, as described above in paragraph The
ASYNCLOG-ZASY port on page 7-3.
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 system as back slash asterisk (\*) is not supported for
synchronization over TCP/IP. The destination system name must be a valid EXPAND node
name.