Preparing to debug for an Eclipse client

Before you can debug your application, you must complete a small number of steps on the IBM Z® machine.

• Contact your system administrator to verify that z/OS® Debugger 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 z/OS Debugger 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 section of the IBM® z/OS Debugger Customization Guide.
• Ensure that you have access to and read permission for z/OS Debugger 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 IBM z/OS Debugger User's Guide describes, by programming language, the files you need to have access to.
  Note: If you are using the Debug Manager, you can skip the next step. The Debug Manager uses your Remote Systems z/OS connection to automatically determine your client IP address and port number.
• 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.
• If you are coding your TEST runtime option yourself, find examples in the TEST runtime option examples for remote debugging table and a complete syntax in Syntax of the TEST runtime option.
• For non-CICS applications, when Debug Profile Service is active, you can use TEST with no suboptions specified to enable delay debug mode. For more information, see Simple TEST option.
• Ensure that you have completed the appropriate instructions described in the Starting z/OS Debugger section of IBM z/OS Debugger User's Guide. That section provides instructions for starting programs that run in different environments.
• If you are debugging assembler code in Debug Tool compatibility mode, you will need to use the LOADDEBUGDATA (LDD) command for each compile unit that you want to debug (use the command to load EQALANGX).
• If you are running the compiled language debugger on Windows Server 2008, ensure that you either add a "New Rule" or enable Inbound Connections to allow the port (usually 8001) to communicate through the firewall.