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

One-time Synchronization
HP AutoSYNC User’s Guide—522580-017
3-20
Keeping NOPURGEUNTIL Attribute
files on the remote destination. See Running the Destination Synchronization
Process as a Local Process below for instructions.
As a local process, the synchronization process can set LICENSE and PROGID
attributes if the proper user ID is used.
Keeping NOPURGEUNTIL Attribute
The NOPURGEUNTIL attribute on a file or a table specifies the earliest date where the
file can be purged.
By default, AutoSYNC does not propagate the NOPURGEUNTIL attribute to the
destination, to insure that future synchronizations of the file or table will be possible.
To retain the NOPURGEUNTIL attribute for a SQL table or alternate index on the
destination, specify the KEEPNOPURGEUNTIL option. Subsequent synchronization
attempts will fail until the NOPURGEUNTIL period has elapsed.
KEEPNOPURGEUNTIL is not supported for Enscribe files, to remain consistent with
the behavior of FUP and RESTORE. FUP and RESTORE do not propagate the
NOPURGEUNTIL attribute for Enscribe files.
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:
ADD * FROM ASYSYNC
SET LIKE ASYSYNC
ALTER CALLABLE^LOCAL^LOGON, CALLABLE ON
SET SAVEABEND ON
BUILD ASYSYNC!
SQLCOMP/IN ASYSYNC/NOREGISTER ON