unregister

Removes an entry from the vob_object or view_object registry

Applicability

Product

Command type

VersionVault

cleartool subcommand

Platform

UNIX®

Linux®

Windows®

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 Help.

If you remove a VOB or view storage directory with an operating system command instead of with rmvob or rmview, the VOB or view remains registered. 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 system and Linux 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 system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

  • On a UNIX® or Linux® system, unregister a VOB storage directory.

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

  • On a Windows® system, 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® or Linux® rm –rf instead of rmvob. In this UNIX® and Linux® 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 all of them.

    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 Windows® example, the VOB tag has already been removed. Therefore, use the versionvault-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\HCL\CCM\VersionVault\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":
    VersionVault object not found
    05/27/99 04:30:58 scrubber: Error: unable to access VOB
    \\neptune\vbstore\src.vbs:  
    VersionVault 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