Toad World® Forums

navigator [1 Attachment]


#1

[ Attachment(s) from john.enevoldson_671 included below]

Message from: john.enevoldson_671

Hi, Not sure if this is really a beta issue but when we open an sql stored
procedure in the editor the navigator does not show the statements as expected -
we simply see “block” for the entire code between the begin and end statemetnts
in the sp. See attachad image. This makes the navigator failry worthless when
editing stored procedures which is a shame as otherwise it’s very useful. Best
regards, John.


Historical Messages

Author: john.enevoldson_671
Date: Fri May 28 04:04:32 PDT 2010
Hi, Not sure if this is really a beta issue but when we open an sql stored
procedure in the editor the navigator does not show the statements as expected -
we simply see “block” for the entire code between the begin and end statemetnts
in the sp. See attachad image. This makes the navigator failry worthless when
editing stored procedures which is a shame as otherwise it’s very useful. Best
regards, John.
__


Attachment(s) from john.enevoldson_671

1 of 1 File(s)

toadnav.rtf


#2

Hi John,

Verify that you have all statements checked in your options for navigation
display. To do this go to Tools|Options|Editor|Tools.

On the right hand side of that dialog you will see the following :

Select all and then Apply the changes. Let me know if you still get the
incomplete results in the navigation panel.
Thanks,

Nancy Alsip
image001.png


#3

Message from: john.enevoldson_671

Hi Nancy, “select all” is checked and applied but makes no difference. The body
of the stored procedure is still shown as “block” rather than as individual
statements. Regards, John.


Historical Messages

Author: john.enevoldson_671
Date: Sun May 30 22:51:28 PDT 2010
Hi Nancy, “select all” is checked and applied but makes no difference. The body
of the stored procedure is still shown as “block” rather than as individual
statements. Regards, John.
__

Author: Nancy Alsip
Date: Fri May 28 06:49:10 PDT 2010
Hi John, Verify that you have all statements checked in your options for
navigation display. To do this go to Tools|Options|Editor|Tools. On the right
hand side of that dialog you will see the following : Select all and then Apply
the changes. Let me know if you still get the incomplete results in the
navigation panel. Thanks, Nancy Alsip
__

Author: john.enevoldson_671
Date: Fri May 28 04:04:32 PDT 2010
[ Attachment(s) from john.enevoldson_671 included below] Message from:
john.enevoldson_671 Hi, Not sure if this is really a beta issue but when we open
an sql stored procedure in the editor the navigator does not show the statements
as expected - we simply see “block” for the entire code between the begin and
end statemetnts in the sp. See attachad image. This makes the navigator failry
worthless when editing stored procedures which is a shame as otherwise it’s very
useful. Best regards, John. _______________________________________ Historical
Messages Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not
sure if this is really a beta issue but when we open an sql stored procedure in
the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. __ _______________________________________ Attachment(s) from
john.enevoldson_671 1 of 1 File(s) toadnav.rtf
__



#4

Hi Nancy,
“select all” is checked and applied but makes no difference. The body of the stored procedure is still shown as “block” rather than as individual statements.
Regards,
John.


#5

Message from: john.enevoldson_671

Hi Nancy, Have you managed to have a look at this yet ? Regards, John.


Historical Messages

Author: john.enevoldson_671
Date: Thu Jun 03 22:53:53 PDT 2010
Hi Nancy, Have you managed to have a look at this yet ? Regards, John.
__

Author: john.enevoldson_671
Date: Sun May 30 22:51:28 PDT 2010
Hi Nancy, “select all” is checked and applied but makes no difference. The body
of the stored procedure is still shown as “block” rather than as individual
statements. Regards, John.
__

