Resource Initialization Manager › CA LMP › How CA LMP Works

How CA LMP Works

CA LMP is designed to operate smoothly and efficiently, whether you are using one CA solution on one central processing unit (CPU) or multiple CA solutions on several CPUs.

Each computer that is running one or more CA products maintained by CA LMP uses common enforcement software and a common KEYS data set member. The KEYS member contains the CA LMP execution keys that are required to run the associated CA solutions on each of the specified CPUs. During product installation, you transfer the 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, each statement is read and verified by CA LMP 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 execution keys with the execution environment. If there is a discrepancy between the execution keys and the environment, it issues messages so that you can resolve the situation and avoid any interruption in the operation of the solution. If after 24 hours there are no further violations for a CA solution, the messages will cease.

The messages are written to the system console, the Event Console, a batch job log, or a TSO terminal, providing a history of the warnings.

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 because of expiration dates, improper execution keys, or changes in the CPU on which it is running.

Example: Verification of Execution Keys at CAIRIM Startup

Each control statement is displayed as it is read, as shown in the following sample:

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)  Œ
     LMPCODE(XXXXXXXXXXXXXXXX)
CAS9190I ‑ PRODUCT CH KEY ACCEPTED FOR THIS CPU                 
CAS9115I ‑ INPUT: PROD(SO) CPU(3090‑600 /000000) DATE(31OCT10)  Ž
     LMPCODE(YYYYYYYYYYYYYYYY)
CAS9125E ‑ INVALID DATA: KEY ALREADY EXPIRED                    
CAS9115I ‑ INPUT: PROD(SO) CPU(3090‑600 /111111) DATE(30DEC12)  
     LMPCODE(ZZZZZZZZZZZZZZZZ)

The statements give the following results:

• The execution key in Œ is valid. The message in  indicates that the key is accepted.
• The execution key in Ž has expired. The message in  displays the fact. A similar situation would exist if the key is invalid or has been tampered with.
• The execution key in  is for a CPU other than the one for which CAIRIM is attempting to initialize solutions. The key is displayed, but no message follows and no action is taken. This can occur if you are sharing a common member to define the execution keys for multiple CPUs.