This book concentrates on the
migration effort in moving from OS PL/I or PL/I for MVS & VM to Enterprise
PL/I V4R1. If you have already moved to Enterprise
PL/I V3R1, V3R2, V3R3, V3R4, V3R5, V3R6, V3R7, V3R8, or V3R9,
migration to Enterprise PL/I V4R1 is relatively easy.
This chapter focuses on differences in the compiler options and in the
compiler messages, but there are some other differences in the compiler
output that might possibly affect users of earlier release of Enterprise PL/I:
- The compiler itself is compiled with ARCH(6) and any use of
it on a machine with older hardware causes the compiler to stop.
- The macro preprocessor now leaves %include
%xinclude, %inscan, and %xinscan in the compiler listing as comments.
- Listings now include 7 columns for the line number in a file.
- The MAP output now also includes a list in order of storage
offset (per block) of the AUTOMATIC storage used by the block.
- The length of the mnemonic field in the assembler listing is
increased to allow for better support of the new z/OS instructions
that have long mnemonics.
- More of the right margin is used in the attributes,
cross-reference and message listings.
- There are some small changes in the SYSADATA produced by the compiler:
- The chaining of the procedure records and their associated statements are changed so
that the block structure of a compilation is readily determined (more details are
available in the appendix in the Programming Guide).
- The edition and sysadata level numbers are updated (and these values could be
used to allow code to handle both the old and new chaining of the procedure recodes).
- The MAXNEST option can flag some old code in which the nesting of DO, IF, or
PROCEDURE statements is too deep.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)