Summary | Fixed bug in LicPoll, IBM LUM polling |
Platform | Windows |
Category | bugfix |
Requires | |
Server Required Patch/es | |
Supersedes | 1044, 1013, 1032, 1028, 1027, 1026, 1021, 1020, 1019, 1015 |
Superseded by | 1063 : Verified / Not hidden |
Affects | Client: License Analyzer |
Last Updated | September 30, 2009 |
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.
Unpack the zip file anywhere on the machine to patch. Run the InstallPatch.exe application. 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.