What are the most common commands and their syntax?

Common commands include `ZIP`, `UNZIP`, `ENCRYPT`, and `DECRYPT`. The `ZIP` command compresses files, while `UNZIP` decompresses them. `ENCRYPT` encrypts files using specified methods, and `DECRYPT` decrypts them. The syntax involves specifying input and output datasets, along with encryption parameters.

What configuration files or interfaces are used?

ZIP/390 uses configuration files to store settings such as encryption keys, compression levels, and default file formats. These files are typically specified during command execution or through environment variables. The specific interface depends on the chosen method of invocation (batch or API).

What types of APIs does ZIP/390 expose?

The product exposes APIs for integration, allowing programmatic access to its features. API endpoints and method names are specific to the functions offered, such as compression, encryption, and file transfer. Supported programming languages and SDKs are available for integration.

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

ZIP/390's architecture includes components for compression, encryption, and file transfer. These components communicate through internal processes and utilize z/OS datasets for storage. Network requirements depend on the file transfer methods used.

How does ZIP/390 provide business value?

ZIP/390 enhances data security by encrypting files using AES or PGP encryption, protecting sensitive information during storage and transfer. It also reduces storage space through compression, optimizing resource utilization.

How does ZIP/390 support regulatory compliance?

By enabling secure file transfer and data compression, ZIP/390 helps organizations comply with data protection regulations. It ensures that sensitive data is protected during transit and at rest, reducing the risk of data breaches.

How does ZIP/390 improve operational efficiency?

ZIP/390 streamlines file transfer processes, reducing manual effort and improving efficiency. Its automation capabilities, through batch jobs and APIs, enable faster and more reliable data exchange.

How does ZIP/390 help reduce costs?

ZIP/390's compression features reduce storage costs by minimizing the space required for storing files. This leads to cost savings and improved resource management within the z/OS environment.

What encryption methods are supported?

ZIP/390 supports encryption using Data 21 Cryptographic Facility for AES encryption, or PGP. This ensures that sensitive data is protected both during storage and transfer, meeting security requirements.

What audit/logging capabilities exist?

ZIP/390 provides audit logging capabilities to track file operations, including compression, encryption, and decryption. These logs help in monitoring and investigating security-related events.

How is access control managed?

Access control is managed through the z/OS security infrastructure, which can include features like RACF or equivalent security managers. This allows for role-based access control and ensures that only authorized users can perform sensitive operations.

How are security configurations managed?

Security configurations are managed through configuration files and system settings. These parameters control encryption key management, access control, and logging levels. Proper configuration is essential for maintaining the security posture of the system.

How is user management handled?

User management is typically handled through the z/OS security system, such as RACF or an equivalent. This includes user authentication, authorization, and access control to ensure that only authorized users can access and modify files.

What are the main configuration parameters?

Main configuration parameters include encryption key settings, compression levels, and file format defaults. These parameters can be adjusted to meet specific security and performance requirements.

What monitoring/logging capabilities exist?

ZIP/390 provides monitoring and logging capabilities to track system activity and identify potential issues. These logs can be used for auditing, troubleshooting, and performance analysis.

Share Your Product Experience

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

Share Your Experience

ZIP/390

Name: ZIP/390
Availability: InStock

Data21 Active z/OS

Encryption Compression File Transfer

Vendor

Data21

Product Overview

The architecture of ZIP/390 comprises several key components: a compression engine, an encryption module, and a file transfer component. The compression engine supports GZip and WinZip compatible compression algorithms. The encryption module utilizes the Data 21 Cryptographic Facility for AES encryption, and also supports PGP encryption.

The file transfer component facilitates secure data exchange. These components interact through internal processes, leveraging z/OS datasets for data storage. The compression engine processes input files, applying the selected compression algorithm.

The encryption module encrypts the compressed data using the specified method and key. The file transfer component then securely transfers the encrypted and compressed data. Configuration files, typically specified during command execution or through environment variables, store settings such as encryption keys, compression levels, and default file formats.

Administrative interfaces include the z/OS console for command-line operations and potentially a web-based interface for configuration and monitoring. User management is handled through the z/OS security system, such as RACF or an equivalent. The product supports batch job and API invocation.

Compared to competitors, ZIP/390 offers robust z/OS integration and supports both AES and PGP encryption.

Frequently Asked Questions

What are the core functions of ZIP/390?

ZIP/390 provides file compression, encryption, and transfer capabilities for z/OS. It supports GZip and WinZip compatible compression. Encryption is available using Data 21 Cryptographic Facility for AES encryption, or PGP. Files can be delivered in various formats including zip, PDF, PGP, and tab-delimited.

What is the primary use case for ZIP/390?

ZIP/390 is designed for z/OS environments, enabling secure file transfer and data compression. It allows users to compress files using GZip or WinZip compatible formats, encrypt them with AES or PGP, and transfer them securely. It supports batch and API invocation for automation.

What file formats does ZIP/390 support?

ZIP/390 supports a variety of file formats for delivery, including zip, PDF, PGP, and tab-delimited files. This flexibility allows users to choose the format that best suits their needs for data exchange and storage.

How can ZIP/390 be invoked?

ZIP/390 can be invoked through both batch jobs and APIs. This dual approach allows for both manual file processing and automated integration with other systems and applications.

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

Share Your Product Experience

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

Share Your Experience

Share Your Product Experience

ZIP/390

Product Overview

Frequently Asked Questions

What are the core functions of ZIP/390?

What is the primary use case for ZIP/390?

What file formats does ZIP/390 support?

How can ZIP/390 be invoked?

What are the most common commands and their syntax?

What configuration files or interfaces are used?

What types of APIs does ZIP/390 expose?

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

How does ZIP/390 provide business value?

How does ZIP/390 support regulatory compliance?

How does ZIP/390 improve operational efficiency?

How does ZIP/390 help reduce costs?

What encryption methods are supported?

What audit/logging capabilities exist?

How is access control managed?

How are security configurations managed?

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 Data21

Similar Products

Help Improve This Directory

Share Your Product Experience