What to do when getting messages CAS9180E/CAS9181A/CAS9012A/CAS9013A

Products

• Common Components and Services for z/OS
• Common Services

Issue/Introduction

You are currently seeing the following alerts in the system log:

• CAS9012A nnnnn Key warnings/violations on CPU nnnnnn
• CAS9013A Product xx about to expire or is expired and is in use

These alerts are related to PROD(xx). However, you have already verified there are no PROD(xx) keys defined in the Keys member.

You also believe that the product is not required in your environment, and you would like to stop/remove these alerts from appearing in the logs.

You suspected the product might still be referenced somewhere, but unable to identify the source.

You are looking for guidance on how to identify the source of these alerts and permanently stop/remove them?

Cause

Explanation for the licensing (LMP) process/scenario:

• When an IPL occurs, the KEYS file is read in during the execution of the CAS9 procedure.
  
  
• As every key in the member is interrogated, you will receive messages as each key is successfully processed:

 	CAS9115I - INPUT: PROD(xx) DATE(ddMONyy) CPU(nnnn-yyy /zzzzzz) LMPCODE(*******)
        CAS9190I - PRODUCT (xx) KEY ACCEPTED FOR THIS CPU

• 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, a CAS9180E violation message occurs for the product that issued the license check.
  
  
• Once a violation occurs, every 15 minutes thereafter the CAS9012A/CAS9013A warning messages are issued.
  
  
• Keep in mind that despite the violation/warning messages, Common Services will not disable any functionality of the solution in violation.
  
  
• If no additional security violations (CAS9180E messages) occur for the same product (additional submissions of batch jobs, or access to panels) the CAS9012A/CAS9013A warning messages will stop after 24 hours. Of course, if another key violation occurs, the 24 hour clock is restarted (from the point of the new violation).

Resolution

Search the system log for the CAS9180E violation message. You should be able to relate it to a user or job. If necessary look back a few lines to identify who or what issued the license check. Once identified, the appropriate action should be taken to prevent future violations.

There are two ways to address the above:

1. Contact the Broadcom License Team to request a valid LMP key for the product and then execute CAS9 to activate/load the key
2. Contact the Broadcom License Team to request an EKG code. Then IPL with the EKG code to stop CAS9180E/CAS9012A/CAS9013A from occurring. 
   • Activation of an EKG CODE (via a CAS9 execution) will not stop CAS9012A/CAS9013A from occurring.

Additional Information

Refer to the Common Components and Services for z/OS documentation for information related to LMP and CAIRIM

Here you can find information in relation to:

• How LMP works
• Add Product License Keys
• Load Product License Keys
• Use Emergency Key Generator (EKG)
• more...