ussAction

The ussAction architecture is centered around three primary components: the monitoring service, the backup service, and the reporting engine. The monitoring service is responsible for continuously tracking changes to USS files. It utilizes system-level access to detect file modifications, including creation, deletion, and modification events.

The backup service is triggered by the monitoring service when a file change is detected. It creates backups of the modified files, storing them in a designated location within the z/OS file system. The reporting engine processes the data collected by the monitoring service and the backup service to generate detailed reports.

These reports include information on the files modified, the nature of the changes, and the timestamps of the modifications. The components communicate internally through system calls and shared memory. The monitoring service detects file changes, which triggers the backup service to create backups.

The reporting engine then processes the data to generate reports. The system does not use a database. Configuration is managed through text-based configuration files, which specify the files and directories to be monitored, backup schedules, and reporting options.

Security is handled through the z/OS security infrastructure, including RACF, for authentication and access control. The product does not expose external APIs and relies on the z/OS security features for data protection. The command-line interface provides the primary means of interaction, with commands such as `ussAction start`, `ussAction configure`, and `ussAction report` used for managing the system.