The lsprivate command lists the file system objects that belong to a dynamic view:
Except for the shared derived objects, all of these objects are stored in the dynamic view's private storage area.
This command does not list checked-out directory elements, because such a checkout does not produce a view-private object. To list directory checkouts, use the lscheckout command.
The objects are listed with full pathnames (thus including the VOB tag), one per line.
Note: lsprivate does not work in a snapshot view. In a snapshot view, (cleartool) ls -recurse -view_only provides output equivalent to that of lsprivate.
lsprivate sometimes lists a view-private file in a special way, because the file has become stranded: it has no name in the VOB namespace, as currently constructed by your dynamic view. There are several possible causes and, hence, several actions you can take.
The lsprivate listing for a file can include a version-extended pathname to some directory element:
In this example, file canUCme is stranded because its parent directory, subdir1, does not appear in the dynamic view as it is currently configured; but the file can be accessed through version /main/3 of directory element src, which contains an entry for subdir1. (Note that you cannot use this pathname to access the view-private object. A version-extended pathname can refer only to an element, branch, or version—not to a view-private file.)
To make a stranded file visible again, you must make its parent directory visible, by reconfiguring the dynamic view (in this case, to select version /main/3 of directory element src).
If a VOB is not currently active on your host, all view-private files corresponding to that VOB are temporarily stranded. lsprivate displays a warning message and prefixes a number sign (#) to pathnames within that VOB:
cleartool: Warning: VOB not mounted: “M:\jc_vw\jc_hw”
VOB UUID is 1127d379.428211cd.b3fa.08:00:69:06:af:65
.
.
..
#M:\jc_vw\jc_hw\src\.cmake.state
#M:\jc_vw\jc_hw\src\findmerge.log.18-Mar-99.13:43:27
#M:\jc_vw\jc_hw\src\hello
#M:\jc_vw\jc_hw\src\hello.o
.
.
.
Reactivating the VOB on your host restores lsprivate command output to normal for pathnames within that VOB.
If a VOB has been unregistered, all view-private files corresponding to that VOB are temporarily stranded; if the VOB has been deleted, the view-private files are stranded permanently. lsprivate cannot distinguish these cases; it may infer the VOB's likely VOB tag, but it lists the view-private files with an Unavailable–VOB prefix:
cleartool: Error: Unable to get VOB object registry information for
replica uuid "1127d379.428211cd.b3fa.08:00:69:06:af:65".
cleartool: Warning: VOB is unavailable -- using name: "<Unavailable-VOB-1>".
If it has been deleted use 'recoverview -vob <uuid>'
VOB UUID is 1127d379.428211cd.b3fa.08:00:69:06:af:65
Last known location of storage is phobos:/usr/people/avid/tut/tut.vbs
#<Unavailable-VOB-1>/<DIR-3587d464.428211cd.b40c.08:00:69:06:af:65>
/.cmake.state
#<Unavailable-VOB-1>/<DIR-3587d464.428211cd.b40c.08:00:69:06:af:65>
/findmerge.log.18-Mar-99.13:43:27
The procedure for cleaning up stranded view-private files is described in the Administrator's Guide.
If a directory element (or its entire VOB) has been deleted, all the corresponding view-private files are permanently stranded. They are listed with the VOB's UUID, as above, with no remedy possible, except to use recoverview to move the files to the dynamic view's lost+found directory (as described in the Administrator's Guide).
pname-in-vob | Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted) |
Note: Specifying a pathname within the VOB does not limit the listing to objects in and below that directory.
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.
cmd-context lsprivate -tag jackson_vu -invob /usr/hw/src
/usr/hw/src/bug.report
/usr/hw/src/convolution.c [checkedout]
/usr/hw/src/edge.sh
/usr/hw/src/hello
/usr/hw/src/hello.c [checkedout]
/usr/hw/src/hello.h [checkedout]
/usr/hw/src/hello.o
/usr/hw/msg.o
/usr/hw/util.c [checkedout]
/usr/hw/util.c.contrib
/usr/hw/util.c.contrib.1
/usr/hw/util.o
cmd-context lsprivate -tag jc_vw -invob M:\jc_vw\jc_hw\src
M:\jc_vw\jc_hw\src\bug.report
M:\jc_vw\jc_hw\src\convolut.c [checkedout]
M:\jc_vw\jc_hw\src\edge.sh
M:\jc_vw\jc_hw\src\hello.c [checkedout]
M:\jc_vw\jc_hw\src\hello.h [checkedout]
M:\jc_vw\jc_hw\src\hello.o
M:\jc_vw\jc_hw\msg.o
M:\jc_vw\jc_hw\util.c [checkedout]
M:\jc_vw\jc_hw\util.c.contrib
M:\jc_vw\jc_hw\util.c.contrib.1
M:\jc_vw\jc_hw\util.o
cmd-context lsprivate –long
view private object M:\jc_vw\tmp_vob\scd_reach\src
\findmerge.log.04-Feb-99.10:01:01
view private object M:\jc_vw\tmp_vob\scd_reach\src\
findmerge.log.04-Feb-99.11:00:59
version M:\jc_vw\doc\reqs@@\main\CHECKEDOUT from
\main\33 Rule: element * CHECKEDOUT
version M:\jc_vw\doc\specs@@\main\CHECKEDOUT from
\main\7 Rule: element * CHECKEDOUT
cmd-context lsprivate –size –age
/tmp/sg_test/.cmake.state
Size: 2724
Age: 05-Apr-99.16:01:10
/tmp/sg_test/bar
Size: 10
Age: 05-Apr-99.16:00:54
/tmp/sg_test/foo
Size: 10
Age: 05-Apr-99.16:00:53
/tmp/sg_test/foobar
Size: 20
Age: 05-Apr-99.16:00:55
total size of view private files is 2764
total size of shared derived objects is 0
Copyright© 2003 Rational Software. All Rights Reserved.