Stored Procedure Builder Debug Features Disabled??

[DB2Novice]

Hi,

I have installed V7.2 of the Stored Procedure Builder on a Win2K client. The database is running on Linux and is V7.1.

I am creating procedures in DB2 for the first time and using the Stored Procedure Builder; all my Debug Options are disabled and I am not sure why? Does anyone know how to configure that or know which component I need to install on the client and on the server?

Is there any documentation I can find on this?

Any advice or tips would be off great help to me.

Thanks,
Kyri

 

[dhecht]

I think interactive debugger requires sp compiled by not linked source residing locally on a workstation in order to see activated dubug pull-downs. That is, the debugger actually requires addressibility to C code on the local workstation. (When sp's are compiled, a C deck is created.)

After starting spb, go to a dos window and run the idebug command. Enter idebug /? to get the options. the -qremotesource option means the source is remote, obviously, and when this is specified, the debug windows will come up; however, you won't be able to set watches or breakpoints, so it's worthless. (-qremotesource isn't listed in the help, but it exists.)

idebug -qdaemon -quiport=nnnnn

I think interactive debugger runs as a daemon and requires a port to listen on or he's simply the listener. If you specify -qdaemon without a port, the daemon won't start.

8000 appears to be the known port for this.

If you don't specify -qremotesource, then windows come up in spb asking for the location of the local source. Once this is specified, the pull downs are activated.

The help text in spb talks about the interactive debugger and there's documentation and presentations on the web, but none of it talks about this. There's also a lot of posting similar to this one.

All said, perhaps it's easier to create a debug table an throw diagnostics out there. There are third-party vendors selling sp debuggers for Oracle but none for z/OS DB2. There could be some selling debuggers for UDB DB2. That's probably be the way to go.