Qshell environment variables

WebSphere Application Server - Express provides these Qshell environment variables that affect the scripts:

To set these variables, run this command:

  export variableName=value

To unset these variables, run this command:

  unset variableName

• WAS_ADDL_JVM_ARGS
  If you set this variable, its value is appended to the Java virtual machine (JVM) arguments for all of the scripts that run a JVM. (All of the scripts except crtwasinst, dltwasinst, updwashost, enbprfwas, startServer, and lstwasinst run a JVM.) For example, this command:

  export WAS_ADDL_JVM_ARGS="-Dtrace=com.ibm.*=all=enabled -Xms256m"

  enables tracing for the JVM that a script starts, and sets the minimum heap size for the JVM to 256 megabytes.

• WAS_OS400_INSTANCE
  The value of this variable replaces the default instance name for all scripts that have an optional -instance parameter. For example, if you frequently run scripts on the instance named myInstance (for example, startServer -instance myInstance), you might want to run this command:

  export WAS_OS400_INSTANCE=myInstance

  After you run this command, you do not need to specify instance myInstance when you run scripts for which the -instance parameter is optional. The instance that a script uses is determined by this priority:

  1. The value of the -instance parameter
  2. The value of the WAS_OS400_INSTANCE variable

• WAS_USER_SCRIPT
  This variable specifies the path to a script that runs before a WebSphere Application Server - Express Qshell script runs. For example, if you want to append a /home/QSYS/classes.jar to the classpath for every script, you might create a script called /home/myDir/classpath.script. The script file contains this command:

  WAS_CLASSPATH=${WAS_CLASSPATH}:/home/QSYS/classes.jar

  After you create the script file, run this command to set the environment variable:

  export WAS_USER_SCRIPT=/home/myDir/classpath.script