OpenMake Meister

OOMLOM and a Life Cycle Model

Defining Search Paths based on the Life Cycle Model involves using a dataset to represent each stage of the life cycle. For example, a common Life Cycle model uses the three stages: DEVELOPMENT, QA, and RELEASE. These life cycle stages are often mapped to "Views" that are managed by your Configuration Management Tool.  The source code associated with each of the stages is mapped to a corresponding dataset on the file system.  For example, the files associated with the Configuration Management tool's DEVELOPMENT "view" would be located in a corresponding directories based on the file Type:

//HR.PAYROLL.DEV.COBOL

//HR.PAYROLL.DEV.COPYBOOK

The TEST files would be located in the datasets:

//HR.PAYROLL.TEST.COBOL

//HR.PAYROLL.TEST.COPYBOOK

The RELEASE files would be located in the datasets:

//HR.PAYROLL.RELEASE.COBOL

//HR.PAYROLL.RELEASE.COPYBOOK

When OOMLOM executes it searches the Search Path in a particular order as defined in the Web Client under "Managing Project".  It first searches the local "High Level Qualifier" as the User's local working dataset. The working dataset contains the source code that the developer is modifying. In addition, as the build progresses, the resulting load modules created from the build are stored in the Load dataset associated to the User's "High Level Qualifier". For this reason, every Search Path must contain a "." (period).  The "." signifies the local Dataset not specifically defined in the Search Path.   Every Search Path must have the local Build Dataset listed. 

It is important to note that the local Build Dataset, defined based on the "High Level Qualifier", is not required to contain any source code.  In fact, for Testing and Release builds, it is recommended that this local Dataset not contain source code.  OOMLOM knows to search the Search Path for the source code that is required by the compiler. OOMLOM will search through the Search Path directories locating the source code on a "first found" basis.  This dataset concatenation allows you to manage a base level of code in one dataset and code that is being changed in another dataset.   OOMLOM finds the correct version of the source code along the Search Path and passes the correct file to the compiler.

The Web Client displays the order in which the datasets are searched.  You can use the Web Client to re-order, add or delete datasets from the Search Path.  OOMLOM searches the directories starting from the top of the Web Client dataset list and ending at the bottom.  There is no limit to the number of Search Path datasets used in a Search Path.