What are the most common commands and their functions?

Common commands include `ARCHIVE`, `RESTORE`, `LIST`, and `DELETE`. The `ARCHIVE` command initiates the archiving process, while `RESTORE` retrieves archived datasets. The `LIST` command displays archive information, and `DELETE` removes archive entries.

Can you provide examples of command syntax?

The `ARCHIVE` command syntax is as follows: `ARCHIVE DATASET(dataset_name) VOLUME(tape_volume)`. The `RESTORE` command syntax is: `RESTORE DATASET(dataset_name) VOLUME(tape_volume)`. The `LIST` command syntax is: `LIST DATASET(dataset_name)`. The `DELETE` command syntax is: `DELETE DATASET(dataset_name)`.

What configuration files or interfaces are used?

Configuration is managed through JCL and control files. JCL is used to define the execution environment and parameters for TapeSaver DiskSaver. Control files specify archiving policies, dataset selection criteria, and tape volume information.

What types of APIs does this product expose?

TapeSaver DiskSaver does not expose REST or SOAP APIs. It provides a native interface through JCL and command-line utilities for integration with z/OS systems. This allows for seamless integration within the z/OS environment.

How does TapeSaver DiskSaver provide business value?

TapeSaver DiskSaver helps organizations reduce storage costs by moving infrequently accessed data from expensive disk storage to more cost-effective tape storage. This frees up disk space and optimizes storage resource utilization.

How does TapeSaver DiskSaver support data protection and business continuity?

The system ensures data protection and business continuity by creating backups of critical datasets on tape. In the event of a disk failure or data loss, archived data can be quickly restored from tape, minimizing downtime and data loss.

How does TapeSaver DiskSaver help with regulatory compliance?

TapeSaver DiskSaver simplifies compliance with data retention policies by providing a secure and reliable method for archiving data. The system's logging and reporting features facilitate audits and ensure adherence to regulatory requirements.

How does TapeSaver DiskSaver improve operational efficiency?

By automating the archiving process, TapeSaver DiskSaver reduces the manual effort required for data management. This automation streamlines operations, minimizes human error, and frees up IT staff to focus on other tasks.

What authentication methods are supported?

TapeSaver DiskSaver supports user authentication through z/OS security features, such as RACF or equivalent security managers. Access to the system's commands and functions is controlled through these security mechanisms.

What access control model is used?

The system uses the z/OS security model, which typically employs role-based access control (RBAC). Users are assigned roles, and these roles determine their access rights to specific commands and resources within TapeSaver DiskSaver.

What encryption is used and where?

Data is not encrypted during the archiving process. However, the security of the archived data relies on the security of the tape storage infrastructure and the access controls implemented within z/OS.

What audit/logging capabilities exist?

TapeSaver DiskSaver provides comprehensive audit logging of all operations, including user actions, dataset archiving, and system events. These logs are essential for security monitoring, incident investigation, and compliance reporting.

What administrative interfaces are available?

TapeSaver DiskSaver is administered through JCL and control files. JCL is used to define the execution environment and parameters. Control files specify archiving policies, dataset selection criteria, and tape volume information.

How is user management handled?

User management is handled through the z/OS security system, such as RACF or equivalent. User access to TapeSaver DiskSaver commands and resources is managed through the assignment of roles and permissions within the security system.

What are the main configuration parameters?

Key configuration parameters include dataset selection criteria, tape volume information, and archiving policies. These parameters are defined in control files and JCL, allowing administrators to customize the archiving process.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

TapeSaver DiskSaver

Name: TapeSaver DiskSaver
Availability: InStock

UNICOM Systems Active z/OS

Archive Files and Datasets Automation

Vendor

UNICOM Systems

Product Overview

The TapeSaver DiskSaver architecture comprises several key components: the Archive Manager, Policy Engine, Tape Interface, and Logging Subsystem. The Archive Manager is responsible for executing archiving and restore operations, interacting with the z/OS system to manage datasets and tape volumes. The Policy Engine evaluates dataset selection criteria defined in control files, determining which datasets should be archived based on criteria such as dataset names, creation dates, and last-used dates.

The Tape Interface manages communication with tape drives, handling tape mounts, data transfers, and tape format conversions. The Logging Subsystem records all archiving operations, including dataset names, tape volume serials, timestamps, and user actions. Communication between components occurs through z/OS system services and internal interfaces.

The system uses JCL and control files for configuration. The system does not expose REST or SOAP APIs. Authentication is handled through z/OS security, typically using RACF or equivalent, with role-based access control (RBAC) for managing user permissions.

Detailed logs are maintained for auditing and monitoring.

Frequently Asked Questions

What is TapeSaver DiskSaver?

TapeSaver DiskSaver automates the process of archiving disk datasets to tape storage on z/OS systems. It provides a reliable method for data backup, disaster recovery, and long-term data retention. The system ensures data integrity during the archiving process.

How does TapeSaver DiskSaver select datasets for archiving?

Disk datasets are archived to tape based on user-defined policies. These policies specify criteria such as dataset name patterns, creation dates, and last-used dates. The system then selects datasets matching the criteria for archiving.

What tape drive types and formats are supported?

TapeSaver DiskSaver supports various tape drive types and formats compatible with z/OS. It can manage different tape cartridge types and densities. The system automatically selects the appropriate tape drive and format based on the dataset characteristics and configuration.

What kind of logging and reporting capabilities are available?

The system provides detailed logs of all archiving operations, including dataset names, tape volume serials, and timestamps. These logs are essential for auditing, troubleshooting, and ensuring data integrity. Users can also generate reports on archive status and dataset locations.

Related Products

Not Supported

by IBM

z/OS

Alternatives available

ACO SolutionPac was an IBM solution for automating MVS operations on z/OS. It integrated with NetView to manage both system and network tasks. The core...

Operating System Automation

View Details →

ADC2

Not Supported

by CA Technologies

z/OS

Alternatives available

ADC2 was a batch job scheduling solution primarily used in z/OS environments. It automated the scheduling and execution of batch jobs, managing dependencies and resource...

Batch Automation

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Are You a Vendor? Claim Your Listing

TapeSaver DiskSaver

Product Overview

Frequently Asked Questions

What is TapeSaver DiskSaver?

How does TapeSaver DiskSaver select datasets for archiving?

What tape drive types and formats are supported?

What kind of logging and reporting capabilities are available?

What are the most common commands and their functions?

Can you provide examples of command syntax?

What configuration files or interfaces are used?

What types of APIs does this product expose?

How does TapeSaver DiskSaver provide business value?

How does TapeSaver DiskSaver support data protection and business continuity?

How does TapeSaver DiskSaver help with regulatory compliance?

How does TapeSaver DiskSaver improve operational efficiency?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from UNICOM Systems

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing