I confirm that your UNC path cannot use localhost, but must start with the host name.
The reason is that the Vob storage path must be globally accessible, ie accessible from any computer (and localhost makes sense only from one computer).
The cleartool mkvob
man page includes:
Windows—vob-storage-pname must be a UNC name.
UNC (Uniform Naming Convention):
The Microsoft Windows UNC, short for Universal Naming Convention or Uniform Naming Convention, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows systems has the generic form:
\\ComputerName\SharedFolder\Resource
Microsoft often refers to this as a "network path".
One way for you to have a local path (without having to define a share) is to use the -stgloc
parameter, referring to the name of a pre-defined storage location (instead of -host -hpath -gpath
arguments)
See cleartool mkstgloc
(which defines storage locations for Vobs or Views).
You can use a local path there.
In many cases, ClearCase heuristically derives appropriate accessibility information from the
stgloc-pname
argument.
In cases where there is no file system connectivity between the server storage location and its clients, ClearCase derives the host name and host-local path, but because no meaningful global path can be derived, you must specify-ngpath
to unset the global path information.To create a server storage location for snapshot views or for VOBs intended to be accessed only through snapshot views, use these options:
-host -hpath -gpath
when there is file system connectivity between the server storage location host and its clients.-ngpath -host -hpath
when there is no file system connectivity between the server storage location host and its clients.
So be careful if you do this (-ngpath
option): your Vob won't be accessible through dynamic views, only snapshot views.