Why Xmanager PXM0203 message indicating detection of Db2 subsystem initialization timing different than Db2 Master message

Products

• Database Management for DB2 for z/OS - Administration Suite
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - Recovery Suite
• Database Management for DB2 for z/OS - SQL Performance Suite
• Database Management for DB2 for z/OS - Utilities Suite
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

Why is Xmanager detection of the completion of Db2 initialization timing different from that of Db2 Master (ssidMSTR) as shown below?

01.49.59 STC24432 PXM0203 XMANAGER DETECTED INIT COMPLETE DB2=ssid
01.49.58 STC24581 *MCI5002I ssidMSTR INITIALIZATION COMPLETE.

Resolution

Db2 status tracking is done by a Xmanager component. This component does not use message tracking to determine DB2 subsystem status.
The tracking component periodically (in this case every 5 seconds) determines the current status of the Db2 subsystems by examining the
subsystems on the SSVT chain and examining the state of the subsystem address spaces and major Db2 control blocks.  Because Xmanager
Db2 status checking is independent of Db2 message activity it may not synchronize exactly with Db2 initialization and termination messages.

If the client is doing automated operations based on message triggers, then for Xmanager based applications such as Detector for Db2 for z/OS (PDT)
and Subsystem Analyzer for Db2 for z/OS (PSA) key off of the Xmanager issued DB2 status messages:

PXM0203 XMANAGER DETECTED INIT COMPLETE DB2=ssid
PXM0201 XMANAGER DETECTED TERM COMPLETE DB2=ssid