Xpediter and Stored Procedures

Eric Pearson

Xpediter and Stored Procedures
Anyone have any success using XPediter from Compuware
for debugging Stored Procedure? IBM recommends using
the "Debug Tool feature of COBOL/390". They want over $13K per
year to add this feature. We already have XPediter and would prefer
to avoid additional expense.

regards,

eric pearson
NS ITO Database Support



Tim Lowe

Re: Xpediter and Stored Procedures
(in response to Eric Pearson)
Eric,
We talked to Compuware about getting Xpediter support for testing stored
procedures, but when they came out with it, the extra cost for this feature
was too much for our management to approve. So, this is on hold for now.

Good luck,
Tim



"Pearson, Eric
L," To: [login to unmask email]
<Eric.Pearson@N cc:
SCORP.COM> Subject: Xpediter and Stored Procedures
Sent by: DB2
Data Base
Discussion List
<[login to unmask email]
>


12/13/2000
02:22 PM
Please respond
to DB2 Data
Base Discussion
List






Anyone have any success using XPediter from Compuware
for debugging Stored Procedure? IBM recommends using
the "Debug Tool feature of COBOL/390". They want over $13K per
year to add this feature. We already have XPediter and would prefer
to avoid additional expense.

regards,

eric pearson
NS ITO Database Support








Sibimon Philip

Re: Xpediter and Stored Procedures
(in response to John Cameron)
Same with us too. Cost seems to be much higher than what IBM is offering, if
it is 13K. We thought of using it for trail sometime to see all features we
want are there.



-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Wednesday, December 13, 2000 02:32 PM
To: [login to unmask email]
Subject: Re: Xpediter and Stored Procedures


Eric,
We talked to Compuware about getting Xpediter support for testing stored
procedures, but when they came out with it, the extra cost for this feature
was too much for our management to approve. So, this is on hold for now.

Good luck,
Tim



"Pearson, Eric
L," To: [login to unmask email]
<Eric.Pearson@N cc:
SCORP.COM> Subject: Xpediter and Stored
Procedures
Sent by: DB2
Data Base
Discussion List
<[login to unmask email]
>


12/13/2000
02:22 PM
Please respond
to DB2 Data
Base Discussion
List






Anyone have any success using XPediter from Compuware
for debugging Stored Procedure? IBM recommends using
the "Debug Tool feature of COBOL/390". They want over $13K per
year to add this feature. We already have XPediter and would prefer
to avoid additional expense.

regards,

eric pearson
NS ITO Database Support













John Cameron

Re: Xpediter and Stored Procedures
(in response to Tim Lowe)
Eric,
If the stored procedure is written in COBOL, we just set up a stub program
to call it and test
the stored procedure like any other COBOL sub-program. After the testing,
recompile it as
a stored procedure and define it to the system. Low-Tech, but it works.

Best of Luck,
John

John Cameron
[login to unmask email]
651.631.7188






[login to unmask email]
UL.COM To: [login to unmask email]
Sent by: DB2 cc:
Data Base Subject: Re: Xpediter and Stored Procedures
Discussion
List
<[login to unmask email]
OM>


12/13/00
02:31 PM
Please
respond to
DB2 Data Base
Discussion
List






Eric,
We talked to Compuware about getting Xpediter support for testing stored
procedures, but when they came out with it, the extra cost for this feature
was too much for our management to approve. So, this is on hold for now.

Good luck,
Tim



"Pearson, Eric
L," To: [login to unmask email]
<Eric.Pearson@N cc:
SCORP.COM> Subject: Xpediter and Stored
Procedures
Sent by: DB2
Data Base
Discussion List
<[login to unmask email]
>


12/13/2000
02:22 PM
Please respond
to DB2 Data
Base Discussion
List






Anyone have any success using XPediter from Compuware
for debugging Stored Procedure? IBM recommends using
the "Debug Tool feature of COBOL/390". They want over $13K per
year to add this feature. We already have XPediter and would prefer
to avoid additional expense.

regards,

eric pearson
NS ITO Database Support













Eric Kwai

Re: Xpediter and Stored Procedures
(in response to John Cameron)
John:
This is an excellent idea. We were having the same issue in our shop,
and your testing method will save us a bundle. Many Thanks.
One question, what do you do to SP that return result set?

Thanks in advance.
Eric Kwai
DBA



John Cameron

Re: Xpediter and Stored Procedures
(in response to Eric Kwai)
Eric,
We currently only have one stored procedure that returns a result set, and
the programmer who wrote it
isn't here today. I think he made a copy of his code and changed it to
send output parms for 1 row.
When his XPeditor testing was done, we wrote a COBOL stub that called it as
a stored procedure
(instructions in the Application Programming and SQL Guide 6-72 for V5) to
make sure it actually
sent the result sets. Again, very low tech.

All of our stored procudure use (so far) is to feed Visual Basic web app's
with
DB2 and VSAM data. It has saved us replicating the data to other
platforms/DBMS's.

Good Luck, John

John Cameron
[login to unmask email]
651.631.7188








Eric Kwai
<[login to unmask email] To: [login to unmask email]
CC.COM> cc:
Sent by: DB2 Subject: Re: Xpediter and Stored Procedures
Data Base
Discussion
List
<[login to unmask email]
OM>


12/14/00
08:56 AM
Please
respond to
DB2 Data Base
Discussion
List






John:
This is an excellent idea. We were having the same issue in our shop,
and your testing method will save us a bundle. Many Thanks.
One question, what do you do to SP that return result set?

Thanks in advance.
Eric Kwai
DBA