EQAVS1007E Error When attempting to run Debug from VS Code

[bigbearjeff63]

i get the infamous "EQAVS1007E' error when attempting to run the Dubugger from VS Code. I suspect this is a certificate related issue. Is there any way I can get it to prompt to set these up? I must have missed it in the initial installation, and I can't seem to get back there to run it again. I've tried uninstalling and reinstalling and have had no luck. Any help would be greatly appreciated as I have a whole team here who'd love to be able to take advantage of this extension.

[sebjulliand]

Hi @bigbearjeff63 , could you share the entire message just to make sure we don't set you in the wrong direction? EQAVS1007E means the connection to the Debug Service failed, but it could be for a couple of reasons.

[sebjulliand]

No, if you debug from the object browser or IFS browser, then the library list and current library defined here should be picked up.

The debug job is submitted in the QSYSNOMAX job queue, so you may be able to check what's going on in it (actual library list, job log, etc) once the debug has started and the first breakpoint is reached.

[bigbearjeff63]

okay thank you

[bigbearjeff63]

The error I'm getting is a CPF4203 and from what I can read on-line it indicates a debugger setting needs to be changed. It states "Either specify the INHWRT(*YES) parameter on the OVRDBF
command, or specify the UPDPROD(*YES) parameter on the CHGDBG command. Then
try your request again." Note: I am not using an OVRDBF command. How do I set the UPDPROD(*YES) value from Visual Studio?

[bigbearjeff63]

Ignore that! I found the setting. Thanks again for all of your help!
In a nutshell. I needed to start the Debug Service and the Debug Job from within Visual Studio by hovering over the system name I'm connected to and then clicking debugger. From there I hovered over Server and started it with the start icon to the right, and then I performed the same task for the Debug Service. After completing that, I was getting an error (CPF4203) as my application was updating production files. I once again hovered over my system name in the bottom task bar of the application and chose settings. From the settings screen there are Tabs across the top, and I chose the Debugger tab and then checked the Update Production Files check box. After that, everything worked great!

[sebjulliand]

You're very welcome 😄