iSeries System Debug Manager – Communication error

85 pts.
Tags:
5250 session
iSeries error messages
iSeries System Debug Manager
iSeries System management
I have just installed the iSeries System Debug Manager. Everything seems to be ok, but I get Communication error when I try to start a debug session on both Systems I am linked to. I have two 5250 interactive sessions open too, of course, via Client Access emulation. Do I need to check any subsystem? Thank you

Answer Wiki

Thanks. We'll let you know when a new response is added.

I found out which subsystem must be running when starting Debug Manager: the Debug Server (of course!). Thanks to an article by Scott Klement who first led me into the subject.
I must check if it is running a job named QTESDBGHUB under QSYSWRK and, in case, simply start it typing STRTCPSVR SERVER(*DBG) on the command line.
Nevertheless, having done everything right (I suppose) I got immediate connection
on the first of the two iSeries I have to mantain (V5R4):
<01/07/10 9.54> Attempting connection to ’192.168.100.30′ (192.168.100.30).
<01/07/10 9.54> Connected successfully to ’192.168.100.30′ (192.168.100.30).
while the second one (V5R2) gets stuck waiting for… boh? I really don’t know:
<01/07/10 9.54> Attempting connection to ’192.168.101.200′ (192.168.101.200)…..

Does anybody have a clue?
Thank you

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Paolo51
    [...] iSeries System Debug Manager - Communication Error [...]
    0 pointsBadges:
    report
  • TomLiotta
    The System i5 Debugger can be run from a PC in two general ways. First, Scott Klement has described his process in a Club Tech iSeries Programming Tips Newsletter item, among other places. His method is as simple and direct as any that I've seen. But second, iSeries Navigator can also be used to start the Debugger. This has an advantage in how it may help with communications or connections problems. If you can make the connection through the iNav method while failing through the direct method, you may learn clues about where the problem lies. From iNav, navigate to the system, then into Databases-> {databasename}. Right-click the {databasename} and select Run SQL Scripts... When the SQL Scripts app starts, select Run-> Debugger from the menu bar. When the Debugger starts, select the debug method. I would choose "Submit and debug program in batch job" and select some trivial test program. The result should give the clues. Tom
    125,585 pointsBadges:
    report
  • Paolo51
    Thank you for your hint, Tom. I had already found something similar in the article you mentioned by Scott Klement. Unfortunately, my iNav (V4 R5) doesn't show the option "Debug" when I click on "Run" in the menu bar of the "Run SQL Scripts" window. Should I get a new release? Moreover, if I try to start debug in the system where I got the connection by clicking on the red bug icon, I get nothing else but this awkward set of messages on the associated java console: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.ibm.iseries.debug.dialog.ISeriesJobNum.isValid(ISeriesJobNum.java :66) at java.awt.Component.invalidateIfValid(Unknown Source) at java.awt.Component.setLocale(Unknown Source) at javax.swing.JComponent.<init>(Unknown Source) at javax.swing.text.JTextComponent.<init>(Unknown Source) at javax.swing.JTextField.<init>(Unknown Source) at javax.swing.JTextField.<init>(Unknown Source) at com.ibm.iseries.debug.dialog.ISeriesJobNum.<init>(ISeriesJobNum.java: 56) at com.ibm.iseries.debug.dialog.StartDebugDialog.createJobPanel(StartDeb ugDialog.java:805) at com.ibm.iseries.debug.dialog.StartDebugDialog.addComponents(StartDebu gDialog.java:348) at com.ibm.iseries.debug.dialog.StartDebugDialog.<init>(StartDebugDialog .java:225) at com.ibm.iseries.debugmanager.action.DebugManagerStartDebugAction.run( DebugManagerStartDebugAction.java:102) at com.ibm.iseries.debug.util.Action.actionPerformed(Action.java:383) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour ce) at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Pretty nice. Isn't it? The only way to start an interactive debugging session seems to be by issuing the STRDBG command from a 5250 command line. This makes i5 Debug Manager to pop up with all the programs I was debugging in the previous session. Well, better than nothing... I'm still wondering why all this works on the i5 under V5R4 while it goes in an endless status of waiting connection in the other i5 which runs V5R2. Anyway, thanks a lot for your help. Paolo
    85 pointsBadges:
    report
  • TomLiotta
    why all this works on the i5 under V5R4 while it goes in an endless status of waiting connection in the other i5 which runs V5R2. Well, the System i5 Debugger wasn't even generally released until V5R2 (though enabled for V5R1 via PTF.) I don't have a V5R2 system available for testing, so I can only guess that general incompatibilities may exist in communications between releases of Windows, OS/400, the Java ToolKit, etc. All of them have changed from V5R1 to V5R4. my iNav (V4 R5) doesn’t show the option “Debug” ... Should I get a new release? V4R5? I'm a little surprised it even can be very effective if you have V5R4 in your mix of systems -- but only a little surprised. In any case, where did you get the jt400.jar and tes.jar files for your debugger use? You should consider getting newer versions for some testing. It's possible that some problems will disappear. I wouldn't lose track of any that you have, but you should try swapping them out for the debugger. Tom
    125,585 pointsBadges:
    report
  • Paolo51
    Yes, it sounds a little strange to me too. iNav V4R5 seems to be a little out of date, compared to V5R2 (not to mention V5R4), in case "version" and "release" refers to i5 OS. I never took it too seriously before. This is what the IT guys in the shop normally use, so why bother them? Well, this could lead me to ask some upgrading, if not too expensive. I took and copied into a local directory the two .jar files from the directory /QIBM/ProdData/HTTP/Public/jt400/lib of IFS of the i5 witch the debug manager connects with (V5R4). I have copied in another directory the version of them from the i5 V5R2 and tried to start the debug manager. Nothing has changed: immediate connection with the V5R4 system, no response from the V5R2 one. Don't know what to do... Thank you
    85 pointsBadges:
    report
  • TomLiotta
    Well, this could lead me to ask some upgrading, if not too expensive. There shouldn't be any expense as long as the AS/400s are legally licensed. The iNav components that you want don't require licensing for the workstation. As I said, I don't have V5R2 anywhere, so I can't look back at the 'Run SQL scripts' function to see if the debugger is available that far back. If you can access it to install, I'd make it my first choice. Then I'd go for the V5R4 release if I needed to. The biggest issue will be ensuring that you can get the latest service packs for whatever release you are working with. You should grab the V5R2 and V5R4 service packs ASAP in case IBM removes them. The iNav debug versions, particularly for V5R2, might give you the best chance at finding where the snag is. Not because the Java is different, but because reporting might be better. There might be logging functions that are more useful. Have you looked at communications traces from the V5R2 system to see if any contact is detected from your PC address? Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following