PLIDUMP now produces a Language Environment-style dump. The way you use PLIDUMP
and the dump output is different. The following list the differences
in the way you use PLIDUMP and the output produced. Compile unit refers
to the primary entry point of the external procedure and Compile unit name refers
to the name of the external procedure.
- The ddname of the dump output file can be CEEDUMP, PLIDUMP,
or PL1DUMP. If you do not define one of these files, Language Environment creates
a default CEEDUMP file to contain the dump output. The LRECL of
the dump output file must be at least 133 bytes to prevent dump
records from wrapping, not the 121 bytes required by OS PL/I.
- When you use the hexadecimal (H) option of PLIDUMP, you must
specify the ddname CEESNAP for MVS, or the file name CEESNAP for
VM; otherwise the H option is ignored. This data set contains the
SNAP dump output.
When you specify the hexadecimal (H) option under MVS, the output
from SNAP includes all system control program information (SDATA=ALL). OS PL/I provides only
partial information (SDATA=CB, Q, and TRT).
- When you use ILC, the dump output contains information related
to other languages (for example, C/C++ or COBOL).
- The identifier character string is limited to 60 bytes rather
than the 90 bytes OS PL/I supported.
- The traceback section lists the compile-unit name associated
with each entry point name. When the entry point is a secondary
entry point, the primary entry point name associated with the actual
entry point is not listed.
The traceback section also contains offsets relative to the address
of the compile unit, as well as offsets
relative to the address of the real entry point.
- Run-time messages are in a separate section; they are
no longer part of the traceback section.
- When you specify the BLOCK (B) option of PLIDUMP, the condition
handler save areas appear in the block section of the dump. If you
do not specify the BLOCK option of PLIDUMP, the condition handler
save areas do not appear in the dump.
- If the program was compiled with the TEST compile-time option,
and a begin-block has a label, the begin-block is identified as Label:BEGIN block.. Otherwise, the begin-block is identified as %BLOCKnn, where nn is the block count for the begin-block.
- Compiler-generated ILC subroutines now appear in the traceback
section. They are identified as the compile unit name concatenated
with the suffix ILC.
- PL/I library routines that have Language Environment-defined Program Prologue Areas
(PPAs) are identified by name in the dump. If the library routines
do not have Language Environment PPAs, they are identified as Library(PL/I).
- A HEX dump of STATIC storage
is included in the Language Environment formatted dump. If more than one routine
from a compilation unit is on the stack when a dump is produced,
static will be dumped only once for that compilation unit.
- Assembler routines that conform to the rules for mimicking PL/I routines
are identified by their CSECT names in the dump output.
- PLIDUMP now conforms to National Language Support standards.
- PLIDUMP can supply information across multiple Language Environment enclaves.
For example, if an application running in one enclave FETCHes a
main procedure (an action that creates another enclave), PLIDUMP
contains information about both procedures.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)