|
2026 March Webinar - Debugging IBM i from VS Code - Seb Julliand
Wednesday, March 18, 2026, 12:00 PM - 1:00 PM PST
Category: Events
Wednesday, March 18, 2026 OCEAN Webinar

12 pm PT - 1 pm PT
REGISTER HERE for this Free Webinar!
Are you troubled when debugging from VS Code? Do you experience feelings of dread when starting the Debug Service? Have you or your coworkers actually been struggling to debug ILE from VS Code? If the answer is yes, then don't wait another minute. Just register for this webinar and get in touch with the professionals - Debuggerbusters !
Woops, wrong movie! But right topic!
It is time to learn how to properly debug ILE from VS Code - and believe it, it's not that hard once everything is set up correctly! So...who you gonna call? Seb Julliand! Seb has a long history (as in "love and hate relationship") of interfacing the IBM i Debug Service with Code for IBM i and knows quite a bit about it. From the architecture of the debugger to an actual live debugging session, Seb will take you on grand debugging tour: - Prerequisites - How it works - Configure and start the debug service from iNavigator - Common pitfalls - How to debug a program call - How to work with Service Entry Points - Variables, Breakpoints, Confitions, Watch
Join this session to finally be comfortable when it comes to debbugging from your favorite IDE. Ain't afraid of no questions!
Sébastien "Seb" Julliand is the R&D Tech Lead for i and me - IT Training and Solutions GmbH, an active contributors to several IBM i open-source projects and an IBM Champion since 2024. Seb loves to talk about anything related to software development or DevOps, on IBM i or not, it doesn't matter to me. RPGLE, Java, TypeScript, Jenkins, TOBi...he loves them all equally He's one of the main maintainer of the Code for i VS Code extension as well as the creator of the IBM i Pipeline Steps Jenkins plugin. When Seb is not busy coding, he gives education sessions about Code for IBM i, VS Code and open source in general.
REGISTER HERE for this Free Webinar!
Contact: Patrick Behr [email protected]
|