302 Using IBM Application Development Tools for z/OS and OS/390
12.4 IBM Distributed Debugger/VisualAge Remote Debugger
In general terms, this section applies to the IBM Distributed Debugger and the VisualAge®
Remote Debugger. For convenience, we will refer to them both as the Remote Debugger.
The Remote Debugger is available with the following products:
VisualAge COBOL
VisualAge PL/I
C/C++ Productivity Tools
VisualAge C++
VisualAge TPF
Some versions of DB2
Any version of the remote debugger should work with z/OS Debug Tool and all of its
supported languages.
Using this interface, your host application running under control of the Debug Tool will start a
TCP/IP connection to a Windows NT® or 2000 workstation on which the Remote Debugger
program was started and listens for requests on a specified port (default 8000). This interface
is supported by all environments including CICS, IMS, and USS.
Remote Debugger is supported by:
COBOL for MVS and VM (and later)
C/C++ for MVS, C/C++ for OS/390 and C/C++ for z/OS
VisualAge PL/I, Enterprise PL/I for z/OS and OS/390
Debugging with the remote debugger is a two-step process:
1. Start the remote debugger on your workstation. For the IBM Distributed Debugger on our
workstation, this involves a command like:
C:\IBMDebug\bin\idebug.exe -qdaemon -quiport=8000
2. Run your program using the TEST runtime option. The runtime option to be used needs to
define your workstation’s TCP/IP address. For example, with a COBOL program this
might be:
/TEST(ALL,*,PROMPT,VADTCPIP&9.30.40.117%8000:*)
Note: In some TCP/IP installations, a SYSTCPD DD card may be needed to point to your
installation’s TCPIPDATA.
Get Using IBM Application Development Tools for z/OS and OS/390 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
