Sun WorkShop TeamWare 2.1 User's Guide

The Workspace Metadata Directory

A Configuring workspace is a directory hierarchy that contains a directory named Codemgr_wsdata in its root directory. the Configuring program stores data (metadata) about that workspace in Codemgr_wsdata. Configuring commands use the presence or absence of this directory to determine whether a directory is a workspace.

TeamWare Configuring provides the tools necessary to maintain the information kept in the Codemgr_wsdata directory. Although not recommended, on rare occasions it may be necessary to modify certain files manually. However, great care must be taken to understand and preserve the format of each file being edited. Table 7-1 briefly describes each of the files and directories contained in the metadirectory. Information regarding the format of these files is available in the man(4) page for each file.

Table 7-1 Contents of the Codemgr_wsdata Metadata Directory


File/Dir Name	Description
`access_control`	The `access_control` file contains information that controls which users are allowed to execute Configuring transactions and commands for a given a workspace. When workspaces are created, a default access control file is also created. See "Controlling Access to Workspaces".
`args`	The `args` file is maintained by the Configuring Bringover and Putback transaction commands and contains a list of file, directory, and FLP arguments. Initially, the `args` file contains the arguments specified when the workspace was created. If you explicitly specify arguments during subsequent Bringover or Putback transactions, the commands determine if the new arguments are more encompassing than the arguments already in the `args` file; if they are, the new arguments replace the old.
`backup/`	The `backup` directory is used to store information that Configuring uses to "undo" a Bringover or Putback transaction. See "Reversing Bringover and Putback Transactions with Undo ".
`children`	The `children` file contains a list of the workspace's child workspaces. The names of child workspaces are entered into the workspace's `children` file during the Bringover Create transaction. Configuring consults this file to obtain the list of child workspaces. When you delete, move, or reparent a workspace, Configuring updates the `children` file in its parent.
`conflicts`	The `conflicts` file contains a list of files in that workspace that are currently in conflict. See Chapter 9, Resolving Conflicts," for more information about conflicts and how to resolve them.
`history`	The `history` file is a historical log of transactions and updated files that affect a workspace. See "Viewing Workspace Command History" for more information.
`locks`	To assure consistency, Configuring locks workspaces during Bringover, Putback and Undo transactions. Locks are recorded in the `locks` file in each workspace; Configuring consults that file before acting in a workspace. See "Ensuring Consistency Through Workspace Locking".
`nametable`	The `nametable` file contains a table of SCCS file names (path names relative to that workspace) and a unique number represented as four 32-bit hexadecimal words. Each entry in the table is terminated by a newline character. The `nametable` file is used by Configuring during Bringover and Putback to accelerate the processing of files that have been renamed. If this file is not available, Configuring rebuilds it automatically during the next Putback or Bringover transaction. See "Renaming, Moving, or Deleting Files".
`notification`	The `notification` file is edited by users to register notification requests. This facility permits Configuring to detect events that involve that workspace and to send electronic mail messages in response to the event. See "How to Notify Users of Changes to Workspaces".
`parent`	The `parent` file contains the path name of the workspace's parent workspace and is created by the Bringover Create transaction, or by the Reparent command if the workspace was originally created with the Create Workspace command (and thus had no parent). Configuring consults this file to determine a workspace's parent. When you delete, move, or reparent a workspace, Configuring updates the `parent` file in its children.
`putback.cmt`	The `putback.cmt` file is a cache of the text of the comment from the last blocked Putback transaction. When a Putback transaction is blocked, the comment is discarded. Configuring caches the comment in `putback.cmt` so that you can retrieve the original text when you reexecute the transaction.