Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 Note that if the last update time for the feature exceeds 2 times the update interval, the last update time will display in red. (The update interval is set in the configuration file.) For example, if the update interval is 2 minutes (120 seconds) and there is no update for 4 minutes, the last update time will display in red.

 

Feature identifiers

Throughout License Statistics, features shown in lists include a separate entry for each version of that feature, and are named feature_version. Versioning provides a finer granularity to report results, which is useful when you have multiple versions of particular features that you want to track individually. For example, under IBM LUM, the Catia MD2 application cost varies depending on version, so feature versioning can help when considering budget for one version versus another version. 

Feature names in lists also include the feature type, which can be Floating, Nodelocked, or Token. Note that if a given feature has more than one type, it will be listed in usage grids once for each type.

 

For example, say you have a feature called F1, for which you have versions 1.0 and 2.0, and both a node-locked and floating installation of version 2.0. This would appear in Feature lists as follows: 

F1_1.0 (Floating) 

F1_2.0 (Floating)

 

F1_2.0 (Nodelocked) 

 Hiding a feature

You can hide the currently selected feature by clicking the Hide icon in the upper right of the General Information title bar.

...