Command/CICS

The architecture of Command/CICS comprises three primary components: the Translator, the Runtime Environment, and the Configuration Manager. The Translator is responsible for parsing CICS macro-level calls and converting them into their command-level equivalents. This component analyzes the macro instructions and, based on the configuration rules, generates the corresponding command-level code.

The Runtime Environment executes the translated command-level code within the CICS environment. This component handles the interaction with CICS services and ensures the correct execution of the translated commands. The Configuration Manager is used to define and manage the translation rules.

These rules are stored in configuration files that map macro calls to command-level equivalents. The configuration files allow for customization of the translation process, enabling users to handle specific application requirements. The communication between these components is managed through the CICS API and z/OS system services.

Command/CICS does not use any external databases or storage mechanisms for its core functionality, relying instead on the CICS environment for data access and management. The product integrates with z/OS security, including RACF, for authentication and authorization. The main configuration parameters are defined in configuration files.

Monitoring and logging capabilities are provided through integration with z/OS logging facilities.