Features Page

The Current Feature Status page shows the availability and utilization details of the features.

By default, only active features are shown in the table. The Features View option has four different views:
This view shows the availability and utilization details of active license features.
This view shows the availability and utilization details of all features, including idle license features.
This view shows the availability and utilization details of time-based features.
This view shows the availability and utilization details of perpetual features

Figure 1. Current Feature Status Page
In the table, a row is displayed for each feature found in each tag. By default, the table is sorted by the utilization percentage in descending order. The following information is displayed in the table:
The tag representing the license server.
The vendor daemon that is serving out the license server.
The license feature name. If the feature name begins with "T:", the feature is a subfeature, which is activated when certain token-based features are checked out. Note that subfeatures are supported on an inclusive basis only. See below for details.
The time left until the license feature expires. If there are multiple instances of the same feature being served by the daemon, the earliest expiration is used.
The total number of tokens of the feature that are available, also known in Monitor as the capacity.
Total number of unique users that have the feature checked out.
The email icon is a mailto link that can be used to send an email to all users of the feature using the client machine's configured email client. The client must be capable of handling mailto links.
The number of tokens of the feature consumed by all users.
The number of token request currently being queued.
The percentage of tokens currently being used.
Oldest Checkout
The age of the longest-held checkout of the feature. This is useful for finding features held by abandoned or neglected tool sessions.
Contains shortcut icons for generating plots and heatmaps.

Token-Based Subfeatures

Some vendors provide licenses that are token-based. Multiple tools can check out this type of license, with varying token counts. For example, a compiler may check out 1 token-based license, whereas a simulator may check out 2 of that license. To perform the token-based feature tracking (FlexNet Publisher only at this time), Monitor relies on an optional field in the lmstat output that is referred to as the "subfeature" field. This field is located between the display and version fields of the lmstat output. The following is an example of this field, which is highlighted in bold:
"Virtuoso_Multi_mode_Simulation" v9999.999, vendor: cdslmd
floating license
bob lnxws1 :0.0 Spectre (v7.000) (licsrv/1797 3031), start Fri 6/20 12:34
In this example, the user bob has checked out 1 multi-mode simulation license token, and that 1 token is activating the "Spectre" product. In the Monitor reports, if the administrator has enabled subfeature tracking in the monitor configuration for this particular tag, the subfeature will show up as "T:Spectre" to help determine how token-based licenses are being used.
Note: Not all vendors/tools support the subfeature field. In fact, some vendors/tools use this field for other data that is completely unrelated. For this reason, Monitor's FlexNet Publisher parser is designed to support subfeature values on an inclusive basis only. Altair will add support for subfeatures as they are reported to the support team.