PILOT/MVS Modernization Guide

PILOT/MVS is a software solution designed to analyze, track, and forecast the capacity and performance of z/OS systems. It provides insights into system behavior, helping organizations optimize resource utilization and plan for future needs. The product supports z/OS systems running with or without WLM (Workload Manager).

PILOT/MVS is a tool set that combines operating system-level data collection with report generation and performance analysis capabilities. It provides a comprehensive view of z/OS system performance, enabling proactive management and optimization.

Organizations that rely on z/OS mainframe environments for critical business applications and require detailed insights into system performance and capacity. This includes enterprises in industries such as banking, finance, insurance, and government.

A company should consider using PILOT/MVS when they need to proactively manage z/OS system performance, optimize resource utilization, and plan for future capacity requirements. It is particularly useful when dealing with complex workloads and the need for detailed performance analysis.

Alternatives to PILOT/MVS include other mainframe performance monitoring and capacity planning tools such as IBM Z Performance and Capacity Analytics, Compuware Strobe, and BMC MainView. These tools offer similar capabilities for analyzing and optimizing z/OS system performance.

PILOT/MVS runs on the z/OS platform and is dependent on the z/OS operating system. It typically runs within an LPAR (Logical Partition) and may require specific z/OS subsystems to be active for data collection and analysis.

PILOT/MVS performs data processing on workstations, suggesting a client-server architecture where data is collected on the mainframe and analyzed on a separate workstation. Specific workstation requirements depend on the version and data volumes.

PILOT/MVS likely uses configuration files to define data collection parameters, reporting options, and system connections. The specific format and location of these files would be detailed in the product documentation.

PILOT/MVS may offer APIs for integration with other systems management tools or for custom reporting. The specific types of APIs (e.g., REST, SOAP) and supported programming languages would be detailed in the product documentation.

PILOT/MVS helps organizations optimize their z/OS environments, reduce costs associated with inefficient resource utilization, and improve overall system performance. By providing detailed insights into workload behavior, it enables better capacity planning and proactive problem resolution.

Without PILOT/MVS, organizations may struggle to effectively manage z/OS system performance, leading to inefficient resource utilization, increased costs, and potential service disruptions. Proactive capacity planning becomes more challenging, and problem resolution may be delayed.

The licensing model for PILOT/MVS is likely based on factors such as the size of the z/OS environment, the number of LPARs, or the volume of data processed. The specific terms and conditions would be outlined in the licensing agreement.

PILOT/MVS likely supports standard authentication methods for z/OS environments, such as RACF, ACF2, or Top Secret. Access control is typically managed through these security systems, ensuring that only authorized users can access performance data and reports.

PILOT/MVS likely uses an access control model integrated with z/OS security systems (RACF, ACF2, Top Secret). This ensures that access to performance data and reports is restricted to authorized personnel based on their roles and responsibilities.

PILOT/MVS should provide audit and logging capabilities to track user access, configuration changes, and system events. These logs are essential for security monitoring, compliance reporting, and troubleshooting.

Implementing PILOT/MVS requires expertise in z/OS systems, performance monitoring, and capacity planning. Ongoing operational requirements include monitoring system performance, maintaining the software, and analyzing performance data to identify potential issues and optimize resource utilization.

PILOT/MVS is typically deployed on-premise within the z/OS environment. This involves installing the software on the mainframe, configuring data collection parameters, and setting up reporting options. The specific deployment steps would be detailed in the product documentation.

Common implementation challenges may include configuring data collection parameters to accurately capture relevant performance metrics, integrating with existing security systems, and ensuring that the software does not introduce any performance overhead to the z/OS environment.