Receiving new LMP keys in a SITEID format and curious if the information in the keys is correct.
For example:
***************************** Top of Data ******************************
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
SITEID(12345678) SITECODE(sitecode) NAME(CompanyName)
PROD(1R) DATE(31DEC24) CPU(*SITE*-/12345678) LMPCODE(lmpcode)
**************************** Bottom of Data ****************************
Release : All
Component : CA COMMON SERVICES FOR Z/OS
Changes with the acquisition from CA by Broadcom. There was a change to another licensing application.
The SITEID previously received was only 6 number, or the 6 preceded by 2 zeros.The license process has changed and now the site-id's are 8 characters.The example shows that NAME is defined on a separate line. This is done for consistency as some customers will have a NAME that is too long to fit on the same line. In order for the NAME to be read as part of the SITEID and SITECODE, it is required to specify the dash character, '-' , in column #72. Also the CPU parameter in the Product statement needs to have as first value (before the slash) the contents '*SITE*-' (without the quotes). The second part of the CPU parameter (after the slash) , its also needed to specify the same 8 character SITEID as specified on your SITEID card. Put the new keys int the KEYS member and the SITEID statement should be the first statement (after the comments, when available) in the member. The current keys can be left in the same member. CAIRIM/CAS9 will check them until it finds the valid once. After adding the new keys, load the new LMP keys by entering the command :
S CAS9,,,LMPKEYS
Benefits:
1. The new LMP keys that are based on SITEID/SITECODES can be used in DR exercises without requesting for a new/different one from Broadcom as it's not based on CPU id.
2. The new LMP keys that are based on SITEID/SITECODES can be used after CPU upgrades without requesting for a new/different one from Broadcom as it's not based on CPU id.