Files on the remote destination. see, Running the destination synchronization, Process as a local process – HP NonStop G-Series User Manual

Page 59

Advertising
background image

One-time Synchronization

HP AutoSYNC User’s Guide522580-020

3-21

Running the Destination Synchronization Process as

a Local Process

Running the Destination Synchronization Process as a Local Process

below for

instructions.

Running the Destination Synchronization Process as a Local
Process

To enable ASYSYNC or ASYSYNCP to become a local process on a remote system,
perform the following operations on the ASYSYNC or ASYSYNCP program on the
destination system:

1. In BIND, issue the following commands:

2. At the TACL prompt, SQL compile ASYSYNC:

3. At the TACL prompt, accelerate ASYSYNC:

4. Then, as SUPER.SUPER, license ASYSYNC:

IF synchronizing over TCP/IP, perform the same steps for ASYSYNCP.

ADD * FROM ASYSYNC
SET LIKE ASYSYNC
ALTER CALLABLE^LOCAL^LOGON, CALLABLE ON
SET SAVEABEND ON
BUILD ASYSYNC!

SQLCOMP/IN ASYSYNC/NOREGISTER ON

AXCEL ASYSYNC, ASYSYNC
or
OCA ASYSYNC

FUP LICENSE ASYSYNC

Note. Once you have altered ASYSYNC or ASYSYNCP with the above Binder commands,
ASYSYNC or ASYSYNCP must be licensed; otherwise, all synchronizations that use that
program will fail.

WARNING. By configuring a callable ASYSYNC or ASYSYNCP, the systems administrator
allows a syncuser to perform operations on the remote system that would have previously
required the knowledge of the local password.

Advertising
This manual is related to the following products: