Ensuring RTS information is accurate for CA DATABASE ANALYZER for DB2 for z/OS

Products

• RC Compare for DB2 for z/OS
• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS
• CA Distributed Database Management
• CA Database Analyzer for DB2 for Oracle
• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS

Issue/Introduction

Description:

The trend today is to use RTS (Real Time Statistics) information.

How do we avoid problems when using RTS to generate accurate action JCL for Utilities during Extract Procedure execution, for

example, SQL+100, -406 or -820 errors caused by RTS inconsistencies?

Solution:

Since maintenance with r11.5 release, CA DATABASE ANALYZER for DB2 for z/OS (PDA) provides help to verify and initialize IBM Real-Time Statistics (RTS) that are missing.

A new feature was added to the main PDA panel ("3) Statistics Maintenance") to the support initializing the Real Time Statistics (RTS) tables. The Update Statistics for IBM Real-Time Statistics (RTS) function will generate the necessary Batch Processor JCL and control cards to either verify or update missing RTS statistics from the DB2 Real-Time Statistics tables for tablespaces and indexes.

Also you can be proactive and make sure that RTS tables are current and accurate by using:

• For r11.5 and r12 releases: <ca_lib>.SRCLIB(RTOSESQL)
  
  
• For r14 and higher releases: <ca_lib>.CDBASRC(RTOSESQL)

Environment

Release:
Component: DBA