Hi,

Would you be able to let us know what is the current process for renewing the RD&T license key? We have been told by IBM that this has recently changed, but haven't been provided any details.

Thanks,
Krystyna

Hi Krystyna,
The process remains the same. You can use the Rational License Key Center
( https://licensing.subscribenet.com/control/ibmr/login ) to renew the update file. The process is to use "View and Return keys" on the left side of the page to return the license for the serial number you need, and then use "Get Keys" to create and download a new license (update file).

If the USB key is a high capacity USB key that is enabled with more than one instance (more than 3 CPs) then the Key Center was not used originally for its activation. In that case, please see the instructions at the RDT hub at http://ibm.co/rationalsystemzdevtest .

Doug Nadel

Thanks Dough,

I was actually looking at the process documented in IBM System z Personal Development Tool Volume 2 Installation and Basic Use (running SecureUpdateUtility, uploading the file through Resource Link and then running SecureUpdateUtility again with the updated version of the file).
Is the process using Rational License Key Center documented anywhere? I have found our key, but am not quite sure what to do next (Generate Another License, Return, Download?).
You have mentioned Return, but the help says” By returning the keys back to the available pool, you are telling IBM that you will no longer use the actually license keys you downloaded”. We obviously need to use the current license while we are renewing it, so it is a bit confusing.
Could you please clarify, as we cannot upset our working environment.

Thanks,
Krystyna

The process documented in the Redbook Vol II is for a different set of users than Rational Developer and Test users (or RDz UT users). The Rational products' USB keys use the update files from the Rational License Key Center only. The update files for the Rational USB keys and non-Rational USB keys are not interchangeable. If your USB key has a metal loop with a tag attached, then it is not a Rational version of the USB token.

Returning and renewing the license simply extends the date until which the license is valid. Using SecureUpdateUtility -u to apply a new update file will just allow the license to work for longer. Once you apply the new update file, you will be using the new license which will be good for one year from the date it is created. There does not need to be an interruption in service as the USB token remains attached during the update.

In practice, I tend to remove the key from the USB port for a second after applying the update and plug it back in just to ensure it is re-read, but that is probably not really necessary. Removing the USB key for a very short time will not cause any interruption (or, if by chance it does due to extraordinary timing, everything will resume when the key is reinserted). You can check the expiration date of the key with the "token" command on the Linux box that owns the key. Note that it may take several minutes for the token command to recognize a new update file.

Hi,

Thanks for clarifying that. Our key does not have a tag attached, so I assume it is a Rational key and I should use the Rational License Key Center to extend the license.

Is this process documented anywhere? As mentioned, I have found our key on the License web site, but am not quite sure what to do next (Generate Another License, Return, Download?, what are these options used for?).

You have mentioned Return, but I’m a bit concerned doing it without knowing what the whole process is. I’m guessing it will generate some sort of file that I will need to download, but it would be nice to know what to expect.

Thanks,
Krystyna