OpenMake Meister

Methods and OOMLOM

In order to understand how to develop your customized Methods, it is important to understand how the Methods interact with the generated Build Control file and the OOMLOM build engine. 

Methods are designed so that they contain no Target specific data.  The Methods are generic and use the Scripting Variables instead of hard coded values.  Methods are read by the OOMLOM engine and are translated into temporary "Target specific" REXX execs.  These REXX execs contain references to the actual Target information. OOMLOM gets the Target information for the batch file from the Build Control file.  OOMLOM also gets the Script information from the Build Control file. The Script information gets included in the Build Control file because OOMLBLDM generates the Build Control file with the generic Command Script appended at the bottom. The final step that OOMLOM performs is the execution of the Target specific batch file, which in turn, executes the build.

The temporary "Target specific" REXX exec is generated as a member of the <OPENMAKE_WORK>.<Generated Name>.CNTL PDS. The member name is randomly assigned. 

Note:  As a debugging tool, you can pass OOMLOM  the -ks parameter.  This parameter forces OOMLOM to "keep" the temporary script, so that it can be viewed to determine if the variables have been set correctly.