Common Services for z/OS uses the KEYS member of the CAS9 proc to validate licensed CA Software. Are product license keys (LMP) dependent upon CPU model number?

Document ID : KB000015646
Last Modified Date : 14/02/2018
Show Technical Document Details

CA LMP (License Management Program), a subcomponent of the Common Services for z/OS CAIRIM component, provides a standardized method of tracking licensed CA software.  LMP is used to verify the CA Software executing on a specific CPU is licensed for that specific machine.  

The format of each key consists of the following:
       PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkkk)

  • PROD - two character product code
  • DATE - the expiration date of the licensing agreement in the format of
    •  01JAN17 = January 1, 2017
      • the two character year assumes 20xx where xx=the last two digits of the year ie. 17 = 2017.
  • CPU
    • tttt=type
    • mmmm=model
    • ssssss=serial number
    • kkkkkkkkkkkkkkkk = the execution key used to run the software solution  



The CPU model and serial number are included in each LMP key.  Are any CA product license keys dependent upon the model number?  

CA Common Services for zOS executing the License Management Program (LMP) as part of the CAIRIM (Resource Initialization Manager) on a specific CPU.

Other than verifying the licensing of the CA Solution(s) executing on a specific CPU, there is no dependency upon the CPU model itself. The serial number and model of the CPU portion of the key are generated based upon information provided by the customer.

Additional Information:

Information about the use, format, and purpose of the License Management Program can be found in the Common Services r14.1 documentation wiki.