CA Look Modernization Guide
CA Look is a monitor product by CA Technologies. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CA Look provided monitoring capabilities for z/OS and z/VSE systems.
Security relied on the host OS (e.g., RACF on z/OS).
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
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.
Technical
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).
Business Value
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.
Security
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.
Operations
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.
Ready to Start Your Migration?
Download our comprehensive migration guide for CA Look or calculate your ROI.