XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''"> File History and User Access
The File Manager maintains information related to the files that it manages and the users accessing them. Most of this tracking is accomplished through a history file. In addition, the File Manager maintains a record of the last file that has been accessed by each user of the system.
History Files
File Manager guarantees the existence of a history file for each file that is stored in the repository. This physical file is used to log the operations that are performed with respect to the associated logical file. The following table lists the actions that automatically generate history record entries and the format of that entry. The <DTU> prefix denotes a preceding date-time-user entry.
Action | History Entry |
NEW | <DTU> Created: template id# <template file id> |
OPEN - Write | <DTU> Accessed for Modification |
SAVE AS | <DTU> Saved from FileManager: file id# <original file id> |
COPY (from UNIX) | <DTU> Copied from UNIX: <original file name> |
COPY (to UNIX) | <DTU> Copied to UNIX: <new file name> |
COPY (from FM) | <DTU> Copied from FileManager: file id# <original file id> |
MOVE (from UNIX) | <DTU> Moved from UNIX: <original file name> |
MOVE (to UNIX) | <DTU> Moved to UNIX: <new file name> |
MOVE (from FM) | <DTU> Moved from FileManager: file id# <original file id> |
COMPRESS | <DTU> Compressed: method# <compression method> |
UNCOMPRESS | <DTU> Uncompressed: method# <compression method> |
ONLINE | <DTU> Online: method# <online method> |
OFFLINE | <DTU> Offline: method# <offline method> |
ASSOCIATE (source) | <DTU> Associated: target file id# <target file id> |
ASSOCIATE(target) | <DTU> Associated: source file id# <source file id> |
UNASSOCIATE (source) | <DTU> Unassociated: target file id# <target file id> |
UNASSOCIATE
(target) | <DTU> Unassociated: source file id# <source file id> |
RELEASE | <DTU> !!! RELEASED !!! |
UNRELEASED | <DTU> !!! UNRELEASED !!! |
In addition to the above automated history entries, the user is presented with the opportunity to add additional comments whenever a file is accessed with write privileges. Multi-line comments are supported and each line is set off by the greater than (>) character to designate it as user added. Below is a simple example of a history file that shows several interactions with and without user added comments.
13-Feb-96 14:32:56 john_smith
Created: template id# 1
14-Feb-96 08:14:22 jane_doe
Opened for Modification
> Updating material properties.
14-Feb-96 10:49:00 john_smith
Opened for Modification
> Creating element properties using new material definitions
> Importing load definitions
16-Feb-96 07:42:21 bob_jones
Copied from FileManager: file id# 1342
> Copy obtained to perform mass property analysis
...
User Access
File Manager records the last file that each user accessed for modification (i.e., the last file which was being worked on). After restarting the File Manager, the user is placed at the hierarchy location that contains the file, even if it has been moved by another user since the last session. In the event that this file has been deleted from File Manager, the user is placed back at the top of the hierarchy tree (this is intended to serve as an immediate indication of the deletion).