In this topic:
Understanding the lmstat output Example lmstat output Check license usage by feature Build license features Continuous Integration license features User license features

Finding out how many licenses are in use

To find out how many licenses are in use, use the FlexNet Publisher utility lmstat. lmstat is installed with the Server package.

From <server_install>/3rdparty/bin, run:

lmstat -a -c <license_server_port>@<license_server_host> -f <feature_name>

Understanding the lmstat output

You need to pay attention to two keywords:

The server keyword shows total build license consumption.
The client keyword shows total user license consumption.

Note: The label used for the license type may differ in your license file. The examples here use "server" and "client". Your license file may use other labels, such as "fixserver", "fixclient" and "client".

Example lmstat output

Here's an example snippet from the lmstat output, showing total build and user license consumption:

Users of kwadmin2017:  (Total of 5 licenses issued;  Total of 4 licenses in use)

"kwadmin2017" v12.0, vendor: klocwork
individual license

tyoung host01 /dev/tty (v12.0) (flex1.klocwork.com/27000 57756), start Mon 3/21 9:06 (linger: 1209600)
jfall host02 /dev/tty (v12.0) (flex1.klocwork.com/27000 17731), start Fri 3/18 12:54 (linger: 1209600)
jfall host03 /dev/pts/1 (v12.0) (flex1.klocwork.com/27000 29438), start Thu 3/24 9:33 (linger: 1209600)
jfall host04 /dev/tty (v12.0) (flex1.klocwork.com/27000 12791), start Thu 3/24 13:39 (linger: 1209600)

Users of client:  (Total of 10 licenses issued;  Total of 5 licenses in use)

"client" v12.0, vendor: klocwork
individual license

ajones ajones01 ajones01 (v12.0) (flex1.klocwork.com/27000 55789), start Fri 3/18 16:08 (linger: 604800)
ayeats ayeats01 ayeats01 (v12.0) (flex1.klocwork.com/27000 10557), start Thu 3/24 15:57 (linger: 604800)
bsmith bsmith01 /dev/tty (v12.0) (flex1.klocwork.com/27000 47368), start Fri 3/18 13:36 (linger: 604800)
pwall pwall2 /dev/tty (v12.0) (flex1.klocwork.com/27000 34499), start Mon 3/21 14:33 (linger: 604800)
tyoung tyoung02 /dev/tty (v12.0) (flex1.klocwork.com/27000 32739), start Mon 3/21 9:06 (linger: 604800)

The line Users of server: (Total of 5 licenses issued; Total of 4 licenses in use) shows that four out of the five available fixed server licenses are currently in use. Below the Users of client line, license usage details by user and host are displayed. The line beginning with "tyoung" shows us that user "tyoung" checked out a build license on the machine named "host01" at 9:06 a.m. on Monday, March 21. Because build licenses are node-locked, the user "jfall" has consumed three build licenses -- one for each machine they're using.

Five out of the 10 client licenses are currently in use. User licenses are reserved for a unique user.

Note: The output of lmstat will show other license features like kwadmin, review and kwcheck. With the exception of language and optional stand-alone features, these are sub-features of the server and user licenses.

Check license usage by feature

You can check how many licenses are in use for a Klocwork feature (or component), such as Klocwork Static Code Analysis by using the -f <feature_name> option with lmstat.

Build license features

To check license usage for this build component (feature)	Enter this argument
Admin tool for integration projects and builds	kwadmin2017
Analysis tool for integration builds	kwbuildproject2017

Continuous Integration license features

To check license usage for this build component (feature)	Enter this argument
Analysis tool for Continuous Integration builds	kwconan2017

User license features

To check license usage for this client component (feature)	Enter this argument
Klocwork Code Review	cahoots2017
Desktop command-line analysis tool	kwcheck2017
Desktop plug-in for Eclipse	plugin.eclipse2017
Desktop plug-in for IntelliJ IDEA	plugin.idea2017
Desktop plug-in for Visual Studio	plugin.msvs2017
Klocwork Static Code Analysis	review2017