SEO

Hi,

I have a statement event monitor on and am looking at the output. I
see a lot of executions of package SYSSH200. I looked in
syscat.statements to see what it executes and didn't find any
matches. How come and where can I find the section/statement
information for the package?

Thanks

Lew

"Lew" <sethwai@yahoo.com> wrote in message
news:66107889-2e29-47f0-8435-22e24841602c@34g2000hsh.googlegroups.com...
> Hi,
>
> I have a statement event monitor on and am looking at the output. I
> see a lot of executions of package SYSSH200. I looked in
> syscat.statements to see what it executes and didn't find any
> matches. How come and where can I find the section/statement
> information for the package?
>
> Thanks
>
> Lew

I believe that is the large cursor package that DB2 uses. Don't worry about
any packages that start with 'SYS'.

Mark A wrote:
> "Lew" <sethwai@yahoo.com> wrote in message
> news:66107889-2e29-47f0-8435-22e24841602c@34g2000hsh.googlegroups.com...
>> Hi,
>>
>> I have a statement event monitor on and am looking at the output. I
>> see a lot of executions of package SYSSH200. I looked in
>> syscat.statements to see what it executes and didn't find any
>> matches. How come and where can I find the section/statement
>> information for the package?
>>
>> Thanks
>>
>> Lew
>
> I believe that is the large cursor package that DB2 uses. Don't worry
> about any packages that start with 'SYS'.

Actually it is one of the _small_ cursor packages (65 sections in v8),
namely the one using WITH HOLD cursors with isolation level CS.
The naming convention for these packages for dynamic SQL can be found here:
http://www-1.ibm.com/support/docview...id=swg21115245

--
Jeroen

Mark A wrote:
> "Lew" <sethwai@yahoo.com> wrote in message
> news:66107889-2e29-47f0-8435-22e24841602c@34g2000hsh.googlegroups.com...
>> Hi,
>>
>> I have a statement event monitor on and am looking at the output. I
>> see a lot of executions of package SYSSH200. I looked in
>> syscat.statements to see what it executes and didn't find any
>> matches. How come and where can I find the section/statement
>> information for the package?
>>
>> Thanks
>>
>> Lew
>
> I believe that is the large cursor package that DB2 uses. Don't worry
> about any packages that start with 'SYS'.

Actually it is one of the _small_ cursor packages (65 sections in v8),
namely the one using WITH HOLD cursors with isolation level CS.
The naming convention for these packages for dynamic SQL can be found here:
http://www-1.ibm.com/support/docview...id=swg21115245

--
Jeroen

The Boss wrote:
> Mark A wrote:
>> "Lew" <sethwai@yahoo.com> wrote in message
>> news:66107889-2e29-47f0-8435-22e24841602c@34g2000hsh.googlegroups.com...
>>> Hi,
>>>
>>> I have a statement event monitor on and am looking at the output. I
>>> see a lot of executions of package SYSSH200. I looked in
>>> syscat.statements to see what it executes and didn't find any
>>> matches. How come and where can I find the section/statement
>>> information for the package?
>>>
>>> Thanks
>>>
>>> Lew
>>
>> I believe that is the large cursor package that DB2 uses. Don't worry
>> about any packages that start with 'SYS'.
>
> Actually it is one of the _small_ cursor packages (65 sections in v8),
> namely the one using WITH HOLD cursors with isolation level CS.
> The naming convention for these packages for dynamic SQL can be found
> here: http://www-1.ibm.com/support/docview...id=swg21115245

Similar info can be found in the Info Center.
For v8:
http://publib.boulder.ibm.com/infoce...d/r0007866.htm
For v9:
http://publib.boulder.ibm.com/infoce...c/r0007866.htm

--
Jeroen

Thanks for all the info. Still the question remains as to why I don't
see the package statement/section information in syscat.statements.

"Lew" <sethwai@yahoo.com> wrote in message
news:65e39b43-f2ee-468f-9fac-b219931f5364@24g2000hsh.googlegroups.com...
> Thanks for all the info. Still the question remains as to why I don't
> see the package statement/section information in syscat.statements.

You have way too much time on your hands. Those packages are for internal
DB2 use.