This chapter gives answers to frequently asked questions regarding development licenses.
Contact us or the product supplier for an additional license key. You then run the License Administration Services to add this license key into the license database.
Yes. Licenses for a product can run with the original product (for example, Server Express 1.0) and any updates for that product (for example, Server Express 1.1). However, you cannot use licenses from earlier products, such as Object COBOL Development System with a later product such as Server Express. Also you cannot use 32-bit licenses with 64-bit Server Express on AIX, nor 64-bit licenses with 32-bit Server Express on AIX.
For details on deployment licenses, see your Deployment License Management Guide.
Yes, if the new version is an update to the old version. For example, a 32-bit license for Server Express 2.0 can be used with Server Express 1.1. It cannot, however, be used with older products, for example Object COBOL Development System.
For details on deployment licenses, see your Deployment License Management Guide.
No. If users cannot run their products because users from other departments are using up the license units, you have insufficient licenses on your system and need to purchase and install additional ones.
If you want the flexibility of reconfiguring machines according to need, you need to uninstall a license from one machine and then install the license on another. Be aware that this is potentially time consuming, especially if you have many licenses, as you have to enter each one manually. Remember too that licenses are specific to hardware and operating system, as well as the product.
Yes. Call us for a temporary license key to use on the machine that is running.
Existing licensed tasks are unaffected. Restart the License Manager from the command line.
However, if there are any outstanding licensed tasks invoked by the previous License Manager, the new License Manager does not start. It closes itself down again. To start the License Manager in this situation, start it from the command line with the FORCE or WAIT directive. See the section on starting the License Manager in the chapter Administering the License Management Facility.
No damage results if you attempt this, because the newly started License Manager detects that another copy is running, and immediately closes itself down again.
Contact Product Support. They will help resolve the problem. They might suggest suspending license checking for a short period while the problem is solved.
When you install a new license key, you are entering the new key into the license database. However, the license key is not yet in the License Manager's copy of the license database. After installing a new license key, you need to refresh the License Manager's copy of the database. To do this, go to the License Administration Services main menu, and press F7=refresh. Alternatively, you can let the License Manager automatically refresh its copy of the license database the next time it is restarted.