Other options

The following table describes other options.

Other option	Description
`@<file>`	Reads command-line options from the specified file. The plain text <file> contains options and parameters, each on a separate line. For example, instead of running the command `sourceanalyzer -b my_build_id -source 17 -cp lib.jar Test.java`, you can run the following command: `sourceanalyzer @optfile.txt` where the `optfile.txt` file contains: Copy `"-b" "my_build_id" "-source" "17" "-cp" "lib.jar" "Test.java"`
`-h` \| `-?` \| `-help`	Prints a summary of the command-line options.
`-debug`	Includes debug information in the OpenText SAST Support log file, which is only useful for Customer Support to help troubleshoot. Equivalent property name: `com.fortify.sca.Debug`
`-debug-verbose`	This is the same as the `-debug` option, but it includes more details, specifically for parse errors. Equivalent property name: `com.fortify.sca.DebugVerbose`
`-debug-mem`	Includes performance information in the OpenText SAST Support log. Equivalent property name: `com.fortify.sca.DebugTrackMem`
`-verbose`	Sends verbose status messages to the console and to the OpenText SAST Support log file. Equivalent property name: `com.fortify.sca.Verbose`
`-logfile <file>`	Specifies the log file that OpenText SAST creates. For default log file locations, see Locating the log files. Equivalent property name: `com.fortify.sca.LogFile`
`-clobber-log`	Directs OpenText SAST to overwrite the log file for each run of sourceanalyzer. Without this option, OpenText SAST appends information to the log file. Equivalent property name: `com.fortify.sca.ClobberLogFile`
`-quiet`	Disables the command-line progress information. Equivalent property name: `com.fortify.sca.Quiet`
`-version` \| `-v`	Displays the OpenText SAST version and versions of various independent modules included with OpenText SAST (all other functionality is contained in OpenText SAST).
`-autoheap`	Enables automatic allocation of memory based on the physical memory available on the system. This is the default memory allocation setting.
`-Xmx<size>M` \| `G`	Manually specifies the maximum amount of memory OpenText SAST uses. Note: OpenText recommends that you use the default memory allocation setting defined by `-autoheap` instead of manually specifying the maximum memory with this option. Heap sizes between 32 GB and 48 GB are not advised due to internal JVM implementations. Heap sizes in this range perform worse than at 32 GB. The JVM optimizes heap sizes smaller than 32 GB. If your scan requires more than 32 GB, then you need 64 GB or more. As a guideline, assuming no other memory intensive processes are running, do not allocate more than 2/3 of the available memory. When you specify this option, make sure that you do not allocate more memory than is physically available, because this degrades performance. As a guideline, and the assumption that no other memory intensive processes are running, do not allocate more than 2/3 of the available memory.