Previous Topic: Start CA MII with the Address Space Creation UtilityNext Topic: Review MIMGLOBL DASD Control File Serialization


Place License Keys in the CA Common Services PPOPTION Data Set

During startup, CA MIM license validation is performed by calling CA LMP service of the CAIRIM component of CCS. For information about installing CAIRIM, activating CA LMP, and coding CA LMP keys, see the CA Common Services for z/OS documentation.

Place CA LMP keys for each of the CA MIM components (CA MIA, CA MIC, CA MII) that you intend to activate in the KEYS member of the PPOPTION data set, found in the CAS9 JCL procedure.

Follow these steps:

  1. Examine the CA LMP Key Certificate you received with your CA MIM installation or maintenance tape.

    Your certificate contains the following information:

    Product Name

    Specifies the trademarked or registered name of CA MIM as licensed for the designated site and CPUs.

    Product Code

    Specifies a two-character code that corresponds to the CA MIM facility.

    Supplement

    Specifies the reference number of your license for the particular CA MIM facility in the format:

    nnnnnn - nnn
    

    This format differs slightly inside and outside North America, and in some cases may not be provided at all.

    CPU ID

    Identifies the specific CPU for which installation of CA MIM is valid.

    Execution Key

    Specifies an encrypted code required by CA LMP for CA MIM installation. During installation, it is referred to as the LMP code.

    Expiration Date

    Specifies the date your license for CA MIM expires. It is of the format: ddmmmyy, as in 27JAN13.

    Technical Contact

    Specifies the name of the designated technical contact at your site who is responsible for installation and maintenance of CA MIM. This is the person to whom CA addresses all CA LMP correspondence.

    MIS Director

    Specifies the name of the Director of MIS or the person who performs such a function at your site. If the title, but not the name of the individual is indicated on the certificate, then you should supply the actual name when correcting and verifying the certificate.

    CPU Location

    Specifies the address of the building in which the CPU is installed.

  2. Define a CA LMP Execution Key to the CAIRIM parameters by modifying member KEYS in CAI.PPOPTION.

    The parameter structure for member KEYS is:

    PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)
    LMPCODE(kkkkkkkkkkkkkkkk)
    
    pp

    Specifies the two-character product code. This code is the same as the product code already in use by the CAIRIM initialization parameters for any earlier releases of CA MIM (if applicable). This is required.

    Valid values for pp are as follows:

    1A - CA MIA (GTAF and TPCF)

    1C - CA MIC (GCMF)

    1D - CA MII (GDIF, ECMF, and EDIF)

    1F - CA MIC (ICMF)

    ddmmmyy

    Specifies the CA LMP licensing agreement expiration date.

    tttt-mmmm

    Specifies the CPU type and model on which CA LMP is to run (for example, 2094-712). If the CPU type, model, or both, require less than four characters, then blank spaces are inserted for the unused characters. This is required.

    ssssss

    Specifies the serial number of the CPU on which CA LMP is to run. This is required.

    kkkkkkkkkkkkkkkk

    Specifies the execution key needed to run CA LMP. This CA LMP execution key is provided on the Key Certificate shipped with each CA LMP software solution.

Example: Code CA LMP Key

The following example shows you how to code a control statement for the CA LMP execution software parameter.

Note: The product code and execution key value will be different when you install CA MIM at your site.

PROD(1B) DATE (27MAR08) CPU(2094-712 /999999) 
LMPCODE(52H2K06130Z7RZD6)