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

NĆ7 Tokens and Locking
All Tokens in Library
If this option is selected, all the commands except CREATE and EXIT will be
disabled. System, section and rack information will not be displayed and the
token status information will not be displayed.
Step 9.
Select one of the following commands:
CREATE Ć Creates held" token(s).
MAKE HELD Ć Makes existing token(s) held" regardless of current state.
MAKE NOT HELD Ć Makes existing token(s) not held" regardless of current state
and clears the token password.
CLEAR PASSWORD Ć Clears the token password on selected token(s).
EXIT Ć Exits the Token Manager utility.
Hierarchical Locking
When a user makes modifications within a system, the AutoMax system will lock
the appropriate files to ensure that the user has exclusive access to them. Once
these files are locked, any other user who attempts to modify them will see a
message on his screen indicating that the files are locked by another user. When
the modifications to the files are complete and the databases have been updated,
the lock will be released. The files will then be accessible for modification by
another user.
Note that only the files that are accessed through the Programming Executive will
be locked. Files that are called up from within the text editor will not be locked,
and will not respect locks that may have been taken on them.
A lock can be taken not only for files, but for whole racks, sections, or an entire
system. Higher level locks protect all the files under them. For example, holding a
section lock prevents other users from modifying any of the files that pertain to
that section (racks or tasks). Lower level locks also provide file protection. For
example, if a rack is locked, the section or system to which it belongs cannot be
deleted.
Setting the User Name
When a lock is taken, the AutoMax system stores the username (entered in the
AutoMax Setup Ć up to 30 characters) with the lock. This name is used in error
messages to other users who attempt to modify a locked file. The error message
displayed when someone attempts to access a locked file would look something
like the following:
If the User Name was undefined when the lock was taken, the message would
look something like the following: