About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Dear James, Thank you for submitting this enhancement request. Our Db2 for z/OS team reviewed it and has the following feedback for you:
Generally speaking, utilities messages issued from the application address space does not have the Db2 subsystem name included, while messages issued from the Db2 DBM1 address space does have the subsystem name included as part of the message. Instead of relying on parsing thru a utility message to determine the subsystem it is run on, Db2 13 introduced the utility history catalog table SYSIBM.SYSUTILITIES, and you can query its GROUP_MEMBER column to determine the Db2 subsystem name the utility was executed in.
We believe this is a more versatile solution for auditing purposes as well as post-analysis of utility executions.
We appreciate your input to the Db2 for z/OS development team. And we hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.
Sincerely,
Db2 for z/OS Team