Eligible compilers
IBM® Automatic Binary
Optimizer for z/OS® 2.3 can optimize CSECTs within program
modules that were generated by the following COBOL compilers:
Notes:
- COBOL modules that have been processed by CA-Optimizer cannot be optimized by ABO. For these types of modules it is recommended to use ABO to optimize the original module created by the COBOL compiler before it was processed by CA-Optimizer.
- Enterprise COBOL 6.4 or later compiler programs must be compiled with the SMARTBIN compiler option to be eligible for ABO optimization. Programs compiled with SMARTBIN contain extra binary metadata that allows ABO to optimize them. This binary metadata is only produced by Enterprise COBOL 6.4 or later and is required for ABO optimization for Enterprise COBOL 6.4 or later produced CSECTs. Compiled programs produced by all earlier versions and releases of the COBOL compiler do not produce this extra binary metadata, nor is it required for ABO optimization.
- The binary metadata produced under SMARTBIN is placed in a NOLOAD section of the module by the compiler. These SMARTBIN enabled modules will require more disk space compared to using NOSMARTBIN but there is no memory increase when the compiled code is running, because NOLOAD sections are not loaded by default. This binary metadata is only loaded when needed for later ABO optimization.
- CSECTs produced by the initial Enterprise COBOL for z/OS 5.1.0 are not eligible for optimization. CSECTs produced by Enterprise COBOL for z/OS 5.1.1 and later are eligible for optimization assuming other eligibility checks pass.
- To be eligible for ABO optimization, VS COBOL II programs must have been migrated away from using the VS COBOL II run time. For the steps required, see Chapter 7. Moving from VS COBOL II run time in Compiler and Runtime Migration Guide for Enterprise COBOL for z/OS 4.2.