CA Mainframe VM Product Manager - 1.2 : Managing LMP Keys

Contents

Overview

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.

Changing CPUs

If you plan to change CPUs in the future, contact CA LMP support. Be prepared to provide the following information:

  • Current CPU make, model, and serial number
  • New CPU make, model, and serial number

Adding New LMP Keys

When you install a new product, you must add an LMP key for the product in the CALMP KEYS file. A product LMP key is valid for all subsequent releases of that product.

When upgrading to a new release of that product, the same LMP key is used; you do not need a new LMP key.

A product LMP key becomes invalid after the expiration date is reached, or the CPU model and serial number changes.

After receiving a new product LMP key, add it to the CALMP KEYS file. At this time you may choose to delete the expiring key. The new LMP key is effective immediately and the expiring or expired key will no longer be used for product validation.

You can add a new LMP key to this file by using the CA Product LMP Key screen, or by manually editing the CALMP KEYS file.

About the CALMP KEYS File

The CALMP KEYS file resides on the VMANAGER 1FF minidisk, and is a fixed record format file with 128 bytes in length. This file can contain three types of keys:

  • Product
  • EKG
  • Site ID

Product Keys

A product key is valid for a specific product for a specific CPU (or a specific site) until the expiration date. Each product key begins with a PROD statement and specifies the product, expiration date, and associated LMP key.

Product keys have the following format:

PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)

or

PROD(pp) DATE(ddmmmyy) CPU(SITE-****/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)

where:

  • PROD
    Defines the two-character product code.
  • DATE
    Defines the CA LMP licensing agreement expiration date. For example:
    25JUL15
    specifies an expiration date of July 25, 2015
    Note: CA LMP licensing supports the 21st century date format. However, only the last two digits of the years will be displayed.
  • CPU
    Specifies the CPU type, model, and serial number on which the product will run. If the CPU type and model require less than four characters, insert blank spaces for the unused characters.
    If your site has been issued a site license for a product, this will specify the site ID that must appear on the SITEID record for this key to be valid, and the CPU serial number.
  • LMPCODE
    Specifies the LMP key for the product.

EKG Keys

In emergency situations, such as disaster recovery, an Emergency Key Generator can issue a temporary key for the products. An EKG key is valid for ten days from the date of activation, and it is valid for all products and on all CPUs.

Each EKG key begins with the EKG statement, and is in the following format:

EKG(nnnnnnnn)

where:

  • EKG
    Specifies the emergency key.

It is not necessary to implement EKG keys to activate products in a disaster recovery situation, because CA LMP allows the products to run uninterrupted regardless of the CPU on which they are running. Note that when bypassing EKG, warning messages will be issued after any product command entered by a user. These messages do not impact product operation, but they will be visible on the console, and to the system administrators and operators.

To suppress these messages, contact CA LMP support and, in an emergency, request an EKG key. Once you have obtained an EKG key, edit the CALMP KEYS file and add the key information as shown in the example above.

Site ID Keys

A site ID key is used in combination with an LMP key to provide non-CPU specific key support. Site ID keys are typically generated by CA LMP support for large sites running many products.

If a site ID exists, it must be the first statement in the CALMP KEYS file.

Each site ID key begins with the SITEID statement, and is in the following format:

SITEID(nnnnnnnn) SITECODE(xxxxxxxxxxxxxxxxxxxx) NAME(name)

where:

  • SITEID
    Specifies the site ID.
  • SITECODE
    Specifies the site ID key.
  • NAME
    Specifies the company name.

Sample LMP Keys File

PROD(AA) DATE(01FEB13) CPU(1234-000/123ZZ2 LMPCODE(ABCD1234H678J098)
PROD(BB) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(1234GH586K79H86L)
PROD(1C) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(87603HNDABCD1234)
PROD(DA) DATE(15JUN14) CPU(1234-000/123ZZ2 LMPCODE(ABSJFLAPS846D089)
PROD(DD) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(BSVDGALF254KUISS)
PROD(3L) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(AK050934GDFG95HD)
PROD(5F) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(NDKSHABCKS944K81)
PROD(HH) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(ABDVD1234H890098)
PROD(K8) DATE(15MAY13) CPU(1234-000/123ZZ2 LMPCODE(D1234H678J098YYX)

Editing the CALMP KEYS File

Typically you edit the CALMP KEYS file only when you have a new LMP key, or if you make a mistake in entering the LMP key. Routine maintenance is not required. Because CA LMP detects that the file was changed and rescans the information in the file, it is not necessary to bring a product down when editing the CALMP KEYS file.

To edit the CALMP KEYS file, use either the menu interface or use XEDIT to edit the file directly. Using the menu interface, you can enter one LMP key at a time; using XEDIT allows you to make all change to the file at one time.

To enter LMP keys in the CALMP KEYS file, perform these steps from the CA Mainframe Product Manager administration ID:

  1. Display the CA Product LMP Key screen by entering the following command:

    VMLMPKEY
    
  2. Follow the instructions on the menu to add a key, or use the steps below to directly edit the keys file.
  3. Press PF12. The CALMP KEYS file opens in XEDIT.
  4. Enter each product LMP key exactly as it appears in the Product Key Certificate you received.
    If you are entering a new LMP key to replace an expiring key, you may choose to delete the expiring or expired key at this time. The new LMP key becomes effective immediately and the expiring or expired key will no longer be used for product validation.
  5. When you are finished, save and exit the file. CA LMP detects that the file was changed and rescans the information in the file. CA LMP key verification runs intermittently at variable intervals. The new LMP key will be used during the next LMP key verification process. If you require that LMP key verification occur immediately after a change, you must end the product and restart it so the file is processed during product initialization.

CA LMP Error Handling

You may encounter error messages either during system startup or when you attempt to use a CA LMP-controlled product. The CA LMP error messages are documented in the Message Reference guide for each product. For assistance with LMP issues, contact a support representative.