The
PLIDEBUG.DAT file contains settings defining whether whether Enterprise Server should generate an "interrupt" when the program is loaded and is about to be executed.
PLIDEBUG.DAT is located in the installation directory.
.
Note: The file is not there when you install the product, it appears when you first try to execute a job.
To view the file and edit it:
- Invoke the dfed32 tool from a Telenet session using a command such as the following:
dfed32 $MFPLI_PRODUCT_DIR/PLIDEBUG.DAT. For additional information on how to use the dfed32 tool, see the Utitlities Guide in your local help.
Find the lines of
OPDEMO and
OPDEMO2. They should look like this:
OPDEMO Y Y
OPDEMO2 Y Y
The
Y in the first column indicates if the debugger
should generate an interupt when the step starts. The
Y in the second column
is not used in a UNIX environment.
If the two lines are not there, you need to create them.
Note:
- Make sure that the first
Y is in the 21st column.
- Always close down the editing session before you start debugging because otherwise the file will be locked and Enterprise Server won't access it.
