Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 277)

NĆ9 Tokens and Locking
read, a lock has been taken in the meanwhile and the files have potentially been
changed. In this case, the source file data will be updated, giving the user a
correct view of the data as it exists in the databases. The following message will
be displayed:
The user will have to reĆinitiate his command. Since this check is done as soon as
the user shows intent to modify, no changes to the database files will be lost.
Lock and Token Handling in Transfer
When transferring into a library that is not on floppy disks, the lock for the
appropriate level (System, Section, Rack, etc.) will be taken in the destination
library. When multiple tasks are transferred, the lock is taken for the entire rack.
The user will be given the option of transferring any held tokens within the scope
of the transfer. If there is a token password, and the user has not entered it
previously, the user will be prompted for the password before the transfer will
execute. If the user chooses to transfer the tokens, the destination copy will hold
the tokens when the transfer is complete. Note that tokens are not required for
transferring in either direction. However, if the user tries to transfer on top of the
copy that holds the token, he will receive a warning message. The user will be
given the option of continuing the transfer or skipping the rack (for racks). If the
files being written over have a token password, the user must enter the password
before the files protected by the token will be written over. If the copy with the
token is written over, the resulting copy will still hold the token. When a token is
transferred, the token password can be either transferred or nulled for the
destination copy.
Note that transferring racks is not considered overwriting the system token
because each rack's database files are protected by that rack's token, not the
system token. If the system token is held by the destination copy, and racks are
transferred into it, the user will not receive a message asking whether he wants to
overwrite the system token. However, the user will receive a warning message if
the destination holds the rack token(s).
Lock and Token Handling in System or Rack Import
System and rack import disregard locks. The import procedure will fail if the
system or rack being imported already exists in the target library. The import
procedure will create tokens for any systems and racks that are imported.