Owner's manual

Scheduled Synchronization

HP AutoSYNC User’s Guide—522580-015

4-7

Bypassing Disabled Log Down

The user must have appropriate remote passwords to any remote destination.

AutoSYNC can only synchronize files that are secured for read access by the user ID.

It can only replace files that are secured for purge access by the user ID. If the

destination is remote, replaced files must be secured for remote purge access.

The ownership of synchronized symbolic links is a special case. By default, the owner

of a synchronized symbolic link is the syncuser and not the owner of the source

symbolic link or the OWNER specified in the ADD SYNCFILESET or ALTER

SYNCFILESET command option.

To change this behavior, see Changing Default Ownership of Symbolic Links on

page 5-6.

Bypassing Disabled Log Down

Some systems have restricted the ability of the Super user or group manager to logon

as another user without entering that user’s password. This restriction is configured

with the SafeGuard PASSWORD-REQUIRED setting but is often referred to as the

disabled log down, and effectively limits AutoSYNC to a single user who is the

authorizer.

In this situation, you have two options:

•

Configure a separate AutoSYNC environment, including a separate monitor

process, for each user who wishes to configure scheduled synchronizations, or

•

Bypass the disabled log down restriction by using a privileged ASYSYNCP process

on the source system. This requires the Super user ID on the source system.

Perform the following operations, on the source system, to make ASYSYNCP a

privileged program that can log down.

1. In BIND, issue the following commands:

2. At the TACL prompt, SQL compile ASYSYNCP:

3. Then, as SUPER.SUPER, issue the following command:

4. At the TACL prompt, accelerate ASYSYNCP

ADD * FROM ASYSYNCP

ALTER CALLABLE^LOG^DOWN, CALLABLE ON

BUILD ASYSYNCP!

SQLCOMP/IN ASYSYNCP/NOREGISTER ON

FUP LICENSE ASYSYNCP

AXCEL ASYSYNCP, ASYSYNCP

OCA ASYSYNCP