Web Client installation error FSUM6807 expression syntax error
book
Article ID: 131629
calendar_today
Updated On:
Products
Vantage Storage Resource Manager
Issue/Introduction
The Web Client Installation fails with error: # ./WebClientSetup.sh test: ./WebClientSetup.sh 116: FSUM6807 expression syntax error java version is not supported. Java version should be greater than or equal to 1.8 Exiting from CA Vantage SRM Web Client Installer although JAVA _VERSION="1.8.0_171" is installed.
Environment
Vantage r14.0, Web Client 14.0.5
Cause
The error message is misleading. The Installation script WebClientSetup.sh issues a "java -version" command to check the java version, but if any error is returned by the command, the check fails and the error message is issued in any case: FSUM6807 expression syntax error java version is not supported. Java version should be greater than or equal to 1.8 Exiting from CA Vantage SRM Web Client Installer
Here the corresponding code from the WebClientSetup.sh: ... javaexe="$javahome"/bin/java export JAVA_HOME="$javahome" export PATH=$JAVA_HOME/bin:$PATH $JAVA_HOME/bin/java -version 2>java.ver JAVA_VERSION=cat java.ver| grep "IBM" | awk '{print $7}' JAVA_MAJOR_VER=echo $JAVA_VERSION|awk -F"." '{print $1}' JAVA_MINOR_VER=echo $JAVA_VERSION|awk -F"." '{print $2}' #echo "java minor = $JAVA_MINOR_VER major = $JAVA_MAJOR_VER" if test $JAVA_MAJOR_VER -ge 1 -a $JAVA_MINOR_VER -ge 8 then rm java.ver LicenseAgree CallInstaller else echo "java version is not supported." echo "Java version should be greater than or equal to 1.8" ExitInstallMsg fi ...
Resolution
If the installation fails with above message, there should still exist the file java.verwhich contains the result from the java -version command issued in the WebClientSetup.sh
In this specific case, the file java.vercontained message - JVMJ9VM015W Initialization error for library j9gc29(2): Failed to instantiate compressed references metadata; 200M requested and the problem was caused by the MAXSIZE of the TSO segment of the userid being 200MB and using 2GB (2096218) as MAXSIZE solved the problem.