PATCH 468-007 ----------------------- You may need to apply this patch if: a. You get error CLN-42 "Fatal error -- check error log." when trying to clean-up stale licenses. b. Your end-users cannot give nodelocked-offline licenses back to the server's pool of concurrent-offline licenses. c. You cannot assign authorizations based on group names to use concurrent-offline licenses in offline mode. d. You can no longer update the max offline period of a concurrent-offline license e. Frequent overload conditions are detected, even under moderate actual workloads, leading to random denial of licensing services f. You find duplicate entries in the list of current users of concurrent- offline licenses. g. Your server performances decrease overtime and the filesystem where the server log files are defined (/var by default) is frequently full. Defects description ----------------------------- a. This patch mitigates the effects of a database corruption condition that hits only one or few database records. Currently, when this occurs, the CLN-42 message is returned and no stale licenses are made available again. Over time this can lead to a severe condition in which users of the product will report you that they cannot start it any longer because no licenses are available. Now the clean-up stale licenses operation is no longer stopped at the first encountered error but it proceeds trying to clean-up as more stale licenses as possible. It may happen that the CLN-42 message shows up again after the installation of the patch, but less frequently. Moreover a second execution of the same clean-up command after a failure should succeed. b. With this patch the following constraints in the handback of a previously reserved nodelocked-offline license are being removed: - only the same Windows user ID that reserved the license can hand it back - the IP address of the portable computer must be the same as at the time of the reservation (so that it cannot be configured using DHCP) - the same version of LUM client code (of the LUM-enabled product) must be used to reserve and handback the license. Note that the hostname of the laptop at handback time must still correspond to the hostname that the machine had at reservation time. c. You are trying to define an authorization list for a Dassault product that should be used by a group of users in disconnected mode. The users belong to the same LUM group and you are granting them full access to the concurrent-offline license ("allowed" mode) using the name of the group. Nevertheless the users fail in reserving the license as offline license for their laptops. d1. If you try to modify the max offline period of a concurrent offline license you may get the following error message: "CLN-142 Not all the Offline Periods have been updated" d2. If you try to modify the max offline period of a concurrent offline license that is an upgrade key of a Custom Configuration license you will get the following error message: "ADM-10932 The maximum allowed Offline Period must be greater than 0 and smaller than 1" e. You see in I4LMD.log that the server is frequently logging a threshold overcome message. Your end-users suffer of frequent denials of service and i4tv, i4blt commands randomly do not work properly. Typically this depends on a too low value for the MaxActivities parameter in i4ls.ini file, but in this case increasing it up to its maximum (1024) does not solve. Note that this patch also introduces a new upper limit (2048) for MaxActivities. f. Listing users of concurrent-offline licenses, either through the BLT graphical interface or the command line i4blt -s, you may find duplicate entries if there are both concurrent and offline users, and the overall number of users exceeds 50. g. On SGI-IRIX servers the limit to the size of the log databases, as defined by the MaxLogFileSize value in the i4ls.ini configuration file, does not work, so the file size grows indefinitely and the switch from one log file to another does not take place. This can lead to frequent filesystem full conditions and to bad performances. Installation instructions --------------------------------- Stop the license server (i4cfg -stop) and replace the i4lmd executable with the one provided with this patch. The executable can be found in: /usr/opt/ifor/ls/os/aix/bin (AIX) /opt/lum/ls/os/solaris/bin (Solaris) /opt/lum/ls/os/hpux/bin (HP-UX 11) /opt/lum/ls/os/svr4.sgi/bin (Irix) /opt/lum/ls/os/linux/bin (Linux) For defects a. and f. only: Also replace the I4blt executable, in the same directory as above, on the server machine and on any other remote system having LUM 4.6.8 installed and being used for the remote administration of the server. For defect d2. only: Download the version of the i4_offline_mig identified as 4.6.8.2 from http://www-306.ibm.com/software/applications/plm/support/prodannounce.html and run it. Restart the license server (i4cfg -start)