4.3 Unloading Elements

If a view's config spec no longer selects an element, ClearCase removes, or unloads, it from the view. Unloading does not affect view-private files or view-private directories.

Updating can cause an element to be unloaded from a view in the following situations:

• You remove the load rule that specifies the element (or that specifies a directory element somewhere above it). For information on removing load rules, see To Change Which Elements Are Loaded into a Snapshot View.

• The version-selection rules no longer select any version of the element. This can happen when your config spec selects a version of the parent directory that no longer contains a version of the file element.

Unloading Files

The action that ClearCase takes to unload a file depends on the file's current state:

• For a file that is not checked out, ClearCase deletes the file from the view.

• For a hijacked file, ClearCase appends .unloaded to the file name, unless you set the Update Tool to delete hijacked files. (Hijacked files are discussed throughout Appendix A, Working in a Snapshot View While Disconnected from the Network.) You change the settings on the Advanced tab in the Start Update dialog box. Refer to Updating the View.

• For a checked-out file, ClearCase appends .unloaded to the file name. The version remains checked out to your view.

Unloading Directories

ClearCase unloads directories recursively. To unload a directory element, ClearCase unloads the files in the directory. If any view-private objects, hijacked files, or checked-out files are in the directory, or if the directory is currently in use (for example, if your current working directory is in or below the directory) ClearCase appends .unloaded to the name of the directory. For example, if the directory src contains view-private files, ClearCase renames the directory to src.unloaded.