Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Migration Guide

Compiler migration

It is strongly recommended that you recompile all your source with the new Enterprise PL/I compiler (unless you have already recompiled all your source with VisualAge PL/I). Since the Enterprise PL/I compiler is a completely different compiler from the ’old’ PL/I compilers, recompiling your source would the best way to avoid the limitations imposed by mixing ’new’ PL/I with ’old’ PL/I object and load modules.

Compiler migration can be done all at once or by separate execution units. How to divide up your PL/I source into separate execution units is described in Partitioning PL/I source programs into units of execution.

If you decide to mix old PL/I modules with Enterprise PL/I modules, there are limited circumstances in which this mix will work. These limitations are described in Object and load module considerations.

In a few cases, some changes to your code will be necessary when moving from OS PL/I to Enterprise PL/I. These cases are described in Understanding when working code must be changed and Understanding when working code may need to be changed.

If you have already moved to Language Environment and are migrating to the new IBM Enterprise PL/I for z/OS compiler, you can begin reading about migrating to the new compiler in Planning to move to the new compiler.

If you are migrating to the PL/I for MVS & VM compiler, you should be using the IBM PL/I for MVS & VM Compiler and Run-Time Migration Guide.


Terms of use | Feedback

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