Note: Using
PLIDEBUG.DAT is currently only supported on Windows platforms.
CodeWatch lets you specify debug settings in a file that is created when JCL for a program is first submitted. The file is called
PLIDEBUG.DAT and is used by the PL/I run time to determine whether to start the debugger for a given referenced user program. Use
PLIDEBUG.DAT to allow the PL/I run time to start the debugger automatically when a program runs.
You can edit this file from the Enterprise Developer IDE to define the program name and how to start and initialize CodeWatch.
When using
PLIDEBUG.DAT, there should only be one one record in the file which matches the name of your user program. Specific columns correspond to data required to run the debugger from
PLIDEBUG.DAT. For example:
--- 0---|--- 10---|--- 20---|--- 30---|--- 40---|--- 50---|--- 60---|--- 70---|--- 80---|--- 90---|
123456789|123456789|123456789|123456789|123456789|123456789|123456789|123456789|123456789|123456789|
TESTPGM1 N 0 SHLIB TESTPGM1.DLL;ENV TESTPGM;BR %ENTRY;BR %EXIT [DET;Q];C
This table outlines the values needed for each record in
PLIDEBUG.DAT.
| Column(s)
|
Value
|
Description
|
| 1 through 8
|
TESTPGM1
|
User program name (without file extension).
|
| 21
|
Y/N (Yes/No)
|
Indicates whether to start the debugger when the program executes.
|
| 23
|
0/1
|
The debugger flavor used to debug the entry. Values are:
- 0 = Code
- 1 = Use the CodeWatch GUI debugger
|
| 25-nn
|
<text string>
|
Initialization string for Codewatch. This is the initial set of commands for the debugger to execute before control is given over to the user.
|
For example:
TESTPGM1 N 0 SHLIB TESTPGM1.DLL;ENV TESTPGM;BR %ENTRY;BR %EXIT [DET;Q];C
TESTPGM2 N 1 SHLIB TESTPGM2.DLL;ENV TESTPGM;BR %ENTRY;BR %EXIT [DET;Q];C
Editing PLIDEBUG.DAT
To open the and edit the debug configuration file:
- After running your JCL job to create the
PLIDEBUG.DAT file, right-click the file in the Solution Explorer and choose
Open File in Data Tools. The Micro Focus Data Tools application starts.
Note: A message box may appear indicating that edits to the file are applied immediately. Select the
Do not show this message again check box to prevent this message from appearing. Then click
OK.
- Right-click in the record editor for
PLIDEBUG.DAT and choose
Insert Indexed Record. The Insert indexed record dialog box appears.
- Enter the value for the User program name without the file extension. This is the Unique key for the record. Click
OK. A line appears showing the Unique key appears in the record editor.
- On the line with the new record, click on column 21 and enter
Y or
N to indicate whether to start the debugger when the program executes.
- Click on column 23 and enter
0 or
1 to specify which debugger to use.
- Click on column 25 and enter the remaining values for the initialization text string. See the section
CodeWatch Commands for detailed information on commands you can use in the initialization text string.
Note:
The Data Tools status bar shows the cursor's current column location. Changes are saved immediately to the file.
When you begin to enter the remaining values for the record, a message box asks you to confirm that you want to edit the record. Click
OK. You can also turn the update warning off for the file in the message box.
