Strange Data studio issues

Myron Miller

Strange Data studio issues
We're running Data Studio 4.1.2 on both Db2 V11 and DB2 V12. we have one set of stored procedures where one SP calls about 15 others sometimes, up to 4-5 deep.


when we execute the first main procedure and it calls the second procedure (both defined with optional debug, we can get them to work. The minute we try to run them under DEBUG, then when the second SP is called, it gets thousands of -805s. procedure works just fine with execution w/o debug turned on but fails when run debug with -805. And if disable call to this SP and try another, same error works.


we have other SPs that call other sps where we don't get the -805s when we enable debug mode and enter DS debug..


How do i get rid of the -805s if debug mode is enable and operational? With it just enabled but NOT IN Data STUDIO Debug mode, it works fine. I've even bound the sps before entering debug mode. But still get -805s. Literally thousands.


And everything is NATIVE mode SPs.


Second question: These SPs all had a owner of XYZ which was also the owner/creator of the tables. But when anyone executes the SP, they get a -551 on access to a XYZ.tbname. Should XYZ have full access to XYZ tables. or am i missing something here.


Thanks Myron W. Miller

Sam Baugh

Strange Data studio issues
(in response to Myron Miller)
Just a thought.guess, refresh the debug WLM environment.

On Mon, Sep 25, 2017 at 2:24 PM, Myron Miller <[login to unmask email]> wrote:

> We're running Data Studio 4.1.2 on both Db2 V11 and DB2 V12. we have one
> set of stored procedures where one SP calls about 15 others sometimes, up
> to 4-5 deep.
>
>
> when we execute the first main procedure and it calls the second procedure
> (both defined with optional debug, we can get them to work. The minute we
> try to run them under DEBUG, then when the second SP is called, it gets
> thousands of -805s. procedure works just fine with execution w/o debug
> turned on but fails when run debug with -805. And if disable call to this
> SP and try another, same error works.
>
>
> we have other SPs that call other sps where we don't get the -805s when we
> enable debug mode and enter DS debug..
>
>
> How do i get rid of the -805s if debug mode is enable and operational?
> With it just enabled but NOT IN Data STUDIO Debug mode, it works fine.
> I've even bound the sps before entering debug mode. But still get -805s.
> Literally thousands.
>
>
> And everything is NATIVE mode SPs.
>
>
> Second question: These SPs all had a owner of XYZ which was also the
> owner/creator of the tables. But when anyone executes the SP, they get a
> -551 on access to a XYZ.tbname. Should XYZ have full access to XYZ
> tables. or am i missing something here.
>
>
> Thanks Myron W. Miller
>
> -----End Original Message-----
>

Myron Miller

Strange Data studio issues
(in response to Sam Baugh)
We've started the entire Data Studio environment over and over. Also tried ALTER PROC REGEN. Works fine when not trying to DEBUG but fails when DEBUG on with call to first DEBUGGABLE SP from original SP with -805.


And what's wierder is it's only one main SP. Others work fine calling others. just this one SP. And it's always to the first debuggable SP.


Thanks Myron W. Miller


________________________________
From: Sam Baugh <[login to unmask email]>
Sent: Monday, September 25, 2017 4:26 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: Strange Data studio issues

Just a thought.guess, refresh the debug WLM environment.

On Mon, Sep 25, 2017 at 2:24 PM, Myron Miller <[login to unmask email]<mailto:[login to unmask email]>> wrote:

We're running Data Studio 4.1.2 on both Db2 V11 and DB2 V12. we have one set of stored procedures where one SP calls about 15 others sometimes, up to 4-5 deep.


when we execute the first main procedure and it calls the second procedure (both defined with optional debug, we can get them to work. The minute we try to run them under DEBUG, then when the second SP is called, it gets thousands of -805s. procedure works just fine with execution w/o debug turned on but fails when run debug with -805. And if disable call to this SP and try another, same error works.


we have other SPs that call other sps where we don't get the -805s when we enable debug mode and enter DS debug..


How do i get rid of the -805s if debug mode is enable and operational? With it just enabled but NOT IN Data STUDIO Debug mode, it works fine. I've even bound the sps before entering debug mode. But still get -805s. Literally thousands.


And everything is NATIVE mode SPs.


Second question: These SPs all had a owner of XYZ which was also the owner/creator of the tables. But when anyone executes the SP, they get a -551 on access to a XYZ.tbname. Should XYZ have full access to XYZ tables. or am i missing something here.


Thanks Myron W. Miller

-----End Original Message-----

Greg Palgrave

RE: Strange Data studio issues
(in response to Myron Miller)

Hi Myron,

Have you applied any patches to Data Studio?

Items included in APAR3:
======IBM Data Studio client======
Fix PMR71151,122,000 - fix the issue debugging for native stored procedure on DB2 for z/OS.

I don't have the details on the PMR, but it may be relevant.

http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information+Management&product=ibm/Information+Management/IBM+Data+Studio&platform=All&function=all

The latest patch is DS412_APAR7_v20170922_0401Patch.zip which includes all the previous patches.

 

Cheers

Greg

In Reply to Myron Miller:

We're running Data Studio 4.1.2 on both Db2 V11 and DB2 V12. we have one set of stored procedures where one SP calls about 15 others sometimes, up to 4-5 deep.


when we execute the first main procedure and it calls the second procedure (both defined with optional debug, we can get them to work. The minute we try to run them under DEBUG, then when the second SP is called, it gets thousands of -805s. procedure works just fine with execution w/o debug turned on but fails when run debug with -805. And if disable call to this SP and try another, same error works.
...
And everything is NATIVE mode SPs.