Requirements for CA Datacom Server

Review the following requirements prior to installing dsv:
cadts
Review the following requirements prior to installing
CA Datacom Server
:
Hardware Requirements
The hardware requirements for the mainframe portion of the 
CA Datacom Server
are as follows:
  • Requires an IBM or compatible mainframe computer.
  • Is distributed by electronic delivery through CA CSM, from the
    Broadcom
    Online.
Software Requirements
The software requirements for
CA Datacom Server
are as follows:
  • CA Datacom/DB
    Version 14.0 or Version 15.x with the SQL Option must be installed.
    The Multi-User Facility that supports a
    CA Datacom Server
    must be active for the
    CA Datacom Server
    to run and must contain the following SYSIN statement in its startup job:
                DATACOM     DTCMSRVR    
  • A version of z/OS as supported by IBM.
  • SMP/E Release 1.8.1 or later must be installed prior to installation.
  • If you are installing the UNIX System Services (USS) component, you must have IBM USS installed.
  • If you are installing the USS component, you must have at least JRE 6 installed on USS.
    CA Datacom Server
    15.x is incompatible with any previous Java Runtime Environments.
  • The CA Common Services for z/OS components that are used by this product are the following:
    • CAICCI is required on the mainframe if implementing CCI communication. However, CAICCI (CCIPCSSL) is optional on a client except when using CCI communication.
    • CAIENF (required)
    • CAIRIM (required), and its subcomponent CA LMP
    • CAISSF (required if security validation will be utilized, otherwise, CAISSF is optional)
    If you are installing the component for USS, the CAICCI component is optional.
  • When running with CA ACF2, CA Top Secret, or IBM RACF, the server must be set up to communicate with the external security package.
CA Common Services for z/OS
CA Common Services for z/OS is a group of system services that protect your investment in products by helping you manage your data center more efficiently. Each service provided by CA Common Services for z/OS offers individual benefits. The following components are used with this product:
  • CAICCI lets
    CA Datacom/DB
    products work together across platforms.
  • CAIENF, CAIRIM, and CA LMP assist you in getting your products running and keeping them running.
  • CAISSF enables your products to offer standardized security interfaces.
CAICCI
CAICCI, CAI Common Communications Interface, enables CA products to communicate with one another. This facility provides a layer that isolates application software from the specifics of the communications environment. Some of the features include:
  • Single point of control
  • Multiple platform support
  • Performance optimization
  • Peer-to-peer (program-to-program) communication
  • Parallel conversations
  • Dynamic installation configuration
  • Ease of customization
  • Error handling
CAIENF
The CAI Event Notification Facility (CAIENF) is an operating system interface service that offers a simple and flexible approach for CA products to obtain data from z/OS. By centralizing operating system interfaces within CAIENF, many features that were formerly available within a single product can be shared across the entire product line. CAIENF features include the following:
  • Dynamic installation and reconfiguration
  • True recovery from system or individual power outages
  • High performance asynchronous processing
  • Single interface between CA products and operating system data
  • Built-in diagnostic aids
  • Ease of customization
  • Exploitation of relational database technology
CAIRIM
The 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 system software. CAIRIM features include the following:
  • Obtaining SMF data
  • Verification of proper software installation
  • Installation of z/OS interfaces
  • Automatic startup of CA and other vendor products
  • Proper timing and order of initialization
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. CA LMP features include the following:
  • Common key data set that can be shared among many CPUs
  • Check digits detects errors in transcribing key information
  • Execution keys you can enter without affecting any CA product already running
  • No special maintenance requirements
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, and can interface with CA security products (CA ACF2 or CA Top Secret) or compatible non-CA security products.
For CA security products, CAISSF features include the following:
  • A single security mechanism
  • Isolation of CA products from CA or vendor mechanisms
For non-CA security products, CAISSF features include the following:
  • Resource class translation
  • Access level translation
  • Selective logging of requests
  • Request type control
  • Message support for failed access
