Project registers are distinct from ordinary registers.
They persist across builds and you can create and view them through
the Management Console interface, making them an ideal way to store
some kinds of configuration information.
For example, you could store an IBM® Rational® ClearCase® config
spec as a project register, then have a step use a .pop -p command
to extract the specification and use it with a cleartool setcs command,
configuring your build. This allows you to manage the configuration
along with the project.
If you have a project register named ALPHA, you could also have
an ordinary register named ALPHA, with entirely different contents.
Project registers are a separate set of values.
You can create and access project registers in two ways:
- Through dot commands (.push and .pop),
by adding a -p option. When you use the -p option,
your command refers to a project register, rather than an ordinary
register.
For example, a command
.push -p ALPHA register.txt
places
the contents of the file register.txt in the project register named
ALPHA.
- Through the Management Console interface. Select Projects, then
click the Edit icon
next to the desired project's name. The project properties
appear in the lower portion of the panel; click the Registers tab
to display the project's registers. The tab provides a panel for managing
registers:- To create a new register, enter a name and contents, and then
click Create.
- To delete a register, click the trash can icon next to the register's
name in the list at the right of the panel.
- To edit a register, click the Edit icon
next to the register's name in the list. The system
populates the register panel with the register's contents. Make
your changes, and then click the Save Edited Register button.
Anyone who has access to a project can view and edit its project
registers.
Note: The case-sensitivity of your underlying database determines
the cases you can use when you create register names.