What were some common commands in CA Look?

Common commands included displaying CPU utilization (e.g., a command to show CPU busy percentage), memory usage (e.g., commands to display allocated and free memory), and I/O statistics (e.g., commands to show disk read/write activity). Exact syntax varied.

What was the architecture of CA Look?

CA Look's architecture included a data collection component on the monitored system and a central reporting component. These components communicated using proprietary protocols. Data was typically stored in VSAM datasets.

How was CA Look administered?

CA Look provided a character-based interface for administration. User management was handled through the host operating system's security mechanisms (e.g., RACF on z/OS).

What business value did CA Look provide?

CA Look provided visibility into system performance, helping to identify bottlenecks and optimize resource utilization. This could lead to improved application performance and reduced costs.

How did CA Look contribute to system availability?

By monitoring system resources, CA Look helped ensure the availability and reliability of critical applications. This reduced the risk of outages and service disruptions.

What security features did CA Look offer?

CA Look relied on the host operating system's security features for authentication and access control. On z/OS, this typically involved RACF. It did not offer advanced encryption capabilities.

How was access control managed in CA Look?

Access control was primarily managed through the host operating system's security mechanisms. CA Look did not implement its own RBAC or ABAC model.

What logging capabilities did CA Look provide?

CA Look generated logs that could be used for auditing and troubleshooting. These logs captured system events and performance data.

How was CA Look configured and monitored?

Administrators used the character-based interface to configure CA Look and monitor system performance. Configuration parameters were stored in parameter files.

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

CA Look

CA Technologies Not Supported z/OS zVSE/VSEn

Monitor

Vendor

CA Technologies

Product Overview

CA Look's architecture comprised several key components: a data collection agent on the monitored z/OS or z/VSE system, a central reporting server, and a character-based terminal interface for user interaction. The data collection agent gathered performance metrics such as CPU utilization, memory usage, and I/O activity. This data was transmitted to the reporting server using proprietary protocols.

The reporting server stored the data in VSAM datasets and provided a command-line interface for querying and displaying the information. Configuration was managed through parameter files. Security relied on the host operating system's security mechanisms, such as RACF on z/OS.

CA Look did not expose standard APIs like REST or SOAP. Competing products include IBM OMEGAMON and BMC AMI Ops. CA Look has been discontinued and replaced by CA Sysview, which offers a more modern architecture with standard APIs and broader platform support.

Migration involves replacing the data collection agents, reporting server, and terminal interface with the components of the new monitoring solution.

Frequently Asked Questions

What system resources did CA Look monitor?

CA Look provided real-time and historical performance data for z/OS and z/VSE systems. It monitored CPU utilization, memory usage, I/O activity, and other key metrics.

How did users interact with CA Look?

The primary interface was a character-based terminal interface. Users entered commands to display system status and performance data. Configuration was managed through parameter files.

What protocols did CA Look use for data collection?

CA Look used proprietary protocols to collect data from the monitored systems. It did not expose standard APIs like REST or SOAP.

Related Products

Adabas Statistics Facility

Active

by Software AG

z/OSz/VMzVSE/VSEn

Adabas Statistics Facility is a key component for monitoring and optimizing Adabas database performance. The system comprises two main parts: the Store Program, which gathers...

ADABAS Performance

View Details →

APM

Not Supported

by Compuware

z/OS

Alternatives available

This APM solution provided monitoring and tracing capabilities for z/OS applications, merging Strobe with Purepath for z/OS CICS and Java. It enabled detailed transaction tracing...

Application/Application Enviroment Monitor

View Details →

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