XMID=2000 After R20 Upgrade

book

Article ID: 196771

calendar_today

Updated On:

Products

CA Database Management for DB2 for z/OS - Performance Suite CA Database Management for DB2 for z/OS - SQL Performance Suite CA Detector for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

After R20 upgrade , why is  xmid=2000 on one system and xmid=0001 on another as shown below? 

PXM0100 CA/XMANAGER 20.0 INIT IN PROGRESS ID=2000
PXM0410 XMANAGER MSLOGGER INIT ENTERED XMID=2000 
PXM0411 XMANAGER MSLOGGER INIT COMPLETE XMID=2000

    
PXM0100 CA/XMANAGER 20.0 INIT IN PROGRESS ID=0001
PXM0410 XMANAGER MSLOGGER INIT ENTERED XMID=0001 
PXM0411 XMANAGER MSLOGGER INIT COMPLETE XMID=0001

Environment

Release : 20.0

Component : General Services for DB2

Resolution

The following display
PXM0100 CA/XMANAGER 20.0 INIT IN PROGRESS ID=2000
PXM0410 XMANAGER MSLOGGER INIT ENTERED XMID=2000 
PXM0411 XMANAGER MSLOGGER INIT COMPLETE XMID=2000

is because the xmanid is 0000 which is the default. During Xmanager execution, the default value 0000 is converted to the current
 Xmanager version number. So a default of 0000 is converted to 2000.

If you check the  CDBAPARM(SETUPXX) and do a find on XMANID you'll find your XMANID.