RE: VSCode debugging

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

 

Don Brown

Senior Consultant
 
[1]OneTeam IT Pty Ltd
P: 1300 088 400

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack
Woehr via MIDRANGE-L
Sent: Wednesday, 20 May 2026 11:40 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Jack Woehr <jack.woehr@xxxxxxxxxxx>
Subject: Re: VSCode debugging

Even better,
[2]https://codefori.github.io/docs/developing/debug/overview/#managing-service-entry-points

Jack Woehr
Independent Consulting Programmer

[icon] 303-847-8442<tel:303-847-8442>

[icon] jack.woehr@xxxxxxxxxxx<[3]mailto:jack.woehr@xxxxxxxxxxx>

[icon] [4]www.procern.com<https://www.procern.com>

[icon] Stay
Connected!<[5]https://www.linkedin.com/company/procern-technology-solutions/>

[photo]
Upgrade your IT state of
mind!<[6]https://procern.com/24-7-monitoring-itil-management/>

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.

[__tpx__]

________________________________

________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Don
Brown via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Tuesday, May 19, 2026 18:23
To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Don Brown <dbrown@xxxxxxxxxxxxxxxx>
Subject: VSCode debugging

In the past I would use RDi where I needed to set service entry points -
this allowed me to specify the user profile so I could control my debug
session - I don't think this is available in VSCode/IBM Debug V3.0.3 ? Am
I best continuing to use RDi for this type of debug session ?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [7]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[8]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
Message protected by MailGuard: e-mail anti-virus, anti-spam and content
filtering.
[9]https://www.mailguard.com.au

References

Visible links
1. https://www.oneteamit.com.au/
2. https://codefori.github.io/docs/developing/debug/overview/#managing-service-entry-points
3. mailto:jack.woehr@xxxxxxxxxxx>
4. file:///tmp/www.procern.com<https:/www.procern.com>
5. https://www.linkedin.com/company/procern-technology-solutions/>
6. https://procern.com/24-7-monitoring-itil-management/>
7. https://lists.midrange.com/mailman/listinfo/midrange-l
8. https://archive.midrange.com/midrange-l.
9. https://www.mailguard.com.au/