Author: john.enevoldson_671
Date: Sun May 30 22:51:28 PDT 2010
Message from: john.enevoldson_671 Hi Nancy, “select all” is checked and applied
but makes no difference. The body of the stored procedure is still shown as
“block” rather than as individual statements. Regards, John.
_______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Sun May 30 22:51:28 PDT 2010 Hi Nancy, “select all” is
checked and applied but makes no difference. The body of the stored procedure is
still shown as “block” rather than as individual statements. Regards, John. __
Author: Nancy Alsip Date: Fri May 28 06:49:10 PDT 2010 Hi John, Verify that you
have all statements checked in your options for navigation display. To do this
go to Tools|Options|Editor|Tools. On the right hand side of that dialog you will
see the following : Select all and then Apply the changes. Let me know if you
still get the incomplete results in the navigation panel. Thanks, Nancy Alsip __
Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 [ Attachment(s)
from john.enevoldson_671 included below] Message from: john.enevoldson_671 Hi,
Not sure if this is really a beta issue but when we open an sql stored procedure
in the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. _______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not sure if this is
really a beta issue but when we open an sql stored procedure in the editor the
navigator does not show the statements as expected - we simply see “block” for
the entire code between the begin and end statemetnts in the sp. See attachad
image. This makes the navigator failry worthless when editing stored procedures
which is a shame as otherwise it’s very useful. Best regards, John. __
_______________________________________ Attachment(s) from john.enevoldson_671 1
of 1 File(s) toadnav.rtf __ _______________________________________
__

Author: Nancy Alsip
Date: Fri May 28 06:49:10 PDT 2010
Hi John, Verify that you have all statements checked in your options for
navigation display. To do this go to Tools|Options|Editor|Tools. On the right
hand side of that dialog you will see the following : Select all and then Apply
the changes. Let me know if you still get the incomplete results in the
navigation panel. Thanks, Nancy Alsip
__

Author: john.enevoldson_671
Date: Fri May 28 04:04:32 PDT 2010
[ Attachment(s) from john.enevoldson_671 included below] Message from:
john.enevoldson_671 Hi, Not sure if this is really a beta issue but when we open
an sql stored procedure in the editor the navigator does not show the statements
as expected - we simply see “block” for the entire code between the begin and
end statemetnts in the sp. See attachad image. This makes the navigator failry
worthless when editing stored procedures which is a shame as otherwise it’s very
useful. Best regards, John. _______________________________________ Historical
Messages Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not
sure if this is really a beta issue but when we open an sql stored procedure in
the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. __ _______________________________________ Attachment(s) from
john.enevoldson_671 1 of 1 File(s) toadnav.rtf
__



#6

Hi Nancy,
Have you managed to have a look at this yet ?
Regards,
John.


#7

Hi John,

I had posted a message on 5/28 with instructions to try setting the options
differently and was waiting for your response.

Did you see that post and have a chance to try the suggestion?
Nancy


#8

Message from: Nancy

Hi John,
My apologies for the delay. I missed your previous response. I will have to send
this issue to the developers responsible for this area. In my test I am able to
see while-loops and if-statements within a block. Can you send me the text
within the block that you are testing so we can document the issue with the
details? I have opened CR 74,518 to track this.
Thanks.
Nancy


Historical Messages

Author: Nancy Alsip
Date: Fri Jun 04 06:02:02 PDT 2010
Hi John,
My apologies for the delay. I missed your previous response. I will have to send
this issue to the developers responsible for this area. In my test I am able to
see while-loops and if-statements within a block. Can you send me the text
within the block that you are testing so we can document the issue with the
details? I have opened CR 74,518 to track this.
Thanks.
Nancy

__

Author: Nancy Alsip
Date: Fri Jun 04 05:17:11 PDT 2010
Hi John, I had posted a message on 5/28 with instructions to try setting the
options differently and was waiting for your response. Did you see that post and
have a chance to try the suggestion? Nancy
__

Author: john.enevoldson_671
Date: Thu Jun 03 22:53:53 PDT 2010
Hi Nancy, Have you managed to have a look at this yet ? Regards, John.
__

