OpenMake Meister

OOMLOM and a Label Model

Depending on the particular configuration management practices of the development team, Project and Project Search Paths may be used to define different release levels of an application.  Development teams often use Version Labels to define a collection of source code to use in a particular build. This label is basically the same thing as a Search.  To support Version Labels using Build Project, a Search Path should be assigned to represent each Version Label. The Search Path would include the list of datasets required to build the application at that particular level. It would also include the local "High level Qualifier" dataset.

The local "High Level Qualifier" dataset is always the first location searched for source code in every build. The local dataset contains the source code that is being updated by the developer. In addition, the load modules created from the build are stored in the local dataset based on the "High Level Qualifier". For this reason, every Search Path must contain a "." (period).  The "." signifies the local dataset.   Every Search Path must have the local dataset listed.

The Version Label Search Path contains fewer datasets than the Life Cycle Search Path.  This method uses a single dataset for each source Type to represent the Project specific source code, unlike the Life Cycle method that uses multiple datasets to represent each state in the life cycle for each dataset Type.