Using ABO and Enterprise COBOL together
IBMAutomatic Binary Optimizer for z/OS (ABO) can optimize the latest IBM® Enterprise COBOL for z/OS® program modules, up to and including Enterprise COBOL 6.5. ABO and the Enterprise COBOL for z/OS compiler serve complementary purposes.
- ABO optimizes COBOL program modules compiled by Enterprise COBOL; Enterprise COBOL compiles and optimizes COBOL source code.
- There is no performance trade-off when using ABO. In performance tests, ABO 2.3 and Enterprise COBOL 6.5 deliver comparable performance.
- ABO offers a faster path to performance gains. Migrating to Enterprise COBOL 6 can require multiple rounds of compile and test. Source code changes will be required if problems like invalid data are detected in existing applications.
- Use the latest Enterprise COBOL to compile new COBOL programs or to recompile COBOL programs that require changes. Use ABO to optimize your COBOL programs that are not in your recompilation plan or if the program source code is not available.
- Use the latest Enterprise COBOL to compile new programs with the best options for development, test, and debug, and then use ABO to optimize for best performance in production. This combination offers quicker time to value, with significantly reduced testing cost, and suits an iterative development model.
Table 1 can help you select which products to use.
| Use case | Automatic Binary Optimizer | Enterprise COBOL 6 | ABO + Enterprise COBOL |
|---|---|---|---|
Improve performance and reduce CPU usage:
|
√
In this case, you can use ABO to optimize modules directly |
√
In this case, you can use Enterprise COBOL 6, but migration, recompilation, and options tuning are required |
√
|
Improve performance and reduce CPU usage:
|
√
In this case, you can use ABO to optimize modules directly. |
||
| Implement new features and fix application defects. |
√
In this case, change your source, recompile with Enterprise COBOL 6 and test. |
||
| Improve performance of your IBM Enterprise COBOL for z/OS 4 and earlier programs that interoperate with OS/VS COBOL. |
√
In this case, ABO can be used to optimize IBM Enterprise COBOL for z/OS 4 and earlier programs that interoperate with OS/VS COBOL. |
√
In this case, the OS/VS programs must be migrated toEnterprise COBOL 6 to interoperate with new compiled code. |
√
|
| Testing requirements |
√
Significantly less as no risk due to invalid data/code and no source changes. Modules are directly optimized. |
√
Detecting problems (e.g. invalid data) requires a 2-step compile/test approach. Fixes require source changes. |
√
|