CA Common Services for z/OS Requirements

2
ce17
2
 
 
CA Endevor SCM uses CA Common Services (CCS) for product licensing and authorization. CCS is a group of system services that protect your investment in software products by helping to manage your data center more efficiently.
The CCS components used by CA Endevor SCM include CAIRIM, CA LMP, and CAIENF. These services help you run CA Endevor SCM.
CAIENF and CAICCI are required only if you want to use the Concurrent Action Processing feature, the Web Services component, or the CA CM Enterprise Workbench product. For more information about CA Common Services for Web Services, see How to Enable CA Common Services for Web Services.
If other CA products are installed at your site, some of these services may be installed.
If your site is running CAIENF Verison 12 or higher, a database is not required for Concurrent Action Processing or Web Services.
CAIRIM
 
 
CA Endevor SCM uses the CA Common Services Resource Initialization Manager (CAIRIM) component for product license authorization. CAIRIM routines are grouped under CA z/OS Dynamic Service Code S910.
CAIRIM is mandatory for CA Endevor SCM. CAIRIM must be installed and started with CA Endevor SCM within 30 minutes of IPL. CAIRIM is part of CCS. For more information about the features and associated utilities of CAIRIM, see CA Common Services for z/OS Getting Started.
CA LMP
 
 
CA Endevor SCM requires the proper level of the CA License Maintenance Program (LMP) to initialize correctly. CA LMP, which provides a standardized, automated approach to the tracking of licensed software, is provided as an integral part of CAIRIM.
The CA License Management Program uses common real-time enforcement software to validate the user's configuration. CA LMP reports on license, usage, and financial activities of CA Endevor SCM. The routines that accomplish this are integrated into the CA z/OS dynamic service code S910 (the CAIRIM service).
Some of the features of CA LMP include:
  • Common key data set can be shared among many CPUs.
  • Check digits
    are used to detect errors in transcribing key information.
  • Execution keys can be entered without affecting any CA software solutions running.
  • No special maintenance requirements exist.
For more information about defining the CA LMP execution key to the CAIRIM parameters, see CA Common Services for z/OS Getting Started.
The LMP Key Certificate
 
 
Examine the CA LMP Key Certificate you received with your CA Endevor SCM installation or maintenance cartridge. Your certificate contains the following information:
  • Product Name
    The trademarked or registered name of CA Endevor SCM as licensed for the designated site and CPUs.
  • Product Code
    A two-character code that corresponds to one or more CA Endevor SCM features.
  • Supplement
    The reference number of your license for the particular CA Endevor SCM feature, if applicable.
  • CPU ID
    The code that identifies the specific CPU for which the installation of CA Endevor SCM is valid.
  • Execution Key
    An encrypted code required by CA LMP for product initialization. Also referred to as the LMP CODE.
  • Expiration Date
    The date your license for CA Endevor SCM expires in the format
    ddmmmyy
    .
  • Contact Technical
    The name of the designated technical contact at your site, who is responsible for installation and maintenance of CA Endevor SCM. This is the person to whom CA addresses all CA LMP correspondence.
  • MIS Director
    The name of the Director of MIS, or the person who performs this function at your site. If the title, but not an individual's name, is indicated on the certificate, you should supply the actual name when correcting and verifying the certificate.
  • CPU Location
    The address of the building in which the CPU is installed.
LMP Execution Keys
 
 
Add the CA LMP Execution Keys provided on the Key Certificate to the CAIRIM parameters to ensure proper initialization of CA Endevor SCM. To define a CA LMP Execution Key, modify member KEYS in CALPPOPTION.
The following information shows the syntax for statements in the KEYS member and describes the individual parameters:
PROD(
pp
) DATE(
ddmmmyy
) CPU(
tttt
-
mmmm
/
ssssss
) LMPCODE(
kkkkkkkkkkkkkkkk
)
  • pp
    The two-character product code. This required code matches the product code in use by CAIRIM for any earlier versions of CA Endevor SCM, if applicable.
  • ddmmmyy
    The licensing agreement expiration date.
  • tttt-mmmm
    The CPU type and model on which the product is to run. If the CPU type or model requires less than four characters, use blanks for the unused characters. This is a required parameter.
  • ssssss
    The serial number on which the product is to execute. This is a required parameter.
  • kkkkkkkkkkkkkkkk
    The Execution Key required to run the product. This key is provided on the Key Certificate shipped with each CA software solution.
This is an example LMP KEYS entry. The product code and execution key values will differ in your installation. Note the trailing blank in the CPU model number.
PROD(ZZ) DATE(08DEC99) CPU(3090-600 /370623) LMPCODE(0408A0423C0123EF)
For more information about defining the CA LMP Execution Key to CAIRIM, see CA Common Services for z/OS Getting Started.
Verification of the LMP Execution Keys Installation
 
 
Before enabling the test environment, ensure that all necessary CA Common Services LMP Execution Keys have been installed as described in CA Common Services for z/OS Getting Started. You can use the same execution key being used for your production environment; a new key is not required when upgrading to a newer release of the product.
Some users may not be licensed for all features of the product. The demonstration job stream that is part of this phase uses facilities from all features of CA Endevor SCM.
Ensure that a valid CA LMP Execution Key, supplied by CA, has been specified to the CA Common Services CAIRIM licensing component.
If you do not have a full feature execution key, you can obtain a temporary one by contacting the CA LMP support group at http://ca.com/support.
LMP Key Requirements
 
mfgii
The CA License Management Program (CA LMP) tracks licensed software in a standardized and automated way. CA LMP uses common real-time enforcement software to validate the user configuration. CA LMP reports on activities that are related to the license, usage, and financials of CA Technologies products.
Your product is licensed with an LMP key. You acquire the LMP key with one of the following methods:
For more information about LMP keys, see the CA Common Services for z/OS documentation.
Verify CA Common Services are Running
 
 
The CCS components CAIRIM, CAIENF, and CAICCI must be installed and running on your mainframe. CAIENF and CAICCI are required only if you want to use the Concurrent Action Processing feature, the Web Services component, or the companion product CA CMEW. If they are not installed and running, install these services according to the instructions in CA Common Services for z/OS Getting Started
.
Follow these steps:
  1. Go to the SDSF status display and enter the prefix ENF*.
    If you do not see ENF* active on your system, contact your systems programmer to start it.
  2. If the job is running, select it and search for (Find) CAICCI within the job.
    • If you find CAICCI, CAIENF and CAICCI are running.
    • If you do not find CAICCI, check the site CAI.CAIPROC library to see if the ENF member has been modified to run CAICCI at your site.
      If the ENF member does not exist, contact your CCS administrator (or systems programmer) to determine the status of CAIRIM, CAIENF, and CAICCI on your system.