Debugging ISPF applications
You can debug ISPF applications in one of the following ways:
- Starting a separate terminal using full-screen mode using a dedicated terminal without the Debug
Tool Terminal Interface Manager. When you run your program, specify
the MFI suboption of the TEST runtime option.
The MFI suboption requires that you specify the VTAM® LU name of the separate terminal
that you started, as in the following example:
TEST(,,,MFI%TRMLU001)
- Starting a separate terminal using full-screen mode using a dedicated terminal with the Debug Tool
Terminal Interface Manager. When you run your program, specify the VTAM suboption
of the TEST runtime option. The VTAM suboption
requires that you specify your user ID, as in the following example:
TEST(,,,VTAM%USERABCD)
- Using remote debug mode.
- Using the same emulator session. PA2 refreshes the ISPF application
panel and removes residual Debug Tool output from the emulator session.
However, if Debug Tool sends output to the emulator session between
displays of the ISPF application panels, you need to press PA2 after
each ISPF panel display.
The rest of this section assumes that you are debugging ISPF applications
using the same emulator session.
When you debug ISPF applications or applications that use line
mode input and output, issue the SET REFRESH ON command.
This command is executed and is displayed in the log output area of
the Command/Log window.
Refer to the following topics for more information
related to the material discussed in this topic.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)