IBM Support

Renaming a Baseline does not change the label type name

Question & Answer


Question

Why does renaming an IBM® Rational® ClearCase® Unified Change Management (UCM) Baseline not rename the corresponding label type?

Answer

Renaming a baseline within the project changes the name of the baseline; however, when looking at the version tree for an element using said baseline, the label displayed has the original label type name.

ClearCase is working as designed. ClearCase does not rename the lbtype automatically when a baseline is renamed because the lbtype is used as a version selector in every view that is attached to a stream using this baseline. If a UCM baseline lbtype is also renamed, it is necessary to run 'cleartool chstream -gen stream:<stream@pvob>' for every stream using this baseline. It is then necessary to run 'cleartool setcs -stream' within every view associated to the stream. Since it cannot be guaranteed that every view is available to the system that is renaming a UCM lbtype, this cannot be automated.

Additional considerations are that many IBM integrations (including IBM Rational ClearQuest and IBM Rational Build Forge) and some third party integrations potentially generate records and text fields depicting the name of UCM baselines. This data is static and, thus, no automated update of baseline name changes is possible.

You need to manually rename the label type (lbtype) from the original baseline name to the new baseline name to achieve the desired affects of having matching names. You may need to manually update records and text fields of integrated products.

Example:

The syntax to rename the label type:

cleartool rename lbtype:<old baseline name>@\<component vob tag> lbtype:<new baseline name>@\<component vob tag>

Note: If the second lbtype name is not entered correctly, you will see an "invalid name" error.

Also note that composite baselines in rootless components do not have a corresponding label to change.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"UCM: Baseline","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0.1;7.0;2003.06.00;2002.05.00","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"UCM: Baseline","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21251401