Rational Developer for System z
Enterprise PL/I for z/OS, Version 4.2, Compiler and Run-Time Migration Guide

OPTIMIZE(2)/OPTIMIZE(3)

To optimize the performance from the compiler generated code, use either OPTIMIZE(2) or OPTIMIZE(3) together with DFT(REORDER).

If you use OPTIMIZE(2) or OPTIMIZE(3) with DFT(ORDER) rather than DFT(REORDER), the runtime performance is less optimal and the compile time might be much longer.

Note that OPT(3) will produce slightly better code than OPT(2), but the compiler will take much longer to compiler programs (especially large programs) under OPT(3) than under OPT(2). For this reason, the compiler maps OPT(TIME) to OPT(2).


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)