Skip to end of metadata
Go to start of metadata

The JobScheduler requires an Oracle Java Runtime Environment (JRE) 32-Bit at least version 1.6.x.

For AIX you can use the IBM Java 32-Bit at least version 1.6.x, too.

You can install the 32Bit Java in parallel to a 64Bit version.

If you start the JobScheduler, it is looking for the Java Virtual Machine, which is normally in ...

  • ... %JAVA_HOME%\bin\client\jvm.dll for Windows.
  • ... ${JAVA_HOME}/lib/i386/client/ for Linux.

If the JVM is not found or is not from above Java environment then you get the error:

  terminate called after throwing an instance of 'zschimmer::Xc'
   what():  Z-JAVA-101  Java Virtual Machine is not started

In this case you must edit the JAVA_HOME variable for the JobScheduler in the ./bin/jobscheduler_environment_variables.(cmd|sh) file.

For Linux:

For example

 #</span> test -z "$JAVA_HOME" && JAVA_HOME="/usr/lib64/jvm/java"

If necessary, the LD_LIBRARY_PATH must be adjusted too in the ./bin/ file.

For Windows:

If necessary, add the location of the Java Virtual Machine to the JobScheduler configuration file .\config\sos.ini like this:

 vm = C:/Program Files (x86)/Java/jre/bin/client/jvm.dll 

For Red Hat:

Look into the ./config/logs/scheduler.log. If you find an identically line

 [ERROR Z-JAVA-100  Java Virtual Machine cannot be loaded [xxx/lib/i386/client/ cannot restore segment prot after reloc: Permission denied] []]

then you must edit the "Security-Enhanced Linux" settings (see

Write a comment…