CA LMP Tracks Licensed Software
CA Datacom Server
requires CA LMP to initialize correctly. CA LMP provides a standardized and automated approach to the tracking of licensed software.
The DATACOM startup option specifies the licensed CA products that will execute with this Multi-User Facility. These features will be verified as licensed for execution by CA LMP.
Key Certificate
Examine the CA LMP Key Certificate you received with your product installation package. The certificate contains the following information:
  • Product Name
    Specifies the trademarked or registered name of the product licensed for the designated site and CPUs.
  • Supplement
    Specifies the reference number (in the format
    nnnnnn - nnn
    ) of your license for the particular product. This format differs slightly inside and outside of North America, and in some cases may not be provided at all.
  • Expiration Date
    Specifies the date (
    month dd, yyyy
    , as in July 10, 2007) your license for this product expires.
  • Technical Contact
    Specifies the name of the technical contact at your site who is responsible for the installation and maintenance of the designated product. CA addresses all CA LMP correspondence to this person.
  • MIS Director
    Specifies the name of the Director of MIS or the person who performs that function at the site. If the title, but not the name of the person, is indicated on the Certificate, supply the actual name when correcting and verifying the Certificate.
  • CPU Location
    Specifies the address of the building where the CPU is installed.
  • Execution Key
    Specifies an encrypted code required by CA LMP for product initialization. During installation, it is referred to as the LMP Code.
  • Product Code
    Specifies the two-character code that corresponds to this particular product.
  • CPU ID
    Identifies the specific CPU for which installation of your product is valid.
 
How the CA LMP Execution Key is Defined
The CA LMP execution key, provided on the Key Certificate, must be added to the CAIRIM parameters to ensure proper initialization of all CA products. To define a CA LMP execution key to the CAIRIM parameters, modify member KEYS in the OPTLIB data set. Parameter structure for member KEYS appears following:
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-600) on which the CA LMP product will run. 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 will run.
  • kkkkkkkkkkkkkkkk
    Specifies the execution key needed to run the CA LMP product. The CA LMP execution key is provided on the Key Certificate shipped with each CA LMP product.
In this example of a control card for the CA LMP execution software parameter, the execution key value is invalid and provided
as an example only.
PROD(YT) DATE(15JAN07) CPU(3090-600 /370623) LMPCODE(52H2K06130Z7RZD6)
For a description of the procedure for defining the CA LMP execution key to the CAIRIM parameters, see the CA Common Services for z/OS Getting Started documentation.
 
Storage Requirements
CA Datacom Server
operates on any processor and with any DASD device supported by your operating system and your current release of
CA Datacom/DB
. The following tables indicate the estimated blocks of DASD space
CA Datacom Server
requires. Each data set, library, or database name is preceded by its high-level qualifier (such as CAI.HLQ or CAI.SHLQ).
Library Allocation
The library allocation for
CA Datacom Server
is displayed in the following table:
LIBRARY NAME
TRKS
SAMPJCL
11
Headings
The VOLUME column heading on the following tables refers to the VOLSER from the installation worksheet. The TRKS heading refers to the number of tracks used with DASD type 3390.
SMP/E CSI and Data Sets
The SMP/E CSI and data sets for
CA Datacom Server
are displayed in the following table. These are required only if you are creating a new SMP/E environment
.
Data Sets
 
TRKS
SMPCSI.CSI
VS KSDS
 
SMPCSI.CSI.DATA
 
225
SMPCSI.CSI.INDEX
 
2
SMPLTS
 
75
SMPMTS
 
75
SMPPTS
 
75
SMPSCDS
 
120
SMPSTS
 
75
SMPPTS1
 
75
SMPLOG
 
75
SMPLOGA
 
75
Base Distribution Libraries
The base distribution libraries for
CA Datacom Server
are displayed in the following table.
Base Distribution Libraries
TRKS
AAYTHFS
245
AAYTMAC
18
AAYTMOD0
58
AAYTXML
20
Target Libraries
The target libraries for
CA Datacom Server
are displayed in the following table:
Target Libraries
TRKS
CAYTLOAD
49
CAYTLPA
10
CAYTMAC
23
CAYTXML
20
Installation Tape Contents
The contents of the installation tape are displayed in the following table:
File
Data Set Name
Description
1
CAI.INSTALL
Unused
2
CAI.IE21.CLIST
Unused
3
CAI.IE21.ISPMLIB
Unused
4
CAI.IE21.ISPPLIB
Unused
5
CAI.IE21.ISPSLIB
Unused
6
CAI.IE21.ISPTLIB
Unused
7
CAI.IE21.LOADLIB
Unused
8
CAI.IE21.PIMLIB
Unused
9
CAI.SAMPJCL
Sample JCL PDS
10-31
 
Unused
32
SMPMCS
SMP/E Modification Control Statements
33
CYTB000.F1
Relfile 1
34
CYTB000.F2
Relfile2
35
CYTB010.F1
Relfile for USS components
36
CYTB020.F1
Relfile for CAECIS