How did applications interact with CA 90s services?

CA 90s provided services through a set of system-level calls. These calls facilitated tasks such as inter-process communication, memory management, and system resource access. Specific commands and syntax varied based on the service being invoked.

What configuration files or interfaces were used by CA 90s?

Configuration was typically managed through system datasets and control files specific to each CA product utilizing CA 90s. The exact files and parameters depended on the specific product.

What types of APIs did CA 90s expose?

CA 90s did not expose APIs in the modern sense (REST, SOAP). Instead, it provided a set of system-level services accessed through internal interfaces and system calls. These were primarily used by other CA products.

What were the main architectural components of CA 90s?

The architecture of CA 90s included components such as the Common Services Manager, the Resource Manager, and various service modules. These components communicated through internal system interfaces.

How did CA 90s impact operational efficiency?

By providing common services, CA 90s helped to streamline the deployment and management of CA Technologies products on z/OS. This led to reduced operational overhead.

How did CA 90s contribute to the integration of CA Technologies products?

CA 90s facilitated the integration of various CA Technologies products, allowing them to work together seamlessly. This integration enhanced the overall functionality and value of the CA product suite.

What authentication methods were supported by CA 90s?

CA 90s relied on the security features of the z/OS operating system. It did not implement its own authentication or access control mechanisms. Security was managed at the system level.

What access control model was used?

Access control was handled through the z/OS security infrastructure, such as RACF or similar security managers. CA 90s leveraged these existing security features.

What encryption capabilities were available in CA 90s?

CA 90s did not provide built-in encryption. Security relied on the underlying z/OS security features and any encryption provided by the CA products that utilized CA 90s.

What audit and logging capabilities existed in CA 90s?

Auditing and logging were managed through the z/OS system logging facilities. CA 90s generated audit records that were integrated with the system logs.

What administrative interfaces were available for CA 90s?

Administration of CA 90s was primarily performed through the z/OS system console and through the administrative interfaces of the CA products that used CA 90s. There was no dedicated GUI or web console.

How was user management handled in CA 90s?

User management was handled through the security features of z/OS, such as RACF. CA 90s did not have its own user management system.

What were the main configuration parameters?

Configuration parameters were set through system datasets and control files specific to the CA products that utilized CA 90s. The specific parameters varied depending on the product.

What monitoring and logging capabilities existed?

Monitoring and logging were integrated with the z/OS system monitoring and logging facilities. CA 90s generated log records that could be used for monitoring.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

CA 90s

CA Technologies Not Supported z/OS

Supporting Services

Vendor

CA Technologies

Product Overview

CA 90s provided a set of common services for CA Technologies products on z/OS. The architecture included components such as the Common Services Manager, Resource Manager, and various service modules. These components communicated through internal system interfaces.

Configuration was managed through system datasets and control files specific to each CA product. Security relied on the z/OS security infrastructure, such as RACF. There were no REST or SOAP APIs.

The product is not supported. The migration path involves re-architecting applications to use the services and APIs of CA TNG Framework. This includes updating system calls to use the new framework's interfaces.

The main competing products are IBM Z solutions. A key technical difference is the architecture, with CA TNG Framework offering a more modern design. CA 90s provided a foundation for CA Technologies products, enabling them to share common services and integrate with the z/OS environment.

The migration process involves identifying all CA 90s dependencies within existing applications, assessing the impact of the transition, and re-implementing the functionality using CA TNG Framework's services. This may involve code modifications, configuration changes, and thorough testing to ensure compatibility and functionality.

Frequently Asked Questions

What was the primary purpose of CA 90s?

CA 90s provided a common set of services for various CA Technologies products on z/OS. It was designed to enable software portability across different platforms. It is no longer supported.

How was CA 90s licensed and distributed?

CA 90s was included with other CA products, and was not sold separately. It was a foundational component for many CA products, providing common services.

What was the main benefit of using CA 90s?

CA 90s was designed to facilitate the execution of the same software across different platforms. It offered a degree of platform independence for CA Technologies software.

What product replaced CA 90s?

CA 90s was superseded by CA TNG Framework. CA TNG Framework offered a more modern architecture and expanded capabilities for managing distributed environments.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

CA 90s

Product Overview

Frequently Asked Questions

What was the primary purpose of CA 90s?

How was CA 90s licensed and distributed?

What was the main benefit of using CA 90s?

What product replaced CA 90s?

How did applications interact with CA 90s services?

What configuration files or interfaces were used by CA 90s?

What types of APIs did CA 90s expose?

What were the main architectural components of CA 90s?

What was the business value of CA 90s?

How did CA 90s impact operational efficiency?

How did CA 90s contribute to the integration of CA Technologies products?

What authentication methods were supported by CA 90s?

What access control model was used?

What encryption capabilities were available in CA 90s?

What audit and logging capabilities existed in CA 90s?

What administrative interfaces were available for CA 90s?

How was user management handled in CA 90s?

What were the main configuration parameters?

What monitoring and logging capabilities existed?

Related Products

More from CA Technologies

ADC2

AutoMate

CA Alert/VM

CA APAS Insight

CA Automated Code Structuring for COBOL

CA Calendar Routines

Similar Products

ACF/NCP

ACF/SSP

AFP DBCS Fonts

AFP Font Colection

Beta 14

Beta 23

Help Improve This Directory

Share Your Product Experience