search cancel



Article ID: 17646


Updated On:


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 Rapid Reorg for DB2 for z/OS



What does the status of PARENT-D and CHSUM-D mean? Is this an enhancement of the old DDF status? Some of the get pages keep increasing, but not all of them. Any reason why these statuses are in RED?

Does the status change when the thread is actually in DB2?


Here are the explanations for all the statuses:

CHILD-D CHILD thread executing SQL code.
PARENT-D PARENT thread executing SQL code.
PARENT-A PARENT thread executing application code.
CHSUM-D CHILD summary thread executing SQL code.
CHILDSUM CHILD summary thread not executing in DB2 code.

To understand these fields, you should read about parallel tasks in the DB2 Administration Guide. Briefly, when the facility is enabled and DB2

determines via its own rules & algorithms that it can process multiple I/O operations for the same request independently, DB2 will create a separate thread to process each I/O. These additional processes are CHILD processes. The original thread is the PARENT.

The SUMMARY record is a record which contains the totals of the parent and all children in a subsystem that

  1. supports parallel processing, and

  2. the appserver threads stay connected because of the Keepdynamic (yes) parameter in the bind plan.

The thread status will change instantaneously to "not-active" or "waiting-for-request" if the appserver threads, both parents and children, are not serving any request.


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