What are the Pointer Check options with Database Analyzer?

Products

• 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:

What are the differences of running FUNCTION=ANALYZE,POINTERCHECK=LOCAL/CROSSDSG/CROSSDBDor FUNCTION=ANALYZEALL using Database Analyzer?

Solution:

There are different kinds of checking possible with Database Analyzer.

1. FUNCTION=ANALYZE,POINTERCHECK=LOCAL
   
   Just checks the pointer within a specific dataset, pointer pointing to related datasets (e.g. index databases or different dataset groups) will NOT be checked.This usually is fine if Database Analyzer will be invoked by DBCOPY to check the pointer at the same time when a dataset will be image copied.
   
   
2. FUNCTION=ANALYZE,POINTERCHECK=CROSSDSG
   
   This forces Database Analyzer also to check pointers which point into a different dataset, containing segments belonging to a differentdataset group.
   
   
3. FUNCTION=ANALYZE,POINTERCHECK=CROSSDBD
   
   This forces Database Analyzer to check all pointers for a specific dataset, including those pointing to index databases, different datasetincluding those pointing to index databases, different dataset groups or logical related databases.
   
   
4. FUNCTION=ANALYZEALL
   
   This function is checking all related database datasets on the deepest level by default (POINTERCHECK=CROSSDBD) and is the recommended FUNCTION when Database Analyzer will be run as standalone execution.

Environment

Release:
Component: DBA