Using Optimizer › JCL

JCL

To execute the Optimizer component, refer to a copy of your installation's cataloged procedures for a compile/optimize and link (or compile/optimize, link, and go).

The standard CA procedure is a compile/optimize and link and is called CAIOPTII. This is an example of how to invoke the procedure and specify Optimizer component options:

//STEP1 EXEC CAIOPTII,
//      COBOPT='MOFFSET,MMAP,MXREF'

where COBOPT is a symbolic option defined in the CAIOPTII procedure.

Note: You can combine Optimizer options with compiler options in any order. If the procedure at your installation does not have a symbolic option for the PARM options, you can pass Optimizer options the same way you specify compiler options:

//STEP1 EXEC CAIOPTII,
//      PARM.COB='MXREF,MOFFSET,MMAP'

When your program is link-edited, an CA Optimizer/II program initialization module is automatically linked with your program. The routine is reentrant so there is never more than one copy in a load module. With one exception*, no other CA Optimizer/II runtime modules are linked with your program. Additional CA Optimizer/II runtime modules are dynamically loaded, as needed, dependent upon the Detector or Analyzer facilities requested at compile-time.

* If you have inserted a CALL in a program to the SNAP routine (CAODSNAP), and NODYN was specified at compile/optimize time, CAODSNAP is link-edited with the program.