If you use PLIDUMP, the following considerations apply:
- If a routine calls PLIDUMP a number of times, use a unique user-identifier
for each PLIDUMP invocation. This simplifies identifying the beginning
of each dump.
- A DD statement with the ddname PLIDUMP, PL1DUMP, or CEEDUMP
can be used to define the data set for the dump.
- The data set defined by the PLIDUMP, PL1DUMP, or CEEDUMP DD
statement should specify a logical record length (LRECL) of at least
133 to prevent dump records from wrapping. If SYSOUT is used as
the target in any one of these DDs, you must specify MSGFILE(SYSOUT,FBA,133,0)
or MSGFILE(SYSOUT,VBA,137,0) to ensure that the lines are not wrapped.
- When you specify the H option in a call to PLIDUMP, the PL/I library
issues an OS SNAP macro to obtain a dump of virtual storage. The
first invocation of PLIDUMP results in a SNAP identifier of 0. For
each successive invocation, the ID is increased by one to a maximum
of 256, after which the ID is reset to 0.
- Support for SNAP dumps using PLIDUMP is only provided under
z/OS. SNAP dumps are not produced in a CICS environment.
- If you want the program unit name, program unit address and program unit offset
to be listed correctly in the dump traceback table, you need to make sure that
your PL/I program unit is compiled with a compile-time option other than TEST(NONE,NOSYM).
For example, you can specify the option as TEST(NOSYM,NOHOOK,BLOCK).
If you want to ensure portability across system platforms, use
PLIDUMP to generate a dump of your PL/I routine.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)