Setting lock file rules
Set lock file rules to define under what circumstances a system will be locked. The more circumstances you apply to a rule, the less restrictive it is. To set lock file rules:
Click Manage the system > Maintenance > Connector concurrency rules.
Select the target system, on which you want the lock to occur, from the Target system drop-down list.
Select one of the following options from the Operation drop-down list:
ACHG – Any operation where target system administrator credentials are used.
VERI – A password verification operation.
AVER – An alternate login ID verification operation.
VRRE – A transparent password synchronization operation.
The lock file is created when the operation selected from this drop-down list occurs on the selected target system.
Select the appropriate Lock file items to determine the circumstances under which the lock file will be created (multiple selections make the lock file less restrictive):
Local – Sets a lock on the primary server rather than on a proxy.
Target system – Sets a lock for the target system so multiple client servers cannot communicate with the target system simultaneously.
Target system type – Sets a lock for the target system type so multiple client servers cannot communicate with the same target system type simultaneously.
PID – Sets a lock so the same process cannot access multiple target systems simultaneously.
User – Sets a lock so an individual user cannot access multiple target systems simultaneously. For example, if you are logged in as user1 on one target system, you cannot log in as user1 on any other target systems.
Admin – Sets a lock so that only one of the multiple target system administrator IDs for the target system can have access to the target system at a given time.
Operation – Sets a lock when the selected operation occurs on the target system.
Checkbox values also determine the name of the lock file. For example, if you select Target and User , then when user bsmith verifies his password on system1, the resulting lock file is named system1 bsmith.lock. This means that bsmith will not be able to perform the same operation on system1 until the initial operation is complete. However, user jwhite can access system1 simultaneously, and generates a lock file named system1white.lock.
Optional : Use the Replace with field to override the name of the lock file as defined by the checkbox values.
You can use variables where the order of the variables is important, or use additional text. For example, you can define the lock file name as
%ADMIN%%PID%mylock. The %LDIR% (lock file directory) variable and .lock suffix are appended automatically.The variables available are:
Variable
Lock file
%LOCAL%
Local
%HOST%
Target
%PLATFORM%
Platform
%PID%
PID
%USER%
User
%ADMIN%
Admin
%OPER%
Operation
Click Update.