What were some common commands or operations performed with CUE?

While specific commands are not available due to the product's age and lack of support, CUE likely used a combination of system commands and its own proprietary interfaces to gather performance data. These commands would have been used to initiate data collection, analyze results, and generate reports.

What types of APIs did CUE expose?

Given its age, CUE likely did not expose modern APIs like REST or SOAP. Integration would have been achieved through older methods such as direct system calls or proprietary communication protocols. Details are unavailable due to the product's unsupported status.

What administrative interfaces were available for CUE?

Administrative interfaces for CUE would have included a command-line interface (CLI) and possibly a GUI for configuring data collection parameters, generating reports, and managing user access. Specific details are unavailable.

What business value did CUE provide?

CUE provided valuable insights into mainframe performance, allowing organizations to optimize resource utilization, reduce operational costs, and improve application response times. By identifying bottlenecks and inefficiencies, CUE helped ensure that mainframe systems were running at peak performance.

How did CUE help reduce costs?

By optimizing mainframe performance, CUE helped organizations avoid unnecessary hardware upgrades and reduce software licensing costs. Efficient resource utilization translated directly into cost savings and improved ROI.

How did CUE contribute to business continuity?

CUE's ability to identify performance bottlenecks allowed organizations to proactively address issues before they impacted critical business applications. This proactive approach helped maintain service levels and ensure business continuity.

What authentication methods were supported by CUE?

Given its age, CUE likely supported basic authentication methods. Specific methods are unavailable, but it would have included password-based authentication and possibly integration with mainframe security systems like RACF.

What access control model was used by CUE?

The access control model in CUE likely involved user roles and permissions, possibly integrated with mainframe security systems. Specific details are unavailable due to the product's age and lack of support.

What encryption methods were used by CUE?

Encryption methods used by CUE are unknown, but given its age, it may not have supported modern encryption standards. Data security would have relied more on the security features of the underlying mainframe system.

What audit and logging capabilities existed in CUE?

CUE likely had audit and logging capabilities to track user activity and system events. These logs would have been used for security monitoring and troubleshooting. Specific details are unavailable.

What were the main administrative tasks for CUE?

Administration of CUE likely involved configuring data collection parameters, scheduling reports, and managing user access. This would have been done through a command-line interface (CLI) or a graphical user interface (GUI).

What monitoring and logging capabilities existed in CUE?

CUE likely provided monitoring and logging capabilities to track system performance and identify potential issues. These logs would have been used for troubleshooting and performance tuning.

How was user management handled in CUE?

User management in CUE likely involved creating user accounts, assigning roles and permissions, and managing access to data and reports. This would have been integrated with the mainframe's security system.

Share Your Product Experience

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

Share Your Experience

Configuration Utilization Evaluator

BMC Not Supported z/OS

Monitor Operating System Performance

Vendor

BMC

Product Overview

Configuration Utilization Evaluator (CUE) was designed to monitor and analyze the performance of z/OS mainframe systems. Its architecture included data collection agents, a central processing component, and reporting tools. The agents gathered performance data, which was then processed and presented in reports.

CUE collected data on CPU utilization, I/O channel activity, device performance, SVC usage, queue lengths, and disk head movements. CUE used system commands and proprietary interfaces to gather performance data. It likely supported basic authentication methods and an access control model based on user roles and permissions.

While CUE is no longer supported, organizations should consider migrating to modern alternatives like BMC MAINVIEW, IBM Z Performance and Capacity Analytics, or CA SYSVIEW Performance Management. These solutions offer enhanced features, integration capabilities, and continued vendor support. Migration involves deploying new monitoring agents, configuring data collection parameters, and adapting reporting processes to the new platform.

These modern tools often use REST APIs for integration and support protocols like SNMP.

Frequently Asked Questions

What was the primary function of Configuration Utilization Evaluator?

Configuration Utilization Evaluator (CUE) provided detailed performance metrics for mainframe systems, focusing on resource utilization. It helped identify bottlenecks and optimize system performance by analyzing CPU usage, channel activity, and device performance.

What types of data did CUE collect?

CUE collected data on CPU utilization, I/O channel activity, device performance, SVC usage, queue lengths, and disk head movements. This data helped administrators understand how system resources were being used and identify areas for improvement.

On what platforms did CUE operate?

CUE was primarily used on z/OS (formerly OS/390) mainframe systems. It was designed to monitor and analyze the performance of these systems to ensure efficient resource utilization.

How could the data from CUE be used to improve system performance?

CUE's data could be used to optimize system configuration, tune application performance, and identify hardware upgrades needed to meet performance goals. By understanding resource utilization, administrators could make informed decisions to improve overall system efficiency.

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

Share Your Product Experience

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

Share Your Experience

Share Your Product Experience

Configuration Utilization Evaluator

Product Overview

Frequently Asked Questions

What was the primary function of Configuration Utilization Evaluator?

What types of data did CUE collect?

On what platforms did CUE operate?

How could the data from CUE be used to improve system performance?

What were some common commands or operations performed with CUE?

What types of APIs did CUE expose?

What were the main system components of CUE?

What administrative interfaces were available for CUE?

What business value did CUE provide?

How did CUE help reduce costs?

How did CUE contribute to business continuity?

What authentication methods were supported by CUE?

What access control model was used by CUE?

What encryption methods were used by CUE?

What audit and logging capabilities existed in CUE?

What were the main administrative tasks for CUE?

What monitoring and logging capabilities existed in CUE?

How was user management handled in CUE?

Related Products

More from BMC

3270 SUPEROPTIMIZER/CICS

3270 SUPEROPTIMIZER/IMS

Administrative Assistant for DB2

Alter for DB2

Application Restart Control for DB2

Application Restart Control for IMS

Similar Products

(E)JES

4Tune

ABARS/Assist

ACC

Access 1

ACO SolutionPac

Help Improve This Directory

Share Your Product Experience