Before you can debug your application, you must complete
a small number of steps on the System z® machine.
About this task
These steps include:
Procedure
- Contact your system administrator to verify that Debug
Tool for z/OS has enough memory to run and debug your application.
Modifying the region size (for example, REGION=0M)
can help ensure that there is enough memory. Also, ensure that the
job class that your application is running can run in this region
size and that it allows for the elapsed time that the debug session
will take.
- If you are debugging a CICS transaction, memory size, transaction
enablement, and file access must be set by a CICS Administrator. If
Debug Tool has been installed and made available to your CICS region,
then these steps should already be addressed. Contact your CICS Administrator
if you require any changes to these. For more information, see the Adding
support for debugging under CICS chapter of the Debug Tool for
z/OS Customization Guide.
- Ensure that you have access to and read permission for
IBM Debug Tool for z/OS executable (SEQAMOD).
- Ensure that you have access to the source of the compiled
unit you are debugging. The source you need access to depends on the
programming language, the compiler options, and the version of the
compiler. The Preparing your program for debugging section
of the Debug Tool for z/OS User's Guide describes,
by programming language, the files you need to have access to.
- Ensure that you have the IP address or host name, including
port number, of the machine that will be running the debugger user
interface. You will need this information when you write the TEST run
time options that will start a debugging session. To obtain the IP
address of the client machine from the debugger user interface, go
to the Debug view and click the down arrow to the right of the daemon
icon and select Get Workstation IP from the
menu. The Get Workstation IP dialog box will open, indicating the
current IP address of the client machine. You can select the IP address
from this dialog box and copy and paste it into a JCL.
Note: If
the workstation has multiple LAN adapters, or if there is a router
or a Virtual Private Network (VPN) between the workstation and server,
this dialog may list more than one IP address. You may have to try
each IP address to find the address that the server can use.
- Ensure that the IP address you use in the TCPIP& parameter
of the TEST run time option matches the TCP/IP address
of the machine that runs the compiled language debugger. Also ensure
that the port number you use in the TCPIP& parameter
of the TEST run time option matches the port number
- or that it is contained by the range of debug daemon port numbers
- used by the debugger user interface. By default, the debugger daemon
listens on port 8001. To set the System
z debug IP address and port number, use the TCPIP& parameter
in the TEST run time option preferences_file parameter
position (in the form TCPIP&tcpip_workstation_id%port_id:).
You can set the user interface daemon port or range of ports in the
Change Daemon Port dialog box or in the debugger preferences.
- Ensure that you have completed the appropriate instructions
described in the Starting Debug Tool section of the Debug Tool for z/OS User's Guide. That section
provides instructions for starting programs that run in different
environments.
- If you are debugging assembler code, you will need to use
the LOADDEBUGDATA (LDD) command
for each compile unit that you want to debug (use the command to load EQALANGX).