Morris Guan
Morris Guan
Can you attach the output of the debug service here? The debug service output either appears at the debug service green screen console, or a QPRINT file for a JVM...
There is a FAQ on this in the Merlin debug doc link (https://www.ibm.com/docs/en/merlin/1.0?topic=environment-debugging): Question: How can I see the output of the debug service? Answer: You can see the output...
If you use RDi, the QPRINT file will appear under the Spool Files filter.
Are you calling the commands without source from the CL? If you have RDi, you can try to debug the same program as batch on RDi. If RDi also sends...
When we run through a program without source, the expected behaviour is that the debugger does not stop and the "source not found" message should not appear. I will try...
I am not able to reproduce the problem. I created two CL programs, with CL1 calling CL2, and removed the source for CL2. When I debug CL1 and step over...
I tried on vscode 1.76.2. No message comes up when I step over or run through a call to a CL program without source.
Sanjula points to an issue in line 485 of vscode-ibmi/src/api/debug/index.ts: "startBatchJobCommand": `SBMJOB CMD(${currentCommand}) INLLIBL(${options.libraries.libraryList.join(` `)}) CURLIB(${options.libraries.currentLibrary}) JOBQ(QSYSNOMAX) MSGQ(*USRPRF) CPYENVVAR(*YES)`, The problem Sanjula observed is likely to be triggered by the...
@edmundreinhardt The CURLIB parameter is not used at the debug level. The RDi debug code path does not set this parameter in SBMJOB when starting a debug session. As Sanjula...
@sebjulliand I am OK to have these parameters in the SBMJOB command, as far as the issue found by Sanjula would be addressed.