unregister

Removes an entry from the vob_object or view_object registry

APPLICABILITY

SYNOPSIS

• Unregister a VOB:

unreg·ister -vob { -uui·d uuid | vob-storage-dir-pname }

• Unregister a view:

unreg·ister -view { -uui·d uuid | view-storage-dir-pname }

DESCRIPTION

The unregister command removes the entry for a particular VOB or view from the network's vob_object or view_object registry. This does not affect VOB-tag or view-tag registry entries, and it does not affect the contents of the physical storage directories. See the Administrator's Guide for a discussion of the registry.

If you remove a VOB or view storage directory with an operating system command instead of rmvob or rmview, the VOB or view remains unregistered. In this case, you must use the -uuid option to unregister the associated storage directory (and use rmtag to remove relevant tag entries, if any still exist).

Other Commands that Affect Storage Registries

The mkview and mkvob commands add an entry to the appropriate registry; the rmview and rmvob commands remove registry entries (and the actual storage directories as well). You can use the register command to update an existing entry, or to re-register a VOB or view that has been unregistered.

The reformatvob command updates a VOB's object registry entry (or creates one, if necessary), but does not affect its tag registry entries.

RESTRICTIONS

None.

OPTIONS AND ARGUMENTS

UNREGISTERING VIEWS AND VOBS.  Default: None.

-vob vob-storage-dir-pname

-vob -uui·d vob-uuid

Use either form to specify the VOB whose vob_object registry entry is to be deleted. Use the VOB replica UUID reported by lsvob -long (not the VOB family UUID).

-view view-storage-dir-pname

-view -uui·d view-uuid

Use either form to specify the view whose view_object registry entry is to be deleted.

EXAMPLES

The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.

The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

NOTE: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf-for example, /vobs/src. A single-component VOB tag consists of a leaf only-for example, /src. In all other respects, the examples are valid for ClearCase LT.

• Unregister a VOB storage directory.

cmd-context unregister -vob /vobstore/vob2.vbs

• Unregister a view storage directory.

cmd-context unregister -view k:\vw_store\view5.vws

• Using the -uuid option, unregister a VOB storage directory that was mistakenly deleted with UNIX rm -rf instead of rmvob. In this example, the VOB replica UUID (do not use the VOB family UUID) is found in the output from lsvob -long. After unregistering the storage directory, remove the VOB-tag. If the VOB has tag registry entries for more than one network region, the -all option removes them all.

cmd-context lsvob -long /vobs/src (find the VOB replica uuid)

Tag: /vobs/src
Global path: /net/neptune/vobstore/src.vbs

.
.
.

Vob replica uuid: cb4caf2f.f48d11cc.abfc.00:01:53:00:e8:c3

ls /net/neptune/vobstore/src.vbs (verify storage directory was removed)

UX:ls: ERROR: Cannot access /net/neptune/vobstore/src.vbs: No such file or directory

cmd-context unregister -vob -uuid cb4caf2f.f48d11cc.abfc.00:01:53:00:e8:c3

cmd-context rmtag -vob -all /vobs/src

• As in the previous example, unregister a removed, but still registered, VOB storage directory. In this example, the VOB-tag has already been removed. Therefore, use the ccase-home-dir\log\scrubber_log, not lsvob, to find the VOB replica UUID. (lsvob lists only VOBs that have registered VOB-tags.) The scrubber utility, which runs nightly by default, reports the required UUID in an error message after failing to find the registered storage directory.

Z:\> type "c:\Program Files\Rational\ClearCase\log\scrubber_log"

.
.
.
05/27/99 04:30:58 scrubber: Error: Unable to get VOB tag registry information for
replica uuid "cb4caf2f.f48d11cc.abfc.00:01:53:00:e8:c3": ClearCase object not found
05/27/99 04:30:58 scrubber: Error: unable to access VOB \\neptune\vbstore\src.vbs:
ClearCase object not found
05/27/99 04:30:58 scrubber: Warning: skipping VOB \\neptune\vbstore\src.vbs errors
.
.
.

cmd-context unregister -vob -uuid cb4caf2f.f48d11cc.abfc.00:01:53:00:e8:c3

SEE ALSO

mktag, mkview, mkvob, mount, register, umount, Administrator's Guide