In part one of this blog, I wrote about some of the commonalities between IDz on Eclipse and IDz on VS Code, specifically around navigation and code editing functionality. In part-two, I’d like to look at code analysis and tools integrations. If you haven’t seen part one yet, here’s a link to that. Please feel free to read it and come back, it gives some context as to the aim of this series and the contents within. With that being said, let’s dive back in to some more commonalities between IDz on Eclipse and IDz on VS Code.

Code Analysis

Find Functionality

Being able to find what you’re looking for in code can be challenging, to put it lightly. Whether tabbing through a 1000 line program or launching a search through a megalithic 20,000+ line program, being able to find a variable or paragraph name (or keyword, or file name, etc) is a deal-breaker in terms of the quality of the development experience. Find functionality within code is easily accessible on both platforms. Additionally, you can search through multiple area of the workbench, including overall workspace, with both IDEs.

Data Elements View

IDz Eclipse contains a function/view called the Data Elements Table, which collates and displays information around data elements found in code graphically, making it very easy to consume the information. This function was released very recently (July of 2025) for IDz on VS Code, and is a fantastic addition to the workbench

Declaration Navigation

This is a function-set that is exclusive to graphical editing, and rather new at that (gaining popularity within the past 10 years or so). It all started with the “hover'“ feature, wherein leaving the cursor hovering over a data element or program structure will populate a small popup with important information. ​Both facilities include a “hover” feature, and they both include right-click/context menu options for navigating to declarations. This gives the developer the ability to get a quick view of a declaration, and upon ascertaining the information provided, the ability to navigate to where the declaration lives, wherever that may be within the code base*.

*- some setup required, specifically copybook library paths and called program libary specification.

Occurences in Compilation Unit

In IDz on Eclipse, the Occurrences in Compilation unit feature shows all occurrences of a data element inside of the main source code program, as well as any include files. In VS Code, this is done through a references option. No matter which path your choose, this feature is available and mightily useful.

Integrations

Interactive Debug

IDz on Eclipse and on VS Code give the developer access to debugging features. This commonality is, of course, dependant on access to debugging products. In IDz on Eclipse, there is a built-in perspective and related views that integrate with IBM’s Debugger, installed on a z/OS LPAR (provided you have access to the IBM Debugger). In VS Code, there is an extension called IBM Z Open Debug that will allow you to interface with IBM’s Debugger. In my case, I have access to IBM Debug for z/OS, and I can access and use the graphical debugging features in Eclipse or VS Code. Your mileage may vary depending on the debug product you use, but the bones are there, so to speak.

DBB User Build

IBM’s Dependency Based Build DBB is a modern build solution for mainframe applications that optimizes and automates dependency tracking and incremental builds, enhancing DevOps efficiency for z/OS® development. It shines in its ability to enable user builds and integrate with multiple platforms without locking you in to one or the other. User Build Actions are included in IDzEE on Eclipse and on VS Code, for both groovy and zBuilder build framework implementations.

TSO Commands and CLISTS

This feature set carries similar sentiment to the Remote Connection Emulator feature set above, it is important to be able to provide access to run TSO commands and CLISTS. IDz on Eclipse gives developers the ability to use a TSO Shell to execute some TSO and CLIST commands. This functionality is achieved in IDz on VS Code using a terminal with the Zowe CLI.

Wow, that’s a lot of common feature/functions, yeah? The above list is not comprehensive, there are many more commonalities between the two platforms. That being said, I didn’t want to write a literal book in this installment in the blog series, so if you’d like to learn more, I would recommend you try both platforms via the IBM Z Trial experience. Here’s the link for IDz on Eclipse, and here’s the link for IDz on VS Code. Enjoy them, they’re a lot of fun.

In the next installment, I’d like to go over some of the differences between IDz on Eclipse and on VS Code. Because differences are what makes life interesting, right? And while the goal may be to bring these platforms closer to parity, there is a certain element of “use the right tool for the job” that plays in to which platform you will choose at the end of the day.