Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Derived objects and configuration records
Learn about derived objects and configuration records.
Reuse of DO IDs
The DO ID for a shareable derived object is guaranteed to be unique within the VOB, for all views.

Managing change and releases
Learn how to manage change and release in the product.
- Managing software projects
- Workflow for creating projects
- Workflow for making baselines
- Workflow for recommending baselines
- Guide to building software on Linux and UNIX
  - HCL VersionVault build concepts
    HCL VersionVault supports makefile based building of software systems and provides a software build environment closely resembling that of the make program.
  - Derived objects and configuration records
    Learn about derived objects and configuration records.
    - Derived objects overview
      Derived objects are created during builds with HCL VersionVault build tools. They are used for build avoidance and derived object sharing.
    - Configuration records
      A configuration record (CR) is the bill of materials for a derived object or set of DOs.
    - Kinds of derived objects
      There are two main types of derived objects (DOs), shareable DOs and nonshareable DOs.
    - Reuse of DO IDs
      The DO ID for a shareable derived object is guaranteed to be unique within the VOB, for all views.
    - Derived object reference counts
      A reference count of a DO is the number of times the derived object appears in HCL VersionVault dynamic views throughout the network.
  - Pointers on using HCL VersionVault build tools
    Learn how to use VersionVault build tools.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The HCL VersionVault build program, clearmake can process makefiles.
  - Using clearmake compatibility modes
    clearmake is designed for compatibility with existing make programs, which minimizes the changes you need to make to your makefiles.
  - Using HCL VersionVault to build C++ programs
    Use clearmake effectively with C++ programs built with various compilers.
  - Using HCL VersionVault build tools with Java
    The build behavior of Java tools causes various problems for clearmake. Understand the problems and some possible solutions to resolve them.
  - Setting up a parallel build
    Learn the process to set up and run builds that use several hosts in the local area network.
  - Building software for multiple platforms
    Learn how to address the challenge of using a single source tree to develop an application for a variety of hardware and software platforms.
  - Setting up a build on a non-VersionVault host
    There is a technique to create configuration records for a build that involves HCL VersionVault data, but is performed on a non-VersionVault host.
- Guide to building software on Windows

Reuse of DO IDs

The DO ID for a shareable derived object is guaranteed to be unique within the VOB, for all views.

That is, if you delete a shareable DO, its numeric file name extension is not reused (unless you reformat the VOB that contains it).

The DO ID for a DO created by an express build (a nonshareable derived object) is unique only at a certain point in time. If you delete a nonshareable DO, the HCL VersionVault build tools can reuse its numeric file name extension. (Because VersionVault tracks derived objects using their VOB database identifiers, no build confusion occurs if a file name extension is reused.)

DO IDs change when any of these events occur:

The DO passes its first birthday. The time stamp changes to include the year the DO was created:
```
util.o@@15-Jul.15:34.8896 (when first created)
```
```
util.o@@15-Jul-2002.8896 (after a year)
```
You convert a nonshareable DO to a shareable DO. (For more information, see Converting nonshareable DOs to shared DOs.)
You process the database of a VOB with reformatvob. All DO-IDs receive new numeric file-name extensions:
```
util.o@@15-Jul.15:34.8896 (before reformatvob)
```
```
util.o@@15-Jul.17:08.734 (after reformatvob)
```

The configuration record reflects these DO-ID changes.