Starting IBM i native debugger STRDBG is slow

When entering the STRDBG command, the green screen debugger communicates with the graphical debugger when the QTESDBGHUB job is running to determine if the user issuing the STRDBG command is registered for graphical debugging. If the user is registered, a graphical debugger session is launched on the client system; otherwise, the green screen debugger proceeds to be launched. 

If STRDBG is taking too long to start and QTESDBGHUB is running, try changing the default value of these two environment variables:

 QTES_HUB_ACK_TIMEOUT = 0. Defaults to 15 seconds. The time STRDBG waits for a response from QTESDBGHUB after placing information in a data queue.

QTES_HUB_PORT_TIMEOUT = 0. Defaults to 30 seconds. The time STRDBG waits for confirmation from QTESDBGHUB that a graphical debugging session has been started when the user is registered for graphical debugging.

 Note: This will disable the automatic launching of graphical debugging session from the green screen. Graphical debug sessions are still operational and may continue to be used if started from the graphical debugger.

 Another alternative is to end the debug server if not in use with “ENDTCPSVR *DBG”.