Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.
Db2 13 function level 509 (FL509) enhances Db2 utility history so that it now captures the SHRLEVEL specification (NONE, REFERENCE, or CHANGE) for each utility execution. Tracking SHRLEVEL can help you:
ensure compliance with your organization’s standards and best practices
troubleshoot any concurrency problems
For example, you can use SHRLEVEL history to identify utilities that ran without SHRLEVEL CHANGE during peak business hours and evaluate their impact on concurrent workloads.
The SHRLEVEL value in effect for each utility execution is recorded in the new SHRLEVEL column in SYSIBM.SYSUTILITIES. The following example shows a snapshot of data from querying SYSUTILITIES: SQL statement: SELECT EVENTID, NAME, RETURNCODE, SHRLEVEL FROM SYSIBM.SYSUTILITIES ORDER BY ENDTS DESC
SELECT EVENTID, NAME, RETURNCODE, SHRLEVEL FROM SYSIBM.SYSUTILITIES ORDER BY ENDTS DESC
Output:
In the SHRLEVEL column, N=NONE, R=REFERENCE, and C=CHANGE. If the value is null, either the utility does not have the SHRLEVEL option, or the utility was run at a function level lower than 509. (In the preceding example, null is represented by?, but that value can vary by tool.) If SHRLEVEL was not explicitly specified for a utility that supports this option, the default value is used and recorded in this table.
?
Make sure to account for the new SHRLEVEL column in any existing queries or tools that reference SYSIBM.SYSUTILITIES.
For more information about utility history, see Monitoring utility history in IBM Documentation.
For more information about FL509, see Function level 509 in IBM Documentation.
Thank you to Kayla Boyd for her contributions to this blog post.
Copy