Hello,
we are currently working on a workload comparison between Db2 for z/OS and Db2 for LUW, focusing strictly on database engine–level activity (not application or middleware events).
Our goal is to understand how to meaningfully align workload volume metrics across the two platforms, and we would appreciate guidance from those who have faced similar comparisons.
In particular, we are trying to clarify the following points:
1) Db2 for z/OS – SQL_CALLS semantics
Can you confirm that SQL_CALLS (from Db2 for z/OS accounting, SMF type 101) represents the total number of executed SQL statements, including:
- SELECT / SELECT INTO
- INSERT, UPDATE, DELETE, MERGE
- CALL statements
- Dynamic DDL (CREATE, ALTER, DROP executed dynamically)
- Other SQL constructs such as VALUES or SET statements
2) Stored procedure activity
Is there any Db2 for z/OS accounting or monitoring metric that represents the number of stored procedure invocations separately from the SQL statements executed inside the procedure?
3) Cross‑platform alignment strategy
When comparing Db2 z/OS and Db2 LUW workload volumes at database engine level, which Db2 LUW metrics are typically used to align with SQL_CALLS?
For example, do teams usually rely on activity/statement counters, UOW statistics, or other monitoring elements?
4) Tooling perspective
From your experience, do tools such as Db2 Performance Monitor add any fundamentally different workload volume metrics beyond SMF 101, or do they mainly provide deeper diagnostic granularity (thread-level detail, wait analysis, service classes)?
We are interested both in product semantics and practical experience on how similar comparisons are usually approached.
If helpful, we are particularly interested in patterns that allow consistent, repeatable comparisons over time.
Thank you in advance for any insights you can share.