The product requires some of the following CA Common Services, and others are optional.
CA-C Runtime is a runtime facility with reentry capabilities. Its modular architecture insulates the CA-C Runtime programs from system and version dependencies. Little, if any, system-dependent code is linked with the user program. This method allows for smaller user programs and easier maintenance. CA-C Runtime uses a memory manager to handle the dynamic allocation requests for small pieces of storage. This manager enables fewer calls to be made on the operating system resulting in faster allocation and deallocation.
Several CA Common Services require the CA-C Runtime service, and it is required when you use the CA 7® Web Client.
CA Datacom/AD Version 14.0 is a common database component that several CA Technologies products like CA Workload Automation CA 7® Edition, CA Workload Automation Restart Option for z/OS Schedulers, and CA CSM use. CA WA CA 7 Edition uses CA Datacom/AD as the major component of its database, which contains both the Definition database and the Active Workload (Queues) database. Both parts are saved into one logical database within Database ID (DBID) 770. Each logical database represents a CA 7 instance. DBID 770 can support several logical databases and thus multiple CA 7 instances. When planning for the database sizing and backup/recovery, remember that multiple CA 7 instances can reside within this single DBID 770.
Use the CA Support Online site to download these PTFs from the CA Datacom/AD pages. Ensure that your maintenance is as current as possible for CA Datacom/AD.
CAICCI, CAI Common Communications Interface, is a communications facility. CAICCI offers a simple yet flexible approach enabling CA Technologies solutions to communicate with one another. This facility provides a layer that isolates your application software from the specifics of the communications environment.
This service is required for several interfaces, including:
CAIENF, CA Technologies Event Notification Facility, is an operating system interface service. CAIENF offers a simple yet flexible approach for CA Technologies solutions to obtain data from the operating system. CAIENF centralizes operating system interfaces. CAIENF includes many features that were formerly available within a single solution can be shared across the entire product line.
This service is required for several interfaces including:
CAIRIM, CAI Resource Initialization Manager, is a required service and the common driver for a collection of dynamic initialization routines. The routines eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements that are commonly encountered when installing systems software.
CAISSF, CAI Standard Security Facility, is a required service. CAISSF lets CA Technologies software offer standardized security interfaces regardless of the underlying access control software. CAISSF offers user authentication and resource access validation facilities. CAISSF can interface with CA Technologies security products, CA ACF2™ or CA Top Secret®, or compatible security products other than CA Technologies. CAISSF is a subservice that is contained within the CAIRIM service.
The CA Earl™ (Easy Access Report Language) Reporting Component is a user-friendly report definition facility with the power of a comprehensive programming system. CA Earl lets you modify and print the contents and layout of a predefined CA Technologies product report using English-like statements.
The CA Earl Service is required to produce CA Workload Automation CA 7® Edition reports using the CA Earl facilities.
CA Easytrieve® is a user-friendly report definition facility with the power of a comprehensive programming system. CA Easytrieve lets you modify and print the contents and layout of a predefined CA Technologies product report using English-like statements.
CA Easytrieve is required to produce CA Workload Automation CA 7® Edition reports using the CA Easytrieve facilities.
CAISDI provides a set of services that open CA Service Desk requests from the z/OS environment. CA Technologies products can open the requests directly, or they can be opened on their behalf. The method of opening requests depends on the requirements of each specific product using the interface. Three main components are involved in this interface. Depending on each individual CA Technologies product using CAISDI, one or more of these components is required. We recommend that you install all three components. In the configuration steps, you can decide to configure only the components you currently need.
This service is required for the CAISDI/els (Event Library Support) component of the CA Service Desk integration feature.
The JCLCheck Common Component is a reduced version of CA JCLCheck™ Workload Automation. The JCLCheck Common Component provides the z/OS JCL statement syntax and execution validation functions to other CA Technologies products.
Some sites have installed the full CA JCLCheck product or the JCLCheck Common Component for another CA Technologies product. CA Workload Automation CA 7® Edition expects CA JCLCheck to be at Version 12.0 or higher.
For the sites other than those sites with the full CA JCLCheck product, the JCLCheck Common Component is provided without charge. The JCLCheck Common Component can be used only from another CA Technologies product.
The JCLCheck Common Component software is found in a separate distribution package.
The Cross-Platform Scheduling Common component lets CA Workload Automation CA 7® Edition receive cross-platform scheduling requests from other CA Technologies solutions like CA Workload Automation AE. The Cross-Platform Scheduling Common component is also described as the Cross-Platform Router or XPS Router. The XPS Router is designed to work with the CA Workload Automation systems that use CAICCI as the form of cross-system communication.
On z/OS systems, the cross-platform scheduling router receives all requests for work from other systems. The router then routes each request to the appropriate CA scheduling solution on that system. The CA scheduling solution generates the feedback information (job initiation, termination, failure) that is used to create CAIENF cross-platform feedback events (CAXPSFBK). The cross-platform scheduling router intercepts these events and sends the feedback to the original requester. Logging this information in CAIENF also prevents the loss of feedback data when communications problems interrupt the links among platforms. When the link is reestablished, the cross-platform scheduling router can retrieve the logged feedback events from CAIENF. The cross-platform scheduling router sends them to the system that originated the request.
Cross-platform scheduling communication is performed by using the CA Common Communications Interface (CAICCI). A copy of CAICCI runs on each system where a CA Technologies solution requires it. The copies of CAICCI on each system communicate with each other using various protocols that are based on CAICCI control parameters. The gateway communication protocol is used for cross-platform scheduling (host-to-host connection).
This service is required for several interfaces, including:
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:
Viewpoint is a windowed execution environment for mainframe systems. Viewpoint uses SAA/CUA standards to enhance the integration of your CA Technologies products.
The Viewpoint service is required when you have CA 7® Web Client.
The zIIP Enablement Service supplies low-level routines to let specific tasks become zIIP-enabled. These tasks are eligible to execute on a zIIP processor. This offloading lets other work execute on the main CP processors while CA WA CA 7 Edition code executes on the zIIP processor. Although there is some overhead in setting up to use zIIP processors, moving CA WA CA 7 Edition processing to zIIP usually decreases overall costs. This service is required when you specify ZIIP=YES on the INIT initialization statement.
This service is required when you plan to offload certain CA 7 subtasks onto a zIIP processor.