QB5SERVER job - MCH3601 unmonitored by QB5IDEAL

[heymchri]

We're running into an intermittent issue on one of our partitions, that we can't figure out why it would happen. We don't have any specific steps to reproduce the issue, but it occurs daily.
Parition is at V7R4, IBM i Debugger is at 3.0.1.

Here's what happens:

• start off with stopped Debug Server and Service jobs

• start both jobs

• set SEP on a pgm

• get SEP to be hit (green screen code)

• debug session works fine

• session completes, both debug server and debug service jobs are kept active

• sometime later, try to do the exact same thing but running into the issue:

• source debug view kicks in, action bar for stepping into/over/etc. shows, but program just blows through, without hitting any breakpoint. Any action results in 'EQARD1056E Request continue is not allowed while thread 1 status is NOT_SUSPENDED.'

• On the server, side, we see the QB5SERVER job showing MCH3601 unmonitored by QB5IDEAL at statement 0000000003, in struction X'0000'. Function check. CEE9901 unmonitored by QTEVBPCH at statement *N, instruction X'000C'.

This also sometimes seems to result in the program source not loading when trying to edit it - VS Code just keeps spinning but never loads the source member. Server side does not show any member locks on that source member.

I realize this is all very circumstantial - but we can't figure out exactly what it is that makes this happen.

[mkwan01]

@heymchri The problem is likely to be in RDi debug server, which is used by both RDi and the debug service. Please provide the debug service log under the following path first:
/QIBM/UserData/IBMiDebugService/startDebugService_workspace/startDebugServiceNavigator.log

[mkwan01]

Then use the following instructions to capture the trace files for RDi debug server:

1. End the debug server if it is running:

ENDDBGSVR

2. Add an environment variable to capture debug server trace:

ADDENVVAR ENVVAR('QB5TRC') value('ALL') LEVEL(*SYS)

3. Start the debug server

STRDBGSVR

4. Recreate the original debug problem from the VSCode debugger
5. Locate the trace files under your user id's IFS home directory (e.g. /home/myid). We have the following trace files:
   -- ROUTER_trace.txt: logs for debug router activities
   -- SEP_userid_trace.txt: logs for SEP activities
   -- DBG_%job_name%_trace.txt: logs for debug activities (one file for each debug session)
6. Send all trace files to us.

[mkwan01]

You can remove the environment variable after capturing the traces:
RMVENVVAR ENVVAR('QB5TRC') LEVEL(*SYS)