Summary for Patch 1067 (Verified)

Summary	Added support for IBM LUM offline usage
Platform	Windows
Category	bugfix
Valid for	4.9.x, 5.0.x, 5.1.x, 5.2.x, 5.3.x
Requires
Server Required Patch/es
Supersedes	1063, 1054, 1044, 1013, 1032, 1028, 1027, 1026, 1021, 1020, 1019, 1015, 1005, 1004
Superseded by	1101 : Released / Not hidden
Affects	Client: License Analyzer
Last Updated	September 30, 2009

Download now

Download_red Patch1067.zip

Description

Fixed bug causing licpoll to use 100 % cpu when FLEXlm poll data showed one feature
using the license of another. In this fix, a warning will be logged in this case, and
no usage reported.

Supersedes Patch Description

Expand all

Patch 1063 — Added support for IBM LUM offline usage

Added support in LicPoll for in cluding offline usage from IBM LUM.

Patch 1054 — Fixed bug in LicPoll, IBM LUM polling

If "Group" was missing from the output from i4blt, the LUM poller, parts
of the poll data would be missed by LicPoll.

Patch 1044 — Fixed parsing problem for FLEXlm 11.3 license files

In PACKAGE lines, a field that was previously present in the license
file seems to have been removed. This could cause LicPoll to sometimes
discard components information.

Patch 1013 — LicensePoller: Adding server name given during installation setup to product name

During installation, when setting up license polling, you can input a server
name. This name was previously not accounted for. This patch will cause the
server name to be attached to the product name: <product name>_<server name>,
allowing you to use the server name to distinguish otherwise identical
product names from different license servers.

Patch 1032 — Fixes a bug in LicPoll when poll interval exceeds 5 minutes

If the poll interval for LicPoll was set to a value greater than 5 minutes,
LicPoll would terminate after just one poll (and not run the entire hour).

Patch 1028 — LicPoll now supporting Elan Valisys/NT

LicPoll will now accept the Valisys/NT Elan format.

Patch 1027 — Fixes problem with LicPoll, parsing IBM LUM offline usage

LicPoll would fail to parse the IBM LUM license information correct
when there were offline usage.

Patch 1026 — Fixes problem with LicPoll, parsing IBM LUM host name

LicPoll would fail to get correct host (node) name when parsing IBM
LUM output, if the host name was followed by ip address.

Patch 1021 — LicPoll will now cd to FLEXlm license file directory before running lmutil

When running lmutil, it has proven to fail in some cases if current directory
is not that of the license file. LicPoll now runs lmutil for each license file
from that license file's directory.

Patch 1020 — Can now read FLEXlm license file locations from Registry

If installed on the FLEXlm server, LicPoll is now able to scan the
Registry in order to locate the license files available on the server.

Patch 1019 — Handle IBM LUM date format with numerical month value

Output from i4blt (IBM LUM status command) can contain numerical
month value, rather than short month name. This patch will allow
LicPoll to handle both formats.

Patch 1015 — LicPoll: Fixes problem with long "-----" appearing as feature name or

Minor variations in output from FLEXlm status command (depending on version
of FLEX) caused a parsing error. The output contains long lines of dashes,
which licpoll didn't handle very well.

Patch 1005 — LicPoll: Fixes problem with first poll of the run being skipped.

When licpoll starts to poll, it will align the poll time according to the poll
interval. If the interval is 5 minutes, then polls will be taken on the hour,
5 minutes past, 10 minutes, etc. When licpoll was started, if only seconds past
the hour, the first poll would be aligned to 5 minutes past. This patch fixes
this, so that the first poll is taken immediately after startup, and then the
polls are aligned as normal (5, 10, 15, etc.).

Patch 1004 — Fixes incompatibility problem in Licpoll towards IBM LUM

Added support for newly discovered format on output from i4blt -s -lc (slightly
different from previously known output format).

Installation

Unpack the zip file anywhere on the machine to patch.
Run install.exe to start installation.
Once the patch has been installed, you may delete the
unpacked patch directory.

NOTE: The patch must be installed by a user with administrator rights.

Corresponding Unix Patches

No corresponding Patches available.

Back to Version List