ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

THREAD DISPLAY IDB2 VERSUS OMEGAMON

book

Article ID: 17658

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer 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 Fast Load for DB2 for z/OS 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: