Links

Tags

Recent tweets

Coming off the holidays, this entry is a short list of the most recent list of the latest and greatest downloads which have gone live from Rational Support since our last downloads post on December 27th! These links below are provided to help you find the fixes you need in order to stay up to date and successful with your Rational products.... And, while you have some down-time before the new year (hopefully) don't forget to check out the downloads tag to see any of the fixes you may have previously missed:

Here's more of the latest and greatest downloads which have gone live from Rational Support since March 28th; presented below to help you find the fixes you need and stay up to date with your Rational products.... and don't forget to check out the downloads tag to see the fixes you may have missed:

Lets discuss a dynamic software analysis tool which is designed to help the developers write more reliable code: IBM Rational Purify Plus. It is now known as an advanced memory error detection tool that helps you accurately find hard-to-debug memory corruption errors. You need to fine-tune your application by using Purify, and when you run the tuned application, Purify scrutinizes every memory access and reports any corruption error before it occurs.

Purify is a very useful tool throughout the software development lifecycle. Developers can use it to ensure that the new code that they have written is not going to inadvertently cause any memory corruption errors or leaks. It includes capabilities like:

Now, by looking at this crisp description some of us would really want to try this software, its functionality, and capabilities Below is the link for those who have a feeling that this would be of great help to his/her organisation and can help developers in many ways.Evaluate the Product and share your thoughts- Rational PurifyPlus: http://www.ibm.com/developerworks/downloads/r/rpp/

In order to use and evaluate the product, or even in your production environment, to run any rational product you would need a license file which will be the key to success. In simple words, to run this dynamic software analysis tool we need a license, the license could be of your choice, for the type of license please see the earlier blog post: Licenses types and their functionality

By using the license file and the setup in order to serve the license we can launch the product. This seems to be easy and yes it is, if we do not consider external factors like network, correct license file, server settings, client settings etc, which is not possible, and we run into issues. These issues are simple if we do things right the first time and do it right all the time.

There would be many instances where you have thought that when everything is in place and we have valid licenses which are imported using the license server as recommended, then what could be the possible cause of the error?

Considering the fact that everything is done correctly and there is a very little room for error, I have done some research on it, and here are my findings: Errors specifically (licensing errors) related to PurifyPlus revolve around few settings. I will talk about them one by one in detail in order to get clear picture of what can be done to eliminate these kind of errors and save time,

One among the most common error is FLEXnet Licensing error:-18,147, License checkout failure while using Purify, Quantify or PureCoverage components of DevelopmentStudio UNIX, Full Error will be like : Purify engine: Error: License checkout failure: License server does not support this feature, FLEXlm error: -18,147.

There could be couple or reasons for this specific error to occur:

1). First among them is due to the environment settings not being configured correctly. Confirm the following environment settings are set as shown:

RSU_LICENSE_MAP=//config/License_MapLM_LICENSE_FILE=@

If your configuration differs from the above, you can manually set the above settings by doing:setenv RSU_LICENSE_MAP //config/License_Mapsetenv LM_LICENSE_FILE @

You can now test the license by using the option -testlicense : %purify -testlicense

If you are still getting license errors, copy the License_Map file to the .Rational directory under the user's home directory%cp /config/License_Map /$HOME/.Rational/ And test the license once again.

If this does not resolve the error we should move on to the second possibility which could cause tis error:

2 ). It is possible to set up a mixed environment where the same license server manages licenses for both a suite product and individual point products.

In this situation, license usage order can be customized by modifying the settings in the License_Map file on a per-component-product basis. For example, when a user starts an application, such as IBM Rational Rose, you can define whether that user claims a Rational Rose license or a Rational Suite license.

3). Now that we have done all other checks and made sure that the License Usage is correctly set and environment variables are fine, you may still find that whenever an attempt is made to launch IBM Rational PurifyPlus it results in the error “FLEXnet Licensing error:-18,147”, or specifically for a Windows server "Unable to connect to your license server" (please note this is only applicable when the License server is Windows Server and client is a UNIX machine).

The issue could be with the incorrect license file in use, which means that Rational PurifyPlus for Windows Authorized User license key has been imported.

If you have a Windows license server and a LINUX or UNIX client then the license key needs to be generated should be : "IBM Rational PurifyPlus for Linux and UNIX Floating License Key"If you have a Windows license server and a Windows client then the license you would need should be: "IBM Rational PurifyPlus for Windows Floating License Key"

The error “ FLEXnet Licensing error:-18,147” should no longer persist, if we have these things in place. Also, these should be followed as the best practice while using the software in order to minimize these kind of errors and increase performance and durability of the product we ( IBM ) is developing for you.

Over the past month of November, these were the most heavily reused support generated documents associated with the PMRs which came in over the same time period. These are the docs which helped solve your cases during November, highlighted here to hopefully help others avoid similar issues or obtain the same information you all were in search of: