Which SPSS log configuration levels expose Java-based component stack traces?

When an SPSS Statistics deployment fails, administrators typically rely on the installation logs to identify issues such as license manager timeouts or engine loading errors. While the /log and /debug flags provide granular detail regarding DLL load sequences and registry writes, there is a persistent gap in the visibility of Java-related modules.

Currently, the default log verbosity does not appear to capture detailed stack traces for components utilizing the Java Virtual Machine. This makes it difficult to determine if a deployment abort is triggered by a JVM-specific exception or a native code failure without manually configuring external environment variables.

Is there a specific environment variable or installer flag that forces the output to include full Java stack traces within the primary deployment log? Additionally, does setting the SPSS_JAVA_OPTS variable affect the output detail of the installer during a failure event?