Other Options

The following table describes other options.

Other Option	Description
`@<file>`	Reads command-line options from the specified file. Note: By default, this file uses the JVM system encoding. You can change the encoding by using the `com.fortify.sca.CmdlineOptionsFileEncoding` property specified in the `fortify-sca.properties` file. For more information about this property, see Translation and Analysis Phase Properties.
`-h` \| `-?` \| `-help`	Prints a summary of command-line options.
`-debug`	Includes debug information in the Fortify Support log file, which is only useful for Micro Focus Fortify 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`
`-verbose`	Sends verbose status messages to the console and to the Fortify Support log file. Equivalent Property Name: `com.fortify.sca.Verbose`
`-logfile <file>`	Specifies the log file that Fortify Static Code Analyzer creates. Equivalent Property Name: `com.fortify.sca.LogFile`
`-clobber-log`	Directs Fortify Static Code Analyzer to overwrite the log file for each run of sourceanalyzer. Without this option, Fortify Static Code Analyzer 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 Fortify Static Code Analyzer version and versions of various independent modules included with Fortify Static Code Analyzer (all other functionality is contained in Fortify Static Code Analyzer).
`-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`	Specifies the maximum amount of memory Fortify Static Code Analyzer uses. 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. Note: Specifying this option overrides the default memory allocation obtained with the `-autoheap` option.