Author: john.enevoldson_671
Date: Thu Jun 03 22:53:53 PDT 2010
Message from: john.enevoldson_671 Hi Nancy, Have you managed to have a look at
this yet ? Regards, John. _______________________________________ Historical
Messages Author: john.enevoldson_671 Date: Thu Jun 03 22:53:53 PDT 2010 Hi
Nancy, Have you managed to have a look at this yet ? Regards, John. __ Author:
john.enevoldson_671 Date: Sun May 30 22:51:28 PDT 2010 Hi Nancy, “select all” is
checked and applied but makes no difference. The body of the stored procedure is
still shown as “block” rather than as individual statements. Regards, John. __
Author: john.enevoldson_671 Date: Sun May 30 22:51:28 PDT 2010 Message from:
john.enevoldson_671 Hi Nancy, “select all” is checked and applied but makes no
difference. The body of the stored procedure is still shown as “block” rather
than as individual statements. Regards, John.
_______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Sun May 30 22:51:28 PDT 2010 Hi Nancy, “select all” is
checked and applied but makes no difference. The body of the stored procedure is
still shown as “block” rather than as individual statements. Regards, John. __
Author: Nancy Alsip Date: Fri May 28 06:49:10 PDT 2010 Hi John, Verify that you
have all statements checked in your options for navigation display. To do this
go to Tools|Options|Editor|Tools. On the right hand side of that dialog you will
see the following : Select all and then Apply the changes. Let me know if you
still get the incomplete results in the navigation panel. Thanks, Nancy Alsip __
Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 [ Attachment(s)
from john.enevoldson_671 included below] Message from: john.enevoldson_671 Hi,
Not sure if this is really a beta issue but when we open an sql stored procedure
in the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. _______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not sure if this is
really a beta issue but when we open an sql stored procedure in the editor the
navigator does not show the statements as expected - we simply see “block” for
the entire code between the begin and end statemetnts in the sp. See attachad
image. This makes the navigator failry worthless when editing stored procedures
which is a shame as otherwise it’s very useful. Best regards, John. __
_______________________________________ Attachment(s) from john.enevoldson_671 1
of 1 File(s) toadnav.rtf __ _______________________________________ __ Author:
Nancy Alsip Date: Fri May 28 06:49:10 PDT 2010 Hi John, Verify that you have all
statements checked in your options for navigation display. To do this go to
Tools|Options|Editor|Tools. On the right hand side of that dialog you will see
the following : Select all and then Apply the changes. Let me know if you still
get the incomplete results in the navigation panel. Thanks, Nancy Alsip __
Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 [ Attachment(s)
from john.enevoldson_671 included below] Message from: john.enevoldson_671 Hi,
Not sure if this is really a beta issue but when we open an sql stored procedure
in the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. _______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not sure if this is
really a beta issue but when we open an sql stored procedure in the editor the
navigator does not show the statements as expected - we simply see “block” for
the entire code between the begin and end statemetnts in the sp. See attachad
image. This makes the navigator failry worthless when editing stored procedures
which is a shame as otherwise it’s very useful. Best regards, John. __
_______________________________________ Attachment(s) from john.enevoldson_671 1
of 1 File(s) toadnav.rtf __ _______________________________________
__

Author: john.enevoldson_671
Date: Sun May 30 22:51:28 PDT 2010
Hi Nancy, “select all” is checked and applied but makes no difference. The body
of the stored procedure is still shown as “block” rather than as individual
statements. Regards, John.
__

