THREAD DISPLAY IDB2 VERSUS OMEGAMON

Products

• CA RC/Migrator
• CA Endevor SCM Interface
• DB2 Administration
• CA RC Compare for DB2 for z/OS
• CA RC Extract for DB2 for z/OS
• CA RC/Query
• CA RC Secure for DB2 for z/OS
• CA RC Update for DB2 for z/OS
• CA Bind Analyzer for DB2 for z/OS
• CA Detector
• CA SQL-Ease for DB2 for z/OS
• CA Sysview Performance Management Option for DB2 for z/OS
• CA Database Detector for DB2 for z/OS
• CA Plan Analyzer for DB2 for z/OS
• CA Subsystem Analyzer for DB2 for z/OS
• CA Database Analyzer for DB2 for z/OS
• CA Fast Unload for DB2 for z/OS
• CA Fast Check for DB2 for z/OS
• CA Fast Index for DB2 for z/OS
• CA Fast Load for DB2 for z/OS
• CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

Insight Active thread display with ALL as variable for a Correlation ID of an application server shows more threads( all of them either PARENT-D OR CHSUM-D, with one exception of DDF ) than Omegamon DB2 display of all active thread for the same time. There is a big discrepancy between IDB2 and Omegamon. How to reconcile the two?

Solution:

The difference between the two is due to the fact that the systems with fewer threads have the current degree set to 1 for parallelism while the system with more threads has the current degree set to any for parallelism.

Environment

Release: BINDAN00200-14-Bind Analyzer-for DB2 for z/OS
Component: