PDA

View Full Version : Cannot get the Integrated Source Level Debugger (ISDB) to work for JAVA.



Guest.Visitor
01-01-1995, 02:00 AM
I read ?A Java Source Level Debugger for the AS/400? by Don Denoncourt In the ?AS/400 NetJava Expert? Technical Journal The machine is on V4R4. I did a recompile with the ?g option in the QSH shell. I know the class file was updated because the time stamp changed, but the file size did not! Problem? I also tried the ?debug option. No go. When I invoke the program I use the *DEBUG option. The programs runs like normal. No source debugger screen comes up. I tried two different programs. Both programs do screen text output. Does this matter? Any thoughts would be helpful.

Guest.Visitor
09-25-2000, 06:34 AM
Paul, I did not read that article, but did you strsrvjob on the job servicing your Java session? Also, did you use strdbg? I have not used strisdb in many years and am not aware of it working for Java programs. If you go to the Java section at IBM's Information Center web site, you can search for Debug. You will find several links to debugging. There are several sections, one is quite old and not very applicable. I posted those links to the Java debugging instructions in this forum a few weeks ago. David Morris

Guest.Visitor
09-25-2000, 06:48 AM
According to the original artical none of that is needed. When you invoke the program the STRSRVJOB happens automatically. That is why I am trying to get it to work. May I suggest you read it and see why I would like to figure out what I am doing wrong so. http://www.midrangecomputing.com/anje/article.cfm?id=293

Guest.Visitor
09-25-2000, 09:02 PM
Paul, Thanks for posting the link. After reading the article, I am confused by the term ISDB, I rember that debugger having different function keys. The steps in the article work fine on my system. I usually use Code/400's debugger which is nothing to brag about, but it seems to step more consistently, especially when you are debugging multiple classes. David Morris

Guest.Visitor
10-04-2000, 07:19 AM
Just in case someone reads this thread here is the final answer to my problem. The system I was on allowed *PUBLIC access to the STRSRVJOB command but it did not allow *PUBLIC access to the ENDSRVJOB command. The RUNJVA command with OPTION(*DEBUG) uses the commands automatically. Once I was give authority to the ENDSRVJOB command also, my problem was gone. I cannot beleive someone else would have the same problem but you never know!