What infrastructure is required?

CA Netman required a mainframe environment running z/OS. It likely depended on specific subsystems and components commonly found in mainframe environments, such as security systems (e.g., RACF, ACF2, Top Secret) and database management systems (e.g., DB2).

For mainframe products: Does this run in an LPAR?

As a mainframe application, CA Netman ran within an LPAR (Logical Partition) on a mainframe system. It was tightly integrated with the z/OS operating system and required specific subsystems to be available.

What configuration files are used?

CA Netman likely used configuration files specific to the mainframe environment. These files would control various aspects of the system's behavior, such as database connections, security settings, and reporting parameters. The Online Customization Facility (OLCF) allowed users to customize CA Netman.

What business problems did CA Netman solve?

CA Netman provided business value by helping organizations manage their IT assets, track and resolve problems efficiently, and control changes to their IT infrastructure. This led to improved operational efficiency, reduced downtime, and better compliance with regulatory requirements.

What would happen if an organization did NOT use this product?

Without CA Netman, organizations would have faced challenges in managing their IT assets, tracking and resolving problems, and controlling changes to their IT infrastructure. This could have led to increased operational costs, higher risk of errors, and reduced compliance with regulatory requirements.

What was the typical licensing model?

The typical licensing model for CA Netman was likely a perpetual license, where organizations paid a one-time fee for the software and then ongoing maintenance fees for support and updates. The total cost of ownership would have included the initial license fee, maintenance fees, and the cost of hardware, software, and personnel required to operate the system.

How was security handled in CA Netman?

CA Netman leveraged the security features of the mainframe environment, such as RACF, ACF2, or Top Secret, for authentication and access control. It likely used an access control model based on roles and permissions, where users were assigned roles that determined their access to specific functions and data.

What specific authentication methods were supported?

CA Netman relied on the security mechanisms provided by the mainframe operating system (z/OS) and security subsystems (RACF, ACF2, Top Secret). These systems provided authentication, authorization, and auditing capabilities. CA Netman likely integrated with these systems to enforce security policies and track user activity.

What audit/logging capabilities existed?

CA Netman provided audit and logging capabilities to track user activity and system events. This information could be used to monitor security, troubleshoot problems, and comply with regulatory requirements. The audit logs likely contained information about user logins, data access, and changes to system configuration.

How was CA Netman typically deployed?

CA Netman was typically deployed on-premise within a mainframe environment. Implementing CA Netman required expertise in mainframe systems, security, and networking. Ongoing operational requirements included monitoring system performance, maintaining security, and providing user support.

What level of technical expertise was required to implement it?

Implementing CA Netman required a team with expertise in mainframe systems, security, and networking. Common implementation challenges included integrating CA Netman with existing systems, configuring security settings, and training users.

What ongoing operational requirements existed?

Ongoing operational requirements for CA Netman included monitoring system performance, maintaining security, providing user support, and performing regular backups. These tasks required a dedicated team of mainframe professionals.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

CA Netman

CA Technologies Not Supported z/OS

Change Management Infrastructure and Computing Assets Administration Data Management

Vendor

CA Technologies

Product Overview

CA Netman was a mainframe-based system designed for asset, problem, and change management. It provided features for inventory control, problem tracking, change management, and ad hoc reporting. The system helped organizations maintain a database of hardware and software assets, manage problem tickets, and control changes to their IT infrastructure.

CA Netman also included an Online Customization Facility (OLCF) for customizing the system. From an architectural perspective, CA Netman likely consisted of several components, including a database for storing asset information, a problem tracking module, a change management module, and a reporting engine. These components would have communicated with each other using mainframe-specific protocols and interfaces.

Given that CA Netman is no longer supported, organizations should consider migrating to modern IT service management (ITSM) platforms like BMC Remedy, ServiceNow, or IBM Control Desk. These platforms offer a more modern architecture with better scalability, flexibility, and integration capabilities.

Frequently Asked Questions

What does CA Netman do?

CA Netman was a mainframe-based software solution designed for asset, problem, and change management. It provided features for inventory control, problem tracking, change management, and ad hoc reporting, helping organizations manage their IT infrastructure and related processes.

Is this a system, application, or tool?

CA Netman is a system designed to manage IT assets, track problems, and control changes within a mainframe environment. It is not simply an application or a tool but a comprehensive system for managing various aspects of IT operations.

What types of organizations used this?

Organizations that relied on mainframe systems for their core business operations used CA Netman. These organizations were typically large enterprises in industries such as banking, finance, insurance, and government.

When should a company consider CA Netman?

Companies considered using CA Netman when they needed a centralized system to manage their IT assets, track and resolve problems, and control changes within their mainframe environment. It was particularly useful for organizations with complex IT infrastructures and strict regulatory requirements.

What are the alternatives to CA Netman?

Alternatives to CA Netman include other mainframe-based change management and asset management solutions, as well as modern IT service management (ITSM) platforms that can integrate with mainframe environments. Examples include BMC Remedy, ServiceNow, and IBM Control Desk.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

CA Netman

Product Overview

Frequently Asked Questions

What does CA Netman do?

Is this a system, application, or tool?

What types of organizations used this?

When should a company consider CA Netman?

What are the alternatives to CA Netman?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

What configuration files are used?

What business problems did CA Netman solve?

What would happen if an organization did NOT use this product?

What was the typical licensing model?

How was security handled in CA Netman?

What specific authentication methods were supported?

What audit/logging capabilities existed?

How was CA Netman typically deployed?

What level of technical expertise was required to implement it?

What ongoing operational requirements existed?

Related Products

More from CA Technologies

ADC2

AutoMate

CA 90s

CA Alert/VM

CA APAS Insight

CA Automated Code Structuring for COBOL

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

ACI Proactive Risk Manager

ACR/Detail

Help Improve This Directory

Are You a Vendor? Claim Your Listing