Quest Management Pack for z/OS Modernization Guide

Quest Management Pack for z/OS is a client that enables the multi-platform Quest Operations Manager to function within a z/OS environment. It facilitates the monitoring and management of z/OS systems from a central Quest Operations Manager console.

It is best described as a client or extension that enhances the capabilities of Quest Operations Manager, allowing it to interact with and manage z/OS systems. It is not a standalone system but rather a component that integrates with an existing management framework.

Organizations that rely on z/OS for critical applications and also use Quest Operations Manager for cross-platform monitoring and management are the primary users. These are typically large enterprises in industries such as banking, finance, insurance, and government.

A company should consider using Quest Management Pack for z/OS when they need to integrate their z/OS systems into a broader, multi-platform monitoring and management solution provided by Quest Operations Manager. This allows for a unified view of their entire IT infrastructure.

Alternatives include other systems management solutions that offer z/OS support, such as IBM Tivoli OMEGAMON, CA SYSVIEW, and BMC MainView. These products provide similar monitoring and management capabilities for z/OS environments.

Quest Management Pack for z/OS requires a running z/OS environment and a functional installation of Quest Operations Manager. It acts as a client on z/OS, communicating with the central Operations Manager server.

Yes, it runs within an LPAR (Logical Partition) on the mainframe. It is z/OS dependent and may require specific subsystems to be active for full functionality.

The product extends Quest Operations Manager, providing it with the ability to monitor and manage z/OS resources. It relies on Operations Manager for its core functionality and reporting capabilities.

The exact commands and operations depend on the version of Quest Operations Manager being used. However, common operations would include configuring monitoring agents, defining thresholds, and viewing performance data.

The product likely uses a proprietary API for communication between the z/OS client and the Quest Operations Manager server. Specific details would be found in the Operations Manager documentation.

The primary business value is the ability to integrate z/OS systems into a unified monitoring and management framework. This provides a single pane of glass for managing the entire IT infrastructure, improving efficiency and reducing operational costs.

Without Quest Management Pack for z/OS, organizations would need to use separate tools to monitor and manage their z/OS systems, leading to increased complexity and potential gaps in visibility. This can result in slower problem resolution and higher operational costs.

The licensing model is likely based on a per-server or per-managed-instance basis. The total cost of ownership includes the cost of the Quest Operations Manager license, the Management Pack license, and the ongoing operational costs of maintaining the system.

Vendor lock-in is a consideration, as the Management Pack is designed to work specifically with Quest Operations Manager. Switching to a different management platform would require replacing the Management Pack and potentially reconfiguring monitoring settings.

Authentication methods would depend on the capabilities of Quest Operations Manager. Common methods include username/password authentication, integration with LDAP directories, and potentially multi-factor authentication.

The access control model is likely Role-Based Access Control (RBAC), where users are assigned roles that grant them specific permissions to access and manage z/OS resources.

Encryption usage would depend on the configuration of Quest Operations Manager. Data in transit between the z/OS client and the Operations Manager server should be encrypted using TLS/SSL.

Audit logging capabilities would be provided by Quest Operations Manager. This would include logging of user activity, configuration changes, and security events related to the z/OS environment.

Deployment is typically on-premise, as both z/OS and Quest Operations Manager are usually deployed within the organization's data center. A hybrid approach is possible if Operations Manager is partially cloud-based.

Implementation requires a moderate level of technical expertise, including knowledge of z/OS, Quest Operations Manager, and networking. Ongoing operations require monitoring of the z/OS client and the Operations Manager server.

Common implementation challenges include configuring the z/OS client to communicate with the Operations Manager server, ensuring proper security settings, and customizing monitoring thresholds to meet specific requirements.

Administrative interfaces are primarily provided through the Quest Operations Manager console. This console allows administrators to manage users, configure monitoring settings, and view performance data for the z/OS environment.