OpenMake Meister

Naming Search Paths

Search Paths should be named according to the Life Cycle State for which they represent. The are two methods for managing Search Paths, one based upon a life cycle model and the other based upon a "Label" code branching model.  How you name the Search Path depends on how you manage your overall configuration management process.

Managing your Search Paths based on a "Life Cycle" indicates that you will define a library concatenation for each stage in the "Life Cycle".  When OOMLOM reads the library concatenation, it would search through the datasets looking for the source code.  When it locates the source code, it would stop searching through the Search Path.  Using this method allows you to define dataset concatenations that represent Life Cycle Stages i.e.,  DEV, TEST, PROD, and EMER, and to tell OOMLOM to create the load modules depending on the Life Cycle State.  It also allows you to manage only the source code that is active at each of the different Life Cycle Stages.  For example, only the source code currently under development would need to be in the development dataset.  The remainder of the source code would be found in the production dataset.

Managing your Search Path based on a "Label" indicates that your datasets will always contain all of the source code and that your Search Path library concatenation will not be specific to a location in the Life Cycle.  This method limits the number of datasets needed for a single Search Path, but increases the physical size of the datasets needed for each build as source code is managed in multiple datasets.

The only restriction on the Search Path Name is that it cannot have the following characters as part of the Name:

\  /  :    *    ?    "   <     >   |   &