Appendix E. Notes on debugging in remote debug mode
Debug Tool can run in remote debug mode, by using TCP/IP to connect to
a remote debugger installed on your workstation. The following remote
debuggers can be used:
- Compiled Language Debugger component of Rational Developer for System z
- Compiled Language Debugger component of WebSphere Developer for zSeries
- Compiled Language Debugger component of WebSphere Developer for System z
- WebSphere Developer Debugger for zSeries
- WebSphere Developer Debugger for System z
When you specify the TCPIP& or VADTCPIP& suboption,
if the default port number has been changed, you must specify the
port number that the remote debugger is using to listen for a debug
session. The remote debuggers use port 8001 as the default port number.
When you use remote debug mode, consider the following possible errors:
- The tcpip_workstation_id or port_id parameters
must be syntactically and functionally correct. If they are not and
you try to start a remote debug mode session, Debug Tool starts a full-screen
mode session. For example, if you try to start a remote debug mode session
from TSO or a CICS® program by using incorrect parameters, a full-screen
mode session is displayed on your 3270 type terminal. This error is
recorded in the MVS SDSF log as an allocation failure.
- If the tcpip_workstation_id or port_id parameters
are not syntactically and functionally correct and you try to debug
batch program, Debug Tool terminates and the batch program runs as though
no debug session was started. This error occurs when, for example,
you run a JES batch job or CICS batch transaction. This error
is recorded in the MVS SDSF log as an allocation failure.
- If your z/OS® environment is not using the default TCP/IP
data set named TCPIP.TCPIP.DATA and you try to start a remote debug mode
session to debug a batch program, Debug Tool terminates. The batch program
runs as though no debug session was started. This error is recorded
in the MVS SDSF log as an allocation error.
To fix this error, specify
the SYSTCPD DDNAME with the appropriate TCP/IP data set name. For
example,
//SYSTCPD DD DISP=SHR,DSN=MY.TCPIP.DATA
- For TCP/IP sessions, the remote debug daemon must be started at the
workstation before you start Debug Tool. Refer to the remote debugger
information for help on using the remote debug daemon.
Tip on monitoring variables in optimized COBOL program
After you start the remote debugger and start your optimized COBOL
program, do the following steps:
- Step into your program by using the Step Into button.
- Monitor a variable. The variable's name and current value are
displayed in the Monitor window.
- Step through your program until you reach a statement that alters
the value of the variable you are monitoring. If you attempt to run
the statement, a Debugger Message window displays the following message:
Error occurred: EQA2421E The assignment was not performed because
the assigned value might not be used by the program,
due to optimization.
- Enter the SET WARNING OFF command in the input line
of the Command Log window. The Command Log window displays a message
that the SET WARNING OFF command was received.
- Step through the statement. A Debugger Message window displays
the following message:
Error occurred: EQA2420W The assignment was performed but the assigned value
might not be used by the program, due to optimization.
The new
value of the variable you are monitoring is displayed in the Monitors
window.
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)