Depending on the type of license, a product execution key statement can have the following formats:
PROD(pp) DATE(ddmmmyy) CPU(tttt‑mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)
PROD (pp) CPU (tttt‑mmmm/ssssss) BEGINS (ddmmmyyyy) EXPIRES (ddmmmyyyy)
LMPCODE (kkkkkkkkkkkkkkkk) [DELETE | REMOVE]
Specifies the two‑character product code.
Specifies the expiration date of the CA LMP licensing agreement. Date supports the twenty-first century date format, and only requires the last two digits of the year. For example, January 1, 2010 is 01JAN10, with 10 representing the year 2010.
Specifies the type, model, and serial number of the CPU (for example, 9672-R83 /447276) on which the software solution is to run. If the type and model require less than four characters, blank spaces are inserted at the end of each field for the unused characters.
Specifies the execution key needed to run the software solution.
Specifies the effective starting date of the key. The key is not valid before this date. Use four digits to identify years.
Specifies the expiration date CA LMP licensing agreement. Use four digits to identify years.
Causes the product key to be marked for bypass and therefore skipped on subsequent scans of the Product Descriptor Table (PDT). The product key entry is not physically removed from the PDT, simply rendered inactive with the raising of the bypass semaphore.
This keyword is valid for existing product keys only. A DELETE keyword on a new product definition statement for which a PDT entry does not exist, is rejected and CAIRIM immediately terminates in error.
Note: Key deletion (removal) is effective only if there are no subsequent license checks (#FLOID) issued against the product. If a #FLOID request is issued against a previously removed key, it preempts any previous DELETE action and LMP key violation warnings and alerts will be resumed for the product.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |