CA ADS Modernization Guide

CA ADS is a programming language and application development system specifically designed for creating and maintaining applications that interact with CA IDMS databases. It provides a comprehensive environment for designing, coding, testing, and deploying database-centric applications. It simplifies the development process by offering high-level language constructs and tools tailored for IDMS.

CA ADS is both a programming language and an application development system. It provides the tools and language constructs necessary to build complete applications. It is not merely a tool or a framework but a comprehensive system for developing and deploying IDMS database applications.

Organizations that rely on CA IDMS for their core business applications are the primary users of CA ADS. These organizations typically include large enterprises in industries such as finance, insurance, and government. Any organization with a significant investment in CA IDMS and a need to develop and maintain IDMS-based applications would benefit from CA ADS.

A company should consider using CA ADS when they need to develop new applications or maintain existing ones that interact with a CA IDMS database. It is particularly useful when the development team has expertise in CA IDMS and requires a specialized language and toolset to efficiently build and deploy IDMS-centric applications. If rapid application development and tight integration with IDMS are critical, CA ADS is a strong contender.

Alternatives to CA ADS include general-purpose programming languages like COBOL or Java, combined with database access libraries or frameworks. Other IDMS-specific development tools might also exist, but CA ADS is tightly integrated with the IDMS environment. Consider tools like Easytrieve Plus if simpler reporting and data extraction are the primary needs.

CA ADS requires a CA IDMS database environment to be present. It runs on mainframe platforms such as z/OS, z/VM, and zVSE/VSEn. It typically operates within an LPAR on z/OS and requires specific IDMS subsystems to be configured and running. It is not a standalone product and extends the capabilities of CA IDMS.

Yes, for mainframe products like CA ADS, it typically runs within an LPAR (Logical Partition) on a mainframe system. It is often z/OS dependent, meaning it relies on the z/OS operating system for its core functions. Specific subsystems within z/OS, related to CA IDMS, are necessary for CA ADS to operate correctly.

The primary architectural components include the ADS compiler, the ADS runtime environment, and the IDMS database. The ADS compiler translates ADS source code into executable modules. The ADS runtime environment provides the necessary services for executing these modules. The IDMS database stores the data accessed and manipulated by ADS applications.

CA ADS uses a proprietary language syntax. Common operations include defining database schemas, creating application programs, compiling and linking programs, and executing transactions. Configuration files define database connections and runtime parameters. The exact syntax is detailed in the CA ADS documentation.

CA ADS provides a specialized environment for developing and maintaining CA IDMS applications, which can lead to increased developer productivity and reduced development costs. By using ADS, organizations can more efficiently manage and evolve their IDMS-based systems, ensuring they continue to meet business needs. It allows for faster development cycles compared to using general-purpose languages.

Without CA ADS, organizations would need to rely on more general-purpose programming languages or other less specialized tools to develop and maintain their IDMS applications. This could lead to increased development time, higher costs, and potentially less efficient applications. The absence of CA ADS might also make it more difficult to find developers with the necessary skills to work with IDMS.

CA ADS integrates tightly with the CA IDMS database environment. It can also integrate with other mainframe systems and applications through standard mainframe communication protocols. Specific integration capabilities depend on the version of CA ADS and the surrounding mainframe environment. It may integrate with job scheduling systems and security systems like ACF2 or Top Secret.

CA ADS leverages the security features of the underlying mainframe environment, including z/OS security systems like RACF, ACF2, or Top Secret. Access control is typically managed through these external security systems, which control access to IDMS resources and ADS applications. Specific authentication methods depend on the configuration of the mainframe security system.

The access control model used by CA ADS is typically based on the access control mechanisms provided by the mainframe security system (RACF, ACF2, Top Secret). These systems often employ a role-based access control (RBAC) model, where users are assigned roles that determine their access privileges to various resources. Access control lists (ACLs) may also be used.

Auditing and logging capabilities are provided by the underlying mainframe environment and CA IDMS. Security events, such as access attempts and modifications to data, are typically logged by the mainframe security system and can be reviewed for auditing purposes. CA IDMS also provides its own logging facilities for tracking database activity.

CA ADS is typically deployed on-premise within a mainframe environment. Implementation requires expertise in CA IDMS, mainframe systems, and the organization's specific security and operational procedures. Ongoing operational requirements include monitoring system performance, managing database resources, and ensuring the availability and security of ADS applications.

Administrative interfaces are typically provided through a combination of command-line interfaces (CLIs) and graphical user interfaces (GUIs) specific to CA IDMS and the mainframe environment. User management is handled through the mainframe security system (RACF, ACF2, Top Secret). Configuration parameters are managed through configuration files and system settings within CA IDMS.

Monitoring and logging capabilities are provided by CA IDMS and the underlying mainframe environment. Performance metrics, system events, and security-related activities are typically logged and can be monitored using mainframe monitoring tools. These logs can be used to identify and resolve issues, as well as to track system usage and security events.