With Enterprise PL/I, you will find that existing PL/I applications are
affected by several areas such as removed or changed compiler options,
different default compiler options, and restrictions in combining
old and new load modules.
The following list of concerns is merely a representative list
that reflects what has been important to some customers. It may
not indicate what is important to any one individual customer. More
details are provided in the rest of this book.
- Enterprise PL/I supports only Language Environment releases currently in support.
- Enterprise PL/I has no support for VM.
- Enterprise PL/I has no support for multitasking (but it does support multithreading).
- Code that is incorrect or invalid (for instance, code that uses
uninitialized variables) may not run the same. This may not seem
like an important problem, but it has been a significant issue for
most of the customers that have migrated.
- You may need to specify some non-default options to get the
most compatible behavior from the compiler and to get the best performance
from the compiler.
- Programs may need to be tuned for optimal performance. In particular,
the use of the runtime option RPTSTG(ON), while useful when tuning,
is much more costly now to leave on in a production program.
- Recompiling all your PL/I source is recommended. If this isn't
done, you need to carefully select the compiler options for compiling Enterprise PL/I code
that will be mixed with older PL/I objects. You will also need
to divide your source into partitions according to how they use
FILEs, CONTROLLED variables and conditions. For more information,
see Object and load module considerations.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)