Mainstar ASAP

The architecture of Mainstar ASAP was designed to automate dataset selection for z/OS backups. The main components included the ASAP control files, the ISPF interface, and the batch job scheduler. The ASAP control files were the heart of the system, defining dataset groups and backup schedules.

These files used a specific syntax to specify datasets based on HLQ (High Level Qualifier) or other criteria. The ISPF interface provided an interactive way to manage these control files, allowing users to define, modify, and view dataset groups and backup schedules. Batch jobs were used to execute the backup processes, leveraging the definitions in the ASAP control files.

Communication between components was primarily through the z/OS operating system. The system integrated with DFSMShsm ABARS to perform the actual backups. There were no external databases or specific network requirements.

Security relied on z/OS security features, such as RACF or equivalent, for access control. The product did not expose any APIs. Configuration parameters were primarily defined within the ASAP control files.

The system generated reports on backup status and dataset selection. Given its end-of-life status, users should migrate to a supported solution like IBM Backup and Recovery Manager.