Data Processing Techniques z/OS

PDS Monitor Modernization Guide

Program and Load LibrariesTools and Utilities

PDS Monitor is a program and load libraries product by Data Processing Techniques. Explore technical details, modernization strategies, and migration paths below.

Product Overview

PDS Monitor is a tool designed for organizations using the z/OS operating system to manage their program and load libraries.

This tool is especially beneficial for enterprises in industries such as banking, insurance, and government, where z/OS systems are critical.

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 PDS Monitor do?

PDS Monitor is a tool for z/OS environments that analyzes program and load libraries. It identifies active and unused programs, audits module updates, locates duplicate modules, and reports on language and COBOL compiler options.

Is this a system, application, or tool?

This is a tool set designed for managing and analyzing load libraries within a z/OS environment. It provides utilities for identifying inefficiencies and potential issues within these libraries.

What types of organizations use this?

Organizations that rely on the z/OS operating system and manage a large number of load libraries would benefit from this product. This includes enterprises in industries such as banking, insurance, and government.

When should we consider PDS Monitor?

A company should consider using PDS Monitor when they need to optimize their load library usage, identify unused programs, audit module updates, or locate duplicate modules. This helps in maintaining a clean and efficient z/OS environment.

Technical

For mainframe products: Does this run in an LPAR?

PDS Monitor runs on the z/OS operating system. It is z/OS dependent and operates within an LPAR. It analyzes load libraries and requires access to the system's program management facilities.

What are the main functions of PDS Monitor?

PDS Monitor analyzes load libraries, identifies active and inactive modules, and reports on COBOL compiler options. Common operations include identifying duplicate modules and auditing module updates.

What configuration files or interfaces are used?

The product likely uses configuration files to specify the load libraries to be analyzed and the reporting options. The exact format and location of these files would be detailed in the product documentation.

Business Value

How does PDS Monitor provide business value?

PDS Monitor helps organizations optimize their z/OS environments by identifying and removing unused programs, reducing storage costs, and improving system performance. It also aids in maintaining compliance by auditing module updates.

How does PDS Monitor reduce costs?

By identifying duplicate modules and unused programs, PDS Monitor helps reduce storage consumption and simplifies program management. This leads to lower operational costs and improved efficiency.

Security

How does PDS Monitor address security concerns?

PDS Monitor likely integrates with z/OS security systems such as RACF, ACF2, or Top Secret to control access to load libraries and ensure that only authorized personnel can update modules. It also provides audit trails of module updates.

What audit/logging capabilities exist?

The product provides audit logging capabilities to track module updates and access to load libraries. These logs can be used to monitor for unauthorized changes and ensure compliance with security policies.

Operations

How is PDS Monitor typically deployed?

PDS Monitor is typically deployed on-premise within a z/OS environment. Implementing it requires expertise in z/OS systems programming and load library management.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the product's performance, maintaining the configuration files, and reviewing the audit logs. Staffing requirements include z/OS systems programmers and security administrators.

What are common implementation challenges?

Common implementation challenges include ensuring compatibility with existing z/OS security systems, configuring the product to analyze the correct load libraries, and interpreting the reports generated by the product.

Ready to Start Your Migration?

Download our comprehensive migration guide for PDS Monitor or calculate your ROI.

Calculate ROI