OpenMake Meister

Example Life Cycle Search Paths

Example Search Path for Development

Project = HR.Payroll 

Search Path Name  = Development

//.

//ARCH.REUSE.TEST.COBOL

//ARCH.REUSE.PROD.COBOL

//ARCH.REUSE.TEST.COPYBOOK

//ARCH.REUSE.PROD.COPYBOOK

//HR.PAYROLL.DEV.COBOL

//HR.PAYROLL.TEST.COBOL

//HR.PAYROLL.RELEASE.COBOL

//HR.PAYROLL.DEV.COPYBOOK

//HR.PAYROLL.TEST.COPYBOOK

//HR.PAYROLL.RELEASE.COPYBOOK

In this example, OOMLOM would first look for the "Architecture" reusable code starting at the "TEST" stage of the Search Path.  If no reusable code modules were found at the "TEST" stage, then OOMLOM would look for the reusable code modules at the "RELEASE" level.  This example also shows that OOMLOM would search for the payroll specific source code starting at the "DEV" stage and ending at the "RELEASE" stage.  When source code is found in the datasets at the top of the list, the datasets at the bottom of the list are not searched.

Example Search Path for Test

Project = HR.Payroll

Search Path Name = TEST

//.

//ARCH.REUSE.PROD.COBOL

//ARCH.REUSE.PROD.COPYBOOK

//HR.PAYROLL.TEST.COBOL

//HR.PAYROLL.RELEASE.COBOL

//HR.PAYROLL.TEST.COPYBOOK

//HR.PAYROLL.RELEASE.COPYBOOK

This example assumes that the "TEST" stage for the Payroll Project is the last build before production release. In this case, it is important to build the Payroll load modules with the "Release" level of the Architecture reusable code.