CA Gen z/OS products require CA LMP keys. CA LMP keys are valid for multiple product releases but not for multiple CPUs. If you are running an earlier release of the product and installing it on the same CPU, skip this section. If you are installing a new product, or installing on a different CPU, install CA LMP keys.
Examine the CA LMP Key Certificates you received with your installation package to ensure you have a key certificate for every product that requires one.
|
Fields |
Descriptions |
|---|---|
|
Product Name |
The trademarked or registered name of the CA product licensed for the designated site and CPUs. |
|
Supplement |
The reference number of your license for the particular product, in the format nnnnnn-nnn. This format differs slightly inside and outside North America. In rare situations, it may be omitted. |
|
Expiration Date |
The date, month dd, yyyy as in January 15, 2010, the product license expires. |
|
Technical Contact |
The name of the technical contact at your site that is responsible for the installation and maintenance of the designated product. CA addresses all CA LMP correspondence to this person. |
|
MIS Director |
The name of the director of MIS, or the person who performs that function at the site. If the title but not the individual's name is indicated on the Certificate, supply the actual name when correcting and verifying the certificate. |
|
CPU Location |
The address of the building where the CPU is installed. |
|
Execution Key |
An encrypted code required by CA LMP for product initialization. During the installation, it is referred to as the LMP code. |
|
Product Code |
A two-character code corresponding to this particular product. |
|
CPU ID |
The code identifying the specific CPU for which installation of your product is valid. |
If your site is already running software from CA, your systems group probably is already running a CAS9 proc (cataloged procedure). If so, add the CA LMP keys for the products you are installing to the CA LMP keys already being used.
The CAS9 proc runs the CAIRIM program that uses a KEYS DD statement. The KEYS DD statement should point to your CA LMP keys. The KEYS DD statement usually points to a member named KEYS in a PARMLIB or OPTLIB. Each line contains the information from one key certificate. If the information does not fit on one line, code a hyphen in column 72 for a continuation character.
The parameter structure for member KEYS is:
PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkk)
Note: The parentheses are required.
|
Parameter |
Definition |
|---|---|
|
pp |
Required. The two-character product code. For any given CA LMP software solution, this code agrees with the product code already in use by the CAIRIM initialization parameter for earlier releases of the product. |
|
ddmmmyy |
The CA LMP licensing agreement expiration date. |
|
tttt-mmmm |
Required. The CPU type and model on which the CA LMP software solution is to run. If the CPU type or the model requires less than four characters, insert blank spaces for the unused characters. |
|
ssssss |
Required. The serial number of the CPU on which the CA LMP software solution is run. |
|
kkkkkkkkkkkkkkk |
Required. The execution key is provided on the Key Certificate shipped with each CA LMP software solution. |
This is an example of a control card for the CA LMP execution software parameter:
PROD(BD) DATE(15JAN02) CPU(3090-600 /370623) LMPCODE(52H2K06130Z7RZ6)
Note: This is an example. The CA LMP execution key is invalid. For more information about CA LMP execution key definition, see the CA Common Services Installation Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|