InfoScope Modernization Guide

InfoScope monitors SQL query performance on Db2 databases. It captures SQL execution statistics, resource consumption, and wait times. This data helps identify performance bottlenecks and optimize SQL queries.

InfoScope integrates with the INFO-OPTIMIZER suite. It can be used during application development to analyze SQL performance early in the development lifecycle. It provides insights into SQL query behavior in different environments.

InfoScope uses configuration files to define monitoring parameters, thresholds, and reporting options. These files specify the Db2 subsystems to monitor, the SQL statements to track, and the performance metrics to collect.

InfoScope captures SQL execution statistics such as CPU time, elapsed time, I/O operations, and buffer pool usage. It also tracks wait times for locks, latches, and other resources. This data is used to identify performance bottlenecks.

InfoScope's architecture includes a data collection component, a data repository, and a reporting interface. The data collection component captures SQL performance data from Db2. The data repository stores the collected data. The reporting interface provides tools for analyzing and visualizing the data.

InfoScope uses a Db2 database to store the collected performance data. The database schema includes tables for SQL statements, execution statistics, wait times, and resource consumption. The database is accessed using standard SQL queries.

InfoScope provides a command-line interface (CLI) for administrative tasks such as configuring monitoring parameters, starting and stopping data collection, and generating reports. The CLI is accessed through a terminal session.

InfoScope helps organizations improve the performance and efficiency of their Db2 applications. By identifying and resolving SQL performance bottlenecks, InfoScope can reduce CPU consumption, improve response times, and lower operating costs.

InfoScope enables organizations to proactively manage SQL performance and prevent performance problems before they impact users. By monitoring SQL execution statistics and wait times, InfoScope can identify potential issues and alert administrators.

InfoScope provides detailed insights into SQL query behavior, enabling developers to optimize SQL statements and improve application performance. By analyzing SQL execution statistics and resource consumption, developers can identify areas for improvement.

InfoScope supports authentication using RACF (Resource Access Control Facility). Users must have appropriate RACF permissions to access InfoScope functions and data. InfoScope integrates with RACF to validate user credentials.

InfoScope uses role-based access control (RBAC) to manage user permissions. Users are assigned to roles, and each role has specific permissions to access InfoScope functions and data. RBAC simplifies user management and ensures that users have only the necessary permissions.

InfoScope encrypts sensitive data at rest and in transit. Data at rest, such as SQL statements and execution statistics, is encrypted using AES (Advanced Encryption Standard). Data in transit is encrypted using TLS (Transport Layer Security).

InfoScope provides audit logging capabilities to track user activity and system events. Audit logs record user logins, logouts, configuration changes, and data access. These logs can be used for security monitoring and compliance reporting.

InfoScope provides monitoring and logging capabilities to track system health and performance. It monitors CPU usage, memory consumption, and disk space. It also logs system events, errors, and warnings. This data helps administrators identify and resolve operational issues.

InfoScope uses configuration files to define monitoring parameters, thresholds, and reporting options. These files specify the Db2 subsystems to monitor, the SQL statements to track, and the performance metrics to collect. Configuration files are typically stored in a dedicated directory.

InfoScope provides a command-line interface (CLI) for administrative tasks such as configuring monitoring parameters, starting and stopping data collection, and generating reports. The CLI is accessed through a terminal session.