Author: john.enevoldson_671
Date: Sun May 30 22:51:28 PDT 2010
Message from: john.enevoldson_671 Hi Nancy, “select all” is checked and applied
but makes no difference. The body of the stored procedure is still shown as
“block” rather than as individual statements. Regards, John.
_______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Sun May 30 22:51:28 PDT 2010 Hi Nancy, “select all” is
checked and applied but makes no difference. The body of the stored procedure is
still shown as “block” rather than as individual statements. Regards, John. __
Author: Nancy Alsip Date: Fri May 28 06:49:10 PDT 2010 Hi John, Verify that you
have all statements checked in your options for navigation display. To do this
go to Tools|Options|Editor|Tools. On the right hand side of that dialog you will
see the following : Select all and then Apply the changes. Let me know if you
still get the incomplete results in the navigation panel. Thanks, Nancy Alsip __
Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 [ Attachment(s)
from john.enevoldson_671 included below] Message from: john.enevoldson_671 Hi,
Not sure if this is really a beta issue but when we open an sql stored procedure
in the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. _______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not sure if this is
really a beta issue but when we open an sql stored procedure in the editor the
navigator does not show the statements as expected - we simply see “block” for
the entire code between the begin and end statemetnts in the sp. See attachad
image. This makes the navigator failry worthless when editing stored procedures
which is a shame as otherwise it’s very useful. Best regards, John. __
_______________________________________ Attachment(s) from john.enevoldson_671 1
of 1 File(s) toadnav.rtf __ _______________________________________
__

Author: Nancy Alsip
Date: Fri May 28 06:49:10 PDT 2010
Hi John, Verify that you have all statements checked in your options for
navigation display. To do this go to Tools|Options|Editor|Tools. On the right
hand side of that dialog you will see the following : Select all and then Apply
the changes. Let me know if you still get the incomplete results in the
navigation panel. Thanks, Nancy Alsip
__

Author: john.enevoldson_671
Date: Fri May 28 04:04:32 PDT 2010
[ Attachment(s) from john.enevoldson_671 included below] Message from:
john.enevoldson_671 Hi, Not sure if this is really a beta issue but when we open
an sql stored procedure in the editor the navigator does not show the statements
as expected - we simply see “block” for the entire code between the begin and
end statemetnts in the sp. See attachad image. This makes the navigator failry
worthless when editing stored procedures which is a shame as otherwise it’s very
useful. Best regards, John. _______________________________________ Historical
Messages Author: john.enevoldson_671 Date: Fri May 28 04:04:32 PDT 2010 Hi, Not
sure if this is really a beta issue but when we open an sql stored procedure in
the editor the navigator does not show the statements as expected - we simply
see “block” for the entire code between the begin and end statemetnts in the sp.
See attachad image. This makes the navigator failry worthless when editing
stored procedures which is a shame as otherwise it’s very useful. Best regards,
John. __ _______________________________________ Attachment(s) from
john.enevoldson_671 1 of 1 File(s) toadnav.rtf
__



#9

Hi John,
My apologies for the delay. I missed your previous response. I will have to send this issue to the developers responsible for this area. In my test I am able to see while-loops and if-statements within a block. Can you send me the text within the block that you are testing so we can document the issue with the details? I have opened CR 74,518 to track this.
Thanks.
Nancy


#10

Message from: john.enevoldson_671

Hi Nancy, Here comes a code sample that the navigator shows only as a block:
CREATE OR REPLACE PROCEDURE “PXX”.“PPVDLS3121SP1” ( INOUT “FTG” CHARACTER(2),
OUT “RETKOD” CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE”
CHARACTER(5) ) SPECIFIC “PPVDLS3121SP1” DYNAMIC RESULT SETS 1 LANGUAGE SQL NOT
DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA CALLED ON
NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL –


#11

Hi Nancy,

Here comes a code sample that the navigator shows only as a block:

CREATE OR REPLACE PROCEDURE “PXX”.“PPVDLS3121SP1” (
INOUT “FTG” CHARACTER(2),
OUT “RETKOD” CHARACTER(22),
OUT “RETTEXT” CHARACTER(50),
OUT “RETSQLSTATE” CHARACTER(5) )
SPECIFIC “PPVDLS3121SP1”
DYNAMIC RESULT SETS 1
LANGUAGE SQL
NOT DETERMINISTIC
COMMIT ON RETURN NO
EXTERNAL ACTION
MODIFIES SQL DATA
CALLED ON NULL INPUT
INHERIT SPECIAL REGISTERS
OLD SAVEPOINT LEVEL
– *********************************************************************************************************
– Beskrivning: Bestämmer default utlämningsställe för en ny order.
– Dcl i CMS: PXXDD053
– Ändrad av Dag/Tid Kommentar
– *********************************************************************************************************
P1: BEGIN
declare SQLSTATE char(5) default ‘00000’;
declare hSqlstate char(5) default ‘00000’;

