Broadcom z/OS

SYSVIEW Modernization Guide

Operating SystemMonitor

SYSVIEW is a operating system product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

SYSVIEW is a system management tool designed for z/OS environments.

Without SYSVIEW, you may face increased system outages and performance bottlenecks.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does SYSVIEW do?

SYSVIEW is a system management tool for z/OS environments. It provides real-time monitoring, automation, and problem diagnosis capabilities. It helps organizations ensure the health and availability of their mainframe systems.

Is this a system, application, or tool?

SYSVIEW is a system and a toolset. It provides a comprehensive view of z/OS systems and allows users to interact with and manage various aspects of the operating environment.

What types of organizations use this?

Organizations that rely on z/OS for critical business applications need SYSVIEW. This includes large enterprises in industries such as banking, finance, insurance, and government.

When should we consider SYSVIEW?

A company should consider using SYSVIEW when they need real-time visibility into their z/OS systems, require automated responses to system events, and want to proactively identify and resolve potential problems.

What are the alternatives to SYSVIEW?

Alternatives to SYSVIEW include IBM Z OMEGAMON, Rocket TMON products, and Compuware Strobe. Each offers a different approach to z/OS monitoring and management.

Technical

For mainframe products: Does this run in an LPAR?

SYSVIEW runs on the z/OS platform and requires a z/OS environment to operate. It typically runs within an LPAR and may require specific subsystems to be active.

What infrastructure is required?

SYSVIEW requires a z/OS operating system and access to the systems it is monitoring. It may also require specific security configurations to access system resources.

How do users interact with SYSVIEW?

SYSVIEW uses a command-line interface (CLI) and a GUI for interaction. Configuration files are used to define system parameters and user preferences.

Does SYSVIEW integrate with other systems?

SYSVIEW can integrate with other systems through APIs, including REST APIs. It uses protocols such as TCP/IP for communication.

Business Value

What is the business value of SYSVIEW?

SYSVIEW helps organizations reduce downtime, improve system performance, and optimize resource utilization. This leads to cost savings and increased business efficiency.

What happens if we do not use SYSVIEW?

Without SYSVIEW, organizations may experience increased system outages, performance bottlenecks, and difficulty in diagnosing and resolving system problems. This can lead to business disruptions and financial losses.

How does SYSVIEW improve system availability?

SYSVIEW provides real-time monitoring and automated responses to system events, enabling proactive problem resolution and minimizing the impact of system issues.

Security

What security features does SYSVIEW offer?

SYSVIEW supports various authentication methods, including RACF, ACF2, and Top Secret. It uses role-based access control (RBAC) to manage user permissions.

Does SYSVIEW provide audit logging?

SYSVIEW provides audit logging capabilities to track user activity and system events. This helps organizations meet compliance requirements and detect potential security breaches.

How does SYSVIEW control access to data?

SYSVIEW controls access to mainframe datasets and resources based on user roles and permissions. This helps prevent unauthorized access and protect sensitive data.

Operations

How is SYSVIEW deployed?

SYSVIEW is typically deployed on-premise in a z/OS environment. Implementation requires technical expertise in z/OS systems and system management tools.

What are the ongoing operational requirements?

Ongoing operational requirements include monitoring system performance, maintaining configuration files, and managing user access. Staffing requirements include system administrators and operators with z/OS experience.

What are common implementation challenges?

Common implementation challenges include integrating SYSVIEW with existing security systems, configuring the product to meet specific monitoring requirements, and training staff on its use.

What are some common commands for monitoring resources?

To monitor a CICS region, you would use the command: `CICS REGION(cicsname)`. To display information about a specific job, you would use the command: `JOB jobname`.

Ready to Start Your Migration?

Download our comprehensive migration guide for SYSVIEW or calculate your ROI.

Calculate ROI