What are the common commands and their syntax?

The most common commands include ERASE and CERTIFY. The ERASE command syntax typically involves specifying the tape volume serial. The CERTIFY command also requires the tape volume serial. Configuration is managed through JCL parameters within the FATSCOPY utility.

Does FATS provide any APIs for integration?

FATS does not expose APIs. It is a utility that is invoked through JCL. Integration with other systems is achieved by incorporating FATSCOPY steps within z/OS batch jobs.

What administrative interfaces and capabilities are available?

FATS does not have a dedicated administrative interface. Administration is performed through JCL, which is used to configure and run the FATSCOPY utility. Monitoring and logging are handled through z/OS system logs and the output generated by FATSCOPY.

What is the business value of using FATS?

FATS provides the ability to erase and certify tapes, ensuring data security and tape reliability. This helps prevent data breaches and ensures that tapes are in good working condition before reuse.

How does FATS improve operational efficiency?

By using FATS, organizations can reduce the risk of data loss and improve the efficiency of tape management operations. The utility helps maintain data integrity and optimize the use of tape resources.

How does FATS support compliance with data retention policies?

FATS helps in adhering to data retention policies by securely erasing tapes. This is crucial for compliance with regulations that require the proper disposal of sensitive data.

What authentication methods are supported?

FATS does not have built-in authentication methods. Security is managed through z/OS security features, such as RACF or similar security products, which control access to the JCL that invokes FATSCOPY.

What access control model is used?

Access control is managed through z/OS security mechanisms, such as RACF, which uses an access control list (ACL) model. This allows administrators to define which users and groups can submit JCL that executes FATSCOPY.

What encryption is used and where?

FATS does not perform encryption directly. Data security relies on the security features of the z/OS environment and any encryption implemented at the tape drive level.

What audit/logging capabilities exist?

Auditing and logging are handled through z/OS system logs. FATSCOPY generates output that can be used for auditing tape operations. The z/OS system logs provide a record of JCL submissions and job executions.

How are operations performed and monitored?

Operations involve submitting JCL jobs that execute FATSCOPY with the ERASE or CERTIFY parameters. Monitoring is done through z/OS system logs and the output from FATSCOPY.

What are the main configuration parameters?

Configuration parameters are set within the JCL used to invoke FATSCOPY. These parameters specify the tape volume serial, and other operational settings. There is no separate configuration file.

How is troubleshooting handled?

Troubleshooting involves reviewing the output from FATSCOPY and consulting the z/OS system logs. Common issues include incorrect JCL parameters or tape drive errors. Error messages provide clues for resolving issues.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

FATS

Name: FATS
Availability: InStock

Innovation Data Processing Not Supported z/OS

Tape Tools and Utilities Administration

Vendor

Innovation Data Processing

Product Overview

FATS, part of FATSCOPY, operated within the z/OS environment. The main components included the FATS module itself, which is part of FATSCOPY, and the tape drives. Communication occurred through the z/OS operating system, using JCL to control the execution of FATSCOPY.

The ERASE and CERTIFY functions were the core operations. The ERASE command securely removed all data from a tape, while the CERTIFY command checked for errors. Administration was performed through JCL, which was used to configure and run the FATSCOPY utility.

Security was managed through z/OS security mechanisms, such as RACF, which uses an access control list (ACL) model. Auditing and logging were handled through z/OS system logs. FATS did not expose any APIs.

Integration was achieved by incorporating FATSCOPY steps within z/OS batch jobs. FATS is no longer supported. Users should migrate to alternative tape management solutions.

These solutions offer enhanced features, improved security, and better integration with current z/OS environments. Migration involves reconfiguring tape operations to use the new software, updating JCL, and training staff on the new system.

Frequently Asked Questions

What is FATS and what are its primary functions?

FATS is a utility designed for tape management on z/OS systems. It provides functionalities to erase and certify tapes, ensuring data integrity and reusability. The utility is integrated within FATSCOPY.

What specific operations does FATS perform on tapes?

FATS is primarily used for erasing and certifying tapes. The ERASE function securely removes all data from a tape, while the CERTIFY function checks for errors before the tape is put back into use. These functions are essential for data security and tape reliability.

How is FATS related to FATSCOPY?

FATS is integrated within FATSCOPY, which is a broader utility for tape management. FATSCOPY provides a suite of tools, including the erase and certify functions of FATS, to manage tape operations efficiently.

When was FATS first released?

FATS was initially released in 1974. As a legacy product, it has been a part of z/OS tape management for a long time.

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

Share Your Product Experience

FATS

Product Overview

Frequently Asked Questions

What is FATS and what are its primary functions?

What specific operations does FATS perform on tapes?

How is FATS related to FATSCOPY?

When was FATS first released?

What are the common commands and their syntax?

Does FATS provide any APIs for integration?

What are the main system components and how do they communicate?

What administrative interfaces and capabilities are available?

What is the business value of using FATS?

How does FATS improve operational efficiency?

How does FATS support compliance with data retention policies?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

How are operations performed and monitored?

What are the main configuration parameters?

How is troubleshooting handled?

Related Products

More from Innovation Data Processing

FATAR

FDRCLONE

UPSTREAM/SOS

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

_beta doc|z plus

_beta doc|z transform

Help Improve This Directory

Are You a Vendor? Claim Your Listing