Hi - a straight-forward question for which I would be grateful for an
explanation.

Why are ALL SQL/PL Stored Procedures associated with SYSIBM.SYSDUMMY1
even though the latter is NOT directly accessed via SQL within the SP?

Both an Explain against the Plan_Table and SYSPACKDEP state that the
Table is used.
>From the Plan_Table:-
- Lock Mode: UR Isolation
- Access: Sequential Scan / No Index.

Thanks

alex.mcshane@btinternet.com wrote:
> Hi - a straight-forward question for which I would be grateful for an
> explanation.
>
> Why are ALL SQL/PL Stored Procedures associated with SYSIBM.SYSDUMMY1
> even though the latter is NOT directly accessed via SQL within the SP?
>
> Both an Explain against the Plan_Table and SYSPACKDEP state that the
> Table is used.
>>From the Plan_Table:-
> - Lock Mode: UR Isolation
> - Access: Sequential Scan / No Index.
The SQL Procedure is doing some basic house-keeping which is done using
SQL Statements.
Keep in mind that SYSIBM.SYSDUMMY1 is just a VIEW over VALUES('Y').
None of these statements ever does an I/O or as much as hit the buffer pool.
There may be some fat in there to reduce basic CPU cycles for trivial
procedures, but that's about it.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab