PATCH 468-003
-----------------------

You may need to apply this patch if:
a. Your end-users cannot give nodelocked-offline licenses back to the  
   server's pool of concurrent-offline licenses. 
b. You cannot assign authorizations based on group names 
   to use concurrent-offline licenses in offline mode.
c. You can no longer update the max offline period of a concurrent-offline
   license
d. Frequent overload conditions are detected, even under moderate actual 
   workloads, leading to random denial of licensing services

Defects description
-----------------------------
a. 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. 

b. 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.

c1. 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"  

c2. 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"
   
d. 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. 


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 defect c2. only: 
Download the new 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)