CA Common Services for z/OS Requirements
To help you quickly understand all that the CA Common Services for z/OS offers, this section provides a brief description of each service that dcs uses.
To help you quickly understand all that the CA Common Services for z/OS offers, this section provides a brief description of each service that
CA Datacom CICS Servicesuses.
CA Common Services for z/OS is a group of system services that protect your software investment by helping to manage your data center more efficiently. Each of the CA Common Services for z/OS offers individual benefits. The following CA Common Services for z/OS components are used with and benefit the
This page contains the following topics:
LMP Key Requirements
The CA License Management Program (CA LMP) tracks licensed software in a standardized and automated way. CA LMP uses common real-time enforcement software to validate the user configuration. CA LMP reports on activities that are related to the license, usage, and financials of products.
Your product is licensed with an LMP key. You acquire the LMP key with one of the following methods:
- From your product media
- With Pax ESD
- From Broadcom Support
For more information about LMP keys, see the CA Common Services for z/OS documentation.
CA LMP provides a standardized and automated approach to the tracking of licensed software. It uses common real-time enforcement software to validate user configuration. CA LMP reports on activities related to the license, usage, and financials of your CA products. CA LMP features include:
- Common key data set which can be shared among many CPUs
- "check digits" used to detect errors in transcribing key information
- Execution keys you can enter without affecting any CA product already running
- No special maintenance requirements
The CA LMP execution key that the Key Certificate provides must be added to the CAIRIM parameters to ensure proper initialization of all CA products.
To define a CA LMP execution key to the CAIRIM parameters, modify member KEYS in the OPTLIB data set. The following code is the parameter structure for member KEYS:
PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)
(Required)The two-character product code. For any given CA LMP product, this code agrees with the product code already in use by the CAIRIM initialization parameters for earlier genlevels of the product.
(Required)The CA LMP licensing agreement expiration date.
(Required)The CPU type and model (for example, 3090 - 600) on which the CA LMP product will run. If the CPU type, model, or both require less than four characters, blank spaces substitute for any unused characters.
(Required)The serial number of the CPU on which the CA LMP product will run.
(Required)The execution key needed to run the CA LMP product. This CA LMP execution key is provided on the Key Certificate shipped with each CA LMP product.
In the following example, the CA LMP execution key value is invalid and is provided here
as an example only.
PROD(BD) DATE(15APR2013) CPU(3090-600 /370623) LMPCODE(52H206130Z7RZD6)
For a full description of the procedure for defining the CA LMP execution key, see the
CA Common Services for z/OSdocumentation.