We have monitors on other tools that the programmers have access to.

How do you monitor the Qshell db2 utility? Or a REXX proc that accepts and runs SQL dynamically (like STRSQL would do)? With monitors for functions like those, adapting for STRSQL should be easy.

If STRSQL is explicitly needed, then either the QIBM_QCA_RTV_COMMAND exit point for a Command Analyzer Retrieve Exit Program or QIBM_QCA_CHG_COMMAND for a Command Analyzer Change Exit Program could be useful. An exit program might run a Start Database Monitor (STRDBMON) command to have a database monitor run while STRSQL is running.

Without additional work, a database monitor that is scoped to a job will continue to run until the job ends. But you can ignore anything collected that isn't in your chosen scope. The monitor will end when the job ends, if nothing else is provided to end it first.

Of course, you could also run STRDBMON for a system-wide monitor. In that scenario, you might want a daily scheduled job that ends and restarts the monitor. When a new monitor repository is created, the scheduled job could process what was in the previous day's repository and save relevant items into a permanent archive before deleting the old daily copy.

If you prefer vendor responses, post back.

Tom