What are the primary functions of SCC Monitor?

SCC Monitor is designed to monitor disk, tape, and DFSMShsm activity on z/OS systems. It automatically performs actions based on user-defined situations, such as sending email notifications, generating reports, and executing z/OS commands. It also integrates with ISPF and offers an Apple iPhone client for remote access.

What interfaces are available for interacting with SCC Monitor?

SCC Monitor provides an ISPF interface for direct interaction and configuration. The optional Mon-Explorer offers a PC-based GUI for enhanced management and visualization of monitoring data.

How does SCC Monitor automate responses to system events?

SCC Monitor can be used to automate responses to specific events, such as low disk space or tape errors. It can trigger actions like sending alerts via email or Websphere MQ, executing z/OS commands, or updating files.

What are the most common commands and their syntax?

Common commands include START, STOP, STATUS, and MODIFY. The syntax for starting the monitor is typically START SCCMONITOR. Configuration is managed through configuration files and the ISPF interface.

What types of APIs does SCC Monitor expose?

SCC Monitor does not expose REST or SOAP APIs. Communication relies on native z/OS interfaces and protocols suitable for the z/OS environment.

What are the main architectural components of SCC Monitor?

The core components include the Monitor Engine, Event Processor, and Action Executor. These components communicate using z/OS system services and internal messaging. Data is stored using z/OS file systems and SMF records.

How is SCC Monitor administered and configured?

SCC Monitor utilizes the ISPF interface for administration, and the Mon-Explorer provides a GUI. User management is handled through z/OS security mechanisms. Configuration parameters are set via configuration files and the ISPF interface. Monitoring and logging are provided through SMF records and internal logging.

How does SCC Monitor provide business value?

SCC Monitor helps reduce downtime by proactively identifying and responding to critical events. It automates routine tasks, freeing up operations staff to focus on other priorities. The reporting capabilities provide insights into system performance and resource utilization.

How does SCC Monitor improve operational efficiency?

By automating responses to system events, SCC Monitor minimizes manual intervention, reducing the risk of human error and improving operational efficiency. The monitoring capabilities provide early warnings of potential issues.

How does SCC Monitor assist with capacity planning and resource optimization?

SCC Monitor provides detailed reporting on disk and tape usage, helping organizations optimize resource allocation and plan for future capacity needs. The monitoring of DFSMShsm activity ensures efficient data management practices.

What authentication methods are supported?

SCC Monitor supports z/OS security features for authentication, including RACF, ACF2, and Top Secret. Access control is managed through the z/OS security system, using user IDs and security profiles.

What access control model is used?

Access control is managed through the z/OS security system, using user IDs and security profiles. This allows for role-based access control, ensuring that users only have access to the resources and functions they need.

What audit/logging capabilities exist?

SCC Monitor utilizes z/OS security features for data protection. Audit logging is provided through SMF records, which track system events and user actions.

What administrative interfaces are available?

The primary administrative interface is the ISPF panel. The Mon-Explorer GUI provides an alternative interface for PC-based administration. The START and STOP commands are used to control the monitor.

How is user management handled?

User management is handled through the z/OS security system, such as RACF, ACF2, or Top Secret. This includes defining user IDs and assigning appropriate security profiles to control access to SCC Monitor functions.

What are the main configuration parameters?

Key configuration parameters include thresholds for disk space, tape usage, and event triggers. These are typically set via configuration files and the ISPF interface.

What monitoring and logging capabilities exist?

Monitoring and logging capabilities are provided through SMF records and internal logging. These logs can be used to track system events, user actions, and performance metrics. The ISPF interface and Mon-Explorer can be used to view logs.

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

SCC Monitor

Name: SCC Monitor
Availability: InStock

DTS Software Active z/OS

Disk Tape Monitor

Vendor

DTS Software

Product Overview

The SCC Monitor architecture is based on a modular design, comprising several key components: the Monitor Engine, Event Processor, Action Executor, and Data Repository. The Monitor Engine is responsible for collecting data from various sources, including SMF records, system APIs, and external interfaces. The Event Processor analyzes this data against user-defined rules, which are configured through the ISPF interface or the Mon-Explorer GUI.

When a rule is triggered, the Action Executor initiates the corresponding action, such as sending email notifications, executing z/OS commands, or updating files. The Data Repository stores historical data and configuration settings. Communication between components is facilitated through z/OS system services and internal messaging.

The system leverages z/OS security for authentication and access control, supporting RACF, ACF2, and Top Secret. The Mon-Explorer GUI provides a PC-based interface for enhanced management and visualization. The system uses z/OS file systems for data storage and SMF records for audit logging.

Integration with other systems is achieved through Websphere MQ and email notifications. The primary command syntax is START SCCMONITOR, STOP SCCMONITOR, and MODIFY SCCMONITOR, followed by specific parameters. The configuration files are used to define monitoring rules, thresholds, and actions.

Frequently Asked Questions

Related Products

Adabas Statistics Facility

Active

by Software AG

z/OSz/VMzVSE/VSEn

Adabas Statistics Facility is a key component for monitoring and optimizing Adabas database performance. The system comprises two main parts: the Store Program, which gathers...

ADABAS Performance

View Details →

Allocate DASD Space and Placement

Active

by Broadcom

z/OS

Allocate DASD Space and Placement is a system-level tool designed for z/OS environments, focusing on efficient disk dataset allocation and the prevention of X-37 abends....

Abend Disk

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