Enhance DSNT375I deadlock message to include DRP global variable use

Following the introduction of the CURRENT LOCK TIMEOUT (CLT) special register and DEADLOCK_RESOLUTION_PRIORITY (DRP) global variable with EPIC 8876, the DSNT376I timeout message has been enhanced to show the timeout values used for both requester and holder, along with the source for those values (IRLMRWT / CLT Special Register / IRLM). However, the DSNT375I deadlock message has not been enhanced accordingly. There is no indication in the DSNT375I message that DEADLOCK_RESOLUTION_PRIORITY was in play or not.
Please consider enhancing the DSNT375I to show the deadlock weighting value for both the victim and victor, along with the source for those values ("System" or DRP global variable) where "System" means that the DRP global variable was not set and therefore deadlock resolution was based on Db2 internal factors such as number of log records for example.
If neither CLT nor DRP are in use, then we'll do what we do now (and have always done) in the event of a timeout or deadlock and go back to first principles.
But with the introduction of these two new features, it seems like such a missed opportunity to externalise the DRP information in the DSNT375I message, to maximise the benefits.
No only will this simplify deadlock investigations (Application Teams and DBA's can do their own analysis from MSTR without having to run OMPE reports for IFCID 172), but it will also increase the likelihood of DBA's being more successful when using the DRP feature in an attempt to force through DDL - if an attempt fails they'll be easily able to see how thier chosen value compares to what process they lost against.
Further still, it will simplify our monitoring of the use of the DRP feature once we've granted the write privilege required to set the global variable value.