CA Alchemist Modernization Guide

CA Alchemist manages software changes through a repository-based system. It tracks versions of source code, configuration files, and other artifacts. Changes are typically managed through check-in/check-out operations.

Common operations include CHECKOUT (to retrieve a file for editing), CHECKIN (to submit changes), UPDATE (to synchronize a workspace), DIFF (to compare versions), and HISTORY (to view the change log).

CA Alchemist uses a mainframe-based repository. The specific database or storage mechanism is typically a VSAM or DB2 database on z/OS.

User management is handled through the z/OS security system (RACF, ACF2, or Top Secret). Access to Alchemist resources is controlled through these security systems.

The core components include the Alchemist Repository (where versions are stored), the Alchemist Server (which manages requests), and the Alchemist Client (used by developers).

The Alchemist client communicates with the Alchemist server using a proprietary protocol over TCP/IP. The server interacts with the z/OS system and the repository database.

Basic operations include CHECKOUT filename, CHECKIN filename, UPDATE filename, DIFF filename version1 version2, and HISTORY filename.

CA Alchemist primarily uses a command-line interface (CLI) for most operations. Configuration is often done through ISPF panels or by directly editing configuration files.

Alchemist uses the underlying z/OS security system for authentication. This typically involves RACF, ACF2, or Top Secret. Access control is based on the permissions defined in these systems.

CA Alchemist provides a centralized repository for managing changes, ensuring consistency and traceability. This reduces errors and improves the reliability of software releases.

By automating change management processes, CA Alchemist reduces the manual effort required for tracking and coordinating changes. This frees up developers to focus on other tasks.

Alchemist's audit trails and reporting capabilities help organizations meet compliance requirements by providing a record of all changes made to the system.

Authentication is handled through z/OS security systems such as RACF, ACF2, or Top Secret. These systems provide robust authentication and authorization capabilities.

CA Alchemist leverages the access control mechanisms provided by z/OS security systems (RACF, ACF2, Top Secret). These systems use an ACL-based model.

Data at rest within the Alchemist repository can be encrypted using z/OS encryption facilities. Data in transit is typically not encrypted unless the underlying network protocols provide encryption.

CA Alchemist provides audit logging capabilities that track all changes made to the system. These logs can be used to monitor activity and identify potential security breaches.

CA Alchemist is administered through a combination of command-line interfaces (CLIs) and ISPF panels. Configuration files can also be directly edited.

Monitoring is typically done through z/OS system monitoring tools and by reviewing Alchemist's audit logs. These logs provide information about system activity and potential issues.

Configuration parameters are typically set through ISPF panels or by editing configuration files. These parameters control various aspects of Alchemist's behavior.