Extended licensing options supported by product integrations are shown in the below given table:

Understanding of "TELELOGIC_ LICENSE_FILE variable":On Microsoft Windows, Telelogic products store the location of the license file in the TELELOGIC_LICENSE_FILE system environment variable. On UNIX, Telelogic products store the location of the license file in the LM_LICENSE_FILE system environment variable.

On Synergy, the location of the file is also stored in license_data.txt file on the same router machine.

The value of TELELOGIC_LICENSE_FILE depends on whether your computer is using either floating licenses, or node-locked licenses. If your computer is using several node-locked and/or floating licenses, the values in TELELOGIC_LICENSE_FILE are separated by semicolons ( on Windows and colons ( on UNIX. The list can consist of the following components:

The full path to a license file

A directory containing one or more license files with a .lic extension

A port@host setting, where port and host are the TCP/IP port number and host name from the SERVER line in the license file. Alternatively, use the shortcut specification @host if the license file SERVER line uses a default TCP/IP port, or specifies a port in the default port range (27000-27009).

Telelogic applications that use FLEXnet rely on the environment settings that FLEXnet uses to find licenses. The applications search for license servers and license files in the following order:

The environment variable TELELOGIC_LICENSE_FILE

On Windows, the registry entry for TELELOGIC_LICENSE_FILE. On UNIX, the registry /.flexlmrc for TELELOGIC_LICENSE_FILE .

The environment variable LM_LICENSE_FILE

On Windows, the registry entry for LM_LICENSE_FILE. On UNIX, the registry /.flexlmrc for LM_LICENSE_FILE .

For Synergy, the location specified by the contents of $CCM_HOME/etc/license_data.txt.

License Value Description:Floating port@license-server-name, The FLEXnet license server from which your computer is requesting server licenses and the port number the server is using.

Node-locked license-file-name The full path to the license file on your computer.

User based feature:
A licensing scheme which uses the FLEXnet attribute USER_BASED to restrict license to specific user of a tool. A user-based license must be served by a license server.

A user-based license is tied to one specific user. This is compared to a floating license which anyone can use. A license Feature for a user-based license is recognized by the attribute USER_BASED on the FEATURE/INCREMENT line. The user who can obtain a user-based license are specified in the FLEXnet options file for the license server.

FEATURE RPE_PUBLISH telelogic 2009.1230 30-oct-2009 4 \

VENDOR_STRING=T10-386113 USER_BASED ISSUED=13-Jan-2009 \

SIGN2="1EAF 827F -"

The users must be defined in a separate configuration file. The configuration file must be explicitly set in the license file

The version number from the configuration file must match the version number from the license file (see in bold)

For the same feature both user based and floating features can be present. The user based should be listed first in the license file.

Please see the top 10 Frequently Asked Questions on the Telelogic licensing concepts:

Can I use my old licenses and Telelogic products with the new license server?Yes, you can continue to use your existing licenses and the associated Telelogic products as before.

Can I use my new licenses and Telelogic products with the previous license server?No, to utilize the new date version licenses and associated Telelogic products you will need to deploy the new License server.

Can I use my current licenses with the new versions of the Telelogic products?Yes, if your maintenance agreement is beyond the release date of the products. The FEATUREs in your license file has a version string that reflects the expiry date of your maintenance agreement. If this version string is larger than 2008.0630 than you can run the new products using this license file.

Can I use my new date-versioned licenses with the older versions of the Telelogic products?Yes, the new date-versioned licenses can be used with the older versions of Telelogic products.

Can I mix older licenses and date-versioned licenses on the new License Server?Yes, the new License Server supports traditionally versioned and date-versioned licenses.

Are date-versioned licenses applicable to patches and service packs?Yes, service packs will be date-versioned. You can use, and continue to use, service packs that are released during your maintenance period.

Can I continue to use Telelogic products after my maintenance has expired?This depends upon the terms of your agreement with Telelogic. The product releases or service pack releases after the maintenance expiration date cannot be used. Other older products can still be used.

What happens when my maintenance contract expires?You will need to renew your maintenance contract and obtain a new license to use Telelogic products and updates that are released after your maintenance period has expired.

When do I need to obtain a new license?If your licensing requirements change (e.g. you require additional users) and when you renew your maintenance contract.

What happens if I renew my maintenance contract for a fewer number of users?Telelogic products that are released after you renew your maintenance can only be utilized by the number of users that are contained in your new license.

We all know (I do) how frustrating it can be to encounter an error message and not know what to do to fix it. Now, you can find troubleshooting information and collaborate with others to improve error messages in the Information Center at: http://publib.boulder.ibm.com/infocenter/rsdp/v1r0m0/index.jspFollowing are a few specific Technotes I have found to be very beneficial when answering questions in PMRs:

This new blog targets Rational Automation Framework (RAF) and DevOps as it relates to Rational Products including UrbanCode Udeploy. This blog is hosted here on the IBM developerWorks platform and works in collaboration with Twitter.

Of course, these are not the only reasons to join the conversations on Twitter. The list below contains the information that will be tweeted daily as it happens in real time.

1. New training

2. Technotes

3. Defects

4. HotFix eligibility

5. Product Release information RAF, Udeploy, AMC

6. All Blogs whether Spotlight, Educational or Other.

This model of doing social business is highly dependent on participation. Any and all participation is encouraged. RAF will do it's best to answer and address any and all questions. We want you to be as successful as you can be.

If you can think of something additional other than what has been listed above. Let us know! We will make it happen!!

I have just been working on couple of IBM Rational ClearCase issues where a downgrade of the nfs version from nfs 4 was needed on their RHEL machines. So, I am sharing the info about the steps to downgrade the nfs version so that it can be handy if any of you also come across the same issues.

For example, when you run showmount -e, you will find the following output for the specific mount point:RCSRHEL6164:/ccstg on /net/RCSRHEL6164/ccstg type nfs (rw,nosuid,nodev,intr,sloppy,vers=4,addr=9.32.253.45,clientaddr=192.168.199.253)

In the above we see that the mount point is using "vers=4" which stands for nfs 4

So if you have to downgrade to nfs 3, then do the following:

On the Server:
-------------
Edit /etc/sysconfig/nfs to have following lines: