Requirements for CA Ideal for CA Datacom

Review the following requirements prior to installing idcm:
cadts
Review the following requirements prior to installing 
CA Ideal for CA Datacom
:
Hardware Requirements
CA Ideal for CA Datacom
requires an IBM or compatible mainframe computer.
If you are installing from tape, a tape drive capable of reading a 3480 cartridge is required.
Software Requirements
The following are the software requirements for a z/OS environment:
  • IBM z/OS operating system with UNIX System Services (USS) is required.
  • IBM SMP/E at the releases supported by IBM is required.
  • IBM CICS Transaction Server at the releases supported by IBM is required.
  • CA Common Services is required. It must be installed before
    CA Ideal for CA Datacom
     is installed.
  • CA IPC
    Version 15.0 is required. It must be installed before
    CA Ideal for CA Datacom
     is installed.
  • CA Datacom/DB
    Version 15.0 or higher is required for
    CA Ideal for CA Datacom
    . The
    CA Datacom/DB
    Multi-User Facility must be active. 
    • This requires the successful completion of the 
      CA Datacom
       14.0 to 15.0/15,1 Core Products upgrade, specifically including the Datadictionary upgrade portion that adds the new DOCUMENT entity-type.
  • For
    CA Ideal for CA Datacom
     for DB2 sites that use
    CA Datacom/AD
    for the dictionary, this must be at Version 15.0. For more information, see the article about CA Ideal Option for DB2 and CA Datacom/AD 14.0 to CA Datacom/AD 15.0 Upgrade.
  • CA Datacom CICS Services
    is required.
    CA Ideal™ for DB2
    users have this already installed as part of their
    CA Datacom/AD
    system.
  • CA Ideal™ for DB2
    requires IBM DB2 at a release currently supported by IBM.
DASD Requirements
SMP/E CSI and Data Sets
The following tracks are needed for both new and upgrade installs:
Name
3390 TRKS
SMPCSI.CSI
 
SMPCSI.CSI.DATA
225
SMPCSI.CSI.INDEX
2
SMPLTS
75
SMPSCDS
120
SMPMTS
75
SMPPTS
75
SMPSTS
75
SMPLOG
75
SMPLOGA
75
SAMPJCL
11
SMPPTS1
75
Total
883
Target Libraries
The following tracks are needed for both new and upgrade installs.
Name
3390 Tracks
CAILLOAD
236
CAILMAC
51
CAILLPA
10
CAILSAMP
117
CAILXML
20
CAILDATV
190
Total
624
Custom Libraries
The following tracks are needed for both new and upgrade installs.
Name
Volume
3390 Tracks
CUSPROC
DASD02
30
CUSLIB
DASD02
30
CUSMAC
DASD02
30
Total
 
90
Distribution Libraries
The following tracks are needed for both new and upgrade installs.
Name
3390 Tracks
AAILMAC
51
AAILMOD0
203
AAILXML
20
AAILSAMP
117
AAILDATV
190
Total
581
VLS Data Sets
The following tracks are needed for both new and upgrade installs.
If you are upgrading, you may already have these.
Name
Volume
3390 Tracks
IDDAT
DASD04
26
IDDVW
DASD04
50
ID$IDSRC
DASD04
58
ID$IDPNL
DASD04
25
ID$IDOBJ
DASD04
67
Total
 
226
DB2 Only Data Sets
The following tracks are needed for both new and upgrade installs.
Name
Volume
3390 Tracks
ILDB2.DBRM
DASD03
3
Total
 
3
Introduction to CA Common Services
To help you understand all that the CA Common Services offer, this section briefly describes each service that
CA Ideal for CA Datacom
uses.
CA Common Services is a group of system services that protect your investment in products by helping you manage your data center more efficiently. Each of the CA Common Services offers individual benefits. The following CA Common Services components are used with and benefit the
CA Ideal for CA Datacom
product:
  • CA LMP and CAIRIM assists you in getting your CA products running and in keeping them running.
  • CAISSF enables your CA products to offer standardized security interfaces.
The remaining pages of this chapter describe these services in more detail.
CA LMP
The CA License Management Program (CA LMP) provides a standardized and automated approach to the tracking of licensed software. It uses common real time enforcement software to validate user configuration. CA LMP reports on activities related to the license, usage, and financials of your CA products. The routines which accomplish this are integrated into the CA z/OS dynamic service code, S910 (CAIRIM). CA LMP features include:
  • Common key data set which can be shared among many CPUs
  • “Check digits” used to detect errors in transcribing key information
  • Execution keys you can enter without affecting any CA products already running
  • No special maintenance requirements
CAIRIM
CAI Resource Initialization Manager (CAIRIM) is the common driver for a collection of dynamic initialization routines that eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements commonly encountered when installing systems software. These routines are grouped under the CA dynamic service code, S910. CAIRIM features include:
  • Obtaining SMF data
  • Verifying proper software installation
  • Installing z/OS interfaces
  • Automatically starting up CA and other vendor products
  • Ensuring proper timing and order of initialization
CAISSF
The CAI Standard Security Facility (CAISSF) allows CA products to offer standardized security interfaces without regard to the particular needs of underlying access control software. CAISSF offers user authentication and resource access validation facilities. It can interface with CA external security products or compatible security products that are not from CA. CAISSF is a subservice contained in the CA service code, S910 (CAIRIM).
For CA security products, CAISSF features include:
  • A single security mechanism
  • Isolation of CA products from CA or vendor mechanisms
For security products that are not from CA, CAISSF features include:
  • Resource class translation
  • Access level translation
  • Selective logging of requests
  • Request type control
  • Message support for failed access
Using CA LMP
CA Ideal requires CA LMP to initialize correctly. CA LMP also provides a standardized and automated approach to the tracking of licensed software.
Examine the CA LMP Key Certificate you received with your product installation package. The Key Certificate contains the following information.
Defining KEYS
Proper initialization of any CA product requires the addition of the CA LMP execution key provided on the Key Certificate to the CAIRIM parameters. To define a CA LMP execution key to the CAIRIM parameters, modify member KEYS in the OPTLIB data set. This is the parameter structure of member KEYS:
PROD(
pp
) DATE(
ddmmmyy
) CPU(
tttt-mmmm
/
ssssss
) LMPCODE(
kkkkkkkkkkkkkkkk
)
  • pp
    Specifies the two-character product code. For any given CA LMP product, this code agrees with the product code already in use by the CAIRIM initialization parameters for earlier genlevels of the product.
  • ddmmmyy
    Specifies the CA LMP licensing agreement expiration date.
  • tttt-mmmm
    Specifies the CPU type and model (for example, 3090&@@endash.600) on which the CA LMP product runs. If the CPU type, model, or both require less than four characters, blank spaces are inserted for the unused characters.
  • ssssss
    Specifies the serial number of the CPU on which the CA LMP product runs.
  • kkkkkkkkkkkkkkkk
    Specifies the execution key needed to run the CA LMP product. This CA LMP execution key is provided on the Key Certificate shipped with each CA LMP product.
Example
In this example, the CA LMP execution key value is invalid and provided as an example only.
PROD(
IL
) DATE(
15JAN06
) CPU(
3090-600 /370623
) LMPCODE(
52H2K06130Z7RZD6
)
For more information about the procedure for defining the CA LMP execution key to the CAIRIM parameters, see the CA Common Services for z/OS Installation and Maintenance documentation.
CA Common Services Requirements
The following CA Common Services are used with your product:
  • CAIRIM
  • CAICCI
  • CA LMP
If other
products are installed at your site, some of these services are already installed.
LMP Key Requirements
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
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.
Security Requirements
To complete the tasks that are described in this documentation, you need sufficient security privileges.
For example:
For the DB2 option, you need BINDADD authority to create the installation and development plans. If this is a new installation, not an upgrade, then you also need DBCREATE authority to create the dictionary extension tables.