Displaying configuration records for DO versions

The catcr command displays the configuration record for a DO version.

When you use catcr -recurse to display the CRs for a DO and all its subtargets, it does not display the CRs for DO versions unless you use the -ci option.

catcr allows precise control over report contents and format. It includes input and output filters and supports a variety of report styles. Input filters, such as -select, control which DOs are evaluated. All DOs that are evaluated can potentially appear in the final listing. Output filters, such as -view_only, control which DOs actually appear in the final listing. Often, this is a subset of all evaluated DOs.

You can tailor the report in several ways:

  • Generate a separate report for each derived object on the command line (default), or a single, composite report for all derived objects on the command line (-union).
  • Specify which derived objects to consider when compiling report output. The -recurse, -flat, -union, -ci, and -select options control which subtargets are evaluated. They generate recursive or flat-recursive reports of subtargets, evaluate checked-in DOs, and allow you to evaluate DOs with a particular name only.
  • Select the kinds of items that appear in the report. The -element_only, -view_only, -type, -name, and -critical_only options exclude certain items from the report.
  • Display the CR in makefile format (-makefile), rather than in a section-oriented format.
  • Choose a normal, long, or short report style. Expanding the listing with -long adds comments and supplementary information; restricting the listing with -short lists file system objects only. You can also list simple path names rather than version-extended path names (-nxname), and relative path names rather than full path names (-wd).

The -check option determines whether the CR contains any unusual entries. For example, it determines whether the CR contains multiple versions of the same element, or multiple references to the same element with different names.

By default, catcr suppresses a CR entirely if the specified filters remove all objects (useful for searching). With the -zero option, the listing includes the headers of such CRs.

The following examples show how to display configuration records for DO versions.

  • To display the configuration record for a single DO version:
    cleartool catcr x 
    Target x built by smg.user
    
    Host "radar" running SunOS 5.5.1 (sun4m)
    Reference Time 20-Jul-06.14:32:32, this audit started 20-Jul-06.14:32:32
    View was radar:/home/smg/views/smg_test.vws
    
    Initial working directory was /vobs/smg_test
    ----------------------------
    MVFS objects:
    ----------------------------
    /vobs/smg_test/file1.txt@@/main/2             <30-Jun-06.15:35:12>
    /vobs/smg_test/file2.txt@@30-Jun.15:33.115
    /vobs/smg_test/x@@/main/3
    ----------------------------
    Build Script:
    ----------------------------
            cat file1.txt > x
            cat file2.txt >> x
    ----------------------------
  • To display the configuration record for a derived object, including the CRs of all subtargets except DO versions:
    cleartool catcr -recurse x 
    ----------------------------
    ----------------------------
    Target x built by smg.user
    ...
    Target file2.txt built by smg.user
    ...
    Target file2sub.txt built by smg.user
    ...
  • To display the configuration record for a derived object, including the CRs of all subtargets:
    cleartool catcr -recurse -ci x 
    ----------------------------
    ----------------------------
    Target x built by smg.user
    ...
    Target file1.txt built by smg.user
    ...
    Target file1sub.txt built by smg.user
    ...
    Target file2.txt built by smg.user
    ...
    Target file2sub.txt built by smg.user
    ...

DOs in unavailable views

catcr maintains a cache of tags of inaccessible views. For each view tag, the command records the time of the first unsuccessful contact. Before trying to access a view, the command checks the cache. If the view's tag is not listed in the cache, the command tries to contact the view. If the view's tag is listed in the cache, the command 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, the command removes the view tag from the cache and tries to contact the view again.

The default time-out 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.

For more information, see the catcr reference page.