DECLARE hRetKod char(22) default '99';
DECLARE hRetText char(50) default '';
declare hRetsqlerrm varchar(500) default '';

declare hhamta char(1) default 'N';

declare hgamforstyp char(2) default '01';
declare hnyforstyp char(2) default '';

– *************************************************************************************************
– Deklarera hantering av fel
– *************************************************************************************************
declare exit handler for sqlexception, sqlwarning
begin
values (‘PPVDLS3121SP1-999’, SQLSTATE) into PPVDLS3121SP1.RetKod, PPVDLS3121SP1.RetSqlState;
– Nu lämnar vi Linux proceduren.
end;

declare continue handler for sqlstate '02000'
begin
  set hSqlState = SQLSTATE;
end;

set PPVDLS3121SP1.RetText = 'Start PPVDLS3121SP1';
values ('999', ' ')
  into PPVDLS3121SP1.RetKod, PPVDLS3121SP1.RetSqlState;

for v1 as

	select ftg,fok,faktnr,levnssa
	from xordutbrutto
	where ftg = '01'

	do

		values('update xordforsandutbrutto','00000') into PPVDLS3121SP1.RetText,hsqlstate;

		update xordforsandutbrutto
		set forsandtyp = (case v1.levnssa when '02' then '01' else '02' end )
		where ftg = v1.ftg
		and fok = v1.fok
		and faktnr = v1.faktnr;

end for;

set PPVDLS3121SP1.RetKod = '000';

END P1;


#12

Message from: john.enevoldson_671

Hi, Ok, I think the problem is linked to the create procedure statement -if I
take this away leaving the block starting P1:begin and ending end P1; and then
formatt the code then everything shows as one expects in the navigator (with the
exception of the for statement, which is soemething you may need to look at).
This is not really so good - we don’t want to have to take away the create
statement in order just to use the navigator (we would need to add the create
statement prior to building the routine). It would be good to get this fixed
under this beta. Regards, John.


Historical Messages

Author: john.enevoldson_671
Date: Sun Jun 06 22:52:02 PDT 2010
Hi, Ok, I think the problem is linked to the create procedure statement -if I
take this away leaving the block starting P1:begin and ending end P1; and then
formatt the code then everything shows as one expects in the navigator (with the
exception of the for statement, which is soemething you may need to look at).
This is not really so good - we don’t want to have to take away the create
statement in order just to use the navigator (we would need to add the create
statement prior to building the routine). It would be good to get this fixed
under this beta. Regards, John.
__

Author: john.enevoldson_671
Date: Sun Jun 06 22:04:22 PDT 2010
Hi Nancy, Here comes a code sample that the navigator shows only as a block:
CREATE OR REPLACE PROCEDURE “PXX”.“PPVDLS3121SP1” ( INOUT “FTG” CHARACTER(2),
OUT “RETKOD” CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE”
CHARACTER(5) ) SPECIFIC “PPVDLS3121SP1” DYNAMIC RESULT SETS 1 LANGUAGE SQL NOT
DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA CALLED ON
NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL –


#13

Hi,

Ok, I think the problem is linked to the create procedure statement -if I take this away leaving the block starting P1:begin and ending end P1; and then formatt the code
then everything shows as one expects in the navigator (with the exception of the for statement, which is soemething you may need to look at).

This is not really so good - we don’t want to have to take away the create statement
in order just to use the navigator (we would need to add the create statement prior to building the routine).

It would be good to get this fixed under this beta.

Regards,

John.


#14

Message from: john.enevoldson_671

