After introduction of EKG key you may receive these messages
Explanation for the LMP process/scenario:
When an IPL occurs, the keys dataset is read in during the CAS9 process.
Every key in the member is interrogated, you will receive messages
CAS9115I - INPUT: PROD(xx) DATE(ddMONyy) CPU(nnnn-yyy /zzzzzz) LMPCODE(*******)
CAS9190I - PRODUCT (xx) KEY ACCEPTED FOR THIS CPU
(once a key is accepted for the z/OS image in question).
An LMP call is made by a CA product (via batch submission or online by panel usage).
If there is a valid LMP key (loaded into CSA/ECSA), processing continues without any interruption/messages.
If there is NO valid LMP key, CAS9180E occurs i.e. lmp key required for PRODUCT xx. This reflect on the product abbreviation xx.
You find the CAS9180E via the console log, look up a few lines, and see what batch job (and user) submitted this.
There will be a library in linklist, steplib or tso logon, which is allowing the above to occur.
Every 15 minutes thereafter CAS9012A/CAS9013A are issued.
CA COMMON SERVICES does not disable any CA SOLUTIONS.
We display warning message in regular intervals (CAS9012A/CAS9013A).
This process has been changed a bit since COMMON SERVICES r11.0 GEN SP07.
A security violation occurs at a certain time (CAS9180E FIRST, then CAS9012A/CAS9013A every 15 minutes after that).
If no additional security violations occur for the same product (additional submissions of batch jobs, or access to panels) CAS9012A/CAS9013A will stop
after 24 hours.
Of course, if another key violation occurs, the 24 hour clock is started again (from the point of the new violation).
Activation of an EKG CODE (via a CAS9 EXECUTION) will not stop CAS9012A/CAS9013A from occurring (BY DESIGN).
There are two ways to address the above:
IPL (with an EKG CODE is required to stop CAS9180E/CAS9012A/CAS9013A from occurring.
- The second way to address the above LMP WARNING messages is to execute CAS9 with temporary LMP keys for product.