Re: VSCode debugging

Justin Taylor <[email protected]>
Newsgroups gmane.comp.hardware.ibm.midrange
Message-ID <CAJu8Sp961pnL-kFa=cscm-C8PPGKVKf4zX8vcGCCLpDjMqJ31Q@mail.gmail.com>
It used to be a limitation in code4i debugging that the source and object
had to be in the same library.  That was a couple years ago.  My current
shop keeps source and objects together, so I haven't kept up with any
changes to that.



On Tue, May 19, 2026 at 10:42 PM Don Brown via MIDRANGE-L <
[email protected]> wrote:

>    Thank you Jack
>
>    Yes, I did find both of those links and did review previously however, I
>    am not seeing the same results when I try to start a debug.
>
>    We have a source library and a different object library.
>
>    I can right click the program object and select Start debug - Debug as
>    batch and that prompts me to run the command to call the program, but
> this
>    does not display the source and seems to do nothing when I press Enter.
>
>    If I right click on the source, there is no debug option.
>
>    I do have both the source library and object libraries in the library
>    list.
>
>    Maybe I am just missing something ?
>
>    Thanks
>    Don
>
>
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact [email protected] for any subscription related questions.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.