Hi again, Another point - the navigator does not seem to handle values stmt at
al eg: values (‘00000’, 'koll1 ') into hSqlState, RETTEXT; Nor do case or if
statements show up. Regards, John.l


Historical Messages

Author: john.enevoldson_671
Date: Sun Jun 06 23:05:44 PDT 2010
Hi again, Another point - the navigator does not seem to handle values stmt at
al eg: values (‘00000’, 'koll1 ') into hSqlState, RETTEXT; Nor do case or if
statements show up. Regards, John.l
__

Author: john.enevoldson_671
Date: Sun Jun 06 22:52:02 PDT 2010
Hi, Ok, I think the problem is linked to the create procedure statement -if I
take this away leaving the block starting P1:begin and ending end P1; and then
formatt the code then everything shows as one expects in the navigator (with the
exception of the for statement, which is soemething you may need to look at).
This is not really so good - we don’t want to have to take away the create
statement in order just to use the navigator (we would need to add the create
statement prior to building the routine). It would be good to get this fixed
under this beta. Regards, John.
__

Author: john.enevoldson_671
Date: Sun Jun 06 22:52:02 PDT 2010
Message from: john.enevoldson_671 Hi, Ok, I think the problem is linked to the
create procedure statement -if I take this away leaving the block starting
P1:begin and ending end P1; and then formatt the code then everything shows as
one expects in the navigator (with the exception of the for statement, which is
soemething you may need to look at). This is not really so good - we don’t want
to have to take away the create statement in order just to use the navigator (we
would need to add the create statement prior to building the routine). It would
be good to get this fixed under this beta. Regards, John.
_______________________________________ Historical Messages Author:
john.enevoldson_671 Date: Sun Jun 06 22:52:02 PDT 2010 Hi, Ok, I think the
problem is linked to the create procedure statement -if I take this away leaving
the block starting P1:begin and ending end P1; and then formatt the code then
everything shows as one expects in the navigator (with the exception of the for
statement, which is soemething you may need to look at). This is not really so
good - we don’t want to have to take away the create statement in order just to
use the navigator (we would need to add the create statement prior to building
the routine). It would be good to get this fixed under this beta. Regards, John.
__ Author: john.enevoldson_671 Date: Sun Jun 06 22:04:22 PDT 2010 Hi Nancy, Here
comes a code sample that the navigator shows only as a block: CREATE OR REPLACE
PROCEDURE “PXX”.“PPVDLS3121SP1” ( INOUT “FTG” CHARACTER(2), OUT “RETKOD”
CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE” CHARACTER(5) )
SPECIFIC “PPVDLS3121SP1” DYNAMIC RESULT SETS 1 LANGUAGE SQL NOT DETERMINISTIC
COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA CALLED ON NULL INPUT
INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL –
__

Author: john.enevoldson_671
Date: Sun Jun 06 22:04:22 PDT 2010
Hi Nancy, Here comes a code sample that the navigator shows only as a block:
CREATE OR REPLACE PROCEDURE “PXX”.“PPVDLS3121SP1” ( INOUT “FTG” CHARACTER(2),
OUT “RETKOD” CHARACTER(22), OUT “RETTEXT” CHARACTER(50), OUT “RETSQLSTATE”
CHARACTER(5) ) SPECIFIC “PPVDLS3121SP1” DYNAMIC RESULT SETS 1 LANGUAGE SQL NOT
DETERMINISTIC COMMIT ON RETURN NO EXTERNAL ACTION MODIFIES SQL DATA CALLED ON
NULL INPUT INHERIT SPECIAL REGISTERS OLD SAVEPOINT LEVEL –


#15

Hi again,

Another point - the navigator does not seem to handle values stmt at al eg:

values (‘00000’, 'koll1 ') into hSqlState, RETTEXT;

Nor do case or if statements show up.

Regards,

John.l


#16

John,

Thank you for the SQL and additional comments. I have added them to the text of the CR Nancy has already created, 74518.

Ken Ryan
Toad for DB2 Developer
Quest Software