Specifying a derived object in commands
In general, you use standard path names to access DOs when you're working in a view that references them.
To standard software (for example, linkers and debuggers), the standard path name of a derived object (util.o) references the DO.
This is another example of HCL VersionVault transparency: a standard path name accesses one of many different variants of a file system object. However, note this distinction.
- A version of an element appears in a dynamic view because it is selected by a configuration specification rule.
- A particular derived object appears in a dynamic view as the result of a build or a winkin.
To access a DO in another dynamic view, use a view-extended path name:
M:\drp\vob_proj\src\msg.obj M:\R2_integ\vob_proj\src\msg.obj |
(the DO in view drp) (the DO in view R2_integ) |
To specify a certain DO in a VersionVault command, use the DO-ID. For example, you can use a DO-ID in the catcr command to view the contents of a config record of a specific DO:
cleartool catcr x.o@@29-Jun.14:40.88
Because DO-IDs can change, avoid using them in files or scripts that operate on a DO.
Instead, use a standard path name or the object identifier (OID) of the derived object,
which never changes. To determine a object identifier of a DO, use
cleartool
describe
-fmt "%On\n"
. For example:
cleartool describe -fmt "%On\n" x.o@@29-Jun.14:40.88
2c5fc68a.2e5311d3.a382.00:01:80:7b:09:69
Also, a derived object is assigned a permanent identifier when it is checked in as a version of an element. For more information, see Working with DO versions.