PM/RS Modernization Guide

PM/RS is a problem management system designed for the z/OS platform. It helps organizations track, manage, and resolve issues related to their IT infrastructure and applications. It provides a centralized system for logging incidents, assigning them to appropriate personnel, and monitoring their resolution.

PM/RS is an application built on the ISPF framework. It provides a set of tools and interfaces for managing problems within a z/OS environment. It is not middleware, but rather a system designed for direct user interaction and data management.

Organizations that rely on the z/OS operating system for critical business applications and infrastructure are most likely to use PM/RS. This includes large enterprises in industries such as banking, finance, insurance, and government. Any organization needing structured problem tracking on the mainframe could benefit.

A company should consider using PM/RS when they need a centralized, structured way to manage problems and incidents within their z/OS environment. This is especially important when dealing with complex systems and a high volume of incidents that require tracking, assignment, and resolution.

Alternatives to PM/RS include other problem management systems that may run on different platforms or offer different features. Some general-purpose ticketing systems could be adapted for mainframe use, but might lack specific z/OS integration. Consider BMC Remedy, ServiceNow (if integrated with z/OS), or custom-built solutions.

PM/RS requires a z/OS environment with ISPF (Interactive System Productivity Facility) installed. It typically runs within an LPAR (Logical Partition) on the mainframe. No specific subsystems beyond standard z/OS components are explicitly required, but integration with security systems like RACF, ACF2, or Top Secret is common.

Yes, PM/RS is z/OS dependent. It is designed specifically to run within the z/OS operating system on an IBM mainframe. It leverages ISPF for its user interface and interacts directly with z/OS datasets and system services.

PM/RS is typically deployed on-premise within the organization's data center, as it is designed for z/OS environments. Cloud deployment is not a typical scenario unless the organization is running z/OS in a cloud environment (which is less common).

Implementing PM/RS requires technical expertise in z/OS, ISPF, and mainframe security systems. Familiarity with problem management processes and ITIL frameworks is also beneficial. The implementation team should include mainframe systems programmers and security administrators.

PM/RS helps organizations reduce downtime and improve service levels by providing a structured approach to problem management. This leads to faster resolution times, reduced impact on business operations, and improved customer satisfaction. It also provides valuable data for identifying recurring problems and implementing preventative measures.

Without PM/RS, organizations may struggle to effectively track and manage problems in their z/OS environment. This can lead to longer resolution times, increased downtime, and a lack of visibility into the root causes of incidents. It can also make it difficult to comply with regulatory requirements and maintain service level agreements.

PM/RS integrates with enterprise ecosystems by providing APIs and interfaces for exchanging data with other systems. This allows organizations to incorporate problem management data into their overall IT service management (ITSM) strategy and gain a holistic view of their IT environment. Integration with security systems like RACF is also common.

PM/RS supports authentication methods provided by the z/OS security environment, such as RACF, ACF2, and Top Secret. It leverages these systems to verify user identities and control access to data and functions within the application.

PM/RS uses an access control model based on roles and permissions. Users are assigned roles that define their level of access to different functions and data within the system. This allows administrators to control who can view, create, modify, or delete problem records.

PM/RS leverages the security features of z/OS to protect data at rest and in transit. Encryption may be used for sensitive data fields within the problem records. The specific encryption algorithms used depend on the configuration of the z/OS security environment.

PM/RS provides audit logging capabilities to track user activity and changes to problem records. This information can be used to monitor compliance with security policies and investigate potential security breaches. The audit logs typically include the user ID, timestamp, and type of activity performed.

Ongoing operational requirements for PM/RS include monitoring system performance, maintaining the z/OS environment, and managing user access. Regular backups of the PM/RS data are also essential. Staffing requirements include mainframe systems programmers and security administrators.

Common implementation challenges for PM/RS include integrating with existing security systems, customizing the application to meet specific business requirements, and training users on the new system. Data migration from legacy systems can also be a challenge.

PM/RS provides monitoring and logging capabilities to track system performance and user activity. This information can be used to identify potential problems and ensure that the system is operating efficiently. The logs can be accessed through ISPF panels or exported for analysis by other tools.