Morris Guan

@zkarj735 If you use the launch template in launch.json, please add the following parameters into the launch entry and try again: "secure": true, "ignoreCertificateErrors": true,

@zkarj735 Yes, we do have a requirement that the source need to be present on the IBM i. This is currently a hard requirement and built into multiple levels of...

We have opened an internal enhancement for local source support. I think we can close this issue now. We just released a new debug client v2.0.2 and a new debug...

This is a generic error message, which does not provide too much useful information. Questions: 1. How do you start the debug service? Do you see any error when starting...

Please note that you need to specify the password when you create the IBM i connection. If the password is not specified, you can get this error message. Please verify...

@duieolson Please try to get the output of the debug service and attach it to this issue. Depending on how you start the debug service, the output may appear in...

Only QSECOFR users can write to the path /QIBM/ProdData/IBMiDebugService/bin. If your user profile does not have QSECOFR authority, the behavior might be expected. Code for i can be changed to...

Code for IBM i 2.9.0 contains a number of fixes for certificate generation. Please reopen the issue if you can still reproduce the problem in 2.9.0.

SEP debug with another user's profile will be supported in the next debug service and client update (probably around end of the year).

I just tested a driver with all the changes as of 03-26 (code-for-ibmi-2.8.5-dev.0.vsix). I found the following problems in the certificate generation area: 1. The certificate is still generated under...