Replies: 2 comments
-
Just encountered this as well. When we migrated our change management to ARCAD a while back, we moved our source repository and debug no longer finds it based off the object description. Would love a way to override the source file location when EQARD1066E is received and point debug to the correct source location. A simple text input on the command palette would be enough for our developers to overcome this hurdle. Would be happy to create a feature request if one isn't out there already. |
Beta Was this translation helpful? Give feedback.
-
Moved to debug issues: codefori/vscode-ibmi-debug-issues#36 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We use MDCMS as our change management tool. We compile our RPGLE and SQLRPGLE programs with DBGVIEW(*SOURCE). The CM software compiles against the stage libraries on our master CM system before promoting to our targets (where it lands in the production libraries). When we try to do service entry point debug in the stage environment it gives us the error:
Could not load source '/QRPGSRC/': EQARD1066E The debug engine could not locate the source or listing file /QRPGSRC().
In RDi the developers get a prompt that allows them to redirect to the source in the production library on the stage LPAR and continue the debug.
We just get the hard error in IBM i Debug in vs code. Is there a work around for this that would allow us to debug in VS Code?
Beta Was this translation helpful? Give feedback.
All reactions