HP NonStop G-Series - Manual (Page 58)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-016
3-20
Preserving Other Security Attributes
Preserving Other Security Attributes
You can also replace destination files even if you have elected to keep local purge
access to the files. To keep the PURGE security of a file on the destination system as
“O” or “G” for example, you will need to make the ASYSYNC or ASYSYNCP (if
synchronizing over TCP/IP) privileged, allowing it to run as a local process. See
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.