lsdo

Lists derived objects created by clearmake, omake, or clearaudit (dynamic views only)

Applicability

Product

Command type

VersionVault

cleartool subcommand

Platform

UNIX

Linux

Windows

Synopsis

lsdo [ –r/ecurse ] [ –me ] [ –l/ong | –s/hort | –fmt format-string ]
[ –zer/o ] [ –sti/me | –sna/me ] [ –nsh/areable_dos ] [ pname ... ]

Description

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 path name.

By default, lsdo lists all derived objects built at a given path name, except for the following kinds of DOs:

  • Unshared DOs with a zero reference count (unless you use the –zero option).
  • DO versions, derived objects that are checked in as versions of elements.
  • Nonshareable DOs built in other dynamic views. (The –nshareable_dos option lists only nonshareable DOs in the current dynamic view.)
  • Derived objects created with one name and subsequently renamed (for example, by winkin –out or some operating system command).

You can use pname arguments to restrict the listing to derived objects with particular path names or to all the derived objects in particular directories. You can specify a derived object with a standard path name or with an extended name that includes a derived object's unique DO ID.

DOs in unavailable dynamic views

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.

Restrictions

None.

Options and arguments

Handling of directory arguments

Default
If any pname argument is a directory, the DOs in pname are listed, but not the DOs in any subdirectories of pname.
–r/ecurse
Includes DOs in the entire subtree below any pname that is a directory (or the current working directory if you do not specify any pname arguments). VOB symbolic links are not traversed during the recursive descent into a directory.

Selection of derived objects

Default
lsdo lists DOs created by any user, but excludes DOs whose data containers no longer exist.
–me
Restricts the listing to derived objects that you created.
–zer/o
In addition to listing DO's that are listed by default, also lists unshared (that is, never shared) derived objects that have zero reference counts. Such objects cannot be candidates for configuration lookup and winkin, because their data containers no longer exist.
–nsh/areable_dos
Lists only nonshareable DOs created in the current dynamic view, by any user.

Controlling report appearance

Default
In a listing of several DOs, the entries are sorted by derived object name. Within a group of like-named DOs, the entries are sorted chronologically, most recent entry first. The –long, –short, and –fmt options are mutually exclusive; the –sname and –stime options are mutually exclusive.

Each DO's listing includes its extended name (including DO ID) along with creation-related data: time, user name, and host name. For example:

11-Jun.12:00 akp "hello.o@@11-Jun.12:00.554" on neptune

–l/ong
Expands the listing to include a DO's size in bytes, the last access time, the reference count, and the dynamic views that reference the DO.
–s/hort
Restricts the listing for a DO to its extended name (including DO ID).
–fmt format-string
Lists information using the specified format string. For details about using this report-writing facility, see the fmt_ccase reference page.
–sti/me
Sorts all entries chronologically, most recent entry first.
–sna/me
(Same as default) Sorts entries alphabetically by name.

Specifying the derived objects

Default
Lists all derived objects created in the current working directory.
pname ...
Standard path names and/or DO IDs:
  • A directory name causes all derived objects built in that directory to be listed.
  • A standard or view-extended path name of a file causes all derived objects built under that name to be listed.
  • A path name that includes a unique DO ID (for example, conv.obj@@19-Nov.21:28.127450) specifies a particular derived object to be listed.

Examples

The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you might 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 might 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.

  • List, in reverse chronological order, all derived objects that you have created in the current working directory.

    cmd-context  lsdo –stime –me –short
    ctl@@05-14T15:18.339307
    ctl_V.o@@05-14T15:18.339305
    libcmd.a@@05-14T15:16.339302
    libcmd_V.o@@05-14T15:16.339300
    cmd_type.o@@05-14T15:15.339297
    cmd_view.o@@05-14T15:15.339294
    cmd_utl.o@@05-14T15:15.339291
    cmd_trig.o@@05-14T15:14.339288
    cmd_lh.o@@05-14T15:14.339285

  • List information on a derived object, identified by its extended path name.

    cmd-context  lsdo util.obj@@12-08T12:06.231
    12-08T12:06 "util.obj@@12-08T12:06.231"

  • List all nonshareable DOs in and under the current working directory.

    cmd-context lsdo –recurse –nshareable_dos
    10-20T16:35 "foo4.o@@10-20T16:35.2147484252"
    10-21T11:39 "foo7.dir/foo.cr_test.o@@10-21T11:39.2147484095"

  • List all derived objects created in the current working directory with file name hello. Use the long format, to show which dynamic views reference the DOs; include DOs that are not referenced by any dynamic view.

    cmd-context  lsdo –long –zero hello
    2006-12-08T12:06:19 Chuck Jackson (test user) (jackson.dvt@oxygen)
     create derived object "hello@@12-08T12:06.234"
     size of derived object is: 18963
     last access: 2007-01-29T13:56:56
     references: 1 => oxygen:/usr/vobstore/tut/old.vws
    2006-12-08T12:05:35 Chuck Jackson (test user) (jackson.dvt@oxygen)
     create derived object "hello@@12-08T12:05.143"
     size of derived object is: 18963
     last access: 2007-01-29T13:56:56
     references: 0 (shared)

  • List the name, kind, and reference count of each derived object in the current working directory.

    cmd-context lsdo –fmt "%n\t%[DO_kind]p\t%[DO_ref_count]p\n"
    foo.c@@05-08T20:00.354170     shared     3
    foo.c@@06-10T18:35.236855     shared     2
    foo.c@@09-25T04:00.456        unshared   1
    ...