Glossary

This glossary defines technical terms and abbreviations used in the z/OS® Debugger documentation.

D

Debug Tool compatibility mode: A remote debug mode that uses the remote debug engine from the former Debug Tool for z/OS to perform all host debugging tasks. This mode supports all features that are available in Debug Tool for z/OS.; With the removal of standard mode in 16.0, Debug Tool compatibility mode is the only remote debug mode and is no longer explicitly called out to differentiate from standard mode.
debug profile: Data that specifies a set of application programs which are to be debugged together.
Debug Profile Service: A REST API to manage debug profiles that determine the applications or transactions to be debugged.
Debug Tool for z/OS: A product name that was used to refer to z/OS Debugger before version 14.0, when the IBM Integrated Debugger and IBM Debug Tool engines were consolidated into one unified technology.

E

Eclipse: A desktop integrated development environment that contains a base workspace and an extensible plug-in that users can customize based on development needs.

F

flow point

A named group of statements in a program. Execution of the program can flow into and out of a flow point many times, or possibly not at all. Flow points can be called differently in various languages, for example:

For COBOL programs, flow points can be sections, paragraphs, compile units, or user-defined functions.
For PL/I programs, flow points can be procedures.
For C/C++ programs, flow points can be functions or classes.
For Java programs, flow points can be classes or methods.

I

IBM® z/OS Debugger: The host component that provides advanced debugging of composite applications for all your z/OS environments.
IBM Developer for z/OS on VS Code: Provides application developers with a set of capabilities to edit, build, and debug their z/OS programs by using a desktop IDE through a set of VS Code extensions.
IMS Translation Isolation Facility: A component that allows debugging an IMS transaction in a private region so that the debug session does not interfere with the rest of transaction processing in the system.

P

parked debug session: A parked debug session is initiated in the Remote Debug Service on the z/OS host, but waiting for a user to begin an interactive debugging process.

R

Remote Debug Service: Acts as a proxy between the Debug Engine and Debug Adapter Protocol (DAP) clients to enable interactive debugging capabilities within the DAP clients.

S

standard mode: A remote debug mode that uses the Program Information and Control Library (PICL) engine technology. Starting from 16.0, standard mode has been removed and Debug Tool compatibility mode has become the only remote debug mode.