DB2 Subsystem List (in Thread Terminator) shows DB2 subsystems in the same SYSPLEX INACTIVE when they are not. See attached screen print. Thx.
Release : 20.0
Component : DB ADMIN SUITE FOR DB2 FOR Z/OS
This was the case of communication between r19 and r20 Xmanagers which is not supported and by default, r19 and r20 Xmanagers will not communicate with each other. We will soon be publishing a rolling sysplex upgrade enhancement, but that will only enable Xmanagers running at different maintenance levels to communicate with each other provided that the Xmanager group is at least at the minimum r20 active level set. So the rolling sysplex upgrade enhancement will prevent the INACTIVE symptom from occurring when you upgrade in the future. But for now, the best course is to wait until all of your Xmanagers are running r20. Once all of your Xmanagers are running r20, the INACTIVE symptom should be resolved.