CA LMP and CAIRIM

CA LMP is a subcomponent of the Resource Initialization Manager (CAIRIM) that lets you track licensed software using a standardized and automated approach.
ccsfzos15
CA License Management Program (CA LMP) is a subcomponent of the Resource Initialization Manager (CAIRIM). CA LMP provides a standardized, automated approach to the tracking of licensed software. CA LMP uses enforcement software to validate the configuration and to report on activities regarding the licensing, usage, and financial aspects of CA software.
CA LMP operates effectively whether you are using one CA solution on one central processing unit (CPU) or multiple CA solutions on several CPUs.
How CA LMP Works
Each computer that is running one or more CA products that CA LMP maintains uses common enforcement software and a common CAW0OPTN(KEYS) data set member. The KEYS member contains the CA LMP product execution keys that are required to run the associated CA solutions on each of the specified CPUs. During the product installation, you transfer the product execution keys from the CA LMP Product Key Certificates to control statements in the KEYS member.
CA LMP is executed as part of the CAIRIM service. The KEYS DD statement in the CAS9 procedure points to the KEYS member. When CAIRIM is started, CA LMP reads and verifies each statement in sequential order, as found in the KEYS member.
During the operation of each CA solution, the CA LMP enforcement software is invoked periodically. This software compares the product execution keys with the execution environment. If there is a discrepancy between the keys and the environment, the software issues messages to help you resolve the situation. Doing so helps you avoid any interruption in the operation of the solution. If no violations occur after 24 hours for a CA solution, the messages cease.
The messages are written to one or more of the following locations, providing a history of the warnings:
  • System console
  • Event console
  • Batch job log
  • TSO terminal
After the messages are issued, the solution continues operation. The enforcement software ensures that a solution under the control of CA LMP is not interrupted for the following reasons:
  • Expiration dates
  • Improper execution keys
  • Changes in the CPU on which CA LMP is running
Example: Verification of Product Execution Keys at CAIRIM Startup
You add the product execution keys to CAIRIM and load them by executing the CAS9 procedure. The product execution keys are then verified during the CAIRIM startup. In this example, each control statement is displayed as it is read:
CAS9075I - SERVICE(CA-RIM/BASE ) VERS(1200) GENLVL(0808AW000) CAS9115I - INPUT: * CAS9115I - INPUT: * KEY PARAMETERS FOR LMP CAS9115I - INPUT: * CAS9115I - INPUT: PROD(CH) CPU(3090-600 /000000) DATE(19JUL11)
1
LMPCODE(XXXXXXXXXXXXXXXX) CAS9190I - PRODUCT CH KEY ACCEPTED FOR THIS CPU
2
CAS9115I - INPUT: PROD(SO) CPU(3090-600 /000000) DATE(31OCT10)
3
LMPCODE(YYYYYYYYYYYYYYYY) CAS9125E - INVALID DATA: KEY ALREADY EXPIRED
4
CAS9115I - INPUT: PROD(SO) CPU(3090-600 /111111) DATE(30DEC22)
5
LMPCODE(ZZZZZZZZZZZZZZZZ)
The statements give the following results:
  • 1
    Indicates that the product execution key is valid.
  • 2
    Indicates that the product execution key is accepted.
  • 3
    Indicates that the product execution key has expired.
  • 4
    Indicates the explanation for the expiration. If the product execution key is invalid or it has been tampered with, a similar situation exists.
  • 5
    Indicates that the product execution key is for a CPU other than the CPU for which CAIRIM is trying to initialize solutions. The key is displayed, but no message follows and no action is taken. This outcome can occur if you are sharing a common member to define the execution keys for multiple CPUs.