Open topic with navigation

ibi™ Open Data Hub for Mainframe Connectors 1.0.8

# Problem: Request fails, and JVM not found messages written to edaprint.log

Problem: The request fails, and JVM not found messages are written to edaprint.log.

Cause: If the server cannot find the Java Virtual Machine (JVM), the JSCOM Listener will not be able to start, and messages will be written to the server log stating that the JVM cannot be found.

Solution: Specify the location of the JVM in JDK_HOME or JAVA_HOME. For more information, see JVM Requirements for Java Services (Server Installations Only).

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

ibi™ Open Data Hub for Mainframe Connectors

Copyright © 2021-2025. Cloud Software Group, Inc. All Rights Reserved.