Common Components and Services
Requirements

Administrators review the considerations and meet the following
Common Components and Services
requirements for installing
View
,
Deliver
, and related products:
view140
Administrators review the considerations and meet the following
Common Components and Services
requirements for installing
View
,
Deliver
, and related products:
2
2
If
Common Components and Services
are not already installed on your system, you must install them before you proceed with the product installation.
Common Components and Services
must be installed or maintained at the genlevel indicated on the cover letter for the product. For more information about the
Common Components and Services
installation requirements, see the
Common Components and Services
documentation
.
We recommend that you maintain
Common Components and Services
at a current maintenance level to ensure compatibility. For the latest information about maintenance requirements, go to
Broadcom Support
Online.
If you intend to use
CSM
for your installation and maintenance tasks, there might be certain additional
Common Components and Services
requirements. For more information, see the
CSM
documentation
.
View
The following
Common Components and Services
are used with
View
:
Note:
If other
Broadcom
products are installed at your site, some of these services may already be installed.
Deliver
The following
Common Components and Services
are used with
Deliver
:
DRAS
The following
Common Components and Services
are required for cooperative viewing with
DRAS
:
Library Authorization
View
,
Deliver
and the EBC subsystem contain authorized programs. To run successfully, these programs must be executed from an authorized library. We recommend that you authorize the CAI Common Load Library (CVDELOAD).
If other
Broadcom
products have been installed, CVDELOAD may already be authorized.
To authorize the CVDELOAD library, modify the appropriate member PROG
xx
in SYS1.PARMLIB to add an entry for CVDELOAD as follows:
APF ADD DSNAME(CAI.CVDELOAD) VOLUME(xxxxxx)
CAI.CVDELOAD is the data set name for the CAI Common Load Library, and
xxxxxx
is the volume serial number on which it resides. Use MVS system command SET PROG=xx to activate update to PROGxx.
CAICCI
CAICCI (Common Communication Interface) provides
Broadcom
enterprise applications with a wealth of capabilities, including common communications, cooperative processing, database server facilities, and distributed database management. Full support for all forms of distributed processing provides the highest degree of flexibility for the enterprise.
DRAS
uses the CAICCI service to provide communication between client applications and the servers. CAICCI is a facility that allows
Broadcom
products to communicate with other applications in a simple, straightforward manner.
CAICCI builds a layer on top of today's communication and network software so that an application can be isolated from the specifics of its environment.
Be aware of the following:
  • CAICCI must be installed into an APF (Authorized Program Facility) authorized library. The library used must be the same as the library used to install the CAIENF component.
  • CAICCI runs as a CAIENF subtask within CAIENFs address space. CAICCI uses the same database as the one allocated and initialized for CAIENF to use.
CAICCI and TCP/IP
CAICCI provides robust TCP/IP support, and this protocol can be used to efficiently connect a wide variety of platforms and applications. Mainframes, PCs, and UNIX systems can all be inter-connected, using TCP/IP.
Be aware of the following:
  • If you are using TCP/IP as your communications protocol, a mainframe TCP/IP product must be installed in addition to the base CAICCI component. Currently,
    TCPaccess
    Communications Server and IBM TCP/IP products are supported for z/OS.
  • CAICCI utilizes TCP/IP using one or more separate server address spaces to coordinate TCP/IP processing for CAICCI.
  • The CCITCP server task uses TCP/IP to support mainframe-to-PC connections and is required for
    DRAS
    .
  • Use the appropriate client/server protocol parameter, depending on the vendor for TCPIP or C runtime, as described in the
    Common Components and Services
    documentation.
CAIRIM
CAIRIM (CAI Resource Initialization Manager) is the common driver for a collection of dynamic initialization routines. These initialization routines eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements that you might commonly encounter when you install systems software.
CAIRIM prepares the operating system for
Broadcom
products and components, and then executes them.
The following is a list of some of the tasks that CAIRIM performs:
  • Obtains SMF data
  • Verifies proper software installation
  • Installs MVS interfaces
  • Automatically starts
    Broadcom
    products and the products of other vendors
  • Properly times and sets the order of the initialization
DRAS
requires CAIRIM to run the required
LMP
if
Web Viewer
Version 12.1 is in use.
Deliver
requires CAIRIM to run the required
LMP
.
CAIENF
DRAS
uses CAIENF (Event Notification Facility) services. CAIENF is an operating system interface component that provides a simple approach for
Broadcom
products to obtain data from an MVS system by interfacing to any
Broadcom
z/OS applications. This interface exploits technologies, such as relational database architectures for the benefit of the entire product line.
The level of integration is improved by enabling operating systems and
Broadcom
software-generated event information to be driven through a standard interface. This standardization simplifies multiple product-to-product interfaces and the associated necessary maintenance.
Note the following points:
  • CAIENF must be installed into an APF authorized library.
    Linklist is recommended although it is not required.
  • CAIENF runs as a started task within its own address space.
    A database must be allocated and initialized for CAIENF to use. For details about space requirements, see the
    Common Components and Services
    documentation.
DRAS
does not use the CAIENF/CICS component.
LMP
The License Management Program (
LMP
) is a standardized automated approach to the tracking of licensed software that uses common real-time enforcement software to validate the user's configuration.
LMP
reports on activities related to the license, usage, and financial activity of program solutions.
LMP
features include:
  • A common key data set that can be shared among many CPUs
  • The use of "check digits" to detect errors in transcribing key information
  • Execution keys that can be entered without affecting any
    Broadcom
    software solution already running
  • No special maintenance requirements
Acquire the LMP keys using one of these methods:
  • From your product media
  • With ESD
  • From
    Broadcom Support
Health Checker Common Service
View
and
Deliver
issue health checks and require the
CA Health Checker
Common Service modules to be available.
View
and
Deliver
link to the
CA Health Checker
Common Service product to provide standard access to the operating system's health checker services. The
CA Health Checker
Common Service runs under the IBM Health Checker for z/OS.
Note:
To successfully register
Broadcom
checks, the IBM Health Checker must be active. For more information about the IBM Health Checker, see the IBM Health Checker for z/OS User's Guide - as appropriate for your release of z/OS.