OpenMake Meister

OOMLOM JCL Usage

Once the Build Control file has been generated by OOMLBLDM, the next step in your JCL is to execute OOMLOM. OOMLOM reads the Build Control file and performs the build.  OOMLOM uses the Search Path, defined at the top of the Build Control file, to search for source code.  OOMLOM then uses PERL to execute the scripts, defined at the end of the Build Control file, to generate the compile JCL to create the Targets.

The first step that OOMLOM performs is the scanning of dependencies that are out of date according to the file date/time stamp.  At the bottom of the generated Build Control file, just above the Scripts, there is an "All Targets" label.  This label displays a list of all the Targets in the Build Control file. OOMLOM uses the "All Targets" label to determine what it needs to scan and build.

OOMLOM can act in many different ways, depending on the OOMLOM options and parameters.  For example, you can tell OOMLOM to build only certain Targets listed in the Build Control file. If you generate a Build Control file for an entire Project, but only want to build a single Target, you can pass the Target Name to OOMLOM. It will determine what needs to be done in order to accurately build the Target that you defined.  Following is the OOMLOM flags, as well as example JCL.

OOMLOM Flags