ADC2 Modernization Guide

ADC2 was primarily used for automating and scheduling batch jobs on z/OS systems. It allowed users to define job dependencies, schedule execution times, and monitor job status. It also provided features for workload balancing and resource management.

ADC2 used a command-line interface (CLI) for most operations. Users interacted with the system through commands entered via a terminal or console. Configuration files defined job schedules, dependencies, and resource allocations.

ADC2's architecture consisted of a central scheduler, agent processes on z/OS systems, and a database for storing job definitions and status. The scheduler communicated with agents to dispatch jobs and monitor their execution. The database stored job definitions, schedules, and historical data.

ADC2 provided features for monitoring job status, tracking resource utilization, and generating reports. Users could view job logs, execution times, and error messages. The system also provided alerts for failed jobs or resource bottlenecks.

Common commands included those for defining jobs (JOB), scheduling jobs (SCHD), monitoring job status (STAT), and managing resources (RES). For example, `JOB DEFINE JOB(jobname) ...` defined a new job, and `SCHD JOB(jobname) TIME(hhmm)` scheduled it to run at a specific time.

ADC2 did not expose standard APIs like REST or SOAP. Integration was typically achieved through custom scripting or by directly accessing the underlying database. Communication between components relied on proprietary protocols.

The main components included the Scheduler, Agents, and Database. The Scheduler dispatched jobs to Agents running on z/OS systems. Agents executed the jobs and reported status back to the Scheduler. The Database stored job definitions, schedules, and historical data.

ADC2 used a proprietary format for configuration files. These files defined job schedules, dependencies, and resource allocations. The administrative interface was primarily command-line based.

ADC2 automated batch job scheduling, reducing manual intervention and improving operational efficiency. It allowed for centralized control and monitoring of batch workloads, optimizing resource utilization and minimizing processing time.

By automating job scheduling and workload balancing, ADC2 helped organizations reduce operational costs and improve service levels. It enabled faster processing of batch jobs and better utilization of system resources.

ADC2 provided features for monitoring job status and tracking resource utilization, enabling organizations to identify and resolve performance bottlenecks. It also offered reporting capabilities for analyzing job execution times and resource consumption.

ADC2 supported authentication through z/OS security systems like RACF, ACF2, and Top Secret. Access control was based on user IDs and groups defined in these security systems. It did not offer granular role-based access control (RBAC).

ADC2 relied on z/OS security systems for access control. It did not implement its own access control model. User permissions were determined by their access rights within RACF, ACF2, or Top Secret.

ADC2 did not provide built-in encryption capabilities. Data was transmitted and stored without encryption. Organizations had to implement their own encryption solutions if required.

ADC2 provided audit logging capabilities, recording user actions and system events. These logs could be used for security monitoring and compliance purposes. The logs were stored in a proprietary format.

ADC2 was administered through a command-line interface (CLI). User management was handled through z/OS security systems like RACF, ACF2, and Top Secret. Configuration parameters were defined in proprietary configuration files.

ADC2 provided monitoring capabilities for job status, resource utilization, and system performance. Logs were stored in a proprietary format and could be analyzed for troubleshooting and performance tuning.

ADC2 required specific ports for communication between the scheduler and agents. These ports had to be open in the firewall to allow job dispatching and status reporting. The exact ports varied depending on the configuration.