What are some common commands and their syntax?

Common commands include VIEW, PRINT, DELETE, and SEARCH. The VIEW command displays a report, PRINT initiates printing, DELETE removes reports, and SEARCH locates reports based on criteria. For example, to view a report, use the command: VIEW report_id.

What configuration files or interfaces are used?

View uses configuration files to define system parameters, report retention policies, and security settings. These files are essential for customizing the system's behavior. The system also uses interfaces for integration with other z/OS components.

What are the main system components?

The main system components include the Report Archiver, the Indexing Engine, the Viewing Interface, the Security Manager, and the Print Subsystem. These components work together to archive, index, secure, and provide access to reports.

How do the main system components communicate?

The Report Archiver captures output data. The Indexing Engine creates indexes for efficient searching. The Viewing Interface provides access to reports. The Security Manager enforces access controls. The Print Subsystem handles printing requests. These components communicate through internal system calls and data exchange.

What is the business value of using View?

View helps organizations reduce paper consumption by archiving reports electronically. It improves operational efficiency by providing quick access to reports. The system also enhances data security through access controls and audit trails.

How does View improve operational efficiency?

View streamlines report management, reducing the need for manual processes. It provides a centralized repository for reports, making them easier to find and manage. This leads to improved productivity and reduced operational costs.

How does View support compliance and data governance?

By providing secure access controls and audit trails, View helps organizations meet compliance requirements. The system ensures that sensitive information is protected and that access is tracked. This supports regulatory compliance and data governance.

What authentication methods are supported?

View supports authentication through RACF, ACF2, and Top Secret. These methods integrate with existing security infrastructure. The system allows organizations to leverage their current security investments for authentication.

What access control model is used?

View uses an RBAC (Role-Based Access Control) model. This model allows administrators to define roles and assign permissions to users based on their roles. This simplifies access management and ensures that users have appropriate access to reports.

What audit/logging capabilities exist?

View provides audit logging capabilities to track user activities and system events. Audit logs record actions such as report access, modifications, and deletions. These logs are essential for security monitoring and compliance.

What encryption is used and where?

Encryption is used to protect sensitive data at rest and in transit. Encryption ensures that confidential information remains secure. The system uses encryption to protect archived reports and during network communications.

What administrative interfaces are available?

Administrative interfaces include a TSO/ISPF interface and a web-based console. The TSO/ISPF interface provides a command-line interface for system management. The web console offers a graphical interface for configuration and monitoring.

How is user management handled?

User management is handled through integration with security systems like RACF, ACF2, and Top Secret. Administrators manage user access and permissions within these security systems. This integration ensures consistent security policies.

What are the main configuration parameters?

Main configuration parameters include report retention policies, storage locations, and security settings. These parameters are set through configuration files and administrative interfaces. Proper configuration is crucial for system performance and security.

What monitoring/logging capabilities exist?

Monitoring and logging capabilities include system activity logs and performance metrics. These logs and metrics are accessible through administrative interfaces. Monitoring helps administrators identify and resolve issues.

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

View

Broadcom Active z/OS

Report Generation and Management Printing and Output Automation

Vendor

Broadcom

Product Overview

The View architecture comprises several key components designed for efficient report archiving and management. The Report Archiver captures output data from various z/OS subsystems. The Indexing Engine creates and maintains indexes for rapid report retrieval.

The Viewing Interface provides users with access to archived reports through various interfaces. The Security Manager enforces access controls and integrates with security systems like RACF, ACF2, and Top Secret. The Print Subsystem handles printing requests.

These components communicate through internal system calls and data exchange. Data storage utilizes VSAM datasets for storing report data and indexes. Network requirements include connectivity to z/OS subsystems and external printing devices.

The system's configuration files define parameters such as report retention policies, storage locations, and security settings. The administrative interfaces, including a TSO/ISPF interface and a web-based console, provide tools for monitoring and managing the system. The architecture is designed for scalability and high availability, ensuring reliable report management in demanding z/OS environments.

The system's design emphasizes security, with RBAC and audit logging capabilities.

Frequently Asked Questions

What is the primary function of View?

View automates the archiving of system output reports and data. It captures and stores reports generated by various z/OS subsystems. This includes reports from CICS, TSO, CA Roscoe, IMS, and VTAM, ensuring they are readily available for viewing and retrieval.

What key features does View offer?

View provides features for report viewing, security, backup, and printing. Users can access archived reports through various interfaces. The system also includes security features to control access and protect sensitive information. Backup and printing capabilities ensure data integrity and accessibility.

What is the history of View?

View was originally released as SAR (Sysout Archival and Retrieval) by Goal Systems. It has evolved to support modern z/OS environments while retaining its core functionality. The system continues to provide robust report management capabilities.

Which z/OS environments does View integrate with?

View integrates with CICS, TSO, CA Roscoe, IMS, and VTAM. This integration allows the system to capture and manage output from these environments. The system provides a centralized solution for report management across different z/OS subsystems.

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

Are You a Vendor? Claim Your Listing

View

Product Overview

Frequently Asked Questions

What is the primary function of View?

What key features does View offer?

What is the history of View?

Which z/OS environments does View integrate with?

What are some common commands and their syntax?

What configuration files or interfaces are used?

What are the main system components?

How do the main system components communicate?

What is the business value of using View?

How does View improve operational efficiency?

How does View support compliance and data governance?

What authentication methods are supported?

What access control model is used?

What audit/logging capabilities exist?

What encryption is used and where?

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 Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

_beta access audit

_beta access monitor

_beta doc|z plus

_beta doc|z transform

$avers

ABARS/Assist

Help Improve This Directory

Share Your Product Experience