PLIDUMP usage notes

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.
In MVS™ or TSO, you can use ddnames of CEEDUMP, PLIDUMP, or PL1DUMP to direct dump output. If no ddname is specified, CEEDUMP is used.
The data set defined by the PLIDUMP, PL1DUMP, or CEEDUMP DD statement should specify a logical record length (LRECL) of at least 131 to prevent dump records from wrapping.
When you specify the H option in a call to PLIDUMP, the PL/I for MVS & VM 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 provided only under MVS. SNAP dumps are not produced in a CICS® environment.
- If the SNAP does not succeed, the CEE3DMP DUMP file displays the message:
```
Snap was unsuccessful
```
  Failure to define a CEESNAP data set is the most likely cause of an unsuccessful CEESNAP.
- If the SNAP is successful, CEE3DMP displays the message:
```
Snap was successful; snap ID = nnn
```
  where nnn corresponds to the SNAP identifier described above. An unsuccessful SNAP does not result in an incrementation of the identifier.
To ensure portability across system platforms, use PLIDUMP to generate a dump of your PL/I for MVS & VM routine.