Info/Man Modernization Guide

Info/Man was a mainframe-based software solution designed for asset, problem, and change management. It provided features such as inventory control, problem tracking, change management, ad hoc reporting, and security features, helping organizations manage their IT infrastructure and processes.

Info/Man is best described as a system, providing a comprehensive suite of tools for managing IT assets, problems, and changes. It offered a centralized platform for organizations to track and manage their IT infrastructure and related processes.

Organizations that relied on mainframe systems for their IT infrastructure and required robust asset, problem, and change management capabilities found Info/Man useful. These organizations typically included large enterprises in industries such as banking, finance, insurance, and government.

Companies considered using Info/Man when they needed a centralized system to manage their IT assets, track and resolve problems, and control changes to their IT infrastructure. It was particularly relevant for organizations heavily invested in mainframe environments.

Given that Info/Man is no longer supported, alternatives include TVL Information Management for z/OS from Log-On Software, as well as other change management and asset management solutions like CA Service Desk Manager, BMC Remedy, and ServiceNow.

Info/Man ran on the z/OS platform and required specific subsystems to be present for it to function correctly. It was tightly integrated with the mainframe environment and leveraged its capabilities for data storage, processing, and security.

Info/Man required a mainframe environment running z/OS, along with specific subsystems and databases for storing and managing its data. It also needed network connectivity for users to access the system and for integration with other applications.

Info/Man used a hierarchical security model, with access controlled through user IDs and passwords managed within the z/OS environment. It leveraged RACF (Resource Access Control Facility) for authentication and authorization, ensuring that only authorized users could access specific functions and data.

Info/Man provided a command-line interface (CLI) and a GUI (Graphical User Interface) for administrators to manage the system. The CLI allowed for scripting and automation of administrative tasks, while the GUI provided a user-friendly interface for configuration and monitoring.

Info/Man provided business value by centralizing IT asset, problem, and change management, leading to improved efficiency, reduced downtime, and better compliance. It enabled organizations to track their IT assets, resolve problems quickly, and control changes to their infrastructure, minimizing disruptions and ensuring smooth operations.

Without a system like Info/Man, organizations faced challenges in tracking their IT assets, managing problems effectively, and controlling changes to their infrastructure. This could lead to increased downtime, higher costs, and compliance issues.

Info/Man helped organizations maintain compliance by providing a centralized system for tracking IT assets, managing changes, and documenting problem resolutions. This enabled them to demonstrate adherence to regulatory requirements and internal policies.

Info/Man leveraged the security features of the z/OS operating system, including RACF, to control access to its functions and data. It supported authentication through user IDs and passwords, and authorized users based on their roles and responsibilities.

Info/Man provided audit logging capabilities, recording user activities and system events. This allowed administrators to track changes, identify security breaches, and ensure accountability.

Info/Man used a role-based access control (RBAC) model, where users were assigned roles that defined their access privileges. This simplified user management and ensured that users only had access to the functions and data they needed to perform their jobs.

Implementing Info/Man required expertise in mainframe systems, z/OS, and the specific subsystems it relied on. It also required careful planning and configuration to ensure it met the organization's specific needs.

Ongoing operational requirements for Info/Man included monitoring system performance, managing user accounts, and performing regular backups. It also required applying patches and upgrades to ensure the system remained secure and stable.

Common implementation challenges included integrating Info/Man with existing systems, migrating data from legacy systems, and training users on the new system. It also required careful planning to minimize disruption to ongoing operations.