Summary | Added functionality for IBM LUM offline usage and fixed bugs and shortcomings |
Platform | Windows |
Category | bugfix |
Valid for | 5.2.x, 5.3.x, 5.4.x, 5.5.0.x, 5.5.1.x |
Requires | 5.2.0.0 - 5.5.0.0: 1094, 5.2.0.0 - 5.4.0.2: 1090 |
Server Required Patch/es | |
Supersedes | 1097, 1067, 1063, 1054, 1044, 1013, 1032, 1028, 1027, 1026, 1021, 1020, 1019, 1015, 1005, 1004 |
Superseded by | |
Affects | Client: License Analyzer |
Last Updated | September 30, 2009 |
Bugs fixed in this patch: 1. A bug while parsing FLEXlm status output (lmstat) would cause LicPoll to crash. 2. The "Server name" configuration option during installation setup now works for License Monitor 3. Reprise LM parsing error causing licpoll to hang. 4. Will now combine FEATURE lines for the same feature+version when the serial number is different. 5. No longer separating features because of different case (FeatureA is not the same as featurea) 6. In Lum, fixed the problem, of overwriting online status file by offline status file. Now two seperate files will be created for online and offline.
Bugs fixed in this patch: 1. A bug while parsing FLEXlm status output (lmstat) would cause LicPoll to crash. 2. The "Server name" configuration option during installation setup now works for License Monitor 3. Reprise LM parsing error causing licpoll to hang. 4. Will now combine FEATURE lines for the same feature+version when the serial number is different. 5. No longer separating features because of different case (FeatureA is not the same as featurea)
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.
Added support in LicPoll for in cluding offline usage from IBM LUM.
If "Group" was missing from the output from i4blt, the LUM poller, parts of the poll data would be missed by LicPoll.
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.
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.
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).
LicPoll will now accept the Valisys/NT Elan format.
LicPoll would fail to parse the IBM LUM license information correct when there were offline usage.
LicPoll would fail to get correct host (node) name when parsing IBM LUM output, if the host name was followed by ip address.
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.
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.
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.
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.
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.).
Added support for newly discovered format on output from i4blt -s -lc (slightly different from previously known output format).
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.
No corresponding Patches available.