Re: RE: Debug Mode.

Hello  Ramanujam,

In that case I would not use debug, but adapt the programme in such way it 
would send the generated SQL statement to the joblog. So any SQL statement can 
be reviewed.

For instance if you send a *RQS message and immediately receive that message, 
you may retrive the SQL statement on a command line.

Just a thought.

An other option is to start a debug session from another job. In the old OPM 
debug this was quite easy, with the ILE debugger you have to start a service 
job yourself.

Just my $0.02.

Regards.
Carel Teijgeler

======= At 2002-07-02, 13:57:00 you wrote: =======

>Assume that the users can set their WHERE and ORDER BY dynamically at run
>time. And at a given time, they complain that the system is slow. I would
>like to look at the SQL statement that was built by the program based on
>user input. If I could dump that SQL statement into the job log, I can try
>and see why certain indexes are missed/omitted by the optimizer, see if I
>can give the user's an easier way to filter/sort, look at response times..
>and other performance issues. If there was some way to get this info. Only
>when the debug mode is on, then all I need to do is to just start a service
>job and then issue the STRDBG command.

= = = = = = = = = = = = = = = = = = = =