Name: Solve:Configuration
Availability: InStock

Question 1

What did Solve:Configuration do?

Accepted Answer

Solve:Configuration was a configuration management system primarily used in z/OS mainframe environments. It allowed administrators to manage and track changes to system configurations, software versions, and other critical components. The product helped ensure consistency and control across the mainframe environment.

Question 2

Was Solve:Configuration a system, application, or tool?

Accepted Answer

Solve:Configuration was primarily a system and a toolset. It provided a centralized platform for managing configurations, but also included tools for auditing, reporting, and change management. It was not an application in the traditional sense, but rather a comprehensive solution for managing the mainframe environment.

Question 3

What types of organizations used Solve:Configuration?

Accepted Answer

Solve:Configuration was most applicable to large enterprises that relied heavily on z/OS mainframe systems. These organizations typically had complex IT environments and needed robust configuration management capabilities. Industries such as banking, insurance, and government were common users.

Question 4

When was Solve:Configuration valuable?

Accepted Answer

Solve:Configuration was valuable when organizations needed to maintain strict control over their mainframe configurations, ensure compliance with regulatory requirements, and minimize the risk of errors or outages due to configuration changes. It provided a centralized view of the environment and automated many manual tasks.

Question 5

What are the alternatives to Solve:Configuration?

Accepted Answer

Alternatives to Solve:Configuration include IBM Z OMEGAMON Configuration Manager, BMC AMI Configuration Manager for z/OS, and ASG-TMON Change Manager. These products offer similar capabilities for managing and tracking configuration changes in mainframe environments.

Question 6

What infrastructure was required for Solve:Configuration?

Accepted Answer

Solve:Configuration ran on z/OS mainframe systems. It required specific subsystems and components to be present in the environment. It was tightly integrated with the z/OS operating system and leveraged its capabilities for managing system resources and configurations.

Question 7

Did Solve:Configuration run in an LPAR?

Accepted Answer

Solve:Configuration typically ran in an LPAR (Logical Partition) on the mainframe. This allowed it to be isolated from other workloads and provided dedicated resources for managing configurations. It was z/OS dependent and required specific versions of the operating system to function correctly.

Question 8

Was Solve:Configuration a standalone product?

Accepted Answer

Solve:Configuration was a standalone product, but it could be integrated with other mainframe management tools. It provided its own set of features and capabilities, but could also exchange data with other systems to provide a more comprehensive view of the environment.

Question 9

What were the underlying technologies?

Accepted Answer

The product used a 3270-based interface. Users interacted with the system through a series of panels and commands. Configuration data was stored in VSAM datasets. The system communicated using standard mainframe protocols.

Question 10

Did Solve:Configuration expose APIs?

Accepted Answer

The primary interface was 3270. It did not expose modern APIs like REST or SOAP. Integration with other systems typically involved data extracts or custom-built interfaces using mainframe programming languages.

Question 11

What business value did Solve:Configuration provide?

Accepted Answer

Solve:Configuration provided significant business value by improving configuration control, reducing the risk of errors, and ensuring compliance with regulatory requirements. It helped organizations maintain a stable and reliable mainframe environment, which was critical for business operations.

Question 12

What happened without Solve:Configuration?

Accepted Answer

Without a configuration management system like Solve:Configuration, organizations faced a higher risk of configuration errors, inconsistencies, and outages. This could lead to business disruptions, data loss, and compliance violations. Manual configuration management was time-consuming and error-prone.

Question 13

What were the business considerations?

Accepted Answer

The licensing model was typically perpetual, with ongoing maintenance fees. The total cost of ownership included the initial license fee, maintenance fees, implementation costs, and ongoing operational expenses. Vendor lock-in was a consideration, as migrating to another configuration management system could be complex.

Question 14

How did Solve:Configuration integrate with enterprise ecosystems?

Accepted Answer

Solve:Configuration integrated with enterprise ecosystems by exchanging data with other mainframe management tools and systems. It could provide configuration data to security information and event management (SIEM) platforms and other monitoring tools.

Question 15

What security features did Solve:Configuration have?

Accepted Answer

Solve:Configuration supported various authentication methods, including RACF, ACF2, and Top Secret. It used a role-based access control (RBAC) model to control access to configuration data and functions. Encryption was used to protect sensitive data at rest and in transit.

Question 16

What access control model was used?

Accepted Answer

The access control model was role-based access control (RBAC). Administrators could assign users to specific roles, which granted them access to certain configuration data and functions. This helped ensure that only authorized personnel could make changes to the system.

Question 17

What audit/logging capabilities existed?

Accepted Answer

Solve:Configuration provided audit logging capabilities to track changes to configuration data and user activity. These logs could be used to investigate security incidents and ensure compliance with regulatory requirements. The logs captured information about who made changes, what changes were made, and when the changes occurred.

Question 18

What encryption was used?

Accepted Answer

The product used standard encryption algorithms to protect sensitive data. Specific encryption methods varied depending on the version and configuration of the system. Encryption was used to protect passwords, configuration data, and other sensitive information.

Question 19

How was Solve:Configuration deployed?

Accepted Answer

Solve:Configuration was typically deployed on-premise in the organization's data center. It required a team of skilled mainframe administrators to implement and maintain the system. Ongoing operational requirements included monitoring system performance, applying maintenance updates, and managing user access.

Question 20

What level of technical expertise was required?

Accepted Answer

Implementing Solve:Configuration required a high level of technical expertise. Mainframe administrators needed to be familiar with z/OS, VSAM, and other mainframe technologies. They also needed to understand the organization's configuration management processes and requirements.

Question 21

What were common implementation challenges?

Accepted Answer

Common implementation challenges included integrating Solve:Configuration with existing mainframe systems, migrating configuration data from legacy systems, and training users on the new system. It was important to plan the implementation carefully and involve experienced mainframe administrators.

Question 22

What ongoing operational requirements existed?

Accepted Answer

Ongoing operational requirements included monitoring system performance, applying maintenance updates, managing user access, and troubleshooting issues. Mainframe administrators needed to be available to respond to incidents and ensure that the system was running smoothly.

Share Your Product Experience

Solve:Configuration

Product Overview

Frequently Asked Questions