Debugging embedded SQL with ISDB or STRDBG

News/400 had a tech tip on how to debug an SQL program using ISDB or STRDBG
(works for RPG also). The sample CL program to generate a debuggable SQL
program object is at the end of this post.

The problem is we keep our DDS source and program source in two separate
source files. Is there anyway to specify in a CL program to obtain the
program source from QCBLSRC and to obtain the DDS from QDDSSRC? Thanks for
any and all suggestions!

  PGM        PARM(&SRCLIB &SRCFILE &PGM)         
  DCL        VAR(&SRCLIB) TYPE(*CHAR) LEN(10)      
  DCL        VAR(&SRCFILE) TYPE(*CHAR) LEN(10)     
  DCL        VAR(&PGM) TYPE(*CHAR) LEN(10)         
                                                   
  CRTSQLCBL  PGM(&PGM) SRCFILE(&SRCLIB/&SRCFILE) + 
               OPTION(*NOGEN)                      
  CRTCBLPGM  PGM(&PGM) SRCFILE(QTEMP/QSQLTEMP) +   
               OPTION(*SRCDBG)                     
  ENDPGM                                           
******* End of data *******************************
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---