The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
Le 14/10/2022 à 19:57, jeremy.ruth@xxxxxxxxxxx a écrit :
Thank you Marc for your help.
Yw, I often used this technique to check firewall issues.
I tried the SSH command from my workstation and it made a connection because I am seeing what you're seeing from netstat. An established entry from my workstation.
So the port is not blocked. Any other ideas?
I am not really used to use the debugger nor I have an access with
enough authority to an IBM i system to be able to help you more.
However, here is what happens on PUB400 when I start the debugger from
iACS SQL scripts like you do.
Job listening on 3825 port is QB5ROUTER in QUSRWRK subsystem.
Unfortunately I cannot see job log of this job.
Job handling the tcp session on port 3825 with my workstation is
QTESDBGSVR in QUSRWRK subsystem. It is submitted by QPGMR/QTESDBGHUB
which runs in QSYSWRK subsystem at the time I request to start debugger.
Unfornately I cannot see job log of this job.
Have you got those two QB5ROUTER and QTESDBGHUB jobs active? Maybe you
could check their job log? I can't do it on PUB400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.