The lsdo command lists information about one or more derived objects (DOs) in a VOB. Derived objects are created by clearmake, omake, and clearaudit when these tools are invoked from a dynamic view. lsdo lists derived objects without respect to which dynamic views (if any) reference them. At any given time, a dynamic view sees at most one derived object at a given pathname.
By default, lsdo lists all derived objects built at a given pathname, except for the following kinds of DOs:
You can use pname arguments to restrict the listing to derived objects with particular pathnames or to all the derived objects in particular directories. You can specify a derived object with a standard pathname or with an extended name that includes a derived object's unique DO ID.
lsdo maintains a cache of tags of inaccessible dynamic views. For each view tag, lsdo records the time of the first unsuccessful contact. Before trying to access a dynamic view, lsdo checks the cache. If the view's tag is not listed in the cache, lsdo tries to contact the dynamic view. If the view's tag is listed in the cache, lsdo compares the time elapsed since the last attempt with the time-out period specified by the CCASE_DNVW_RETRY environment variable. If the elapsed time is greater than the time-out period, lsdo removes the view tag from the cache and tries to contact the dynamic view again.
The default timeout period is 60 minutes. To specify a different time-out period, set CCASE_DNVW_RETRY to another integer value (representing minutes). To disable the cache, set CCASE_DNVW_RETRY to 0.
Each DO's listing includes its extended name (including DO ID) along with creation-related data: time, user name, and host name. For example:
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 lsdo –stime –me –short
ctl@@14-May.15:18.339307
ctl_V.o@@14-May.15:18.339305
libcmd.a@@14-May.15:16.339302
libcmd_V.o@@14-May.15:16.339300
cmd_type.o@@14-May.15:15.339297
cmd_view.o@@14-May.15:15.339294
cmd_utl.o@@14-May.15:15.339291
cmd_trig.o@@14-May.15:14.339288
cmd_lh.o@@14-May.15:14.339285
cmd-context lsdo –long –zero hello
08-Dec-98.12:06:19 Chuck Jackson (test user) (jackson.dvt@oxygen)
create derived object "hello@@08-Dec.12:06.234"
size of derived object is: 18963
last access: 29-Jan-99.13:56:56
references: 1 => oxygen:/usr/vobstore/tut/old.vws
08-Dec-98.12:05:35 Chuck Jackson (test user) (jackson.dvt@oxygen)
create derived object "hello@@08-Dec.12:05.143"
size of derived object is: 18963
last access: 29-Jan-99.13:56:56
references: 0 (shared)
Copyright© 2003 Rational Software. All Rights Reserved.