Control-M/Restart

The architecture of Control-M/Restart is centered around three primary components: the Monitor, the Rule Engine, and the Recovery Manager. The Monitor continuously tracks the status of batch jobs, capturing completion codes and system messages. The Rule Engine evaluates these events against a set of predefined rules, which dictate the actions to be taken in response to specific failure conditions.

The Recovery Manager is responsible for initiating the restart process, which may involve resubmitting the job or executing a series of recovery steps. Communication between these components occurs over TCP/IP, ensuring reliable data transfer within the z/OS environment. The system leverages the z/OS security infrastructure, such as RACF, for authentication and access control.

Data storage is primarily managed within the Control-M environment, with configuration settings and restart rules stored in datasets. The Control-M GUI serves as the primary administrative interface, providing a centralized point for managing restart rules, monitoring job statuses, and configuring system settings. The system's design prioritizes automation, reliability, and integration with the existing Control-M and z/OS infrastructure.