Dino Smart

The Dino Smart architecture consists of three primary components: the Monitor, the Collector, and the Reporting Engine. The Monitor is responsible for tracking the status of batch jobs. The Collector gathers job-related data, including start and end times, resource usage, and error messages.

The Reporting Engine processes the collected data to generate reports and provide historical analysis. These components communicate via internal messaging queues. The system stores job data in a VSAM database.

The Monitor component interfaces with the z/OS operating system to retrieve job information. The Collector uses system APIs to gather job metrics. The Reporting Engine provides a TSO/ISPF interface for report generation.

The system uses RACF for user authentication and access control. The configuration files define parameters such as data retention periods, alert thresholds, and report formats. The system uses a proprietary API for integration.

The API supports operations such as retrieving job status, submitting jobs, and retrieving job logs. API calls are made via a native interface. Supported programming languages include Assembler and COBOL.

The API uses a custom protocol for communication. Compared to competitors, Dino Smart offers a streamlined interface for z/OS batch job management.