IBM IMS Explorer for VS Code

Known issues and limitations

The IBM IMS Explorer for VS Code extension has some known issues and limitations. This page provides the status of the current release. Also review the list of open issues and enhancement requests in our Github repositoryopen in new window. It might list issues that are not yet documented here.

Java™ 21 64-Bit JRE or SDK required

If the right version of Java cannot be found in the current user's path or if no JAVA_HOME environment variable was defined, you might see error messages in the Output view of VS Code. Such errors could also be caused by other reasons such as not enough free memory for Java on your system.

The IMS Explorer for VS Code extension starts by searching for Java in the following locations, in the order specified:

  1. ims.explorer.connection.property.javaHome
  2. java.jdt.ls.java.home
  3. JAVA_HOME environment variable
  4. System PATH
  5. Platform-specific discovery (e.g., /usr/libexec/java_home -V on macOS, where java.exe on Windows)

If your installation is not found and you see a IMS Explorer failed to start error reporting Java cannot be found, try specifying a path to your Java for your ims.explorer.connection.property.javaHome or java.jdt.ls.java.home value in your VS Code settings, or setting your system's JAVA_HOME environment variable. To configure the ims.explorer.connection.property.javaHome path for a supported Java installation, see Configuring the extension.

Reporting issues

If you want to provide feedback or report an issue, open an issue in the GitHub repositoryopen in new window. Any report and feedback is appreciated.