SCAState command-line options
The following table describes the SCAState options.
| SCAState option | Description |
|---|---|
|
|
Displays all available information. |
|
|
Displays information that is useful to debug SCAState behavior. |
|
|
Prints a thread dump for every thread. |
|
|
Displays the help information for the SCAState tool. |
|
|
Specifies the file to which the heap dump is written. The file is interpreted relative to the remote scan’s working directory; this is not necessarily the same directory where you are running SCAState. |
-liveprogress |
Displays the ongoing status of a running scan. This is the default. If possible, this information is displayed in a separate terminal window. |
-nogui |
Causes the OpenText SAST state information to display in the current terminal window instead of in a separate window. |
|
|
Displays information about the source code being scanned, including how many source files and functions it contains. |
-pid <process_id> |
Specifies the currently running OpenText SAST process ID. Use this option if there are multiple OpenText SAST processes running simultaneously. To obtain the process ID on Windows systems:
To find the process ID on Linux systems:
|
|
|
Displays scan information up to the point at which the command is issued. This includes the elapsed time, the current phase of the analysis, and the number of results already obtained. |
|
|
Displays configuration settings (this does not include sensitive information such as passwords). |
|
|
Displays the OpenText SAST version number for the sourceanalyzer that is currently running. |
|
|
Prints a thread dump for the main scanning thread. |
|
|
Displays information from the timers and counters that are instrumented in OpenText SAST. |
|
|
Displays the SCAState version. |
|
|
Displays the following statistics that JVM standard MXBeans provides: ClassLoadingMXBean, CompilationMXBean, GarbageCollectorMXBeans, MemoryMXBean, OperatingSystemMXBean, RuntimeMXBean, and ThreadMXBean. |
|
<none> |
Displays scan progress information (this is the same as |
OpenText SAST writes Java process information to the location of the TMP system environment variable. On Windows systems, the TMP system environment variable location is C:\Users\<username>\AppData\Local\Temp. If you change this TMP system environment variable to point to a different location, SCAState cannot locate the sourceanalyzer Java process and does not return the expected results. To resolve this issue, change the TMP system environment variable to match the new TMP location. OpenText recommends that you run SCAState as an administrator on Windows.