简体   繁体   中英

IBM System i - Debug Server for RDi debugging doesn't work

I recently read an article about debugging ILE programm within the RDi IDE. So according to several YT videos and articles on varios blogs I just have to create a object filter and a member filter for my rpg(le) source and the compiled program.

Then I have to use the context menu of the *PGM object and either start with an service entry point (SEP) or just debug the programm als "Batch".

RDi tells me there is no Debug Server started, so I opened a 5250 session, logged in and entered the command "STRDBGSVR". But still the debug server is not running according to RDi.

Does anyone know how to solve this?

Edit:

Versions:

Windows 10 x64

RDI 9.6.0.3

V7R2

I already installed the necessary PTFs but the debug server is not starting. (IDE gets frozen and "un-freezes" after ~ 10 Minutes, but server is not started)

  • I changed the port for the debugger from 8001 to 3001, same result.

  • I started RDI as administrator, same result

  • I also configured the winows firewall and allowed all programs related to "ibm", "eclipse" and "rdi" to pass the firewall for a domain network.

For RDi I installed the CL/Cobol/RPG toolset and skipped the Websphere part. Like some tutorials say I have to open the "server" view and create a new server. But this does not work, since I haven't installed the WebSphere toolset. Maby this is the reason.

There are two different ways to debug programs using RDi. The old way using STRRSESVR , also called Batch , and the new way using SEP . I prefer SEP .

To use SEP you can open your source in RDi by whatever means you desire. If the source already exists, and you know what it is, just use Ctrl-Shift-A and open the source file. Place your cursor somewhere in the source, preferably an executable statement, and open the right click menu. The bottom entry of the right click menu should be Set Service Entry Point... . Verify the info for your service entry point, and click OK .

If the SEP debug server isn't running, you will get a dialog to start the debug server. Click Yes . The SEP is now set up. I am using RDi 9.6. There was a time where you had to set up the debug server separately, and then you could use the right click menu. If you are on one of those old versions of RDi you should upgrade, RDi is a lot better now. But, in the mean time you can right click on any of the remote connection subsystems like Objects in RSE. Then from the menu navigate to Remote Servers => Debug => Start . Now you can try to set a Service Entry Point again.

From here you can run the program however you need to on your 5250 terminal, or by any other means necessary. This works for all jobs, including server jobs, SQL triggers, batch jobs, interactive jobs, even CGI jobs.

Make sure you change the user the SEP is running under to the user profile that the application is running under.

One important thing to remember is this feature may not work depending on the operating system version of your IBM machine. I know that on 5.4, we cannot debug through RDi, and have to do it through green screen. This is most likely responsible for the missing PTF error.

To set an entry point and debug server jobs interactively in green screen follow the process described here: https://www.itjungle.com/2012/10/03/fhg100312-story01/

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM