Previous Topic: Loading Help Files

Next Topic: Changing CPUs

Managing LMP Keys

Each CA VM product is identified by an assigned two-character LMP key. You are issued an LMP Product Key Certificate for each LMP-enabled product. This Key Certificate contains an execution key for the product, which consists of the product LMP key code, an expiration date, and the CPU model and serial number on which the product is being licensed to run. You must enter this key as part of the product installation process.

CA VM:Backup HiDRO, CA VM:Spool V/Seg Plus, DASD Utilities and utility products like CA VM:Sort do not require LMP keys.

LMP keys are maintained in a central CALMP KEYS file, residing on the VMANAGER 1FF minidisk. Products link to this minidisk as 1FF.

The existence and validity of the LMP key is checked at product start-up and any time the CALMP KEYS file is changed. When a product runs, it performs LMP verification to determine whether it is authorized to execute at your site on that specific CPU. If a CA VM product cannot find a valid LMP key for the model and serial on which the product is running, warning messages are issued at product initialization and at each user command. These messages do not affect product performance, and the product will continue to run.

Each LMP key has an expiration date. Warning messages are issued for each product whose LMP key is about to expire. When you start getting messages that your LMP key is due to expire, contact CA LMP support as soon as possible to avoid potential license expiration. When an LMP key expires, the product will continue to operate but messages will be generated that indicate the LMP key is invalid.

This section contains the following topics:

Changing CPUs

Adding New LMP Keys

About the CALMP KEYS File

CA LMP Error Handling