Shijesh Velayudhan 270004VGUQ Visits (1697)
License Usage Order
IBM Rational products requests licenses in a specific order. In an organization we may have combination of authorized user, floating, suite, point-product licenses in the environment, it is essential that we understand the license usage order.
Now let’s try to understand the license usage order. An IBM Rational product that users IBM Rational Common Licensing will request the license in the following order.
For version 7.0 of IBM Rational products, the license key usage order has changed. In releases before 7.0, when a Suite product was being installed, the Rational License Key Administrator (LKAD) application would first try to find a license key corresponding to the Suite. If the Suite key was not available, LKAD would then look for a key corresponding to the product that was running.
The table below describes the license usage order for each IBM Rational Product that uses IBM Rational Common Licensing.
Now let’s check how to change the license usage order. Any changes made in the license usage order can be reversed to previous setting by clicking the "Restore to Defaults" in the license usage mapping window.
To change the license usage order:
The license usage order that you set on your computer is tied to your user ID. If different users log in to your computer with their own user IDs, the license usage order that you may have changed resets to the default order. The new users can set the license usage order for their user IDs. Their settings do not affect your settings.
AcdntlPoet 2700019V2G Visits (2010)
If you're an administrator for a Rational Synergy/Change installation that uses Informix and you haven't seen this technote: "Increase IBM Informix Dynamic Server 11.5 STACKSIZE parameter to prevent Informix crashes", then we STRONGLY suggest that you give it a read and implement the setting change it suggests.
Under certain circumstances, the default STACKSIZE for the Informix server is too small and can possibly lead to a stack overflow condition, which can bring the server offline. While the server can usually be brought back online without incident, in some cases it cannot and the server needs to be re-created from backups.
The tech note above suggests increasing STACKSIZE and restarting the Informix server to pro-actively prevent the stack overflow issue. If you're an admin for Rational Synergy or Rational Change, and use Informix as your back-end database, we highly encourage you to implement the changes addressed in this technote.