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

Partitioning PL/I source programs into units of execution

You will need to partition your PL/I source programs into units of execution to accommodate the restrictions on mixing and condition handling between old and new PL/I modules as described above.

Careful attention must be paid when partitioning your PL/I source programs into units of execution. Your goal is to contain any restrictions on mixing old and new PL/I modules within the boundaries of the units of execution that you define. For example, if Program A defines a CONTROLLED EXTERNAL variable and Program B references this variable and Program B also creates a file variable that it shares with Program C, then all three Programs A, B, and C must be compiled with Enterprise PL/I in order to work correctly.

Finally, note that when mixing old and new code, you must pay attention to the differences between how the new and old compilers handle various language constructs, as described in Understanding when working code must be changed.


Terms of use | Feedback

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